1 SYSTEM ARCHITECTURE

1.1

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

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

Page 1.1


Objectives: to be able to

describe the interaction between the 1353NM

describe the system architecture

1 System Architecture
Session presentation

and the 1354RM

Program:

1.1 NR7 TMN description

1.2 Functional Management Domains

1.3 System architecture

1.2

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

Page 1.2

1 SYSTEM ARCHITECTURE
1.1 NR7 TMN description

1.3

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

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

Page 1.3

1.1 NR7 TMN description

Layers
NML

1354RM

Interface
IOO

OPTIC-IM / SEN-IM

1353NM

EML
Q3

ECT

DXC
CT

Q3

1320
CT

Q3

DXC 4/3/1 OMSN

DXC 6/4
WDM

SNMP

QB3*/Q2

1320NX

NECTAS
CT

NECTAS

NE

QB3*

ADM
SR

ADM/LS/OA
WDM/MW

W PDH
ATM

W
PDH
1.4

NE Network Element
 PDH or SDH Transmission equipment.

TN Telecommunication 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, crossconnections, synchronisation, protections, alarms, performance...
 The Alcatel NR7 EML layer is made of 1353NM (centralised system) and Craft Terminals (local
management. E.g: 1320NX and 1320CT).

NML Network Management Layer
 The system belonging to this layer allows the operators to manage connectivity, routing (trails and
paths) and the relevant protections in various topologies. Furthermore the NML is in charge of
Network 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.

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

Page 1.4

1.1 NR7 TMN description

Interfaces

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 this
case, 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).

1.5

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

Page 1.5

1 SYSTEM ARCHITECTURE
1.2 Functional Management Domains

1.6

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

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

Page 1.6

1.2 Functional Management Domains

EML and NML Functional Domains
Functions Configuration
management
Layers
NML
1 level
st

1354RM

EML

1353NM

Nodes (note 1)
Physical
connections
MS-trails
HO-trails
Protection schemes
Paths (note 2)

NE Address
Hardware units
EPS schemes
Synchronisation
Cross connections
(note4)

Fault
management

Performance
management

Nodes (note 1)
Physical
connections
MS-trails
HO-trails
Paths

HO-trails
Paths

Alarm monitoring:
Hardware
Synchronisation
MSP
SDH functional
blocks

Regeneration
section
Multiplex section
HO and LO TPs
(note 3)

Security and
Administration
Backup / restore
Process
monitoring

Backup / restore
Process
monitoring

1.7

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. The
relevant Performance Monitoring has to be started from the RM application. Performance Monitoring of RS
and MS is fully manage from the 1353NM application.

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

All Protection schemes but EPS are managed from 1354RM

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

Page 1.7

1.2 Functional Management Domains

Examples of Network Configuration (1/3)
2F MS-SPRING
Cross connects

STM-16

ADMs or OMSNs

STM-4

Interconnected rings
STM-1

SNCP ring

1641SX

1641SX

Interconnected rings
STM-1

STM-1

STM-4

STM-4

STM-1

Linear chain
1.8

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

Page 1.8

1.2 Functional Management Domains

Examples of Network Configuration (2/3)

 RM operator operates from the Browser. The Network View interface is

integrated 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 needed
protection level:

SNCP, 2F / 4F- MS-SPRING , MSP 1+1, MSP 1:N
 1354RM system provides facilities to modify a Network topology without traffic
affecting at TN level. In this case the operator will have to perform commands
such as download disable / enable, consistency check and MIB audit. The
way to make it is described in the administration training.

1.9

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

Page 1.9

1.2 Functional Management Domains

Examples of Network Configuration (3/3)

 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 HOPaths.

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

1.10

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

Page 1.10

1.2 Functional Management Domains

Fault Management

1354RM
Network view
Browser
Alarm

AS1330
Network

1.11

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 the
corresponding 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 and
Paths (manually or automatically).

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

Page 1.11

1.2 Functional Management Domains

Performance Management viewer

1.12

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

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

Page 1.12

1.2 Functional Management Domains

Administration 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
1.13

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

Page 1.13

1 SYSTEM ARCHITECTURE
1.3 System architecture

1.14

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

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

Page 1.14

 Hardware-Architecture

1.3 System architecture

Hardware architecture (1/2)

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.

1.15

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

Page 1.15

1.3 System architecture

Hardware architecture (2/2)

IM Server

USM Server

PCs

1.16

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

Page 1.16

1.3 System architecture

Software 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 and
issuing 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. The
modifications are sent towards the EML layer.
 This subdivision is reflected in the installation (Master and Client servers)

1.17

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

Page 1.17

 The Master Server (IM)

1.3 System architecture

Software architecture (2/2)

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

 1 server where many instances of 1353NM and 1354RM can
coexist.( 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.

1.18

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

Page 1.18



1 System Architecture
Exercises

Exercise 1 : TMN description

Exercise 2 : TN description

Time allowed :
20 minutes

See next pages

1.19

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

Page 1.19

1 System Architecture
Exercise 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)

1.20

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

Page 1.20

1 System Architecture
Exercise 2: TN description

Draw here below the TN structure available for the training:

Ring, meshed or linear topologies

ADMs, OMSNs or DXC

GNE(s)

1.21

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

Page 1.21

1 System Architecture
EVALUATION

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

1.22

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

Page 1.22