introduction to netact

1 © Nokia Siemens Networks CN3401IEN40GLA3

NetAct Basics

The complexity of mobile services and technologies is increasing day by day. Hence, there are more and more terminal variations, diverse services and technologies and elements in the delivery chain. All these technologies are connected to a single network management system, the NetAct framework.

Netact Cluster

GSM 3G

CoreRadioR4

…


/

Benefits

NetAct has the following benefits:

• It allows seamless management of different network technologies with integrated and interworking tools.

• It controls costs while redeploying competencies and resources from 2G to 3G.

• It allows all network element failures, service quality indicators and entire traffic to be visible on a single screen.

• It allows multi-vendor capability with its open interfaces and multi-vendor integrations.


/

NetAct Clusters


/

NetAct OSS 5.1 Architecture

J2EE cellJ2EE cell

Dara Storage cellDara Storage cell

GUI cellGUI cell

User WorkstationsUser Workstations

Windows Linux

Net

Act

Sec

ure

Dom

ain

Net

Act

Sec

ure

Dom

ain

Linux LinuxNetwork Elements / Managed Network

FIREWALL

Database / Linux

User workstations / Tier 1

NAS Layer / Tier 2

DSS Layer / Tier 3

Connectivity cellConnectivity cell

Linux

NAS = NetAct Application Servers

DSS = Data Storage Subsystem

Backup device

SAN/FC switch

Disk Array

Storage


/

Server Types in NetAct


/

NetAct Hardware: Blade Servers

rackshelf

Server-blade


/

Reporting

NetAct Reporting features:

• Provides efficient capturing, analyzing and displaying of all performance data in the network.

• Helps to understand and enhance the network behavior.

• Provides multi-technology views.

• Collects and stores performance and quality information from the network and services.

• Provides drill-down functions from higher to lower network level.

• Produces reports for O&M, analysis and long-term planning.


/

Reporting flow


/

Monitoring

NetAct monitors the entire network for failures and messages at various levels.

The network monitoring process covers the following areas of the operator’s routine tasks:


/

Monitoring process


/

Configuring

NetAct Configuring uses tools like:

• CM Editor

• CM Analyzer

• CM Operation Manager

• others


/

Configuring

Application Server

Database

Unix Client

CM Editor

CM Analyser

CM Operation Manager

Configurator

Actuals Plans


/

Main Functions

The main functionalities of Configurator are:

• Uploading and storing the network parameters.

• Data exchange with external tools.

• Setting, modifying, viewing, and comparing network configuration data.

• Support offline network planning.

• Automatic provisioning of network plans.

• Mass modifications on the network.


/

NetAct Configurator


/

Overview of CM3 for core networks• Offers comprehensive feature set for configuration management of

MSS and MGW (R4 NE)• Three major CM components – CM Editor, CM Operational Manager, CM

Analyzer• Tasks include uploads, preparing plans, management of plans and

provisioning

Through upload, configure and provision, the majority of use cases in daily operations can efficiently be covered such as

• Configuration of International Roaming Partners • Configuration of PCM links • Modification of cell-related data on MSC • Extension / modification of signaling network • Modification of Code Point routing • Modification of Destination Point Codes • Modification of Global Title addresses • Adaptation of ATM bandwidth


/

CM Editor

• Configuration Visualization

• Plan Management

• Template Management

• Search & Modify

• User Interface Customization

• Send to Network for 2G & 3G

• Management of Routing Areas


/

CM Operations Manager

• Importing & Exporting

• Plan & Template Management

• Plan Provisioning

• Configuration Upload

• Plan Actual Compare

• 3G Rehosting

• MML Command Visualization for R4 Core


/

CM Analyser

• Checking Radio Network Parameters and Managed Objects

• Checking for discrepancies

• Auto-correction


/

Configurator CoreUse Case Examples

MSS configuration use cases

• Destinations (incl. signaling, routing, digit analysis)

• Iu-Cs interface via MGW towards RNC (with IP signaling, radio parameters)

• A interface via MGW towards BSC (with IP signaling, radio parameters)

• SIGTRAN towards MGW (incl. association, IP signaling)

• Special routes (HLR interrogation, GSM traffic termination, inter-MSC handover)

• Nc interface towards another MSS (with association, IP signaling, BICC, SCCP)

• Roaming agreements (PLMN parameters, IMSI analysis)

MGW configuration use cases• Destinations (incl. signaling, routing with load sharing, digit analysis)• A interface towards BSC (signaling, routing, virtual MGW)• Mc interface towards MSS (virtual MGW)• PSTN interface (TDM signaling, TDM user plane, routing)• H.248 protocol towards MSS (virtual MGW)• SCCP service with subsystems


/

ROU-156

ROU-157

DIGITA-7088

Altern

ative

rout

e

60%

of t

he tr

affic

Alternative route

40% of the

traffic

ROU-155

SDEST-155

TREE-4500

Primary route MSC Tampere

MSC Turku

Existing route

Existin

g ro

uteCGR

TONES

MSC Mira

MSC Helsinki

DEST-155

SDEST-156

SDEST-157

Existing object

New object

ROU - Route SDEST - Subdestination TREE - Analysis tree

DEST - Destination CGR - Circuit group DIGITA - Analysis digits

Use Case: Create Alternative Routing


/

Network Plan - Create Alternative Routing


/

Provisioning dialog in CM Operations Manager

introduction to netact

Documents