1 System Architecture

7/26/2019 1 System Architecture

1/22

Alcatel University - 3FL 41022 AAAA WBZZA Ed. 02 November 2004 Page 1.1

Alcatel University 3FL 41022 AAAA WBZZA Ed. 02 November 20041.1

1 SYSTEM ARCHITECTURE


2/22


1.2

1 System ArchitectureSession presentation

Objectives: to be able to

describe the interaction between the 1353NM

and the 1354RM

describe the system architecture

Program:

1.1 NR7 TMN description

1.2 Functional Management Domains

1.3 System architecture


3/22




1.1 NR7 TMN description


4/22


1.4

1.1 NR7 TMN descriptionLayers

Interface

IOO

NML 1354RM

OPTIC-IM / SEN-IM

EML 1353NM

QB3*/Q2

NE

1320NXNECTAS

1320

CTECT

DXC 4/3/1

DXC 6/4

ADM/LS/OA

WDM/MW

W

PDH

ADM

SR

W PDH

ATM

OMSN

WDM

DXC

CT

NECTAS

CT

Q3Q3Q3 QB3* SNMP

FF F

NE Network Element

PDH or SDH Transmission equipment.

TNTelecommunication Network This network is made of interconnected NEs . It represents the physical media ensuring the

transmission function ( e.g.: STM16 ring made of 1660SM OMSNs).

EML Element Management Layer

The whole NE configuration can be managed from this layer on an individual basis: hardware, cross-connections, synchronisation, protections, alarms, performance...

The Alcatel NR7 EML layer is made of 1353NM (centralised system) and Craft Terminals (localmanagement. E.g: 1320NX and 1320CT).

NML Network Management Layer

The system belonging to this layer allows the operators to manage connectivity, routing (trails andpaths) and the relevant protections in various topologies. Furthermore the NML is in charge ofNetwork Alarms and Performance Monitoring.

The Alcatel NR6 NML layer is made of 1354RM6 (centralised system) . TMN Telecommunication Management Network

This management network is made of 5 layers. Only EML and NML are referred in this document.


5/22


1.5

1.1 NR7 TMN descriptionInterfaces

1354RM is able to manage QB3* NEs and Q3 NEs by using :

SEN-IM protocol to manage QB3* type NEs through a MIB located into

the 1353NM system.

OPTIC-IM protocol to manage Q3 type NEs such as OMSNs. In thiscase, 1354RM has to interact directly with these NEs because of the

relevant MIB-less structure of the 1353NM.

The 1354RM operator will have to take into account these two

types of interfaces when performing alignment operation (e.g.:

consistency check and download enable / disable).


6/22




1.2 Functional Management Domains


7/22


1.7

1.2 Functional Management DomainsEML and NML Functional Domains

Functions

Layers

Configurationmanagement

Faultmanagement

Performancemanagement

Security andAdministration

NML1st

level

1354RM

Nodes (note 1)

Physicalconnections

MS-trailsHO-trails

Nodes (note 1)

PhysicalconnectionsMS-trailsHO-trailsPaths

HO-trails

Paths Backup / restoreProcess

monitoring

EML

1353NM

NE AddressHardware unitsEPS schemesSynchronisation

Cross(note4)

Alarm monitoring:HardwareSynchronisationMSPSDH functionalblocks

RegenerationsectionMultiplex sectionHO and LO TPs(note 3)

Backup / restore

Process

monitoring

(note 2)Paths

Protection schemes

connections

Note 1: Nodes represent NEs in the Network topology at the 1354RM level.

Note 2: HO-Trails and Paths are shown at the 1353NM level as Cross-Connections sets.

Note 3: Only data monitoring of HO and LO TPs is allowed when the NEs are under 1354RM control. Therelevant Performance Monitoring has to be started from the RM application. Performance Monitoring of RSand MS is fully manage from the 1353NM application.

Note 4 : Cross connection creation can not be done from 1353NM when the NEs are under 1354RMcontrol. They can only be inspected.

All Protection schemes but EPS are managed from 1354RM


8/22


1.8

1.2 Functional Management DomainsExamples of Network Configuration (1/3)

STM-4

STM-1

STM-1 STM-4

STM-1

STM-16

STM-4

STM-1

Linear chain

Interconnected rings

2F MS-SPRING

Cross connects

ADMs or OMSNs

1641SX 1641SX

SNCP ring

Interconnected rings


9/22


1.9


RM operator operates from the Browser. The Network View interface isintegrated in the Browser.

Network layers (network, sub networks) according to G803/G805.

Upload of EMLs, NEs for each 1353NM system in order to create relevant

Nodes. Not managed NEs replaced by created External Network References .

Physical connections declared by the RM operator.

Insert /remove NE from topologies

Topologies are provided to partition the Network

Network Protection Architecture (NPA) are provided to implement the neededprotection level:

SNCP, 2F / 4F- MS-SPRING , MSP 1+1, MSP 1:N

1354RM system provides facilities to modify a Network topology without trafficaffecting at TN level. In this case the operator will have to perform commandssuch as download disable / enable, consistency check and MIB audit. Theway to make it is described in the administration training.


10/22


1.10


Manual and automatic life cycles of HO-Trails and Paths.

Network resources can be assigned as constraints sets.

Protections mechanisms according to NEs features:

SNCP HO-trails or paths, Drop and Continue

2F / 4F- MS-SPRING.

MSP 1+1 or 1:N

Restoration rules can be defined and assigned to HO-Trails or HO-Paths.

Current status of the protections schemes can be forced.

Join and Split of existing HO-Trails and Paths.

Join and Split physical connections to insert new NEs in topology

Loop back management at NAP, C12 and CTP level AU4 concatenation and relevant Paths

ATM, Ethernet and SNMP paths management


11/22


1.11

1.2 Functional Management DomainsFault Management

Alarm

Network view

Browser

1354RM

AS1330

Network

EML elementary alarm notifications processed by 1354RM in order to detect the impacted NML entities.

Management of Network Alarms related to Physical Link Connections, MS-Trails, HO-Trails, Paths and thecorresponding optical trails and paths, EML and NEs.

Separated in service /all alarm list for Physical connections, path , trails (also optical).

Network alarms correlated to default ASAPS.

Possibility to modify the default ASAP

Alarm events shown in different applications:

Browser and AS1330 and Network view

Current and historical alarms records managed separately.

Customisation of AS1330.

Q3 NEs (eg:OMSNs) ASAP managed from 1354RM according to the lifecycle of relevant HO-Trails andPaths (manually or automatically).


12/22


1.12

1.2 Functional Management DomainsPerformance Management viewer

Performance Monitoring based on created measures.

Only HO-Trails and Paths entities can be correlated to these measures.

Automatic or manual PM TPs choice according to the relevant NEs features.

PM data displayed in 15minutes or 24hours strategy.

PM thresholds and reports:

TCA: Threshold Crossing Alarms

Threshold report according to the data quality.

Counter report whatever the data quality.

PM data archiving, backup.

Export of PM data to an external system


13/22


1.13

1.2 Functional Management DomainsAdministration and Security

UNIX System Security: user login and password protected access.

Different Operator profiles using: FAD and NAD.

Administrator applications:

System Backup and Restore System Process Control, Start-up and Shut-down

System Logs and Process / Agent traces

Periodic actions

Printing (for every profile)

Functional Access Domain

Administrators, Constructor, Operator, Viewer

Network Access Domain

Subsets of Network Entities such as Trails, Paths, NAPs, link

connections


14/22




1.3 System architecture


15/22


1.15

1.3 System architectureHardware architecture (1/2)

Hardware-Architecture

Alcatel 1354 RM may run on a scalable set of computers ranging from

small to large servers, providing the best cost performance ratio

depending on the managed network size.

Access to the system is provided using PCs through Bridges.

High Availability

In order to provide high service availability, different levels of resilient

configurations can be provided on servers, ranging from simple disk

mirroring, cold standby systems, warm active/standby systems and

remote crash recovery centre.


16/22


1.16

1.3 System architectureHardware architecture (2/2)

IM Server

USM Server

PCs


17/22


1.17

1.3 System architectureSoftware architecture (1/2)

From the software point of view, the 1354RM is composed of two subsystems:

User Service Manager

This subsystem interacts with the user, processing his requests andissuing them to the appropriate IM subsystem.

Information Manager (SNML-IM)

This subsystem is in charge of managing data belonging to SNML MIB.This data base is updated according to USM configuration requests. Themodifications are sent towards the EML layer.

This subdivision is reflected in the installation (Master and Client servers)


18/22


1.18

1.3 System architectureSoftware architecture (2/2)

The Master Server (IM)

2 types of architecture can be chosen to built the NR7 TMN:

1 server where many instances of 1353NM and 1354RM cancoexist.( for example 1 1353NM and 1 1354RM)

1 server for each instance.

The Client server (USM)

A Client server can provide the client instances for 1353NM and

1354RM.


19/22


1.19

1 System ArchitectureExercises

Exercise 1 : TMN description

Exercise 2 : TN description

Time allowed :

20 minutes

See next pages


20/22


1.20

1 System ArchitectureExercise 1 : TMN description

Draw here below the TMN available for the training:

1354RM and 1353NM servers (master and client if any)

Bridges PCs

DCN (LAN, Hubs and routers if any)


21/22


1.21

1 System ArchitectureExercise 2: TN description

Draw here below the TN structure available for the training:

Ring, meshed or linear topologies

ADMs, OMSNs or DXC

GNE(s)


22/22

1.22

1 System ArchitectureEVALUATION

Objectives: to be able to

describe the interaction between the

1353NM and the 1354RM

describe the system architecture

Thank you for answering

the self-assessment

of the objectives sheet

Documents

1 System Architecture