8DG42094BAAA - V1 - Alcatel-Lucent 1350 OMS EML 9.1.1 User Guide (Maint-2)

Title page
1350 OMS EML 9.1.1

User Guide
8DG42094BAAA
ISSUE 1
MARCH 2010
Legal notice
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2010 Alcatel-Lucent. All rights reserved.
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to
change.
Warranty
Alcatel-Lucent provides a limited warranty for this product. For more information, consult your local Alcatel-Lucent customer support team.
Ordering information
The ordering number for this document is 8DG42094BAAA. To order 1350 OMS information products, contact your local Alcatel-Lucent customer support
team.
Technical support
For technical support, contact your local customer service support team. You can reach them through the Web at the Alcatel-Lucent Customer Support web
site (http://www. alcatel-lucent.com/support) or the customer support telephone number listed at the Alcatel-Lucent Contact Us web site (http://www.alcatel-
lucent.com/contact).
Information product support
For questions or concerns about this or any other Alcatel-Lucent information product, please contact us at one of the following numbers: (888) 727 3615 (for
the continental United States); +1 (630) 713 5000 (for all countries).
Contents
About this document

Purpose ......................................................................................................................................................................................... xxv
xxv
Reason for revision ................................................................................................................................................................... xxv

xxv
Safety information .................................................................................................................................................................... xxv

xxv
Intended audience .................................................................................................................................................................... xxvi

xxvi
How to use this information product ................................................................................................................................ xxvi
Conventions used ................................................................................................................................................................... xxvii

xxvii
Related documentation .......................................................................................................................................................... xxix

xxix
How to order .............................................................................................................................................................................. xxxi

xxxi
How to comment ...................................................................................................................................................................... xxxi

xxxi
1 Product Overview
Overview ...................................................................................................................................................................................... 1-1

1-1
1350OMS and its applications
1350 OMS Overview ............................................................................................................................................................... 1-3

1-3
1350 OMS Modules for System Resiliency and Northbound Communication ................................................. 1-6
1-6
System Overview
System access from Desktop ................................................................................................................................................ 1-7

1-7
Functionality available from Web desktop .................................................................................................................... 1-11

1-11
Work Environment ................................................................................................................................................................. 1-12

1-12
View Description
Equipment View Description ............................................................................................................................................. 1-14

1-14
Equipment View
Open in Window command ................................................................................................................................................ 1-24

1-24
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 iii
March 2010
Contents
....................................................................................................................................................................................................................................
NE Equipment views ............................................................................................................................................................ 1-25
1-25
NE Alarms and NE Status
NE Alarms ................................................................................................................................................................................. 1-29

1-29
NE Status ................................................................................................................................................................................... 1-31

1-31
On Line Documentation
Overview ................................................................................................................................................................................... 1-34

1-34
Help on MS-GUI Framework ............................................................................................................................................ 1-35

1-35
Help Activation ....................................................................................................................................................................... 1-36

1-36
Help on context ....................................................................................................................................................................... 1-37

1-37
Glossary ..................................................................................................................................................................................... 1-38

1-38
2 Alarm Management
Overview ...................................................................................................................................................................................... 2-1

2-1
AS Overview
Alarm Information .................................................................................................................................................................... 2-3

2-3
Alarm Surveillance Functionalities .................................................................................................................................... 2-4

2-4
Current Alarm Management ................................................................................................................................................. 2-5

2-5
Historical Alarm Management ............................................................................................................................................. 2-6

2-6
An Iterative Approach for Alarm Description ................................................................................................................ 2-7

2-7
Alarm Management
Access AS .................................................................................................................................................................................... 2-8

2-8
Reserving/Unreserving Alarms ............................................................................................................................................ 2-9

2-9
Acknowledging Alarms ........................................................................................................................................................ 2-12

2-12
Manually Purging an Alarm ............................................................................................................................................... 2-14

2-14
Manually Clearing an Alarm .............................................................................................................................................. 2-15

2-15
Exporting and Printing (Output...) an Alarm ................................................................................................................ 2-16

2-16
....................................................................................................................................................................................................................................
iv 8DG42094BAAA Issue 1
March 2010
Contents
....................................................................................................................................................................................................................................
Navigations
Navigation to/from Alarm Surveillance ......................................................................................................................... 2-20

2-20
Alarm Debouncing
Function Description ............................................................................................................................................................. 2-25

2-25
Alarm Debouncing Management ...................................................................................................................................... 2-26

2-26
3 Event and Alarm Log Browser
Overview ...................................................................................................................................................................................... 3-1

3-1
ELB Application
Event Log Browser .................................................................................................................................................................. 3-2

3-2
ELB Graphical User Interface
Introduction ................................................................................................................................................................................. 3-5

3-5
Menu Bar ..................................................................................................................................................................................... 3-8

3-8
Tabbed Panes ........................................................................................................................................................................... 3-13

3-13
Filter Management
Filters for ELB Application ................................................................................................................................................ 3-19

3-19
4 1350 OMS EML Graphical User Interface
Overview ...................................................................................................................................................................................... 4-1

4-1
Introduction
1350 OMS EML GUI Features ............................................................................................................................................ 4-2

4-2
Workflow ..................................................................................................................................................................................... 4-4

4-4
Window Structure
Window and Menu for 1350 OMS EML ......................................................................................................................... 4-5

4-5
Filtering Area ........................................................................................................................................................................... 4-10

4-10
Error Management
Error Management in 1350 OMS EML ......................................................................................................................... 4-12

4-12
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 v
March 2010
Contents
....................................................................................................................................................................................................................................
5 EML Management
Overview ...................................................................................................................................................................................... 5-1

5-1
Action Menu
Menu Composition ................................................................................................................................................................... 5-2

5-2
Create Network Elements ...................................................................................................................................................... 5-4

5-4
Discover Gateway NE ............................................................................................................................................................. 5-7

5-7
Global EML Resynchronize ............................................................................................................................................... 5-10

5-10
Search Menu
NE Global Inventory ............................................................................................................................................................. 5-11

5-11
EML Domains ......................................................................................................................................................................... 5-13

5-13
EML Instances ......................................................................................................................................................................... 5-14

5-14
6 Network Element Management
Overview ...................................................................................................................................................................................... 6-1

6-1
Network Elements and Links
Management States .................................................................................................................................................................. 6-3

6-3
NE Time Configuration
Configuration ............................................................................................................................................................................. 6-6

6-6
Action Menu
Menu Composition ................................................................................................................................................................... 6-9

6-9
Create and Remove Network Elements ......................................................................................................................... 6-14

6-14
Network Element Resynchronize ..................................................................................................................................... 6-18

6-18
Managing the Supervision of an NE ............................................................................................................................... 6-19

6-19
Set Network Element Access Control Domain ............................................................................................................ 6-21

6-21
Managing the NE Time ........................................................................................................................................................ 6-23

6-23
Managing the NE MIB ......................................................................................................................................................... 6-25

6-25
Modifying the Access State of an NE ............................................................................................................................. 6-28

6-28
....................................................................................................................................................................................................................................
vi 8DG42094BAAA Issue 1
March 2010
Contents
....................................................................................................................................................................................................................................
NTP Configuration ................................................................................................................................................................. 6-30
6-30
Set Network Element Access Control Domain ............................................................................................................ 6-34

6-34
Create ISA board .................................................................................................................................................................... 6-36

6-36
Set OS Address ........................................................................................................................................................................ 6-38

6-38
Set NE Address ....................................................................................................................................................................... 6-41

6-41
Set 4G (Q3) NE Address ..................................................................................................................................................... 6-43

6-43
Uploading the Remote Inventory ..................................................................................................................................... 6-59

6-59
Global Remote Inventory .................................................................................................................................................... 6-61

6-61
Information about NEs ......................................................................................................................................................... 6-64

6-64
Current Status Consultation ................................................................................................................................................ 6-67

6-67
Ping NE ...................................................................................................................................................................................... 6-69

6-69
Search Menu
NE Global Inventory ............................................................................................................................................................. 6-71

6-71
EML Domains ......................................................................................................................................................................... 6-73

6-73
EML Instances ......................................................................................................................................................................... 6-74

6-74
Navigations
Navigations and Inventories ............................................................................................................................................... 6-76

6-76
Modification of NE or Link Characteristics
Changing an OS Address ..................................................................................................................................................... 6-78

6-78
7 TSS Network Element Management
Overview ...................................................................................................................................................................................... 7-1

7-1
Product overview
1850TSS Product Family ....................................................................................................................................................... 7-2

7-2
1850 TSS Management in 1350 OMS EML ................................................................................................................... 7-3

7-3
1350 OMS EML activation
Access to the 1350 OMS EML System ............................................................................................................................ 7-4

7-4
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 vii
March 2010
Contents
....................................................................................................................................................................................................................................
Preliminary Operations
Overview ...................................................................................................................................................................................... 7-5

7-5
New Account on Network Element .................................................................................................................................... 7-6

7-6
New Account on EML ............................................................................................................................................................ 7-9

7-9
User Profiles ............................................................................................................................................................................. 7-14

7-14
Overview ................................................................................................................................................................................... 7-15

7-15
1850 TSS Network Element Creation ............................................................................................................................. 7-16

7-16
1850 TSS Network Element Supervision ...................................................................................................................... 7-22

7-22
Navigations ............................................................................................................................................................................... 7-23

7-23
Ping NE ...................................................................................................................................................................................... 7-24

7-24
Alarm Management and Navigations
Alarm Management ............................................................................................................................................................... 7-25

7-25
Navigations ............................................................................................................................................................................... 7-26

7-26
8 Performance Monitoring
Overview ...................................................................................................................................................................................... 8-1

8-1
Performance Monitoring
Accessing Performance Monitoring ................................................................................................................................... 8-3

8-3
Performance Monitoring Reports
Create a Report .......................................................................................................................................................................... 8-5

8-5
Reporting Criteria ..................................................................................................................................................................... 8-9

8-9
Filters .......................................................................................................................................................................................... 8-12

8-12
Search ......................................................................................................................................................................................... 8-13

8-13
Report Destination ................................................................................................................................................................. 8-18

8-18
Report Options ........................................................................................................................................................................ 8-20

8-20
....................................................................................................................................................................................................................................
viii 8DG42094BAAA Issue 1
March 2010
Contents
....................................................................................................................................................................................................................................
9 Network Physical Resources Management
Overview ...................................................................................................................................................................................... 9-1

9-1
NPR Application
Network Physical Resources ................................................................................................................................................ 9-2

9-2
NPR Search Functions
EML Domains ............................................................................................................................................................................ 9-4

9-4
Nodes ............................................................................................................................................................................................. 9-7

9-7
Physical Connections ............................................................................................................................................................ 9-11

9-11
NPR Actions
Create Physical Connection ................................................................................................................................................ 9-14

9-14
Create Alarm Profile .............................................................................................................................................................. 9-17

9-17
Create External Network ..................................................................................................................................................... 9-20

9-20
Discover Physical Topology ............................................................................................................................................... 9-22

9-22
10 Procedures for EML Configuration
Overview ................................................................................................................................................................................... 10-1

10-1
Q3 based NE management
Data storage and recovery procedures ............................................................................................................................ 10-3

10-3
The backup of Q3 NE into 1350 OMS EML ............................................................................................................... 10-6

10-6
The on–board simulator of Q3 NE into 1350 OMS EML .................................................................................... 10-13

10-13
SDH behavior towards the MIB–less architecture .................................................................................................. 10-19

10-19
OMSN and ATM board management
Introduction ............................................................................................................................................................................ 10-21

10-21
OMSNs and ISA board: PNM customization ............................................................................................................ 10-22

10-22
ISA Board Creation ............................................................................................................................................................. 10-24

10-24
Set ISA Board Address ...................................................................................................................................................... 10-28

10-28
OMSN + ISA: Supervision .............................................................................................................................................. 10-31

10-31
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 ix
March 2010
Contents
....................................................................................................................................................................................................................................
Rename OMSN Network Element and all ISA boards .......................................................................................... 10-33
10-33
Error Recovery ...................................................................................................................................................................... 10-36

10-36
Procedures to handle Transmission Alarms
Introduction ............................................................................................................................................................................ 10-37

10-37
Why Transmission alarms are not shown at subrack view? ................................................................................. 10-38
10-38
How to identify transmission alarms starting from NE subrack view .............................................................. 10-40
10-40
Transmission alarms sub–list in AS component. ...................................................................................................... 10-44

10-44
Alarm Severity Assignment Profile for OMSN
Overview ................................................................................................................................................................................. 10-45

10-45
Introduction ............................................................................................................................................................................ 10-46

10-46
Customizing a new ASAP on NM–OS ........................................................................................................................ 10-47

10-47
Object Assignment Domain
How to define OAD ............................................................................................................................................................ 10-52

10-52
File Transfer Scheduler
Introduction ............................................................................................................................................................................ 10-63

10-63
Job Planning ........................................................................................................................................................................... 10-66

10-66
FT Scheduler Job Descriptor ........................................................................................................................................... 10-67

10-67
Create an FTS Job ................................................................................................................................................................ 10-68

10-68
File Transfer Scheduler Job Editor ................................................................................................................................ 10-71

10-71
FTS Job Status ...................................................................................................................................................................... 10-74

10-74
View Report ........................................................................................................................................................................... 10-76

10-76
Software Status ..................................................................................................................................................................... 10-78

10-78
DCN network example ...................................................................................................................................................... 10-86

10-86
11 Supervision System Configuration
Overview ................................................................................................................................................................................... 11-1

11-1
....................................................................................................................................................................................................................................
x 8DG42094BAAA Issue 1
March 2010
Contents
....................................................................................................................................................................................................................................
Supervision Area
Supervision Area Definition ............................................................................................................................................... 11-3

11-3
Supervision Area Configuration
Different Types of Configuration ...................................................................................................................................... 11-7

11-7
Configuration Example ...................................................................................................................................................... 11-11

11-11
12 Integrated SPLM Management
Overview ................................................................................................................................................................................... 12-1

12-1
Product overview
References ................................................................................................................................................................................. 12-2

12-2
Using SPLM functions from common MS-GUI
Access from MS-Gui ............................................................................................................................................................ 12-3

12-3
Search Functions ..................................................................................................................................................................... 12-4

12-4
Centralized Channel Margin .............................................................................................................................................. 12-8

12-8
APE Sequencer ..................................................................................................................................................................... 12-11

12-11
Power Reference Reset ...................................................................................................................................................... 12-18

12-18
APA Optimization ................................................................................................................................................................ 12-22

12-22
13 Integrated CPB
Overview ................................................................................................................................................................................... 13-1

13-1
CPB Overview ......................................................................................................................................................................... 13-3

13-3
Optical NEs Window ............................................................................................................................................................ 13-6

13-6
Optical Systems Window .................................................................................................................................................... 13-8

13-8
Show Loss Reports Window ............................................................................................................................................ 13-10

13-10
Discover NEs (using Plan) Window ............................................................................................................................. 13-11

13-11
Provisioning (using Plan) Window ................................................................................................................................ 13-14

13-14
Initial/Greenfield (using Plan) Window ....................................................................................................................... 13-18

13-18
Power Balancing (manual) Window ............................................................................................................................. 13-21

13-21
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xi
March 2010
Contents
....................................................................................................................................................................................................................................
Power Balancing (using Plan) Window ....................................................................................................................... 13-23
13-23
Create Loss Report Window ............................................................................................................................................ 13-25

13-25
Create Loss Report (using Plan) Window ................................................................................................................... 13-27

13-27
Access and View the CPB for Optical NEs ................................................................................................................ 13-29
13-29
Access and View the CPB for Optical Systems ........................................................................................................ 13-30
13-30
Discover NEs (using Plan) ............................................................................................................................................... 13-31

13-31
Provision NE Power Attributes (using Plan) ............................................................................................................. 13-33

13-33
Set Initial/Greenfield Power Levels (using Plan) ................................................................................................... 13-38

13-38
Create a Loss Report ........................................................................................................................................................... 13-41

13-41
Create a Loss Report (using Plan) ................................................................................................................................. 13-44

13-44
Power Balance to Rebalance Power Levels ............................................................................................................... 13-46

13-46
Power Balance (using Plan) to Re-optimize Power Levels .................................................................................. 13-49

13-49
View a Loss Report ............................................................................................................................................................. 13-52

13-52
14 IP over OSI Tunneling
Overview ................................................................................................................................................................................... 14-1

14-1
IP over OSI Tunneling Overview
IP over OSI Tunneling architecture ................................................................................................................................. 14-2

14-2
System Configuration for IP over OSI Tunnelling
Configure the Processes ....................................................................................................................................................... 14-5

14-5
Start Configured Process ..................................................................................................................................................... 14-9

14-9
IP over OSI Tunnelling Setup
Operations on OMSN NE ................................................................................................................................................. 14-12

14-12
Operations on 1350 OMS EML System ...................................................................................................................... 14-22

14-22
Start Supervision on ISA Board ...................................................................................................................................... 14-29

14-29
IP over OSI Tunnelling GUI Functions
Remove NE from Tunnel .................................................................................................................................................. 14-30

14-30
....................................................................................................................................................................................................................................
xii 8DG42094BAAA Issue 1
March 2010
Contents
....................................................................................................................................................................................................................................
Tunnel Remove ..................................................................................................................................................................... 14-31
14-31
15 Generic Functions
Overview ................................................................................................................................................................................... 15-1

15-1
NE Auto–Discovery
How to use this function ...................................................................................................................................................... 15-2

15-2
SWPA Software Package Administrator
SWPA Functionality .............................................................................................................................................................. 15-4

15-4
SWPA ......................................................................................................................................................................................... 15-5

15-5
Index
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xiii
March 2010
Contents
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xiv 8DG42094BAAA Issue 1
March 2010
List of tables
3-1 Alarm severity and colour .................................................................................................................................... 3-15
10-1 Default Assignment of Service Dependency and Severity on OMSN .............................................. 10-50
10-2 Possible customization Assignment of Service Dependency and Severity on OMSN ............... 10-50
10-3 Link load of level 1 with LAN load max=4 ................................................................................................ 10-88
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xv
March 2010
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xvi 8DG42094BAAA Issue 1
March 2010
List of figures
1-1 Web Desktop login .................................................................................................................................................... 1-8

1-8
1-2 Web Desktop portal .................................................................................................................................................. 1-9

1-9
1-3 The 1350 OMS EML workspace Front Panel. ............................................................................................. 1-12
1-4 Q3 NE view example. ........................................................................................................................................... 1-15
1-5 Example of a Q3 NE Board view. ..................................................................................................................... 1-20
1-6 Example of a detailed port view for Q3 NE. ................................................................................................. 1-22
1-7 Opening a view in a window .............................................................................................................................. 1-24
1-8 Example of a Board view for a Q3 NE. .......................................................................................................... 1-26
1-9 Selecting a specific port view of a Q3 NE Board View. ........................................................................... 1-27
1-10 Example of a Q3 NE Port View. ........................................................................................................................ 1-28
1-11 Alarm representation in the Equipment views. ............................................................................................ 1-30
2-1 Iterative Approach for Alarm Description ........................................................................................................ 2-7
2-2 Alarm Surveillance Window ................................................................................................................................. 2-8
2-3 Alarm Reservation .................................................................................................................................................. 2-10

2-10
2-4 Alarm reserved ......................................................................................................................................................... 2-10

2-10
2-5 Unreserve Alarms .................................................................................................................................................... 2-11

2-11
2-6 Acknowledging Alarms ........................................................................................................................................ 2-13
2-7 Ack. Status change ................................................................................................................................................. 2-13

2-13
2-8 AS Output window ................................................................................................................................................. 2-17
2-9 File Chooser dialog box ........................................................................................................................................ 2-18
2-10 Navigation from NE list to AS ........................................................................................................................... 2-21
2-11 Alarm Sublist for selected NE ............................................................................................................................ 2-22
2-12 Navigation to NE USM ......................................................................................................................................... 2-23
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xvii
March 2010
List of figures
....................................................................................................................................................................................................................................
2-13 NE USM ..................................................................................................................................................................... 2-24
2-24
3-1 ELB Application ........................................................................................................................................................ 3-2

3-2
3-2 Show equipment activation .................................................................................................................................... 3-3
3-3 Navigation from EML USM to ELB .................................................................................................................. 3-3
3-4 Loading Dialog ........................................................................................................................................................... 3-4

3-4
3-5 NAV Message Information Dialog ...................................................................................................................... 3-4
3-6 Alarm Log Display selected .................................................................................................................................. 3-6
3-7 Event Log Display selected ................................................................................................................................... 3-7
3-8 Menu Bar ...................................................................................................................................................................... 3-8

3-8
3-9 File Menu ...................................................................................................................................................................... 3-8

3-8
3-10 Export Dialog .............................................................................................................................................................. 3-9

3-9
3-11 Export Successful Information Dialog .............................................................................................................. 3-9
3-12 Write protected error message ............................................................................................................................ 3-10
3-13 Export Failed Error Message .............................................................................................................................. 3-10
3-14 Print Dialog ............................................................................................................................................................... 3-11

3-11
3-15 Print Failed Error Message .................................................................................................................................. 3-11
3-16 Print Preview Dialog .............................................................................................................................................. 3-12

3-12
3-17 Print Preview Error Message .............................................................................................................................. 3-12
3-18 ELB Tabbed Panes .................................................................................................................................................. 3-13

3-13
3-19 Alarm Log request Start Up ................................................................................................................................ 3-14
3-20 Progress Dialog ........................................................................................................................................................ 3-15

3-15
3-21 Alarm Log Display ................................................................................................................................................. 3-16

3-16
3-22 Event Log request Start Up ................................................................................................................................. 3-17
3-23 Event Log Display .................................................................................................................................................. 3-18

3-18
3-24 Event Log Filters Dialog ...................................................................................................................................... 3-20
3-25 Alarm Log Filters Dialog ..................................................................................................................................... 3-21
3-26 Example of Logical Operators in Alarm Log Filters Dialog ................................................................... 3-22
....................................................................................................................................................................................................................................
xviii 8DG42094BAAA Issue 1
March 2010
List of figures
....................................................................................................................................................................................................................................
3-27 Selected filters for Alarm Filters Dialog ......................................................................................................... 3-23
3-28 Selected filters for Event Filters Dialog ......................................................................................................... 3-24
4-1 Dynamic Filtering ................................................................................................................................................... 4-10

4-10
4-2 Static Filtering .......................................................................................................................................................... 4-11

4-11
5-1 Action Menu from menu bar ................................................................................................................................. 5-2
5-2 Commands list from EML Domain Inventory ................................................................................................ 5-3
5-3 Search - Get All NE ................................................................................................................................................ 5-11

5-11
6-1 Action Menu from menu bar ............................................................................................................................... 6-10
6-2 Action Menu popup from NE Global Inventory .......................................................................................... 6-12
6-3 Commands list from EML Domain Inventory .............................................................................................. 6-13
6-4 Supervision Selection ............................................................................................................................................ 6-19

6-19
6-5 Time Management–Set Time Dialog Box (before command execution) ........................................... 6-24
6-6 MIB Alignment–Align MIB Up Dialog Box ................................................................................................ 6-27
6-7 Local Access––Switch to Local Dialog Box ................................................................................................. 6-28
6-8 Local Access–Switch to OS Dialog Box ........................................................................................................ 6-29
6-9 Set NE NTP Configuration .................................................................................................................................. 6-31
6-10 Set NE NTP Configuration (IP configuration) ............................................................................................. 6-32
6-11 ACD window for an NE ....................................................................................................................................... 6-35
6-12 Create ISA board window .................................................................................................................................... 6-37
6-13 OS Address Wizard ................................................................................................................................................ 6-39

6-39
6-14 Upload Remote Inventory Dialog Box ............................................................................................................ 6-59
6-15 Global Remote Inventory ..................................................................................................................................... 6-62
6-16 Information window for an NE .......................................................................................................................... 6-65
6-17 Current Status Window for an NE .................................................................................................................... 6-68
6-18 Search - Get All NE ................................................................................................................................................ 6-71

6-71
6-19 OS Address Dialog Box ........................................................................................................................................ 6-79
7-1 Web Portal application - MS-GUI Activation ................................................................................................. 7-4
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xix
March 2010
List of figures
....................................................................................................................................................................................................................................
7-2 Create Account selection on NE ZIC GUI ....................................................................................................... 7-6
7-3 TSS Account List ....................................................................................................................................................... 7-7

7-7
7-4 Change password window on TSS NE ZIC GUI ........................................................................................... 7-8
7-5 Login window on TSS NE ZIC GUI .................................................................................................................. 7-8
7-6 Account creation on EML System ...................................................................................................................... 7-9
7-7 Attribute Name Value ............................................................................................................................................ 7-10

7-10
7-8 SEC User Authentication GUI ............................................................................................................................ 7-11
7-9 Declare Sec Users Selection ................................................................................................................................ 7-12
7-10 Declare the new user .............................................................................................................................................. 7-13

7-13
7-11 Operator Profile Setting ........................................................................................................................................ 7-14

7-14
7-12 NE Global Inventory activation ......................................................................................................................... 7-16
7-13 1350 OMS EML Create Network Element .................................................................................................... 7-17
7-14 1850 TSS NE Creation .......................................................................................................................................... 7-18
7-15 1850 TSS Set Address ........................................................................................................................................... 7-20
7-16 Error Details .............................................................................................................................................................. 7-22

7-22
7-17 1850 TSS User Interface ...................................................................................................................................... 7-23
7-18 Ping NE result .......................................................................................................................................................... 7-24

7-24
7-19 Navigation to AS application .............................................................................................................................. 7-26
7-20 Navigation to AS USM ......................................................................................................................................... 7-27
7-21 TSS NE Alarms Sublist ......................................................................................................................................... 7-28
8-1 EML Performance Monitoring selection from MS-GUI ............................................................................. 8-3
8-2 PM Domains on EML List ..................................................................................................................................... 8-4
8-3 Set reporting Criteria ............................................................................................................................................. 8-10

8-10
8-4 Select filtering criteria ........................................................................................................................................... 8-12

8-12
8-5 Search Functions ..................................................................................................................................................... 8-13

8-13
8-6 Search Window: TP Name ................................................................................................................................... 8-14
8-7 Search Functions ..................................................................................................................................................... 8-15

8-15
....................................................................................................................................................................................................................................
xx 8DG42094BAAA Issue 1
March 2010
List of figures
....................................................................................................................................................................................................................................
8-8 Search Window: TP Value ................................................................................................................................... 8-16
8-9 Report destination selection ................................................................................................................................ 8-19
8-10 Setting presentation options ................................................................................................................................ 8-20
9-1 NPR activation ............................................................................................................................................................ 9-3

9-3
10-1 Q3 NE NM connection types .............................................................................................................................. 10-4
10-2 Misalignement (warning alarm) between NE NM MIB and NE configuration ............................... 10-7
10-3 NE Statuses shown window ................................................................................................................................ 10-9
10-4 Simulator menu "Align Up" option ............................................................................................................... 10-10
10-5 Information window during a MIB Align Up procedure ....................................................................... 10-11
10-6 NM MIB representation ..................................................................................................................................... 10-12
10-7 SDH connected to NE simulator ..................................................................................................................... 10-14
10-8 On–board Simulator monitoring ..................................................................................................................... 10-15
10-9 OMSN and ISA board ......................................................................................................................................... 10-22
10-10 Create ISA selection ............................................................................................................................................ 10-25

10-25
10-11 Create ISA Window ............................................................................................................................................. 10-26

10-26
10-12 Set Addresses: IP Address ................................................................................................................................. 10-29
10-13 Start Supervision on OMSN. ............................................................................................................................ 10-31
10-14 Rename OMSN NE ............................................................................................................................................. 10-34
10-15 Alarm indication synthesis ................................................................................................................................ 10-39
10-16 Alarm Menu ............................................................................................................................................................ 10-40

10-40
10-17 Alarm surveillance window .............................................................................................................................. 10-41
10-18 AS navigation back to NE EML USM ......................................................................................................... 10-42
10-19 Relationship between AS and Port View of NE EML USM ................................................................. 10-43
10-20 Configuring Alarm Severity Assignment Profile. ..................................................................................... 10-47
10-21 ASAPs Management dialogue box. ............................................................................................................... 10-48
10-22 ASAP Edition dialogue box example. .......................................................................................................... 10-49
10-23 Example of Management dialogue box with two customized ASAPs .............................................. 10-51
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xxi
March 2010
List of figures
....................................................................................................................................................................................................................................
10-24 OAD: Object: Create ........................................................................................................................................... 10-54
10-54
10-25 Elementary OAD: Create ................................................................................................................................... 10-56
10-26 Create NE ................................................................................................................................................................ 10-61

10-61
10-27 Create NE ................................................................................................................................................................ 10-62

10-62
10-28 FT Scheduler option ............................................................................................................................................ 10-63
10-29 Job status and "View Report" command ...................................................................................................... 10-75
10-30 Backup report window example ...................................................................................................................... 10-76
10-31 SW Status menu ................................................................................................................................................... 10-78

10-78
10-32 NEs SWDL Status ................................................................................................................................................ 10-79

10-79
10-33 SW Status selected by name with a NE list menu .................................................................................... 10-80
10-34 NE software status detail ................................................................................................................................... 10-82
10-35 Q3–NE Software unit detail example ............................................................................................................ 10-83
10-36 Software management action example ......................................................................................................... 10-84
10-37 SW Status Selected by NE Type with a NE list menu ............................................................................ 10-85
10-38 DCN network example ....................................................................................................................................... 10-86
10-39 Balancing the DCN traffic load ....................................................................................................................... 10-87
10-40 Optimizing the load traffic for session .......................................................................................................... 10-88
10-41 Example of DCN traffic increasing the LAN load ................................................................................... 10-90
10-42 Job editor example ............................................................................................................................................... 10-92

10-92
10-43 SWDL job report example ................................................................................................................................. 10-93
10-44 NEs software status table example ................................................................................................................. 10-94
10-45 Action on NE software package memory banks ....................................................................................... 10-94
11-1 Supervision Area Selection in System Configuration ................................................................................ 11-4
11-2 Configuration of Supervision Area Parameters ............................................................................................ 11-5
11-3 Confirmation Dialog before Supervision Area is deconfigured ............................................................. 11-5
11-4 Supervision Area selection in OSI Stack configuration ............................................................................ 11-7
11-5 OSI Tunnel Configuration .................................................................................................................................... 11-8

....................................................................................................................................................................................................................................
xxii 8DG42094BAAA Issue 1
March 2010
List of figures
....................................................................................................................................................................................................................................
11-6 Supervision Area selection during Q3 EML–IM configuration ............................................................. 11-9
11-7 Supervision Area selection during SNMP EML–IM configuration ...................................................... 11-9
11-8 Supervision Area selection during 4G EML–IM configuration .......................................................... 11-10
11-9 Supervision Area selection for coordinator ................................................................................................. 11-10
14-1 System Configuration ............................................................................................................................................ 14-6

14-6
14-2 Save inserted data ................................................................................................................................................... 14-8

14-8
14-3 Update Config Selection ....................................................................................................................................... 14-8
14-4 Start IP over OSI Processes .............................................................................................................................. 14-10
14-5 netstat command with osi tunnelling process running ............................................................................ 14-11
14-6 netstat command with osi tunnelling process stopped ............................................................................ 14-11
14-7 Show equipment activation ............................................................................................................................... 14-12
14-8 Network Element USM ...................................................................................................................................... 14-13
14-9 Point–to–Point Address Configuration selection ...................................................................................... 14-14
14-10 IP Address for PtoP Configuration ................................................................................................................. 14-14
14-11 IP over OSI Selection .......................................................................................................................................... 14-15
14-12 IP over OSI Tunnelling Configuration .......................................................................................................... 14-16
14-13 IP Static Routing Configuration Selection .................................................................................................. 14-17
14-14 IP Static Routing Configuration ...................................................................................................................... 14-18
14-15 Create ISA board selection ................................................................................................................................ 14-19
14-16 Create ISA window .............................................................................................................................................. 14-20

14-20
14-17 Tunnel Configuration Application .................................................................................................................. 14-23
14-18 Create Tunnel window ........................................................................................................................................ 14-24
14-19 Tunnel configuration list window ................................................................................................................... 14-25
14-20 Add IP NE on selected Tunnel ......................................................................................................................... 14-26
14-21 Add IP NE on Tunnel .......................................................................................................................................... 14-27
14-22 Detail Window for a Tunnel ............................................................................................................................. 14-28
14-23 Start Supervision on ISA board ....................................................................................................................... 14-29
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xxiii
March 2010
List of figures
....................................................................................................................................................................................................................................
14-24 Remove NE from Tunnel ................................................................................................................................... 14-30
15-1 AS NE Autodiscovery sublist ............................................................................................................................. 15-3
....................................................................................................................................................................................................................................
xxiv 8DG42094BAAA Issue 1
March 2010
About this document
About this document
Purpose
This preface provides an overview of this information product (IP), which is the 1350
OMS EML User Guide.
The purpose of the 1350 OMS EML User Guide is to explain to system and network
administrators how to use the 1350 OMS 9.1.1 to manage all Alcatel-Lucent Network
Elements.
Reason for revision

The revision history of this document is shown in the following table:
Location Revision Issue

1350 OMS EML User Guide Document changes reflect the Issue 1, October 2009
new 9.1.1 release of the 1350
OMS.
1350 OMS EML User Guide Revised issue for 9.1.1 Issue 2, December 2009
Maint-1 Release
1350 OMS EML User Guide Revised issue for 9.1.1 Issue 2, March 2010
Maint-2 Release
1350 OMS EML User Guide Reissued for R9.1.1 Maint -2 Issue 1, March 2010
with new part and issue
numbers.
Safety information
This document does not contain any safety information (cautions or warnings) because
the 1350 OMS is a software product.
Important! When working with any hardware that is associated with any piece of
software, always refer to the safety information that the hardware manufacturer provides
for that particular piece of hardware. For example, when working with an HP® server,
...................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xxv
March 2010
About this document
....................................................................................................................................................................................................................................
refer to safety information that is provided in the HP® documentation for that server.
When working with any Alcatel-Lucent network element, refer to safety information that
is provided in the Alcatel-Lucent documentation for that particular NE.
Intended audience
The 1350 OMS EML User Guide is written primarily for operations personnel who use
the 1350 OMS for network provisioning.
How to use this information product

In the broadest sense, the 1350 OMS EML User Guide contains the following:
• Conceptual information, which is specific data related to the tasks
• Task information, which includes user tasks (that is, step-by-step instructions)
The conceptual information complements and enhances the step-by-step instructions that
are found in each task. Use the conceptual information to broaden your general
knowledge of the network management system. It is best if you read all conceptual
information and have a good understanding of the concepts being presented before
undertaking the step-by-step instructions given in any task.
The task information is based on a user needs analysis that has been performed for each
management system user job; therefore, use the task information to get the job at hand
done quickly and with minimal system impact.
The conceptual and task information portions of the document have extensive hyperlinks.
Use these links to toggle between the two types of information presented so you can
access all pertinent information related to particular concepts and tasks.
A term that is presented in the text of this document, along with any used abbreviation for
the term, is typically defined where the term is initially introduced. Many of the more
generic terms that are defined in this document, along with the terms that are defined in
other documents in this documentation set, are also defined in the Glossary, which is part
of the 1350OMS Getting Started User Guide. We encourage our readers to rely on the
Glossary for a comprehensive set of terms and any abbreviations of the terms.
This document can be used in its on-line versions (HTML/PDF) or in paper version (print
PDF). The on-line HTML document version has a search capability, a full table of
contents in the front matter of the document, a partial table of contents in each chapter, an
index for each document, and an index for the entire documentation set. Use all of these
tools to help find information quickly. However, be aware that the index for each
document and the index for the entire documentation set are the preferred search tools.
Important! This document contains information on the complete line of network
elements (NEs) that the product supports. Each release of the 1350 OMS and its
applications supports certain NEs within the Alcatel-Lucent family of optical NEs.
Mention of NEs or specific NE features in the text of this document, or any document
....................................................................................................................................................................................................................................
xxvi 8DG42094BAAA Issue 1
March 2010
About this document
....................................................................................................................................................................................................................................
in the 1350 OMS documentation set, that are not supported in this particular product
release can apply to prior or future product releases. Such material may not be
currently visible or operable on the GUI and/or the server and has been added only as
a convenience for our customers. This material is subject to change. For a list of NEs
that are supported in the 1350 OMS 9.1.1, contact your Alcatel-Lucent local customer
service support team.
In addition, this document, or any document in the 1350 OMS documentation set,
may contain information that is related to features, service packs (SPs), maintenance
releases, or other updates that our product and its applications supported in prior
releases or is to support in the near future. This material may not be visible or
operable on the supported servers and/or GUI, and has been added only as a
convenience for our customers. This material is subject to change. For a list of all
supported features for a particular release, contact your Alcatel-Lucent local customer
service support team.
In general, the technical material in this document is augmented by technical material
that is provided in other documents in this documentation set. It is the reader's
responsibility to read all pertinent material in the documentation set in order to
understand a particular concept or procedure and/or to implement the procedure in his
or her working environment.
Example: The Administration Guide for the 1350 OMS is a set of documents that is
published in volumes to reduce the size of the overall document. Each volume
contains technical material that can augment material in other documents in the
document set. The system administrator must be knowledgeable of the material that is
in each volume of the set. In addition, other documents in the documentation set, such
as the 1350OMS Getting Started User Guide and the 1350OMS Service Assurance
Guide, contain other important information to the administration of the system. The
administrator must also be knowledgeable of the material that is in each of these
documents.
Conventions used
The conceptual information typically introduces each chapter or section of each chapter.
The information presented in this area varies according to the topic being
explained—sections, subsections, tables, figures, and screen captures can be commonly
found.
The task information is presented as series of tasks that follows the conceptual
information. These tasks are typically presented in the following functional order,
depending on the nature of the subject being explained:
• View a List of . . .
• View the Details of . . .
• Add . . .
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xxvii
March 2010
About this document
....................................................................................................................................................................................................................................
• Configure . . .
• Create . . .
• Change . . .
• Enter . . .
• Modify . . .
• Delete . . .
Each task consists of sections that are called When to use, Before you begin, Related
information, and Task.
The intent of the When to use, Before you begin, and Related information sections is
self-explanatory—they explain when a task is to be used, what needs to be considered or
done before you begin the task, and any related information that you would need to know
while doing the task.
When a task does not have any conditions that must be considered before it is started, the
Before you begin section for that task states the following:
This task does not have any preconditions.
When a task does not have any related information that must be considered before it is
started, the Related information section for that task states the following:
This task does not have any related information.
Each Task section consists of any number of steps. The completion of all steps, which are
sequentially numbered, are required for the entire task to be completed successfully. In
some instances, a step might be prefaced with the wording Optional, which indicates that
the step can be skipped and the task can still be successfully completed. A task is
considered to be completed when all of its steps are completed and when the wording End
of Steps appears.
Many times, the management system affords the user with multiple ways to accomplish
the same task. In these instances, one task can present the user with several Methods of
how to accomplish the same set of steps successfully.
This document, and the documents in this document set, rely on the following
typographical conventions to distinguish between user input and computer output.
• When describing the 1350 OMS software, fields in windows and field entries are
identified with this font.
• When describing the UNIX® environment, text and numbers that the user inputs to
the computer are identified with boldface type.
• When describing system output in the UNIX® environment, text and numbers are
identified with monospace type.
• When displaying system output in the UNIX® environment, output displays are
identified with the following boundary:
....................................................................................................................................................................................................................................
xxviii 8DG42094BAAA Issue 1
March 2010
About this document
....................................................................................................................................................................................................................................
This is an example of system output in the UNIX® environment.

This document uses the following convention to indicate a path of pages or windows that
should be navigated through to arrive at a destination page:
• Network > Submaps
This same convention is also used to show a path through a series of menu items, for
example:
• Click the filtering tool, and select Node > Node Type.
Occasionally, a set of 1350 OMS features is not supported for all NEs or for all operating
component and/or environments. This set of features is clearly marked to show these
exceptions.
Related documentation
The document set that supports the Alcatel-Lucent 1350 OMS 9.1.1 release set can be
ordered on CD-ROM. The part number for this CD-ROM is 8DG42098AAAA. This
CD-ROM contains the following 1350 OMS 9.1.1 release set documents:
1. The 1350OMS Getting Started User Guide (8DG42094AAAA) explains the
look-and-feel of the user and administration GUIs to new users. This document
contains a complete explanation of the 1350 OMS information product set and a
glossary of terms that is applicable to the entire documentation set.
2. The 1350 OMS Administration Guide (8DG42094KAAA) explains how to use the
tools and the administration GUIs to administer and maintain the element
management layer, network management layer, and service management layer of the
1350 OMS.
This document consists of the following volumes:
• The 1350OMS Administration Guide, Vol 1: Common Tools and Processes
(8DG42094KAAA-Vol1) is volume 1 of the 6 volume set. This document explains
how to administer and maintain the common tools and processes that are
associated with the 1350 OMS.
• The 1350OMS Administration Guide, Vol 2: Common GUI Functions
how to administer and maintain the common administration GUIs that are
associated with the 1350 OMS.
• The 1350OMS Administration Guide, Vol 3: 1350OMS-EML (8DG42094KAAA-
Vol3) is volume 3 of the 8 volume set. This document explains how to administer
and maintain the 1350 OMS EML, which is the element management layer of the
1350 OMS.
• The 1350 OMS Administration Guide, Vol 4: 1350 OMS eOMS
how to administer and maintain the 1350 OMS eOMS, which is the embedded
Optical Management System application of the 1350 OMS.
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xxix
March 2010
About this document
....................................................................................................................................................................................................................................
• The 1350 OMS Administration Guide, Vol 5: 1350 OMS PKT (8DG42094KAAA-
and maintain the Packet application of the 1350 OMS that provides Ethernet
network management layer support.
• The 1350 OMS Administration Guide, Vol 6: 1350 OMS SDH (8DG42094KAAA-
and maintain the Synchronous Digital Hierarchy (SDH) network management
layer for the 1350 OMS.
3. The 1350 OMS EML User Guide (8DG42094BAAA) explains how to use 1350 OMS
EML application of the 1350 OMS, which is the element management layer of the
1350 OMS.
4. The 1350 OMS PKT User Guide (8DG42094DAAA) explains how to use Packet
(PKT) application of the 1350 OMS that provides Ethernet network management
layer support.
5. The 1350 OMS SDH User Guide, Vol 1: Basic Management (8DG42094CAAA Vol1)
and 1350 OMS SDH User Guide, Vol 2: Enhanced Solutions (8DG42094CAAA Vol2)
are a set of documents that explain how to use the Synchronous Digital Hierarchy
(SDH) network management layer of the 1350 OMS.
6. The 1350OMS Service Assurance Guide (8DG42094FAAA) explains how to maintain
the 1350 OMS in terms of activities such as alarm clearing and performance
monitoring.
7. The 1350OMS eOMS Connection Management User Guide (8DG42094QAAA)
explains how to provision and manage connections in the 1350 OMS eOMS
environment of the 1350 OMS.
8. The 1350OMS-eOMS Ethernet Management User Guide (8DG42094RAAA) explains
how to use the Ethernet Management feature to provision and manage Ethernet
connections in the 1350 OMS eOMS environment of the 1350 OMS.
9. The 1350OMS-eOMS Service Assurance User Guide (8DG42094TAAA) explains
how to manage and interpret fault and performance monitoring information that is
collected from the 1350 OMS eOMS environment of the 1350 OMS.
10. The 1350OMS-eOMS Network Element Management User Guide (8DG42094SAAA)
explains how to use the 1350 OMS eOMS to provision and manage network
elements.
11. 1350 OMS CLI Reference (8DG42094JAAA) provides detailed reference material on
the Command Line Interface for the advanced user of the 1350 OMS.
The 1350 OMS 9.1.1 also supports modules for system resiliency and northbound
communication. These modules are explained in the following documents:
• 1350 OMS HA Guide (8DG42094GAAA) explains how to install, administer, and use
the High Availability feature.
• 1350 OMS OI Guide (8DG42094HAAA) explains how to install, administer, and use
the Open Interfaces that are supported for the 1350 OMS.
....................................................................................................................................................................................................................................
xxx 8DG42094BAAA Issue 1
March 2010
About this document
....................................................................................................................................................................................................................................
In addition, the 1350 OMS 9.1.1 also supports installation and migration activities with
related documentation. Contact your Alcatel-Lucent local customer service support team
for additional details.
Help products
The 1350 OMS includes an extensive set of help systems that are designed to consider the
task the user is performing and help that user successfully perform the task. The help
products can be accessed from the Help menu that is displayed on the GUI window.
How to order
The ordering number for this document is 8DG42094BAAA. To order any 1350 OMS
document, contact your local Alcatel-Lucent local customer service support team.
In addition, to order the 1350 OMS and/or any of its applications, add-on features or
upgrades, contact your local Alcatel-Lucent local customer service support team.
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/enus/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 xxxi
March 2010
About this document
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xxxii 8DG42094BAAA Issue 1
March 2010
1 Product Overview
1
Overview
Purpose
This section describes 1350 OMS product family, introduces the 1350 OMS EML
working environment in terms of getting access to the system, the environment utilities,
the existing 1350 OMS EML functionalities and navigation through the system.
Contents
1350OMS and its applications 1-3

1350 OMS Overview 1-3
1350 OMS Modules for System Resiliency and Northbound Communication 1-6
System Overview 1-7
System access from Desktop 1-7
Functionality available from Web desktop 1-11
Work Environment 1-12
View Description 1-14
Equipment View Description 1-14
Equipment View 1-24
Open in Window command 1-24
NE Equipment views 1-25
NE Alarms and NE Status 1-29
NE Alarms 1-29
NE Status 1-31
On Line Documentation 1-34
Help on MS-GUI Framework 1-35
...................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 1-1
March 2010
Product Overview Overview
....................................................................................................................................................................................................................................
Help Activation 1-36

Help on context 1-37
Glossary 1-38
....................................................................................................................................................................................................................................
1-2 8DG42094BAAA Issue 1
March 2010
Product Overview 1350 OMS Overview
....................................................................................................................................................................................................................................
1350 OMS Overview

1350 OMS and its supported management layers
The 1350 OMS is a network management system that supports several management
layers that can accommodate and grow with a customer's optical network.
The Element Management Layer, or EML, provides the functionality that is needed to
access any Alcatel-Lucent supported network elements (NEs) that are deployed in a
customer network. The EML provides a single access point for communication with an
NE.
The Network Management Layer, or NML, provides the functionality that is needed to
commission, provision, and supervise the network that is deployed in a customer premise.
The Service Management Layer, or SML, provides the functionality that is needed to
commission, provision, and supervise a Virtual Private Network (VPN) that an
Alcatel-Lucent customer deploys to its end users or to its customers.
1350 OMS and its applications

The 1350 OMS is the Alcatel-Lucent converged and unified network management
system. It manages the complete portfolio of Alcatel-Lucent's active network elements
(NEs) and it maintains the complete portfolio of Alcatel-Lucent's legacy NEs.
The 1350OMS consists of the following set of integrated, licensed applications:
• “1350 OMS EML” (p. 1-3)
• “1350 OMS PKT” (p. 1-4)
• “1350 OMS SDH” (p. 1-4)
Refer to the 1350OMS Getting Started User Guide for a more detailed system description.
1350 OMS EML

The 1350 OMS EML application provides element level management (EML) capabilities
for both Alcatel-Lucent ANSI and ETSI NEs. Its set of protocol adapters support basic
NE functions such as NE MIB backup/restore and software downloads. Because the 1350
OMS provides all of the element layer functions that are required to manage the deployed
network, it requires the 1350 OMS EML application and/or the 1350 OMS eOMS legacy
management system to also be deployed. (See “Legacy management and NE support”
(p. 1-5).)
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Refer to the 1350OMS Administration Guide, Vol 3: 1350OMS-EML and the 1350 OMS
EML User Guide; and contact your Alcatel-Lucent local customer service support team
for additional details.
1350 OMS PKT

The 1350 OMS PKT application provides Ethernet network management layer support
along with provisioning, alarm correlation, and historical PM data services. Ethernet
services include Multi-Protocol Label Switching (MPLS), Transport-Multi-Protocol Label
Switching (T-MPLS), bridging, connection-oriented traffic, and packet rings.
Refer to the 1350 OMS PKT User Guide; and contact your Alcatel-Lucent local customer
service support team for additional details.
1350 OMS SDH

The 1350 OMS SDH application provides the Synchronous Digital Hierarchy (SDH)
network management layer along with provisioning, alarm correlation, and PM
correlation capabilities. The 1350 OMS SDH functions as a client for the 1350 OMS
WDM application and as a server for the 1350 OMS PKT application.
Refer to the 1350 OMS SDH User Guide, the 1350 OMS CLI Reference, and the
1350OMS Service Assurance Guide; and contact your Alcatel-Lucent local customer
service support team for additional details.
For 1350 OMS support of SDH in a legacy system, refer to “Legacy management and NE
support” (p. 1-5) for details.
1350 OMS software and the Web

1350 OMS is run through an Internet browser-based Graphical User Interface (GUI). It
supports the standard web features that a browser offers, such as bookmarks, back,
forward, reload, and print.
The Web Desktop is the available mechanism that both system administrators and users
can use to access the 1350OMS GUI. It provides a central access point from which both
system administrators and users are authenticated and from which they can navigate to
the Web Portal to access the 1350OMS applications.
The Web Portal is a Java application that is started when the administrator or user logs in
from the Web Desktop. The Web Portal provides the administrator with a view of all
1350OMS applications and manages GUI navigation between the subsystem components.
The Web Portal also provides various methods of navigation—such as menus, icons, and
a left tree navigation area—between applications and tools.
From the 1350OMS Web Portal, administrators can set up each application and its users,
and users can access the network and element level applications that enable the family of
Alcatel-Lucent NEs to be provisioned.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Refer to the 1350OMS Getting Started User Guide for a more detailed description of the
look and feel of the software and for a glossary of terms and acronym list.
Legacy management and NE support

Through its Web Portal, the 1350OMS provides users with the ease of accessing and
using the familiar embedded Optical Management System (eOMS) to provision the NEs
that are managed through the 1350 OMS eOMS or the NEs that are managed through an
XML-over-socket (XoS) interface (such as TNA, CNA, or ITM-SC).
Refer to the following documents for additional information on the 1350 OMS eOMS:
• 1350OMS Getting Started User Guide
• 1350 OMS Administration Guide, Vol 4: 1350 OMS eOMS
• 1350OMS-eOMS Ethernet Management User Guide
• 1350OMS-eOMS Service Assurance User Guide
• 1350OMS-eOMS Network Element Management User Guide
Because the 1350 OMS provides all of the element layer functions that are required to
manage the deployed network, it requires the 1350 OMS EML application and/or the
1350 OMS eOMS legacy management system to also be deployed. (See “1350 OMS
EML” (p. 1-3).)
1350 OMS supported NEs

The 1350 OMS supports the Alcatel-Lucent family of optical network elements (NEs). To
accommodate the world of optical transmission standards, these NEs operate using
different transport structures and they support different native command languages.
Contact your local customer support team for a list of NEs that are supported by the 1350
OMS and its particular applications.
Important! Each release of the 1350 OMS and its applications supports certain NEs
within the Alcatel-Lucent family of optical NEs. Mention of NEs or specific NE features
in the text of this document, or any document in the 1350 OMS documentation set, that
are not supported in this particular product release can apply to prior or future product
releases. Such material may not be currently visible or operable on the GUI and/or the
server and has been added only as a convenience for our customers. This material is
subject to change. For a list of NEs that are supported in the 1350 OMS 9.1.1, contact
your Alcatel-Lucent local customer service support team.
....................................................................................................................................................................................................................................
March 2010
Product Overview 1350 OMS Modules for System Resiliency and Northbound
1350OMS and its applications Communication
....................................................................................................................................................................................................................................
1350 OMS Modules for System Resiliency and Northbound

Communication
1350 OMS HA
The 1350 OMS supports High Availability (HA) as an added value module, which is
referred to as the 1350 OMS HA. The 1350 OMS HA software package is installed on top
of an already installed and configured NML and EML platform and independently of any
other application such as the 1350 OMS SDH or 1350 OMS PKT, or any element
manager such as the 1350 OMS EML or 1350 OMS eOMS.
As its name suggests, the 1350 OMS HA provides high availability to these applications
whose main task is to manage transport networks. It protects the 1350 OMS applications
and its HP® server platform against hardware and software failures that could be caused
by system failures (such as the failure of the system power supply or a system
component), a site failure (such as a natural disaster or fire), a backplane failure, a
processor failure, or any unplanned outage.
The 1350 OMS HA is explained in detail in the 1350 OMS HA Guide
(8DG42094GAAA). This document includes installation, administration, and user
information for the 1350 OMS High Availability (HA) feature.
Contact your Alcatel-Lucent local customer service support team for additional details.
1350 OMS OI
The 1350 OMS supports Open Interfaces (OI) as an added value module, which is
referred to as the 1350 OMS OI. The 1350 OMS OI software package is installed on top
of an already installed and configured MW-INT platform and independently of any other
application such as the 1350 OMS SDH or 1350 OMS PKT, or any element manager such
as the 1350 OMS eOMS or 1350 OMS eOMS.
The 1350 OMS OI enables the 1350 OMS applications to export or import data to
multiple external operation systems (OSs). The 1350 OMS OI is a flexible, powerful, and
effective set of generic OS-to-OS interfaces (GENOS) that allow an external OS to
synchronize alarms, performance monitoring, network inventory, and remote inventory
data with any of the 1350 OMS applications.
The 1350 OMS OI is explained in detail in the 1350 OMS OI Guide (8DG42094HAAA).
This document includes installation, administration, and user information for the Open
Interfaces (OIs) that are supported for the 1350 OMS.
Contact your Alcatel-Lucent local customer service support team for additional details.
....................................................................................................................................................................................................................................
March 2010
Product Overview System access from Desktop
System Overview
....................................................................................................................................................................................................................................
System Overview
System access from Desktop

Logging using Web desktop
The system can be invoked from any web browser:
Login
...................................................................................................................................................................................................
1 Insert Web desktop address in the browser.

...................................................................................................................................................................................................
2 Click Enter in the Web Desktop welcome page.

...................................................................................................................................................................................................
3 Insert login name (user) and password in the pop-up window.
....................................................................................................................................................................................................................................
March 2010
System Overview
....................................................................................................................................................................................................................................
Figure 1-1 Web Desktop login
...................................................................................................................................................................................................
4 Web portal home page opens.
....................................................................................................................................................................................................................................
March 2010
System Overview
....................................................................................................................................................................................................................................
Figure 1-2 Web Desktop portal
Web portal provides the user with a view of all the 1350 OMS applications and allows
the user to navigate the application sub-systems and components.
The Web portal provides various method to navigate among applications and tools
such as menus, icons, and tree navigation area.
First Login
Logging-in the first time the user enters the name and the password provided at
installation time. After the first login, the system prompts the user for changing password.
....................................................................................................................................................................................................................................
March 2010
System Overview
....................................................................................................................................................................................................................................
Change password
To change the password the user has to choose from main menu bar: File > Change
password
Log out
To Log out the user has to choose from main menu bar: File > Log Out or close all Web
desktop windows. Logging out from the Web desktop quits automatically all graphical
applications that you opened.
Log out operation disconnects user work session, it does not stop running application
started during the session.
Password Expiration
Password periodical expiration is not foreseen in Web desktop.
Locking and Unlocking the session

Manual session lock is not foreseen in Web desktop. The lock of the Web desktop can
only occur for inactivity time-out. To prevent other users from using your working
environment lock the screen at terminal level.
Inactivity Timeout
During a work session, if you have not undertaken any operations since a certain time, the
Web desktop is automatically locked by the system. The parameters to manage the screen
lock cannot be configured (for example the timeout period before the screen locks). When
the Web desktop is locked a message and the login pop up window are shown. To unlock
the Web desktop the user must log in again.
....................................................................................................................................................................................................................................
March 2010
Product Overview Functionality available from Web desktop
System Overview
....................................................................................................................................................................................................................................
Functionality available from Web desktop

Application Categories
Applications are divided by their logical function in the following main categories:
• Provisioning - includes applications for network provisioning and inventory
management.
• Maintenance - includes applications for network maintenance operations
• Tools - includes management system tools.
Each category contains the following functions related to 1350OMS-EML application:
• Provisioning
Element Mgt
• Maintenance
Fault
– Current Alarms (EML)
– Historical Alarms (EML)
EML Performance Monitoring
• Tools
Security Administration
– User Profile (EML)
– User Admin (EML)
System Monitoring
– System Monitor (EML)
Data Management
– Backup (EML)
– Restore (EML)
– Scheduler (EML)
– EML PM Administration (EML)
– NE Data Scheduler
Configuration
– NE-SW Administration
– NE Auto-Discovery
– DCN Tunneling
....................................................................................................................................................................................................................................
March 2010
Product Overview Work Environment
System Overview
....................................................................................................................................................................................................................................
Work Environment
Workspace Description
Your workspace is described as the functionalities that are on your workstation screen
after login.
The workspace Front Panel is described below.
Figure 1-3 The 1350 OMS EML workspace Front Panel.
The components of this front panel are distributed across two rows.
Top row of the Front Panel (from left to right):
• The Clock icon displays the current time on your workstation.
• The Date display indicates the day and the date and enables you to access a calender.
• The WS activity icon indicates the internal activity of the workstation.
• The Help icon enables you to launch the help application.
• The Lock icon enables you to lock your workstation screen.
• The Workspace icons enable you to access different workspaces. There are only two
available workspaces (workspaces One and Two) used in the 1350 OMS EML
product.
• The Printer icon enables you to access the printing facilities. You can drag a file to
the printer icon to print it or simply access printer information.
• The Letter icon gives access to the electronic mail service.
• The File Manager icon gives you access to the files in your home directory.
• The Terminal icon launches a hp–term command shell on your workspace.
Bottom row of the Front Panel (from left to right):
• The Alcatel-Lucent logo icon gives access to information about the 1350 OMS EML
product.
• The Workspace naming icon enables you to rename your workspaces.
....................................................................................................................................................................................................................................
March 2010
Product Overview Work Environment
System Overview
....................................................................................................................................................................................................................................
• The Key icon launches the password modification application on your workspace
enabling you to change your password.
• The EXIT icon launches the logout procedure.
....................................................................................................................................................................................................................................
March 2010
Product Overview Equipment View Description
View Description
....................................................................................................................................................................................................................................
View Description
Equipment View Description

View Types
There are three types of equipment views. The NE views, the board views, and the port
views.
Network Element View

The front side of an NE may be composed of several racks, containing several subracks.
Each subrack is composed of several slots containing boards.
The number of views related to an equipment depends on the NE type. Several types of
equipment are made only of one subrack, the rack view is not available when this
equipment is displayed.
An example of NE view is given in the following figure:
....................................................................................................................................................................................................................................
March 2010
View Description
....................................................................................................................................................................................................................................
Figure 1-4 Q3 NE view example.
This picture shows an NE subrack in which the different boards are represented.
Boards may be duplicated in an NE for equipment protection reasons, to avoid loss of
communications in case of equipment failure.
Some boards contain several ports used for transmission purposes and interconnections
between the different boards.
....................................................................................................................................................................................................................................
March 2010
View Description
....................................................................................................................................................................................................................................
The lock representation which appears over some boards (with the "Put in service"
command for Q3 NE), indicates that these boards cannot be removed because they are
involved in one of the following processes:
• Cross connection.
• Equipment protection.
• Multiplex section protection.
• Synchronization.
• NML assigned port.
To be able to remove one of this board (the lock, with the "Put out of service" command
for Q3 NE), you must first stop the running process in which it is involved. (Only the
unlocked boards can be removed with the "Remove" command for Q3 NE).
The NE view contains an alarm panel, a management states control panel and a message
area. They provide you with information needed to manage the network.
Icons in the top left-hand corner give information on the number and the severity of the
current alarms. Icons representing the management states are defined in the right side
view.
Note: Details on NE states and alarms relationship is given in the chapter “NE Alarms
and NE Status” (p. 1-29). For Transmission Alarm identification refer to chapter
“Procedures to handle Transmission Alarms” (p. 10-37).
Panel Description:
1. The Severity Alarm Panel.
The 1350 OMS EML provides an alarm functionality that informs the operator on the
severity of the different alarms in the NE as well as on the number of current alarms.
There are five different alarm severity levels.
In the 1350 OMS EML these different levels are associated with colors:
• Red: Critical alarm (CRI).
• Orange: Major alarm (MAJ).
• Yellow: Minor alarm (MIN).
• Cyan: Warning alarm (WNG).
• Blue: Indeterminate (IND).
Each alarm severity is represented by an alarm icon situated in the top left-hand
corner of the view. These alarm icons are constantly represented on the different
Equipment views (NE view, Board view, or Port view) so that the operator is always
aware of the alarms occurring in the system.
Furthermore the shape of the alarm icons in the alarm panel gives an indication of the
occurrence of alarms.
....................................................................................................................................................................................................................................
March 2010
View Description
....................................................................................................................................................................................................................................
The following figure describes different examples:
• An alarm icon with a circle inside it (and a number at the bottom of the icon)
indicates that alarms of the number and the type defined by the icon are occurring.
• An alarm icon with a rectangle inside indicates that no alarms of the type defined
by the icon are occurring.
• An alarm icon greyed out indicates that spontaneous incoming alarm notification
have been inhibited.
The Q3 NE view presents three or four other icons in the top right of the window.
These icons summarize the alarms per domain: Synchronization (SYNC), External
Point (EXTP for ADM only), Equipment (EQP) and Transmission (TRNS).
Since some synchronization alarms are counted as a communication alarm on a

synchronization object, it is counted one time in transmission alarm and one time in
synchronization alarm. The result is that the sum of the numbers in the domain icons
cannot correspond to the sum of the numbers displayed in the severity icons: the
severity alarm total number is always <= to the domain alarm total number.
2. The Management States Control Panel.
The different management states concerning the NE (see Q3 Generic NE Management
manual) are also represented by means of icons located in the right side of the
equipment views. These icons are:
• The SUP icon: The Supervision state indicates whether the NE is under OS
supervision.
• The ALI icon: The Alignment state indicates whether the NE and OS MIBs are
aligned.
• The icon with a key symbol: The Local Access state indicates whether the NE is
managed by a craft terminal or by the OS.
....................................................................................................................................................................................................................................
March 2010
View Description
....................................................................................................................................................................................................................................
•
The Q3 / COM icon: The Operational state indicates whether the communication
with the OS is established.
• The CTC icon: The Connected state indicates whether the NE is connected to local
Craft terminal.
• The NML / MGR icon: The Assignment state indicates whether the NE is assigned
to Network Management tasks.
• The NTP icon: The Network Time Protocol indicates whether the NTP
communication protocol is Enable (green frame) or Disable (brown frame).
• The SIM icon: The Simulator state indicates whether the Simulator is disabled
(green) or enabled (blue).
• The AC icon: The Abnormal Condition state indicates whether some abnormal
conditions have been recognized. The user can visualize them with the
Diagnosis—> Abnormal condition list command.
Position the cursor over one of the states icons, to display in the message area the
management state corresponding to the color displayed by this icon.
A color is applied to each management states icons. They give an indication of the
status of the NE. These colors may be configured.
As for the alarm icons, a rectangular management state icon represents the stable
state while a circular icon shape represents an unstable management state.
3. The Message area.
The information displayed in the message area depends on the mouse cursor location
within the view. It can give two main types of information:
• Information on the contents of the view, that is, board name, port name and so on.
This information depends on the type of view (NE view, Board view, or Port
view).
• Information on the control panel. Displays the visual information provided by the
icons in a written form.
....................................................................................................................................................................................................................................
March 2010
View Description
....................................................................................................................................................................................................................................
Board view
Each board that appears in the NE view has a particular detailed view concerning it. To
avoid representing all the views, only the general layout is described in this section using
a 2 Mbit tributary board view for a Q3 NE.
The following figures represent these board views.
Note: The control panel and the message area are identical to those in the NE view
and are not described again in this section.
....................................................................................................................................................................................................................................
March 2010
View Description
....................................................................................................................................................................................................................................
Figure 1-5 Example of a Q3 NE Board view.
The board view shows:

• The icon representation of the ports. There are as many icons as there are different
ports. In the above figure one type of ports is represented: a PDH port for the Q3 NE
board.
• An alarm probable cause information area which enable you to determine the
probable cause of the alarms occurring in the board. This area uses the alarm severity
color definition described previously to indicate the severity of the alarms occurring.
• Small alarm icon on a corner of the port icons that indicate the most critical alarm
occurring in the port. To get details on the alarms occurring in the ports, navigate to
the port view.
....................................................................................................................................................................................................................................
March 2010
View Description
....................................................................................................................................................................................................................................
Note: Some Q3-NE transmission alarms detected in the port view are not propagated
to the board view.
Port view
Navigation to the port views is explained in the Navigation Chapter.
The port view is the final view of the NE and shows in the most detail the composition of
the ports, in terms of the TPs that compose them.
To avoid representing all the different port views an STM1 optical port view (Q3 NE) is
used to underline the descriptions given hereafter.
The port view is represented in the following figure:
....................................................................................................................................................................................................................................
March 2010
View Description
....................................................................................................................................................................................................................................
Figure 1-6 Example of a detailed port view for Q3 NE.
The port views show:

• The signal processing functional blocks concerning the port.
These functional blocks are placed in the top part of the view. The acronyms situated
on each functional block identifies the specific operations undertaken by the
functional block.
• The Termination Points (TPs) associated with each type of port.
The TPs are placed under the functional blocks. The acronyms of the TPs identify the
type of TP. This helps to identify the type of signal that transits by the port.
....................................................................................................................................................................................................................................
March 2010
View Description
....................................................................................................................................................................................................................................
• A port functional state information message area.
This message area gives information on the Administrative state, the Protection state,
the Laser shutdown state and the Operational state of the port.
The information in the functional state message area may change from port to port.
For example, electrical ports do not have the Laser shutdown information and PDH
ports only have the NML assignment information.
• Small alarm icons placed next to the TP representations, and in the functional blocks,
indicate alarm occurrence. These alarm icons are identified by acronyms indicating
the probable cause of the alarm occurring.
These alarm icons use the alarm severity color feature to indicate the severity of the
alarm. The operator can therefore determine the type and severity of the alarm
occurring in a specific part of the port.
Note: The control panel and the message area are identical to those in the NE view
and are not described again in this section.
....................................................................................................................................................................................................................................
March 2010
Product Overview Open in Window command
Equipment View
....................................................................................................................................................................................................................................
Equipment View
Open in Window command

The Command
Navigating among different views may be performed either inside the same window, or
opening a new window. This is useful if you want to navigate to another view without
clearing the current view.
This operation can be carried out from Equipment views.
After selecting the desired element (board, port) from the current equipment view, select
the Open In Window option from the Views pull down menu as shown in the following
figure.
Figure 1-7 Opening a view in a window
The selected view is then displayed in a new window.

Note: Only three windows can be opened simultaneously. This option is not available
in the Port view.
....................................................................................................................................................................................................................................
March 2010
Product Overview NE Equipment views
Equipment View
....................................................................................................................................................................................................................................
NE Equipment views
The View
The NE symbols in the Network Topology views allow the user to open a detailed NE
view. It is then possible to navigate among the different NE Equipment views and to
access other management domains.
There are two types of NE Equipment views:
• The views that reflect the equipment structure on different levels namely Room view,
Equipment view with rack and subrack level, Board view and Port view. These views
follow a hierarchical order. From the access point Room view, the user has to navigate
through the various levels down to the destination view. On the other hand it is
possible to directly access the various levels via Equipment Overview. For W/OMSN
and WDM equipments the USM representation starts from the Equipment View at
rack level.
• The views providing specific information according to management domains i.e.:
Equipment Overview, Synchronization view and Transmission view. These views
are described in the Q3 NE Management section for Q3 NE equipments. They can be
directly accessed via Views menu.
Navigating to the Board View

The Board view can be opened from the subrack level of the Equipment view. To get
there, access the Room view via Views menu and then navigate through rack level of the
Equipment view by double-clicking on the relevant rack and subrack. Or select the
relevant board in the Equipment Overview (for OMSG only) and directly navigate to the
Board view.
There are two ways of opening a Board view from the subrack level of the Equipment
view:
• Via Views pull down menu.
• By double-clicking on the desired board.
If you use the menu option, click on the board you want to visualize. The contour is
highlighted in the view showing that the board is selected. Select the Open Object or
Open In Window option of the Views pull down menu.
The Board view is then opened.
....................................................................................................................................................................................................................................
March 2010
Equipment View
....................................................................................................................................................................................................................................
Figure 1-8 Example of a Board view for a Q3 NE.
Navigating to the Port View

The Port view can be opened from the Board view. To get there, access the Room view
through Views menu and then navigate through rack level and subrack level of the
Equipment view by double-clicking on the relevant rack, subrack and board. Or select the
relevant port in the Equipment Overview and directly navigate to the Port view. For
W/OMSN and WDM equipments the USM representation starts from the Equipment
View at rack level and the board view is opened through the previous to the Board view
navigation.
From the Board view you can access a specific Port view by double-clicking on the
desired board.
....................................................................................................................................................................................................................................
March 2010
Equipment View
....................................................................................................................................................................................................................................
Figure 1-9 Selecting a specific port view of a Q3 NE Board View.
....................................................................................................................................................................................................................................
March 2010
Equipment View
....................................................................................................................................................................................................................................
Figure 1-10 Example of a Q3 NE Port View.
Navigating to Management menu commands

These views are described in the Q3 NE Management section for Q3 NE equipments.
....................................................................................................................................................................................................................................
March 2010
Product Overview NE Alarms
....................................................................................................................................................................................................................................
NE Alarms
Description
This section describes the types of alarms defined for 1350 OMS EML Subsystem, in
terms of severity levels, and the way they are propagated through the different Equipment
views (NE, Board or Port views).
Five different alarm severity levels are provided by the 1350 OMS EML:
• Critical (CRI)
• Major (MAJ)
• Minor (MIN)
• Warning (WNG)
• Indeterminate (IND)
These levels are represented with different colors. They enable you to know the severity
of the current alarms occurring in the Equipment.
Propagation
In all the equipment views, small icons synthetically summarizing the alarms occurring in
these different entities, are represented next to the Board or Port entities themselves. The
"Transmission" alarms, related to the received information stream, are recognized on the
TP points of the boards but are not signaled on the synthesis small icon alarm of the Q3
NEs board. To find out the board with the occurred transmission alarm the user can open
the AS applicative selecting "Diagnosis—>Alarms—>Transmission Alarms menu option
in the USM menu commands. Then, after reading the listed physical board indications,
come back to the USM, select the board, and open the Port view to check the previous
transmission alarms.
These icons have the following characteristics:
• Colour: enables you to determine the severity of the alarm occurring (critical,
major,...) in the board or port. This functionality enables a rapid diagnosis and
navigation to the views where the source of the problem lies.
• Aspect: inside the icon either a "-" is drawn, in which case no alarm is occurring in the
entity, or a "x" sign is drawn, in which case alarms are occurring in the entity.
Using these two characteristics that are depicted in Figure 1-11, “Alarm representation in
the Equipment views.” (p. 1-30), you can determine the existence of alarms in the entities
you manage.
....................................................................................................................................................................................................................................
March 2010
Product Overview NE Alarms
....................................................................................................................................................................................................................................
The figure below shows:
• A section of a NE view with some boards defined and the alarm icon below the board
representations.
• A section of a Board view with a port defined and the alarm icon next to the port
representation.
• A section of a Port view with the alarm icons drawn next to the subunits composing
the port.
Figure 1-11 Alarm representation in the Equipment views.
....................................................................................................................................................................................................................................
March 2010
Product Overview NE Status
....................................................................................................................................................................................................................................
NE Status
Description
In the Network topology views, each NE composing the Telecommunication Network is
associated with a status that is related to its functional state. This section describes the
relationship between the different NE statuses, the NE management states and the alarm
severities. Furthermore, the propagation of the statuses through the hierarchy of views is
described.
The status of the NE is displayed on the Network Topology views graphical interface
using colors. The color of an NE indicates its status.
The different NE statuses are:
• Critical.
• Major.
• Minor.
• Warning.
• Restricted.
• Disabled.
• Unknown.
• Normal.
The NE status is a function of its alarm severity (listed in paragraph “NE Alarms”
(p. 1-29)), its alignment state, its operational state and its supervision state. Details on NE
states are given in the chapter “Management States” (p. 6-3).
Note: The "–" sign signifies that the value of this state does not impact on the final
NE status.
The relationships between the NE statuses and these different states are represented in the
tables that follow:
1. Critical NE status.
A NE status is critical if the NE operational state is disabled, or, if it presents a critical
alarm status and no other dysfunctions.
NE Status Alarm NE Alignment NE Operational NE Supervision

Status state state State
CRITICAL - - Disabled Supervised
Critical In configuration Enabled Supervised
Critical Aligned Enabled Supervised
2. Major NE status.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
A NE status is major if the OS and NE MIBs are misaligned, or, if the NE presents
major alarms and no other dysfunctions.

MAJOR - Misaligned Disabled Supervised
Major In configuration Enabled Supervised
Major Aligned Enabled Supervised
3. Minor NE status.
A NE status is minor if the NE presents minor alarms and no other dysfunctions.

MINOR Minor In configuration Enabled Supervised
Minor Aligned Enabled Supervised
4. Warning NE status.
A NE status is warning if alarms are either warning, indeterminate or cleared and the
alignment state in configuration, or, if the alarms are warning and no other
dysfunctions present.
NE Status Alarm Status NE Alignment NE Operational NE Supervision

state state State
WARNING Warning, In configuration Enabled Supervised
Indeterminate,
Cleared
Minor Aligned Enabled Supervised
5. Restricted NE status.
A NE status is restricted when it is currently undergoing operations (aligning MIB or
activating/de–activating Supervision). This means that no other operations can be
carried out on the NEs until the operations are completed.
NE Status Alarm Status NE Alignment NE NE

state Operational Supervision
state State
RESTRICTED - - - Activating/
Deactivating
- Aligning Enabled Supervised
6. Disabled NE status.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
A NE status is disabled when the NE is just declared.

state State
DISABLED - - - Declared
7. Unknown NE status.
A NE status is unknown if the alarms are indeterminate (meaning that the OS has not
received an update of the current alarms occurring) and no other dysfunctions are
present in the NE.

state State
UNKNOWN Indeterminate Aligned Enabled Supervised
8. Normal NE status.
This occurs when all the alarms are cleared and the NE is functioning correctly.

state State
NORMAL Cleared Aligned Enabled Supervised
A color is associated to each of these NE statuses. The default colors set are listed below:
• Critical : Red
• Major : Orange
• Minor : Yellow
• Warning : Cyan
• Restricted : Tan
• Disabled : Dark brown
• Unknown : Blue
• Normal : Green
The alarm status propagation and the modification of the default alarm severity is
described in the chapter “Alarm Severity Assignment Profile for OMSN” (p. 10-45).
....................................................................................................................................................................................................................................
March 2010
Product Overview Overview
....................................................................................................................................................................................................................................
Overview
Purpose
The Help is an important aspect of the 1350 OMS EML product. Using this functionality
you can get information on actions you are carrying out or on any particular topic linked
to the 1350 OMS EML.
Contents
Help on MS-GUI Framework 1-35

Help Activation 1-36
Help on context 1-37
Glossary 1-38
....................................................................................................................................................................................................................................
March 2010
Product Overview Help on MS-GUI Framework
....................................................................................................................................................................................................................................
Help on MS-GUI Framework

Description
The MS-GUI framework defines the following different functions for the help on line
support:
• contextual help pages linked to the product documentation;
• tooltips for menu items, buttons and input field;
• wizard information field, dynamically filled according with the cursor position on the
windows;
• “What’s this” function that, activated on request, allows selecting a target item on the
active window.
....................................................................................................................................................................................................................................
March 2010
Product Overview Help Activation
....................................................................................................................................................................................................................................
Help Activation
Description
The Help application is activated from Web Desktop home page selecting the HELP link
on the right corner of the window. A page is displayed with the available 1350 OMS
documentation library where you can find the information needed.
....................................................................................................................................................................................................................................
March 2010
Product Overview Help on context
....................................................................................................................................................................................................................................
Help on context
Contextual Help
To access the on line context sensitive help you can either:
• Press on the F1 key placed on top of the keyboard to get help on the active window.
• Select the On Context option from the Help pull down menu to get help on the
relevant application window.
• Click the Help push button from any window.
The advantage of the help on context using push buttons is that it directly brings up the
help that applies to the actual context you are in. For example, in a dialogue box
concerning the creation of a network element symbol, clicking the Help push button
opens a help window giving information on this action.
....................................................................................................................................................................................................................................
March 2010
Product Overview Glossary
....................................................................................................................................................................................................................................
Glossary
Find the Glossary
This help option enables you to display the 1350 OMS EML on-line glossary.
To access the 1350 OMS EML Glossary, select the Glossary option from the Help pull
down menu.
....................................................................................................................................................................................................................................
March 2010
2 Alarm Management
2
Overview
Purpose
The functionality is provided by the Alarm Surveillance (AS) application. This
management functionality provides efficient mechanism to control, supervise and manage
equipment anomalies that may occur in a Telecommunication Network. It covers
provision of information concerning alarm surveillance, and alarm management such as
displaying alarm lists and acknowledging alarms.
Contents
AS Overview 2-3
Alarm Information 2-3
Alarm Surveillance Functionalities 2-4
Current Alarm Management 2-5
Historical Alarm Management 2-6
An Iterative Approach for Alarm Description 2-7
Alarm Management 2-8
Access AS 2-8
Reserving/Unreserving Alarms 2-9
Acknowledging Alarms 2-12
Manually Purging an Alarm 2-14
Manually Clearing an Alarm 2-15
Exporting and Printing (Output...) an Alarm 2-16
Navigations 2-20
Navigation to/from Alarm Surveillance 2-20
Alarm Debouncing 2-25
...................................................................................................................................................................................................................................
March 2010
Alarm Management Overview
....................................................................................................................................................................................................................................
Function Description 2-25

Alarm Debouncing Management 2-26
....................................................................................................................................................................................................................................
March 2010
Alarm Management Alarm Information
AS Overview
....................................................................................................................................................................................................................................
AS Overview
Alarm Information
Description
Alarms consist in messages emitted by network resources that have detected problems or
failures in the network. Information contained in the alarm belongs to two classes:
• Resource identification.
• Type Identification.
Resource Identification: Identifies the resource which has raised the alarm. The
information is:
• The resource type.
• The resource name which has to be unique ( Full Distinguished Name) in order to
avoid identification ambiguities.
Type Identification: Identifies the type of the problem the alarm refers to. The kind of
problem regroups three basic elements of information:
• The problem type belonging to following list:
• Quality of service.
• Communications.
• Processing error.
• Equipment.
• Environmental.
• The probable cause of the problem, which belongs either to standard probable cause
values (ITU–T Recommendation X.733), or locally defined values.
• The severity level of the problem ( Alarm Perceived Severity) when the alarm is
raised.
Malfunctions are ranked into five severity levels:
– Critical when it is no longer possible to provide the service you have requested.
– Major.
– Minor.
– Warning which means no impact is reported upon the quality of service offered to
you.
– Indeterminate, if the severity level cannot be defined by the resource which raises
the alarm.
Note: A particular severity level (Cleared) is used when the alarm is cleared by the
resource which has raised it before.
....................................................................................................................................................................................................................................
March 2010
Alarm Management Alarm Surveillance Functionalities
AS Overview
....................................................................................................................................................................................................................................
Alarm Surveillance Functionalities

Description
The AS application is dedicated to receive, store, display and manage in real time alarms
(current alarms) raised by different sources, facilitating the overall alarm surveillance of
the network, and improving the reaction time of the network users in case of anomalies in
the network. It also provides the possibility to archive and retrieve the alarms, the called
historical alarms, allowing post–analysis of anomalies in the network.
The alarms, current and historical, can be displayed in lists. By mouse clicking, you can
get detailed information, or perform action on the alarm when the alarm is raised.
In the current alarm case, a synthesis of alarm information can be displayed in submap.
This alarm information is displayed for each NE present within the submap.
....................................................................................................................................................................................................................................
March 2010
Alarm Management Current Alarm Management
AS Overview
....................................................................................................................................................................................................................................
Current Alarm Management

Description
This section describes how to supervise the network activity to interfere with the network
in order to take anomalies into account and solve them.
Raised Alarm: When an alarm is raised by a faulty resource, it is received by Alarm
Surveillance which stores it. The alarm can be displayed as soon as it is signalled.
Displayed Alarm: The alarm is displayed on the screen, the basic information is
immediately available to the user who can decide:
• To get detailed information contained in the alarm.
• To reserve the alarm for further exclusive investigation. This action of reservation on
the alarm prevents other users to perform any action on the alarm.
• To request the creation of a trouble ticket
• To acknowledge the alarm, indicating that the cause of the alarm has been taken into
account, and that repair actions have been launched.
• To let other user take it into account.
During the whole period an alarm is considered to be current (alive), its state is
permanently real–time refreshed so that any user who displays this alarms knows the
actual state of the alarm.
Cleared Alarm: The alarm is cleared by the emitting resource as soon as the problem is no
longer present at resource level.
• As soon as the alarm is acknowledged by the user, it is no longer considered as a
current alarm. The alarm is removed from the current alarm set and is archived into
the set of historical alarms.
• The problem the alarm is linked to may not be solved immediately. In such a case the
alarm is repeated until the problem is solved. AS associates a repetition counter to
each received alarm. If the alarm is not cleared by the resource which raised it, then
AS offers the possibility to archive it manually on user's request.
Note: A single anomaly in the network may cause the raising of several alarms; it may
also generate other anomalies or dysfunctions that raise additional alarms. These
alarms, called correlated alarms may be marked as linked to each other.
....................................................................................................................................................................................................................................
March 2010
Alarm Management Historical Alarm Management
AS Overview
....................................................................................................................................................................................................................................
Historical Alarm Management

Description
Once alarms are no longer considered as current alarms, they are archived in the historical
Alarm section of the AS application, where they can be consulted.
A consultation of historical alarms is generally performed in four steps:
Extracting the required alarm list from the repository or from personal files. The user is
requested to specify filtering criteria in order to extract only useful part of the alarms.
These alarms are stored in a main alarm list.
Creating sublists from the main alarm list.
Opening the alarm sublists. The user can get basic information on the alarms including
the date of the archiving and the reason.
Getting detailed information on a particular alarm.
The historical part of the Alarm Surveillance is particularly useful to follow the activity of
a network, its robustness, the recurrence of the problems, or to help the user to dimension
the network and detect its critical points.
....................................................................................................................................................................................................................................
March 2010
Alarm Management An Iterative Approach for Alarm Description
AS Overview
....................................................................................................................................................................................................................................
An Iterative Approach for Alarm Description

Approach
Alarm Surveillance offers a window divided in three panels for viewing the alarms :
• The Counter Summary panel : Main window used to display statistics on alarms. It
shows alarm counters, according to severity levels or statuses of the alarms.
• The Alarm Sublist panel : The sublist is a basic working window. It regroups alarms
according to filtering criteria defined by the user, and allows to work on a limited
subset of alarms.
• The Sublist Display panel : It displays all the alarms according to the sublist selected
by the user and allows working on these alarms.
Figure 2-1 Iterative Approach for Alarm Description
....................................................................................................................................................................................................................................
March 2010
Alarm Management Access AS
Alarm Management
....................................................................................................................................................................................................................................
Alarm Management
Access AS
Start Alarm Surveillance
To access this management functionality, follow from Web Portal application the path
Operation > Alarms > Alarms (Selected_Instance).
The Alarm Management window opens. The window provides the user with all the
available sublists informing the user about the status of the network in terms of alarm, as
shown in following figure.
Figure 2-2 Alarm Surveillance Window
....................................................................................................................................................................................................................................
March 2010
Alarm Management Reserving/Unreserving Alarms
Alarm Management
....................................................................................................................................................................................................................................
Reserving/Unreserving Alarms
When to use
To ensure to be the only one responsible for an alarm (or a group of alarms), the user can
perform the reservation action on alarms.
Related Information
Related Information can be found in “Alarm Management” (p. 2-8)
Before you begin

Display the alarm list in the Fault Management application.
Task
To reserve one or several alarms:
...................................................................................................................................................................................................
1 Select the alarm in the alarm list.

...................................................................................................................................................................................................
2 Use the menu path: Alarm > Reserve.
....................................................................................................................................................................................................................................
March 2010
Alarm Management
....................................................................................................................................................................................................................................
Figure 2-3 Alarm Reservation
The Reservation Status changes from NRSV to RSV as shown in the figure.
Figure 2-4 Alarm reserved
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Alarm Management
....................................................................................................................................................................................................................................
Unreserving Alarms
To unreserve one or several alarms:
...................................................................................................................................................................................................
1 Select the alarms.

...................................................................................................................................................................................................
2 Use the menu path: Alarm > Unreserve.
Figure 2-5 Unreserve Alarms
The Reservation Status changes from RSV to NRSV.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Alarm Management Acknowledging Alarms
Alarm Management
....................................................................................................................................................................................................................................
Acknowledging Alarms
When to use
Use this task to take one or more alarms into account to investigate them.
Related information
Before you begin

Task
By acknowledging a single or a group of selected alarms in the Alarm Sublist window, the
user notifies he is taking them into account.
To acknowledge one or several alarm(s):
...................................................................................................................................................................................................
1 Select the alarm(s).

...................................................................................................................................................................................................
2 Use the menu path: Alarm > Acknowledge.

A confirmation is required.
....................................................................................................................................................................................................................................
March 2010
Alarm Management Acknowledging Alarms
Alarm Management
....................................................................................................................................................................................................................................
Figure 2-6 Acknowledging Alarms
The status of the selected alarm(s) changes in the Ack. Status column from NACK (not
acknowledged) to ACK (acknowledged).
Figure 2-7 Ack. Status change
Acknowledging a cleared alarm is an implicit archiving action. Thus, in this case the
acknowledgement will archive the alarm and cause the disappearance from the list.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Alarm Management Manually Purging an Alarm
Alarm Management
....................................................................................................................................................................................................................................
Manually Purging an Alarm

When to use
Use this task to manually purge an alarm.
Related information
Before you begin

Task
To manually purge one or several alarm(s) of the Alarm Sublist window:
...................................................................................................................................................................................................
1 Select the alarm(s).

...................................................................................................................................................................................................
2 Use the menu path: Alarm > Manual Purge...

The purged alarm(s) disappear from the sublist, or main list, and are archived, if matching
the archiving filter.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Alarm Management Manually Clearing an Alarm
Alarm Management
....................................................................................................................................................................................................................................
Manually Clearing an Alarm

When to use
Use this task to set the alarm status to cleared.
Related information
Before you begin

Task
When Alarm Clear Event is never received from an alarm agent, an AS operator is
authorized to clear manually this kind of alarm. AS can be informed about this kind of
alarm either by the alarm agent or by AS off–line configuration. To manually clear one or
several alarm(s) of the Alarm Sublist window:
...................................................................................................................................................................................................
1 Select the alarm(s) whose alarm status must be Clearable.

...................................................................................................................................................................................................
2 Use the menu path: Alarm > Manual Clear...

A confirmation dialog box opens.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Alarm Management Exporting and Printing (Output...) an Alarm
Alarm Management
....................................................................................................................................................................................................................................
Exporting and Printing (Output...) an Alarm

When to use
Use this task to export the alarm in a format that can be saved or printed.
Related information
Before you begin

Task
The content of a sublist can be exported to a file or sent to a printer as well as the content
of a single alarm. In both cases the user will be requested to fill the Output dialog box
with the desired parameters.
To export a part or the whole Alarm Sublist:
...................................................................................................................................................................................................
1 Select one or several alarm(s).

...................................................................................................................................................................................................
2 Use the menu path: File > Export...

The output window is:
....................................................................................................................................................................................................................................
March 2010
Alarm Management
....................................................................................................................................................................................................................................
Figure 2-8 AS Output window
The user can change the default options, exporting the alarms to an ASCII file or
using a specific print command. To activate either the Print or the Export field.
...................................................................................................................................................................................................
3 The Export field should be filled with a file name:

• specify in the field the name of the file.
• use the Choose File push button. The File Chooser dialog box opens and allows the
user to browse the existing file. The use can select a file from the list which will be
overwritten or specify a file name.
....................................................................................................................................................................................................................................
March 2010
Alarm Management
....................................................................................................................................................................................................................................
Figure 2-9 File Chooser dialog box
The exported information concerns only the attributes displayed in the sublist.
...................................................................................................................................................................................................
4 To print a part or the whole Alarm Sublist:

• Select one or several alarm(s)
• Use the menu path : File > Print ...
The output window is
....................................................................................................................................................................................................................................
March 2010
Alarm Management
....................................................................................................................................................................................................................................
To activate either the Print field, click on the radio button beside the field. Then fill the
field with data corresponding to the selected type of export (printer or ASCII file).
The user is requested to fill the Print field with a user command:
• keep the default command
• develop a print command that handles as a parameter the name of the temporary
formatted file generated by AS. This file is not accessible and AS application should
execute the user command.
The exported information concerns only the attributes displayed in the sublist.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Alarm Management Navigation to/from Alarm Surveillance
Navigations
....................................................................................................................................................................................................................................
Navigations
Navigation to/from Alarm Surveillance

When to use
Use this task to navigate from and to Alarm Surveillance to and from other applications.
Related information
Before you begin

Task
It is possible from other applications to navigate towards AS application.
...................................................................................................................................................................................................
1 From Multi Service GUI, selecting a NE and the menu item Search > Show NE Alarms,
the EML-AS is displayed listing the alarms for the selected NE.
....................................................................................................................................................................................................................................
March 2010
Navigations
....................................................................................................................................................................................................................................
Figure 2-10 Navigation from NE list to AS
....................................................................................................................................................................................................................................
March 2010
Navigations
....................................................................................................................................................................................................................................
Figure 2-11 Alarm Sublist for selected NE
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Navigations
....................................................................................................................................................................................................................................
Task
It is possible from AS application to navigate towards the NE USM.
...................................................................................................................................................................................................
1 From Alarm Surveillance select Navigation > External Application > Related_EmlUsm
the NE USM is displayed listing the alarms for the selected NE.
Figure 2-12 Navigation to NE USM
The NE USM is displayed.
....................................................................................................................................................................................................................................
March 2010
Navigations
....................................................................................................................................................................................................................................
Figure 2-13 NE USM
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Alarm Management Overview
Alarm Debouncing
....................................................................................................................................................................................................................................
Alarm Debouncing
Function Description
Introduction
SNMP and Q3 NE Management is improved with an alarm filtering in the time–scale of
several seconds to minutes (ca. 30 seconds to 4–5 minutes).
Each filter is identified by a probableCause and its holdPeriod and configured by the
Alarm Debouncing GUI. The Alarm De–bouncing GUI produces a filtering configuration
file and EML–IM will be alerted, as soon as the file is updated, to re–read the file.
EML–IM (Q3 and SNMP), by using the filtering configuration file, will apply this
filtering mechanism to alarm notifications before sending alarms to Upper Managers:
• When a clear notification is received and it falls in a filter criteria (e.g. probableCause
of clear notification has filter enabled), the clear notification is frozen and not
forwarded, and a timer is activated for the holdPeriod.
• If a raise notification, with the same MOC, MOI, ProbableCause, SpecificProblem,
EventType of clear notification, is received before the holdPeriod is exhausted, the
frozen clear notification is discarded, the timer is removed, and the raise notification
is forwarded.
• Instead, if no raise notification is received before the holdPeriod is exhausted, on
timer expiration the frozen clear notification is forwarded.
The default configuration is no filter activated. The maximum number of activable filters
is 1000.
....................................................................................................................................................................................................................................
March 2010
Alarm Management Alarm Debouncing Management
Alarm Debouncing
....................................................................................................................................................................................................................................
Alarm Debouncing Management

When to use
Use this task to filter alarm in the time–scale of several seconds to minutes (ca. 30
seconds to 4–5 minutes)
Related information
Before you begin

Task
...................................................................................................................................................................................................
1 The Alarm Debouncing parameters can be configured during the system configuration of
an EMLIM. The parameters are provided in the Parameters Definition window as shown
in the following figure
....................................................................................................................................................................................................................................
March 2010
Alarm Debouncing
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
Alarm Debouncing
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Edit the values and Push the Apply button to confirm the inserted data.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
3 3vent and Alarm Log
E
Browser
Overview
Purpose
This section describes the main functionalities of ELB (Event Log Browsing) tool, which
provides a way to browse Event Log and Alarm Log for different types of NEs: Q3 and
SNMP Network Elements. ELB displays the events in a clear form for the operator,
retrieves records from NE using some filter and has the possibility to export, print and
print preview Log Records.
Contents
ELB Application 3-2

Event Log Browser 3-2
ELB Graphical User Interface 3-5
Introduction 3-5
Menu Bar 3-8
Tabbed Panes 3-13
Filter Management 3-19
Filters for ELB Application 3-19
...................................................................................................................................................................................................................................
March 2010
Event and Alarm Log Browser Event Log Browser
ELB Application
....................................................................................................................................................................................................................................
ELB Application
Event Log Browser

Application Overview
ELB (Event Log Browsing) tool provides a way to browse Event Log and Alarm Log for
different types of NEs: Q3, SNMP and TL/1 NEs. ELB displays the events in a clear form
for the operator, retrieves records from NE using some filter and has the possibility to
export, print and print preview Log Records.
Figure 3-1 ELB Application
The ELB application can start from the EML USM application. The EML USM is started
from Multi Service GUI as shown in the figure below:
....................................................................................................................................................................................................................................
March 2010
ELB Application
....................................................................................................................................................................................................................................
Figure 3-2 Show equipment activation
Select the NE in the Get All NE list, select the path Search > Network Element > Show
Equipment or from popup menu Search > Show Equipment, the corresponding NE
USM opens.
Select Diagnosis > Log Browsing > Alarm Log for Alarm and Diagnosis > Log Browsing
> Event Log for Event in the Diagnosis menu of the EML USM application as show in
figure below:
Figure 3-3 Navigation from EML USM to ELB
ELB starts with a temporary Loading Window, before showing ELB Main View.
....................................................................................................................................................................................................................................
March 2010
ELB Application
....................................................................................................................................................................................................................................
Figure 3-4 Loading Dialog
ELB can process one request a time. If a new NAV message arrives when ELB is already
processing a request, a Message Dialog box appears.
Figure 3-5 NAV Message Information Dialog
....................................................................................................................................................................................................................................
March 2010
Event and Alarm Log Browser Introduction
....................................................................................................................................................................................................................................
Introduction
Description
The ELB GUI displays a window with the following main areas:
• Title Bar.
• Menu Bar.
• Status Bar.
• Tabbed Panes: Alarm Log Display and Event Log Display with tables containing one
row per log item.
The table supports sorting, column reordering and column exclusion.
Alarm log items are coloured according to associated severity.
• A log item detail panel; this panel displays additional information that could not fit
into the basic table–based display.
• A filter panel. Filtering is possible on the standard fields of the table; it is not possible
on the additional information fields.
The ELB window dimension is set according to the dimension of the screen where the
application is running.
The operator can change the dimension of ELB window with the usual mouse actions.
Following pictures show the Log Browsing GUI for Alarm and Event Log display in ELB
application.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 3-6 Alarm Log Display selected
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 3-7 Event Log Display selected
....................................................................................................................................................................................................................................
March 2010
Event and Alarm Log Browser Menu Bar
....................................................................................................................................................................................................................................
Menu Bar
Description
The Menu Bar contains five menus and has a platform–dependent location along the top
of the window. Every Menu displays a popup menu when activated.
A popup menu is a menu that is invisible until the user makes a platform–specific mouse
action, such as pressing the right mouse button, over a popup–enabled component. The
popup menu then appears under the cursor.
Figure 3-8 Menu Bar
File Menu
The File popup menu is composed by a submenu and three menu items.
Figure 3-9 File Menu
Export
ELB provides the possibility to export log items to a file with a specific format.
The export formats are:
• CSV: Comma Separated Value (Excel format).
• HTML with two different types: text file or table.
• PDF.
• PS.
• XML.
• TXT.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
After choosing the file format, ELB shows an Export Dialog with a default export file
name that depends on the current Display, Alarm or Event, and on a default repository
folder (export in the example), which is set in a configuration file.
Figure 3-10 Export Dialog
If the export operation has succeeded, ELB displays the information about path and name
of the exported file in a dialog box.
Figure 3-11 Export Successful Information Dialog
If the export operation fails, ELB returns an error message. The message depends on the
kind of problem that occurred.
This error message is displayed if the inserted directory is not accessible or
write–protected.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 3-12 Write protected error message
This error message is displayed if ELB has problem with an internal library that converts
XML file with XSL style in desired format file.
Figure 3-13 Export Failed Error Message
Print
ELB provides the possibility to print log items in PDF format only.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 3-14 Print Dialog
The Print Dialog allows to choose the Printer and set the Print range and Copies number.
If for any reason print operation fails, ELB displays an error message
Figure 3-15 Print Failed Error Message
Print Preview
ELB provides the possibility to preview log items in PDF format only.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 3-16 Print Preview Dialog
Print Preview Dialog allows to scroll all log items in PDF format, page by page, to chose
Print or Reload operation and to set the preferred View format.
If print preview operation fails, ELB gives back to operator an error message.
Figure 3-17 Print Preview Error Message
....................................................................................................................................................................................................................................
March 2010
Event and Alarm Log Browser Tabbed Panes
....................................................................................................................................................................................................................................
Tabbed Panes
Description
Two ELB components share the same space on screen: Alarm Log Display and Event Log
Display. Only one display is visible at a time. The user chooses which component view by
selecting the tab corresponding to the desired Display.
Figure 3-18 ELB Tabbed Panes
Alarm Log Display

If an USM navigation requires a Log Browsing Alarm Log, the ELB window is activated
and displayed, presenting the Filters Dialog for Alarm Log on top of the empty ELB Main
View (which by default presents the empty Event Log Display).
Initially the menu items are disabled: the operator must set the filters configuration to
continue.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 3-19 Alarm Log request Start Up
After setting the desired filters configuration, the event log application starts uploading
Data Items from the Network Element. A Progress Dialog appears above of the Main
View of ELB that initially is empty.
The Progress Dialog shows with a numeric index in the Title Bar and with an animation
in the figure, the collection of Items by ELB.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 3-20 Progress Dialog
When the Alarm Log collection is completed, all Items are shown in the ELB Main View
that has switched on Alarm Log Display automatically.
Every item assumes a colour according to his Perceived Severity, so the Alarm Log Table
results to be a multicoloured table.
Table 3-1 Alarm severity and colour
Severity Number Severity String Severity Colour

1 CRITICAL Red
2 MAJOR Orange
3 MINOR Yellow
4 WARNING Cyan
5 CLEARED Green
0 INDETERMINATE White
An operator can also switch to Alarm Log Display from Event Log Display by clicking
on tabbed pane.
Alarm Log Display reports data of last Alarm Log navigation on considered NE.
Alarm Log Display is empty if no navigation required a Log Browsing Alarm Log on this
NE yet.
The operator can require a new Alarm Log navigation by selecting Filters Menu.
If an USM navigation requires a Log Browsing Alarm Log for a different NE, ELB clears
current Alarm Log Display (as well as Event Log Display) and prepares to show new
Alarm Logs (Event Log Display remains empty).
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 3-21 Alarm Log Display
Alarm Log Display has eight columns by default.

The number of rows depends by the number of Alarm Log Items read by ELB from NE:
every row is an Alarm Log Item of the NE.
• Event Time and Date: date and time of the alarm occurrence. The format of Data and
Time is: yyyy/mm/dd hh:mm:ss.
• Perceived Severity: indication of the severity of the alarm occurrence. The possible
severities are six and every severity is associated to a specific colour. The Perceived
Severity of the alarm occurrence determines the colour of the whole row of the Alarm
Log Display.
• Event Type: type of the alarm event occurrence defined in the Optics–IM Model.
• Notification ID: a unique identifier for the alarm.
• Managed Object Class: is the class of the object that emitted the alarm, as defined by
the Optics–IM Model.
• Managed Object Instance: is the instance of the managed object class.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
• Probable Causes: is an attribute of the alarm event occurrence defined in the
Optics–IM Model.
• Specific Problem: is an attribute of the alarm event occurrence defined in the
Optics–IM Model.
Event Log Display

If an USM navigation requires a Log Browsing Event Log, the ELB window is activated
and displayed, presenting the Filters Dialog for Event Log on top of the Main View of
ELB that initially is empty.
Initially the menu items are disabled: the operator must set the filters configuration to
continue.
Figure 3-22 Event Log request Start Up
After setting the desired filters configuration, ELB starts to upload Data Items from the
Network Element. The Progress Dialog appears above the empty Event Log Display.
When the Event Log collection is completed, all Items are shown in Event Log Display.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 3-23 Event Log Display
The operator can also switch to Event Log Display from Alarm Log Display by clicking
on tabbed pane.
Event Log Display reports data of last Event Log navigation on considered NE.
Event Log Display reports data of last Event Log navigation on considered NE. Event
Log Display is empty if no navigation requires a Log Browsing Event Log on this NE yet.
The operator can require a new Event Log navigation by selecting Filters Menu.
If an USM navigation requires a Log Browsing Event Log for a different NE, ELB clears
current Event Log Display (as well as Alarm Log Display) and prepares to show new
Event Logs (Alarm Log Display remains empty).
....................................................................................................................................................................................................................................
March 2010
Event and Alarm Log Browser Overview
Filter Management
....................................................................................................................................................................................................................................
Filter Management
Filters for ELB Application

Filtering Description
The retrieval of Events and Alarms Log is managed using filters to make the analysis
easier.
The filter selection operation is performed every time that a NAV Message arrives, at
application start–up, or by explicitly activating the Filters Menu item.
For Q3 NE events and alarms log, the filter can be applied to log retrieve operation, for
SNMP NE this is not possible due to protocol restrictions. The filtering for SNMP log is
performed by ELB application on the totality of log data retrieved from NE.
For some fields, the user must choose a value from predefined lists, these are:
For alarms:
• Probable causes.
• Alarm type.
• Alarm severity.
For events:
• Event type.
Following figure shows the Filter Dialog for event. The dialog allows setting the filters to
apply during the retrieval of event items.
....................................................................................................................................................................................................................................
March 2010
Event and Alarm Log Browser Filters for ELB Application
Filter Management
....................................................................................................................................................................................................................................
Figure 3-24 Event Log Filters Dialog
Following figure shows the Filter Dialog for alarms. The dialog allows selecting the
filters to apply during the retrieval of alarm items.
....................................................................................................................................................................................................................................
March 2010
Filter Management
....................................................................................................................................................................................................................................
Figure 3-25 Alarm Log Filters Dialog
At application start–up the Filter Dialog is clear, without any selection.
Filtering Criteria
The applicable filters are displayed in the Filters Dialog. The selected filters can be zero
or more of the possible filters.
The global condition defining the filter is built by applying an AND operator between the
elementary conditions defined by groups. When, inside a group, a list offers multiple
selections for an attribute, the condition on this attribute results from an OR on different
selected values.
For example, Figure 55 shows the logical tree corresponding to the filter selection of
Figure 56.
Suppose you are on October 17th 2003 16:27:28 and you want to filter for Alarm Logs
with Equipment or Quality of Service Alarms, that occurred after October 17th 2003
16:21:19 and before November 17th 2003 16:21:19, whose perceived severity is major,
....................................................................................................................................................................................................................................
March 2010
Filter Management
....................................................................................................................................................................................................................................
minor or cleared, and that have five types of probable causes, Call Set Up Failure, or
Clock Data Recovery Unlock, or Commercial Power Failure, or Common Loss Alarm, or
Communications Protocol Error.
The filter can be expressed as follows:
Figure 3-26 Example of Logical Operators in Alarm Log Filters Dialog
To activate or deactivate one of the groups (e.g. Event Type), you have to click the check
button of the zone. If you deactivate one of the groups, his panel becomes greyed.
The following paragraphs detail the operations for the different groups.
Filter Selection
The filter selection window displays all available filters. The last filter selection
performed is proposed; this selection can be confirmed or reset using a dedicated button
on the window. The selected combination of filters is displayed in the ELB application
window to be remembered consulting the list.
Following figure shows the Filter Dialog with selected filters for Alarm.
....................................................................................................................................................................................................................................
March 2010
Filter Management
....................................................................................................................................................................................................................................
Figure 3-27 Selected filters for Alarm Filters Dialog
Following figure shows the Filter Dialog with selected filters for Event.
....................................................................................................................................................................................................................................
March 2010
Filter Management
....................................................................................................................................................................................................................................
Figure 3-28 Selected filters for Event Filters Dialog
Filter Dialog
The filter is defined through a panel composed of several groups: the Filter Dialog.
Filter Dialog is different for Alarm Log and Event Log.
The filters defined for Alarm Log are:
• Event Type for alarm.
• Event Time.
• Perceived Severity.
• Probable Causes.
The filters defined for Event Log are a subset of Alarm Log filters:
• Event Type for event.
• Event Time.
....................................................................................................................................................................................................................................
March 2010
4 4350 OMS EML Graphical
1
User Interface
Overview
Purpose
The EML MultiService-GUI is the specialization of the MS-GUI for the EML
sub-system. The MS-GUI framework is the reference graphic environment for the
1350OMS. The EML MS-GUI rendered is connected with the TM Server, which
translates data object, actions and results according with the system model managed by
the PNM-IM.
Contents
Introduction 4-2
1350 OMS EML GUI Features 4-2
Workflow 4-4
Window Structure 4-5
Window and Menu for 1350 OMS EML 4-5
Filtering Area 4-10
Error Management 4-12
Error Management in 1350 OMS EML 4-12
...................................................................................................................................................................................................................................
March 2010
1350 OMS EML Graphical User Interface 1350 OMS EML GUI Features
Introduction
....................................................................................................................................................................................................................................
Introduction
1350 OMS EML GUI Features

Graphical User Interface
The 1350 OMS EML GUI is based on the generic MultiService-GUI framework, from
which inherit objects definition, frames structure and basic behaviors. The 1350 OMS
EML GUI main window includes the menu bar, the tool bar and is split in more section
views as shown in the below figure. The main view area could be managed as set of
tabbed panels, defined by the operator: in the EML-GUI main view area shows the
Inventory list panel and the Log panel. According with the MS-GUI common behavior
the main view area supplies filtering and searching facility and table management. Details
on the MultiService-GUI generic behavior are defined in the referenced documents 1.
Menu Items
The main menu items Search and Action are customized for the EML domain.
....................................................................................................................................................................................................................................
March 2010
1350 OMS EML Graphical User Interface 1350 OMS EML GUI Features
Introduction
....................................................................................................................................................................................................................................
The most significant commands supplied by the EML sub-system are defined under these
menus:
• NE Management commands (Actions): NE Management commands are directly
impacting the managed Network Element and are available for each type of Network
Element.
• search: Queries are operations that do not modify the system Database or the NEs
status and attributes.
• Tools: Tools are supplying commands developed for specific NE Types and Release
and are available at EML in order to manage specific operation on these NEs.
Search and Action menus contain static commands, which are available independently
from the context, and dynamic commands, that are made available or enabled according
with the selected objects and its status. The main view area shows the NE/EML inventory,
that is the result of the NE/EML query sent to the TM server. The NE/EML inventory
view gives the possibility to modify the order of the listed object (sorting) and the type
and the position of the attributes (columns significance and position). The dynamic
filtering area, on the left panel, specifies filters criteria applicable to queries. The local
filtering area, inside the main view area, specifies filters locally applicable to the listed
object. All these basic functions of the main windows are defined in details in the
document [5].
....................................................................................................................................................................................................................................
March 2010
1350 OMS EML Graphical User Interface Workflow
Introduction
....................................................................................................................................................................................................................................
Workflow
Description
The following figure shows the schematic representation of the EML-GUI workflow: the
EML operator accesses the system functions both from the main menu and from the
pop-up menu available from the Global Inventory list, for single or multiple selected NEs.
Functions are grouped under the main menu and, for the more complex ones, the menu
items give access to specific submenus, organized in a hierarchical tree.
....................................................................................................................................................................................................................................
March 2010
1350 OMS EML Graphical User Interface Window and Menu for 1350 OMS EML
Window Structure
....................................................................................................................................................................................................................................
Window Structure
Window and Menu for 1350 OMS EML

Generic Window Structure
The following figure shows the generic format of the wizard used in 1350 OMS EML.
Each defined area is devoted for specific functions:

• The caption bar contains the window title;
• The functional description area contains a short description of the function supplied
by the windows and gives command result evidence;
• The working area supplies all the input field and interactive objects in order to guide
the operator performing the action required. This area is dynamically managed;
....................................................................................................................................................................................................................................
March 2010
Window Structure
....................................................................................................................................................................................................................................
• The dynamic description area is used to show to the operator some detailed help
information on input field, buttons and other widget available in the working area.
Texts inside this section are managed dynamically according with the cursor position
inside the working area.
• The command buttons area contains the buttons to acknowledge or launch the
command defined by the wizard and to close it. Activation buttons are enabled only
when all the input values have been defined.
Command results are managed changing the background of the functional description
area (green for successful commands; red for failed). From this area is also possible
access to the error detail description.
Main Menu
The main menu bar contains the following items: File, Edit, search, Action, Utilities,
Windows, Help. Functions and commands availability depends from the authorization
profile (FAD) associated to the logged operator and from the object selection on the GUI.
....................................................................................................................................................................................................................................
March 2010
Window Structure
....................................................................................................................................................................................................................................
The following tables are a schematic description of the main menu bar items as defined
for 1350 OMS EML Graphical User Interface.
File Menu
Item Accelerator Enabled When Effect

Close Ctrl Q Always Closes the selected view
Print Ctrl P Always
Properties Ctrl O Always Shows operator, system and language
properties.
Exit Ctrl E Always Closes all the view and stops the
application
Edit Menu
Item Accelerator Enabled When Effect

Copy Ctrl C Object Selected
Paste Ctrl V Copied object available and no other
object selected
Select All Ctrl G Always
Find Ctrl F Always
Search Menu
Item Accelerator Enabled Effect

When
Network Element Ctrl I Always Shows the NE list in the main
view area
EML Domains Ctrl M Always Shows the EML Domains list in
Inventory the main view area
EML Instances Always Shows the EML Instances list in
Inventory the main view area
....................................................................................................................................................................................................................................
March 2010
Window Structure
....................................................................................................................................................................................................................................
Action Menu
Item Enabled When Effect

Create NE Always Launch the NE Creation wizard
Remove NE Object selected Remove a declared NE
Create ISA Object selected Create a new ISA board
Rename ISA Object selected Rename ISA boards and location
Set NE Address Object selected Define/modify NE Addresses
Ping NE Object selected Check network connection with the NE
Start Supervision Object selected Activate the NE management
Stop Supervision Object selected Stop the NE management
Abort Supervision Object selected Abort the NE management
LAC Management Object selected Control the CT access control
Get NE Time Object selected Read the NE time
Set NE Time Object selected Set the NE time
NTP Configuartion Object selected Configuration of the NTP protocol
Set OS Address (not Object selected Define the OS Address
available)
Set NE ACD Object selected Define the NE Access Control Domain
NE Resynchronize Object selected Activate the NE resynchronization
NE Upload Remote Object selected Activate the upload of the Remote
Inventory Inventory data
NE Properties Object selected Show the NE properties details
NE Modify Object selected Modify the NE parameters
Modify All Object selected Modify common NE parameters
NE Status Object selected Show the NE status
NE Information Object selected Show main NE Information
Tools Menu

Left Area Always Opens the documentation window
Macro Always Allows to activate a Recorder or Player
....................................................................................................................................................................................................................................
March 2010
Window Structure
....................................................................................................................................................................................................................................

Customize Always Changes the cursor format and allows
selecting a window object in order to ask
detailed help on its function
Options Always Displays the window that allows to set/reset
some generic options
Display Pending Operations Always Put the Log window on the top view
Stop All Pending If pending Stops all pending operations
Operations operations
Templates Always Displays the available template list
Windows Menu

Lists Always Lists the active windows
Logs Always Access the MS-GUI command log view
(Server or Operations)
Help Menu

Help Always Opens the documentation window
What’s this Always Changes the cursor format and allows
selecting a window object in order to ask
detailed help on its function
About... Always Displays a dialog box containing
information about the application version
....................................................................................................................................................................................................................................
March 2010
1350 OMS EML Graphical User Interface Filtering Area
Window Structure
....................................................................................................................................................................................................................................
Filtering Area
Filter Definition
The main view allows defining local filtering criteria in order to focus the object selection
on defined attribute and values. Two kind of filtering facilities are supported:
• local, this modality is directly managed by the EML MS-GUI and keep as targets the
objects already present on the GUI;
• dynamic, this modality invokes a new request towards the TM server. The filtering
criteria are managed according with the object shown in the main view area.
The following figures show an example of filtering definition:
• the left panel show the dynamic filtering criteria (Figure 4-1, “Dynamic Filtering”
(p. 4-10) );
• the filtering area in the main view show the local filtering criteria (Figure 4-2, “Static
Filtering” (p. 4-11)).
The filtering results are shown in the main view.
Figure 4-1 Dynamic Filtering
....................................................................................................................................................................................................................................
March 2010
1350 OMS EML Graphical User Interface Filtering Area
....................................................................................................................................................................................................................................
Figure 4-2 Static Filtering
....................................................................................................................................................................................................................................
March 2010
1350 OMS EML Graphical User Interface Overview
Error Management
....................................................................................................................................................................................................................................
Error Management
Error Management in 1350 OMS EML

MS-GUI Error Management
Error management is supplied by 1350 OMS EML application at two different levels:
• the general command log view shows the command result for all the commands,
keeping them into an history view;
• the single wizard window manages command error highlighting the error cases with a
change in the Functional Description Area. If an error occurs the area becomes red.
The error management inside wizards will allow operator to see the error details and the
associated diagnostic message. The wizard will keep available all the command
parameters and arguments previously inserted, in order to allow the operator to correct or
modify them and, when significant, to repeat the command applying the corrections. The
following figure shows the example of a wizard error management in case of successful
command and in case of error.
....................................................................................................................................................................................................................................
March 2010
1350 OMS EML Graphical User Interface Error Management in 1350 OMS EML
Error Management
....................................................................................................................................................................................................................................
The operator can access to the detailed description of the error clicking into the
Functional Description Area.
....................................................................................................................................................................................................................................
March 2010
1350 OMS EML Graphical User Interface Error Management in 1350 OMS EML
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
5 EML Management
5
Overview
Purpose
The EML subsystem is intended to manage the elementary building blocks of any
telecommunication network that are the Network Elements (NEs). The connection
between two NEs is called a link.
Contents
Action Menu 5-2

Menu Composition 5-2
Create Network Elements 5-4
Discover Gateway NE 5-7
Global EML Resynchronize 5-10
Search Menu 5-11
NE Global Inventory 5-11
EML Domains 5-13
EML Instances 5-14
...................................................................................................................................................................................................................................
March 2010
EML Management Menu Composition
Action Menu
....................................................................................................................................................................................................................................
Action Menu
Menu Composition
Introduction
The Action menu supplies several main functionality offered by 1350 OMS EML: the
basic Action menu of the Multi Service GUI framework is configured for 1350 OMS
EML, adding specific actions. The user access is controlled by the authorization profile
managed (FAD) according with the rules defined for each user profile.
Commands from Main Menu

The action menu is available from the main menu bar; it is dynamically built according
with the selected Network Element properties and status. Commands are applied to the
selected Network Element(s).
Figure 5-1 Action Menu from menu bar
Commands from EML Domains Inventory

The contextual popup action menu from EML Domain Inventory is dynamically built
according with the selected EML properties and status. This menu is available only after
EML selection. Commands are applied to the selected NE. For the Create action only
the single selection is allowed, the command is enabled only if a single EML domain has
been selected. The same list of actions/command is available from popup menu and from
the action menu on the main menu bar.
....................................................................................................................................................................................................................................
March 2010
EML Management Menu Composition
Action Menu
....................................................................................................................................................................................................................................
Figure 5-2 Commands list from EML Domain Inventory
....................................................................................................................................................................................................................................
March 2010
EML Management Create Network Elements
Action Menu
....................................................................................................................................................................................................................................
Create Network Elements

When to use
This wizard guides the user to the definition of a new Network Element to be managed by
the 1350 OMS EML system.
Related Information
Before you begin

Collect the NE info you need to insert during the creation operation.
Create a Network Element

...................................................................................................................................................................................................
1 From the Multiservice GUI follow the path Actions > EML > Create NE.
Result: The Create NE window is displayed.
...................................................................................................................................................................................................
2 Select the Network Element Family, consequently Type and Release (in the order) is
restricted to the type and values supported by the current system release.
Example : if the family chosen is Omsn, the Type is automatically filled with the list of
types belonging to the Omsn family (ne1670sm, ne1660sm, ...)
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Select the Network Element Type. This parameter value is related to the family chosen in
step1.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Select the Network Element Release. This parameter value depends on the family chosen
in step 1 and the type chosen in step 2.
...................................................................................................................................................................................................
5 Insert the User Label. This parameter is a free string. The system checks the maximum
length applicable to the User Label and prevents duplication. For TL1 Network Elements
the GUI manages a specific User Label length (according with TID) and character set.
...................................................................................................................................................................................................
6 Insert the Location. This parameter is a free string describing the location of the Network
Element.
...................................................................................................................................................................................................
7 Select the PNMIM from the list for the NE that is created in the Directory field.
...................................................................................................................................................................................................
8 Select the Supervision Area from the list of available areas. The system applies
load-balancing rules if the user doesn’t select a value.
...................................................................................................................................................................................................
9 Select the EML Domain between the ones already available, to force the assignment of the
NE to that EML domain, provided that it supports the required NE type and release. The
available Domains depends on the Supervision area chosen in step 6. The parameter
inserted in step 1 through 6 are mandatory for the definition of the Network Element.
After the insertion of all these parameters, the button OK for confirming the creation is
enabled.
Note: If none of the two previous attributes (Supervision Area and EML domain) are
provided, the NE will be allocated to the least loaded EML domain among all of those
supporting the required NE type and release.
...................................................................................................................................................................................................
10 This step is optional. Select the Access Control Domain from the possible values
displayed in the drop-down list.
...................................................................................................................................................................................................
11 Select the OK button to proceed with the Network Element Creation.

Result: Command progress and result are shown into the Log panel. The Network
Element is created or an error is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
EML Management Discover Gateway NE
Action Menu
....................................................................................................................................................................................................................................
Discover Gateway NE
When to use
This function allows to manage the discovered Network Elements that should be managed
by the 1350 OMS EML system.
Related Information
Before you begin

This task does not have any preconditions..
Task
...................................................................................................................................................................................................
1 From the Multiservice GUI follow the path Actions > EML > Discover Gateway NE.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Result: The discover Gateway NE window is displayed. The list of discovered NEs is
displayed in the upper part of the window. The discovered NEs can be GNE, RNE or
1830PSS NEs.
...................................................................................................................................................................................................
2 Click on the icon in the lower part of the window to add NEs to the Import NE list.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Result: The Discovered NE List is displayed.
...................................................................................................................................................................................................
3 Select the NE to import and confirm with the check icon. The selected NEs are displayed
in the list.
...................................................................................................................................................................................................
4 Confirm the import operation with OK or Apply button.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
EML Management Global EML Resynchronize
Action Menu
....................................................................................................................................................................................................................................
Global EML Resynchronize

When to use
This function allows to resynchronize the EML and all Network Elements to be managed
by the 1350 OMS EML system.
Related Information
Before you begin

This task does not have any preconditions..

...................................................................................................................................................................................................
1 From the Multiservice GUI follow the path Actions > EML > Global EML Resynchronize.
Result: The confirmation window is displayed.
...................................................................................................................................................................................................
2 Click on the button to end start the operation.
if… then…
Yes the Global EML synchronization starts
No no action is taken
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
EML Management Overview
Search Menu
....................................................................................................................................................................................................................................
Search Menu
NE Global Inventory
Description
The NE Global Inventory query retrieves the list of all the NEs defined on the system,
with the associated attributes and status. The NE Global Inventory supplies a synthetic
view of the managed network and is the starting point for management commands
(Action/Search). The NE Global Inventory is shown in the main view area of the 1350
OMS EML GUI. Filtering, searching and sorting capability, as supplied by the MS-GUI
framework, are applicable to this view.
Figure 5-3 Search - Get All NE
This window shows the list of all defined NEs and their most significant attributes.
Columns are representing the NE attributes and could be moved in a different position
(shift left/right). Filtering and sorting could be applied to each column/attribute. Rows are
representing NE instances; single and multiple selections are available. On selected
Network Element(s) is possible to apply action/commands according with the dynamic
definition of the main menu or of the popup menu (right mouse click). Attribute values
shown into this window are automatically updated when AVC notification are received.
....................................................................................................................................................................................................................................
March 2010
EML Management NE Global Inventory
Search Menu
....................................................................................................................................................................................................................................
The available list of NE could be filtered according to values given to the following
attributes (filtering criteria):
• ACD;
• Alarm Status;
• EML Domain;
• LAC;
• Location Name;
• Release;
• Supervision Area;
• Supervision State;
• Type
....................................................................................................................................................................................................................................
March 2010
EML Management EML Domains
Search Menu
....................................................................................................................................................................................................................................
EML Domains
Description
From the Search menu the user can obtain the list of the EML Domains defined in the
1350 OMS System.
Follow the path Search > EML > EML Domains, the list of EML Domains is displayed in
the MS-GUI list area.
From the Domains list the use can display the list of Network Elements belonging to the
selected domain in the list.
Select the domain in the list and from the popup menu the path Search > Network
Element. The list of NE belonging to the domain is displayed. The Domain is shown in
the list title, as shown in the following figure.
....................................................................................................................................................................................................................................
March 2010
EML Management EML Instances
Search Menu
....................................................................................................................................................................................................................................
EML Instances
Description
From the Search menu the user can obtain the list of the EML Instances defined in the
1350 OMS System.
Follow the path Search > EML > EML Instances, the list of EML Instances is displayed in
From the Instances list the user can display the list of EML Domains belonging to the
selected instance in the list.
Select the instance in the list and from the popup menu the path Search > EML Domains.
The list of Domains belonging to the instance is displayed. The Domain is shown in the
list title, as shown in the following figure.
....................................................................................................................................................................................................................................
March 2010
Search Menu
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
6 6 etwork Element
N
Management
Overview
Purpose
The elementary building blocks of any telecommunication network are the Network
Elements (NEs). The connection between two NEs is called a link.
Topology Management can manage Several types of NEs:
• Basic NEs (that are not remote NEs).
• Remote NEs and remote units.
• Sub NEs.
Contents
Network Elements and Links 6-3

Management States 6-3
NE Time Configuration 6-6
Configuration 6-6
Action Menu 6-9
Menu Composition 6-9
Create and Remove Network Elements 6-14
Network Element Resynchronize 6-18
Managing the Supervision of an NE 6-19
Set Network Element Access Control Domain 6-21
Managing the NE Time 6-23
Managing the NE MIB 6-25
Modifying the Access State of an NE 6-28
NTP Configuration 6-30
...................................................................................................................................................................................................................................
March 2010
Network Element Management Overview
....................................................................................................................................................................................................................................
Set Network Element Access Control Domain 6-34

Create ISA board 6-36
Set OS Address 6-38
Set NE Address 6-41
Set 4G (Q3) NE Address 6-43
Uploading the Remote Inventory 6-59
Global Remote Inventory 6-61
Information about NEs 6-64
Current Status Consultation 6-67
Ping NE 6-69
Search Menu 6-71
NE Global Inventory 6-71
EML Domains 6-73
EML Instances 6-74
Navigations 6-76
Navigations and Inventories 6-76
Modification of NE or Link Characteristics 6-78
Changing an OS Address 6-78
....................................................................................................................................................................................................................................
March 2010
Network Element Management Management States
....................................................................................................................................................................................................................................
Management States
Definition
This section describes the different management states of NEs and dynamic links from the
OS point of view.
Management states are available for any manageable entity, including remote NEs and
remote units. In this section, NE stands for any manageable entity.
The NE and dynamic link management states are as follows:
• NE management states: Supervision, Alignment, Communication, Administrative,
Usage, Operational, Local Access, and a single Alarm status.
• Dynamic link management states: Supervision, Alignment, Administrative,
Operational and a single Alarm status.
Actions undertaken from Topology Management can influence only the NE management
states, not the link management states.
Management states:
Supervision state: gives information relative to the supervision state of the NE or the
dynamic link. There are four possible values. Operational state and Access state can then
be fixed. Possible values are:
• Declared: the NE or the dynamic link is just declared to the OS.
• Supervised: the NE or the dynamic link is under supervision.
• Activating: the NE or the dynamic link is being brought under supervision and no
management tasks can be performed on it.
• Deactivating: the supervision process on the NE or the dynamic link is being stopped
and no management tasks can be performed on it.
Communication state: reflects the capability of the NE to communicate with the EML.
This management state does not concern dynamic links. Possible values are:
• Disabled: the communication between the EML and the NE is interrupted.
• Enabled: the EML can communicate with the NE.
Administrative state: reflects the administration of a resource. Possible values are:
• Locked: the resource is administratively prohibited from performing services for its
users.
• Unlocked: the resource is administratively permitted to perform services for its users.
this is independent of its inherent operability.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Usage state: reflects the usage of the NE. This management state does not concern
dynamic links. Possible values are:
• Idle: the resource is not currently in use.
• Busy: the resource is in use and it has no spare operating capacity to provide for
additional users simultaneously.
• Active: the resource is in use and it has sufficient spare operating capacity to provide
for additional users simultaneously.
Alignment state: indicates whether the NE MIB and its image in the OS are aligned or
not. There are five possible values:
• Aligning Up: the system is performing a 'MIB Align Upwards' operation. No
operation can be done on the NE or the dynamic links.
• Aligning Down: the system is performing a 'MIB Align Downwards' operation. No
operation can be done on the NE or the dynamic links.
• Aligned: the NE MIB and its image in the OS are identical. In Config: the NE or the
dynamic link is being configured and no alignment has been undertaken yet.
• Misaligned: the NE MIB and its image in the OS are not identical and eventually, the
NE or the dynamic link has to be re–configured.
• Auditing: the NE or the dynamic link is under OS supervision and the system is
comparing the NE MIB with its image in the OS.
Local access state: denotes the granting or denial of access for management operations on
the NE via the craft terminal. This management state does not concern dynamic links.
There are three possible values:
• Granted: the NE can be managed by the local craft terminal.
• Requested: the local manager has requested update permission from the remote
manager and is waiting for a reply.
• Denied: the NE cannot be managed by the local craft terminal.
Operational state: reflects the capability for the NE or the dynamic link to accept the
EML supervision. There are two possible values:
• Disabled: the NE or the dynamic link cannot be supervised. This means the resource
is internally facing a major failure.
• Enabled: the NE or the dynamic link can be supervised.
Alarm status: indicates the highest severity alarm currently present on the NE or the
dynamic link. There are six possible values:
• Critical: the NE or the dynamic link operational state is disabled, or the NE or the
dynamic link presents malfunctions. An immediate corrective operation is required.
• Major: the OS and NE or dynamic link MIBs are misaligned, or the NE or the
dynamic link presents dysfunctions. Urgent corrective operation is required.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
• Minor: the NE or the dynamic link presents dysfunctions. A corrective operation
should be taken in order to prevent more serious fault (for example service affecting).
• Warning: it indicates the detection of a potential or impending service affecting fault
before any significant effects have been felt. Operation should be taken to further
diagnose (if necessary) and correct the problem in order to prevent it from becoming a
more serious fault.
• Active Pending: the NE or the dynamic link is in a pending state.
• Cleared: there is no outstanding alarm within the NE or the dynamic link.
• Indeterminate: the OS has not received an update of the current alarms occurring.
A mechanism enables the OS to determine whether it manages the supervised NEs or the
supervised dynamic link. This mechanism enables the OS to detect changes in the NE or
in the dynamic link configuration or in the operational state of the NE or the dynamic
link. This mechanism is launched automatically after the NE, or the dynamic link, is
brought under supervision by the OS. It is stopped if the OS is shut down or if the NE or
the dynamic link is no longer under supervision.
Any disruption in the communication link between the OS and the NE or the dynamic
link results in an update of the management states once the OS has detected the
communication failure.
....................................................................................................................................................................................................................................
March 2010
Network Element Management Configuration
....................................................................................................................................................................................................................................
Configuration
Time Configuration
1350 OMS time is configured in Local Time at system installation for both Master and
Client servers, if present. The 1350 OMS time configuration is described in 1350 OMS
Installation Guide.
Network Elements managed by EML system have to be configured to use 1350 OMS as
NTP server.
The configuration is done setting for the Network Element NTP configuration the IP
address of the relevant 1350 OMS and keeping the offset value to 0 (Offset=”+00-00”).
Network Elements and 1350 OMS components work internally in UTC/GMT0 and time
stamps of data exchanged between NE and 1350 OMS are in UTC/GMT0. The time
stamps comes from Alarms, Events, PM Data, Command Logs, ...: the GUI applications
have the task to show time stamps in Local Time.
Also Open Interfaces follow same approach: namely, IOO exports Alarms and PM Data
with time stamp GMT0 and it will be up to OSS to show time stamp in Local Time.
Operator PC clients are natively in Local Time and do not require any configuration to
host applications of 1350 OMS and ZIC.
Example
Considering a 1850 TSS320 Network Element Rel.3.0, the management system 1350
OMS 9.1.1 and Italian Day Time (GMT+1), an example of time configuration is
described. Server hosting 1350 OMS is configured with GMT+1, user PC clients are in
Local Time as shown in following figure.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Configure the 1350 OMS server as NTP server for the Network Element from the
Network Element GUI NTP config window:
• Current NTP Server Synchronization : Enabled
• Current Offset : +00-00
• Current Operating Mode : HOLDOVER
Note: It is important to set the Current Offset to +00-00, in case the offset is different
the Network Element has a wrong behavior.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
Network Element Management Menu Composition
Action Menu
....................................................................................................................................................................................................................................
Action Menu
Menu Composition
Introduction
The Action menu supplies several main functionality offered by 1350 OMS EML: the
basic Action menu of the Multi Service GUI framework is configured for 1350 OMS
EML, adding specific actions. The user access is controlled by the authorization profile
managed (FAD) according with the rules defined for each user profile.
Commands from Main Menu

The action menu is available from the main menu bar; it is dynamically built according
with the selected Network Element properties and status. Commands are applied to the
selected Network Element(s).
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Figure 6-1 Action Menu from menu bar
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Commands from NE Global Inventory List
The action menu is also available from the NE Global Inventory List, shown into the
main view area. This is a dynamic menu built according with the NE properties and
status. This menu is available only after NE selection. Commands are applied to the
selected NE.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Figure 6-2 Action Menu popup from NE Global Inventory
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Commands from EML Domains Inventory
The contextual popup action menu from EML Domain Inventory is dynamically built
according with the selected EML properties and status. This menu is available only after
EML selection. Commands are applied to the selected NE. For the Create action only
the single selection is allowed, the command is enabled only if a single EML domain has
been selected. The same list of actions/command is available from popup menu and from
the action menu on the main menu bar.
Figure 6-3 Commands list from EML Domain Inventory
....................................................................................................................................................................................................................................
March 2010
Network Element Management Create and Remove Network Elements
Action Menu
....................................................................................................................................................................................................................................
Create and Remove Network Elements

When to use
This wizard guides the user to the definition of a new Network Element to be managed by
the 1350 OMS EML system.
Related Information
Before you begin


...................................................................................................................................................................................................
1 From the Multiservice GUI follow the path Actions > EML > Create NE.
Result: The Create NE window is displayed.
...................................................................................................................................................................................................
2 Select the Network Element Family, consequently Type and Release (in the order) is
restricted to the type and values supported by the current system release.
Example : if the family chosen is Omsn, the Type is automatically filled with the list of
types belonging to the Omsn family (ne1670sm, ne1660sm, ...)
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Select the Network Element Type. This parameter value is related to the family chosen in
step1.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Select the Network Element Release. This parameter value depends on the family chosen
in step 1 and the type chosen in step 2.
...................................................................................................................................................................................................
5 Insert the User Label. This parameter is a free string. The system checks the maximum
length applicable to the User Label and prevents duplication. For TL1 Network Elements
the GUI manages a specific User Label length (according with TID) and character set.
...................................................................................................................................................................................................
6 Insert the Location Name. This parameter is a free string describing the location of the
Network Element.
...................................................................................................................................................................................................
7 Select the PNMIM from the list for the NE that is created in the Directory field.
...................................................................................................................................................................................................
8 Select the Supervision Area from the list of available areas. The system applies
load-balancing rules if the user doesn’t select a value.
...................................................................................................................................................................................................
9 Select the EML Domain between the ones already available, to force the assignment of the
NE to that EML domain, provided that it supports the required NE type and release. The
available Domains depends on the Supervision area chosen in step 6. The parameter
inserted in step 1 through 6 are mandatory for the definition of the Network Element.
After the insertion of all these parameters, the button OK for confirming the creation is
enabled.
Note: If none of the two previous attributes (Supervision Area and EML domain) are
provided, the NE will be allocated to the least loaded EML domain among all of those
supporting the required NE type and release.
...................................................................................................................................................................................................
10 This step is optional. Select the Access Control Domain from the possible values
displayed in the drop-down list.
...................................................................................................................................................................................................
11 Select the OK button to proceed with the Network Element Creation.

Result: Command progress and result are shown into the Log panel. The Network
Element is created or an error is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Remove a Network Element
Note: If a Network Element is a node in a map, before removing it, remove the node
on the map. If this operation is not done, for some types of Network Elements a
misalignment will occur and you won't be able to remove it no more from the map
and also all related connections, if any.
...................................................................................................................................................................................................
1 Select one or more Network Element that you want to remove on the Inventory list or on
the graphical map.
...................................................................................................................................................................................................
2 Select from the Action menu Actions > Network Element > Delete NE
or the Maps from the NE Popup menu Actions > Delete NE
...................................................................................................................................................................................................
3 Confirm the deletion.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Network Element Resynchronize
Action Menu
....................................................................................................................................................................................................................................
Network Element Resynchronize

When to use
To make sure that the NE states displayed on the map and in inventory list are really up to
date, you can perform a manual resynchronization by proceeding as described.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 Select the NE to be resynchronized.

...................................................................................................................................................................................................
2 Use the menu path: Action > EML > Network Element > Resynchronize.
You can also resynchronize completely Topology Management, but in that case, you
must know that this can take a long time according to the number of NEs and links to
be resynchronized. NE resynchronize is an internal TM Server action that force the
resynchronization of all the attributes and status of the selected NE(s)
Note: Action progress and result are shown in the log panel.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Managing the Supervision of an NE
Action Menu
....................................................................................................................................................................................................................................
Managing the Supervision of an NE

Description
Supervising NEs is an essential aspect of the network management. It enables the
gathering of information concerning the behavior of the NE with respect to its functional
state.
The supervision of an NE consists in establishing a communication that allows the user to
perform EML operations such as configuration and alarm management.
The NE address must be declared before starting the supervision of this NE. Otherwise
error messages will be displayed.
This section explains how to:
• Start the NE supervision.
• Stop the NE supervision.
Starting the NE Supervision

Select the Start Supervision option compliant with the Network Element Type and a
confirmation box is displayed to confirm the operation.
Figure 6-4 Supervision Selection
The NE supervision state changes to Supervised.
....................................................................................................................................................................................................................................
March 2010
Network Element Management Managing the Supervision of an NE
Action Menu
....................................................................................................................................................................................................................................
Once the NE is supervised, an association between the NE and the OS is created. Thus
EML application is able to animate the NE symbol color according to the changes of the
NE states.
Stopping the NE Supervision

To stop the supervision of an NE, select it then use the menu path:
Action > Network Element > Supervision > Stop.
A confirmation dialog box opens, confirm the operation.
The NE supervision state changes to Stopped.
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set Network Element Access Control Domain
Action Menu
....................................................................................................................................................................................................................................
Set Network Element Access Control Domain

When to use
This function allows reading and modifying the Access Control Domain defined for a
Network Element.
Related information
Before you begin

The available Access Control Domains defined with SEC application should be known to
assign them in the correct way.
Task
...................................................................................................................................................................................................
1 Select the NE on the displayed map, or on the Inventory List.

...................................................................................................................................................................................................
2 Follow the path Actions > Network Element > ACD or

from the NE Popup menu Actions > ACD
...................................................................................................................................................................................................
3 The set ACD window is displayed.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Access Control Domain (ACD) is managed on NE base, for NE Type & Release
supporting it. The wizard shows the current ACD assigned to the target NE and, in order
to modify it, allows selecting one of the available, defined by SEC application.
Confirm the operation with OK or Apply button
Result: The new Access Control Domain is assigned to Network Element. If you use
the OK button the Create NE window is closed, if you use the Apply button the
operation is done but the window remains open.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Managing the NE Time
Action Menu
....................................................................................................................................................................................................................................
Managing the NE Time

When to use
This functions can be used to get time from a Network Element or synchronize the time
of a Network Element with the OS.
Related information
Before you begin

This operation is only allowed if the NE supervision state is Supervised, so check the
Network Element supervision state.
Getting the Time of an NE

To get the time of an NE, proceed as follows:
...................................................................................................................................................................................................
1 On the map window or inventory list, select an NE whose supervision state is Supervised
and communication state is enabled.
...................................................................................................................................................................................................
2 Use the menu path: Action > Network Element > Time > Get Time.
The NE time is updated in the EML system.
E...................................................................................................................................................................................................
N D O F S T E P S
Synchronizing the NE Time with the OS Time

To synchronize the NE time with the OS time, proceed as follows:
...................................................................................................................................................................................................
1 On the map or inventory list, select an NE whose supervision state is Supervised and
communication state is enabled.
...................................................................................................................................................................................................
2 Use the menu path: Action > Network Element > Time > Set Time.
The following dialog box opens:
....................................................................................................................................................................................................................................
March 2010
Network Element Management Managing the NE Time
Action Menu
....................................................................................................................................................................................................................................
Figure 6-5 Time Management–Set Time Dialog Box (before command execution)
Confirm the operation with OK or Apply button. The NE time appears in the NE Time
field. It is now the same as the OS time.
Note: If the NE is associated with an NTP server (see ), you cannot synchronize its
time with the OS time. The time shown in the window is converted according with the
local terminal time zone; time sent to the NE is GMT.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Managing the NE MIB
Action Menu
....................................................................................................................................................................................................................................
Managing the NE MIB

When to use
During the construction of the network topology the creation of a new NE in the network
is associated with the description of its configuration in the OS. This NE configuration
may be different from the actual physical configuration of the NE, described in the NE
MIB (Management Information Base), and an alignment operation may be necessary to
adjust the NE MIB and the OS.
Moreover, during the normal functioning of the network it may be necessary to modify
the NE configuration, physically or by using the graphical interface. After that operation
an alignment between the NE MIB and its image in the OS appears to be necessary.
• Upload the NE MIB into the OS.
• Download MIB information from the OS into the NE MIB.
Related Information
Before you begin

Downloading Information from the OS into the NE MIB

This function consists in aligning the NE MIB with the NE configuration coming from
the OS. This operation may be necessary when the OS is launched or if a new
configuration is needed for a NE. This operation may be necessary when the OS is
launched or if a new configuration is needed for a NE. There are two available
possibilities for this operation: A manual alignment, the NE configuration present in the
OS is as much as necessary downloaded into the NE MIB, according to the EML agent
decision; A global alignment, the NE configuration is unconditionally downloaded. In the
first case, the entire NE configuration could be downloaded as well if needed.
To download the NE configuration from the OS into the NE MIB, proceed as follows:
...................................................................................................................................................................................................
1 Select the NE on the Topology Management map window.

There are two available possibilities for this operation:
• A manual alignment, the NE configuration present in the OS is as much as necessary
downloaded into the NE MIB, according to the EML agent decision.
• A global alignment, the NE configuration is unconditionally downloaded.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
In the first case, the entire NE configuration could be downloaded as well if needed.
...................................................................................................................................................................................................
2 Use the menu path:

Action > MIB > Manual Align Down
or
Action > MIB > Global Align Down
...................................................................................................................................................................................................
3 Confirm the operation with OK button.

The NE configuration contained in the OS is downloaded into the NE MIB. The NE MIB
and its image in the OS are now aligned.
E...................................................................................................................................................................................................
N D O F S T E P S
Network Element MIB Alignment

This function consists in aligning the NE MIB with the NE configuration coming from
the OS. This operation may be necessary when the OS is launched or if a new
configuration is needed for a NE. There are two available possibilities for this operation:
• A manual alignment, the NE configuration present in the OS is as much as necessary
downloaded into the NE MIB, according to the EML agent decision.
• A global alignment, the NE configuration is unconditionally downloaded.
In the first case, the entire NE configuration could be downloaded as well if needed.
Uploading the NE MIB into the OS

This function consists in aligning the OS with the NE MIB.
This operation may be necessary if:
• A communication failure between the OS and the NE has occurred.
• The NE configuration has been changed during a local management by a craft
terminal and the NE MIB differs from its image in the OS.
To upload the NE MIB into the OS, proceed as follows:
Select the NE on the map or on the inventory list.
Use the menu path: Action > Network Element > MIB > Align Up.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Figure 6-6 MIB Alignment–Align MIB Up Dialog Box
The NE configuration contained in the NE MIB is uploaded into the OS. The NE MIB
and its image in the OS are now aligned.
....................................................................................................................................................................................................................................
March 2010
Network Element Management Modifying the Access State of an NE
Action Menu
....................................................................................................................................................................................................................................
Modifying the Access State of an NE

NE Access State
The NE access state indicates if the NE is managed by the OS or from a craft terminal.
This section describes following actions:
• Switch the NE access state from OS to local.
• Switch the NE access state from local to OS.
• Request a local access from a craft terminal.
• Grant the local access for all NEs in requested access state.
• Deny the local access for all NEs in requested access state.
Switching the NE Access State from OS to Local

This function allows a craft terminal located next to the NE to manage it instead of the
OS. To switch the NE access state from OS to local, proceed as follows:
Select the NE whose local access state is Denied on the map or on the inventory list.
Use the menu path: Actions > Network Element > Access State > Local
Figure 6-7 Local Access––Switch to Local Dialog Box
Confirm the operation with Yes button. The NE local access state changes to Granted
....................................................................................................................................................................................................................................
March 2010
Network Element Management Modifying the Access State of an NE
Action Menu
....................................................................................................................................................................................................................................
Once the NE is in local access state, the OS cannot manage it anymore. However it
continue to provide some services like:
• The reception and processing of alarms.
• The switching back to the OS access state.
The access state of a remote NE or a remote unit cannot be modified as it keeps aligned
on the access state of its master NE.
Switching the NE Access State from Local to OS

This function allows the OS to manage an NE that was under control of a craft terminal.
To switch the NE access state from local to OS, proceed as follows:
Select the NE whose local access state is Granted on the map or in the inventory list. Use
the menu path: Action > Access State > OS.
Figure 6-8 Local Access–Switch to OS Dialog Box
The NE local access state changes to Denied.

The access state of a remote NE or a remote unit cannot be modified as it keeps aligned
on the access state of its master NE.
....................................................................................................................................................................................................................................
March 2010
Network Element Management NTP Configuration
Action Menu
....................................................................................................................................................................................................................................
NTP Configuration
When to use
This wizard allows managing the NTP configuration on the Network Element. The initial
visualization shows the current NTP status. This command is available only for NE Type
and Release that are supporting NTP protocol.
Related Information
Before you begin

Display the Network Element List.
Task
...................................................................................................................................................................................................
1 On the MS-GUI use the menu path:

Actions > Network Element > NTP Configuration.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Result: The NTP Configuration window is displayed.
Figure 6-9 Set NE NTP Configuration
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select False if the NTP protocol is disabled on the NE, True if it is enabled.
...................................................................................................................................................................................................
3 Define the NTP Server address on the Network Element, according with the Network
Element network connection interface (OSI/IP).
Figure 6-10 Set NE NTP Configuration (IP configuration)
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 The wizards supply input fields for the definition of two different NTP servers : main and
spare.
Action progress and result are shown into the log panel.
...................................................................................................................................................................................................
5 Confirm with Apply button to keep the window open or with OK to close the window.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Set Network Element Access Control Domain

When to use
This section explains how to modify or set the Access Control Domain of a selected NE
on the Global Inventory.
Related information
Before you begin

Set ACD Task

...................................................................................................................................................................................................
1 Select an NE on the map or on the Inventory list.

...................................................................................................................................................................................................
2 Use the menu path: Action > Network Element > Set ACD .
Following information windows opens:
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Figure 6-11 ACD window for an NE
To close the window, click on the Cancel push button.

...................................................................................................................................................................................................
3 Select the ACD from the list of the available ACDs.

...................................................................................................................................................................................................
4 Execute the assignment clicking on the OK or Apply button.

Result: The new ACD is Assigned to Network Element.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Create ISA board
Action Menu
....................................................................................................................................................................................................................................
Create ISA board

Description
The ISA board management for OMSN is described in Section Procedures (ref. to chapter
“OMSN and ATM board management” (p. 10-21) ). This command allows defining an
ISA board hosted by an OMSN. The user is fully guided in order to create board with
attributes compliant to the 1350 OMS EML naming rules.
....................................................................................................................................................................................................................................
March 2010
Network Element Management Create ISA board
Action Menu
....................................................................................................................................................................................................................................
Figure 6-12 Create ISA board window
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set OS Address
Action Menu
....................................................................................................................................................................................................................................
Set OS Address
When to use
Network Elements exchanging their management information directly with the OS need
addressing information in order to be able to communicate with the OS across the
network. Such an OS address is conveyed to the NE by the EML agent during the creation
process.
Related Information
Actually certain types of NEs have two OS addresses available: the main OS address and
a spare OS address, enabling them to switch from one OS to another. This is intended to
support, for instance, OS resilience or OS migration.
At the beginning, both addresses conveyed to the NE are identical, and they are known by
the EML agent by configuration. The given address relates to the workstation which hosts
the EML agent.
Once the NE is created, each OS address may be individually changed (for NEs which
support it).
Before you begin

Task
...................................................................................................................................................................................................
1 Select an NE whose supervision state is Supervised on the map or on the inventory list.
...................................................................................................................................................................................................
2 Use the menu path: Action > Network Element > Set OS Address or from the popup
menu in the inventory list Action from Network Element > Set OS Address.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Result: The Set OS Address window opens
Figure 6-13 OS Address Wizard
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 The first time an OS Address dialog box opens, the OS Main Address and OS Spare
Address that are known by configuration, are displayed in the corresponding fields.
The user can change the main OS presentation (PSAP) address in accordance with the
ISO definition (AFI, IDI, Organization Id., Area, System Id. and Sel. fields).
The user can also change the optional spare OS PSAP address by using the same format.
Note: The OS main address can only be changed if the NE is supervised, that is its
supervision state is Supervised. However the OS Address dialog box can always be
displayed whatever the supervision state is and you can change the OS spare address
in all cases.
...................................................................................................................................................................................................
4 Confirm the modifications with Apply or OK button.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set NE Address
Action Menu
....................................................................................................................................................................................................................................
Set NE Address
When to use
Set NE address is the function that allows the user defining and modifying Network
Elements Address values and, for NEs supporting it, the user and the password to access
the NE itself.
EML application manages different types of NE addresses: OSI (Q3), RFC1006 (a special
case of OSI address) and free addresses such as TCP–IP (SNMP) addresses. That is the
reason why the address declaration is separated from the NE creation and address input
forms depend on the NE type.
The NE address management could be handled out of the system in particular cases (for
instance, the EML agent may take care of it). This function can also be used to change the
NE address later on.
Moreover some NE types, such as remote NEs, do not embed their own address, as they
exchange their management information with the OS through other NEs. Therefore no
address capture is expected for such NEs.
Note: The currently supported NE address formats are IP addressing for SNMP
Network Elements (also for TL1 NEs), Q3 addressing.
Related information
Before you begin

This operation is only allowed if the NE supervision state is Declared, so check the
Network Element supervision state. The local NE address on the equipment must be
previously set up via the Craft Terminal.
Task
...................................................................................................................................................................................................
1 Select the NE on the displayed map, or on the Inventory List.

...................................................................................................................................................................................................
2 Follow the path Actions > Network Element > Set NE Address or
from the NE Popup menu Actions > Set NE Address
...................................................................................................................................................................................................
3 Depending from the Network Element Type select the set address menu item, the
corresponding set address window is displayed.
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set NE Address
Action Menu
....................................................................................................................................................................................................................................
Result: The corresponding set NE address window is displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set 4G (Q3) NE Address
Action Menu
....................................................................................................................................................................................................................................
Set 4G (Q3) NE Address

When to use
the NE itself.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 Select the 4G (Q3) NE in the Network Element list on the MS-GUI.

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Result: The Set 4G (Q3) NE Address window is displayed
...................................................................................................................................................................................................
3 For the OSI address (primary address) part insert following parameters:
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Field AFI (Authority and Format Identifier) prescribes the basic format layout for an OSI
NE address. GUI prevents users to give an illegal address by:
• Disabling unnecessary input fields for certain AFI.
• Any non–hex–digit character is rejected; the uppercase or lowercase form of
hexadecimal digit characters "A–F" makes no difference.
• The length of any non–free field must conform to OSI rule exactly.
• The length of free field must be an even number (because 2 hexadecimal digits form a
"byte").
The length of free field is up to the user.
Supported values of AFI are 39, 47, 49 and "free".
OSI addresses can be divided into two parts:
• NSAP is a unique address in an OSI network that identifies the network service.
• Selectors (TSel, SSel, and PSel) identify services of peer entities. For example, the
TSel identifies the service provided by the transport layer.
After NE creation, the users configure the agent application address –NSAP plus upper
selectors– through a dedicated form. The NE address definition is mandatory before
starting NE supervision.
The length of upper selectors are:
• Transport Selector: 2 digits.
• Session Selector: 2 digits .
• Presentation Selector: 4 digits.
In OSI standard, NSAP consists of 40 digits (short address and RFC 1006 address form
are the exception):
• AFI: 2 BCD digits.
• IDI: 4 digits.
• Org. Id: 16 digits.
• Area: 4 digits.
• System Id: 12 digits.
• NSAP Selector: 2 digits (1D for all, except 01 for OMSG).
While NSAP shall be unique in the DCN and it is assigned according to the designed
addressing plan, TSP selectors are always the same for a given family of NEs:
• OMSN, MW, WDM: T = 00, S = 00, P = 0002.
• ION/OMSG (full OSI and RFC1006): T = 31, S = 31, P = 31.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
In case of short address form the NSAP address length can range from 8 to 20 bytes (that
is 16 to 40 hex digits).
• If AFI= 39 is selected, text boxes IDI, Organisation ID, Area, System ID, NSAP
Selector are enabled:
AFI= 39 (ISO–DCC): a Q3 NE address is composed of 40 digits:
AFI (2 digits) + IDI (4 digits) + Organization ID (16 digits) + Area Address (4 digits)
+ System ID (12 digits) + NSAP Selector (2 digits).
• If AFI= 47 is selected, text boxes IDI, System ID, NSAP Selector and Free are
enabled:
AFI=47 (ISO 6523–ICD): the length of Q3 NE address ranges from 16 digits to 40
digits:
AFI (2 digits) + IDI (4 digits) + free part (0 to 20 digits) + System ID (12 digits) +
NSAP Selector (2 digits)'.
• If AFI= 49 is selected, text boxes System ID, NSAP Selector and Free are enabled:
AFI= 49 (Private), the length of Q3 NE address ranges from 16 digits to 40 digits:
AFI (2 digits) + free part (0 to 24 digits) + System ID (12 digits) + NSAP Selector (2
digits).
• If AFI= "free" is selected, only text box "Free" is enabled. The length of Q3 NE
address ranges from 0 digit to 40 digits: free part (0 to 40 digits)
...................................................................................................................................................................................................
4 For the IP address (secondary address) insert following parameters: IP Address in dot
notation, for example 151.98.43.187, and Port number (usually it is 161). The secondary
address is optional.
...................................................................................................................................................................................................
5 Confirm the set address operation with OK or Apply button. The OK button save the data
and exists from wizard.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set Q3 NE Address
Action Menu
....................................................................................................................................................................................................................................
Set Q3 NE Address
When to use
the NE itself.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 Select the Q3 NE in the Network Element list on the MS-GUI.

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Result: The Set Q3 NE Address window is displayed
...................................................................................................................................................................................................
3 To set the Q3 NE Address insert following parameters:
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Field AFI (Authority and Format Identifier) prescribes the basic format layout for an OSI
NE address. GUI prevents users to give an illegal address by:
• Disabling unnecessary input fields for certain AFI.
• Any non–hex–digit character is rejected; the uppercase or lowercase form of
hexadecimal digit characters "A–F" makes no difference.
• The length of any non–free field must conform to OSI rule exactly.
• The length of free field must be an even number (because 2 hexadecimal digits form a
"byte").
The length of free field is up to the user.
Supported values of AFI are 39, 47, 49 and "free".
OSI addresses can be divided into two parts:
• NSAP is a unique address in an OSI network that identifies the network service.
• Selectors (TSel, SSel, and PSel) identify services of peer entities. For example, the
TSel identifies the service provided by the transport layer.
After NE creation, the users configure the agent application address –NSAP plus upper
selectors– through a dedicated form. The NE address definition is mandatory before
starting NE supervision.
The length of upper selectors are:
• Transport Selector: 2 digits.
• Session Selector: 2 digits .
• Presentation Selector: 4 digits.
In OSI standard, NSAP consists of 40 digits (short address and RFC 1006 address form
are the exception):
• AFI: 2 BCD digits.
• IDI: 4 digits.
• Org. Id: 16 digits.
• Area: 4 digits.
• System Id: 12 digits.
• NSAP Selector: 2 digits (1D for all, except 01 for OMSG).
While NSAP shall be unique in the DCN and it is assigned according to the designed
addressing plan, TSP selectors are always the same for a given family of NEs:
• OMSN, MW, WDM: T = 00, S = 00, P = 0002.
• ION/OMSG (full OSI and RFC1006): T = 31, S = 31, P = 31.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
In case of short address form the NSAP address length can range from 8 to 20 bytes (that
is 16 to 40 hex digits).
• If AFI= 39 is selected, text boxes IDI, Organisation ID, Area, System ID, NSAP
Selector are enabled:
AFI= 39 (ISO–DCC): a Q3 NE address is composed of 40 digits:
AFI (2 digits) + IDI (4 digits) + Organization ID (16 digits) + Area Address (4 digits)
+ System ID (12 digits) + NSAP Selector (2 digits).
• If AFI= 47 is selected, text boxes IDI, System ID, NSAP Selector and Free are
enabled:
AFI=47 (ISO 6523–ICD): the length of Q3 NE address ranges from 16 digits to 40
digits:
AFI (2 digits) + IDI (4 digits) + free part (0 to 20 digits) + System ID (12 digits) +
NSAP Selector (2 digits)'.
• If AFI= 49 is selected, text boxes System ID, NSAP Selector and Free are enabled:
AFI= 49 (Private), the length of Q3 NE address ranges from 16 digits to 40 digits:
AFI (2 digits) + free part (0 to 24 digits) + System ID (12 digits) + NSAP Selector (2
digits).
• If AFI= "free" is selected, only text box "Free" is enabled. The length of Q3 NE
address ranges from 0 digit to 40 digits: free part (0 to 40 digits)
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set SNMP NE Address
Action Menu
....................................................................................................................................................................................................................................
Set SNMP NE Address

When to use
the NE itself.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 Select the SNMP NE in the Network Element list on the MS-GUI.

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set SNMP NE Address
Action Menu
....................................................................................................................................................................................................................................
Result: The Set SNMP NE Address window is displayed
...................................................................................................................................................................................................
3 For the SNMP address insert following parameters: IP Address in dot notation, for
example 151.98.43.187, and Port number (usually it is 161).
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set 4G (TL1) NE Address
Action Menu
....................................................................................................................................................................................................................................
Set 4G (TL1) NE Address

When to use
the NE itself.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 Select the 4G TL1 NE in the Network Element list on the MS-GUI.

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Result: The Set 4G (TL1)NE Address window is displayed
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 To set the 4G (TL1) Network Element Address set following parameter:

Note: For NEs supporting multiple interfaces the Set Address wizard initial
configuration allows the definition of the primary interface. An additional panel,
enabled when supported by the target NE, allows managing user and password for the
NE access. For Network Release 9.1.1 user and password are managed for NE with
TL1 (primary) interface and for NEs implementing ZIC GUI.
On the Set Address window:
• Primary Address: IP Address/Port of primary Gateway NE for Remote NE or IP
Address/Port of Gateway NE itself for Primary Gateway NE;
• Secondary Address (optional): IP address/Port of Secondary Gateway NE for a
Remote NE or IP Address/Port of Gateway NE itself for Secondary Gateway NE;
• Primary NE Login and Password of target NE;
• Secondary NE Login and Password (optional), used as a backup login and password
for target NE;
• GNE flag: Boolean that defines if a NE has a GNE or RNE role (configurable only in
ANSI network);
• FTAM : Select the File Transfer Type for the NE.
• TID: string of NE TID (max 20 characterss), is used for TL1 commands.
TID value can be either up to 20 noncase-sensitive alphanumeric characters, including
the special hyphen (-) character, or up to 20 characters quoted string. If it is a non
quoted string, the hyphen (-) is the only special character allowed. The TID must start
with a letter and shall end with an alphanumeric character. Consecutive hyphens (-)
shall not be allowed. Number of hyphens shall be not greater than 4. If a lower-case
character string is entered for the TID, it is automatically converted to an uppercase
character string. If it is a quoted string, any character is allowed, included any special
character, and no case conversion is applied.
Passwords are encrypted. A Security Administrator from CT ZIC creates Logins and
default Passwords for EML. This EML operator, always from CT ZIC, is in charge to
change from default Passwords to new ones, because TSS NEs oblige to change password
at first connection. Login and Password are used during start supervision phase, if they
are not right, supervision fails and the user has to change the password.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Set TSS5 NE Address
Action Menu
....................................................................................................................................................................................................................................
Set TSS5 NE Address

When to use
the NE itself.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 Select an 1850TSS-5-EIU, 1850TSS-5-TIU, 1850TSS-5-SIU Network Element on the

MS-GUI NE List.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Result: The Set TSS5 NE Address window is displayed
...................................................................................................................................................................................................
3 To set the TSS5 Network Element Address set following parameter:
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
On the Set Address window:
• Primary Address: IP Address. In case of SIU: IP address of primary TL1 Gateway NE
for Remote NE or IP Address of TL1 Gateway NE itself for Primary Gateway NE. In
case of EIU/TIU: IP address of target SNMP/CLI NE.;
• Secondary Address (optional): IP address of Secondary TL1 Gateway NE for a
Remote NE or IP Address of TL1 Gateway NE itself for Secondary Gateway NE. It is
applicable only in case of SIU, greyed in case of EIU/TIU.
• Primary NE Login and Password of target NE. In case of SIU login and password for
TL1 connection. In case of EIU/TIU login and password for CLI connection.
• Secondary NE Login and Password (optional), used as a backup login and password
for target TL1 NE. It is applicable only in case of SIU, greyed in case of EIU/TIU.
• GNE flag: Boolean that defines if a NE has a GNE or RNE role (configurable only in
ANSI network); It is applicable only in case of SIU, greyed in case of EIU/TIU.
• FTAM: Select the File Transfer Type for the NE.
• TID: string of NE TID (max 20 characterss), is used for TL1 commands.
TID value can be either up to 20 noncase-sensitive alphanumeric characters, including
the special hyphen (-) character, or up to 20 characters quoted string. If it is a non
quoted string, the hyphen (-) is the only special character allowed. The TID must start
with a letter and shall end with an alphanumeric character. Consecutive hyphens (-)
shall not be allowed. Number of hyphens shall be not greater than 4. If a lower-case
character string is entered for the TID, it is automatically converted to an uppercase
character string. If it is a quoted string, any character is allowed, included any special
character, and no case conversion is applied.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Uploading the Remote Inventory
Action Menu
....................................................................................................................................................................................................................................
Uploading the Remote Inventory

When to use
Use this task to inventory the NE components.
Related information
Before you begin

Task
This function consists in launching the EML process that inventories the components of
an NE. No response is provided for this operation.
To perform this operation, proceed as follows:
...................................................................................................................................................................................................
1 Select an NE on the map window or in the inventory list.

...................................................................................................................................................................................................
2 Use the menu path: Actions > Upload Remote Inventory.

Figure 6-14 Upload Remote Inventory Dialog Box
....................................................................................................................................................................................................................................
March 2010
Network Element Management Uploading the Remote Inventory
Action Menu
....................................................................................................................................................................................................................................
Note: The uploaded Remote Inventory file can be found under the directory
/usr/Systems/EML/data/ri
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Global Remote Inventory
Action Menu
....................................................................................................................................................................................................................................
Global Remote Inventory

When to use
Use this task to check Remote Inventory state of one or several NE components.
Related information
Before you begin

Task
This function consists in launching the EML process that inventories the components of
an NE. No response is provided for this operation.
To perform this operation, proceed as follows:
...................................................................................................................................................................................................
1 Select one or more NE, that are in state Supervised, on the map window or in the
inventory list.
...................................................................................................................................................................................................
2 Use the right mouse button popup menu path: Action > Global Remote Inventory.
The following window is displayed:
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Figure 6-15 Global Remote Inventory
...................................................................................................................................................................................................
3 Select one or more NEs in the list, for which you want to check the Global Remote
Inventory state.
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Confirm the action with OK or Apply button.

Result: The status will be updated in the GRI Status field, or an error occurs.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Information about NEs
Action Menu
....................................................................................................................................................................................................................................
Information about NEs

When to use
Use this task to display the NE information.
Related information
Before you begin

Task
This section explains how to display information of a selected NE.
...................................................................................................................................................................................................
1 Select an NE on the displayed map or on the Inventory list.

...................................................................................................................................................................................................
2 Use the menu path: Actions > Network Element > Get NE Information or the popup
menu Actions > Get NE Information.
Following information windows opens:
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
Figure 6-16 Information window for an NE
This window shows the following NE information:

• NE type
• NE Release
• User Label
• Location Name
• Supervision Area
....................................................................................................................................................................................................................................
March 2010
Action Menu
....................................................................................................................................................................................................................................
• EML Domain
• Current ACD
• Comments field
This window is read–only.
To close the window, click on the Cancel push button.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Current Status Consultation
Action Menu
....................................................................................................................................................................................................................................
Current Status Consultation

When to use
This functions can be used to get the current status of a Network Element.
Related information
Before you begin

This operation is only allowed if the NE supervision state is Supervised, so check the
Network Element supervision state.
Consulting the NE Management States

To consult the management states of an NE, proceed as follows:
...................................................................................................................................................................................................
1 Select an NE on the map or in the inventory list.

...................................................................................................................................................................................................
2 Use the menu path: Action > Network Element > Get NE Current Status.
The following window opens:
....................................................................................................................................................................................................................................
March 2010
Network Element Management Current Status Consultation
Action Menu
....................................................................................................................................................................................................................................
Figure 6-17 Current Status Window for an NE
The NE user label appears in the field Current NE of the dialog box.
This dialog box is read–only.
Unused attributes are greyed.
To close the dialog box, click on Cancel push button.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management Ping NE
Action Menu
....................................................................................................................................................................................................................................
Ping NE
When to use
Use this task to ping one or several NEs to see if they are reachable.
Related Information
Before you begin

Display the Network Element list in the MS-GUI window.
Task
...................................................................................................................................................................................................
1 Select one or more NEs in the NE list and from the MS-GUI main menu.
...................................................................................................................................................................................................
2 Follow the main menu path Actions > Network Element > Ping NEs.
....................................................................................................................................................................................................................................
March 2010
Network Element Management Ping NE
Action Menu
....................................................................................................................................................................................................................................
Result: The Ping NE window is displayed.
...................................................................................................................................................................................................
3 Select Apply button to refresh the NE reachability.

...................................................................................................................................................................................................
4 Press the OK or Cancel button to close the window.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Element Management NE Global Inventory
Search Menu
....................................................................................................................................................................................................................................
Search Menu
NE Global Inventory
Description
The NE Global Inventory query retrieves the list of all the NEs defined on the system,
with the associated attributes and status. The NE Global Inventory supplies a synthetic
view of the managed network and is the starting point for management commands
(Action/Search). The NE Global Inventory is shown in the main view area of the 1350
OMS EML GUI. Filtering, searching and sorting capability, as supplied by the MS-GUI
framework, are applicable to this view.
Figure 6-18 Search - Get All NE
This window shows the list of all defined NEs and their most significant attributes.
Columns are representing the NE attributes and could be moved in a different position
(shift left/right). Filtering and sorting could be applied to each column/attribute. Rows are
representing NE instances; single and multiple selections are available. On selected
Network Element(s) is possible to apply action/commands according with the dynamic
definition of the main menu or of the popup menu (right mouse click). Attribute values
shown into this window are automatically updated when AVC notification are received.
....................................................................................................................................................................................................................................
March 2010
Network Element Management NE Global Inventory
Search Menu
....................................................................................................................................................................................................................................
The available list of NE could be filtered according to values given to the following
attributes (filtering criteria):
• ACD;
• Alarm Status;
• EML Domain;
• LAC;
• Location Name;
• Release;
• Supervision Area;
• Supervision State;
• Type
....................................................................................................................................................................................................................................
March 2010
Network Element Management EML Domains
Search Menu
....................................................................................................................................................................................................................................
EML Domains
Description
From the Search menu the user can obtain the list of the EML Domains defined in the
1350 OMS System.
Follow the path Search > EML > EML Domains, the list of EML Domains is displayed in
From the Domains list the use can display the list of Network Elements belonging to the
selected domain in the list.
Select the domain in the list and from the popup menu the path Search > Network
Element. The list of NE belonging to the domain is displayed. The Domain is shown in
the list title, as shown in the following figure.
....................................................................................................................................................................................................................................
March 2010
Network Element Management EML Instances
Search Menu
....................................................................................................................................................................................................................................
EML Instances
Description
From the Search menu the user can obtain the list of the EML Instances defined in the
1350 OMS System.
Follow the path Search > EML > EML Instances, the list of EML Instances is displayed in
From the Instances list the user can display the list of EML Domains belonging to the
selected instance in the list.
Select the instance in the list and from the popup menu the path Search > EML Domains.
The list of Domains belonging to the instance is displayed. The Domain is shown in the
list title, as shown in the following figure.
....................................................................................................................................................................................................................................
March 2010
Network Element Management EML Instances
Search Menu
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
Network Element Management Navigations and Inventories
Navigations
....................................................................................................................................................................................................................................
Navigations
Navigations and Inventories

Navigation towards Other Applications
The navigation interface allows to switch between different EML application GUI
keeping the focus on a single object, for example : a Network Element, a port, the alarm
set of a NE, in order to have a different view of the object or a different set of
operations/feature to manage the object itself. 1350 OMS EML application can be
integrated with other applications which allows the user to:
• Manage alarms.
• Visualize and configure the NE equipment.
• Manage Performance Monitoring data.
Alarm Management
Thanks to Alarm Surveillance application, you can perform operations on the alarms
occurring on an NE. To access Alarm Surveillance, proceed as follows:
• Starting from Multi Service GUI, select a Network Element on the map on the
inventory List.
• Use the main menu path: Search > Network Element > Show NE Alarms or from the
popup menu Search > Show NE Alarms.
The AS Alarm sub–list window related to the selected NE opens.
We may also decide at integration time that there will be only one Alarm sub–list window
for all the currently selected NEs.
Refer to the ALMAP AS User's Guide for more information about the alarm management.
Visualizing Alarm Information
For each NE symbol present within a sub–map, the AS application allows the display of
the corresponding alarm synthesis information:
• A flashing symbol when the NE is impacted by incoming alarms.
• The total and acknowledged active alarm numbers.
• The most severe alarms.
Refer to the ALMAP AS User's Guide for more information about the NE symbol
management by AS
....................................................................................................................................................................................................................................
March 2010
Network Element Management Navigations and Inventories
Navigations
....................................................................................................................................................................................................................................
Navigating towards an Equipment View
To navigate towards an equipment (or a CNE) view, proceed as follows:
• Starting from Multi Service GUI, select a Network Element on the map or on the
inventory List.
• Use the main menu path: Search > Network Element > Show Equipment or from
the popup menu Search > Show Equipment.
The equipment view related to the selected NE opens.
Refer to the external application documentation for more information.
Navigating towards Performance Monitoring

To navigate towards Performance Monitoring view, proceed as follows:
• Use the main menu path: Search > PM > PM Domains on EML.
The Performance Monitoring view related to the selected NE opens.
Refer to the external application documentation for more information.
....................................................................................................................................................................................................................................
March 2010
Network Element Management Overview
....................................................................................................................................................................................................................................
Changing an OS Address
Function
NEs exchanging their management information directly with the OS need addressing
information in order to be able to communicate with the OS across the network. Such an
OS address is conveyed to the NE by the EML agent during the creation process.
Actually certain types of NEs have two OS addresses at their disposal: the main OS
address and a spare OS address, enabling them to switch from one OS to another. This is
intended to support, for instance, OS resilience or OS migration.
At the beginning, both addresses conveyed to the NE are identical, and they are known by
the EML agent by configuration. The given address relates to the workstation which hosts
the EML agent.
Once the NE is created, each OS address may be individually changed (for NEs which
support it).
To change an OS address, proceed as follows:
Select an NE whose supervision state is Supervised on the Topology Management map.
Use the menu path: Actions > Network Element > Set OS Address.
....................................................................................................................................................................................................................................
March 2010
Network Element Management Changing an OS Address
....................................................................................................................................................................................................................................
Figure 6-19 OS Address Dialog Box
....................................................................................................................................................................................................................................
March 2010
Network Element Management Changing an OS Address
....................................................................................................................................................................................................................................
The user label of the NE whose OS addresses are to be changed is reported in the
Selected NE box..
The first time an OS Address dialog box opens, the OS Main Address and OS Spare
Address (known by configuration) are displayed in the corresponding fields.
You can change the main OS presentation (PSAP) address in accordance with the ISO
definition (AFI, IDI, Organization Id., Area, System Id. and Sel. fields).
You can also change the optional spare OS PSAP address by using the same format.
Note: The OS main address can only be changed if the NE is supervised (i.e. its
supervision state is Supervised). However the OS Address dialog box can always be
displayed whatever the supervision state is and you can change the OS spare address
in all cases.
Validating the OS Addresses
To validate the modifications in the dialog box, click on the Apply push button.
....................................................................................................................................................................................................................................
March 2010
7 7 SS Network Element
T
Management
Overview
Purpose
The aim of this chapter is to describe the management of Network Elements of type 1850
TSS-x, integrated in 1350 OMS EML Subsystem.
Contents
Product overview 7-2

1850TSS Product Family 7-2
1850 TSS Management in 1350 OMS EML 7-3
1350 OMS EML activation 7-4
Access to the 1350 OMS EML System 7-4
Preliminary Operations 7-5
New Account on Network Element 7-6
New Account on EML 7-9
User Profiles 7-14
1850 TSS Network Element Management 7-15
1850 TSS Network Element Creation 7-16
1850 TSS Network Element Supervision 7-22
Navigations 7-23
Ping NE 7-24
Alarm Management and Navigations 7-25
Alarm Management 7-25
Navigations 7-26
...................................................................................................................................................................................................................................
March 2010
TSS Network Element Management 1850TSS Product Family
Product overview
....................................................................................................................................................................................................................................
Product overview
1850TSS Product Family

Description
The 1850 Transport Service Switch (TSS) is a new breed of multi-service transport
platform able to support any mix of traffic from 100% circuits to 100% packets. This is
achieved by a unique technology-independent (universal) switch capable of switching
packets or circuits in their native format and transporting them as they are, thus
optimizing overall transport network efficiency for any bandwidth requirement of current
and future broadband applications. With one single platform service providers can address
the transition from (TDM)/circuit based transport towards packet transport with a flexible
provisioning of carrier Ethernet/transport MPLS, SONET/SDH, WDM and OTN
technologies in any proportion with only a simple change of the line cards. This flexibility
ensures providers can support any current and future traffic requirement by eliminating
scalability issues encountered by traditional multiservice provisioning/transport platform
(MSPP / MSTP) solutions as packet-based traffic grows. The 1850 TSS provides service
providers with the configuration flexibility to build with the same platform a scalable
MSPP and a powerful carrier Ethernet transport switch with integrated WDM capabilities.
This offers service providers total freedom in planning network resources to support the
delivery of new broadband network applications such as Triple Play, IP Video, Mobile
and Ethernet business services, while ensuring seamless interworking with the existing
transport assets that support existing revenues.
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management 1850 TSS Management in 1350 OMS EML
Product overview
....................................................................................................................................................................................................................................
1850 TSS Management in 1350 OMS EML

Integration
The management of 1850 TSS NEs is based on Zero Installation Code (ZIC) application
which allows to access the NE user interface. EML architecture on 1350OMS-EML
platform is based on agent / manager schema, which is also used for EML-USM in order
to graphically display NE information. ZIC GUI is the evolution of EML-USM and uses a
different approach, based on HTTP or HTTPS requests directly sent to NE without using
EML-IM.
ZIC GUI Manager is in charge of provide several functionalities in different scenarios:
• Authentication of the ZIC GUI session accomplished verifying the provided token
with Session & Authentication Service (SAS).
• Authorization accomplished retrieving from Security application the security
information for the connected operator and sending it to the NE.
• Gateway between ZIC GUI and NE, mandatory when there is no ability to reach DCN
from the machine running ZIC GUI.
• Catch some requests that need some extra processing before dispatch them to NE, for
example software download, which needs the list of available packages to download.
• Local process of particular requests that cannot be forwarded to NE, for example
navigations requests coming from GUI ZIC and directed towards generic components.
In order to accomplish to its requirements, ZIC GUI Manager has several external
interfaces, which let this component connect to SAS, SEC-IM, NAV Router, OAM and all
web server for NE. 1850 TSS are managed as any other Network Element by EML.
Operations carried out by 1350OMS-EML on TSS are:
• Create TSS NE starting from NE Global Inventory or provisioning map.
• Start/Stop Supervision of TSS NEs.
• Show Equipment.
• Alarm management.
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management Access to the 1350 OMS EML System
....................................................................................................................................................................................................................................
Access to the 1350 OMS EML System

The Web Desktop
The 1350 OMS EML is now integrated in the Multiservice GUI application. The
description to use Web Desktop and Web Portal can be found in “System access from
Desktop” (p. 1-7)
Select Provisioning > Network Management to activate the Multiservice GUI.
Figure 7-1 Web Portal application - MS-GUI Activation
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management Overview
....................................................................................................................................................................................................................................
Overview
Purpose
This section explains the preliminary operations to be done in order to manage a 1850
TSS NE from 1350 OMS EML NE Global Inventory application. These operations should
be done before activating any 1350 OMS EML function towards a TSS Network Element.
Contents
New Account on Network Element 7-6

New Account on EML 7-9
User Profiles 7-14
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management New Account on Network Element
....................................................................................................................................................................................................................................
New Account on Network Element

Create a new Account on TSS Network Element
The first operation to be fulfilled is the creation of a new account on the TSS Network
Element. Connect to the TSS NE using the Web Browser inserting the NE address,
following window will be displayed:
Figure 7-2 Create Account selection on NE ZIC GUI
For managing the NE a user account can be created with Network Administration profile.
For example the new account can be DOC001.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-3 TSS Account List
The first time you login with the new account, the system asks to change the password.
Do this operation to proceed and login towards the TSS NE.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-4 Change password window on TSS NE ZIC GUI
Finally the login on TSS NE is possible.
Figure 7-5 Login window on TSS NE ZIC GUI
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management New Account on EML
....................................................................................................................................................................................................................................
New Account on EML

Create the Account on EML System
The same account created on the TSS NE should be created on the EML System. To
perform the operation follow the path Tools > Security Management > SEC User
Administration on Web Portal application.
Figure 7-6 Account creation on EML System
Insert in login field the same value inserted in the ZIC Account creation. In our example
the login will be DOC002. The password can be also different, but it is recommendable to
use the same value. Confirm the password inserted. Remember to insert the Name
Attributes on the Attributes window.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-7 Attribute Name Value
Save the new account with the Apply button.

The new account created should be declared. To do this operation follow the path Tools >
Security Administration > SEC User Authentication GUI
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-8 SEC User Authentication GUI
To authenticate the created user follow the path Tools > Show > Operators, then click on
Operators on the left tree and the right mouse button, select Declare Sec Users from the
popup menu as shown below
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-9 Declare Sec Users Selection
The list of the created users is displayed, only the users not yet declared appear in the list.
Use the Add Users button to declare the new user. The user appears in the Sec Users list.
To get the user operative in the EML System perform the Unlock operation selecting the
user in the list and clicking on the Unlock button.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-10 Declare the new user
The profile for the new user should be set in order to manage the TSS NEs in a correct
way.
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management User Profiles
....................................................................................................................................................................................................................................
User Profiles
Assign the User Profiles
Follow the path Tools > Show > Operator Profiles. Select the new created user to assign
the right profiles. If the user manages administrative operations, then an admin profile
should be assigned, but if the user manages Network Elements in the Management
Network, then an Opertaor profile should be sufficient. Select the profiles and click on the
> button. More than one profile can be assigned. Select the Apply button to confirm the
profile selection.
Figure 7-11 Operator Profile Setting
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Overview
Purpose
The aim of the described operations is to create and supervise the 1850 TSS Network
Element in the 1350 OMS EML environment. The operations are described starting from
NE Global Inventory application, but they can be done also from MS-GUI Framework
interface.
Contents
1850 TSS Network Element Creation 7-16

1850 TSS Network Element Supervision 7-22
Navigations 7-23
Ping NE 7-24
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management 1850 TSS Network Element Creation
....................................................................................................................................................................................................................................
1850 TSS Network Element Creation

The Creation
In order to manage 1850 TSS Network Elements from 1350 OMS EML a new Network
Element should be created. The creation of the new Network Element starts from
Management Network application, to open the application select from Web Portal
application Provisioning NE Inventory.
Figure 7-12 NE Global Inventory activation
To create the 1850TSS Network Element select from the Multiservice GUI main menu
Actions > EML > Create NE as shown in following figure.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-13 1350 OMS EML Create Network Element
The above selection will display the NE Creation window where the new Network
Element data should be inserted.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-14 1850 TSS NE Creation
Network Element data to insert for the 1850 TSS NE creation are:
• Family: TransportServiceSwitch.
• Type: 1850TSS-100, 1850TSS-15, 1850TSS-3, 1850TSS-5, 1850TSS-5-EIU,
1850TSS-5-SIU, 1850TSS-5-TIU, 1850TSS-320, 1850PSS-1, 1850PSS-32.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
• Release: depends on the NE Type selected.
• User Label: User Label for the Network Element, it is the same assigned on the NE.
• Location Name: where the NE is positioned.
• Supervision Area: select the LAN where the NE is connected.
• EML domain: select from the list the domain corresponding to the EMLServer. The
information about the domain can be found in the System Configuration window.
• Access Control Domain: select the ACD from the list.
Click on the OK button to confirm the Network Element creation and then click on the
Close button to close this window.
After the NE creation, the 1850 TSS IP address should be assigned to the new Network
Element. To set the NE address, select the NE on the NE list and from the Action menu
Actions > Set NE Address > Set 4G(Q3) NE Address from the menu.
After the selection a dialog box to insert the IP address is displayed, as shown hereafter:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-15 1850 TSS Set Address
The data to insert are

• The Primary Address is the NE IP Address and the port on which it is configured.
• The Primary User Id is the user on the NE and the user created on the EML System.
• The Primary Password is the password defined on the 1850 TSS Network Element.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Click on the OK button to confirm the Network Element creation, the click on the Close
button to close this window.
After this operation, the Network Element creation is completed.
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management 1850 TSS Network Element Supervision
....................................................................................................................................................................................................................................
1850 TSS Network Element Supervision

Start Supervision
After the creation, a Network Element should be supervised by 1350 OMS EML
Subsystem in order to be managed by the Network Management system. Select on the
Multi Service GUI the NE on the NE list and from the popup menu Actions >
Supervision > Start Supervision.
A box is displayed with the operation result. To start the supervision click the button Yes
and wait for the operation to finish. If the operation fails, the details about the errror
occurred can be seen on the log window on the multiservice GUI.
Figure 7-16 Error Details
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management Navigations
....................................................................................................................................................................................................................................
Navigations
Navigation from 1350 OMS EML NE list to USM
Once 1850 TSS is supervised, navigation to the ZIC GUI management application is
allowed selecting the TSS Network Element in the list and from the popup menu Search
> Show Equipment.
This operation opens the 1850 TSS ZIC user interface as shown in following figure.
Figure 7-17 1850 TSS User Interface
....................................................................................................................................................................................................................................
March 2010
TSS Network Element Management Ping NE
....................................................................................................................................................................................................................................
Ping NE
Test NE Reachability
A useful function to test the 1850 TSS NE reachability from 1350 OMS EML is the "Ping
NE" function. Select the 1850 TSS NE on the NE Inventory list on Multiservice GUI,
select from the menu Actions > Network Element > Ping NE. The Ping NE window is
displayed, select the NE and click on the push button Apply to start the ping operation.
The result will be displayed after a few seconds as shown in following figure.
Figure 7-18 Ping NE result
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Alarm Management
Alarms for 1850 TSS
Alarms are managed by a generic component called AS (Alarm Surveillance) integrated
in the common platform MW-INT and can be activated from Web Portal window. For
1850 TSS NEs a list of the corresponding alarms can be see using AS USM. Starting from
Web Portal window menu the main AS USM window is displayed as shown in following
figure. This list contains all the alarms received.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Navigations
Navigation from AS to 1850 TSS USM
Starting from the main alarm list window it is possible to navigate to 1850 TSS USM
selecting Navigation > External Application > Related EmlUsm. Each time a navigation
is selected a new SANman USM window will be opened.
Figure 7-19 Navigation to AS application
Selecting the above navigation the TSS USM is displayed.
Navigation from Multi Service GUI to AS USM

On the other side it's possible to navigate from Multi Service GUI NE List, selecting the
TSS Network Element, to AS USM displaying the alarm's sublist concerning TSS
Network Element alarms. From the MS-GUI, select the TSS Network Element and from
the main menu follow the path Search > Network Element > Show NE Alarms.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-20 Navigation to AS USM
The list of 1850TSS alarms will be displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 7-21 TSS NE Alarms Sublist
....................................................................................................................................................................................................................................
March 2010
8 Performance Monitoring
8
Overview
Purpose
This section describes the main functionality of Performance Monitoring management
from EML application, which offers a graphical user interface to generate different types
of reports for performance monitoring data.
Performance management in the context of CPM application means the storage of historic
performance data of managed Network Elements, reporting of the stored performance
data, and long term trend analysis of the stored performance data.
1350 OMS EML provides the following functionality related to management of
performance data collected by each NE:
• Start and Stop PM on a specific TP (Termination Point) through USM. Also CT and
other NML managers may start or stop PM.
The following different measurement types may be started:
– Digital PM with either 15 minutes or 24 hour granularity.
– Ethernet PM with either 1-hour or 24 hour granularity.
– Analog PM with either 15 minutes or 24 hour granularity.
• Periodical collection of PM data from each NE.
The collection is done:
– Once a day for 24h PM data.
– Once every two (but this value is configurable in EMLIM configuration files)
hours for 15min and 1h PM data.
• Forced collection of all PM data of a NE through EML–USM.
• Navigation to CPM GUI for display of PM historical data and graphical reports built
on top of them.
PM data collection is triggered by:
• Either EML–IM (periodical PM collection).
• Or EML–USM (forced collection).
...................................................................................................................................................................................................................................
March 2010
Performance Monitoring Overview
....................................................................................................................................................................................................................................
EML–IM collects the PM data by NE in one of the following two ways:
• Either through a file transfer session (in case of 4G NEs).
• Or though a set of Q3 or SNMP requests (for all other NEs).
A specific process (Perfstorage) processes the PM config files written by EMLIM and, for
each NE, saves:
• A file to be used by CPM GUI for inserting PM collection data inside MySQL
database.
• A file to be used by IOO or other external products.
Contents
Performance Monitoring 8-3

Accessing Performance Monitoring 8-3
Performance Monitoring Reports 8-5
Create a Report 8-5
Reporting Criteria 8-9
Filters 8-12
Search 8-13
Report Destination 8-18
Report Options 8-20
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Accessing Performance Monitoring
....................................................................................................................................................................................................................................
Accessing Performance Monitoring

Start the Application
The Performance Monitoring application is included in 1350OMS-EML Subsystem and
can be activated:
• From MS-GUI window: Search > PM > PM Domains on EML
Figure 8-1 EML Performance Monitoring selection from MS-GUI
The list of PM domains on EML is displayed.
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Accessing Performance Monitoring
....................................................................................................................................................................................................................................
Figure 8-2 PM Domains on EML List
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Overview
....................................................................................................................................................................................................................................
Create a Report
When to use
When the user wants to do performance analysis of Performance Monitoring, a report
should be generated.
Related Information
Related information can be found at “Accessing Performance Monitoring” (p. 8-3)
Before you begin

Open the MS-GUI application.
Generating Reports
To generate a report following steps are required starting from MS-GUI window:
...................................................................................................................................................................................................
1 Follow the path Search > PM > PM Domains on EML.

Result: The list of EML PM domains is displayed.
...................................................................................................................................................................................................
2 Select a domain in the list and follow the path from the popup menu Search > Monitored
NEs/TPs.
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Create a Report
....................................................................................................................................................................................................................................
Result: The list of monitored NEs is displayed:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Select a monitored NE from the list and use the popup menu Search > Monitored
NEs/TPs..
Result: The list of the monitored TP for the NE is displayed.
...................................................................................................................................................................................................
4 Select a monitored TP from the list and use the popup menu to select the desired report.
Actions > Generate Report
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The possible options are
• Generate Tabular Report
• Generate LineChart Report
• Generate BarChart Report
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Reporting Criteria
....................................................................................................................................................................................................................................
Reporting Criteria
Setting Reporting Criteria
After choosing the report type (tabular, linechart or barchart) a criteria window is
displayed to choose the Reporting Criteria (report period, granularity) to direct the
contents of a report.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 8-3 Set reporting Criteria
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Setting the reporting criteria includes:
• Reporting Period : The user must enter the From Time and the End Time selecting it
from the displayed calendar. Start Date must be before end date, otherwise an error
occurs in the report generation.
• Selecting granularity from a list of selectable Granularities. Granularity cannot be set
for Reference Value Reports.
Confirm the selection with OK or Apply button.
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Filters
....................................................................................................................................................................................................................................
Filters
Filtering criteria
A filter combination can be optionally chosen to filter the Performance Entity in the list as
shown in figure below:
Figure 8-4 Select filtering criteria
The operator can filter by choosing a single filter or a combination of filters.

Basic filters available now are:
• No Filtering.
• Supported Granularities .
• User Label
These filtering criteria applies on the Monitored NE list and also on the monitored TP list
After filtering, the performance entity list will show only those performance entities that
match the filtering criteria.
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Search
....................................................................................................................................................................................................................................
Search
Search by Name
The user can Search to select Performance Entities in the Performance Entity list as
shown in following picture. From the Monitored NE list, select a NE and follow the path
from the popup menu Actions > Search by Name:
Figure 8-5 Search Functions
If the selection is Search by Name following window is displayed:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 8-6 Search Window: TP Name
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
This window consists of these areas:

StartPoints consists of the NE selected.
TpType contains the list of names of TP types, click on the list icon to view the list and
select the desired name for this search.
NETypeRelease contains the list of NE types and releases, click on the list icon to view
the list and select the desired type and release for this search.
Click on OK or Apply to run the search.
Search by Value
The user can Search to select Performance Entities in the Performance Entity list as
shown in following picture. From the Monitored NE list, select a NE and follow the path
from the popup menu Actions > Search by Value:
Figure 8-7 Search Functions
If the selection is Search by Value following window is displayed:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 8-8 Search Window: TP Value
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Following data can be entered in the window:
• Search Period : UserSpecific, the user can choose start and end period, Last...Until,
the user can insert the End Time and Granularity, Latest, the user can choose the
granularity, Current , the user can choose the granularity.
• Search Values : the user can combine with AND and OR operator five Counters, the
counters are chosen from the list and each counter can be set >, = or < to a value
specified by the user.
Click on OK or Apply to run the search.
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Report Destination
....................................................................................................................................................................................................................................
Report Destination
Setting Destination
The user can specify the export of TP to a comma separated file that will be generated.
From the PM Domain list, select one or several PM domain on EML and follow the path
Actions > PM Domain > Export TPs to CSV file. The corresponding window is displayed.
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Report Destination
....................................................................................................................................................................................................................................
Figure 8-9 Report destination selection
Insert the destination name for the CSV file. Confirm with OK or Apply button.
....................................................................................................................................................................................................................................
March 2010
Performance Monitoring Report Options
....................................................................................................................................................................................................................................
Report Options
Setting Report Options
The operator wants to set presentation options before or after report generation.
Figure 8-10 Setting presentation options
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Setting the report options includes:
• Setting unified counter name : check the box to have the counter names unified..
• Set time shift : the user can choose between use end time or use start time. The current
time shift is displayed.
Confirm the selection with OK or Apply button.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
9 9 etwork Physical
N
Resources Management
Overview
Purpose
This section describes the main functionality of NPR component (Network Physical
Resources). The NPR is a subsystem of the 1350 OMS Network Management solution, in
the scope of the physical network construction handling. It covers an application
managing physical network, network elements, physical ports and links.
Contents
NPR Application 9-2

Network Physical Resources 9-2
NPR Search Functions 9-4
EML Domains 9-4
Nodes 9-7
Physical Connections 9-11
NPR Actions 9-14
Create Physical Connection 9-14
Create Alarm Profile 9-17
Create External Network 9-20
Discover Physical Topology 9-22
...................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Network Physical Resources
NPR Application
....................................................................................................................................................................................................................................
NPR Application
Network Physical Resources

Application Overview
The NPR subsystem is devoted to the handling of a physical network, including network
elements, physical ports and links.
The main functionalities provided by NPR subsystem can be grouped as follows:
• System configuration: NPR supports different system configurations
• Supported Network Elements: NPR supports the management of different Network
Elements with different technologies
• Physical network discovery: NPR allows the discovery of the physical network
resources, such as network elements and physical ports
• Physical network construction: NPR allows the construction of the physical
network, in term of physical links, starting from the discovered physical network
resources. The physical network construction can be performed both manually and
automatically. The construction is successful only if the proper information are
provided by the network elements.
• Physical network management: NPR allows the management of the
created/discovered physical network
• Physical network maintenance: NPR allows the management of the alarms received
from the physical network resources, correlating them to the physical links
• Inventories: NPR allows the rendering of information managed by the NPR itself
• Command Line Interface: NPR allows the operator to perform commands by means
of a CLI (batch mode)
• Northbound Interfaces: NPR allows to expose its network view and provisioning
capabilities to other OSS client application (Alcatel-Lucent or not)
According to the flexibility, provided by the 1350 OMS architecture, to install only the
applications that are required by the customer, NPR can work with any combination of
the supported applications (SDH, SONET, WDM and PKT).
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Network Physical Resources
NPR Application
....................................................................................................................................................................................................................................
Figure 9-1 NPR activation
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management EML Domains
....................................................................................................................................................................................................................................
EML Domains
When to use
When the user wants to list the EML domains defined on the 1350 OMS system..
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 From the MS-GUI main menu bar select Search > Physical > EML Domains
Result: The EML Domains list is displayed.
...................................................................................................................................................................................................
2 Selecting a domain from the list it is possible using the right mouse button to display the
popup menu.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Following the path Search > NEs, the Network Elements defined for the selected EML
domain are listed.
...................................................................................................................................................................................................
4 Following the path Search > Show > Active Alarms, the active alarm list is displayed
filtered on the selected EML domain.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Nodes
....................................................................................................................................................................................................................................
Nodes
When to use
When the user wants to list the nodes defined on the 1350 OMS system..
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 From the MS-GUI main menu bar select Search > Physical > Nodes
Result: The nodes list is displayed.
...................................................................................................................................................................................................
2 Selecting a node from the list, it is possible using the right mouse button to display the
popup menu.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 For a node the user can display following lists.

Search ⇒
• NAPs (Network Access Points)
• TTPs (Trail Termination Point)
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
• CTPs
• Cross Connections
• HO CTPs
• LO CTPs
• MS-TPs
• Subnetwork Point Poll (SNPP) Links
• Paths
• Starting/Ending Paths
• Starting/Ending HO Trails
• Ports
• NEs
• Node View
• Paths (with Source/Sink)
• Starting/Ending Paths (with End Points)
• NAPs (with Path Information)
• Physical Connections
• Physical Connections (with End Points)
• NPAs
• Control Plane
• SDH CTPs Statistics
• NAPs Statistics
• Show ⇒ Equipment View
• Alarmed Objects
• Not aligned TPs and Cross Connections
Each of this functionality has different behavior depending on the node's technology :
SDH, Ethernet, WDM, ... For further information refer to the technology specific
documentation, see “Related documentation” (p. xxix)
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Physical Connections
....................................................................................................................................................................................................................................
Physical Connections
When to use
When the user wants to list the physical connections defined on the 1350 OMS system..
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 From the MS-GUI main menu bar select Search > Physical > Physical Connections
Result: The physical connection list is displayed.
...................................................................................................................................................................................................
2 Selecting a physical connection from the list, it is possible using the right mouse button to
display the popup menu.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 For a physical connection the user can display following lists.

Search ⇒
• Ports
• Show Active Alarms
• Show Elementary Alarms
• Alarm Profile
• Show ⇒ Active Alarms
Each of this functionality has different behavior depending on the physical connection's
technology : SDH, Ethernet, WDM, ... For further information refer to the technology
specific documentation, see “Related documentation” (p. xxix)
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Overview
NPR Actions
....................................................................................................................................................................................................................................
NPR Actions
Create Physical Connection

When to use
When the user wants to create a physical connection on the 1350 OMS system..
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 From the MS-GUI main menu bar select Actions > Physical > Create Physical
Connection
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Create Physical Connection
NPR Actions
....................................................................................................................................................................................................................................
Result: The Create Physical Connection wizard window is displayed.
...................................................................................................................................................................................................
2 The possible physical connection types are : SDH, WDM, SDH/WDM Interworking,
Generic Digital Client/WDM Interworking, ETH/WDM Inteworking, Ethernet, SONET,
SONET/WDM Interworking. Selecting a connection type from the list it is possible define
the connection with the particular characteristics. For details concerning each type of
connection refer to the technology documentation in “Related documentation” (p. xxix).
In the figure you can see an example for WDM Physical connection.
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Create Physical Connection
NPR Actions
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Confirm the physical connection creation with OK or Apply button.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Create Alarm Profile
NPR Actions
....................................................................................................................................................................................................................................
Create Alarm Profile

When to use
When the user wants to create a new Alarm Profile on the 1350 OMS system..
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 From the MS-GUI main menu bar select Actions > Physical > Create Alarm Profile
....................................................................................................................................................................................................................................
March 2010
NPR Actions
....................................................................................................................................................................................................................................
Result: The Create Alarm Profile window is displayed.
...................................................................................................................................................................................................
2 Insert a User Label for the Alarm Profile to be created.

...................................................................................................................................................................................................
3 For each Probable Cause listed the corresponding Alarm Severity can be defined..
....................................................................................................................................................................................................................................
March 2010
NPR Actions
....................................................................................................................................................................................................................................
Then select for each probable cause in the list the severity to be assigned:
• Critical
• Minor
• Major
• Warning
• Indeterminate
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Create External Network
NPR Actions
....................................................................................................................................................................................................................................
Create External Network

When to use
When the user wants to create an external network on the 1350 OMS system. An External
Network is a NE that is created to represent a NE that is not managed by the NPR
application itself, such as a not Alcatel-Lucent NE. This ENE can be used as end points of
SDH, SONET and ETH physical connections.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 From the MS-GUI main menu bar select Actions > Physical > Create External Network
Result: The Create External Network window is displayed.
...................................................................................................................................................................................................
2 Insert a User Label and a Location Name, both fields are mandatory.
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Create External Network
NPR Actions
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Confirm the creation with OK or Apply button.

Result: The new external network is created.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Network Physical Resources Management Discover Physical Topology
NPR Actions
....................................................................................................................................................................................................................................
Discover Physical Topology

When to use
When the user wants to discover physical connections defined on the 1350 OMS system.
NPR allows the discovery of the physical network resources, such as network elements
and physical ports.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 From the MS-GUI main menu bar select Actions > Physical > Discover Physical
Topology
....................................................................................................................................................................................................................................
March 2010
NPR Actions
....................................................................................................................................................................................................................................
Result: The Discover Physical Topology wizard window is displayed.
...................................................................................................................................................................................................
2 Depending on which kind of connectivity the user wants to upload, select an item from
the list.
For details on the different connectivity upload procedures see 1350 OMS SDH User
Guide, Vol 1: Basic Management1350 OMS SDH User Guide, Vol 1: Basic Management,
section 2.6 (Discovery Topology and Connections) and 1350 OMS SDH User Guide, Vol
....................................................................................................................................................................................................................................
March 2010
NPR Actions
....................................................................................................................................................................................................................................
2: Enhanced Solutions, section 2.3 (WDM Network Create).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
10 10
Procedures for EML
Configuration
Overview
Purpose
The aim of this chapter is to describe some procedures clarifying all the necessary items
to achieve specific functionalities and configuration. For the correct understanding of this
Procedures Manual all the commands described in the 1350OMS-EML User Guide have
to be considered known.
Q3 Based NE Management explains concepts related to the new Q3 MIB management
OMSN and ATM Board Management for NM Operator explains how to configure and
manage the ATM ISA board.
Procedures to Handle Transmission Alarms explains how to consider the transmission
alarm in NM system.
Alarm Severity Assignment Profile (ASAP) Customization for OMSN explains how to
assign a customization ASAP to a PDH path. The procedure must be executed on 1350
OMS EML and on 1350 OMS SDH.
Contents
Q3 based NE management 10-3

Data storage and recovery procedures 10-3
The backup of Q3 NE into 1350 OMS EML 10-6
The on–board simulator of Q3 NE into 1350 OMS EML 10-13
SDH behavior towards the MIB–less architecture 10-19
OMSN and ATM board management 10-21
Introduction 10-21
OMSNs and ISA board: PNM customization 10-22
ISA Board Creation 10-24
...................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Overview
....................................................................................................................................................................................................................................
Set ISA Board Address 10-28

OMSN + ISA: Supervision 10-31
Rename OMSN Network Element and all ISA boards 10-33
Error Recovery 10-36
Procedures to handle Transmission Alarms 10-37
Introduction 10-37
Why Transmission alarms are not shown at subrack view? 10-38
How to identify transmission alarms starting from NE subrack view 10-40
Transmission alarms sub–list in AS component. 10-44
Alarm Severity Assignment Profile for OMSN 10-45
Introduction 10-46
Customizing a new ASAP on NM–OS 10-47
Object Assignment Domain 10-52
How to define OAD 10-52
File Transfer Scheduler 10-63
Introduction 10-63
Job Planning 10-66
FT Scheduler Job Descriptor 10-67
Create an FTS Job 10-68
File Transfer Scheduler Job Editor 10-71
FTS Job Status 10-74
View Report 10-76
Software Status 10-78
DCN network example 10-86
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Data storage and recovery procedures
....................................................................................................................................................................................................................................
Data storage and recovery procedures

Introduction
In NR5, the MIB–less architecture has been adopted in NM concerning the management
of Q3 NEs. This implies that 1350 OMS EML system does not mirror the NE
configuration, and directly uses the NE itself as a reference configuration base.
This has a bunch of consequences in the procedures to be used by the Network Operators
in managing the Network, e.g. backup/restore and configuration alignment procedures.
Moreover, a new entity appears in the scope of the management of Q3 Network Elements,
the NE on–board simulator on 1350 OMS EML management platform.
This technical description aims at describing the new management architecture, why and
how the NE on–board simulator shall be used when managing a Telecommunication
Network, and how the management procedures are impacted from Operator viewpoint.
The MIB–less architecture of 1350 OMS EML

1350 OMS EML is the Element Management platform that provides the Network
operator with the capabilities to configure and monitor the supported Network Elements
(NEs). The 1350 OMS EML product allows managing NEs different both in transmission
technology (SDH, WDM, Radio, ATM, IP) and in management interface they provide
towards the management system (Q3 and SNMP). In this paper, we will focus on Q3
technology.
The 1350 OMS EML implements an important architecture change in the management of
Q3 NEs, the so–called "MIB–less architecture".
As far as Q3 NEs are concerned, no replication of NE configuration data is kept within
NM and the NM relies on the database stored within the Q3 NEs themselves. This is due
to the capability of NM to manage very big NEs (i.e. DXCs) so that it is not reasonable to
duplicate the NE configuration inside NM and to perform configuration synchronization.
This MIB–less architectural choice has some consequences on the Network Management
in general, on management procedures and on Operator perspective. It is worth reminding
once more that this new concept applies to the management of Q3 NEs only.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The following list includes the main concepts associated to this new architecture:
1. The reference database for NM is the NE database itself. The NM operator actually
works on the NE database, and not anymore on a local copy of the NE configuration.
Only some administrative NE configuration data are stored within the NM (typically
NE name, location, address, and some other few information). This choice avoids any
possible problem of de–synchronization of data between EML and NE.
2. The Data Communication Network (DCN) connecting the NM to the NE assumes a
bigger relevance both in terms of reliability and rate. In fact, the faster the network,
the faster the response time of the system in displaying NE configuration data (normal
USM views). Moreover, if the NE is isolated, the operator has no possibility (in
principle, see later chapter on simulator) to see its actual configuration.
3. The MIB–less architecture implies that there is no need at (re–) connection time for
the NM to perform a complete database resynchronization against the actual NE
configuration. Only alarms, the identification of monitored Termination Points and
some few other configuration data have to be synchronized at connection time.
Figure 10-1 Q3 NE NM connection types
RM DB
RM
optics –IM
2 USM
1
1
Q3 EML –IM
2
OPTICS –IM
Q3 NE
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Despite the fact that NM is not any more the repository of the NE configuration for Q3
NEs, NM product maintains a central role in the management of the network and in
recovery procedures. The following list includes the main functions (visible or not to the
operator) that can be performed only from NM:
1. The NM is still the unique management system directly connected to the NEs (with
the only exception of 1664SX which can be directly managed by 1354NP for
restoration purposes). Any other management system (SDH, SY, PKT…) which needs
to act on the NE has to pass through the NM.
2. The NM product is responsible for establishing and maintaining the OSI association
with the managed NEs. It is up to the NM to retry to establish the OSI association
after any disconnection of the management link.
3. The NM is responsible for the handling of alarms generated by the NE, also with
respect to upper managers so acting as a sort of mediation device.
4. The NM is responsible for the collection of PM historical data from the NE,
independently of the Manager who started them.
5. The NM is responsible for the recovery actions to be taken in case of major NE
problem (NE substitution, NE loss of configuration memory…).
6. The NM is responsible for the NEs SW download and NEs MIB backup.
7. Finally, the NM is responsible for equipment provisioning, synchronization
configuration, external point configuration, and for all the functionalities which are
not available at NML level.
In few words, the NM is the management platform devoted to all the maintenance
activities of the transmission network, and it acts as a central agent between all the
network management systems and the NEs. Nevertheless, it maintains all the capabilities
to completely configure and manage the NEs in all their management domains.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration The backup of Q3 NE into 1350 OMS EML
....................................................................................................................................................................................................................................
The backup of Q3 NE into 1350 OMS EML

Q3 Backup
The 1350 OMS EML product does not maintain any updated copy of the NE
configuration. The NM directly works on the NE MIB to read and change the current NE
configuration.
Nevertheless, in the scope of providing recovery procedures, the NM provides facilities to
backup and restore the database (MIB) of each Q3 NE. The MIB align–up/align–down
procedures are all based on the same protocol (ISO 802.1e on top of CLNP) used for the
SW download.
The MIB file copied into NM is used only as a backup copy of the actual NE
configuration, and it is not, in any case, used during normal network management
activities. Therefore, the NE MIB image is not updated on–line when the actual NE is
being configured (independently on the originator of the configuration changes, either
NM operator, or SDH / SY systems).
The MIB backup includes all the NE information (i.e. N–SAP address, Ethernet, LAPD,
…) excepts the payload structure, cross–connection and PM data.
The MIB backup file size depends on the NE–type. Examples of file sizes are:
• 1640FOX around 140 KB.
• 1650SMC around 170 KB.
• 1660SM around 630 KB.
• 1664SM around 90 KB.
• 1666SR around 30 KB.
• 1641SX around 40 MB (for a big DXC configuration).
and the time required for backup is in the order of few minutes (5 to 10 for DXC).
It is likely worth noting that the backup of DXC is performed via SMF.
Note: Note that backup files for new equipments are compressed, then requiring less
memory space and less transmission time.
Now, the MIB of the NE backed up into NM is actually the exact copy of the memory
inside the NE. This copy is strictly dependent on NE type and release, and it's basically
readable by the NE only.
Since SDH contains in its internal database all the configuration of the NE as far as the
transmission fragments are concerned, it is mandatory for the MIB backed–up into the
NM to be always synchronized with the latest changes in the Equipment and
Synchronization configuration information.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
In other words, the NM operator shall perform an upload of the NE MIB every time either
CT or NM operators performed any change in the Equipment (board provisioning) or
Synchronization configuration. In this way, NM and SDH systems together contain a
global and consistent information of the actual NE configuration.
In order to trigger the Operator for such upload, an alarm is generated by the system
every time there is even the doubt that the Synchronization or Equipment configuration
changed with respect to the copy present in the NM system. The alarm (with MIB backup
misaligned probable cause and warning severity see Figure 10-2, “Misalignement
(warning alarm) between NE NM MIB and NE configuration” (p. 10-7)) will be cleared
by the system as soon as the MIB upload operation has been successfully performed on
the relevant NE using the Supervision Align Up option.
Figure 10-2 Misalignement (warning alarm) between NE NM MIB and NE

configuration
The MIB upload operation is manual, and not automatic, since the system cannot
automatically know when the sequence of configuration operations done by NM Operator
is finished, or if the configuration operation done by CT Operator is really to be adopted
by the centralized management platforms.
The utility of the backup copy is basically associated to the possibility to restore the
previous configuration data into a NE that failed. In this scope, it is mandatory for the
management systems to be able to re–create the latest configuration of the NE in order to
download it.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The backup and restore of the MIB database can be performed by CT as well, so that the
NE MIB will be transferred onto CT platform.
The MIB operation is completely decoupled from the existence and usage of NE
on–board simulator in NM. In fact, for example, DXC and WDM NEs do not support the
simulator on NM, while they do support the possibility to backup and restore their MIB.
The NE simulator, named also "on–board simulator", utilizes the same NM NE MIB (NE
MIB copy in the 1350 OMS EML system) and the different expression is often used to
distinguish the environment of NM NE MIB activation. So the "on–board simulator" is
activated in read/write configuration when the NE Supervision has been stopped: the
Supervision State is "Declared".
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-3 NE Statuses shown window
The MIB align–up.

The align–up option allows the operator to upload the copy of the MIB image from the
NE into the area of the NM simulator. The simulator will use this copy, which is supposed
to be the last updated one of the NE database. When the database is being align–down,
this MIB image will be downloaded into the NE. The last NE MIB image align–up
always overwrites the previously one, even if its contents have been changed using the
NE simulator.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-4 Simulator menu "Align Up" option
With the NE Supervision State "Supervision", open NE USM application and select the
Align Up option, confirm the align up and wait the end of the operation (see Figure 10-5,
“Information window during a MIB Align Up procedure” (p. 10-11)).
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-5 Information window during a MIB Align Up procedure
Note: The "Activate" option should be performed after an "Align Down" to NE

command to activate the NM NE MIB copy into the NE equipment
Important! After pushing the Activate button the related NE shall restart itself
therefore the NM operator has to wait a few minutes until the NE will became aligned
with the new MIB previously downloaded. During this transitory period no actions on
the NE are possible because the NE is in Q3 isolation.
The following picture depicts the NM MIB repository:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-6 NM MIB representation
NM
Q3 USM Q3 OBS
NM NE MIB
OPTICS –IM
ISO 802.1e
Q3 NE
DB
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration The on–board simulator of Q3 NE into 1350 OMS EML
....................................................................................................................................................................................................................................
The on–board simulator of Q3 NE into 1350 OMS EML

When to use
Use this task to simulate NE procedures.
On-board Simulator
An important change in NR5 is related to the introduction within the NM of NE on–board
simulators (OBS). The on–board simulator is used to simulate the presence of the actual
NE on the NM in order to read (and write) the MIB copy resident on the NM. The
on–board simulator is actually the same SW of the NE, just ported onto NM platform.
The on–board simulator is a tool that shall be used in the scope of precise procedures,
hereafter listed, and normally it is always switched off. The OBS is not provided for
testing or debugging purposes, but it is an integral part of NM product.
The reasons why the OBS is required on NM are the following:
1. In case of a DCN failure between the NM and the GNE, the NM operator has lost
access to the NE–MIB. He is not anymore able to know the NE configuration.
Normally there is no strong reason why the NM operator should be interested in
knowing the last known NE configuration, but if he/she does want to navigate through
the NE configuration, he/she can start up the simulator and read the backup copy of
that NE.
2. When an offline configuration operation is performed. The offline configuration
procedure is the possibility for SDH operator to act on the configuration of one Q3
NE even if it is not yet currently reachable (because not yet installed). This feature
can offer to the Network Administrator the possibility to pre–configure the network,
starting creating the network topology and even transmission configuration before the
network actually exists. Hence this feature applies only once in the network lifetime.
All the NEs pertaining to the network shall be declared and provisioned, even if not
yet installed in field. In this scope, the NM Operator can use the on–board simulator
to provision each new NE, one at a time. Through this simulator, the 1350 OMS SDH
system can get aware of ports existing in each NE, so that SDH can populate its
internal database. From this moment on, the on–board simulator shall be switched off
and SDH will work on its own database.
3. The replacement of an Equipment Controller (EC) is in fact the main reason for the
development of the OBS The replacement requires a procedure which synchronizes
on–site activities on the management system to avoid traffic perturbation. The
procedure is based on a re–synchronization between the data stored into 1350 OMS
SDH system and the NE MIB backup. In this scope, the simulator is mandatory to
allow SDH to write onto NE MIB backup in order to realize the realignment.
Therefore this is an emergency procedure applied when a NE is unreachable or to replace
the EC, per default, only one OBS can be opened at a time.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Hence, it is clear that the simulator shall be used only in very special and delicate network
phases, and that its usage shall be controlled by expert network operators.
The OBS is manageable by NM not by Craft Terminal
A more detailed description of the above procedures are provided in para. “Equipment
boards replacement procedures without affecting the service” (p. 10-16) and “Procedure
to perform an offline configuration” (p. 10-16).
Figure 10-7 SDH connected to NE simulator
RM
DB
OPTICS–IM
USM
NM
OPTICS –IM
Q3 EML –IM OPTICS –IM NE

NEs IDs Simulator
STARTED
DB
OPTICS–IM
Q3 NE
Once understood why and when the NE OBS shall be used, it is clear why the operator
can only start the NE simulator manually. No automatic mechanism to start–up the
simulator exists in NM. Moreover, the NE simulator can be started only if the associated
NE is not currently read (condition of Q3 isolation).
The NM operator shall start–up only one simulator at a time.
As it is manually started, the NE simulator shall be manually stopped. If the simulator of
a given NE is started, and maybe the NE becomes reachable again, the operator keeps on
working on the NE simulator until he manually stops it.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Once started, the NM operator is aware of the fact that he/she is currently working on the
simulator, and not on the actual NE, by the relevant state on the right side of the USM.
Moreover an OBS monitoring process is available to detect globally which simulator is
active, if any (see Figure 10-8, “On–board Simulator monitoring” (p. 10-15)).
The on–board simulator can be opened from TMN–OS view. On Board Simulator
Monitoring. Clicking on the monitor picture, the box window shows the NE equipment
name where the OBS is running. Note that this window is not automatically updated:
push the "Refresh" button to know the current on–board simulator status.
Figure 10-8 On–board Simulator monitoring
Assuming that the supervision of that NE was not previously stopped on a given NE, if
this latter becomes again reachable while the NM Operator is working on the simulator,
and hence on the local MIB, the operator is aware of this by the clearing of the "Q3
isolation" alarm, which is visible on both AS and USM. If, on the other hand, the
supervision was previously stopped for that NE, the operator can check about the
reachability of the NE by the OSI ping functionality.
Select the "Administration" icon —>System Management features —>Local Data
Management —>Ping NE to open the communication test tool window.
The OBS feature is not available at all for DXCs, because the DXC is already redundant
with two AUs.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Moreover, OBS is not available for WDM, since not yet managed at NML level.
Finally, it is worth adding a note on the releases of simulators and associated NEs. It
could occur that the release of a given NE simulator is different (lower) than the release
of the actual NE. This is possible, and due to the fact that the NE simulator needs to be
aligned with the actual NE as far as the configuration of the NE is concerned. All the
dynamic NE behaviors (e.g. event or alarm reporting, PM collection) are not relevant for
the NE OBS. Therefore, it can happen that during the testing phase, some NE behaviors
related to the dynamic mechanisms of the NE have been corrected, but they did not
require a new NE simulator version.
Equipment boards replacement procedures without affecting the service

The Equipment boards replacement have to be performed following specific procedures
written taking in account the NR and the board type. The operator can refer to the
network integration of existing documents.
Before you begin

Procedure to perform an offline configuration

Note: This feature applies only once in the network lifetime
The offline configuration procedure applies to SDH and NM operators to act on the
configuration of one Q3 NE even if the latter not yet currently reachable (because not yet
installed). This feature offers to the network administrator the possibility to pre–configure
the network, starting creating the network topology and even transmission configuration
even before the network actually exists (pre–deployment phase).
In order to start the offline configuration, the NM operator shall start–up the on–board
simulator as soon as SDH has to retrieve ports from that NE. NM operator shall configure
the NE in terms of equipment configuration (boards, etc.). Then the SDH can upload the
ports from the simulator according to the configuration entered by NM operator. Once
aware of the NE equipment configuration, SDH works locally configuring the NEs SDH
MIB in download disable mode. During the network configuration done by SDH, the
simulators on NM shall remain stopped. The network population offline procedure is:
...................................................................................................................................................................................................
1 Open the EML PNM window and create the NEs on the Map View in the "Declared"
Supervision State.
...................................................................................................................................................................................................
2 Select, on EML PNM, the NE and open the USM. Select the "Start" Simulator option
from the Supervision menu.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Configure the NE equipment and the NE synchronization sources.

...................................................................................................................................................................................................
4 On 1350 OMS SDH enable the NE EML MIB uploading to upload the NE Simulator
ports.
...................................................................................................................................................................................................
5 On 1350 OMS SDH disable the NE NM MIB uploading. The 1350 OMS SDH will work
with its internal NEs SDH MIB.
...................................................................................................................................................................................................
6 Stop the EML on–board simulator and restart from step Step 1 up to consider all the NEs
involved in the network configuration.
E...................................................................................................................................................................................................
N D O F S T E P S
Operations on Network Element

As soon as the actual NE will become reachable, two possible policies are implemented:
1. The NM operator shall download the NE NM MIB onto the actual NE, in order to
instruct it about equipment configuration, and then the consistency download from
SDH will be performed directly with the NE in order to download the SDH related
configuration information. Once downloaded the image stored in NM, the
configuration can be activated in the NE even if not complete (it does not include the
configuration performed by SDH). This operation affects traffic, if the network
already carries traffic. Normally it is not a problem since the NE is new and it does
not carry any traffic.
The procedure is:
a. On NM, open the PNM window and change the NE Supervision State in
"Supervision" for all the reachable NEs.
b. Open the USM window and select the "Align down" option from the Supervision
menu. Repeat the operation for all the NEs involved in the network configuration.
c. On 1350 OMS SDH enable the NEs SDH MIB downloading mode to manage the
NEs transmission network.
2. The simulator is activated on NM. SDH performs a consistency download, actually
working on the on–board simulator, and hence on the NE NM MIB. The NE NM MIB
is Aligned down onto the real NE, which will be then automatically aligned with both
NM and SDH. The SDH is working in disable downloading mode and the NM
simulator has been stopped.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The following procedure has to be applied to any NE taken over by NM–SDH
management system.
a. On NM open the PNM window and change the NE Supervision state in
"Supervision".
b. Open the NE USM window and select the Align Up option from the Supervision
>Simulator menu.
c. On NM open the PNM window and change the NE Supervision state in
"Declared".
d. Open the NE USM window and select the Start option from the Supervision
>Simulator menu to start up the on–board simulator.
e. On SDH enable the NE NM MIB uploading to upload the SDH and PDH ports.
f. On SDH in disable downloading mode, execute a mark audit and verify that the
list of misaligned objects does not concern the equipment and synchronization
configuration.
g. On NM open the PNM window and change the NE Supervision State in
"Supervision" to manage the NE configuration.
h. On SDH enable the NE downloading to manage the NE paths.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration SDH behavior towards the MIB–less architecture
....................................................................................................................................................................................................................................
SDH behavior towards the MIB–less architecture

Mib-less Architecture
1350 OMS SDH product reflects in its internal behavior the new NR5 MIBless
architecture of NM management platform. Actually, this is rather an internal issue and
does not impact the procedures for managing the network at Network Management Level.
The MIBless architecture of NM does not have any impact on the type and amount of
data managed by SDH. SDH is the manager of the transmission network, and contains in
its internal database all the information related to the transmission network only. SDH is
not aware of the Equipment configuration of a NE, and not even of the synchronization or
networking configuration of a given NE.
On the other hand, the pass–through role of NM implies that SDH system sends
commands directly to NEs, and their actual reachability becomes an important parameter
for SDH. In case of command to be sent to an unreachable NE, the SDH stores the
relevant commands internally, and automatically re–sends them as soon as the NE
becomes again reachable. But this has no impact on the operator's view of the
management. If the NE is not currently reachable, the path cannot be implemented
anyway.
Since SDH keeps on having its internal database mirroring the Network configuration,
there is the need to maintain the SDH database synchronized with the actual Network
Element MIB.
SDH is now responsible for guaranteeing that there is no misalignment about
configuration information. An efficient mechanism has been set–up in order to allow SDH
to immediately identify whether there could be misalignment with a given NE. In such a
case, the SDH operator is informed, and he/she can react by auditing the misalignment
and eventually forcing the SDH configuration information into the NE.
As for NR3, the SDH operator is able to specify whether he wants to really act on the
network element configuration (download enabled mode) or just work on the SDH
database (download disabled mode). If the download disable mode is entered by SDH
operator, the SDH operator can still work configuring its network, but configuration
commands are not sent to NEs for modification change, but just stored internally for later
appliance or for cross–check with actual NE configuration.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration SDH behavior towards the MIB–less architecture
....................................................................................................................................................................................................................................
The SDH system enters the download–disabled mode status as soon as either of the
following events occurs:
• A given NE is not reachable by SDH for any reason (DCN failure, NE failure, NM
restart, etc.). Once the NE is reachable again, the SDH automatically downloads
towards it the locally stored configuration changes.
• The NM operator has granted the access to the CT operator into a given NE. Once the
NE is reachable again, the SDH system informs the operator about possible
inconsistencies, but no automatic download is performed towards the involved NE. It
is up to the operator to act and decide whether to perform an audit or just to force the
realignment (download from SDH).
• The SDH operator has asked for download disable to a given NE. Once the operator
exits the download disable status, the SDH performs an automatic download towards
the NE.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Introduction
....................................................................................................................................................................................................................................
Introduction
Board Management
This document describes the procedures associated to the management of the ISA board
into OMSN NEs, in particular focusing on board creation and supervision operations
performed through EML–USM and PNM applications. This is a guideline document
oriented to NM Operators involved in management of ATM boards.
Basic EML operations, like Create/Remove NE and Start/Stop Supervision, are assumed
to be known, as well as NE–specific operations to be done with the EML–USM, like
Set/Remove Board and IP address configuration.
Since OMSNs are actually multi–service nodes and the provisioning of different
communication services is achieved via different management entities, from now on the
term "entities" will refer to both the OMSN NEs and the ATM boards.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration OMSNs and ISA board: PNM customization
....................................................................................................................................................................................................................................
OMSNs and ISA board: PNM customization

ISA board Management
ISA boards cannot be considered as all the other PDH/SDH boards normally equipped
into the NEs, since they run a SNMP agent interworking with the SNMP EML–IM at NM
level, that is supporting parallel management sessions with respect to Q3 connections
established between the Q3 EML–IM and the OMSN ECs.
Figure 10-9 OMSN and ISA board
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration OMSNs and ISA board: PNM customization
....................................................................................................................................................................................................................................
The peculiar nature of ISA boards and the generic requirement on PNM to support both
SDH and ATM alarm synthesis in the OMSN icon, has lead the design of a PNM
customization where all the managed ISA boards are represented by dedicated icons (in
the same way standard NEs are).
In the following, a procedure is described for the configuration of PNM enabling proper
ISA management inside network maps/submaps.
ISA management in PNM needs basically two preliminary operations, to be carried out
just once, before the first ISA board is to be equipped into a given OMSN described into a
given Map.
• the SDH equipment (one element).
• the ATM boards (n elements, as many as the ISA equipped).
As usual, the Operator shall select the NE of interest from the PNM Global Inventory (in
this context the ISA boards are listed into the Global Inventory as standard NEs). The
insertion of the SDH OMSN into the OMSN submap itself is mandatory, otherwise the
PNM will not perform a correct behavior.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration ISA Board Creation
....................................................................................................................................................................................................................................
ISA Board Creation

When to use
Use this task to create an ISA board.
Related information
Before you begin

How to create an ISA Board

...................................................................................................................................................................................................
1 Select on the Multi Service GUI Network Element list the NE which houses the ISA
board and follow the path Action from Network Element > Create ISA. See following
figure:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-10 Create ISA selection
...................................................................................................................................................................................................
2 The Create ISA dialog box is displayed. You can select the board type.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-11 Create ISA Window
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Enter the suitable selections and click on OK button to confirm. The ISA board is
displayed with an icon similar to NE icon. The User Label contains the name of the parent
NE and the ISA slot position.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Set ISA Board Address
....................................................................................................................................................................................................................................
Set ISA Board Address

When to use
Use this task to set the ISA board address.
Related information
Before you begin

Task
...................................................................................................................................................................................................
1 From MS-GUI Interface, select the ISA Board NE previously created and follow the
popup menu clicking the right mouse button Network Element > Set NE Address
...................................................................................................................................................................................................
2 Assuming that the IP–over–OSI tunnelling is already correctly configured in the OMSN
(it is out of scope of this procedure description), the Operator can set the IP Address of
the ISA board inserting the correct IP Address in the window.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-12 Set Addresses: IP Address
When a new board has to be provisioned into the OMSN, the first step is always
setting–in–service the board itself via the EML–USM. The same applies to ISA boards.
The Operator starts the OMSN EML–USM, selects the slot of interest and, from the
Equipment > Set menu chooses the ATM board type: "ATM4x4" in case of a 4x4 ATM
matrix, "ATM8x8" in case of a 8x8 ATM matrix.
In the reference case an ATM4x4 is provisioned.
Now the Operator shall perform a parallel description of the ISA as NE contained within
the OMSN domain (submap) into the PNM, as it is for all the managed NEs at EML level.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Reminding that the submap could in general contain the OMSN itself plus a number of
already described ISA boards, the Operator can create the new ISA instance from
MS-GUI application selecting the OMSN icon on the map and choosing the menu' option
Network Element > Create ISA Board, thus opening the ISA Board creation window.
The User Label of the ISA board is automatically generated as derived from the OMSN
User Label, once Rack/Subrack/Slot coordinates of ISA itself are inserted by the
Operator. Also ISA IP address shall be inserted (dotted format). No complete Friendly
names shall be chosen by the Operator, as per all other NEs. If no OMSN (namely
1640FOX, 1650SMC or 1660SM) is selected the menu is greyed out.
It is worth noting that the NM Operator shall insert consistent information about ISA
coordinates and IP address between OMSN EML–USM and PNM, otherwise the NM will
not be able to start the supervision on ISA and manage the ATM services.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration OMSN + ISA: Supervision
....................................................................................................................................................................................................................................
OMSN + ISA: Supervision

When to use
Use this task to start the supervision on the OMSN NE and corresponding ISA board.
Related information
Before you begin

Start Supervision
...................................................................................................................................................................................................
1 Select the ISA board icon from the map, select with the right mouse button Actions >
EML > Supervision > Start Supervision.
Figure 10-13 Start Supervision on OMSN.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration OMSN + ISA: Supervision
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Rename OMSN Network Element and all ISA boards
....................................................................................................................................................................................................................................
Rename OMSN Network Element and all ISA boards

When to use
As already highlighted, the ISA User Labels must be aligned to the parent OMSN User
Label. As a consequence, each time the OMSN friendly name changes, the user labels of
slave ISA Boards shall be modified accordingly.
Related Information
Before you begin

Stop the supervision on all the NE provided services (Q3 OMSN + all ISAs).
Task
...................................................................................................................................................................................................
1 From the MS-GUI main menu select the path Actions > Network Element > Rename
NE.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: The Rename NE window is displayed.
Figure 10-14 Rename OMSN NE
...................................................................................................................................................................................................
2 Modify the User Label and/or the Location Name.

....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The Rename NE wizard for OMSN Network Elements addresses just the OMSN–label
change only, not the change of ISA physical coordinates (e.g. slot change into the
subrack). If an ISA has to be moved from Slot X to Slot Y, the only available procedure is
first removing the ISA and then recreating it as a new board to be setup.
...................................................................................................................................................................................................
3 The user has the responsibility to update the OMSN label according to what already
defined when performed the Change Q3 Ne name procedure, since no double–checks are
implemented to detect errors.
It is worth noting that the new OMSN name shall be inserted just once, and the tool will
automatically upgrade the labels of all the equipped ISA inside the OMSN.
...................................................................................................................................................................................................
4 Confirm the modification with Apply or OK button.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Error Recovery
....................................................................................................................................................................................................................................
Error Recovery
Commands for EML Administrators
In case an NM User made an error during the ISA Board creation phase (wrong rack
and/or subrack and/or slot position), the NM administrators (axadmin profile) with
granted access to the Command Line will be able to perform a manual renaming of the
user label associated to the ISA board.
The command syntax will be provided in the 1350 OMS EML Administration Guide.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Introduction
Description
This technical description provides a high–level description for procedures to be followed
by Operators to deal with Transmission Alarms with 1350 OMS EML product, starting
from release 5.x, when supervising Q3 CMISE–based NEs.
The basic reason for these guidelines is that, for CMISE based NEs, transmission alarms
do not contribute to the alarm synthesis shown in the subrack view of the Network
Element. Therefore, starting from the subrack view of a given NE, a new procedure is
required to identify immediately where transmission alarms are.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Why Transmission alarms are not shown at subrack view?
....................................................................................................................................................................................................................................
Why Transmission alarms are not shown at subrack view?

Description
This section aims explaining the rationale behind the choice of preventing transmission
alarms to be part of Alarm Synthesis in the NE subrack view.
The new behavior, applying to 2nd generation NEs, based on CMISE management
interface, has been designed according to the principle that the 1350 OMS EML, as a
product devoted to the maintenance of the equipment in the network, is not basically
involved in the management of the Transmission services provided by the network, which
is a core task of other Network Management Platforms.
Therefore, the 1350 OMS EML product shall be designed and optimized in order to help
the Operators to identify immediately the roots of equipment alarms. This will improve
the network maintenance process by reducing reaction times, without being flooded by
alarms referred to the Transmission Services, which are the responsibility of other
personnel in the Customers' organization.
The subrack view of 2nd generation NEs provides a per–board Alarm Synthesis related to
equipment alarms only. Hence, the Operator can immediately identify which boards
currently have some maintenance–relevant alarms.
Nevertheless, the counters on the top–left part of the NE GUI, indicating the total number
of active alarms on the NE, do include the Transmission alarms, in order to provide a
global view of the NE alarm status. Moreover, the new splitting of alarms in alarm
domains and associated counters, on the top–right part of the GUI, allows the Operator
identifying specifically the number of transmission alarms currently active on the NE (see
Figure 10-15, “Alarm indication synthesis” (p. 10-39)).
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Why Transmission alarms are not shown at subrack view?
....................................................................................................................................................................................................................................
Figure 10-15 Alarm indication synthesis
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration How to identify transmission alarms starting from NE
Procedures to handle Transmission Alarms subrack view
....................................................................................................................................................................................................................................
How to identify transmission alarms starting from NE subrack

view
Description
As stated, the transmission alarms do not contribute to the alarm synthesis associated to
each board of the NE subrack view. Therefore, a procedure has been setup to allow the
Operator to identify where Transmission alarms are, with no need of an un–focused,
time–consuming navigation activity through all the Views of the GUI before detecting
which transmission object has been affected.
A new set of options is present in Figure 10-16, “Alarm Menu” (p. 10-40), under
Diagnosis/Alarms menu item.
Figure 10-16 Alarm Menu
The Transmission Alarms item allows the operator to open the Alarm Surveillance
application (AS), focusing only on the current transmission alarms of that NE, as shown
in Figure 10-17, “Alarm surveillance window” (p. 10-41).
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-17 Alarm surveillance window
The Operator can now select the current alarm of interest and, exploiting the
AS–EMLUSM navigation capability, moving back to the NE EMLUSM application, now
addressing the proper View with respect to the affected resource.
The AS menu of Figure 10-18, “AS navigation back to NE EML USM” (p. 10-42) allows
performing the required navigation:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-18 AS navigation back to NE EML USM
In this scope, the Operator does not have to navigate throughout the NE configuration,
starting from the subrack view, in order to identify the Transmission alarm: the right view
displaying the resource actually affected by the alarm of interest is immediately available,
so that remote diagnostic tasks from the NOC could be started with no delays. You can
look at the following figure and see that the Operator has selected a Loss–Of–Signal item
in the AS and the navigation back to the EML–USM has automatically popped–up the
Port View associated to the SPI experiencing the LOS.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-19 Relationship between AS and Port View of NE EML USM
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Transmission alarms sub–list in AS component.
....................................................................................................................................................................................................................................
Transmission alarms sub–list in AS component.

Description
In case the Operator wishes to pay even more attention to Transmission alarms, thus
orienting the 1350 OMS EML to be a management system pushed beyond the pure
equipment maintenance scope, it is possible to customize the system by creating an alarm
view devoted to transmission alarms only.
Starting from such view, the Operator can again select an alarm, and navigate onto the
GUI associated to that alarm, and again the GUI will be opened on the View where the
alarmed resource is shown.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Overview
Purpose
The user has to follow the procedure having care in avoiding any human error.
The ASAP (alarm severity assignment profile) is a descriptor which associates the proper
severity to the probable cause of each alarm.
This profile is then associated to the relevant resource.
For more detailed explanation please refer to 1350 OMS SDH User Guide, Section
Maintenance.
Contents
Introduction 10-46
Customizing a new ASAP on NM–OS 10-47
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Introduction
Scope
The scope of this procedure is to change the severity of some alarms. In particular, PDH
functional blocks concerned are:
• PPI, E* (E1 or E3), P* (P12 or P3).
while SDH functional blocks V * (V12 or V3) are not concerned:
Description and Warnings

The procedure must be executed first on 1350 OMS EML, then on 1350 OMS SDH.
Important! It is mandatory to assign the same ASAP identifiers to the whole network,
i.e. to each NE, to each EML to each SDH of the network.
Since the ASAP identifiers are automatically assigned by 1350 OMS EML, it is
important to execute the same identical ASAP creation procedure per each 1350 OMS
EML.
Description of the procedure

The procedure is constituted by the following main steps:
1. The 1350 OMS EML operator, per each NE, creates the new customized ASAP,
associating the severity to the Probable Cause for the involved alarm.
2. The 1350 OMS SDH operator associates to each type of PDH port involved, the
ASAP identifier previously created by the NM operator.
The detailed procedures are described in the paragraphs which follow.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Customizing a new ASAP on NM–OS
....................................................................................................................................................................................................................................
Customizing a new ASAP on NM–OS

Introduction
This section describes the procedures on NM to provide the ASAP customization required
from SDH.
The free–use ASAPs are always created cloning an already existing ASAP: hence, also in
free–use ASAPs all foreseen (for a certain NE) probableCauses will be always present.
Removing or adding probableCauses is not allowed.
The maximum number of free–use ASAPs supported in NM–OS is product dependent: the
free–use ASAPs are 2 for OMSN.
ASAP creation Procedure on NM

Select the supervised OMSN NE in the NE list on the Multiservice GUI, follow the path
Search > Network Element > Show Equipment to open the NE EML–USM window.
Then click on Configuration > Alarms Severities as shown in Figure 10-20,
“Configuring Alarm Severity Assignment Profile.” (p. 10-47)
Figure 10-20 Configuring Alarm Severity Assignment Profile.
The following window opens:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-21 ASAPs Management dialogue box.
Select an ASAP in the "List of ASAP" field to enable the "Clone" button. Obviously the
operator should select the ASAP which most matches the required customization, since
the customization procedure is manual in this NM release. click on the Clone button to
create the new free–use ASAPs identifier with the default number #10001 (as shown in
Figure 10-22, “ASAP Edition dialogue box example.” (p. 10-49)). It is important not to
change the ASAP "Id" since the same shall be used on SDH and therefore it is guarantee
of coherence among the network.
The user can mark the new ASAP, adding a character string after the identifier (#10001,
#10002) as shown in the following.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-22 ASAP Edition dialogue box example.
The operator can modify the severity associated with each probable cause. Hence, select
the Probable Cause Families: Communication, Equipment,... whose severity level you
want to modify. Then select the Probable Causes Name and click on the option button:
Service Affecting (SA), and then Non Service Affecting (NSA) and then Service
Independent (SI). For each one you can choose the severity value among "Critical",
"Major", "Minor", "Warning" or "Non Alarmed". A "Non Alarmed" probable cause
corresponds to no alarm emitted for this probable cause.
OMSN do not support the SI severity but the SI severity can be provided selecting, in SA
and NSA fields, the same severity value as indicated in Table 10-1, “Default Assignment
of Service Dependency and Severity on OMSN” (p. 10-50) and Table 10-2, “Possible
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
customization Assignment of Service Dependency and Severity on OMSN”
(p. 10-50) case 2 (SI). Usually the NSA default severity is lower than the SA severity (see
Table 10-1, “Default Assignment of Service Dependency and Severity on OMSN”
(p. 10-50)) but in general any possible severity customization assignment can be chosen
(see Table 10-2, “Possible customization Assignment of Service Dependency and
Severity on OMSN” (p. 10-50)).
Table 10-1 Default Assignment of Service Dependency and Severity on OMSN
Non Service Affecting Service Independent

Case Service Affecting (SA)
(NSA) (SI)
minor or warning or
1 major not used
non–alarmed
2 (SI) major, minor, warning major, minor, warning not used
Table 10-2 Possible customization Assignment of Service Dependency and

Severity on OMSN
Non Service Affecting Service Independent

Case Service Affecting (SA)
(NSA) (SI)
critical or major or minor critical or major or minor
1 or warning or or warning or not used
non–alarmed non–alarmed
critical, major, minor, critical, major, minor,
2 (SI) not used
warning warning
When you have configured the ASAP, press the OK button to confirm the settings and
close the dialogue box or the Cancel push button to cancel the new settings and close the
dialog box. If necessary, repeat the previous ASAP creation starting from the ASAP clone
of Figure 10-21, “ASAPs Management dialogue box.” (p. 10-48)The second new ASAP
identifier will begin with #10002... as shown in Figure 10-23, “Example of Management
dialogue box with two customized ASAPs” (p. 10-51)
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-23 Example of Management dialogue box with two customized ASAPs
When the procedure has been completed close the selected NE EML USM and start again
from the beginning selecting a new NE from the map view window. Therefore to assign
to PDH ports of SDH–OS the customized ASAPs the above same procedure has to be
applied to any NE involved in the path communication circuit.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration How to define OAD
....................................................................................................................................................................................................................................
How to define OAD

When to use
Use this task to create a new OAD.
Related information
Before you begin

Task
...................................................................................................................................................................................................
1 From Web Portal application, follow the path Administration > Security Administration.
Select the icon User Profiles(EML <Instance Number>-<Release>). The ACI/OAD
Management Tools window is displayed.
...................................................................................................................................................................................................
2 From the System Management window follow the path Tools > Show > objects.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: The Create Object window is displayed.
...................................................................................................................................................................................................
3 Create an object called for example RegionE with Criterion Family : ACD and SystemId
: RegionE. To create a criterion, select the Criterion Name in the list and the value in the
Criterion Value list, then click on the > to add the criterion to the list. To confirm the
object creation, select the Apply button.
...................................................................................................................................................................................................
4 From the System Management window follow the path Tools > Show > OADs..
...................................................................................................................................................................................................
5 Select OAD: Object and click on Create Object button. (see below figure).
...................................................................................................................................................................................................
6 Enter name (e.g. RegionE), family (e.g. Access Control Domain), System Id (string or
FDN) and click on Apply button. The new OAD is now displayed in the list.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-24 OAD: Object: Create
...................................................................................................................................................................................................
7 Create the profile for managing new created OAD RegionE. Follow the path Tools >
Show > Operator Profiles.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
8 Create the association OAD-FAD for the operator profile. Select the profile in the list,
select the tab panel Create Association to create the OAD-FAD association for the
operator profile.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-25 Elementary OAD: Create
...................................................................................................................................................................................................
9 Use the Add button to add the FAD to be associated to the OAD. Click on Apply button to
confirm.
...................................................................................................................................................................................................
10 Open the User Accounts application following the path Administration > Security
Administration > User Accounts.
Result: The User Accounts application opens.
...................................................................................................................................................................................................
11 Create the new user RegionE selecting Create New User from the popup menu.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
12 Create the user RegionE, define Login, Attributes and Profiles.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
13 In the EML User Profiles application, select the path Tool > Show > Opearators, select
the path Declare Operator, to declare the sec user previously created.
...................................................................................................................................................................................................
14 In the EML User Profiles application, select the path Tool > Show > Opearators, the Edit
window is displayed. Add the RegionE Sec User created. Select in the profile list the
RegionE profile and add it with the > button.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
15 Add RegionE profile to RegionE user.

...................................................................................................................................................................................................
16 Add RegionD and RegionE profile previously defined to Alcatel operator.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
17 An operator with profile=alcatel will be able to select ACD=RegionD, RegionE ,unknown

to include or not the management of the new NE.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-26 Create NE
RegionE operator is able to search and create Ne with ACD RegionE and unknown
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-27 Create NE
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Introduction
File Transfer Scheduler Application
The FT Scheduler allows to execute software downloading operations on multiple NEs,
defining the sequence to be followed and the activation time as SWDL ( Software
Downloading Scheduler).
The FT Scheduler is an application useful to launch multiple file transfer (SW Download,
MIB backup) between the OS and the NEs providing scheduling & periodic services. In
addition, to avoid critical network load, the FTS allows to plan the DCN loading during
the file transfer.
The FT Scheduler is an application designed for SNMP and Q3 NE protocol interfaces
that allows to execute the SNMP MIB back up and the Q3 MIB align up.
To open the FT Scheduler, from the MS-GUI application window, select Search > File
Transfer Scheduler option to display the job and SW status lists; select Action > File
Transfer Scheduler to open the create job window.
Figure 10-28 FT Scheduler option
The USM process can be installed on any OS types (Master or Presentation). Only one FT
Scheduler USM can run at the same time on the same OS workstation: if the user tries to
open a new FT Scheduler USM, a warning box will advice that the application is already
running.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
FTS Application
The FTS application can be applied to all NEs independently from the technologies
and/or the protocol type: the application automatically excludes those NEs that do not
support SWDL protocol or MIB Backup/ Align Up.
The application masks operational differences so operativity and results are uniformed for
different NE protocol type (Q3 or SNMP). Then the same FTS windows and procedures
will be applicable for different NE types.
Dynamic Bandwidth Optimization is adopted for data transfer between FTS application
and NEs. This method implements the possibility to modify the bandwidth according to
the reliability of the transmission channel, in order to reach the best transfer data speed
allowed.
Impacted functionality are SW download and MIB restore managed according to the
protocol ISO 802.1e CLNP and over TCP/IP.
Functionality
The main features offered by the FT Scheduler are:
• scheduling of SWDL jobs.
• scheduling of MIB backup jobs.
• scheduling of MIB restore jobs
• periodic scheduling of MIB backup Jobs.
• Job (SWDL or MIB backup) progress monitoring.
• NE SW status retrieving in single or multiple form.
• NE SW management.
• NE SW status data export.
• operation and result logging.
SWDL and MIB backup functionality are offered working simultaneously on a set of
NEs.
Operational scenario
The managed file transfers are:
• SW Download (scheduling services).
• MIB backup (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 the 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 programmed. In addition, MIB Backup Jobs
may be periodically re–activated every 24 hours.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The SW management function allows managing SW versions loaded on the NE. The
allowed SW Management commands set depends from the NE SW status and from the
functionality supported by the target NE. SW management is allowed on a single NE at a
time and it's not scheduled, i.e. commands are immediately sent to the target NE.
The FTS application allows to retrieve the list of the SW version loaded on all the NEs,
with the associated status. The NEs SW version may be retrieved on single NE or on a set
of NEs. Some filters are available to select subset of NEs. When the SW status is
retrieved on a set of NEs is possible to save the result in an exportable file (ASCII
format), useful for external analysis.
Note: MIB backup operation may be implemented differently for different NE types:
may be MIB align up or MIB backup. This document and the FTS, use the operation
name "MIB backup".
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Job Planning
....................................................................................................................................................................................................................................
Job Planning
Function
The FTS Scheduling function is based on the information contained into the "Job"
descriptor file. The "Job" is composed by different sessions, each one containing a set of
NEs.
The same job allows having a priority level approach in the FTS operation. All the NEs
belonging to a session are Down–loaded / Backed–up before the NEs of the next session:
the job will start from the first NE of the first session and will go on, respecting the order
of sessions and in each session the order of NEs. This permits to control the DCN traffic
in the network, then the global FT phase can be organized in order to avoid overloading
some specific GNEs or DCN links.
In order to have a good balanced DCN traffic load each LAN node divides the network
into two links, each of one will support, in both sides, quite the same NE number. The
FTS application emphasizes the possibility to maintain a reduced DCN load dividing the
file transfer load time by sessions (See chapter “DCN network example” (p. 10-86)).
The application launches, for each session, the maximum number of simultaneous file
transfer allowed (<=10 for each involved NM LAN: then the maximum simultaneous file
transfer, inside a session, is 10 multiply by the number of involved LAN). When one
session terminates, the application launches the next defined session.
The maximum NE number for any session is 90 but there is no limit regarding the
maximum session number in a job.
The DCN traffic load affects the NEs and the network branches involved in the OS–NE
communication Considering any NE load equivalent to "1", charging any DCN branch
with a balanced load, it can be suggested the following job planning rule:
• Distribute the DCN traffic dividing the global traffic load of each branch through
different sessions trying to reduce the session numbers: in each session the same
network branch will be passed through by the traffic the minimum number of times.
In a real DCN network, each session will contain NEs belonging to different LANs and
the optimum traffic load for branches will take in account the network communication
capacity and the file transfer traffic between NM and tens / hundred of NEs.
We can reduce the session numbers increasing the LAN load value but the traffic load for
branches will be increased too.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration FT Scheduler Job Descriptor
....................................................................................................................................................................................................................................
FT Scheduler Job Descriptor

The Descriptor
The FT scheduling function is based on the information contained into the Job descriptor
file.
The Job menu allows to create job descriptor files, to open the existing descriptor files, to
show the running job status and the job report.
The job editor allows to generate 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 Down–loaded / Backed–up before the NEs of the next session: the job will
start from the first NE of the first session and will go on, respecting the order of sessions
and in each session the order of NEs. This permits to control the DCN traffic in the
network, then the global FT phase can be organized in order to not overload 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.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Create an FTS Job
....................................................................................................................................................................................................................................
Create an FTS Job

When to use
Use this task to create a File Transfer Scheduler job. This is the first action to be done for
managing software download and backup operations.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 Select the on the MS-GUI main menu Actions > File Transfer Scheduler > Create Job
to open the Create Job window.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: The Create Job window is displayed.
...................................................................................................................................................................................................
2 Insert the Job Name, this field is mandatory.

...................................................................................................................................................................................................
3 Select the Job Type : MIB Backup, Software Download or MIB Restore. Also this field is
mandatory.
Backup : the NE data are stored on the server to be kept as backup data.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Download : the software is downloaded on one or more NEs.
...................................................................................................................................................................................................
4 Select the Activation Time : Immediate or Deferred, a time chosen from a calendar. Also
this field is mandatory.
...................................................................................................................................................................................................
5 Insert the Duration: maximum duration time for the job, if this field contains a value,
after that time the job is stopped if not yet finished.
...................................................................................................................................................................................................
6 Confirm the creation with OK or Apply button. Apply button save the job and keeps the
window open, OK button saves the job and closes the window.
Result: The created job appears in the Create Job list on the MS-GUI window.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration File Transfer Scheduler Job Editor
....................................................................................................................................................................................................................................
File Transfer Scheduler Job Editor

Software Download (SWDL) Session
To create SWDL Sessions select in the Create Job list the job to edit, select from the
popup menu the path Actions > Create Download Session, the Create Software
Download session window is opened.
To create a Session:
• Select a NE from the list, click on the icon to open the popup list.
• Select the FT Server from the list.
• Define a package filter, this is used to filter the package that can be downloaded on
the NE.
• Select the package to be downloaded.
• Select if the download is forced, in this case select Forced download in the list of
parameters.
• If required you can add another SWDL to the session.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Click on OK or on Apply to add the SWDL Session (Software Download) to the job.
To list the SWDL sessions belonging to a job, select the path Search > JOB > Show
SWDL Session.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
In the SWDL window, the NE Label can be filtered choosing the Supervision area and
the NE Type. If many NEs are managed the filters visualize a restricted NE set in the NE
Label field making easier the required selection.
The selected NE label will be also shown at the left window side as name of the tree
branch: the NE detail will be reported in the related NE detail field accordingly.
Depending on the selected server and on the NE type, the list of available software
package will be shown. Then select the package version in the list to complete the NE
SWDL package configuration. If the operator wants to select a SWDL package belonging
to another NE Type, he can enter the NE type into the "Package Filter" and then, clicking
on the "Apply Package Filter" button, choose the NE package.
The "Apply Package Filter" command can be also used to perform two other operations:
• If a ISA board is equipped into a OMSN, the OMSN software package can be selected
by "Apply Package Filter" option to show an enhanced OMSN software package: for
example to change the Software package "650SMC" with the "650SMCE" enter it in
the Package Filter and click on the "Apply Package Filter" button.
• The same "Apply Package Filter" option associated to the "CTRL" button can be used
to force the software package list updating in the FT Scheduler editor after a new
software package installation.
Repeat the same "Add NE" or Add Session" items to complete the job procedure. At the
end the user can select "Submit" to start the SWDL job, "Save" to save the job into a file
name or close, selecting the "Exit" option to close Job Scheduler Editor menu. Note that
before submitting a job, all branches have to be correctly updated, the red check sign
indication will appear on every completed item.
The same concepts can be applied to a Backup job but the backup job window is slightly
different to the SWDL one. The main differences are the periodic job and the
misalignment flag options.
A periodic backup job is automatically re–scheduled every 24 hours selecting "At Time"
and the "Periodic Job" options.
If the "Misalignment Flag" is selected the Backup operation on the target NE will be
executed only if the MIB NE–NM misalignment is detected. This option is available only
for those NEs supporting it.
1350 OMS EML does not manage Backup Misalignment alarm/Flag for 4G NEs.
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration FTS Job Status
....................................................................................................................................................................................................................................
FTS Job Status

Staus
To see the SWDL or Backup job status select the job in the job list and the path Search >
Job.
The job status is displayed in the job list:
• Green colour indicates that the SWDL procedure has been successfully executed.
• Red colour indicates a failed procedure.
• Grey colour indicates that the procedure has not been started.
• Orange colour indicates the procedure is still running.
On the right window side are reported the selected NE SWDL / Backup details.
Select the "Abort" button to interrupt the SWDL in progress job or the "Close" button to
close the monitoring window. From the SWDL / Backup monitoring window the user can
open the "View Report" window selecting from the "Job" menu, the relative command
Note that in Backup job window the "Abort" button is not active selecting the single NE
branches.
In the status of job / session / SWDL–NE or Backup–NE, the following coloured icons
can be found:
• Grey : Waiting start
• Orange : Activated
• Green : finished operation with No Error
• Red : finished operation with Errors
• Red with a crossed sign : Aborted operation
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration FTS Job Status
....................................................................................................................................................................................................................................
Figure 10-29 Job status and "View Report" command
The "View report" is described in para. “View Report” (p. 10-76).
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration View Report
....................................................................................................................................................................................................................................
View Report
Description
Two View Report options are available: the "View SWDL Report" and the "View Backup
Report". These view report files can be opened with the relevant options from the "job"
menu or with the "View Report" commands from the SWDL / Backup "job" menu.
The View report starts with the beginning data and time of the "FT Scheduler Job" and the
Job name indication.
Then, for each NE lists, the beginning data and time of the "SW Download / Backup", NE
name, software name, software version, software type, Server address (alias named EML
Area Domain) and the forced/not forced SWDL type attribute. It follows, for each NE, the
end data and time of the "SW Download / Backup", NE name, SWDL / Backup result
and, eventually, the Error indication.
The report terminates with the end data and time of the "SW Download / Backup
Scheduler Job" and the summary indication of the SWDL successfully executed and the
SWDL failed.
The Backup view report is shown in Figure 10-30, “Backup report window example”
(p. 10-76)
Figure 10-30 Backup report window example
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration View Report
....................................................................................................................................................................................................................................
The SWDL / Backup View report can be configured in two different ways:
• Adding info in the report file at each job start time: all the SWDL / Backup info will
be stored in the report file appending them to the existing.
• Writing a new report file at each job start time: the report file is created new and only
the last SWDL / Backup info will be stored.
To configure the SWDL / Backup View report, access to the directory:
/alcatel/Kernel/SystemInstances/EML_<Inst_number>/swdl/swdlsched/conf,
select the file param.cfg and modify the following parameters:
• BCKP_LOG_FILE_REWRITE.
• SWDS_LOG_FILE_REWRITE.
in following way:
• False = if the job report file must be created new only if it doesn't exist, at job start
time, otherwise it will be appended.
• True = if the job report file must be created new at each job start time, it will be
rewritten each time that a job starts.
The default values are:
• SWDS_LOG_FILE_REWRITE= "True";.
• BCKP_LOG_FILE_REWRITE= "False".
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration Software Status
....................................................................................................................................................................................................................................
Software Status
Description
The Software Status menu allows visualizing the NE software status on different
modalities: for all NEs, for NE name and for NE type. The info is retrieved from NEs
themselves.
To get the SW Status of all NEs, select on the MS-GUI main menu Search > File
Transfer Scheduler > View SW Status.
Figure 10-31 SW Status menu
This option lists the SW Status of all the reachable NEs created on the EML system,
independently of the NE Supervision state, excluding the NEs not managed by the tool as
mentioned in the previously paragraph (see Figure 10-32, “NEs SWDL Status”
(p. 10-79)).
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-32 NEs SWDL Status
Clicking on the column names (grey) it is possible to sort rows. The up/down arrow
visualizes the increasing/decreasing sorting chosen (by name, by version,...).
A similar SW status window can be opened selecting the NE by Type. Depending on the
NE number, defined on the NM system, it is possible to have two different "Select By
Name" menus. The first one, shown in Figure 10-33, “SW Status selected by name with a
NE list menu” (p. 10-80), represents a menu with a NE list while the second one a menu
with the "Select one from list" indication, used to help selection on large number of NEs.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-33 SW Status selected by name with a NE list menu
Selecting the Get SW Detail by Name option, a window is displayed to select the NE
name.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Select the icon on the right of the NE label field to display the NE label list. Select the NE
label to display the NE Software status table.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-34 NE software status detail
Selecting a Q3–NE element the "Software Unit Status" button will be enabled while the
"View Descriptor File" button will be disable (greyed). Clicking on the "Software Unit
Status" button Figure 10-35, “Q3–NE Software unit detail example” (p. 10-83)opens.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-35 Q3–NE Software unit detail example
Note: It should be noted that in the Software Unit detail window the ATM SW
package types can be visualized, as shown in the example of Figure 10-35, “Q3–NE
Software unit detail example” (p. 10-83).
Some "Software Management Action" can be accessed via the NE Software Status Detail
Dialog box. The available actions depend on the NE type and loaded SW Package status.
A pull up menu shows the available actions (see Figure 10-36, “Software management
action example” (p. 10-84)). The possible actions are:
• None: no action.
• Activate: serves to activate the selected software package.
• Force: force reactivating of active SW package.
• Commit: the selected SW package (the active one) will be activated at NE restart.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
• Delete: the selected package will be deleted on the NE.
• Duplicate: the selected package will be duplicated on the NE.
Figure 10-36 Software management action example
To activate the required action select the network Element from the Get Software Details
list and follow the path Actions > Activate the Software from the popup menu, click on
the desired action to be executed.
To get the Software Status by NE Type select the path Search > File Transfer Scheduler
> Get SW Status by Type, the NE Type selection window is displayed. .
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-37 SW Status Selected by NE Type with a NE list menu
....................................................................................................................................................................................................................................
March 2010
Procedures for EML Configuration DCN network example
....................................................................................................................................................................................................................................
DCN network example

Description
The DCN examples, here below reported, concern elementary networks with a single
LAN and a few NEs.
Figure 10-38 DCN network example
The procedures show how to divide the total DCN traffic without exceeding the suggested
optimum traffic load for branches.
Higher is the LAN load, lower will be the session numbers and vice–versa.
Let us assume, in the examples that follow, the optimum DCN traffic load for branch <=1.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-39 Balancing the DCN traffic load
In the example of Figure 10-39, “Balancing the DCN traffic load” (p. 10-87) the link
connection between NM and each NE types have been represented: the traffic in the
branch NM–NE1 has been balanced with the traffic in the branch NM–NE4 but these
branches, in each session, are passed through by the traffic two times and the suggested
planning rule has been disappointed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-40 Optimizing the load traffic for session
In the example of Figure 10-40, “Optimizing the load traffic for session” (p. 10-88),
following the suggested planning rule, a LAN load <=4 has been considered and the job
has been divided in the following sessions:
• First session: GNE1, GNE2, GNE3 and GNE4.
• Second session: NE1, NE2, NE4 and NE6.
• Third session: GNE5, NE3, NE5 and NE7.
• Fourth session: GNE6.
The link load will be:
Table 10-3 Link load of level 1 with LAN load max=4
Branch Session 1 Session 2 Session 3 Session 4

link load link load link load link load
Lan load = 4 4 4 1
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................

Router
1 1 1 1
1–GNE1=
Router
1 1 1 0
1–GNE2=
Router
1 1 1 0
1–GNE3=
Router
1 1 1 0
1–GNE4=
The traffic load, in any branch of each session, is <=1 (Table 10-4, “Link load of level 2
with LAN load max=4” (p. 10-89)) as suggested in the planning rule.

GNE1–NE1 = 0 1 0 0
GNE2–NE2 = 0 1 0 0
GNE3–NE4= 0 1 0 0
GNE4–NE6= 0 1 0 0
GNE1–GNE5= 0 0 1 1
GNE2–NE3= 0 0 1 0
GNE3–NE5= 0 0 1 0
GNE4–NE7= 0 0 1 0

GNE5–GNE6 = 0 0 0 1
As before the traffic load, reported on Table 10-5, “Link load of level 3 with LAN load
max=4” (p. 10-89)and Table 10-6, “Link load of level 4 with LAN load max=4”
(p. 10-89), in any branch of each session, is <=1
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The traffic load has been represented dividing the DCN network with different network
levels. In Figure 10-40, “Optimizing the load traffic for session” (p. 10-88)the DCN has
been divided into 4 levels and the load, in any branch of each session, is minimum (<=1).
With a higher LAN load it is possible to reduce the session numbers but we can not
minimize the traffic load in any branch of each session.
Figure 10-41 Example of DCN traffic increasing the LAN load
Consider the same DCN network of Figure 10-38, “DCN network example”
(p. 10-86) but with a LAN load <=7: the job could be divided in the following sessions:
• First session: GNE1, GNE2, GNE3, GNE4, GNE5 and GNE6.
• Second session: NE1, NE2, NE3, NE4, NE5, NE6 and NE7.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The distribution traffic load, at different network levels, has been visualized in Figure
10-41, “Example of DCN traffic increasing the LAN load” (p. 10-90)
Branch Session 1 Session 2

Lan load 6 7

Router 1–GNE1= 3 1
The traffic load, in many branches is >1 (Router1–GNE1 of Session1 is =3). That could
cause an overloading of the DCN traffic.

GNE1–NE1= 0 1
GNE2–NE2= 0 1
GNE3–NE4= 0 1
GNE4–NE6= 0 1
GNE1–GNE5= 2 0
GNE2–NE3= 0 1
GNE3–NE5= 0 1
GNE4–NE7 0 1
As before the traffic load, reported on Table 10-9, “Link load of level 3 with LAN load
max=7” (p. 10-91) in branch GNE1–GNE5 of Session1, is >1.

GNE5–GNE6 1 0
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Therefore this second job planning does not optimize the network traffic load.
Job Editor
The job planning is built through the job editor Figure 10-42, “Job editor example”
(p. 10-92): the generic NEs have been substituted by the real ones.
Figure 10-42 Job editor example
Job Scheduling
A defined job may be executed at the submitted time (option Now) or at programmed time
(option At Time), in addition, only for MIB backup, can be also chosen "At Time" with a
"Periodic Job" parameter that allows an automatic MIB backup job activation every 24
hours.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Moreover in the MIB backup Scheduler editor, the user can select, for each NE, the
"Misalignment flag". This flag allows to load (or re–load) the MIB backup file only when
the MIB misalignment alarm has been recognized, avoiding unnecessary MIB backup
operation.
Job Monitoring
During the job running the job status can be checked by the job in progress window.
The colours icons identify the job status:
• grey : "Waiting start"
• orange : "Activated"
• green : "Finished operation with Success"
• red : "Finished operation with Errors"
• red with a crossed sign: "Aborted operation"
Job Report
Moreover the FTS application allows programming a SWDL / Back–up job not obliging
the NM operator to be present (and awake) during the operation (overnight). A log report
is provided to verify how the job operation worked out (see Figure 10-43, “SWDL job
report example” (p. 10-93)).
Figure 10-43 SWDL job report example
NE SW Status Visualization
The FTS allows checking the SW releases currently loaded on the NEs, the running one
(active) and the ones stored in the spare bank of the memory. This operation is possible on
a single NE (menu option: Selected by name), or on a predefined set of NEs of a given
type (menu option: Select by NE Type), or globally on all the managed NEs (menu
option: All NEs).
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 10-44 NEs software status table example
The information is retrieved directly from the NEs so that it reflects the current status of
the network. The NE SW Status table, used to show SW Status for a set of NEs, allows to
export values in a file for the external analysis.
NE SW Management
A new software package downloaded is stored in the NE stand–by bank: the activation
can be performed in a second time. The same Figure 10-45, “Action on NE software
package memory banks” (p. 10-94)can be opened with a double click on the selected NE
of the software status list or selecting the "Select By Name" option from SW Status pull
down menu.
Figure 10-45 Action on NE software package memory banks
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
NE SW Detail window shows the status of the data loaded in each memory bank of the
NE and the allowed SW Management operation (actions).
The SW Management actions that can be performed on the NE are:
• None: no action.
• Activate: to activate the selected software package on the NE.
• Force: to force the selected software package activation on the NE.
• Commit: to commit the software package activated on the NE.
• Delete: to delete the selected software package on the NE.
• Duplicate: to duplicate the selected software package on the NE .
The SW Management Action list shows the allowed operation depending from the NE
SW Status.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
11 11
Supervision System
Configuration
Overview
Purpose
The Supervision Areas is instantiated and configured in the System Configuration GUI; a
Supervision Area is not necessarily linked to an OSI Stack.
The new configuration scheme managing:
• Pure IP networks without OSI traffic.
• IP over OSI tunneling.
Three types of Supervision Area are possible:
OSI
• Linked to a lan card (physical device).
• Used by an OSI Stack (that is, referred to by a Necom Subsystem instance).
IP
• Linked to a LAN card (physical device).
• Not used by any OSI Stack.
Virtual
• Linked to a virtual device.
• Not directly linked to any OSI Stack but sharing the same OSI Supervision Area LAN
card.
• Used for IP over OSI tunneling.
It is possible to manage:
1. OSI traffic as usual.
...................................................................................................................................................................................................................................
March 2010
Supervision System Configuration Overview
....................................................................................................................................................................................................................................
In this case configuring:
• An OSI Supervision Area X on a lan card.
• An OSI Stack (Necom Subsystem) linked to X.
• Any EML–IM referring to X.
2. IP traffic tunneled on an OSI network (IPoverOSI).
• An OSI Supervision Area X on a lan card N.
• An OSI Stack (Necom Subsystem) linked to X.
• A virtual Supervision Area V on the same lan card N.
• An OSI tunneling process referring to V.
• SNMP EML–IMs referring to V.
3. IP traffic on IP networks.
• An IP Supervision Area X on a lan card.
• SNMP EML–IMs referring to X.
Contents
Supervision Area 11-3

Supervision Area Definition 11-3
Supervision Area Configuration 11-7
Different Types of Configuration 11-7
Configuration Example 11-11
....................................................................................................................................................................................................................................
March 2010
Supervision System Configuration Supervision Area Definition
Supervision Area
....................................................................................................................................................................................................................................
Supervision Area
Supervision Area Definition

Introduction
• Define an OSI (real) supervision area for OSI traffic.
• Define a virtual supervision area for IP over OSI tunnel.
• Check parameters of an already configured supervision area.
• De–configure an existing supervision area.
• See which supervision area is associated to each component.
Definition of Real Supervision Area

The Supervision Area can be instantiated from the left side of the System Configuration
GUI.
....................................................................................................................................................................................................................................
March 2010
Supervision Area
....................................................................................................................................................................................................................................
Figure 11-1 Supervision Area Selection in System Configuration
Selecting a Supervision Area instance on the right side, another GUI is displayed. This
GUI to define:
• The related LAN card.
• The Supervision Area logical name.
....................................................................................................................................................................................................................................
March 2010
Supervision Area
....................................................................................................................................................................................................................................
Figure 11-2 Configuration of Supervision Area Parameters
In older NM versions, operations described in precedence were done in the NECOM

Subsystem configuration window.
Remark: on selection of a Supervision Area instance in the System Configuration GUI,
the operator is required to confirm its removal before applying it.
Figure 11-3 Confirmation Dialog before Supervision Area is deconfigured
If removal is confirmed, the operator is obliged to modify all instances currently linked to
the Supervision Area just removed.
....................................................................................................................................................................................................................................
March 2010
Supervision Area
....................................................................................................................................................................................................................................
Definition of virtual Supervision Area for IP over OSI Tunnels
A second Supervision Area must be associated to a LAN where another OSI (real)
Supervision Area is already configured. The "StackInterface.txt" file is updated with new
Supervision Area.
The 'IP over OSI tunnel' configuration window can be opened only if two supervision
Areas (one real and one virtual) exist and the NECOM component is correctly configured
on the real SA.
How to see parameters already configured for Supervision Area

NM operator sees the parameters already configured for Supervision Area by opening
'Configure Supervision Area' dialog with right mouse button.
How to safely close 'Configure Supervision Area' dialog box

When opening 'Configure Supervision Area' dialog box for display only, it is necessary to
close the dialog with 'Close' button. In this case, some warning dialogs appear, which
have no side effects, provided that operator does not choose to de–configure the
supervision area.
Note: If the 'Configure Supervision Area' is closed with 'Apply and exit' button, then
the associated NECOM is de–configured.
There is a restriction on dialog management: check commands fail even if processes are
down and some warning dialogs appear when operator refuses to de–configure the
supervision area.
How to De–Configure an existing Supervision Area

Supervision Area is de–configured with the standard procedure but this operation triggers
de–configuration of all existing NECOM instances.
No message is currently displayed to warn the operator that all NECOM instances will be
de–configured if the supervision area is de–configured.
How to see Supervision Area associated to EML–IM and other components

Operator chooses 'Configure <component>' menu (with right mouse button) and then exit
from dialog with 'Apply and exit' menu.
....................................................................................................................................................................................................................................
March 2010
Supervision System Configuration Overview
....................................................................................................................................................................................................................................
Different Types of Configuration

OSI Stack (RETIX) Configuration
The OSI Stack (NECOM Subsystem) configuration does not change with respect to
previous NM versions: all Supervision Areas are listed for selection.
Figure 11-4 Supervision Area selection in OSI Stack configuration
Association of two NECOM components to the same SA

Note: It is impossible to associate more than one NECOM to the same supervision
area but there is no error message that informs the operator that the new Supervision
Area is not correctly configured.
The StackInterface.txt is updated with new Supervision Area.
NM operator is responsible of making sure that one and no more than one NECOM is
associated to each OSI Supervision Area.
How to see parameters already configured for NECOM

NM operator sees the parameters already configured for NECOM by opening 'Configure
NECOM' dialog with right mouse button.
....................................................................................................................................................................................................................................
March 2010
Supervision System Configuration Different Types of Configuration
....................................................................................................................................................................................................................................
OSI Tunnel Configuration
Operator must choose the desired virtual Supervision Area and then configure the
remaining parameters. OSI Supervision Area are not listed for selection.
Figure 11-5 OSI Tunnel Configuration
Q3 EML–IM Configuration
Only OSI Supervision Areas are listed for selection when operator needs to configure a
new instance of Q3 EML–IM.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 11-6 Supervision Area selection during Q3 EML–IM configuration
SNMP EML–IM Configuration

All Supervision Areas are listed for selection, because the final choice depends on the
network architecture.
Figure 11-7 Supervision Area selection during SNMP EML–IM configuration
4G EML–IM Configuration
Configuration of supervision area for 4G EML–IM is performed in two different steps.
As a first step the operator needs to select the OSI Supervision Area for Q3 traffic on OSI
Stack.
In this case, only OSI Supervision Areas are listed for selection.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 11-8 Supervision Area selection during 4G EML–IM configuration
After this selection has been done, it is necessary to associate the supervision area for the
SNMP protocol adapter, which should use either an OSI or a Virtual Supervision Area
depending on the network architecture.
Two cases are possible:
• If no virtual Supervision Areas exist, the whole 4G process group (coordinator, Q3
adapter, SNMP adapter) is automatically linked to the selected OSI Supervision Area.
In this case, operator needs not to select any other supervision area.
• If at least one virtual Supervision Area exists, a second window is displayed, which
lists both the selected OSI Supervision Area and all the available virtual supervision
area. NM operator needs to choose one of the displayed supervision areas.
Figure 11-9 Supervision Area selection for coordinator
The selected Supervision Area applies also to the coordinator.
....................................................................................................................................................................................................................................
March 2010
Supervision System Configuration Configuration Example
....................................................................................................................................................................................................................................
Configuration Example
Configuration Steps Example
An example of configuration steps follows:
OSI Supervision Area & Stack configuration:
• Supervision_Area_0 on lan0.
• Necom_SubSystem_0 on SupArea_0.
Virtual Supervision Area configuration:
IP Supervision Area configuration:
Other processes configuration:
• ositunnelling_0 on Supervision_Area_2 (for IP over OSI).
• EMLIMCORBASNMP on Supervision_Area_2 (for IP over OSI).
• EMLIMCORBASNMP on Supervision_Area_1 (for IP networks).
• EMLIMADMQ3 on Supervision_Area_0 (for OSI traffic).
....................................................................................................................................................................................................................................
March 2010
Supervision System Configuration Configuration Example
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
12 12
Integrated SPLM
Management
Overview
Purpose
This section describes how to use the Smart Photonic Layer Manager (SPLM) integrated
in 1350 OMS. SPLM is a software application which provides an algorithm dedicated to
optical line optimization for a given photonic Subnetwork of 1626LM R5.0. Some of the
functionalities of SPLM have been integrated onto the 1350 OMS EML R.9.1.1
component.
Contents
Product overview 12-2

References 12-2
Using SPLM functions from common MS-GUI 12-3
Access from MS-Gui 12-3
Search Functions 12-4
Centralized Channel Margin 12-8
APE Sequencer 12-11
Power Reference Reset 12-18
APA Optimization 12-22
...................................................................................................................................................................................................................................
March 2010
Integrated SPLM Management References
Product overview
....................................................................................................................................................................................................................................
Product overview
References
SPLM Description
The Alcatel-Lucent Smart Photonic Layer Manager is a GUI-based tool dedicated to
optical line optimization for a given photonic subnetwork. The SPLM can:
• provides a network topology management function,
• calculates and displays the available channel margin for each channel,
• tunes the output power of WSS based boards for TR-OADM configurations.
Using SPLM application, the user can:
• manage a graphical representation of your optical network with the ability of
displaying OTS, OMS and OCH layers,
• identify the channels to be monitored,
• anticipate the required tuning tasks to avoid any transmission service disruption when
BER becomes too high and FEC does not correct transmission errors,
• tune the optical spectrum to be as flat as possible at terminal and TR-OADM nodes,
via APE process.
Some of the functionalities of SPLM application have been integrated onto the 1350
OMS EML R9.1.1 component. This integration brings a great advantage because the user
will only need one server to provision and tune the power. In phase 1 the default Pref
values for ALC and TDMX/TRBD and WMAN boards are set bye the NE team before
1350 OMS can start executing the APE tool.
....................................................................................................................................................................................................................................
March 2010
Integrated SPLM Management Overview
....................................................................................................................................................................................................................................
Access from MS-Gui

Menus
From the MS-Gui the user can access the SPLM functions from the Search menu for the
listing of the managed objects and from the Action menu for executing the available
functions.
....................................................................................................................................................................................................................................
March 2010
Integrated SPLM Management Search Functions
....................................................................................................................................................................................................................................
Search Functions
Lines
From the MS-Gui main menu follow the path Search > Line Tuning > Lines. The
avilable lines are displayed.
Selecting one of the lines, click on the right mouse button and the popup menu is
displayed.
Selecting Contained OCH Groups or Contained OCH Trails, the trails or groups
corresponding to the selected line are displayed.
OCH Groups
From the MS-Gui main menu follow the path Search > Line Tuning > OCH Groups. The
available OCH Groups are displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Selecting an OCH Group, click on the right mouse button and the popup menu is
displayed.
Select Search > Involved OCH Boards, the corresponding boards are displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Selecting an OCH Group board from the list, click on the right mouse button and the
popup menu is displayed.
OCH Trails
From the MS-Gui main menu follow the path Search > Line Tuning > OCH Trails. The
avilable OCH Trails are displayed.
Selecting an OCH Group, click on the right mouse button and the popup menu is
displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Select Search > Involved OCH Boards, the corresponding boards are displayed.
Selecting an OCH Group board from the list, click on the right mouse button and the
popup menu is displayed.
....................................................................................................................................................................................................................................
March 2010
Integrated SPLM Management Centralized Channel Margin
....................................................................................................................................................................................................................................
Centralized Channel Margin

When to use
Use this function to retrieve the Line & OCH trail information.
Related Information
Before you begin

Open the centralized MS-GUI.
Task
...................................................................................................................................................................................................
1 To activate the function follow the path Action > Line Tuning > Channel Margin or from
the Line list, select a Line and from the popup menu select Actions > Channel Margin. In
the second case only the channel related to the selected line are displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select a line on the list and Click on the Next Button to retrieve the information. The
information are displayed as soon as the are available.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated SPLM Management APE Sequencer
....................................................................................................................................................................................................................................
APE Sequencer
When to use
Use this function to manage the APE Sequencer.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 To activate the APE Sequencer function follow the path Action > Line Tuning > APE
Sequencer or from the Line list, select a Line and from the popup menu select Actions >
APE Sequencer. In the second case only the channel related to the selected line are
displayed.
Click on the icon to retrieve the OCH groups related to the selected line.
Select one or more OCH group, to retrieve the contained boards, these are displayed in
the bottom part of the window.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Click on the icon to retrieve the OCH boards.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Select the boards to insert and click on the verify sign. The boards are inserted in the list
on the bottom part of the window.
Click on the Next button to proceed.
...................................................................................................................................................................................................
3 Select the OCH group in the list, the information on the contained channels are displayed
as soon as the are available in the bottom part of the window.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The field Pref(dBm) can be edited clicking twice on the field. Adjust the value as it is
recommended
Confirm the modification with the Next button.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: A data review window is displayed.
...................................................................................................................................................................................................
4 The field Pref(dBm) can be modified if desired for all the boards. Confirm with Next
button.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: A procedure result window is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated SPLM Management Power Reference Reset
....................................................................................................................................................................................................................................
Power Reference Reset

When to use
Use this function to reset the Power Reference for a Line.
Related Information
Before you begin

Task
...................................................................................................................................................................................................
1 To activate the Power Reference Reset function follow the path Action > Line Tuning >
Power Reference Reset or from the Line list, select a Line and from the popup menu
select Actions > Power Reference Reset. In the second case only the channel related to
the selected line are displayed.
...................................................................................................................................................................................................
2 Select the icon to display the available OCH Groups.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Confirm the selection with the check icon. Click on Next to proceed.
...................................................................................................................................................................................................
3 Select one OCH group and the icon to display the list of channels to reset.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Click on Next to start the reset procedure. A result window is displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated SPLM Management APA Optimization
....................................................................................................................................................................................................................................
APA Optimization
When to use
APA is Automatic Power Adjustment, based on a flat BER use this function to reset the
Power Reference for a Line adjustment at the channel endpoints.
Related Information
Network modifications like adding or removing channels may require a lot of tuning
actions to set the output power for each channel at an optimized value. Depending on the
network topology, such operation may involve a lot of boards across a lot of network
nodes.
This application helps in reducing the manual interventions with the Automatic Pre
Emphasis Adjustment (APA) process. APA process consists in optimizing tributary output
power, based on measures realized at reception.
APA process applies to long haul networks for the following topologies and network
element configurations
• Point To Point (PTP)
• Line Terminal
• Line Repeater
• Programmable Gain Equalizer
• R-OADM, WMA1100 based
• Band OADM
Before you begin

Task
...................................................................................................................................................................................................
1 To activate the Power Reference Reset function follow the path Action > Line Tuning >
APA Optimization or from the Line list, select a Line and from the popup menu select
Actions > APA Optimization. In the second case only the channel related to the selected
line are displayed.
...................................................................................................................................................................................................
2 Select the Line from the list, confirm the selection with the check icon.
...................................................................................................................................................................................................
3 Select the Optimization Direction (either GO or RETURN).
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
GO : From source node to destination node; RETURN : From destination node to source
node.
...................................................................................................................................................................................................
4 Then select the Mode (Manual Mode or Sequencer).
Click on Next to proceed.

...................................................................................................................................................................................................
5 Set the CG-APA and the FG-APA parameters .
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Parameters Description Possible Values

FG-APA Target The value you define as the From 0 to 10 dB, 0.1 dB step Default:
Channel Margin target performance to be • For 10 Gbps transponders only: 5.5
achieved. Application dB
ensures that APA process
• A soon as threre is a 40 Gbps
calculates the optimized transponders, value is set to 6 dB.
output power
corresponding to the
targeted channel margin
value.
FG-APA Min. Channel The value you define as the From 0 to 7.5 dB, 0.1 dB step Default
Margin minimum performance to • For 10 Gbps transponders: 3.0 dB
be achieved
• A soon as threre is a 40 Gbps
Must be less or equal of 1 transponders, value is set to 3.5 dB
dB than FG-APA Target
Margin.
Max. Iter. Number Enables to set the From 10 to 50 Default: 10.
maximum FG-APA process
iteration.
Margin Measurement Time for errors in 10 or 60 seconds. Default: 60 seconds
receiving before FEC
which is involved in
determining the channel
margin.
CG-APA Target The value you define as the From 0 to 10 dB, 0.5 dB step Default:
Channel Margin target performance to be 2 dB.
achieved. Application
ensures that APA process
calculates the optimized
output power
corresponding to the
targeted channel margin
value.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Not desired channels can be removed by selecting them in the list and clicking on the red
cross.
Click on Next to start the APA optimization procedure. A result window is displayed.
The following table describes the state values that can be displayed when APA Sequencer
runs.
...................................................................................................................................................................................................
6 A result window is displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
APA Sequencer State are reported in following table:
Parameter Description Possible Values

APA Sequencer Displays the current state of APA • Initializing
State Sequencer process execution.
• Running
• Ending
• Stopped On Errors
• Stopped With Success
• Stopped On Demand
• Stopped
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Parameter Description Possible Values

Sequencer Error Displays the eventual types of error • NE Error
Type during APA Sequencer process • Channel Error
execution.
Block Under Displays the functional block of the
Execution APA Sequencer process which is
running
Number of Subsets Displays the number of channel A number from 1 to x,
subsets that SPLM has determined. A depending on the complexity of
subset may be one of the following: the network.
• A group of channels having the
same optical path. At least one
channel must be at Involved
state.
• A group of channels having
different optical paths where new
channels optimization may
impact other channels which
have already been optimized.
Processing Subset Displays the number of specific
channel subset under execution.
Channel Parameters: The following table describes the parameters associated to channels.

Subset The subset number where the channel has A number from 1 to x,
been attached. A subset may be one of the depending on the complexity of
following: the network
• A group of channels having the same
optical path. At least one channel
must be at Involved state.
• A group of channels having different
optical paths where new channels
optimization may impact other
channels which have already been
optimized.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................

Initial A flag which informs about the channel • Involved: the channel is
Involvement status regarding optimization selected for optimization.
• Not Involved: the channel is
not selected for optimization.
• Observed: the channel has
been already optimized.
Current The current status of the channel with • Involved: the channel is
Involvement regard APA Sequencer process. selected for optimization.
• Not Involved: the channel is
not selected for optimization.
• Observed: the channel has
been already optimized.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
13 Integrated CPB
13
Overview
Purpose
This chapter contains the conceptual information and the related tasks that are needed to
run Commissioning and Power Balancing (CPB), which provides the functionalities for
commissioning and power balancing optical networks.
Contents
CPB Overview 13-3

Optical NEs Window 13-6
Optical Systems Window 13-8
Show Loss Reports Window 13-10
Discover NEs (using Plan) Window 13-11
Provisioning (using Plan) Window 13-14
Initial/Greenfield (using Plan) Window 13-18
Power Balancing (manual) Window 13-21
Power Balancing (using Plan) Window 13-23
Create Loss Report Window 13-25
Create Loss Report (using Plan) Window 13-27
Access and View the CPB for Optical NEs 13-29
Access and View the CPB for Optical Systems 13-30
Discover NEs (using Plan) 13-31
Provision NE Power Attributes (using Plan) 13-33
Set Initial/Greenfield Power Levels (using Plan) 13-38
Create a Loss Report 13-41
...................................................................................................................................................................................................................................
March 2010
Integrated CPB Overview
....................................................................................................................................................................................................................................
Create a Loss Report (using Plan) 13-44

Power Balance to Rebalance Power Levels 13-46
Power Balance (using Plan) to Re-optimize Power Levels 13-49
View a Loss Report 13-52
....................................................................................................................................................................................................................................
March 2010
Integrated CPB CPB Overview
....................................................................................................................................................................................................................................
CPB Overview
CPB functional definition
The CPB is a 1350 OMS feature that enables the user to commission and power balance
(CPB) an optical domain. An optical domain is a network of supported network elements
(NEs) that are connected by Optical-Optical-Optical (OOO) connections. If the NEs are
connected by Optical-Electrical-Optical (OEO) connections, they are in different optical
domain.
The CPB is an optional part of the 1350 OMS EML that is integrated into the 1350 OMS
EML photonic management capabilities. CPB has its own database and communicates
with supported NEs through its own Simple Network Management Protocol (SNMP)
interface. Refer to “CPB licensing, installation, access, and interworking” (p. 13-5) for
details.
From the Web Portal, the 1350 OMS user can invoke the CPB and initiate
commissioning.
For initial/greenfield commissions, the CPB prompts the user to select an EPT file, which
is file that is generated by the NE Engineering and Planning Tool (EPT). The EPT is used
to validate card and link topology and to configure power management attributes on the
EML and NEs. One EPT commissioning file exists per ring or linear system.
The CPB retrieves the IP addresses and other SNMP parameters and does the necessary
discovery and validations. The CPB performs the commissioning and sets the optical
parameters that are specified in the EPT file. The CPB notifies the user when
commissioning has been completed and if any errors have occurred. In addition, users can
perform various types of incremental commissioning. Refer to “CPB commissioning”
(p. 13-3) for details for both initial/greenfield and incremental commissions.
Users can also re-optimize power levels throughout an optical networking system at any
given time. Refer to “CPB power balancing” (p. 13-4) for details.
The CBP outputs appropriate loss reports to inform users of power and system conditions.
Refer to “CPB reports” (p. 13-5) for details.
CPB commissioning
Functionally, the CPB enables users to commission an optical network in any of the
following types of installations:
• Initial/Greenfield commissioning can be performed when the optical NEs are added
to the network and are interconnected without any services or cross-connects in the
system. Refer to “Initial/Greenfield (using Plan) Window” (p. 13-18) for details.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Important! Initial/Greenfield commissioning is only supported when appropriate
files are obtained from the supported NE Engineering Planning Tool (EPT).
Conventional, but secure, file transfers using FTP must be used to transfer these
commissioning files from the EPT to a specified directory in the 1350 OMS EML.
Any type of automatic file download from the NE EPT does not exist.
• Incremental NE commissioning can be performed when NEs are added or removed.
• Incremental ILA commissioning for In-Line Amplifier (ILA) nodes, which are NEs
without Reconfigurable Optical Add Drop Multiplexer (ROADM) switching
capability, can be performed when ILA NE are upgraded or these NEs are upgraded
with a new release or when more degrees (egress ports) are added.
The CPB operates in the following commissioning modes:
• In the clean slate commissioning mode, the EML retrieves the required parameters
from the its database, retrieves the equipage of each NE in the file, validates the file
contents, and begins commissioning from the terminal node, if the system is linear.
• In the continue commissioning mode commissioning continues and does not need to
be rerun once an adjustment has been completed. This mode is a performance
enhancement.
CPB power balancing

The Power Balancing function of the CPB is used to re-optimize power levels throughout
an optical networking system.
The Power Balancing function is supported for auto power managed degrees as well as
for a mix of auto and manual power managed degrees in the optical domain. However, in
a network with mixed power management type settings, power balancing is supported
only for the system portions whose power management type settings are automatic.
The Power Balancing function of the CPB can be executed/triggered as follows:
• Power Balancing can be performed on-demand, which means at any time, on a ring or
linear optical network.
• Power Balancing can also be instantaneously triggered when an NE that is carrying
customer traffic is added or deleted from the optical domain. Power Balancing can be
triggered to re-optimize the power levels with the existing power management target
power levels or to download a new EPT file with new power level target points before
re-balancing.
Since NEs can raise alarms when power adjustments are in progress, the EML disables all
autonomous notifications from the NEs and enables them when the power balancing is
completed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Users can choose one of the following power balancing operations:
• Users can download a new Plan file with new power level target points before
re-balancing. Refer to “Power Balancing (using Plan) Window” (p. 13-23) for details.
• Users can re-balance network power levels with the existing power level targets that
are already provisioned in the NEs.
Users who choose Power Balancing without a Plan file are prompted to select an NE
to start the power balancing operation. If the NE has more than one egress port (as
multi-degree nodes do), one egress port must be selected to start the power balancing
operation. Refer to “Power Balancing (manual) Window” (p. 13-21) for details.
With either user choice, Power Balancing triggers all ingress and egress adjustments in
the system. The CPB only follows through path connections (not the dropped
trails/wavelength services) when balancing the system.
CPB reports
At the end of the CPB execution, the following reports are generated:
• The Power Loss report is automatically generated at the end of the Commissioning
or the Power Balancing operation. In addition, users can manually invoke a Power
Loss report whenever the CPB creates a new Power Loss report from the current
power level data that is retrieved from the NEs.
• The System Loss report is only supported for systems that are fully auto power
managed. This report summarizes the power loss through the NEs and spans the
system. When a system is in-service, Wavelength Tracker (WT) readings are used to
calculate the average power loss through components of the system. If WT readings
are not available, the commissioning loss (which the NE stores after successful power
adjustments are made) is retrieved from the NE.
CPB licensing, installation, access, and interworking

The CPB is an optional feature that is part of the 1350 OMS EML photonic manager. The
CPB does not require a separate license.
The 1350 OMS EML can be co-resident or distributed with other components of 1350
OMS; however, all supported NEs that are in the EPT commissioning file must be
managed by one CPB/EML instance.
The CPB is installed on the command-line (and not with an Installation Wizard).
Users can access the CBP from the 1350 OMS Web Portal. Once users access the CPB,
they cannot cut-through from the CPB to the 1350 OMS EML.
The 1350 OMS HA platform configurations support the CPB; however, the CPB itself
does not support switchovers. If a switchover occurs during CPB commissioning, the user
must restart the commissioning and power balancing operation.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Optical NEs Window
....................................................................................................................................................................................................................................
Optical NEs Window

Optical NEs window purpose
The Optical NEs window enables the user to view a list of the NEs that are in the CPB
database along with their associated parameters.
Optical NEs window access

The Optical NEs window is accessed from the Web Portal by way of the following path:
Search > Commission and Power Balance > Optical NEs
From the Optical NEs window, the user can view a list of all NEs in the CPB database
along with their pertinent parameters. Refer to “Optical NEs window fields” (p. 13-6) for
details.
Optical NEs window fields

The fields of the Optical NEs window display information for the following:
• The NE name field enables the user to view the NE name as it appears in the EPT file.
This name corresponds to the same name in the 1350 OMS EML database.
• The Model field enables the user to view the model name of the NE.
• The Release field enables the user to view to the release number that is associated
with the named NE.
• The NE status field enables the user to view the status that is associated with the
named NE and the CPB.
The status, which is returned by the CPB, that is associated with the NE can be one of
the following:
– Declared indicates that a connection to the NE has been created.
– Activating indicates that a connection to the NE is in the connecting state or is
already connected.
– Deactiviting indicates that a disconnect to the NE is in progress.
– Declared indicates that the NE has been disconnected.
– Activating indicates that a logging in to the NE is in progress or a log in to the
NE has been successful.
– Supervised indicates that an NE is logged in. Traffic can occur (active) or no
traffic can occur (inactive). Messages can be sent to the NE.
– Deactivating indicates that the system is logging out from the NE.
– Declared indicates that the system is logged out of the NE.
• IP field indicates the SNMP IP address of the NE as it was retrieved from the 1350
OMS EML database.
• The Port field is always set to 161.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Optical NEs Window
....................................................................................................................................................................................................................................
Optical NEs window action menu

When the user right clicks on any of the rows in the “Optical NEs window fields”
(p. 13-6) , the Action menu becomes activated.
The Action menu provides the following two selections:
• Equipment view displays the appropriate 1350 OMS EML equipment view for the
selected NE.
• If the status field of the NE shows that the NE is Disconnected, the Establish
communication is only enabled so the user can communicate with the NE.
Optical NEs window related task

The following task is related to the Optical NEs window:
• “Access and View the CPB for Optical NEs” (p. 13-29)
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Optical Systems Window
....................................................................................................................................................................................................................................
Optical Systems Window

Optical Systems window purpose
The Optical Systems window enables the user to view the parameters that are associated
with the optical systems as they are known to the EPT along with the locations of
pertinent directories and reports.
Optical Systems window access

The Optical Systems window is accessed from the Web Portal by way of the following
path:
Search > Commission and Power Balance > Optical Systems
From the Optical Systems window, the user can view pertinent parameters that deal with
a particular optical system. Refer to “Optical Systems window fields” (p. 13-8) for
details.
Optical Systems window fields

The fields of the Optical NEs window display information for the following:
• The System name field enables the user to view the name of the system as it is
appears in the EPT file.
• The Directory field enables the user to view the default directory name where the
commissioning files are stored.
• The Report directory field enables the user to view the name of the Report Directory
where all of the Loss Reports are stored. Refer to “CPB reports” (p. 13-5) for details.
Optical Systems window action menu

When the user right clicks on any row in the “Optical Systems window fields” (p. 13-8) ,
the Action menu becomes activated.
The Action menu provides the following selections:
• Show Loss Reports enables the user to view the selected Loss Report that has been
created for a previous commissioning or power balance operation. Refer to “Show
Loss Reports Window” (p. 13-10) for details.
• Provisioning Status is only enabled when at least one provisioning operation is in the
in progress state. When selected, the system displays the status screen of any
Provisioning Status operation that is currently in progress. Refer to “Provisioning
(using Plan) Window” (p. 13-14) for details.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Optical Systems Window
....................................................................................................................................................................................................................................
• Greenfield commissioning status is only enabled when at least one greenfield
commissioning operation is in the in progress state. When selected, the system
displays the status screen of any Greenfield commissioning status operation that is
currently in progress. Refer to “Initial/Greenfield (using Plan) Window” (p. 13-18) for
details.
• Power Balance status is only enabled when at least one power balancing operation is
in the in progress state. When selected, the system displays the status screen of any
Power Balance status operation that is currently in progress. Refer to “Power
Balancing (manual) Window” (p. 13-21) or “Power Balancing (using Plan) Window”
(p. 13-23) for details.
Optical Systems window related task

The following task is related to the Optical Systems window:
• “Access and View the CPB for Optical Systems” (p. 13-30)
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Show Loss Reports Window
....................................................................................................................................................................................................................................
Show Loss Reports Window

Show Loss Reports window purpose
The Show Loss Reports window enables the user to view the selected Loss Report that
was created for a previous commissioning operation or power balance operation.
Show Loss Reports window access

The Show Loss Reports window is accessed from the Web Portal by way of either of the
following paths:
Search > Commission and Power Balance > Optical Systems > [Right Click] Action >
Show Loss Reports
Search > Commission and Power Balance > Action > Show Loss Reports
From the Show Loss Reports window, the user can view the pertinent parameters that
deal with the losses that are associated with a particular optical system. Refer to “Show
Loss Reports window fields” (p. 13-10) for details.
Show Loss Reports window fields

The fields of the Show Loss Reports window display information for the following:
• The Loss Reports Directory field is pre-populated with the default directory.
For example:
/usr/Systems/EML_{instance}/commissioning
• The Report file name is a read-only, non-editable field that, when clicked on,
displays a dialog box that contains all Loss Report filenames that are stored in the
client PC.
Show Loss Reports window buttons

The following buttons are displayed on the Show Loss Reports window:
• When clicked, the OK button opens a browser window and the contents of the Loss
Report is displayed on the browser window. The user can print, save, or delete the file
through standard browser operations.
• When clicked, the APPLY button opens a browser window and the contents of the
Loss Report is displayed on the browser window. The user can print, save, or delete
the file through standard browser operations.
• When clicked, the Cancel button closes the window.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Discover NEs (using Plan) Window
....................................................................................................................................................................................................................................
Discover NEs (using Plan) Window

Discover NEs (using Plan) window purpose and operation
The Discover NEs (using Plan) window enables the user to add NEs that are specified in a
Plan file to the CPB database.
For every NE in the Plan file that does not exist in CPB database, the CPB retrieves the
following NE parameters from the EML database and stores them in CPB database.
• NE Model
• NE version
• SNMP IP address
• SNMP Port
• Authentication Information
The Discover NEs operation adds all of the NEs that are specified in the selected Plan file
to the CPB database, if they are not already added.
The NE names in the Plan file and in the 1350 OMS EML database must be identical. If
the NE in the EPT file already exists in CPB database, the NE parameters that are
retrieved replace the parameters that are already associated with the NE. This
retrieval/replacement action updates any NE parameter that has changed since the last
retrieval (such as the release number or any authentication information). For every NE
that the CPB discovers, the status field is updated to Discovered.
Discover NEs (using Plan) window prerequisite

The Discover NEs operation must be performed before the Provisioning and
Initial/Greenfield Commissioning operations are performed using the Plan files.
Discover NEs (using Plan) window access

The Discover NEs (using Plan) window is accessed from the Web Portal by way of the
following path:
Action > Commission and Power Balance > Discover NEs (using Plan)
From the Discover NEs (using Plan) window, the user can specify a Plan file that is to be
used for the discovery operation. Refer to “Discover NEs (using Plan) window fields”
(p. 13-12) for details.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Discover NEs (using Plan) window fields
The fields of the Discover NEs (using Plan) window display information for the
following:
• The System is a selection, pre-populated field that displays the default System where
the EPT files are stored.
For example:
default
• The Plan File is a selection field that, when clicked, displays all available Plan files in
the directory that were specified in the previous System field. Select the Plan File
field value to run the discovery operation.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Discover NEs (using Plan) window buttons
The following buttons are displayed on the Discover NEs (using Plan) window:
• When clicked, the OK button confirms the specifications made and activate the
discovery operation closing the window.
• When clicked, the APPLY button confirms the specification made and activate the
discovery operation.
• When clicked, the Cancel button voids the action and closes the window.
Discover NEs (using Plan) error messages

Any error messages that the CPB generated due to a failure in the discovery operation are
logged in the Operations Log. A flashing Log icon notifies the user that error messages
have been generated. The user can open the Operations Log screen by clicking on the
Operations icon at the bottom of the screen to see the logged messages.
After the discovery operation is completed successfully, the user can select the
Commissioning and Power Balancing Optical NEs under the Search main menu and
view the list of NEs that the CPB has discovered.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Provisioning (using Plan) Window
....................................................................................................................................................................................................................................
Provisioning (using Plan) Window

Provisioning (using Plan) purpose
The Provisioning (using Plan) operation validates the fiber connections between the
various circuit packs within the NE and provisions them by sending commands to the NE.
The NE processes the command requests and creates the appropriate fiber links in its
database.
Provisioning (using Plan) window prerequisites

Before the user begins the Provisioning operation, the Discover NEs must be completed.
If the Discover NEs operation is not completed, it is performed as a logical step in the
Provisioning process. Refer to 2 for details.
The user must perform the Provisioning (using Plan) operation before any
Initial/Greenfield operation is executed or whenever a new optical NE is added to the
network.
Steps of the CPB provisioning process

The CPB provisioning process assumes that the Discover NEs operation has already been
performed; however, if the Discover NEs operation has not been performed, the
provisioning process performs this discovery operation.
The provisioning process includes the following steps:
1. Card topology is verified. The CPB verifies the equipage of each circuit packs in
each NE in the EPT file. If the actual topology does not match the topology in the
EPT file, an error message is displayed in the scrollable message area and the status
for this step becomes Failed.
Users must correct the problem and re-initiate the provisioning operation.
2. Wait for discovery. The CPB performs the discovery operation; and for each NE in
the EPT file, the CPB retrieves the following NE parameters from the 1350 OMS
EML database and stores them in the CPB:
• NE Model
• NE release
• SNMP IP address
• SNMP port
• SNMP version
• Authentication information
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
For each NE discovered, the CPB updates the NE Status field to discovered in its
database. If the NE in the EPT file already exists in CPB database, the NE parameters
that are retrieved replace the parameters that are already associated with the NE,
which updates any NE parameter that has changed since the last retrieval (for
example, the release number or any authentication information).
3. Create fiber topology. The CPB provisions the fiber connectivity between the
various circuit packs in the NE as well as the fiber connections between the NEs.
If the actual topology does not match the topology in the EPT file, an error message is
displayed in the scrollable message area and the status for this step becomes Failed.
The user must correct the problem and re-initiate the commissioning operation.
4. Provision power attributes. The CPB provisions the power attributes that are
specified in the commissioning file for the various amplifiers and attenuators.
Provisioning (using Plan) window access

The Provisioning (using Plan) window is accessed from the Web Portal by way of the
following path:
Action > Commission and Power Balance > Provisioning system (using Plan)
From the Provisioning (using Plan) window, the administrator can specify the pertinent
options and parameters to commence provisioning. Refer to “Provisioning (using Plan)
window fields” (p. 13-15) for details.
Provisioning (using Plan) window fields

The fields of the Provisioning (using Plan) window display information for the following:
• The System name field enables the user to view the name of the system as it is
appears in the EPT file.
• The Directory field enables the user to view the default directory name where the
commissioning files are stored.
• The Report directory field enables the user to view the name of the Report Directory
where all of the Loss Reports are stored. Refer to “CPB reports” (p. 13-5) for details.
• The Plan File is a read-only, non-editable field that, when clicked, displays all
available Plan files in the directory that was specified in the previous Directory field.
When the Plan File field is clicked on, the file selection dialog is displayed so the user
can select a Plan file to be used in the discovery operation.
• The Report file name field is the default name of the report file. The user can enter
another filename if the default filename is to be changed.
Provisioning (using Plan) window buttons

The following buttons are displayed on the Provisioning (using Plan) window:
• When clicked, the OK button opens a confirmation window that enables the user to
confirm or to cancel the action.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
If the action is confirmed, the Provisioning operation commences and initiates a
request to each NE in the selected EPT file to provision all of the internal links among
the various circuit packs based on the parameters in the EPT file.
• When clicked, the APPLY button opens a confirmation window that enables the user to
confirm or to cancel the action.
• When clicked, the Cancel button cancels the action and closes the window.
Provisioning (using Plan) NE Selection window

The NE Selection window is accessed from the Provisioning (using Plan) window.
The NE Selection window displays a list of NEs for provisioning. The user can select a
single NE or multiple NEs by a left click. The user can deselect any selections with a
second left click.
The user can click the NEXT button to continue to the “Provisioning (using Plan)
Provisioning Option Selection window” (p. 13-16).
Provisioning (using Plan) Provisioning Option Selection window

The Provisioning Option Selection window is accessed from the NE Selection window.
The Provisioning Option Selection window displays the following fields:
• The Preprovision cards in empty slots field enables the user to specify whether (Yes
or No) circuit packs should be provisioned in empty NE slots.
• If the Preprovision cards in empty slots field is Yes, the Create cards AINS (if
preprovisioning) field enables the user to specify whether (Yes or No) AINS circuit
packs should be created.
• The Set existing non-OT cards to admin up field enables the user to specify whether
(Yes or No) existing non-optical transponder cards should be set to admin up.
• The Optical Power Level Management (OPLM) attributes field enables the user to
specify whether the attributes should be set to Force line power mgmt to Plan file or
Force actual gain within Plan file min/max range.
Provisioning Summary window” (p. 13-16).
Provisioning (using Plan) Provisioning Summary window

The Provisioning Summary window is accessed from the Provisioning Option Selection
window.
The Provisioning Summary window provides a visual summary of the provisioning
options that the user has specified for the following fields:
• Commissioning File
• EPT name
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
• EPT version
• EPT System name
The Provisioning Summary window provides the following buttons:
• The BACK button enables the user to revert to previous windows so corrections to the
parameter specifications can be made.
• The FINISH button enables the user to complete the provisioning specifications so the
provisioning process can commence.
• The Cancel button enables the user to stop any provisioning specifications that have
been made.
Provisioning Summary window” (p. 13-16).
Provisioning (using Plan) Provisioning Status window

The Provisioning Status window is accessed from the Provisioning Summary window.
In addition, the Provisioning Status window can also be accessed when users search
optical systems and right click on any in-progress provisioning operation:
Search > Commission and Power Balance > Optical Systems > [Right Click] Action >
[Provisioning status/Greenfield commissioning status/Power Balance status]
The Provisioning Status window displays all of the steps that are performed for
provisioning.
The window is divided into the following sections:
• The top section of the window displays the list of operations that are performed for
the Provisioning operation, along with the start date and time and the status of each
operation. The top section is dynamically updated as each step is completed.
If any step of the operation fails, the user can use the Retry option for the failed step,
which enables user to repeat that step instead of re-starting the entire operation.
• The bottom section of the window displays a dynamically updated and scrollable
message area where the operation for each step is displayed.
Any error messages that the CPB generated due to a failure in the provisioning
operation are logged in the Operations Log. The user is notified by the flashing Log
icon. The user can open the Operations Log screen by clicking on the Operations icon
at the bottom of the screen to see the logged messages.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Initial/Greenfield (using Plan) Window
....................................................................................................................................................................................................................................
Initial/Greenfield (using Plan) Window

Initial/Greenfield (using Plan) window purpose
The Initial/Greenfield (using Plan) window enables the user to set the initial power levels
in each circuit pack of each NE that is specified in the Plan file.
Initial/Greenfield (using Plan) window prerequisite

Before starting the Initial/Greenfield Commissioning (using Plan) operation, both the
Discover NEs and the Provisioning (using Plan) operations must be completed for the
particular optical network domain. The Initial/Greenfield Commissioning (using Plan)
operation must be performed before any wavelength services are provisioned in the
domain.
Steps of the CPB Initial/Greenfield Commissioning process

The commissioning process includes the following steps:
1. Verify card topology. The CPB verifies the equipage of each circuit pack in each NE
in the EPT file.
2. Verify fiber topology. The CPB verifies the fiber connectivity between the various
circuit packs within the NE as well as the fiber connections between the NEs.
3. Provision power attributes. The CPB provisions the power attributes that are
specified in the commissioning file for the amplifiers and attenuators.
4. Set NE(s) to not commissioned. The CPB sets the physical ports in each NE in the
Plan file to the not commissioned state.
5. Adjust/accept Power. The CPB sends commands to run ingress/egress power
adjustments on the NEs that are specified in the commissioning file.
6. Set NE(s) to commissioned. The CPB sets the physical ports in each NE in the Plan
file to the commissioned state.
7. Create System Loss Report. If the user specified to Create a Loss Report, the CPB
creates a Loss Report with the user specified filename in the original request. The
Loss Report is created on the client PC in HTML. The user can open the HTML file
through a browser window and can save, print, or delete the report.
Initial/Greenfield (using Plan) window access

The Initial/Greenfield (using Plan) window is accessed from the Web Portal by way of the
following path:
Action > Commission and Power Balance > Initial/Greenfield (using Plan)
From the Initial/Greenfield (using Plan) window, the administrator can specify the
pertinent options and parameters to commence the initial/greenfield commissioning.
Refer to “Initial/Greenfield (using Plan) window fields” (p. 13-19) for details.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Initial/Greenfield (using Plan) window fields
The fields of the Initial/Greenfield (using Plan) window display information for the
following:
• The Commissioning Type field provides options for Clean slate, which is specified
when the commissioning operation must start from scratch, or Continue
commissioning, which is specified when greenfield commissioning must be resumed
because it has failed as a Clean slate operation.
• The Directory is a read-only, pre-populated field that displays the default directory
where the EPT files are stored.
For example:
/usr/Systems/EML_{instance}/commissioning
• The Plan File is a drop-down field that, when clicked, displays all available Plan files
in the directory that was specified in the previous Directory field. When the Plan File
field is chosen, the Plan file is used during the initial/greenfield operation.
• The Report file is a editable field which should contain the Loss Report filename that
the CPB generates.
Initial/Greenfield (using Plan) window buttons

The following buttons are displayed on the Initial/Greenfield (using Plan) window:
confirm or to cancel the action. If the action is confirmed, the commissioning
operation commences.
confirm or to cancel the action. If the action is confirmed, the commissioning
Initial/Greenfield (using Plan) Status window

The Initial/Greenfield Status window is accessed from the Initial/Greenfield (using Plan)
window.
The Initial/Greenfield Status window displays all of the steps that are performed for
commissioning.
• The top section displays the list of operations performed for the Commissioning
operation, the start date and time, and the status of each operation. The top section is
dynamically updated as each step completes.
If any step of the operation fails, the user can use the Retry option for that failed step,
• The bottom section of the screen displays a dynamically updated and scrollable
message area where the individual operation for each step is displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Any error messages that the CPB generated due to a failure in the commissioning
operation are logged in the Operations Log. The user is notified by the flashing Log icon.
The user should open the Operations Log screen by clicking on the Operations icon at the
bottom of the screen to see the logged messages.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Power Balancing (manual) Window
....................................................................................................................................................................................................................................
Power Balancing (manual) Window

Power Balancing window purpose
The Power Balancing window enables the user to re-optimize power levels throughout the
optical domain.
The user should select any node in the optical domain to start the power balancing
operation. For mesh networks, the power balancing operation should be divided into
linear networks and ring networks. The power balancing operation traverses the
connectivity from the selected node to all of the nodes in the linear or ring network. The
feature triggers all ingress and egress adjustments in the system. The optical powers on
the ingress and egress points are adjusted to the current target levels that are already
specified and stored in the NE.
To re-optimize power levels by downloading a new commissioning file with new power
target points.
Power Balancing window access

The Power Balancing window is accessed from the Web Portal by way of the following:
Action > Commission and Power Balance > Power Balancing
From the Power Balancing window, the administrator can specify the pertinent options
and parameters to commence power balancing levels throughout the network. Refer to
“Power Balancing window fields” (p. 13-21) for details.
Power Balancing window fields

The fields of the Power Balancing window display information for the following:
• The NE field lists all NEs that are in CPB database that can be selected to start Power
Balancing.
• The Egress port field lists all egress ports on the specified NE that can be selected.
• The Create Loss Report field specifies whether (Yes or No, the default) a loss report
should be created.
• If the Create Loss Report field is Yes, the Report file name field is the default name
of the Loss Report file or another user-specified filename.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Power Balancing (manual) Window
....................................................................................................................................................................................................................................
Power Balancing window buttons
The following buttons are displayed on the Power Balancing window:
confirm or to cancel the action. If the action is confirmed, the power balancing
• When clicked, the Submit button advances the user to the next window.
Power Balancing Status window

The Power Balancing Status window is accessed from the Power Balancing window.
The Power Balancing Status window displays all of the steps that are performed to
balance power levels throughout the network.
• The top section displays the list of operations performed for the Power Balancing
which enables the user to repeat that step instead of re-starting the entire operation.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Power Balancing (using Plan) Window
....................................................................................................................................................................................................................................
Power Balancing (using Plan) Window

Power Balancing (using Plan) window purpose
The Power Balancing (using Plan) window enables the user to re-optimize power levels
throughout the network by downloading a new Plan file that contains new power level
target points.
The user must choose the commissioning file to trigger the operation. There should be a
separate commissioning file for linear and ring networks. For mesh networks, the power
balancing operation should be divided into linear networks and ring networks. The feature
triggers all ingress and egress adjustments in the system. The optical powers on the
ingress and egress points are adjusted to the target power levels that are specified in the
commissioning file.
To rebalance power levels without downloading a new commissioning file and by using
the existing target levels in the system.
Power Balancing (using Plan) window access

The Power Balancing (using Plan) window is accessed from the Web Portal by way of the
following path:
Action > Commission and Power Balance > Power Balancing (using Plan)
From the Power Balancing (using Plan) window, the administrator can specify the
pertinent options and parameters to commence balancing power levels throughout the
network.
Power Balancing (using Plan) window fields

The fields of the Power Balancing (using Plan) window display information for the
following:
• The System is a drop-down selection field that displays the default system where the
EPT files are stored.
• The Plan File is a drop-down selection field that displays all available Plan files in the
previous Directory field..
• The Report file name is field in which the user inserts a valid name for the Loss
Report filen that the CPB generates.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Power Balancing (using Plan) Window
....................................................................................................................................................................................................................................
Power Balancing (using Plan) window buttons
The following buttons are displayed on the Power Balancing (using Plan) window:
Power Balancing (using Plan) status window

The Power Balancing (using Plan) Status window is accessed from the Power Balancing
(using Plan) window.
The Power Balancing (using Plan) Status window displays all of the steps that are
performed to balance power levels throughout the network.
• The top section displays the list of operations performed for the Power Balancing
(using Plan) operation, the start date and time, and the status of each operation. The
top section is dynamically updated as each step completes.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Create Loss Report Window
....................................................................................................................................................................................................................................
Create Loss Report Window

Create Loss Report purpose
The Create Loss Report window enables the user to generate a report that summarizes the
failed auto power management, the status of the last ingress/egress adjustment that was
performed for each NE, and any components that are suspected to be out of specification.
Loss Report description

The system loss report provides a summary of the loss through NEs and spans the system.
When a system is in-service, the Wavelength Tracker readings are used to calculate the
average loss through the components of the system. If WT readings are not available, the
commissioning loss (that is stored by the NE after successful power adjustments) is
retrieved from the NE. The system loss report is only supported for systems that are fully
auto power managed.
Loss reports are generated under the following conditions:
• Automatically after the CPB sequenced commissioning
• Automatically after System Power Balancing
• Manually invoked by a user through the CPB at anytime
The loss report has the following attributes:
• List of failed auto power management adjustments at the beginning of the report
• Segregated node/span view + summary
• Status of last ingress/egress adjust performed for each NE
• Auto-generation and save
• Date/Time of report generation and name of EPT commissioning file
Create Loss Report operation

To create a Loss Report, the user must first select the NE and the egress port on the NE
for the system to identify the optical network. The Create Loss Report request is sent to
the CPB to retrieve the current power levels and the target power levels (expected power
level) from all the decoder points in the optical network. The CPB then calculates the
power loss at each decoder point and creates a Loss Report file in HTML format and
stores it in the specified directory.
Colors are used to indicate normal or abnormal conditions for the egress and ingress
components. Yellow highlighting indicates a suspect component. Red highlighting
indicates defective component.
The Loss Report, when displayed to the user, can be saved locally in the client PC or sent
to a network printer.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Create Loss Report Window
....................................................................................................................................................................................................................................
Create Loss Report window access
The Create Loss Report window is accessed from the Web Portal by way of the following
path:
Action > Commission and Power Balance > Create Loss Report
From the Create Loss Report window, the administrator can specify the pertinent options
and parameters to generate a wavelength commissioning loss report. Refer to “Create
Loss Report window fields” (p. 13-26) for details.
Create Loss Report window fields

The fields of the Create Loss Report window display information for the following:
• The NE field lists all NEs that are in CPB database that can be selected to create the
loss report.
• The Egress port field lists all egress ports on the specified NE that can be selected.
• The Report file name field is a 20 character alphanumeric field that the user specifies
as the name of the Loss Report that is to be created.
Create Loss Report window buttons

The following buttons are displayed on the Create Loss Report window:
confirm or to cancel the action. If the action is confirmed, the Create Loss Report
confirm or to cancel the action. If the action is confirmed, the Create Loss Report
• When clicked, the Submit button advances the user to the next window.
Create Loss Report Status window

The Create Loss Report Status window is accessed from the Create Loss Report window.
The Create Loss Report Status window displays all of the steps that are performed to
balance power levels throughout the network.
• The top section displays the list of operations performed for the Loss Report
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Create Loss Report (using Plan) Window
....................................................................................................................................................................................................................................
Create Loss Report (using Plan) Window

Create Loss Report (using Plan) window purpose
The Create Loss Report (using Plan) window enables the user to generate a report, using
an existing commissioning file from the EPT, that details the power loss that occurs
through the NEs and throughout the optical networking system.
Create Loss Report (using Plan) window access

The Create Loss Report (using Plan) window is accessed from the Web Portal by way of
the following path:
Action > Commission and Power Balance > Create Loss Report (using Plan)
From the Create Loss Report (using Plan) window, the user can specify the pertinent
options and parameters to generate a Loss Report. Refer to “Create Loss Report (using
Plan) window fields” (p. 13-27) for details.
Create Loss Report (using Plan) window fields

The fields of the Create Loss Report (using Plan) window display information for the
following:
• The System is a drop-down selection field that displays the default system where the
EPT files are stored.
• The Plan File is a drop-down selection field that displays all available Plan files in the
previous Directory field..
• The Report file name is field in which the user inserts a valid name for the Loss
Report file that is to be created.
Create Loss Report (using Plan) window buttons

The following buttons are displayed on the Create Loss Report (using Plan) window:
confirm or to cancel the action. If the action is confirmed, the Loss Report operation
commences.
confirm or to cancel the action. If the action is confirmed, the Loss Report operation
commences.
Create Loss Report (using Plan) Status window

The Create Loss Report (using Plan) Status window is accessed from the Create Loss
Report window.
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Create Loss Report (using Plan) Window
....................................................................................................................................................................................................................................
The Create Loss Report (using Plan) Status window displays all of the steps that are
performed to create a Loss Report.
• The top section displays the list of operations performed for the Loss Report
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Access and View the CPB for Optical NEs
....................................................................................................................................................................................................................................
Access and View the CPB for Optical NEs

When to use
Use this task to view a list of the NEs that are in the CPB database along with their
associated parameters.
Related information
See the following topics in this document:
• “CPB Overview” (p. 13-3)
• “Optical NEs Window” (p. 13-6)
Before you begin

Task
Complete the following steps to view a list of the NEs that are in the CPB database along
with their associated parameters.
...................................................................................................................................................................................................
1 From the MS-GUI main menu, follow this path:

Search > Commission and Power Balance > Optical NEs
Result: The Optical NEs window is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Access and View the CPB for Optical Systems
....................................................................................................................................................................................................................................
Access and View the CPB for Optical Systems

When to use
Use this task to view the parameters that are associated with the optical systems as they
are known to the EPT along with the locations of pertinent directories and reports.
Related information
• “Optical Systems Window” (p. 13-8)
Before you begin

Task
Complete the following steps to view the parameters that are associated with the optical
systems as they are known to the EPT along with the locations of pertinent directories and
reports.
...................................................................................................................................................................................................

Search > Commission and Power Balance > Optical Systems
Result: The Optical Systems window is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Discover NEs (using Plan)
....................................................................................................................................................................................................................................
Discover NEs (using Plan)

When to use
Use this task to discover NEs, which enables you to add NEs that are specified in a Plan
file to the CPB database.
Related information
• “Discover NEs (using Plan) Window” (p. 13-11)
Before you begin

Task
Complete the following steps to discover NEs, which enables you to add NEs that are
specified in a Plan file to the CPB database.
...................................................................................................................................................................................................
1 From the MS-GUI main window, follow this path:

Action > Commission and Power Balance > Discover NEs (using Plan)
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Discover NEs (using Plan)
....................................................................................................................................................................................................................................
Result: The Discover NEs window is displayed.
...................................................................................................................................................................................................
2 Select System value from the drop-down field list.

...................................................................................................................................................................................................
3 Select Plan File value from the drop-down field list. Select the Plan File containing the
NEs the user wants to add
...................................................................................................................................................................................................
4 To confirm or cancel the discover action, use on the Discover NEs (using Plan) window:
• the OK button confirms the specifications made and activate the discovery operation
closing the window.
• the APPLY button confirms the specification made and activate the discovery
operation.
• the Cancel button voids the action and closes the window.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Provision NE Power Attributes (using Plan)
....................................................................................................................................................................................................................................
Provision NE Power Attributes (using Plan)

When to use
Use this task to provision NE power attributes using an existing Plan file.
Related information
• “Provisioning (using Plan) Window” (p. 13-14)
Before you begin

Before you begin the Provisioning operation, the Discover NEs must be completed. If the
Discover NEs operation is not completed, it is performed as a logical step in the
Provisioning process in this task. Refer to “Steps of the CPB provisioning process”
(p. 13-14), Step 2 for details.
You must perform the Provisioning (using Plan) operation before any Initial/Greenfield
operation is executed or whenever a new optical NE is added to the network.
Task
Complete the following steps to provision NE power attributes using an existing Plan file.
...................................................................................................................................................................................................
1 From the Web Portal, follow this path:

Action > Commission and Power Balance > Provisioning system (using Plan)
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: The Provisioning window is displayed.
...................................................................................................................................................................................................
2 Select the System from the drop-down field list.

...................................................................................................................................................................................................
3 Select the Plan File from the drop-down field list.

...................................................................................................................................................................................................
4 Insert a name for the loss report file, that is produced after the provisioning operation is
completed.
...................................................................................................................................................................................................
5 Click on the Next button to proceed in the provisioning procedure. The next step window
is displayed. The list displays the NE contained in the chosen Plan File. To exclude a NE
from the provisioning, select the NE in the list and click on the icon to delete it from the
list.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
6 Click on the Next button to proceed in the provisioning procedure and select the
provisioning options. The default value is Yes.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
7 Click on the Next button to proceed in the provisioning procedure, the summary window
is displayed for the user to confirm the provisioning
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
8 Click on OK or Apply button to confirm the provisioning process. The process starts and a
provisioning status window is displayed.
The process is completed when all the action in the list have the status set to Completed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Set Initial/Greenfield Power Levels (using Plan)
....................................................................................................................................................................................................................................
Set Initial/Greenfield Power Levels (using Plan)

When to use
Use this task to set the initial power levels in each circuit pack of each NE that is
specified in the Plan file.
Related information
• “Initial/Greenfield (using Plan) Window” (p. 13-18)
Before you begin

Before starting the Initial/Greenfield Commissioning (using Plan) operation, you must
complete both the Discover NEs and the Provisioning (using Plan) operations for the
particular optical network domain.
In addition, you must perform the Initial/Greenfield Commissioning (using Plan)
operation before you provision any wavelength services in the domain.
Task
Complete the following steps to set the initial power levels in each circuit pack of each
NE that is specified in the Plan file.
...................................................................................................................................................................................................

Action > Commission and Power Balance > Initial/Greenfield (using Plan)
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: The Initial/Greenfield (using Plan) window is displayed.
...................................................................................................................................................................................................
2 Select the Commissioning Type from the drop-down selections : Clean Slate or
Continue Commissioning. There is no default.
The Clean Slate option is used when the commissioning operation is required to start
from scratch.
The Continue Commissioning option is used when the user wants to resume the
green field commissioning if it has failed during Clean Slate operation.
...................................................................................................................................................................................................
3 Select the Directory from the drop-down selections. The Directory field is populated
with a “Default’ value which points to the default directory in the system where the EPT
files are stored.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The location where the EPT files are stored is currently /usr/Systems/EML_{instance}/
commissioning
...................................................................................................................................................................................................
4 Select the Plan File you want to use for the operation from the drop-down selections, all
the available files in the directory specified in the previous field are listed.
...................................................................................................................................................................................................
5 Insert a Report File name for the file CPB will produce during the operation. The reports
are generated by CPB application as HTML files and stored in client PCs.
...................................................................................................................................................................................................
6 Click on OK or Apply button to confirm the process. The process starts and a status
window is displayed.
The process is completed when all the action in the list have the status set to Completed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Create a Loss Report
....................................................................................................................................................................................................................................
Create a Loss Report

When to use
Use this task to create a loss report.
Related information
• “Create Loss Report Window” (p. 13-25)
Before you begin

Task
Complete the following steps to create a loss report.
...................................................................................................................................................................................................

Action > Commission and Power Balance > Create Loss Report
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: The Create Loss Report window is displayed.
...................................................................................................................................................................................................
2 Select the NE from the list and the egress port, if there is more than one on the selected
NE.
...................................................................................................................................................................................................
3 Enter a Report File Name; there is no default report name for this operation. The report
name can be up to 20 alphanumeric characters and all special characters except white
space, “/” (forward slash), “%” (percent), “@” (ampersand), “>”, “<”, and “|” (pipe)
characters.
...................................................................................................................................................................................................
4 Confirm the operation with OK or Apply button to send a request to create a loss report.
The process starts and a status window is displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The CPB will retrieve the current optical power values from all the NEs based on the
connectivity from the selected port.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Create a Loss Report (using Plan)
....................................................................................................................................................................................................................................
Create a Loss Report (using Plan)

When to use
Use this task to create a Loss Report (using Plan).
Related information
• “Create Loss Report (using Plan) Window” (p. 13-27)
Before you begin

Task
Complete the following steps to create a Loss Report (using Plan).
...................................................................................................................................................................................................

Action > Commission and Power Balance > Create Loss Report (using Plan)
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Create a Loss Report (using Plan)
....................................................................................................................................................................................................................................
Result: The Create Loss Report (using Plan) window is displayed.
...................................................................................................................................................................................................
2 Select a Plan File from the drop-down list.

Insert the Report File Name, it can be up to 20 alphanumeric characters and all special
characters except white space, “/” (forward slash), “%” (percent), “@” (ampersand), “>”,
“<”, and “|” (pipe) characters.
...................................................................................................................................................................................................
The CPB will retrieve the current optical power values from all the NEs specified in the
Plan file.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Power Balance to Rebalance Power Levels
....................................................................................................................................................................................................................................
Power Balance to Rebalance Power Levels

When to use
Use this task to rebalance power levels throughout the optical domain by using the
existing target levels in the system and without downloading a new commissioning file.
Related information
• “Power Balancing (manual) Window” (p. 13-21)
Before you begin

To re-optimize power levels by downloading a new commissioning file with new power
target points, refer to “Power Balancing (using Plan) Window” (p. 13-23) and the “Power
Balancing (using Plan) Window” (p. 13-23) task for details.
Task
Complete the following steps to re-optimize power levels throughout the optical domain
by using the existing target levels in the system and without downloading a new
commissioning file.
...................................................................................................................................................................................................

Action > Commission and Power Balance > Power Balancing
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: The Power Balancing window is displayed.
...................................................................................................................................................................................................
2 Select the NE from the drop-down list displaying the NEs that are in CPB database.
Selecting the NE, the Egress Port drop-down field is populated.
Select the Egress Port from the list.
...................................................................................................................................................................................................
3 Confirm the operation with OK or Apply button to send a request to launch the power
balance operation. The process starts and a status window is displayed.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated CPB Power Balance (using Plan) to Re-optimize Power Levels
....................................................................................................................................................................................................................................
Power Balance (using Plan) to Re-optimize Power Levels

When to use
Use this task to re-optimize power levels throughout the network by downloading a new
Plan file that contains new power level target points.
Related information
• “Power Balancing (using Plan) Window” (p. 13-23)
Before you begin

To rebalance power levels without downloading a new commissioning file and by using
the existing target levels in the system, refer to “Power Balancing (manual) Window”
(p. 13-21) and the “Power Balance to Rebalance Power Levels” (p. 13-46) task for
details.
Task
Complete the following steps to re-optimize power levels throughout the network by
downloading a new Plan file that contains new power level target points.
...................................................................................................................................................................................................

Action > Commission and Power Balance > Power Balancing (using Plan)
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: The Power Balancing (using Plan) window is displayed.
...................................................................................................................................................................................................
2 Select a Plan File from the drop-down list.

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
Integrated CPB View a Loss Report
....................................................................................................................................................................................................................................
View a Loss Report

When to use
Use this task to view a loss report.
Related information
• “Show Loss Reports Window” (p. 13-10)
Before you begin

Task
Complete the following steps to view a loss report.
...................................................................................................................................................................................................
1 From the MS-GUI main menu, follow either path:

Search > Commission and Power Balance > Optical Systems , select an Optical System
in the list and using the right mouse button select from the popup menu
Search > Show Loss Reports
Result: The Loss Report window is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
14 IP over OSI Tunneling
14
Overview
Purpose
This section describes the steps required to manage IP over OSI tunnelling.
Contents
IP over OSI Tunneling Overview 14-2

IP over OSI Tunneling architecture 14-2
System Configuration for IP over OSI Tunnelling 14-5
Configure the Processes 14-5
Start Configured Process 14-9
IP over OSI Tunnelling Setup 14-12
Operations on OMSN NE 14-12
Operations on 1350 OMS EML System 14-22
Start Supervision on ISA Board 14-29
IP over OSI Tunnelling GUI Functions 14-30
Remove NE from Tunnel 14-30
Tunnel Remove 14-31
...................................................................................................................................................................................................................................
March 2010
IP over OSI Tunneling IP over OSI Tunneling architecture
....................................................................................................................................................................................................................................
IP over OSI Tunneling architecture

Description
The aim of introducing new processes in 1350 OMS EML System is to pass on IP
Addresses, managed by SNMP EML–IM, over the OSI Stack processes. The figure
outlines the new components added to support the IP over OSI tunnelling function.
The figure outlines the two different treatments of IP addresses, with and without
"ositunnelling" process. In the first case (on the right of the figure), the IP addresses are
treated by OSI processes and on the OMSN Network Element are processed to decide if
the address is of type Q3 or IP and then redirected to the right agent.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
In the sequel of the document the steps required to setup the tunnelling on OMSN
Network Elements using a dedicated GUI are described.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The IP–over–OSI feature introduced at 1350 OMS EML level aims at:
• Keeping OSI DCN backbones (no OPSFv2 introduction, no router re–configuration).
• Supporting SNMP traffic to/from ISA Boards with a single end–to–end tunnel.
• One tunnel per OMSN, fully exploitation of OSI DCN resilience.
....................................................................................................................................................................................................................................
March 2010
IP over OSI Tunneling Configure the Processes
....................................................................................................................................................................................................................................
Configure the Processes

When to use
In order to be able to setup an IP over OSI Tunnelling operation, 1350 OMS EML System
should be configured with processes managing this application.
Related Information
Before you begin

Login to the Unix Server machine.
Task
...................................................................................................................................................................................................
1 On the CDE front panel, press the terminal icon to start a Unix terminal application.
Result: The terminal window is displayed.
...................................................................................................................................................................................................
2 Login as root user.

...................................................................................................................................................................................................
3 Open a telnet session on the server machine.

...................................................................................................................................................................................................
4 Set the export of the display:

export DISPLAY=<hostname>:<session number>
...................................................................................................................................................................................................
5 Insert following command after the prompt :

/alu/Install_Wizard/Install.sh –config
and select EML as the system to configure.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Result: The System Configuration window is displayed. The left pane of the window
displays Instantiable Subsystems. The right pane of the window displays a
Subsystems List.
Figure 14-1 System Configuration
...................................................................................................................................................................................................
6 Parameters to be inserted are:

• SUPERVISION_AREA: select the virtual supervision area.
• OSI_TUN_DEVICE: number of tunnel device to be used, an integer number from 0 to
15.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
• OSI_TUN_ADDRESS: address assigned to create the tunnel, it should be a unique IP
address.
• OSI_TUN_GATEWAY: IP address of the default Gateway tunnel (ISA Board Address).
• OSI_TUN_NETMASK: Net mask for the tunnel.
OSI_TUN_ADDRESS is the IP address of 1350 OMS EML, OSI_TUN_ADDRESS is the IP
address that 1350 OMS EML uses to manage the ISA boards.
The IP over OSI application allows creating a point-multipoint network and maps the OSI
address where the tunnel ends and one or more IP addresses associated to the tunnel.
To avoid having a large number of entries in the IP routing table OSI_TUN_NETMASK and
OSI_TUN_GATEWAY are used; the combination of these two values allows to reduce the
numbers of entries in the IP routing table, defining the subnetwork managed by the virtual
network card.
If the ISA boards IP addresses belong to the subnetwork a new entry is not required in the
table. Otherwise if the ISA board has an IP address that doesn’t belong to the subnetwork,
the application will create a new entry in the HP routing table for that board.
For example :
OSI_TUN_NETMASK = 255.255.0.0
OSI_TUN_GATEWAY = a.b.c..d
=> The subnetwork is a.b.0.0
This means that all the ISA boards with IP addresses between "a.b.0.0" and "a.b.255.255"
do not require specific table entry. If there is a board with address e.f.g.h, this requires a
specific entry in the routing table. If the address is for example OSI_TUN_ADDRESS =
w.x.y.z
In the HP routine table there is :
Dest Mask Gateway
a.b.c.d 255.255.255.255 w.x.y.z
a.b.0.0 255.255.0.0 a.b.c.d
e.f.g.h 255.255.255.255 a.b.c.d
Note: while OSI_TUN_ADDRESS is the 1350 OMS EML IP address,
OSI_TUN_GATEWAY is not an address of any network element; OSI_TUN_GATEWAY is
a trick necessary in HP-UX to allow writing the routing table.
...................................................................................................................................................................................................
7 Selecting Actions > Apply & Exit the data inserted are saved.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-2 Save inserted data
...................................................................................................................................................................................................
8 The modified configuration for the system should be saved to become active. Select from
System Configuration main window Main > Update Config and wait until the operation
has finished.
Figure 14-3 Update Config Selection
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2010
IP over OSI Tunneling Start Configured Process
....................................................................................................................................................................................................................................
Start Configured Process

Description
The new configured process should be started using PMC application. From Web desktop
(Search menu, Navigation area): Tools > System Monitoring > System Monitor (Global
Instance). The processes to be started are:
• ositunneling_<n> in the process group "Stack_Services_<n>".
• OsiManager in the process group "Osi_Manager".
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-4 Start IP over OSI Processes
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
The IP over OSI tunnelling application is now active on the System.

On a HP–UX terminal run the command netstat –rn, you can notice that the addresses
insert configuring the processes appear in the routing tables with the interface set as
"du0".
Figure 14-5 netstat command with osi tunnelling process running
If you stop the process ositunneling_n, automatically the process Osi_Manager stops and
if you run again the command you see that the addresses defined for ositunnelling process
are no more present.
Figure 14-6 netstat command with osi tunnelling process stopped
....................................................................................................................................................................................................................................
March 2010
IP over OSI Tunneling Operations on OMSN NE
....................................................................................................................................................................................................................................
Operations on OMSN NE
OMSN NE Setup
Note: The precondition to setup correctly the IP over OSI Tunnelling is that the
OMSN Network Element has already been created and is supervised by 1350 OMS
EML System.
This paragraph describes the operations needed on Network Element side to define the IP
over OSI tunnel completely. Starting from 1350 Optical Multi Service GUI window, there
are several ways to activate the Show Equipment function.
Select the path Search > Physical > Nodes (all Lev.) , the list of all nodes is displayed,
selecting the desired node, with the right mouse button select Inventory from Node >
Show Equipment or start from the map where the desired node is displayed and select
with the right mouse button Inventory from Node > Show Equipment. On the GUI
select the map with the Network Elements on which the tunnel should be configured.
Figure 14-7 Show equipment activation
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-8 Network Element USM
IP Point to Point
As first operation the IP Point–to–Point configuration should be defined.
Follow the path from menu Configuration > Comm/Routing > IP Configuration > IP
Address Configuration of Point–to–Point Interfaces as shown hereafter:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-9 Point–to–Point Address Configuration selection
The window to insert the required address is displayed. Insert the address used by the
board interfaces.
Figure 14-10 IP Address for PtoP Configuration
IP over OSI Tunnelling Definition

The next operation to do on Network Element side is define the IP over OSI tunnel. From
the menu Configuration > Comm/Routing > Tunnelling > IP over OSI as shown
hereafter:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-11 IP over OSI Selection
The configuration window is displayed to insert the required data.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-12 IP over OSI Tunnelling Configuration
IP Static Routing Configuration

The next operation to be performed to setup the IP over OSI tunnel is the configuration of
the IP static routing. Select from the menu Configuration > Comm/Routing > IP
Configuration > IP Static Routing Configuration as shown hereafter:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-13 IP Static Routing Configuration Selection
The configuration window is displayed to insert the required data.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-14 IP Static Routing Configuration
Create ISA Board on OMSN NE

The next operation we perform on the OMSN Network Element is the creation of the ISA
board. The ISA boards should be also already created. Select from the menu bar Action >
Network Element > Create ISA as shown in the figure:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-15 Create ISA board selection
The creation window is displayed to insert the required data.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-16 Create ISA window
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Insert the data to create the ISA board for the OMSN NE:
• Family, Type and Release corresponding to the ISA board.
• Compose the label with the right rack, subrack and slot number.
• Insert the board IP address.
• Insert the Eml Domain for the ISA board.
....................................................................................................................................................................................................................................
March 2010
IP over OSI Tunneling Operations on 1350 OMS EML System
....................................................................................................................................................................................................................................
Operations on 1350 OMS EML System

Description
The application is a GUI that allows creating, displaying, modifying and deleting IP over
OSI tunnels. This operation should be done before starting the supervision on the OMSN
NE. More ISA boards compose an OMSN NE. A different tunnel is defined for each
OMSN Network Element.
The access to the application is from the Web Portal application Maintenance >
TunnelGui (EML).
The IP over OSI Tunnelling main window is displayed as shown hereafter:
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-17 Tunnel Configuration Application
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Create a tunnel on 1350 OMS EML System
Select the button <Create> on the displayed window; the creation window is displayed to
insert the required data. The NE list can be filtered by type or name or the whole NE list
can be displayed.
Select the desired NE from the list and the type of tunnel needed. Selecting the
<Confirm> button, the tunnel is created for the selected NE. In the main window the
updated list is displayed.
Figure 14-18 Create Tunnel window
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-19 Tunnel configuration list window
Add Network Element on Tunnel

The next operation required is adding an IP NE to the tunnel on OMSN NE previously
created. To perform this operation, select the tunnel on which the IP NE should be added
and press the button Add in the "NE IP on Tunnel" part of the window.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-20 Add IP NE on selected Tunnel
The list of available IP NEs is displayed. Select the desired NE (the previously created
ISA board) from the list and Confirm with the button.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-21 Add IP NE on Tunnel
IP NEs on a Tunnel
The list of IP Network Elements inserted in a tunnel on OMSN NE can be shown
selecting the button <Detail> on the "Tunnel" part of the main window.
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Figure 14-22 Detail Window for a Tunnel
The Information displayed in the detail window are name, address and type of the OMSN
Network Element, below is the list of the IP NE added to create an IP over OSI tunnel.
....................................................................................................................................................................................................................................
March 2010
IP over OSI Tunneling Start Supervision on ISA Board
....................................................................................................................................................................................................................................
Start Supervision on ISA Board

Supervision for NE
Once the previous operations are completed the new created ISA should be supervised to
setup the created IP over OSI tunnel. Start from Multi Service GUI Application, select the
ISA board on the NE list and on the popup menu follow the path Action from Network
Element > Supervision > No Alignment....
Figure 14-23 Start Supervision on ISA board
....................................................................................................................................................................................................................................
March 2010
....................................................................................................................................................................................................................................
Remove NE from Tunnel

Remove Function
A previously added Network Element can be deleted from the added IP NE. Select the
Remove button in the main window in the NE IP on Tunnel part of the window. The
window shown in the figure below is displayed, choose the NE to be deleted and confirm
with the button.
Figure 14-24 Remove NE from Tunnel
....................................................................................................................................................................................................................................
March 2010
IP over OSI Tunneling Tunnel Remove
....................................................................................................................................................................................................................................
Tunnel Remove
Remove Function
The tunnel created can also be removed. The operation is possible on the main window
selecting the Remove button on the Tunnel part of the window. A dialog box is displayed
to confirm the operation.
....................................................................................................................................................................................................................................
March 2010
IP over OSI Tunneling Tunnel Remove
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
15 Generic Functions
15
Overview
Purpose
This chapter collects some generic functions available on 1350 OMS EML Subsystem.
Contents
NE Auto–Discovery 15-2
How to use this function 15-2
SWPA Software Package Administrator 15-4
SWPA Functionality 15-4
SWPA 15-5
...................................................................................................................................................................................................................................
March 2010
Generic Functions How to use this function
NE Auto–Discovery
....................................................................................................................................................................................................................................
NE Auto–Discovery
How to use this function

Function
The automatic creation of a new equipment is triggered by Craft Terminal. A new
message with commissioning information (NE Type & Release, UserLabel,
LocationName, NE address) is sent by CT NES to a dedicated daemon of 1350 OMS
EML Platform, passing through the Network Element. When NEs will be able to support
this commissioning message, NEs will be in charge to re–trigger this notification
periodically (each ten minutes, configurable parameter). Anyway, CT has the full control
on discovery message. CT sends periodically the message until an acknowledge from a
1350 OMS EML daemon is received.
On 1350 OMS EML, a daemon receives this message and acknowledges it to the sender.
Before sending the acknowledge message to CT, daemon has to check its correctness:
duplicated NE address, duplicated discovery message on the same NE. When
acknowledged, daemon sends a special alarm (persisted by an APT internal to the
daemon) to AS containing all the information related to the new NE.
This new alarm is displayed on a specific sub–list on AS. 1350 OMS EML user then
selects the alarm on AS and navigate to a 'Create NE' dialog, which displays the
parameters of the new NE as they appear in the AS alarm. The operator may then change
some of these parameters and confirm the NE creation, which is then processed by
PNM–IM as a normal NE creation. It may then succeed or fail and, in this last case, the
operator may retry it by changing some parameter. 'Create NE' dialog, when NE is
created, sends an action to the daemon in order to clear the alarm. The daemon, at its turn,
will send the clear of the alarm to AS.
....................................................................................................................................................................................................................................
March 2010
Generic Functions How to use this function
NE Auto–Discovery
....................................................................................................................................................................................................................................
Figure 15-1 AS NE Autodiscovery sublist
TL1 Network Elements Auto-discovery

This function allows the user to discover automatically all NEs physically connected at
Layer to a Gateway Network Element.
....................................................................................................................................................................................................................................
March 2010
Generic Functions SWPA Functionality
....................................................................................................................................................................................................................................
SWPA Functionality
Description
The SW Package Tool is provided to create software package to download towards NEs.
An OMSN SW package is composed by a common part (SDH) and one or more Service
Specific part (ATM. IP etc.), each of them is distributed separately. These packages are
loaded separately on the OS with the Server Administration application, then they have to
be merged before downloading them to an OMSN NE. The SW Package Merging tool
provides a functional and reliable way to include all files of a Service Specific package,
such as IP and ATM, into a base SDH package.
Start SWPA Application

There are two ways to start SWPA application:
• from Web Desktop application following the path Administration > Data
Management > SRVADMIN
• running the script
/usr/Systems/EML_1/swdl/srvadmin/script/run_srvadmin
To be able to run this script, the user opens a Go-Global session from his Personal
Computer. The use of Go-Global is required because the interface that opens is
graphical. Once the Go-Gloabl session is open, select the terminal option on the Unix
machine and run the command.
Note: Both kind of activation should start from a master workstation.
....................................................................................................................................................................................................................................
March 2010
Generic Functions SWPA
....................................................................................................................................................................................................................................
SWPA
The Application
The main window is partitioned in three areas, implemented with tabbed panes, showing:
• the basic software packages
• the Service Specific packages (e.g. IP, ATM, etc.)
• the OMSN packages.
The actions allowed by the application main window are:
• selecting a valid basic NE Software Package and create the base OMSN one (at the
creation there isn’t any relation with the Service Specific packages)
• selecting an OMSN package and add an available service specific package; the
application shows the list of the packages already included and the list of available
ones, following the compatibility rules guaranteed by the application itself;
• removing Service Specific package(s) from an OMSN package;
• removing installed packages (basic, Service Specific, OMSN).
The root directory and the structure used for the resulting OMSN packages is compliant
with the one used for the Server Administrator application.
....................................................................................................................................................................................................................................
March 2010
Generic Functions SWPA
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2010
Index
Numerics Alarm Management CPB

1350 OMS Acknowledge, 2-12 Access and View the CPB for
applications, 1-3 Optical NEs task, 13-29,
Alarm Severity Assignment
13-30
definition, 1-3 Profile, 10-45
Create a Loss Report (using
supported NEs, 1-5 Alarm Surveillance, 2-1
Plan) task, 13-44
1350 OMS EML Clear, 2-15
Create a Loss Report task,
functional definition, 1-3 Export, 2-16 13-41
related documentation, 1-3 Perceived Severity, 2-3 definition, 13-3
1350 OMS PKT Print, 2-16 Discover NEs (using Plan)

task, 13-31
functional definition, 1-4 Probable cause, 2-3
installation, 13-5
related documentation, 1-4 Purge, 2-14
licensing, 13-5
1350 OMS SDH Reserve, 2-9
Power Balance (using Plan) to
functional definition, 1-4 Severity panel, see Equipment
Re-optimize Power Levels
View, 1-16
related documentation, 1-4 task, 13-38, 13-49
Align Up, 10-9
1350OMS Getting Started User Power Balance to Rebalance
Guide, 1-5 Audience intended for this Power Levels task, 13-46
document, xxv, xxvi
1350OMS-eOMS Provision NE Power Attributes
Authority and Format Identifier, (using Plan) task, 13-33
related documentation, 1-5 6-45, 6-49
user access, 13-5
support of, 1-5 .............................................................
View a Loss Report task, 13-52
.............................................................
B Board view, 1-19
Customer documentation
A Added value modules ............................................................. See: Documentation
1350 OMS HA, 1-6 .............................................................
C Conventions
1350 OMS OI, 1-6
typographical, xxvii D Documentation
Alarm
1350OMS Getting Started User
Log, 3-1 Guide, 1-5
font usage, xxvii
....................................................................................................................................................................................................................................
8DG42094BAAA Issue 1 IN-1
March 2010
Index
....................................................................................................................................................................................................................................
how to order, xxxi ............................................................. Software Download Scheduler,
10-63
list of available customer N NE Auto–Discovery, 15-2
documentation, xxix, xxxi software package, 10-73
NE Management states, 6-3
Dynamic Bandwidth Optimization, .............................................................
10-64 NE MIB, 6-25
T Technical documentation
Dynamic Link, 6-3 NE view, 1-14
See: Documentation
............................................................. NEs
Transmission Alarm, 10-37
those supported for this
E Equipment View, 1-14 Typographical conventions, xxvii
release, 1-5
Message area, 1-18 .............................................................
Network Element, 5-1, 6-1
Event Log Browser, 3-1 U User guides
Network Physical Resources, 9-1
............................................................. See: Documentation
Non Service Affecting, 10-49
.............................................................
F File Transfer Scheduler, 10-63 NSAP, 6-45, 6-49
Font usage, xxvii W Web Portal, 1-4, 1-5
.............................................................
Front Panel, 1-12 workspace, 1-12
O OMSN management, 10-21
Full Distinguished Name, 2-3 workstation, 1-12
On-line help
............................................................. See: Help
G Glossary, xxix on–board simulator, 10-13
Granularity, see Performance .............................................................

Monitoring, 8-1
P Performance Monitoring
.............................................................
Granularity, 8-1
H Help, xxix, 1-34 Port View, 1-21
............................................................. Probale Cause family, 10-49
I ISA board, 10-21 Process Monitoring Control
(PMC), 14-9
.............................................................
Processing error, 2-3
L Legacy support, 1-5
Profile, see Alarm Management,
Lock, 1-12 10-45
............................................................. .............................................................
M Management State Control Panel, Q Quality of service, 2-3
1-17
.............................................................
Manuals
See: Documentation S Safety information, xxv
Message area, see Equipment Selectors, 6-45, 6-49

View, 1-18
Service Affecting, 10-49
MIB–less architecture, 10-3
Service Independent, 10-49
....................................................................................................................................................................................................................................
IN-2 8DG42094BAAA Issue 1
March 2010

8DG42094BAAA - V1 - Alcatel-Lucent 1350 OMS EML 9.1.1 User Guide (Maint-2)

Uploaded by

Copyright:

Available Formats

8DG42094BAAA - V1 - Alcatel-Lucent 1350 OMS EML 9.1.1 User Guide (Maint-2)

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

8DG42094BAAA - V1 - Alcatel-Lucent 1350 OMS EML 9.1.1 User Guide (Maint-2)

Uploaded by

Copyright:

Available Formats

Title page

1350 OMS EML 9.1.1

Information product support

About this document

Reason for revision ................................................................................................................................................................... xxv

Safety information .................................................................................................................................................................... xxv

Intended audience .................................................................................................................................................................... xxvi

How to use this information product ................................................................................................................................ xxvi

Conventions used ................................................................................................................................................................... xxvii

Related documentation .......................................................................................................................................................... xxix

How to order .............................................................................................................................................................................. xxxi

How to comment ...................................................................................................................................................................... xxxi

Overview ...................................................................................................................................................................................... 1-1

1350OMS and its applications

1350 OMS Overview ............................................................................................................................................................... 1-3

System access from Desktop ................................................................................................................................................ 1-7

Functionality available from Web desktop .................................................................................................................... 1-11

Work Environment ................................................................................................................................................................. 1-12

Equipment View Description ............................................................................................................................................. 1-14

Open in Window command ................................................................................................................................................ 1-24

NE Alarms and NE Status

NE Alarms ................................................................................................................................................................................. 1-29

NE Status ................................................................................................................................................................................... 1-31

Overview ................................................................................................................................................................................... 1-34

Help on MS-GUI Framework ............................................................................................................................................ 1-35

Help Activation ....................................................................................................................................................................... 1-36

Help on context ....................................................................................................................................................................... 1-37

Glossary ..................................................................................................................................................................................... 1-38

Overview ...................................................................................................................................................................................... 2-1

Alarm Information .................................................................................................................................................................... 2-3

Alarm Surveillance Functionalities .................................................................................................................................... 2-4

Current Alarm Management ................................................................................................................................................. 2-5

Historical Alarm Management ............................................................................................................................................. 2-6

An Iterative Approach for Alarm Description ................................................................................................................ 2-7

Access AS .................................................................................................................................................................................... 2-8

Reserving/Unreserving Alarms ............................................................................................................................................ 2-9

Acknowledging Alarms ........................................................................................................................................................ 2-12

Manually Purging an Alarm ............................................................................................................................................... 2-14

Manually Clearing an Alarm .............................................................................................................................................. 2-15

Exporting and Printing (Output...) an Alarm ................................................................................................................ 2-16

Navigation to/from Alarm Surveillance ......................................................................................................................... 2-20

Function Description ............................................................................................................................................................. 2-25

Alarm Debouncing Management ...................................................................................................................................... 2-26

3 Event and Alarm Log Browser

Overview ...................................................................................................................................................................................... 3-1

Event Log Browser .................................................................................................................................................................. 3-2

ELB Graphical User Interface

Introduction ................................................................................................................................................................................. 3-5

Menu Bar ..................................................................................................................................................................................... 3-8

Tabbed Panes ........................................................................................................................................................................... 3-13

Filters for ELB Application ................................................................................................................................................ 3-19

4 1350 OMS EML Graphical User Interface

Overview ...................................................................................................................................................................................... 4-1

1350 OMS EML GUI Features ............................................................................................................................................ 4-2

Workflow ..................................................................................................................................................................................... 4-4

Window and Menu for 1350 OMS EML ......................................................................................................................... 4-5

Filtering Area ........................................................................................................................................................................... 4-10

Error Management in 1350 OMS EML ......................................................................................................................... 4-12

Overview ...................................................................................................................................................................................... 5-1