Alcatel-Lucent 1350OMS Release - 11JobAid

RESTRICTED
Alcatel-Lucent 1350OMS Release 11

Job Aid
RESTRICTED
Table of Contents
Page
Introduction ......................................................................................................................................... 5
1.1 Purpose ........................................................................................................................................ 5
1.2 Scope ........................................................................................................................................... 5
1.3 References ................................................................................................................................... 5
1.4 Product Description...................................................................................................................... 5
1.4.1
Modular Architecture ..................................................................................................... 5
1.4.2
Hardware ....................................................................................................................... 6
1.4.3
Virtualisation ................................................................................................................. 6
1.4.4
Network Architecture ..................................................................................................... 7
1.4.5
Communications and High Availability (HA) ................................................................. 7
System Login: Web Desktop ................................................................................................................ 8

2.1 Web Portal ................................................................................................................................... 8
2.2 Network Management (MS-GUI) ................................................................................................. 9
Operation & Provisioning .................................................................................................................. 11

3.1 EML .......................................................................................................................................... 11
3.1.1
NE Provisioning ........................................................................................................... 11
3.1.2
NTP Configuration ....................................................................................................... 13
3.1.3
MIB Backup................................................................................................................. 13
3.1.4
MIB Restore................................................................................................................. 14
3.1.5
Download NE Software ................................................................................................ 15
3.1.6
Alarm Debouncing ....................................................................................................... 18
3.2 NPR ........................................................................................................................................... 19
3.2.1
Sub-Network creation................................................................................................... 20
3.2.2
Node Management ....................................................................................................... 20
3.2.3
External Network creation ............................................................................................ 21
3.2.4
External Physical Links Discovery ............................................................................... 22
3.2.5
Physical Connection creation ........................................................................................ 23
3.2.6
Internal OS connections creation .................................................................................. 24
3.3 OTN .......................................................................................................................................... 27
3.3.1
End-to-End service provisioning................................................................................... 28
3.3.2
OTU Trail creation ....................................................................................................... 29
3.3.3
OTU Trail deletion ....................................................................................................... 39
3.3.4
ODU Trail creation....................................................................................................... 39
3.3.5
ODU Trail deletion....................................................................................................... 45
3.3.6
Protected Path creation (Y-cable) ................................................................................. 46
3.3.7
Unprotected Path creation............................................................................................. 46
3.3.8
Unprotected Path deletion............................................................................................. 53
3.3.9
Protected Path creation (OPS)....................................................................................... 53
3.4 IOO ........................................................................................................................................... 54
3.4.1
External OS definition .................................................................................................. 54
3.4.2
IOO GUI startup........................................................................................................... 54
3.4.3
Alarms Configuration ................................................................................................... 55
3.4.4
PM FTP Configuration ................................................................................................. 57
3.5 File Transfer Scheduler (FTS) .................................................................................................... 59
3.5.1
Scheduled MIB Backup ................................................................................................ 60
2
RESTRICTED
3.5.2
Scheduled Software Download ..................................................................................... 63
Administration ................................................................................................................................... 67
4.1 Security Administration ............................................................................................................. 67
4.1.1
User Accounts Administration ...................................................................................... 67
4.1.2
Session Administration ................................................................................................. 74
4.2 Data Management ...................................................................................................................... 76
4.2.1
Backup (EML, NPR, WDM) ........................................................................................ 76
4.2.2
Restore (EML, NPR, WDM) ........................................................................................ 78
4.2.3
NE Software Packages ................................................................................................. 81
4.3 Task Scheduler........................................................................................................................... 84
4.3.1
Task Scheduler EML .................................................................................................... 84
4.3.2
Task Scheduler NPR .................................................................................................... 86
4.3.3
Task Scheduler WDM (OTN) ....................................................................................... 88
4.4 Performance Monitoring ............................................................................................................ 90
4.4.1
Enable Performance Monitoring ................................................................................... 90
4.4.2
Performance Monitoring on EML ................................................................................. 92
4.5 NE Remote Inventory ................................................................................................................ 94
4.5.1
Upload Remote Inventory............................................................................................. 94
4.5.2
Global Remote Inventory ............................................................................................. 95
Maintenance & Troubleshooting ....................................................................................................... 98

5.1 Alarm Surveillance .................................................................................................................... 98
5.1.1
Current Alarms............................................................................................................. 98
5.1.1.1 Show NE alarms ......................................................................................... 98
5.1.1.2 Show EML alarm list.................................................................................. 99
5.1.1.3 Navigate from EML alarms to NE view ..................................................... 99
5.1.1.4 Alarm correlation on NPR ....................................................................... 100
5.1.1.5 Show physical object alarms .................................................................... 101
5.1.1.6 Show NPR alarm list ................................................................................ 101
5.1.1.7 Navigate from NPR alarms to Physical view ........................................... 102
5.1.1.8 Alarm correlation on OTN ....................................................................... 103
5.1.1.9 Show WDM alarm list .............................................................................. 103
5.1.1.10 Navigate from WDM alarms to OTN view .............................................. 104
5.1.2
Historical Alarms ....................................................................................................... 105
5.2 User Activity Log .................................................................................................................... 106
5.3 System Monitor ....................................................................................................................... 107
5.3.1
View Application Information .................................................................................... 108
5.3.2
Austostart Management .............................................................................................. 108
5.3.3
Control Management .................................................................................................. 109
5.3.4
Start/Stop Processes ................................................................................................... 110
5.3.5
Trace Files Viewing ................................................................................................... 112
5.4 High Availability (HA) Management ....................................................................................... 113
5.4.1
Start HA..................................................................................................................... 113
5.4.2
Start Data Replication................................................................................................. 115
5.4.3
Stop Data Replication................................................................................................. 117
5.4.4
Global Switchover ...................................................................................................... 118
5.4.5
Stop HA ..................................................................................................................... 120
5.5 Loopbacks ............................................................................................................................... 122
5.5.1
Line port loopbacks .................................................................................................... 122
5.5.2
Client port loopbacks.................................................................................................. 125
3
RESTRICTED
5.6
5.7
5.8
5.9
5.5.3
Y-cable protection ports loopbacks ............................................................................. 127
Optical Power Monitoring ........................................................................................................ 128
5.6.1
Optical power on Trail................................................................................................ 128
5.6.2
Optical power on Physical connection ........................................................................ 130
Inconsistency Check ................................................................................................................ 131
5.7.1
Inconsistent Connections ............................................................................................ 131
5.7.1.1 SNC Mismatches....................................................................................... 132
5.7.1.2 Parameter Mismatches ............................................................................. 133
5.7.1.3 Download Disable Mismatches................................................................. 135
5.7.2
Uncorrelated Cross-connections ................................................................................. 136
Protection Switching ................................................................................................................ 139
5.8.1
OSNCP with Y-cable ................................................................................................. 139
5.8.2
OSNCP with OPS ...................................................................................................... 139
EOS Simulator ......................................................................................................................... 139
5.9.1
EOS installation and configuration ............................................................................. 139
5.9.2
EOS usage.................................................................................................................. 140
Miscellaneous ................................................................................................................................... 143

6.1 Transponder Removal .............................................................................................................. 143
6.2 Transponder Addition .............................................................................................................. 144
Document Control .................................................................................................................................. 145

Authorisation ..................................................................................................................................... 145
Amendment List ................................................................................................................................ 145
Appendix A
Glossary .......................................................................................................................... 146
RESTRICTED
Introduction
1.1
Purpose
This document aims to describe the basic procedures used to operate the Alcatel-Lucent 1350OMS
system (Release11), focused on provisioning, administration and troubleshooting of WDM systems.
1.2
Scope
This document is intended primarily for operations personnel who use the1350OMS for network
administration and provisioning. It is only a quick reference guide and does not replace the vendors
handbooks/manuals. Users should always refer to vendors documents for detailed information.
1.3
References
The following documents are available on IME server:
Alcatel-Lucent 1830PSS Long Haul DWDM Job Aid.
NGTT+ ALU OMS NPN.
1350 OMS Administration Guide: Common Tools and Processes.
1350 OMS Administration Guide: Common GUI Functions.
1350 OMS Getting Started Guide.
1350 OMS EML Guide.
1350 OMS OI Guide.
1350 OMS OTN Guide.
1350 OMS HA Guide.
1350 OMS Service Assurance Guide.
1.4
Product Description
The Alcatel-Lucent (ALU) 1350 Optical Management System (1350OMS) is the unified network
management application suite for the Alcatel-Lucent Optics equipment portfolio. It is the network
management platform that is used to manage the 1830PSS network elements in NGTT+.
1.4.1 Modular Architecture

1350OMS architecture employs a concept of modular SW components, where each component is
specialized in a well-defined task or over a specific network technology.
1350 OMS-EML provides NE supervision and administration, Alarm Supervision, Common PM,
FTS (File Transfer Scheduler) including MIB back-up and restore for all the technologies.
1350 OMS-NPR manages all network physical resources and provides a map view of the
network.
1350 OMS-OTN provides end-to-end provisioning and supervision of the WDM services and
infrastructure.
1350 OMS-OI (IOO) enables the 1350 OMS applications to export data to multiple external
operation systems (OSs). It allows an external OS to synchronize alarms, performance
RESTRICTED
monitoring, network inventory, and remote inventory data with any of the 1350OMS
applications.
1350 OMS-HA provides 1+1 High Availability capabilities at both platform and application
level, offering a complete resilience solution to be offered to Disaster Recovery Centres.
1350 OMS-GUI provides the function of displaying the 1350 OMS GUI to users and is located
between the user and the master servers.
1.4.2 Hardware
The servers used for the 1350OMS include 2x Mascot servers and 2x Blacktown servers. All
servers share the following specification:
DL380G8-16core 128GB RAM; 4 x 600GB HDD 2 RU.
2x 4 port LAN card for the master servers (1 built in, 1 extra).
1x 4 port LAN card for the GUI servers (1 built in).
The Mascot 1 server is installed with the OTN, NPR and GUI applications while the Mascot 2
server is installed with 2x EML and 1x GUI applications. The Blacktown servers are a replica of the
Mascot pair, providing redundancy for OTN, NPR and EML applications.
Below is a generic picture of the HP ProLiant DL380G8.
In addition to the servers, 4x HP DAT160 tape drives are provided to provide on-site backup for
each server. They are connected to the servers via USB cables.
1.4.3 Virtualisation
The 1350OMS R11 introduces the new HP Linux ProLiant platforms and makes use of the
Virtualisation mechanism of Red Hat OS Kernel. Virtualisation allows for virtual servers to be
created within one physical server allowing applications to be installed on separate virtual servers
and physical resources allocated to each virtual server. This approach provides better server
utilisation and helps to reduce the number of physical servers needed.
Each application on the servers is housed in a virtual machine with dedicated resources. See below
the virtual machine allocation on each server:
RESTRICTED
1.4.4 Network Architecture

Users access the 4x GUI servers via the Citrix Farm. EML1 and EML2 of each server are
responsible to communicate with network elements as well as OSS for sending alarms. Each server
communicates with each other for internal information exchange and high availability data
replication.
Users
Citrix Farm
HA Data replication
Mascot 1 - GUI1,
NPR, OTN
Blacktown 1 GUI1, NPR, OTN
HA Data replication
Mascot 2 GUI2,
EML1, EML2
Blacktown 2
GUI2, EML1,
EML2
OSS
1830 PSS
Network
1.4.5 Communications and High Availability (HA)

LAN0 (called northbound) of each server handles all external and internal communications of the
1350OMS virtual servers with the exception of communications with the network elements. Each
EML virtual server has two dedicated LANs (LAN1, 2 and LAN3, 4) assigned for communications
with the network elements, also called southbound.
The OTN, NPR, EML1 and EML2 applications in one site have data replicated to the other site for
redundancy via LAN0.
The 4x GUI servers do not have data replication. Therefore if user accounts need to be consistent
across the servers, they need to be managed manually. All GUI servers communicate with all the
other virtual servers in all 4 physical machines.
RESTRICTED
System Login: Web Desktop
The Web Desktop is the web application which provides a central access point. From this access
point, the user is authenticated and can navigate to the 1350OMS Web Portal to access 1350OMS
Applications.
Since Optus uses Citrix environment to access the NMS applications, the Web Desktop is bypassed
and reduced to only a login window. Follow the steps below to login to the system via Citrix/Web
Desktop.
1) Open an Internet browser and type in the Citrix URL.
2) Enter the username and password for Citrix and login. The NMS user interface will be shown as
below:
3) Click on the relevant USM/GUI server icon to open the Web Portal login window.
4) Enter the Alcatel-Lucent User/Password and click on Login to launch the Web Portal.
2.1
Web Portal
The Web Portal is a Java application that is started when the user logs in from the Web Desktop.
The Web Portal provides the user with a view of all the 1350OMS Applications and manages GUI
navigation between the subsystem components.
Once the Web Portal is launched via the Web Desktop, the following screen will be shown:
RESTRICTED
2.2
Network Management (MS-GUI)
The Multi Service Graphical User Interface (MS-GUI) presents maps, lists, queries, and graphical
views of network definitions. Examples of graphical views include routing displays and physical
connection structures. The MS-GUI provides a central point supporting comprehensive functional
navigation across the whole managed network and includes applications for network provisioning
and inventory management.
5) From the Web Portal, select the Management folder on the left panel and double click (or right
click and select Start) on the Network Management icon in the right panel to start the Network
Management application.
6) The Network Management window will open as shown below:
RESTRICTED
Verify that all application servers are connected: if the plug icon located at the bottom left
corner in unplugged, it means that one or more applications are not running.
For more information on application servers connection; from the main menu click on File
Properties. The pop-up window shows the connection status of the applications:
10
RESTRICTED
Operation & Provisioning
3.1
EML
The 1350OMS EML application provides element level management (EML) capabilities for
Alcatel-Lucent NEs. Its set of protocol adapters provides all of the element layer functions that are
required to manage the deployed network; such as NE creation, NE MIB backup/restore, software
downloads, etc.
For more information regarding EML application, please refer to 1350 OMS EML Guide.
3.1.1
NE Provisioning
Create NE:
From the main menu, select Actions EML Create NE.
In the Create NE window (shown below), select the correct settings for the NE being created.
Click on Apply and wait for the green banner confirmation; then click on Cancel to close the
window.
11
RESTRICTED
The NE should appear on the NE list in a Declared Supervision State and Misaligned
Alignment State. To display NE list, from the main menu select Search EML Network
Elements.
Set NE Address:
Highlight the newly created NE from the list, right click and select Actions Composite NE
Set Address. Enter the Primary Address, Primary User Id (admin) and Primary Password
(admin). The Partner NE address must be entered as 0.0.0.0, unless there is a Partner NE, in
which case the address will be automatically populated. Click on Apply and wait for the green
banner confirmation; then click on Cancel to close the window:
Start Supervision:
Highlight the new NE from the list, right click and select Actions Supervision Start
Supervision. In the pop-up window, click on Yes to confirm the operation. The Supervision State
will change to Activating and then to Supervised. A pop-up window will confirm the command
execution being successful. Click on OK to close the window.
The NE has been created successfully and the Alarm Synthesis field may change colour to red,
orange, yellow, or light blue, depending on the alarm status on the NE.
Navigate to Equipment Alarm list:
Highlight the NE from the list, right click and select SearchNE Alarms. The Fault
Management application will start and the selected NE alarms will be filtered at the bottom of
the left panel list:
Navigate to Equipment view:
Highlight the NE from the list, right click and select SearchShow Equipment. An Internet
Explorer window will be launched, showing the equipment view.
12
RESTRICTED
3.1.2
NTP Configuration
The NTP server IP address can be checked/changed via NMS with the following operation:
Highlight the NE from the list, right click and select Actions NTP Configuration.
Switch to the NTP IP tab to check the configured values.
Enter a new value (if needed), click on Apply and wait for the green banner confirmation.
Click on Cancel to close the window.
Warning: If only one NTP IP address is configured and its changed via NMS, it will cause the
NTP to be disabled and needs to be re-enabled. Follow the steps below to re-enable NTP:
1) Right click on the NE and select Actions NTP Configuration.
2) Switch to the NTP IP tab.
3) Change NTP Enabled value to False.
4) Click on Apply and wait for the green banner confirmation.
5) Change NTP Enabled value back to True.
6) Click on Apply, wait for the green banner confirmation and click on Cancel to close the
window.
3.1.3
MIB Backup
Follow the steps below to perform single NE MIB backup.

1) From EML NE list highlight the desired NE, right click and select ActionsSingle click MIB
Backup.
2) A pop-up window will confirm the operation. Click OK to close it.
13
RESTRICTED
3) Find the job on the Jobs list: SearchFile Transfer SchedulerJobs. The Job Status will be
Running or Successful.
4) Check the job progress: while the job is in running status, right click on the job and select
SearchJob Status.
5) Check the job report: once the job is finished, right click on the job and select SearchBackup
Report.
3.1.4
MIB Restore
MIB restore can only be performed from NE equipment view. Follow the steps below to restore a
MIB backup.
1) From EML NE list, highlight the desired NE, right click and select SearchShow Equipment.
2) In the NE view, select AdministrationDatabaseBackup and Restore.
3) The Last Backup Data will be displayed.
Note: The Last Backup Date/Time information will not match with the backup file saved in
EML server (1350OMS) if MIB restore or Craft Terminal MIB backup was performed last; log
into the relevant EML server via terminal window to check the correct date and time of the
BACKUP file before restoring the database.
4) SFTP, User ID, Password, Server IP, Directory and Filename are populated automatically.
14
RESTRICTED
5) If agreed with BACKUP file date and time information retrieved via EML click on Apply and
Restore. A warning message will pop up, click on OK to confirm.
6) Network Element will warm reboot and after successful restore the Last Command and Last
Command Status will be as below:
3.1.5
Download NE Software
Follow the steps below to download software to one or multiple NEs.

1) From EML NE list highlight the desired NE/NEs, right click and select ActionsDownload NE
Software
15
RESTRICTED
2) In the Create and Activate Software Download Job window, enter a Job Name and choose the
Activation time:
Immediate activation means that the job will start upon creation.
Deferred activation means that the job will start at the selected date and time.
Note: Duration: If this field contains a value, the job will end after the stipulated time even if it
is not yet finished.
3) The selected NE/NEs will appear in the Network Elements list. Highlight the NE (or the first NE
in case of multiple NEs) and the fields Target NE Software and Server will be automatically
populated. Enter a Package filter (optional) and click on the SW Package selection icon, select a
package from the list and click OK. Repeat step 3 for all NEs in case of multiple NEs.
4) The selected NE/NEs and software version will appear in the Software Download List. Click on
Apply, wait for the green banner confirmation and then click on Cancel to close the window.
16
RESTRICTED
6) Find the job on the Jobs list: SearchFile Transfer SchedulerJobs. The Job Status will be
Running (if the activation time is Immediate) or Waiting (if the activation time is
Deferred.
SearchJob Status.
8) Check the job report: once the job is finished, right click on the job and select SearchSW
Download Report.
17
RESTRICTED
3.1.6 Alarm Debouncing
This function allows editing the hold off period for each alarms Probable Cause on the 1350OMS
EML system. If an alarm is raised, cleared, and raised again before the hold off time expires, the
repetition counter field in AS gets incremented instead of showing two sets of raise-clear events for
the same alarm.
By default, the hold off time for all alarms is 180 seconds. Follow the steps below to modify this
value, if needed.
1) From the main menu select ActionsEMLConfigure Alarm Debouncing.
2) Enter the filtering criteria (a wildcard must be used in the Search Filter) and click on Click to
Populate button to list the matching alarms.
3) Click on the Hold Period of the desired alarm and use the arrows to modify the value.
4) Click on Apply. Wait for the green banner confirmation and click on Cancel to close the window.
18
RESTRICTED
3.2
NPR
The physical maps can be accessed from the Network Management by selecting Maps on the
bottom-left panel. A tree of Network and Subnetwork maps will be displayed on the top-left panel.
Double click on the desired network or subnetwork to launch the map application.
For more information regarding Map management, please refer to 1350 OMS Getting Started
Guide.
19
RESTRICTED
3.2.1
Sub-Network creation
1) If a new network/subnetwork map needs to be created, right click on ROOT (for Network) or on
the desired parent Subnetwork (for Subnetwork) and select Actions Create Sub-Network.
2) In the Create Sub-Network window, enter a user label and comments for the new network and
click on Apply. Wait for the green banner confirmation and click on Cancel to close the window.
A new subnetwork icon will now appear in the maps tree view panel.
3) Double click on the parent Subnetwork (in case of adding a new Subnetwork) or on ROOT (in
case of adding a new Network) to display the relevant map.
4) A Not Placed icon will appear on the top-left corner of the Map. This icon represents objects
like NEs or Subnetworks that are declared in the system but not graphically added on the map.
This object appears/disappears on the map based on whether not placed objects are present or
not.
5) Double click on the Not Placed icon to display on the right panel the available
Networks/Subnetworks.
6) Drag the new Network/Subnetwork to the desired position in the map and click on the save icon
to save changes. Click on Yes to confirm.
3.2.2
Node Management
Once a NE has been commissioned and added at EML level, a Node will be automatically created
in the Physical layer and it should be ready to be placed in the Map. Before proceeding with the
actions below, check the physical network and subnetwork views to ensure the node has not already
been added.
1) Right click on the desired Subnetwork on the tree view and select ActionsModify SubNetwork.
2) On the Modify Sub-Network window, click on the List Objects to add into the sub-network
button to display the available nodes list, as shown below.
20
RESTRICTED
3) From the node list, highlight the desired NE/NEs, and click on OK. The NE/NEs should now
appear in the Contained Nodes and Sub-Networks list. Click on Apply to confirm the node
addition, wait for the green banner confirmation and then click on Cancel.
4) A Not Placed icon will now appear at the top left corner of the relevant map. Double click on
this icon and the newly added NE/NEs will be displayed on the right panel.
5) Drag the NE/NEs into the desired position in the map and click on the save icon to save changes.
6) Right click on the NE and select ActionsPhysical SynchronizeFull.
3.2.3
External Network creation
An External Network can represent an adjacent subnetwork not supervised by 1350OMS (e.g.
Nortel or Huawei) or Customer Edge (CE) devices. This object is defined in order to improve the
USM representation.
1) On the main menu select Actions Physical Create External Network.
2) In the Create External Network window, enter the user label and location name.
3) Click on Apply and wait for the green banner confirmation. Click on Cancel to close the window.
21
RESTRICTED
4) Follow steps 1) to 5) of section 3.2.2 to add the external network to the map.
3.2.4
External Physical Links Discovery
Once the NE has been fibered up, the physical connections can be uploaded to the map.
1) Right click on the NE on the map and select ActionsPhysicalDiscover External Physical
Links (OTN).
2) When the operation is complete, a message will be displayed at the bottom-left corner of the
main window:
3) A new link will appear in the map, or the number of links will increase in case of already
existing links. Double click on the link to display the physical connections.
4) During Physical connection upload, the OMS connection will be automatically created between
the two end points. To display OMS details, right click on the physical connection and select
SearchOTNClient LC.
22
RESTRICTED
5) The OMS details will be displayed.
3.2.5
Physical Connection creation
Under normal circumstances, physical connections will be automatically created during External
Physical Links Discovery. However, if the fibre connections between source and sink NEs are not
present, or broken; physical connection can be manually created.
Follow the steps below to manually create an external physical connection.
1) From the main menu select ActionsPhysicalCreate Physical Connection.
2) In the Basic Information window, enter a user label, select WDM connection type and click on
Next.
3) In the End Points window select A and Z nodes by clicking on the selection icon or right click on
the NE on the map and select Send ToCreate Physical Connection A Node (or Z Node).
23
RESTRICTED
4) Select A Port and Z Port and click on Apply. Wait for the green banner confirmation and click on
Cancel to close the window.
5) The newly created physical connection will be displayed in a list.
6) During physical connection creation, the OMS connection will be automatically created between
the two end points. To display OMS details, right click on the physical connection and select
SearchOTNClient LC.
3.2.6
Internal OS connections creation
Internal connections refer to connections between transponders line ports and CWR/SFD cards. The
internal OS connections will normally be created at NE level during commissioning and uploaded
to the NMS physical topology during full synchronisation in step 3.2.2
However, if the internal connections need to be created from 1350OMS, follow the steps below:
1) From the main menu select ActionsOTNCreate Internal OS Connection.
2) In the Connection window select the Signal type: OTU4 for 100G transponders, OTU2 for 10G
transponders; enter a Connection Name and click on Next.
24
RESTRICTED
3) In the End Points window, select the end points and click on Next.
Note: since it is an internal connection both end points are in the same NE.
4) In the Supplemental Ports windows leave parameters as default and click on Next.
25
RESTRICTED
5) In the Assurance window leave parameters as default and click on Next.
6) In the Transmission window leave parameters as default and click on Next.
7) In the Order window leave parameters as default and click on Apply. Wait for the green banner
confirmation and click on Cancel to close the window.
.
26
RESTRICTED
8) The new internal connection will be displayed.
9) To search for internal connections, right click on the desired NE (on the map or on the nodes list)
and select SearchOTNInternal Connectivities (OTN).
10)
3.3
The internal connections list will be displayed.
OTN
Once NEs have been added to the system and power balanced/commissioned, added to the map and
fully synchronised, including physical connection discovery, they are ready to be managed by the
OTN application.
This section explains how to use the OTN application provisioning features and provides step-bystep instructions that will help the user to perform end-to-end provisioning tasks.
For more information regarding OTN management, please refer to 1350 OMS OTN Guide.
27
RESTRICTED
3.3.1
End-to-End service provisioning
End to end service provisioning includes two basic tasks:

Trail creation: OTU4, OTU2, or ODU2 (depending on the type of service).
Path creation: DSR (100GEth, 10GEth, SDH, FC) or ODU2 (G.709).
Different types of service will require creation of different types of trails and paths. Use the
schematics below as a guideline to trail/ path creation scenarios:
1) 100GEth
Create OTU4 trail.
ODU4 trail will be automatically created.
Create 100GbE DSR path.
2) G.709 (OTU2) (using 100G Transponder)
Create OTU4 trail.
Create ODU2 path.
28
RESTRICTED
3) 10GEth 10G SDH FC (using 100G Transponder)
Create OTU4 trail.
Create 10GbE/SDH/FC DSR path.
3.3.2
OTU Trail creation
OTUk trails will normally be created during commissioning of transponders. During OTUk trail
creation, all end-to-end optical power levels will be automatically adjusted. Under normal
circumstances there is no need of user intervention to adjust optical power levels.
Before proceeding to OTUk trail creation, make sure the trail hasnt already been created:
Highlight source or sink NE from the map (or from the nodes list), and from the main menu
select SearchOTN TrailsOTUk trails (OTN)
Scroll to the right and check From port/To port of existing trails (if any) to make sure the trail
hasnt already been created.
Follow the steps below if a new OTUk trail needs to be created:

29
RESTRICTED
1) From the main menu select ActionsOTNCreate Trail.
2) In the Connection window: select Connection Rate (e.g. OTU4), enter Connection Name and
leave other parameters as default. Click on Next.
3) In the End Points window click on the From NE1 icon, select the source NE and click OK.
30
RESTRICTED
4) Now click on the From Port ID1 icon, select an Available line port in the desired transponder and
click OK.
5) Repeat steps 3 and 4 to select To End Point 1 Node and Port (sink NE). Then click on Next.
31
RESTRICTED
6) Leave Transmission parameters as default and click on Next.
7) In the Routing window, click on the Walker tab. This window will define the routing constraints for
the trail.
Make sure that the walker mode is set to Link Connection Based.
The source NE should appear in the Focus Node field. If not, use the icon on the right to select it.
8) Select the Neighbor Node using the icon on the right of the field. The Neighbor Node is the NE
adjacent to the Focus Node (next hop). Click OK.
32
RESTRICTED
9) Click on the connection selection icon and choose the desired OMS connection between Focus and
Neighbor NEs. Click OK.
10) Click on the channel selection icon to choose the desired Available frequency. If the link is
unidirectional, the frequency will appear twice in the list (one each direction), select both
directions. Click OK.
33
RESTRICTED
11) The first constraint will be displayed in the Link Connection list and the former Neighbor Node
will now be the Focus Node.
12) Repeat steps 8 and 9 until the Focus Node is the sink NE. The channel (frequency) will be
automatically assigned as per the first constraint (in the example 9170); therefore step 10 is no
longer needed. Click Next.
34
RESTRICTED
13) In the Assurance window change the following settings and then click on Next.
Fault Management area: change Alarm Enabling field to Enable (OTU4 Profile Name will be
displayed).
Performance Monitoring area:
15-minute PM: Yes.
TP monitoring selection: All.
Direction: Bidirectional.
Report Info: No Report.
PM Data Purge Policy: Delete PM Data upon Connection Deletion.
Use same settings for 24-hour PM.
35
RESTRICTED
14) Leave Wave Key Type in Automatic and click on Next.
15) Leave Order parameters as default and click on Apply. Wait for the green banner confirmation and
click on Cancel to close the window.
Note: During OTUk creation, end-to-end optical power levels will be automatically adjusted. This
operation may take over 15 minutes depending on the number of hops in the link. Check the creation
36
RESTRICTED
progress via the Command Deployer: right click on the trail from the list and select SearchCommand
Deployer (the view is not auto refreshed, click on the refresh icon to update the view). Command
Deployer is only available while the operation is In Progress.
Note: Due to a bug in the system, the trail creation wizard might timeout before the trail creation
operation is completed. If this happens, an error message will be displayed in the bottom left corner
(and in the log area): Create Trail: Timeout expired. Ignore this message and allow a few more
minutes for the operation to complete. Monitor the trail creation operation via the trail list Step State.
The trail will be successfully created once Step State is Completed AND Order Step is Commissioned.
37
RESTRICTED
16) After a successful creation, the trail routing display window will be displayed. If the trail creation
failed (timed out) due to the bug mentioned above, open the routing display manually: right click
on the trail and select SearchRouting Display (or click on the routing display icon
).
Note: if the trail creation fails due to any other reason than timeout, the Order Step might stay in
Implemented or Partially implemented status. If this is the case, the Order needs to be cancelled
in order to remove the failed creation before attempting re-creation: right click on the trail and
select ActionsConfigurationCancel.
17) Right click on the trail icon (or the trail name on the list) and select SearchOptical
Power Optical Power A->Z.
18) Verify that power level bars are all green. Click on Refresh to update power levels.
Repeat the reading for the opposite direction Z->A.
38
RESTRICTED
3.3.3
OTU Trail deletion
There are four ways of removing a trail, pay close attention to the implications of each method
before proceeding.
1) Remove: this action will remove the OTUk trail from the NMS and from the NE, only if there
are no clients riding inside the trail, e.g. ODUk trails, Paths. Right click on the trail and select
ActionsRemove.
2) Remove Connections and Clients: this action will remove the OTUk trail AND all ODUk trails
AND Paths riding inside the OTUk trail, from the NMS and from the NE. Right click on the trail
and select ActionsRemove Connection and Clients.
3) DB Remove: this action will remove the OTUk trail from the NMS, only if there are no clients
riding inside the trail, e.g. ODUk trails, Paths. The configuration will still be present at NE level.
Right click on the trail and select ActionsConfigurationDB Remove.
4) DB Remove Connections and Clients: this action will remove the OTUk trail AND all ODUk
trails AND Paths riding inside the OTUk trail, only from the NMS. The configuration will still
be present at NE level. Right click on the trail and select ActionsConfigurationDB Remove
Connection and Clients.
Note: to search for clients riding inside an OTUk trail, highlight the trail from the list, right click
and select SearchClients.
3.3.4
ODU Trail creation
Higher order ODUk trails will be automatically created when higher order OTUk trail is created
(e.g. ODU4 trail will be automatically created when OTU4 trail is created).
Lower order ODUk trails that will ride inside a higher order ODUk trail need to be created (e.g.
ODU2 riding inside an ODU4). Follow the steps below to create an ODUk trail.
1) From the main menu select ActionsOTNCreate Trail.
2) In the Connection window: select Connection Rate (e.g. ODU2), enter Connection Name and
leave other parameters as default. Click on Next.
39
RESTRICTED
4) Now click on the From Port ID1 icon, select an Available line port sub-interface in the desired
transponder and click OK.
40
RESTRICTED
41
RESTRICTED
6) Leave Transmission parameters as default and click on Next.
7) Leave Network Protection Type as None and click on Next.
8) In the Routing window, click on the Walker tab. Make sure that the Walker Mode is set to Trail
Based.
42
RESTRICTED
9) Select the Neighbor Node using the icon on the right of the field. The Neighbor Node is the sink
NE. Click OK.
10) Click on the connection selection icon and choose the desired ODUk trail between Source and
Sink NEs. Click OK.
11) The Connections window will display the details of the higher order ODUk trail that will
transport the new lower order ODUk trail. Click on Next.
43
RESTRICTED
Fault Management area: change Alarm Enabling field to Enable (ODUk Profile Name will
be displayed).
Performance Monitoring area: leave as default.
44
RESTRICTED
13) Leave Order parameters as default and click on Apply. Wait for the green banner confirmation
and click on Cancel to close the window.
14) After a successful creation, the trail routing display window will be displayed:
Note: if the trail creation fails, the Order Step might stay in Implemented or Partially
implemented status. If this is the case, the Order needs to be cancelled in order to remove the
failed creation, before attempting re-creation: right click on the trail and select
ActionsConfigurationCancel.
3.3.5
ODU Trail deletion
There are four ways of removing a trail, pay close attention to the implications of each method
before proceeding.
1) Remove: this action will remove the ODUk trail from the NMS and from the NE, only if there
are no clients riding inside the trail, e.g. ODUk trails, Paths. Right click on the trail and select
ActionsRemove.
45
RESTRICTED
2) Remove Connections and Clients: this action will remove the ODUk trail AND all ODUk trails
AND Paths riding inside the ODUk trail, from the NMS and from the NE. Right click on the trail
and select ActionsRemove Connection and Clients.
3) DB Remove: this action will remove the ODUk trail from the NMS, only if there are no clients
riding inside the trail, e.g. ODUk trails, Paths. The configuration will still be present at NE level.
Right click on the trail and select ActionsConfigurationDB Remove.
4) DB Remove Connections and Clients: this action will remove the ODUk trail AND all ODUk
trails AND Paths riding inside the ODUk trail, only from the NMS. The configuration will still
be present at NE level. Right click on the trail and select ActionsConfigurationDB Remove
Connection and Clients.
Note: to search for clients riding inside an ODUk trail, highlight the trail from the list, right click
and select SearchClients.
3.3.6
Protected Path creation (Y-cable)
TBA
3.3.7
Unprotected Path creation
Follow the steps below to create an unprotected path.

1) From the main menu select ActionsOTNCreate Path.
2) In the Connection window select the following parameters and then click on Next:
Connection Rate: DSR for 100GEth, 10GEth, SDH, FC; or ODU2 for G.709 (OTU2).
Service Rate Type: e.g. Ethernet (use SDH for STM-N services and DATA for FC services).
Service Rate: e.g. 100GbE
Enter Connection Name and leave other parameters as default.
46
RESTRICTED
4) Now click on the From Port ID1 icon, select an Available client port in the desired
transponder and click OK.
47
RESTRICTED
6) In the Transmission window, only if theres a customer requirement to enable LOS propagation,
click on the Edit Parameters(s) button. Otherwise, click on Next and go to step 9.
48
RESTRICTED
7) In the General Parameters window, change A End LOS Propagation and Z End LOS Propagation
to Laser_OFF. Click on Apply, wait for the green banner confirmation and click on Cancel to
close the window.
8) Check that the values have been changed in the parameters list. Click on Next.
49
RESTRICTED
9) In the Routing window, click on the Walker tab. Make sure that the Walker Mode is set to Trail
Based.
10) Select the Neighbor Node using the icon on the right of the field. The Neighbor Node is the
sink NE. Click OK.
50
RESTRICTED
11) Click on the connection selection icon and choose the desired ODUk trail between Source and
Sink NEs. Click OK.
12) The Connections window will display the details of the ODUk trail that will transport the path.
Click on Next.
51
RESTRICTED
Fault Management area: change Alarm Enabling field to Enable (DSR Profile Name will be
displayed).
Performance Monitoring area:
15-minute PM: Yes.
TP monitoring selection: End-pointsonly.
14) Leave Order parameters as default and click on Apply. Wait for the green banner confirmation
and click on Cancel to close the window.
52
RESTRICTED
15) After a successful creation, the path routing display window will be displayed.
Note: if the path creation fails, the Order Step might stay in Implemented or Partially
implemented status. If this is the case, the Order needs to be cancelled in order to remove the
failed creation, before attempting re-creation: right click on the path and select
ActionsConfigurationCancel.
3.3.8
Unprotected Path deletion
There are two different ways of removing a path from 1350OMS:

1) Remove: this will remove the path from the NMS and from the NE. Right click on the path and
select ActionsRemove.
2) DB Remove: this will remove the path only from the NMS; the configuration will still be present
at NE level. Right click on the path and select ActionsConfigurationDB Remove.
3.3.9
Protected Path creation (OPS)
TBA
53
RESTRICTED
3.4
IOO
1350 OMS IOO refers to a set of OS-to-OS interfaces (GENOS) each one providing a specific
service, which can be separately installed on top of the Alcatel-Lucent OS, plug and play
application, or collective to hand off data to several External OS in a default form of notifications.
Management areas covered by IOO are the following:
IOO Alarm Data Handoff Interfaces (IOO ALM)
Exports alarms through ASCII interface data through TCP/IP using either CSV or AVA formats.
IOO Performance Monitoring Data Handoff Interfaces (IOO PM)
Exports performance monitoring through ASCII interface data through TCP/IP using either CSV
or AVA formats.
Exports performance monitoring through ASCII interface data through FTP, the format of the file
is very similar to that exported through socket base interface.
IOO NE Directory Data Handoff Interfaces (IOO NED)
Exports the list of the managed Networks Elements through ASCII interface through TCP/IP.
IOO Web Genos Tool
Web Graphic User Interface to configure IOO subsystems.

For more information regarding IOO, please refer to 1350 OMS OI Guide.
3.4.1
External OS definition
The external OS and its IP address must be defined in the relevant EML server under the hosts file.
1) Login as root to the EML server via Go-Global and open an X-Terminal.
2) Check the External OS name and IP address are included in the hosts file:
$more /etc/hosts
# External Alarm IOO OS for TeMIP
172.18.101.18 temipp2-2.optus.com.au
172.18.101.19 temipp2-3.optus.com.au
172.18.109.41 temipr2-2.optus.com.au
172.18.109.42 temipr2-3.optus.com.au
172.18.109.31 temips2-2.optus.com.au
172.18.109.32 temips2-3.optus.com.au
# External OS for IOO PM-FTP
172.18.12.1 NPRS cdun2040.optus.com.au cdun2040
3) If the IP address and name of the external OS is not present in the hosts file, use vi command
to edit the hosts file and add the entry.
3.4.2
IOO GUI startup
The Web Graphic User Interface (GUI), called Web Genos Configuration Tool, can be started by
launching an Internet browser on a Citrix session and typing the relevant EML server Genos GUI
address. In the example below, the IP address represents EML_1 server in the lab. Change this IP
address and EML instance to login to a different EML server.
54
RESTRICTED
http://10.127.245.2/CGI-BIN/EML_1-11_sop.pl?user_id=alcatel
Alternatively, log in to the individual EML VM via Citrix, and from the Web Portal, select
Operations Network Tools and double click (or right click and select Start) on
GENOSEOS_EML to launch the GUI.
3.4.3
Alarms Configuration
Configure ALM_ASCII EOS to export alarms from EML application to an External OS.
1) Expand ALM_Ascii tree and select EOS_Ascii.
55
RESTRICTED
2) The right panel will show the configured External OS (EOS). Click on the Next button to check
all existing EOS.
3) To add a new EOS click on the Add EOS button.
4) Enter the Identifier (name or IP address of external OS), Key= alcatel, and tick on
AS_identity_name1. Other parameters can be modified as per EOS requirements.
Note: If the Identifier is entered as text (i.e. External OS name), it must be defined in the hosts
file on the relevant EML server. Refer to section 3.4.1 to check/add external OS to hosts file.
5) Click on the Save Data button (floppy disk icon) to save the new EOS configuration. The
following window will pop up:
6) Click on OK to close the pop-up window.

7) Refresh the browser and check that the new EOS has been successfully created.
8) Launch the Processes Monitor and Control (PMC) application from the Web Portal and Stop
the Alarm_ASCII_IH and Alarm_ASCII_CPA processes under the relevant EML-Genos.
56
RESTRICTED
9) A confirmation window will pop up. Click on Yes to confirm the operation.
10) Wait until the processes turn red and re-start them.
12) Wait until both processes go green and close the PMC application.
3.4.4 PM FTP Configuration
Configure PM FTP to export PM data via FTP to external OS.
1) Follow steps 1 to 3 of section 3.4.1 to check/add external OS to hosts file on EML server.
2) Launch the Web Genos Configuration Tool following the steps in section 3.4.2
3) Expand PMFTP tree and select EOS_Pmftp.
57
RESTRICTED
4) The right panel will show the configured External OS (EOS). Click on the Next button to check
all existing EOS.
5) To add a new EOS click on the Add EOS button.
6) Enter the Identifier (name or IP address of external OS), Key= alcatel (or create a new
password)
Note: If the Identifier is entered as text (i.e. External OS name), it must be defined in the hosts
file on the relevant EML server. Refer to section 3.4.1 to check/add external OS to hosts file.
7) Click on the Save Data button (floppy disk icon) to save the new EOS configuration. The
following window will pop up:
8) Click on OK to close the pop-up window.

9) Refresh the browser and check that the new EOS has been successfully created.
10) Launch the Processes Monitor and Control (PMC) application from the Web Portal and Stop
the PM_Handoff_IH and PM_Handoff_FTP_CPA processes under the relevant EML-Genos.
58
RESTRICTED
12) Wait until the processes turn red and re-start them.
14) Wait until all processes go green and close the PMC application.
3.5
File Transfer Scheduler (FTS)
The FT Scheduler is an application to launch multiple file transfer (SW Download, MIB backup)
between the NMS and the NEs, providing scheduling and periodic services.
File Transfer operations are based on the application task named "Job". A Job is defined by a
Descriptor File, that contains the list of target NEs and all the parameters related to the action to be
scheduled (SWDL or MIB Backup).
The Job activation time may be immediate or deferred. In addition, MIB Backup Jobs may be
periodically re-activated every 24 hours.
The job editor allows generating a "Job" containing a sequence of "Sessions", each one composed
of a set of NEs. The policy of providing different sessions within the same job allows having a two
levels approach in the FT operation. All the NEs belonging to a session are downloaded / backed-up
before the NEs of the next session: the job starts from the first NE of the first session and will go
on, following the order of sessions and in each session the order of NEs. This permits to control the
DCN traffic in the network by programming the FT phase to avoid overloading some specific GNEs
or interconnecting DCN links. The maximum NE number for any session is "90" but there is no
limit regarding the maximum session number in a job.
For more information regarding File Transfer Scheduler, please refer to 1350 OMS EML Guide.
59
RESTRICTED
3.5.1
Scheduled MIB Backup
Follow the steps below to perform a Scheduled MIB backup.

Create MIB backup Job:
1) From the main menu select ActionsFile Transfer SchedulerCreate Job.
2) In the Job Creation window enter a Job Name, select MIB Backup type and choose the
Activation time:
Immediate activation means that the job will start upon activation.
Note: Duration: If this field contains a value, the job will end after the stipulated time even if it is
not yet finished.
3) Click on Apply, wait for the green banner confirmation and click on Cancel to close the window.
4) Find the newly created job by selecting from the main menu SearchFile Transfer
SchedulerJobs.
Create MIB Backup Session:

5) Right click on the MIB backup job on the jobs list and select ActionsCreate Backup Session.
6) Enter NE filter criteria (if needed) and click on Select NE icon to retrieve the NE list.
60
RESTRICTED
7) Highlight the desired NEs and click on OK. The Selected NEs will be populated on the Network
Elements list.
8) Click on Apply and wait for the green banner. A confirmation window will pop-up, click on OK
to close it. Click on Cancel to close the Create Backup Session window.
9) Repeat steps 5 to 8 to add more sessions to the job (if needed).
10) Check the backup sessions and NEs associated to a job: from the Jobs list, right click on the job
and select SearchBackup Sessions.
11) Right click on a session and select SearchBackup NEs.
61
RESTRICTED
Activate MIB backup Job:

12) Find the job on the Jobs list: SearchFile Transfer SchedulerJobs.
13) Right click on the job and select ActionsActivate Job.
15) The Job Status will change from Not Active to Running (if the activation time is Immediate)
or Waiting (if the activation time is Deferred)
SearchJob Status.
62
RESTRICTED
17) Check the job report: once the job is finished, right click on the job and select SearchBackup
Report.
3.5.2
Scheduled Software Download
Before you begin:

The NE software must be uploaded to the relevant EML server through NE SW Packages
application. Refer to section 4.2.4 to check/upload NE software.
Once the NE software is present on the EML server, follow the steps below to perform a Scheduled
Software Download.
Create Software Download Job:
1) From the main menu select ActionsFile Transfer SchedulerCreate Job.
2) In the Job Creation window enter a Job Name, select Software Download type and choose the
Activation time:
Immediate activation means that the job will start upon activation.
63
RESTRICTED
Note: Duration: If this field contains a value, the job will end after the stipulated time even if it is
not yet finished.
4) Find the newly created job by selecting from the main menu SearchFile Transfer
SchedulerJobs.
Create Software Download Session:

5) Right click on the Software Download job on the jobs list and select ActionsCreate Download
Session.
6) Enter NE filter criteria (if needed) and click on Select NE icon to retrieve the NE list.
7) Highlight the desired NE and click on OK. The Selected NE will be populated on the Target NE
field.
8) In the SWDL Parameters section, click on the Server selection icon, select localhost and click
OK.
64
RESTRICTED
9) Enter a Package Filter criterion (if needed) and click on the SW Package selection icon.
10) Select the desired SW package and click OK. The Software Download list will be populated
with the selected NE/SW Package.
11) Repeat steps 6 to 10 to add more NEs (if needed). Click on Apply and wait for the green banner
and pop-up window confirmation.
12) Click OK to close the pop-up window and click on Cancel to close the Software Download
Session Creation window.
Activate Software Download Job:
65
RESTRICTED
13) Find the job on the Jobs list: SearchFile Transfer SchedulerJobs.
14) Right click on the job and select ActionsActivate Job.

16) The Job Status will change from Not Active to Running (if the activation time is Immediate)
or Waiting (if the activation time is Deferred)
SearchJob Status.
18) Check the job report: once the job is finished, right click on the job and select SearchSW
Download Report.
66
RESTRICTED
Administration
4.1
Security Administration
4.1.1
User Accounts Administration
The User Accounts application provides the following features:

Displays users and their profiles.
Create/Delete/Edit users accounts.
Change passwords.
Import/Export users database.
Start the User Accounts application from the Web Desktop: select Security Administration folder
under Administration tree and double click (or right click and select Start) on User Accounts icon.
The User Accounts window will display, on the left panel tree, all users currently configured in the
selected USM server.
1) Display User profile: check the user profile type: Administrator, Constructor, Operator,
Viewer, etc.
Click on the desired user on the left panel tree. The users attributes will be shown on the right
panel. Select the Username-Profiles tab to view the associated applications and profile types.
67
RESTRICTED
2) Modify user profile: this action allows the administrator to change the user profile type.
Highlight the user from the left panel tree and select the Username-Profiles tab on the right
panel.
Select the Assigned OS profile that needs to be modified and click on the
it from the list.
68
icon to remove
RESTRICTED
Click on the OS Name to show the available profiles. Select the desired profile and click on the
icon to add it to the Assigned OS column.
Click on Modify to save changes.
A confirmation message will appear at the bottom of the window.

69
RESTRICTED
3) Change password: this action allows the administrator to change/reset a users password.
Select the user from the left panel tree and click on the Set Password button.
The Set User Password window will pop up. Enter the new password and click on Change.
4) Delete user: this action allows the administrator to delete an existing user.
Select the user from the left panel tree and perform one of the following actions:
70
RESTRICTED
From the main menu User ManagementRemove User(s)
Right click and select Remove User.
Press Ctrl+M.
Click on the Remove User(s) icon
A confirmation window will pop up. Click on Yes to confirm the operation.
5) Create user: this action allows the administrator to create a new user.
Select the secdb folder from the left panel tree and perform one of the following actions:
From the main menu User ManagementCreate User
Right click and select Create New User
Press Ctrl+U.
Click on the User Creation panel icon
71
RESTRICTED
In the User Login tab, enter the Login (User name), the New Password and confirm the new
password.
Click on Attributes tab and enter the user name (mandatory). All other parameters are optional.
The new user will be prompted to change its password upon first login. If this is not desired,
change the ResetPassword field to FALSE.
72
RESTRICTED
Click on the Profiles tab, select the OS Name (e.g. EML), the desired Profile Name (e.g.
Constructor) and click on the
icon to add the profile.
Repeat step 4 for all applications (NPR, OTN) and click on Apply.
73
RESTRICTED
4.1.2
Session Administration
The User Session application provides the following features:

Force logout.
Broadcast messages.
Purge closed sessions.
Start the User Session application from the Web Desktop: select Security Administration folder
under Administration tree and double click (or right click and select Start) on User Session icon.
The Sessions Administration window will display all users currently logged in the selected USM
server.
1) Force logout: this action allows the administrator to close (logout) a selected session.
Highlight the user session from the list and perform one of the following actions:
From the main menu select ActionsForce logout
Right click and select ActionsForce logout
Click on the Force logout icon
The Session logout confirmation window will pop up.

Select a Logout Type: If Logout after a grace delay is selected, enter the delay time in
seconds.
Enter a Logout Message: this message will be sent to the session user before the force
logout is performed.
74
RESTRICTED
Click Confirm. The session will change state, first to Forced and after a few seconds to Closed.
2) Purge closed sessions: this action will remove closed sessions from the Sessions list.
Closed sessions can be purged by performing one of the following actions:

From the main menu select ActionsPurge closed sessions
Click on the Purge closed sessions icon
A Purge Confirmation window will pop up. Click on Yes to confirm the operation.
3) Send a message: this action allows the administrator to send messages to selected sessions or
broadcast messages to all sessions.
Highlight a session/sessions from the list and perform one of the following actions:
Right click and select ActionsSend a message
From the main menu select Actions Send a message
Click on the Send a message icon
The Send a Message window will pop up. Enter the message text and select the message
priority. Choose the Sending Type (Selected session(s) only or Broadcast to all sessions), tick
the Include my session box (if needed) and click on Send.
75
RESTRICTED
4.2
Data Management
4.2.1
Backup (EML, NPR, WDM)
3) Start the Backup feature by selecting the desired application (EML, NPR or WDM) from the
Web Portal: select Data Management folder under Administration tree and double click (or
right click and select Start) on the relevant application backup icon:
4) From the main menu select JobNew, or click on the new job icon.
5) In the Backup window, enter a Job Name, tick on the desired backup box and click on Apply
and OK to confirm. Note: Backup on tape is not supported in the current 1350OMS SW
release, do not choose Disk and tape option.
76
RESTRICTED
6) Highlight the created job and from the main menu select JobRun, or click on the Run icon. In
the pop-up window click on Yes to confirm the operation.
7) A pop-up window will display the job progress.
8) When the job is finished, a confirmation message will be displayed in the Messages Area.
77
RESTRICTED
4.2.2
Restore (EML, NPR, WDM)
1) Start the Restore feature by selecting the desired application (EML, NPR or WDM) from the
Web Portal: select Data Management folder under Administration tree and double click (or
right click and select Start) on the relevant application restore icon:
2) The Backup List will display all available backup files. Click on the desired file to restore and
from the main menu select BackupStatus, or click on the status icon, to verify the backup
file.
78
RESTRICTED
3) A pop-up window will display the status of the selected backup file. Click on Close.
4) Click on the verified backup file and from the main menu select BackupRestore, or click on
the restore icon.
5) A confirmation window will pop up. Click on OK to confirm.
79
RESTRICTED
6) A pop-up window will display the job progress.
7) During restore operation, the relevant application (WDM in this example) will change mode to
RestoreMode (no provisioning activities will be allowed during restore).
8) When the job is finished, a confirmation message will be displayed in the Messages Area.
9) From the PMC, change the relevant application mode back to Full Functionality: click on the
application icon (WDM in the example) and select ActionsSet Rub Level WDM_10
FullFunctionality.
80
RESTRICTED
10) Click on Yes to confirm the operation.
11) Wait until the application mode goes back to Full Functionality and the icon turns green.
4.2.3
NE Software Packages
The NE SW Packages application is provided to create NE software packages to download towards

NEs. Follow the steps below to upload new NE software towards the EML server.
1) Start the NE SW Packages application from the Web portal: select Data Management folder
under Administration tree and double click (or right click and select Start) on the relevant EML
NE SW Packages icon.
81
RESTRICTED
2) The SWPAdmin window will pop up as shown below. Click on Install to open a browser in the
Citrix server.
3) Select the first folder where the NE software is located (1830PSSxx) and click on Open to
navigate down to the folder containing the .DSC file.
Note: due to a bug in the system, before uploading 1830PSS R6.0 software packages, ensure
that the NE software descriptor and files are stored in the following directory structure on the
client PC:
\1830PSS-6.0-0\EC\1830PSS-6.0-0\1830PSS\6_0_0\1830PSS.DSC
\1830PSS-6.0-0\EC\1830PSS-6.0-0\1830PSSM\6_0_0\1830PSSM.DSC
82
RESTRICTED
Note: 1830PSS NE Software is composed of two folders: 1830PSSxx and 1830PSSxxM. The
contents of both folders have to be uploaded to the EML server.
4) Select the .DSC file and click on Open. The contents of the folder will be verified and uploaded
to the EML server.
83
RESTRICTED
5) Repeat steps 2 to 4 to upload the contents of the second folder (1830PSSxxM).

6) The newly uploaded software will appear in the Installed Basic Packages window.
7) Click on Close to close the window and stop the NE SW Packages application.
4.3
Task Scheduler
The Task Scheduler GUI enables the administrator to schedule the execution of tasks on one or
several hosts. Tasks typically include backup, purge, and clean-up of data.
4.3.1 Task Scheduler EML
Launch EML Task Scheduler from the Web Portal Administration folder by selecting System and
double click (or right click and Start) on the Task Scheduler (EML 1-11).
The EML Task Scheduler GUI window will pop up.

84
RESTRICTED
To create a new scheduled task (plan), from the main menu select PlanNew Plan or click on the
New Plan icon.
In the New Plan window enter the Plan name. Use the drop-down menu under Host name to select
the workstation on which the scheduling plan is to be executed. Choose the operation to be
performed from the Command drop-down menu.
Enter the Start date and time. If the plan is to be repeated, select the stop date and time, tick the
Repeat delay box and enter the repetition period.
Click on Apply and then close the window.
The new plan will appear in the Plan list window with a blue cross. This means that the new plan
hasnt been activated yet.
85
RESTRICTED
Click on the new plan and validate (activate) it from the main menu PlanValid Plan (or click on
the Validate icon)
The plan blue cross will change to a green arrow indicating its activated.
4.3.2 Task Scheduler NPR

Launch NPR Task Scheduler from the Web Portal Administration folder by selecting System and
double click (or right click and Start) on the Task Scheduler (NPR 1-11).
The NPR Task Scheduler GUI window will pop up.

86
RESTRICTED
New Plan icon.
87
RESTRICTED
the Validate icon).
4.3.3 Task Scheduler WDM (OTN)

Launch WDM Task Scheduler from the Web Portal Administration folder by selecting System and
double click (or right click and Start) on the Task Scheduler (WDM 1-11).
88
RESTRICTED
The WDM Task Scheduler GUI window will pop up.
New Plan icon.
89
RESTRICTED
the Validate icon).
4.4
Performance Monitoring
The 1830PSS NE family automatically send PM data towards the EML application but, unlike
1350OMS release 9.4.10, in release 11, PM data collection has to be enabled at NML level in order
to be processed by EML.
4.4.1 Enable Performance Monitoring
PM data collection at NML level is enabled during OTUk trail creation (for ANALOG and SDH
counters) and during Path creation (for end points Ethernet and SDH counters), see sections 3.3.2
90
RESTRICTED
and 3.3.5. However, if data collection was not enabled during trail/path creation, it can be done at
any time. Follow the steps below to enable PM data collection on a created trail/path.
1) From the Paths /OTUk Trails list highlight the desired connection, right click and select
ActionsModify Parameters.
2) In the Modify Parameters window, select the Assurance tab and modify the parameters as
follows:
On OTUk trails:
15-minute PM: Yes.
TP monitoring selection: All.
On Paths:
15-minute PM: Yes.
TP monitoring selection: End-points only.
91
RESTRICTED
4.4.2 Performance Monitoring on EML
Follow the steps below to display the PM counters collected from the NEs.
1) From the main menu select SearchPMPM Domains on EML.
2) Highlight the online version of the desired PM Domain (e.g. ANALOG), right click and select
SearchMonitored NEs/TPs
3) From the list of monitored NEs, highlight the desired NE , right click and select
SearchMonitored NEs/TPs
4) From the list of monitored TPs, highlight the desired TP and counter (e.g. 15 minutes, CDR,
receive on 112SCA1-1-10-L1), right click and select:
ActionsGenerate Tabular Report: to view a numeric output.
ActionsGenerate Line Chart Report: to view a graphical output.
92
RESTRICTED
5) Use the icons on the right hand side to enter the Granularity, From time and To time parameters
and click on Apply.
6) PM counters will be displayed:

Tabular: click on the + sign on the top-left corner to expand the list and view the PM output
result
93
RESTRICTED
Chart
7) Click on Cancel to close the window.
4.5
NE Remote Inventory
The NE remote inventory feature provides an inventory of NE components, such as board types,
part numbers, serial numbers, slot numbers, etc.
4.5.1 Upload Remote Inventory
This function will upload the NE inventory to the EML server but no information will be displayed.
In order to view the uploaded inventory a Search action needs to be performed. Follow the steps
below to upload and display NE inventory.
Note: To perform NE remote inventory upload, the NE must be Supervised and Reachable.
1) Right click on the desired NE from the EML NE list and select ActionsUpload Remote
Inventory.
2) Click on Yes to confirm the operation and wait for a pop-up confirmation.
94
RESTRICTED
3) Click on OK to close the window.
4) Right click on the NE from the EML NE list and select SearchDisplay Remote Inventory.
The Remote Inventory will be displayed in Notepad format.
4.5.2
Global Remote Inventory
The Global Remote Inventory introduces a wizard that allows the upload of multiple NEs inventory
and also displays the uploaded inventory. Just bear in mind that the more NEs added to the wizard,
the longer it will take to complete the action.
Follow the steps below to upload and display multiple NEs inventory.
1) Highlight the desired NEs from the EML list, right click and select Actions Global Remote
Inventory.
2) The Global Remote Inventory pop-up window will display all selected NEs. Click on Global
Remote Inventory button to upload the remote inventory.
95
RESTRICTED
3) The GRI Status column will display Completed when the action is successful. If the GRI
status is other than Completed, check NE supervision state and reachability.
4) Click on Apply to display the remote inventory.
96
RESTRICTED
5) If needed, the Remote Inventory list can be exported in a .CSV file. Click on the Export data
icon, select a destination folder, enter a file name and click on Save.
97
RESTRICTED
Maintenance & Troubleshooting
5.1
Alarm Surveillance
The 1350OMS alarm management functionality is provided by the Fault Management (FM)
application. The FM GUI displays alarms and network events as correlated by the various
1350OMS components.
FM functionality supports navigation from network correlated alarms in the FM system into the
raising network level component and assesses the elementary or server layer network layer alarms
that have been correlated.
For more information regarding Fault Management, please refer to 1350 OMS Service Assurance
Guide.
5.1.1 Current Alarms
When an alarm is raised by a faulty resource, it is received by Fault Management and the basic
information is immediately available to the user.
The alarm is cleared by the emitting resource as soon as the problem is no longer present at the
resource level. As soon as the alarm is acknowledged by the user, it is no longer considered a
current alarm. The alarm is removed from the current alarm list and is archived into the historical
alarm list.
5.1.1.1 Show NE alarms
Follow the steps below to view the current alarms of a desired NE.
1) Highlight the desired NE from the EML NE list, right click and select ShowNE Alarms.
2) The Fault Management application will be launched and the current NE alarms will be displayed.
98
RESTRICTED
5.1.1.2 Show EML alarm list
In order to see all the current alarms present at EML layer, launch the Fault Management
application (if nor already open) from the Web Portal:
Select Alarms folder under Operation tree and double click (or right click and select Start) on the
relevant EML Alarms icon.
If the Fault Management application is already open but showing alarms for particular NE (as per
step 5.1.1.1), click on MAIN ALARM LIST on the left panel to show alarms on the entire EML
instance.
5.1.1.3 Navigate from EML alarms to NE view

Follow the steps below to navigate from the alarms list to the equipment view of the alarmed NE.
1) Right click on the desired alarm and select External ApplicationsRelated_EmlUsm.
2) Equipment view of alarmed NE will be displayed.

99
RESTRICTED
5.1.1.4 Alarm correlation on NPR

1) Right click on the alarmed physical object (physical connection in the example) and select
SearchPhysicalActive Alarms, or click on the Active Alarms icon.
2) The active alarm at NPR level will be displayed.
3) To find the Elementary Alarm (correlated EML alarm), right click on the alarmed physical
connection and select SearchPhysicalElementary Alarms or click on the Elementary Alarms
icon.
100
RESTRICTED
4) Click on the + sign next to Probable cause to expand the tree and display the elementary
alarm/s.
5.1.1.5 Show physical object alarms

Follow the steps below to navigate from the alarmed object (physical connection ion the example)
to the NPR alarm list.
1) From the Physical Connections list right click on the alarmed physical connection and select
Search PhysicalNPR AS Current Alarms, or click on the NPR AS Current Alarms icon.
2) The Fault Management application will be launched and the current physical connection alarms
will be displayed.
5.1.1.6 Show NPR alarm list

In order to see all the current alarms present at NPR layer, launch the Fault Management application
(if nor already open) from the Web Portal:
101
RESTRICTED
NPR Alarms icon.
If the Fault Management application is already open but showing alarms for a particular physical
connection (as per step 5.1.2.2), click on MAIN ALARM LIST on the left panel to show alarms on
entire NPR layer.
5.1.1.7 Navigate from NPR alarms to Physical view

Follow the steps below to navigate from the alarms list to the physical view.
1) Right click on the desired alarm and select External ApplicationsFault_Localization.
2) Physical view of the alarmed object will be displayed.
102
RESTRICTED
5.1.1.8 Alarm correlation on OTN

1) Right click on the alarmed OTN object (DSR in the example) and select SearchAlarms.
2) The active OTN alarms will be displayed. Click on the + sign to expand the tree and view the
Elementary Alarms.
5.1.1.9 Show WDM alarm list

In order to see all the current alarms present at WDM layer, launch the Fault Management
application from the Web Portal:
WDM Alarms icon.
103
RESTRICTED
The alarms list window will display all alarms in WDM later:
5.1.1.10
Navigate from WDM alarms to OTN view
Follow the steps below to navigate from the alarms list to the OTN view.
1) Right click on the desired alarm and select External ApplicationsFault_Localization.
2) OTN view of the alarmed object will be displayed.

104
RESTRICTED
5.1.2 Historical Alarms

Once alarms are no longer considered as current, they are archived in the historical alarm section of
the FM application, where they can be reviewed.
Follow the steps below to access the historical alarms archive.
1) Launch the Fault Management application of the desired application (e.g. WDM).
2) From the main menu select WindowFM Historical.
3) The historical alarms GUI will open. From the main menu select ArchiveRetrieve from public
archiveWDM_1_11_H.
4) A filter window will pop up. Apply a filter, if needed, and click on OK.
105
RESTRICTED
5) Once the retrieve process is finished (this may take a few minutes, depending on the number of
alarms stored), the archived alarms will be displayed.
5.2
User Activity Log
User Activity Log management collects actions and command logs records from NEs and also from
the OMS applications (EML, NPR, OTN). 1350OMS processes these logs every 6 hours; therefore
the displayed information is not real time.
Follow the steps below to view the user activity log.
From the main menu select SearchUser Activity LogAll Records
Note: only admin users have access to All Records, for all other users select My Records
The activity records will be shown in the list. The list can be filtered using the filter icon and can
be sorted by clicking on the desired column.
The list can be exported by clicking on the Export Data icon

106
RESTRICTED
5.3
System Monitor
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 such as start, stop, and
various control functions for a selected item, including HA management and trace files viewing.
The System Monitor GUI is accessed from the web portal: select System folder under
Administration tree and double click (or right click and select Start) on System Monitor (Global
Instance-11):
The System Monitor GUI displays the Process Monitoring and Control window:
107
RESTRICTED
5.3.1 View Application Information
This feature enables the administrator to view static information such as load averages, CPU states,
memory allocations, and file systems for the selected item. The Info area is updated every 8
seconds. Click on the desired application (e.g. npr) and the information will be displayed in the
bottom panel. This action can also be performed by clicking on the View Info icon or selecting
ViewInfo from the main menu.
Note: by default the Disk/CPU usage will turn yellow (Warning) when it reaches 80% and red
(Critical) when it reaches 90%. These values can be changed from ConfigurationSet Threshold,
but the changes will only affect the current PMC view. Once the PMC window is closed, the values
will return to default.
5.3.2 Austostart Management

The automatic start of all processes in the selected application will occur when the AutoStart Enable
is active and the PMC server is restarted, for example, after a system reboot.
If AutoStart Disable is set, the administrator has to manually start individual processes after a PMC
server restart (or system reboot).
Complete the following steps to enable/disable AustoStart:
1) Highlight the desired application (e.g. NPR) and from the main menu select
ActionsControlAutoStart Enable.
108
RESTRICTED
2) Click on Yes to confirm the operation:
3) Highlight the desired application icon, and the bottom pane of the Process Monitoring and
Control window will display whether Auto Start is ON or OFF.
5.3.3 Control Management

The Control function continuously verifies the status of all processes and can be used to re-start a
crashed process. When a process crashes, the Control function attempts for two consecutive tries to
restart it. After two consecutive retries, the process can then be restarted manually.
Complete the following steps to activate/deactivate control on a desired application:
109
RESTRICTED
1) Highlight the desired application (e.g. NPR) and from the main menu select
ActionsControlActivate.
3) In the PMC tree structure, the Control icon (the eye) will be displayed next to the application
instance. Also, the bottom pane of the Process Monitoring and Control window will display
whether Control is ON or OFF.
5.3.4
Start/Stop Processes
Administrators can start/stop individual processes, group of processes and whole applications via
the PMC.
110
RESTRICTED
1) In the PMC tree structure, highlight the item that you want to start/stop and do one of the
following (in the example will stop LogParseMgr process)
ActionsStopSelected Item.
Click on the Stop Selected Item icon
Right click and select Stop.
Note: If the Control state is ON, the tool warns you that Control is activated for the selected group
or agent. In addition, if you are starting a Group of items (but not a whole application), the tool
prompts you to:
Confirm Start Group/Agent?
If you are starting a Group of items, and a whole application is included between the items (e.g.
NPR), the tool prompts you to
Confirm Start Product NPR_1?
3) The application icons will turn light blue to indicate a status change, and once the process is
stopped, the process icon will turn red, unless Control is activated, in which case the process will
be automatically restarted.
111
RESTRICTED
5.3.5
Trace Files Viewing
This feature enables the administrator to view the details for the Selected Agent Trace. When a
trace file is not available, the tool displays a pop-up window to inform the administrator.
1) In the PMC tree structure, click the particular Agent Item or process for which you want to view
agent trace information and select ViewSelected Agent Trace (or right click on the process and
select View Agent Trace)
2) A pop-up window will display a list of available agent trace files. If the selected Agent item or
process does not have any available trace information, the following message will be displayed:
No Trace available for this item
3) Click the particular agent trace file for which you want to view information and click OK.
4) Use the scroll bars to view all the lines in the file.
112
RESTRICTED
5.4
High Availability (HA) Management
The 1350OMS HA feature is employed to protect the 1350OMS applications (EML, NPR and
OTN) in a Geographical Redundancy Configuration, which relies on Data Replication to manage
data.
Data Replication Configuration is a mechanism to ensure that data and/or applications are available
on the standby server when the active one became out of order in its HW, SW or both components.
The 1350OMS HA NMS system is divided into two sites or centers:
The Network operation Center (NOC) contains the main NMS instances (Mascot).
The Disaster Recovery Center (DRC) contains the spare NMS instances (Blacktown).
For more information regarding HA, please refer to 1350 OMS HA Guide.
5.4.1
Start HA
When starting HA on all applications from the PMC GUI, it is recommended to follow the
sequence:
1) Start HA on the Stand By instance in the following order: EMLNPRWDM.
2) Start HA on the Active instance in the following order: EMLNPRWDM.
3) Start HA on the Presentation GUI instances in the following order: EMLNPRWDM.
4) Start Data Replication (see section 5.4.2).
Follow the steps below to start HA for an application (e.g. EML).
1) Log onto the Presentation and individual VMs (Main and Spare) of the application where HA
will be started. In the example below HA will be started for EML.
2) In the Spare VM: Make sure that kernel services (Services) are running (green icon) and that the
application (EML) is stopped (blue icon).
3) In the Main VM: Make sure that kernel services (Services) are running (green icon) and that the
application (EML) is also running (green icon).
4) In the Spare VM: click on the application icon (EML) and from the main menu select
ActionsStart HA.
113
RESTRICTED
5) In the pop-up window, click on Yes to confirm the operation.
6) The PMC window will reload after a few minutes and the HA view will appear under the
application icon (EML). The HA application status will change to Stand-by on the Spare VM and
Mute on the Main VM. The data replication status will be Replication-Off. Also, a triangle with
an exclamation mark will appear next to the application icon (only in the Stand by instance).
7) Repeat steps 4 and 5 in the Main VM and then in the Presentation VM.
8) The HA application status will change to ToActive in the Main VM and data replication status
will change to Replication-Off on both Main and Spare VMs.
9) The PMC window will reload after a few minutes and the HA application status will be Active on
the main VM and Stand-by in the Spare VM.
114
RESTRICTED
5.4.2
Start Data Replication
Follow the steps below to start data replication.

1) Click on the Replication-Off icon of the desired application (e.g. EML) and from the main menu
select ActionsData Replication Manager.
2) In the Data Replication Manager window, tick the boxes of the desired Non Critical Data to be
replicated (if any), then, in the Global Data Replication area, select the Off icon and click on the
Start Global Replication icon.
115
RESTRICTED
4) A window will pop up showing the progress of the operation.
5) The Data Replication icon will change status to Replication-Starting.
6) A pop-up window will confirm data replication started successfully. Click OK to close the
window.
7) Close the Data Replication Manager window: File Close.
8) The Data Replication icon will change status to Replication-On.
116
RESTRICTED
5.4.3
Stop Data Replication
Follow the steps below to start data replication.

1) Click on the Replication-ON icon of the desired application (e.g. EML) and from the main menu
select ActionsData Replication Manager.
2) In the Data Replication Manager window, select the On icon in the Global Data Replication
area, and click on the Stop Global Replication icon.
4) A window will pop up showing the progress of the operation.
5) The Data Replication icon will change status to Replication-Stopping.
117
RESTRICTED
6) A pop-up window will confirm data replication stopped successfully. Click OK to close the
window.
7) Close the Data Replication Manager window: File Close.
8) The Data Replication icon will change status to Replication-Off.
5.4.4
Global Switchover
1350OMS HA in release 11only supports Global Switchover, which means, all applications (EML,
NPR and OTN) will switch at the same time from Main to Spare or vice versa.
The user can execute the following switchover actions manually from the PMC GUI:
Switchover from Active status to Standby status: the NMS instance in Active status is forced to
switch to Standby status and the NMS instance in Standby status switches to Active status
automatically.
Switchover from Standby status to Active status: the NMS instance in Standby status is forced to
switch to Active status and the NMS instance in Active status switches to Standby status
automatically.
It is recommended that switchover is performed from the presentation GUI.
In the example below, the Global Switchover is performed from Main (NOC) to Spare (DRC)
1) Click the HA Active icon and from the main menu select ActionsGlobal Switchover to DRC.
118
RESTRICTED
3) Three windows will pop up showing the progress of the operation on EML, NPR and WDM
applications.
4) NOC HA status on all three applications (EML, NPR and WDM) will change to To Stand-by.
5) Once the NOC HA status becomes Sand-by, the DRC HA status will change to To Active.
119
RESTRICTED
6) PMC window will reload a few times to reflect the new HA status and warning windows will
pop up. Once switchover is complete the following messages will be displayed; click OK to
close the windows.
7) All three applications will be active on DRC.
5.4.5
Stop HA
When stopping HA on an application from the PMC GUI, it is recommended to follow the
sequence:
1) Stop Data Replication.
2) Stop HA on the Presentation GUI instance.
3) Stop HA on the Active instance.
4) Stop HA on the Stand by instance.
Follow the steps below to stop HA for an application (e.g. EML).
1) Log onto the presentation VM and individual VMs (Main and Spare) of the application where
HA will be stopped. In the example below HA will be stopped for EML.
2) Stop Data Replication on the application where HA will be stopped (see section 5.4.3)
3) In the Presentation VM: click on the application icon (EML) and from the main menu select
ActionsStop HA.
120
RESTRICTED
5) The PMC window will refresh after a few minutes and the HA application status will be Mute on
Main and Spare VMs. Also, the data replication status will be Replication-Undef.
6) Repeat steps 3 to 5 on the Main and Spare VMs.

7) Close and re-open the PMC windows. The HA view will no longer be displayed under the
application icon (EML).
Presentation/Main:
Spare:
121
RESTRICTED
5.5
Loopbacks
From the Routing Display, the loopback options that are available to users, for both line and client
ports, are the following:
Terminal Loopback: for a Terminal Loopback initiated on an OTUk trail or a DSR path, the
loopback indicator on the left and right ends of the trail/path shows the loopback arrow pointing
towards the NE (towards the connection).
Facility Loopback: for a Facility Loopback initiated on an OTUk trail or a DSR path, the
loopback indicator on the left and right ends of the trail/path shows the loopback arrow pointing
away from the NE (away from the connection).
5.5.1
Line port loopbacks
Warning: Be aware that a loopback on the line side of the transponder will interrupt traffic on all
client ports of the transponder.
1) Open a routing display of the desired path.
2) Right click on the Line port and select the desired loopback type (Terminal or Facility):
ActionsTerminal Loopback.
3) A pop-up window will remind you about traffic interruption due to the loopback. Click on Yes to
confirm the operation (All client ports traffic will be interrupted).
4) The loopback icon will appear on the affected line port:
122
RESTRICTED
5) You can check the affected services: right click on the node icon and select SearchLoopback
List.
6) The list will show all connections/services affected by the loopback.
7) To remove the loopback right click on the line port and select:
ActionsSynchronize loopback status.
123
RESTRICTED
ActionsRelease.
8) The loopback icon should disappear from the routing display:
124
RESTRICTED
5.5.2 Client port loopbacks
Warning: Be aware that a loopback on the client side of the transponder will interrupt traffic on the
selected client port of the transponder.
1) Open a routing display of the desired path.
2) Right click on the Client port and select the desired loopback type (Terminal or Facility):
ActionsFacility Loopback.
3) A pop-up window will remind you about traffic interruption due to the loopback. Click on Yes to
confirm the operation.
4) The loopback icon will appear on the affected client port:
125
RESTRICTED
5) You can check the affected services: right click on the node icon and select SearchLoopback
List.
6) The list will show all connections/services affected by the loopback.
7) To remove the loopback right click on the client port and select:
ActionsSynchronize loopback status.
126
RESTRICTED
ActionsRelease.
8) The loopback icon should disappear from the routing display:
5.5.3 Y-cable protection ports loopbacks

TBA
127
RESTRICTED
5.6
Optical Power Monitoring
The optical power display feature allows the user to monitor the optical power in two different
approaches:
Optical power on Trail: allows the operator to trace the power of a single wavelength from end to
end.
Optical power on Physical Connection: shows the power of all wavelengths at a single end of a
physical connection.
5.6.1 Optical power on Trail
1) Right click on the desired trail (from the trails list or from the trail icon on the routing display)
and select the direction to check the optical power levels A->Z or Z->A: SearchOptical
Power A->Z
2) The top left panel will show the end-to-end channel power. Position the mouse pointer on a
power bar to view the current value details.
128
RESTRICTED
3) The bottom-left panel shows the total power end-to-end.
4) The right panel shows the details of the selected connection. Click on the Refresh button to
update current values.
129
RESTRICTED
5.6.2 Optical power on Physical connection
1) From the Physical Connections list, right click on the desired physical connection and select the
direction and the port to check the optical power levels.
2) The left panel will display the selected direction and port power level. Hover the mouse pointer
over the power bar to view current values.
3) The right panel shows the details of the selected connection. Click on the Refresh button to
update current values.
130
RESTRICTED
5.7
Inconsistency Check
1350OMS provides tools to identify and fix discrepancies between NE and OTN databases. These
discrepancies are defined as:
Inconsistent Connections.
Uncorrelated Cross-connections.
5.7.1
Inconsistent Connections
An Inconsistent Connection is a Commissioned or Implemented connection on 1350OMS that is

inconsistent at NE level (not present on the NE).
Inconsistent connections are divided in two types:
Inconsistent Paths.
Inconsistent Trails.
Inconsistent paths and inconsistent trails can occur during one of the following events:
SNC Mismatches.
Parameter Mismatches.
Download Disable Mismatches.
1350OMS enables users to acknowledge or, in some cases, restore inconsistent connections.
131
RESTRICTED
5.7.1.1 SNC Mismatches
An SNC Mismatch is a type of inconsistent connection in which a cross connection associated with
a Commissioned or Implemented connection that is not provisioned in the NE (i.e. a connection
present in the NMS but not present in the NE).
The user can fix SNC mismatches by either one of the below actions:
Reclassify: SNC Mismatches are automatically reclassified in 1350OMS OTN when the
connection is resolved at NE level. The 1350OMS OTN is notified of the newly created
cross-connection and, if the end ports and shape match those of the inconsistent connection,
then the inconsistent connection is automatically removed from the SNC Mismatches list.
Restore: SNC Mismatches can be restored by creating the missing cross-connections to
match the NMS database. The 1350OMS OTN determines all the cross-connections that
need to be created to restore an inconsistent connection.
Note: when performing a restore, the 1350OMS OTN does not attempt to create OS
connections.
Restoring inconsistent connections is not supported for the following:
If any port in any cross connection to be restored is being used in another existing cross
connection. Exception: if all existing cross connections are uncorrelated and use the
same ports as the inconsistent cross connection, the Restore function is allowed.
Follow the steps below to find and restore inconsistent SNC Mismatches:
1) From the main menu select SearchOTN Inconsistent ConnectionsTrail SNC Mismatches
(or Path SNC Mismatches)
2) The Trail SNC Mismatches window (or Path SNC Mismatches window) will display the
inconsistencies found, if any.
132
RESTRICTED
3) To restore the missing cross-connections, right click on the inconsistent connection and select
ActionsRestore.
5) Once the connection has been successfully restored, a message will appear on the bottom-left
corner:
6) Refresh the Trail SNC Mismatches window (or Path SNC Mismatches window) and the
inconsistent connection should be gone.
5.7.1.2 Parameter Mismatches
Parameter mismatches are those inconsistent connections in which the connection parameters
associated with a Commissioned or Implemented connection are different from the parameters that
are provisioned on the NE.
The only way of fixing a parameter mismatch is by resolving the inconsistency at NE level, in
which case the 1350OMS OTN will be notified of the newly modified parameters and the
inconsistent connection will be automatically removed from the Parameter Mismatch list.
The restoration of these inconsistent connections from 1350OMS OTN is not supported.
Follow the steps below to find and fix inconsistent Parameter Mismatches:
1) From the main menu select SearchOTN Inconsistent ConnectionsPath Parameters
Mismatches (or Trail Parameters Mismatches).
133
RESTRICTED
2) The Path Parameters Mismatches window (or Trail Parameters Mismatches window) will
display the inconsistencies found, if any.
3) Right click on the inconsistent connection and select ActionsConnections Details.
4) In the Connection Details window, click on the Transmission tab and identify the parameter with
mismatching values between Parameter Value and Network Value columns.
5) Click on Cancel to close the window.

134
RESTRICTED
6) Open the equipment view of the NE where the mismatch was identified and change the valu e
to match the Parameter Value.
7) Refresh the Path Parameters Mismatches window (or Trail Parameters Mismatches window)
and the inconsistent connection should be gone.
5.7.1.3 Download Disable Mismatches
Download disable mismatches are those Commissioned or Implemented inconsistent connections
that have commands that have not been implemented because one or more NE in the connection has
been set to download disable.
Inconsistent connections that have a download disable mismatch are automatically reclassified in
the1350OMS OTN in the following situations:
If a download disable NE becomes download enabled, and all un-implemented
commands for a connection are no longer disabled, the inconsistent connection is
automatically removed from the Download Disable list.
If any command sent to the NE, as a result of enabling the download, fails, the connection is
added to the Inconsistent Connection SNC Mismatches list and/or the Inconsistent
Connection Parameter Mismatches list.
The viewing of these inconsistent connections is supported. The acknowledgement and restoration
of these inconsistent connections is not supported.
Follow the steps below to find inconsistent Download Disable Mismatches:
1) From the main menu select SearchOTN Inconsistent ConnectionsPath Download
Disabled Mismatches (or Trail Download Disabled Mismatches).
135
RESTRICTED
2) The Path Download Disabled Mismatches window (or Trail Download Disabled Mismatches
window) will display the inconsistencies found, if any.
3) Right click on the inconsistent connection and select SearchRouting Display.
4) In the Routing Display window, identify the NE/NEs that is/are in Download Disabled and
enable download.
5) Allow a few minutes for the configuration to be downloaded to the NE/NEs and refresh the Path
Download Mismatch window (or Trail Download Mismatch window) and the inconsistent
connection should be gone.
5.7.2
Uncorrelated Cross-connections
An Uncorrelated cross-connection is a cross connection that is not associated with a connection that
is provisioned in the1350OMS OTN. Uncorrelated cross-connections exist on the NE and are
created outside the1350 OMS OTN, for example, by using the Craft Terminal or EML Equipment
view.
136
RESTRICTED
The user can fix uncorrelated cross-connections by either one of the below actions:
Delete uncorrelated cross-connection: If the uncorrelated cross-connection is no longer
required, the user can remove it from the NE.
Reclassify uncorrelated cross-connection: If an uncorrelated cross-connection becomes a
part of a connection that is either Implemented/Completed or Commissioned, the
management system automatically reclassifies the uncorrelated cross-connection as
correlated.
Follow the steps below to find and fix uncorrelated cross-connections:
From the main menu select SearchOTN Uncorrelated Cross Connections.
The Uncorrelated Cross Connections window will display the uncorrelated cross-connections
found, if any.
Example 1: client port was set In Service from EML equipment view, but there is no path
associated to it in the 1350OMS OTN and the client port is no longer in use.
1) Identify the unwanted cross-connection from the Uncorrelated Cross Connections list.
2) Open the equipment view of the relevant NE, navigate to the port involved in the unwanted
cross-connection and set it Out of Service and Submit.
137
RESTRICTED
3) Click on the Delete tab, tick the Delete this Port box and Submit. A warning message will
pop up. Click on OK to confirm the operation.
4) Refresh the Uncorrelated Cross Connections list and the unwanted cross-connection should
disappear.
Example 2: a DSR path was deleted from 1350OMS while one NE (A2) was in Download
Disabled, therefore the client port is still In Service at NE level. In this case we will recreate the DSR path from 1350OMS so the uncorrelated cross-connection will be reclassified
as correlated.
1) Identify the uncorrelated cross-connection from the Uncorrelated Cross Connections list.
2) Ensure that the NE is in download enabled state and re-create a DSR path using the
identified ports.
3) Once the path is successfully created, Refresh the Uncorrelated Cross Connections list and
the uncorrelated cross-connection should disappear.
138
RESTRICTED
5.8
Protection Switching
TBA
5.8.1
OSNCP with Y-cable
TBA
5.8.2
OSNCP with OPS
TBA
5.9
EOS Simulator
The External Operating System (EOS) Simulator is used for simulating and monitoring the
northbound interface for alarm and PM data being sent from the EML IOO Interface towards the
EOS (e.g. TeMIP and NPRS).
Unlike 1350OMS release 9.4.10, in release 11 this feature is no longer integrated in the EML
application server (virtual machine), but comes as an external application to be installed in the
users PC. In order to run this EOS application the user PC needs to be able to access the EML
servers via the relevant telnet ports: Alarms ASCIIport 25125, PM dataport 25129,
PMFTP25130.
5.9.1
EOS installation and configuration
The EOS application software is available in IME server:

Z:\tximedocs\Alcatel\NGTT+\EOS
Follow the steps below to install and configure EOS in your PC:
1) Follow step 3.4.3 to add your PC as a new EOS to receive alarms from EML server (use IP
address, do not use alias or PC name)
2) Copy and unzip the file EOSSIM_R1.1.0.B2RP1.zip to your PC.
3) Go to the folder config and edit the file eos.cfg (using WordPad or notepad)
4) Change the value of ASCII_HOSTNAME to the IP address of the desired EML server:
5) Change the value of SNMPAGENT to the IP address of the desired EML server :
6) Save the file and close it.

139
RESTRICTED
5.9.2
EOS usage
1) Execute the file startEOS under bin folder.

2) In the pop-up window select the ASCII ALM tab to monitor the alarm interface.
3) Click on TCP/IP Connect, then click on Connect Request and a pop-up window will ask for a
password. Enter alcatel or whatever password was defined in step 1 of section 5.9.1 and click
OK.
4) A connection confirmation message will appear in the Received Message area.

140
RESTRICTED
5) Once connected, use the buttons in the middle area to list the desired alarms. Below is an
example of retrieving current alarms.
Click on List Current Alarms and a window will pop up with filtering options. Enter filter
criteria (if needed) and click OK.
6) All alarms matching the filter criteria will be displayed in the Received Message area and the
alarm count will be shown in the counters area.
141
RESTRICTED
7) The Received Message area can be exported to a log file by clicking on Start Logging BEFORE
retrieving the alarms. Once the alarms have been retrieved, click on Stop Logging. The log file
alm_data.log will be located in the log folder of the EOS application.
8) To quit the EOS Simulator, click Disconnect Request, then click TCP/IP Disconnect, and then
click on the Exit button.
142
RESTRICTED
Miscellaneous
6.1
Transponder Removal
In order to delete a transponder board from the NE, all paths and trails starting/ending on the
transponder must be fully removed from 1350OMS.
Follow the steps below to remove transponder configuration from 1350OMS:
1) Perform a SearchOTNTrails OTUk Trails (OTN) and identify the OTUk trail
starting/ending on the desired NE and transponder.
2) Right click on the trail and select ActionsRemove Connection and Clients.
Warning: this action will remove the OTUk trail and all ODUk trails and Paths riding inside the
trail. Also, the client ports will be deleted and the line ports will be set to Out of Service on the
NE.
4) Right click on the NE from the map or from the Nodes list and select SearchOTN Internal
Connectivities (OTN).
143
RESTRICTED
5) Identify the Internal connection starting/ending on the desired transponder, right click and select
ActionsRemove.
Note: this action will delete the Physical Topology on the NE. The SFD44 and CWR8-88 CLS
ports will be automatically put in out of service and the CLS port will be also deleted during
this step.
6.2
Transponder Addition
Transponder addition activities are performed from CT during commissioning; the only action
required from 1350OMS is a full synchronization of the NE once configuration is done at NE level.
1) Follow 1830PSS job aid for Transponder Addition and Physical Topology Creation.
2) Perform a full synchronisation: right click on the NE from the map or from the nodes list and
select ActionsPhysicalSynchronizeFull.
144
RESTRICTED
Document Control
Authorisation
Approved:
Simon P Love
Transmission Access Engineering, Fixed Core Engineering, Networks
Authorised:
Andrew Clark
Transmission IME Fixed Core Engineering, Networks.
Author:
Julio Gauvry
Transmission IME, Fixed Core Engineering, Networks
Amendment List
Version
Amendment
Version 1 Document compilation.
145
Section
When
Who
All
6/09/2013
Julio Gauvry
RESTRICTED
Appendix A Glossary
1350OMS
Alcatel-Lucent Network Management System
AS
Alarm Surveillance
CIT
Craft Interface Terminal
CLI
Command Line Interface
CT
Craft Terminal
CWR8-88
Colourless Wavelength Route
DCN
Data Communication Network
DRC
Disaster Recovery Centre
DSR
Digital Service Rate
EML
Element Management Layer
EO
Engineering Order
FTS
File Transfer Scheduler
GENOS
Generic OS-OS Interfaces
GUI
Graphical User Interface
HA
High Availability
ILA
In-Line Amplifier
IOO
OS-OS Interface
MIB
Management Information Base
NE
Network Element
NML
Network Management Layer
NMS
Network Management System
NOC
Network Operations Centre
NPR
Network Physical Resources
NTP
Network Time Protocol
ODU
Optical Demultiplexer Unit; Optical channel Data Unit
OI
Open Interfaces
OMS
Optical Multiplex Section; Optical management System
OS
Operation System; Optical Section
OTN
Optical Transport Network
OTS
Optical Transmission Section
OTU
Optical channel Transport Unit
PM
Performance Monitoring
PMC
Process Monitoring & Control

146
RESTRICTED
RU
Rack Unit
SFD44
Static Filter DWDM 44 channels even
SFD44B
Static Filter DWDM 44 channels odd
SWP
Software Packages
TCA
Threshold Crossing Alert
TID
Target Identifier
TP
Termination Point or Terminal Point
URL
Uniform Resource Locator
USM
User Services Manager
VM
Virtual Machine
WDM
Wavelength Division Multiplexing
WR2-88
Wavelength Router
WR8-88A
Wavelength Router
WT
Wavelength Tracker
147

Alcatel-Lucent 1350OMS Release - 11JobAid

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alcatel-Lucent 1350OMS Release - 11JobAid

Uploaded by

Copyright:

Available Formats

RESTRICTED

Alcatel-Lucent 1350OMS Release 11

System Login: Web Desktop ................................................................................................................ 8

Operation & Provisioning .................................................................................................................. 11

Scheduled Software Download ..................................................................................... 63

Maintenance & Troubleshooting ....................................................................................................... 98

Miscellaneous ................................................................................................................................... 143

Document Control .................................................................................................................................. 145

Glossary .......................................................................................................................... 146

The following documents are available on IME server:

Alcatel-Lucent 1830PSS Long Haul DWDM Job Aid.

NGTT+ ALU OMS NPN.

1350 OMS Administration Guide: Common Tools and Processes.

1350 OMS Administration Guide: Common GUI Functions.

1350 OMS Getting Started Guide.

1350 OMS EML Guide.

1350 OMS OI Guide.

1350 OMS OTN Guide.

1350 OMS HA Guide.

1350 OMS Service Assurance Guide.

1.4.1 Modular Architecture

1.4.4 Network Architecture

Blacktown 1 GUI1, NPR, OTN

1.4.5 Communications and High Availability (HA)

System Login: Web Desktop

Network Management (MS-GUI)

6) The Network Management window will open as shown below:

Operation & Provisioning

From the main menu, select Actions EML Create NE.

Navigate to Equipment Alarm list:

Navigate to Equipment view:

Switch to the NTP IP tab to check the configured values.

Click on Cancel to close the window.

Follow the steps below to perform single NE MIB backup.

2) A pop-up window will confirm the operation. Click OK to close it.

Follow the steps below to download software to one or multiple NEs.

5) A pop-up window will confirm the operation. Click OK to close it.

External Network creation

External Physical Links Discovery

Physical Connection creation

5) The newly created physical connection will be displayed in a list.

Internal OS connections creation

6) In the Transmission window leave parameters as default and click on Next.

The internal connections list will be displayed.

End-to-End service provisioning

End to end service provisioning includes two basic tasks:

Create OTU4 trail.

ODU4 trail will be automatically created.

Create 100GbE DSR path.

2) G.709 (OTU2) (using 100G Transponder)

Create OTU4 trail.

ODU4 trail will be automatically created.

Create ODU2 path.

Create OTU4 trail.

ODU4 trail will be automatically created.

Create 10GbE/SDH/FC DSR path.

OTU Trail creation

Follow the steps below if a new OTUk trail needs to be created:

14) Leave Wave Key Type in Automatic and click on Next.

OTU Trail deletion

ODU Trail creation

7) Leave Network Protection Type as None and click on Next.

Performance Monitoring area: leave as default.