Alcatel 1353

Alcatel 1353NM Alcatel 1353NM rel. 7.
4 Operation
3FL41020ACAAWBZZA Edition 1.00
TRAINING MANUAL
Alcatel 1353NM - Alcatel 1353NM rel. 7.4 Operation

All rights reserved 2005, Alcatel
Copyright 2005 by Alcatel - All rights reserved Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel
Alcatel 1353NM rel. 7.4 Operation - Page 1
Legal Notice
2
Page 2
to Safety Switch Warning
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. 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 and may be used for training purposes only. No other use or transmission of all or any part of this document is permitted without Alcatels written permission, and must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel. Use or transmission of all or any part of this document in violation of any applicable Canadian or other legislation is hereby expressly prohibited.
Alcatel 1353NM - Alcatel 1353NM rel. 7.4 Operation All rights reserved 2005, Alcatel
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. Alcatel, The Alcatel logo, MainStreet and Newbridge are registered trademarks of Alcatel. All other trademarks are the property of their respective owners. Alcatel assumes no responsibility for the accuracy of the information presented, which is subject to change without notice. 2005 Alcatel. All rights reserved. Disclaimer In no event will Alcatel 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 products or services is for information purposes only and constitutes neither an endorsement nor a recommendation. Please refer to technical practices supplied by Alcatel for current information concerning Alcatel equipment and its operation.
Table of Contents
3
Page
Page 3
Section Product Overview Switch to1notes view! Module 1.1 Product Overview
1.1.1 NR7 TMN Description 1.1.2 1353NM Management Functions 1.1.3 System Architecture 1.1.7 1.1.13 1.1.19
Section 2 Graphical Interface Module 2.1 How to Logon

2.1.1 Login and Workspace Front Panel 2.1.2 The TMN-OS Icon 2.1.3 Windows and Workspace Menu 2.1.7 2.1.13 2.1.21 2.2.7 2.2.19 2.2.21 2.2.35 2.2.55 2.2.105 2.2.111 2.2.127 2.2.139 2.2.145 2.2.151 2.2.161
Module 2.2 Network Topology

2.2.1 Creating a Map 2.2.2 Managing and Addressing a NE on a Map 2.2.2.1 Creating and Addressing a Q3 NE 2.2.2.2 Creating and Addressing ISA boards 2.2.2.3 Creating and Addressing a 1850TSS NE
2.2.2.4 Creating and Addressing a SNMP NE 2.2.2.5 NE Autodiscovery 2.2.2.6 Map Population
2.2.3 Creating a Graphical Connection 2.2.4 Creating the GNE List 2.2.5 Addressing the NEs with IP Tunnel: OSI over IP 2.2.6 Distributing Maps
Section 3 System Operation Module 3.1 NE Supervision

3.1.1 Displaying NE Management and Alarm State 3.1.2 Modifying the management State of a NE 3.1.3 Simulator 3.1.4 Schedule a MIB Backup 3.1.5 Backing up/Restoring the MIB 3.1.7 3.1.21 3.1.39 3.1.49 3.1.57 3.2.7 3.2.13 3.2.23 3.2.27 3.2.47 3.2.53
Module 3.2 NE Management

3.2.1 NE Time management from the 1353NM 3.2.2 Performing a Remote Inventory 3.2.3 Resetting a NE 3.2.4 Downloading Software to the NE 3.2.5 List Abnormal Conditions 3.2.6 Event Log Archiving
Table of Contents [cont.]

4
Page
Page 4
Section Maintenance Application Switch to4notes view! Module 4.1 Alarm Management
4.1.1 Displaying Current Alarms 4.1.2 Alarm Debouncing 4.1.3 Creating, Modifying and Deleting and Alarm Sublist 4.1.4 Performing Actions on Current Alarms 4.1.5 Displaying the Alarm History 4.1.6 Handling the AS Facility 4.1.7 Administrating the AS 4.1.7 4.1.19 4.1.27 4.1.39 4.1.47 4.1.57 4.1.67 4.2.7 4.2.19 4.2.27 4.2.33
Module 4.2 Performance Management

4.2.1 Definition of Counters 4.2.2 Configuring Performance Points 4.2.3 Displaying Performance Data 4.2.4 Performance Reports
Section 5 Administration Features Module 5.1 Administration for Operators

2.1.1 Login and Workspace Front Panel 2.1.2 The TMN-OS Icon 2.1.3 Windows and Workspace Menu
2.1.7
2.1.13 2.1.21
Course Objectives
5
Page 5
Switch to notes view!

Welcome to Alcatel 1353NM rel. 7.4 Operation
After successful completion of this course, you will be able to:
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
Course Objectives [cont.]

6
Page 6
This page is left blank intentionally
About this Student Guide

7
Conventions used in this guide Switch to notes view!

Note
Page 7
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 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.
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.com
About this Student Guide [cont.]

8
Page 8
Self-Assessment of Objectives
Contract number : Course title :
9
Page 9
Client (Company, Center) : Language :
At the end of each section you will be asked to fill this questionnaire Please, return this sheet to the trainer at the end of the training Switch to notes view!
Dates from : Location : to :
Number of trainees :
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 globally yes) No (or globally no)
Instructional objectives 1 2 To be able to Identify and localise the system functions into the TMN Describe the system architecture
Comments
To be able to Login, start the TMN-OS icon, start the Alcatel 1353NM - Alcatel 1353NM rel. Operation main application of7.4 1353NM 3 To be able to Create a network topology including Q3, 1850TSS and SNMP NEs 4 To be able to Supervise a Q3, 1850TSS-320 and SNMP Network Element 5 To be able to Perform the basic management operations on Q3, 1850TSS-320 and SNMP NE management 6 To be able to Handle the AS application for current alarms and the alarm history 7 8 To be able to Manage the transmission quality records To be able to Perform the basic administration tasks in the operator field
Self-Assessment of Objectives [cont.]

10
Page 10

Instructional objectives Yes (or Globally yes) No (or globally no) Comments
Other comments
Thank you for your answers to this questionnaire
Section 1 Product Overview

Module 1 Product Overview

All rights reserved 2006, Alcatel 3FL41020ACAAWBZZA Edition 1.00 Section 1 - Module 1 - Page 1
Blank Page
Product Overview - Product Overview 1-1-
Alcatel 1353NM Alcatel 1353NM rel. 7.4 Operation
Document History Edition 01 Date 2007-02-07 Author Sangalli Roberto Remarks First edition
Objectives
Objective: To be able to
identify and localise the system functions into the TMN describe the system architecture
Objectives [cont.]
Table of Contents

1 TMN Description 2 1353NM Management Functions 3 System Architecture
Page 7 15 23

Product Overview - Product Overview
1-1-
1 TMN Description
1 TMN description
The TMN
A Telecommunication Management Network (TMN) is a structured network featuring management functions for a Telecommunication Network (TN) The TMN is structured in layers
EML: Element Management Layer
To manage the network element configuration, alarms and performance
NML: Network Management Layer

To manage network connectivity, routing and protections in various topologies and across different regions
SML: Service Management Layer

To manage services offered to the customer: order handling, service handling, billing, service development, planning
BML: Business Management Layer

To manage the overall sales activity: e.g. return on investment, system decision support, market analysis
1353NM belongs to the EML 1354RM belongs to the NML
1 TMN description
TMN Layers
NML
1354RM
Interface IOO
OPTICS-IM / SEN-IM
EML
Q3/SNMP Q3 Q3
1353NM
Q3
1540 CT DXC CT
Interface IOO QB3*

1320NX NECTAS
SNMP
1320 CT
ECT
1320 CT
F
2G ADM(*), OMSN, ION, Terr. WDM, 2G Radio
F
Subm. WDM
F
ISA, CWDM(***), Melodie(****), AWY, Radio SONET,
NE
4G 1850TSS
Litespan(**)
OMSG F
NE Network Element PDH or SDH Transmission equipment. ECT Equipment Craft Terminal for local management TN Telecommunication Network This network is made of interconnected NEs . It represents the physical media ensuring the transmission function (e.g.: STM16 ring made of 1660SM OMSNs). EML Element Management Layer The whole NE configuration can be managed from this layer on an individual basis: hardware, crossconnections, synchronisation, protections, alarms, performance... The Alcatel EML layer is made of 1353NM (centralised system) NML Network Management Layer The system belonging to this layer allows the operators to manage connectivity, routing (trails and paths) and the relevant protections in various topologies. Furthermore the NML is in charge of Network Alarms and Performance Monitoring. The Alcatel NML layer is made of 1354R (centralised system) . TMN Telecommunication Management Network This management network is made of 5 layers. Only EML and NML are referred in this document. (*) 1664SM and 1666-55SR starting from Rel 3.2 (**) 1540SDH starting from Rel. 2.1B (***) 1692MSP (****) 946LUX50
1 TMN description
NEs managed by the 1353NM7

10
1353NM 1353NM
OSI QB3* interface OSI CMIP interface IP SNMP interface IP CMIP interface OSI CMIP + IP SNMP interface
CWDM(***) Submarine WDM ISA
AWY 4G 1850TSS
Melodie(****)
Radio SONET 3rd party NEs(*****) 2G ADM(*) OMSN ION MW 2G
Terr. WDM
OMSG
Litespan(**)
Alcatel 1353NM Alcatel 1353NM rel. 7.4 Operation All rights reserved 2006, Alcatel
1353NM Rel7.4 doesnt support anymore the 1G QB3* NEs, that are: 1G ADM 1G MW 1G WDM The only exception are the QB3* Submarine WDM, still managed due to the long-term support required by these NEs (*) (**) (***) (****) (*****) 1664SM and 1666-55SR starting from Rel 3.2 1540SDH starting from Rel. 2.1B 1692MSP 946LUX50 LineView Rel2.0; OA512 Rel1.0; LightSand 1693SE R1.0; LightSand 1696SE R1.0; Tropic Networks 1696ROADM R4.0; Selta 1615BCE R1.0; Stratex Networks A9500MXC R1.0; Aimsys 1608LS R1.0
1 TMN description
EML-IM
11
The NEs are managed from the 1353NM via EML IM The EML IM is responsible for maintaining a consistent view of the NE configuration and status. It is responsible for managing NEs of different types and releases There are several EML IM classes per 1353NM (see notes). Each EML IM classes can have several instances, created during the system installation and configuration
EML IMs available in 1353NM Rel7.4 EMLIMWDMSUBNR7: EMLIMADMQ3: EMLIMDXCQ3: EMLIMCORBASNMP: EMLIMSGM: EMLIM4G: EMLIM9500MXC: Information Manager for QB3* Submarine WDM Information Manager for NEs managed via the OSI CMIP-Q3 interface Information Manager for OMSG (Digital cross connect) managed via the IP CMIP-Q3 interface Information Manager for NEs managed via the IP SNMP interface SNMP Generic Mapper; Information Manager for some 3rd party NEs managed via the IP SNMP interface Information Manager for 4G NEs Information Manager for Microwave Radio Equipment 9500MXC managed via the IP SNMP interface
1 TMN description
QB3* / Q3 NE
12
QB3* NE
NE local configuration based on NECTAS tables Requires translation between NECTAS tables and OS object management Duplication of configuration database (MIB) in NE and in OS
Q3 NE
NE local configuration based on object management Only one database in the NE Any modification is performed directly on the NE
N.B.: 1353NM Rel7.4 doesnt 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
1 TMN description
NE QB3*/Q3 - OS dialogue
13
RM
SEN-IM USM
DB
TSD-IM USM
1
PNM
1 2
QB3* EML-IM SH-IM
Nectas tables
2
TSD-IM
USM AS DB
AS-IM
PNM-IM PNM-IM SH-IM MIB
1
Q3 EML-IM
SH
QB3*
TSD-IM Q3
Nectas tables
ADM
NE
DB
The 1353NM acts as a pass-through for messages from/to 1354RM to/from Q3 NEs. 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. 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.
Blank Page
Product Overview - Product Overview 1 - 1 - 14
1-1-
15
2 1353NM Management Functions
Network Topology Functions

16
Network Topology Management
Network Topology Management Creating the topology Adding/deleting symbols Declaring NEs NE inventory
Network Element and Software Management Functions

17
Network Element Management
Software Management
Network Element Management Supervising NEs Swapping boards and subracks Configuring protection plans Enabling/disabling alarm notifications Configuring the alarm severity profile Managing NE time and synchronisation sources Managing interconnections Managing ports Configuring external points Backing up and restoring the NEs configuration Software management Get information on software downloaded to the NE Downloading software from a server to an NE Activating / deactivating NE software Commissioning NE software
Alarm Functions
18
Alarms Management
Alarms Management Receiving and processing alarms Setting up filter criteria for receiving alarms Managing alarm log files Internal storage and processing of current alarms information Internal storage and processing of alarm history information User interface service for display purposes Alarms represented summarily in all views concerning an entity
Performance Functions
19
Performance Monitoring Management
Performance Monitoring Management Configuring the error counters threshold Monitoring performance counters Logging performance data Search for degraded quality TP
System administration Functions

20
System Management
Security Management
1353NM
System Management (for the administrator) Starting/stopping the system System trace and logs Displaying and managing all 1353NM processes System Backup/Restore Periodic actions Security Management Accessing the system Assigning profiles Distributing maps Access rights to the NE
Functions of the 1354RM

21
STM/16 2400Mb/s
STM/4 600Mb/s
Interconnected rings Network management Topology management Routing provisioning Protections management Alarm management Performance Monitoring System administration
Meshed subnetworks
STM/4 600Mb/s
STM/1 150 Mb/s
Cross Connect/ION ADM, OMSN and WDM NEs
STM/1 150 Mb/s
Linear chain
Upload of available NE and Port information from the 1353NM7 Construction of the static part of the managed network Link Connections Elementary topologies (rings, meshes, ...) Applying the layered concept according to G. 803 Physical, Multiplex section, HO trails, LO trails, Paths Configuring and managing the dynamic part of the network Payload configuration Path provisioning Path supervision and maintenance Join / Split Consistency control of SEN-IM and OPTICS-IM based NEs Download disable management Consistency audit and download management NE isolation detection and recovery Protections management SNCP Drop & Continue 2F MS-SPRING and NPE Restoration rules ASON/GMRE management on ION nodes Performance Monitoring Customised measures creation and analysis Alarms Management Alarm severity management (ASAP) Alarm monitoring and records management Northbound Interface management (ioo)
IOO interface Functions

22
NML Alcatel Transport Network
NML
External OS
Access Access Network Network
EML
IOO interface
switching switching Network Network Data Data Network Network
1353NM Alarms Performance Monitoring Network Directory Remote Inventory 1354RM
Ioo is an interface allowing the synchronization between an external application and the Alcatel Transmission Management Network application. Two different services are provided Solicited service. The EOS requests the data as soon as it is interested in. Unsolicited service. The EOS registers itself to receive automatically all the new data. Alarms The Ioo is able to export alarms (throughout SNMP or a socket based ASCII interface) using either CSV or AVA formats. The EOS can ask for the current alarm list, and then receive alarms in unsolicited way. Performance monitoring The Ioo is able to export Performance Monitoring data (through a socket based ASCII interface or FTP) using either CSV or AVA formats. The Ioo interface can export The list of TPs where PM has been activated The actual PM measurements data. Network directory 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 The Ioo is able to export the Remote Inventory of Network Elements managed by the 1353NM product.
1-1-
23
3 System Architecture
Hardware architecture
24
Hardware-Architecture
Alcatel 1353 NM may run on a scalable set of computers ranging from small to large servers, providing the best cost performance ratio depending on the managed network size. Access to the system is provided using PCs through Go-Global software.
High Availability
In order to provide high service availability, different levels of resilient configurations can be provided on servers, ranging from simple disk mirroring, cold standby systems, warm active/standby systems and remote crash recovery centre.
Hardware architecture
25
1353NM Master Server LAN
1353NM Presentation Server
QB3*/Q3
GNE
QECC*/ QECC STM-n
(Gateway Network Element)
NE
PC
NE
The 1353NM system can be installed as: A master server (to run the IM and USM processes) 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
Hardware architecture [cont.]

26
IM Server USM Server
PCs
Software architecture
27
From the software point of view, the 1353NM is composed of two subsystems:
User Service Manager (USM)
This subsystem interacts with the user, processing his requests and issuing them to the appropriate IM subsystem.
Information Manager (IM)

This subsystem handles the logical functional data processing and its persistency
This subdivision is reflected in the installation (Master and Presentation servers)
Software architecture [cont.]

28
The Master Server (IM)

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.
The Presentation server (USM)

A Presentation server can provide the presentation instances for 1353NM and 1354RM.
1353NM rel.7.3 and rel. 7.4 co-hosting

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.
Exercise
29
Exercise 1: TMN description Exercise 2: TN description
Exercise 1: TMN description

30
Draw here below the TMN available for the training:

1353NM servers (master and presentation if any) Bridges PCs DCN (LAN, Hubs and routers if any)
Exercise 2: TN description
31
Draw here below the TN structure available for the training:

Ring, meshed or linear topologies OMSNs, ISA or 4G 1850TSS GNE(s)
1-1-
32
End of Module Product Overview
Section 2 Graphical Interfaces

Module 1 How to Logon

Blank Page
Graphical Interfaces - How to Logon 2-1-2
Objectives
Objectives: to be able to
Login, start the TMN-OS icon, start the main applications of 1353NM
Objectives [cont.]
Table of Contents

1 Login and Workspace Front Panel 2 The TMN-OS Icon 3 Windows & Workspace Menu
Page 7 13 21

Graphical Interfaces - How to Logon
2-1-7
1 Login and Workspace Front Panel
Access from PC with Go-global

1. Double click on the Go-global icon on the
desk
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
At step 2, instead of Normal Desktop, also Alcatel TMN Oss can be chosen. In this latter case, the user can open the 1353NM session without providing any additional login. 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
Login screen
Work Station name Login name Push buttons
Enter user name then click OK or press "Enter" key Enter "password" then click "OK" or press "Enter" key
OK Start Over Options Help
confirms deletes input changes session option (to log onto single windows for example) opens the help window
The default user defined on the systems is: alcatel It has the administrator privileges. Other users with different profiles can be created by the administrator. The former axadmin must not be used as administrator for graphical session.
2 - 1 - 10
Ws activity Clock Date Padlock Workspaces File manager
TMN OS
Text editor
Exit
Printer Mail
Terminal
Only admin profiles can access "file manager" and "terminal" files.
Locking the session

Graphical Interfaces - How to Logon 2 - 1 - 11
Manual lock is used to lock the screen immediately

select the padlock icon in the front panel
When the session is locked, enter the password and press Enter key to continue the job
Blank Page
Graphical Interfaces - How to Logon 2-1-
12
2 - 1 - 13
2 The TMN-OS Icon
2 The TMN-OS Icon
2 - 1 - 14
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. All the instances installed on the server are displayed. The menus & icons are context sensitive.
The 1353NM is selected

The color of each icon depends on the OS process state: Green: all the processes are running Red: at least one process is not running Blue: all the processes are stopped Yellow: the process state is unknown. It may be due to a isolation condition.
2 The TMN-OS Icon
2 - 1 - 15
Performance monitoring
Exit
System configuration
Topology manager Alarms
Process monitoring System information
1353NM Admin
System configuration, Process monitoring and 1353NM Admin are Administrative functions System information: gives infos 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
2 The TMN-OS Icon
View and OS Menus

This menu permits to hide/show the message area.
This are administrative functions. They depend on the user profile.
2 The TMN-OS Icon
Action menu
This menu permits to start the main operations available on the 1353NM. The SMF depends on the user profile.
2 The TMN-OS Icon
Global action 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.
2 The TMN-OS Icon
Close 1353NM session

First possibility: with the workspace menu

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

Select the "exit" button on the control panel
Remember : close all the graphical applications before closing the session
Blank Page
20
2 - 1 - 21
3 Windows & Workspace Menu
3 Window & Workspace Menu
Window menu button

On an opened window, click on the upper left corner 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 workspace Window is removed from the current workspace Close the current window
Workspace menu
Locate the mouse pointer on the background (i.e. outside any window). Press the right-hand button of the mouse. The following menu appears:
Starts the TMN-OS icon Opens a Unix terminal (for OS Admin only) Prints the screen or a window
2 - 1 - 24
Locate the mouse pointer on the background (i.e. outside any window). Press the left-hand button of the mouse. The following menu appears:
Pops up the selected window Pops down the selected window Minimize the front panel: useful when the task bar is enabled
Exercise
Exercise 1: Explore the TMN-OS icon for the 1354RM instance
See next pages
Exercise 1: Explore the TMN-OS icon for the 1354RM instance

1. Log on the 1354RM 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:
User Interface Alarms

5. Move a window from one workspace to another one. 6. Manually lock and unlock the session
Blank Page
27
2 - 1 - 28
End of Module How to Logon
Section 2 Graphical Interfaces

Module 2 Network Topology

Blank Page
Graphical Interfaces - Network Topology 2-2-2
Objectives
Objective: to be able to
create a network topology including Q3, 1850TSS and SNMP NEs
Objectives [cont.]
Table of Contents

1 Creating a map 2 Managing and addressing a NE on a map 2.1 Creating and Addressing a Q3 NE 2.2 Creating and Addressing ISA boards 2.3 Creating and Addressing a 1850TSS NE 2.3.1 1850TSS NE in PTRP Configuration 2.3.2 1850TSS NE in MSPP Configuration 2.3.3 1850TSS NE in Full Data Configuration 2.4 Creating and Addressing a SNMP NE 2.5 NE Autodiscovery 2.6 Map Population 3 Creating a Graphical Connection 4 Creating the GNE List 5 Addressing the NEs with IP Tunnel: OSI over IP 6 Distributing Maps
Page 7 19 21 35 55 59 71 103 105 111 127 139 145 151 161

Page
Graphical Interfaces - Network Topology
2-2-7
1 Creating a map
1 Creating a map
Reminder: map definition

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 Child submap related to a parent object
Map
Submap SM1
NE
Submap SM2
Submap SM11
NE NE
Submap SM12
NE NE Browser
MAP: collection of symbols interconnected to represent a network SUBMAP: collection of related symbols displayed in a single graphical window submaps are organised in a hierarchical way each submap may contain symbols representing other submaps OBJECTS: Sites, NEs, connections between these different entities managed symbols: supervised entities managed by the OS (e.g. NEs) 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.
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
The operator can customise this new map automatically created. Nevertheless, from this step, the operator can create, manually, one more new map and then, customise it (see next page).
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 hierarchy
1 Creating a map
Creating a new map

1. From the current map, select
File
New map
A new map, containing only a Root submap, appears.

2. Authorise a free layout, selecting
Edit
3. Disable Frozen Mode if necessary :
Layout Network Frozen Mode
1 Creating a map
Customizing a Map
The root submap can be customised as follow: 1. Select the menu
View
View Parameters
2. Define the following parameters:
Name : unique and without spaces Background : from the list Layout : e.g. Cartesian 3. Click OK and the update of the related window appears:
1 Creating a map
Creating a submap : by Child View

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
1.
5.
Double click on the new symbol, an empty Child view appears

1 Creating a map
Creating a submap : by Add Symbol

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 , the new symbol appears
1.
5.
Double click on the symbol to attach a Child view and answer OK

1 Creating a map
Creating a submap : by Add Symbol [cont.]

1.
Define the following parameters using View

Background : from the list Layout : e.g. Cartesian
View Parameters :
2.
Click OK and the created submap appears
1 Creating a map
Saving a map
1. Select the menu 2. Click
File
Local Persistency
Save Map as
Define a File Name : --- (unique name without spaces)
Save
1 Creating a map
Restoring a map
1. Select the menu 2. Click
File
Local Persistency
Restore Map
Select a File then the File Name field is updated
Restore
1 Creating a map
Exercise
Create a new map (each group should use a different name) Create a child submap Save the created map, close it and open it
2 - 2 - 19
2 Managing and addressing a NE on a map
Blank Page
Graphical Interfaces - Network Topology 2-2-
20
2 - 2 - 21
2.1 Creating and Addressing a Q3 NE
Prerequisites
A Q3 NE can be created and correctly supervised only if the following processes have been configured and are running on the 1353NM System:
A Supervision_Area linked to the System Ethernet interface (e.g. lan0) A Necom_SubSystem associated to this Supervision_Area A EMLIMADMQ3 associated to the same Supervision_Area
Check the correct configuration and process status with the System Administrator
NE Creation
1. Open the related submap 2. Choose
Declarations
Create
NE
3. Fill in the NE Creation window
Select the appropriate:

NE family Type of equipment Release of equipment
Fill in the two mandatory fields :

User label Location Name
4. Click
Apply to launch the creation
The created NE appears on the submap
5. Close the window or create more NEs 6. Manage the related addresses (NE &
OS). See next pages.
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.
EMLIM and Supervision Area assignement

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. To display the list of the existing EML-IMs, open the Process Monitoring window as follow:
From TMN-OSs Management window, select 1353NM icon then click on the Process Monitoring Icon In the Process Monitoring window , expand the tree structure up to the Retix stack and the EML-IM list. Identify the processes which can be in charge of the NE to be created.
Supervision Area (primary)
The Retix stack sub processes suffix suggest the Supervision EML domain (100 or 101) Area EML domain must be chosen among the EMLIMADMQ3 ones
System addressing - NSAP address

An NSAP address represents globally a unique location in the OSI environment (i.e. it must be unique for the specified equipment) The NSAP address is made of two parts :
IDP : defining the address structure DSP : the address itself
NSAP IDP AFI

1 byte
DSP IDI DFI

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

D1
Area
D2
A1
A3
NE System ID
A2
Domain
A4

Two types of equipment:

Intermediate Systems (IS), with routing table End Systems (ES), without routing table
ES IS
Two protocols:
ES-IS between an ES equipment and an IS equipment IS-IS between two IS equipment.
Each Alcatel equipment runs as an Intermediate System (IS) equipment and uses the IS-IS protocol.
Level L1, L2, non-pure L2 for routing tables

Level L1
Knowledge of the topology of the area in which the NE is located.
Level L2
Knowledge of the topology of all L2 routers in the domain (i.e. knowledge of all the NEs which make the inter-area routing in a given domain). L1 L2 Non pure
Level non-pure L2
Knowledge of the topology of the area and of all level L2 routers in the domain. (Nonpure L2 = L2 + L1 )
NE addressing
1. By the CT, get or configure
the NE address from the Equipment View (NE): Select menu Configuration Comm/Routing Local Configuration
If already configured the following addresses are shown:
Presentation: Session: Transport: 0002 00 00
If necessary, configure or modify and click "OK If no modification is done, click Cancel
To open the Equipment view from 1320CT: Select the supervised NE into the map
Supervision
NE Login
NE addressing [cont.]
2. By the CT, configure the OS
address on the NE from the Equipment View (NE): Select menu Configuration Comm/Routing OS Configuration
Enter the main (and the spare if any) OS NSAP addresses: Click OK
3. By the CT, verify or set the
LAPD configurations from the Equipment View (NE): Select menu Configuration Comm/Routing Interfaces Configuration LAPD Configuration
For each SDH port between the GNE and any other NE to reach, make sure the LAPD interfaces are created and configured :
Network / User
Click Apply to confirm any modification then Close
4. By the CT, enable the Ethernet
configuration if necessary from the Equipment View (NE): Select menu Configuration Comm/Routing Interfaces Configuration Ethernet Configuration
Click on yes to enable it Click Apply to confirm any modification then Close
For the gateway NE it is necessary to enable the Ethernet interface
Configure the address of the NE on the 1353NM

Select the NE to be addressed Select the menu Declarations
Set Addresses
Presentation: Session: Transport:
NE Address
0002 00 00
Enter the values for the selectors
Enter the NSAP address (as for Local Configuration) Click Apply then close
The NE address can be modified only if the NE is not supervised (i.e. in the "declared" state). However, it can still be displayed.
Blank Page
34
2 - 2 - 35
2.2 Creating and Addressing ISA boards
ISA boards and 1353NM interworking

ISA boards are inserted into the OMSN shelves. The communication towards the 1353NM is via SNMP protocol. Each of them will be considered by the 1353NM as a Sub NE while the related OMSN will be considered as a Host NE. Therefore their creation and addresses will have to be managed. See next pages.
1353NM SNMP EMLIM Q3 EMLIM
DCN DCN
ISA Board
OMSN Equipment Controller
Creating an ISA board

1. From Equipment view of the Host NE,
insert the ISA configuration:
board
in
the
NE
Select the unit and the slot in which the ISA board has to be inserted Choose the menu Equipment Set Choose the desired board and click on Ok
Creating an ISA board [cont.]

2. From Equipment view of the
Host NE get or set the IP address of the ISA board:

Choose the menu
Configuration Comm/Routing Configuration IP address
IP ISA board
select the required board If necessary set the IP address and Apply Click Close
When the Host NE is not yet supervised, step 2) can be performed using the craft terminal 1320CT ISA board IP address can be managed also using the options: Equipment
ISA board IP Address

3. Open the submap in which the Host
NE (OMSN) is located and select it 4. Choose the menu Declarations
Create ISA
5. Fill in the window :
Create ISA
Family type, Board type, Release type, Label (slot), IP address and (optionally, only if Advanced is selected) EML domain
6. Click
Apply then Quit (*)
Clicking on Add on Tunnel, an IP over OSI tunnel is automatically configured (see next slides for explanations)
The use of Advanced configuration is not mandatory. Instead of automatic choices made by the 1353NM, it provides the operator the opportunity to : Assign a particular EML IM Set a particular NE ID (*) N.B.: Click Quit only after the ISA board just configured appears in the bottom part of the screen

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 of any other NE.
ISA board OMSN

The ISA board as a Sub NE can be removed as standard NE using
Declarations
option.
Delete
Generic
ISA boards and communication stacks concept

OSI DCN
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
Communication between 1353NM and ISA boards

The IP-over-OSI feature at 1353NM level aims at:

Keeping OSI DCN backbones (no OPSFv2 introduction, no router reconfiguration) Supporting SNMP traffic to/from ISA Boards with a single e2e tunnel Fully exploitation of OSI DCN resilience
IP over OSI tunnel setting up procedure

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 2. 3. 4. 5. 6.
processes have been instantiated in the NM Configure the IP Point-to-Point interface into the OMSN hosting the ISA board Configure the IP over OSI tunnel into the OMSN Configure the IP Static Routing Configuration into the OMSN Create the IP over OSI Tunnel into the 1353NM Eventually, add other ISA board to the created IP over OSI tunnel
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 tunnels towards different NEs. It means that with a single ositunneling process, different ISA boards located in different OMSN can be supervised.
Step 1
1. Click on
2. Check that a EMLIMCORBANSNMP, ositunneling and Osi_Manager processes are running. EMLIMCORBANSNMP process must be associated to an OSI tunnel
If the required processes are not running, ask to the System Administrator for their instantiation
Step 2
1. From the OMSN Equipment View, click on
2. Insert the IP Address of the IP Point-to-Point interface
Step 3
2. Insert the NSAP (OSI) Address of the 1353NM 3. IP Routing = None

Step 4
2. Insert the IP Address of the tunnel defined in the 1353NM system configuration (ask the System Administrator) 3. Select CLNP Tunnel
Step 5
1. From the TMN-OS Management, issue 1353NM Admin
2. Click on NE Administration and then on IP over Osi Tunneling
As shown at page 57, the IP over OSI Tunnel can be automatically configured by the System during the ISA board declaration.
Step 5 [cont.]
4. Select the desired NE. Set Tunnel Type = ALCATEL and then Confirm
3.
Step 6
5. Eventually Add the NE IP (ISA Boards) on Tunnel: Now the user can start supervision on the added ISA Board
The tool automatically add the already declared NE IP to the tunnel
Tunnel details
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/host file):
Removing Tunnels
Before removing the tunnel, all the NE IP on tunnel must be removed 1. Click on Remove (NE IP on tunnel) 2. Click on Check in to remove this IP NE
Removing Tunnels [cont.]

3. Remove the Tunnel
The tool automatically add the already declared NE IP to the tunnel
Blank Page
54
2 - 2 - 55
2.3 Creating and Addressing a 1850TSS NE
Generalities
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. The Alcatel 1850 TSS platform comes in five sizes, according to different transport switching capacities: 1850 TSS-15, TSS-40, TSS-100, TSS-320 and TSS-640. In NR 8.1 (1353NM Rel7.4) only TSS-40 and TSS-320 are supported. 1850 TSS-40 is seen by the network management as a pure SNMP NE, so please refer to the chapter dedicated to the SNMP NE creation and addressing further on in this chapter 1850 TSS-320 is an integrated TDM/Data platform that can be configured as:
Pure TRansport Platform (PTRP), providing pure TDM and WDM transport capability Multi-Service Provisioning Platform (MSPP), providing the capability of integrated transport of TDM and data traffic. Carrier Ethernet Transport Platform (CETP), or Full Data, providing data traffic transport capability.
Management of 1850 TSS-320

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

SNMP Agent
Management of 1850 TSS-320 [cont.]

Regardless if the agents hosted are one or two (Q3 or/and SNMP), the 1850 TSS320 NE is managed as a single NE by the 1353NM
A single NE is represented on the MAP The protocols and models used to interface the NE (Q3 and/or SNMP) are correlated by a EML coordinator process Based on the NE configuration, one or two communication sessions are established between the 1353NM and the NE: a Q3 session or/and a SNMP session. 4G EMLIM
EML Coordinator
Q3 Protocol adapter
Q3
SNMP Protocol adapter

SNMP
TSS-320 MSPP
Q3 Agent SNMP Agent
Example of a TSS-320 in MSPP configuration

2 - 2 - 59
2.3.1 1850TSS NE in PTRP Configuration
Creating a 1850TSS NE in PTRP Configuration

A 1850TSS MSPP NE in PTRP configuration is managed by the 1353NM, through the 4G EMLIM, by means of the only Q3 communication session. It can be created and correctly supervised only if the following processes have been configured and are running on the 1353NM System:
A Supervision_Area linked to the System Ethernet interface (e.g. lan0) A Necom_SubSystem associated to this Supervision_Area A EMLIM4G associated to the same Supervision_Area
4G EMLIM
EML Coordinator
Q3 Protocol adapter Q3 TSS-320 PTRP

Q3 Agent
In this configuration, only the Q3 communication session needs to be established between the 1353NM and the 1850TSS NE. Therefore, a Q3 DCN is needed in order to manage the equipment.
2.3.2 1850TSS NE in MSPP Configuration
Creation Procedure
The following procedure must be applied for managing a 1850TSS MSPP NE in PTRP configuration in the 1353NM
1. Check the correct configuration and process status with the System 2. 3. 4. 5. 6.
Administrator (see previous page) Create the 1850TSS NE Check/Configure the OSI Local Address of the NE by the CT Check/Configure the OS Address in the NE by the CT Check/Configure the LAPD and the Ethernet interface in the NE by the CT Configure the NE address in the 1353NM
Creation Procedure: Step 1

1. Click on
Primary Supervision Area linked to a Necom OSI stack EMLIM4G

Declarations
Create
NE

NE family: TransportServiceSwitch Type of equipment: 1850TSS-320 Release of equipment

4. Click
5. Close the window or create more NEs
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 EMLIM4G ones trying to make it homogeneous.
Creation Procedure: Step 2 [cont.]

From TMN-OSs Management window, select 1353NM icon then click on In the Process Monitoring window , expand the tree structure up to the Retix stack and the EML-IM list. Identify the processes which can be in charge of the NE to be created.
The Retix stack sub processes suffix suggest the Supervision Area EML domain must be chosen among the EMLIM4G
EML domain (103)

By the CT, get or configure the NE address from the Equipment View (NE):
Select menu Configuration Comm/Routing Local Configuration OSI Configuration If already configured the following addresses are shown:
Supervision
NE Login

By the CT, configure the OS address on the NE from the Equipment View (NE):
Select menu Configuration Comm/Routing OS Configuration Enter the main (and the spare if any) OS NSAP addresses: Click OK

By the CT, verify or set the LAPD configurations from the Equipment View (NE):
Select menu Configuration Comm/Routing Interfaces Configuration LAPD Configuration For each SDH port between the GNE and any other NE to reach, make sure the LAPD interfaces are created and configured : Network / User Network Protocol = OSI Click Apply to confirm any modification then Close
Creation Procedure: Step 5 [cont.]

By the CT, enable the Ethernet configuration if necessary from the Equipment View (NE):
Select menu Configuration Comm/Routing Interfaces Configuration Ethernet Configuration Click on yes to enable it Network Protocol = OSI Click Apply to confirm any modification then Close


Set Addresses
NE Address
0002 00 00
Enter the NSAP address (as for Local Configuration) Leave blank the IP Address field Click Apply then close
Blank Page
70
2 - 2 - 71
Creating a 1850TSS NE in MSPP Configuration

A 1850TSS MSPP NE in MSPP configuration is managed by the 1353NM, through the 4G EMLIM, by means of both a Q3 and a SNMP communication session. The two sessions can be supported:
By a OSI/IP DCN, with both the Q3 and the SNMP sessions running independently. By a pure OSI DCN, with the SNMP session flowing through an IP over OSI tunnel between the 1353NM and the Q3 interface of the 1850TSS NE 4G EMLIM
EML Coordinator
Q3 Protocol adapter
Q3

SNMP
TSS-320 MSPP
Q3 Agent SNMP Agent
In this configuration, both the Q3 and the SNMP communication sessions need to be established between the 1353NM and the 1850TSS NE. Therefore, the DCN must support both the protocols. This can be achieved in two ways: A DCN able to transport contemporarily both the Q3 and the SNMP traffic (OSI/IP DCN) A Q3 DCN over which an IP over OSI tunnel must be instantiated (OSI DCN)
Creating a 1850TSS NE in MSPP Configuration: OSI/IP DCN

When a OSI/IP DCN is available, both the OSI and the SNMP management session can contemporarily run over the same network infrastructure.
4G EMLIM
EML Coordinator
Q3 Protocol adapter
TSS-320 MSPP
OSI/IP DCN
SNMP session (IP traffic) Q3 session (OSI traffic)
Q3 Agent
SNMP Agent
Creating a 1850TSS NE in MSPP Configuration: OSI/IP DCN [cont.]

In this case, the 1850TSS NE can be created and correctly supervised only if the following processes have been configured and are running on the 1353NM System:
A Supervision_Area linked to the System Ethernet interface (e.g. lan0) A Necom_SubSystem associated to this Supervision_Area A EMLIM4G associated to the same Supervision_Area
Creation Procedure: OSI/IP DCN

The following procedure must be applied

1. Check the correct configuration and process status with the System 2. 3. 4. 5. 6. 7.
Administrator (see previous page) Create the 1850TSS NE Check/Configure the OSI Local Address of the NE by the CT Check/Configure the IP Local Address of the NE by the CT Check/Configure the OS Address in the NE by the CT Check/Configure the LAPD and the Ethernet interface in the NE by the CT Configure the NE address in the 1353NM
Creation Procedure (OSI/IP DCN): Step 1

1. Click on

Declarations
Create
NE


4. Click
Creation Procedure (OSI/IP DCN): Step 2 [cont.]

From TMN-OSs Management window, select 1353NM icon then click on In the Process Monitoring window , expand the tree structure up to the Retix stack and the EML-IM list. Identify the processes which can be in charge of the NE to be created.
The Retix stack sub processes suffix suggest the Supervision Area EML domain must be chosen among the EMLIM4G
EML domain (103)


Select menu Configuration Comm/Routing Local Configuration IP Configuration Assign the IP Address and click Apply If no modification is done, click Close
Supervision
NE Login


Select menu Configuration Comm/Routing Interfaces Configuration LAPD Configuration For each SDH port between the GNE and any other NE to reach, make sure the LAPD interfaces are created and configured : Network / User Network Protocol = IP and OSI Click Apply to confirm any modification then Close
Creation Procedure (OSI/IP DCN): Step 6 [cont.]

Select menu Configuration Comm/Routing Interfaces Configuration Ethernet Configuration Click on yes to enable it Network Protocol = OSI and IP Configure an IP address and IP mask in the IP section IP Routing Protocol = ISIS Click Apply to confirm any modification then Close


Set Addresses
NE Address
0002 00 00
Enter the NSAP address (as for Local Configuration) Configure the IP Address field:
X.Y.Z.W:161 (the UDP Port is always 161)
Click Apply then close
The NE address can be modified only if the NE is not supervised (i.e. in the "declared" state). However, it can still be displayed. 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
Creating a 1850TSS NE in MSPP Configuration: OSI DCN

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. 1353NM
4G EMLIM
EML Coordinator
Q3 Protocol adapter
OSI DCN
IP over OSI Tunnel
SNMP session (IP traffic) IP over OSI tunnel (encapsulates IP traffic in OSI traffic) Q3 session
Alcatel 1353NM Alcatel 1353NM rel. 7.4 Operation TSS-320 MSPP
Q3 Agent SNMP Agent
Creating a 1850TSS NE in MSPP Configuration: OSI DCN [cont.]

In this case, the 1850TSS NE can be created and correctly supervised only if the following processes have been configured and are running on the 1353NM System:
A Supervision_Area (e.g. primary) linked to the System Ethernet interface (e.g. lan0) A Necom_SubSystem associated to this Supervision_Area A Supervision_Area (e.g. virtual) dedicated to the IP over OSI Tunnel A OSI_MANAGER and a ositunnel associated to the virtual Supervision_Area A EMLIM4G associated to both the primary and the virtual Supervision_Area
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
Creation Procedure: OSI DCN

The following procedure must be applied

1. Check the correct configuration and process status with the System
Administrator (see previous page) 2. Create the 1850TSS NE 3. Check/Configure the OSI Local Address of the NE by the CT 4. Check/Configure the IP Local Address of the NE by the CT 5. Check/Configure the OS Address in the NE by the CT 6. Check/Configure the LAPD and the Ethernet interface in the NE by the 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
Creation Procedure (OSI DCN): Step 1

1. Click on
Ositunnel and Osi_Manager

Declarations
Create
NE


4. Click
Creation Procedure (OSI DCN): Step 2 [cont.]

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. To display the list of the existing EMLIMs, open the Process Monitoring window as follow:
From TMN-OSs Management window, select 1353NM icon then click on In the Process Monitoring window , expand the tree structure up to the EML-IM list. Identify the processes which can be in charge of the NE to be created.
EML domain must be chosen among the EMLIM4G The Supervision Area must be the secondary supervision area, linked with an IP over OSI tunnel, associated to the chosen EMLIM4G (e.g. virtual)
EML domain (102)

By the CT, get or configure the NE NSAP address from the Equipment View (NE):
Supervision
NE Login

By the CT, get or configure the IP NE address from the Equipment View (NE):
Select menu Configuration Comm/Routing Local Configuration IP Configuration Assign the IP Address and click Apply If no modification is done, click Close


Select menu Configuration Comm/Routing Interfaces Configuration LAPD Configuration For each SDH port between the GNE and any other NE to reach, make sure the LAPD interfaces are created and configured : Network / User Network Protocol = IP and OSI Click Apply to confirm any modification then Close

Select menu Configuration Comm/Routing Interfaces Configuration Ethernet Configuration Click on yes to enable it Network Protocol = OSI Click Apply to confirm any modification then Close


Set Addresses
NE Address
0002 00 00
Enter the NSAP address (as for Local Configuration) Configure the IP Address field:
X.Y.Z.W:161 (the UDP Port is always 161)
The NE address can be modified only if the NE is not supervised (i.e. in the "declared" state). However, it can still be displayed. 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

1. From the NE Equipment View, click on
2. Click on New, then insert the NSAP (OSI) Address of the 1353NM 3. IP Routing = None

1. From the NE 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 choose the relevant tunnel among the configured ones

1. From the TMN-OS Management, issue 1353NM Admin
2. Click on NE Administration and then on IP over Osi Tunneling

4. Select the 1850TSS NE. Set Tunnel Type = ALCATEL and then Confirm
3.

5. Add the NE IP (SNMP agent) on Tunnel: Now the user can start supervision also on the data SNMP agent of the 4G NE
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/host file):
Blank Page
102
2 - 2 - 103
2.3.3 1850TSS NE in Full Data Configuration
2.3.3 1850TSS NE in Full Data Configuration
Creating a 1850TSS NE in Full Data Configuration

A 1850TSS NE in Full Data configuration is managed by the 1353NM, through the 4G EMLIM, by means of the only SNMP communication session. At present time, the NE in this configuration is not yet available.
4G EMLIM
EML Coordinator
Q3 Protocol adapter

SNMP
TSS-320 Full Data

SNMP Agent
In this configuration, only the SNMP communication session needs to established between the 1353NM and the 1850TSS NE. Therefore, a TCP/IP DCN is needed in order to manage the equipment.
2 - 2 - 105
2.4 Creating and Addressing a SNMP NE
Prerequisites
A SNMP NE can be created and correctly supervised only if the following processes have been configured and are running on the 1353NM System:
A Supervision_Area linked to the System Ethernet interface (e.g. lan0) A EMLIMCORBASNMP associated to the same Supervision_Area
NE Creation
Declarations
Create
NE

NE family Type of equipment Release of equipment

4. Click
5. Close the window or create more NEs 6. Manage the related addresses (NE &
OS). See next pages.
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.
EMLIM and Supervision Area assignement

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. To display the list of the existing EMLIMs, open the Process Monitoring window as follow:
From TMN-OSs Management window, select 1353NM icon then click on In the Process Monitoring window , expand the tree structure up to the EMLIM list. Identify the processes which can be in charge of the NE to be created.
EML domain must be chosen among the EMLIMCORBASNMP ones
EML domain (103)
NE addressing
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):
Some SNMP NEs must be reached via their Local Address
Configuration Configuration Comm/Routing Comm/Routing Local Configuration Ethernet Configuration
Some other SNMP NEs must be reached via their Ethernet Interface Address 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
Please refer to the specific NE documentation for details
Supervision
NE Login

Set Addresses
NE Address
Enter the IP address (as for Local or Ethernet Configuration) followed by the UDP Port. UDP Port is always 161:
X.Y.Z.W:161
2 - 2 - 111
2.5 NE Autodiscovery
Principles
NE-autodiscovery is a feature that makes automatic the procedure of creating a new NE in the NM database. The following cosiderations apply:
The NE must first be created in the Craft Terminal and the following parameters must be set-up by the CT:
node name networking set-up (NE/OS addresses, routing protocols, tunnels, etc.)
Furthermore, DCN interconnecting the NE to the 1353NM must be up and running NE Autodiscovery procedure must be launched first by the CT after all the local transmission tests have been carried out, and the node is considered ready to support live traffic NE-autodiscovery procedure (bottom-up) is anyway compatible with the traditional top-down method, where new NEs are manually created on 1353NM
Principles [cont.]
The Discovery messages pass the following information:

NE type & release NE name and location NE address OS address (Q3 only)
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. Since the messages go through the node, they exploit the same DCN routes available to 1353NM when it will request the node supervision The procedure is different if the NE to be discovered is or not a 4G NE
NON-4G NEs: CT Perspective

If the NE to be discovered is NOT a 4G NE, the 1320CT (NES) provides a function dedicated to NE auto-discovery Node 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 addresses for every NE In-field engineers get the result of the autodiscovery procedure DISCOVERY OK the autodiscovery message has been ack-ed by 1353NM, NOC team is now informed DISCOVERY KO the autodiscovery 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
CT Perspective for 4G NE
If the NE to be discovered is a 4G NE, the auto-discovery function is directly exploited by the NE The 4G NE USM provides a Autodiscovery option, which triggers the discovery message directly from the NE to the 1353NM
ACK
DCN
1320CT New NE! 1353NM
NON-4G NE: What to do on the CT

1. Trigger the Autodiscovery Procedure by clicking on NEAD Update
Warning: The NE Autodiscovery feature is available on the CT starting from the CT-K Rel 3.3
For more detailed information, please refer to CT-K Rel. 3.3 Training Manual and Operator Handbook
NON-4G NE: What to do on the CT [cont.]

2. Select NMs address config
3. Insert the 1353NM Name and Address
NON-4G NE: What to do on the CT [cont.]

4. Choose the desired NM into the NE autodiscovery GUI
5. From the NE List, choose the relevant one
6. Click on Send
What to do on 4G NE
1. Trigger the Autodiscovery Procedure by issuing Configuration Management Autodiscovery
What to do on 4G NE [cont.]
2. Issue Autodiscovery = Enable
3. Click OK
4. Click Cancel: the window is closed
5. Open again the Autodiscovery window: the Status is now Succeeded 6. With Autodiscovery = disable, click OK to stop the procedure, then Cancel
What to do on the NM
On receipt of the NE autodiscovery message coming from the NE, into the NM the AS (Alarm Surveillance) application generates a Warning alarm into the specific NE Autodiscovery sublist. Then, the NE operator has two choices:
Navigate from the Autodiscovery alarm to Create NE Open the NE Autodiscovery application from the TMN-OS and then click on Create NE
In both cases, the Create NE Dialog window is presented to the operator.
What to do on the NM [cont.]

1. From the AS, click on External Application Related EmlUsm, or....
Next Page
1. ... from the TMN-OS, click on NE Autodiscovery Create NE

New NE 1. Click on the NE(s) to be created 2. Optionally, the user can modify the NE name or the Location name
4. Click on Create
3. Chose or leave unspecified Supervision Area and EML domain
The NE can also be refused


Ne new NE has been created into the NM database with the parameters contained in the Create NE window
ISA board Autodiscovery

Also ISA board can be created using the NE autodiscovery feature, provided that:
1. The ISA board must be first created in the NE together with its IP address; the 2. 3. 4. 5.
DCN must be up and running with all the necessary IP over OSI tunnels. By the CT, issue the NE autodiscovery window After having selected the ISA board to auto-discover, click on the send button A warning alarm is generated into the AS and the NM operator can then open the Create NE dialog window 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
Blank Page
126
2 - 2 - 127
2.6 Map Population
2.6 Map Population
Map and IM database

USM
IM
icon N1 NE1
(Map 1)
NE1
icon N2 NE1
(Map 2)
Graphic database
NE2
Processing database
The procedures for creating NEs which have been previously presented add an entry in the database of the IM process and adds an icon to the current submap (USM). This icon is linked to the entry in the IM database. Several icons, even icons belonging to different maps, can be linked to a given database entry (i.e. an NE). 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).
2.6 Map Population
Populating the map from the OS MIB

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 NEs already created appears
3. Select the targeted NEs from the list

2.6 Map Population
Populating the map from the OS MIB

4. Select the menu
Inventory
Population
5. If necessary, change the population
selection 6. Click Apply then Close
2.6 Map Population
Deleting an NE from a submap

This action simply deletes the NE from the current submap

1. In the network topology view, select the NE to be deleted from the
submap 2. Select the menu or or
Edit Edit Edit
Cut Delete Delete from all views
2.6 Map Population
Deleting a NE from the MIB

This action deletes the NE from the OS database 1) Select a NE in the map and Declarations Delete 2) Click Apply and Close after deletion
Generic
Exercise
Exercise 1: Create and address a Q3 NE Exercise 2: Create and address a ISA Board Exercise 3: Create and address a 1850TSS NE in MSPP configuration Exercise 4: NE autodiscovery feature Exercise 5: Map population
See next Pages
Exercise 1: Create and address a Q3 NE

Create a NE Set addresses of this new NE
Exercise 2: Create and address a ISA Board

For a given ISA board, set the required configuration in order to create the corresponding Sub NE and create it. For a Host NE and a related ISA board, set the IP routing configuration Create the IP over OSI tunnel
Exercise 3: Create and address a 1850TSS NE in MSPP configuration

Check the existence of the processes necessary to manage a 1850TSS NE Based on the DCN configuration:
Create the NE Assign the address to the NE Set the IP routing configuration Create the IP over OSI tunnel if necessary
Exercise 4: NE Autodiscovery
Perform the Autodiscovery procedure for a 1850TSS NE
Exercise 5: MAP Population

Add a NE on the map from the OS MIB Remove from the MIB one of the previously created NEs
2 - 2 - 139
3 Creating a Graphical Connection
3 Creating a graphical connection
Procedure
Two symbols can be linked by a connection

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

Blank Page
142
Exercise
Create a connection between two NEs
Blank Page
144
2 - 2 - 145
4 Creating the GNE List
4 Creating the GNE list
Principle
The GNE list is manually created by the operator The 1353NM doesn't check information validity This list could be used to make easier IP tunneling creation
Action 1353NM Admin NE administration List Gateway NE

Display a GNE list

Display Filter 1. Select the NE 2. Click here to modify the address 3. Enter the IP address if necessary (for IP tunneling)
Refresh
Save data on the disk 4. OK
Blank Page
148
Exercise
Set the GNE list to match the network structure
Blank Page
150
2 - 2 - 151
5 Addressing the NEs with IP Tunnel: OSI over IP
5 Addressing NEs with IP tunnel:OSI over IP
Principle
OSI over IP tunneling is a technique that consists in the insertion (encapsulation) of the OSI traffic in IP packets. The extremities of the tunnels are typically a 1353NM server and an NE. The DCN connecting the 1353NM and the NE will carry IP packets. The NE and the 1353NM server need to support the OSI and IP protocols, the routers only need to support the IP protocol.
SH
IS-IS ES-IS CLNP
NE
IS-IS ES-IS CLNP
IP Packets
IP network
NE have to be compatible with this feature
5 Addressing NEs with IP tunnel: OSI over IP
Network example
1353NM CLNP GRE IP 802.2 Ethernet

IP network OSI over IP GNE OSI NE OSI OSI NE OSI over IP IP network GNE OSI NE OSI OSI network OSI GNE OSI NE
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. Warning: SH: max 32 tunnels per LAN I/F Tunnels give important processing load to terminating nodes Take care of L2 backbone design
5 Addressing NEs with IP tunnel : OSI over IP
NE Configuration Procedure
On the 1320 CT (Equipment view): 1. Start the supervision of the NE and Login 2. Choose the menu Configuration
(3)
Comm/Routing Configuration Configuration
Interfaces Ethernet
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 5. Click on Apply
(4)
(5)
NE Configuration Procedure [cont.]

Configuration Comm/Routing Tunneling Configuration OSI over IP 7. Set the Remote Destination IP Address to match the IP address of the
6. Choose the menu
1353NM server 8. Click on Apply
(7)
(8)
The IP address of the SH can be get by typing the command cat /etc/hosts in a UNIX terminal from 1353NM
1353 NM Configuration Procedure [cont.]

On the 1353NM : 1. From TMN-OSs Management window, select the 1353NM icon then Actions
1353NMAdmin
2. Select the menu
NE Administration and IP Tunneling
1353 NM Configuration Procedure [cont.]

3.
Click on Create to open the corresponding window and enter the previous NE IP Address (inserted in Ethernet Configuration), or select it from the GNE List, and give the IP Tunnel ID (from 0 to 31):
Enter IP Address or choose the GNE from the list Define the IP Tunnel ID
Confirm
Blank Page
158
Exercise
Create an IP tunnel between 1353NM and an NE
Blank Page
160
2 - 2 - 161
6 Distributing Maps
6 Distributing maps
Principle of distribution
DCN Master server

Map dB
DCN Presentation server

USM
Map dB
Local LocalMaps Maps
Local LocalMaps Maps
USM
Distribute map
Distributed Distributed Network NetworkMaps Maps IM IM(DNM (DNM- -IM) IM)
Get map
distribute map
IM
DNM-IM Maps
Get map
DCN
DNM: Distributed Network Map Distributed maps are accessible from any workstation. They are saved when the application is backed up.
6 Distributing maps
Saving as distributed maps

1. 2. 3. 4. 5. 6.
Open the local map Select File Save Map as Enter the Name of the distributed map Enter any useful comment Click OK After update, click Close
6 Distributing maps
Retrieving distributed maps

1. Create a new
map 2. Select File
Map Management
3. Select the map
from the "Map Tree" list 4. Click the Retrieve button 5. Click the Close button
6 Distributing maps
Locked maps
PNM USM
Local displayed map
DNM IM DNM map 1 map 2 map 3
PNM USM
Local displayed map
DNM IM DNM map 1 map 2 map 3 map 4 *
map 4
map 4
After "save as" or " retrieve"
6 Distributing maps
Unlocking distributed maps

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
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. 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 adviced that the map has been unlocked by user2 The map is marked as locked by user2
6 Distributing maps
Deleting a distributed map

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 4. Click the Close button
Blank Page
168
6 Distributing maps
Exercise
Distribute the map previously created Retrieve the map into a new local map
2 - 2 - 170
End of Module Network Topology
Section 3 System Operation

Module 1 NE Supervision

Blank Page
System Operation - NE Supervision 3-1-2
Objectives
supervise a Q3, 1850TSS-320 and SNMP Network Element
Objectives [cont.]
Table of Contents

1 2 3 4 5 Displaying NE Management and Alarm State Modifying the Management State of a NE Simulator Schedule a MIB Backup Backing-up/Restoring the MIB
Page 7 21 39 49 57

Page
System Operation - NE Supervision
3-1-7
1 Displaying NE Management and Alarm State
1 Displaying NE management and alarm state
Management states
Supervision state Communication state Administrative state (not managed) Usage state (not managed) Alignment state Local access state Operational state (not managed) Alarm status NML assignment state Simulator state (for Q3 NE only)
MIB alignment state for the Q3 NE: between the NE MIB and its representation in the simulator's database
Supervision state
SUP DECLARED
Starting supervision
DEACTIVATING
ACTIVATING
Stopping supervision
SUP SUPERVISED Transient states
Stable states
Supervision state declared: the NE is simply created in the OS MIB but is not supervised supervised: the NE is under supervision activating: supervision is being started (no management task can be performed on the NE) deactivating: supervision is being stopped (no management task can be performed on the NE)
Communication state
System Operation - NE Supervision 3 - 1 - 10
1353 NM
A 1353 NM has lost communication with the equipment
DISABLED
ENABLED
1353 NM The equipment can be reached from the 1353 NM
Communication state Disabled: The Communication between the OS and the NE is interrupted Enabled: The OS can communicate with the NE 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
Alignment state
Stable states Transient states
MIB
1353 NM
ALIGNED
ALIGNING UP
MIB
1353 NM
ALIGNING DOWN
MIB
1353 NM
AUDITING
MIB
1353 NM
MIB
1353 NM
MISALIGNED 1353 NM
MIB
Alignment state: 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 are down, the Communication state stays in Enabled 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 Aligning Up: The system is performing a MIB Align Upwards operation. No operation can be done on the NE Aligning Down: The system is performing a MIB Align Downwards operation. No operation can be done on the NE Auditing: The NE is under OS supervision and the system is comparing the NE MIB with its image in the OS 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. In Config: The NE is being configured and no alignment has been undertaken yet
Local access state

key
Craft terminal
The NE allows access from the craft terminal
GRANTED
Supervision Access State Local Supervision Access State OS
DENIED key
Craft terminal The NE refuses modifications from the craft terminal
Local access state granted: the local craft terminal can modify the configuration denied: no change is allowed with the local craft terminal Critical requested: the local craft terminal has asked permission to OS and is waiting for a response (granted or denied)
Alarm states
The alarm state indicates the most critical alarm present on the NE
Critical Major Minor Warning Active Pending Clear Indeterminate
Indeterminate: the severity level cannot be defined by the resources which raise the alarm Clear: no alarm
NML assignment state

It is accessible to the operator for reading only into the Equipment View: (MGR box) Gives information about the NE assignment to 2nd (EML) or 3rd (NML) level managers:
RM SY manager NPOS EML manager
Simulator state
SIM DISABLED DEACTIVATING ENABLED

Supervision Simulator Stop
(in the equipment view)
Supervision Simulator Start

(in the equipment view)
ACTIVATING
SIM Transient states

Concerns Q3 NEs only!
Stable states
Simulator state disabled enabled activating: (no management task can be performed on the NE) deactivating: (no management task can be performed on the NE) The availability of the simulator depends on the type and release of the NE
Displaying NE management and alarm state
Displaying NE states
Display NE management states

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

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

1. 2.
In equipment view, move the mouse over SIM icon Read simulator state on the bottom left of the window
Refreshing NE states
An automatic refresh is performed at regular intervals 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
Blank Page
System Operation - NE Supervision 3-1-
18
Exercise
Display states for an NE Display states for a group of NEs Refresh the states for an NE
Blank Page
20
3 - 1 - 21
2 Modifying the Management State of a NE
2 Modifying the management states of a NE
Q3 or QB3* NEs: Starting supervision

In the network topology view, select one or more sites and NEs 2. Select the menu Operations Supervision Align up or Align down
1.
For a Q3 NE, start supervision and upload NE MIB (whether Align up or Align down is selected)
3.
OS
Click on Apply in the Supervision window and wait for the result message to be displayed
4.
Click Close
SNMP or 1850TSS-320 MSPP NEs: Starting supervision

In the network topology view, select one or more sites and NEs 2. Select the menu Operations
1.
Supervision
No Alignment
3.
Click on Apply in the Supervision window and wait for the result message to be displayed
4.
Click Close
In case of 1850TSS-320 MSPP NE, during the Set NE Address phase only one of the two addresses belonging to the NE (Q3 or SNMP) 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.
How to ping an NE
If the supervision doesn't start, the good reflex is to ping the NE

From the Map view, select the relevant NE and issue:
Operations
Ping NE
How to ping an NE: 1850TSS-320 MSPP NE

From the Map view, select the relevant NE and issue:
Operations
Ping NE
The system pings both the management interfaces of the NE: Q3 and SNMP
The reachable interfaces are marked with a green bullet The non-reachable interfaces are marked with a red bullet
If one of the two interfaces is not reachable, the supervision is still started, but:
the NE alarm state is set to Critical the NE alignment state is set to Misaligned
If one of the two interfaces are not reachable, a NE not reach critical alarm is issued in the Alarm Surveillance Application
How to ping an NE: Communication test Tool

From the TMN-OS window, select Actions then NE Administration, then Ping NE: the Communication Test Tool will appear
1353NM Admin,
Display Filter
2. Ping selected NE(s)
1.Select the NE(s)
How to ping an NE Communication test Tool [Cont.]

3. Results
Stopping supervision
Stopping supervision:
stops management of the selected NE, deactivates alarm collection and configurations, retrieves collected PM data from NE before closing management session.
Stopping supervision [cont.]

1. In the network topology view, select one or more sites and NEs 2. Select the menu
Operations
Supervision
3. Click on
Stop Apply in the
Supervision window and wait for the result message to be displayed
4. Click
Close
Aborting supervision
Aborting supervision
stops management of the selected NE deactivates alarm collection and configurations NM immediately close the management session without collecting PM data from NE faster than "stop supervision
1. In the network topology view, select one or more sites and NEs 2. Select the menu 3. Click
Operations
Supervision
Abort Supervision
OK
Enabling/disabling NE operation access: Q3 and SNMP NE

Access granted
Configuration of the NE managed from a craft terminal only The OS continues to receive and process alarms and performance data The OS can switch back to the OS access state (access denied)
Access denied
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) Local (CT granted) or 3. Click OK 4. Wait for the Local Access icon in the equipment view to be updated:
Green colour for CT denied Light blue colour for CT granted
When a Host NE (OMSN containing ISA board(s) in its submap) is selected, the Local Access is managed simultaneously for the OMSN and the ISA board(s) at the same time. Nevertheless, it is always possible to manage them individually. 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
Enabling/disabling NE operation access: Q3 and SNMP NE [Cont.]

IN THE EQUIPMENT VIEW FROM 1353NM 1. Select the menu Supervision Access State OS (CT denied) or Local (CT granted) 2. Confirm by clicking OK 3. Wait for the Local Access icon in the equipment view to be updated:
IN THE EQUIPMENT VIEW FROM 1320CT 1. Select the menu Supervision Access State OS (CT denied) Requested or 2. Confirm by clicking OK (check OS isolation) 3. Wait for the Local Access icon in the equipment view to be updated:
Light blue colour for CT denied White colour during the checking of the OS isolation. After that, it turns green if the OS is isolated, light blue if it is reachable (i.e., when requested by the CT, the access status can become CT granted only if the OS is isolated)
Enabling/disabling NE operation access: 1850TSS-320 MSPP NE

Due to the dual management domain of the 1850TSS-320 MSPP NEs, the Access State management is separately applied to the Q3 or to the SNMP agent IN THE NETWORK TOPOLOGY VIEW: 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) Local (CT granted) or 3. Click OK 4. Wait for the Local Access icon in the equipment view to be updated:
Enabling/disabling NE operation access: 1850TSS-320 MSPP NE [Cont.]

IN THE EQUIPMENT VIEW FROM 1353NM Q3 management domain: 1. Select the menu Supervision Access State OS (CT denied) or Local (CT granted) 2. Confirm by clicking OK 3. Wait for the Local Access icon in the equipment view to be updated:
SNMP management domain: 1. Select the PP20G card (data processor), Select the menu
Equipment
2.
Data Board Navigation
From the Data Management window, Select the menu
Access State OS (CT denied) or Granted (CT granted) 3. Wait for the Local Access icon in the equipment view to be updated: (same behaviour as for the Q3 management domain)
Supervision
Enabling/disabling NE operation access: 1850TSS-320 MSPP NE [Cont.]

IN THE EQUIPMENT VIEW FROM 1320CT Q3 management domain: 1. Select the menu Supervision Access State OS (CT denied) or Requested 2. Confirm by clicking OK (check OS isolation) 3. Wait for the Local Access icon in the equipment view to be updated:
Light blue colour for CT denied White colour during the checking of the OS isolation. After that, it turns green if the OS is isolated, light blue if it is reachable (i.e., when requested by the CT, the access status can become CT granted only if the OS is isolated)
SNMP management domain: 1. Select the PP20G card (data processor), Select the menu
Equipment
2.
Data Board Navigation
From the Data Management window, Select the menu
Access State OS (CT denied) Requested or 3. Wait for the Local Access icon in the equipment view to be updated: (same behaviour as for the Q3 management domain)
Supervision
Blank Page
36
Exercise
Start supervision of a Q3 or SNMP NE by alignment up Allow local access to this NE Stop supervision on this NE Start supervision of a 1850TSS-320 MSPP NE Allow local access to the Q3 agent of this NE Allow local access to the SNMP agent of this NE Stop supervision on this NE
Blank Page
38
3 - 1 - 39
3 Simulator
3 NE simulator
Principles
RM
TSD-IM PNM PNM PNM-IM Q3 EML-IM
BD BD USM USM USM USM TSD-IM AS DB DB AS-IM
TSD-IM
NEs IDs
NE NE simulator simulator DB DB
ST
ED T AR
TSD-IM
NE NE
DB DB
3 NE simulator
Principles [cont.]
Work on an NE or on the NE simulator, but never on both The NE simulator is used in cases of :
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 backup).
off-line configuration restoration of the NE MIB
The simulator can be started only if the NE is in the "OS isolation" state
The NE simulator is 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.
3 NE simulator
Simulator and MIBs

1353NM Simulator simulator MIB
Simulator Align up
NE Q3
Simulator Align down

Not active MIB
active MIB
activate
In default configuration, the Simulator can be started only once at a time on a given 1353NM
Align up Activate
menu Supervision
Simulator Simulator Simulator
Align up Align down Activate
Align down menu Supervision

menu Supervision
3 NE simulator
Loading the simulator with a configuration

IN THE EQUIPMENT VIEW Align the configuration of the real NE with the simulator menu : Supervision Simulator Align up
3 NE simulator
Configuration off-line
Load NE configuration in the simulator (Note 1) 2. Stop supervision of NE (Note 2)

1.
FOR A NOT SUPERVISED EQUIPMENT VIEW:

Start the simulator, menu : Supervision Modify the configuration 5. Stop the simulator, menu : Supervision
3. 4.
Simulator Simulator
Start Stop
Start supervision (changes done in the simulator don't appear) 7. Align the simulator's MIB down to the NE,
6.
menu : Supervision
8.
Simulator
Align down
Activate the new configuration

menu : Supervision Simulator Activate wait for communication to be re-established following "OS Isolation"
Note 1 Steps #1 and #2 have to be done when the NE is already supervised. If the NE cannot be supervised, start from step #3. In this last case, steps #6 up to #8 will be done as soon as possible. Note 2 Caution: If you stop the equipment supervision in order to use the simulator, note that the OS isolation state switch will occur after a few minutes.
3 NE simulator
Off-line browsing
FOR A SUPERVISED EQUIPMENT VIEW in OS ISOLATION state:

1. Start the simulator, menu : Supervision 2. Display the configuration
Simulator
Start
last known configuration last NE alarm state

3. Stop the simulator, menu : Supervision
Simulator
Stop
Blank Page
46
3 NE simulator
Exercise
Display the on board simulator state window Align up the supervised NE in the simulator Activate the off-line configuration Add a board Restart NE supervision and activate the modifications made in the simulator Restore the NE's original configuration
Blank Page
48
3 - 1 - 49
4 Schedule a MIB Backup
.4 Schedule a MIB backup
Schedule a MIB backup

1. From network view: 2.
Operations FT Scheduler Select Job New
The FT Scheduler can also be started from: TMN-OS Window: issue Actions
1353NM Admin
NE Administration
FT Scheduler
The FT Scheduler updates the MIB configuration in the simulator. In order to restore a MIB backed-up with the FT scheduler, the Simulator must be issued to the NE.
Align down command
Therefore, scheduling a MIB backup makes sense only for those NEs that support the simulator. If the NE doesnt support the simulator, the MIB backup can be scheduled, but then there is no way to restore it
4 Schedule a MIB backup
Schedule a MIB backup [cont.]

3. Enter a "Job name" and "information

(optional)
5
4. Click on the right arrow and answer "yes" to the question "A job may be for SWDL or backup. Do you want a backup Job ?" 5. Set activation date and time
Schedule a MIB backup [cont.]

6. Select the backup
session then click on the right arrow to create a NE 7. Select the NE and enter NE details for MIB backup 8. If required, select the parameter "misalignment flag" 9. Save your job with the "save" button 10. Submit your job with the "submit" button 11. Click on yes if you want to see the status of the running job
10
11
In the Save as window, write the job name in the bottom line
The parameter "misalignment flag is used to avoid the NE Configuration upload towards the Simulator when the two entities are already aligned.
Monitor MIB backup schedule

To see the status of the running job, the user can also select menu Job Show backup running job on the File Transfer Scheduler
To see the result of backup, select menu Job View backup report
Blank Page
54
How to do it
Schedule a MIB backup for two NEs
Exercise
Schedule a MIB backup for one NE Display the status while job is running Display the report
3 - 1 - 57
5 Backing-up/Restoring the MIB
5 Backing up/Restoring the MIB
Principle
Warning : THIS FUNCTION IS AVAILABLE ONLY FOR Q3 AND SNMP EQUIPMENTS WHICH HAVE NO SIMULATOR INTO THE 1353NM SYSTEM.
1353NM
modification
file
backup
restore
NE Q3
active MIB
Not active activate MIB

With Q3 NE, modifications from 1353NM (or 1320CT) are performed directly on the NE MIB. The backup can be performed before any change to the NE, so that the previous configuration can be restored quickly.
Backing up the configuration

Q3 and 1850TSS-320 MSPP NEs:

1. In Equipment view, select the menu
Download
3. Click
MIB management
2. Enter a name for the backup
Backup and confirm with OK
wait for the message
backup successfully completed!

to be displayed
SNMP NEs:
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
Restoring the configuration

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 to be displayed
Restore completed
4. Click Activate and confirm
SNMP NEs:
How to do it
How to perform a backup and a restore
Exercise
Perform a backup Modify an element of the configuration (for example, add a board) Perform a restore Check that the change made previously has been overwritten by rewriting
Blank Page
63
3 - 1 - 64
End of Module NE Supervision
Section 3 System Operation

Module 2 NE Management

Blank Page
System Operation - NE Management 3-2-2
Objectives
perform the basic management operations on Q3, 1850TSS MSPP and SNMP NE
Objectives [cont.]
Table of Contents

1 2 3 4 5 6 NE Time Management from the 1353NM Performing a Remote Inventory Resetting a NE Downloading Software to the NE List Abnormal Conditions Event Log Archiving
Page 7 13 23 27 47 53

System Operation - NE Management
3-2-7
1 NE Time Management from the 1353NM
1 NE time management from the 1353NM
NE and OS date and time

The system realigns the time of all the NEs supervised by default every 24 hours. The NE's local time can be displayed and/or configured. Open the equipment view of a NE. 2. Select the menu Configuration
1.
NE Time
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"
3.
Getting the NE time

This action is used by an user to display time and date of a number of NEs.
In the network view, select the relevant NEs 2. Select: Operations Time
1.
Get
3.
Click Apply "Working" (until the response from the NE to the GET request has been received) NE date and time (when the response from the NE has been received (and is correct)
For each NE, a message is displayed:
This operation is allowed only if the NE is under supervision, its access state is DENIED and its operational state is ENABLED.
Setting NE time
System Operation - NE Management 3 - 2 - 10
You use this action to send the OS time and date to a number of NEs.
1. 2. 3.
In the network view, select the relevant NEs Select the menu: Operations Time Set Click OK
Each selected NE sends a response to the setting request

Date and time values if the request has been executed correctly. Processing failure with args, if a problem has occurred.
If the NE has the NTP protocol enabled, the Set time procedure from NM will fail
Exercise
Set the time (on the OS time) for an NE Display the time of the NEs in a domain Set the time (on the OS time) for a selection of NEs on the map
Blank Page
System Operation - NE Management 3-2-
12
3 - 2 - 13
2 Performing a Remote Inventory
2 Performing a remote inventory
Remote Inventory content

ALCATEL company Identifier Mnemonic of the R.U. Unit part number Software part number CLEI code Factory number Unit serial number Date identifier Date R.U. inventory field for the customer
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 standardised: 00 manufacturing date which corresponds to the end of the test phase 01 date of the manufacturing order 02 date of manufacturing R .U. lot 03 date of customer delivery 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.
For the NE whole subrack

To perform this remote inventory

From PNM, select the NE 2. Select menu Operations
1.
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
This action can also be undertake from equipment view 1) In equipment view, select menu Supervision 2) Wait for completion message 3) To display the result, select menu Diagnosis
Upload Remote Inventory View Remote Inventory
For a single NE board: Q3 or 1850TSS-320 MSPP NE

To perform this remote inventory

1. 2.
In equipment view, select a board in the NE Select menu Equipment Remote Inventory
Board Level
For a single NE board: SNMP NE

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. Choice printer or file for the output 4. If you choose file, select the destination file and data format 5. Click
OK
This operation is not possible in case of SNMP NE
Remote inventory on the whole network

To perform this Remote Inventory from PNM

1. Select
Operations Remote Inventory Wizard
2. Select the relevant NE(s) 3. Click on the magic wand to
upload the R.I.

4. Click on Search RI button
2
This function allows to search for boards of a given type deployed in the network
Remote inventory on the whole network [cont.]

6. Enter the Unit type or part number
7. Search
5. Optionally, enter the NE Family and/or NE Type Clicking on the arrow opens the USM view of the relevant equipment 7. Results are displayed in this area
8. Close
Exercise
Perform a NE subrack remote inventory from the MAP Perform a remote inventory for a board Search for a given board in the network (for example CONGI)
Blank Page
22
3 - 2 - 23
3 Resetting a NE
3 Resetting a NE
3 - 2 - 24
An NE reset may be necessary in certain failure situations. This operation resets, shuts down and restarts all the processes currently running on the NE Traffic is unaffected.
1. Open the NE's equipment view. 2. Select the menu:
Supervision
Restart NE
3. Communication between the NE and the OS is lost for a few minutes.
3 Resetting a NE
Exercise
Perform an NE reset
Blank Page
26
3 - 2 - 27
4 Downloading Software to the NE
4 Downloading software to the NE
Set server name (Q3 and 1850TSS-320 MSPP NEs)

1. In
EMLUSM, select the menu
Download Server management... 2. Select "local (local server is being automatically chosen) 3. Click "Close"
Set server name (SNMP NEs)

Downloading (Q3 NEs)

1. In
Download Init download 2. Select the SW Release to be downloaded 3. Click "OK" and confirm the download wait for the message "Software download completed!" to appear in
the download window.
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)
Downloading (1850TSS-320 MSPP NEs)

1. In
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 wait for the message "Software download completed!" to
appear in the download window.
Downloading (SNMP NEs)

Activating the new software (Q3 NEs)

1.
In EMLUSM, select the menu

Download Units info...
SW Release installed
2.
Select the new software tab (Standby) In the action pull-down menu, select
"Activate"
3.
Click "OK" and confirm

wait for Q3 communication to be re-established (it may be necessary to restart EMLUSM)
Activating the new software (1850TSS-320 MSPP NEs)

1.
In EMLUSM, select the menu

Download Units info...
SW Release installed
2.
Select the new software tab (Standby) In the action pull-down menu, select
"Activate"
3.
Click "OK" and confirm

wait for Q3 communication to be re-established (it may be necessary to restart EMLUSM)
Activating the new software (SNMP NEs)

.4 Downloading software to the NE
Schedule a SW Download
1. From network view: 2.
Operations FT Scheduler Select Job New
The FT Scheduler can also be started from: TMN-OS Window: issue Actions
1353NM Admin
NE Administration
FT Scheduler
Schedule a SW Download [cont.]

3. Enter a "Job name" and "information

(optional)
5
4. Click on the right arrow and 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

6. Select the session then
click on the right arrow to create a NE 7. Select the NE 8. Optionally, select the server hosting the SW 9. Select the SW package to download 10. Save your job with the "save" button 11. Submit your job with the "submit" button 12. Click on yes if you want to see the status of the running job
10 11 12
In the Save as window, write the job name in the bottom line
The parameter "misalignment flag is used to avoid the NE Configuration upload towards the Simulator when the two entities are already aligned.

When dealing with a 1850TSS-320 NE, at step 9 the operator must also choose the Package Type among:
1850TSS320D (Full Data Configuration) 1850TSS320M (MSPP Configuration) 1850TSS320T (PTRP Configuration)
Monitor SW Download schedule

To see the status of the running job, the user can also select menu Job Show SWDL running job on the File Transfer Scheduler
To see the result of backup, select menu Job View SWDL report
Stop a running job

The user can stop a scheduled SW download on a single NE or on a group of NEs. 1. Select the relevant NE(s) 2. Click on Abort 3. Confirm clicking on Yes
See the SW status of the managed NEs

In order to see the SW status of the managed NEs: 1. on the File Transfer Scheduler, issue the menu SW Status 2. select the NE by:
NE Type NE Name All NEs
The list of NE SW status can be exported in a text file
See the SW status of the managed NEs: details

To get SW status details or to perform actions, double click on the desired NE
Click here to get SW status details
Select the action and then Apply Action

Blank Page
44
Exercise
Download software to the NE CAUTION: the download may take some time
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)
Blank Page
46
3 - 2 - 47
5 List Abnormal Conditions
5 List Abnormal conditions
List NEs in abnormal condition

1.Select AC viewer from PMN 2.Eventually select the involved NE(s) Refresh the NE list in the window
3.Navigate using USM on the selected NE
AC information are retrieved from EMLIM every 15 minutes Automatic refreshment period can be set-up from menu Option
Set Automatic refresh
Display abnormal condition list for one NE (Q3 and 1850TSS-320 MSPP)
1. Open 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 in the USM view with the corresponding AC.
Display abnormal condition list for one NE (SNMP NE)

Exercise
Create an AC on a NE (for example a loop) Display NEs in Abnormal condition status Display the list of AC for this NE Suppress the AC
Blank Page
52
3 - 2 - 53
6 Event Log Archiving
Q3 Event Log Browsing

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:
Diagnosis Log Browsing Event Log
Q3 Event Log Browsing [cont.]

The event records can be filtered by the user per type and time:
Q3 Event Log Browsing [cont.]

Example of Event Log Display window
Q3 and SNMP NE Event Log Archiving

The NE Event Log is not persistent after a NE restart The 1353NM gives the possibility to save on a persistent file the Q3 and the SNMP Events selected by the operator. 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
The administrator can then manage the Event Log File to produce a text file with event fields translated like ELB application.
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.
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 4. Enable Filter and confirm clicking Yes in the confirmation window 5. Cancel to close the window
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
3 - 2 - 60
End of Module NE Management
Section 4 Maintenance Applications

Module 1 Alarm Management

Blank Page
Maintenance Applications - Alarm Management 4-1-2
Objectives
handle the AS application for current alarms and the alarm history
Objectives [cont.]
Table of Contents

1 2 3 4 5 6 7 Displaying Current Alarms Alarm Debouncing Creating, Modifying and Deleting an Alarm Sublist Performing Actions on Current Alarms Displaying the Alarm History Handling the AS Facilities Administrating the AS
Page 7 19 27 39 47 57 67

Page
Maintenance Applications - Alarm Management
4-1-7
1 Displaying Current Alarms
1 Displaying current alarms
AS principles
Real Time Management
Static analysis
Display alarms
Manage alarms Archive alarms
Display alarms
Current alarms
Raise and clear alarms
Archived alarms
Alarm surveillance
Network resources
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)
Current alarms and alarm history

Current alarms:
"live" alarms (permanently refreshed)
Alarm history:
cleared AND acknowledged alarms alarms purged by operators (even non-cleared alarms) overflow of the current alarm list
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 his network.
Starting AS
Maintenance Applications - Alarm Management 4 - 1 - 10
Select the "alarm" icon in the list of applications or Alarms in Action menu.
OR
Inactive sublists have all their counters set to x To activate a sublist: select the sublist select menu
Sublist --> Activate
Starting AS
Select the "alarm" icon in the list of applications Flag to indicate new alarms in the sublist
Specific counter of cleared alarms

Different levels of information

Starting point of AS
alarms
Operator request Alarm sublist More information
Counter summary
Actual network
Global vision
Local vision
Detailed vision Increasing detail
Displaying a sublist
Select a sublist in the "counter summary" window Double click on it OR select Sublist Open
Displaying more information

Select an alarm in the sublist Double click on it OR select Display
More Info...
Other info are being displayed selecting the other menu
Monitoring new alarms

This function automatically displays the AS window when a new alarm appears. 1. Start AS Current USM 2. Activate the "auto-raise" function check the option in the menu Display Auto-Raise 3. Minimise the window
Blank Page
Maintenance Applications - Alarm Management 4-1-
16
How to do it
How to navigate within the AS
Exercise
Start the AS application Display a sublist containing alarms Display more information on a given alarm
4 - 1 - 19
2 Alarm Debouncing
2 Alarm Debouncing
Principles
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. 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 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. Alarm debouncing reduce the number of records stored/displayed in the AS CAL and the related traffic to upper managers (1354RM, 1354BM etc)
2 Alarm Debouncing
Principles [cont.]
Alarm Raise Event
Alarm Clear Event
Alarm ON Alarm OFF T1 T2 T3 T4 T5 T6
Resource Name XXXX XXXX XXXX
Probable Cause YYYY YYYY YYYY
Event Time T1 T3 T5
Clear Time T2 T4 T6
Repetition Counters 0 0 0
To End-Customers, T1-T6 is the faulty period as a whole, in which the resource is not able to support a given function
Debouncing ON
Event Time T1 Clear Time T6 Repetition Counters 2
NO Debouncing
Resource Name XXXX
Probable Cause YYYY
The Feature applies to alarms notified by Q3 and SNMP agents
2 Alarm Debouncing
Architecture Overview
The Feature applies to alarms notified by Q3 and SNMP agents
2 Alarm Debouncing
How to configure
1. Select Actions Alarm Debouncing
Alarm Debouncing GUI
2. Select the Probable Cause
3. Select and configure the Hold Period
4. Click on Apply
5. Save and Exit
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
2 Alarm Debouncing
Alarm Debouncing Case

Raise
T1 Raise Clear
T1
T2
T1
T2
T3
r01/sr1/sl33
Bouncing Alarm
2 Alarm Debouncing
Alarm Debouncing Case [cont.]

T1
T2 T3 T4
T1 T2 T3 T4 T5
r01/sr1/sl33
Bouncing Alarm
2 Alarm Debouncing
Alarm Debouncing Case

T1 T2 T3 T4 T5 T6
T1 T2 T3 T4 T5 T6 Hold Period expiration
r01/sr1/sl33
Bouncing Alarm
4 - 1 - 27
3 Creating, Modifying and Deleting an Alarm Sublist
3 Creating, modifying and deleting an alarm sublist
Create or modify a sublist

To create an alarm sublist, select Sublist Create To modify it, select Sublist Modify and "Sublist Properties" window is being displayed
Create or modify a sublist

This window is made up of several Items :

DISPLAY FILTER SORT TRIGGER parameter to identify the sublist appearance to select alarms to display in the sublist sort criteria for the alarms in the sublist actions to be taken in case of an alarm
Sublist DISPLAY parameters

Sublist name
Sublist colour (single click to modify)
Other available attributes (to move to the displayed attributes list, select and click on the arrow)
Click here to apply the modifications

To hide
Currently displayed attributes in the sublist (select and click on the arrow to remove from the list)
Sublist FILTER parameters - Basic

To save your filter To select a saved filter
Sublist FILTER parameters - Basic

Filter by date and time
Filter by status attribute
Filter by severity
Filter by alarm type Filter by correlation parameter

Filter by probable cause (click on "Select... to make your choice)

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
Sublist FILTER parameters - Advanced

Select Instance to filter a specific Management System as alarm source Select to filter by Specific Problem Select to filter by Status Select to filter by TT assignement Select to filter by Repetition Counter value
Sublist SORT parameters

To select a saved sort
To save your sort choice Parameters used to sort the sublist
Parameters not used to sort the sublist (select and click on the arrow to use one)
Click here to select the sorting order (increment or decrement)
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 To execute a script if the number of alarms in the sublist is smaller than a given value
By executing the script you could, for example, load a particular process as soon as the number of critical alarms exceeds a certain value.
How to do it
How to create a sublist How to set a filter
Exercise
Create a sublist Choose a name and a colour for your sublist Set the filter to select only:
cleared alarms unacknowledged alarms alarms in the last 24 hours
Sort the sublist by event date & time and severity Set the sublist parameters to emit a tone for incoming alarms
4 - 1 - 39
4 Performing Actions on Current Alarms
4 Performing actions on current alarms
Reserving / unreserving an alarm

Reservation ensures that you are the only operator responsible for an alarm To reserve:
open a sublist select an alarm select Action
Reserve
To unreserve:
open a sublist select the reserved alarm select Action Unreserve
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 initially reserved it.
Generating trouble tickets

Trouble ticket = collection of all information about one problem Open a sublist Select a single alarm or a group of alarms Select Action Trouble Ticket... Confirm indicator in the sublist change to YES
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 customised 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. greyed).
Acknowledging
By acknowledging alarms, you indicate that they have been registered. Open a sublist Select one or a group of alarms Select Action Acknowledge
the state changes from NACK (Non ACKnowledge) to ACK (ACKnowledge)
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.
Manual purge
Open a sublist Select one alarm or a group of alarms Select Action Manual Purge
Purged alarms disappear from the current alarms list and are now archived, if they match the archiving filter.
Blank Page
44
Exercise
Reserve an alarm Try to unreserve an alarm reserved by an other user Unreserve the previously reserved alarm If ARS is active generate a trouble ticket for an alarm Acknowledge a cleared alarm (note the effect on the sublist) Acknowledge an not cleared alarm (note the effect on the sublist) Unreserve the previously reserved alarm Purge alarms (cleared, not cleared, acknowledged, non acknowledged)
Blank Page
46
4 - 1 - 47
5 Displaying the Alarm History
5 Displaying the alarm history
Description
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):
auto-purging manual purging overflow acknowledged and cleared alarms synchronisation
Auto-purging these alarms have never been inserted in the Current Alarm List (CAL). Manual purging an AS operator has manually removed one or more selected alarms from the CAL. Overflow Maximum size of the CAL has been reached and alarms are removed from it Synchronisation Alarms that are not confirmed on a synchronisation command are automatically cleared by the application. Among them, those which were previously acknowledged are forwarded to the HAL
Principle
CAL or auto purge filter

Archiving filter HAL (HP LOG) filter HAL (Public Archive) filter Sublist Main list
Automatic Operator action
filter User file User file User file
Save selection
User file
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.
Starting up
In the Current Alarm List, select Navigation A window opens with an empty list
Archive >> confirm
Retrieve alarms
1. Retrieve the alarm list with 2. Set the filter parameters
Archive
OR
Retrieve from Public Archive... Retrieve from User Files...
3. Click "Apply : the historical alarm list (HAL) is displayed
Retrieve alarms [cont.]

The main operations on archived sublists are performed in the same way as for current alarms.
Saving alarms to a user file

SAVE
Open a sublist of the HAL Select one or a group of alarms Select Action Save As Enter a file name
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.
Removing an archived user file

REMOVE
From the "counter summary", window, select Archive
Remove User
Files...
Select the file to remove and move it to "selected user files" list by clicking on the arrow Click "OK"
To select
To unselect
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.
Exercise
Start the Historical Alarm List Retrieve the alarms from public archive Look for the alarms purged in the previous exercise and find the insertion cause Create a sublist (e.g. with Manual purge as Insertion cause) Create a user file with a selection of alarms from the sublist Close and restart the Historical Alarm List
Exercise [cont.]
Retrieve the alarms from your user file and check that it is the same list Remove your user file
4 - 1 - 57
6 Handling the AS Facilities
6 Handling the AS facilities
Navigating from AS to PNM

To view the Network Element having generated an alarm 1. Select an alarm from the sublist 2. Select Navigation Topology Manager
A PNM window opens displaying the submap of the Network Element generating the alarm
Navigating from AS to an external application

You can navigate to an external application of your choice 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
Autodiscovery Alarm
An autodiscovery alarm is generated whenever a NE in the managed network sends to the 1353NM an autodiscovery notification. See the Module Network Topology in the Section Graphical Interface for details
1. Select a NE autodiscovery alarm 2. Select External Application CreateNe

3. The Create NE GUI is opened
Exporting alarms to a printer or text file

You can export a whole sublist or a selection of alarms

1. Open the sublist 2. Select the relevant alarms 3. Select
Action
Output
an "output" window opens TO PRINT Select the "print" button Click "OK"
Exporting alarms to a printer or text file [cont.]

You can export a selection of alarms (the selection may include all the alarms contained in the sublist) TO CREATE A TEXT FILE Select the "Export" button Choose "select" and enter a file name Click "OK"
Obtaining a report on an action

It allows you to view a report giving detailed information on the progress or execution (successful or not) of an operator action. In the "Counter summary" window, select
Navigation
Report
Status column
the following window is displayed
Report detail
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. 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 Synchronise Application Possible status of the operation In Progress (Indeterminate severity level colour): the request is ongoing. Aborted (Minor severity level colour): the request has not been sent. Failure (Critical severity level colour): request failed. Success (Cleared severity level colour): request succeeded. Half Success (Major severity level colour): the request has partially succeeded. In this case, read the report details to find out what failed in the request.
Clearing or deleting a report on a performed action

Clear the whole report list

Clear Delete reports for some selected actions
Open the report window Select the reports to be deleted from the list Select menu Report Delete... Open the report window Select menu Report
Exercise
Navigation:
Open a sublist Select an alarm Start PNM with the AS facility
Print out a set of alarms with the export facility Display the reports on the actions performed
Blank Page
66
4 - 1 - 67
7 Administrating the AS
Advanced feature mechanisms and alarm flow

Because of the Current Alarms List has a limited size, the operator is provided with several advanced features for solving capacity overflow problems The default size of the CAL is 10000 alarms. It can be changed by the operator in the CAL Administration window (see next slides)
Trouble Ticket filter

ARS
Archive filter
CAL
HAL
Auto-Ack filter AutoPurge filter
Alarm NE
delete
CAL size The operator can assign the percentage fill level at which a warning is emitted. The operator can also specify the behaviour of the CAL when the overflow occurs (wrap/halt). 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 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 According to the filter criteria, the operator may decide to acknowledge some alarms automatically when they enter the CAL. Automatic trouble ticket creation 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 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. Synchronisation Because the CAL, for any reason, may become out of step with the network alarms situation, the operator can provoke a synchronisation mechanism which performs a global refresh of the CAL checking all the resources involved.
Configuring the AS
In the "counter summary" window, select
Option Administration 1353NM-7.4

There are five pages
CAL Administration Archiving filter Auto-Purge Auto-Trouble Ticket Auto-Acknowledge
CAL Administration To view the size of the Current Alarm List, and to customise 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
Configuring the AS [cont.]

You can set a filter for:

Archiving filter Auto-Purge Auto-Trouble Ticket Auto-Acknowledge
Refer to the previous chapter to learn how to set the filter
Exercise
Set Overflow action mode to wrap and purge size to 20 Filter

Change the auto-purge filter to archive MINOR alarms automatically Create a minor alarm on an NE Check that the alarm is sent directly to the historical alarm list Reset the filter to Match-none
4 - 1 - 72
End of Module Alarm Management
Section 4 Maintenance Applications

Module 2 Performance Management

Blank Page
Maintenance Applications - Performance Management 4-2-2
Objectives
manage the transmission quality records
Objectives [cont.]
Table of Contents

1 2 3 4 Definition of Counters Configuring Performance Points Displaying Performance Data Performance Reports
Page 7 19 27 33

Maintenance Applications - Performance Management
4-2-7
1 Definition of Counters
1 Definition of counters
Introduction to SDH performance monitoring

Principles:
Based on counting errored BIP bytes.
Byte B1: BIP8 (RSOH) Byte B2: BIP24 (MSOH of an STM1 rate) Byte B3: BIP8 (VC4 POH) Byte V5: BIP2 (VC12)
1. Calculates the BIPs (on frame transmission)
Time N+3 N+2

BIP
N+1
BIP
Introduction to SDH performance monitoring [cont.]

2. Comparison of BIPs (on frame reception)
Time N+3 N+2 Extraction N+1 N BIP computation COMPARE INCREMENT COUNTERS

Maintenance Applications - Performance Management 4 - 2 - 10
Far End (Node A)

V C 1 2 V C 1 2 V C 4 V C 4 M S O H M S O H R S O H R S O H
Near End (Node B)

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

The performance counters are linked to TPs to count transmission errors. The operator can initiate performance monitoring on one or more subsets of counters for each TP. Data is collected automatically and periodically by the OS. The main performance management functions are:
configuring the counting period (15 min and/or 24 hours) for each of the NE's performance points, configuring quality thresholds, collecting performance data, displaying performance data.
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 The thresholds can be defined separately for 15 minute and 24 hour counters. If threshold values are exceeded for a TP, a Threshold Crossing Alarm (TCA) is generated by the NE.
Managed SDH performance counters (local)

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

FEBBE FEBC FEBE FECSES FEES FESES FEUAS
Far End Background Block Error Far End Block Error Count Far End Block Error Far End Consecutive Severely Errored Second Far End Errored Second Far End Severely Errored Second Far End UnAvailable Second
FEBBE Far end BBE FEBC Identifies, on a terminal, the number of errored blocks counted within a second, received by the far end terminal FEBE Far end EB FECSES Far end CSES FEES Far end ES FESES Far end SES FEUAS Far end UAS
Managed SDH performance counters (other)

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

On WDM equipment, some transponder boards also support PM at FEC layer:

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

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

TRCO: TRCF: TTO: TTF: TDF: TRSEF:
Total Received Correct Octects: total number of octets of Ethernet frames received correctly by the Virtual Ethernet Interface, including Ethernet header characters Total Received Correct Frames: total number of Ethernet frames received correctly by the Virtual Ethernet Interface Total Transmitted Octects: total number of octets of Ethernet frames transmitted out by the Virtual Ethernet Interface, including Ethernet header characters Total Transmitted Frames: total number of Ethernet frames transmitted out by the Virtual Ethernet Interface Total Discarded Frames: total number of Ethernet frames which were chosen to be discarded bue to buffer congestion Total Received Service Errored Frames: total number of Ethernet frames received uncorrectly by the Virtual Ethernet Interface
Counters are sampled with 1h (or 15 min, see notes) and 24h granularity period All counters are free-running: this means that they are not reset at the end of the sampling period. This lead easily to an unfriendly GUI representation. For this reason, reports on Ethernet counters are available in 1353NM showing deltas with respect to the previous measurement.
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. either15min or 1h). For these kinds of board, 1353NM support the two granularity type, with the following configuration notes and constraints: 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): EMLIMs then set 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 board 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 When the supervision is started by the 1353NM on a ISA-ES with a different monitoring granularity period, the PM points of then NE all switch to the granularity configured in the 1353NM
Analog performance monitoring

1620LM Rel 2.2 and 1626LM Rel 3.0 DWDM equipment support the monitoring of analog values. Basically, the Analog PM involves all the measurements available by the NE USM by the choice Equipment (or Board) Istantaneous Measurements; these include:
Tx Optical Power Level Rx Optical Power Level Bias Current Level Temperature Etc. For boards such as TRBD/TRBC/MCC30/SFP/BMDX/CMDX/LOFA/ALCT
1353NM is in charge to sample and store input/output power values in the PM DB. The user can then select Monitoring Points for Report generation (Table Chart) The sampling periods are 15m & 24h
4 - 2 - 19
2 Configuring Performance Points
2 Configuring performance points
Configuring thresholds
Open an equipment view Select the menu:
Configuration Performance Threshold Tables

In this window, you can perform the following operations on a thresholds table
create modify display delete 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
N.B.: In this Chapter only the configuration of SDH performance points and Analog PMare 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.
Configuring threshold tables

1. Enter the 2. 3. 4. 5. 6.
table name (creation
7.
only) (a number!) Select granularity (creation only) Define the upper threshold value Define the lower threshold value Select the alarm severity Disable "send notification" if no message is to be sent on a threshold crossing Click apply
Section / Path type STM16 - RS STM16 MS STM1 RS STM1 MS VC4 VC3 VC12
Block size (bits) 311040 801 19440 801 18792(261x9x8) 6120 1120
Blocks per frame 1 384 1 24 1 1 0,25
Blocks per second 8000 3072000 8000 192000 8000 8000 2000
BIP type BIP 8 BIP 384 BIP 8 BIP 24 BIP - 8 BIP - 8 BIP - 2
Example
Granuality: 15 minutes STM1 - RS Counters Low Threshold / BER BBE 58 ( ~ 10-9) ES 50 STMn For STM4, BBE values must be multiplexed by 4 For STM16, BBE values must be multiplexed by 16
High Treshold / BER 5790 (~ 10-7) 150
Gruanuality: 24 hours For 24 hours period, values must be multiplexed by 4* 24
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 4. 5. 6. 7. 8.
Port Performance Configure Performance Monitoring Select a POM/SUT (if required) Define the parameters Mode, EML OS Monitoring and Notifications Choose a proper Threshold table and Attach it Click Apply Click on "set ASAP " if you want to configure
ASAP 9. Click Apply Repeat steps 5 to 9 for all other POM/SUT 10. Click the Close button
POM: Path Overhead Monitoring SUT: Supervise Unequipped Termination Mode data collection: Select this button to enable performance monitoring create history data: If this option is selected, history data is collected in the entity selected for the corresponding TP 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 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 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, threshold violation of each counter is indicated. Threshold table 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). Click the Attach... button to open the window for selecting the threshold table, PM Threshold Table Select, and configure the threshold table. Select the Remove button to separate the threshold table from the entity.
How to set Analog PM in NE USM

Open the equipment view Select Configuration Analog PM Configuration

On Equipment
for configuring the Analog PM on all the equipment (the following window will open)
On selected object
for configuring the Analog PM on the single selected board
How to set Analog PM in NE USM

Start the PM by selecting Start in the PM action column for the 15 or the 24h If the data must be sent to the 1353NM, the Archiving cell must be set to Yes Click on Apply after setting the desired configuration
Exercise
Display a threshold configuration table and note down the parameters Create a new threshold configuration table, using the previous pointers as an example Start performance monitoring for two TPs (15-minute counter)
Blank Page
Maintenance Applications - Performance Management 4-2-
26
4 - 2 - 27
3 Displaying Performance Data
3 Displaying performance data
Displaying performance data for single TP

From the Equipment view : 1. Display the port view of a board 2. Select a suitable TP 3. Select the menu Port
Performance Data
Display Current POM/SUT
4. Select the necessary
(in case of AU4 CTP or TU-n CTP) 5. Select the required granularity Click Refresh to update the window data
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.
Displaying the performance data history for single TP

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 the required
POM/SUT (in case of AU4 CTP or TUx CTP) 5. Select the required granularity
Click Refresh to update the window data
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 counter; the number of data items is three maximum for 24 hour entities. 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.
Blank Page
30
Exercise
Display the current performance data for the TPs started on the last exercise Test the Refresh and Reset button Display the performance data history
Blank Page
32
4 - 2 - 33
4 Performance Reports
Navigation in performance data views

4 ways to get the RRC window

1
3 2
4 ways to get the generated report 1. 2. 3. 4. Screen Mail File Printer
Menu in PNM USM
Menu in EML USM

4 ways to get the Report Request Control window:

1. from TMN OSs window, click on the relevant icon 2. from PNM USM, Tool
Diagnose
Show Performance Data Diagnose
user selection Show Performance Data 15 minutes or 24 hours 15
3. from PNM USM, select a NE in the map, then Tools
minutes or 1 day
4. from the Equipment view (EML USM), Diagnosis
Performance Data
4 ways to get the generated report: from Reporting Criteria, Report Destination section : choose Screen, Mail, File or Printer
Navigation in performance data views (RRC view)

Select performance entity(ies) to make a report on them (directly in the list or with the "PE selection window" or with the filter)
Set reporting Criteria
RRC : Report Request Control Set Report period Last Until . (Set to) Latest Current User Specific (choose the period) Set Report Destination On screen Mail File Printer Set Report Type PM Data Tabular PM Data Graphical Delta Counter Tabular (for Ethernet TPs) Delta Counter Graphical (for Ethernet TPs) Comparison Tabular (for Analog PM) Comparison Graphical (for Analog PM) Reference Value
Performance Entity Selection

A Performance Entity is a set of PM TPs. The NM operator can save the selection of several TPs into a Performance Entity. Then, he can recall this saved selection in order to fasten a further selection and management of the same TP set
Save Performance Entity Selection

The operator can save all the selected Performance entities belonging to the Performance entity tree. PE selection name
Comments
Selected TPs
The Operator can delete one or more PEs selection(s) :
Performance Entity Selection (PE selection window)

From the Report Request Control window, selection of a PE family from the performance entity tree.
Performance Entity Selection (in the list or with the filter)

From the Report Request Control window, performance entities can be filtered selecting the granularity
Selecting performance parameters

Select Param. : to make a report on

selected PEs.
Report Request Control Window

One or more Performance Parameters may already be selected, and will be shown in the Selected list (if operator didnt 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. The following actions are allowed to manipulate the set of selected Performance Parameters: Make a Performance Parameter from Available to Selected by single select one available parameter and click the [>] button. Make a Performance Parameter from Selected to Available by single select one selected parameter and click the [<] button. Make all Performance Parameters from Available to Selected by the [>>] button. Make all Performance Parameter from Selected to Available by click the [<<] button. Filtering Raw or Derived parameters by select/deselect [Raw Param] and [Derived Param] check boxes. Click [OK] to apply selections or [Cancel] to discard all selection changes
Setting Thresholds
Set Threshold for a certain TP or all TPs.(not mandatory) Define threshold

Select parameter
Notify if PM Data exceed the given value
Save
Apply for all TPs
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 RESET and SET values. In addition, the operator can set the direction of one threshold (with the default 'Threshold on Max' value). In "Threshold Setting Window", if the operator click the [Apply to all TPs], then this 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 setting threshold, the operator can click [Save] button to save all settings or click [Cancel] button to discard all settings.
Setting presentation Options

Set presentation Options before or after report generation

Setting the presentation options includes: Setting graphical report scale, either linear or logarithmic. Specify whether one report grouping multiple PMPs or one report per PMP. Also, specify how many reports will be show if one report per PMP. The number must be 1, 2 or 3. Specify whether show chart annotation or reference value in report. Specify whether to show or not threshold value in report. Choose date format in report. Choose compact or full report Use end time or start time to mark the reporting periods in the report 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 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.
Set reporting Criteria

1.
1
2. 3.
2 3 4
4.
To specify specific Reporting Criteria to direct the contents of a report User selection period Granularity Specifying the report destination Specifying the report type and the report style

Set reporting Criteria [cont.]

2
The Reporting Period can be specified on 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 grayedout. 2. The last period: The operator can choose from the following options: 15min: hour: day: 15min: hour: day: 15min: hour: day: last 15 minutes last hour yesterday these 15 minutes . week: this hour today 15 minutes 1 hour 24 hours . week: . month: . year: last week last month last year
3. The current period: The operator can choose from the following options: this week starting with Monday . month: . year: . week: . month: . year: this month this year 1 week 1 month 1 year
4. The Last Until period: The operator can choose from the following options:
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.
Display PCT Report

Report period chosen Select Performance entity(ies)
Results
Select Performance parameters

Report view with Tabular choice in the setting presentation option (all entities in one table)
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)
If the operator chose the menu Option->Show Threshold Crossing Rows Only on, then the PCT report will be turned to TCT report, which considers only the rows with at least one counter value exceeding thresholds. Chose this menu item again, and it will be toggled off to return to PCT report.
Display PCG (Graphical Report - line chart)

Select Performance entity(ies)
Select Line or Bar chart
Report view when the operator chooses Graphical in the setting presentation option.
Select Performance parameter(s)

Legenda
Display PCG (Graphical Report - Bar chart)

Select Bar chart

Legenda
Display PCG (Graphical Report - Bar chart) [cont.]

Select Line orBar chart
Graphical Report view with one Entity per table (see setting presentation option).

Legend
Forced reading of performance counters

Forced reading is used to collect data immediately without waiting for the end of the next collection period Valid only for 15 minutes counters.
1. Display any equipment view 2. Select
Configuration collection
Performance
Forced Performance
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.
Search for a TP
In the RRC window, select the TP or TP group as search root and click on Search TP Name or Search by Value
Search for a TP by name and type

Define the search conditions or use the profile function to load saved search conditions. Click the Start button to start search. Search root must be defined before opening the window Optionally define the Name Pattern (substring of TPs) using * as wild character Results are displayed in this area
Select the TP type Select the NE type
Start the search
During the search, operator can pause, resume and restart search. During the search, the found items will be filled into the result list. Optional: Make found items selected in the performance entity tree in RRC window (navigate to network tree). Optional: Print found items.
Search for a TP by Value

Locate quality degraded TP Define the search conditions or use the profile function to load saved search conditions. Click the Start button to start search. Search root must be defined before opening the window Select value(s) Results are displayed in this area
Start the search
During the search, operator can pause, resume and restart search. During the search, the found items will be filled into the result list. Optional: Make found items selected in the performance entity tree in RRC window (navigate to network tree). Optional: Print found items.
Blank Page
54
Exercise
Force counters collection Display the performance data for TPs started in the previous exercise
graphical report textual report
Locate TPs with errors detected Create a Performance Entity corresponding to the TPs previously started Delete the Network Entity
4 - 2 - 56
End of Module Performance Management
Section 5 Administration features

Module 1 Administration for operators

Blank Page
Administration features - Administration for operators 5-1-2
Objectives
perform the basic administration tasks in operator field
Objectives [cont.]
Table of Contents

1 List of Administration Functions 2 Managing Personal Settings 3 Command Log Viewer
Page 7 9 15

Administration features - Administration for operators
5-1-7
1 List of Administration Functions
1 List of administration functions
SMF
1353NM administration is conducted mainly using the System Management Features (SMF) application and "Global actions" SMF lets you perform
Operators administration Trace & log management Backup & restore Failure management Scheduler management PMDS DB Administration Cleanup Management
There are different access levels according to the user profile and the terminal used for the connection
Operators administration add/remove operators, list connected operators, close a session Trace & log management view and back up process traces view and back up log files (events, user commands, SMF) Backup & restore back up and restore application data Failure management System Snapshot view Scheduler management To schedule different actions PMDS management To Manage the performance monitoring data base Cleanup Management To suppress useless files
5-1-9
2 Managing Personal Settings
2 Managing personal settings
Changing your password

Administration features - Administration for operators 5 - 1 - 10
Enter the old password Enter the new password The shortest way to change the password, select : Global Actions Confirm OK
change password
2 Managing personal settings
Selecting the printer

Global Action printer
Set Personal
Select the printer
Close the session and re-open it Apply
Blank Page
Administration features - Administration for operators 5-1-
12
Exercise
Change your password Set a default printer
Blank Page
14
5 - 1 - 15
3 Command Log Viewer
3 Command log viewer
How to proceed
The command log viewer permits to check the content of the command log files (EMLUSM and PNMUSM). Simple and advanced filters are provided. 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. 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. Step 1: open the CLV (Actions Command Log Viewer); select a log and click on Parse 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).
Step 1: select the log

Click on Parse
Step 2: create a simple filter

Query Panel : two types of filters are provided : Simple or advanced

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

Filtering result
Complex filters
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.
Complex filters
Once created, save the filter and apply (as for simple filters) Variable
Compare to
Operator
Blank Page
22
Abbreviations and Acronyms

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

I IAP IDI IEEE

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

Switch to notes view! S 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 Threshold Crossing Alarm TCA Alcatel 1353NM TCP Transmission Control Protocol Alcatel 1353NM rel. 7.4 Operation 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 UPSR USM
V VC W WS X XC XCC
User Datagram Protocol Unidirectional Path Switched Rings User Service Manager
Virtual Container
WorkStation
Cross-Connect EXternal Communication Control
5 - 1 - 26
End of Module Administration for operators
1
Page 1
@@COURSENAME
2
Page 2
@@COURSENAME

Alcatel 1353

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Alcatel 1353

Hochgeladen von

Copyright:

Verfügbare Formate

Alcatel 1353NM Alcatel 1353NM rel. 7.

Alcatel 1353NM - Alcatel 1353NM rel. 7.4 Operation

Alcatel 1353NM rel. 7.4 Operation - Page 1

to Safety Switch Warning

Alcatel 1353NM rel. 7.4 Operation - Page 2

Section 2 Graphical Interface Module 2.1 How to Logon

Module 2.2 Network Topology

Section 3 System Operation Module 3.1 NE Supervision

Module 3.2 NE Management

Alcatel 1353NM rel. 7.4 Operation - Page 3

Table of Contents [cont.]

Module 4.2 Performance Management

Section 5 Administration Features Module 5.1 Administration for Operators

All rights reserved 2005, Alcatel

Alcatel 1353NM rel. 7.4 Operation - Page 4

Switch to notes view!

After successful completion of this course, you will be able to:

Alcatel 1353NM - Alcatel 1353NM rel. 7.4 Operation

All rights reserved 2005, Alcatel

Alcatel 1353NM rel. 7.4 Operation - Page 5

Course Objectives [cont.]

Switch to notes view!

Alcatel 1353NM - Alcatel 1353NM rel. 7.4 Operation

All rights reserved 2005, Alcatel

This page is left blank intentionally

Alcatel 1353NM rel. 7.4 Operation - Page 6

About this Student Guide

Conventions used in this guide Switch to notes view!

Alcatel 1353NM - Alcatel 1353NM rel. 7.4 Operation

Where you can get further information

All rights reserved 2005, Alcatel

Alcatel 1353NM rel. 7.4 Operation - Page 7

About this Student Guide [cont.]

Switch to notes view!

Alcatel 1353NM - Alcatel 1353NM rel. 7.4 Operation

All rights reserved 2005, Alcatel

This page is left blank intentionally

Alcatel 1353NM rel. 7.4 Operation - Page 8

Client (Company, Center) : Language :

All rights reserved 2005, Alcatel

Alcatel 1353NM rel. 7.4 Operation - Page 9

Self-Assessment of Objectives [cont.]

Switch to notes view!

Alcatel 1353NM - Alcatel 1353NM rel. 7.4 Operation

All rights reserved 2005, Alcatel

Thank you for your answers to this questionnaire

Alcatel 1353NM rel. 7.4 Operation - Page 10

Section 1 Product Overview

Alcatel 1353NM - Alcatel 1353NM rel. 7.4 Operation

Alcatel 1353NM Alcatel 1353NM rel. 7.4 Operation

This page is left blank intentionally

All rights reserved 2006, Alcatel

Alcatel 1353NM Alcatel 1353NM rel. 7.4 Operation

All rights reserved 2006, Alcatel

Alcatel 1353NM Alcatel 1353NM rel. 7.4 Operation

This page is left blank intentionally

All rights reserved 2006, Alcatel

Switch to notes view!

Alcatel 1353NM Alcatel 1353NM rel. 7.4 Operation

All rights reserved 2006, Alcatel

Table of Contents [cont.]

Switch to notes view!