1350 Oms Wdmr9.6 Sgv2 Ce

All rights reserved Alcatel-Lucent 2011
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 2012

1350 OMS WDM Operation and Maintenance
Page 1
This page is left blank intentionally

Page 2
1. Safety Warning
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to wear
conductive jewelry while working on the products. Always observe all safety precautions and do not work on the equipment alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (Marks) are the property of their respective holders, including Alcatel-Lucent. Users
are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning the Mark. The absence of
a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to change
without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other use or
transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and must include all
copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used, copied, disclosed
or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and is
expressly prohibited from modifying the information or creating derivative works without the express written consent of AlcatelLucent.
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost profits,
lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel-Lucent has been advised
of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement, nor a
recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The information
contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some cases, due to
contractual limitations, certain compromises have been made and therefore some features are not entirely accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment and its
operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. Alcatel-Lucent
disclaims any warranties in connection with the products as used and described in the courses or the related documentation,
whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties, including warranties of
merchantability, non-infringement and fitness for a particular purpose, or arising from a course of dealing, usage or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed internet
connections, interruptions, any computer virus or any other technical defect, whether human or technical in nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are governed by the
laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal Notices, or the application
thereof to any person or circumstances, is held invalid for any reason, unenforceable including, but not limited to, the warranty
disclaimers and liability limitations, then such provision shall be deemed superseded by a valid, enforceable provision that matches,
as closely as possible, the original provision, and the other provisions of these Terms of Use and Legal Notices shall remain in full
force and effect.

Page 3

Page 4
Section 1. Product Overview

Module 1. 1350OMS Overview
Module 2. 1350 OMS WDM Overview
Section 2. Graphical Interface
Module 1. Web Portal
Module 2. Multi Service GUI
Module 3. 1350 OMS MAP version 2.0
Section 3. Network Management
Module 1. Network Element Management
Section 4. Link, Cross and Inconsistent Connections
Module 1. Link Connections
Module 2. Cross Connections
Module 3. Inconsistent Connections
Section 5. WDM Connection Management
Module 1. Physical Connections
Module 2. Path and Trail Connections
Module 3. Optical Transport Services
Section 6. Wavelength Tracker (WLT)
Module 1. WLT Concepts
Section 7. Commissioning and Power Balancing (CPB)
Module 1. CPB Concepts
Section 8. Fault Management
Module 1. 1350 OMS Alarm Management
Module 2. WDM Alarm Management
Section 9. Performance Monitoring (PM)
Module 1. PM Management

Page 5
Welcome to 1350 OMS WDM R 9.6 Operation
Upon completion of this course, you should be able to:
1.
Explain the 1350 OMS WDM application topology
2.
Use the 1350 OMS WDM Graphical User Interface
3.
Describe Network Element Management
4.
Identify Link, Cross, and Inconsistent connection concepts
5.
Determine Physical, Path and Trail requirements
6.
Determine Transport Services requirements
7.
Identify Wavelength Tracker concepts
8.
Explain Commissioning and Power Balancing
9.
Identify Fault Management principles
10. Determine Performance Monitoring requirements

Page 6
Conventions used in this guide

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

If you want further information you can refer to the following:
Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

Page 7

Page 8

Page 9

Page 10

Page 11

Page 12
The 1350OMS focuses on the Telecommunication Management Networks Element Management and Network
Management layers.
These management layers functions are accomplished by a set of different "applications.
The Element Management Layer (EML) is implemented by the 1350OMS-EML application.
The Network Management Layer (NML) is implemented by the 1350OMS-SDH, 1350OMS-PKT, 1350OMS-SONET,
and 1350OMS-WDM applications.
The applications of the NML provide network functionalities for specific topologies. Each application has its own
data and database, with data shared between applications via network interfaces.
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 also provides a
unique map.
Common functionalities such as alarm and performance correlation capabilities are bundled into components that
are shared by the applications.
Fault management and Performance Monitoring information is common to all the applications. Every application
renders the alarms and the PM results according to the own management, therefore the user can retrieve the
data collected for any single application.
Craft Terminal is meant for commissioning and for maintenance when the Network Element is not reachable from
1350OMS.

Page 13
Each application is license controlled and separately purchasable.

1350OMS-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 1350OMS-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.
1350OMS-SDH for the SDH technology and for the WDM technology in some equipment, e.g. 1626LM.
1350OMS-PKT for the data technologies, such as Ethernet, T-MPLS, CES (Circuit Emulation Service).
1350OMS-SONET for the SONET technology.
1350OMS-WDM for the WDM technology in some equipment, e.g. 1830PSS.
1350OMS provides users with the ease of accessing and using the eOMS (embedded Optical Management
System) to provision the former Lucent legacy network. 1350OMS-eOMS accomplishes both the EML and NML
functions. It is integrated with the 1350OMS 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.

Page 14
The slide depicts a Gigabit Ethernet service across SDH and WDM networks.
Ethernet management of 1850TSS requires 1350OMS-PKT.
The Ethernet/SDH network is made of 1850TSS equipment. SDH management of 1850TSS requires 1350OMS-SDH.
The WDM network is made of 1830PSS equipment. 1830PSS management requires 1350OMS-WDM.
While provisioning the Ethernet service, the user selects the end-ports of node A and node F. The Ethernet
configurations are executed on node A and node F.
While provisioning the SDH network, the user selects the suitable points of node A and node F. All the SDH nodes
between the two points are configured.
While provisioning the WDM network, the user selects the end-ports of node C and node D. All the WDM nodes
between the two ports are configured.

Page 15
1350OMS runs on servers with an automatic download of the GUI client from the server to the users P.C.
In the server, the usage of the applications is accomplished by the GUI server processes which 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.
On this slide, all the applications and processes are installed in one server. The management of the network may
require more servers (Master and Presentation) which we will discuss on the next slide.
The 1350 OMS GUI follows a full web-based approach. The user simply needs a standard PC Windows XP
configuration with a web-browser, Java Run Time 6, and 2 gigabyte RAM.
No manual client software distribution and installation procedure are required.

Page 16
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.
For 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.

Page 17
1350OMS-HA is the High Availability application. It requires at least two servers 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 is unable 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: this 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.
Page 18

Page 19

Page 20

Page 21

Page 22
This section presents an introduction to the 1350 OMS WDM functionality and its relationship to the Element
Management Layer (EML).
Futher discussion of the functionality depicted on these slides will be discussed in more detail through out the
course.

Page 23
WDM is a multiplexing technique used to increase the bandwidth of a single mode optical fiber, enabling
simultaneous transport of several different signals on one fiber. Each signal is transported into a well-defined
wavelength, usually identified as "lambda".
1350OMS WDM supports layers, such as OTS (Optical Transport Section), OMS (Optical Multiplex Section), and OCH
(Optical Channel) and presents to the user an end-to-end connection management with these connection rates.
1350 OMS WDM also supports 1350 OMS generic features such as Fault Management and Performance Monitoring.
The 1350 OMS WDM application is a Network Management Layer (NML) management system which supports
Alcatel-Lucent 1350 OMS WDM Network Elements (NEs) and provides full G.709 model compliance.
1350 OMS WDM Layer Management provides:
Service creation
Network provisioning
Network protection management
SDH/PKT interworking
Optical power commissioning and power balancing
Wavelength Tracker capabilities
Fault management
Performance monitoring

Page 24
The Web Desktop is the web application which provides a central access point. From this access point, the user is
authenticated and from which the user can navigate to the 1350 OMS Web Portal to access 1350 OMS
Applications.
To start the Web Portal, enter the Web Desktop address in the browser, then enter your login/password in the
pop-up window and the Web Portal window is opened.

Page 25
The Network Topology Map provides a graphical representation of the nodes, physical links between nodes and
node and link alarm status.
The network map is composed of a left panel which provides a tree of the network and the sub-networks
associated with that network. Double clicking on a sub-network from the left panel, causes the map of the subnetwork to display in the Main View panel. The Icons represent the various types of objects represented on the
Map.

Page 26
NEs may be auto discovered or manually created.

The slide displays some of the steps associated with the NE creation:
WDM NE discovery is performed via the Element Management Layer (EML) Actions menu which opens a Create NE
wizard.
Using the 1350 OMS EML Creation Wizard, the user can manually create the NE in 1350 OMS.
Population of the fields in the Creation Wizard are dependent on the type of NE, the way it is managed and the
type of NE interface (TL1+SNMP, CNA, SNMPetc.).
By creating a NE, a Node is created that is used by the NML application, in this case WDM.
Supervising NEs is an essential aspect of the network management.

The supervision of an NE consists in establishing a communication that allows the user to perform EML operations
such as configuration and alarm management.
We will further discuss discovery and NE supervision in a later module.

Page 27
A physical connection is a connection that uses wires, cables, or optical fibers to connect two physical ports. In
the 1350 OMS WDM application, OTS and OS rate connections are physical connections.
Physical connections are commonly referred to as topological links (TLs) and are divided into two types:
Optical Section (OS)
Optical Transmission Section (OTS)
Optical Section connections can be either internal (provisioned within the NE) or external (provisioned
between two NEs.
OTS/OS Physical connections are provisioned through the GUI and are displayed in the maps where they are
animated according to the network alarms.
OTS links auto discovery is supported by 1350 OMS.

Page 28
Logical connections (Trails or Paths) in a DWDM network are connections typically between DWDM NEs, spanning
more than one DWDM NE carrying one or more (that is, Mux OTs) client signals converted into a single wavelength
(or frequency) or multiple wavelengths, with each one carrying one or more client signals. These logical
connections are also referred to as optical logical layers.
The rates for trail are OTUk, ODUk and the rates for path are ODUk and DSR.
For optical channel provisioning there is a dedicated wizard for channel configuration. The Create Wizard
provides a series of panels in order to manage the definition of :
1. Optical channel connection parameters
2. Node and port termination points

3. Routing method (Automatic, Manual, etc.) and constraints (link connection, Lambda, Termination
Point/Node)
4. Alarms and Performance Monitoring (PM) settings
5. Transmission parameter settings (client ports configurations etc.)
There also additional panels not displayed that also require configuration. These include; Wave Key parameters
and Order assignment.

Page 29
The EPT is used to design the NE configurations and traffic services through the network.
The EPT data provides minimum and maximum values for span losses, port-to-port losses between wavelength
tracker detect points, and amplifier gains.
The EPT must be uploaded to the 1350 OMS EML application before commissioning and power balancing can be
performed in the 1350 OMS.

Page 30
The Commissioning and Power Balancing (CPB) software is packaged with the EML application software and is
integrated into the 1350 OMS WDM photonic management capabilities.
CPB enables the system to perform the following:
1. Discovers the NEs in the EPT file and gets the parameters (e.g. NE model, NE release, SNMP address,
SNMP port etc.) for each NE from the EML database and stores them in the CPB database.
2. Uses the EPT commissioning file to validate the NE HW inventory comparing the planned verses installed
cards. It configures the internal fiber connections (topological connections) between the circuit packs
and sets target power for all amplifier outputs.
3. Enables the user to set up the target power values on the amplifier cards of TOADM NEs in order to
match span losses on OTS provided by EPT. Amplified Spontaneous Emission (ASE) power is used to
perform commissioning on rings and on the intermediate NEs in linear chains.
4. Applies the new target power values and power balances the optical domain with the services present.
The power balancing can be done using a Plan file from EPT or by selecting a NE in the optical domain.
5. Generates a power loss report based on the current power values against the target power settings for
the optical domain. Both Greenfield commissioning and power balancing operations also generate Loss
reports.

Page 31
Wavelength Tracker (WLT) technology is a sophisticated but simple-to-use monitoring function that optimizes OA&M
tasks.
1350 OMS includes all the management capabilities to drive and exploit WLT technology
Fault connection detection at fiber/WSS level
On-demand per-channel connection (OTU) optical power levels along the route
On-demand per-span (OTS) optical spectrum
High/low optical level threshold adjustment

Page 32
The Optical Power Display feature is supported for NEs that are directly managed by 1350 OMS WDM.
The Optical Power Display option allows the user to access a OTS Power Display screen that reflects the power
levels from either the Ingress or Egress transmission directions of a selected port. The OTS WLT power graph
displays power measurements on points along one wavelength.
You can jump from the OTS Power Display to the OTU WLT power graph by use of a cascade menu. The OTU
power graph displays an optical fiber view of all wavelengths on a selected fiber.
The slide depicts:
1. Access to the Optical Power Display feature via a cascade menu on the Trails list
2. The Jump from the Optical Path (OTS) view to the Optical Fiber (OTU) view via a cascade menu
3. The Jump from the OTU Fiber view back to the Optical Path view.

Page 33
WDM NE alarms are correlated to the affected transport objects (OTS links, OTU/ODU trails, DSR paths etc.).
The WDM manager receives alarms in real time from WDM NEs through EML layer propagation.
1350 OMS EML provides real time alarm notification processing. These alarms are called Elementary Alarms (EAs).
Elementary alarms reside in a centralized repository common to all managed NEs.
The slide displays access to the EML Alarm Surveillance from the EML Network Elements list via the Show NE
Alarms option for a specified NE.
The Alarm Sublist is a basic working window of the EML Alarm Surveillance application. Using the Alarm Sublist,
you can isolate the probable cause for a specific alarm type. On the slide, the probable cause URU-S stands for
Underlying Resource Unavailable Card Failure. This probable cause code is applicable to optical transponders,
amplifiers, filters and other 1830 PSS cards.

Page 34
The slide displays access to the EML Alarm Surveillance window.

WDM alarms can be viewed directly from the EML Alarm Surveillance application.

Page 35
For additional information on an alarm, the user can right-click on any alarmed connection and access the
External Applications Fault_Localization option and navigate to the WDM Routing Display for the corresponding
connection.

Page 36
In 1350 OMS there is a single PM data repository database at the EML level.
The generic common component used to manage PM issues for all components is referred to as Converged
Performance Monitoring (CPM).
1350 OMS EML provides the following functionality related to management of performance data collected by each
NE:
Start and Stop PM on a specific TP (Termination Point) through .(User Server Manager) USM.
Periodic collection of PM data from each NE.
Forced collection of all PM data of a NE through EMLUSM.
Navigation to CPM GUI for display of PM historical data and graphical reports built on top of them.

Page 37
1350 OMS PM operates at the Network Management Layer in conjunction with EML.
The WDM manager uses the PM data retrieved from the EML as it relates to the services under measure and
presents this data with graphs and tabular reports.
1350 OMS WDM provides the following functionality related to management of performance data collected by
each NE:
Automatic and manual PM data start and stop
Periodic collection of PM data from each NE
Threshold Crossing Alert profiles
Navigation to CPM (Converged Performance Monitoring) GUI for display of PM historical data and graphical
reports built on top of them

Page 38

Page 39

Page 40

Page 41

Page 42
course.

Page 43
To gain full access to the 1350OMS GUIs through the Web Desktop, the PC must be configured so that the
1350OMSs server can be reached using the servers hostname.
If the Domain Name Server (DNS) is configured on the PC, it should be configured so that the servers hostname is
managed.
If such a configuration is not feasible, the servers hostname IP address association must be manually
inserted in the following file:
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

Page 44
Java Version 6 is required.

The system can be invoked from any web browsers.

Page 45
On the first log in, the user will be asked to change the password.
The user password is subject to the following constraints:
At least 24 hours should lapse 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

Page 46
The web Portal provides the user with a view of all the 1350OMSs applications.
The Left Tree Panel is a navigational panel which is organized with a hierarchical tree that lists the 1350OMSs
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 applications and Web Portals messages.
The Status bar displays the last application or Web Portals message.

Page 47
The user can add or remove preferred applications to the Tool bar by means of Edit Customize the toolbar
or double click an application and then Add to toolbar.
The applications added to the toolbar can be listed by issuing View Preferred Application List.

Page 48
Common system applications are grouped by their logical function as follows:

The applications are grouped as:
Operation - (Management, Alarm, Network Tools)
Management - contains the MS-GUI Network Management.
Alarm - provides presentation functions for all managed network Alarms.
Network Tools - provides access by cut-through functionality to the Data Communications Network (DCN )
Tunnels EML.
Administration - (System, Data Management and Security Administration)
System provides system (machine)Process Monitoring and Control (PMC) and scheduled execution of jobs
based on application.
Data Management includes Backup and Restore operations and NE SW packages EML.
Security Administration manages user privileges and provides command log file manipulation.

Page 49
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.

Page 50
The Alarms application is the single common fault management GUI which provides presentation functions for the
alarm of all managed NEs 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 NEs 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 a GUI for handling the SNCP switch events for 1850TSS-100, 1850TSS-160/320 and
1830PSS.

Page 51
In previous releases, Network Tools provided the IP over OSI tunnels configuration.
In 1350OMS R9.5, the IP over OSI tunnels configuration is available in MS-GUI.

Page 52
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.

Page 53
From the Process Monitoring and Control window, administrators can view and perform process monitoring
functions on items that appear in a tree structure on the left of the window, directly below PMC.
The slide displays:
The Node item is made up of three icons and a node label. The node label displays the host_name or the IP
address of the machine where the Process Monitoring server is running.
The System Instance consists of an system instance icon and a label. The System instance icon displays the state
of the application. The label displays the name of the application and its instance which is defined in the Process
Monitoring configuration. The run level (RL) is also displayed.
The Process Group is made up of one icon and a label. The label displays the name of the Group as defined in the
Process Monitoring configuration. In this case Emlims.
The Agent is composed of one icon and a label. The icon displays state of the Agent and the label displays the
name of the Agent as defined in the Process Monitoring configuration.
The Information area displays the application instance name and current state.
From a global perspective, the System Monitor GUI enables the administrator to retrieve and to view information
about the functional state of the machine on which an Application_Instance is installed and managed.
In addition, the System Monitor enables the administrator to issue commands to the machine for the managed
Application_Instance along with its respective and/or selected items.
Consult the Alcatel-Lucent 1350 OMS Getting Started Guide, for additional information on Processing Monitoring
and Control.

Page 54
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.

Page 55
There are three GUIs associated with the 1350 OMS Administration application which is used to administer and
maintain user security throughout the 1350 Optical Management System.
These GUIs include User Session, User Accounts, and User Profiles. These three Security Administration GUIs are
explained in detail in the 1350 OMS Administration Guide, Vol 2: Common GUI Functions.

Page 56
User preferences are customized attributes of the main windows, such as position, size, visible areas, and area
size . These preferences are saved in the in the User Data Manager server for later reuse.
User preferences may also be viewed and customized from the Tools > Options command displays the
Preferences window.

Page 57

Page 58

Page 59

Page 60

Page 61

Page 62
course.

Page 63
The MS-GUI presents maps, lists, queries, and graphical views of networks 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 1350OMS.
The Map of a network is a graphical view of the network upon which various network objects are displayed (e.g.
sub-networks, Nodes, and Links). The Map enables the user to perform actions on these network objects, such as,
creation, modification, deletion, retrieval, and provisioning.
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 (see
the Module Map Management)
Use menus contextual to the selected entity and the user profile
Start the provisioning wizards

Page 64
The Map enables the user to perform actions on these network objects, such as, creation, modification, deletion,
retrieval, and provisioning.
The left panel is a hierarchical tree composed of the main (root) network, sub-networks at the various levels and
a second level toolbar.
The Map Contextual menu is composed of icons that are active at the opening of the map and icons that are
dependent on the selected object.

Page 65
The GUI server 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.
Unavailable Menu options will be grayed out.
The PC Date and Time is displayed. This is not the 1350OMS servers date and time.
It is necessary for the PCs date and time to be aligned to the server, 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.

Page 66
The slide displays the Graphical Routing display which provides a pictorial representation of a managed
connection including the NEs. ports, connections, alarms and directional and protection scheme.
There are two other types of Routing Display windows:
The Server Routing Display is a pictorial representation that displays the underlying optical connections.
The Text Routing Display presents the same information as the Graphical Routing display in text format.
The Reload icon is used to refresh the Routing Display from the application database after a change has been
performed on the ports menu or when fault conditions change.
There are many icons associated with the Routing Display. A mouse over of the icon provides a tooltip describing
the purpose of the icon (directionality, protection type, alarm level etc.).
The Connection Icon symbol varies depending on the whether the Routing Display is for a Physical, Trail or Path
Connection. The connection name is displayed beneath the icon.
The Connection icon is color coded to the connection configuration state: pink indicates that the service has been
defined but provisioning is incomplete, lime green indicates that the provisioning is complete but the service has
not been activated and sea green indicates that the connection configuration has been activated.
The Network Element icon is represented by a color coded rectangle. Managed NEs with no fault indicators are
represented by a green rectangle. Non-managed NEs (ENEs) are represented by a gray rectangle and NEs in
maintenance or experiencing a loss of communication are represented by a magenta rectangle.
Note
External Network Element (ENE) is a set of NEs that are outside the managed domain. These
may represent non-supervised adjacent sub-networks or Customer Edge devices.
The NE port icon is a square containing two triangles and is located to either side of the NE rectangle. Each port
is labeled with the address of the port. Ports are color coded to indicate the highest severity alarm on the port.
Page 67
At the bottom left of the window are two Log icons:

Servers log provides a list of the type and the connection time of all servers.
Operations provides a list and description of all operations that have been performed by the user.
The description covers the following information:
Operation, Involved Object (performed action), Status (executing, completed, failed), Start-Time, and End-Time.
When an Operation is selected from the list, it is possible to see the Filter, Details, and Parameters. This is
helpful in the resolution of failed procedures.

Page 68
File Close
Selected view or all windows
File Print
Selected view
Edit Find
Find a text string in the Main View. Its case sensitive.
Tools Left Area
Change the appearance of the left tree area to Maps, Search,

Windows, Command , Favorites, and Objects
Tools Options
Enables the user to control certain types of GUI screen behavior
Tools Manage server connection
Disconnect or re-connect previously disconnected application GUI

servers (i.e. TDM, FTS, CPM, TM, CLOG, PKT, MAP, CPB, WDM, and
All)
Windows
Displays currently open windows

Page 69
By the Search Menu the user can retrieve lists of the networks objects and information related to the power
adjustment procedures on WDM NEs. In addition, the Performance Monitoring domain can be accessed.
Because query options for the Search command are dependent on the 1350 OMS installation parameters. Menu
options may vary for individual applications and systems.
OTN: commands for 1350OMS-SDH
Packet: commands for 1350OMS-PKT

Page 70
From the Actions Menu the user can:
Perform tasks on the networks objects (create, delete, discover, synchronize, )
Schedule jobs on File Transfer Scheduler
Set the Performance Monitoring (PM) report options
Retrieve and modify objects properties, etc.
Because query options for the Actions command are dependent on the 1350 OMS installation parameters. Menu
options may vary for individual applications and systems.

Page 71

Page 72
Using the Find operation, the user can search the information that appears in the Main View panel.
A Sub-network is an arbitrary collection of ports into a group. Each sub-network is linked up with a sub-network
or with the main network. A sub-network contains other sub-networks, NEs and/or ENEs. Typically sub-networks
are defined to include entire NEs, but is not a requirement.
The Parent sub-network of a sub-network (or a NE or an ENE) is the sub-network that contains it.

Page 73
The Search icon located on the tool bar at the bottom of the left tree panel allows the user (with or without a list
being displayed) to locate a specific item on a list based on user provided criteria.
The Contains field is optional. You can enter text information in this field to limit the search operation.
The Advanced area of the Search Criteria panel is optional and can be performed with the initial search or after
the initial search has been executed.
The Reset icon refreshes the Advanced area.
The More icon opens and additional filter panel.

Page 74
Search for specific criteria in a system-generated list by applying filters to your search action. This filtering is
only performed for the displayed list.

Page 75
You can also search for specific criteria from a system-generated via the filter (Change Search Criteria) icon on
the toolbar at the top of the list.
Remember to click on the Modify icon to initialize the filter panel.

Page 76
You can perform a search from the query area beneath a list. The first graphic displays 18 objects in the All Paths
List with zero objects selected and no filter applied. When you type search criteria in the filter bar (in this case
DSR), 1350 OMS will automatically filter out all objects that do not meet the criteria provided. The second
graphic displays this filtered results.
Deleting the search item from the filter bar, returns you to the original list (i.e. all Paths and rates are
displayed).

Page 77
The Windows Manager mode icon on the left tree panel allows navigational functionality among the open
windows. In the left panel, a hierarchical tree is displayed that lists the MS-GUI open windows grouped by
category. Select an item from the list and click on the Undock
icon in the Windows tool bar. The Window
can be sized, and moved around on the screen.
To dock the window, click on the Dock
icon.

Page 78
Using the Windows Manager, Undock icon, you can also split the screen between two open windows.
This is useful for viewing more than one list at one time.
To return to the original window format, double click on a list title bar.

Page 79
When the Operations icon is slected a hierarchical tree is displayed in the left panel.
Selection of this icon enales shortcuts to certain operations to be displayed in the left panel. The GUI provides
commands that are pre-loaded with the system. You can also define your own categories and populate them with
their own preferred commands.
The commands that are placed in the tree cannot be customized. For example, a shortcut for a list runs the list
request without filters.
To remove an added category, select the category from the Remove Category drop-down menu a confirmation
message will be displayed. Click on Yes.

Page 80
When the Favorites icon is selected, the left panel switches to the Favorites mode. The Favorites mode allows
you to display a hierarchical tree in which user defined bookmarks are listed.
Each bookmark is composed of a set of query or search operations that can be stored with filters and options.

Page 81
To delete Favorites, highlight the Favorites item to be deleted and click on the Remove Selected Favorites icon.
A confirmation message box is displayed, click on Yes.

Page 82

Page 83
The slide displays all of the icons associated with the First Level Toolbar.
The First Level toolbar is located under the Main Menu and contains icons representing non-contextual functions.
The toolbar is composed of icons which are independent of the selected object instance and icons that are
dependent on the selected object instance.
The independent icons include:
The Enable Filtered Searches allows the user to enable or disable the filter for the Search operations. If this
button is enabled and the user launches a retrieval operation using the Search menu, the system provides an
additional window from which to set the filter criteria for the selected object class to be retrieved.
The Operate in Normal Mode icon allows the user to switch between normal and advanced profile. The profile
can only be applied to the open windows related to the list view and Physical Map categories. The advanced
profile includes all commands related to the active window.
The Help for active view icon provides access to topics on MS-GUI navigation.
The Backward icon returns to the previously selected window.
The Forward icon proceeds to the next selected window list.

Page 84
Reload Data reopens the Map related to the involved sub-network.

Zoom Best Fit modifies the object sizes and the background picture size so the entire sub-network appears in the
Main View panel.
Normal Size restores the default dimensions of the objects and the background picture on the Map.
Change Background changes the background picture of the Map. Before changing the background, the system
allows the user to preview the available background pictures from a pop-up Background Selection window.
Go to the parent view allows the user to view from the current Map the associated sub-network and/or network
to which the current view is linked.
Save Map Configuration saves the background picture and the position of the objects on the Map. This feature
does not save any modification to the original size of the objects and background picture when the Zoom in or
Zoom Out are used.
Technology options are dependent on the applications installed in the server.
Layer options are dependent on the selected Technology.

Page 85
Dependant icons rely on the selected layer and object instance therefore, Dependent icons will vary based on the
current map view and the object selected.

Page 86
A list is a presentation form that is displayed as a result of a query request from the user. Lists are displayed in
tabular format.
You can move the columns of the table forward and backward in the list. Click on the Reload Data icon to return
the table to the default settings.
A right-click on a column header provides a contextual menu used as a shortcut to the possible commands and
queries of a selected object.
The table data may be exported as a .CSV file to your desk top. The modified table may be saved upon exit of the
MS-GUI by answering Yes to the Do you want to save working session before exit MS-GUI? message box.

Page 87

Page 88

Page 89

Page 90

Page 91

Page 92

Page 93

Page 94

Page 95

Page 96

Page 97

Page 98

Page 99

Page 100

Page 101

Page 102

Page 103

Page 104

Page 105

Page 106

Page 107

Page 108

Page 109

Page 110

Page 111

Page 112

Page 113

Page 114

Page 115

Page 116

Page 117

Page 118
Futher discussion of the functionality depicted on these slides will be discussed in more detail throughout the
course.

Page 119
When a Q3 interface is used, the NE needs to be configured with a NSAP OSI address.
When a SNMP or TL1 interface is used, the NE needs to be configured with an IP address.
Note
This module will discuss the creation of an 1830PSS (4G TL1) NE. The 1350 OMS
EML R 9.6 Operation course (TOS63017) provides creation procedures for the
different families of equipment based on their management interfaces (Q3, TL1,
SNMP, Q3 CNA etc.).

Page 120
The SID is known as the Target Identifier (TID) in 1830 PSS.

The SID/TID is composed of a string of up to 32 (for ETSI) and 20 (for ANSI) non case-sensitive alphanumeric
characters, including the hyphen (-) character or a quoted string up to 32 (for ETSI) and 20 (for ANSI), including
any special characters.
In the non-quoted string, the SID/TID must start with a letter and end with an alphanumeric character.
Consecutive hyphens (-) are not allowed. The number of hyphens used in the string must not be greater than four.
The OSPF routing for the OAMP port should be set to redistribute if the routing table of the Gateway NE is not to
be advertised externally.

Page 121

Page 122

Page 123

Page 124

Page 125

Page 126
OSPF Areas is for an OSPF configuration where automatic routing is required. OSPF is a form of dynamic routing
which uses a routing table to determine the best route path.
Static routes are routes through a data network described by fixed paths (statically).

Page 127
This slide and the next two slides focus on the creation and addressing of an 1830 PSS without security.

Page 128

Page 129
The NE can connect to the Network Element Management System (EMS) via the OAMP port if it is configured to
act as a Gateway Network Element (GNE). The IP address must provisioned and the OAMP port enabled to use this
port.
In addition, and IP route must be established to route connections to the Remote Network Elements (RNE).

Page 130

131 1 Page 131
Section 3 Page
Module
Check the correct configuration and process status with the System Administrator.

Page 132
If the operator doesnt select the Supervision Area and the EML Domain, in the above procedure, EML will
automatically chose these two parameters. The system takes account of each available EMLIMSNA and tries to
make their load homogeneous.
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 1350 OMS and the field is
automatically completed with the proper value. If more than one EML instance is available, the operator must
select the desired PNM GUI Server from the drop-down list.

Page 133

Page 134
The GNE Flag enables a TL1 command line interface operator to act on a Remote NE (RNE) through a Telnet
access to he Gateway NE (GNE). This feature is applicable only to the ANSI environment.
If 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.
The TID (Target Identifier) i.e. the NE identifier used in the messages exchanged between the NE and the EML,
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).
The SNMP address setting is not required.
Note
For the creation of 1830 PSS NEs, the GNE/RNE flag setting is not critical and should be
left in the default state.
1830PSS GNE/RNE roles are defined at the IP DCN level and transparent to 1350 OMS.
1350 OMS treats all the PSS NEs as GNEs. However, the GNE/RNE flag is critical for other
NE types thought. For example correct settings are mandatory for TL1 NEs.

Page 135
Prior to starting supervision, check to see if the NE is reachable.
Ping (Packet Internet Grouper) tests the DCN parameters (address, DCC, LAN interfaces etc.)
Supervision tests the supervision rights
The Ping NE function of the Telecommunication Network Management OS enables the administrator to test the
communication link with an NE. The Ping NE function is managed by the Middleware Interface (MW-INT)
application, which is the platform on which the 1350 OMS is built.

Page 136

Page 137
Supervising NEs is an essential aspect of the network management. It enables the gathering of information
concerning the behavior of the NE with respect to its functional state.
The supervision of an NE consists in establishing a communication that allows the user to perform EML operations
such as configuration and alarm management.
The NE address must be declared before starting the supervision of this NE.
After supervision is started, the Supervision State attribute changes from DECLARED to SUPERVISED.

Page 138

Page 139

Page 140
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 Create Sub-Network) or list
the first-level sub-networks (Search Sub-Networks).
From the Sub-Networks in the Sub-Network lists, it is then possible:
To search the contained Sub-Networks or other Physical or SDH (OTN) objects.
To create a new contained sub-network.
To modify (or even delete) the selected sub-network

Page 141
ROOT is always configured by default as the root network under which all managed sub-networks must be
created, based on the desired hierarchy.
ROOT cannot directly contain nodes.

Page 142

Page 143
If the creation is successful, the header window of the Create Sub-network panel turns green for success; red
indicates a failure.

Page 144

Page 145

Page 146

Page 147

Page 148

Page 149

Page 150

151 1 Page 151
Section 3 Page
Module

Page 152
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.

Page 153
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 the case of an Abort request, the NEs discovered up to the time the discovery was interrupted can be created
by clicking on Next.

Page 154
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.
Eventually change the location name, check NE IP address, User ID and password, and start supervision.

Page 155

Page 156

Page 157

Page 158

Page 159

Page 160

Page 161

Page 162

Page 163

Page 164

Page 165

Page 166

Page 167

Page 168

Page 169

Page 170

Page 171

Page 172

Page 173

Page 174

Page 175

Page 176

Page 177

Page 178

Page 179

Page 180

Page 181

Page 182

Page 183
Deletion of Correlated Cross Connections is not allowed.

Uncorrelated Cross Connections may be deleted.
Fixed cross Connections can neither be created nor deleted.
Inconsistent Cross Connections can be reconciled.

Page 184

Page 185
A cross connection with a state of partial can result from:

Deletion of a Cross Connection from the NE Cross Connection Page which partially fails
Create/Modify/Delete of a Cross Connection on a Network Connection Provisioning Order partially fails

Page 186

Page 187
Only correlated cross connections have a Connection Name displayed in the list. Correlated Cross Connections
cannot be manually deleted.

Page 188

Page 189

Page 190

Page 191

Page 192

Page 193

Page 194

Page 195

Page 196

Page 197

Page 198

Page 199

Page 200

Page 201

Page 202

Page 203

Page 204

Page 205

Page 206

Page 207

Page 208
Depending upon the status of the ASAP (enabled or disabled) the following occurs:
If ASAP is currently enabled, Manual Disable ASAP is available
If ASAP is currently disabled, Manual Enable ASAP is available

Page 209

Page 210

Page 211
Inconsistent Trails or Paths with SNC Mismatches, Parameter Mismatches, and ASAP Mismatches can be
acknowledged.

Page 212

Page 213

Page 214

Page 215

Page 216

Page 217

Page 218

Page 219

Page 220

Page 221

Page 222

Page 223

Page 224
course.

Page 225
Internal Optical Section (OS) - is a physical fiber connection that is provisioned within the NE and established as
bidirectional connections either automatically by the NE when it detects a valid signal, or explicitly through a TL1
command.
The OS connection can be either discovered, provisioned by the user, or created by the user during Path/Trail
connection provisioning in 1350 OMS as Optical Sections.
External Optical Section connections are physical fiber connections configured between two nodes (a physical
connection between the TDM NE OC-n port and the WDM OT client side port).
Internal Optical Transmission Section connections are physical connections between 1830 PSS Nodes. These
connections are created in EML and auto-discovered in WDM based on the connection tables of the NEs.
External Transmission Section (OTS) connections are physical fiber bidirectional connection between two high
speed lines of DWDM NEs which consist of two unidirectional fibers making up a bidirectional connection. These
can be discovered ONLY.

Page 226

Page 227
The Job Updates window is used to view the progress of orders created, and monitor background tasks that are
running.
The Job Updates page can be left open while tasks are performed so that the progress of each connection can be
monitored.

Page 228
Connection Panel options:

Configuration Rate; OS, OTS
Source Type; Not applicable
Protection Type; Unprotected, Protected
Connection Shape; Simple (bi), Double Simple (bi), Simple (uni)
Domain Type; NA
Name Format; Free Format, Telcordia, M14000 (If Telcordia or M1400 are selected, additional fields are displayed
for input).
Connection Name; 83 character name for the connection following Name Format rules (Telcordia, M1400 or Free
Format
Connection Alias; 83 character alternative name for the connection (optional)

Page 229

Page 230
The Supplemental Panel is only displayed for WDM Physical Connections.

The VA port field is applicable only for 4DPA4, 11DPE12 and 11QPA4 circuit packs. For all other circuit packs
select NA.
For keyed service on the 4DPA4 circuit pack select the eVOA port on the OT which will provide the Wavelength
Tracker encoding (WTE) and monitoring functionality. For unkeyed service on the 4DPA4 circuit pack select NA.
For the 11DPE12 and 11QPA4 circuit packs, if an optional sVOA port on the OT will be used to provide attenuation
and monitoring for DWDM configurations select the sVOA port in the VA port field. Otherwise select NA.
For CWDM configurations select NA.
VA1 and VA2 ports are applicable for 4DPA4, 11DPE12 and 11QPA4 circuit packs. VA3 and VA4 ports are applicable
only for the 11QPA4 circuit pack.

Page 231
Most of the Performance Monitoring (PM) options are self explanatory.

In the 15-minute PM and 24-Hour PM fields selecting Yes from the drop-down menu enables the subsequent
fields.
If No is selected the fields remain inactive.
You can select both 15-minute and 24-hour PM data collection on this panel.

Page 232
Starting in 1350 OMS WDM R9.5 the Transmission Parameters shall be displayed if for the selected connection rate
and service type any one of the end points supports the parameter.
As with this scenario, if one of the end NE/port supports a transmission parameter (11DPE12-1-7-L2) but the other
end NE/port does not the system will send the command to the NE that supports the transmission parameter.
Note
If the user types in the NE name on the End Points panel instead of selecting it, the
transmission parameters panel shall not be enabled. I.e., the system shall treat the
scenario as use NE values.

Page 233
Order Panel parameters:

Order Number Is a unique number that identifies the order. This is an optional field as you can either manually
enter an order number or allow 1350 OMS WDM to generate it.
Order Step - During its life, an order goes through a list of successive steps (Defined, Allocated, Implemented or
Commissioned). 1350 OMS WDM validates the connection and then moves it through the steps of the order
management process.
Order Type - Each order type corresponds to a type of provisioning task (Add, Discover, Delete etc.).
Due Date - The date and time the Order completed and moves to the Commissioned order Step.
Ignore Alarm For Completion - The possible values are Yes and No, with a default of Yes. Pertains to the
movement of an order from the Implemented to the Commissioned step.
If Yes, no special processing will be performed.
If No, any alarms on the end ports or any fault states other than (Working) on the direct servers of
the object will prevent the transition to the Commissioned step and the order will remain in the Implemented
step.
Comments Manually enter any notes associated with the connection. This is an optional field.
Technical Reference
Consult the Alcatel-Lucent 1350OMS WDM Guide, Order Management chapter
for additional information on the topic being discussed.

Page 234

Page 235
The Job Updates window is used to view the progress of orders created, and monitor background tasks that are
running.
The Job Updates page can be left open while tasks are performed so that the progress of each connection can be
monitored.

Page 236
Connection Type Select the connection type (e.g. SDH (default), WDM, SDH,SDH/WDM/Interworking etc.).
Transport Alarm Enabling Rule On Definition, On Implementation, On Set in-service, Manual
Implement Rule Automatic, User
Allocation Cost Physical connection cost used in the routing algorithm (range is 0-100). This is the nominal cost
of the physical connection which will be used by the allocation algorithm (Dijkstra static). Allocation sets a cost
threshold and is used to limit resources exceeding the upper threshold.
Show created Physical Connection (Yes (default) or No) If the user selects Yes after creation, a view
containing the created physical connection will automatically appear.

Page 237
You must click on the selection icon to the right of the A Node field to generate the selection options.
Selection options:
Nodes for Physical Connection creation (Filtered) provides a filtered list from which you can select a specific
Node.
Use this option, to filter the Node list based on your criteria. Clicking on the Ok button of the Filter form
presents the Node list displaying only those nodes that meet your criteria. From the Node list highlight a
node and click on Ok.
Nodes for Physical Connection creation provides the entire list of available nodes.
Select the desired node from the Node list and click on Ok. This is the option displayed in the slide.

Page 238

Page 239
On the successful submission of the creation request, the status bar of the Create Physical Connection wizard will
turn Green. The order to create a physical OTS connection is processed.
1350 OMS will automatically provide the Order parameters such as order number, date and time, and completion
information.

Page 240

Page 241
OTS graphical view presents the list of supported lambdas (LC at OCH layer) and for each of them the related (if
provisioned) OTU trail and supported DSR path(s).
This graphical view summarizes in a single window the OTS/OS link characteristics suc as:
OTS alarms
OTU trail name, state and alarms
Used and free channels(frequencies)
Related services (DSR paths) state and alarms
Technical Reference
Consult the Alcatel-Lucent 1350OMS WDM Guide, Internal OS Physical
Connections chapter for additional information on the Physical Connection
Structure graphical feature.

Page 242

Page 243

Page 244

Page 245

Page 246
course.

Page 247

Page 248

Page 249
The slide features the creation of a CWDM OTUk Trail using the Double-Simple (uni) connection shape to illustrate
the complementary port pairs concept.

Page 250

Page 251

Page 252
Connection Rate OCH (default) ensure that you select rates that are based on the circuit packs capability.
Service Type Not Applicable for trails
Routing Field Automatic, Manual, Cross Connection Based, in this example we have selected Automatic hence
we select the Automatic tab in the routing panel.
Protection Type only appears in Automatic routing
Automatic Provisioning Server Layer the system automatically provisions the server layer (Och, OTUk, ODUk)
when a client is provisioned. Automatic provisioning of the server layer is not available for all NEs.
Connection Name 138 character string (optional) If you do not specify a connection name, 1350 OMS WDM will
automatically generate one.
Connection Alias 138 character string (optional)
Server Rate must be compatible with the Connection Rate.

Page 253
Section 4, Module 1 Physical Connections provides an explanation of the End Points panel.

Page 254
Transmission parameters have two behaviors:
AZ trail trace parameter will be displayed only if both the From NE, and To NE support AZ trail trace for that
connection rate and service type (same for ZA trail trace).
The Payload AZ trail trace parameter will be displayed only if both the From NE, and To NE support Payload
AZ trail trace for that connection rate and service type (same for the Payload ZA trail trace).
Other parameters will be displayed only if one of the end NEs supports the parameter for that connection
rate and service type.
Starting in 1350 OMS WDM R9.5 the Transmission Parameters will be displayed if any one of the end points
supports the parameter for the selected connection rate and service type. In previous releases the parameters
were displayed based on the From Port ID1 port only.

Page 255

Page 256
The Routing Effort field drop-down menu contains two options.

Best Effort (default):
The system will at first attempt to find a route with the protection type selected by the user.
If a route of the requested protection type is not found, the system will find a higher or lower
protection type.
If necessary, the protection type selected by the user will be updated by the system.
Enforce Protection Type:
The system will attempt to find a route with the protection type selected by the user.
If a route of the requested protection type is not found, the system will reject the provisioning
request and send an error message.
The Ignore Alarm For Route field is only visible when the routing mode is Automatic. This option is
used by the system to move a network connection from the Defined step to the Allocated step (find the
route).
The drop-down menu contains two options.
Yes- the system will not consider the fault state of the direct servers to find the route.
No (default) - the system will select only those link connections whose servers are not alarmed.

Page 257

Page 258
Port Constraint Node Name allows you wish to include a Port as a routing constrain by selecting the node that
contains the port.

Page 259
You can also populate the Auto Routing Constraints Table using the Send To menu item when you have a list of
Trail Connections, Link Connections and Nodes.

Page 260
When Alarm Enabling is set to Not Set, no Alarm Severity Assignment Profile (ASAP) is set on the connection.
When set to Enable, the ASAP on a connection implies that the alarms are reported by default based on the ASAP
rules for that particular path/trail/physical connection.
When set to Disable, the ASAP is set to None where no alarms are reported and all alarm severities are set to
Not Reported (NR).
This feature is not available for all Network Elements, Enabling or Disabling ASAP could take several minutes to
complete.
Alarm Severity Assignment Profile is the function that allows the assignment of severities to the alarms
depending on their probable causes.
Note
Check the Job Updates window and the Operations log for completion information.

Page 261

Page 262

Page 263

Page 264

Page 265

Page 266

Page 267

Page 268

Page 269

Page 270

Page 271
Note
Check the Job Updates window and the Operations log for completion information.

Page 272

Page 273

Page 274
Oder Sensitive indicates whether or not the exact order of the selected links should be used when using fully
constrained routing (manual routing). This will be discussed in detail later in this section.

Page 275
Show All Link Connections - allows the user to view all of the link connections with system link ownership
independently of the link connection state.
No indicates that not all links are shown. The Link Connection Selection window displays only the link connections
with system link ownership in the Available or Connected link connection state.
Yes indicates that all links are displayed.

Page 276

Page 277

Page 278

Page 279

Page 280

Page 281

Page 282

Page 283

Page 284

Page 285

Page 286

Page 287

Page 288

Page 289

Page 290

Page 291

Page 292

Page 293

Page 294

Page 295

Page 296

Page 297

Page 298

Page 299

Page 300

Page 301

Page 302

Page 303

Page 304

Page 305

Page 306

Page 307

Page 308

Page 309

Page 310

Page 311

Page 312

Page 313

Page 314

Page 315

Page 316
course.

Page 317
The Optical Data Unit1 (ODU1) may be multiplexed into an ODU2 or ODU3 (e.g. 4 ODU1s = ODU2, 16 ODU1s or 4
ODU2s = ODU3).
The termination of the OPU, ODU and OTU is performed at the electrical level as referenced by ITU-T G.709.
The termination of the Och, OMS and OTS is performed at the optical levels as referenced by ITU-U G.872.

Page 318
Y-Cable Protection is also known as Optical Sub-Network Connection Protection.
The graphic does not display the Z end which is between two routers.
On the graphic, following the left to right signal path, an unprotected client signal is
passively head-end bridged by the Y-cable to a pair of redundant transponders.
Each transponder transmits a WDM line signal onto a diversely routed fiber. One signal
is the primary, and one signal is the secondary. At the far end, the primary and secondary
signals are received by another pair of redundant transponders.
The transponder receiving the primary line signal converts it to a client signal and
passes it through the Y-cable to the client equipment.
The secondary transponder has its client interface turned off. In the event of a primary
line fiber cut, primary transponder failure, or primary signal degrade, the primary
transponder in the failed path will disable client signal transmission and the secondary
transponder will turn on its client signal transmission.
A major advantage to O-SNCP vs. using an OPS card is that the transponders perform the
switching. Because the transponders are O-E-O devices, protection switching can be
triggered by digital performance monitoring.

Page 319

Page 320
Four OS connections will be created:

An OS Connection between the Working Port on the A End Y-cable circuit pack and the OTU client port
selected by the user as the A End Working Port
An OS Connection between the Protection Port on the A End Y-cable circuit pack and the OTU client port
selected by the user as the A End Protection Port
An OS Connection between the Working Port on the Z End Y-cable circuit pack and the OTU client port
selected by the user as the Z End Working Port
An OS Connection between the Protection Port on the Z End Y-cable circuit pack and the OTU client port
selected by the user as the Z End Protection Port.
Note: When a DSR/ODUk path with Y-Cable Protection is deleted

or canceled, the OS will not be removed.

Page 321
The protection capabilities supported by the 1830 PSS-36/PSS-32/PSS-16 OTs is detailed in the following table.

Page 322

Page 323

Page 324
If the user selects any value except Use NE Values for the Signal Type, the From and To Optical Transponder
Working and Protection Ports, must be assigned with the user selected signal type.
If the user selects any value except Use NE Values for the Signal Type, the From and To Optical Transponder
Working and Protection Ports, must be assigned the same signal type.

Page 325

Page 326

Page 327

Page 328

Page 329

Page 330
Following the left to right signal path, an unprotected client signal is converted to a
WDM line signal by a transponder.
An Optical Protection Switch (OPS) pack is inserted between the transponder and WDM
filter.
The OPS head-end bridges (passive optical splitting) the line signal to a pair of diversely
routed fibers.
At the far end of the network, the two line signals are received by the far-side OPS.
The OPS switches (optically) a valid line signal to the far-end transponder, which
forwards the signal to the far-end client. In the event of a line fiber cut on the working
path, the far-end OPS switches to the alternate signal.
The switching criteria is based on loss of optical power.
The OPS also monitors the health of the protect path so that if there is a fiber cut, the
signal will be switched to a known good path.
The reverse path operates in the same but independent manner, i.e., the OPS supports
unidirectional switching.
The 1350 OMS WDM operator selects Optical Transport Service endpoints and defines
the service protection type to be OPSA protected via a Create wizard.

Page 331

Page 332

Page 333
Ensure the 1350 OMS WDM application can communicate with all NEs in the connection.
Open the Job Updates window to monitor the status of the added connection.

Page 334

Page 335

Page 336

Page 337

Page 338
Check the Job Updates and Operations windows for order completion.

Page 339

Page 340

Page 341
Note
Working and protection ports must have the same port number. Ex. OPS-2-5-SIG

Page 342
Note
Working and protection ports must have the same port number. Ex. OPS-2-5-SIG

Page 343

Page 344
See Section 4 Module 2 Path and Trail Connections: Create a Path w/Walker routing for an explanation of the
Order Sensitive field.

Page 345

Page 346

Page 347

Page 348

Page 349

Page 350

Page 351

Page 352
The OT performs single channel OEO to translate the CWDM signal to an electrical and the electrical signal to a
DWDM signal.
When a connection has CWDM-DWDM regeneration multiple OTUk trail connections are required for a single
DSR/ODUk path connection. Separate OTUk connections are required for each CWDM and DWDM portion of
the connection. An OTUk connection must be terminated whenever the optical signal is translated to an
electrical signal at a circuit pack performing OEO regeneration.
If a connection performs CWDM-DWDM regeneration two OTUk connections are required.
Each OTUk connection carries a pair of transmit and receive frequencies for the CWDM Single Fiber in our
example.
CWDM and DWDM support different frequency ranges and the frequency of the connection must change during
CWDM-DWDM or DWDM-CWDM Regeneration.
For the DWDM OTUk connections a connection shape of Simple (bi) is required.
For the CWDM OTUk connection, Single-Fiber a connection shape of Double Simple (uni) is required.
The DWDM OTUk connections may be keyed or unkeyed. The CWDM connections must be unkeyed.
All OTUk connections composing the DSR/ODUk path connection do not have to have the same value of keyed/
unkeyed.

Page 353
NPR the Network Physical Resource is part of the 1350OMS-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.

Page 354

Page 355

Page 356

Page 357

Page 358

Page 359

Page 360

Page 361

Page 362

Page 363

Page 364

Page 365

Page 366

Page 367

Page 368

Page 369

Page 370

Page 371

Page 372

Page 373

Page 374

Page 375

Page 376

Page 377

Page 378

Page 379

Page 380

Page 381

Page 382

Page 383

Page 384
DSR - Digital Service Rate, a layer rate that carries either SONET signals, or data services.

Page 385

Page 386

Page 387

Page 388

Page 389

Page 390

Page 391

Page 392

Page 393

Page 394

Page 395
electrical Variable Optical Attenuator (eVOA) - Works with the Tap module to provide input for Wavelength
Tracker modulation and provides optical tap for feedback signal to the Wavelength Tracker.
Orthogonal coding - provides the ability to make changes in isolated areas of code with minimum impact to
other parts of the system.

Page 396

Page 397

Page 398

Page 399

Page 400

Page 401

Page 402

Page 403

Page 404

Page 405

Page 406

Page 407

Page 408

Page 409

Page 410

Page 411

Page 412

Page 413

Page 414

Page 415

Page 416

Page 417

Page 418

Page 419

Page 420

Page 421

Page 422

Page 423

Page 424

Page 425

Page 426

Page 427

Page 428

Page 429

Page 430

Page 431

Page 432

Page 433

Page 434

Page 435

Page 436

Page 437

Page 438

Page 439

Page 440

Page 441

Page 442

Page 443

Page 444

Page 445
The Green field commissioning process flow is described as follows:

1.
The 1350 OMS user initiates a request to start commissioning from the integrated GUI. The user will receive a
prompt to select an already transferred, (through FTP), EPT file.
2.
The CPB will obtain the IP addresses and other SNMP parameters from the Physical Network Manager (PNM) by
means of a DB View.
3.
The CPB will do the necessary discovery and validations and will implement the commissioning and set the
optical parameters specified in the EPT file.
4.
In case of errors, CPB will notify the GUI server and the user will be notified.
5.
When commissioning has completed, CPB will send a completion notification to the user through the GUI
server.

Page 446

Page 447

Page 448

Page 449

Page 450
The CPB Plan File Upload Page is shown in an Internet Explorer window .

Page 451

Page 452

Page 453

Page 454

Page 455

Page 456

Page 457

Page 458

Page 459

Page 460

Page 461

Page 462

Page 463

Page 464
ASE Commissioning commissioning process using inter and intra-node losses to set amplifier gains and expected
per-channel powers at various Wavelength Tracker detect points.

Page 465

Page 466

Page 467

Page 468

Page 469
Coloring is used to indicate normal, abnormal conditions in the egress and ingress components. Yellow
highlighting indicates suspect component. Red highlighting indicates defective component. The Loss Report,
when displayed to the user, can be saved locally in the client PC or sent to a network printer.

Page 470

Page 471

Page 472

Page 473

Page 474

Page 475

Page 476

Page 477

Page 478

Page 479

Page 480

Page 481

Page 482

Page 483

Page 484

Page 485

Page 486

Page 487

Page 488

Page 489

Page 490

Page 491

Page 492

Page 493
Counter Summary groups alarms according to user defined filtering criteria

Sublist Content shows all the alarms according to the sublist selected by the user
Sublist Counter The Sublist Counter area is composed of a table that displays the counters showing the total
alarms for the sublist selected in the Counter Summary table.
Pagination area allows the user to adjust the number of alarmed rows viewed at one time (max = 200)
Message area displays commands as they are performed.

Page 494

Page 495

Page 496

Page 497

Page 498

Page 499

Page 500

Page 501

Page 502

Page 503

Page 504

Page 505

Page 506

Page 507

Page 508

Page 509

Page 510

Page 511
Reservation ensures that only one operator is responsible for an alarm.

An alarm can be reserved only if it has not been reserved by another operator.
To unreserve an alarm follow the procedure on the slide however click on the Unreserve icon on the Main
toolbar.

Page 512

Page 513
To un-reserve an assigned alarm, follow the procedures on the Reserve an alarm slide however click on the
Unreserve icon on the Main Toolbar.

Page 514

Page 515

Page 516

Page 517

Page 518

Page 519

Page 520

Page 521

Page 522

Page 523

Page 524

Page 525

Page 526

Page 527

Page 528

Page 529

Page 530

Page 531

Page 532

Page 533

Page 534

Page 535

Page 536

Page 537

Page 538

Page 539

Page 540

Page 541

Page 542

Page 543

Page 544

Page 545

Page 546

Page 547

Page 548

Page 549

Page 550
This feature is not available for all NEs.

Enabling/Disabling ASAP can take several minutes to complete.

Page 551

Page 552

Page 553

Page 554

Page 555

Page 556

Page 557

Page 558

Page 559

Page 560

Page 561

Page 562

Page 563

Page 564

Page 565

Page 566

Page 567

Page 568

Page 569

Page 570
Auto Purge Automatic purge of measure (True/False)

Collect Counter counters belonging to the granularity period will or will not be collected (True/False). False
indicates that the historical data counters will not be collected, even when the measure is activated. This implies
that the goal of the measure is set to Threshold Crossing Alert profiles on the termination points.

Page 571

Page 572

Page 573

Page 574

Page 575

Page 576

Page 577

Page 578

Page 579

Page 580

Page 581

Page 582

Page 583

Page 584

Page 585

Page 586

Page 587

Page 588

Page 589

Page 590

Passing on and copying of this document, use and communication of its contents
not permitted
without
written
authorization
All Rights
Reserved
Alcatel-Lucent
2012 from Alcatel-Lucent
@@COURSENAME - Page
591

Page 591

1350 Oms Wdmr9.6 Sgv2 Ce

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1350 Oms Wdmr9.6 Sgv2 Ce

Caricato da

Copyright:

Formati disponibili

All rights reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2012

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2012

Section 1. Product Overview

All Rights Reserved Alcatel-Lucent 2012

Welcome to 1350 OMS WDM R 9.6 Operation

Upon completion of this course, you should be able to:

Explain the 1350 OMS WDM application topology

Use the 1350 OMS WDM Graphical User Interface

Describe Network Element Management

Identify Link, Cross, and Inconsistent connection concepts

Determine Physical, Path and Trail requirements

Determine Transport Services requirements

Identify Wavelength Tracker concepts

Explain Commissioning and Power Balancing

Identify Fault Management principles

10. Determine Performance Monitoring requirements

All Rights Reserved Alcatel-Lucent 2012

Conventions used in this guide

Where you can get further information

All Rights Reserved Alcatel-Lucent 2012

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

Each application is license controlled and separately purchasable.

It relies on the Common Fault Management component to display alarms.

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

For NMS constraints, the following rules apply.

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

Network protection management

Optical power commissioning and power balancing

Wavelength Tracker capabilities

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

NEs may be auto discovered or manually created.

Supervising NEs is an essential aspect of the network management.

All Rights Reserved Alcatel-Lucent 2012

Optical Section (OS)

Optical Transmission Section (OTS)

All Rights Reserved Alcatel-Lucent 2012

2. Node and port termination points

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

Fault connection detection at fiber/WSS level