1350 Oms Eml r9.6 o&m Tos63017_student Guide

1350 OMS EML R9.6 Operation and Maintenance Student Guide TOS63017_V3.1-SG-R9.6-Edition 1

COPYRIGHT © ALCATEL-LUCENT @@YEAR. ALL RIGHTS RESERVED.

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

Terms of use and legal notices Switch toUSEnotes view! TERMS OF AND LEGAL NOTICE Alcatel-Lucent provides this training course to you subject to these Terms of Use and Legal Notice. Your use of this training course and/or this site constitutes your acceptance of and agreement to these Terms of Use and Legal Notice. These Terms of Use and Legal Notice, as well as the contents of this training course, may be updated or amended by Alcatel-Lucent from time to time without prior notice to you. Your use of the Alcatel-Lucent training materials after such update or amendment constitutes your acceptance of and agreement to said updated or amended Terms of Use and Legal Notice. SAFETY WARNING Alcatel-Lucent training materials can be for products or refer to products that have both lethal and dangerous voltages present. Always observe all safety precautions and do not work on the equipment alone. The user is strongly advised not to wear conductive jewelry while working on the products. Equipment referred to or used during this course may be electrostatic sensitive. Please observe correct anti-static precautions. PERMISSION TO USE CONTENT The information, communications, scripts, photos, text, video, graphics, music, sounds, images and other materials provided in this training course (collectively the "Content"), is intended for the lawful use of employees of Alcatel-Lucent and other authorized participants in this Alcatel-Lucent training course. You are hereby granted a non-exclusive, non-transferable permission to access and use the Content solely for your personal training and non-commercial use. This permission may be terminated by Alcatel-Lucent at any time for any reason or no reason, with or without notice. You must immediately cease use of the Content upon such termination. COPYRIGHTS AND TRADEMARKS The unauthorized copying, displaying or other use of any Content from this training course is a violation of the law and Alcatel-Lucent’s corporate policies. The Content is protected in France, the U.S. and other countries by a variety of laws, including but not limited to, copyright laws and treaty provisions, trademark laws, patent laws and other proprietary rights laws (collectively, "IP Rights"). In addition to Alcatel-Lucent’s IP Rights in the Content, in part and in whole, Alcatel-Lucent, and any of the third parties who have licensed and/or contributed to the Content, owns a copyright in the formatting and presentation of the Content. Alcatel-Lucent does not grant you any permission to use the Content other than the permission expressly stated in these Terms of Use and Legal Notice. All other use of Content from this training course, including, but not limited to, modification, publication, transmission, participation in the transfer or sale of, copying, reproduction, republishing, creation of derivative 2 © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED. works from, distribution, performance, display,COPYRIGHT incorporation into another training course or presentation, or in any other way @@PRODUCT exploiting any of the Content, in whole or in part, for uses other than those expressly permitted herein is strictly prohibited @@COURSENAME and shall not be made without Alcatel-Lucent’s prior written consent. All characters appearing in this training course are fictitious. Any resemblance to real persons, living or dead, is purely coincidental. There may be a number of proprietary logos, marks, trademarks, slogans and product designations found in the Content. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logos are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. Alcatel-Lucent does not grant you a license to use any of the foregoing logos, marks, trademarks, slogans and product designations in any fashion. Granting of the right to access and use the Content for training purposes does not confer upon you any license under any of Alcatel-Lucent’s or any third party's IP Rights. DISCLAIMER ALCATEL-LUCENT DISCLAIMS ALL WARRANTIES REGARDING THE TRAINING COURSES OR THE CONTENT, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THE ALCATEL-LUCENT WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY INJURY, LOSS, CLAIM, DAMAGE, OR ANY SPECIAL, EXEMPLARY, PUNITIVE, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING WITHOUT LIMITATION LOSS PROFITS OR LOSS SAVINGS), WHETHER BASED IN CONTRACT, TORT, STRICT LIABILITY OR OTHERWISE, THAT ARISES OUT OF OR IS IN ANY WAY CONNECTED WITH (A) ANY USE OR MISUSE OF THE CONTENT OR THE TRAINING COURSES BY YOU, OR (B) ANY FAILURE OR DELAY BY ALCATEL-LUCENT, ITS OFFICERS, DIRECTORS, AGENTS OR EMPLOYEES IN CONNECTION WITH THE CONTENT OR THE TRAINING COURSES (INCLUDING, WITHOUT LIMITATION, THE USE OF OR INABILITY TO USE ANY COMPONENT OF THE CONTENT OR TRAINING BY YOU). SOME JURISDICTIONS LIMIT OR PROHIBIT SUCH EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITIES AND SO THE FOREGOING EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITY MAY NOT APPLY TO YOU. GOVERNING LAW These Terms of Use and Legal Notice are governed by the laws of France. The operation and use of the training course is governed by the laws of the country that governs your employment contract, if applicable. If any provision of these Terms of Use and Legal Notice, or the application thereto to a person or circumstance, is held invalid or unenforceable by law, statute or a court of competent jurisdiction, for any reason, then such provision shall be modified and/or superseded by a provision that reflects the intent of the original provision as closely as possible. All other provisions of these Terms of Use and Legal Notice shall remain in full force and effect. You may not assign these Terms of Use or any permission granted hereunder without Alcatel-Lucent’s prior written consent. Nothing herein shall be deemed an employment agreement or an offer of employment or an alteration in any way of a user’s terms of employment with or within Alcatel-Lucent. Copyright © 2011 Alcatel-Lucent. All Rights Reserved

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Course outline 4. Topic/Section is Positioned Here to 1350 OMS EML 1. Welcome Product Overview 1. 1350 OMS Overview R9.6 Operation and Maintenance 5. Topic/Section is Positioned Here 2. Graphical Interface 1. Product Overview 1. Web Portal 6. Topic/Section is Positioned Here 1. 1350 OMS Overview 2. Multi Service GUI 2. Graphical Interface 7. Topic/Section is Positioned Here 3. System Operation 1. Web Portal 1. NE Creation and GUI Supervision 2. Multi Service 2. Maps Operation and Sub-networks 3. System 3. Physical 1. NE connections Creation and Supervision 2. Maps and Sub-networks 4. Commissioning and Power Balancing for 1830 PSS 3. Physical connections 5. NE Management 4. Commissioning and Power Balancing for 1830 PSS 6. Q3 NE simulator and NE MIB backup and restore 5. NE Management 4. Maintenance Applications 6. Q3 NE simulator and NE MIB backup and restore 1. Alarm management 4. Maintenance Applications 2. Performance Monitoring management 1. Alarm management management Performance Monitoring management 3 3. Logs 2. 3. Logs management 4. NE software download COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.

@@PRODUCT @@COURSENAME

4. NE software download


Course objectives

1350 OMS EML Upon completion of this course, you should be able to: R9.6 Operation and Maintenance describe the 1350 OMS functions and architecture, login and start with the 1350 OMS, navigate the Graphical Interfaces, Upon completion of this User course, you should be able to: create in the system database the NEs deployed in the network, configure the parameters required for supervising the NEs, describe themanage 1350 OMS architecture, create and thefunctions network and map, create in the system the physical connections that represent the network cabling, login and start with the 1350 OMS, perform the main provisioning and commissioning procedures for 1830 PSS networks, navigate the Graphical User Interfaces, use the simulator for off-line configuration of Q3-OSI NEs, create inthe thebackup system & database NEs NE deployed in the network, perform restorethe of the database, perform set parameters of NE management operations, configurea the required for supervising the NEs, download into the NE a new software package to update its software release, create and manage the network map, browse the operation log, create in system the physicalapplication connections representthe the current networkand cabling, handle thethe Alarm Surveillance forthat monitoring the historical alarms, perform the main provisioning and commissioning procedures for 1830 PSS networks, manage the transmission quality records. use the simulator for off-line configuration of Q3-OSI NEs, perform the backup & restore of the NE database, perform a set of NE management operations, download into the NE a new software package to update its software release, 4

browse the operation log,

COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.


handle the Alarm Surveillance application for monitoring the current and the historical alarms, manage the transmission quality records.

Your feedback is appreciated! Please feel free to Email your comments to: [email protected] Please include the following training reference in your email: TOS63017_V3.1-SG Edition 1 Thank you!


Do not delete this graphic elements in here:

@@SECT LE Section 1 Product Overview Module 1 1350 OMS Overview

TOS63017_V3.1-SG-R9.6-Ed1 Module 1.1 Edition 1

1350 OMS EML R9.6 Operation and Maintenance TOS63017_V3.1-SG Edition 1

All Rights Reserved © Alcatel-Lucent @@YEAR

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. TOS63017_V3.1-SG-R9.6-Ed1 Module 1.1 Edition 1 Section 1 · Module 1 · Page 1

Blank page

1·1·2


Product Overview · 1350 OMS Overview 1350 OMS EML · R9.6 Operation and Maintenance

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2012-11-10

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Detail the set of 1350 OMS’s applications and their interworking Illustrate the 1350 OMS EML’s purposes Describe how 1350 OMS EML interacts with the Network Elements

1350 OMS 13 - Rep software 50 - rep 3rd gen O - Optical M - management S- system

EML - Element management layer EML - Divided into IM andUSM IM - Information Management USM - User Services Management

1·1·3 Product Overview · 1350 OMS Overview 1350 OMS EML · R9.6 Operation and Maintenance



Module objectives [cont.]





Table of contents Switch to notes view! 1 1350 OMS Product and its Applications 2 EML Management Functions 3 EML Architecture




Page 7 15 23

Table of contents [cont.] Switch to notes view!





1 1350 OMS Product and its Applications





TMN description 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





Applications and Common Components

Login and Security

GUI & maps

Fault Management

Performance Monitoring

1350 OMS PKT NML layer

1350 OMS SDH

135 0OMS SONET

1350 OMS eOMS

1350 OMS Hardware Platform

1350 OMS WDM EML layer

1350 OMS EML

Network 1·1·9 Product Overview · 1350 OMS Overview 1350 OMS EML · R9.6 Operation and Maintenance

Craft Terminal


The 1350 OMS focuses on the TMN’s Element Management and Network Management layers. These management layers functions are accomplished by a set of different "applications”. The Element Management Layer is implemented by the 1350 OMS-EML application. The Network Management Layer is implemented by the 1350 OMS-SDH, 1350 OMS-PKT, 1350 OMSSONET, and 1350 OMS-WDM applications. Common functionalities are bundled into components that are shared by the applications. By means of a unique login, the user is granted the access to the applications according to the security settings. The commands of all the applications are available in the same Graphical User Interface that provides a unique map, too. Fault management and Performance Monitoring information is common to all the applications. The user can retrieve the data collected by a single application, too. Every application renders the alarms and the PM results according to the own management. Craft Terminal is meant for commissioning and for maintenance when the Network Element is not reachable from 1350 OMS.



Data Ethernet, MPLS, CES

TDM

1350 OMS PKT

1850TSS, 9500MPR, ISA-ES

1350 OMS SONET

1350 OMS SDH 1850TSS, OMSN

WDM

1350 OMS WDM 1830PSS

Element Mng

1350 OMS EML

1626LM

1350 OMS eOMS

Networking management

Applications’ purposes

Legacy LegacyLucent Lucent Network Network Client/Server relationship 1 · 1 · 10 Product Overview · 1350 OMS Overview 1350 OMS EML · R9.6 Operation and Maintenance


Each application is license controlled and separately purchasable. 1350 OMS-EML for the Element Layer functions such as NE creation, SW download, NE data backup/restore. The Network Physical Resource (NPR) module is also part of the 1350 OMS-EML application. It manages network construction and inventory on physical resource (i.e. NE, boards, ports). It provides support for manual/automatic physical link creation. 1350 OMS-SDH for the SDH technology and for the WDM technology in some equipment, e.g. 1626LM. 1350 OMS-PKT for the data technologies, such as Ethernet, T-MPLS, CES (Circuit Emulation Service). 1350 OMS-SONET for the SONET technology. 1350 OMS-WDM for the WDM technology in some equipment, e.g. 1830PSS. 1350 OMS provides users with the ease of accessing and using the eOMS (embedded Optical Management System) to provision the former Lucent legacy network. 1350 OMS-eOMS accomplishes both the EML and NML functions. It is integrated with the 1350 OMS GUI for single login and common GUI navigation. It relies on the Common Fault Management component to display alarms. It is integrated with EML, SDH, WDM and SONET applications for sub-network management.



Example of service provisioning: Ethernet over SDH over WDM 1830PSS 1850TSS Ethernet”

1350 OMS WDM “1350 OMS SDH for SDH” + “1350 OMS PKT for end-points selection for provisioning

1350 OMS PKT 1350 OMS SDH

B

A S

1350 OMS SDH

S 0P 3 18

S

1350 OMS WDM

E TS 50 8 1


F

GbE

1350 OMS SDH

1350 OMS PKT

1350 OMS PKT 1 · 1 · 11

S

effect of provisioning

S 0T 5 18

D

C

STM-N

GbE

STM-N

1350 OMS WDM


Let’s consider a Gigabit Ethernet service across SDH and WDM networks. The WDM network is made of 1830PSS equipment; the Ethernet/SDH network is made of 1850TSS equipment. 1830PSS management requires 1350 OMS-WDM; SDH management of 1850TSS requires 1350 OMS-SDH; Ethernet management of 1850TSS requires 1350 OMS-PKT. While provisioning the WDM network, the user has to select the end-ports of node C and node D. All the WDM nodes between the two ports are configured. While provisioning the SDH network, the user has to select the suitable points of node A and node F. All the SDH nodes between the two points are configured. While provisioning the Ethernet service, the user has to select the end-ports of node A and node F. The Ethernet configurations are executed on node A and node F.



Master and Presentation: GUI processes GUI: Graphical User Interface

Browser - Explorer, Mozilla Firefox, ... JAVA 1.6 and patches - 32 bit configuration 2GB RAM (3GB RAM strongly recommended)

PC GUI clients

Server

Components Alarms

GUI servers

Automatic download of GUI clients from Server to PC

Perf. Monit. Security

GUI server

WDM

PKT

Network Physical Resource (Ports, Physical connections, ...)

GUI server

EML


SONET

SDH

GUI server

Maps

1 · 1 · 12

GUI server

GUI server

NML

GUI server

GUI server

eOMS

NE management

protocol adapters & basic NE functionalities


1350 OMS runs on servers and the user makes use of PC. In the server, the usage of the applications is accomplished by the GUI server processes. These processes are driven by the GUI client processes that run on the PC. The PC downloads those processes from the server at the first login and whenever a feature (e.g. open the equipment view) is used for the first time. This slide features the case where all the applications and processes are installed in one server. The management of the network may require more servers. OMS GUI follows a full web-based approach. No manual client software distribution and installation procedures are required in the PC apart from a web browser and Java. To know the PC’s requirements, click the REQUIREMENTS link in the web desktop. Note: previous Java versions (e.g.: 1.4) are not supported. Java 64 bit is not supported. Note: Internet Explorer 8 is supported on Win 7, configured in backward compatibility mode to work as IE7.



Master and Presentation example More users more load of GUI server processes GUI server processes can be installed on Presentation servers in order to unload the Master servers Master: Presentation

for Applications (+ GUI servers)

Presentation: for GUI servers Example of platform architecture Distributed (more than one server) one presentation three masters Co-hosted SDH and PKT on the same server

1 · 1 · 13 Product Overview · 1350 OMS Overview 1350 OMS EML · R9.6 Operation and Maintenance

Server A

PKT GUI server SDH GUI server EML GUI server

Master : SDH + PKT GUI server 1350 OMS-SDH

1350 OMS-PKT

Master : EML 1 GUI server

Server B

GUI server

Master : EML 2 Server C

1350 OMS-EML

GUI server

Server D

1350 OMS-EML


The type and the number of servers to deploy in the network depend on two concerns: the Network Management System load and the Network Management System constraints. The NMS load can be evaluated taking into account a number of factors; mainly: •the size/configuration of the network, that is the number and type of Network Elements. •the required applications. •the Added-Value components: Open Interfaces, High Availability. •the number of active users working with the system at the same time.

As NMS constraints, the following rules apply. •The EML application can be split over multiple servers. •Each single NML application can not be distributed over multiple servers. •More applications can co-reside in a single server.



High Availability Usually Main Spare

Active Stand-by (aligned to Main)

Resilient configurations 1+1 N+1 Mutual protection Server X Application#1 Application#2 Server Y Application#1 Application#2

NMS A Master Main

1+1

NMS A Master Spare

Local storage Local storage

DCN

is Active is Stand-by is Stand-by is Active

2Mb/s min between Main and Spare

1 · 1 · 14



1350 OMS-HA is the High Availability application. It foresees at least two server machines. The commitments of High Availability are: •Replication of the Core applications and their relevant data from the Active server to the Standby one. •Monitoring of the health status of the active machine and all its processes. •Triggering the switchover of network supervision from Active to Standby in case the former one is no more able to carry out its task. The activation of the Spare NMS in place of the Main one can be done automatically or manually.

In principle the protection is provided at the application level: it means that a failure on a single process in any of the Core applications can trigger a selective switch-over involving just the affected application and not all the others. The database of the spare server is populated by the replication mechanisms, but it is kept inactive with respect to the network supervision. According to the customer requirements, High Availability is able to protect single NMS applications, whole sites or partial sites through the following different resilient configurations: •"1+1”: the Main server is connected with a dedicated communication link to the protecting Spare server, usually located in a geographically remote site when Disaster Recovery Centers are envisaged. •"N+1“ [N-plus-1]: multiple servers/applications are protected by only one Spare server that duplicates the application data of all the running applications on the active servers but, upon failure, protects only one application per type. •“Mutual Protection”: the Main server is concurrently Active for the first application and Standby for the second one. The other server configuration is dual: the first application is OFF, the second one is ON. This solution aims at providing load balancing in the nominal situation, so better scalability targets. Upon failures the customer could pay some performance degradation while keeping full Network Management capabilities from one host.


2 EML Management Functions





EML functions EML supplies functionalities as defined in ITU-T M.3100: Configuration management Fault management Performance management Security management





NE Directory Functions

Network Element list

NE creation window



NE Directory Management: NE Creation/Removal Global NE inventory NE naming and addressing



Network Topology Functions Sub-network tree

Sub-Network Map

Nodes and Physical links

1 · 1 · 18



Network Topology Management: Creating the topology (Network, Sub-Network) Adding/deleting Node in maps Creating Physical Links between Nodes Topology Autodiscovery Alarm status propagation in maps



Equipment View and Software Management Functions Equipment View like the local management’s (Craft Terminal, ZIC, WEB-UI, ...)

Software Management

1 · 1 · 19



Network Element management: NE Supervision management Allow/inhibit Local Craft access to NE NE Remote Inventory management NE “Show equipment” for accessing all the equipment management functions Enabling/disabling alarm notifications Configuring the alarm severity profile Managing NE time and synchronization sources Backing up and restoring the NEs configuration NE Software management Get information on the NE software Downloading software from a server to an NE Activating/deactivating NE software



Alarm Functions Alarm Surveillance

1 · 1 · 20



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 synthesis represented in all views concerning an entity



Performance Monitoring Functions

Measure Monitored counters

1 · 1 · 21



Performance Monitoring Management: Enabling the error counters Configuring the error counters threshold Performance Monitoring collection Report generation Logging performance data



System administration Functions System Management

Security Management 1 · 1 · 22



For the administrator: System Management: Starting/stopping the system System trace and logs Displaying and managing the processes System Backup/Restore Periodic actions scheduling Security Management: Accessing the system Assigning profiles Access rights to the NE


3 EML Architecture




3 EML Architecture

EML-IM processes 1350 OMS EML interacts with the NEs by means of the EML-IM (Information Manager) processes EML-IM is called also Network Adapter (NA) There are several EML-IM types. Each EML-IM type: can manage several NEs types and releases is based on the communication protocol/s supported by the NEs: OSI Q3 IP SNMP IP TL1

can have several instances that are created during the system installation and configuration. Each instance is responsible for a number of NEs.



SNMP: Simple Network Management Protocol TL1: Transaction Language 1 EML-IM processes implement the interface toward the network’s NEs. Different types of EML-IMs are provided in order to manage different NEs interfaces (Q3, SNMP,TL1) and/or different NEs technologies (DXC/ADM/WDM/ETH/SDH/SONET/…). EML-IM acts as a bridge between NML Managers, GUIs, and the NEs, too.


3 EML Architecture

EML-IM vs NE - examples EML-IM type

Protocol

Notes

Examples

ADM Q3

OSI Q3

-

1642EM, 1650SMC, 1662SMC, 1660SM, 1664SM, 1670SM, 1666-55SR, LHR, UHD, UHR, 1640WM, 1620LM R<=3.8, 1626LM R<=3.4, 1686WM, 1696MS

DXC Q3

OSI Q3

Digital cross Connect

1678MCC R>=3.0, 1641SX, 1664SX, 1674LG

CORBA SNMP

IP SNMP

-

9500MPR, ISA-ES, LUX50, ULS, 1692MSE, P8FES in 1646SM R2.2 and 1646SMC R2.2

4G

OSI Q3 + IP SNMP

-

1626LM R4&R5, 1850TSS-3, 1850TSS-320 R<=2.0

9500MXC

IP SNMP

-

9500MXC

SNA

IP TL1 + IP SNMP

Most recent NEs

Most 1850TSS [5; 5C; 5R; 100; 160 & 320 R>=3.0], 1830PSS, 1540LINA, 1870TTS, 1620LM R>=4.2, 1626LM R>=6.0, 1646SM/C, P8FES in 1646SM R2.0 and 1646SMC R1.0

CNA

OSI Q3

-

1645AMC

TNA

IP TL1

-

1675LU

SGM

-

3rd party NEs

Raman Pump, 1511EM

1 · 1 · 25



ADM: Add and Drop Multiplexer SGM: SNMP Generic Mapper SNA: Smart Network Adapter SNMP: Simple Network Management Protocol CMISE: Common Management Information Service Element. It’s an application (layer 7) protocol of Q3 stack. CORBA: Common Object Request Broker Architecture CNA: CMISE Network Adapter TNA: TL1 Network Adapter TL1: Transaction Language 1 4G: 4th Generation – time frame between “NEs with ADM Q3 EML-IM” and “NEs with SNA EML-IM” TSS: Transport Service Switch PSS: Photonic Service Switch OMSN: Optical Multi Service Node UHR: 9600USY LHR: 9600LSY MPR: Microwave Packet Radio N.B.: Each release of 1350 OMS and its applications support certain NEs within the Alcatel-Lucent family of optical NEs. Mention of NEs or specific NE features in the text of this document, or any document in the 1350 OMS documentation set, that are not supported in this particular product release can apply to prior or future product releases. Such material may not be currently visible or operable on the GUI and/or the server and has been added only as a convenience for our customers. This material is subject to change. For the list of NEs that are supported in the 1350 OMS 9.6, contact your Alcatel-Lucent local customer service support team.


Discussion or question List and define the EML functionnalities ?




End of module 1350 OMS Overview





@@SECT LE Section 2 Graphical Interface Module 1 Web Portal





Blank page

2·1·2


Graphical Interface · Web Portal 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Login, log out and start the 1350 OMS Start the 1350 OMS’s applications Customize the Web Portal

2·1·3 Graphical Interface · Web Portal 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 Login Windows 2 Web Portal Overview 3 How to Logout


Page 7 11 22








1 Login Windows




1 Login Windows

Preliminary setting 1. Select the following folder: C : \ WINNT \ system32 \ drivers \ etc 2. Edit and save the file “hosts”

4. Save the file and exit


3. Insert the IP address and hostname of the Server COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.

To gain full access to the 1350 OMS GUIs through the Web Desktop, the PC must be configured so that the 1350 OMS’s server can be reached using the server’s hostname. If the Domain Name Server (DNS) is configured on the PC, it should be configured so that the server’s hostname is managed. If such a configuration is not feasible, the “server’s hostname” manually inserted in the following file:

“IP address” association must be

C:\WINDOWS\system32\drivers\etc\hosts in case the PC runs the Windows® Operating System /etc/hosts in case PC runs the PC-Linux Operating System


1 Login Windows

Web Browser 1. Open a Web Browser and type the Server’s IP address as Address




1 Login Windows

Web Desktop To check the PC requirements

2. Insert User and Password and then Login

VERSION: to check the 1350 OMS’s software

1. Click anywher e

2 · 1 · 10 Graphical Interface · Web Portal 1350 OMS EML · R9.6 Operation and Maintenance


The user password is subject to the following constraints: At least 24 hours should last since the last change The new password should contain at least one digit [0-9] The new password should contain at least eight characters The new password should contain at least two special characters The new password should contain at least one uppercase letter The new password should not contain the user identifier


2 Web Portal Overview





Web Portal Web Portal is a Java application that is started when the user logs in from the Web Desktop Main bar Toolbar

Left Tree Panel

Application List Area

Message Area

Status bar 2 · 1 · 12 Graphical Interface · Web Portal 1350 OMS EML · R9.6 Operation and Maintenance


The web Portal provides the user with a view of all the 1350 OMS’s applications. The Left Tree Panel is a navigational panel which is organized with a hierarchical tree that lists the 1350OMS’s applications. The applications are grouped as Operation (Management, Alarm, Network Tools) and Administration (System, Data Management and Security Administration). When a folder is selected from the Left Tree Panel, the subtended applications’ icons are displayed in the Application List Area. The Application List Area allows to start an application, double click an icon or right click the icon to display a Start button. The Message Area displays application’s and Web Portal’s messages. The Status bar displays the last application or Web Portal’s message.



Main bar and Toolbar

While closing the Web Portal... 2 · 1 · 13 Graphical Interface · Web Portal 1350 OMS EML · R9.6 Operation and Maintenance


The user can add or remove preferred applications to the Tool bar by means of “Edit toolbar” or double click an application and then “Add to toolbar”. The applications added to the toolbar can be listed by issuing “View

Customize the

Preferred Application List”.



Web Portal navigation

Administration

Operation



Common system applications are grouped by their logical function as follows: Operation includes applications for Network Provisioning and Inventory, Alarms and Network Tools. Administration includes system administration tools, such as System Monitoring, Task Scheduler, Data Backup and Restore and Security Administration.



Operation applications: Network Management Multi Service - Graphical User Interface (MS-GUI) commands for the 1350 OMS’s applications (EML/SDH/PKT/WDM) Maps Performance Monitoring Right click and ... choose “Start” or double click on the related icon to start the desired application

MS-GUI



The Network Management application provides the Multi Service Graphical User Interface (MS-GUI), to create, modify, delete, retrieve and provision the NEs and the SDH, SONET, WDM and PKT network. It provides inventory lists for querying the content of the management applications’ databases. It also provides a map of the managed network on which various network objects are displayed, such as Subnetworks, Nodes, Links, etc. Performance Monitoring is also issued by the MS-GUI.



Operation applications: Alarms

Alarms PKT

Alarms WDM

Alarms EML

NE Auto Discovery

Events: SNCP switch tunnel switch loopback

Alarms & Logs


Alarms SDH


The Alarms application is the single common fault management GUI which provides presentation functions for the alarm of all managed NE’s and network. The GUI presents a dynamic view of all current and historical alarms in the managed network. Besides the Global Alarm Management, which consolidates all the NE’s elementary alarms and SNCP switching events and the network correlated alarms of the whole system, the user can choose to start the applications dedicated to the alarms filtered per single application (EML, SDH, WDM, PKT). The NEAD_USM (Network Element Auto Discovery User Service Management) opens the GUI for the creation of the auto-discovered NEs. The Current Events log opens an Alarm Surveillance like GUI that lists the SNCP switch, T-MPLS/MPLS-TP tunnel switch, and loopback configuration events for 1850TSS-100, 1850TSS-160/320 and 1830PSS.



Operation applications: Network Tools GENOS: Open Interface to export alarms, performance monitoring, network inventory, and remote inventory to external Operation Systems.

GENOS: generic OS-to-OS interface EOS: External OS OS: Operation System



The 1350 OMS supports Open Interfaces (OI) as an added value module, which is referred to as the 1350 OMS OI. The 1350 OMS OI software package is installed independently of any other application such as the 1350 OMS SDH, 1350 OMS PKT, 1350 OMS WDM, or 1350 OMS SONET, or any element manager such as the 1350 OMS eOMS or 1350 OMS eOMS. The 1350 OMS OI enables the 1350 OMS applications to export or import data to multiple external operation systems (OSs). The 1350 OMS OI is a flexible, powerful, and effective set of generic OS-to-OS interfaces (GENOS) that allow an external OS to synchronize alarms, performance monitoring, network inventory, and remote inventory data with any of the 1350 OMS applications. Up to Network Release 9.4, Network Tools reports also the icon to start the “IP over OSI tunnel” configuration that is available in MS-GUI for R9.6.



Administration applications: System

Applications meant only for users who carry out administration activity on the server

It is useful for users who carry out provisioning, too (see next slide) 2 · 1 · 18 Graphical Interface · Web Portal 1350 OMS EML · R9.6 Operation and Maintenance


The Task Scheduler enables the administrator to schedule the execution of jobs that typically include backups of data, purges of data, clean ups of data, and PM data collection. The System Monitor is the graphical interface that allows the user to perform process monitoring functions (start, stop, view the status, view the traces, etc.) on items that appear in a tree structure.



Administration applications: System [cont.] Processes Monitoring and Control

1350 OMS

1350 OMS EML

EML-IMs ADM Q3 (e.g. 1660SM) CORBA SNMP (e.g. ISA boards, 9500MPR) SNA (e.g. 1850TSS, 1830PSS, 1626LM R6) IM: Information Manager SNA: Smart Network Adapter 2 · 1 · 19 Graphical Interface · Web Portal 1350 OMS EML · R9.6 Operation and Maintenance




Administration applications: Data Management Applications meant only for users who carry out administration activity on the server

To install on the EML the NE software packages to be then downloaded to the NEs 2 · 1 · 20


Graphical Interface · Web Portal 1350 OMS EML · R9.6 Operation and Maintenance

The Backup and Restore applications allow the administrator to dump and restore a copy of the application data to a disk or a tape. Examples of jobs: •Ntw: which is all management system data and NE backup data, meaning, network data •AS: which is all alarm surveillance data •PM: which is all performance monitoring data •Swdl: which is all data pertaining to NE software downloads •Log: which is all log file data •System Configuration: which is all system configuration data •Operator: which is user data that includes the home directory of all created and predefined 1350OMS-

EML users The NE SW Packages allows the administrator to install on the EML the NE software packages to be downloaded to the NEs for possible upgrades.



Administration applications: Security Administration User Session to check and force out the logged user User Accounts to create, modify and delete the users User Profiles to manage Functional Access Domain, Object Access Domain, user profiles, etc. per single application




3 How to Logout




3 How to Logout

How to do it

From the Web Portal, select: “File Log

out…”




Discover Log on the EML application and discover the web portal

Time allowed: 5 minutes




End of module Web Portal





@@SECT LE Section 2 Graphical Interface Module 2 Multi Service GUI





Blank page

2·2·2


Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Operate the Multi Service - Graphical User Interface (MS-GUI)

2·2·3 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 MS-GUI layout 2 Main command-bar 3 Left area 4 Filtering and searching 5 List management 6 Copy/paste 7 Options




Page 7 17 21 30 41 53 58





Page

1 MS-GUI layout




1 MS-GUI layout

Main points MS-GUI is shared by all the applications: 1350 OMS EML/SDH/PKT/WDM

Two types of application’s commands: Actions: for provisioning Search: to retrieve the provisioned objects (e.g. NEs) according to the object type, the query’s result is a list or a graphical window

Four main operational panels: Maps Lists Graphical Logs

2·2·8



The MS-GUI presents maps, lists, queries, and graphical views of network’s objects. It provides a central point supporting comprehensive functional navigation across the whole managed network. The MS-GUI is the unique interface to access to the features of all the Element Management (EML) and the Network Management (SDH, WDM, PKT, SONET) applications of the 1350 OMS. From the map of the MS-GUI the user is able to: view all nodes and physical links between them, animated by their alarm status retrieve lists of network entities organize nodes into recursive sub-networks, so having a partitioned map view of the managed network use menus contextual to the selected entity and to the user profile start the provisioning wizards


1 MS-GUI layout

Search and Actions




1 MS-GUI layout

Overview Main command-bar Fixed toolbar Main Area • Logs • Lists • Graphical Left Area

Icons that depend on the selected object

• Maps •Compound Views

2 · 2 · 10 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance



1 MS-GUI layout

Maps Maps toolbar

Left Area




1 MS-GUI layout

Lists Example: Network Elements list




1 MS-GUI layout

Graphical Example: Physical Connection structure




1 MS-GUI layout

Logs Click any column’s header to sort




1 MS-GUI layout

Compound Views

1830PSS Wavelength Tracker’s outcome




1 MS-GUI layout

Info from GUI

Click the basket (Run the Garbage Collector) to clean the not-used segments of the heap memory

GUI servers connection status synthesis

Heap memory size [used] of [max]

PC’s Date and Time

Ongoing or last operation 2 · 2 · 16

Progress Bar



The GUI servers connection status synthesis icon shows if all the GUI servers are connected (plug close) or if some of them are disconnected (plug open). If a GUI server is disconnected, the execution of its operations is not available or fails. If the plug is open, the “Application Properties” window can be opened by clicking the plug. Such a window states the status (connected or not) of each GUI server. If the plug is close, the “Application Properties” window can be opened just by: File Properties. •

TDM: 1350 OMS SDH

•

FTS: File Transfer Scheduler

•

CPM: Converged Performance Management

•

TM: Topology Manager – 1350 OMS EML

•

CLOG: Common Log

•

PKT: 1350 OMS PKT

•

MAP

•

CPB: Commissioning and Power Balancing (for 1830 PSS)

•

WDM: 1350 OMS WDM

•

LT: Line Tuning (for 1626 LM)

Common means that it is shared by all the applications. The Date and Time are the PC’s ones; they are not the 1350 OMS server’s ones. It is necessary that the PC’s date and time are aligned to the server’s, so that the difference is lower than 5 minutes, otherwise some applications (e.g.: Processes Monitoring and Control GUI) will not start and/or will not work correctly.


2 Main command-bar




2 Main command-bar

First level drop-down menus

2 · 2 · 18



File

Close

Selected view or all windows

File

Print

Selected view

Edit

Find…

Find a text string in the Main View. It’s case sensitive.

Tools

Left Area

Change the appearance of the left tree area to Maps, Search, Windows, Command or Favorites

Tools

Options

Enables the user to control certain types of GUI screen behavior

Tools

Manage server connection

Allows to disconnect or re-connect previously disconnected application GUI servers (i.e. TDM, FTS, CPM, TM, CLOG, PKT, WDM, MAP, CPB, LT)


2 Main command-bar

The Search Menu

Query options dependent on the 1350 OMS installation (e.g. 1350 OMS WDM is not installed) Query option dependent on the object selected in the map or list (e.g. a Node)

2 · 2 · 19



OTN: commands for 1350 OMS SDH Packet: commands for 1350 OMS PKT


2 Main command-bar

The Actions Menu

Query options dependent on the 1350 OMS installation (e.g. 1350 OMS WDM is not installed)

Query option dependent on the object selected in the map or list (e.g. a SubNetwork) 2 · 2 · 20 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance


By the Actions Menu the user can perform tasks on the network’s objects (create, delete, discover, synchronize, …) and on File Transfer Scheduler jobs, set the Performance Monitoring (PM) report options, retrieve and modify objects properties, etc.


3 Left area




3 Left area

Overview

Left Area

Maps

Selection of this icon causes the categories of domain map resource trees (Sub-networks) to be displayed in the left panel.

Search

Selection of this icon causes a search capability to be displayed in the left panel. The user enters search criteria, the results of which are displayed in the Main View panel.

Windows


Selection of this icon enables the left panel to display the list of open windows grouped by categories.

Operations

Selection of this icon enables shortcuts to certain operations to be displayed in the left panel.

Favorites

Selection of this icon enables the left panel to be populated with a tree that shows the folders containing bookmarks defined by the user.

Objects

Selection of this icon enables shortcuts to certain objects (Nodes, Network Elements, Physical Connections, …) to be displayed in the left panel.



3 Left area

Maps

Reload maps tree Find (Sub-) Network Tree

To show the selected Sub-network • double click, OR • right click

Search

Map

Displayed map




3 Left area

Search (filter)

A new list containing the filtering’s outcome is opened

As far as EML is concerned, it’s the User Label




3 Left area

Windows Group by category Sort by name Close

OR double click Move to front

Dock

OR double click the header of the undocked window

Undock




3 Left area

Operations Add new category

Remove selected operation

Shortcuts for the preferred “Search” and “Actions” commands

1. “Drag” the desired Search or Actions command following such a path

2. “Drop” when the pointer appears 2 · 2 · 26 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance



3 Left area

Favorites 1. Click “Add a New Favorite” icon 3. Assign a name

4. OK

2. Choose some windows among the open “Lists”, “Maps”, “Graphical” Groups of “Lists”, “Maps”, “Graphical” windows 2 · 2 · 27 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance


Execute at startup: the selected windows are opened at MS-GUI opening (Network Management


Start).

3 Left area

Favorites [cont.] 1. To open all the windows belonging to the created favorite, select the favorite and ... Create a new group of Favorites

Modify

2. ... click this icon, OR ...

Load associated windows Remove Selected Favorite

Add a New Favorite

3. ... double click the favorite




3 Left area

Objects Add Category

Delete Categor y

1. Select an object (e.g. NE) in the list and drag&drop

List of preferred objects (NE, Nodes, Physical Connections, ...)

2. Select the object and: • right click to get the drop-down commands list • double click to get its properties 2 · 2 · 29 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance



4 Filtering and searching





Search (filter) from the left area

A new list containing the filtering outcome is opened

As far as EML is concerned, it’s the User Label





Open a list as filtered

1. Click the “Enable Filtered Searches” icon

You can decide to show the outcome of the filtered searching in an already open list of the same type. If so, the current content of the list is lost.

2. Do a Search

3. The window that opens is a filter configuration 4. Set the filter 2 · 2 · 32 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance

5. OK




Open a list as filtered [cont.] 1. Instead of clicking the “Enable Filtered Searches” icon, ...

2. ..., it’s possible to enable such a filtering by “Tools Options”,...

3. ...and ticking “Display Filter dialog on Search”





Filter an open list 2. Click “Modify”

3. Set the filter

1. Click the “Change Search Criteria” icon





Filter per column





FILTER by means of the bottom bar 1. Click the Display Find Toolbar icon

2. Type





FIND by means of the bottom bar 1. Click the Display Find Toolbar icon

Find the next occurrence of the phrase Find the previous occurrence of the phrase


Highlights all occurrences of the phrase




List’s counters NEs filtered per column with “Location Name = Milan” or by means of the bottom bar filter

All NEs (not filtered)

3 selected items

1 selected item

7 items in the not filtered list 2 · 2 · 38 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance



5 items that don’t match the filter


Simply by editing: for lists 1. Click any cell of any row, except cells that belong to frozen columns

2. Start typing. This box opens.

The first occurrence is highlighted





Simply by editing: for left area e.g. Maps

2. Start editing. This box opens. 1. Click anywhere The first occurrence is highlighted 2 · 2 · 40 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance



5 List management




5 List management

Two different ways to manage the lists

The new setting applies to the new open lists




5 List management

Show group tables as default Show group tables as default (not valid for hierarch and if cols are forced) If enabled (default)

This section is available

An example in next slide If disabled Grouping columns is not possible




5 List management

Group columns By means of “column’s title” drag&drop ...

...it’s possible to group one column or ...


... or commands in drop-down menu from “column’s title”,...

... more than one column



5 List management

Move a column

Click the column’s title and drag&drop e.g.

...




5 List management

Move a column: freeze 1. Right click the column title

The yellow columns are the frozen ones

2. Freeze ...

e.g. Freeze Left




Freeze/Unfreeze are available for the lists opened while “Show group tables as default” is disabled

5 List management

Show/hide columns By default, some columns are hidden

From any column title




5 List management

Save the list configuration List configuration: shown columns, column’s position, ...




5 List management

Sort a column

Click the column title




5 List management

Filter a column




5 List management

Update Flag When a row is updated (e.g. “Set in Service” a Physical Connection), a flag is put in the relevant column

To delete the flag, refresh the list .... ... OR do “Clear * Flag” 2 · 2 · 51 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance


Such a column can be shown and hidden from the list as any other column.


5 List management

Export list “Export to CSV...” OR ... ... “Export data”




6 Copy/paste




6 Copy/paste

Copy/paste objects

Copy object: to copy the selected object/s to the buffer. The copied object/s can be “pasted” in the suitable wizard forms (e.g. a node in the “Create Physical Connection” wizard). The selected objects replace the current buffer’s content. Add to copied object: to add further objects to the buffer without erasing its content Clear copied object: to clear the buffer




6 Copy/paste

Copy/paste objects: Example

1. Select the objects

2. Copy object




6 Copy/paste

Copy/paste objects: Example [cont.] “Create Physical Connection” wizard (Actions

Physical

Create Physical Connection)

1. Right click 2. Paste object List of the objects in the buffer




6 Copy/paste

Copy/paste attribute To copy the cell content to be pasted to an editable field, e.g. “Find”

1. Right click a cell (e.g. Milan) 2. Copy attribute

3. Use the keyboard’s “ctrl-V” to paste




7 Options




7 Options

Available options

Default settings




7 Options

Always show full menus If enabled (default)

If disabled

Collapsed commands list E.g. “Links Over Cable” in PKT: Search Packet Construction Transport Link Links Over Cable 2 · 2 · 60 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance



Complete commands list

7 Options

Display Filter dialog on Search

It corresponds to clicking the “Enable Filtered Searches” icon

You can decide to show the outcome of the filtered searching in an already open list of the same type. If so, the current content of the list is lost.

1. Do a Search

2. The window that opens is a filter configuration 3. Set the filter 2 · 2 · 61 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance

4. OK



7 Options

Automatically display Details Panel on Lists If disabled (default)

If enabled

Details Panel


E.g. “Links Over Cable” in PKT: Search Packet Construction Transport Link Links Over Cable



7 Options

Define Highlight Name based on selection

2. If enabled (default) If disabled

1.

3. Edit

4. Outcome 2 · 2 · 63 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance



7 Options

Display Host Name on windows title User

Host Name

If enabled (default)

If disabled

W

eb

to sk e D

Anyway Host Name is shown in Web Portal and Web Desktop

W 2 · 2 · 64 Graphical Interface · Multi Service GUI 1350 OMS EML · R9.6 Operation and Maintenance

eb

rta Po

l



p

7 Options

Use MAP version 2.0 If disabled

If enabled (default)

Basic

Advanced (MAP version 2.0)

The training addresses the “MAP version 2.0”




7 Options

Use old hierarchical tables E.g. “Links Over Cable” in PKT: Search Packet Construction Transport Link Links Over Cable If enabled If disabled (default)

Expand is available




7 Options

Show group tables as default Show group tables as default (not valid for hierarch and if cols are forced) If enabled (default)

This section is available

If disabled Grouping columns is not possible




7 Options

Include hidden columns during Export

It doesn’t work

2.

1.




Exercise 1. 2. 3. 4.

Open the map dedicated for the training List the network elements Move the column as the first one Save the list





End of module Multi Service GUI





@@SECT LE Section 3 System Operation Module 1 NE Creation and Supervision TOS63017_V3.1-SG-R9.6-Ed1 Module 3.1 Edition 1




Blank page

3·1·2


System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Create manually the Network Elements by setting the required parameters Let 1350 OMS EML auto-discover the deployed Network Elements Supervise the Network Elements Delete the Network Elements

3·1·3 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 Introduction 2 NE supervision and deletion 3 NSAP address 4 Creating and addressing a Q3 NE 5 Creating and addressing ISA boards 6 Creating and addressing a 4G Q3 NE 6.1 4G Q3 NE in PTRP configuration 6.2 4G Q3 NE in MSPP configuration 7 Creating and addressing an SNMP NE 7.1 9500MXC 8 Creating and addressing a 4G TL1 NE 8.1 Creating and addressing an 1850TSS 8.2 Creating and addressing an 1830PSS 9 Creating and addressing a Q3 CNA NE 10 Creating and addressing a TL1 NE 11 Creating and addressing a Generic NE 12 NE auto discovery 12.1 NE initiated procedure 12.2 1320CT initiated procedure 12.3 EML procedure for Q3 and 4G NEs 12.4 1830PSS and 9500MPR Auto discovery Procedure 13 Addressing the NEs with “OSI over IP” tunnel 14 Security in ALU networks 3·1·5 COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED. System Operation · NE Creation and Supervision 14.1 RADIUS 1350 OMS EML · R9.6 Operation and Maintenance 14.2 SSH 14.3 SSL 14.4 SNMPv3 14.5 Secure mode


Page 7 11 25 30 41 62 66 68 89 95 101 104 115 131 139 147 154 157 163 168 172 178 188 190 200 208 210 217





Page

1 Introduction




1 Introduction

Network management To create the NEs, start the MS-GUI

1. Select

“Operation Management ” 2. Select Network Management

3. Right click and Start 3·1·8 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance



1 Introduction

System Monitor Check the processes !

Right click and “Start”




1 Introduction

NE Interface Q3 Interface

SNMP/TL1 Interface

OMSN, 1678MCC, 1696MS, 1626LM (R3.0 and earlier), …

SNMP interface: ISA board, 1692MSE, 9500MXC, 9500MPR, …

4G Q3 interface: TSS-320 (R1.x), TSS-40, TSS-3, 1626LM (R4.0x and R5.0x)

4G TL1 interface: 1850TSS, 1830PSS, 1626LM R6.x, 1870TTS …

Q3 CNA interface: 1643AM/AMS, 1645AMC, 1655AMU, …

NSAP OSI address

3 · 1 · 10 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance

TL1 interface: 1675LU, 1665DMX, 1625LX

IP address


CNA: CMISE Network Adapter. CMISE: Common Management Information Service Element. It’s an application (layer 7) protocol of Q3 stack.


2 NE supervision and deletion





Notes It’s possible to supervise an NE only if the NE ... has been created is reachable has been given the address and all the required DCN parameters

The NE creation and reachability are addressed in the following chapters. The NE supervision is addressed in this chapter. Use it after having created the NE.





How to ping an NE Prior to starting supervision, check if the NE is reachable “ping” cares of the DCN parameters: addresses, DCC, LAN interfaces, ... “supervision” cares of the supervision rights, too: OS configuration for Q3 NEs, user ID and password for TL1 NEs, ...

1. Open the NE list 2. Right click the NEs

3. Select “Ping NEs” 3 · 1 · 13 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




How to ping an NE [cont.]

4. Apply. It’s not necessary to select the NEs. 3 · 1 · 14 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


In case of 4G Q3 NE: If the Q3 interface is not reachable, a “Primary interface isolation” critical alarm is issued in Alarm Surveillance. If the SNMP interface is not reachable, a “Secondary interface isolation” critical alarm is issued in Alarm Surveillance. If both the Q3 and the SNMP interfaces are not reachable, a “Node isolation” critical alarm is issued in Alarm Surveillance.

4G EML-IM

EML Coordinator

Q3 Protocol adapter

SNMP Protocol adapter

Q3

SNMP TSS-320 MSPP

Q3 Agent

SNMP Agent

Example of TSS-320 in MSPP configuration



Starting supervision on an NE “Start supervision” starts the management of the selected NE activates alarm collection and configurations

1. From the Network Element List, right click the NE

2. Select “Actions

Supervision Start Supervision



In case of 4G NE, where the element management is performed via both a Q3 (or TL1) agent and an SNMP agent, during the “Set NE Address” phase only one of the two addresses belonging to the NE (NSAP and IP) can be configured by the operator in the EML. The EML is in fact able to discover the missing address during the start supervision procedure. After supervision is started, the “Supervision State” attribute changes from DECLARED to SUPERVISED.



Stopping Supervision “Stop supervision” and “Abort supervision” stops managing the selected NE deactivates alarm collection and configurations “Stop supervision” retrieves collected Performance Monitoring data from NE, if any, before closing the management session (it may take some time), whereas “Abort supervision” (only for Q3 NEs) doesn’t.





Equipment View 1. NE list 2. Select the NE

3. Right-click Search Show Equipment





Node By creating an NE, a Node is created, too the Node is used by NML applications: SDH, PKT, WDM,... the Node can be placed in the Map

Nodes



A Node is a representation of the NE that is composed only by the NE objects that has to do with the transmission management model, that are Ports and Termination Points.



Procedure to delete an NE To delete a non-TL1 NE 1. Stop the NE supervision 2. Remove the Node 3. Delete the NE

To delete a TL1 NE 1. 2. 3. 4.

Stop the NE supervision Remove the Node Unlock the NE Delete the NE





Step 1: Stop the NE supervision 1. Issue the NE List by

“Search EML Network Elements”

2. From the Network Element List, right click the NE and then

“Actions Supervision


...”




Step 2: Remove the Node

1. Open the Node List by

“Search Physical Nodes”

2. From the Node List, right click the Node and then “Actions

Physical Remove”





Step 3: Unlock the NE (for TL1 NEs) 1. You need to know the EML-IM that manages the NE NE list

Select the NE

Actions

Get NE Information

2. Open the EML-IM list Search

Physical


EML Domains




Step 3: Unlock the NE (for TL1 NEs) [cont.] 3. Search for the NEs managed by the EML-IM Select the EML-IM

Search

NEs

4. Unlock the NE Select the NE


Actions

Set unLocked




Step 4: Delete the NE

In the Network Element List, right click the NE and then

“Actions

Delete NE”




3 NSAP address




3 NSAP address

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) AFI

IDI

DFI

ORG

RSD

RD

Area

ID

SEL

1 byte

2 bytes

1 byte

3 bytes

2 bytes

2 bytes

2 bytes

6 bytes

1 byte

xx

xxxx

xx

xxxxxx

0000

xxxx

xxxx

xxxxxxxxxxxx

1D

System ID 00206000163B

1D

AFI 39 39 AFI

380F80000000000000010001 380F IDI

8000000000000001 Organisation ID

0001 Area

00206000163B 1D System ID Selector

Examples of NSAP partitioning

3 · 1 · 26



NSAP: Network Service Access Point IDP: Initial Domain Part AFI: Authority and Format Identifier 39: IDI is an ISO DCC (Data Country Code) (ANSI format) 47: IDI is an ISO6523 ICD (GOSIP format) IDI Initial Domain Identifier example in ISO DCC format 032F Argentina 710F RSA

250F France

826F UK

372F Ireland

380F Italy

840F USA

DSP: Domain Specific Part DFI

DSP Format Identifier

ORG

Organization Name (numeric form)

RSD

Reserved

RD

Routing Domain Identifier

Area

Area Identifier

ID

System Identifier (using the MAC address as the ID field can be useful, but not mandatory)

SEL

NSAP Selector

For further information on NSAP refer to RFC1629.


3 NSAP address

System addressing: NSAP address [cont.] D1

D2 Area

A1

A3

NE System ID

A2

A4 Domain




3 NSAP address

System addressing: NSAP address [cont.] 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 another IS equipment IS-IS between two pieces of IS equipment



Alcatel-Lucent Q3 equipment runs as an Intermediate System (IS) and uses the IS-IS protocol.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. TOS63017_V3.1-SG-R9.6-Ed1 Module 3.1 Edition 1

3 NSAP address

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

Knowledge of the topology of the area and of all level L2 routers in the domain. (Non-pure L2 = L2 + L1 )


L2 Non pure

Level non-pure L2

3 · 1 · 29

L1



4 Creating and addressing a Q3 NE





Procedure Preliminary NE configuration by means of Craft Terminal 1. 2. 3. 4.

Configure Configure Configure Configure

the the the the

Local NE OSI Address (NSAP) OS Address (NSAP of the EML server) in the NE LAPD interface Ethernet interface

EML configuration 5. Check the EML configuration and process status 6. Create the NE 7. Configure the NE address in EML



LAPD (Link Access Procedure on D-channels): supervision protocol that relies on STM-N’s DCC bytes.



Step 1: OSI address of the NE By CT, open the Equipment View and check or configure the NE address. This address will be set in EML, too.

1. Select “Local

Configuration ”

2. NE’s address (NSAP) 3 · 1 · 32



To open the Equipment view from 1320CT: Select the supervised NE into the map Supervision

Show equipment



Step 2: OSI address of the OS First of all, ask the System Administrator for the OS’s NSAP. Then, by CT, open the Equipment View and check or configure it.

1. Select “OS

Configuration”

2. OS’s address (NSAP) 3 · 1 · 33 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


For setting the OS Address in 1678MCC, please refer to the equipment documentation.



Step 3: LAPD configuration By CT, open the Equipment View and check or configure the LAPD. LAPD must be enabled on the STM interfaces.

1. Select “LAPD

Configuration ”

2. LAPD



As far as two connected STM-N interfaces are concerned: “LAPD interface” must be of the same type: MsTTP or RsTTP (OTS or OMS in case of WDM equipment) “LAPD Role” must be different: one interface as “Network” and the other one as “User” Connection Oriented (used to interconnect the NE with Alcatel NE) Connection Less (used to interconnect the NE with not Alcatel NE). When “Connection-less” is used, the Role of the LAPD interface must be set as “Network”. For 4G equipment used as Q3 NE, it’s necessary to configure the Network Protocol, too: choose “OSI”.



Step 4: Ethernet interface configuration By CT, open the Equipment View and check or configure the Ethernet interface.

1. Select “Ethernet

Configuration”


2. “Yes” must be By CT enable the ticked Ethernet if the interface of the NEequipment from the is a Equipment View. Usually is Gatewayit NE necessary in the GNE. Select menu Configuration Comm/Routing Interfaces Configuration Ethernet Configuration Select Yes to enable it Click Apply to confirm any modification and then Close


It is necessary to enable the Ethernet interface only in the gateway NE. In case of pure OSI DCN TMN network, no IP configuration is required.



Step 5: check the EML’s processes RetixStack Emlims: EMLIMADMQ3 for OMSN, 1696MS and 1626LM R3.0A and earlier EMLIMDXCQ3 for OMSG (1678MCC and 1674 LG)

The NE creation form gives the operator the opportunity to select himself a particular EMLIM. From Process Monitoring Control: The suffix of the RetixStack’s sub-processes suggests the Supervision Area name EML domain must be chosen among the “EMLxxxQ3” processes



For the System Administrator: by means of the System Config, configure the following items: A Supervision Area linked to the System’s Ethernet interface (e.g. lan0) A Necom Subsystem associated to this Supervision Area An EMLIM associated to the same Supervision Area: EMLIMADMQ3 for OMSN, 1696MS and 1626LM R3.0A and earlier EMLIMDXCQ3 for 1678MCC and OMSG N.B: Refer to Administrator Guide for details



Step 6: NE creation

1. From the MS-GUI, Select “Create NE”

“Directory” see notes 3 · 1 · 37 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


If the operator doesn’t select the Supervision Area and the EML Domain, the above procedure leads to an automatic choice of the Supervision Area and EML-IM made by the EML. In this case, the system takes into account of each available “EMLIMxxxQ3” EML-IM trying to make their load homogeneous. 1350OMS provides EML Federation: a number of EML instances can run on presentation server, but they are joined in one single application contributions to the operator. The “Directory” field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in which the NE must be created. Normally there is only one EML instance installed in a 1350OMS System; thus, the field is automatically filled with the proper value. If more than one EML instances are present in a Federation, the operator must select the desired PNM GUI Sever from the drop-down list (see the picture below).



Step 7: NE address in EML 1. Retrieve the list of the NEs. Select

“Network Elements”

2. Right click the created NE

3. Select “Set

NE Address”





Step 7: NE address in EML [cont.]

Assign the NSAP written in the Local Configuration menu of the Equipment View (Step 1). Click “OK” or “Apply”



The NE address can be modified only if the NE is not supervised (i.e. its supervision state is “Declared").


Exercise If available on the training platform, declare a Q3 NE. Supervise the NE. Check that the NE is reachable





5 Creating and addressing ISA boards





ISA boards and EML interworking EML SNMP

Q3

EML-IM

EML-IM

DCN DCN

ISA Board


OMSN’s Equipment Controller




Communication between EML and ISA boards OSI DCN

IP+OSI DCN EML

EML

OSI for Q3 IP for SNMP

OSI for Q3 “IP over OSI” for SNMP LAN

LAN

“IP over OSI” tunnel

DCC DCC “IP over OSI” tunnel

The “IP over OSI” tunneling exploited by EML aims at: • Keeping OSI DCN backbones • Fully exploiting the OSI DCN resilience • Supporting SNMP traffic to/from ISA boards with a single e2e tunnel

OMSN OMSN with ISA 3 · 1 · 43



ISA boards (ATM, ES1, ES4, ES16, ES-64, PREA) in the equipment are managed by means of SNMP (Simple Network Management Protocol), which is an application of the TCP/IP reference model. To manage the SDH features of the NE and ISA boards together, it is necessary to encapsulate SNMP messages inside the OSI layers ("IP over OSI tunneling"). In this way the SNMP management information is transported over the existing SDH networks. The OS enters the network management messaging over an Ethernet link (IEEE-802.3 protocol) of a GNE; here the messages are transported over the SDH DCC links by means of the LAPD protocol; at the remote managed nodes, the messages are acknowledged as belonging to: OSI reference model, for SDH management SNMP (IP) reference model for ISA boards management The encapsulation of SNMP messages inside the OSI layers can be carried out by the OS itself: in this case the tunnel end-points are the NE and the OS. The operator must provide the tunneling configuration only in the NEs which are the end-points of the tunnel.

ISA: Integrated Service Adapter DCN: Data Communication Network DCC: Data Communication Channels LAPD: Link Access Procedure on D-channels



Procedure for IP+OSI DCN NE configuration 1. 2. 3. 4.


the the the the

IP address of ISA IP Point-to-Point interface “IP over OSI” tunnel toward another NE IP address of the Ethernet interface into the GNE

EML configuration 1. Check that an “EMLIMCORBASNMP” process has been instantiated in the EML 2. Create the ISA board 3. Create the IP routing in the EML





Procedure for OSI DCN NE configuration 1. 2. 3. 4.


the the the the

IP address of ISA IP Point-to-Point interface “IP over OSI” tunnel toward the EML IP static routing

EML configuration 1. Check that an “EMLIMCORBASNMP”, the “ositunneling” and the “OSI_Manager” processes have been instantiated 2. Create the ISA board 3. Create the “IP over OSI” tunnel toward the OMSN and add the ISA board to the created “IP over OSI” tunnel





Step 1: IP address of ISA Open the Equipment View and check or configure the ISA address. This address will be set in EML, too.

1. Select the ISA board

2. Select

“ISA Board IP Address” 3. IP Address of ISA 3 · 1 · 46 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Step 2: Point-to-Point interface Open the Equipment View and check or configure the IP address of the Point-to-Point interface

1. Select “IP Address

Configuration of PointTo-Point Interfaces”

2. IP Address





Step 3: “IP over OSI” tunnel into the OMSN Open the Equipment View and check or configure the “IP over OSI” tunnels 2. NSAP address of: • EML, in case of OSI DCN • another OMSN, in case of IP+OSI DCN

1. Select “IP

Over OSI”

3. IP Routing: • “None” in case of OSI DCN • “OSPF” in case of IP+OSI DCN





Step 4: (only for OSI DCN) IP static routing Open the Equipment View and check or configure the IP Static Routing 2. Insert the IP Address of the tunnel defined in the EML System configuration (ask the System Administrator)

3. Select “CLNP Tunnel” and select the tunnel whose destination NSAP is the EML’s one 1. Select “IP

Static Routing Configuration ”





Step 5:(only for IP+OSI DCN) Ethernet interface configuration Open the Equipment View of the Gateway NE and check or configure its Ethernet interface 2. IP Address

1. Select “Ethernet

Configuration”





Step 6: check the EML’s processes OSI DCN RetixStack StackServices: ositunneling Emlims: EMLIMCORBASNMP OsiManager

RetixStack

ositunneling

IP+OSI DCN RetixStack Emlims: EMLIMCORBASNMP

EMLIMCORBASNMP

OsiManager 3 · 1 · 51 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


For the System Administrator: by means of the System Config, configure the following items when dealing with a pure OSI DCN: 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 An OSI_MANAGER and an ositunnel associated to the “virtual” Supervision_Area An EMLIMCORBASNMP associated to 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.



Step 7: ISA board creation in EML 1. Select the OMSN that contains the ISA board and right click

2. Actions

Create ISA





Step 7: ISA board creation in EML [cont.]

OMSN

ISA

IP address of ISA EMLIMCORBASNMP Add On Tunnel (only for OSI DCN): - creates the tunnel in the EML - associates the ISA to the tunnel 3 · 1 · 53 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Step 8: (only for OSI DCN) “IP over OSI” tunnel in the EML To double check that the tunnel creation in EML is succesful: 1. Retrieve the Tunnel list: Search EML Tunnel Get IP Over OSI Tunnels

2. Double check that the ISA board is associated to the Tunnel: Select the Tunnel Search Get NEs in Tunnel



Tunnel ID: the System ID of the OMSN’s NSAP



Step 8: (only for OSI DCN) “IP over OSI” tunnel in the EML Instead of creating automatically the tunnel along with the ISA board creation, it’s possible to create manually the tunnel. 1. Create the ISA board 2. Create the Tunnel 3. Associate the ISA board to the Tunnel

Between an NE and EML there’s just one “IP over OSI” Tunnel The Tunnel is exploited for all the NE’s ISA boards





Step 8: (only for OSI DCN) “IP over OSI” tunnel in the EML To create the Tunnel: Actions EML

Tunnel

3 · 1 · 56

Create IP over OSI Tunnel



Gateway Type = Gateway (not the case of OMSN + ISA): it is used to create an IP Over OSI tunnel to an IP based NE to manage NEs connected there after. the list of NEs which support Gateway IP Over OSI are given in this server’s file: /usr/Systems//OSITUN/conf/GatewayNeTypeReleaseDefinition. When this training guide was developed, the suitable NEs were: 1850TSS-320/160: 1.1 – 3.4 1850TSS-100: 1.1 – 3.1 1850TSS-15: 1.0 1850TSS-5: 4.0 – 7.0 1692MSE: 1.4 - 3.5 1696MS: 3.0 1678MCC: 2.0 – 4.5 1830PSS-1: 1.0 – 1.1 Gateway Address: NE’s IP address; automatically filled in. Gateway OSI/NSAP Address: to be populated by the operator.



Step 8: (only for OSI DCN) “IP over OSI” tunnel in the EML To associate the ISA to the Tunnel: 1. Retrieve the Tunnel list: Search EML Tunnel Get IP Over OSI Tunnels

2. Select the Tunnel

Actions

Add IP To Tunnel

see next slide





Step 8: (only for OSI DCN) “IP over OSI” tunnel in the EML





Step 8: (only for OSI DCN) “IP over OSI” tunnel in the EML To delete the Tunnel: 1. Remove the ISA board associated to the Tunnel

2. Delete the Tunnel

It’s possible to delete the Tunnel only if it has no ISA board





Step 9: (only for IP+OSI DCN) IP routing in EML

Dynamic routing

Static routing the UNIX “route” command is used. It allows to declare the network where the ISA boards are located and to declare the relationship with the gateway. route add net netmask 1 route add net 10.10.0.0 netmask 255.255.0.0 151.98.33.87 1


the Open Shortest Path First (OSPF) protocol has been chosen for exchanging the routing information among the routers and the OS servers. It’s a matter of System configuration; ask the System Administrator whether it is enabled.



Exercise If available on the training platform, declare an ISA board. Declare the IP over OSI tunnel





6 Creating and addressing a 4G Q3 NE





Generalities about 1850TSS and 4G Q3 equipment In this chapter it is described how to create and address 4G Q3 equipment. 1850TSS-320 R1.1 and 1.4 1850TSS-40 R4.x 1850TSS-10 R1.0 1850TSS-3 R1.x and 2.x 1626LM R4.0x and 5.0x

This equipment hosts, in the most general model, both a Q3 and an SNMP management agents. The “EMLIM4G” EML-IM process is required. It includes a primary Q3 and a secondary SNMP protocol adapters.

3 · 1 · 63



1850TSS-320 hosts both the Q3 and the SNMP agents. 1850TSS-3 hosts only the SNMP agent. 1626LM hosts only the Q3 agent. The Alcatel-Lucent 1850 Transport Service Switch (TSS) 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 switch that is capable of switching packets and circuits in their native format and transport them as they are. The Alcatel-Lucent 1850TSS comes in several sizes, according to different switching capacities: 1850 TSS-3, TSS-5/5C/5R, TSS-10, TSS-40, TSS-100/100C, TSS-160/160C, TSS-320.



Management of 4G Q3 equipment

Q3 management agent 1850 TSS-320 R1.1/R1.4 as PTRP 1626LM R4.0x/R5.0x

4G Q3 PTRP NE Q3 Agent


Q3 and SNMP management agents 1850 TSS-320 R1.1/R1.4 as MSPP or PTN 1850TSS-40 R4.x

4G Q3 MSPP NE Q3 Agent

SNMP Agent


The 1850 TSS-320 can be configured in three different flavors, based on the offered transport capabilities: Pure TRansport Platform (PTRP), providing pure TDM and WDM transport capability Multi-Service Provisioning Platform (MSPP), providing the capability of integrating transport of TDM and data traffic Full Data or Packet Transport NE (PTN), providing only data traffic capability PTRP (Pure TRansport Platform): TDM and WDM transport capability MSPP (Multi-Service Provisioning Platform): transport of TDM and data traffic PTN (Packet Transport NE) or Full Data: only data traffic capability



Management of 4G Q3 equipment

EML Coordinator

4G EML-IM SNMP Protocol adapter

Q3 Protocol adapter Q3

SNMP 4G Q3 NE

Q3 Agent


SNMP Agent



6.1 4G Q3 NE in PTRP configuration




6.1 4G Q3 NE in PTRP configuration

Creating a 4G Q3 NE in PTRP Configuration

EML Coordinator

Q3 Protocol adapter

4G EML-IM


Q3 Q3 4G Q3 NE PTRP Agent

An “EMLIM4G” must be chosen as EML-IM



In this configuration, only the Q3 communication session needs to be established between the EML and the NE. Therefore, a Q3 DCN is needed in order to manage the equipment.


6.2 4G Q3 NE in MSPP configuration





Q3 and SNMP sessions TSS equipment case 4G EML-IM

EML Coordinator

Q3 Protocol adapter Q3

Q3 Agent


SNMP Protocol adapter SNMP

SNMP Agent




OSI DCN When a pure OSI DCN is available, the SNMP management session must run over an “IP over OSI” tunnel configured between the EML and the NE. 4G EML-IM EML Coordinator

EML Q3 Protocol adapter


IP over OSI Tunnel

OSI DCN

SNMP session (IP traffic) IP over OSI tunnel (it encapsulates IP traffic in OSI traffic) Q3 session


Q3 Agent

SNMP Agent

TSS-320 MSPP




OSI+IP DCN When an OSI/IP DCN is available, both the Q3 and the SNMP management sessions can contemporarily run over the same network infrastructure.

EML Coordinator

4G EML-IM

Q3 Protocol adapter

OSI/IP DCN SNMP session (IP traffic) Q3 session (OSI traffic) 3 · 1 · 71 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance



Q3 Agent

SNMP Agent

TSS-320

TSS-3 TSS-320


IP over OSI tunnel OSI DCN

IP+OSI DCN EML

OSI for Q3 IP for SNMP

EML

OSI for Q3 “IP over OSI” for SNMP LAN

LAN



DCC DCC supporting OSI + “IP over OSI” tunnel

DCC DCC supporting OSI

O R

DCC supporting OSI+IP





Procedure for OSI+IP DCN NE configuration by means of Craft Terminal: 1. 2. 3. 4. 5.

Configure Configure Configure Configure Configure

the the the the the

Local NE OSI address (NSAP) Local NE IP address LAPD interfaces OS address in the NE Ethernet interface

EML configuration 1. Check the EML configuration and processes status 2. Create the NE 3. Set the address(es) of the created NE





Procedure for OSI DCN NE configuration by means of Craft Terminal: 1. 2. 3. 4. 5. 6. 7.

Configure Configure Configure Configure Configure Configure Configure

the the the the the the the

Local NE OSI address (NSAP) Local NE IP address LAPD interfaces OS address in the NE Ethernet interface “IP over OSI” tunnel toward the EML IP static routing

EML configuration: 1. 2. 3. 4.

Check the EML configuration and processes status Create the NE Set the address(es) of the created NE Create the “IP over OSI” tunnel toward the NE and add the NE to the created “IP over OSI” tunnel

3 · 1 · 74



In case of OSI DCN, check that: an ositunneling process has been instantiated in the System Configuration. An EML-IM (EMLIM4G_xxx) linked to the 4G Q3 NE has been instantiated and associated to a “primary and a “virtual” supervision area in the System Configuration. Check with the system administrator. The same ositunneling process instance can support more than one tunnel towards different NEs. It means that with a single ositunneling process, different 4G Q3 NE can be supervised.



Step 1: OSI address of the NE By CT, open the Equipment View and check or configure the NE NSAP address. This address will be set in EML, too. 1. Select “Local

Configuration OSI Configuration”

2. NE’s OSI address (NSAP) 3 · 1 · 75 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Step 2: IP address of the NE By CT, open the Equipment View and check or configure the NE IP address. This address will be set in EML, too. 1. Select “Local Configuration

IP Configuration”

2. NE’s IP address





Step 3: LAPD configuration By CT, open the Equipment View and check or configure the LAPD. LAPD must be enabled on the STM-N interfaces.

1. Select “LAPD

Configuration” 2. LAPD



As far as two connected STM-N interfaces are concerned: “LAPD interface” must be of the same type: MsTTP or RsTTP “LAPD Role” must be different: one interface as “Network” and the other interface as “User” “Network Protocol”: Choose OSI in case of OSI DCN Choose “IP and OSI” in case of “OSI+IP” DCN “IP and OSI” option is valid also in case of OSI DCN



Step 3: LAPD configuration [cont.]

In case of OSI DCN:

“OSI” In case of “OSI+IP” DCN (also valid in case of “OSI” DCN): • “OSI and IP” • “IntegrIS-IS”





Step 4: OSI address of the OS First of all, ask the System Administrator for the OS’s NSAP. Then, by CT, open the Equipment View and check or configure the OS address.

1. Select “OS

Configuration”

2. OS’s address (NSAP) 3 · 1 · 79 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Step 5: Ethernet interface configuration 2. “Yes” must be ticked 3. Network Protocol … …”OSI”, in case of OSI DCN …”OSI and IP”, in case of IP+OSI DCN 1. Select “Ethernet

Configuration”

4. Only in case of IP+OSI DCN: • set the IP address • tick “IntegrIS-IS” 3 · 1 · 80 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Step 6: (only for OSI DCN) “IP over OSI” tunnel in the NE Open the Equipment View and check or configure the “IP over OSI” tunnels

2. NSAP address of the EML

1. Select “IP

Over OSI”





Step 7: (only for OSI DCN) IP static routing Open the Equipment View and check or configure the IP Static Routing

2. Insert the IP Address of the tunnel defined in the EML System configuration (ask the System Administrator)

3. Select “CLNP Tunnel” and select the tunnel whose destination NSAP is the EML’s one 1. Select “IP Static

Routing Configuration”





Step 8: check the EML’s processes OSI DCN RetixStack RetixStack StackServices: ositunneling Emlims: EMLIM4G OsiManager ositunneling IP+OSI DCN RetixStack Emlims: EMLIM4G EMLIM4G

OsiManager 3 · 1 · 83 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


For the System Administrator: by means of the System Config, configure the following items: OSI+IP DCN A Supervision_Area linked to the System Ethernet interface (e.g. lan0) A Necom_SubSystem associated to this Supervision_Area An EMLIM4G associated to the same Supervision_Area OSI DCN 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 An OSI_MANAGER An ositunnel associated to the “virtual” Supervision_Area An 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.



Step 9: NE creation

“Directory” see notes

1. Select

“Create NE”

They depend on the instantiated processes



By leaving “Supervision Area” equal to “Not Specified”, the EML carries out an automatic choice of the Supervision Area and EML-IM. In this case, the system takes into account of each available “EMLIM4G” EML-IM trying to make their load homogeneous. 1350OMS provides EML Federation: a number of EML instances can run on presentation server, but they are joined in one single application contributions to the operator. The “Directory” field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in which the NE must be created. Normally there is only one EML instance installed in a 1350OMS System and the field is automatically filled with the proper value. If more than one EML instances are present in a Federation, the operator must select the desired PNM GUI Sever from the drop-down list (see the picture below).



Step 10: NE address(es) in EML

1. Retrieve the list of the NEs. Select

“Network Element” 2. Right click the NE 3. Select “Actions

Set NE Address” 3 · 1 · 85 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Step 10: NE address(es) in EML [cont.]



UDP Port is always 161 (SNMP)



Step 11: (only for OSI DCN) “IP over OSI” tunnel in the EML Refer to “5 Creating and addressing ISA boards” chapter




Exercise If available on the training platform, create and address a 4G Q3 NE





7 Creating and addressing an SNMP NE





Procedure Preliminary NE configuration by means of Craft Terminal The IP addresses of the local NE (normally, the DCN interface address and the NE address) must be configured, along with the routing settings necessary to make the NE reachable by the EML Please refer to the specific NE documentation for information about the local NE address configuration procedures

EML configuration 1. If needed, configure the routing settings necessary to make the NE reachable by the EML 2. Check the EML configuration and process status 3. Create the NE 4. Configure the NE address in EML





Step 2: check the EML’s processes

A Supervision_Area linked to the System Ethernet interface (e.g. lan0) An EMLIMCORBASNMP associated to the same Supervision_Area

EMLIMCORBASNMP 3 · 1 · 91 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Step 3: NE creation “Directory” See Notes

1. Select “Create NE”



If the operator doesn’t select the Supervision Area and the EML Domain, the above procedure leads to an automatic choice of the Supervision Area and EML-IM made by the EML. In this case, the system takes into account of each available “EMLIMCORBASNMP” EML-IM trying to make their load homogeneous. Be careful to check that the selected EML-IM is suitable for IP DCN, that is to say it must be associated to a Supervision Area belonging to the System Ethernet Interface 1350OMS provides EML Federation: a number of EML instances can run on presentation server, but they are joined in one single application contributions to the operator. The “Directory” field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in which the NE must be created. Normally there is only one EML instance installed in a 1350OMS System and the field is automatically filled with the proper value. If more than one EML instances are present in a Federation, the operator must select the desired PNM GUI Sever from the drop-down list (see the picture below).



Step 4: NE address in EML 1. Retrieve the list of the NE. Select

“Network Element”

2. Right click the NE 3. Select “Actions

Set NE Address”






Write the IP address of the NE and the UDP port dedicated to SNMP (161)



The NE address can be modified only if the NE is not supervised (i.e. in the “Declared" state).


7.1 9500MXC




7.1 9500MXC

Prerequisites 9500MXC NE can be created and correctly supervised only if the following processes have been configured and are running on the EML System: A Supervision_Area linked to the System Ethernet interface (e.g. lan0) A 9500MXC EMLIM associated to the same Supervision_Area

Check the correct configuration and process status with the System Administrator



Please refer to the specific NE documentation for information about the local NE address configuration procedures.


7.1 9500MXC

NE creation “Directory” see notes

1.Select

“Create NE”



If the operator doesn’t select the Supervision Area and the EML Domain, the above procedure leads to an automatic choice of the Supervision Area and EML-IM made by the EML. In this case, the system takes into account of each available “9500MXC” EML-IM trying to make their load homogeneous. Be careful to check that the selected EML-IM is suitable for IP DCN, that is to say it must be associated to a Supervision Area belonging to the System Ethernet Interface. 1350OMS provides EML Federation: a number of EML instances can run on presentation server, but they are joined in one single application contributions to the operator. The “Directory” field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in which the NE must be created. Normally there is only one EML instance installed in a 1350OMS System and the field is automatically filled with the proper value. If more than one EML instances are present in a Federation, the operator must select the desired PNM GUI Sever from the drop-down list (see the picture below).


7.1 9500MXC

NE address in EML 1. Retrieve the list of the NE. Select “Network

Element”

2. Right click the NE

3. Select “Action

Set NE Address”




7.1 9500MXC

NE address in EML [cont.]

Write the IP address of the NE and the UDP port (161) dedicated to SNMP



The NE address can be modified only if the NE is not supervised (i.e. in the "declared" state).


Exercise If available on the training platform, create and address a SNMP NE





8 Creating and addressing a 4G TL1 NE





Overview

Some NEs that are managed by EML via the SNA EML-IM processes are: 1646SM/C 1830PSS-1, 1830PSS-4, 1830PSS-16, 1830PSS-32 1850TSS-5, 1850TSS-100, 1850TSS-160, 1850TSS-320 R3/R4 1870TTS

Both the TL1 and the SNMP management models run over an IP network layer. So, an IP DCN is needed to supervise 4G TL1 NEs. If OSI protocol is enabled in the NE, the NSAP of the NE must be a valid address





Overview [cont.] The new releases of some types of NEs support the security management. 1850TSS-100, from R3.2 1850TSS-320, from R4.0 1830PSS, from R3.5.2

Security is configured in the “Set NE address” window if the NE supports security, the window provides its configuration if the NE doesn’t support security, the window doesn’t provide its configuration.

For details about security, refer to the last chapter of this student guide’s module: “14 Security in ALU networks”




8.1 Creating and addressing an 1850TSS





Procedure Preliminary NE configuration by means of Craft Terminal (ZIC) The SID (Source IDentifier) of the Local NE must be configured (see notes) The IP addresses of the local NE (usually the DCN interface address and the NE address) must be configured, along with the routing settings necessary to make the NE reachable by the EML Please refer to the specific NE documentation for details about the local NE configuration procedures

EML configuration 1. If needed, configure the routing settings necessary to make the NE reachable by the EML 2. Check the EML configuration and process status 3. Create the NE 4. Configure the NE address in EML



SID (or TID – Target IDentifier) is a string of up to 32 (for ETSI) or 20 (for ANSI) non case-sensitive alphanumeric characters, including the hyphen (-) character, or a quoted string of up to 32 (for ETSI) or 20 (for ANSI) characters, including any special character. If it is a non-quoted string, SID (or TID) must start with a letter and end with an alphanumeric character. Consecutive hyphens (-) shall not be allowed. Number of hyphens shall not be greater than four.



Preliminary NE configuration by ZIC: SID

1850TSS-100

System

DB backup & SID

1850TSS-320

System Management DB Management Set Site Identifier





Preliminary NE config. by ZIC: IP addresses – 1850TSS-100 Commu. Local address NE’s IP address

LAN’s IP address





Preliminary NE config. by ZIC: IP addresses – 1850TSS-320 Communication IP Address

Communication LAN manag


DCN Phys. If

NE’s IP address

DCN Phys. If LAN’s IP address




Step 2: check the EML’s processes

A Supervision_Area linked to the System Ethernet interface (e.g. lan0) An “EMLIMSNA” associated to the same Supervision_Area

EMLIMSN A






1. Select

”Create NE”



If the operator doesn’t select the Supervision Area and the EML Domain, the above procedure leads to an automatic choice of the Supervision Area and EML-IM made by the EML. In this case, the system takes into account of each available “EMLIMSNA” EML-IM trying to make their load homogeneous. 1350OMS provides EML Federation: a number of EML instances can run on presentation server, but they are joined in one single application contribution to the operator. The “Directory” field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in which the NE must be created. Normally there is only one EML instance installed in a 1350OMS System and the field is automatically filled with the proper value. If more than one EML instances are present in a Federation, the operator must select the desired PNM GUI Sever from the drop-down list (see the picture below).



Step 4: NE address in EML

1. Retrieve the list of the NEs. Select “Network

Elements”







Assign the address of the TL1 (primary) interface in the format: IP Address:TL1 Port (3082 or 3083). The TL1 port is not mandatory. The Primary User ID and Password must match what configured in the NE (see next slide for details) Leave the “GNE Flag” (*) and the “FTAM” (**) parameters to their default values The TID must be equal to the SID configured in the NE (***)

It is shown only if the NE supports SSH2 3 · 1 · 112



(*) The “GNE Flag” enables a TL1 command line interface operator to act on a Remote NE (RNE) through a Telnet access to the Gateway NE (GNE). This feature is applicable only to the ANSI environment. (**) Il the “FTAM” parameter is set to “Use GW”, the NE under creation can be used as a repository to download the SW to its Remote NE. This feature will be available in future releases. (***) TID = Target IDentifier (i.e. the NE identifier used in the messages exchanged between the NE and the EML). It must be equal to the “Source IDentifier” (SID) set into the NE. SID (or TID) is a string of up to 32 (for ETSI) or 20 (for ANSI) non case-sensitive alphanumeric characters, including the hyphen (-) character, or a quoted string of up to 32 (for ETSI) or 20 (for ANSI) characters, including any special character. If it is a non-quoted string, SID (or TID) must start with a letter and end with an alphanumeric character. Consecutive hyphens (-) shall not be allowed. Number of hyphens shall not be greater than four. The NE address can be modified only if the NE is not supervised (i.e. in the "declared" state). SNMP address setting is not required.




It’s possible to select the key if SSH2 has been enabled in the previous window





Primary User ID



“Primary User ID” must match a user defined in the NE. Make sure that it has been configured in the NE with the “NOTMOUT” parameter enabled, that means that the user session inactivity timeout is not taken in account for that user. If not, after the expiration of the session inactivity timeout the NE status will switch to: “Communication state” = Unreachable “NE Reachability” = Unreachable leading to the NE isolation. Also, make sure that “Primary User ID” configured in the NE is dedicated to the 1350OMS access. Please refer to the Equipment training documentation for details about the user account configuration procedures.


8.2 Creating and addressing an 1830PSS





Procedure Preliminary NE configuration by means of Craft Terminal The SID (System IDentifier) of the Local NE must be configured. The following IP addresses must be configured in the NE: OAMP address and Loopback IP address (together with their subnet masks) in case of Gateway NE The OAMP port must be set to “enabled”: this is the NE port that is connected to the DCN The OSPF Routing for the OAMP port must be set to “enabled” or “redistribute” (see notes)

Loopback IP address (together with its subnet mask) in case of Remote NE Configuring the Loopback IP address allows the Remote NEs to be reachable by the 1350OMS

All the necessary routing settings must be configured for assuring the network reachability.

EML configuration 1. If needed, configure the routing settings necessary to make the NE reachable from the EML 2. Check the EML configuration and process status 3. Create the NE 4. Configure the NE address in EML



SID (or TID – Target IDentifier) is a string of up to 32 (for ETSI) or 20 (for ANSI) non case-sensitive alphanumeric characters, including the hyphen (-) character, or a quoted string of up to 32 (for ETSI) or 20 (for ANSI) characters, including any special character. If it is a non-quoted string, SID (or TID) must start with a letter and end with an alphanumeric character. Consecutive hyphens (-) shall not be allowed. Number of hyphens shall not be greater than four. Set to redistribute if you don’t want the IP routing table of the Gateway NE not to be advertised externally.



Preliminary NE configuration: check the SID Access to the local NE by Internet Explorer. In the “System” tag, check that a valid Network Element Name (SID) has been given to the NE (check the site documentation)





Preliminary NE configuration: Loopback IP address 1. In the resource tree, select the “System” tag


2. Assign the Loopback IP address and subnet mask (check the site documentation)




Preliminary NE configuration: OAMP Address 1. In the resource tree, select the “OAMP” tag expanding the “USRPNL”


2. Assign the OAMP IP address and subnet mask (check the site documentation). Enable the port by ticking on the “Port Enabled” box.




Preliminary NE configuration: OSPF settings of the OAMP Port 1. In the resource tree, select the “OAMP” tag expanding the “USRPNL”


2. Assign the OSPF parameters as recommended by the network administrator




Preliminary NE configuration: IP routes 1. Select “Networking IP Routes” to open the related window. “OSPF Areas” is for OSPF configuration, if automatic routing is required.

2. Assign the OAMP IP address and subnet mask. Enable the port by ticking on the “Port Enabled” box 2. Click on “Create” to create IP static routes (check the site documentation)





Network reachability: connectivity details Optical Supervisory Channel (OSC) Connectivity Uses 1510 nm optical channel, multiplexed onto C-Band traffic channels by OSC module on amplifier card Provides ~100 Mbps connection between NEs NE runs OSPF on OSC interfaces so that full management connectivity will be maintained during fiber cut

Gateway Network Element (GNE) Connectivity

DCN

Inter -NE Communication (OSC)

IP

Static Route via DCN

1350OMS

An NE that connects to a customer data network through its OAMP port Uses Ethernet cables A default route must be configured between the NE and the neighbor router


OSPF Routing




Network reachability: connectivity options – Example 1 1.

Direct connection through the OAMP LAN port Each NE is connected to the management network through the OAMP LAN port The OAMP LAN port supports 10/100 and auto-negotiates accordingly Configure the following attributes on each NE: • OAMP IP address • OAMP IP address mask • Default router IP address Client PC


1350OMS Server



Client PC


Network reachability: connectivity options – Example 2 2.

Single GNE with static route One NE selected as the gateway (GNE) • 1350OMS access via the GNE • OSC for inter-NE communications Gateway NE configuration • OAMP IP address and mask • Default route (which is redistributed) • NE loopback IP address and mask Configuration of other NEs • NE loopback IP address and mask Router configuration • static route for the NE loopback IP address subnet

Client PC Client PC

1350OMS Server

Router

Management Network

Router

Node1

Node3

Node2





Network reachability: connectivity Example

1350OMS Server Router 152.148.66.xxx 152.148.66.xxx

CIT Port

Node Loopback IP Addresses

172.16.0.1

10.10.0.3

10.10.0.2 GNE Router 152.148.66.xxx

PhM Servr Node #3

Node #2

DHCP-assigned (typically 172.16.0.2)

Local Craft PC: Web / CLI

PC Client DCN Router(s)

PC Client 152.148.66.xxx

Node #1

OAMP Port 152.148.66.xxx

Node #4

OSC Connectivity

Node #5

10.10.0.4

10.10.0.1

10.10.05 Node Loopback IP Addresses





Procedure Step 2: check the EML’s processes

A Supervision_Area linked to the System Ethernet interface (e.g. lan0) An “EMLIMSNA” associated to the same Supervision_Area

EMLIMSN A





Procedure Step 3: NE creation Family = “OTN” Type = “1830PSS-x”

1. Select

”Create NE”



If the operator doesn’t select the Supervision Area and the EML Domain, the above procedure leads to an automatic choice of the Supervision Area and EML-IM made by the EML. In this case, the system takes into account of each available “EMLIMSNA” EML-IM trying to make their load homogeneous. 1350OMS provides EML Federation: a number of EML instances can run on presentation server, but they are joined in one single application contribution to the operator. The “Directory” field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in which the NE must be created. Normally there is only one EML instance installed in a 1350OMS System and the field is automatically filled with the proper value. If more than one EML instances are present in a Federation, the operator must select the desired PNM GUI Sever from the drop-down list (see the picture below).



Procedure Step 4: NE address in EML


“Network Elements” 2. Right click the NE 3. Select “Actions





Procedure Step 4: NE address in EML [cont.]

Assign the address of the TL1 (primary) interface in the format: IP Address:TL1 Port (3082 or 3083). The TL1 port is not mandatory. The Primary User ID and Password must match what configured in the NE. Leave the “GNE Flag” (*) and the “FTAM” (**) parameters to their default values

The TID must be equal to the SID configured in the NE (***)

3 · 1 · 129



(*) The “GNE Flag” enables a TL1 command line interface operator to act on a Remote NE (RNE) through a Telnet access to the Gateway NE (GNE). This feature is applicable only to the ANSI environment. (**) Il the “FTAM” parameter is set to “Use GW”, the NE under creation can be used as a repository to download the SW to its Remote NE. This feature will be available in future releases. (***) TID = Target IDentifier (i.e. the NE identifier used in the messages exchanged between the NE and the EML). It must be equal to the “System IDentifier” (SID) set into the NE SID (or TID) is a string of up to 32 (for ETSI) or 20 (for ANSI) non case-sensitive alphanumeric characters, including the hyphen (-) character, or a quoted string of up to 32 for ETSI (20 for ANSI) characters, including any special character. If it is a non-quoted string, SID (or TID) must start with a letter and end with an alphanumeric character. Consecutive hyphens (-) shall not be allowed. Number of hyphens shall not be greater than four. The NE address can be modified only if the NE is not supervised (i.e. in the "declared" state). SNMP address setting is not required.


Exercise If available on the training platform, create and address a 4G TL1 NE





9 Creating and addressing a Q3 CNA NE




9 Creating and Addressing a Q3 CNA NE

Overview In this chapter it is described how to create and address the “Metropolis” Q3 equipment (from the former Lucent portfolio), that are: 1643AM/AMS, 1645AMC, 1655AMU

A specific EML-IM, called CNA, is required to manage this kind of equipment. The user can find it in the process management window under the name “EMLIMCNA”. An OSI DCN is required to manage the Q3 CNA NEs.

CNA: CMISE Network Adapter CMISE: Common Management Information Service Element. It’s an application (layer 7) protocol of Q3 stack.





Procedure Preliminary NE configuration by means of Craft Terminal Please refer to the specific NE documentation for information about the local NE configuration procedures






Step 1: check the EML’s processes A Supervision_Area linked to an “ATOS” OSI stack This Supervision_Area must be linked to a dedicated System Ethernet interface, physically different from any other System Ethernet interface already used by other Supervision Areas An EMLIMCNA associated to the same Supervision_Area The configuration of a single EMLIMCNA process automatically generates four EML Domains of the same type to be instantiated. Each of these instances manages a specific group of NE(*). See the administration guide for details.

EMLIMCNA 3 · 1 · 134 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


For the System Administrator: When instantiating the EMLCNA process, make sure that its label ends up with “93”. In the EML Domains List, 4 EML Domains of the CNA type, linked to an “ATOS” supervision area, must be found, their identifier ending up with “93”, “94”, “95” and “96”. (*) For example, the EML Domain “*95” can manage the 1643AM/AMS and the 1645AMC NE, while the EML Domain “*96” can manage the 1655AMU.




1. Select “Create NE” Leaving “Supervision Area” and “Eml Domain” unspecified, the system will automatically choose the correct values among the configured processes



1350OMS provides EML Federation: a number of EML instances can run on presentation server, but they are joined in one single application contributions to the operator. The “Directory” field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in which the NE must be created. Normally there is only one EML instance installed in a 1350OMS System and the field is automatically filled with the proper value. If more than one EML instances are present in a Federation, the operator must select the desired PNM GUI Sever from the drop-down list (see the picture below).



Step 2: Set the NE address 1. Retrieve the list of the NEs. Select “Network

Element”

2. Right click the NE


Set NE Address”





Step 2: Set the NE address [cont.] Assign the OSI NSAP address of the configured NE

“NSAP Selector” = 01





Exercise If available on the training platform, create and address a Q3 CNA NE





10 Creating and addressing a TL1 NE




10 Creating and Addressing a TL1 NE

Overview In this chapter it is described how to create and address the “Metropolis” 1665DMX and 1675LU (from the former Lucent portfolio) and the terrestrial WDM equipment 1626LX (from the former Lucent portfolio, too). This equipment is managed by the “TNA” EML-IM process. An IP DCN is required to manage the “Metropolis” TL1 equipment.

TNA: TL1 Network Adapter 3 · 1 · 140 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Procedure Preliminary NE configuration by means of Craft Terminal Please refer to the specific NE documentation for information about the local NE configuration procedures






Step 1: check the EML’s processes A Supervision Area linked to the system Ethernet interface An “EMILMTNA” process associated to the same supervision area

EMLIMTNA



Please refer to the 1350OMS-EML System Administration Guide for details about the System Configuration.




1. Select

”Create NE”



If the operator doesn’t select the Supervision Area and the EML Domain, the above procedure leads to an automatic choice of the Supervision Area and EML-IM made by the EML. In this case, the system takes into account of each available “EMLIMTNA” EML-IM trying to make their load homogeneous. 1350OMS provides EML Federation: a number of EML instances can run on presentation server, but they are joined in one single application contributions to the operator. The “Directory” field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in which the NE must be created. Normally there is only one EML instance installed in a 1350OMS System and the field is automatically filled with the proper value. If more than one EML instances are present in a Federation, the operator must select the desired PNM GUI Sever from the drop-down list (see the picture below).



Step 3: Set the NE address in EML


“Network Elements” 2. Right click the NE 3. Select “Actions

Set NE Address”





Step 3: Set the NE address in EML [cont.]

Assign the address of the TL1 (primary) interface in the format: IP Address:TL1 Port (3082 or 3083). The TL1 port is not mandatory. The Primary User ID and Password must match what configured in the NE. Leave the “GNE Flag” (*) and the “FTAM” (**) parameters to their default values

The TID must be equal to the SID configured in the NE (***)

3 · 1 · 145



(*) The “GNE Flag” enables a TL1 command line interface operator to act on a Remote NE (RNE) through a Telnet access to the Gateway NE (GNE). This feature is applicable only to a ANSI environment. (**) Il the “FTAM” parameter is set to “Use GW”, the NE under creation can be used as a repository to download the SW to its Remote NE. This feature will be available in future releases. (***) TID = Target IDentifier (i.e. the NE identifier used in the messages exchanged between the NE and the EML). It must be equal to the “System IDentifier” (SID) set into the NE SID (or TID) is a string of up to 32 (for ETSI) or 20 (for ANSI) non case-sensitive alphanumeric characters, including the hyphen (-) character, or a quoted string of up to 32 for ETSI (20 for ANSI) characters, including any special character. If it is a non-quoted string, SID (or TID) must start with a letter and end with an alphanumeric character. Consecutive hyphens (-) shall not be allowed. Number of hyphens shall not be greater than four. The NE address can be modified only if the NE is not supervised (i.e. in the "declared" state). SNMP address setting is not required.


Exercise If available on the training platform, create and address a TL1 NE





11 Creating and addressing a Generic NE





Overview The “Generic NE” is used to manage 3rd party equipment that are boxes managed in a light fashion, meaning: Alarms can be shown Ports can be created to terminate Physical Connections, but have no relationships with the real ports inside the equipment

A typical example of Generic NE is the external Raman Pump used in 1830PSS-32, R2.0 and later. Preliminary NE configuration by means of Craft Terminal The IP addresses of the 3rd party equipment must be configured, together with the routing settings necessary to make the NE reachable by the EML Please refer to the specific equipment documentation for information about the local NE address configuration procedures

EML configuration 1. If needed, configure the routing settings necessary to make the NE reachable by the EML 2. Check the EML configuration and process status 3. Create the NE 4. Configure the NE address in EML 3 · 1 · 148 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Step 2: check the EML’s processes A Supervision_Area linked to the System Ethernet interface (e.g. lan0) An EMLIMSGM or an EMLIMCORBASNMP (depending on the 3rd party equipment) associated to the same Supervision_Area

EMLIMCORBASNMP or EMLIMSGM 3 · 1 · 149 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Step 3: NE creation In case of external Raman Pump for the 1830PSS, select the Parent PSS NE and its location

1. Select “Create NE”

“Directory” See Notes



If the operator doesn’t select the Supervision Area and the EML Domain, the above procedure leads to an automatic choice of the Supervision Area and EML-IM made by the EML. In this case, the system takes into account of each available “EMLIMCORBASNMP” or “EMLIMSGM” EML-IMs trying to make their load homogeneous. Be careful to check that the selected EML-IM is suitable for IP DCN, that is to say it must be associated to a Supervision Area belonging to the System Ethernet Interface. 1350OMS provides EML Federation: a number of EML instances can run on presentation server, but they are joined in one single application contributions to the operator. The “Directory” field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in which the NE must be created. Normally there is only one EML instance installed in a 1350OMS System and the field is automatically filled with the proper value. If more than one EML instances are present in a Federation, the operator must select the desired PNM GUI Sever from the drop-down list (see the picture below).



Step 4: NE address in EML 1. Retrieve the list of the NEs. Select “Network

Element”


Set NE Address”






Write the IP address of the NE and the UDP port (161) dedicated to SNMP





Exercise If available on the training platform, create a generic NE





12 NE auto discovery





Principles NE auto discovery is a feature that makes automatic the procedure of creating a new NE in the EML database. The NEs must be reachable by EML NE’s DCN parameters already configured

There are three procedures, according to the NE type the NE initiated procedure available for 4G Q3 and 4G TL1 NEs. the 1320CT initiated procedure for Q3 NEs and ISA boards. the procedure fully managed by the 1350OMS, available for 1830PSS and 9500MPR.

NE auto discovery procedure (bottom-up) is anyway compatible with the traditional top-down method, where new NEs are manually created on EML.



NE auto discovery is available for ISA boards, too.



Principles [cont.] The discovery messages pass the following information: NE type & release NE name and location NE address OS address (if relevant)

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 EML. Since the messages go through the NE, they exploit the same DCN routes available to EML for supervising the NE.




12.1 NE initiated procedure





CT perspective

ACK

DCN New NE! 1320CT’s USM or ZIC


EML


In case of 4G Q3 or 4G TL1 NEs, the auto discovery function is directly exploited by the NE itself. The USM/ZIC provides the “Auto discovery” option, which triggers the discovery message directly from the NE to the EML.



What to do on NE (4G Q3 NE) 1. Trigger the auto discovery procedure by issuing

“Configuration Management Auto Discovery”





What to do on NE (4G Q3 NE) [cont.] 2. Issue “Auto

Discovery”=“enable”

3. Click “OK”

4. Click “Cancel” to close the window

5. Open again the Auto Discovery window: the Status is now

“succeeded” 6. With “Auto

Discovery”=“disable”, click OK to stop the procedure, then “Cancel”





What to do on NE (4G TL1 NE, e.g. 1850TSS-320) 1. From the local terminal, issue

“Communication Network Domain OSI Mng OSI OS Address”

2. Select “IP” (or OSI) as Operating System, and insert the IP (or OSI) address of the 1350OMS server



In this and the following slides, an example is given on how to trigger the auto discovery procedure from an 1850TSS-320 NE. For other NEs belonging to the 4G TL1 (SNA) family, please refer to the specific equipment documentation.



What to do on NE (4G TL1 NE, e.g. 1850TSS-320) [cont.] 3. Issue “Communication

NE Autodiscovery”

4. Choose “Y” in the “ENABLED” box and the click on

“Save”

5. Open again the Autodiscovery window: the Status is now

“SUCCEEDED”




12.2 1320CT initiated procedure





CT Perspective In-field engineers get the result of the auto discovery procedure DISCOVERY OK the auto discovery message has been ack-ed by EML; NOC team is now informed DISCOVERY KO the auto discovery message has not been ack-ed by EML Time-out expiration: EML not available or DCN not OK Message refused by EML: NE Type&Rel. unknown, duplicated NE address, etc

ACK

DCN 1320CT


New NE!

EML


For Q3 NEs and ISA boards, the 1320CT provides a function dedicated to NE auto discovery. NE address is retrieved from the NE configuration; the list of target EML is based on a list of platform names (offline edit) to avoid the manual set-up of the OS address for every NE.



What to do on CT

2. Select “NMs address

config”

1. Select “NE

Autodiscovery” or “NEAD Update”



Warning: The NE Auto discovery feature is available on the CT starting from CT-K Rel 3.3



CT initiated procedure: What to do on CT [cont.]

1. Insert the OS name 2. Insert the address of the OS

AD

3. Do “Add”

4. The OS is put in the list



The last two digits (NSAP selector) of the OS OSI address must be “AD”.



CT initiated procedure: What to do on CT [cont.] 6. STATE changes into

“sent successfully” 3. Select the OS 2. Select the NE 4. It’s possible to change the Location name 5. Do

“Send”

1. Select “NEAD Update” 3 · 1 · 167 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance



12.3 EML procedure for Q3 and 4G NEs





What to do on EML 1.

On receipt of the NE auto discovery message coming from the NE, the Alarm Management application generates a Warning alarm.

2.

Then, the operator must navigate from the auto discovery alarm to

“CreateNE”. 3.

The “Create NE Dialog” window is presented to the operator.





What to do on EML [cont.]

2. Select the warning and click on 1. In the Alarm management Application, select the

“External Applications CreateNe”

“NE Auto Discovery” Sublist





What to do on EML [cont.]

2. Optionally, the operator can modify the “NE name” or the

1. Click on The auto discovered NE selected in the previous view

“Location name” 3. Choose or leave unspecified Supervision Area and EML domain

4. Click on Create

The NE can also be refused




12.4 1830PSS and 9500MPR Auto discovery Procedure





Procedure Prerequisites: The Gateway NE must be manually created and supervised in EML. The Remote NEs to be discovered must be reachable by EML.

Procedure: 1. In the NE List, select the Gateway NE, right click and issue “Actions Discover NE”: the Discover NE Wizard is opened. 2. Optionally enter a filtering criteria in terms of a list of IP Address/IP Mask pairs. 3. Click “Next” and trigger the “Get Auto Discovered NE” process: wait for its completion. 4. Click “Next” and trigger the Automatic NE Creation: the previously discovered NEs are created into the EML database. 5. Check that NEs have been actually created.





Step 1: Issue the Discover NE Wizard 1. In the Network Element List, select the GNE and issue

“Actions

Discover NE”

2. The “Discover NE” wizard is opened



Copyright © 2012 Alcatel-Lucent. All Rights Reserved. TOS63017_V3.1-SG-R9.6-Ed1 Module 3.1 Edition 1 Section 3 · Module 1 · Page 174v


Step 2: Optional Filter 1. Optionally insert an IP Address/IP Mask pair as filtering criteria

2. “Next”, to trigger the discovery



The operator is optionally allowed to enter a filtering criteria defined in terms of a list IP Address/Mask pairs. Only the filtered list of NE belonging to the “subnets” defined by any of the masks will be given back to the GUI. In case of the operator is not filling in any filtering criteria, the discovery scope will consist of the overall subset of 1830PSS network elements that are reachable from the NE where the action is triggered.



Step 3: Discover NE 1. The Discovery process is triggered by clicking on “Next” in the previous step. Wait for the discovery process to be completed (check in the operation log).

2. After the completion, the discovered NEs are shown in this table. The user can remove NEs not to be created by selecting them and clicking on the “red cross”.

The discovered NEs are created with the Location Name of the GNE

The user can abort the process by clicking on this button

3. “Next”, to trigger the creation 3 · 1 · 176 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


N.B.: The discovery process can last several minutes, depending on the number of NEs to be discovered. Location Name and Supervision area are populated based on the gateway NE by which the process has been started. In case an ‘Abort’ request is issued, the NEs discovered up to the time the discovery was interrupted can be created by clicking on “Next”.



Step 4: Create NE

1. The automatically created NEs are shown in this table. 2. Check in the NE List that the new ones have been created. Eventually change the location name, check their address, User ID and Password and start supervision



The address and User ID and password of the auto discovered NEs are automatically set during the discovery procedure. Address is set based on the info sent by the discovered NEs. User ID and password are the same as the ones of the Gateway NE.


13 Addressing the NEs with “OSI over IP” tunnel





Principle 1350 OMS

NE managed by OSI protocol (Q3) IS-IS

ES-IS

IS-IS ES-IS

CLNP

CLNP

IP Packets

IP network 3 · 1 · 179 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


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 1350OMS server and an NE. The DCN connecting the 1350OMS and the NE will carry IP packets. The NE and the 1350OMS server need to support the OSI and IP protocols, whereas the routers only need to support the IP protocol.

NE has to be compatible with this feature. IS-IS: Intermediate System – Intermediate System ES-IS: End System – Intermediate System IS-IS and ES-IS are two OSI routing protocols. CLNP: Connection-Less Network Protocol. It’s the OSI network (layer 3) protocol.



Network example

I OS

er v o

1350OMS CLNP GRE IP 802.2 Ethernet

IP

OS

IP network

I

OSI network

GNE

GNE OSI

OSI NE OSI 3 · 1 · 180

NE OSI o ver IP

OSI

OSI

IP network

NE

NE

GNE

OSI



The OSI-over-IP can be used to: 1.

Interconnect the 1350OMS 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 1350OMS to a Router through an IP network. In this case, 1350OMS will be able to manage all the NEs reachable via that router using OSI protocol.

3.

Interconnect two NEs one 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 1350OMS is not used.

4.

To manage a Q3 NE by the OSI protocol (e. g. a 1660SM) when the gateway NE, connected to the DCN, is an 1850TSS-320/160 (see next slide).



Example: 1660SM managed through an 1850TSS-320 1350OMS

O IP SI o tu ve nn r el



In this example, the bidirectional OSI over IP tunnel between the 1350OMS and the TSS-320 is necessary for the management of the 1660SM. In fact, the 1660 management uses OSI protocol and it’s therefore necessary to create an OSI over IP tunnel up to the TSS-320. Between TSS-320 and 1660SM, the OSI protocol is transported by the DCC.



NE Configuration procedure: Q3 GNE By means of Craft Terminal: 1. Start the supervision of the NE and Login 2. Choose the menu “Configuration

(3)

Comm/Routing Interfaces Configuration Ethernet Configuration” 3. Enable the Ethernet interface 4. Assign an IP address and mask to the Ethernet interface 5. Click on Apply

(4)

(5) 3 · 1 · 182 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




NE Configuration procedure: Q3 GNE [cont.] 6. Choose the menu “Configuration

Comm/Routing

Tunneling

Configuration OSI over IP” 7. As Remote Destination IP Address, enter the 1350OMS server’s IP address 8. Click on Apply

(7)

(8)



The IP address of the 1350OMS can be get by typing the command “cat /etc/hosts” from a UNIX shell.



NE Configuration procedure: 1850TSS-320 GNE First of all, configure the OSI AREA that the NE is part of (must be the same as the one of 1350OMS). To open the OSI Address menu select: Communication Network Domain OSI Mng OSI NE Area

1. Insert the address

2. Click on Save 3. Click on Yes 3 · 1 · 184 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


The OSI page contains the OSI AREA panel: OSI AREA: Combobox to determine an access Identifier for an OSI area. Level 3 Initial Domain Part: Assign the initial domain part of the manual area address (8 hexadecimal characters). Level 3 Domain Format Identifier: Assign the domain format identifier field of the manual area address (2 hexadecimal characters). Level 3 Organization: Assign the organization field of the manual area address (8 hexadecimal characters). Level 3 Reserved: Assign the reserved field of the manual area address (4 hexadecimal characters). Level 3 Routing: Assign the routing domain and routing area within the routing domain of the manual area address (8 hexadecimal characters). Level 3 System Identifier: This is the system identifier assigned to the card (12 hexadecimal characters).



NE Configuration procedure: 1850TSS-320 GNE [cont.] Then, create the OSI over IP tunnel. To open the OSI Tunnel menu select: Communication Domain OSI Mng OSI Tunnel

Network

1. Click on Create to create a new OSI over IP tunnel

2. Insert the Access Identifier and the IP address of the target NE

3. Click on Save 3 · 1 · 185 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance




Configuration Procedure on the 1350OMS

3. “Managed NE” or “External Gateway”

4. Select the GW NE from the list. Its IP address is automatically retrieved

1. Actions

EML Tunnel Create OSI over IP Tunnel

2. Select the Supervision Area

5. “Apply”





OSI over IP Tunnel List

Search

EML


Tunnel

Get OSI over IP Tunnels



14 Security in ALU networks




14 Security in ALU networks

Introduction Involved NEs 1850TSS-100, from R3.2 1850TSS-320, from R3.6 1830PSS, from R3.5.2 Protocol

Purpose

RADIUS (Remote Authentication Dial In User Service)

User management: Authentication, Authorization, Accounting

SSH (Secure SHell)

TL1 management interface SFTP: Secure File Transfer Protocol CLI: Command Line Interface

SSL (Secure Socket Layer)

Equipment View in 1350OMS

SNMPv3 (Simple Network Management Protocol version 3)

SNMP management interface

Secure mode

The NE replies only to secure protocols: SSH-2, SFTP, SSL, SNMPv3




14.1 RADIUS




14.1 RADIUS

Introduction Remote Authentication Dial In User Service (RADIUS) is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for hosts to connect and use a network service. RADIUS server is responsible for AAA 1350OMS and NEs act as RADIUS clients




14.1 RADIUS

User profile management The user account is no more configured on the client devices (1350OMS and NEs). It is configured in the RADIUS server along with its profile, that is its rights. The following table provides the “RADIUS server role” to “user profile” mapping. RADIUS server role

User profile in User profile in User profile in 1350OMS 1830PSS 1850TSS

administrator

Administrator

Admin

Administrator

unrestricted_read_write

Constructor

Provider

Constructor

restricted_read_write

Operator

Provisioner

Operator

read_only

Viewer

Observer

Viewer




14.1 RADIUS

Configuration in 1350OMS The customization of RADIUS parameters in the 1350OMS is in the scope of Software installation. It’s not addressed by this Student Guide.




14.1 RADIUS

Configuration in NE Main and Spare RADIUS servers the NE can be configured to reach two RADIUS servers

RADIUS server parameters IP address port: by default 1812 Shared secret: 5 to 32 character-long ASCII string

Authentication order configuration Local 1830PSS and 1850TSS: authentication carried out by the NE. No RADIUS implementation required.

RADIUS 1830PSS: authentication carried out by RADIUS server. 1850TSS: first, the authentication is carried out by NE. If it fails, the RADIUS server takes over.

RADIUS, then Local 1830PSS: first, the authentication is carried out by the RADIUS server. If it fails, the NE takes over. 3 · 1 · 194 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance


IETF rfc2865: Transactions between the client and RADIUS server are authenticated through the use of a shared secret, which is never sent over the network. In addition, any user passwords are sent encrypted between the client and RADIUS server, to eliminate the possibility that someone snooping on an unsecure network could determine a user’s password. In case of authentication carried out by the NE, the user account must be configured in the NE.


14.1 RADIUS

Configuration in NE: 1830PSS-32 To configure the RADIUS server parameters, use the Equipment View or ZIC Administration

Security

RADIUS

Servers

(click on “Create” )

RAD1/RAD2



Server: select RAD1 or RAD2 for main or spare RADIUS server. Server IP: IP address of the RADIUS server. Port: Port of the RADIUS server (default port is 1812). Shared Secret: it is the shared secret key between the NE and the RADIUS server. 5 to 32 character-long ASCII string.


14.1 RADIUS

Configuration in NE: 1830PSS-32 [cont.] To configure the authentication order, use the Equipment View or ZIC Administration Security RADIUS Properties

1-1000 0-100



Timeout (1-1000s): it indicates the maximum timeout value for connectivity. Retries (0-100): it specifies the number of retries allowed in connecting to the RADIUS server. Authentication Order (Local/RADIUS/RADIUS, then Local): - Local: the check for the user account in only performed in the local database of the NE. - RADIUS: the check for the user account in only performed in the RADIUS server database. - RADIUS, then local: a first check is performed in the RADIUS server; in case of the user account is not present, the request is sent to the local database of the NE.


14.1 RADIUS

Configuration in NE: 1850TSS-100 To configure the RADIUS server parameters and the authentication order, use the Equipment View or ZIC Security Configure

Radius/Local

active/suspended

3 · 1 · 197



Order (Local/RADIUS): - Local: the check for the user ID in only performed in the local database of the NE. - RADIUS: a first check is performed in the local database of the NE; in case of the user account is not present, the request is sent to the RADIUS server. Retries (0-100): it specifies the number of retries allowed in connecting to the RADIUS server. Timeout (1-1000 sec): it indicates the maximum timeout value for connectivity. Address: IP address of the RADIUS Server. Port: Port of the RADIUS Server (default port is 1812). Status: Active or Suspended. Secret: it is the shared secret key between the NE and the RADIUS server. 5 to 32 character-long ASCII string.


14.1 RADIUS

Configuration in NE: 1850TSS-320 To configure the RADIUS server parameters, use the Equipment View or ZIC Security Administration Management RADIUS Configure RADIUS

Create



Server Number: select RAD1 or RAD2 for main or spare RADIUS server. Status (ENABLE/DISABLE): it indicates whether the authentication is active or disabled. IP Address : it indicates the IP address of the RADIUS Server. Port: it is the authentication port of the RADIUS server. The default port value is 1812. Secret Key: it is the shared secret key between the NE and the RADIUS server. 5 to 32 character-long ASCII string.


14.1 RADIUS

Configuration in NE: 1850TSS-320 [cont.] To configure the authentication order, use the Equipment View or ZIC Security Administration Management RADIUS Configure Authority

0-100 1-1000

3 · 1 · 199



Authority Order (LOCAL/RADIUS): - LOCAL: the check for the user ID in only performed in the local database of the NE. - RADIUS: a first check is performed in the local database of the NE; in case of the user account is not present, a request is sent to the RADIUS server. Retries (0-100): it specifies the number of retries allowed in connecting to the RADIUS server. Timeout (1-1000s): it indicates the maximum timeout value for connectivity.


14.2 SSH




14.2 SSH

Overview SSH (Secure SHell) is a communication protocol used to create a securely access to a remote host. It uses special algorithms to encrypt the data stream, ensure data stream integrity and perform authentication in a safe and secure way.

SSH authentication protocols are based on a pair of cryptographic keys, called “private key” and “public key”, used to encrypt and decrypt data.

SSH is used for the following services between NE and 1350OMS TL1 management interface SFTP: Secure File Transfer Protocol CLI: Command Line Interface




14.2 SSH

Configuration By default, preconfigured SSH keys are already available both in the NEs and in the 1350OMS. So, while creating the NE in 1350OMS, the user can select the default key. However, the user can generate other keys, but this is an administration issue.

Apart from the keys that must be available in the NE and in the 1350OMS, the SSH configuration concerns just 1350OMS in NE creation or ... later on for not supervised NEs

The NEs require no configuration.




14.2 SSH

Enable SSH and set the key

1. In the “Set NE Address” window set SSH2 as Secure Communication

2. Next

3. Choose

“DEFAULT”




14.2 SSH

Select another key for one or more NEs To select another key for the NEs that are already enabled for SSH: Actions

EML


Configure NE Interface

Configure SSH



14.2 SSH

Select another key for one or more NEs [cont.] The window shows all the NEs with SSH enabled

Next




14.2 SSH

Select another key for one or more NEs [cont.]

1. Select another key 2. Apply




14.2 SSH

Select another key for one NE Two methods Set NE address Select the NE

right click

Actions

Configure SSH

you get the same wizard described in the previous slides




14.3 SSL




14.3 SSL

Overview The SSL (Secure Socket Layer) protocol relies on TCP/IP. An SSL-enabled server and an SSL-enabled client authenticate one each other to establish an encrypted connection. SSL is used by 1350OMS to manage the Equipment View of the NEs. No operation via Equipment View or 1350OMS’s GUIs is required. The NE’s certificates must be copied from the NE to the 1350OMS this is an administration issue




14.4 SNMPv3




14.4 SNMPv3

Overview SNMPv3 provides secure access to devices by a combination of authenticating and encrypting packets over the network. The security features provided by SNMPv3 are: Message integrity Ensuring that a packet has not been tampered while in-transit.

Authentication Determining whether the message is from a valid source.

Encryption Scrambling the content of a packet preventing it from being seen by an unauthorized source.

SNMPv3 must be configured both in the 1350 OMS and in the NEs. Two parameters are necessary: authentication: The process of ensuring message integrity and protection against message replays. It includes both data integrity and data origin authentication. privacy: An encrypted state of the contents of an SNMP packet where they are prevented from being disclosed on a network. 3 · 1 · 211 System Operation · NE Creation and Supervision 1350 OMS EML · R9.6 Operation and Maintenance



14.4 SNMPv3

Configuration in 1350OMS for one NE 1. Set NE address

2. Set “V3” as SNMP version

3. Configure the appropriate parameters (see

Notes)



Security Level: it specifies the possible configuration in terms of Authentication and Encryption:

NoAuthorizationNoPrivacy: uses only a username to match for authentication. AuthorizationNoPrivacy: provides only authentication, based on the selected protocol. AuthorizationPrivacy: provides both authentication and privacy, based on the selected protocols. USM User: enter the SNMP user ID. USM Authentication Password: enter the password for authentication.

N.B: in case of TSS the Authentication password is the same as login password . USM Privacy Password: enter the password for privacy connection.

N.B: in case of TSS the Privacy password is like USM Auth. password but inverted. Authentication Method (HMAC-MD5 / HMAC-SHA): specifies the algorithm for Authentication. Privacy Method (DES / AES-128): specifies the algorithm for encryption.

N.B: in case of PSS-32 the Authentication and Privacy algorithms are fixed: MD5 and AES-128.


14.4 SNMPv3

Configuration in 1350OMS for one NE or more NEs Two methods that provide the same wizard described in the previous slide From the MS-GUI toolbar Actions

EML

Configure NE Interface

Configure SNMP

From the NE list Select the NE


right click

Actions

Configure SNMP



14.4 SNMPv3

Configuration in NE: 1850TSS-100 To configure the SNMP, use the Equipment View or ZIC Security Users (select a User)

Configure the specific protocols



SNMPv3 privacy protocol (disabled / CBCDES / AES): it specifies the encryption algorithm for the privacy protocol. SNMPv3 authorization protocol (disabled / MD5 / SHA): it specifies the encryption algorithm for the authentication protocol.


14.4 SNMPv3

Configuration in NE: 1850TSS-320 To configure the SNMP, use the Equipment View or ZIC Security Administration Accounts Change accounts account

Modify

Configure the specific protocols



SNMPv3 Privacy Protocol (NOPRIV / CBCDES / AES): it specifies the encryption algorithm for the privacy protocol. SNMPv3 Authorization Protocol (NOAUTH/ HMACMD5): it specifies the encryption algorithm for the authentication protocol.


14.4 SNMPv3

Configuration in NE: 1830PSS-32 To configure the SNMP, use the Equipment View or ZIC Administration Security SNMP v3 Users (select a User and click on “Details”)



Authentication Password: enter the password for authentication. Privacy Password: enter the password for privacy connection. N.B: SNMPv3 Privacy protocol and Authentication protocol are fixed to MD5 and AES-128 .


14.5 Secure mode




14.5 Secure mode

Definition The NE can work either in SECURE or UNSECURE mode. By default, the NE shall start in UNSECURE mode. This allows backward compatibility towards existing Network Management Systems that do not support encryption.

When the NE is in SECURE mode, several non-secure protocols are disabled: as SNMP, only SNMPv3 is supported SSH-2 encryption protocol is used for TL1 and CLI SSL is used for HTTPS SFTP is used to transfer files between 1350OMS and NE

The Secure/Unsecure mode must be configured only in the NEs and not in the 1350OMS. First, configure SSH, SSL,SNMPv3, and then enable the SECURE mode.

N.B: RADIUS functionality can be used regardless the NE’s SECURE/UNSECURE mode configuration.




14.5 Secure mode

Configuration in NE: 1830PSS-32 The following steps must be executed in order to transform a PSS node into secure Mode: 1. Configure SSL, SSH and SNMPv3 as explained in previous chapters 2. Open the main GUI and modify UI Mode 3. Click on “Submit”

Set “Encrypted” in the UI Mode field



UI indicates the user interfaces: CLI/TL1/WEBUI.


14.5 Secure mode

Configuration in NE: 1850TSS-100 The configuration via ZIC, for the TSS-100, is accessible under the menu Security Configure

Set “secure” in the SECACC field



SECACC – Secure mode: set “secure” for Secure mode. DHCP protocol on the CT port: if checked, it enables the DHCP protocol on the CT port of the NE. PHYSPORT – Enable physical port on NE: if checked, it enables the debug port of the NE (Q and F ports are always available).


14.5 Secure mode

Configuration in NE: 1850TSS-320 The configuration via ZIC is accessible, for the TSS-320, under the menu Security Administration Account Default Settings

Set “SECURE” in the Security Access field



Security Access: set “SECURE” for Secure mode. ICMP Protocol: “ENABLE” or “DISABLE” ICMP protocol on the NE. DHCP Protocol: “ENABLE” or “DISABLE” DHCP protocol on the CT port of the NE. Physical Ports: “ENABLE” or “DISABLE” the debug port of the NE (Q and F ports are always available).


Answer the questions Which is the condition to auto-discover an NE ? Which is the SSH protocol functionnality ? Which parameters are necessaries to configure the SNMPv3 ?




End of module NE Creation and Supervision





@@SECT LE Section 3 System Operation Module 2 Maps and Sub-networks





Blank page

3·2·2


System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Create and manipulate the maps

3·2·3 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 Overview 2 Sub-Network and Node management 3 Zoom 4 Size 5 Background 6 Grid 7 Some settings in “View management panel” 8 Link management panel




Page 7 14 29 35 42 47 52 57






1 Overview




1 Overview

MS-GUI Map Features 1350 OMS provides the following features: Network topology partition, enabling the user to organize the network by creating sub-networks and assigning nodes to them. Link creation, enabling the user to create or let the system auto-discover the physical connectivity between nodes of the managed network. Graphical Object Management, enabling the user to move on the maps the icons representing the network’s objects. The object position can then be fastened or unfastened on the maps. Map View Manipulation, enabling the user to zoom in, zoom out, assign a background picture and so on. Alarm status propagation, so that the color of an icon is determined by the most severe alarm affecting its subtended objects. Shortcut to queries or actions, enabling the user to retrieve lists or perform commands on the network’s objects from pop-up menus, available by right-clicking on the related icons.



A Map is a graphical view where the network’s objects, such as sub-networks, nodes, links, are represented by graphic symbols (icons). Maps are shared among all the Management Application: EML, SDH, PKT, WDM, SONET. MS: Multi-Service. The map is shared by all of the applications.


1 Overview

ROOT network The System automatically instantiates a ROOT network, that recursively contains all the Sub-Networks created by the users. Only Sub-Networks (and not Nodes) can be added to ROOT

ROOT network Sub-Networks, recursively contained in ROOT

3·2·9



All the procedures on networks and sub-networks described in the present Module can be issued as well from the MS-GUI networks and sub-networks lists. To open the network list: “Search

Map

Networks” (only ROOT is shown).

From the ROOT object in the list it is possible to create sub-networks (“Actions Network”) or list the first-level sub-networks (Search Sub-Networks).

Create Sub-

From the Sub-Networks in the Sub-Network lists, it is then possible to search several items.


1 Overview

Two methods for Map management There are two methods for managing the Sub-Networks: Basic

Advanced (Map version 2.0)

The training addresses the “Map version 2.0” method 3 · 2 · 10 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance



1 Overview

Two methods for Map management [cont.]

1. To switch from one method to the other one ... 2. ... open the “Options” window (Tools Options) 3. Tick to enable 4. Close the map and reopen it

3 · 2 · 11 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance



1 Overview

Panels Hide/Show the right panel

Go to parent map Miniature




1 Overview

Panels [cont.]

View management panel Background management panel Object management panel Link management panel Object not belongs to map General info 3 · 2 · 13 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance



2 Sub-Network and Node management





Sub-Network creation 1. Double click “ROOT” to get its map

2. Right click in the Map panel and “Create Subnetwork”





Save the objects position

To save the object’s position





Add a node to the Sub-Network There are two methods for adding a node to a Sub-Network: Method #1: using just the Right panel Method #2: using the Sub-Network tree AND the Right panel

Sub-Network tree

Right panel

3 · 2 · 17



First of all, the node must be available



Add a node to the Sub-Network – Method #1

1. Open the map

2. Drag & Drop the Node





Node’s info in pop-up The icons shown beside the node depend on the Technology being displayed

Communication State Local Access Control Alignment State

Reachable, Unreachable, Partially reachable It concerns the craft-terminal. Granted, Denied. Node vs 1350OMS

only Phys.

Supervision State

only OTN

Conf. Download Status

While Disabled, NE is not configured by 1350OMS-SDH

only Phys.

Multi NEs

e.g. OMSN with ISA board

only OTN

Control Plane status

for GMPLS/ASON

3 · 2 · 19



Multi NEs: e.g. 1660SM with ISA boards. Communication state •Partially reachable: the node supervision relies on two protocols (e.g. OSI and IP) and one of them is not operational. For example, 1660SM is reachable, whereas its ISA board is not.

Conf. Download Status •Default = Enabled. If disabled, the configurations carried out by means of 1350OMS-SDH are just kept in the 1350OMS-SDH’s database and not applied to the NE.



Move a node in the Sub-Network e.g. Move Node2

1. e.g. Enter the node from the top right vertex

It’s not possible to overlap objects

2. A cross appears

3. Click. Then drag ...

4. ... and drop

5. Save the map 3 · 2 · 20 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance




Remove a node from the Sub-Network





Add a node to the Sub-Network – Method #2

1. Modify Sub-Network 3 · 2 · 22 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance




Add a node to the Sub-Network – Method #2 [cont.]

2. Click this icon 3. Select one or more objects 4. OK

5. Apply 3 · 2 · 23 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance




Add a node to the Sub-Network – Method #2 [cont.] The Node is assigned to the map’s “Not placed” group. (Not placed: the position of the object in the map has not been yet defined) The “Not placed” icon is shown in the map

Drag & Drop the Node to define its position. (the node is removed from the “Not placed” group)





Assign an object back to the “Not placed” group

1. Select the object (e.g. a Node)

2. Click this icon





Another way to remove a node from the Sub-Network 1. Select the Sub-Network in the Sub-Network tree Actions Modify Sub-Network

3. Click the red cross 2. Select the node to be removed

4. Apply 3 · 2 · 26 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance




Show/hide the links to unplaced object Node 3 belongs to the “Not placed” group There’s a Physical Connection between Node1 and Node3

Show

Hide





“General Info” panel



OPC (Off-Page Connector) stands for a Sub-Network at higher level than or at the same level of the current map’s with which the current map shares physical connections. They don’t contribute to the above “Link” counter.


3 Zoom




3 Zoom

By means of percentage




3 Zoom

By means of mouse wheel & CTRL 1. Position the cursor on the map area 2. Press CTRL on the keyboard 3. Roll the mouse wheel back and forth




3 Zoom

By means of miniature




3 Zoom

By means of miniature [cont.]




3 Zoom

Fit to page

Page

The zoom is adjusted so that at least one dimension (e.g. height) is entirely shown 3 · 2 · 34 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance



4 Size




4 Size

Node and Sub-Network

1.5 1.5

2.0




4 Size

Map

842 / 40 = 21.05

2. Look at the max

m

ap

siz e

412 / 40 = 10.3

1. Scroll up to the end




4 Size

Increase the Map size

delta delta

Click and hold down




4 Size

Resize map function of object position The map is resized so that it fits the area occupied by the map’s objects

1080 919 3 · 2 · 39 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance

727

Constant ratio 919/1080 = 619/727 COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.


619

4 Size

Increase distance between objects ...

e.g. click 5 times

The map size changes accordingly




4 Size

Decrease distance between objects ...

e.g. click 5 times

Overlapping


In case of overlapping, click this icon, and eventually the nodes



5 Background




5 Background

Add 800 (20)

m

ap

siz e

600 (15)

Double click the picture

3 · 2 · 43



Most of the background images are “800 x 600”, that corresponds to “20 x 15” in the rulers. If the map size is lower than the background size: then the map size is set equal to the background size, else the map size doesn’t change.


5 Background

Fit image to map size The background becomes as big as the map (at least one dimension). The background size ratio is constant.

Before

After




5 Background

Resize image function of object position The background size gets closer to the area occupied by the objects The map size changes accordingly e.g. The objects area is initially quite smaller than the background size. (This command works for the opposite case, too)

Before After




5 Background

Remove 3. se oo Ch a r lo co

Even though “Size: 200 x 150”, the whole map is colored

2. Double click 1. Scroll down up to the bottom

To get the default color 3 · 2 · 46 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance



6 Grid




6 Grid

Show/Hide

Hide

Show




6 Grid

Grid size

Grid size = 10

Grid size = 50 3 · 2 · 49 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance



6 Grid

Align to grid The top left vertex of the objects fits to a grid’s point

n ig Al o t id gr

“Align to grid” is applied ... ... only to the selected objects, if any ...to all of the objects, if no object is selected 3 · 2 · 50 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance



6 Grid

Snap to grid When moving the objects in the map, their top left vertex fits to the a grid’s point




7 Some settings in “View management panel”





Object selection, color, vertex Change selection border to line/dashed Select all Select none

Change selection color


Collapse vertex



Expand vertex


Edge Type St

Edge Type

ht ig ra

n


tio


la Re

l

al nt

ca rti

o riz System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance

Ve

Ho

3 · 2 · 54


Label policy NE Label policy

AUTO: the labels are shown or not depending on the zoom level: - high zoom: shown - low zoom: hidden Link Label policy





Search for objects in the Map Go to previous occurrence

1st

2nd 3rd

Go to next occurrence

1. As you type “6”, the node 63B is selected 2. By clicking once “Go to next occurrence”, the node 164B is selected 3. By clicking again “Go to next occurrence”, the node 165B is selected 3 · 2 · 56 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance



8 Link management panel




8 Link management panel

Overview The operator can show/hide some links By default, all of the links are shown. So, all of the Map’s objects are in the list.

Click this button to remove element from list

Click this button to add all objects in list

Click this button to add element in list 3 · 2 · 58 System Operation · Maps and Sub-networks 1350 OMS EML · R9.6 Operation and Maintenance

Click this button to clear list



Exercise Create a map with a proper background Drag training NE‘s inside it Save the map





End of module Maps and Sub-networks





@@SECT LE Section 3 System Operation Module 3 Physical connections





Blank page

3·3·2


System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to:

Create manually the physical connections Let 1350 OMS auto-discover the physical connections deployed in the network

3·3·3 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 Introduction 2 Physical Connection_manual creation 3 Internal Physical Connection_automatic upload 3.1 Uploading the SDH physical connections 3.2 Uploading the WDM internal OPS Physical Connections (1626LM) 3.3 Uploading the WDM OTS Physical Connections (1830PSS) 3.4 Uploading the radio links (9500MPR) 4 Highlight




Page 7 11 26 28 39 45 51 58





Page

1 Introduction




1 Introduction

Node List



When a Network Element is created in EML, a correspondent object, called Node, is automatically created too. A Node is the logical representation of the NE, containing the objects used by the network managers for modeling the transmission network, that are ports and termination points. Sometimes, when a new NE is created, the new correspondent node is not appearing in the node list. In this case, the following steps must be performed: 1.

Issue “Search

Physical

EML Domains”

2.

Select the neGroup or the EML corresponding to the EMLIM instance of the newly created NE

3.

Double-click and “Actions

Synchronize

Synchronize EML”


1 Introduction

Synchronize NE Before Physical Connection creation, it is required to perform “Actions Synchronize Synchronize NE” from the new Node.

Physical

The “Synchronize NE” procedure uploads in the Node the ports that are discovered in the NE.




1 Introduction

Two ways to create physical connections 1. Manual procedure The user manually creates the physical connections between the Nodes, based on the information he has about the network connectivity.

2. Automatic upload procedure For SDH Physical Connections: The physical connections are autodiscovered based on the Trace Identifier information contained in the J0 byte of the SDH frame. For WDM OPS Physical Connections internal to 1626LM Nodes: The physical connections are auto-discovered based on the equipment internal cabling information retrieved by the 1350OMS. For WDM OTS Physical Connections between 1830PSS Nodes: The physical connections are auto-discovered based on the information contained in the connection tables of the NEs. For Radio links between 9500MPR Nodes: The physical connections are auto-discovered based on the IP routing information contained in the NEs not operational when the Student Guide was developed 3 · 3 · 10 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance



2 Physical Connection_manual creation

3 · 3 · 11 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance



2 Manually creating physical connections

Procedure 1. Select the two end-Nodes of the Physical Connection (optional) 2. Issue “Actions Physical Create Physical Connection” The “Create Physical Connection” Wizard is opened 3. Assign a User Label to the Physical Connection 4. Select “Connection Type” (SDH, WDM, Ethernet, …) and other relevant parameters of the PC to be created. Set the “Implement Rule” to “User” (*) 5. Click “Next” 6. Based on the “Connection Type” chosen at point 4, select the “STM Type” or “WDM Type” etc. 7. Select the “A Node”, “Z Node”, “A Port and “Z port” 8. Click “Apply” to start the Physical Connection creation



All the configurable parameters that are not referenced in the present Module are specific of the proper Network Management application (SDH, WDM, etc.) in charge to manage the physical connection. See the specific documentation for details. (*) If the “Implement Rule” is set to “Automatic”, the proper Network Management application, if installed, will try to implement the Physical connection, so instantiating all the transmission objects (Trails, Link connections, …) which are necessary for the management of the physical connection at network layer. See the specific documentation of the proper Network Management application (SDH, WDM, etc.) for details.



Open the creation wizard

2. Issue “Actions

Physical Create Physical Connection” 1. Select the two endNodes of the Physical Connection





Example: SDH Physical Connection Defined

3. Assign a User Label to the Physical Connection

Implemented

4. Select “Connection Type” and other relevant parameters of the PC to be created. Set the “Implement Rule” to “User”

Deimplemented

6. Next

5. Set “Yes”, so that the Physical Connection structure is displayed after creation 3 · 3 · 14 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance


Leave “Transport Alarm Enabling Rule” equal to “On Implementation” to display the alarms of the physical connection when it is “Implemented”.



Example: SDH Physical Connection [cont.] 7. select the

“STM Type” 8. The nodes are available because they were selected in the map 9. Leave “From List” 10. Select the ports. Click the icon or anywhere in the port’s space. Then, see next slide. 11. Finally, Apply 3 · 3 · 15 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance




Options for retrieving the object lists





Example: SDH Physical Connection [cont.]

List

Double-click the link

Physical Connection

Node

Port Structure

3 · 3 · 17



•To get the PC structure, it’s possible to select the PC

Search

Physical Connection Structure.

•This slide reports a Defined PC.



Example: SDH Physical Connection [cont.] Defined Implemented Deimplemented

To change the PC state, double-click it Actions Configuration Implement/ Deimplement

Defined

AU4 3 · 3 · 18 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance

Multiplex Section COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.


Implemented


Example: Ethernet Physical Connection

Yes: to open a Physical Connection list with the PC being created at the end of the creation

on

ly

ed fin e D

Defined Implemented

Deimplemented 3 · 3 · 19 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance




Example: Ethernet Physical Connection [cont.]

Physical Connection structure not available

PC list 3 · 3 · 20 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance




Example: Radio Physical Connection for 9500MPR

Yes: to open a Physical Connection list with the PC being created at the end of the creation





Example: Radio Physical Connection for 9500MPR [cont.]

Physical Connection structure not available

PC list on

ly

ed fin e D

Defined Implemented

Deimplemented 3 · 3 · 22 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance




Example: OTS Physical Connection for 1626LM

Yes: to open the Physical Connection structure at the end of the creation





Example: OTS Physical Connection for 1626LM [cont.]





Example: OTS Physical Connection for 1626LM [cont.]




3 Internal Physical Connection_automatic upload




3 Automatic upload of physical connections

Generalities Physical Connections can be uploaded by the 1350 OMS relying on the information contained in the nodes. The procedure applies to the following physical connections types: SDH Physical Connections: The auto-discovery process is based on the Trace Identifier information contained in the J0 byte of the SDH frame. WDM OPS Physical Connections internal to 1626LM Nodes: The autodiscovery process is based on the equipment internal cabling information that can be retrieved by the 1350OMS. WDM OTS Physical Connections between 1830PSS Nodes: The autodiscovery process is based on information embedded in the Optical Supervisory Channel. Radio links between 9500MPR Nodes: The auto-discovery process is based on the IP information contained in the NEs

In the following, the relevant examples. 3 · 3 · 27 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance



3.1 Uploading the SDH physical connections





Procedure 1. Select the Nodes involved in the creation of the physical connectivity 2. Issue “Actions Physical Discover Physical Topology” The “Discover Physical Topology” wizard is opened

3. Put “Action selection = Automatic Generation of Trace

Identifier” 4. Click on “Next” 5. Check that all the desired nodes appear in the “Node” window. To add the missing nodes: right-click them in the map issue “Send to

Discover Physical Topology 6. Click on “Apply”

Node”

7. Check in the Log that the Trace Identifier has been sent to the SDH ports of the desired nodes

8. See next slide





Procedure [cont.] 8. Do “Back” in the wizard 9. Put “Action selection = Physical Connectivity from J0” 10. Click on “Next” 11. Check that all the desired nodes appear in the “Node” window. To add the missing nodes: right-click them in the map issue “Send to

Discover Physical Topology

Node”

Leave “Implement” to “False”

12. Click on “Apply” 13. Check in the Log that the relevant Physical Connections have been correctly created





Example

2. Issue “Actions

Physical Discover Physical Topology”

1. Select the Nodes involved in the creation of the physical connectivity 3 · 3 · 31 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance




Example [cont.]

3. Put “Action

Selection = Automatic Generation of Trace Identifier”

4. Click on “Next”





Example [cont.]

5. Check that the selected nodes appear in the “Node” section

6. Click on “Apply”





Example [cont.]

8. To close the Log window: Options Close Log 7b. Click “Details” and check that the Trace Identifier has been sent and updated in the SDH ports of the nodes 7a. Issue “More Log” in the wizard





Example [cont.]

11. Next 10. Physical Connectivity from J0 9. Do “Back” 3 · 3 · 35 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance




Example [cont.]

12. Check that all the selected node appears in the “Node” window

See Notes

13. Click on

“Apply”



If “Implement” is set to “True”, the proper Network Management application, if installed, will try to implement the Physical connection, so instantiating all the transmission objects (Trails, Link connections, …) which are necessary for the management of the physical connection at network layer. See the specific documentation of the proper Network Management application (SDH, WDM, etc.) for details.



Example [cont.]

14. Have a look at the Log to check that the relevant physical connections have been correctly created





Example [cont.]

Procedure result




3.2 Uploading the WDM internal OPS Physical Connections (1626LM)





Procedure Prerequisite: The user must already have configured the 1626LM internal connectivity using the option “Configure Connectors/Cabling…” 1. Select the Node (or more than one) involved in the creation of the physical connectivity 2. Issue “Actions Physical Discover Physical Topology” The “Discover Physical Topology” wizard is opened

3. Put “Action selection = Physical Connectivity from WDM

Internal Cable” 4. Click on “Next”

5. Check that the selected node appears in the “Node” window, otherwise right-click the Node in the map and issue “Send to

Discover Physical Topology

Node” 6. Select the desired option into the “Implement” box 7. Click on “Apply”

8. Check in the Log that the relevant Physical Connections have been correctly created





Example

2. Issue “Actions


1. Select the desired Node 3 · 3 · 41 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance




Example [cont.]

3. Put “Action

Selection = Physical Connectivity from WDM Internal Cable”






Example [cont.] 5. Check that the selected node appears in the “Node” window

6. Select the desired option into the “Implement” box (if “Implement = True”, OCH-CTPs and OCH-Links are created [*])




[*] The internal Physical connections are, at least in this example, OPS Links. As such, they support no OMS-CTP, OMS-Links or OMS-Trails.



Example [cont.] 8b.Click on the “Upload Tools” Operation, click on “Details” and check that the relevant physical connections have been correctly created. Note that the creation and implementation of the Physical Connections imply as side effect the discovery of the OCH, OTU and ODU trails. 8a. Issue “More Log” in the wizard 3 · 3 · 44 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance



3.3 Uploading the WDM OTS Physical Connections (1830PSS)






3. Put “Action selection = Physical Connectivity from NE” 4. Click on “Next” 5. Check that the desired nodes appear in the “Node” window, otherwise Discover right-click the Node in the map and issue “Send to

Physical Topology Node” 6. Leave “False” in the “Implement” box (*) 7. Click on “Apply” 8. Check in the Log that the relevant Physical Connections have been correctly created

NEs in the same EMLIM 3 · 3 · 46 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance


(*) No implementation is required for OTS physical connections between 1830PSS nodes.



Example Slot 2 1830 PSSPSS-32 C33

Slot 9 1830 PSSPSS-16 C34

ALPHG

ALPHG

2. Issue “Actions


1. Select the desired Nodes. Even one is enough. 3 · 3 · 47 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance




Example [cont.]

3. Put “Action Selection

= Physical Connectivity from NE”






Example [cont.] 5. Check that the selected nodes appears in the “Node” window

6. Leave “False” in the “Implement” box






Example [cont.]




3.4 Uploading the radio links (9500MPR)






3. Put “Action selection = Radio Physical Links from OAM” 4. Click on “Next” 5. Check that the desired nodes appear in the “Node” window, otherwise Discover right-click the Node in the map and issue “Send to

Physical Topology 6. Click on “Apply”

Node”

7. A Web browser window is opened containing the operation log: check that the relevant Physical Connections have been correctly created Only the following kinds of radio links are automatically discovered: a) 1+0 configuration: the Main Link; b) 1+1 configuration: the Main Link (spare Link has to be manually created); c) N*(1+1) configuration: the Active Link.



OAM (Operations Administration & Maintenance): it is a 1350OMS’s process responsible for some functions: show remote inventory, ping NE, NE-SW download, MIB backup, CLI, NE scheduled backup/SW Mgt, NE auto-discovery, password management,…



Example 2. Issue “Actions


1. Select the desired Nodes 3 · 3 · 53 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance




Example [cont.]

3. Put “Action selection

= Radio Physical Links from OAM”






Example [cont.]

5. Check that the selected nodes appear in the “Node” window






Example [cont.]

Upload Failure case 3 · 3 · 56



EML NE ‘105/3’ •105: is the number of the EMLIM (EMLIMCORBASNMP) that manages the NE. It corresponds to the NE “EML Domain” attribute. •3: is the NE identifier •you can read them in the NE list

node ’75’ •75: is the node identifier •you can read it in the node list

SDH NE ’57’ •to get it: Main toolbar Search NEs

Search

Physical

EML Domains; then, select the neGroup


right click

Exercise Based on the network available for the training course: create a suitable sub-network hierarchy create the Physical Connections by using both the manual and the automatic upload procedure Check the physical connection structure





4 Highlight




4 Highlight

Introduction The objects that can be highlighted are some objects created by means of Physical or OTN menus Node, Physical Connection, Path, Trail, ...

Only one object can be highlighted at a time.

Disable highlight mode To clear the current highlight Add to highlights To highlight the selected object and to add it to the Highlight table 3 · 3 · 59 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance

Display Highlights To open the Highlight table COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.


4 Highlight

Node

The sub-network that contains the Node is automatically opened and the Node is highlighted

2. Click 1. Select the Node

prior to highlighting another object

3. The node 3 · 3 · 60 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance



4 Highlight

Physical Connection The sub-network that contains the Physical Connection is automatically opened and highlighted

double-click the sub-network

highlighted Physical Connection 3 · 3 · 61 System Operation · Physical connections 1350 OMS EML · R9.6 Operation and Maintenance



Discover Discover the highligt tool





End of module Physical connections





@@SECT LE Section 3 System Operation

Module 4 Commissioning and Power Balancing for 1830 PSS TOS63017_V3.1-SG-R9.6-Ed1 Module 3.4 Edition 1




Blank page

3·4·2 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance




Date

Author

Remarks

01

2012-11-08

Vallet, carole

First edition


Module objectives Upon completion of this module, you should be able to: Describe the generalities about the commissioning and power balancing feature for 1830PSS networks Carry out the main provisioning and commissioning procedures for 1830PSS networks









Table of contents Switch to notes view! 1 Generalities and CPB integration in 1350 OMS 2 Overview on CPB commands 3 Import the EPT commissioning file 4 Import NE data to CPB 5 Provision system (using Plan) 6 Initial/Greenfield (using Plan) 7 Create Loss Report 8 Power Balance system 9 Export File for EPT




Page 7 16 22 27 31 40 49 54 61





Page

1 Generalities and CPB integration in 1350 OMS




1 Generalities and CPB integration in 1350OMS

EPT & CPB In deploying and operating an 1830PSS network, three stages are foreseen: 1. Network Planning using the Engineering and Planning Tool (EPT) 2. Greenfield commissioning of the network 3. Ongoing maintenance and network upgrade

Commissioning and Power Balance (CPB) addresses the commissioning phase and also helps the operator during the ongoing maintenance with the Loss Report and Power Balancing options report based on the current power values against the target ones


to apply new target power values and power balance




System A System may include several NEs Ring

Point to point

1830PSS network must be decomposed by the EPT user into Rings or Point-to-Point Systems Each System has to be commissioned separately





Splitting network into Systems example AHPHG (1-6) CLS8

CLS8

CWR8 (1-8)

AHPLG (1-2)

CLS1 CLS2 CLS3 CLS4 CLS5 CLS6

Any Ch

Ch 30

L4 L3 L2 L1 11QPA4 (1-13) C4 C3 C2 C1

NE 1

GbE


Any Ch

L1 11STGE12 (1-18) C1 C2 …. C12

AHPHG (1-6)

System

CLS1 CLS2 CLS3 ………. CLS7 CLS8

C1 C2 C3 C4 From 11STGE12 L1 (1-8)

2

AHPLG (1-2)

NE 3

1GbE

3 · 4 · 10 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance

ALPHG (2-2)

(25 )

1

CLS1

CWR8-88 (2-4)

CLS2 CLS8

Ch 30

L1 11QPA4 L2 (2-13) L3Any Ch L4 Any Ch

NE 2

CLS1 CLS2 CLS3

CWR8 (2-8)

CLS4

ALPHG (2-6)

CWR8 (1-4) CLS1 CLS2 CLS3 CLS4 CLS5 CLS6

L1 L2 11DPE12 (1-16) C1 C2 …. C12

O

OMD

Ch 35

From 4DPA4 L1 (1-5)

System THRU

ITLB

SFD44 (26)

Ch 53 From 11STAR1 L1 (1-15)

10GELAN

Ch 35

STM-4 1GbE

E

10GELAN

CWR8 (1-8)

L1 L2 4DPA4 (1-19) C1 C2 C3 C4

CWR8-88 (1-4)

CLS connections between the CWR boards the ring must be split in two Point-to-Point Systems



CLS8


Commissioning scenarios In case of ring System (assuming that at least a pre-amplifier is present on each OTS): commissioning is completely accomplished leveraging on the light source represented by the ASE (Amplifier Spontaneous Emission)

In case of Point-to-Point System: commissioning is carried out in two steps: 1.commissioning is only partially accomplished leveraging on the light source represented by the ASE because the nodes that are not fed by any light source (e.g. ASE) cannot be configured 2.the commissioning of the remaining nodes requires the operator to create a dedicated service, that can be disrupted after the task completion or can be kept for real traffic





Point-to-Point System commissioning AHPHG (1-6) CLS8

CLS8

CWR8 (1-8)

AHPLG (1-2)


Any Ch

E

System

Ch 35

From 4DPA4 L1 (1-5)

10GELAN

System

C1 C2 C3 C4

10GELAN

From 11STGE12 L1 (1-8)

AHPHG (1-6)

THRU

CWR8 (1-8) CLS1 CLS2 CLS3 ………. CLS7 CLS8

L1 L2 4DPA4 (1-19) C1 C2 C3 C4 STM-4 1GbE

CWR8 (1-4) CLS1 CLS2 CLS3 CLS4 CLS5 CLS6

Ch 35 L1 L2 11DPE12 (1-16) C1 C2 …. C12

ITLB O

SFD44 (26)

Ch 53 From 11STAR1 L1 (1-15)

Ch 30

L4 L3 L2 L1 11QPA4 (1-13) C4 C3 C2 C1

NE 1

GbE


Any Ch

L1 11STGE12 (1-18) C1 C2 …. C12

CWR8-88 (1-4)

OMD

1

CLS1

CWR8-88 (2-4)

CLS2 CLS8

Ch 30

L1 11QPA4 L2 (2-13) L3Any Ch L4 Any Ch

2

ALPHG (2-2)

(25 )

NE 2

CLS1 CLS2 CLS3

CWR8 (2-8)

CLS8

CLS4

ALPHG (2-6)

AHPLG (1-2)

NE 3

Point configured with the help of ASE Point skipped due to ASE unavailability

1GbE





Prerequisites to use CPB in 1350 OMS The network is planned using EPT CPB component installed on the 1350 OMS server: CPB (optional) is packaged with EML check with the system administrator

1830PSS NEs must be created and given an address by 1350 OMS EML: Physical connections can either be created or not. They are for sure necessary for creating the service in Point-to-Point System commissioning.





Network Commissioning macro-steps 1. EPT (Engineering Planning Tool) to be used to design and plan the network it provides an .xml commissioning file per System that contains info about: card types, position and mutual connectivity min and max values for span losses port-to-port losses between wavelength tracker detect points amplifier gains ...

2. 1350 OMS import the .xml commissioning files provided by EPT comparison of design data against installed equipment configuration and creation of connections between cards optical Power provisioning (setting of nominal values) and Commissioning (setting of actual values based on real measures) Power Balancing





Onwards CPB application in 1350 OMS is addressed No details about the commissioning guidelines for 1830PSS networks are given: the trainee must already be familiar with them for details, please refer to the “Installation and System Turn-Up Guide” which is part of the Alcatel-Lucent 1830PSS customer product documentation




2 Overview on CPB commands





Optical NEs and System lists





Actions





Operations from Optical System list: Status

These “status” windows have been retrieved after CPB completion. They are created by the commands that we’ll see onwards. 3 · 4 · 19 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance




Operations from Optical System list: Logs

Logs for ...





Operations from Optical System list: Show Loss Report

Provided by ...




3 Import the EPT commissioning file






2. 1350 OMS import the .xml commissioning files provided by EPT comparison of design data against installed equipment configuration and creation of connections between cards optical Power provisioning (setting of nominal values) and Commissioning (setting of actual values based on real measures) Power Balancing





How to do

1. Search

Commission and Power Balance Optical System

2. Select the System

Upload Plan File

Search

3. See next slide 3 · 4 · 24 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance




How to do [cont.] Internet Explorer window

3. “Browse” to search for the desired commissioning file in the local PC’s file system

4. File’s name can be edited 5. Upload File 3 · 4 · 25 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance




How to do [cont.]

6. Wait for the upload to complete




4 Import NE data to CPB






2. 1350 OMS import the .xml commissioning files provided by EPT comparison of design data against installed equipment configuration and creation of connections between cards import NE data to CPB Provision system (using Plan)

optical Power provisioning (setting of nominal values) and Commissioning (setting of actual values based on real measures) Power Balancing 3 · 4 · 28 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance




How to do 1. Actions

Commission and Power Balance Discover NEs (using Plan)

2. “Plan File” must be selected 3. Apply





How to do [cont.] 4. Wait for the header gets green. It may take some minutes.

5. Search

6. Check that the NEs with related info have been correctly imported:

Commission and Power Balance Optical NEs

Search


CPB

Optical NEs


Some minutes are necessary to complete the process, based on the number of NEs to be discovered. It’s possible to double check that the discovery is ongoing looking at the Logs - the tab nearby Maps, Lists, Graphical.


5 Provision system (using Plan)











Provision system (using Plan) Validates the NE hardware inventory comparing EPT plan with cards installed in field. Creates the internal fiber connections between the circuit packs. Loads the target power values on the configurable cards (LD, xWRy,...). Fails in case of comparison mismatch.

Actions Commission and Power Balance Provision system (using Plan)





Select the System 1. Select the System and the Plan File

2. Next





Check the NEs NEs that belong to the System

Next





Select the Options Refer to the commissioning recommendations for setting the parameters

Select the correct option

Then click Next 3 · 4 · 36 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance




Start the automatic procedure

OK 3 · 4 · 37 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance




See the results Provision Detail Status





See the results: failure details If some actions are not completed correctly, the Status is set to “Failed” and the procedure stops. Click on the “Provision Detail Status” icon to see the details.




6 Initial/Greenfield (using Plan)











Initial/Greenfield (using Plan) Commissioning to set up the target power values on the configurable cards (LD, xWRy,...) in order to match the working condition envisaged by EPT. ASE power is used to perform commissioning on Ring systems and on the intermediate NEs in Point-to-Point systems.

Actions Commission and Power Balance Initial/Greenfield (using Plan)





Setting the commissioning parameter Clean state: commissioning starts from scratch Continue Commissioning: resume a previous commissioning that failed

Report File is automatically filled in

Nex t 3 · 4 · 43 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance




Setting the commissioning parameter [cont.]

Refer to the commissioning recommendations for setting the parameters Select the correct option

Outcome in next slide 3 · 4 · 44 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance



Appl y


Check the executed operations





Failure details If some actions are not completed correctly, the Status is set to “Failed” and the procedure stops. Click on the “Provision Detail Status” icon to see the details.





Show Loss Report 1. Search

Balance

Commission and Power Optical System 2. Select the System and issue Search Show

Loss Reports

3. Select the desired report and issue

Search Report

Show Loss





Show Loss Report [cont.] Loss Report File yellow highlighted cells: measure not possible




7 Create Loss Report





Create Loss Report “Create Loss Report” generates a power loss report based on the current power values against the target power settings for the optical domain. Greenfield commissioning and Power Balancing operations always generate loss reports.

Two options: “Create Loss Report” generates a report that summarizes the failed auto power management, the status of the last ingress/egress adjustment that was performed for each NE, and any components that are suspected to be out of specification. “Create Loss Report (using Plan)” generates a report, using an existing commissioning file from EPT, that details the power loss that occurs throughout the optical networking system.





Issue the Wizard

Actions Commission and Power Balance “Create Loss Report” or “Create Loss Report (using Plan)”





Create Loss Report 1. Select the NE and its desired Egress port

2. Insert a name for the Loss Report file. It’s HTML. 3. Apply



The generated Loss Report file can be opened using the procedure already described for “Initial/Greenfield Commissioning”:

1) Select the Optical System 2) Select the desired report

Search Search

Show Loss Reports Show Loss Report

The report file is put in the subdirectory: /usr/Systems/EML_/maintenance/cpb/reports



Create Loss Report (using plan) 1. Select the Plan File

2. Insert a name for the Loss Report file. It’s HTML. 3. Apply



The generated Loss Report file can be opened using the procedure already described for “Initial/Greenfield Commissioning”:

1) Select the Optical System 2) Select the desired report

Search Search




8 Power Balance system











Power Balance system It is performed to: apply new target power values and power balance the optical domain with the services present. Or complete the power adjustment during commissioning once the dedicated service is created.

It can be done: By using a Plan file from EPT - Power Balance system (Using Plan). Or By selecting an NE in the optical domain - Power Balance system. In this case the user has to select a node and one of its egress ports to start the power balancing operation.





Power Balance system [cont.]

Actions Commission and Power Balance “Power Balance system” or

“Power Balance system (using Plan)”





Power Balance system

1. Select the NE and the Egress port from which the balancing operation has to start 2. Insert a name for the Loss Report file. It’s HTML.

3. Apply






Power Balance system (using Plan)

1. Select the Plan File 2. Insert a name for the Loss Report file. It’s HTML.

3. OK






Loss Report 1) Select the Optical System 2) Select the desired report

Search Search


Now




Before:

9 Export File for EPT





How to do 1350OMS can generate an .xml file containing the equipment configuration and export it to EPT for possible network re-design. The .xml file is saved in the directory: /usr/Systems/EML_/CPB_CORE/export/

1. Actions Commission and Power Balance Export file for EPT 3 · 4 · 62 System Operation · Commissioning and Power Balancing for 1830 PSS 1350 OMS EML · R9.6 Operation and Maintenance




How to do [cont.]

2. Click the icon to select the equipment whose configuration must be exported

3. Apply




Answer the questions Which are the three stages foreseen in deploying and operationg an 1830PSS? List the commisionning macro steps.




End of module Commissioning and Power Balancing for 1830 PSS





@@SECT LE Section 3 System Operation Module 5 NE Management





Blank page

3·5·2


System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Describe the status of the Network Element Grant the access to the local operator Align the Network Element’s time to the 1350 OMS’s one Retrieve the Network Element’s card list as remote inventory Reset the network Element

3·5·3 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 NE status 2 Granting access to Craft Terminal 3 NE time and NTP 4 Remote inventory 4.1 Remote Inventory as text file for a single NE 4.2 Remote Inventory as a list in the MS-GUI for one or more NEs 5 Resetting an NE from Equipment View




Page 7 14 22 35 39 44 48






1 NE status




1 NE status

Displaying NE states From the Network Element list, select an NE right click Actions Get NE Current Status An automatic refresh is performed periodically To check that the NE states displayed are up to date, perform a manual refresh: 1. Select the NE in the Network Element List 2. Right click on it and choose

“Actions

Resynchronize”



The Communication state (NE Reachability) is shown in the “Get NE Current Status” window with the two possible values: Disabled – Correspondent to the “Unreachable” state Enabled – Correspondent to the “Reachable” state


1 NE status

Alarm status The alarm state indicates the most critical alarm present on the NE Critical Major Minor Warning Cleared no alarm

Indeterminate the severity level cannot be defined by the resources which raise the alarm




1 NE status

Supervision state

Starting supervision…

DECLARED

DEACTIVATING

Stopping supervision…

ACTIVATING

SUPERVISED

Stable states 3 · 5 · 10 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance

Transient states COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.

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)


1 NE status

Alignment state Stable states Transient states

MIB

=

1350OMS

ALIGNED

ALIGNING UP

MIB

AUDITING

MIB

1350OMS

MIB 1350OMS

1350OMS

MISALIGNED ≠ 1350OMS MIB

3 · 5 · 11 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance


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 “Declared” In case of Q3 or SNMP NE, when the communication link between the EML and the NE is down (Communication state = Unreachable) In case of 1850TSS-320 MSPP NE, when the primary (Q3) or the secondary (SNMP) or both the communication links are down N.B.: In case only one of the communication links is down, the Communication state stays in Reachable 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

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 EML with the NE are fully completed. The synchronization procedure involves the alarms, the PM and NE.


1 NE status

Communication state – NE reachability 1350 OMS

EML has lost communication with the equipment…

UNREACHABLE

REACHABLE The equipment can be reached by the EML …

1350 OMS



Communication state

Unreachable: The Communication between the OS and the NE is interrupted Reachable: The OS can communicate with the NE Undefined: The address hasn’t yet been assigned to the NE N.B.: If the equipment is an 1850TSS-320 1.4 in MSPP configuration, it has a double communication link with the OS (Q3 and SNMP). In this case the Communication state is Unreachable only in case BOTH the links are down.


Exercise Check the status of the NE in training network





2 Granting access to Craft Terminal





MS-GUI commands Local Access Control Denied (default for a supervised NE) NE managed by the OS only Craft Terminal has read-only rights can ask for the access in case of the OS is “pending”

Local Access Control Granted (default for a not supervised NE) Craft Terminal can manage the NE The OS continues to receive and process alarms and performance data. For some kinds of NE, the OS can manage the NE, too.

1. Issue “Actions

Access State” 2. Select

“Granted” or “Denied” 3 · 5 · 15 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance


After confirmation, the “Local Access Control” attribute is updated. For Q3 NEs, it’s possible to manage the Local Access by means of Equipment View. “Supervision Access State Local” (granted) or OS” (denied) The Local access state is always “Granted” for the 1830PSS up to R3.0. 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 EML is supervising the equipment.



Effect: example for 1850TSS-320 “Save” NOT available “Save” available Light blue Green

Equipment View

Local Access = Granted 3 · 5 · 16 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance

ZIC COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.

In the opposite case, that is “Local Access = Denied”, the configuration commands are available in Equipment View, whereas are not available in ZIC; the “key” color changes accordingly.



Effect: example for 1850TSS-100 “Declare” available “Declare” NOT available

Equipment View

ZIC

Local Access = Granted see next slide

Local Access = Denied 3 · 5 · 17

The “key” is shown and green in both the views COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.


The modification of the Local Access for 1850TSS-100 forces Equipment View and ZIC logout. 1350OMS and ZIC must use different users. The example concerns “admin” users.



Effect: example for 1850TSS-100 [cont.]

“Declare” available in both the views

Equipment View

ZIC


No “key” in both the views COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.



Effect: example for 1660SM “Set” NOT available “Set” available

Equipment View


LCA is light blue “key” is Green COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.


Craft Terminal


Note for 1850TSS-320 R1.4 Due to the dual management domain of the 4G Q3 NEs (Q3 agent and SNMP agent), the Access State management needs a specific handling: From the Network Element list the access state is directly managed only on the Q3 management domain. The access state to the SNMP domain must be further handled in the data USM. navigate from Equipment View to the data USM Select the PP20G card (data processor) and then “Equipment

Data Board Navigation”

grant the access Supervision

Access State

Granted

Data USM



In the SNMP domain • If “Granted” is selected, the CT has access to the SNMP domain only if the Access state has been previously set to “Local” by the EML operator from the NE list. • If “OS” is selected, the CT has no access to the SNMP domain only if the Access state has been previously set to “OS” by the EML operator from the NE list.


Exercise Give the access to the craft terminal Check the local access control state





3 NE time and NTP




3 NE time and NTP

Network Time Protocol NTP: to synchronize the date and time of the NEs with a time source that typically is the server hosting the 1350 OMS. The 1350 OMS realigns the time of all the supervised NEs every 24 hours by default. NTP configuration: in 1350 OMS: NTP must have been enabled during 1350 OMS installation

in NEs: NTP is automatically activated upon NE supervision The 1350 OMS EML server’s address is used as “Main NTP Server Address”

NTP types: Q3 NEs rely on OSI NTP TL1 NEs rely on IP NTP 3 · 5 · 23 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance



3 NE time and NTP

NTP in Q3 NEs 2. Set “False” to disable, “True” to enable the NTP protocol

1. Right-click on the NE and issue: “Actions NTP configuration” 3. Check the OSI address of the NTP server in the “NTP OSI” folder




4. “Apply”

3 NE time and NTP

NTP in Q3 NEs [cont.] In Equipment View: Configuration


Comm/Routing

NTP Server Configuration



3 NE time and NTP

NTP in TL1 NEs Right click the NE: Actions

NTP configuration

1.Set “False” to disable, “True” to enable the NTP protocol

2. Check the IP address of the NTP server in the “NTP IP” folder 3. “Apply”



When working with 1830PSS, make sure no NTP servers have been configured by the local craft terminal operator. If it is so, then remove the manually configured NTP servers by the “Show Equipment” window.


3 NE time and NTP

NTP state in the NE List

Q3 NEs are synchronized by an OSI NTP server

TL1 NEs are synchronized by an IP NTP server




3 NE time and NTP

Reminder

The date and time shown in the MS-GUI are the PC’s




3 NE time and NTP

Getting the NE time

Select “Actions Time Get NE Time”



This operation is allowed only if the NE is under supervision and its NE reachability state is ENABLED.


3 NE time and NTP

Setting NE time Select “Actions Time Set NE Time” It’s available only if NTP is disabled.

EML server local time NE time

To align the NE time to the OS time 3 · 5 · 30 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance


In case of 1830PSS, don’t use this procedure to set the NE time: To manually set the date and time the user has to access the NE by the Craft Terminal (don’t use Show Equipment by the 1350OMS).


3 NE time and NTP

NE time in Equipment View: 1850 TSS-320

1. System Management Network Time Protocol “NE Time” shown in MS-GUI is equal to “Current Time” + the NTP server time zone

2. It’s read-only. “Save” command is unavailable.

In case of NTP enable: “Current Time” = “NTP server UTC time” + “Current Offset” “Current Offset” usually is null. It can be set by means of ZIC.




3 NE time and NTP

NE time in Equipment View: 1850 TSS-100 MS-GUI time, that is the PC time

Difference between “Local time” and “UTC time”

“Save” has no effect


If NTP is operational, it’s equal to the NTP server UTC time

1. In the Equipment View, issue Commu NTP config



3 NE time and NTP

NE time in Equipment View: Q3 and 4G Q3 equipment

1. In the Equipment View, issue Configuration NE Time

If NTP is operational, it’s equal to the NTP server local time MS-GUI time, that is the PC time

2. If NTP is not enabled, it’s possible to align the NE time to the OS time by “Set”



For Q3 and 4G Q3 equipment, the “Start supervision” action issued from the EML can enable the NTP on the NE; the address of the EML server is automatically written as main NTP server in the NE comm/routing configuration. Ask the system administrator whether this feature is enabled.


Discussion or question Why is is crucial for the network maintenance to have all NE’s at the same time reference ?




4 Remote inventory




4 Remote inventory

Provided info Alcatel-Lucent Identifier (AID) Unit Type (Mnemonic of the R.U.) Unit part number Software part number CLEI code Manufactory Plant Unit serial number Date identifier Date R.U. inventory field for the customer

3 · 5 · 36

Example: “All inventory” from 1850 TSS-100’s Equipment View



ALCATEL-LUCENT company Identifier: This field contains the abbreviation of the company using 4 characters (uppercase). For instance: AITA, ACIT , ASEL , ATEL , ALCL. Unit Type: 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-Lucent code to identify the R.U. This number includes the ICS at the end. Software part number: The Software Part Number is the Alcatel-Lucent identifier of the resident software supported by the R.U. It is an Alcatel-Lucent 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. Manufactory plant: It identifies the manufacturing plant within the company. 4 characters to be used. Unit serial number: This number specifies the manufacturing chronological number of this R.U. type (in the current year). Date identifier: The date identifier specifies the meaning of the date field. The following codes are standardized: 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. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. TOS63017_V3.1-SG-R9.6-Ed1 Module 3.5 Edition 1 Section 3 · Module 5 · Page 36

4 Remote inventory

How to retrieve it From Network Elements list in MS-GUI to get all the NEs’ boards remote inventory provided as text file for one NE at a time commands to use: “Upload Remote Inventory” and “Display Remote Inventory” the file is saved on the user’s PC

remote inventory provided as a list in the MS-GUI for one or more NEs at a time commands to use: “Global Remote Inventory” and “Apply”

From Equipment View refer to the documentation of the specific equipment




4 Remote inventory

Workflow 1350 OMS

“

” ly p Ap

R al b o Gl

CSV file A CSV file B CSV file C

I

Text file: RI of C

“Glob al RI” (3 x C 6 files SV + 3 x tx

text file A text file B text file C

t)

Uploa d RI 1 file (1 x tx t)

y RI Displa E C) N (e.g.

C

B text file C A

User’s PC

Overall list in MS-GUI: A, B, C

NEs RI: Remote Inventory

3 · 5 · 38



“Upload Remote Inventory” creates a text file for the selected NE in the 1350 OMS EML’s server: •directory: /usr/Systems//data/ri/ •file name: _.ri [e.g. 103_2.ri]

“NE identifier” can be read in the “Network Elements” list in the “Identifier” column. Every further “Upload Remote Inventory” on the same NE overwrites the previous text file. “Display Remote Inventory”: •it uploads the text file from the 1350 OMS EML’s server and puts it in the user’s PC. The text file could have been generated either by means of “Global RI” or “Upload RI”. •

:\tmp\runtimeDir\\\\displayRI\script\_.txt [e.g. C:\tmp\runtimeDir\151.98.33.94\paolo_5036\EML_1-9.6\displayRI\script\103_2.txt]

•and then opens that file.

“Global Remote Inventory” : •it creates in the 1350 OMS EML’s server: •

one CSV file per NE

•

one text file per NE as the one created by means of “Upload Remote Inventory”, or overwrites it if already present in the server

•directory: /usr/Systems//data/ri/ •CSV file name: GLOBAL_RI_yyyy-mm-dd_hh-mm-ss.ri [e.g. GLOBAL_RI_2012-04-21_21-53-55.ri]


4.1 Remote Inventory as text file for a single NE





Upload 1. In the Network Elements list, select the NE 2. Right-click and select “Actions Upload Remote Inventory” 3. Confirm the choice with “Yes” 4. Wait for the message “Operation successfully completed”





Display 1. From Network Element list, select the NE 2. Right-click and “Search Display Remote Inventory”




_


Export the file By default, the file is saved in the PC. It’s at user disposal.

:\tmp\runtimeDir\\\\displayRI\script




Exercise Select a NE and ask for a global remote inventory. Save the file





4.2 Remote Inventory as a list in the MSGUI for one or more NEs




4.2 Remote Inventory as a list in the MS-GUI for one or more NEs

How to retrieve

3. Wait for the “GRI Status” equal to “Completed” 1. From the NE list, select one or more supervised NEs, and “Actions Global Remote Inventory”

2. Click on “Global Remote Inventory”

4. “Apply” 3 · 5 · 45 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance




Result as a list in MS-GUI





Export Remote Inventory data to the local PC 1. Select the rows to be exported

2. Click on the “Export data” icon

3. Save the CSV file




5 Resetting an NE from Equipment View





Example for 1660 SM R4.6 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. The communication between the NE and the OS is lost for a few minutes.

Click on “Restart NE” 3 · 5 · 49 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance




Example for 1850 TSS-320 R4.0 1. Select the Equipment Controller board

2. In the “Restart” box, select “Command Mode = FRCD” and then “Save” 3 · 5 · 50 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance


For other kinds of equipment, the commands and associated menus to be selected into the equipment view are specific for each single NE type, so please refer to the relevant Operator Handbooks or Student Guides.



Example for 1830 PSS-32 R3.6 1. Select the Active EC (Equipment Controller board) 2. Select the “Reboot” folder

3. Select “Warm Reboot” or “Cold Reboot”

4. “Submit” 3 · 5 · 51 System Operation · NE Management 1350 OMS EML · R9.6 Operation and Maintenance


For other kinds of equipment, the commands and associated menus to be selected into the equipment view are specific for each single NE type, so please refer to the relevant Operator Handbooks or Student Guides.


End of module NE Management





@@SECT LE Section 3 System Operation

Module 6 Q3 NE simulator and NE MIB backup and restore TOS63017_V3.1-SG-R9.6-Ed1 Module 3.6 Edition 1




Blank page

3·6·2


System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Perform the NE MIB backup/restore either by MS-GUI or Equipment View Operate the simulator for QB3 Network Elements

3·6·3 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view!

Page

1 Principles & FTS 4G TL1 equipment and 1678MCC (R4.3 and later) 1.1 “Single click MIB Backup” command 1.2 “Multiple NE MIB Backup” command 1.3 Job and Session management: Backup 1.4 Job and Session management: Restore 1.5 Examples of MIB backup/restore from Equipment View 1830PSS: Backup 1830PSS: Restore 4G TL1 equipment and 1678MCC (R4.3 and later): Procedure 1850TSS-320 backup: Current Database  Backup Database 1850TSS-320 backup: Backup Database  FTP server 2 Q3 NE simulator




7 9 15 20 25 34 40 44 45 47 48 49 52






1 Principles & FTS




1 Principles & FTS

Q3, SNMP, 4G Q3 equipment

1350OMS-EML modification

file

backup

NE active MIB


activate

restore

Not active MIB


The NE modifications carried out by means of the OS (or 1320CT) are performed directly on the NE MIB. In case of Q3, SNMP or 4G Q3 NEs, the backup procedure copies the NE MIB into a file in the OS, which location into the server is: /usr/System//swdl/swdlserv/data//B Where X is the “NE identifier” parameter (it can be retrieved by the “Properties” of the NE), while Y identifies different backups for the same NE. In case of 1830PSS NE, the backup database can be saved and retrieved to/from a TFTP (or SFTP) location, which normally resides on the 1350OMS server and that is presented by default as: /usr/System//swdl/swdlserv/data//U Where X is the “NE identifier” parameter. It can be retrieved by the “Properties” of the NE. The user can however choose a location other than the one proposed by the system.


1 Principles & FTS

4G TL1 equipment and 1678MCC (R4.3 and later) EML

modification

NE

Copy Remote File from NE to FTP server backup Current Database restore


file Copy Remote File from FTP server to NE

Backup Database


The NE modifications carried out by means of OS (or 1320CT) are performed directly on the NE current database (called “Primary Backup Database” in TSS-320, or “Running Database” in TSS-100). The backup copies the Current Database into the Backup Database in the NE (called “Secondary Backup Database” in TSS-320, or “Backup Database” in TSS-100). The Backup Database can be saved/retrieved to/from an FTP location, which normally resides on the 1350OMS server (which is normally presented by default). The user can however choose a location other than the one proposed by the system (see next slides). Ref to the restore procedure, once the backup files have been copied from the FTP server to the Backup Database, it must be activated to the Current Database (restore).


1 Principles & FTS

Simulator DB DB

1350 OMS SDH

USM USM USM USM

Network Network Physical Physical Resources Resources

AS

AS-IM DB DB

NPR-IM Q3 EML-IM

NE NE simulator simulator

NEs IDs

DB DB

NE NE

3 · 6 · 10 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance

DB DB



D E T R A T S

1 Principles & FTS

Simulator [cont.] Work on an NE or on the NE simulator, but never on both The NE simulator is used in case of: DCN failure: the NE simulator is the only way for the 1350OMS-EML operator to look up the NE's configuration (the configuration stored at the time of the last alignment).

off-line configuration restoration of the NE MIB

The simulator can be started only if the NE is in the “OS isolation” state

The simulator is only available for some releases of Q3 NEs.



The NE simulator is the NE software which runs on the 1350 OMS EML. The availability of the NE simulator depends on the type (only Q3) and version of the NE. The NE simulator is started up (and stopped) manually by the 1350O MS EML operator. The system never automatically starts or stops the NE simulator.


1 Principles & FTS

Simulator [cont.]

1350 OMS EML Simulator simulator MIB

Simulator Align up Q3 NE

Simulator Align down

active MIB

activate

not active MIB

By default, the Simulator can be started only once at a time on a given 1350 OMS system instance 3 · 6 · 12 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance


From NE equipment view: Align up: Align down: Activate:

menu Supervision

Simulator

menu Supervision menu Supervision

Simulator

Align up Simulator

Align down

Activate


1 Principles & FTS

Job and Session File Transfer Scheduler (FTS)

Job

Job 1

Type

Session 1 NE1 NE2 NE3 Session 2 NE4 NE5 Job 2 Session 1 NE6 NE7

NE MIB Backup NE MIB Restore NE Software Package Download

Activation Immediate Deferred

Timetable the Backup/Restore/SwDw is executed at the same time for the NEs of a session Sessions: one at a time e.g. Session 2 is executed when Session 1 is over

NE8 3 · 6 · 13 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance


File Transfer Scheduler launches, for each session, the maximum number of simultaneous file transfer allowed (<=10 for each involved LAN: then the maximum simultaneous file transfer, inside a session, is 10 multiply by the number of involved LAN). The maximum NE number for any session is 90 but there is no limit regarding the maximum session number in a job.


1 Principles & FTS

Backup and Restore from FTS “Single click MIB Backup” command in NE list

Backup only

for only one NE a Job and its Session are created automatically activation time: the Job is activated as soon as the “Single click MIB Backup” command is issued

“Multiple NE MIB Backup” command in NE list

Backup only

for one or more NEs a Job and its Session are created by the user in one shot activation time immediate: the Job is activated as soon as it is created deferred: the user can set an activation date/time

Job and Session management

Backup and Restore

for one or more NEs Jobs and Sessions are created by the user: first the Job, then its Session/s. activation time immediate: the job must be activated by the user deferred: the user can set an activation date/time




1.1 “Single click MIB Backup” command





Execution The procedure is the same for all the families of NEs

From the Network Element list, select the desired NE, right click and “Actions

Single click MIB Backup” This message means that the backup is started. To check the outcome, see next slides. 3 · 6 · 16 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance


The backup files are put into the 1350OMS server directory: /usr/System//swdl/swdlserv/data//U Where X is the “NE identifier” parameter. It can be retrieved by the “Properties” of the NE. In case of Q3 NEs, the backup overwrites the simulator MIB.



Check: Jobs list Issue the job list by

“Search File Transfer Scheduler Jobs”

Verify the Job status: wait until it becomes “Successful”

NE user label

Date

Local time





Check: failure analysis

Backup Report Example for 1850TSS-320 If you get such a message, open the equipment view System Management Initialize and Upgrade In-Service Upgrade Remove Old Upgrade

Successful backup

Failed backup




Exercise Select a NE and perform a single click backup on the training platform.





1.2 “Multiple NE MIB Backup” command





Execution 2. Edit the Job Name

1. Select one or more NEs Actions Multiple NE MIB Backup





Execution [cont.] Immediate: the backup is executed upon Apply Deferred: the backup is executed at the time chosen by the user

3. Choose

4. For “Deferred” 5. Apply 3 · 6 · 22 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance




Execution [cont.] Immediate

Deferred

Wait for Status = Successful 3 · 6 · 23 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance



Exercise Select few NE‘s and perform a multiple backup on the training platform.





1.3 Job and Session management: Backup





Procedure 1. Select “Actions File Transfer Scheduler Create Job” 2. Assign a name to the new job, whose “Type” must be “MIB Backup” 3. Set the job periodicity (immediate, deferred): for scheduled backup, select “Deferred” 4. Set the periodicity 5. Issue the Job list by “Search File Transfer Scheduler Jobs” 6. Right click on the new job and issue “Actions Create Backup

Session” 7. In the “Backup Session Creation” window, choose the desired NE for backup 8. Right click on the new job and issue “Actions Activate Job”





Step 1 and 2: job creation and job type


File Transfer Scheduler Create Job” 2. Assign a name to the new job. Select type “MIB Backup”





Step 3 and 4: time scheduling

Available for “Deferred”

1. The user can specify a duration in hours, after which the job will be automatically stopped





Step 5 and 6: job list and session creation 2. Right click on the new job and

“Actions Create Backup Session”

1. Issue the Job list by “Search

File Transfer Scheduler Jobs”





Step 7: NE(s) selection

1. Choose the NE(s)

2. Apply 3 · 6 · 30 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance




Step 8: job activation

1. Right click on the new job and

“Actions

Activate Job” The Job is “waiting” its Activation Time

The Job has been successfully completed





Other actions on Backup jobs A Backup job can be: Edited (if not pending) to modify its periodicity (immediate or deferred; periodic) Aborted (if Waiting) Deleted (if not pending)

Multiple sessions can be created in a single job: choose “Create Backup

Sessions” Backup sessions can be retrieved by “Search

Backup Sessions”

The status of an activated backup job can be retrieved by “Search

Status”

“Action” • is not available if the job is Running • is available if the job is Waiting 3 · 6 · 32 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance



Job

Exercise 1.Using the scheduler, create a backup session, details should be given by the instructor. 2. Check that the backup is done.





1.4 Job and Session management: Restore





Restore Procedure 1. 2. 3. 4.

Select “Actions File Transfer Scheduler Create Job” Assign a name to the new job, which “Type” must be “MIB Restore” Issue the Job list by “Search File Transfer Scheduler Jobs” Right click on the new job and issue “Actions Create Restore

Session” 5. In the “Restore Session Creation” window, choose the desired NE and the backup file to restore Activate Job” 6. Right click on the new job and issue “Actions





Step 1 and 2: job creation and job type 2. Assign a name to the new job. Select type “MIB

Restore”


File Transfer Scheduler Create Job” Immediate only





Step 3 and 4: job list and session creation 2. Right click on the new job and

“Actions Create Restore Session”

1. Issue the Job list by “Search

File Transfer Scheduler Jobs”





Step 5: session configuration 1. Select the NE 2. Select “Yes” to automatically activate the restored MIB, “No” otherwise (*) 3. Select the backup file 4. Highlight 5. Apply

To assign a second NE, repeat the steps from 5a through 5c 3 · 6 · 38 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance


MIB Active Flag •Meaning •

No (False): after the restore procedure has been completed, the operator must activate the new MIB from Equipment View as described later on in this module.

•

Yes (True): the restored MIB is automatically activated at the end of the restore.

•Effectiveness (at the time the Student Guide was developed) •

for 1830PSS, after the backup file has been restored on the NE, an automatic restart will occur in any case, leading to the new MIB activation.

•

for OMSN (e.g. 1660SM), “MIB Active Flag” is disregarded: the restored MIB is never activated automatically. The operator has to activate.

•

for 1850TSS-100 R3.1 and 1850TSS-320 R4.0, “MIB Active Flag” is operational.



Step 6: job activation

1. Right click on the new job and “Actions

Activate Job”

Wait until the Job has been successfully completed




1.5 Examples of MIB backup/restore from Equipment View





Q3, SNMP, 4G Q3 equipment: Backup

2. Enter a name

1. Select “Download

Mib management” 3. Click on “Backup” SNMP NEs: The commands and associated menus are specific for each single NEs. So, please refer to the Operator Handbooks and to the Training Manuals of each single NE type. 3 · 6 · 41 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance


In case of Q3, SNMP or 4G Q3 NEs, the backup procedure copies the NE MIB into a file in the OS, which location into the server is: /usr/System//swdl/swdlserv/data//B Where X is the “NE identifier” parameter (it can be retrieved by the “Properties” of the NE), while Y identifies different backups for the same NE.



Q3, SNMP, 4G Q3 equipment: Restore Backups created by means of FTS (File Transfer Scheduler) fts_YYYYMMDDhhmmx

1. Select the backup to be restored (*) 2. Click on “Restore”; wait for the message

“Restored completed” 3. Click on

“Activate” 3 · 6 · 42 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance


The 1350OMS proposes for the restore only the MIBs that were backed-up from this specific NE.


1 NE MIB backup/restore

Notes about Q3 NEs – e.g. 1660SM Three methods for managing backup/restore: File Transfer Scheduler Simulator Mib management

(from MS-GUI) (from Equipment View) (from Equipment View)

FTS and Simulator: 1350OMS-EML keeps only one backup file, that is the last one The backup performed by means of Simulator overwrites the one performed from FTS, and vice versa

The backup file can be restored by means of Simulator or FTS FTS can restore the backups created by means of “Mib management”, too

Mib management: every backup creates a new backup file in 1350OMS-EML “Mib management” can restore only the backups created by means of “Mib management” 3 · 6 · 43 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance




1830PSS: Backup From the “Show Equipment” view, issue “Administration Database Backup and Restore” Choose the SFTP protocol Provide the root UserID and Password

The default location in the 1350OMS server is proposed by the system Click “Apply” and then “Backup”

Wait for the procedure results 3 · 6 · 44 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance


The URL absolute path is: /usr/System/EML_/swdl/swdlserv/data//U The backup performed by means of Equipment View overwrites the one performed by means of File Transfer Scheduler, and vice versa.



1830PSS: Restore From the “Show Equipment” view, issue “Administration Database Backup and Restore” Choose the TFTP or the SFTP protocol If SFTP is chosen, provide the UserID and Password of the 1350OMS’s server The default location in the 1350OMS server is proposed by the system. Change the filename to be restored if desired. Click “Apply” and then “Restore” The user is logged out and the system is warm restarted. After the reboot, check the restore procedure results in this window. 3 · 6 · 45 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance


The URL absolute path is: /usr/System/EML_/swdl/swdlserv/data//U



1830PSS: Restore [cont.] After the reboot, check the results of the restore operation. “Administration Database Backup and Restore”





4G TL1 equipment and 1678MCC (R4.3 and later): Procedure Backup 1. Back-up the current database on the backup database 2. Copy the backup database on an external archive by using the Remote file copy from NE to FTP server feature

Restore 1. Copy the backup files previously saved on an external archive by using the Remote file copy from FTP server to NE feature 2. Activate the backup database

In the following, an example based on a 1850TSS-320 R4.0 is shown. Consider that the commands and associated menus to be selected into the equipment view are NE specific, so please refer to the Operator Handbooks and to the Training Manuals of each single NE type.





1850TSS-320 backup: Current Database

Backup Database

1. From the “Show Equipment” view, issue “System Management DB Management Database DB Backup” and confirm the choice clicking on “Yes” Wait for the confirm notification

This message comes up immediately 3 · 6 · 48 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance

This message comes up after some time COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.


Perform


1850TSS-320 backup: Backup Database

FTP server

2. From the “Show Equipment” view, issue “System Management DB Management Copy From NE to FTP”

Remote File

Perform

Wait for the completion notification

The system automatically inserts the needed FTP user and password

The system proposes the 1350OMS server as host location. Port must be 21.

Click “Apply” and then confirm with “Yes”



The URL absolute path is: /usr/System/EML_/swdl/swdlserv/data//U



Restore example with 1850TSS-320 R3.1 1. From the “Show Equipment” view, issue “System Management DB Management Copy From FTP to NE”

Remote File

Perform

Wait for the completion notification

The system automatically inserts the needed Location

The Command Mode can be “Normal” or “Forced” (*)

Click “Apply” and then confirm with “Yes” 3 · 6 · 50 System Operation · Q3 NE simulator and NE MIB backup and restore 1350 OMS EML · R9.6 Operation and Maintenance


The URL absolute path is: /usr/System/EML_/swdl/swdlserv/data// (*) If “Forced”, the operation is performed regardless of mismatch on SID, SW version type, etc.



Restore example with 1850TSS-320 R3.1 [cont.] 2. From the “Show Equipment” view, issue “System Management DB Management Database Restore DB” Eventually choose “forced” (not recommended) and then “Apply” If “Forced”, the operation is performed regardless of mismatch on SID, SW version type, etc.

Wait for the confirm notification The NE will then automatically restart

N.B.: If “No” was chosen during the restore procedure subsequent to a “Single click MIB backup”, this is the “Restore DB” procedure the operator must execute after the restore job completion




2 Q3 NE simulator




2 Q3 NE simulator

Loading the simulator with a configuration FROM EQUIPMENT VIEW Copy the configuration of the real NE into the simulator “Supervision Simulator Align up”




2 Q3 NE simulator

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

Simulator Start Start the simulator: Supervision Modify the configuration (note 2: 1350OMS-SDH can do it) Stop the simulator: Supervision Simulator Stop Start supervision (changes done in the simulator don't appear) Align the simulator's MIB down to the NE Supervision Simulator Align down 9. Activate the new configuration Supervision Simulator Activate 4. 5. 6. 7. 8.

wait for communication to be re-established following “OS isolation”



note 1: Caution: stopping the equipment supervision in order to use the simulator, the “OS isolation” state will occur after a few minutes. note 2: The 1350OMS-SDH can update the simulator. This feature is used for the equipment controller card replacement procedure (i.e. in OMSN).


2 Q3 NE simulator

Off-line browsing FOR A SUPERVISED EQUIPMENT in OS ISOLATION state: 1. Start the simulator: Supervision 2. Display the configuration

Simulator

Start

Simulator

Stop

last known configuration last NE alarm state

3. Stop the simulator: Supervision




2 Q3 NE simulator

NE simulator as NE MIB backup NE simulator can help the user keep an NE MIB backup aligned with the modifications carried out by means of the Equipment View or Craft Terminal. Every command issued from Equipment View/CT raises the “MIB backup misalignment”. You can see it in Alarm Surveillance. To get that alarm disappear the user must execute the “Align Up” of the simulator.




End of module Q3 NE simulator and NE MIB backup and restore





@@SECT LE Section 4 Maintenance Applications Module 1 Alarm management





Blank page

4·1·2


Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: handle the Alarm Surveillance application for current and historical alarms

4·1·3 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 Displaying current alarms 2 Alarm debouncing 3 Creating, modifying and deleting an alarm sublist 4 Performing actions on current alarms 5 Handling the Alarm Surveillance facilities 6 Displaying the alarm history 7 Administrating the AS




Page 7 20 28 37 43 50 59





Page

1 Displaying current alarms





AS principles Real Time Management

Static analysis

Display alarms

Manage alarms

Display alarms

Current

Archive

Historical

alarms

alarms

alarms

Alarm Surveillance

Raise and clear alarms

Network resources 4·1·8



The Alarm Surveillance function for the EML is supported by the Converged Fault Management component of the 1350OMS. 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 (HISTORICAL ALARMS). Current alarms “live” alarms (permanently refreshed) Historical alarms auto-purging “live” alarms that are automatically removed from the Current Alarms list as soon as they rise because the operator has set such a filter criteria manual purging alarms that are manually removed from the Current Alarms list by the operator overflow alarms removed from the Current Alarms list because it is full (max 10,000 alarms) “acknowledged AND cleared” alarms synchronization



The available GUIs for alarm management Web Portal

Operation

WDM

PKT

Alarms

SDH

EML

Global: EML + WDM + PKT + SDH + Current Events Log

4·1·9



The “Global Alarm” provides a GUI for the management of the alarms related to all the applications installed on the server (e.g. EML, SDH, PKT). From the Global Alarm Management the user can exploit the same feature described in the following for the EML Alarm Management component. All the Fault Management GUIs provide the user with the same look and feel. 1350OMS supports a single common fault management GUI which provides presentation functions for all managed network elements. The Fault Management GUI: Presents a dynamic view of all current alarms in the managed network and also all historical alarms Supports actions on alarms Allows to search, sort and filter the alarm lists Allows customized alarm list configurations in terms of attributes displayed and ordering of attributes Supports the saving of multiple user defined alarm sub-list configurations The operator can select an alarm and contextually navigates to permitted operations screens (i.e. the equipment view) for the selected entity. The menu items presented to the user are contextual to the entity selected and to the user profile.



The available GUIs for alarm management [cont.] Global

Default sublists

EML

4 · 1 · 10 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance

SDH

PKT



WDM


Navigating from Equipment View to Alarm Surveillance Q3 and 4G Q3 NEs

“Diagnosis Alarms NE (or Equipment, Transmission, External Points) Alarms… to open the related Alarm Management GUI





Navigating from Equipment View to Alarm Surveillance 1850TSS-320/160

1. Select the node 2. Click on “NE (or Equipment,

Transmission, Synchronization, External Points) Alarms to open the related Alarm Management GUI





Navigating from Equipment View to Alarm Surveillance 1830PSS

Click on “Alarms” to display all the NE alarms

Or, click on the “Fault” button, then select the Alarm Category and click

“Submit”



For other kinds of 4G TL1 NEs, please refer to the specific equipment documentation.



EML Current Alarm Management main window Sublist’s alarms

Sublists

Message area





Display preferences By selecting/deselecting the specific option it’s possible to show/hide the related area.

e.g. only the alarm sublist is shown



Operator can change GUI visualization also by using the icons on the Toolbar:



Paginate sublist It’s possible to show/hide paginate sublist and, in case of paginate, to define the number of rows per page (max = 200).





Freeze data 1. Do “Freeze data” 2. The counters in the sublist summary area are updated by the new alarms, while … 3. … the sublist content area is not.





Displaying more information Select an alarm in the sublist “Alarm More Info” or

Double click the alarm

Different details can be displayed

4 · 1 · 18



Further actions are possible from “More Alarm Information Window”: •Print or Export the Alarm Information •Navigate to ... •

the related EML-USM

•

the NE Creation GUI, in case of “NE autodiscovery” warning alarm



Monitoring new alarms AS GUI can be kept minimized. It will be automatically raised up by new alarms. 1.Check the option in the menu View

Auto-Raise

2.Minimize the window




2 Alarm debouncing




2 Alarm debouncing

Principles [cont.] Alarm Clear Event

Alarm Raise Event

To End-Customers, T1-T6 is the faulty period as a whole, in which the resource is not able to support a given function

Alarm ON Alarm OFF T1

T2 T3 T4 T5

T6

Resource Name

Probable Cause

Event Time

Clear Time

Repetition Counters

XXXX

YYYY

T1

T2

0

XXXX

YYYY

T3

T4

0

XXXX

YYYY

T5

T6

0

Resource Name

Probable Cause

Event Time

Clear Time

Repetition Counters

XXXX

YYYY

T1

T6

2

NO Debouncing 4 · 1 · 21 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance

Debouncing ON


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 reduces the number of records stored/displayed in the AS Current Alarm List and the related traffic to the Network managers (1350OMS-SDH, 1350OMS-PKT, etc).


2 Alarm debouncing

Architecture Overview (example for Q3 and SNMP NEs)

4 · 1 · 22



SNML: SDH Network Management Layer


2 Alarm debouncing

Configuration for Q3, 4G Q3 and SNMP equipment

1. In the MS-GUI, issue

“Actions EML Configure Alarm Debouncing”




2 Alarm debouncing

Configuration for Q3, 4G Q3 and SNMP equipment [cont.] 2. In case of EML federation, select the desired PNMIM 3a. Type the new Hold Period in seconds for the desired Probable cause(s) 3b. Or, set a Hold period to all the Probable Causes (click “Set to All”) Max=3600 The new values become active in the system after a maximum of 2 minutes, without the need to restart any process. The default value is 180s on any Probable Cause. 4 · 1 · 24 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance

4. “Apply”



2 Alarm debouncing

Alarm Debouncing case

Raise

T1 Raise Clear




T1

T2

T1

T2 T3

2 Alarm debouncing

Alarm Debouncing case [cont.]

T1 T2 T3 T4

T1 T2 T3T4 T5




2 Alarm debouncing

Alarm Debouncing case [cont.]

T1 T2 T3T4 T5 T6

T1 T2 T3T4 T5 T6 Hold Period expiration




3 Creating, modifying and deleting an alarm sublist





Create a new sublist The new sublist is a copy of an existing sublist. Later on, it can be modified.

1. Select a sublist to copy 2. Sublist

New

3. Enter a name and OK 5. The sign (*) is put beside the shared sublist’s name 4. Answer Shared: any operator can see it 4 · 1 · 29 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance


To delete a sublist, select it and then Sublist

Delete.



Modify a sublist To modify an alarm sublist, select a sublist and

“Sublist


Modify”




Sublist DISPLAY parameters Sublist name

Other available attributes (to move to the Displayed Attributes list, select and click on the arrow)

Sublist color (single click to modify)

To display

To hide Do Apply to apply the modifications 4 · 1 · 31 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance



Currently displayed attributes in the sublist (select and click on the arrow to remove from the list)

To change the order, select an attribute and click these arrows


Sublist FILTER parameters 1. Select “Include alarms

matching the following …” 2. It’s possible to modify a filter (Edit) or to create a new one (New)





Sublist FILTER parameters - New Check the box and click “Fewer” to remove the filtering criteria

Choose “More” to add more filtering criteria


Choose “Not” to deny the criteria



Remove all filtering criteria


Sublist SORT parameters To save your sort choice To remove the sort from the repository

To select a saved sort

Right click here to select the sorting order (increment or decrement)

Parameters not used to sort the sublist (select and click on the arrow to use one)

Parameters used to sort the sublist





Sublist TRIGGER parameters Activate this option to start a sound file each time an alarm appears in the sublist To get the warning

blink

To execute a script or a navigation if the number of alarms in the sublist is greater than a given value or for an incoming alarm To execute a script or a navigation if the number of alarms in the sublist is smaller than a given value or for an outgoing alarm 4 · 1 · 35 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance


By executing the script you could, for example, load a particular process as soon as the number of critical alarms exceeds a certain value.


Exercise 1. If possible, create an equipment alarm on a selected NE. 2. Create a sublist wich selects equipment alarms from the selected NE. 3. Check that the alarm appears.





4 Performing actions on current alarms





Reserving / unreserving an alarm Reservation ensures that only one operator is responsible for an alarm. To reserve: 1. select an alarm 2. select “Alarm

Reserve”

To reserve and assign 1. select an alarm 2. select “Alarm

The alarm becomes white

Reserve

and Assign” 3. Specify the operator to whom the alarm must be assigned

To unreserve:

Double-click the alarm

select the reserved alarm select “Alarm

Unreserve”



The reserved alarm becomes white in the list. An alarm can be reserved only if it has not been reserved before by another operator. The operator who can unreserve a given alarm is only the one who reserved it.



Acknowledging an alarm By acknowledging alarms, you indicate that they have been registered. As soon as the alarm becomes cleared, it will be removed from the Current AS and added to the Historical AS. 1. Select one or a group of alarms Acknowledge” 2. Select “Alarm the Acknowledgement attribute changes from NACK (Non ACKnowledged) to ACK (ACKnowledged)

4 · 1 · 39

The alarm becomes grey



The acknowledged alarm is grayed. Acknowledging a cleared alarm is an implicit archiving action. So the acknowledgement will move the cleared alarms into the Historical AS and remove them from the current alarms list.



Manual purge 1. Select one alarm or a group of alarms 2. Select “Alarm Manual

Purge” Purged alarms disappear from the Current alarms list and are moved into the Historical alarm list, if they match the archiving filter.





Generating trouble tickets Trouble ticket = collection of all information about one problem 1. Select a single alarm or a group of alarms 2. Select “Alarm Trouble

Ticket” 3. Confirm the indicator “Trouble Ticket Creation Flag” in the sublist change to YES

This feature requires the installation of a third party software component



A trouble ticket contains at least the information on the problem, but can also include information on the actions performed to solve the problem. The Fault Management component can be customized to interface with the third-party Trouble-Ticketing management product ARS (Action Request System - published by Remedy Corporation).


Exercise Acknoledge the alarm previously created

Time allowed: 1 minute




5 Handling the Alarm Surveillance facilities





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

1. Select an alarm 2. Select ”Window”

“External Applications Related_EmlUsm CreateNe: for NE autodiscovery feature 4 · 1 · 44 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance

1850TSS-100 COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED.

“CreateNe” only in case of NE autodiscovery warnings, to create the correspondent NE. “Related_EmlUsm” to open the equipment view, to the point which raised the corresponding alarm.



Exporting alarms to a file You can export to your PC in a .html , .txt, .CSV file a selection of alarms or a number of pages (if paginate is enabled) To export to a file: 1. In the alarm sublist select at least one alarm Export” 2. Select “File

4 · 1 · 45



By selecting Pages, the page set must be specified: To export the pages 1 and 3: 1;3 To export the pages from 1 through 3: 1-3 Use default: the following attributes are exported whatever the displayed attributes are: Perceived Severity Event Date and Time Friendly Name Alarm Type Probable Cause Name CAL Recording Time Managed Object Class Managed Object Instance Probable Cause Id Clearable Status N.B.: In case of a .ASCII file is chosen for the export operation, it must then be properly parsed by a worksheet application.



Exporting alarms to a file [cont.]

CSV format (the get a better data view, use “Data


Text to column” Excel’s command)




Copy / Paste 1. Select some alarms and do

“Copy” 2. Paste in a text program. The copied alarms can be pasted also in a worksheet application.





Exporting alarms to a printer You can print a selection of alarms or a number of pages (if paginate is enabled) To print: 1. In the alarm sublist select at least one alarm Print” 2. Select “File “Print Management” window opens




Exercise 1. Save a file with the alarm on your PC. 2. Repair the equipment. 3. Check that the alarm is now disappeared.





6 Displaying the alarm history





Description The Historical Alarm List (HAL) contains former current alarms that have been archived through one of the following processes: Auto-purging Manual purging Overflow Acknowledged and cleared alarms Synchronization

Alarms are archived if they match the archiving filter



Auto-purging these alarms have never been inserted in the Current Alarm List (CAL). As soon as they arise, they are sent to the HAL. Manual purging an AS operator manually removes the alarm from the CAL. Overflow Maximum size of the CAL has been reached and alarms are removed from it. Synchronization Alarms that are not confirmed on a synchronization command are automatically cleared by the application. Among them, those which were previously acknowledged are forwarded to the HAL.



Principle CAL or auto purge filter Archiving filter HAL (Public Archive) filter Sublist Main list

Save selection

filter User file


User file

User file

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 Public Archive, or in conjunction with this source.



Starting up 1. Select “FM Historical”

2. Select:

“Retrieve from public archive” OR

“Retrieve from user file” 4 · 1 · 53 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance


Retrieve from user file: it’s meaningful if a user file has been previously created.



Retrieve from public archive

It’s possible to apply filters on the retrieval





Retrieved alarms The main operations on the archived sublists are performed in the same way as for current alarms.





Create a user file 1. 2. 3. 4.

Select one or a group of alarms in a Historical sublist Right click on the selected group and choose “Save As” Enter a file name Click on “Apply”



The directory in which the file will be stored has already been configured by the administrator.



Remove a user file 1. From the Historical Alarm Management window: “Archive

Remove

user file” 2. Select the file to remove and move it to “Selected User Files” list by clicking on the arrow 3. Click “Apply”

To select

To unselect




Exercise Retrieve the alarm from the historical database.





7 Administrating the AS





Advanced feature mechanisms and alarm flow The Current Alarms List (CAL) has a limited size. The operator is provided with several advanced features for managing the overflow. The default size of the CAL is 10000 alarms, that is its maximum size, too.

Trouble Ticket filter ARS

Archive filter

CAL

HAL

Auto-Ack filter AutoPurge filter

Alarm NE 4 · 1 · 60

delete



CAL size The operator can assign the percentage fill level at which a warning is emitted. The operator can also specify the behavior of the CAL when the overflow occurs (wrap/halt). 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 to the current alarms list. 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. Synchronization Because the CAL, for any reason, may become out of step with the network alarms situation, the operator can provoke a synchronization mechanism which performs a global refresh of the CAL checking all the resources involved.



Configuring the AS In the AS-GUI window select

Alarm Sources EML_1_9.5


Administration

IM




CAL Administration WRAP: a quantity of alarms equal to “Overflow Purge Size” are automatically purged to make room for new alarms HALT: new alarms are forwarded to HAL

If “CAL Filling Percentage” > “Warning Filling %” then ...

In case of overflow, the relevant alarm is provided in the AS-GUI and ...

Quantity of alarms in CAL



CAL Administration To view the size of the Current Alarm List, and to customize the parameters relating to overflows and view the current alarm fullness rate. CAL size The operator can assign the percentage fill level at which a warning is emitted. The operator can also specify the behavior of the CAL when the overflow occurs (wrap/halt). 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). The Fault Management component can be customized to interface with the third-party Trouble-Ticketing management product ARS (Action Request System - published by Remedy Corporation).



Archiving filter Choose an option to assign a filtering criteria for archiving Click on “New” to open a window for a new personal filter

Activate the personal filter



Archiving Filter: to archive alarms which are removed from the CAL and should be forwarded to the HAL.



Auto Purge Choose an option to assign a filtering criteria for purging Click on “New” to open a window for a new personal filter



Auto Purge: to divert some incoming alarms automatically to the HAL.



Auto Acknowledge Choose an option to assign a filtering criteria for acknowledging Click on “New” to open a window for a new personal filter



Auto ACK: to acknowledge automatically the incoming alarms.



Aging

Define the status and the time of aging

Filter: to define the alarms for which Aging applies

By Aging the operator can set an action to be done by the system, for those alarms that are in a specified status since a configurable time


Define the action to be done when “aging time” has expired




Aging [cont.]

After the creation of an Aging filter, it must be activated

Click “Apply” to complete the procedure





Trigger

Define the action to be executed, or a navigation, on each incoming alarm Define the action to be executed, or a navigation, on each outgoing alarm Incoming alarm: new alarm Outgoing alarm: cleared alarm 4 · 1 · 68 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance


By enabling Trigger on Incoming or Outgoing alarms the operator can assign an action (execute a script, navigate to NE GUI, send an e-Mail/SMS) for each incoming or outgoing alarm. “Send Mail/SMS” option needs a Mail/SMS service to be configured and activated on the 1350OMS server. Ask the system administrator.



Severity Change

1. Assign a name to the Severity Change rule and choose the new severity Severity Change allows to change the severity of the alarms that match a configurable condition. The new severity is applied to the new raised alarms (not to the current ones).


2. Filter: specify the filter criteria to select the alarms which severity must be changed




Severity Change [cont.]

After the creation, the severity change rule must be activated

Finally, click

“Apply” 4 · 1 · 70 Maintenance Applications · Alarm management 1350 OMS EML · R9.6 Operation and Maintenance



End of module Alarm management





@@SECT LE Section 4 Maintenance Applications Module 2 Performance Monitoring management TOS63017_V3.1-SG-R9.6-Ed1 Module 4.2 Edition 1




Blank page

4·2·2


Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Explain the meaning of the counters Activate the error measurement on the desired points Retrieve and analyze the results

4·2·3 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 Definition of counters 2 Configuring performance points 3 Displaying performance data 4 Performance reports




Page 7 25 37 42






1 Definition of counters





Introduction to SDH performance monitoring Principles: Based on BIP (Bit Interleaved Parity) bytes: Byte Byte Byte Byte

B1: BIP8 (RSOH) B2: BIP24 (MSOH of an STM1 frame) B3: BIP8 (VC4 POH) V5: BIP2 (VC12 POH)

1. Computation of the BIPs (on frame transmission)

Time N+3

N+2 BIP


N

N+1 BIP




Introduction to SDH performance monitoring [cont.] 2. Comparison of BIPs (on frame reception)

Time N+2

N+3

N+1

N

Extraction

BIP computation COMPARE

≠ INCREMENT COUNTERS 4·2·9 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance




Introduction to SDH performance monitoring [cont.] Near End (Node B)

Far End (Node A) V C 1 2

V C 4

M S O H

R S O H

V C 1 2

V C 4

M S O H

R S O H

TX

STM-N

RX

RX

STM-N

TX

R S O H

M S O H

V C 4

V C 1 2

R S O H

M S O H

V C 4

V C 1 2

Byte B1 Byte B2 Byte M1 (B2 return) MS-REI Byte B3 Byte G1 (B3 return) P-REI Byte V5 Byte V5 4 · 2 · 10 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance

P-REI


On Node A the near-end information reflects the performance of the one-way section or path from B to A the far-end information reflects the performance of the one-way section or path from A to B On Node B the near-end information reflects the performance of the one-way section or path from A to B the far-end information reflects the performance of the one-way section or path from B to A



Introduction to SDH performance monitoring [cont.] The performance counters are linked to Termination Points (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

4 · 2 · 11 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance


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, xx:45 for 15-minute periods. Data collection takes place at 00:02 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 based on 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 is a 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 unavailable time period ends 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 Far End Background Block Error FEBC Far End Block Error Count FEBE Far End Block Error FECSES Far End Consecutive Severely Errored Second FEES Far End Errored Second FESES Far End Severely Errored Second FEUAS 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



Other SDH performance counters 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 Monitor on OTN-G.709 frames (Digital Wrapper) There are two BIP-8 bytes carried by the G.709 frames. A BIP-8 byte in the OTU-k header, monitoring the OTU link (Section Monitoring) A BIP-8 byte in the ODU-k header, monitoring the ODU link (Path Monitoring)

1

4

4080

3825

OTUk OH

Client Signal mapped in OPUk Payload

2 3

3824

14 15 16 17

7 8

1

Also, the FEC decoding process gives information about how many errors could be corrected or not in the received frame.

ODUk OH


OTUk FEC


Some types of equipment supported by the 1350 OMS (e.g. 1830PSS) are compliant with the OTN-G.709 ITU-T recommendation (Digital Wrapper), and as such they support PM at Digital Wrapper layer. Digital Wrapper supports a performance monitoring mechanism based on BIP-8, similar to the one previously described for SDH. RS Corrected Count: Number of errors corrected by the FEC RS Uncorrected Count: Number of errors not corrected by the FEC SMBIP8 Error Count: Number of errors counted in the OTU-k BIP-8 (Section Monitor) PMBIP8 Error Count: Number of errors counted in the ODU-k BIP-8 (Path Monitor) SM Errored Seconds: Number of errored seconds counted in the Section Monitor PM Errored Seconds: Number of errored seconds counted in the Path Monitor SM Severely Errored Seconds: Number of errored seconds counted in the Section Monitor PM Errored Seconds: Number of severely errored seconds counted in the Path Monitor SM Unavailable Seconds: Number of unavailable seconds counted in the Section Monitor PM Unavailable Seconds: Number of unavailable seconds counted in the Path Monitor



Performance Monitoring on FEC The equipment supported by the 1350OMS (e.g. 1830PSS) and compliant with the OTN-G.709 ITU-T recommendation (Digital Wrapper) also supports PM at FEC layer: FEC is inserted by the transponder on the colored transmission side, and the receiving transponder is able to detect errors and possibly correct them while decoding the FEC. PM on FEC layer gives information about the signal quality between the transmitting transponder colored output and the receiving transponder colored input. PM on WDM signal (FEC)



CS (Corrected Second): a second in which at least a corrected error is detected US (Uncorrected Second): a second in which at least an uncorrected error is detected BEC (Background Error Corrected): a FEC corrected error that occurred outside a SCS (result is divided by 512) SCS (Severely Corrected Second): a second with a FEC layer defect or at least one FEC uncorrected block or more than 33,538,048 FEC corrected errors BBU (Background Block Uncorrected): a FEC uncorrected block that occurred outside a SUS SUS (Severely Uncorrected Second): a second in which a FEC layer defect occurred or in which more than 33,538,048 FEC blocks were uncorrected UAS (UnAvailable Second): A UAS is a second that is part of an unavailable time period. An unavailable period is a period of time which begins on the occurrence of ten consecutive SUS events. These 10 seconds are considered to be part of an unavailable time period, so these 10 seconds are UnAvailable Seconds. An unavailable time period ends when ten consecutive non-SUS events occur. BER (Bit Error Rate): not a primitive counter; the EML computes the BER based on the BEC counter QF (Q-Factor): not a primitive counter; the EML computes the Q-Factor based on the BER



Performance Monitoring on Ethernet It allows to analyze traffic behavior on a specific Ethernet interface. Incoming and Outgoing traffic directions are analyzed.

Received Received packets packets Port 1

Port 3

Port 2

Port 4

Discarded Discarded Packets Packets




Transmitted Transmitted packets packets


Performance Monitoring on Ethernet [cont.] The system supports Ethernet Aggregated octet/frame counters and also octet/frame counters on per flow (service) basis.

OUT FLOW

SDH port A

IN FLOW

AU4

Received frames

SDH XC

ETS XC

Monitored object:

Transmitted frames

LOCAL Eth. Port


REMOTE Eth. Port

COPYRIGHT © ALCATEL-LUCENT 2012. ALL RIGHTS RESERVED. Section 4 · Module 2 · Page 18


Transmitted frames Received frames


Managed Ethernet performance counters TRCO (Total Received Correct Octets): total number of octets of Ethernet frames received correctly by the Ethernet Interface, including Ethernet header characters TRCF (Total Received Correct Frames): total number of Ethernet frames received correctly by the Ethernet Interface TTO (Total Transmitted Octets): total number of octets of Ethernet frames transmitted out by the Ethernet Interface, including Ethernet header characters TTF (Total Transmitted Frames): total number of Ethernet frames transmitted out by the Ethernet Interface TRDF (Total Received Discarded Frames): total number of Ethernet frames on incoming signal which were chosen to be discarded TTDF (Total Transmitted Discarded Frames): total number of Ethernet frames on outgoing signal which were chosen to be discarded TRSEF (Total Received Service Errored Frames): total number of Ethernet frames received incorrectly by the Virtual Ethernet Interface

Counters are sampled with “1h OR 15 min” AND 24h granularity periods. All counters are free-running. This means that they are not reset at the end of the sampling period. For this reason, reports on Ethernet counters are available in EML 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. either 15min or 1h). For these kinds of board, EML supports the two granularity types, with the following configuration notes and constraints: The desired granularity is set in the configuration file of the EMLIM supporting the NE (EMLIMCORBASNMP) during the system configuration (see details in the Administration handbooks and Training Manuals); EMLIM then sets the monitoring granularity on the NE at the Start Supervision. Due to the fact that the configuration file is unique for all the EMLIMCORBASNMP instantiated in the system, the consequence is that the selected granularity should apply to the ISA-ES boards of the whole network supervised by EML. 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 EML on an ISA-ES with a different monitoring granularity period, all the PM points of that NE switch to the granularity configured in EML.



Performance Monitoring on Ethernet: Aggregated Counters Aggregate counters on Received Frames: •TRCF •TRCF Broadcast •TRCF Multicast •TRCF Unicast •TRCO •TRDF •TRSEF

IN FLOW

OUT FLOW

AU4

Received frames

SDH port A

Aggregate counters on Transmitted Frames: •TTDF •TTF •TTF Broadcast •TTF Multicast •TTF Unicast •TTO

Transmitted frames

Transmitted frames


Received frames


TRCF: number of Total Received Correct Frames TRCF-Broadcast: number of Total Received Correct Frames of Broadcast type TRCF-Multicast: number of Total Received Correct Frames of Multicast type TRCF-Unicast: number of Total Received Correct Frames of Unicast type TRCO: number of Total Received Correct Ethernet Octets TRDF: number of Total Discarded Frames on Incoming signal TRSEF: number of Total Received Service Errored Frames TTDF: number of Total Discarded Frames on outgoing signal TTF: number of Total Transmitted Ethernet Frames TTF-Broadcast: number of Total Transmitted Ethernet Frames of Broadcast type TTF-Multicast: number of Total Transmitted Ethernet Frames of Multicast type TTF-Unicast: number of Total Transmitted Ethernet Frames of Unicast type TTO: number of Total Transmitted Ethernet Octets



Performance Monitoring on Ethernet: Per Flow Counters

Ingress Flow counters: •TRCFg •TRCFy •TRCOg •TRCOy

IN FLOW


OUT FLOW

AU4

Received frames

SDH port A

Egress Flow counters: •TTFg •TTFy •TTOg •TTOy


TRCFg: number of Total Received Correct green Frames TRCFy: number of Total Received Correct yellow Frames TRCOg: number of Total Received Correct green Ethernet Octets TRCOy: number of Total Received Correct yellow Ethernet Octets TTFg: number of Total Transmitted green Ethernet Frames TTFy: number of Total Transmitted yellow Ethernet Frames TTOg: number of Total Transmitted green Ethernet Octets TTOY: number of Total Transmitted yellow Ethernet Octets


Transmitted frames

Notes page only (standard notes text field extended) Some NEs managed by 1350 OMS (e.g 1626LM and 1830PSS) also support the so-called “PCS” (Physical Coding Sublayer) or “Ethernet Layerview! 1” Performance Monitoringon some of their Ethernet interfaces . Switch to notes They are normally available on 1GBEth or 10GBEth interface and are based on how the Physical Coding Sublayer of the Ethernet protocol stack manages the coding structure of the Ethernet frame. In case of 1GBEth interface, the 8B/10B coding is used: Tables 36-1 and 36-2 of the 802.3 standard (2005 ed., section 3) list all possible combinations of received encoded word (10B) for each initial word (8B) according to their running polarity (non-zero disparity blocks must alternate in polarity) Based on those tables, an error event is raised when the received word is found in Tables 36-1 or 36-2 but in the column with wrong disparity, meaning that an error occurred during transmission => “RDE” event (Running Disparity Error) the received word is not found in any of both tables => “Invalid Word” event In case of 10GBEth, the 64B/66B coding is instead used When the receiver detects a wrong configuration of the 2 synch header bits of the 66B block, an errored block is detected Errors are accumulated in a counter (called ICG=Invalid Code Group) Based on the ICG, the following SDH-like counters are processed by the system: ES At least one ICG or one LOS or LOF within the second SES Number of ICG corresponding to a BER<10E-5 or one LOS or LOF BBE ICG occuring outside an SES 4 · 2 · 22 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance




Analog performance monitoring Some WDM NEs (e.g. 1626LM, 1620LM, 1696MS, 1830PSS) support the monitoring of analog values. Basically, the Analog PM involves all the measurements available in the NE USM at Equipment (or Board) Instantaneous Measurements. These include: Tx Optical Power Level Rx Optical Power Level Bias Current Level Temperature Etc. for boards such as Transponders, Mux/Demux, Amplifier, etc.

EML is in charge of sampling and storing the input/output power values in the PM DB. The user can then select Monitoring Points to generate the Reports. The sampling periods are 15m & 24h.





T-MPLS performance monitoring Some equipment supporting T-MPLS (e.g. 1830TSS-320 R3.0), provides the monitoring of some specific counters. These include: MINB (Monitored Incoming Number of Bytes) MINP (Monitored Incoming Number of Packets) MONB (Monitored Outgoing Number of Bytes) MONP (Monitored Outgoing Number of Packets)

Outgoing and Incoming Bytes and Packets are counted per port.




2 Configuring performance points





Threshold tables (Q3 and 4G Q3 NEs) 1. Open an equipment view 2. Select the menu:

Configuration Performance Threshold Tables In this window, you can perform the following operations on a thresholds table: create modify display delete attach (link to a TP entity) (Some operations are forbidden if the node is managed by 1350OMS-SDH)

3. Select the table from the list (except for creation) 4. Click the button representing the action you want to carry out 4 · 2 · 26 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance


N.B.: In this chapter only the configuration of SDH performance points and Analog PM on Q3, 4G Q3 and 1350TSS-320 R3 equipment are taken into consideration. Performance points on 1830PSS equipment are automatically enabled as soon as the related interface is set in service by the operator or by the management system. For the configuration of Ethernet, T-MPLS and FEC performance points, and for other kinds of equipment, please refer to the Operator Handbooks and Training Manuals of the specific NE family.



Example of threshold tables (Q3 and 4G Q3 NEs) “Display” gives this view


Section / Pa th type STM-N - RS STM-N – MS STM-1 – RS STM-1 – MS VC4 VC3 VC12


Block size (bits) 19440 x N 801 19440 801 18792(261x9x8) 6120 1120

Blocks per fra me 1 24 x N 1 24 1 1 0,25

Blocks per second 8000 192000 x N 8000 192000 8000 8000 2000


BIP type BIP – 8 BIP – 24xN BIP – 8 BIP – 24 BIP - 8 BIP - 8 BIP - 2


Threshold tables (1830PSS) 2.

1. Open an equipment view 2. Select “System” in the left resources tree 3. Click on “Performance” in the “Selection Function” 4. Click on “TCA Profiles” tab and then

3.

4.

“Retrieve” 5. Select a “Profile type” 6. Select a Profile ID and then click on “Details”

6.

5. 4 · 2 · 28 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance




Example of threshold tables (1830PSS) “Details” gives this view: the user can change the desired values and click on “Apply”





Starting/stopping PM (Q3 and 4G Q3 NEs) 1. Display the port view of a board 2. Select a TP (MST, RST, AU4, VC-n, TU-n) Performance 3. Select the menu Port

Configure Performance Monitoring 4. Select a POM/TCM/TCT as Monitor (if required) 5. Tick “Data Collection” 6. EML OS Monitoring: select archiving or

archiving on threshold crossed 7. Choose a proper Threshold table and Attach it 8. Click Apply 9. Click on Set ASAP if you want to configure ASAP 10. Click Apply 11. Click the Close button 4 · 2 · 30 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance


POM: Path Overhead Monitoring. TCM: Tandem Connection Monitoring. TCT: Tandem Connection 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 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” or “Archiving on threshold crossed”. 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, the 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. Select the Remove button to separate the threshold table from the entity. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. TOS63017_V3.1-SG-R9.6-Ed1 Module 4.2 Edition 1 Section 4 · Module 2 · Page 30


How to set Analog PM in NE USM (Q3 and 4G Q3 NEs) Open the equipment view Analog PM Configuration Select Configuration On Network Element 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 (Q3 and 4G Q3 NEs) [cont.] Start PM by selecting Start in the “PM action” column for the 15min or the 24h If the data must be sent to the OS, the “Archiving” cell must be set to Yes Click on Apply





Starting/stopping PM (1850TSS-320 R3) 1. Select the desired port, then click on “STM PM”





Starting/stopping PM (1850TSS-320 R3) [cont.]

2. Click on “PM Mode”

3. Fill in the desired value for all the parameters shown in the page 4. Click on “Save”

Location: Near End, Far End, Bidir, All Direction: Receive, All Mode Type: PM for All Parameters, only for RS, only for MS PM State: On, Off or Disabled. Set to ON Time Period: 15 Min, 1 Day, Both





Starting/stopping PM (1830PSS) There isn’t any manual procedure to start the PM on the 1830PSS. Counters are monitored and processed in the NE as soon as the involved interfaces are set in service in the NE. These counters can be retrieved: With the local ZIC terminal (not the “show equipment” of the 1350OMS-EML) With the procedures available in the MS-GUI of the 1350OMS-EML (see in the following).




Exercise Following instructor recommendations, configure a PM measurement.





3 Displaying performance data





Displaying PM data for a single TP (Q3 and 4G Q3 NEs) From the Equipment view: 1. Display the port view of a board 2. Select a suitable TP 3. Select the menu Port

Performance Current Data

Display

4. Select TP/POM/TCM/TCT (in case of AU4 or TU-n) 5. Select the required granularity Click Refresh to update the counters’ value



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 on Q3, 4G Q3 and 1850TSS-320 R3 equipment are taken into consideration. For the display of Ethernet and FEC performance data, and for other kinds of equipment, please refer to the Operator Handbooks and Training Manuals of the specific NE family.



Displaying PM data history for a single TP (Q3 and 4G Q3 NEs) From the Equipment view: 1. Display the port view of a board 2. Select the TP 3. Select the menu Port

Performance Display History Data 4. Select TP/POM/TCM/TCT (in case of AU4 or TU-n) 5. Select the required granularity Click Refresh to update the window’s data



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



Displaying PM data for a single TP (1850TSS-320 R3) From the Equipment view: 1. Display the desired port 2. Select the STM PM folder 3. Select PM Report subfolder 4. Fill in the desired value for all the parameters shown in the page (See Notes) 5. Click Retrieve to update the counters’ value



Monitor Level: Two windows combo box. The second widow can be set to: DN: all intervals are retrieved, except for the incomplete intervals DNORNCMPL: all intervals are retrieved UP: only the intervals with counters equal or greater than the values set in the first window are shown, except for the incomplete intervals UPORNCOMPL: only the intervals with counters equal or greater than the values set in the first window are shown Location: FEND, NEND, BIDIR, ALL Monitored parameter type: Counters to be shown Direction: RCV, TRMT, ALL Time Period: 15 MIN, 1 DAY or ALL N.B.: When using a 1830PSS, the performance data cannot be retrieved by the equipment view of the 1350OMS. The operator must use the local terminal (ZIC).


Exercise Display the PM data.





4 Performance reports





Step 1: Navigation to PM Domains From the MS-GUI, select “Search

PM

PM Domains on EML”

Available PM Domains: if “Offline”, it is an Archive.





Step 2: Navigation to Monitored NEs Right click the desired domain and “Search

Monitored NEs/TPs”





Step 3: Navigation to Monitored TPs Right click the desired NE Monitored and “Search

NEs/TPs”





Navigation to Monitored TPs from the NE List Right click the desired NE and “Search Show PM”





Step 4: Generating the Report

1. Select the desired TP (or group of TPs), right click and “Actions

Generate Tabular, Line Chart or Bar Chart Report” 2. Select the monitoring period using the calendar (click on ) and the granularity, then click on “Apply”





Tabular Report (Example) The table can be sorted by the desired column





Line Chart Report (Example)

Absolute or logarithmic scale on the Y axis Select the desired object and parameters by clicking on them 4 · 2 · 49 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance




Bar Chart Report (Example)

Move the view to the right or to the left by acting on the bar





Forced reading of PM counters Forced reading is used to collect data immediately without waiting for the end of the next collection period. Valid only for 15-minute counters. 1. Display any equipment view 2. Select Configuration Performance

Forced Performance

Collection



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 or an NE by name/type/release 2. Select the search type: NE or TP 1. Right click the desired domain (or NE) and

“Actions Name”

Search by

3. Set at least one filter: - Name Pattern - in case of “Search NE”: the NE’s user label - in case of “Search TP”: the TP’s name - case sensitive - wildcard character * - TP Type - NE type and release

4.“OK” or “Apply” 4 · 2 · 52 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance


•Examples of TP name: •

1660SM •

•

63B/r01sr1sl25/port#001-MsTTP-PMNETR15

1850TSS-320 •

C322/STM16-1-1-21-4, L, FEND, RCV, 15-MIN



Search for a TP by Value 1. Right click the desired domain (or NE) and

“Actions Value”

Search by

2. Configure “Search period”

3. Set the search criteria: select the counter, the operator and the reference value 4 · 2 · 53 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance

4. Click “OK” or Apply”


Search period: •User specific – Start time – End time •Last...Until – End time – Granularity •Latest - Granularity •Current - Granularity



Delete “Not active” items Delete the selected “Not Active” TPs

Delete all the “Not Active” TPs Delete the selected “Not Active” NEs





Export “PM TPs list” to a CSV file on the Server

1. Select a domain Actions Export TPs to CSV file 2. Edit the “path/filename” the file is to be saved to in the server.

“/tmp/” by default

• if you don’t specify any file name (e.g. you keep just “/tmp/”) the file name will be “TPList.csv”

3. Apply

TP example (1850TSS-320)

"SDH@EML_1-9.5/C322/C322/STM16-1-1-21-4, L, FEND, RCV, 15MIN" NE user label 4 · 2 · 55 Maintenance Applications · Performance Monitoring management 1350 OMS EML · R9.6 Operation and Maintenance

TP




Export data to a CSV file on the PC 1. Generate a tabular report

3. Click 2. Select the rows to be exported




Exercise Create a line report Export data to a CSV file on your PC





End of module Performance Monitoring management





@@SECT LE Section 4 Maintenance Applications Module 3 Logs management





Blank page

4·3·2


Maintenance Applications · Logs management 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Monitor the commands issued from MS-GUI, Equipment View and local management tools

4·3·3 Maintenance Applications · Logs management 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 Available log reports 2 Logs provided as a list in MS-GUI 3 Logs in Equipment View 3 Alarm Surveillance-like event logs




Page 7 9 15 22






1 Available log reports




1 Available log reports

Three types of reports

Logs provided as a list in MS-GUI

Logs in Equipment View

Alarm Surveillance-like event logs 4·3·8 Maintenance Applications · Logs management 1350 OMS EML · R9.6 Operation and Maintenance



2 Logs provided as a list in MS-GUI





Open the UAL GUI My ...: • commands • commands All ...: • commands • commands ZIC

by the 1350 OMS login from EML, SDH, PKT, WDM by all 1350 OMS and ZIC logins from EML, SDH, PKT, WDM,

... Priority Records: • priority 1 commands

4 · 3 · 10 Maintenance Applications · Logs management 1350 OMS EML · R9.6 Operation and Maintenance


Addressed logs application’s logs: commands executed in MS-GUI (EML/SDH/PKT/WDM) NE’s logs commands executed in ZIC/WEB-UI 1850TSS-100 R3.2, 1850TSS-320 R3.6, 1830PSS R3.5.2 commands executed in NE’s Equipment View in 1350OMS-EML Default collection times (UTC): 02:00 – 08:00 – 14:00 - 20:00 the collected data is available in UAL-GUI almost after 1 hour Command’s priority 1 (high) or 0 (low): by default, all the events have priority=0 it’s assigned by 1350OMS according to a configuration file Acknowledgement of the commands in UAL-GUI priority 0 commands automatically acknowledged at collection times by 1350OMS (Acknowledged by Admin) if older than 28 hours OR ... ... to be manually acknowledged by the user priority 1 commands to be manually acknowledged by the user Logs are deleted from UAL-GUI after 30 days



UAL GUI info





Examples: operation by means of 1350 OMS’s applications Path creation by means of 1350 OMS SDH

GUI Server

Path’s name

1350 OMS’s user

PC’s address

“Delete NE” and “Local access granted” by means of 1350 OMS EML

NE’s name





Examples: NE configuration Commands on NE by means of EML’s Equipment View “MSP lockout” on 1850TSS-320

“Set” a card in 1660SM

Commands on NE by means of ZIC

NE’s name

1350 OMS’s user

NE’s name

1350 OMS’s user

“Declare a card” and “Login” on 1850TSS-320

NE’s name 4 · 3 · 13 Maintenance Applications · Logs management 1350 OMS EML · R9.6 Operation and Maintenance



ZIC’s user


Acknowledge Acknowledgement of the commands in UAL-GUI: priority 0 commands automatically acknowledged by 1350 OMS (Admin) if 28-hour old OR manually acknowledged by the user

priority 1 commands manually acknowledged by the user only List sorted by “Time”

Last collection

Previous collection




3 Logs in Equipment View





Example for 1850TSS-320

Security Administration Network Element Logs





Example for 1850TSS-320 [cont.] Configuration executed by means of ZIC admin: ZIC’s user


Configuration executed by means of 1350 OMS 151.98.33.99: server’s IP address




Example for 1850TSS-320 [cont.] Comparison between NE log and 1350 OMS log “Declare a card” by means of ZIC ZIC’s user

UAL GUI

NE’s name

NE log

Client/User TL1/paolo

From/To

Command

127.0.0.1/3082


'ENT-EQPT::10GSO-1-16:c22857:: :PROVISIONEDTYPE=1P10GSO AINSMODE=NOWAIT SSBIT=SS10:IS'




Example for 1660SM By the EMLUSM, the user has the possibility to browse the event log stored in the MIB of that single NE. Click on Event Log





Example for 1660SM [cont.] The event records can be filtered by the user per type and time: Filter by Event Type

Filter by Event time

Choose “Filter” or “No Filter” to apply or not the filter 4 · 3 · 20 Maintenance Applications · Logs management 1350 OMS EML · R9.6 Operation and Maintenance




Example for 1660SM [cont.]




3 Alarm Surveillance-like event logs





Web Portal

Start “Current Events Log” from the Web Portal





Sublists Events: - SNCP switch - Loopback - T-MPLS tunnel switch

Sublist for Loopbacks

NEs: 1850TSS-100 1850TSS-160/320 1830PSS 1626LM

Sublists for SNCP and Tunnel switch





Loopback on 1850TSS-320

How to issue a loopback on an STM port in 1850TSS-320 from Equipment View: - Select the STM port - Set “Port Mode” (default=AUTO) to “NMON” or “MON” - Set “Primary State” to “OOS” (Out Of Service)

Save

Save

- Issue the loopback: “Operate Loopback” 4 · 3 · 25 Maintenance Applications · Logs management 1350 OMS EML · R9.6 Operation and Maintenance




T-MPLS tunnel on 1850TSS-320

Protection Switch (Manual): e.g. Lockout command


2. Choose “Additional Information”

Fo r to ce sp sw ar itc e h

Lo ck

ou t

1. To get details on the alarm: double click the alrm




Historical alarms/events




Exercise Retrieve the three types of logs which are in relation with the alarm equipment created in the Alarm management chapter





End of module Logs management





@@SECT LE Section 4 Maintenance Applications Module 4 NE software download





Blank page

4·4·2


Maintenance Applications · NE software download 1350 OMS EML · R9.6 Operation and Maintenance



Date

Author

Remarks

01

2012-11-08

Vallet, Carole

First edition


Module objectives Upon completion of this module, you should be able to: Download a new software package to the NE to upgrade its software release

4·4·3 Maintenance Applications · NE software download 1350 OMS EML · R9.6 Operation and Maintenance








Table of contents Switch to notes view! 1 Downloading software to the NE 1.1 Software download by FTS 1.2 Software download from Equipment View




Page 7 9 20






1 Downloading software to the NE




1 Downloading software to the NE

Two methods

From MS-GUI by means of the File Transfer Scheduler (FTS)…

From Equipment View…




1.1 Software download by FTS





NE Software Package preparation Prior to downloading a new Software Package (SWP) to the NE, it’s necessary to have it in the server.

1. In Web Portal, start NE SW Packages

4 · 4 · 10 Maintenance Applications · NE software download 1350 OMS EML · R9.6 Operation and Maintenance




NE Software Package preparation [cont.]

2. Click Install and look for the .DSC file of the SWP that is on your PC or on another media 4 · 4 · 11 Maintenance Applications · NE software download 1350 OMS EML · R9.6 Operation and Maintenance




SW download procedure 1. Select the NE to download in the Network Element list 2. Right click and select “Actions Download NE Software”: the “Create and activate software download job” is opened 3. Assign a name to the new job 4. Set the job periodicity (immediate, deferred): in case of “deferred” choose the activation time 5. Click on the NE in the list, choose the Server and the SW package to download 6. Click “OK” or “Apply” to submit the software download job 7. In the job list, right click on the new job and issue “Actions

Activate Job” Besides the above procedure, the operator can manage manually the job/session creation, too.





SW download procedure [cont.] 1. From the Network Element list, select the desired NE(s)

2. Right click and

“Actions Download NE Software”





SW download procedure [cont.] If the activation is deferred choose date and time by clicking here

3. Assign a name to the job 4. Set the job periodicity (immediate, deferred)

The user can specify a duration in hours, after which the job will be automatically stopped





SW download procedure [cont.] Additional NE’s can be added to the list by clicking here 5a. Click on the Network Element in the list 5b. Check/select the Server 5c. Select the SW package to be downloaded By default, Force=True. To have Force=False, create manually Job and Session. 6. “Apply” 4 · 4 · 15 Maintenance Applications · NE software download 1350 OMS EML · R9.6 Operation and Maintenance




SW download procedure [cont.]

Immediate: after “Apply”, the download is started

Deferred: it waits for the Activation Time





Other actions on SW Download jobs A SW download job can be: Edited (if not pending) to modify its periodicity (immediate or deferred; periodic) Aborted (if Waiting) Deleted (if not pending)

Job Status: for running Jobs Report: for ended Jobs





Activate the downloaded SW In order to see the SW status of the managed NEs: Select “File Transfer

Scheduler


Deployed SW”




Activate the downloaded SW [cont.]

1.Right click on NE and “SW Details”

2. Click on Activate to commit the Stand-by SWP



A SW package can also be Forced activated, Committed and Deleted by using the same menu.


1.2 Software download from Equipment View





Set the server data (Q3 and 4G Q3 NEs)

1. In Equipment view, select:

“Servers management...”

2. Select “local” (the local server is automatically chosen)



If “local” is not available in the server list, write “local” in the “Software server name”, close and re-open the window.



Set the server data (4G TL1 NEs): 1850TSS-320 R3.1 1. Issue the command “System Management

Initialize and Upgrade In-Service Upgrade Upgrade Status” to make sure that the Upgrade Status is “NOSTAIP”.

2. Select “System

management DB Management Remote File Perform Copy Software Download”, and check

3. Select the desired package (“D” for Data; “M” for Merged; “T” for Transport”)

the proposed location.



Note that the commands and associated menus to be selected into the equipment view are specific for each single NE, so please refer to the Operator Handbooks and to the Training Manuals of each single NE family.



Set the server name (SNMP NEs) The commands and associated menus to be selected into the equipment view are specific for each single NE, so please refer to the Operator Handbooks and to the Training Manuals of each single NE family.





Downloading (Q3 and 4G Q3 NEs)

1. In Equipment view, select:

“Init download” 2.Select the SW Release to be downloaded

wait for the message “Software download completed!” to appear in the download window. 4 · 4 · 24 Maintenance Applications · NE software download 1350 OMS EML · R9.6 Operation and Maintenance




Downloading (4G TL1 NEs): 1850TSS-320 R3.1 After having selected “System

management DB Management Remote File Perform Copy Software Download” and having chosen the desired package, click “Apply”






Downloading (SNMP NEs) The commands and associated menus to be selected into the equipment view are specific for each single NE, so please refer to the Operator Handbooks and to the Training Manuals of each single NE family.





Activating the new software (Q3 and 4G Q3 NEs) SW Release 1. In Equipment view select the menu Download

Units info...

2. Select the tab that corresponds to the Standby software (look in Current state\Action field) In the Current state\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) 4 · 4 · 27 Maintenance Applications · NE software download 1350 OMS EML · R9.6 Operation and Maintenance




Activating the new software (4G TL1 NEs): 1850TSS-320 R3.1 1. Now it is possible to activate the new software release using the:

“System Management Initialize and Upgrade Initialize System With New Release”. After that the NE will restart and will be activated the new software release 2. You can check the SW release downloaded : “Equipment

Information” 3. Select “System Management Initialize and Upgrade Service Upgrade Remove Old Upgrade” menu.


System In-





Activating the new software (SNMP NEs) The commands and associated menus to be selected into the equipment view are specific for each single NE, so please refer to the Operator Handbooks and to the Training Manuals of each single NE family.





Downloading SW to 1830PSS-32: Procedure 1. From the equipment view, issue “Administration

Software

Upgrade” 2. Select “Action = Audit”, set the correct Release Directory and click “Apply” 3. Select “Action = Download” and click “Apply” Once the Download has been completed (check in the “Software Status” window), the operator can activate the new release: 1. In the same window, Select “Action = Activate” and click “Apply” 2. The NE restart. After the restart, commit the new release by selecting “Action = Commit” and clicking “Apply” The activation of the new software can be reverted by selecting “Action = Commit” and clicking “Apply” before committing the new release





Downloading SW to 1830PSS-32: Software Upgrade Window “Administration Software Upgrade” FTP location information

Software status box

Actions to be applied 4 · 4 · 31 Maintenance Applications · NE software download 1350 OMS EML · R9.6 Operation and Maintenance



Answer the questions What is the advantage of using the FTS ?




End of module NE software download




Last but one page

Congratulations You have finished the training

Your feedback is appreciated! Please feel free to Email your comments to: [email protected] Please include the training reference in your email (see cover page)

Thank you!

1



All Rights Reserved © Alcatel-Lucent @@YEAR @@COURSENAME - Page 1

All rights reserved © Alcatel-Lucent Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent All Rights Reserved © Alcatel-Lucent @@YEAR @@COURSENAME - Page 2

1350 Oms Eml r9.6 o&m Tos63017_student Guide

Recommend Documents