01 OS82121EN80GLA00 Getting Started With NetAct

Version 1 Nokia Solutions and Networks

NetAct 8 Getting Started with NetAct

Legal notice


1 (115)

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Solutions and Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Solutions and Networks training material, are the exclusive property of Nokia Solutions and Networks. Nokia Solutions and Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Solutions and Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Solutions and Networks training material. Individuals can use the Nokia Solutions and Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Solutions and Networks. The Nokia Solutions and Networks training material cannot be used outside of an agreed Nokia Solutions and Networks training session for development of groups without the prior written agreement of Nokia Solutions and Networks.

Indemnity

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document 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 document 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 document 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 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 the document as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT

This document and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The NSN logo 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.

Export Control Marks:

AL: N and ECCN=5E991 or AL: N and ECCN=N (as in TCM course core data)

This course is subject to the European Export Control Restrictions.

Copyright 2014 Nokia Solutions and Networks. All rights reserved.

.

Contents


2 (115)

Contents

1 Nokia Solutions and Networks Operations and Support System 4

1.1 What is NetAct? 5

1.2 iSON Manager iSON Content Packs 6

1.3 Operations on Demand 7

1.4 Multi-vendor support with NetAct Performance Manager, Advanced Monitor and Advanced Configurator 8

1.5 NetAct Service Quality Manager 9

1.6 Serve atOnceTraffica 9

2 NetAct Releases 10

3 NetAct 8 Architecture 11

3.1 Virtualization 12

3.2 Components Overview 14

3.3 Software Environment 16

3.4 NetAct 8 Hardware 18

3.5 Cabinet and Console Solution 19

3.6 System High Availability 21

3.7 Backup 23

4 Interfaces 24

4.1 Mediations and Adaptations 24

4.2 NetAct Interfaces 24

4.3 Southbound interfaces 26

4.4 Northbound interfaces 28

5 Accessing NetAct 42

5.1 NetAct Start Page 43

5.2 NetAct Applications Categories 46

5.3 Administration Category 48

5.4 Deployment Category 51

5.5 Configuration Category 53

5.6 Optimization Category 58

5.7 Monitor Category 60

5.8 Reporting Category 65

5.9 User Assistance Category 70

Contents


3 (115)

5.10 Security Category 72

6 NetAct User Assistance 74

6.1 Operating Documentation 75

6.2 Online Documentation 80

6.3 Rich Media in Operating Documentation 82

6.4 Object Information Browser 84

7 NOLS and My Active SW Support Portal 91

7.1 NOLS 92

7.2 My Active SW Support Portal 96

8 Exercises 102

Exercise 1 104

Exercise 2 105

Exercise 3 107

Exercise 4 108

Exercise 5 109

Exercise 6 110

Exercise 7 111

Exercise 8 112

Nokia Solutions and Networks Operations and Support System


4 (115)

1 Nokia Solutions and Networks Operations and Support System

NSN has an extensive OSS/BSS product portfolio covering all telecom domains from element management layers to service and business management. Key products have been commercially available since 1992, and today over 1.2 billion end-users enjoy services accessed through networks managed by our network management systems.

To address the challenges service providers are today facing on their local and global markets, Nokia Solutions and Networks is developing and renewing its product portfolio to provide topical solutions for operator customers. Telecom business transformation shaping many markets today calls for OSS transformation in a form of a well-designed next-generation OSS. Nokia Solutions and Networks new CIE / OSS products with new architecture fulfill the following expectations:

Ability to support operators business processes by introducing modifiable operator process templates out-of-the-box to enable higher level of automation in many of operators daily routines.

Shared information and data model; enabling OSS level application interoperability through Common Information Models.

Modularity of application architecture, allowing flexible building of solutions based on customer needs. The architecture also provides the openness that allows easy implementation of additional 3rd party applications on top of the platform.

Separation of the application architecture from network element adaptation/mediation layer. Thus, the applications should be built as multi-vendor and multi-technology capable by nature. In practice, this would speed up the rollout of new network elements or functionalities, as new equipment can be implemented and integrated without major changes to the OSS application architecture. Similarly, introducing new OSS functionality can be done independently from managing the network element adaptations.

Common platform for converged OSS solutions, and harmonized software and hardware assets when building these solutions. This harmonization will reduce operators costs on system administration and maintenance, system integration, training and naturally, on the initial infrastructure investments.



5 (115)

1.1 What is NetAct?

As the range of devices and subscriber services continues to grow, new technologies and elements are introduced into the telecom ecosystem. This poses challenges on network management, network services and the business as a whole. Furthermore, an increased number of stand-alone management solutions, producing resource-consuming management processes, as well as many overlapping functions require additional coordination. The key task for any network management system is to provide a coherent and customer-focused view of this multidimensional combination of different networks, network elements and end user services.

NSN NetAct offers a uniform set of efficient tools for radio and core network management. Because it is based on industry standards and has an open architecture, NetAct cuts through the complexity, and helps the operator to manage multi-technology and multivendor networks with one single system. This means reduced administration, maintenance and system integration cost.

With its growing set of automated tools and tasks mapped to operator processes as well as a comprehensive suite of premium, modular applications for managing all network domains, NetAct helps to improve network quality while reducing operational costs. NetAct is a key enabler of self-organizing networks (SON).

The system is designed for smooth evolution from existing to future network technologies. NetAct is highly scalable and can handle not only technology lifecycle requirements, but also network growth and changes in service offering. With NetAct, the operator can protect hardware and software investment, as well as retain existing processes and manage the network with same amount of personnel, when upgrading the network, for example, from WCDMA to LTE. NetAct also supports customer-specific extensions and thus can adapt to operator-specific business processes and needs.

NetAct comprises a common computing platform, an adaptation and mediation layer and an application layer.

NetAct consolidates the views and services available to the network management personnel by moving from a network- and resource-centric approach towards a customer-centric approach. This improves the user experience and ultimately improves quality and saves costs in network management operations.



6 (115)

7 2014 Nokia Solutions and Networks. All rights reserved.

NSN CIE / OSS PortfolioWhat is NetAct?

Fig. 1

1.2 iSON Manager iSON Content Packs

Nokia Solutions and Networks intelligent Self Organising Networks (iSON) is an end to end automation solution adding efficiencies to key operational tasks and processes in radio and core networks. By making the network self-organizing, reacting to changes takes less resources from the network operations center, changes happen faster and reach higher levels of quality.

iSON helps the operator assess the best SON deployment strategies, implement new network elements on a plug and play basis, automatically optimize the networks to adapt and balance itself to changing traffic load and other network conditions and helps the network to heal itself in case of failures.

iSON key components are iSON Radio, Core, Operations and Services.

iSON Manager is an independent platform that gathers PM, CM and FM data from NetAct 8 (given that the corresponding SON functionalities are enabled in NetAct 8) and provides content packs for executing network self-configuration, self-optimization and self-healing. Each content pack includes support for specific end-to-end process for SON, for radio networks or for core networks.

New content packs can be flexibly included in NSN iSON manager based on operator needs.



7 (115)

Some examples of Content Packages for iSON for Radio are: Self Configuration, Self Optimization Mobility, Self Optimization Performance and Self Healing. Examples of content packages for Core are: Dynamic TDM Circuit Balancer, VLR load balancer, LAC based susbscriber balancer, S-GW Balancer, SGSN Pool Balancer. For an updated list of content packages please contact NSN support team.

iSON Manager is an essential part of the NSN iSON solution. It is also possible to mix & match content packs from iSON Manager and Operations on Demand, thus reducing the need for additional hardware.

1.3 Operations on Demand

Operations on Demand (OoD) is a network operations process automation tool, typically working on top of NetAct or, if needed, with direct interfaces to various NSN products such as PaCO Network elements, or Traffica.

OoD simplifies the business process or daily operations by reusing the existing interfaces and building workflows on top that can be run manually or automatically. The product delivery contains process automation execution environment software and Content Packs which then contain the actual process automation and applications to help process simplification. Examples of OoD content packs are Traffic Steering applications and applications to manage elasticity in telco clouds: WiFi Activation Manager (for traffic management) and Network 360.

Network 360 allows fast and accurate network troubleshooting by providing:

Visualization of the NEs failures

Single indicator for NE health

Visualization of NEs of Core, PaCo, ePaCo and Radio 2G,3G, LTE on a GIS (Geographical Information System)

Context sensitive application launches

Interworking with other OoD content packs



8 (115)

1.4 Multi-vendor support with NetAct Performance Manager, Advanced Monitor and Advanced Configurator

NetAct Performance Manager is an umbrella assurance tool for the global Management of the network performance data. NPM Provides long term data warehousing solution and advanced reporting and PM monitoring data functionalities.

NetAct Advanced Monitor is an umbrella assurance tool that provides centralized end-to-end monitoring workflows on a single screen. Due to its open architecture, Advanced Monitor can provide a consolidated end-to-end view of the whole installed base in complex multi-vendor and multi-technology networks. Advanced Monitor utilizes various data sources, each containing valuable information about networks and services.

The following list provides an overview of the areas covered by the Fault Manager NetAct Base Advanced Monitor:

Alarm Enrichment with extra information from external source through 3GPP. SNMP and NE3S.

A library of MVI adaptations with all the major protocols supported.

Optional automatic root cause analysis for IP/MPLS networks based on codebook

Automatic View Generation based on predefined templates.

Intuitive trouble ticket handling supported by standardized OSS/J based trouble ticket client interface.

Direct access to EMS/NEs allowing instantaneous analysis and fault resolution, for example Cell Reset.

Support for cross-domain and connectivity correlation use cases.

Report generation for alarms and correlation metric measurements.

Centralization of FM operations and processes in multi-vendor and multi-technology networks.

Efficient monitoring workflow acceleration with interaction of tools integrated to one desktop framework, for example Trouble Ticket tools.

Full set of fault management applications with high usability and full GUI customization.

Fast fault detection and RCA (Root Cause Analysis) via alarm collection, filtering, processing, advanced correlation, automation and enrichment.

Resource mapping and modeling of connectivity between network elements

NetAct Advanced Configurator is an umbrella fulfillment tool offering a network-level workspace for multi-vendor configuration management tasks. With Advanced Configurator and the tools, the operator can process network-wide configuration management data and and execute network operations and plan network configuration tasks, such as consistency check, network audit or border area adjacency management. Advanced Configurator can integrate to multiple network management systems, through which the operator can access network elements and/or lower-level management systems.



9 (115)

NetAct Advanced Configurator contains vendor-specific data models that describe the network from a certain vendors perspective. The vendor-specific models offer the same adaptation content for configuration management as the lower level systems.

1.5 NetAct Service Quality Manager

Service Quality Manager (SQM) presents a uniform, end-to-end view of the quality of service offered in the network. SQM is multi-vendor and multi-technology capable. The information received from the network enables SQM determine the current service status and service level (calculated by service-specific correlation rules). Examples of such services are voice and data services in 2G and 3G networks.

Service Quality Manager handles service problems according to priority sets for service areas, service types or end-user groups. Prioritization is based on operators business priorities, that is, problems with the operators main revenue-generating services are of high priority.

1.6 Serve atOnceTraffica

Serve atOnce Traffica offers versatile applications for multi-technology customer-centric network and service management by providing subscriber-specific mobile and fixed call, SMS, MMS, GPRS and WCDMA event information.

Traffica shows network traffic and service delivery capability in real time. It extracts information from selected NSN network elements directly or, in multi-vendor networks, it collects signaling information or DPI probes. Traffica visualizes the network traffic both via predefined and user-definable format. The tool also stores records for each call attempt, SMS delivery and packet core event into a database for further use in troubleshooting and customer care.

Traffica provides subscriber-specific information about successful and unsuccessful traffic events, such as subscriber Attach and PDP Context Activation, voice and data calls, as well as SMS deliveries. It also collects information from the network, analyzes the network status and initiates actions that maintain network quality. Traffica can also be used for verifying the effects of corrective actions. For customer care personnel, Traffica provides a unique solution by giving fast access to detailed subscriber activity, as well as root causes of faults in an easy-to-use format. Thus customer complaints can be resolved quicker, which increases customer satisfaction and improves call center efficiency.

Traffica supports different operator processes such as operation and maintenance, network and system management, customer care, service and product development, as well as marketing and customer account management. Traffica can be scaled and has multi-vendor integration ability.

NetAct Releases


10 (115)

2 NetAct Releases Release is normally reserved for platform changes and new features. According to the current NetAct release model, one major release is published per year.

Enhancement Packs (EP) include additional new functionality (minor new features and support for new network elements) and fault corrections.

Each EP replaces the previous one; bugs are fixed in the upcoming EP unless there is no workaround in which case the bug is deployed as a hot fix on installed EP.

Releases need to be purchased separately, and an upgrade fee applies. The upgrade fee includes all the on top Enhancement Packs. Optional functionality always needs to be purchased separately.

NetAct releases are named and numbered as follows:

The first digit in the release number indicates a significant platform change Example: NetAct 8

Minor software releases: Enhancement Packs (EP), for example: NetAct 8 EP1

NetAct 8 Architecture


11 (115)

3 NetAct 8 Architecture The hardware platform of NetAct consists of three main parts, namely servers, storage devices and network equipment, such as switches and routers. NetAct utilizes x86-64-based servers with multicore processors and supports blade solutions. NetAct operating environment is fully virtualized.

NetActs software architecture is three-tiered: the tiers are

Presentation tier

Business logic tier and

Data tier. Business logic and Data tiers are separated from Presentation tier by firewalls and reside inside the secure domain.

Presentation tier hosts client applications. The client applications access Business logic tier and reside typically on a user workstation, for example, a laptop or a desktop computer. The recommended workstation is an office PC with either Windows or Linux operating system.

Business logic tier hosts the business logic and data access specific for NetAct. Data tier hosts NetAct data storages, that is, the database and directory servers. Both Business logic tier and Data tier utilize virtual machines running on one or more host servers dedicated to NetAct.



12 (115)



Fig. 2

3.1 Virtualization

With NetAct 8, we are stepping into a virtualized environment. 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.

The virtualization layer (HW virtualization capability) is provided by the VMware hypervisor. Servers simply add I/O, CPU and RAM computing resources to the HW pool and virtualization provides a logical view of data, computing power, storage capacity and other server resources.

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.



13 (115)


NetAct 8 ArchitectureVirtualization

Fig. 3

3.1.1 Benefits of virtualization in NetAct

Virtualization in NetAct brings the following benefits:

Reduced CAPEX and OPEX by consolidation, for example, improved HW utilization, and the possibility to co-locate NSN products.

Near zero downtime upgrade: Upgrade can be performed by cloning the system within the virtualized infrastructure. Upgrades are performed on the clone side and then after upgrade testing, the clone system becomes the live system.

Zero downtime hardware maintenance and capacity can be added without business impact.

Efficient high availability and disaster avoidance solutions by using shared redundancy resources.

All HW resources are in efficient use: No more fixed amount of physical servers or standby nodes as virtual machines are distributed by load. In addition, decoupling NetAct and 3rd party HW/SW makes HW planning more flexible.

Increased elasticity, in other words, scalability in a virtual environment.



14 (115)

3.1.2 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 machines 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.

3.2 Components Overview

NetAct comprises a common computing platform, an adaptation and mediation layer and an application layer.

NetAct computing platform provides preconfigured 3rd party hardware and software to support the operation of the upper layers. 3rd party software includes components for virtualization infrastructure.

Adaptation and mediation layer provides the interface through which data originating from network elements enters NetAct and can be handled by NetAct applications. It also provides the application layer with services which are not specific to any network management operation, for instance access control and logging.

Application layer contains the applications for common management tasks, such as fault management, configuration management, performance management and network optimization. Applications are accessible via user workstations. Depending on the operators installation, the tools allow management of part or all of the network domains.

Computing Platform

Hardware Servers, network equipment and storage devices

IT Software Operating System, J2EE Server, J2SE/JRE, JBI Server, Perl, Authentication, Database, Directory Server, File System Access, IP Connectivity, Start-up, Scheduling, Backup and Restore, Process Supervision, OSI Connectivity, CORBA Connectivity, Messaging Backbone and System Deployment

OSS Application Platform

System Services Authorization, Credential Access, Certificate Access, Data Access, Data Logging, License Access, Scheduling, Documentation Access, Preferences, Java UI Framework, Web UI Framework and Common Message Bus.



15 (115)

Common OSS components

Fault Management: Event collecting, Event processing, Event monitoring, Event post-processing, Event forwarding, FM administration.

Configuration Management: Basic CM, NE hardware management, NE software management, NE license management. NE remote backup.

Performance Management: Measurement collecting, Measurement processing, Measurement visualization, Measurement post-processing, Measurement forwarding, Measurement administration, PM administration.

Security Management: User account management, User group management, User permission management, NE account management, NE access control, User activity monitoring.

System Management: System monitoring, On-line documentation GUI, Time management, Backup and restore GUI

Mediations: Fault management, Configuration management, Performance management, Security management.

Adaptation Management: Generic adaptation deployment interfaces.

Mediation Framework: Common tools and definitions for mediation implementation.

OSS Applications

Domain-specific application - Applications and adaptations for Core and Radio networks.

Domain-agnostic applications - Service Management applications.


NetAct 8 ArchitectureProduct Structure

Computing Platform

OSS Application Platform

OSS Applications

Common OSS Components

Fault

Management

Configuration

Management

Performance

Management

Security

Management

Adaptation Management

Mediation

Tools

System

Management

System Services

IT Software

Hardware

Common CM Services

Domain-specific ApplicationsDomain-agnostic Applications

System components

Fig. 4



16 (115)

3.3 Software Environment

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.

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

Function Software Used

Operating System RedHat Enterprise Linux (RHEL) version 6.5 on NetAct VMs, SuSe Linux for VCA and VDP and Windows Server 2008 for Node Managers.

Database Oracle Enterprise Edition Version 11R2

Application Server WebSphere Application Server (WAS) version 8.0

Load Balancer LINUX Virtual Server (LVS) provided by RHEL

Business Logic J2EE Version 1.4

JBI Server Apache ServiceMix 3.4

Java JRE Version 7 for apps and JRE 1.5 for WAS

Virtualization VMware vSphere Enterprise Plus 5.5 and VMware vCenter Server Standard for vSphere 5.5

Perl Version 5.8

ESPER 3.5.0

Authentication/ Directory Server

LDAP Version 3 / RedHat Directory Server provided by RHEL 6.4

File System NFS Version 3 provided by RHEL 6.4

OSI Stack Marben

IP Connectivity FTP, NFS, SSH, HTTP, SNMP, NTP, BIND and DNS protocols, provided by RHEL



17 (115)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


NetAct 8 ArchitectureSoftware environment

Operating System: RHEL 6.5

IP Connectivity: FTP, NFS, SSH, HTTP, SNMP, NTP, BIND and DNS protocols

Directory Server: RHDS 9.0

Database: Oracle Enterprise Edition 11G R 11.2.0.3.0

Java: JRE 6 for applications & JRE 1.5 for WebSphere

Business Logic:

J2EE version 4

JBI Server:

Apache Service Mix 3.4

Perl:

Version 5.8.8

Application Server: IBM WebSphere version 8.0

Load Balancer: LINUX Virtual Server (LVS)

ESPER:

Version 3.5.0

Virtualization components

vCenter: VMware vCenter Server Standard for vSphere Plus 5.5

vSphere: VMware vSphere Enterprise Plus 5.5

Hypervisor: EXSi Linux: SuSe

File System: NFS version 3Windows Server:

2008R2

Fig. 5



18 (115)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4 NetAct 8 Hardware

NetAct 8 system provides the following Hardware Units:


NetAct 8 ArchitectureHardware Components

Cabinet solution

Console solution

Servers

Storage

DCN Switches

DCN Routers

DCN Firewalls

Backup solution

HW components:

Fig. 6



19 (115)

3.5 Cabinet and Console Solution

Product Model Notes

Cabinet

alternatives

1,2m HP10622G2 with 2x16Amps PDUs Max two blade chassis per cabinet *)

1,6m HP10636G2 with 4x16Amps PDUs Max two blade chassis per cabinet *)

2m HP 10642G2 with 4x16Amps PDUs Max two blade chassis per cabinet*)

HP seismic cabinet Only on request

Customers own 19 industry standard, full deep cabinet Open Cabinet concept

Console HP TFT7600 flat panel Common console solution

DVD External 16xSATA DVD-ROM drive in StorageWorks 1U USB rack

USB connection

In the figure below there is an example of the rack mounting for NetAct:


NetAct 8 ArchitectureHardware: Rack mounting Example

*) recommendation

Primary Storage solution

(space depends on model)

(7 EIA)

Flat panel (1 EIA)

Rack 42U

HP C7000 blade chassis

( 10 EIA)

L2-Switch (1 EIA)

L2-Switch (1 EIA)

Router (2-3 EIA)

Router (2-3 EIA)

DVD drive (1-2 EIA)

Blade Solution:

Blade chassis with

Blade servers

Console solution:

Flat panel + DVD

DCN solution:

2x external LAN +

2x routers

Backup Storage solution

(space depends on model)

(4 EIA)

Storage solution:

Primary + Backup

storage

Fig. 7



20 (115)

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

NetAct Configuration

Server Model No. of Blades

Storage System

Small 22 VMs

HP BL460c G8

1x Intel E5-2658 six core processor,

32GB memory,

2x300GB 15K SAS internal disks

2x10GbE LAN; fc controller (8G)

4

VNX Small.

VNX5300: 13x300GB SAS + 7x2TB NL-SAS

Mainstream 31 VMs

HP BL460c G8

2x Intel E5-2620 six core processor

64GB memory,

2x300GB 15K SAS internal disks,


6

VNX Medium

VNX5300: 17x300GB SAS + 9x2TB NL-SAS + 2x100GB SSD

Large 39 VMs

HP BL460c G8

2x Intel E5-2658 eight core processor

128GB memory,

2x300GB 15K SAS internal disks,


6

VNX Large

VNX5300: 25x300GB SAS + 13x2TB NL-SAS + 5x100GB SSD


NetAct 8 ArchitectureHardware: Server Blades

Blade chassis

C7000, 16 slots

SAN blade switch

LAN blade switch

Blade chassis

Front Back

Blade servers

BL460c

HP C7000 blade chassis with blade servers

Power units

Fig. 8



21 (115)

3.6 System High Availability

System reliability refers to all features included in NetAct platform that facilitate high availability and disaster avoidance of the NetAct system. The following chapters explain the concepts and solutions in more detail.

High availability aims to eliminate single points of failure (power supply, disk space, CPU, software or connectivity) by introducting redundancy of in software and hardware components.

Connections between any two servers and inside the storage system are built to incorporate redundancy, that is, there always are two independent paths between any two components in a virtualized cluster. The same principle applies also to routers and firewalls. High availability guarantees that critical resources are available for NetAct operations even in failover situations.

Load balancing concerns other server configurations than single server configuration. In multi-server configuration, load balancing ensures that server load is distributed among the servers in an application server cluster. Automatic load balancing is not used on the data tier, but balances traffic on the application.

The following lists the HA mechanisms in use in NetAct:

Virtual Machine (VM/guest) availability monitored by Virtual Infrastructure Manager

Service availability monitored on guest System by Watchdog

J2EE Application availability guaranteed with WebSphere cluster

Automatic restart of failed application or virtual machine in case of application or guest failure

Priorities and VM startup order

Redundant HW components: Running NetAct node (VM) can be relocated to another physical server online

There is no service interruption for end users



22 (115)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Blade chassis

Virtual Infrastructure

8G8G

2 x Brocade 8/242 x VC Flex10

8G8G

1G 1G 1G 1G

1/10G1/10G

8G 8G

1

Service availability within virtual machine via watchdog

Watchdog availability

via virtual manager

Virtual machine availability via hypervisors

Server and network interface availability via redundancy

DCN availability via redundancy

Storage area network

availability via redundant

connections

NetAct 8 Architecture High Availability

2

3

4

1

2

3

4

5

6

56

Fig. 9



23 (115)

3.7 Backup

NetAct offers both an online backup and an offline disk-based backup of the file system and databases. Online backups are taken while the system is up and running and are automatically scheduled. Offline backup is taken when the database is not running, typically after the installation of the database or when changes requiring a shutdown have been performed, also before an upgrade. The backup disk can either be part of the online disk storage or located on separate backup disk storage.

NetActs open backup interface enables operators to build their own or use a third-party backup solution. However, using a custom-made or a 3rd party backup solution requires that the chosen solution is compatible with the other software components installed on the NetAct cluster and does not interfere with NetAct integrity. Furthermore, it must be ensured that there is enough processing capability and data storage available for the custom-made or 3rd party backup solution.

Interfaces


24 (115)

4 Interfaces

4.1 Mediations and Adaptations

The support for network elements is divided into mediations and adaptations.

Mediations are responsible for the conversion of the network element interface to the NetAct internal format. Mediations are, in most cases, network technology independent. Mediations hide different network element interfaces from applications. Applications can thus concentrate on processing relevant data, and do not need to take into account different protocols (for example SNMP, http, or Q3) and data formats (for example ASCII, or XML).

An adaptation is software that adapts NetAct System applications for a certain vendors network technology. Technically, an adaptation configures the user interfaces, database, mediation, business rules, etc. Adaptations introduce all the information to NetAct that is specific for a certain network element type and release.

4.2 NetAct Interfaces

In NetAct, interface-related issues are very important, since dependencies are controlled via interfaces, and controlled dependencies are a key enabler of modularity - an important property of the NetAct 8 architecture.

NetAct can be integrated into external systems via northbound interfaces. External systems are employed for similar monitoring, reporting and network planning tasks as NetAct, but at a higher abstraction level. These higher-level systems can be either NSN or third-party management systems.

Lower-level systems or network elements can be integrated into NetAct via southbound interfaces. Again, these lower-level systems can be either NSN or third-party element management systems.

Mediations are responsible for the interworking or conversion between the protocols or data formats used in the lower-level or higher-level systems and the protocols or data formats used in the NetAct system.

Protocols used in the lower-level or higher-level systems are, for instance, SNMP, SOAP or HTTP, and data formats are, for instance, ASCII or XML

Interfaces


25 (115)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


NetAct InterfacesNorthbound and Southbound

Integrate NetAct with Service Management

systems

Lower-level Systems / Network Elements

Southbound Mediations

NetAct Applications and Services

Northbound Mediations

Higher-level Systems

NetAct 8

Northbound Interfaces

Southbound Interfaces

Lower-level systems can be either NSN or 3rd

party Element Management Systems or

Mediators

Higher-level systems can be either NSN or 3rd

party Network Management Systems

Fig. 10

Interfaces


26 (115)

4.3 Southbound interfaces

NetAct supports a set of transport and application protocols as well as provides Integration SDK to integrate and manage 3rd party network elements and element management systems (EMS). Integration to a 3rd party network element or EMS involves the creation of mediation and adaptation. The mediation converts the interface protocol and data model exposed by the 3rd party system to the NetAct internal data model and the adaptation models the resources of the 3rd party system.

The transport and application protocols supported by NetAct for integrating with 3rd party systems are UDP, SSH, FTP, SFTP, HTTP, SNMP (v1, v2c, v3), CORBA, EJB, JDBC, and SOAP.

In the next tables there is a description of the supported functionalities and corresponding network elements.

Supported Network Elements Supported Functions

Flexi NG

Flexi NS

MGW

NEBR

NT HLRFE

One-NDS

Open MGW

PCS-5000

AoM

Audit Trail

Basic Configuration Management (topology)

CM

FM

HW Management

PM

SW Management

User Management

CMD

FIU 19E

Flexi ISN

Flexi NG 2.0

Flexi NG 2.1

FTFA

LIG

NBG / Flexi Content Optimizer

PowerHopper Vario

Q1 Agent

Tellabs SR5.0

Traffica

AoM

FM

PM

Interfaces


27 (115)

Supported Network Elements

Used for

AXC

Femto BTS

Flexi Direct

Flexi LTE BTS

Flexi WCDMABTS

McRNC

NEMU

OMU

RNC

Ultra BTS

AoM

Certificate management

CM

FM

HW Management

Integration Data Upload

License Management

PM

SW Management

System Level Trace (events)

User log Management (audit Trail)

User Management

CDS

HLR

MSC

FM

PM

System Level Trace Management

BSS

Flexi NS

Flexi NS SGSN

AoM

Audit Trail

Backup and Restore

CM

Element Management

FM

License Management

Network Element User Management

PM

SW Management

System Level Trace (events)

Time Management

Cisco IOS

Cisco XE

Cisco XR

Infoblox DNS

Juniper JUNOS

LIG

NetViewer

TP5000

Basic Configuration Management (topology)

FM

PM

Interfaces


28 (115)

4.4 Northbound interfaces

Northbound interfaces provide a means to integrate NetAct to 3rd party upper level management systems. Many of the interfaces can be utilized equally well with NetAct and umbrella management system tools.

The 3GPP Rel6 CORBA FM northbound interface is a 3GPP standard compliant interface used for exchanging topology and alarm information.

The SNMP northbound interface provides SNMP v2c and SNMP v3 based alarm forwarding and alarm uploading functionality with filtering capabilities. Cancel and acknowledge operations of alarms can be invoked from upper level management systems. The interface supports both network alarms and NetAct internal alarms.

The ASCII Alarm Forwarding interface provides the capability for continuous alarm information forwarding from NetAct to external systems in ASCII format using common TCP/IP and UNIX services. The ASCII Alarm Forwarding interface supports all alarms collected by NetAct as well as the alarms generated by the NetAct self-monitoring application.

The XML (OMeS) Based Measurement Data Export interface is a solution for publishing performance management data in OMeS format for upper level management systems. OMeS is an XML based NSN proprietary format for specifying measurement data.

The 3GPP XML Format PM Northbound interface exports raw measurement data in 3GPP formatted XML files to external systems. FTIRP is supported, and FTP or sFTP can be used for transferring performance management files. The interface is applicable for all PM supported network elements managed by NetAct.

The OSS/J Trouble Ticket Client interface can be used to integrate 3rd party trouble ticket systems with NetAct. After the integration it is possible to create, modify, view or close trouble tickets from NetAct Monitor desktop.

The 3GPP Rel6 BulkCM Northbound interface is a 3GPP compliant interface for configuration management data upload, download and configuration management operations. The interface supports WCDMA and LTE.

The TMF615 Unified User Management interface is a standard solution for integrating NetAct to external central user management systems. It centrally facilitates management of users and their access rights for all OSS systems.

The XML Based Inventory Data Export interface exports hardware inventory data in XML formatted files to be transmitted to external systems. 3GPP FTIRP is supported, and FTP or sFTP can be used for transferring performance management files.

The XML/CSV Planning Data and Hardware Inventory Data File interfaces are solutions for exporting configuration management planning data and hardware inventory data in XML/CSV formatted files.

The Email Alarm Forwarding NBI is an interface for forwarding alarm events to external systems in specific e-mail format.

Interfaces


29 (115)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview

NetAct Open Northbound Interfaces

FM northbound interfaces:

3GPP Rel6 CORBA FM NBI

ASCII Alarm Forwarding NBI

SNMP NBI

PM northbound interfaces:

XML (OMeS) Based Measurement Data Export

3GPP XML Format PM NBI

CM northbound interfaces:

3GPP Rel6 CORBA BulkCM NBI

XML/CSV Interface for Planning Data

Inventory northbound interface:

XML Based Inventory Data Export

Other northbound interfaces:

OSS/J Trouble Ticket Client Interface

Email Alarm Forwarding NBI

TMF615 Unified User Management Interface

Fig. 11

Interfaces


30 (115)

4.4.1 3GPP Rel6 Corba FM and PM interface

The 3GPP CORBA Northbound interface is part of the NetAct open interfaces concept. This northbound, 3GPP-compliant interface is used for exchanging alarm information and performance information between NetAct and external systems, for example, a third-party system. The interface complies with 3GPP Fault Management requirements v6.0.0, Performance measurement XML file format definition v10.0.0 and File Transfer (FT) Integration Reference Point (IRP) v10.0.0.

In addition to fault management and performance management, this interface also supports basic configuration management. It provides the following functionality in detail:

Alarm upload for alarm synchronization.

Spontaneous alarm notifications for new alarms, acknowledged alarms, and cleared alarms.

Alarms can be acknowledged through the open interface by the external system.

Flexible alarm filtering capabilities for alarm upload.

Configurable filter for notifications set by external system at subscription time.

Query information about the available PM XML files ready to be uploaded.

Receiving notifyFileReady notification when at least one new PM data file is ready for uploading.

Receiving notifyFilePreparationError notification in case an error occurs during the PM data file preparation.

External systems can use FTP (secure File Transfer Protocol) or sFTP (security File Transfer Protocol) to upload the available 3GPP compliant PM XML files through this interface.

Interfaces


31 (115)


Interface for forwarding alarm event notifications to external systems via CORBA interface

Functionality covers alarm upload, alarm notification and co-operative alarm acknowledgement

NetAct internal alarms are supported

Basic CM (topology / containment upload and object lifecycle notifications) functionality is also covered

Alarm event notifications can be filtered (client NMS specifies a notification filter at subscription)

Supports communication surveillance between the NetAct CORBA agent and the external NMS manager

Supports multiple client NMSs

Compliant to 3GPP Fault Management release 6 (TS32.111-3) and relevant references

3GPP Rel6 CORBA FM NBI


Alarm Notification

Alarm Upload

Alarm Ack/Cancel

Basic CM Notification

Basic CM Upload

Flexible Filtering

Multi-NMS Support


Interface for transferring measurement data to external systems.

Applicable for all PM supported Network Elements managed by NetAct

The supported 3GPP XML schema does not use the optional positioning attributes on measurement types and results

[3GPP TS 32.435 v10.0.0]

Comply with 3GPP file naming convention

FTIRP is implemented, and used NotificationIRP, CSIRP, EPIRP provided by 3GPP CORBA NBI

File transmitted using FTP or sFTP

3GPP XML Format PM NBI


File Based

XML (3GPP) Format

File Transfer IRP

Fig. 12

Interfaces


32 (115)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.2 3GPP Rel6 CORBA Bulk CM NBI


For WCDMA / LTE (and TD-LTE) technology

Support for all CM parameters

Interface implementation based on (and compliant with) 3GPP Bulk CM standard release 6, CORBA solution set

Information model adapted to respective 3GPP release 6 and release 8 standards

3GPP Rel6 CORBA Bulk CM NBI


CM Upload

CM Download

CM Activation

Other CM Operations

Fig. 13

Interfaces


33 (115)

4.4.3 ASCII Alarm Forwarding

ASCII Alarm Forwarding Northbound Interface (ASCII Alarm Forwarding NBI) is a solution for sending alarm information from Nokia Siemens Networks NetAct to external system in ASCII format using TCP/IP.

It provides the following functions:

Alarm notifications for multiple external systems.

Alarm upload for multiple external systems.

Filtering capability for alarm notifications and alarm upload.

Configurable alarm format.


Socket interface for forwarding alarms event notifications to external systems in ASCII format

Alarms from all network elements supported by NetAct are forwarded

NetAct internal alarms are forwarded

Retry re-establish in case of socket connection loss

Format of forwarded alarms is configurable

Filtering rules can be defined to specify the kind of alarms forwarded

Supports alarm upload operation by re-sending all active alarms (activated from user interface)

Supports multiple client NMSs

ASCII Alarm Forwarding NBI


Alarm Notification

Alarm Upload

Filtering

Multi-NMS Support

Fig. 14

Interfaces


34 (115)

4.4.4 SNMP Northbound Interface

SNMP Northbound Interface is an interface for mediating fault management data. It facilitates an easy integration of NetAct and 3rd party equipment in a multi-vendor environment, and provides a unified network management view of interface technologies.

The main purposes of the interface are:

Supporting fault management related supervision of network elements in different domains and technologies.

Supporting request and response interaction for the management information.

Supporting spontaneous event notifications.

Identifying the physical or logical fault network resource of a generic, domain, and technology independent alarm in the entire managed network.


Interface for forwarding alarm events to external systems via SNMP traps

Functionality covers alarm notification, alarm synchronization and alarm cancel operation.

NetAct internal alarms are supported

Support of forwarding notifications to multiple upper-level Network Management Systems

Capability of setting and updating filtering criteria for the alarm notifications forwarded.

Event reporting reliability (including lost trap retrieval)

Compliant with SNMP v2c and SNMP v3

2/11/2014 Document ID / v. 0.1 / Life cycle status / Dept. / Author

SNMP NBI


Alarm Notification

Alarm Upload

Alarm Ack/Cancel

Filtering

Multi-NMS Support

Trap Retransmission

Fig. 15

Interfaces


35 (115)

4.4.5 PM North Mediation Interface

PM NMI (Performance Management North Mediation Interface) is a solution for publishing PM (Performance Management) data in OMeS (Open Measurement Standard) format. With PM NMI, it is possible to transfer PM data to an external system. In OMeS, data export and file transfer are based on an advanced XML format.

The main advantages of the interface are:

The OMeS file format exported through the interface allows the use of universal tools with XML support. This enables easy and cost-effective integration of any external system to NetAct.

The rule-specific filtering function avoids transferring irrelevant PM data to the external system.

Third-party integrations do not cause extra load on the performance database. The capacity of NetAct is thus ensured in all circumstances.


Interface for transferring raw measurement data to external systems

Performance data is exported in OMeS formatted XML files

Network technology independent

Filtering supported to specify PM data to be exported

File transmitted using FTP or sFTP

PM North Mediation Interface: XML (OMeS) Measurement Data Export


File Based

XML (OMeS) Format

Filtering

Multi-NMS Support

Open Measurement Standard (OMeS) is a Nokia Solutions Networks standard.

According to OMeS, the files are transferred in XML format. In NetAct, the PM

data is transferred over the north and south mediation interfaces in OMeS format.

Fig. 16

Interfaces


36 (115)

4.4.6 XML Interface for Configuration Management Data

This interface is used for exchanging network configuration data with other planning systems. The file format is a markup language for configuration management, RAML, which is based on XML. The current supported versions of the mark-up language are RAML/CM2.0 and CM2.1.

Nokia Siemens Networks provides schemas for validating RAML/CM2.0 and CM2.1 files. However, the schemas can only be used to check the generic file structure. They cannot be used to validate parameter names and values.

The managed objects and parameters that need to be imported with the XML file or exported to an XML file are defined with a profile. Nokia Siemens Networks provides ready-made profiles, for example, for site creation and adjacency management tasks. The user can also create own profiles using an external text or XML editor.

There are four different types of configuration data files that can be transferred over the interface:

Actual configuration

An actual configuration contains the actual configuration of a certain network area. Actuals are transferred to the planning system to make sure that the future plans are based on the actual network configuration.

New configuration

A New configuration contains a new configuration plan which is planned to be provision into the network.

Reference

A reference configuration contains all objects and parameters of the network in their intended optimal configuration, as well as modifications planned for the (immediate) future.

Template

Templates define a collection of parameter values for a particular managed object class. They are used for two purposes:

They define managed object parameters for new planned (CREATE) managed objects that define how the object should behave. Parameter values in plans override the corresponding value provided by the assigned template.

They identify the objects type: for example, pico, micro, and macro for BTS. This can be used as object classification or assigning templates for related managed objects. For this purpose, the template can be assigned both for new planned (CREATE) and existing actual managed objects.

There are two types of templates:

System templates

There is a single system template supporting the latest network element version for each managed object class. The system template values are defined according to the latest release of the network element. Versioning of templates is not supported in system templates. These templates are provided as part of NetAct Configurator and they cannot be edited by users.

Interfaces


37 (115)

User templates

A managed object class can have multiple user templates or no user template. A user template only contains values that differ from the system template, as the system template is always automatically used under the user template to provide all missing values.

4.4.7 CSV Interface for Configuration Management Data

This interface is used for exchanging network configuration data with other planning systems. The format of the configuration data is CSV (comma-separated value). A CSV file is an ASCII (that is, plain text) representation of spreadsheet data. In NetAct Configurator, a CSV file contains data that represents the managed objects in the network. Data in CSV format can be used in exporting actual configurations, importing and exporting plans and site information.

The managed objects and parameters that need to be imported with the CSV file or exported to a CSV file are pre-defined in an open, well-described fixed format.

There are four different types of conf

01 OS82121EN80GLA00 Getting Started With NetAct

Documents

Transcript of 01 OS82121EN80GLA00 Getting Started With NetAct