1353NM Rel. 7.4B Operation

Alcatel 1353NM
Alcatel 1353NM rel. 7.4B

Operation
3FL41020ADAAWBZZA
Edition 1.00
TRAINING MANUAL
Alcatel 1353NM - Alcatel 1353NM rel. 7.4B Operation

All rights reserved © 2007, Alcatel-Lucent
Copyright © 2007 by Alcatel-Lucent - All rights reserved

Passing on and copying of this document, use and
communication of its contents not permitted without
written authorization from Alcatel-Lucent
All Rights Reserved © 2007, Alcatel-Lucent

Alcatel 1353NM rel. 7.4B Operation - Page 1
Legal Notice
2
Switch
Warning
Safety to notes view!
Both lethal and dangerous voltages are present within the equipment. Do not wear conductive jewelry
while working on the equipment. Always observe all safety precautions and do not work on the
equipment alone.
Caution
The equipment used during this course is electrostatic sensitive. Please observe correct anti-static
precautions.
Trade Marks
Alcatel and MainStreet are trademarks of Alcatel.
All other trademarks, service marks and logos (“Marks”) are the property of their respective holders
including Alcatel-Lucent. Users are not permitted to use these Marks without the prior consent of Alcatel
or such third party owning the Mark. The absence of a Mark identifier is not a representation that a
particular product or service name is not a Mark.
Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training
purposes only. No other use or transmission of all or any part of this document is permitted without
Alcatel-Lucent’s
Alcatel 1353NM
written permission, and must include all copyright and other proprietary notices. No
otherAlcatel
use 1353NM
or transmission of all or any partAll Rights
rel. 7.4B Operation of its contents may be used, copied, disclosed or conveyed to
Reserved © Alcatel-Lucent 2007
any party in any manner whatsoever without prior written permission from Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable Canadian or other
legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it
includes or describes, and is expressly prohibited from modifying the information or creating derivative
works without the express written consent of Alcatel-Lucent.
Alcatel-Lucent, The Alcatel-Lucent logo, MainStreet and Newbridge are registered trademarks of Alcatel-
Lucent. All other trademarks are the property of their respective owners. Alcatel-Lucent assumes no
responsibility for the accuracy of the information presented, which is subject to change without notice.
© 2007 Alcatel-Lucent. All rights reserved.
Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential
damages, including lost profits, lost business or lost data, resulting from the use of or reliance upon the
information, whether or not Alcatel has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes
neither an endorsement nor a recommendation.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-
Lucent equipment and its operation.

Table of Contents
3
1. Product Overview
Switch to notes view!
Module 1. 3JK Product Overview
2. Graphical Interfaces
Module 1. 3JK How to Logon
Module 2. 3JK Network Topology
3. System Operation
Module 1. 3JK NE Supervision
Module 2. 3JK NE Management
4. Maintenance Applications
Module 1. 3JK Alarm Management
Module 2. 3JK Performance Management
5. Administration features
Module 1. 3JK Administration for operators
Alcatel 1353NM
All Rights Reserved © Alcatel-Lucent 2007
Alcatel 1353NM rel. 7.4B Operation

Table of Contents [cont.]
4
Alcatel 1353NM
This page is left blank intentionally

Course Objectives
5
Welcome to Alcatel 1353NM rel. 7.4B Operation
After successful completion of this course, you should understand :
Identify and localize the system functions into the TMN

Describe the system architecture
Login, start the TMN-OS icon, start the main applications of the 1353NM
Create a network topology including Q3, 1850TSS and SNMP NEs
Supervise a Q3, 1850TSS-320 and SNMP Network Element
Perform the basic management operations on Q3, 1850TSS-320 and SNMP NE management
Handle the AS application for current alarms and the alarm history
Manage the transmission quality records
Perform the basic administration tasks in the operator field
Alcatel 1353NM

Course Objectives [cont.]
6
Alcatel 1353NM

About this Student Guide
7
Conventions used in this guide

Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful
or interesting.
Technical Reference
(1) 24.348.98 – Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment
damage or personal injury.
Alcatel 1353NM
Where you can get further information

If you want further information you can refer to the following:

Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

About this Student Guide [cont.]
8
Alcatel 1353NM

Self-Assessment of Objectives
9
Contract number :
At the end of each section you will be asked to fill this questionnaire
Course title :
Please, return this sheet to the trainer at the end of the training
Client (Company, Center) :

Language :
Switch to notes view! Dates from : to :
Number of trainees : Location :
Surname, First name :
Did you meet the following objectives ?

Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Yes (or No (or

Instructional objectives globally globally Comments
yes) no)
Product Overview
• identify and localise the system functions into
the TMN
• describe the system architecture
Graphical Interface - How to Logon
• Login, start the TMN-OS icon, start the main
Alcatel 1353NM
applications
Alcatel 1353NM rel. of
7.4B1353NM
Operation
Graphical Interface - Network Topology

• manage the maps
• create several types of NEs
• configure the OSI over IP tunneling
System Operation - NE Supervision
• supervise the NE
• use the simulator
• perform a MIB backup/restore
System Operation - NE Management
• perform the basic management operations on
Q3, 1850TSS-320 MSPP and SNMP NE
Maintenance Applications - Alarm Management
• handle the AS application for current alarms
and the alarm history
Maintenance Applications - Performance
Management
• manage the transmission quality records
Administration Features - Administration for
Operators
• perform the basic administration tasks in
operator field


Self-Assessment of Objectives [cont.]
10
Yes (or No (or

Instructional objectives Globally globally Comments
yes) no)
Alcatel 1353NM
Other comments
Thank you for your answers to this questionnaire


Do not delete this graphic elements in here:
Section 1
Product Overview
Module 1
Product Overview
3JK Edition 1.00
Alcatel 1353NM · Alcatel 1353NM rel. 7.4B Operation


3JK Edition 1.00
Section 1 · Module 1 · Page 1
Blank Page
Product Overview · Product Overview 1·1·2
Alcatel 1353NM
Document History
Edition Date Author Remarks
01 2007-10-30 Pirola Paolo First edition

3JK Edition 1.00
Objectives
z To be able to
z identify and localise the system functions into the TMN
z describe the system architecture
Alcatel 1353NM

3JK Edition 1.00
Objectives [cont.]
Alcatel 1353NM

3JK Edition 1.00
Table of Contents
Page
1 TMN description 7
2 1353NM management functions 15
3 System architecture 23
Alcatel 1353NM

3JK Edition 1.00
Alcatel 1353NM
Alcatel 1353NM rel. 7.4B Operation This page is left
All Rights blank
Reserved intentionally
© Alcatel-Lucent 2007

3JK Edition 1.00
1 TMN description
Alcatel 1353NM

3JK Edition 1.00
1 TMN description
The TMN
z A Telecommunication Management Network (TMN) is a structured

network featuring management functions for a Telecommunication
Network (TN).
z The TMN is structured in layers
z EML: Element Management Layer
} To manage the network element configuration, alarms and performance
z NML: Network Management Layer
} To manage network connectivity, routing and protections in various topologies and
across different regions
z SML: Service Management Layer
} To manage services offered to the customer: order handling, service handling,
billing, service development, planning
z BML: Business Management Layer
} To manage the overall sales activity: e.g. return on investment, system decision
support, market analysis
Alcatel 1353NM
1353NM belongs to the EML

1354RM belongs to the NML

3JK Edition 1.00
1 TMN description
TMN Layers
Interface
IOO
NML 1354RM
Interface
IOO
EML 1353NM
SNMP SNMP Q3 Q3 Q3 QB3* SNMP

SNMP
1320NX
ECT Browser ZIC 1320CT 1540CT
NECTAS
1320CT
2G ADM(1) ISA
1850TSS-40 1850TSS-320 OMSN CWDM(3)
Subm.
OMSG Litespan(2) Melodie(4)
NE WDM
AWY
1850TSS-3 Terr. WDM
2G Radio Radio SONET
Alcatel 1353NM
NE: Network Element

z PDH or SDH Transmission equipment.
ECT: Equipment Craft Terminal
z for local management
EML: Element Management Layer
z The whole NE configuration can be managed from this layer on an individual basis: hardware, cross-
connections, synchronization, protections, alarms, performance...
z The Alcatel EML layer is made of 1353NM (centralized system)
NML: Network Management Layer
z 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.
z The Alcatel NML layer is made of several products (i.e. 1354RM, 1354BM-ETH, 1354BM-ATM, 1354SY).
TMN: Telecommunication Management Network
z This management network is made of 5 layers. Only EML and NML are referred in this document.
ZIC: Zero Installation Craft Terminal
(1) 1664SM and 1666-55SR starting from Rel 3.2

(2) 1540SDH starting from Rel. 2.1B
(3) 1692MSE
(4) 946LUX50

3JK Edition 1.00
1 TMN description
NEs managed by the 1353NM7
Product Overview · Product Overview 1 · 1 · 10
1353NM
1353NM
OSI QB3* OSI CMIP IP SNMP OSI CMIP + IP
interface interface interface SNMP SNMP
interface
QB3*
Q3 Q3
CWDM(3) AWY
SNMP
Submarine ISA Melodie(4)
WDM
Radio SONET 1850TSS-320
3rd party NEs(5)
2G ADM(1) 1850TSS-3
OMSN OMSG
Terr. WDM MW 2G
Litespan(2)
Alcatel 1353NM
1353NM Rel7.4 doesn’t support anymore the 1G QB3* NEs, that are:
z 1G ADM
z 1G MW
z 1G WDM
The only exception are the QB3* Submarine WDMs, still managed due to the long-term support required by
these NEs.
(1) 1664SM and 1666-55SR starting from Release 3.2

(2) 1540SDH starting from Rel. 2.1B
(3) 1692MSP
(4) 946LUX50
(5) 1850TSS-40; ETX202; LineView R2.0; OA512 R1.0; 1693SE R1.0; 1696SE R1.0; 1696MS (ROADM) R4.0;
1615BCE R1.0; A9500MXC R1.0; EMX3660
CMIP: Common Management Information Protocol

SNMP: Simple Network Management Protocol

3JK Edition 1.00
1 TMN description
EML-IM
z The NEs are managed by the 1353NM via EML-IM.

z EML-IM is responsible for maintaining a consistent view of the NE
configuration and status.
z EML-IM is responsible for managing NEs of different types and
releases.
z There are several EML-IM classes per 1353NM:
z EMLIMWDMSUBNR7
z EMLIMADMQ3
z EMLIMDXCQ3
z EMLIMCORBASNMP
z EMLIMSGM
z EMLIM4G
z EMLIM9500MXC
z Each EML-IM class can have several instances, created during the
system installation and configuration.
Alcatel 1353NM
Available EML-IMs:
z EMLIMWDMSUBNR7: Information Manager for QB3* Submarine WDM
z EMLIMADMQ3: Information Manager for NEs managed via the OSI CMIP-Q3 interface
z EMLIMDXCQ3: Information Manager for OMSG (Digital cross connect) managed via the
OSI CMIP-Q3 interface
z EMLIMCORBASNMP: Information Manager for NEs managed via the IP SNMP interface
z EMLIMSGM: SNMP Generic Mapper; Information Manager for some 3rd party NEs
managed via the IP SNMP interface (i.e. 1850TSS-40, ETX202)
z EMLIM4G: Information Manager for some 4G NEs (i.e. 1850TSS-320, 1850TSS-3, 1626LM
R4.0)
z EMLIM9500MXC: Information Manager for Microwave Radio Equipment 9500MXC managed
via the IP SNMP interface

3JK Edition 1.00
1 TMN description
QB3*/Q3 NE
z QB3* NE
z NE local configuration based on NECTAS tables
z Requires translation between NECTAS tables and OS object management
z Duplication of configuration database (MIB) in NE and in OS
z Q3 NE
z NE local configuration based on object management
z Only one database in the NE
z Any modification is performed directly on the NE
Alcatel 1353NM
N.B.: 1353NM Rel7.4 doesn’t support anymore the 1G QB3* NEs. The only exception are the QB3*
Submarine WDM, still managed due to the long-term support required by these NEs

3JK Edition 1.00
1 TMN description
QB3*/Q3 NE - OS dialogue
RM DB
USM
1
USM PNM 2 USM
1 2 AS AS-IM
DB
NM-IM
QB3*
1 2
MIB
EML-IM Q3 EML-IM
Nectas tables
NM
3 4
QB3* Q3
Nectas ADM NE DB
tables
Alcatel 1353NM
z The 1353NM acts as a pass-through for messages from/to 1354RM to/from Q3 NEs.
z Each single configuration request from the 1354RM does not require mapping in the 1353NM, and only
this configuration request is sent to the Q3 NE (not the configuration tables, including unchanged
information, as in the NR3.x). This improves 1354RM performance with the NEs.
z Consistency checks on the required operation are performed by the NE itself. So the 1353NM does not
need to know all the implementation details of all NE types and releases.

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
2 1353NM management functions
Alcatel 1353NM

3JK Edition 1.00
Network Topology Functions
Network
Topology
Management
Alcatel 1353NM
Network Topology Management

z Creating the topology
z Adding/deleting symbols
z Declaring NEs
z NE inventory

3JK Edition 1.00
Network Element and Software Management Functions
Network
Element
Management
Software
Management
Alcatel 1353NM
Network Element Management

z Swapping boards and subracks
z Configuring protection plans
z Enabling/disabling alarm notifications
z Configuring the alarm severity profile
z Managing NE time and synchronization sources
z Managing interconnections
z Managing ports
z Configuring external points
z Backing up and restoring the NEs configuration
Software management
z Get information on the NE software
z Downloading software from a server to an NE
z Activating deactivating NE software
z Commissioning NE software

3JK Edition 1.00
Alarm Functions
Alarms
Management
Alcatel 1353NM
Alarms Management
z Receiving and processing alarms
z Setting up filter criteria for receiving alarms
z Managing alarm log files
z Internal storage and processing of current alarms information
z Internal storage and processing of alarm history information
z User interface service for display purposes
z Alarms represented summarily in all views concerning an entity

3JK Edition 1.00
Performance Functions
Performance
Monitoring
Management
Alcatel 1353NM
Performance Monitoring Management

z Configuring the error counters threshold
z Monitoring performance counters
z Logging performance data
z Search for degraded quality TP

3JK Edition 1.00
System administration Functions
System
Management
Security 1353NM
Management
Alcatel 1353NM
System Management (for the administrator)

z Starting/stopping the system
z System trace and logs
z Displaying and managing all 1353NM processes
z System Backup/Restore
z Periodic actions
Security Management
z Accessing the system
z Assigning profiles
z Distributing maps
z Access rights to the NE

3JK Edition 1.00
Functions of the 1354RM
STM/16
2400Mb/s STM/4
600Mb/s
Interconnected
rings
STM/1
150 Mb/s
Network management STM/4

• Topology management Meshed 600Mb/s
• Routing provisioning subnetworks

• Protections management STM/1
• Alarm management 150 Mb/s
• Performance Monitoring Cross Connect
• System administration ADM, OMSN, 1850TSS, WDM
Linear chain
Alcatel 1353NM
Upload of available NE and Port information from the 1353NM

Construction of the ‘static’ part of the managed network
z Link Connections
z Elementary topologies (rings, meshes, ...)
Applying the ‘layered concept’ according to G.803
z Physical, Multiplex section, HO trails, LO trails, Paths
Configuring and managing the ‘dynamic’ part of the network
z Payload configuration
z Path provisioning, supervision, maintenance
Consistency control of SEN-IM and OPTICS-IM based NEs
z Download disable management
z Consistency audit and download management
z NE isolation detection and recovery
Protections management
z SNCP, Drop & Continue, 2F/4F MS-SPRing
z Restoration rules
z ASON/GMRE management on ION nodes
Performance Monitoring
z Customized measures creation and analysis
Alarms Management
z Alarm severity management (ASAP)
z Alarm monitoring and records management
“Northbound Interface” management (ioo)
3JK Edition 1.00
IOO interface Functions
External Access
NML NML Access
OS Network
Network
Alcatel IOO interface
Transport EML
Network Switching
Switching
Network
Network
Data
Data
Network
Network
1353NM 1354RM
Alarms
Performance
Monitoring
Network Directory
Remote Inventory
Alcatel 1353NM
Ioo is an interface allowing the synchronization between an external application and the Alcatel
Transmission Management Network application.
Two different services are provided
z Solicited service.
The EOS requests the data as soon as it is interested in.
z Unsolicited service.
The EOS registers itself to receive automatically all the new data.
Alarms
z The Ioo is able to export alarms (throughout SNMP or a socket based ASCII interface) using either CSV or
AVA formats.
z The EOS can ask for the current alarm list, and then receive alarms in unsolicited way.
Performance monitoring
z The Ioo is able to export Performance Monitoring data (through a socket based ASCII interface or FTP)
using either CSV or AVA formats.
z The Ioo interface can export
} The list of TPs where PM has been activated
} The actual PM measurements data
Network directory
z The Ioo is able to export the list of Network Elements managed by the 1353NM product, together with
their main attributes and states.
Remote Inventory
z The Ioo is able to export the Remote Inventory of Network Elements managed by the 1353NM product.

3JK Edition 1.00
3 System architecture
Alcatel 1353NM

3JK Edition 1.00
Hardware architecture
z Hardware architecture
z Alcatel 1353NM 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.
z Access to the system is provided using PCs through “Go-Global” software.
z High Availability
z 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 center.
Alcatel 1353NM

3JK Edition 1.00
Hardware architecture
1353NM 1353NM
Master Server Presentation Server
LAN
QB3*/Q3/SNMP
GNE
STM-n
NE NE
PCs
Alcatel 1353NM
GNE: Gateway Network Element
The 1353NM system can be installed as:

z A master server (to run the IM and USM processes)
z A presentation station (to run the USM processes only)
PCs running Windows NT/2000/XP and Go-Global can be used to access remotely the 1353NM

3JK Edition 1.00
Hardware architecture [cont.]
IM Server
PCs
USM Server
Alcatel 1353NM

3JK Edition 1.00
Software architecture
z From the software point of view, 1353NM is composed of two

subsystems:
z User Service Manager (USM)
} This subsystem interacts with the user, processing his requests and issuing them to
the appropriate IM subsystem.
z Information Manager (IM)

} This subsystem handles the logical functional data processing and its persistency.
z This subdivision is reflected in the installation (Master and Presentation

servers)
Alcatel 1353NM

3JK Edition 1.00
Software architecture [cont.]
z The Master Server (IM)

z 2 types of architecture can be chosen to install the TMN system:
} 1 server where many “instances” of 1353NM and 1354RM can coexist (for example
1 1353NM and 1 1354RM).
} 1 server for each instance.
z The Presentation server (USM)

z A Presentation server can provide the presentation instances for 1353NM and
1354RM.
z 1353NM rel.7.3 and rel. 7.4 co-hosting
z Due to QB3* dismission in Release 7.4, 1353NM rel. 7.3 and 7.4 master and
presentation instances shall be able to run over the same HW platform.
} In this way, there is no need to add new TMN HW dedicated to QB3* management
when migrating to NM7.4.
Alcatel 1353NM

3JK Edition 1.00
Exercise
Exercise 1: TMN description

Exercise 2: TN description
Alcatel 1353NM

3JK Edition 1.00
Exercise 1: TMN description
z Draw here below the TMN available for the training:

z 1353NM servers (master and presentation if any)
z Bridges PCs
z DCN (LAN, Hubs and routers if any)
Alcatel 1353NM

3JK Edition 1.00
Exercise 2: TN description
z Draw here below the TN structure available for the training:

z Ring, meshed or linear topologies
z OMSN, ISA, 1850TSS, WDM, …
z GNE(s)
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
End of Module
Product Overview
Alcatel 1353NM

3JK Edition 1.00
Section 2
Graphical Interfaces
Module 1
How to Logon
3JK Edition 1.00


3JK Edition 1.00
Blank Page
Graphical Interfaces · How to Logon 2·1·2
Alcatel 1353NM
Document History

3JK Edition 1.00
Objectives
z To be able to
z Login, start the TMN-OS icon, start the main applications of
1353NM
Alcatel 1353NM

3JK Edition 1.00
Objectives [cont.]
Alcatel 1353NM

3JK Edition 1.00
Table of Contents
Page
1 Login and workspace front panel 7
2 The TMN-OS icon 11
3 Windows & workspace menu 19
Alcatel 1353NM

3JK Edition 1.00
Alcatel 1353NM
All Rights blank

3JK Edition 1.00
1 Login and workspace front panel
Alcatel 1353NM

3JK Edition 1.00
Access from PC with GO-Global
1. Double click on the GO-Global icon

on the desktop
2. Give the server address and click on

Connect
3. Give username and password to

access the server and click OK
4. Launch Normal Desktop
Alcatel 1353NM
z At step 4, instead of “Normal Desktop”, also “Alcatel TMN OSs” can be chosen. The PC Windows user
interface look and feel is then used for managing the session, instead of Unix X-Windows. See the
following figure as example.
Windows XP
look and feel

3JK Edition 1.00
Control panel
Ws activity TMN-OS
Clock
Date Padlock Workspaces File manager Text editor
Printer Mail Terminal

Exit
Alcatel 1353NM
Only admin profiles can access “File manager" and “Terminal" files.
Locking the session:

z Manual lock is used to lock the screen immediately
} select the padlock icon in the front panel
z When the session is locked, enter the password and press Enter key to continue the job

3JK Edition 1.00
Blank Page
Graphical Interfaces · How to Logon 2 · 1 · 10
Alcatel 1353NM

3JK Edition 1.00
2 The TMN-OS icon
Alcatel 1353NM

3JK Edition 1.00
2 The TMN-OS icon
Start TMN-OSs
z The TMN-OS icon is the starting point for all the operation and
administration actions that can be done on the instances installed on
the server.
z All the instances installed on the server are displayed. The menus &
icons are context sensitive.
Click the
icon
The set of icons depends

on the selected instances.
In this case the 1353NM_74
instance is selected
Alcatel 1353NM
The color of each icon depends on the OS process state:

z Green: all the processes are running
z Red: at least one process is not running
z Blue: all the processes are stopped
z Yellow: the process state is unknown. It may be due to an isolation condition.

3JK Edition 1.00
2 The TMN-OS icon
1353NM functionalities
Performance
monitoring Open 1353NM-SE map
Exit
Topology
System manager
configuration
Alarms
Process
monitoring 1353NM
System Admin
information
Alcatel 1353NM
System configuration, Process monitoring and 1353NM Admin are Administrative functions.
System information: gives info about the installed product version.
Alarms: starts the alarm surveillance tool.
Topology Manager: opens the graphical interface for managing Maps and NEs.
Performance Monitoring: starts the Performance Monitoring viewer.
1353NM-SE map: it allows the management of 1693SE and 1696SE (SAN Extender) equipment.

3JK Edition 1.00
2 The TMN-OS icon
View and OS menus
These are administrative

functions. They depend
This menu permits to
on the user profile.
hide/show the message area.
Alcatel 1353NM

3JK Edition 1.00
2 The TMN-OS icon
Actions menu
This menu permits

to start the main
operations available
on the 1353NM.
SMF depends on the
user profile.
Alcatel 1353NM
SMF: System Management Feature

3JK Edition 1.00
2 The TMN-OS icon
Global Actions menu
This menu is common to the 1353NM

and 1354RM. It permits for example
to define new operators on the
systems. It contains mainly
administrative functions.
Alcatel 1353NM

3JK Edition 1.00
2 The TMN-OS icon
Close 1353NM session
z First possibility: with the workspace menu

z Place the mouse in an empty place on the workspace
z Click on the left mouse button
z Select “Log out”
z Second possibility: with the control panel

z Select the “exit” button on the control panel
z Remember: close all the graphical applications before closing the

session
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
3 Windows & workspace menu
Alcatel 1353NM

3JK Edition 1.00
Window menu button
z On an opened window, click on the upper left corner

z The following menu appears:
Restore the default size of the window

Move the current window in the screen
Resize the current window in all directions
Minimize the window
Full screen window
Put the window in the back of others
Display the window in the selected workspace
Display the window in all workspaces
Window is removed from the current workspace
Close the current window
Alcatel 1353NM

3JK Edition 1.00
Workspace menu
z Locate the mouse pointer on the background (i.e. outside any window).
z Press the right-hand button of the mouse.
Start the TMN-OS icon

Open a Unix terminal (for OS Admin only)
Print the screen or a window
Alcatel 1353NM

3JK Edition 1.00
Workspace menu [cont.]
z Locate the mouse pointer on the background (i.e. outside any window).
z Press the left-hand button of the mouse.
Pop up the selected window

Pop down the selected window
Minimize the front panel: useful when the
task bar is enabled
Alcatel 1353NM

3JK Edition 1.00
Exercise
Explore the TMN-OS icon for the NM instance:

1. Log on the 1353NM system.
2. Open the TMN-OS icon.
3. Identify the software release of the 1353NM system.
4. Explore the icons and menus. Start and stop the following
applications:
z User Interface
z Alarms
5. Move a window from one workspace to another one.
6. Manually lock and unlock the session.
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
End of Module
How to Logon
Alcatel 1353NM

3JK Edition 1.00
Section 2
Graphical Interfaces
Module 2
Network Topology
3JK Edition 1.00


3JK Edition 1.00
Blank Page
Graphical Interfaces · Network Topology 2·2·2
Alcatel 1353NM
Document History

3JK Edition 1.00
Objectives
z To be able to
z manage the maps
z create several types of NEs
z configure the OSI over IP tunneling
Alcatel 1353NM

3JK Edition 1.00
Objectives [cont.]
Alcatel 1353NM

3JK Edition 1.00
Table of Contents
Page
1 Creating a map 7
2 Managing and addressing a NE on a map 19
2.1 Creating and addressing a Q3 NE 21
2.2 Creating and addressing ISA boards 35
2.3 Creating and addressing a 1850TSS NE 55
2.3.1 TSS-320 in PTRP configuration 59
2.3.2 TSS-320 in MSPP configuration and TSS-3 71
2.4 Creating and addressing a SNMP NE 103
2.4.1 SNMP NE in IP DCN 105
2.4.2 SNMP NE in OSI DCN 111
2.4.3 Third party SNMP NE 115
2.4.4 9500MXC 121
2.5 NE auto discovery 127
2.6 Map population 143
3 Creating a graphical connection 155
4 Addressing NEs with IP Tunnel: OSI over IP 161
1353NM Configuration Procedure 166
5 Distributing Maps 171
Alcatel 1353NM

3JK Edition 1.00
Page
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Reminder: map definition
z A map or a network topology view represents a set of sites, NEs and

connections between symbols.
Object
Root submap
Open by clicking
on the object
Submap Submap Child submap

Map related to a
SM1 NE SM2 parent object
Submap Submap
SM11 SM12
NE NE NE NE
Map’s tree
Alcatel 1353NM
MAP: collection of symbols interconnected to represent a network
SUBMAP: collection of related symbols displayed in a single graphical window

z submaps are organized in a hierarchical way
z each submap may contain symbols representing other submaps
OBJECTS: Sites, NEs, connections between these different entities

z managed symbols: supervised entities managed by the OS (e.g. NEs)
z graphical symbols: entities not supervised by the OS (e.g. Sites and connections between symbols)
There may be multiple representations (symbols) in a map for a given managed object, but there is only
one description of the object in the OS database.

3JK Edition 1.00
1 Creating a map
Creating an empty map
1. Log in as an operator having relevant rights

2. Access to TMN-OSs Management window
3. Start 1353NM application, selecting Actions Î Topology Manager or
click on the icon
Alcatel 1353NM
z The operator can customize this new map automatically created. Nevertheless, from this step, the
operator can create, manually, one more new maps and then, customize them (see next page).

3JK Edition 1.00
1 Creating a map
Creating an empty map [cont.]
Graphical Interfaces · Network Topology 2 · 2 · 10
New Map
Click here
to see the
(sub)map’s
tree
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Creating a new map
1. From the current map, select File Î New map
z A new map, containing only a “Root” submap, appears.

2. Authorize a free “layout”, selecting Edit Î Layout Î Network
3. Disable “Frozen Mode” if necessary : Frozen Mode
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Customizing a Map
z The root submap can be

customized as follow:
1. Select the menu
View Î View Parameters
2. Define the following
parameters:
z Name: unique and without
spaces
z Background: from the list
z Layout: e.g. “Cartesian”
3. Click OK and the update of the
related window appears
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Creating a submap: by “Child View”
1. To add a child view, select the menu Edit Î Create Child View
2. Define a Name: unique name without spaces
3. Select a symbol
4. Click Apply; a new symbol appears
5. Double click on the new symbol; an empty Child view appears
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Creating a submap: by “Add Symbol”
1. To add a symbol, select the menu Edit Î Add Symbol

2. Select a Type (no graphical view)
3. Define a User label: unique name without spaces
4. Click Apply; a new symbol appears
5. Double click on the symbol to attach a Child view and answer OK
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Creating a submap: by “Add Symbol” [cont.]
1. Define the following parameters using View Î View Parameters:

z Background: from the list
z Layout: e.g. “Cartesian”
2. Click OK and the created submap appears
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Saving a map
1. Select the menu File Î Local Persistency Î Save Map as

z Define a File Name : --- (unique name without spaces)
2. Click Save
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Restoring a map
1. Select the menu File Î Local Persistency Î Restore Map

z Select a File and then the File Name field is updated
2. Click Restore
Alcatel 1353NM

3JK Edition 1.00
1 Creating a map
Exercise
z Create a new map (each group should use a different

name)
z Create a child submap
z Save the created map, close it and open it
Alcatel 1353NM

3JK Edition 1.00
2 Managing and addressing a NE on a

map
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
2.1 Creating and addressing a Q3 NE
Alcatel 1353NM

3JK Edition 1.00
Prerequisites
z A Q3 NE can be created and correctly supervised only if the following

processes have been configured and are running on the 1353NM System:
z A Supervision_Area linked to the System’s Ethernet interface (e.g. lan0)

z A Necom_SubSystem associated to this Supervision_Area
z A EMLIMADMQ3 associated to the same Supervision_Area
z Check the correct configuration and process status with the System
Administrator
Alcatel 1353NM

3JK Edition 1.00
NE Creation
1. Open the related submap

2. Choose Declarations Î Create
Î NE
3. Fill in the NE Creation window
z Select the appropriate:
} NE family
} Type of equipment
} Release of equipment
z Fill in the two mandatory fields :
} User label
} Location Name
4. Click Apply to launch the creation
z The created NE appears on the submap
5. Close the window or create other
NEs
6. Manage the related addresses (NE
& OS). See next pages.
Alcatel 1353NM
z The above procedure leads to an automatic choice of the Supervision Area and EML-IM made by the
1353NM system. In this case, the system takes into account the load of each available EML-IM among the
“EMLIMADMQ3” ones trying to make it homogeneous.

3JK Edition 1.00
EML-IM and Supervision Area assignment
z The NE creation form gives the operator the

opportunity to select himself a particular EML-IM.
To do that, the fields “Supervision Area” and “EML
Domain “ have to be used. The “Process
Monitoring” analysis of the system can be helpful
to make such a choice.
z To display the list of the existing EML-IMs, open
the Process Monitoring window as follow:
z From TMN-OSs Management window, select 1353NM
icon and then click on the Process Monitoring Icon
z In the Process Monitoring window, expand the tree
structure up to RetixStack and EML-IM list (Emlims).
z Identify the processes which can be in charge of the
NE management.
} The suffix of the Retix stack’s sub processes suggests the
Supervision Area
} EML domain must be chosen among the “EMLIMADMQ3”
ones
Alcatel 1353NM

3JK Edition 1.00
System addressing: NSAP address
z An NSAP address represents globally a unique location in the OSI

environment (i.e. it must be unique for the specified equipment)
z The NSAP address is made of two parts:
z IDP : define the address structure
z DSP : the address itself
NSAP
IDP DSP
AFI IDI DFI ORG RSD RD Area ID SEL
1 byte 2 bytes 1 byte 3 bytes 2 bytes 2 bytes 2 bytes 6 bytes 1 byte
xx xxxx xx xxxxxx 0000 xxxx xxxx xxxxxxxxxxxx 1D
Alcatel 1353NM
NSAP Network Service Access Point
IDP Initial Domain Part

z AFI Authority and Format Identifier
} 39 ==> IDI is an ISO DCC (Data Country Code) (ANSI format)
} 47 ==> IDI is an ISO6523 ICD (GOSIP format)
z IDI Initial Domain Identifier
} example in ISO DCC format
{ 032F Argentina 250F France 372F Ireland 380F Italy
{ 710F RSA 826F UK 840F USA
DSP Domain Specific Part
z DFI DSP Format Identifier
z ORG Organisation Name (numeric form)
z RSD Reserved
z RD Routing Domain Identifier
z Area Area Identifier
z ID System Identifier (useful for using the MAC address as the ID field, but this is not mandatory)
z SEL NSAP Selector
for further information on NSAP refer to RFC1629, for example, at
z http://www.alternic.org/rfcs/rfc1600

3JK Edition 1.00
System addressing: NSAP address [cont.]
D1 D2
Area
A1 A3
NE System ID
A2 A4
Domain
Alcatel 1353NM

3JK Edition 1.00
System addressing: NSAP address [cont.]
z Two types of equipment:

z Intermediate Systems (IS), with
routing table
z End Systems (ES), without ES
routing table
IS
z Two protocols:
z ES-IS between an ES equipment
and an IS equipment
z IS-IS between two IS equipment
Alcatel 1353NM
Each Alcatel equipment runs as an Intermediate System (IS) equipment and uses the IS-IS protocol.

3JK Edition 1.00
Level L1, L2, non-pure L2 for routing tables
z Level L1
z Knowledge of the topology of the
area in which the NE is located.
z Level L2
z Knowledge of the topology of all L2
routers in the domain (i.e. knowledge
of all the NEs which make the inter- L1
area routing in a given domain). L2
z Level non-pure L2
Non
z Knowledge of the topology of the
area and of all level L2 routers in the pure
domain. (Non-pure L2 = L2 + L1 )
Alcatel 1353NM

3JK Edition 1.00
NE addressing
1. By CT, get or configure

the NE address from the
Equipment View (NE):
z Select menu Configuration
Î Comm/Routing Î Local
Configuration
z If already configured the
following addresses are
shown:
} Presentation: 0002
} Session: 00
} Transport: 00
z If necessary, configure or
modify and click OK
z If no modification is done,
click Cancel
Alcatel 1353NM
To open the Equipment view from 1320CT:

z Select the supervised NE into the map
z Supervision Î NE Login

3JK Edition 1.00
NE addressing [cont.]
2. By CT, configure the OS

address on the NE from
the Equipment View (NE):
z Select menu
Configuration Î
Comm/Routing Î OS
Configuration
z Enter the main (and the
spare if any) OS NSAP
addresses:
z Click OK
Alcatel 1353NM

3JK Edition 1.00
3. By CT, verify or set the

LAPD configurations from
z Select menu Configuration
Î Comm/Routing Î
Interfaces Configuration
Î LAPD Configuration
z For each SDH port between
the GNE and any other NE
to reach, make sure the
LAPD interfaces are
created and configured:
} “Network” / “User”
z Click Apply to confirm any
modification and then
Close
Alcatel 1353NM

3JK Edition 1.00
4. By CT, enable the Ethernet

configuration if necessary from
z Select menu Configuration Î
Comm/Routing Î Interfaces
Configuration Î Ethernet
Configuration
z Select Yes to enable it
z Click Apply to confirm any
modification and then Close
Alcatel 1353NM
For the gateway NE it is necessary to enable the Ethernet interface

3JK Edition 1.00
z Configure the address of the

NE on the 1353NM
z Select the NE to be
addressed
z Select the menu
Declarations Î Set
Addresses Î Set Ne Address
z Check the values for the
selectors
} Session: 00
} Transport: 00
z Enter the NSAP address (as
for Local Configuration of CT)
z Click Set and then Exit
Alcatel 1353NM
The NE address can be modified only if the NE is not supervised (i.e. in the "declared" state).

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
2.2 Creating and addressing ISA boards
Alcatel 1353NM

3JK Edition 1.00
ISA boards and 1353NM interworking
z ISA boards are inserted into the 1353NM

OMSN shelves.
SNMP Q3
z The communication towards the
1353NM is via SNMP protocol. EML-IM EML-IM
z Each ISA board will be considered
as a NE with its own address.
DCN
DCN
OMSN’s
Equipment
ISA Controller
Board
Alcatel 1353NM

3JK Edition 1.00
Creating an ISA board
1. In the Equipment view of the OMSN

configure the ISA board:
z Select the slot in which the ISA board
has to be inserted
z Choose the menu Equipment Î Set
z Choose the ISA board type and click OK
Alcatel 1353NM

3JK Edition 1.00
Creating an ISA board [cont.]
2. In the Equipment view of

the OMSN get or set the IP
address of the ISA board:
z Choose the menu
Configuration Î
Comm/Routing Î
IP Configuration Î
ISA board IP address
z select the board
z If necessary set the IP
address and Apply
z Click Close
Alcatel 1353NM
z Step 2 can be performed using the craft terminal 1320CT.

z In Equipment view, ISA board IP address can be managed also using the option: Equipment Î ISA board
IP Address

3JK Edition 1.00
3. Open the submap in which the OMSN

is located and select it
4. Choose the menu Declarations Î
Create ISA
5. Fill in the window: Create ISA Board
z Family type, Board type, Release type,
Label (slot), IP address and (optionally,
only if Advanced is selected) EML
domain
6. Click Apply and then Quit (note1)
Selecting “Add on Tunnel” the ISA

board is automatically added to the
“IP over OSI” tunnel toward the
OMSN. If the tunnel doesn’t exist, it’s
automatically created.
Alcatel 1353NM
The use of «Advanced» configuration is not mandatory.

Instead of automatic choices made by the 1353NM, Advanced provides the operator with the opportunity
to:
z Assign a particular EML-IM
z Set a particular NE ID
note1: Click Quit only after the ISA board just configured appears in the bottom part of the screen

3JK Edition 1.00
After the creation, the ISA

board icon must be populated
into the wanted map (see “MAP
Population” chapter, further on
in this Module) and can be
managed into the submap as
one NE.
ISA board
OMSN
The ISA board can be removed
as standard NE using
Declarations Î Delete Î
Generic
Alcatel 1353NM

3JK Edition 1.00
ISA boards and communication stacks concept
OSI DCN
Alcatel 1353NM
IP over OSI tunneling is a technique that consists in the insertion (encapsulation) of the IP packets in
OSI traffic.
Starting from 1353NM, SNMP messages carrying the IP address of the target ISA board are encapsulated
in OSI packets and then sent through the OSI tunnel to the OMSN hosting the target ISA board.
The OSI tunnel is terminated, into the OMSN, by the “Point to Point” IP address belonging to its
Equipment Controller. From here, the IP packets are routed to the proper local ISA board.
By means of the “IP Tunnel Provisioning GUI”, the user can configure and activate the “IP over OSI”
tunnels on the 1353NM. The tunnels are then managed by the system by means of the “IP Tunnel
Engine”, working on the IP tunnel list. The Tunnel driver encapsulates the IP packets into OSI and
forwards the packets to the tunnel engine.

3JK Edition 1.00
Communication between 1353NM and ISA boards
z The IP-over-OSI feature at 1353NM level aims at:

z Keeping OSI DCN backbones (no OPSFv2 introduction, no router re-
configuration)
z Supporting SNMP traffic to/from ISA Boards with a single e2e tunnel
z Fully exploitation of OSI DCN resilience
Alcatel 1353NM

3JK Edition 1.00
IP over OSI tunnel setting up procedure
z The following procedure must be applied for managing a configured

ISA board in 1353NM:
1. Check that a “EMLIMCORBASNMP”, the “ositunneling” and the
“OSI_Manager” processes have been instantiated in the NM
2. Configure the IP Point-to-Point interface into the OMSN hosting the ISA
board
3. Configure the IP over OSI tunnel into the OMSN
4. Configure the IP Static Routing Configuration into the OMSN
5. Create the IP over OSI Tunnel into the 1353NM
6. Add the ISA board to the created IP over OSI tunnel
z The steps 5 and 6 are necessary if during ISA board creation the option
“Add On Tunnel” has not been used.
Alcatel 1353NM
The ositunneling process and the EML-IM (EMLIMCORBASNMP_xxx) linked to the ISA board must be
associated to a “virtual” supervision area. Check with the system administrator.
The same ositunneling process instance can support more than one tunnel towards different NEs. It means
that with a single ositunneling process, different ISA boards located in different OMSNs can be supervised.

3JK Edition 1.00
Step 1: Check the 1353NM
1. Click on
2. Check that a “EMLIMCORBANSNMP”,

“ositunneling” and Osi_Manager” processes
are running. EMLIMCORBANSNMP process
must be associated to an OSI tunnel
Alcatel 1353NM
If the required processes are not running, ask the System Administrator for their instantiation

3JK Edition 1.00
Step 2: Point-to-Point interface
1. From the
OMSN
Equipment
View, click on
2. Insert the IP Address of

the IP Point-to-Point
interface
Alcatel 1353NM

3JK Edition 1.00
Step 3: IP over OSI tunnel into the OMSN
1. From the OMSN

Equipment View, click on
IP over OSI
2. Insert the NSAP (OSI)

Address of the 1353NM
3. IP Routing
= “None”
Alcatel 1353NM

3JK Edition 1.00
Step 4: IP static routing into the OMSN
1. From the OMSN

Equipment View, click on
2. Insert the IP Address of the tunnel

defined in the 1353NM system
configuration (ask the System
Administrator)
3. Select “CLNP Tunnel” and select

the tunnel whose destination NSAP
is the 1353NM’s NSAP
Alcatel 1353NM

3JK Edition 1.00
Step 5: IP over OSI tunnel into the 1353NM
1. From the TMN-OSs Management,

issue “1353NMAdmin”
2. Click on “NE Administration” and

then on “IP over OSI Tunneling”
Alcatel 1353NM

3JK Edition 1.00
Step 5: IP over OSI tunnel into the 1353NM [cont.]
4. Select the desired NE.

Set Tunnel Type = ALCATEL
and then Confirm
3.
Alcatel 1353NM

3JK Edition 1.00
Step 6: Assign the ISA board to the tunnel
5. Add the NE IP (ISA

board) on Tunnel.
Now the user can start supervision

on the added ISA board.
Alcatel 1353NM

3JK Edition 1.00
Tunnel details
Alcatel 1353NM
The command “netstat –r”, issued by in a unix shell, shows the configured tunnel in the routing table
(“virtual” is the hostname of the ositunnel, set by the system administrator by updating the /etc/hosts
file):
n
o

3JK Edition 1.00
Removing Tunnels
Before removing the tunnel, all the NE IPs on tunnel must be removed
1. Click on Remove
(NE IP on tunnel)
2. Click on “Check
in to remove this
IP NE”
Alcatel 1353NM

3JK Edition 1.00
Removing Tunnels [cont.]
3. Remove
the tunnel
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
2.3 Creating and addressing a 1850TSS

NE
Alcatel 1353NM

3JK Edition 1.00
2.3 Creating and addressing a 1850TSS NE
Generalities
z The Alcatel 1850 Transport Service Switch (TSS) (a.k.a. 4G NE) is a multi-
service transport platform able to support any mix of traffic from 100% TDM to
100% data. This is achieved by a technology independent (universal) switch that
is capable of switching packets or circuits in their native format and transport
them as they are.
z The Alcatel 1850TSS platform comes in several sizes, according to different
transport switching capacities: 1850 TSS-3, TSS-5, TSS-15, TSS-40, TSS-100,
TSS-160, TSS-320 and TSS-640.
z In NR 8.1PL1 (1353NM Rel7.4B) only TSS-3, TSS-40 and TSS-320 are supported.
z 1850 TSS-40 is seen by the network management as a SNMP NE by means of the
EML-IM SGM (SNMP Generic Mapper).
z 1850 TSS-3 is seen by the 1353NM as a SNMP NE by means of the EML-IM 4G.
z 1850 TSS-320 can be seen by the 1353NM as a Q3 and/or SNMP NE by means of
the EML-IM 4G. TSS-320 is an integrated TDM/Data platform that can be
configured as:
z Pure TRansport Platform (PTRP), providing pure TDM and WDM transport capability.
z Multi-Service Provisioning Platform (MSPP), providing the capability of integrating
transport of TDM and data traffic.
z Carrier Ethernet Transport Platform (CETP), or Full Data, providing data traffic
transport capability.
Alcatel 1353NM

3JK Edition 1.00
Management of 1850 TSS-320
z The 1850 TSS-320 in PTRP configuration hosts only a Q3 management

agent.
z The 1850 TSS-320 in MSPP configuration hosts both the Q3 and the SNMP
management agents
z The Q3 agent is dedicated to the equipment control and to the TDM
transmission management
z The SNMP agent is dedicated to the data transmission management
z The 1850 TSS-320 in Full data configuration hosts only the SNMP agent
TSS-320 PTRP TSS-320 MSPP TSS-320 Full Data
Q3 Q3 SNMP SNMP
Agent Agent Agent Agent
Alcatel 1353NM

3JK Edition 1.00
Management of 1850 TSS-320 [cont.]
z Regardless if the hosted agents are one or two (Q3 and/or SNMP), the
1850 TSS-320 NE is managed as a single NE by the 1353NM
z A single NE is represented on the MAP.
z The protocols and models used to interface the NE (Q3 and/or SNMP) are
correlated by a EML coordinator process.
z Based on the NE configuration, one or two communication sessions are
established between the 1353NM and the NE: a Q3 session and/or a SNMP
session.
EML Coordinator 4G
EML-IM
Q3 Protocol SNMP Protocol
adapter adapter
Q3 SNMP
TSS-320 MSPP
Q3 SNMP Example of TSS-320

Agent Agent in MSPP configuration
Alcatel 1353NM

3JK Edition 1.00
2.3.1 TSS-320 in PTRP configuration
Alcatel 1353NM

3JK Edition 1.00
Creating a 1850TSS NE in PTRP Configuration
z A 1850TSS MSPP NE in PTRP configuration is managed by the 1353NM,

through the 4G EML-IM, by means of the only Q3 communication session.
z It can be created and correctly supervised only if the following
z A Supervision_Area linked to the System Ethernet interface (e.g. lan0)
z A EML-IM 4G associated to the same Supervision_Area
Administrator
4G
EML Coordinator
EML-IM
adapter adapter
Q3
Q3 TSS-320
Agent PTRP
Alcatel 1353NM
In this configuration, only the Q3 communication session needs to be established between the 1353NM
and the TSS-320.
Therefore, a Q3 DCN is needed in order to manage the equipment.

3JK Edition 1.00
Creation procedure
z The following procedure must be applied for managing a TSS-320 in

PTRP configuration by means of 1353NM:
1. Check the 1353NM configuration and process status with the System
Administrator
2. Create the TSS-320
3. Check/Configure the OSI Local Address of the NE by CT
4. Check/Configure the OS Address in the NE by CT
5. Check/Configure the LAPD and the Ethernet interface in the NE by CT
6. Configure the NE address in the 1353NM
Alcatel 1353NM

3JK Edition 1.00
Step 1: Check the 1353NM
1. Click on
Primary Supervision Area

linked to a Necom OSI stack
EML-IM 4G
Alcatel 1353NM
If the required processes are not running, ask the System Administrator for their instantiation.

3JK Edition 1.00
Step 2: Create the TSS-320

2. Choose Declarations Î Create Î
NE
} NE family: TransportServiceSwitch
} Type of equipment: 1850TSS-320
z Fill in the two mandatory fields:
} User label
} Location Name

z The created NE appears on the
submap
NEs
Alcatel 1353NM
The above procedure leads to an automatic choice of the Supervision Area and EML-IM made by the
“EMLIM4G” ones trying to make it homogeneous.

3JK Edition 1.00
Step 2: Create the TSS-320 [cont.]
Supervision Area
z The NE creation form gives the (primary)
operator the opportunity to select
himself a particular EML-IM. To do that,
the fields “Supervision Area” and “EML
Domain “ have to be used. The
“Process Monitoring” analysis of the
system can be helpful to make such a
choice.
z In the Process Monitoring window,
expand the tree structure up to the
Retix stack and the EML-IM list and
identify the processes which can be in
charge of managing the NE being
created.
z The Retix stack sub processes suffix
suggest the Supervision Area EML domain (103)
z EML domain must be chosen among
the “EMLIM4G”
Alcatel 1353NM

3JK Edition 1.00
Step 3: Local address
z By CT, get or configure the

NEs address:
z Select Configuration Î
Comm/Routing Î Local
Configuration Î OSI
Configuration
z The selectors:
} Session: 00
} Transport: 00
modify the NSAP and click OK
Alcatel 1353NM

z Select the supervised NE into the map of NES
z Supervision Î Show equipment

3JK Edition 1.00
Step 4: OS address
z By CT, assign the OS

address to the NE:
Comm/Routing Î
OS Configuration
address
z Click OK
Alcatel 1353NM

3JK Edition 1.00
Step 5: LAPD
z By CT, verify or set the

LAPD:
Comm/Routing Î
Interfaces Configuration
Î LAPD Configuration
the GNE and any other NE
to reach, make sure the
LAPD interfaces are
created and configured
z Network Protocol = OSI
Alcatel 1353NM

3JK Edition 1.00
Step 5: Ethernet interface
z For the gateway NE it is

necessary to enable the Ethernet
interface
z By CT:
Configuration
z Click on Yes to enable
z Click Apply to confirm
Alcatel 1353NM

3JK Edition 1.00
Step 6: NE address in 1353NM
z Configure the address of

the NE in the 1353NM
z Select the NE
z Select the menu
Declarations Î Set
Addresses Î Set Ne
Address
z Enter the values for the
selectors
} Session: 00
} Transport: 00
z Enter the NE NSAP address
(as for Local
Configuration)
z Leave blank the “IP
Address” field
z Click Apply
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
2.3.2 TSS-320 in MSPP configuration and

TSS-3
Alcatel 1353NM

3JK Edition 1.00
2.3.2 TSS-320 in MSPP configuration and TSS-3
Q3 and SNMP sessions
z TSS-3 is managed by 1353NM, through the 4G EML-IM, by means SNMP

communication sessions.
z TSS-320 in MSPP configuration is managed by 1353NM, through the 4G
EML-IM, by means of both Q3 and SNMP communication sessions.
z The two sessions can be supported:
z By a OSI/IP DCN, with both the Q3 and the SNMP sessions running
independently: TSS-3 and TSS-320.
z By a pure OSI DCN, where the SNMP session messages flows through an IP
over OSI tunnel between the 1353NM and the Q3 interface of the TSS-320.
4G
EML Coordinator
EML-IM
adapter adapter
Q3 SNMP
Q3 SNMP
Agent Agent
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN
z When a OSI/IP DCN is available, both the Q3 and the SNMP management
sessions can contemporarily run over the same network infrastructure.
4G
EML Coordinator EML-IM

adapter adapter
Q3 SNMP
Agent Agent
OSI/IP DCN
TSS-320 TSS-3
SNMP session (IP traffic) TSS-320
Q3 session (OSI traffic)
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN [cont.]
z In this case, TSS-3 and TSS-320 can be created and correctly supervised
only if the following processes have been configured and are running on
the 1353NM System:
z A EMLIM4G associated to the same Supervision_Area
Administrator
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN: Creation procedure
z The following procedure must be applied for managing a TSS-3 and a

TSS-320 in MSPP configuration by means of 1353NM:
Administrator
2. Create the NE
4. Check/Configure the IP Local Address of the NE by CT
7. Configure the NE address in the 1353NM
The following slides refer mainly to TSS-320.
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN - Step 1: Check the 1353NM
1. Click on
Primary Supervision Area

linked to a Necom OSI stack
EML-IM 4G
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN - Step 2: Create the NE

NE
} Type of equipment: 1850TSS-320 or
TSS-3
} User label
} Location Name

submap
NEs
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN - Step 2: Create the NE [cont.]
Supervision Area
z The NE creation form gives the
operator the opportunity to select (primary)
himself a particular EML-IM. To do that,
the fields “Supervision Area” and “EML
Domain “ have to be used. The
“Process Monitoring” analysis of the
system can be helpful to make such a
choice.
Retix stack and the EML-IM list and
identify the processes which can be in
charge of managing the NE being
created.
z The Retix stack sub processes suffix
suggest the Supervision Area EML domain (103)
z EML domain must be chosen among the
“EMLIM4G”
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN - Step 3: OSI Local address
z By CT, get or configure the

OSI NE address:
Configuration
z The selectors:
} Session: 00
} Transport: 00
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN - Step 4: IP Local address
z By CT, get or configure the IP

NE address:
Configuration Î IP
Configuration
z Assign the IP Address and click
Apply
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN - Step 5: OS address
z By CT, assign the OS address

to the NE:
Comm/Routing Î OS
Configuration
spare if any) OS NSAP address
z Click OK
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN - Step 6: LAPD
z By CT, verify or set the LAPD:

Configuration Î LAPD
Configuration
z For each SDH port between the
GNE and any other NE to
reach, make sure the LAPD
interfaces are created and
configured
z Network Protocol = IP and OSI
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN - Step 6: Ethernet interface
z For the gateway NE it is necessary

to enable the Ethernet interface
z By the CT:
Configuration
z Network Protocol = OSI and IP
z Configure the IP address and IP
mask in the IP section
z IP Routing Protocol = ISIS
Alcatel 1353NM

3JK Edition 1.00
OSI/IP DCN - Step 7: NE address in 1353NM – TSS-320

NE in the 1353NM
z Select the NE
z Select the menu
Declarations Î Set
Addresses Î Set Ne Address
selectors
} Session: 00
} Transport: 00
z Enter the NE NSAP address
(as for Local Configuration)
z Configure the NE “IP
Address” field:
} X.Y.Z.W:161 (the UDP Port is
always 161)
z Click Apply
Alcatel 1353NM
In the declaration phase, it is enough to configure only one of the two addresses: OSI or IP. The remaining
one will be automatically discovered when the supervision process is started.

3JK Edition 1.00
OSI/IP DCN - Step 7: NE address in 1353NM – TSS-3
Alcatel 1353NM

3JK Edition 1.00
2.3.2 TSS-320 in MSPP configuration
OSI DCN
z When a pure OSI DCN is available, the SNMP management session must
run over an IP over OSI tunnel configured between the 1353NM and the
1850TSS NE.
4G EML-IM
EML Coordinator
1353NM
adapter adapter
OSI DCN
IP over OSI Tunnel
SNMP session (IP traffic)
IP over OSI tunnel

(encapsulates IP traffic in OSI traffic) Q3 SNMP
Agent Agent
Q3 session
TSS-320 MSPP
Alcatel 1353NM

3JK Edition 1.00
OSI DCN [cont.]
z In this case, the TSS-320 can be created and correctly supervised only if the
following processes have been configured and are running on the 1353NM
System:
z A Supervision_Area (e.g. primary) linked to the System Ethernet interface (e.g. lan0)
z A Supervision_Area (e.g. virtual) dedicated to the IP over OSI Tunnel
z A OSI_MANAGER and a ositunnel associated to the “virtual” Supervision_Area
z A EMLIM4G associated to both the “primary” and the “virtual” Supervision_Area
Administrator
z N.B.: “primary” and “virtual” are only specimens used to explain the roles of
the two supervision areas. The administrator is free to give any other name to
the processes involved
Alcatel 1353NM

3JK Edition 1.00
OSI DCN: Creation procedure
z The following procedure must be applied

Administrator
2. Create the TSS-320
4. Check/Configure the IP Local Address of the NE by CT
7. Configure the NE address (both NSAP and IP or at least one of the two)
in the 1353NM
8. Configure the IP over OSI tunnel into the NE
9. Configure the IP Static Routing Configuration into the NE
10. Create the IP over OSI Tunnel into the 1353NM
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 1: Check the 1353NM
1. Click on
Primary Supervision Area linked

to a Necom OSI stack
EML-IM 4G
ositunneling and
Osi_Manager
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 2: Create the TSS-320

Î NE
} Type of equipment: 1850TSS-320
} User label
} Location Name
4. Click Apply to launch the
creation
submap
NEs
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 2: Create the TSS-320 [cont.]
z The NE creation form gives the operator EML domain (102)

the opportunity to select himself a
particular EML-IM. To do that, the fields
“Supervision Area” and “EML Domain
“ have to be used. The “Process
Monitoring” analysis of the system can
be helpful to make such a choice.
EML-IM list and identify the processes
which can be in charge of managing the
NE being created.
z EML domain must be chosen among the
“EMLIM4G”
z Supervision Area must be the secondary
supervision area, linked with an IP over
OSI tunnel, associated to the chosen
EMLIM4G (e.g. “virtual”)
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 3: OSI Local address
z By CT, get or configure the OSI

NE address:
Configuration
z The selectors:
} Session: 00
} Transport: 00
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 4: IP Local address
z By CT, get or configure the IP

NE address:
Configuration Î IP
Configuration
z Assign the IP Address and click
Apply
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 5: OS address
z By CT, assign the OS address

to the NE:
Comm/Routing Î OS
Configuration
address
z Click OK
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 6: LAPD
z By CT, verify or set the

LAPD:
Comm/Routing Î
Interfaces Configuration Î
LAPD Configuration
the GNE and any other NE to
reach, make sure the LAPD
interfaces are created and
configured
z Network Protocol = IP and
OSI
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 6: Ethernet interface
z For the gateway NE it is necessary

to enable the Ethernet interface
z By the CT:
Configuration
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 7: NE address in 1353NM

NE in the 1353NM
z Select the NE
z Select the menu Declarations
Î Set Addresses Î Set Ne
Address
selectors
} Session: 00
} Transport: 00
z Enter the NE NSAP address (as
for Local Configuration)
z Configure the NE “IP Address”
field:
} X.Y.Z.W:161 (the UDP Port is
always 161)
z Click Apply
Alcatel 1353NM
In the declaration phase, it is enough to configure only one of the two addresses: OSI or IP. The remaining
one will be automatically discovered when the supervision process is started

3JK Edition 1.00
OSI DCN - Step 8: IP over OSI tunnel into the NE
1. Click on
2. Insert the NSAP (OSI)

Address of the 1353NM
3. IP Routing
= “None”
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 9: IP static routing
1. Click on
2. Insert the IP Address of the tunnel

defined in the 1353NM system
configuration (ask the System
Administrator)
3. Select “CLNP Tunnel” and

choose the relevant tunnel
among the configured ones
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 10: IP over OSI tunnel into the 1353NM
1. From the TMN-OS Management,

issue “1353NM Admin”
2. Click on “NE Administration” and

then on “IP over OSI Tunneling”
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 10: IP over OSI tunnel [cont.]
4. Select the TSS-320. Set

Tunnel Type = ALCATEL
and then Confirm
3.
Alcatel 1353NM

3JK Edition 1.00
OSI DCN - Step 10: IP over OSI tunnel [cont.]
5. Add the NE IP (SNMP agent) on

Tunnel. Now the user can start
supervision also on the data SNMP
agent of the TSS-320.
Alcatel 1353NM
The command “netstat –r”, issued by a unix shell, shows the configured tunnel in the routing table
(“virtual” is the hostname of the ositunnel, set by the system administrator by updating the /etc/hosts
file)
n
o

3JK Edition 1.00
2.4 Creating and addressing a SNMP NE
Alcatel 1353NM

3JK Edition 1.00
2.4 Creating and addressing a SNMP NE
The two families of SNMP NEs
z 1353NM distinguishes two families of SNMP NEs:

z SNMP NE (i.e. 1692MSE)
z Third party SNMP NE (i.e. 1850TSS-40)
Alcatel 1353NM

3JK Edition 1.00
2.4.1 SNMP NE in IP DCN
Alcatel 1353NM

3JK Edition 1.00
Prerequisites
z A SNMP NE can be created and correctly supervised only if the following


z A EMLIMCORBASNMP associated to the same Supervision_Area
Administrator
Alcatel 1353NM

3JK Edition 1.00
NE Creation

Î NE
} NE family
} Type of equipment
} User label
} Location Name
5. Close the window or create more
NEs
Alcatel 1353NM
“EMLIMCORBASNMP” ones trying to make it homogeneous.

3JK Edition 1.00

himself a particular EML-IM. To do
that, the fields “Supervision Area”
and “EML Domain” have to be used.
The “Process Monitoring” analysis
of the system can be helpful to
make such a choice.
EML-IM list and identify the
processes which can be in charge of
managing the NE being created. EML domain
z EML domain must be chosen among
(103)
the “EMLIMCORBASNMP” ones
Alcatel 1353NM

3JK Edition 1.00
NE addressing
z Based on the specific NE to be created and the DCN topology, by the CT

get or configure the NE address from the Equipment View (NE):
z Some SNMP NEs must be reached via their Local Address
} Configuration Î Comm/Routing Î Local Configuration
z Some other SNMP NEs must be reached via their Ethernet Interface Address
} Configuration Î Comm/Routing Î Ethernet Configuration
z If the NE is connected to the DCN via the LAPD interface, it must be reached
via its Local Address
} Configuration Î Comm/Routing Î Local Configuration
z Please refer to the specific NE documentation for details
Alcatel 1353NM

z Select the supervised NE into the map
z Supervision Î Show equipment

3JK Edition 1.00

NE on the 1353NM
z Select the NE
Address
z Enter the IP address and the
UDP Port. The default UDP
Port is 161:
} X.Y.Z.W:161
z Click Set
Alcatel 1353NM

3JK Edition 1.00
2.4.2 SNMP NE in OSI DCN
Alcatel 1353NM

3JK Edition 1.00
Creation procedure
z 1692SME can be assigned an NSAP address

z The main differences with respect to the other NEs from supervision
point of view are:
1. EML-IM and Supervision Area assignment
2. Creation of the IP over OSI tunnel
Alcatel 1353NM

3JK Edition 1.00
Point 1: EML-IM and Supervision Area assignment
z 1692SME in OSI DCN can be created and correctly supervised only if the
following processes have been configured and are running on the 1353NM
System:
z A Supervision_Area (e.g. primary) linked to the System Ethernet interface (e.g. lan0)
z A Supervision_Area (e.g. virtual) dedicated to the IP over OSI Tunnel
z A OSI_MANAGER and a ositunnel associated to the “virtual” Supervision_Area
z A CORBA EM-LIM associated to the “virtual” Supervision_Area
Administrator
z N.B.: “primary” and “virtual” are only specimens used to explain the roles of
the two supervision areas. The administrator is free to give any other name to
the processes involved
Alcatel 1353NM

3JK Edition 1.00
Point 2: Creation of the IP over OSI tunnel
1. Select the
1692SME
2. Confirm
3. Insert the NSAP of

the 1692SME
Alcatel 1353NM

3JK Edition 1.00
2.4.3 Third party SNMP NE
Alcatel 1353NM

3JK Edition 1.00
Prerequisites
z A third party SNMP NE can be created and correctly supervised only if

the following processes have been configured and are running on the
1353NM System:

z A EMLIMSGM associated to the same Supervision_Area
} SGM: SNMP Generic Mapper
Administrator
Alcatel 1353NM

3JK Edition 1.00
NE Creation

NE
} NE family
} Type of equipment
} User label
} Location Name
NEs
Alcatel 1353NM
“EMLIMSGM” ones trying to make it homogeneous.

3JK Edition 1.00

and “EML Domain “ have to be
used. The “Process Monitoring”
analysis of the system can be
helpful to make such a choice.
processes which can be in charge
of managing the NE being created.
z EML domain must be chosen among EML domain (107)
the “EMLIMSGM” ones
Alcatel 1353NM

3JK Edition 1.00
NE addressing
z Based on the specific NE to be created and the DCN topology, by the

specific Element Manager tool get or configure the NE address.
z i.e. The address of 1850TSS-40 is configured by means of an Internet
browser.
Alcatel 1353NM

3JK Edition 1.00

NE on the 1353NM
z Select the NE
Address
UDP Port. The default UDP Port
is 161:
} X.Y.Z.W:161
z Click Set
Alcatel 1353NM

3JK Edition 1.00
2.4.4 9500MXC
Alcatel 1353NM

3JK Edition 1.00
2.4.4 9500MXC
Prerequisites
z 9500MXC NE can be created and correctly supervised only if the

following processes have been configured and are running on the
1353NM System:

z A 9500MXC EMLIM associated to the same Supervision_Area
Administrator
Alcatel 1353NM

3JK Edition 1.00
2.4.4 9500MXC
NE Creation

NE
} NE family
} Type of equipment
} User label
} Location Name
NEs
Alcatel 1353NM
“9500MXC” ones trying to make it homogeneous.

3JK Edition 1.00
2.4.4 9500MXC

and “EML Domain “ have to be
used. The “Process Monitoring”
analysis of the system can be
helpful to make such a choice.
processes which can be in charge
of managing the NE being created.
z EML domain must be chosen among EML domain (107)
the “9500MXC” ones
Alcatel 1353NM

3JK Edition 1.00
2.4.4 9500MXC
NE addressing
z Based on the specific NE to be created and the DCN topology, by the

specific Element Manager tool get or configure the NE address.
Alcatel 1353NM

3JK Edition 1.00
2.4.4 9500MXC

NE on the 1353NM
z Select the NE
Address
UDP Port. The default UDP Port
is 161:
} X.Y.Z.W:161
z Click Set
Alcatel 1353NM

3JK Edition 1.00
2.5 NE auto discovery
Alcatel 1353NM

3JK Edition 1.00
Principles
z NE auto discovery is a feature that makes automatic the procedure of

creating a new NE in the NM database.
z The following cosiderations apply:
z The NE must first be created in Craft Terminal and the following parameters
must be set-up by CT:
} node name
} networking set-up (NE/OS addresses, routing protocols, tunnels, etc.)
z Furthermore, the DCN interconnecting the NE to the 1353NM must be up and
running
z NE auto discovery procedure must be launched first by CT after all the local
transmission tests have been carried out, and the NE is considered ready to
support live traffic
z NE auto discovery procedure (bottom-up) is anyway compatible with the
traditional top-down method, where new NEs are manually created on
1353NM
Alcatel 1353NM

3JK Edition 1.00
Principles [cont.]
z The discovery messages pass the following information:

z NE type & release
z NE name and location
z NE address
z OS address (Q3 only)
z The discovery message is directly sent over the appropriate Layer 3
(CLNS – also for ISA Boards - or IP). No application session is established
between the NE and 1353NM.
z Since the messages go through the NE, they exploit the same DCN
routes available to 1353NM when it will request the NE supervision
z There are two procedures:
z the NE initiated procedure available for 1850TSS-320 and 1626LM R.4.0
z the CT initiated procedure for the rest of NEs supported by 1320CT
Alcatel 1353NM

3JK Edition 1.00
CT initiated procedure: CT Perspective
z The 1320CT (NES) provides a function dedicated to NE autodiscovery

z NE address is retrieved from the NE configuration; the list of target
1353NM is based on a list of platform names (offline edit) to avoid the
manual set-up of the OS address for every NE.
z In-field engineers get the result of the autodiscovery procedure
z DISCOVERY OK Æ the auto discovery message has been ack-ed by 1353NM;
NOC team is now informed
z DISCOVERY KO Æ the auto discovery message has not been ack-ed by
1353NM
} Time-out expiration: 1353NM not available or DCN not OK
} Message refused by 1353NM: NE Tyep&Rel. unknown, duplicated NE address, etc
ACK
DCN
1320CT New NE!
1353NM
Alcatel 1353NM

3JK Edition 1.00
NE initiated procedure: CT Perspective
z The autodiscovery function is directly exploited by the NE itself.

The USM provides a “Auto discovery” option, which triggers the
discovery message directly from the NE to the 1353NM.
ACK
DCN
New NE!
1320CT 1353NM
Alcatel 1353NM

3JK Edition 1.00
CT initiated procedure: What to do on CT
1. Trigger the
Autodiscovery
Procedure by
clicking on “NEAD
Update”
Warning: The NE Auto discovery feature is available on the CT

starting from CT-K Rel 3.3
Alcatel 1353NM
For more detailed information, please refer to CT-K Training Manual and Operator Handbook

3JK Edition 1.00
CT initiated procedure: What to do on CT [cont.]
2. Select “NMs
address config”
3. Insert the 1353NM

Name and Address
Alcatel 1353NM
The last two letters of the 1353NM OSI address must be substituted by AD.

3JK Edition 1.00
CT initiated procedure: What to do on CT [cont.]
4. Choose the desired

NM into the NE
auto discovery GUI
5. From the NE list, choose

the relevant one
6. Click on Send
Alcatel 1353NM

3JK Edition 1.00
NE initiated procedure: What to do on NE
1. Trigger the auto discovery

procedure by issuing
“Configuration Î
Management Î Auto
Discovery”
Alcatel 1353NM

3JK Edition 1.00
NE initiated procedure: What to do on NE [cont.]
2. Issue “Auto Discovery =

enable”
4. Click Cancel to
close the window
3. Click OK
5. Open again the Auto Discovery

window: the Status is now
“Succeeded”
6. With “Auto Discovery = disable”,

click OK to stop the procedure,
then Cancel
Alcatel 1353NM

3JK Edition 1.00
What to do on NM
z On receipt of the NE auto discovery message coming from the NE, the
NM’s AS (Alarm Surveillance) application generates a Warning alarm
into the specific “NE AUTO DISCOVERY” sublist. Then, the operator
has two choices:
z Navigate from the auto discovery alarm to “Create NE”
z Open the “NE Auto discovery” application from the TMN-OS and then click
on “Create NE”
z In both cases, the Create NE Dialog window is presented to the
operator.
Alcatel 1353NM

3JK Edition 1.00
What to do on NM [cont.]
1. In AS, click on
“External
Application Î
CreateNe”, or....
Next Page
1. ... from the TMN-OS,
click on “NE Auto-
Discovery Î Create
NEs
Alcatel 1353NM

3JK Edition 1.00
The
new
NE
1. Click on the NE
to be created 2. Optionally,
the operator
can modify
the NE
name or the
Location
name
4. Click on Create 3. Choose or leave

unspecified
Supervision Area
and EML domain
The NE can also be refused
Alcatel 1353NM

3JK Edition 1.00
The new NE has been created into

the NM database with the
parameters contained in the
“Create NE” window
Alcatel 1353NM

3JK Edition 1.00
ISA board auto discovery
z Also ISA board can be created using the NE auto discovery feature,
provided that:
1. The ISA board must be first created in the NE along with its IP address; the
DCN must be up and running with all the necessary IP over OSI tunnels.
2. By CT, issue the “NE auto discovery” window
3. After having selected the ISA board to auto discover, click on the “send”
button
4. A warning alarm is generated into the NM’s AS and the NM operator can then
open the “Create NE” dialog window
5. In this window, the parameters of the ISA board to be created are shown
and the user can modify some of them (NE name and Location name).
Clicking on “Create NE” the ISA board is created into the NM database.
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
2.6 Map population
Alcatel 1353NM

3JK Edition 1.00
2.6 Map population
Map and IM database
USM IM
icon N°1 NE1

(Map 1) NE1
icon N°2 NE1

(Map 2) NE2
Graphic database Processing database

Alcatel 1353NM
z The procedures for creating NEs which have been previously presented add an entry in the database of
the IM process and add an icon to the current submap (USM). This icon is linked to the entry in the IM
database.
z Several icons, even icons belonging to different maps, can be linked to a given database entry (i.e. an
NE).
z For NEs already created in the database, one more related icon can be added to any submap at any
time. To do this, the operator has to work from the “Global Inventory” (See next page).

3JK Edition 1.00
2.6 Map population
Populating the map from the OS MIB
z This procedure can be used to add an NE icon to a submap if the NE

already exists in the database
1. Select the menu Tools Î Ne Inventory Î Global
2. The list of the NEs already created appears
3. Select the targeted NEs from the list
Alcatel 1353NM

3JK Edition 1.00
2.6 Map population
Populating the map from the OS MIB [cont.]
4. Select the menu Inventory Î

Population
5. If necessary, change the
population selection
6. Click Apply then Close
Alcatel 1353NM

3JK Edition 1.00
2.6 Map population
Deleting an NE from a submap
z This action simply deletes the NE from the current submap and not
from the OS database
1. In the network topology view, select the NE to be deleted from the

submap
2. Select the menu Edit Î Cut
or Edit Î Delete
or Edit Î Delete from all views
Alcatel 1353NM

3JK Edition 1.00
2.6 Map population
Deleting a NE from the MIB
z This action deletes the NE from the OS database

1. Select a NE in the map and Declarations Î Delete Î Generic
2. Click Apply and Close after deletion
Alcatel 1353NM

3JK Edition 1.00
2 Managing and addressing a NE on a map
Exercise
z Exercise 1: Create and address a Q3 NE

z Exercise 2: Create and address a ISA Board
z Exercise 3: Create and address a 1850TSS-320 NE in
MSPP configuration
z Exercise 4: NE auto discovery feature
z Exercise 5: Map population
See next Pages
Alcatel 1353NM

3JK Edition 1.00
Exercise 1: Create and address a Q3 NE
z Create a NE
z Set the addresses of this new NE
Alcatel 1353NM

3JK Edition 1.00
Exercise 2: Create and address a ISA Board
z Configure all the parameters necessary to get

reachable the ISA board, both in the OMSN and in the
NM: IP addresses, IP over OSI tunnels, …
Alcatel 1353NM

3JK Edition 1.00
Exercise 3: Create and address a TSS-320 in MSPP config.
z Check the existence of the processes necessary to

manage a 1850TSS-320 NE
z Based on the DCN configuration:
z Create the NE
z Assign the address to the NE
z Set the IP routing configuration
z Create the IP over OSI tunnel if necessary
Alcatel 1353NM

3JK Edition 1.00
Exercise 4: NE auto discovery
z Perform the auto discovery procedure for a 1850TSS-

320 NE
Alcatel 1353NM

3JK Edition 1.00
Exercise 5: MAP Population
z Add a NE on the map from the OS MIB

z Remove from the MIB one of the previously created
NEs
Alcatel 1353NM

3JK Edition 1.00
3 Creating a graphical connection
Alcatel 1353NM

3JK Edition 1.00
Procedure
z Two symbols can be linked by a connection

z This connection is nothing else than a graphical object and therefore it is
not managed by the 1353NM as an SDH object
1. Open the submap
2. Click on the symbol which is the source of the connection (first NE)
3. Shift-Click on the symbol which is the destination of the connection
(second NE)
4. Select the menu Edit Î Add Connection
5. Select a Type in the list
6. Define a User Label
7. Click Apply and Close
Alcatel 1353NM
N.B. The User Label MUST be a unique name without spaces

3JK Edition 1.00
Final submap view
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Create a connection between two NEs
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
4 Addressing NEs with IP Tunnel: OSI over IP
Alcatel 1353NM

3JK Edition 1.00
4 Addressing NEs with IP tunnel: OSI over IP
Principle
z OSI over IP tunneling is a

technique that consists in the NM NE
insertion (encapsulation) of the
OSI traffic into IP packets. IS-IS IS-IS
ES-IS CLNP ES-IS CLNP
z The extremities of the tunnels
are typically a 1353NM server
and a NE.
z The DCN connecting the 1353NM
and the NE will carry IP packets.
z The NE and the 1353NM server IP Packets
need to support the OSI and IP
protocols; the routers only need IP network
to support the IP protocol.
Alcatel 1353NM
NE have to be compatible with this feature

3JK Edition 1.00
Network example
1353NM
CLNP
GRE
IP 802.2
Ethernet
IP network OSI network
OSI over IP OSI
GNE GNE
OSI
OSI NE OSI OSI
OSI over IP
NE OSI IP network NE OSI NE
GNE
Alcatel 1353NM
The OSI over IP can be used to:

1. Interconnect the 1353NM to a GNE through an IP network. In this case, the connectivity is provided
also with all the other NEs reachable from this GNE (e.g. using OSI protocol on DCC).
2. Interconnect the 1353NM to a Router through an IP network. In this case, 1353NM will be able to
manage all the NEs reachable via that router using OSI protocol.
3. Interconnect two NEs one to each other, e.g. one of them being located at customer premises and not
being reachable using DCCs, or one NE with a Router. In this scope, the OSI over IP feature of 1353NM
is not used.
Warnings:
z NM: max 32 tunnels per LAN I/F
z Tunnels give high processing load to terminating nodes
z Take care of L2 backbone design

3JK Edition 1.00
NE Configuration Procedure
z On the 1320 CT (Equipment view): (3)

1. Start the supervision of the NE
and Login
2. Choose the menu Configuration
Î Comm/Routing Î Interfaces
Configuration
3. Check that the Ethernet interface
is enabled
4. In the part IP Section, set the IP
address of the NE and the network
mask (4)
5. Click on Apply
(5)
Alcatel 1353NM

3JK Edition 1.00
NE Configuration Procedure [cont.]
6. Choose the menu ConfigurationÎ Comm/Routing Î Tunneling

Configuration Î OSI over IP
7. Set the Remote Destination IP Address to match the IP address of the
1353NM server
8. Click on Apply
(7)
(8)
Alcatel 1353NM
The IP address of the NM can be get by typing the command “cat /etc/hosts” in the UNIX terminal

3JK Edition 1.00
1353NM Configuration Procedure
z On the 1353NM:
1. From TMN-OSs
Management window,
select the 1353NM icon
and then Actions Î
1353NMAdmin
2. Select the menu
NE Administration and
OSI over IP Tunneling
Alcatel 1353NM

3JK Edition 1.00
1353NM Configuration Procedure [cont.]
3. Click on Create to open the corresponding window and enter the IP

address assigned to the NE’s Ethernet interface, or select an NE from
the GNE List (see next slides). Give the IP Tunnel ID (from 0 to 31).
1. Enter IP Address or
choose the GNE from the list
2. Define the 3. Create

IP Tunnel ID
Alcatel 1353NM

3JK Edition 1.00
GNE list
z The GNE list is manually created by the operator

z The 1353NM doesn't check information validity
z This list could be used to make easier the IP tunneling creation
1. Actions Î 1353NM Admin

2. NE administration Î List Gateway NE
Alcatel 1353NM

3JK Edition 1.00
GNE list [cont.]
Display
Filter
1. Select the NE 3. Enter the IP
address
2. Click here to if necessary
modify the (for IP
address tunneling)
Save data
Refresh on the
disk
4.Apply
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Set the GNE list to match the network structure

z Create an OSI over IP tunnel between 1353NM and an
NE
Alcatel 1353NM

3JK Edition 1.00
5 Distributing Maps
Alcatel 1353NM

3JK Edition 1.00
5 Distributing maps
Principle of distribution
DCN
DCN
Master server Presentation server
Local
LocalMaps
Maps USM Local
LocalMaps
Maps USM
Map Map
dB Distribute map dB
Get map distribute map
IM
Distributed
Distributed
DNM-IM
Network
NetworkMaps
MapsIM
IM
Maps
(DNM
(DNM -IM)
- IM)
Get
map DCN
Alcatel 1353NM
DNM: Distributed Network Map

Distributed maps are accessible from any workstation.
They are saved when the application is backed up.

3JK Edition 1.00
5 Distributing maps
Saving as distributed maps
1. Open the local map

2. Select File Î Save Map as…
3. Enter the Name of the
distributed map
4. Enter any useful comment
5. Click OK
6. After update, click Close
Opening again the same window …

Alcatel 1353NM

3JK Edition 1.00
5 Distributing maps
Retrieving distributed maps
1. Create a new
map; it must
be empty
2. Select File Î
Map
Management
3. Select the map
from the "Map
Tree" list
4. Click the
Retrieve
button
5. Click the
Close button
Alcatel 1353NM

3JK Edition 1.00
5 Distributing maps
Locked maps
PNM USM DNM IM PNM USM DNM IM

Local Local
displayed DNM displayed DNM
map map 1 map
map 1
map 4 map 4
map 2 map 2
map 3 map 3
map 4 *
After "save as" or " retrieve"
Alcatel 1353NM

3JK Edition 1.00
5 Distributing maps
Unlocking distributed maps
z A map is locked when it is opened to be modified, but it can always be

unlocked
1. Select the menu File Î Map Management
2. Select the map in the "Map Tree" list
3. Click the Unlock button
4. Click the Close button
Alcatel 1353NM
z A distributed map is marked by the system as “Locked” by the user who has retrieved it last. It is kept
Locked until this map is displayed by the Map Management.
z As soon as the user select a new empty map or retrieves another map, the Locked attribute is reset.
If another user (user2) issues the retrieving of a distributed map while it is Locked by another user
(user1), user2 must “Unlock” the map. This triggers two actions:
} user1 is warned that the map has been unlocked by user2
} the map is marked as locked by user2

3JK Edition 1.00
5 Distributing maps
Deleting a distributed map
z This operation deletes a map from the list of distributed maps

previously stored in the DNM database
1. Select the menu File Map Management
2. Select the map in the "Map Tree" list
3. Click the Delete button
Alcatel 1353NM

3JK Edition 1.00
5 Distributing maps
Exercise
z Distribute a map previously created

z Retrieve the map into a new local map
Alcatel 1353NM

3JK Edition 1.00
End of Module
Network Topology
Alcatel 1353NM

3JK Edition 1.00
Section 3
System Operation
Module 1
NE Supervision
3JK Edition 1.00


3JK Edition 1.00
Blank Page
System Operation · NE Supervision 3·1·2
Alcatel 1353NM
Document History

3JK Edition 1.00
Objectives
z To be able to
z supervise the NE
z use the simulator
z perform a MIB backup/restore
Alcatel 1353NM

3JK Edition 1.00
Objectives [cont.]
Alcatel 1353NM

3JK Edition 1.00
Table of Contents
Page
1 Displaying NE management and alarm state 7
2 Modifying the management states of a NE 21
3 NE simulator 39
4 Schedule a MIB backup 49
5 Backing-up/Restoring the MIB 55
Alcatel 1353NM

3JK Edition 1.00
Alcatel 1353NM
Alcatel 1353NM rel. 7.4B Operation ThisAllpage is left
Rights Reserved blank intentionally

3JK Edition 1.00
1 Displaying NE management and alarm state
Alcatel 1353NM

3JK Edition 1.00
Management states
z Supervision state
z Communication state
z Administrative state (not managed)
z Usage state (not managed)
z Alignment state
z Local access state
z Operational state (not managed)
z Alarm status
z NML assignment state
z Simulator state (for Q3 NE only)
Alcatel 1353NM
MIB alignment state

z for the Q3 NE: between the NE MIB and its representation in the simulator's database

3JK Edition 1.00
Supervision state
SUP
Starting
DECLARED supervision…
DEACTIVATING ACTIVATING
SUP
Stopping
supervision… SUPERVISED
Stable states Transient states

Alcatel 1353NM
Supervision state
z declared: the NE is simply created in the OS MIB but is not supervised
z supervised: the NE is under supervision
z activating: supervision is being started (no management task can be performed on the NE)
z deactivating: supervision is being stopped (no management task can be performed on the NE)

3JK Edition 1.00
Communication state
System Operation · NE Supervision 3 · 1 · 10
1353 NM 1353 NM has lost

communication
with the equipment
…
DISABLED
ENABLED
1353 NM The equipment can

be reached by the
1353NM …
Alcatel 1353NM
z Communication state
} Disabled: The Communication between the OS and the NE is interrupted
} Enabled: The OS can communicate with the NE
z N.B.: If the equipment is a 1850TSS-320 in MSPP configuration, it has a double communication link with
the OS (Q3 and SNMP). In this case the Communication state is Disabled only in case BOTH the links are
down.

3JK Edition 1.00
Alignment state
Stable states = 1353 NM

MIB
Transient states
ALIGNED
MIB
ALIGNING UP ALIGNING DOWN AUDITING
1353 NM
MIB MIB MIB
1353 NM 1353 NM 1353 NM
MISALIGNED
≠ 1353 NM
MIB
Alcatel 1353NM
Alignment state:
z Misaligned: The NE MIB and its image in the OS are not identical. Typically, the NE is in this state when:
} The Supervision state is “Not supervised”
} In case of Q3 or SNMP NE, when the communication link between the 1353NM and the NE is down
(Communication state = Disabled)
} In case of 1850TSS-320 MSPP NE, when the primary (Q3) or the secondary (SNMP) or both the
communication links are down
{ N.B.: In case only one of the communication links is down, the Communication state stays in
Enabled
z During the alignment phase, (Aligning up or down or Auditing), the shown Alignment State is still
“Misaligned”. It turns into “Aligned” when the alignment phase is finished
z Aligning Up: The system is performing a “MIB Align Upwards” operation. No operation can be done on
the NE
z Aligning Down: The system is performing a “MIB Align Downwards” operation. No operation can be done
on the NE
z Auditing: The NE is under OS supervision and the system is comparing the NE MIB with its image in the
OS
z Aligned: the system becomes aligned when all the operations for synchronizing the 1353NM with the NE
are fully completed. The synchronization procedure involves the alarms, the PM and NE.
z In Config: The NE is being configured and no alignment has been undertaken yet

3JK Edition 1.00
Local access state
Craft terminal
The NE allows
Key or LCA Read
access from the
is green craft terminal …
Write
GRANTED
Supervision Î Supervision Î
Access State Î Access State Î
Local OS
DENIED
The NE refuses
Key or LCA Read modifications
is blue from the craft
Write terminal …
Craft terminal
Alcatel 1353NM
Local access state

z granted: the local craft terminal can modify the configuration
z denied: the local craft terminal can NOT modify the configuration
z requested: the local craft terminal has asked permission to OS and is waiting for a response (granted or
denied)

3JK Edition 1.00
Alarm states
z The alarm state indicates the most critical alarm present on the NE
z Critical
z Major
z Minor
z Warning
z Active Pending
z Clear
z Indeterminate
Alcatel 1353NM
Indeterminate: the severity level cannot be defined by the resources which raise the alarm
Clear: no alarm

3JK Edition 1.00
NML assignment state
z It is accessible to the operator for reading only into the “Equipment

View”: (MGR box)
z Gives information about the NE assignment to 2nd (EML) or 3rd (NML)
level managers:
z RM
z SY manager
z NPOS
z EML manager
z …
Alcatel 1353NM

3JK Edition 1.00
Simulator state
Supervision Î
SIM Simulator Î
Start
DISABLED (in the equipment view)
DEACTIVATING ACTIVATING
ENABLED
Supervision Î
Simulator Î SIM Concerns
Stop Q3 NEs
(in the equipment view) only!
Stable states Transient states

Alcatel 1353NM
Simulator state
z disabled
z enabled
z activating: (no management task can be performed on the NE)
z deactivating: (no management task can be performed on the NE)
The availability of the simulator depends on the type and release of the NE

3JK Edition 1.00
Displaying NE states
z Display NE management states

1. In the network topology view, select sites, NEs or a single NE
2. Select the menu Operations Î Show Statuses
z Display NML assignment for an NE

1. In the network topology view, select a NE
2. Select the menu Tools Î View Equipment
3. Move the mouse over MGR icon
4. Read assignment on the bottom left of the window
z Display simulator state for an NE

1. In equipment view, move the mouse over SIM icon
2. Read simulator state on the bottom left of the window
Alcatel 1353NM

3JK Edition 1.00
Refreshing NE states
z An automatic refresh is performed at regular intervals

z To check that the NE states displayed are up to date, perform a manual
refresh
1. In the network topology view, select a site, one or more NEs

2. Select the menu Operations Î Resynchronize
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Display states for an NE

z Display states for a group of NEs
z Refresh the states for an NE
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
2 Modifying the management states of a

NE
Alcatel 1353NM

3JK Edition 1.00
2 Modifying the management states of a NE
Q3 or QB3* NEs: Starting supervision
1. In the network topology view, select one or more sites and NEs
2. Select the menu Operations Î Supervision Î Align up
or Î Align down
For a Q3 NE, start supervision uploads the NE MIB into the OS either Align up or Align
down is selected
3. Click on Apply in the
Supervision window
4. Wait for the result message to
be displayed
Alcatel 1353NM

3JK Edition 1.00
SNMP or 1850TSS-320 MSPP NEs: Starting supervision
1. In the network topology view,

select one or more sites and NEs
2. Select the menu Operations Î
Supervision Î No Alignment
3. Click on Apply in the Supervision

window
4. Wait for the result message to be
displayed
Alcatel 1353NM
z In case of 1850TSS-320 MSPP NE, during the “Set NE Address” phase only one of the two addresses
belonging to the NE (NSAP and IP) can be configured by the operator in the 1353NM (see Module
“Network Topology” for details). The 1353NM is in fact able to discover the missing address during the
start supervision procedure.

3JK Edition 1.00
How to ping an NE
z If the supervision doesn't start,

the good reflex is to ping the
NE:
z From the Map view, select the
relevant NE and issue:
Operations Î Ping NE
} A green bullet indicates that the
NE is reachable
} A red bullet indicates that the NE
is NOT reachable
Alcatel 1353NM

3JK Edition 1.00
How to ping an NE: 1850TSS-320 MSPP NE
z From the Map view, select the

relevant NE and issue:
Operations Î Ping NE
z The system pings both the
management interfaces of the
NE: Q3 and SNMP
z The reachable interfaces are
marked with a green bullet
z The non-reachable interfaces are
marked with a red bullet
z If one of the two interfaces is not reachable,

the supervision is still started, but:
z the NE alarm state is set to “Critical”
z the NE alignment state is set to “Misaligned
Alcatel 1353NM
If the Q3 interface is not reachable, a “Primary interface isolation” critical alarm is issued in AS.
If the SNMP interface is not reachable, a “Secondary interface isolation” critical alarm is issued in AS.
If both the Q3 and the SNMP interface are not reachable, a “Node isolation” critical alarm is issued in AS.
EML Coordinator 4G
EML-IM

adapter adapter
Q3 SNMP
TSS-320 MSPP
Q3 SNMP Example of TSS-320

Agent Agent in MSPP configuration

3JK Edition 1.00
How to ping an NE: Communication test Tool
z From the TMN-OS

window, select
Actions Î 1353NM
Admin, then NE
Administration, then
Ping NE:
the “Communication
Test Tool” appears
Display Filter
2.Ping selected
NE(s)
1.Select the NE(s)
Alcatel 1353NM

3JK Edition 1.00
How to ping an NE: Communication test Tool [cont.]
3.Results:
R: Reachable
U: Unreachable
Alcatel 1353NM

3JK Edition 1.00
Stopping supervision
z Stopping supervision:
z stops management of the selected NE
z deactivates alarm collection and configurations
z retrieves collected PM data from NE before closing the management session
Alcatel 1353NM

3JK Edition 1.00
Stopping supervision [cont.]
2. Select the menu Operations Î Supervision Î Stop
3. Click on Apply in the
Supervision window.
4. Wait for the result message

to be displayed.
Alcatel 1353NM

3JK Edition 1.00
Aborting supervision
z Aborting supervision
z stops management of the selected NE
z deactivates alarm collection and configurations
z NM immediately close the management session without collecting PM data
from NE
z faster than “stop supervision”
2. Select the menu Operations Î Supervision Î Abort Supervision
3. Click OK
Alcatel 1353NM

3JK Edition 1.00
Enabling/disabling NE operation access: Q3 and SNMP NE
z Access granted
z Configuration of the NE managed from a craft terminal only
z The OS continues to receive and process alarms and performance data
z The OS can switch back to the OS access state (access denied)
z Access denied
z NE managed by the OS only
IN THE NETWORK TOPOLOGY VIEW

1. Select one or more sites and NEs
2. Select the menu Operations Î Access State Î OS (CT denied)
or Î Local (CT granted)
3. Click OK
4. Wait for the “Local Access” icon in the equipment view to be updated:
z Green color for “CT denied”
z Light blue color for “CT granted”
Alcatel 1353NM
N.B.: Some SNMP NEs do not support this feature. For the NEs not supporting this feature it is not possible
to grant CT access while the 1353NM is supervising the equipment.

3JK Edition 1.00
En./dis. NE operation access: Q3 and SNMP NE [Cont.]
IN THE EQUIPMENT VIEW FROM 1353NM

1. Select the menu Supervision Î Access State Î OS (CT denied)
2. Confirm by clicking OK
IN THE EQUIPMENT VIEW FROM 1320CT

1. Select the menu Supervision Î Access StateÎ OS (CT denied)
or Î Requested
2. Confirm by clicking OK (check OS isolation)
z Light blue color for “CT denied”
z White color during the checking of the OS isolation. After that, the icon turns green
if the OS is isolated, turns light blue if the OS is reachable (i.e., when requested by
the CT, the access status can become “CT granted” only if the OS is isolated)
Alcatel 1353NM

3JK Edition 1.00
En./dis. NE operation access: 1850TSS-320 MSPP NE
z Due to the dual management domain of the 1850TSS-320 MSPP NE, the
Access State management is separately applied to the Q3 or to the
SNMP agent
IN THE NETWORK TOPOLOGY VIEW:

z Only the Access State of the Q3 management domain is impacted
1. Select one or more sites and NEs
2. Select the menu Operations Î Access State Î OS (CT denied)
3. Click OK
Alcatel 1353NM

3JK Edition 1.00
En./dis. NE operation access: 1850TSS-320 MSPP NE [cont.]
IN THE EQUIPMENT VIEW FROM 1353NM

z Q3 management domain:
2. Confirm by clicking OK
z SNMP management domain:

1. Select the PP20G card (data processor) and select the menu
Equipment Î Data Board Navigation
2. From the Data Management window, Select the menu
Supervision Î Access StateÎ OS (CT denied)
or Î Granted (CT granted)
(same colors as for the Q3 management domain)
Alcatel 1353NM

3JK Edition 1.00
En./dis. NE operation access: 1850TSS-320 MSPP NE [cont.]
IN THE EQUIPMENT VIEW FROM 1320CT

z Q3 management domain:
or Î Requested
2. Confirm by clicking OK (check OS isolation)
z Light blue color for “CT denied”
z White color during the checking of the OS isolation. After that, the icon turns green
if the OS is isolated, turns light blue if the OS is reachable (i.e., when requested by
the CT, the access status can become “CT granted” only if the OS is isolated)
z SNMP management domain:

1. Select the PP20G card (data processor) and select the menu
Equipment Î Data Board Navigation
2. From the Data Management window, select the menu
Supervision Î Access State Î OS (CT denied)
or Î Requested
3. Wait for the “Local Access” icon in the equipment view to be updated: (same
colors as for the Q3 management domain)
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Start the supervision of a Q3 or SNMP NE by alignment up

z Allow local access to this NE
z Stop supervision on this NE
z Start the supervision of a 1850TSS-320 MSPP NE
z Allow local access to the Q3 agent of this NE
z Allow local access to the SNMP agent of this NE
z Stop supervision on this NE
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
3 NE simulator
Alcatel 1353NM

3JK Edition 1.00
3 NE simulator
Principles
DB
DB
RM USM
USM
Physical
Physical
Network
Network USM
USM AS-IM
Management
Management AS
DB
DB
PNM-IM
Q3 EML-IM
NE
NE
NEs IDs simulator
simulator
E D
R T
DB
DB
T A
S
NE
NE DB
DB
Alcatel 1353NM

3JK Edition 1.00
3 NE simulator
Principles [cont.]
z Work on an NE or on the NE simulator, but never on both

z The NE simulator is used in cases of:
z DCN failure:
} the NE simulator is the only way for the 1353NM operator to look up the NE's
configuration (the configuration stored at the time of the last alignment).
z off-line configuration
z restoration of the NE MIB
z The simulator can be started only if the NE is in the “OS isolation” state
Alcatel 1353NM
The NE simulator is the NE software which runs on the 1353NM.

The availability of the NE simulator depends on the type and version of the NE.
The NE simulator is started up (and stopped) manually by the 1353NM operator.
The system never automatically starts or stops the NE simulator.

3JK Edition 1.00
3 NE simulator
Simulator and MIBs
1353NM
Simulator
simulator
MIB
Simulator
Align up Simulator
Align down
Q3
NE Not
active
MIB active
activate MIB
z In default configuration, the Simulator can be started only once at a

time on a given 1353NM
Alcatel 1353NM
Align up menu Supervision Î Simulator Î Align up

Align down menu Supervision Î Simulator Î Align down
Activate menu Supervision Î Simulator Î Activate

3JK Edition 1.00
3 NE simulator
Loading the simulator with a configuration
FROM EQUIPMENT VIEW

z Copy the configuration
of the real NE into the
simulator
z menu: Supervision Î
Simulator Î Align up
Alcatel 1353NM

3JK Edition 1.00
3 NE simulator
Off-line configuration
1. Start supervision
2. Upload the NE configuration into the simulator (align up)
3. Stop the supervision of NE (note 1)
FOR A NOT SUPERVISED EQUIPMENT:
4. Start the simulator: Supervision Î Simulator Î Start

5. Modify the configuration (note 2: 1354RM can do it)
6. Stop the simulator: Supervision Î Simulator Î Stop
7. Start supervision (changes done in the simulator don't appear)
8. Align the simulator's MIB down to the NE
z Supervision Î Simulator Î Align down
9. Activate the new configuration
z Supervision Î Simulator Î Activate
z wait for communication to be re-established following “OS Isolation”
Alcatel 1353NM
note 1:
Caution: stopping the equipment supervision in order to use the simulator, the “OS isolation” state will
occur after a few minutes.
note 2:
The 1354RM can update the simulator. This feature is used for the equipment controller card replacement
procedure (i.e in OMSN).

3JK Edition 1.00
3 NE simulator
Off-line browsing
FOR A SUPERVISED EQUIPMENT in OS ISOLATION state:
1. Start the simulator: Supervision Î Simulator Î Start

2. Display the configuration
z last known configuration
z last NE alarm state
3. Stop the simulator: Supervision Î Simulator Î Stop
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
3 NE simulator
Exercise
z Display the on board simulator state window

z Align up the supervised NE in the simulator
z Activate the off-line configuration
z Add a board
z Restart the NE supervision and activate the modifications made in the
simulator
z Restore the NE's original configuration
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
4 Schedule a MIB backup
Alcatel 1353NM

3JK Edition 1.00
Schedule a MIB backup
1. From network view:

Operations Î FT Scheduler
2. Select Job Î New
Alcatel 1353NM
z FT Scheduler can be used for two purposes:

} MIB backup
} software download.
z This training manual’s module addresses the MIB backup. The software download is addressed by
another training manual’s module.
z Selecting some NEs in the map and afterwards issuing FT Scheduler, the FT Scheduler window is opened
as Software Download task and is automatically populated with the selected NEs.
z FT Scheduler can also be started from the TMN-OS Window: issue Actions Î 1353NM Admin Î NE
Administration Î FT Scheduler
z For the nodes that support the simulator, FT Scheduler updates the simulator. In order to restore the
simulator’s data to the NE, the « Simulator Î Align down » command must be issued.
z For the nodes that don’t support the simulator, FT Scheduler creates a MIB backup named « fts » . In
order to restore the backup to the NE, the « Download Î Mib management » window must be used.

3JK Edition 1.00
Schedule a MIB backup [cont.]
3. Enter the job

“Name” and
“Optional Info”
4. Click on the right 3
arrow and
answer "yes" to 5
the question 4
“A job may be
for SWDL or
backup. Do you
want a backup
Job ?”
5. Set Activation
Date and Time
Alcatel 1353NM

3JK Edition 1.00
Schedule a MIB backup [cont.]
6. Select the backup

session and then
click on the right
arrow to create a NE
7. Select the NE box 7
and choose the NE
8. If required, select
the parameter
“misalignment flag” 6
9. Save your job with
the “save” button 8
10. Submit your job with
the “submit” button
11. Click on “yes” if you
want to see the
status of the running 9
job
10 11
Alcatel 1353NM
z In the « Save as » window, write the job name in the bottom line
z The parameter “misalignment flag” is used to avoid the NE Configuration upload towards the Simulator
when the two entities are already aligned.

3JK Edition 1.00
Monitor MIB backup schedule
z To see the status of the

running: Job Î Show Backup
running job… on the File
Transfer Scheduler window
z To see the result of backup:

Job Î View Backup Report…
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Schedule a MIB backup for one NE

z Display the status while job is running
z Display the report
Alcatel 1353NM

3JK Edition 1.00
5 Backing-up/Restoring the MIB
Alcatel 1353NM

3JK Edition 1.00
Principle
This function is available only for Q3 and SNMP NEs which have no
simulator into the 1353NM system.
1353NM
file
modification
backup restore
Q3 Not
NE active active
MIB activate MIB
Alcatel 1353NM
The Q3 NE modifications carried out by means of 1353NM (or 1320CT) are performed directly on the NE
MIB.
The backup copies the NE MIB into a file in 1353NM.

3JK Edition 1.00
Backing up the configuration
z Q3 and 1850TSS-320 MSPP NEs:

1. In Equipment view, select the menu
Download Î MIB management
2. Enter a name for the backup
3. Click Backup and confirm with OK
} wait for the message
backup successfully completed!
to be displayed
z SNMP NEs:
z The commands and associated menus to be selected into the equipment
view are specific for each single NEs, so please refer to the Operator
Handbooks and to the Training Manuals of each single NE family.
Alcatel 1353NM

3JK Edition 1.00
Restoring the configuration
z Q3 and 1850TSS-320 MSPP NEs:

1. In Equipment view, select the menu
Download Î MIB management
2. Select the backup to be restored
3. Click Restore
} wait for the message
Restore completed
to be displayed
4. Click Activate and confirm
z SNMP NEs:
view are specific for each single NEs, so please refer to the Operator
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Perform a backup
z Modify the configuration of a NE (for example, add a
board)
z Perform a restore
z Check that the change made previously has been
overwritten by the restore operation
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
End of Module
NE Supervision
Alcatel 1353NM

3JK Edition 1.00
Section 3
System Operation
Module 2
NE Management
3JK Edition 1.00


3JK Edition 1.00
Blank Page
System Operation · NE Management 3·2·2
Alcatel 1353NM
Document History

3JK Edition 1.00
Objectives
z To be able to
z perform the basic management operations on Q3,
1850TSS-320 MSPP and SNMP NE
Alcatel 1353NM

3JK Edition 1.00
Objectives [cont.]
Alcatel 1353NM

3JK Edition 1.00
Table of Contents
Page
1 NE time management from the 1353NM 7
2 Performing a remote inventory 13
3 Resetting a NE 24
4 Downloading software to the NE 28
5 List abnormal conditions 47
6 Event log archiving 53
Alcatel 1353NM

3JK Edition 1.00
Alcatel 1353NM
All Rights blank

3JK Edition 1.00
1 NE time management from the

1353NM
Alcatel 1353NM

3JK Edition 1.00
1 NE time management from the 1353NM
NE and OS date and time
z The NM realigns the time of all

the NEs supervised by default
every 24 hours.
z The NE's local time can be
displayed and/or configured.
1. Open the equipment view of a

NE.
2. Select the menu Configuration
Î NE Time
3. If the time does not need to be
modified, click Close
4. To align the time of the NE on
the OS time, click Set
Alcatel 1353NM
z The NE time can be manually set equal to the NM’s time only if the Network Time Protocol (NTP) is not
enabled on the NE.
z The “Start supervision” action issued from the 1353NM’s map can enable the NTP on the NE; the
address of the 1353NM is automatically written as main NTP server in the NE comm/routing
configuration.
Ask the system administrator whether this feature is enabled.

3JK Edition 1.00
Getting the NE time
z This action is used to display the

time and date of a number of
NEs.
1. In the network view, select the
relevant NEs
2. Select: Operations Î Time Î
Get
3. Click Apply
z For each NE, a message is
displayed:
z “Working”: until the response from
the NE to the Get request has
been received
z NE date and time: when the
response from the NE has been
received (and is correct)
Alcatel 1353NM
This operation is allowed only if the NE is under supervision and its operational state is ENABLED.

3JK Edition 1.00
Setting NE time
System Operation · NE Management 3 · 2 · 10
z This action is used to send the OS

time and date to a number of NEs.
1. In the network view, select the
relevant NEs
2. Select the menu: Operations Î
Time Î Set
3. Click OK
z Each selected NE sends a response
to the setting request
z Date and time values if the request
has been executed correctly.
z “Processing failure with args”, if a
problem has occurred.
} If the NE has the NTP protocol enabled,
the “Set time” procedure fails
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Set the time (on the OS time) for a NE

z Display the time of the NEs in a domain
z Set the time (on the OS time) for a selection of NEs
on the map
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
2 Performing a remote inventory
Alcatel 1353NM

3JK Edition 1.00
Remote Inventory content
z ALCATEL company Identifier

z Mnemonic of the R.U.
z Unit part number
z Software part number
z CLEI code
z Factory number
z Unit serial number
z Date identifier
z Date
z R.U. inventory field for the customer
Alcatel 1353NM
ALCATEL company Identifier: This field contains the abbreviation of the company using 4 characters
(uppercase). For instance: ACIT , ASEL , ATEL , ALCL
Mnemonic of the R.U.: The mnemonic of the R.U. gives information about the type (function) performed by
the R.U. (e.g. STM1 I/O , MATRIX ,....). This mnemonic is suggested to be identical to the printed name
on the front panel of the unit.
Unit part number: The Unit Part Number is the Alcatel code to identify the R.U. This number includes the
ICS at the end.
Software part number: The Software Part Number is the Alcatel identifier of the resident software
supported by the R.U. It is an Alcatel code to identify the resident software of the R.U. considered as a
single piece.
CLEI code: CLEI Code is specified in Bellcore recommendations. When this field is not used, it is filled with
10 characters.
Factory number: It identifies the manufacturing plant within the company. 4 characters to be used.
Unit serial number: This number specifies the manufacturing chronological number of this R.U. type (in the
current year)
Date identifier: The date identifier specifies the meaning of the date field. The following codes are
standardized:
z 00 manufacturing date which corresponds to the end of the test phase
z 01 date of the manufacturing order
z 02 date of manufacturing R .U. lot
z 03 date of customer delivery
z 04 date of customer order
Date: Date format: YYMMDD. When the year only is defined the field shall be encoded as “YY----“.
R.U. inventory field for the customer: This field is reserved for the customer inventory information. The
customer data are loaded into the EEPROM during the manufacturing process only.
3JK Edition 1.00
For the whole NE subrack
z To perform this
remote inventory
1. From PNM, select the
NE
2. Select menu
Operations Î
Upload Remote
Inventory
3. Click on Apply and
wait for completion
message
4. To display the result,
select menu
Operations Î
Display Remote
Inventory
5. From the Remote
Inventory display
window, select File
Î Print to print the
Remote Inventory file
Alcatel 1353NM
This action can also be undertaken from equipment view
1) In equipment view, select menu Supervision Î Upload Remote Inventory

2) Wait for completion message
3) To display the result, select menu Diagnosis Î View Î Remote Inventory

3JK Edition 1.00
For a single NE’s board: Q3 or 1850TSS-320 MSPP NE
z To perform this remote inventory

1. In equipment view, select a board in the NE
2. Select menu Equipment Î Remote Inventory Î Board Level
Alcatel 1353NM

3JK Edition 1.00
For a single NE’s board: SNMP NE

view are specific for each single NE, so please refer to the Operator
Alcatel 1353NM

3JK Edition 1.00
Remote inventory to printer or file
1. In equipment view, select a board in the NE

2. Select menu Equipment Î Remote Inventory Î Subrack Level
3. Choose Printer or File as destination
4. If you choose File, select the destination file and Output format
5. Click OK
Alcatel 1353NM
This operation is not possible in case of SNMP NE

3JK Edition 1.00
Remote inventory wizard
z To open this wizard:

Select Operations Î
Remote Inventory Wizard
z This wizard can be used for

two different purposes:
1. To upload and view the
remote inventory of the
NE(s)
2. To look for the NEs that
host a specific card
Alcatel 1353NM

3JK Edition 1.00
Remote inventory wizard: upload and view the RI
1. Select “Display RI”.

Get it green.
2. Select the NE(s).

Get it green.
3. Click the magic wand
Alcatel 1353NM

3JK Edition 1.00
Remote inventory wizard: cards in which NE(s)
1. Click Search RI
3. Do Search
2. Enter the
Unit type or
part number
(case
sensitive)
Clicking on the
arrow opens
the USM view
of the relevant
equipment 4. The Nes
hosting
that card
Alcatel 1353NM
This function allows to search for boards of a given type deployed in the network.
A21E1 is a 2Mbit/s access cars for the OMSN equipment (1650SMC, 1660SM, …).

3JK Edition 1.00
Exercise
z Perform a NE subrack remote inventory from the

MAP
z Perform a remote inventory for a board
z Search for a given board in the network (for example
CONGI)
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
3 Resetting a NE
Alcatel 1353NM

3JK Edition 1.00
3 Resetting a NE
From equipment view
z A NE reset may be necessary in certain failure situations.

z This operation resets, shuts down and restarts all the processes
currently running on the NE
z Traffic is unaffected.
1. Open the NE's equipment view.

2. Select the menu: Supervision Î Restart NE
3. The communication between the NE and the OS is lost for a few
minutes.
Alcatel 1353NM

3JK Edition 1.00
3 Resetting a NE
Exercise
z Perform a NE reset
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
4 Downloading software to the NE
Alcatel 1353NM

3JK Edition 1.00
Set the server name (Q3 and 1850TSS-320 MSPP NEs)
1. In EMLUSM, select the menu

z Download Î Servers
management...
2. Select “local” (the local server is
automatically chosen)
3. Click Close
Alcatel 1353NM
If “local” is not available in the server list, write “local” in the “Software server name”, close and reopen
the window.

3JK Edition 1.00
Set the server name (SNMP NEs)

Alcatel 1353NM

3JK Edition 1.00
Downloading (Q3 NEs)
1. In the equipment view, select the

menu
z Download Î Init download
2. Select the SW Release to be
downloaded
3. Click OK and confirm the download
z wait for the message “Software
download completed!” to appear in
the download window.
Alcatel 1353NM
Thanks to the file transfer Dynamic Bandwidth Optimization (DBO) feature implemented in the 1353NM
Rel 7.4, significant improvement can be obtained in the Software download time (up to twenty time
quicker than without DBO)

3JK Edition 1.00
Downloading (1850TSS-320 MSPP NEs)
1. In the equipment view, select

the menu
z Download Î Init download
2. Select the SW Release and the
Package (Transport, Data or
Multiservice) to be
downloaded
3. Click OK and confirm the
download
z wait for the message “Software
download completed!” to
appear in the download
window.
Alcatel 1353NM

3JK Edition 1.00
Downloading (SNMP NEs)

Alcatel 1353NM

3JK Edition 1.00
Activating the new software (Q3 and 1850TSS-320MSPP NEs)
1. In EMLUSM, select the menu

z Download Î Units info... SW Release
2. Select the tab that corresponds to the

Standby software (look in Current
state\Action field)
z In the Current state\Action pull-down menu,
select Activate
3. Click OK and confirm

z wait for Q3 communication to be
re-established (it may be necessary to
restart EMLUSM)
Alcatel 1353NM

3JK Edition 1.00
Activating the new software (SNMP NEs)

Alcatel 1353NM

3JK Edition 1.00
Schedule a SW Download
1. From network view: Operations Î FT Scheduler

2. Select Job Î New
Alcatel 1353NM
The FT Scheduler can also be started from:

z TMN-OS Window: issue Actions Î 1353NM Admin Î NE Administration Î FT Scheduler
Selecting some NEs in the map and afterwards issuing FT Scheduler, the FT Scheduler window is opened as
Software Download task and is automatically populated with the selected NEs.

3JK Edition 1.00
Schedule a SW Download [cont.]
3. Enter a “Job
3 name” and
“information”
(optional)
4. Click on the
5
right arrow and
4 answer “no” to
the question
“A job may be
for SWDL or
backup. Do you
want a backup
Job ?”
5. Set Activation
Date and Time
Alcatel 1353NM

3JK Edition 1.00
6. Select the session and

then click on the right
arrow to create a NE
7. Select the NE
7
8. Optionally, select the
server hosting the SW
9. Select the SW package
to download
6
10. Save your job with the
“save” button
11. Submit your job with 8
the “submit” button
12. Click on “yes” if you
want to see the status 9
of the running job
10 12
11
Alcatel 1353NM
In the « Save as » window, write the job name in the bottom line

3JK Edition 1.00
z When dealing with a

1850TSS-320 NE, at step 9
the operator must also
choose the Package Type
among:
z 1850TSS320D (Full Data
Configuration)
z 1850TSS320M (MSPP
Configuration)
z 1850TSS320T (PTRP
Configuration)
Alcatel 1353NM

3JK Edition 1.00
Monitor SW Download schedule
z To see the status of the running

job, the user can also select
menu Job Î Show SWDL
running job… on the File
Transfer Scheduler window
z There’s also “View SWDL

Report”
Alcatel 1353NM

3JK Edition 1.00
Stop a running job

z The user can stop a

scheduled SW
download on a
single NE or on a
group of NEs.
1. Select the relevant
NE(s) 1
2. Click on Abort
3. Confirm clicking on 2
Yes
Alcatel 1353NM

3JK Edition 1.00
See the SW status of the managed NEs
z In order to see the

SW status of the
managed NEs:
1. on the File Transfer
Scheduler, issue the
menu SW Status
2. select i.e. All NEs
z The NE SW status
can be exported in a
CSV file
Alcatel 1353NM

3JK Edition 1.00
See the SW status of the managed NEs [cont.]
z To get SW status details or to perform actions, double click on the

desired NE
Click here to
get the SW
status details
Select the
action and then
“Apply Action”
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Download software to the NE

z CAUTION: the download may take some time
Alcatel 1353NM
Thanks to the file transfer Dynamic Bandwidth Optimization (DBO) feature implemented in the 1353NM
Rel 7.4, significant improvement can be obtained in the Software download time (up to twenty time
quicker than without DBO)

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
5 List abnormal conditions
Alcatel 1353NM

3JK Edition 1.00
List the NEs in abnormal condition
3.Navigate to
1.Select AC the NE’s USM
viewer
2.Eventually select
the involved NE(s)
Refresh the NE list

in the window
Alcatel 1353NM
AC information is retrieved from EMLIM every 15 minutes

Automatic refreshment period can be set-up from menu Option Î Set Automatic refresh

3JK Edition 1.00
Display the AC for one NE (Q3 and 1850TSS-320 MSPP)
1. Open the equipment view (EMLUSM)

2. Select menu Diagnosis Î Abnormal Condition List
3. In the AC List window, it is possible to double click on one item to
navigate to the USM view related to that item.
Alcatel 1353NM

3JK Edition 1.00
Display abnormal condition list for one NE (SNMP NE)

Handbooks and to the Training Manuals of each single NE family
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Create an AC on a NE (for example a loop-back)

z Display the NEs in abnormal condition status
z Display the list of AC for this NE
z Suppress the AC
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
6 Event log archiving
Alcatel 1353NM

3JK Edition 1.00
Q3 Event Log Browsing
z By the EMLUSM, the user has the possibility to browse the event log
stored in the MIB of that single NE by issuing the command:
z Diagnosis Î Log Browsing Î Event Log
Alcatel 1353NM

3JK Edition 1.00
Q3 Event Log Browsing [cont.]
z The event records can be filtered by the user per type and time:
Alcatel 1353NM

3JK Edition 1.00
Q3 Event Log Browsing [cont.]
Example of
Event Log
Display
window
Alcatel 1353NM

3JK Edition 1.00
Q3 and SNMP NE Event Log Archiving
z The NE Event Log is not persistent after the NE restart.

z 1353NM gives the possibility to save on a persistent file the Q3 and the
SNMP Events selected by the operator.
z This operation must be performed in two steps:
1. Configure the Log: the operator can select a subset of notifications that
wants to store into the persistent file
2. Retrieve the archived event notification
z The administrator can then manage the Event Log File to produce a
text file with event fields translated like ELB application.
z The log file creation is allowed only to Administrator user in order to avoid
log files proliferation and because only Admin can run a text editor on NM
machine.
Alcatel 1353NM

3JK Edition 1.00
Configure the Log
1.From the TMN-OS, select

Actions Î NE Event
Archiving Configuration
2. Select Q3 or SNMP
as protocol
3.Select the notification to

be stored in the
persistent file 5. Cancel to close
the window
4.Enable Filter and
confirm clicking Yes in
the confirmation window
Alcatel 1353NM

3JK Edition 1.00
Retrieve the Archived Events
1.From the Map, select the

desired node and then issue
Operation Î Event Log
Display
2. The Log file is shown
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
End of Module
NE Management
Alcatel 1353NM

3JK Edition 1.00
Section 4
Maintenance Applications
Module 1
Alarm Management
3JK Edition 1.00


3JK Edition 1.00
Blank Page
Maintenance Applications · Alarm Management 4·1·2
Alcatel 1353NM
Document History

3JK Edition 1.00
Objectives
z To be able to
z handle the AS application for current alarms and the alarm
history
Alcatel 1353NM

3JK Edition 1.00
Objectives [cont.]
Alcatel 1353NM

3JK Edition 1.00
Table of Contents
Page
1 Displaying current alarms 7
2 Alarm debouncing 17
3 Creating, modifying and deleting an alarm sublist 25
4 Performing actions on current alarms 37
5 Displaying the alarm history 45
6 Handling the AS facilities 55
7 Administrating the AS 63
Alcatel 1353NM

3JK Edition 1.00
Page
Alcatel 1353NM

3JK Edition 1.00
1 Displaying current alarms
Alcatel 1353NM

3JK Edition 1.00
AS principles
Real Time Static analysis

Management
Display alarms Manage alarms Display alarms
Current Archive Archived

alarms alarms alarms
Alarm Surveillance
Raise and clear alarms
Network
resources
Alcatel 1353NM
The AS is designed to receive, store and display in real time the alarms generated by different sources
(CURRENT ALARMS)
The AS provides the option of archiving and retrieving alarms (ALARM HISTORY)

3JK Edition 1.00
Current alarms and alarm history
z Current alarms:
z “live” alarms (permanently refreshed)
z Alarm history:
z cleared AND acknowledged alarms
z alarms purged by operators (even non-cleared alarms)
z overflow of the current alarm list
Alcatel 1353NM
Maximum number of current alarms: up to 10,000

The alarm history is used to monitor the activity of the network and the recurrence of problems and to
help the operator detect the critical points on the network.

3JK Edition 1.00
Starting AS
Maintenance Applications · Alarm Management 4 · 1 · 10
z Select the “alarm” icon in the list of applications or Alarms in Actions

menu.
OR
Flag to indicate new

alarms in the sublist
Alcatel 1353NM
Inactive sublists have all their counters set to “x”

To activate a sublist:
z select the sublist
z select menu Sublist Æ Activate

3JK Edition 1.00
Different levels of information
Starting point of AS Operator request
alarms Counter Alarm More

summary sublist information
Actual network Global vision Local vision Detailed vision
Increasing
detail
Alcatel 1353NM

3JK Edition 1.00
Displaying a sublist
z Select a sublist in the “counter summary” window

z Double click on it OR select Sublist Î Open
Alcatel 1353NM

3JK Edition 1.00
Displaying more information
z Select an alarm in the sublist

z Double click on it OR select Display Î More Info...
Alcatel 1353NM
Further info is displayed selecting the other menus

3JK Edition 1.00
Monitoring new alarms
z This function automatically displays the AS window when a new alarm

appears.
1. Start AS Current USM
2. Activate the “auto-raise” function
z check the option in the menu Display Î Auto-Raise
3. Minimize the window
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Start the AS application

z Display a sublist containing alarms
z Display more information on a given alarm
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
2 Alarm debouncing
Alcatel 1353NM

3JK Edition 1.00
2 Alarm debouncing
Principles
z Alarm debouncing consists in holding the Clear events (no propagation

to AS and upper Managers) for a given period, to check whether a new
Raise of the same Probable Cause on the same NE resource is generated.
z If the alarm is raised again, the Clear notification is not propagated to
upper managers, and the record in the AS is kept with Repetition
Counter attribute increased by one.
z If the alarm is not raised within the hold period, the Clear event is
normally propagated. The Clear Time is kept according to the NE
timestamp.
z Alarm debouncing reduce the number of records stored/displayed in
the AS Current Alarm List and the related traffic to the upper managers
(1354RM, 1354BM, etc).
Alcatel 1353NM

3JK Edition 1.00
2 Alarm debouncing
Principles [cont.]
Alarm Raise Event Alarm Clear Event
Alarm ON To End-Customers,
T1-T6 is the faulty
Alarm OFF period as a whole,
T1 T2 T3 T4 T5 T6
in which the
resource is not able
Resource Probable Event Clear Repetition to support a given
Name Cause Time Time Counters function
XXXX YYYY T1 T2 0
XXXX YYYY T3 T4 0
Debouncing ON
XXXX YYYY T5 T6 0
Resource Probable Event Clear Repetition

NO Name Cause Time Time Counters
Debouncing
XXXX YYYY T1 T6 2
Alcatel 1353NM
The Feature applies to alarms notified by Q3 and SNMP agents

3JK Edition 1.00
2 Alarm debouncing
Architecture Overview
Alcatel 1353NM
The Feature applies to alarms notified by Q3 and SNMP agents

3JK Edition 1.00
2 Alarm debouncing
Configuration
1. Select Actions Î Alarm Debouncing
3. Select and
configure the
2. Select the Hold Period
Probable
Cause 4. Click on Apply
5. Save and Exit
Alcatel 1353NM
Only Operators with Administrator or Constructor privileges can configure the Hold Period in the
debouncing GUI.
Multiple Probable causes can be selected and associated to the same Hold Period.
Debouncing filter values have a network-wide scope (they apply to all NEs supervised by 1353NM).
Default value: no debouncing (Hold Period = 0) on any Probable Cause.
The “Save” command automatically triggers the relevant EMLIMs to update the new table of Hold Periods.

3JK Edition 1.00
2 Alarm debouncing
Alarm Debouncing Case
Raise
T1
Raise Clear
T1 T2
T1 T2 T3
Alcatel 1353NM
r01/sr1/sl33
Bouncing Alarm

3JK Edition 1.00
2 Alarm debouncing
Alarm Debouncing Case [cont.]
T1 T2 T3 T4
T1 T2 T3 T4 T5
Alcatel 1353NM
r01/sr1/sl33
Bouncing Alarm

3JK Edition 1.00
2 Alarm debouncing
Alarm Debouncing Case
T1 T2 T3 T4 T5 T6
T1 T2 T3 T4 T5 T6
Hold Period
expiration
Alcatel 1353NM
r01/sr1/sl33
Bouncing Alarm

3JK Edition 1.00
3 Creating, modifying and deleting an

alarm sublist
Alcatel 1353NM

3JK Edition 1.00
3 Creating, modifying and deleting an alarm sublist
Create or modify a sublist
z To create an alarm sublist, select Sublist Î Create

z To modify it, select Sublist Î Modify and Sublist Properties window
is displayed
Alcatel 1353NM

3JK Edition 1.00
Create or modify a sublist
z This window is made up of several items:

z DISPLAY to identify the sublist appearance
z FILTER to select alarms to display in the sublist
z SORT sort criteria for the alarms in the sublist
z TRIGGER actions to be taken in case of an alarm
Alcatel 1353NM

3JK Edition 1.00
Sublist DISPLAY parameters
Sublist Sublist
name color
(single click
to modify)
Other available To
attributes (to display
move to the
displayed Currently
attributes list, displayed
select and click attributes
on the arrow) in the
sublist
(select and
click on the
Click here to To hide arrow to
apply the remove
modifications from the
list)
Alcatel 1353NM

3JK Edition 1.00
Sublist FILTER parameters
To save
your filter
To select a
saved filter
Alcatel 1353NM

3JK Edition 1.00
Sublist FILTER parameters - Basic
Filter by date Filter by

and time status
attribute
Filter by
severity
Filter by
alarm type Filter by
probable
cause (click
Filter by on “Select…”
correlation to make your
parameter choice)
Alcatel 1353NM

3JK Edition 1.00
Sublist FILTER parameters - Source
Select Instance
to filter a
specific
Managed Object
as alarm source
By comparing a
string with the
Friendly Name
Option to filter
by alarm class
Alcatel 1353NM

3JK Edition 1.00
Sublist FILTER parameters - Advanced
Select to filter a
specific
Management
System as alarm
source
Select to filter
by Specific
Problem
Select to filter by
Expiration Status
Select to filter by
Trouble Ticket
assignment
Select to filter by
Repetition
Counter value
Alcatel 1353NM

3JK Edition 1.00
Sublist SORT parameters
To
save
your
sort
choice
To select a
saved sort Parameters
used to sort
the sublist
Parameters not
used to sort the
sublist (select and Click here to
click on the arrow select the
to use one) sorting order
(increment or
decrement)
Alcatel 1353NM

3JK Edition 1.00
Sublist TRIGGER parameters
Activate this option to

receive a beep each time an
alarm appears in the sublist
To have a blinking warning

that a script is being
executed
To execute a script if the

number of alarms in the
sublist is greater than a
given value or for an
incoming alarm
To execute a script if the

number of alarms in the
sublist is smaller than a
given value or for an
outgoing alarm
Alcatel 1353NM
By executing the script you could, for example, load a particular process as soon as the number of critical
alarms exceeds a certain value.

3JK Edition 1.00
Exercise
z Create a sublist
z Choose a name and a color for the sublist
z Set the filter to select only:
z cleared alarms
z unacknowledged alarms
z alarms in the last 24 hours
z Sort the sublist by “event date & time” and “severity”
z Set the sublist parameters to emit a tone for incoming alarms
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
4 Performing actions on current alarms
Alcatel 1353NM

3JK Edition 1.00
Reserving / unreserving an alarm
z Reservation ensures that you are the only operator responsible for an
alarm
z To reserve:
1. open a sublist
2. select an alarm
3. select Action Î Reserve
z To unreserve:
1. open a sublist
2. select the reserved alarm
3. select Action Î Unreserve
Alcatel 1353NM
An alarm can be reserved only if it has not been reserved before by another operator.
The only operator who can unreserve a given alarm is the one who reserved it.

3JK Edition 1.00
Generating trouble tickets
z Trouble ticket = collection of all

information about one problem
1. Open a sublist
2. Select a single alarm or a group of
alarms
3. Select Action Î Trouble Ticket...
4. Confirm
z the indicator in the sublist change to
YES
Alcatel 1353NM
A trouble ticket contains at least the information on the problem, but can also include information on the
actions performed to solve the problem.
AS can be customized to interface with the third-party Trouble-Ticketing management product ARS
(Action Request System - published by Remedy Corporation).
If AS is configured to run without ARS, all menus concerning the management of trouble tickets are
inaccessible (i.e. grayed).

3JK Edition 1.00
Acknowledging
z By acknowledging alarms,
you indicate that they
have been registered.
1. Open a sublist
2. Select one or a group of
alarms
3. Select Action Î
Acknowledge
z the state changes from
NACK (Non ACKnowledge)
to ACK (ACKnowledge)
4. In the new window, add
the user notes (optional)
and do OK
Alcatel 1353NM
Acknowledging a cleared alarm is an implicit archiving action. So the acknowledgement will archive the
cleared alarms and remove them from the current alarms list.
The user notes are reported in the “More Info…” of the alarm.
Erase and Append: although the second, third,… acknowledge actions on the same alarm give a “Failure”
report, by means of the second, third, … acknowledge actions on the same alarm it’s possible to update
the user note:
z Erase: the new user note replaces the previous one
z Append: the new user note is appended to the previous one

3JK Edition 1.00
Manual purge
1. Open a sublist
2. Select one alarm or a group of
alarms
3. Select Action Î Manual Purge
z Purged alarms disappear from the
current alarms list and are
archived, if they match the
archiving filter.
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Reserve an alarm
z Try to unreserve an alarm reserved by an other user
z Unreserve the previously reserved alarm
z If ARS is active generate a trouble ticket for an alarm
z Acknowledge a cleared alarm (note the effect on the sublist)
z Acknowledge a not cleared alarm (note the effect on the
sublist)
z Unreserve the previously reserved alarm
z Purge alarms (cleared, not cleared, acknowledged, non
acknowledged)
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
5 Displaying the alarm history
Alcatel 1353NM

3JK Edition 1.00
Description
z The Historical Alarm List (HAL) contains former current alarms that
have been archived through one of the following processes (if these
alarms match the archiving filter):
z auto-purging
z manual purging
z overflow
z acknowledged and cleared alarms
z synchronization
Alcatel 1353NM
Auto-purging
z these alarms have never been inserted in the Current Alarm List (CAL).
Manual purging
z an AS operator has manually removed one or more selected alarms from the CAL.
Overflow
z Maximum size of the CAL has been reached and alarms are removed from it
Synchronization
z Alarms that are not confirmed on a synchronization command are automatically cleared by the
application. Among them, those which were previously acknowledged are forwarded to the HAL.

3JK Edition 1.00
Principle
CAL or auto purge filter Automatic

Archiving filter Operator action
HAL HAL
(HP LOG) (Public Archive)
filter filter
Sublist
Main
list
filter Save selection
User file User file User file User file
Alcatel 1353NM
The HAL is stored using a specific ad-hoc format (the Public Archive format). This repository receives all
the alarms passing through the Archiving filter.
You can store a set of alarms (put together by selecting from the Main List or any sublist) in a user-
defined file. You can then retrieve alarms from this file instead of from the HP-Log or Public Archive, or
in conjunction with this source.

3JK Edition 1.00
Starting up
z In the Current Alarm List, select Navigation Î Archive

z Do Yes to confirm the navigation
z A window opens with an empty list
Alcatel 1353NM

3JK Edition 1.00
Retrieve alarms
1. Retrieve the alarm list with Archive Î Retrieve from Public

Archive...
OR Î Retrieve from User Files...
2. Set the filter parameters
3. Click Apply: the historical alarm list (HAL) is displayed
Alcatel 1353NM

3JK Edition 1.00
Retrieve alarms [cont.]
z The main operations on the archived sublists are performed in the same
way as for current alarms.
Alcatel 1353NM

3JK Edition 1.00
Saving alarms to a user file
z SAVE
1. Open a sublist of the HAL
2. Select one or a group of alarms
3. Select Action Î Save As
4. Enter a file name
Alcatel 1353NM
The directory in which the file will be stored has already been configured by the administrator.
During the storage process, a process window is displayed.

3JK Edition 1.00
Removing an archived user file
z REMOVE
1. From the “counter summary”, window, select Archive Î Remove
User Files...
2. Select the file to remove and move it to “selected user files” list by
clicking on the arrow
3. Click OK
To
select
To
unselect
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Start the Historical Alarm List

z Retrieve the alarms from public archive
z Look for the alarms purged in the previous exercise
and find the insertion cause
z Create a sublist (e.g. with “Manual purge” as
“Insertion cause”)
z Create a user file with a selection of alarms from
the sublist
z Close and restart the Historical Alarm List
Alcatel 1353NM

3JK Edition 1.00
Exercise [cont.]
z Retrieve the alarms from your user file and check

that it is the same list
z Remove your user file
Alcatel 1353NM

3JK Edition 1.00
6 Handling the AS facilities
Alcatel 1353NM

3JK Edition 1.00
Navigating from AS to PNM
z To view the Network Element having generated an alarm

1. Select an alarm from the sublist
2. Select Navigation Î Topology Manager
z A PNM window opens displaying the submap of the Network Element
generating the alarm
Alcatel 1353NM

3JK Edition 1.00
Navigating from AS to an external application
z You can navigate to an external application of your choice

z This navigation feature has to be configured during installation
3. The NE USM
showing the
alarmed object is
shown
1. Select
an alarm 2. Select
“External
Application Î
Related_EmlUsm”
Alcatel 1353NM

3JK Edition 1.00
Exporting alarms to a printer or text file
z You can export a whole sublist or a selection of alarms
1. Open the sublist

2. Select the relevant alarms
3. Select Action Î Output
z an “output” window opens
z TO PRINT
z Select the “print” button
z Click OK
Alcatel 1353NM

3JK Edition 1.00
Exporting alarms to a printer or text file [cont.]
z You can export a selection of alarms (the selection may include all the
alarms contained in the sublist)
z TO CREATE A TEXT FILE

z Select the Export button
z Choose Select and enter a file name
z Click OK
Alcatel 1353NM

3JK Edition 1.00
Obtaining a report on an action
z It allows you to view a report giving detailed information on the

progress or execution (successful or not) of an operator action.
z In the “Counter summary” window, select Navigation Î Report; the
following window is displayed
Status column
Report detail
Alcatel 1353NM
z For example, you may try to purge alarms manually although some of them have been previously
reserved by another operator. The operation will succeed for some alarms and fail for others. This kind
of event is reported by the AS.
z Possible type of action
} Get Alarm List Attributes
} Get All Alarms
} Get More Alarm Info
} Get Correlated Alarms
} Set Alarm List Attributes
} Set User Note
} Reserve Alarms
} Unreserve Alarms
} Acknowledge Alarms
} Create Trouble Ticket
} Manually Purge Alarms
} Synchronize Application
z Possible status of the operation
} In Progress (Indeterminate severity level color): the request is ongoing.
} Aborted (Minor severity level color): the request has not been sent.
} Failure (Critical severity level color): request failed.
} Success (Cleared severity level color): request succeeded.
} Half Success (Major severity level color): the request has partially succeeded. In this case, read the
report details to find out what failed in the request.
3JK Edition 1.00
Clearing or deleting a report on a performed action
z Clear the whole report list

1. Open the report window
2. Select menu Report Î Clear
z Delete reports for some selected

actions
1. Open the report window
2. Select the reports to be deleted from the
list
3. Select menu Report Î Delete...
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Navigation:
z Open a sublist
z Select an alarm
z Start PNM with the AS facility
z Print out a set of alarms with the export facility
z Display the reports on the actions performed
Alcatel 1353NM

3JK Edition 1.00
7 Administrating the AS
Alcatel 1353NM

3JK Edition 1.00
Advanced feature mechanisms and alarm flow
z Because of the Current Trouble

Alarms List has a limited Ticket Archiv
size, the operator is filter e filter
provided with several
advanced features for ARS CAL HAL
solving capacity
overflow problems
z The default size of the CAL Auto-Ack

is 10000 alarms. It can be filter
changed by the operator in
AutoPurge
the “CAL Administration” filter
window (see next slides)
delete
Alarm
NE
Alcatel 1353NM
CAL size
z The operator can assign the percentage fill level at which a warning is emitted. The operator can also
specify the behavior of the CAL when the overflow occurs (wrap/halt).
z In wrap mode, a purge will automatically begin. The operator specifies the size of the purge (number of
alarms) and the criteria by which the alarms are to be deleted (these alarms are archived in the
historical list).
Automatic purge
z According to the filter criteria, some incoming alarms may be immediately archived, without going
through the current state, that is without being displayed in the current alarms part of Alarm
Supervision.
Automatic acknowledgement
z According to the filter criteria, the operator may decide to acknowledge some alarms automatically
when they enter the CAL.
Automatic trouble ticket creation
z According to the filtering criteria, the operator has a way of automatically requesting the creation of
trouble tickets in an external ARS application when the alarms appear in the CAL.
Selective archiving mechanism
z According to the filter criteria, the operator can prevent some alarms from being archived in the
historical list. By default, the system plans to archive all the alarms. If this filter is changed, the alarms
that are not archived are lost.
Synchronization
z Because the CAL, for any reason, may become out of step with the network alarms situation, the
operator can provoke a synchronization mechanism which performs a global refresh of the CAL checking
all the resources involved.

3JK Edition 1.00
Configuring the AS
z In the “counter
summary” window,
select
Option Î
Administration Î
1353NM_1-7.4.4
Alcatel 1353NM
CAL Administration
z To view the size of the Current Alarm List, and to customize the parameters relating to overflows and
view the current alarm fullness rate
Archiving Filter: to archive alarms which are removed from the CAL to the HAL
Auto-Purge: to divert some incoming alarms automatically to the HAL
Auto-TT: to generate a trouble ticket automatically for some alarms
Auto-Ack: to acknowledge incoming alarms automatically
Overflow Action Mode is the action taken on the arrival of a new alarm when the CAL already contains “CAL
maximum size” alarms:
z Wrap: “Overflow Purge Size” alarms are removed from CAL according to the criteria stated in “Selected
Criteria”. The purged alarms are sent to HAL.
z Halt: the new alarm is discarded

3JK Edition 1.00
Configuring the AS [cont.]
z You can set a filter for:

z Archiving filter
z Auto-Purge
z Auto-Trouble Ticket
z Auto-Acknowledge
z Refer to the previous

chapter to learn how
to set the filter
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Set Overflow action mode to wrap and purge size to 20

z Filter
z Change the auto-purge filter to archive MINOR alarms
automatically
z Create a minor alarm on an NE
z Check that the alarm is sent directly to the historical
alarm list
z Reset the filter to Match-none
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
End of Module
Alarm Management
Alcatel 1353NM

3JK Edition 1.00
Section 4
Maintenance Applications
Module 2
Performance Management
3JK Edition 1.00


3JK Edition 1.00
Blank Page
Maintenance Applications · Performance Management 4·2·2
Alcatel 1353NM
Document History

3JK Edition 1.00
Objectives
z To be able to
z manage the transmission quality records
Alcatel 1353NM

3JK Edition 1.00
Objectives [cont.]
Alcatel 1353NM

3JK Edition 1.00
Table of Contents
Page
1 Definition of counters 7
2 Configuring performance points 19
3 Displaying performance data 27
4 Performance reports 33
Alcatel 1353NM

3JK Edition 1.00
Alcatel 1353NM
All Rights blank

3JK Edition 1.00
1 Definition of counters
Alcatel 1353NM

3JK Edition 1.00
Introduction to SDH performance monitoring
z Principles:
z Based on BIP bytes:
} Byte B1: BIP8 (RSOH)
} Byte B2: BIP24 (MSOH of an STM1 frame)
} Byte B3: BIP8 (VC4 POH)
} Byte V5: BIP2 (VC12 POH)
1. Computation of the BIPs (on frame transmission)
Time
N+3 N+2 N+1 N
BIP BIP
Alcatel 1353NM
BIP: Bit Interleaved Parity

3JK Edition 1.00
Introduction to SDH performance monitoring [cont.]
2. Comparison of BIPs (on frame reception)
Time
N+3 N+2 N+1 N
Extraction
BIP computation
COMPARE
≠
INCREMENT
COUNTERS
Alcatel 1353NM

3JK Edition 1.00
Maintenance Applications · Performance Management 4 · 2 · 10
Far End (Node A) Near End (Node B)

V
V
M R TX STM-N RX R M
V
V
C S S S S C
C C
1 O O O O 1
4 4
2 H H H H 2
V M R R M V
V V
C
C
S S RX STM-N TX S S
C
C
1 O O O O 1
4 4
2 H H H H 2
Byte B2
Byte M1 (B2 return) MS-REI
Byte B3
Byte G1 (B3 return) P-REI
Byte V5
Byte V5 P-REI
Alcatel 1353NM
On Node A
z the near-end information reflects the performance of the one-way section or path from B to A
z the far-end information reflects the performance of the one-way section or path from A to B
On Node B
z the near-end information reflects the performance of the one-way section or path from A to B
z the far-end information reflects the performance of the one-way section or path from B to A

3JK Edition 1.00
z The performance counters are linked to TPs to count transmission

errors.
z The operator can initiate performance monitoring on one or more
subsets of counters for each TP.
z Data is collected automatically and periodically by the OS.
z The main performance management functions are:
z configuring the counting period (15 min and/or 24 hours) for each of the NE's
performance points
z configuring quality thresholds
z collecting performance data
z displaying performance data
Alcatel 1353NM
TP: Termination Point

The history files are date-and-time-stamped by the UTC (as for alarms).
The measurement intervals begin at 00 : 00 (UTC) for 24 hour periods and at xx : 00, xx : 15,
xx : 30 and xx : 45 for 15-minute periods.
Data collection takes place at 00h02 for 24-hour periods and every two hours for 15-minute periods.
Thresholds
z The thresholds can be defined separately for 15 minute and 24 hour counters.
z If threshold values are exceeded for a TP, a Threshold Crossing Alarm (TCA) is generated by the NE.

3JK Edition 1.00
Managed SDH performance counters (local)
z BBE Background Block Error

z EB Error Block
z ES Errored Second
z SES Severely Errored Second
z CSES Consecutive Severely Errored Second
z UAT UnAvailable Time
z UAS UnAvailable Second
Alcatel 1353NM
BBE
z The BBE counter measures the number of errored blocks occurring outside of an SES.
z For the NEs that are based on G.821 counter format.
EB
z A block with one or more errored bits.
ES
z A period of one second with one or more errored blocks.
SES
z A period of one second which contains more than 30% errored blocks, or at least one Severely Disturbed
Period (SDP).
z An SES is also counted as an errored second.
CSES
z A sequence of X consecutive SES, in which X can be configured.
UAT
z A UAT period which begins on the occurrence of ten consecutive SES events.
z These 10 seconds are considered to be part of an unavailable time period.
z A new unavailable time period begins when ten consecutive non-SES events occur.
UAS
z A UAS is a second that is part of an unavailable time period.

3JK Edition 1.00
Managed SDH performance counters (remote)
z FEBBE Far End Background Block Error

z FEBC Far End Block Error Count
z FEBE Far End Block Error
z FECSES Far End Consecutive Severely Errored Second
z FEES Far End Errored Second
z FESES Far End Severely Errored Second
z FEUAS Far End UnAvailable Second
Alcatel 1353NM
FEBBE
z Far end BBE
FEBC
z Identifies, on a terminal, the number of errored blocks counted within a second, received by the far
end terminal
FEBE
z Far end EB
FECSES
z Far end CSES
FEES
z Far end ES
FESES
z Far end SES
FEUAS
z Far end UAS

3JK Edition 1.00
Managed SDH performance counters (other)
z OFS Out of Frame Second

z PSC Protection Switch Counter
z PSD Protection Switch Duration
z PJC Pointer Justification Counter
z FEC Forward Error Correction
Alcatel 1353NM
OFS
z An OOF (Out Of Frame) second is defined as a second in which one or more out-of-frame events occur.
z This event is identified on octets A1/A2 of the SDH frame.
PSC
z Number of switches between the service channel and the defence channel.
PSD
z Defence duration.
PJC
z Represents the number of pointer justification events counted, increasing or reducing the pointer.
z Justification is used to adapt the ratio of the received container with the ratio of the transmitted
container.
FEC
z Number of errored FEC blocks during a time unit.

3JK Edition 1.00
Performance Monitoring on FEC
z On WDM equipment, some transponder boards also support PM at FEC

layer:
z FEC is inserted by the transponder on the colored transmission side, and the
receiving transponder is able to detect errors and possibly correct them
while decoding the FEC.
z PM on FEC layer gives information about the signal quality between the
transmitting transponder colored output and the receiving transponder
colored input
PM on WDM signal (FEC)
Alcatel 1353NM

3JK Edition 1.00
Managed FEC performance counters
z ES (Errored Second): a second in which at least a corrected error is detected

z US (Uncorrected Second): a second in which at least an uncorrected error is
detected
z BEC (Background Error Corrected): a FEC corrected error that occurred outside
a SCS (result is divided by 512)
z SCS (Severely Corrected Second): a second with a FEC layer defect or at least
one FEC uncorrected block or more than 33 538 048 FEC corrected errors
z BBU (Background Block Uncorrected): a FEC uncorrected block that occurred
outside a SUS.
z SUS (Severely Uncorrected Second): a second in which a FEC layer defect
occurred or in which more than 33 538 048 FEC blocks were uncorrected
z BER (Bit Error Rate): not a primitive counter; the NM computes the BER based
on the BEC counter
z QF (Q-Factor): not a primitive counter; the NM computes the Q-Factor based on
the BER
Alcatel 1353NM

3JK Edition 1.00
Managed Ethernet performance counters
z TRCO (Total Received Correct Octets): total number of octets of Ethernet frames
received correctly by the Virtual Ethernet Interface, including Ethernet header
characters
z TRCF (Total Received Correct Frames): total number of Ethernet frames received
correctly by the Virtual Ethernet Interface
z TTO (Total Transmitted Octets): total number of octets of Ethernet frames
transmitted out by the Virtual Ethernet Interface, including Ethernet header
characters
z TTF (Total Transmitted Frames): total number of Ethernet frames transmitted out by
the Virtual Ethernet Interface
z TDF (Total Discarded Frames): total number of Ethernet frames which were chosen to
be discarded due to buffer congestion
z TRSEF (Total Received Service Errored Frames): total number of Ethernet frames
received incorrectly by the Virtual Ethernet Interface
z Counters are sampled with 1h (or 15 min, see notes) and 24h granularity period
z All counters are free-running. This means that they are not reset at the end of
the sampling period. For this reason, reports on Ethernet counters are available
in 1353NM showing deltas with respect to the previous measurement.
Alcatel 1353NM
ISA-ES1/4, starting from Rel 1.3 on, and ISA-ES16, starting from Rel. 2.2 on, support PM granularity period
of either 1h or 15min (please note that ALL cards on the same NE must be configured with the same
granularity period, i.e. either 15min or 1h).
For these kinds of board, 1353NM supports the two granularity types, with the following configuration
notes and constraints:
z The desired granularity is settled in the configuration file of the EMLIM supporting the NE
(EMLIMCORBASNMP) during the system configuration (see details in the Administration handbooks and
Training Manuals); EMLIM then sets the monitoring granularity on the NE at the Start Supervision. Due to
the fact that the configuration file is unique for all the EMLIMCORBASNMP instantiated in the system,
the consequence is that the selected granularity should apply to the ISA-ES boards of the whole network
supervised by the 1353NM.
} Mixed networks where some ISA-ES provide 15min and some others ISA-ES provide 1h data are not
supported
z When the supervision is started by the 1353NM on a ISA-ES with a different monitoring granularity
period, all the PM points of that NE switch to the granularity configured in the 1353NM.

3JK Edition 1.00
Analog performance monitoring
z 1620LM Rel 2.2 and 1626LM Rel 3.0 DWDM equipment support the
monitoring of analog values.
z Basically, the Analog PM involves all the measurements available by in
the NE USM at Equipment (or Board) ÎInstantaneous Measurements.
These include:
z Tx Optical Power Level
z Rx Optical Power Level
z Bias Current Level
z Temperature
z Etc.
For boards such as TRBD/TRBC/MCC30/SFP/BMDX/CMDX/LOFA/ALCT
z 1353NM is in charge of sampling and storing the input/output power
values in the PM DB. The user can then select Monitoring Points to
generate the Reports (Table Chart).
z The sampling periods are 15m & 24h.
Alcatel 1353NM

3JK Edition 1.00
2 Configuring performance points
Alcatel 1353NM

3JK Edition 1.00
Configuring threshold tables
z Open an equipment view

z Select the menu:
z Configuration Î Performance Î Threshold
Tables
In this window, you can perform the following
operations on a thresholds table:
z create
z modify
z display
z delete
z link to a TP entity
1. Select the table from the list (except for

creation)
2. Click the button representing the action you
want to carry out
Alcatel 1353NM
N.B.: In this Chapter only the configuration of SDH performance points and Analog PM are taken into
consideration.
For the configuration of Ethernet and FEC performance points, please refer to the Operator Handbooks
and Training Manuals of the specific NE family.

3JK Edition 1.00
Configuring threshold tables [cont.]
1. Enter the table name (creation

only)
2. Select granularity (creation
only)
3. Define the upper threshold
values
4. Define the lower threshold
values
5. Select the alarm severity
6. Disable “send notification” if no
message is to be sent on a
threshold crossing
7. Click Apply
Alcatel 1353NM
Section / Path type Block size (bits) Blocks per frame Blocks per second BIP type
STM-N - RS 19440 x N 1 8000 BI P – 8
STM-N – MS 801 24 x N 192000 x N BI P – 24xN
STM-1 – RS 19440 1 8000 BI P – 8
STM-1 – MS 801 24 192000 BI P – 24
VC4 18792(261x9x8) 1 8000 BI P - 8
VC3 6120 1 8000 BI P - 8
VC12 1120 0,25 2000 BI P - 2
Example
Granuality: 15 minutes
STM1 - RS
Counters Low Threshold / BER High Treshold / BER
BBE 58 ( ~ 10-9) 5790 (~ 10-7)
ES 50 150
STMn
For STM4, BBE values must be multiplexed by 4
For STM16, BBE values must be multiplexed by 16
Gruanuality: 24 hours
For 24 hours period, values must be multiplexed by 4* 24

3JK Edition 1.00
Starting/stopping performance monitoring
1. Display the port view of a board

2. Select a TP (MST, RST, AU4, VC-n or TU-n)
3. Select the menu Port Î Performance
Î Configure Performance Monitoring
4. Select a POM/TCM/TCT as Monitor (if
required)
5. Define the parameters Mode, EML OS
Monitoring and Notifications
6. Choose a proper Threshold table and
Attach it
7. Click Apply
8. Click on Set ASAP if you want to configure
ASAP
9. Click Apply
Alcatel 1353NM
POM: Path Overhead Monitoring.

TCM: Tandem Connection Monitoring. TCT: Tandem Connection Termination.
Mode
z data collection: select this button to enable performance monitoring
z create history data: if this option is selected, history data is collected in the entity selected for the
corresponding TP
z Lock data collection: If the Lock option is selected, performance monitoring remains active but data
collection is stopped. All the history data remains available. All current values are set to zero
EML OS Monitoring: Click on Enable and select “Archiving”, otherwise the PM data are not sent to the OS
Notifications
z UAT: notifications of UAT (UnAvailable Time) are created if the option is enabled. This notification is
reflected in a UAT alarm in the AS.
} N.B. This parameter can only be selected when creating and cannot be modified subsequently
z Suppress Additional threshold:
} If this option is enabled, notification is sent only for the first counter that exceeds the threshold
defined during a granularity period.
} If the option is disabled, the threshold violation of each counter is indicated.
Threshold table
z Link a threshold table to the selected TP. Assign only the threshold tables that correspond to the
granularity period of the data sets (a 15-minute threshold table must not be assigned to a data set
covering 24 hours).
z Click the Attach... button to open the window for selecting the threshold table, PM Threshold Table
Select, and configure the threshold table.
z Select the Remove button to separate the threshold table from the entity.
3JK Edition 1.00
How to set Analog PM in NE USM
z Open the equipment view

z Select Configuration Î Analog PM Configuration Î
z On Equipment
} for configuring the Analog PM on all the equipment (the following window will open)
z On selected object
} for configuring the Analog PM on the single selected board
Alcatel 1353NM

3JK Edition 1.00
How to set Analog PM in NE USM [cont.]
z Start PM by selecting Start in the “PM action”

column for the 15’ or the 24h
z If the data must be sent to the 1353NM, the
“Archiving” cell must be set to Yes
z Click on Apply
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Display a threshold configuration table and note

down the parameters
z Create a new threshold configuration table, using
the previous parameters as an example
z Start performance monitoring for two TPs (15-
minute counter)
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
3 Displaying performance data
Alcatel 1353NM

3JK Edition 1.00
Displaying performance data for a single TP
z From the Equipment view:

1. Display the port view of a board
2. Select a suitable TP
3. Select the menu Port Î
Performance Î Display Current
Data
4. Select TP/POM/TCM/TCT
(in case of AU4 or TU-n)
5. Select the required granularity
z Click Refresh to update the

counters’ value
Alcatel 1353NM
Administrative State: Indicates whether performance data selection is locked for the local user.
Operational State: Indicates whether performance monitoring is operational.
Suspect Data: Indicates whether data collection errors have occurred during the collection period.
Threshold Table: Indicates which threshold table is assigned to the entity.
Current Problem List: Indicates the current UAT (unavailable time) and TCA (threshold crossing alarm)
alarms.
Elapsed Time: Indicates the time that has elapsed since the start of the monitoring interval. This
information tells the user whether data collection covers the total period.
Reset: Reset counters to zero for the running period.
N.B.: In this Chapter only the displaying of SDH performance data are taken into consideration.
For the display of Ethernet and FEC performance data, please refer to the Operator Handbooks and
Training Manuals of the specific NE family.

3JK Edition 1.00
Displaying the performance data history for a single TP
z From the Equipment

view:
1. Display the port view of
a board
2. Select the TP
3. Select the menu Port Î
Performance Î
Display History Data
4. Select
TP/POM/TCM/TCT
(in case of AU4 or TU-n)
5. Select the required
granularity
z Click Refresh to update

the window’s data
Alcatel 1353NM
Interval End Time: in dd.mm.yyyy hh:mm:ss format.

Elapsed Time: indicates whether data collection is finished.
susp: indicates suspect data for which collection errors have occurred during the collection period.
In the case of 15-minute entities, up to 16 data sets can be displayed simultaneously for each TP; the
maximum number of data items for 24 hour entities is equal to three (equal to one for OMSN). These
values cannot be modified by the user.
If the limit of 16 data sets for a granularity of 15 minutes and three data sets for a granularity of
24 hours is reached, the oldest data in the list is overwritten by the new data collected.

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Display the current performance data for the TPs

started on the last exercise
z Test the Refresh and Reset buttons
z Display the performance data history
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
4 Performance reports
Alcatel 1353NM

3JK Edition 1.00
Navigation to performance data views
3 ways to get
the RRC
window 2 From PNM USM
1
From TMN-OSs
3 formats
for the
generated
report 3
From EML USM
1. Screen
2. File
3. Printer
Alcatel 1353NM

3JK Edition 1.00
Navigation to performance data views (RRC window)
Select one or more performance entities

to make a report on them (directly in the
list or with the “PE selection window” or
with the filter)
Set Reporting
Criteria
Alcatel 1353NM

3JK Edition 1.00
Performance Entity Selection
z A Performance Entity is a set of PM TPs.

z The NM operator can save the Performance Entity.
z Then, he can recall this saved selection in order to fasten a further
selection and management of the same TP set.
Alcatel 1353NM

3JK Edition 1.00
Save Performance Entity Selection
1. Select some TPs

z File Æ Performance Entity Selection Æ Save
z Assign a name and a description (optional)
z Do Save
Comments
The selected TPs
Alcatel 1353NM
To delete one or more PE selections:

3JK Edition 1.00
Recall a saved Performance Entity Selection
z File Æ Performance Entity Selection Æ Select

z Choose a saved PE
z Do Select
Alcatel 1353NM

3JK Edition 1.00
Filtering
Alcatel 1353NM

3JK Edition 1.00
Selecting the counters to be displayed
Report Request
Control Window
Alcatel 1353NM
One or more Performance Parameters may already be selected, and will be shown in the “Selected” list
(if operator didn’t change his Performance Entity selection), other unselected and supported
Performance Parameters will be shown in the “Available” list. If no Performance Parameters previously
selected, then all supported Performance Parameters of those selected Performance Entities will be
selected by default.

3JK Edition 1.00
Setting Thresholds
z These thresholds are appyed by the PM viewer to highlight some PM

TPs’ values
z These thresholds don’t concern the Threshold Crossin Alarm
1. Select a
parameter
2. Set the
threshold’s
parameters
Alcatel 1353NM
A different threshold setting window will be shown according to different database: if Analog PM TPs are
selected, the threshold setting window will provide a button “Delete Threshold” to delete the
corresponding threshold bond to a parameter of a certain TP under a certain granularity; if other
database's TPs are selected, no “Delete Threshold” button is displayed.
The operator can click one parameter and set its Critical and Warning values.
Threshold on Max:
z the parameters whose value is lower than WARNING will not be highligthed
z the parameters whose value is between WARNING and CRITICAL will be highligthed in yellow
z the parameters whose value is higher than CRITICAL will be highligthed in red
Threshold on Min:
z the parameters whose value is higher than WARNING will not be highligthed
z the parameters whose value is between WARNING and CRITICAL will be highligthed in yellow
z the parameters whose value is lower than CRITICAL will be highligthed in red
Apply to all TPs: the threshold will apply to all TPs listed in the combo box; otherwise, this threshold will
apply only to the currently selected TP in combo box by default.
After the threshold setting, the operator can click the Save button to save all settings or click the Cancel
button to discard all settings.

3JK Edition 1.00
Setting presentation Options
Alcatel 1353NM
If the operator chooses to set presentation options before report generation (i.e. in RRC window), the
setting will be remembered and be applied on the report that is to be generated.
If the operator chooses to set presentation options after report generation (i.e. in Report window), the
setting will be applied immediately on the report and the report will be changed accordingly.

3JK Edition 1.00
Set Reporting Criteria
Alcatel 1353NM
The Reporting Period can be specified in four ways:

1. User Selection period: The operator must enter the ’From Date and Time’ and
the ’To Date and Time’ manually. The From Date starts at the earliest of 1
January 1970, the To Date ends at the latest of 31 December 2037. The pre-
selected periods are grayed–out.
2. The last period: The operator can choose from the following options:
· 15min: last 15 minutes . week: last week
· hour: last hour . month: last month
· day: yesterday . year: last year
3. The current period: The operator can choose from the following options:
· 15min: these 15 minutes . week: this week starting with Monday
· hour: this hour . month: this month
· day: today . year: this year
4. The Last … Until period: The operator can choose from the following options:
· 15min: 15 minutes . week: 1 week
· hour: 1 hour . month: 1 month
· day: 24 hours . year: 1 year
The ‘To Date and Time’ is entered by the operator manually. The ’From Date and
Time’ is updated automatically according to the selected period and cannot be
modified anymore.
Specifying the Report Type:
· Performance Counter Tabular Reports
· Performance Counter Graphical Reports
· Delta Counter Report, Graphical or Tabular (for Ethernet TPs)
· Comparison Reports, Tabular or Graphical (for Analog PM TPs)
· Reference Value Reports.

3JK Edition 1.00
Display PCT Report
The chosen
Report period
Select Performance
entity(ies)
Results
Report view with

Tabular choice in the
Select setting presentation
Performance option (all entities in
parameters one table)
Alcatel 1353NM

3JK Edition 1.00
Display PCT Report [cont.]
Report view when the

operator chooses
Tabular in the setting
presentation option
and with one Entity per
table (see setting
presentation option)
Alcatel 1353NM
If the operator choose the menu “Option->Show Threshold Crossing Rows Only”, then the PCT report will
be turned to TCT report, which considers only the rows with at least one counter value exceeding
thresholds.

3JK Edition 1.00
Display PCG (Graphical Report - line chart)
Select Line
or Bar chart
Select
Performance
entity(ies)
Report view when the

operator chooses
Graphical in the
setting presentation
option.
Select
Performance
parameter(s) Legend
Alcatel 1353NM

3JK Edition 1.00
Display PCG (Graphical Report - Bar chart)
Select
Bar chart
Select
Performance
entity(ies)
Select
Performance
parameter(s) Legend
Alcatel 1353NM

3JK Edition 1.00
Display PCG (Graphical Report - Bar chart) [cont.]
Select Select
Performance Line or
entity(ies) Bar chart
Graphical
Report view
with one Entity
per table (see
setting
presentation
Select option).
Performance
parameter(s) Legend
Alcatel 1353NM

3JK Edition 1.00
Forced reading of performance counters
z Forced reading is used to collect data immediately without waiting for

the end of the next collection period
z Valid only for 15 minute counters.
1. Display any equipment view
2. Select Configuration Î Performance Î Forced Performance collection
Alcatel 1353NM
Forced reading has no effect on the automatic performance counter collection process, except that
blocks already collected will be collected again.
If the forced reading request occurs at the same time as an automatic collection period, the forced
collection will be ignored.
The forced collection will be rejected if the request happens in the two minutes following the end of a 15
minute counting period.

3JK Edition 1.00
Search for a TP
z In the RRC window, select a

family (i.e. SDH) as search root
and click on “Search TP Name”
or “Search by Value”
Alcatel 1353NM

3JK Edition 1.00
Search for a TP by name and type
1. The root selected

in the RRC window
2. Define the Name Pattern
(substring of TPs) using * as
wild character
5. Start the search
3. Optionally select
the TP type
4. Optionally
select the NE type
6. The found TPs are

displayed in this area.
7. Clicking “All”, all the found TPs are highlighted in the RRC
window. Selecting some found TPs and clicking Selected,
only the selected TPs are highlighted in the RRC window.
Alcatel 1353NM
During the search, operator can pause, resume and restart search.

3JK Edition 1.00
Search for a TP by Value
z Locate quality degraded TP

z Define the search conditions
or use the profile function to
load saved search conditions.
Start
z Click the “Start” button to
the
start search.
search
Search root must be
defined before
opening the window
Select value(s)
Results are
displayed
in this area
Alcatel 1353NM
During the search, operator can pause, resume and restart search.

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Force counters collection

z Display the performance data for TPs started in the
previous exercise
z graphical report
z textual report
z Locate TPs with errors detected
z Create a Performance Entity corresponding to the
TPs previously started
z Delete the Performance Entity
Alcatel 1353NM

3JK Edition 1.00
End of Module
Performance Management
Alcatel 1353NM

3JK Edition 1.00
Section 5
Administration features
Module 1
Administration for operators
3JK Edition 1.00


3JK Edition 1.00
Blank Page
Administration features · Administration for operators 5·1·2
Alcatel 1353NM
Document History

3JK Edition 1.00
Objectives
z To be able to
z perform the basic administration tasks in operator field
Alcatel 1353NM

3JK Edition 1.00
Objectives [cont.]
Alcatel 1353NM

3JK Edition 1.00
Table of Contents
Page
1 List of administration functions 7
2 Managing personal settings 9
3 Command log viewer 15
Alcatel 1353NM

3JK Edition 1.00
Alcatel 1353NM
All Rights blank

3JK Edition 1.00
1 List of administration functions
Alcatel 1353NM

3JK Edition 1.00
1 List of administration functions
SMF
z 1353NM administration is conducted mainly using the System

Management Features (SMF) application and “Global actions”
z SMF lets you perform
z Operators administration
z Trace & log management
z Backup & restore
z Failure management
z Scheduler management
z PMDS DB Administration
z Cleanup Management
z There are different access levels according to the user profile and the
terminal used for the connection
Alcatel 1353NM
Operators administration
z add/remove operators, list connected operators, close a session
Trace & log management
z view and back up process traces
z view and back up log files (events, user commands, SMF)
Backup & restore
z backup and restore application data
Failure management
z System Snapshot view
Scheduler management
z To schedule different actions
PMDS management
z To Manage the performance monitoring data base
Cleanup Management
z To suppress useless files

3JK Edition 1.00
2 Managing personal settings
Alcatel 1353NM

3JK Edition 1.00
Changing your password
Administration features · Administration for operators 5 · 1 · 10
Enter the old

password
Enter the new

password
z The shortest way to Confirm

change the password,
select: Global Actions OK
Î Change Password
Alcatel 1353NM

3JK Edition 1.00
Selecting the printer
Global Actions Î Set Personal

Printer
1. Select the
printer
3. Close the session

and re-open it
2. Apply
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
Exercise
z Change your password

z Set a default printer
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
3 Command log viewer
Alcatel 1353NM

3JK Edition 1.00
How to proceed
z The command log viewer permits to check the content of the command
log files for several USMs. Simple and advanced filters are provided.
z The set of logs provided depends on the server on which the user is
working: the set of USM logs on the master can be different from the
set on the client and has a different content.
z For simple filters, the variable content depends on the content of the
parsed file. For example, the range of date shows the operator only the
dates on which operations have been made.
z Step 1: open the CLV (Actions Î Command Log Viewer); select a log
and click on Parse
z Step 2: after the log is parsed, the operator can apply filters to extract
the required information. Select the query panel and create a filter
(simple or complex).
Alcatel 1353NM

3JK Edition 1.00
Step 1: select the log
Click on Parse
Alcatel 1353NM

3JK Edition 1.00
Step 2: create a simple filter
z Query Panel: two types of filters are provided : Simple or Advanced

2. Click on save
1. Create a simple
filter by selecting:
• Operator
• Machine
• Entity (the
equipment)
• Date
• Command provided
4. Click on Apply 3. Insert the filter

name and click on OK
Alcatel 1353NM

3JK Edition 1.00
Filtering result
Alcatel 1353NM

3JK Edition 1.00
Advanced filter
z Each row of the table represents a single logical condition made up by a

subject (Variable), relational operator (Compare to) and a value of
comparison (Value). Several logical conditions can be set by Boolean
operators and grouped by round brackets.
Alcatel 1353NM

3JK Edition 1.00
Advanced filter [cont.]
Once created, save

the filter and apply
(as for simple
Variable filters)
Compare to
Operator
Alcatel 1353NM

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
Abbreviations and Acronyms
A z Switch to notes view!

ACD Access Control Domain
ACK ACKnowledged DDS Digital Data Storage (DDS1, DDS2,
ACM Automatic Connection Management DDS3, DDS4)
ACSE Association Control Service Element DM Distributed Management
ADM Add and Drop Multiplexer DNM Distributed Network Maps
AFI Authority Format Identifier DS Degraded Signal
AIS Alarm Indication Signal DVD Digital Versatile Disk
ALMAP ALcatel Management Platform DXC Digital Cross-Connect
ALS Automatic Laser Shutdown
ANTP Alcatel Network Timing Protocol E
AP Access Point ECC Embedded Communication Channels
API Application Procedure Interface ECT Equipment Craft Terminal
APMAN Application Process Management EFD Event Forward Discriminator
APS Automatic Protection Switching ELM Events & Log Management
ARF Application Registration Files EM Element Manager
AS Alarm Surveillance EML Element Management Layer
ARF Application Registration Files EM-OS Element Manager – Operation System
AS Alarm Surveillance EMS Event Management Service
ASAP Alarm Severity Assignment Profile ENE Equivalent Network Element
ATM Asynchronous Transfer Mode EPS Equipment Protection Switching
AU Administrative Unit ES End System
AU PJC Administrative Unit Pointer Justification ESCT Equipment and Shelf ConTroller
Alcatel Counter
1353NM ES-IS2007
All Rights Reserved © Alcatel-Lucent End System to Intermediate System
ESN Elementary Subnetwork
B ET Elementary Topology
BER Bit Error Rate
BN Backbone Network F
FAD Functional Access Domain
C FERF Far End Received Failure
CAP Client Access Point FLS Frame Loss Second
CDE Common Desktop Environment FM Fault Management
CD-ROM Compact Disc Read Only Memory FOX Fiber optic Extender
CETP Carrier Ethernet Transport Platform FTP File Transfer Protocol
CI Communication infrastructure
CLR Clear G
CLNP Connection Less Network Protocol GDMO Guidelines for the Definition of Managed
CLNS Connection Less Network Service Objects
CMIS Common Management Information GMT Greenwich Meridian Time
Service GNE Gateway Network Element
CMISE Common Management Information GUI Graphical User Interface
Service Element
CMOT Common Management Info Protocol on H
TCP/IP HMI Human Machine Interface
COMET C++ Object Management Extended HO Higher Order
Toolchain HOA High Order Assembler
CORBA Common Object Request Broker HO-AP High Order Access Points
Architecture HOPL Higher Order Path Layer
CSV Comma Separated Values HOP-LN High Order Path Layer Network
CT Craft Terminal HPA High Order Path Adaptation
CTP Connection Termination Point HPC High Order Path Connection
HPT High order Path Termination
D HPPT Hyper Text Tranfer Protocol
DBNS Data Base Management System HVC Higher order Virtual Container
DCC Data Communication Channel
DCN Data Communication Network
3JK Edition 1.00
Abbreviations and Acronyms [cont.]
I z Switch to notes view!

IAP Inventory APplication
IDI Initial Domain Identifier NFS Network File System
IEEE Institute of Electrical and Electronics NM Network Manager
Engineers NML Network Management Layer
IM Information Manager NN National Network
IOO Interface OS to OS NNM Network Node Manager
IP Internet Protocol NR Network Release
IS Intermediate System NRSV Not ReSerVed
ISA Integrated Service Adapter NSAP Network Service Access Point
IS-IS Intermediate System to Intermediate NTP Network Timing Protocol
System
O
L OCT Office Craft Terminal
LAN Local Area Network OFS Out of Frame Seconds
LAP Link Access Protocol OH Over Head
LAPD Link Access Protocol on D channel OMSN Optinex Multi Service Node
LC Link Connection ORS Object Registration Service
LLC Logical Link Control OS Operation System
LO Lower Order OSI Open System Interconnexion
LO-AP Low Order Access Point OSPF Open Shortest Path First
LOF Loss Of Frame
LOP Loss Of Pointer P
LOPLAlcatel Low Order Path Layer
1353NM PCMAP Payload Configuration Management
LOP-LN
Alcatel Low Order
1353NM Path
rel. 7.4B Layer Network
Operation Application
LOS Loss Of Signal PDH Plesiochronous Digital Hierarchy
LOT Loss Of Tributary PDU Protocol Data Unit
LPA Lower Order Path Adaptation PERF PERFormance Management
LPC Local Process Controller PERL Practical Extraction and Report Language
LPC Lower Order Path Connection PI Physical Interface
LPT Lower Order Path Termination PM Performance Monitoring
LRF Local registration files PMD Postmaster Daemon
LTS Line Transmission System PMV Performance Monitoring Visualisation
LVC Lower Order Virtual Container PNM Physical Network Management
POH Path Overhead
M PPI PDH Physical Interface
MAC Media Access Control PRTP Pure TRansport Platform
MESA Manual End System Adjacency PTM Path Trace Mismatch
MIB Management Information Base
MS Multiplex Section Q
MS-AP Multiplex Section Access Point Q3 CMISE Q3 OPTICS-IM based
MS-TP Multiplex Section Termination Point management interface
MSL Multiplex Section layer QECC Q Embedded Communication Channel
MS-LN Multiplex Section Layer Network
MSP Multiplex Section Protection R
MSPP MultiService Provisioning Platform RAP Reachable address Prefix
MST Multiplex Section Termination RIP Routing Information Protocol
RECT Remote Craft Terminal
N RM Regional Manager
NACK Not ACKnowledged ROSE Remote Operation Service Element
NAD Network Access Domain RS Regeneration Section
NAP Network Access Point RST Regeneration Section Termination
NAV NAVigation RSV Reserved
NCLR Not Clear
NE Network Element
NECTAS Network Equipment Craft Terminal
Application Software
3JK Edition 1.00
Abbreviations and Acronyms [cont.]
S z Switch to notes view!

SA Section Adaptation
SBN SuBNetwork
SCSI Small Computer Serial Interface
SDH Synchronous Digital Hierarchy
SEC SECurity
SEN Simple Element Network
SEN-IM Simple Element Network Information
Manager
SF Signal Failure
SMF System Management Functions
SMTP Simple Mail Transfer Protocol
SNCP Subnetwork Connection Protection
SNML SDH Network Management Layer
SNMP Simple Network Management Protocol
SOH Section Over Head
SPI SDH Physical Interface
STM-N Synchronous Transport Module level N
SWDL SoftWare DownLoad
SWM SoftWare download Management
SWS SoftWare Server
T
TCA Alcatel Threshold
1353NM Crossing Alarm All Rights Reserved © Alcatel-Lucent 2007
TCP Transmission Control Protocol
TF Transmit Fail
T-FEP TSD Front End Processor
TFTP Trivial File Transfer Protocol
TM Terminal Mode
TMN Telecommunications Management
Network
TN Telecommunications Network
TP Termination Point
TSS Transport Service Switch
TTP Trail Termination Point
TU Tributary Unit
TU PJC Tributary Unit Pointer Justification Counter
U
UDP User Datagram Protocol
UPSR Unidirectional Path Switched Rings
USM User Service Manager
V
VC Virtual Container
W
WS WorkStation
X
XC Cross-Connect
XCC EXternal Communication Control

3JK Edition 1.00
Blank Page
Alcatel 1353NM

3JK Edition 1.00
End of Module
Administration for operators
Alcatel 1353NM

3JK Edition 1.00
DRAFT
@@SECTIONTITLE - @@MODULETITLE @@SECTION - @@MODULE - 1
@@PRODUCT
@@COURSENAME This page is left blank intentionally
Copyright © 2007 by Alcatel-Lucent - All rights reserved
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel

1353NM Rel. 7.4B Operation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1353NM Rel. 7.4B Operation

Uploaded by

Copyright:

Available Formats

Alcatel 1353NM

Alcatel 1353NM rel. 7.4B

Alcatel 1353NM - Alcatel 1353NM rel. 7.4B Operation

Copyright © 2007 by Alcatel-Lucent - All rights reserved

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

 Switch to notes view!

All Rights Reserved © 2007, Alcatel-Lucent

 Switch to notes view!

Welcome to Alcatel 1353NM rel. 7.4B Operation

After successful completion of this course, you should understand :

 Identify and localize the system functions into the TMN

All Rights Reserved © 2007, Alcatel-Lucent

 Switch to notes view!

All Rights Reserved © 2007, Alcatel-Lucent

Conventions used in this guide

Where you can get further information

If you want further information you can refer to the following:

All Rights Reserved © 2007, Alcatel-Lucent

 Switch to notes view!

All Rights Reserved © 2007, Alcatel-Lucent

Did you meet the following objectives ?

Yes (or No (or

Graphical Interface - Network Topology

All Rights Reserved © 2007, Alcatel-Lucent

 Switch to notes view!

Yes (or No (or

Thank you for your answers to this questionnaire

All Rights Reserved © 2007, Alcatel-Lucent

Alcatel 1353NM · Alcatel 1353NM rel. 7.4B Operation

All Rights Reserved © 2007, Alcatel-Lucent

Edition Date Author Remarks

01 2007-10-30 Pirola Paolo First edition

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

Switch to notes view!

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

z A Telecommunication Management Network (TMN) is a structured

1353NM belongs to the EML

All Rights Reserved © 2007, Alcatel-Lucent

SNMP SNMP Q3 Q3 Q3 QB3* SNMP

NE: Network Element

ZIC: Zero Installation Craft Terminal

(1) 1664SM and 1666-55SR starting from Rel 3.2

All Rights Reserved © 2007, Alcatel-Lucent

(1) 1664SM and 1666-55SR starting from Release 3.2

CMIP: Common Management Information Protocol

All Rights Reserved © 2007, Alcatel-Lucent

z The NEs are managed by the 1353NM via EML-IM.

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

2 1353NM management functions

All Rights Reserved © 2007, Alcatel-Lucent

Network Topology Management

All Rights Reserved © 2007, Alcatel-Lucent

Network Element Management

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

Switch to notes view!

Switch to notes view!

Identify and localize the system functions into the TMN

Switch to notes view!

Switch to notes view!

Switch to notes view!