LightSoft UM ETSI A00 V4.2R1 en PDF

LightSoft®
User Manual
Version 4.2R1
432006-2421-0H3-A00
LightSoft (ETSI) User Manual
V4.2R1
Catalog No: X37125
January 2009
1st Edition
© Copyright by ECI Telecom, 2009. All rights reserved worldwide.
This is a legal agreement between you, the end user, and ECI Telecom Ltd. (“ECI Telecom”). BY OPENING THE
DOCUMENTATION AND/OR DISK PACKAGE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS
AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE
UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE ACCOMPANYING ITEMS (INCLUDING
WRITTEN MATERIALS AND BINDERS OR OTHER CONTAINERS), TO THE PLACE FROM WHICH YOU
OBTAINED THEM.
The information contained in the documentation and/or disk is proprietary and is subject to all relevant copyright,
patent, and other laws protecting intellectual property, as well as any specific agreement protecting ECI Telecom's
rights in the aforesaid information. Neither this document nor the information contained in the documentation and/or
disk may be published, reproduced, or disclosed to third parties, in whole or in part, without the express prior
written permission of ECI Telecom. In addition, any use of this document, the documentation and/or the disk, or the
information contained therein for any purposes other than those for which it was disclosed, is strictly forbidden.
ECI Telecom reserves the right, without prior notice or liability, to make changes in equipment design or
specifications. Information supplied by ECI Telecom is believed to be accurate and reliable. However, no
responsibility whatsoever is assumed by ECI Telecom for the use thereof, nor for the rights of third parties, which
may be affected in any way by the use and/or dissemination thereof.
Any representation(s) in the documentation and/or disk concerning performance of ECI Telecom product(s) are for
informational purposes only and are not warranties of product performance or otherwise, either express or implied.
ECI Telecom's standard limited warranty, stated in its sales contract or order confirmation form, is the only warranty
offered by ECI Telecom.
The documentation and/or disk is provided “AS IS” and may contain flaws, omissions, or typesetting errors. No
warranty is granted nor liability assumed in relation thereto, unless specifically undertaken in ECI Telecom's sales
contract or order confirmation. Information contained in the documentation and in the disk is periodically updated,
and changes will be incorporated in subsequent editions. If you have encountered an error, please notify ECI
Telecom. All specifications are subject to change without prior notice.
The documentation and/or disk and all information contained therein is owned by ECI Telecom and is protected by
all relevant copyright, patent, and other applicable laws and international treaty provisions. Therefore, you must
treat the information contained in the documentation and disk as any other copyrighted material (for example, a
book or musical recording).
Other Restrictions. You may not rent, lease, sell, or otherwise dispose of the documentation and disk, as
applicable. YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR
ANY COPY IN WHOLE OR PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE. ALL RIGHTS NOT
EXPRESSLY GRANTED ARE RESERVED BY ECI TELECOM.
All trademarks mentioned herein are the property of their respective holders.
ECI Telecom shall not be liable to you or to any other party for any loss or damage whatsoever or howsoever
caused, arising directly or indirectly in connection with this documentation and/or disk, the information contained
therein, its use, or otherwise. Notwithstanding the generality of the aforementioned, you expressly waive any claim
and/or demand regarding liability for indirect, special, incidental, or consequential loss or damage which may arise
in respect of the documentation and/or disk and/or the information contained therein, howsoever caused, even if
advised of the possibility of such damages.
This is a legal agreement between you, the end user, and ECI Telecom Ltd. (“ECI Telecom”).
The end user hereby undertakes and acknowledges that they read the "Before You Start/Safety Guidelines"
instructions and that such instructions were understood by them.
It is hereby clarified that ECI Telecom shall not be liable to you or to any other party for any loss or damage
whatsoever or howsoever caused, arising directly or indirectly in connection with you fulfilling and/or failed to fulfill
in whole or in part the "Before You Start/Safety Guidelines" instructions.
Notwithstanding the generality of the aforementioned, you expressly waive any claim and/or demand regarding
liability for indirect, special, incidental or consequential loss or damage which may arise in respect of the
information contained therein howsoever caused even if advised of the possibility of such damages.
Contents
About this Manual ................................................................... xix
Overview .......................................................................................................... xvii
Intended Audience ........................................................................................... xvii
Document Organization ................................................................................... xviii
Document Conventions ...................................................................................... xx
Related Publications.......................................................................................... xxi
Obtaining Technical Documentation ................................................................. xxi
Technical Assistance........................................................................................ xxii
Introduction.............................................................................. 1-1
What is LightSoft? ............................................................................................ 1-1
Multidimensional Concept ........................................................................... 1-2
User Interface ............................................................................................. 1-2
Management Interfaces .............................................................................. 1-3
Fault Management ...................................................................................... 1-4
Trail Management ....................................................................................... 1-4
Security Management ................................................................................. 1-5
Secure UNIX Environment ............................................................................... 1-6
Getting Started......................................................................... 2-1

Overview .......................................................................................................... 2-1
Accessing LightSoft .......................................................................................... 2-1
Starting the LightSoft Client ........................................................................ 2-2
Logging In ................................................................................................... 2-3
Locking/Unlocking the User Client .............................................................. 2-5
Logging In at a Locked Client - "Fast Login" ............................................... 2-7
Logging Out ................................................................................................ 2-9
Exiting LightSoft ........................................................................................ 2-10
Initial LightSoft Screen .............................................................................. 2-11
Working in LightSoft ....................................................................................... 2-12
Menus and Commands ............................................................................. 2-12
Keyboard Options ..................................................................................... 2-13
Showing and Hiding Window Panes ......................................................... 2-14
Showing, Hiding, and Auto-Fitting Columns ............................................. 2-15
Resizing List Columns .............................................................................. 2-18
Sorting List Lines ...................................................................................... 2-19
Justifying the Column Contents ................................................................ 2-20
Moving Columns in Tables ....................................................................... 2-20
Paginating List Windows ........................................................................... 2-21
Customizing Time Formats ....................................................................... 2-21
Customizing LightSoft Object Colors ........................................................ 2-22
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary i

Contents LightSoft User Manual
Printing and Exporting to File ......................................................................... 2-24

Printing ...................................................................................................... 2-24
Exporting to CSV ...................................................................................... 2-30
Root Menu ...................................................................................................... 2-31
Object Status Color Coding ............................................................................ 2-32
GUI Cut-Through (GCT) ................................................................................. 2-32
About LightSoft Window ................................................................................. 2-33
About Tab ................................................................................................. 2-33
Info Tab ..................................................................................................... 2-33
Optional Features Tab .............................................................................. 2-34
LightSoft User Interface .......................................................... 3-1

Overview .......................................................................................................... 3-1
Main Window .................................................................................................... 3-2
Selecting Objects in the Main Window Views ............................................. 3-4
Moving Elements in the Main Window ........................................................ 3-5
Menu and Toolbar ....................................................................................... 3-6
Alarm Counter Bar ...................................................................................... 3-7
Trail Consistency Indicator (TCI) Flag and Counter.................................... 3-8
Tunnel Segment Consistency (TSC) Counter ............................................ 3-8
Alarm State Mode ....................................................................................... 3-9
Advanced Zoom and Scrolling .................................................................. 3-11
Advanced Zoom ........................................................................................ 3-11
Scrolling the Map View ............................................................................. 3-13
Navigator Window ..................................................................................... 3-13
Topology Tree ........................................................................................... 3-15
Status Bar ................................................................................................. 3-16
Topology Layers ............................................................................................. 3-17
Selecting a Topology Layer ...................................................................... 3-18
Supported Topology Layers ...................................................................... 3-18
Relationship Between Physical and Technology Layers .......................... 3-20
Virtual Links - Connecting Technology Layers ......................................... 3-21
Logical Elements (LEs) ............................................................................. 3-21
Groups ...................................................................................................... 3-21
Searching and Locating Objects .................................................................... 3-22
Search Procedure ..................................................................................... 3-23
Configuring the Search ............................................................................. 3-26
Using Bookmarks ...................................................................................... 3-29
Messaging in LightSoft ................................................................................... 3-35
Posting Messages to a Bulletin Board ...................................................... 3-36
Sending Messages to Logged-In Users .................................................... 3-38
Viewing and Attaching Notes on Fault Notifications ................................. 3-39
Creating Ongoing Notepad Notes ............................................................. 3-41
Posting LightNotes on your Desktop ........................................................ 3-43
LightSoft Properties ........................................................................................ 3-44
ii ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual Contents
Managing Elements, Groups, and Networks......................... 4-1

Overview .......................................................................................................... 4-1
Working with MEs ............................................................................................. 4-3
Creating MEs .............................................................................................. 4-3
Forcing an ME Upload ................................................................................ 4-4
LightSoft Aspects of SR9700 MEs .............................................................. 4-5
ME Properties ............................................................................................. 4-7
Working with LEs .............................................................................................. 4-9
LE Icons and Direction Representations .................................................. 4-11
Setting LE Location ................................................................................... 4-12
Creating Secondary LEs ........................................................................... 4-13
Creating a Secondary LE .......................................................................... 4-15
Modifying LE Ports .................................................................................... 4-19
Viewing ETH/MPLS LEs with the Same Network ID................................. 4-20
LE Properties ............................................................................................ 4-21
Recommendations for Creating Secondary LEs in the Optical Layer ....... 4-27
Working with Groups ...................................................................................... 4-29
Creating Groups ....................................................................................... 4-30
Adding MEs, LEs, and Groups to a Group ............................................... 4-31
Removing MEs, LEs, and Groups from a Group ...................................... 4-31
Deleting Groups ........................................................................................ 4-32
Group Properties ...................................................................................... 4-32
Automatic Network Groups ....................................................................... 4-33
Working with UMEs ........................................................................................ 4-34
Creating UMEs ......................................................................................... 4-35
Modifying UME Ports ................................................................................ 4-50
Telnetting a UME ...................................................................................... 4-51
UME Properties ........................................................................................ 4-52
Working with EMSs ........................................................................................ 4-53
EMS List ................................................................................................... 4-54
Creating an EMS ...................................................................................... 4-56
Managing and Unmanaging EMSs ........................................................... 4-57
Forcing EMS Uploads ............................................................................... 4-58
Accessing an EMS .................................................................................... 4-58
Discovering MEs ....................................................................................... 4-59
EMS Properties ......................................................................................... 4-60
Working with Ethernet Networks .................................................................... 4-62
Network Types .......................................................................................... 4-63
Network Topology Validity ........................................................................ 4-67
Network Properties ................................................................................... 4-74
Common Operations on Objects .................................................................... 4-86
LightSoft Operations ................................................................................. 4-86
GCT Operations ........................................................................................ 4-94
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary iii

Topology Links and Ports ...................................................... 5-1

Overview .......................................................................................................... 5-1
Topology Link Concepts ................................................................................... 5-1
Multilinks ..................................................................................................... 5-2
Link Direction .............................................................................................. 5-3
Physical Links and Virtual Links ................................................................. 5-3
Shared Risk Link Groups (SRLGs) ............................................................. 5-4
Viewing Topology Link Information .................................................................. 5-6
Creating Topology Links ................................................................................... 5-9
Creating a Topology Link .......................................................................... 5-10
Create Topology Link Dialog Box ............................................................. 5-15
Create Topology Link Advanced Attributes .............................................. 5-17
Path Trace Configuration Dialog Box ....................................................... 5-19
Deleting Topology Links ................................................................................. 5-20
Managing NEs in Topology Links ................................................................... 5-20
Inserting Elements into SDH Links ........................................................... 5-21
Provisioning Low Order XCs for SDM-16 following Insert to a Link .......... 5-26
Removing an Element from a Link ............................................................ 5-28
Inserting/Removing Elements to/from Optical Links ................................. 5-32
Maintenance Operations on Links .................................................................. 5-34
Link Properties ............................................................................................... 5-34
Properties for Link Toolbar ....................................................................... 5-35
Properties for Link - SDH .......................................................................... 5-36
Properties for Link - OTN .......................................................................... 5-41
Properties for Link - EoS Virtual Link ........................................................ 5-43
Properties for Link – MoT Virtual Link ....................................................... 5-45
Automatic Link Adaptation ........................................................................ 5-50
Port Properties ............................................................................................... 5-51
Properties for Port Toolbar ....................................................................... 5-52
Properties for Port - SDH .......................................................................... 5-53
Properties for Port - OTN .......................................................................... 5-56
Properties for Port – ETH/MPLS ............................................................... 5-58
Viewing Resource Availability on Links .......................................................... 5-65
Availability Map ......................................................................................... 5-66
Availability for Link .................................................................................... 5-74
Link Availability Constraints ...................................................................... 5-81
Fault Management ................................................................... 6-1

Overview .......................................................................................................... 6-1
Fault Management Concepts ........................................................................... 6-2
Notification Types ....................................................................................... 6-2
Object Status Color Indications .................................................................. 6-6
Clearable and Nonclearable Alarms and TCAs .......................................... 6-7
Accessing Fault Management Windows .......................................................... 6-8
Common Window Elements ....................................................................... 6-9
Refreshing the Window .................................................................................. 6-13
iv ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Fault Window Parameters .............................................................................. 6-14

Default Window Columns ......................................................................... 6-15
Optional Window Columns ....................................................................... 6-16
Fault Info Dialog Boxes ............................................................................. 6-20
Alarm Correlation ........................................................................................... 6-24
Alarm Correlation Columns and Icons ...................................................... 6-26
Showing or Hiding Secondary Alarms ...................................................... 6-28
Showing Secondary Alarms of a Primary ................................................. 6-29
Showing Primary Alarms of a Secondary ................................................. 6-30
Filtering Correlated Alarms ....................................................................... 6-30
Acknowledging Notifications ........................................................................... 6-31
Viewing Suggested Corrective Actions .......................................................... 6-32
Fault Management Customization .................................................................. 6-33
Customizing Fault Color Coding ............................................................... 6-33
Changing the Alarm State Mode ............................................................... 6-35
Historical Events............................................................................................. 6-37
Viewing Historical Events ......................................................................... 6-37
Configuring Event Logging, Archiving, and Historical Viewing ................. 6-38
Filtering Fault Lists ......................................................................................... 6-42
Applying a Filter ........................................................................................ 6-44
Setting a Filter as Default ......................................................................... 6-45
Filter Panel ................................................................................................ 6-46
Creating a New Filter ................................................................................ 6-49
Editing a Filter, or Creating a Filter Based on an Existing One................. 6-51
Deleting a Filter ......................................................................................... 6-53
Filter Criteria ............................................................................................. 6-54
Using Alarm Counters .................................................................................... 6-61
Viewing Counter Information .................................................................... 6-62
Creating or Editing a Counter ................................................................... 6-63
Deleting a Counter .................................................................................... 6-66
Using Alarm Indicators ................................................................................... 6-67
Viewing AI Information .............................................................................. 6-69
Creating and Editing an AI ........................................................................ 6-71
Enabling and Disabling an AI .................................................................... 6-74
Configuring an AI's Audio/Visual Behavior ............................................... 6-74
Deleting an AI ........................................................................................... 6-75
Viewing Alarmed Entities ................................................................................ 6-76
Viewing Traffic Entities Affected by an Alarm ........................................... 6-76
Viewing Alarms for Selected Traffic Entities ............................................. 6-77
Viewing EMS Current Alarms ................................................................... 6-78
Alarm Forwarding by FTP to Remote Servers ............................................... 6-79
Alarm Forwarding by FTP Workflow ......................................................... 6-80
Alarm Forwarder Configuration Window ................................................... 6-80
Alarm Forwarding by FTP Configuration .................................................. 6-82
Remote Host Setup .................................................................................. 6-84
FTP Export File Format ............................................................................ 6-86
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary v

Alarm Forwarding by SMS and Email ............................................................ 6-87

Alarm Forwarding by SMS/Email Workflow .............................................. 6-87
Alarm Export by SMS/Email Configuration ............................................... 6-88
SMS/Email Export per User Setup ........................................................... 6-91
Enabling a LightSoft Station to Send Email .............................................. 6-93
Enabling a LightSoft Station to Send SMS ............................................... 6-94
Setting SMS/Email Notification Filters ...................................................... 6-95
SMS and Email Alarm Format .................................................................. 6-98
Statistical Summary Message Format ...................................................... 6-98
User Notes ..................................................................................................... 6-99
Managing Traffic ...................................................................... 7-1

Overview .......................................................................................................... 7-1
Transport Architecture ...................................................................................... 7-3
Traffic Management Preferences ..................................................................... 7-5
Setting Traffic Preferences ......................................................................... 7-5
Provisioning SDH and EoS/MoT Trails .................................. 8-1

Overview .......................................................................................................... 8-1
Trail Concepts .................................................................................................. 8-3
Trails and Virtual Links ............................................................................... 8-3
SRLG and Other Shared Resource Minimization in Path Selection ........... 8-4
Connection Admission Control (CAC) ........................................................ 8-6
LAG Support ............................................................................................... 8-7
CNM and Trail Provisioning ........................................................................ 8-8
LightSoft ASON Support ............................................................................. 8-9
ASON Protection Schemes ...................................................................... 8-10
Trail Creation Management ............................................................................ 8-12
Trail Management Preferences ................................................................ 8-12
Trail Management Constraint Preferences ............................................... 8-14
Trail Creation Options .................................................................................... 8-18
Creating SDH and EoS/MoT Trails ................................................................ 8-20
Before Starting EoS/MoT Trail Creation ................................................... 8-21
Creating a Trail ......................................................................................... 8-22
ASON Trail Provisioning Notes ................................................................. 8-27
Create Trail Window ....................................................................................... 8-32
Create Trail Toolbar .................................................................................. 8-34
Map View .................................................................................................. 8-35
Basic Trail Parameters Pane .................................................................... 8-36
Advanced Trail Parameters Pane ............................................................. 8-39
EoS/MoT Configuration Pane ................................................................... 8-40
Trail Properties Pane ................................................................................ 8-42
Path Completion Method .......................................................................... 8-43
Endpoints List Pane .................................................................................. 8-44
Select Segment Pane ............................................................................... 8-49
Select Server Trail and Services Panes ................................................... 8-52
vi ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Select Resource Pane .............................................................................. 8-54

Resource Tree Pane ................................................................................. 8-56
Resource List ............................................................................................ 8-57
Ring Interworking Protection .......................................................................... 8-59
Dual Ring Interworking ............................................................................. 8-59
Dual Node Interworking ............................................................................ 8-61
Creating DRI trails .................................................................................... 8-62
Planned Trails ................................................................................................ 8-65
Creating a Planned Trail ........................................................................... 8-66
Importing Planned Trails ........................................................................... 8-67
Performing Actions on Trails ................................................. 9-1

Overview .......................................................................................................... 9-1
Accessing the Trail List Window ....................................................................... 9-2
Trail List Window .............................................................................................. 9-4
Trail List Toolbar ......................................................................................... 9-5
Map View .................................................................................................... 9-6
Trails Pane .................................................................................................. 9-7
Trail Properties Pane ................................................................................ 9-14
Endpoints List Pane .................................................................................. 9-20
Resource Tree Pane ................................................................................. 9-20
Resource List ............................................................................................ 9-20
Viewing Trail Information ................................................................................ 9-21
Viewing Information Detail ........................................................................ 9-21
Viewing Associated Client or Server Trails ............................................... 9-22
Viewing Alarms for Selected Trails ........................................................... 9-22
Monitoring the ASON Domain .................................................................. 9-23
Performing Trail Operations ........................................................................... 9-25
Filtering the Trails Pane ................................................................................. 9-26
Creating a Quick Trail Filter ...................................................................... 9-27
Working with Advanced Trail Filters.......................................................... 9-29
Reconnecting Trails ........................................................................................ 9-36
Editing and Deleting SDH, Optical, and EoS/MoT Trails ................................ 9-38
Editing Trails ............................................................................................. 9-39
Deleting Trails ........................................................................................... 9-44
Splitting a Long Trail ....................................................................................... 9-46
Increasing, Decreasing, or Activating Data Trail Bandwidth .......................... 9-48
Increasing Trail Bandwidth ....................................................................... 9-48
Decreasing Trail Bandwidth ...................................................................... 9-50
Activating Trail Bandwidth ........................................................................ 9-52
S-VLAN Registration from a Trail ................................................................... 9-52
Inserting MPLS PEs to MoT Trails ................................................................. 9-53
Insert PE Procedure ................................................................................. 9-54
Insert PE Window ..................................................................................... 9-57
Insert PE Results Summary ...................................................................... 9-58
What Insert PE Does ................................................................................ 9-60
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary vii

Removing MPLS PEs from MoT Trails ........................................................... 9-62

Remove PE Procedure ............................................................................. 9-63
Remove PE Window ................................................................................. 9-68
Redefining an ASON Trail’s Provisioned Path ............................................... 9-76
Batch Trail Operations .................................................................................... 9-77
Exporting Trails ......................................................................................... 9-77
Importing Trails ......................................................................................... 9-82
Synchronizing Trails ............................................................. 10-1

Overview ........................................................................................................ 10-1
Trail Synchronization Concepts ...................................................................... 10-1
Accessing Trail Inconsistency Information ................................................ 10-2
Trail Synchronization Exceptions .............................................................. 10-3
Performing Trail Synchronization ................................................................... 10-4
Trail Synchronization Procedure ............................................................... 10-5
Trail Consistency Indicator Window ............................................................... 10-9
TCI Details Pane ..................................................................................... 10-10
Parameters Pane .................................................................................... 10-11
Selected Objects Pane ........................................................................... 10-12
Trail Synchronization Window ...................................................................... 10-14
Floating Windows ................................................................................... 10-16
Trail Consistency Indicator Use Cases ........................................................ 10-21
Provisioning MPLS Tunnels ................................................. 11-1

Overview ........................................................................................................ 11-1
MPLS Tunnel Concepts ................................................................................. 11-2
Label Switching ......................................................................................... 11-2
Tunnel Types – P2P and P2MP ............................................................... 11-3
FRR Tunnel Protection ............................................................................. 11-4
CAC for MPLS Tunnels ............................................................................ 11-9
Tunnel Pathfinding .................................................................................. 11-11
Tunnel Traffic Engineering and QoS ...................................................... 11-12
Tunnel Creation Management ...................................................................... 11-16
Tunnel Management Preferences .......................................................... 11-16
Tunnel Management Constraint Preferences ......................................... 11-17
Tunnel Management Consistency Preferences ...................................... 11-19
Tunnel Management Appearance Preferences ...................................... 11-20
Tunnel Creation Options .............................................................................. 11-22
Creating Tunnels .......................................................................................... 11-22
Creating a Tunnel ................................................................................... 11-23
Create Tunnel Window ................................................................................. 11-32
Create Tunnel Menu and Toolbar ........................................................... 11-33
Other Create Tunnel Options .................................................................. 11-35
Map View ................................................................................................ 11-35
Tunnel Parameters ................................................................................. 11-36
Endpoints and Path ................................................................................ 11-43
viii ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Automatic Multi-tunnel Creation ................................................................... 11-46

Automaton Windows ............................................................................... 11-49
Performing Actions on Tunnels ........................................... 12-1

Overview ........................................................................................................ 12-1
Accessing the Tunnel List Window ................................................................. 12-2
Tunnel List Window ........................................................................................ 12-4
Tunnel List Menu and Toolbar .................................................................. 12-5
Other Tunnel List Options ......................................................................... 12-8
Map View .................................................................................................. 12-9
Tunnels Pane ............................................................................................ 12-9
Tunnel Parameters Tab .......................................................................... 12-13
Endpoints and Path Tab ......................................................................... 12-16
Viewing Tunnel Information .......................................................................... 12-18
Viewing Tunnel Information .................................................................... 12-18
Showing Tunnels Associated with a Link ................................................ 12-19
Viewing Associated Traffic Entities ......................................................... 12-20
Viewing Alarms for Selected Tunnels ..................................................... 12-21
Performing Tunnel Operations ..................................................................... 12-22
Actions on Bypass Tunnels .......................................................................... 12-23
Filtering the Tunnels Pane ........................................................................... 12-24
Creating a Quick Tunnel Filter ................................................................ 12-26
Working with Advanced Tunnel Filters ................................................... 12-28
Reconnecting Tunnels .................................................................................. 12-35
Updating FRR Protection ............................................................................. 12-36
Modifying Tunnel Protection ......................................................................... 12-37
Editing and Deleting Tunnels ....................................................................... 12-38
Adding or Removing P2MP Tunnel Tail Endpoints ................................. 12-38
Modifying Tunnel Bandwidth ................................................................... 12-43
Deleting Tunnels ..................................................................................... 12-44
Batch Tunnel Operations .............................................................................. 12-46
Exporting Tunnels ................................................................................... 12-47
Importing Tunnels ................................................................................... 12-51
Synchronizing Tunnels ......................................................... 13-1

Overview ........................................................................................................ 13-1
Performing Tunnel Synchronization ............................................................... 13-3
Tunnel Segment Consistency (TSC) Window ................................................ 13-7
Severity Breakdown Pane ........................................................................ 13-8
Selected Objects Pane ............................................................................. 13-9
Tunnel Synchronization Window .................................................................. 13-10
Tunnel Synchronization Window Toolbar ............................................... 13-11
Tunnel Synchronization Floating Window Columns ............................... 13-12
Tunnel Consistency Use Cases ................................................................... 13-13
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary ix

Provisioning Ethernet Services ........................................... 14-1

Overview ........................................................................................................ 14-1
Ethernet Service Concepts ............................................................................. 14-2
Supported Ethernet Service Types ........................................................... 14-3
Ethernet Transport Networks .................................................................... 14-4
Services per Network Type ....................................................................... 14-4
Ethernet Service Endpoint Interfaces ....................................................... 14-5
CoS for Ethernet Services ........................................................................ 14-6
Policing ..................................................................................................... 14-7
Service Overbooking ................................................................................ 14-7
Service Discrimination .............................................................................. 14-8
S-VLAN Registration for a Service ........................................................... 14-8
Pseudowire ............................................................................................... 14-9
CAC for Ethernet Services ........................................................................ 14-9
Dedicated Tunnel Services ..................................................................... 14-10
Dual Homing ........................................................................................... 14-10
Service Acquisition ................................................................................. 14-10
Service Non-Conformancy ...................................................................... 14-11
Service Creation Management ..................................................................... 14-12
Creating Ethernet Services .......................................................................... 14-13
Creating a Service .................................................................................. 14-13
Using Global Service Templates ............................................................ 14-17
Diagnosing a Create Service Failure ...................................................... 14-18
Actions Performed by Complete and Activate ........................................ 14-19
Create Ethernet Service Window ................................................................. 14-20
Create Service Menu and Toolbar .......................................................... 14-21
Other Create Service Toolbar Options ................................................... 14-22
Map View ................................................................................................ 14-23
Service Summary Pane .......................................................................... 14-23
Service Details Tab ................................................................................. 14-24
Endpoints Tab ......................................................................................... 14-36
Networks Tab .......................................................................................... 14-51
Managing Policer Profiles ............................................................................. 14-59
Policer Profiles List ................................................................................. 14-60
Creating a Policer Profile ........................................................................ 14-62
Editing a Policer Profile ........................................................................... 14-62
Deleting a Policer Profile ........................................................................ 14-63
Acquisition of Policer Profiles ................................................................. 14-63
Performing Actions on Ethernet Services........................... 15-1

Overview ........................................................................................................ 15-1
Accessing the Ethernet Service List Window ................................................. 15-2
Ethernet Service List Window ........................................................................ 15-4
Service List Menu and Toolbar ................................................................. 15-6
Other Service List Toolbar Options ........................................................... 15-8
Map View .................................................................................................. 15-8
Services Pane ........................................................................................... 15-9
x ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Service Summary Pane .......................................................................... 15-13

Service Details Tab ................................................................................. 15-13
Endpoints Tab ......................................................................................... 15-14
Networks Tab .......................................................................................... 15-14
Viewing Service Information ......................................................................... 15-15
Viewing Information Detail ...................................................................... 15-15
Viewing Associated Traffic Entities ......................................................... 15-16
Viewing Alarms for Selected Services .................................................... 15-16
Viewing Services Associated with a Policer Profile ................................ 15-16
Viewing RSTP Information ........................................................................... 15-17
RSTP Map Window ................................................................................ 15-17
Modifying RSTP Map Preferences ......................................................... 15-19
Performing Service Operations .................................................................... 15-20
Filtering Ethernet Services ........................................................................... 15-21
Creating a Quick Service Filter ............................................................... 15-23
Working with Advanced Service Filters .................................................. 15-25
Reconnecting Services ................................................................................. 15-33
Editing and Deleting Services ...................................................................... 15-34
Editing Services ...................................................................................... 15-34
Deleting Services .................................................................................... 15-38
Acknowledging Service Modifications .......................................................... 15-40
Unacknowledged Modifications Window ................................................ 15-41
Batch Service Operations ............................................................................. 15-42
Exporting Services .................................................................................. 15-43
Importing Services .................................................................................. 15-46
Provisioning Optical Trails ................................................... 16-1

Overview ........................................................................................................ 16-1
Optical Trail Concepts .................................................................................... 16-2
Optical Devices ......................................................................................... 16-2
Optical Links and Ports ............................................................................. 16-5
Optical Trails ............................................................................................. 16-5
Optical Trail Protection ............................................................................. 16-7
Channels ................................................................................................... 16-7
Relations between Ports or Cards ............................................................ 16-8
Alarms Master Mask (AMM) ..................................................................... 16-9
Optical Trail Creation Options ...................................................................... 16-10
Additional Cases .......................................................................................... 16-11
LP Without Client Equipment Termination .............................................. 16-11
COSCs in Optical Networks .................................................................... 16-12
Combiners in Optical Networks .............................................................. 16-13
Regenerators in Optical Networks .......................................................... 16-17
Optical Performance Monitoring (OPM) .................................................. 16-17
Initial System Setup ...................................................................................... 16-18
Creating Optical Trails Through Discovery ................................................... 16-19
Optical Trail Parameters ............................................................................... 16-23
Individual Optical Trail Provisioning ............................................................. 16-25
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xi

OMS Trail Provisioning ................................................................................. 16-27

OMS Trail Endpoint Selection ................................................................. 16-30
OMS Trail Endpoint Validations .............................................................. 16-32
OMS Trail Use Cases ............................................................................. 16-33
OCH Trail Provisioning ................................................................................. 16-34
OCH Trail Endpoint Selection ................................................................. 16-36
OCH Trail Endpoint Validations .............................................................. 16-38
OCH Trail Channel Issues ...................................................................... 16-38
OCH Protection ....................................................................................... 16-39
OCH Trail Use Cases ............................................................................. 16-40
LP Trail Provisioning .................................................................................... 16-42
LP Trail Endpoint Selection .................................................................... 16-44
LP Trail Endpoint Validations .................................................................. 16-45
LP Trail Use Cases ................................................................................. 16-46
Trail Acquisition by Synchronization ............................................................. 16-48
Workflow for Acquiring Trails by Synchronization ................................... 16-49
Creating OMS Trails with TCI ................................................................. 16-50
Creating OCH Trails with TCI ................................................................. 16-53
Creating LP Trails with TCI ..................................................................... 16-54
Other Actions on Optical Trails ..................................................................... 16-55
Editing Optical Trail Parameters ............................................................. 16-55
Deleting Optical Trails ............................................................................. 16-55
Inserting and Removing Optical Components ........................................ 16-55
Coupling LP Trails .................................................................................. 16-55
Viewing Optical Channel Availability ............................................................ 16-56
Optical Availability Tables ....................................................................... 16-56
Opening Availability Tables .................................................................... 16-60
Navigating from the Availability Table ..................................................... 16-61
Printing and Exporting Availability Information ....................................... 16-62
Channel Frequencies and Wavelengths ................................................. 16-63
Performance Monitoring and Maintenance ......................... 17-1

Overview ........................................................................................................ 17-1
Trail Performance Monitoring ......................................................................... 17-3
Viewing Trail Performance Data ............................................................... 17-3
Enabling or Disabling PM Counters .......................................................... 17-6
Resetting Counters ................................................................................... 17-7
Filtering Performance Monitoring Data ..................................................... 17-8
Multi Period PM ............................................................................................ 17-10
Producing Multi Period PM Reports ........................................................ 17-11
Multi Period PM Window ......................................................................... 17-13
Step 1: Traffic and Template .................................................................. 17-15
Step 2: Report Definitions ....................................................................... 17-18
Step 3: Counter List ................................................................................ 17-20
Working with Templates ......................................................................... 17-25
Configuring Thresholds ........................................................................... 17-27
Advanced Formatting .............................................................................. 17-28
Report Output Setup ............................................................................... 17-30
xii ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Exporting PM Data to CSV ..................................................................... 17-31

Filtering by CoS ...................................................................................... 17-32
Previewing the Report ............................................................................ 17-33
Generating the Report ............................................................................ 17-35
Report Format ......................................................................................... 17-36
Maintenance Operations .............................................................................. 17-41
Maintenance Operations Window ........................................................... 17-41
Performing Maintenance Operations ...................................................... 17-45
Filtering Maintenance Operation Data .................................................... 17-46
Path Protection Switching ............................................................................ 17-48
Path Protection Switch Window .............................................................. 17-49
Applying Path Protection Switch Commands.......................................... 17-52
Filtering Path Protection Switch Data ..................................................... 17-53
ASON Maintenance Operations ................................................................... 17-54
Opening the ASON Maintenance Operations Window ........................... 17-55
Performing ASON Maintenance Operations ........................................... 17-56
ASON Maintenance Operations Window and Options ........................... 17-57
Filtering ASON Maintenance Operation Data ......................................... 17-61
Viewing NE Timing Sources ......................................................................... 17-62
Timing Map Window ............................................................................... 17-62
Accessing Timing Source Information .................................................... 17-64
Viewing Timing Data in CSV Format ...................................................... 17-65
Modifying Timing Display Preferences ................................................... 17-66
Security .................................................................................. 18-1

Overview ........................................................................................................ 18-1
Security Concepts .......................................................................................... 18-3
VPNs and CNMs ....................................................................................... 18-3
Security Building Blocks ........................................................................... 18-5
Provisioning Mode .................................................................................... 18-7
CNM Restrictions ...................................................................................... 18-8
Workflow for the Security Structure ................................................................ 18-9
Security Configuration Dialog Box ................................................................ 18-10
Viewing Security Configuration Object Details ....................................... 18-12
Viewing Used by Information .................................................................. 18-13
Managing Resource Domains ...................................................................... 18-14
Resource Domains Tab .......................................................................... 18-16
Adding New Resource Domains ............................................................. 18-18
Editing Resource Domains ..................................................................... 18-21
Deleting Resource Domains ................................................................... 18-21
Managing Profiles ......................................................................................... 18-22
Profiles Tab ............................................................................................. 18-23
Adding New Profiles ............................................................................... 18-28
Editing Profiles ........................................................................................ 18-30
Deleting Profiles ...................................................................................... 18-30
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xiii

Managing Network Operators ...................................................................... 18-31

Network Operators Tab .......................................................................... 18-32
Adding Network Operators ..................................................................... 18-33
Editing Network Operators ...................................................................... 18-34
Deleting Network Operators ................................................................... 18-35
Managing User Groups ................................................................................ 18-36
User Groups Tab .................................................................................... 18-37
Adding New User Groups ....................................................................... 18-39
Editing Existing User Groups .................................................................. 18-41
Deleting User Groups ............................................................................. 18-42
Managing User Accounts ............................................................................. 18-42
Users Tab ............................................................................................... 18-43
Adding New User Accounts .................................................................... 18-44
Editing User Accounts ............................................................................ 18-46
Deleting User Accounts .......................................................................... 18-46
Customizing Security Preferences ............................................................... 18-47
Changing Your Password ............................................................................. 18-50
Viewing Active Users .................................................................................... 18-51
Forcing a User Logout .................................................................................. 18-52
Activity and Security Logs ............................................................................ 18-54
Activity Log Window ................................................................................ 18-56
Security Log Window .............................................................................. 18-57
Configuring the Export of Excess Log Records ...................................... 18-58
Viewing Exported Log XML Data ............................................................ 18-58
Filtering the Activity and Security Logs ................................................... 18-60
Summary of Menu Commands .............................................. A-1

Overview .......................................................................................................... A-1
View Menu ........................................................................................................ A-2
Faults Menu...................................................................................................... A-4
Configuration Menu .......................................................................................... A-5
Traffic Menu ..................................................................................................... A-6
Security Menu .................................................................................................. A-8
Tools Menu....................................................................................................... A-8
System Menu ................................................................................................... A-9
Window Menu ................................................................................................. A-10
Help Menu ...................................................................................................... A-10
Import/Export Traffic Syntax ................................................. B-1

Overview .......................................................................................................... B-1
XML Export/Import Concepts ........................................................................... B-2
XML Structure and DTD ............................................................................. B-2
XML File Components ................................................................................ B-2
Simplified Examples ................................................................................... B-3
XML File Structure ...................................................................................... B-5
xiv ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Trail Syntax and Examples ............................................................................... B-6

Trail Syntax Details ..................................................................................... B-6
Example XML Files for Trails ......................................................................... B-30
Example 1 for Trails .................................................................................. B-30
Tunnel Syntax and Examples ......................................................................... B-39
Tunnel Syntax Details ............................................................................... B-39
Example XML File for Tunnels .................................................................. B-54
Service Syntax and Examples ........................................................................ B-55
Service Syntax Details .............................................................................. B-55
Example XML File for Services ................................................................. B-71
Report Generation using SQL and LightSoft ....................... C-1

Overview .......................................................................................................... C-1
Using SQL to Generate Reports ...................................................................... C-1
SQL Tables Summary ................................................................................ C-4
Functional Description of SQL Tables ...................................................... C-10
Using the LightSoft Report Generator ............................................................ C-82
Root Menus ............................................................................. D-1

Overview .......................................................................................................... D-1
Working with Root Menus ................................................................................ D-2
Root Menu Applications ................................................................................... D-3
Backing Up and Restoring the LightSoft Database..............E-1

Overview .......................................................................................................... E-1
Backup and Restore Script ............................................................................... E-1
Supported Rates and Payload Types .................................... F-1

Overview .......................................................................................................... F-1
Optical Trails .................................................................................................... F-2
SDH Trails ........................................................................................................ F-3
EoS/MoT Trails ................................................................................................. F-4
Client Switchover Utility ........................................................ G-1

Overview ......................................................................................................... G-1
Switchover Procedure ..................................................................................... G-3
Installation Procedure ...................................................................................... G-3
Using the Utility ............................................................................................... G-4
Client List Definition Methods .......................................................................... G-5
Method 1 – Using a Client List File ............................................................ G-5
Method 2 – Manual Client Entry Mode ...................................................... G-6
Method 3 – Automatic Client Detection ..................................................... G-6
Method 4 – Interactive Mode ..................................................................... G-7
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xv

FTS and Orbix Cluster Resilience ......................................... H-1

Overview .......................................................................................................... H-1
Configuring Cluster Resilience ......................................................................... H-2
Index .......................................................................................... I-1
xvi ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

About This Manual
In this chapter:
Overview ........................................................................................................ xvii
3
Intended Audience .......................................................................................... xvii

3
Document Organization ................................................................................. xviii

3
Document Conventions .................................................................................... xx

3
Related Publications ........................................................................................ xxi

3
Obtaining Technical Documentation ............................................................... xxi

3
Technical Assistance ...................................................................................... xxii

3
Overview
This manual describes LightSoft®, an advanced Network Management System
(NMS) designed to manage ECI Telecom and third party telecommunications
equipment.
Intended Audience
The LightSoft User Manual is intended for network operations center (NOC)
personnel who manage ECI Telecom equipment.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xvii

About This Manual LightSoft User Manual
Document Organization
The manual contains the following chapters and appendices:
| Introduction provides an overview of the LightSoft application and
3
describes its basic concept and functions.

| Getting Started describes the basics of working with LightSoft: logging in,
3
working with windows, and viewing information.

| LightSoft User Interface provides a detailed overview of the user interface,
3
including windows, toolbars, menus, and additional useful features

included in the application.
| Managing Elements, Groups, and Networks describes the process for
3
creating and managing network objects, groups of objects, and Ethernet

networks.
| Topology Links and Ports describes the process for creating and editing
3
links and ports.

| Fault Management provides a complete description of LightSoft's
3
sophisticated fault management tools, which enable you to track network

problems easily and efficiently.
| Managing Traffic provides an overview of LightSoft traffic management.
3
| Provisioning SDH and EoS/MoT Trails describes how to create SDH and
3
SDH-based Ethernet trails and planned trails.

| Performing Actions on Trails describes the trail management interface for
ongoing trail-related operations. Trail operations include importing and/or
exporting trail definitions to/from XML files.
| Synchronizing Trails describes the trail synchronization process, which
3
reconciles differences between trail definitions in LightSoft and trail

definitions in an EMS.
| Provisioning MPLS Tunnels describes how to create MPLS tunnels, which
are the infrastructure for Ethernet services.
| Performing Actions on Tunnels describes the tunnel management interface
for ongoing tunnel-related operations.
| Synchronizing Tunnels describes the tunnel synchronization process which
reconciles differences between tunnel definitions in LightSoft and tunnel
definitions in an EMS.
| Provisioning Ethernet Services describes how to create Ethernet L1 and L2
services. LightSoft provides network operators with E2E and top-down
provisioning capabilities of carrier class Ethernet services.
| Performing Actions on Ethernet Services describes the tunnel management
interface for ongoing tunnel-related operations.
xviii ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual About This Manual
| Provisioning Optical Trails describes how to create and manage optical

trails using various methodologies.
| Performance Monitoring and Maintenance describes how to view current
3
trail performance, diagnose problems involving connections and ports, and

view and redirect traffic flow across the main and protection paths. The
Multi Period PM feature enables historical reporting. This section also
describes how to view the timing sources of network elements (NEs).
| Security describes the various security features and processes for creating
3
resource domains, capability profiles, network operators, user groups, and

users.
Appendices:
| Summary of Menu Commands describes the functions available from the
3
LightSoft main window menu bar and toolbar icons.

| Import/Export Traffic Syntax describes the structure of the XML files used
3
for defining trail, MPLS tunnel, and Ethernet service data in LightSoft,
including command references and examples of XML syntax.
| Report Generation using SQL describes the main elements of the
3
Structured Query Language (SQL) supported by LightSoft, including

parameters, SQL data type, and a short description of each parameter,
enabling you to perform user queries on the application's database.
| Root Menus shows how to access various useful functions from the Sun
3
desktop.
| Backing Up and Restoring the LightSoft Database shows how to use a
3
script to manually back up or restore the LightSoft database on the same

station, or to purge old backups, in addition to the replication features
provided by the Remote Data Replication (RDR) application.
| Supported Rates and Payload Types provides a table of typical supported
3
payload types.
| Client Switchover Utility eases operations in multi-server configurations,
3
allowing administrators to conveniently switch several LightSoft clients

from one server to another by automating the switchover process.
| FTS and Orbix Cluster Resilience describes LightSoft’s hot standby
mechanisms for increased cluster resilience.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xix

Document Conventions
When applicable, this manual uses the following conventions.
Document Conventions
Convention Indicates Example

Bold | Names of menus and commands On the Alarms menu...
| To Do procedures
> Current menu option opening a On the LightSoft main window
submenu, or leading you to another menu bar, select Configuration
command > Create > Topology Link.
Bold Title Case Used to indicate window and dialog Filters are created in the Filter
box names, and most GUI elements dialog box.
Italics New terms and emphasized text See examples in text.
Boxes around Notes, cautions, warnings See examples following.

text
Courier Command line text, programming /opt/NMS/server/sql
code, /sqlDump
user-typed information
Icons Used in text descriptions and within Click the Create Bookmark
procedures
icon in the main window.
NOTE: Text set off in this manner presents clarifying

information, specific instructions, commentary, sidelights, or
interesting points of information.
OPTIONAL FEATURE: Text set off in this manner

describes a fully integrated add-on capability, available on a
cost basis from LightSoft. Only functions and menu options
of features purchased are activated in the application.
CAUTION: Text set off in this manner indicates that failure

to follow directions could result in damage to equipment or
loss of information.
WARNING: Text set off in this manner indicates that

failure to follow directions could result in bodily harm or loss
of life.
xx ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual About This Manual
Related Publications
The following additional publications may be of assistance to you:
| LightSoft General Description
| XDM® General Description
| EMS-XDM User Manual
| LCT-XDM User Manual
| Remote Database Replicator (RDR) User Manual
| Master Glossary and Acronyms
Obtaining Technical
Documentation
To obtain technical documentation related to LightSoft or any other ECI
Telecom product, please contact:
ECI Telecom Ltd.
Network Solutions Division
Documentation Department
30 Hasivim St.
Petach Tikva 49130
Israel
Fax: +972-3-9268022
Email: on.documentation@ecitele.com
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xxi

Technical Assistance
The configuration and operation of LightSoft are highly specialized processes.
If you have questions or concerns about your network design or operation, ECI
Telecom maintains a team of design engineers and highly trained field service
personnel. Their services are available to customers at any time.
If you are interested in obtaining design assistance or a network installation
plan from the ECI Telecom customer support team, contact your ECI Telecom
sales representative. With any support related issues, technical or logistic,
please contact the ECI Telecom customer support center at your location. If
you are not familiar with that location, contact our central customer support
center action line at:
International: + 972-3-9266000
Telephone
US: 1-888-ECI-TECH (324-4406)
International: +972-3-9266370
Telefax
US: 1-954-351-4406
Email on.support@ecitele.com
Website www.ecitele.com
xxii ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

1
Introduction
In this chapter:
What is LightSoft? ........................................................................................... 1-1
3
Secure UNIX Environment ............................................................................. 1-6

3
What is LightSoft?
LightSoft is an advanced Network Management System (NMS) designed to
manage ECI Telecom and third-party telecommunications equipment. It
supports open interfaces and a distributed architecture for maximum scalability
and flexibility.
LightSoft consists of a server and a client application. Depending on the size of
the managed network, number of Element Management Systems (EMSs), and
number of clients, the server application may reside on one or more stations
(Sun workstations).
Many EMSs of different types may be managed by one LightSoft application.
Communication to these EMSs is implemented via a CORBA interface based
on TMF (TeleManagement Forum)-814 (MTNM v.2 and v.3, MultiTechnology
Network Management) recommendations, with proprietary extensions where
relevant.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary 1-1

Introduction LightSoft User Manual
Multidimensional Concept
LightSoft supports the following views or layers:
| Physical layer, representing actual physical equipment (shelves or racks)
and the fiber links between them.
| Management layer, representing the EMSs and the Managed Elements
(MEs) they control.
| Technology layers: SDH, optical, and ETH/MPLS. An additional SDH
Server layer is available to CNM users.
Physical MEs or cards are represented as logical elements (LEs) in each of the
technology layers. LEs can be customized to achieve the desired topological
representation.
User Interface
The LightSoft Graphical User Interface (GUI) is a powerful yet easy-to-use
tool for managing your network. It combines configuration, maintenance, and
performance management tools with fault handling and end-to-end trail
definition.
The LightSoft user interface features recent advancements in topology map
design - multilayer topology views. These views enable you to show the
topology of each technology layer independently of the topology of the
physical layer.
The LightSoft main window features a map with zoom and navigator that
displays NEs, nestable NE groups, and links between NEs. NE and NE group
icons and links are color coded according to alarm and operational statuses. In
addition, a tree lists all NEs and NE groups with their alarm indicators.
Netwide alarm counters and trail consistency indicators are also shown.
Map windows allow you to view existing trail capacity on system segments,
monitor the timing sources of each NE in the SDH topology, and view the
RSTP configuration that controls Ethernet packet routing.
1-2 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual Introduction
Management Interfaces
LightSoft supports an open CORBA-based north- and southbound interface to
manage or be managed by third-party applications. The interface, which covers
alarms and configuration northbound, and alarms, configuration, and
provisioning southbound, complies with the MTNM information model being
developed by the TMF, a consortium of all major telecom equipment vendors.
The TMF MTNM standard interface of LightSoft enables LightSoft to easily
integrate under and be managed by higher level management systems (OSSs),
as well as manage various third-party EMSs. LightSoft complies with all
relevant ITU-T standards and Telemanagement Forum (TMF)
recommendations.
The Northbound interface is easily developed between LightSoft and
Operational Support Systems (OSS) using the TMF MTNM interface
definition. OSS may be used to manage several management systems,
LightSoft being one of them. LightSoft supports the standard interface
northbound (MTNM V 2.1).
The Southbound interface to EMS systems allows top-down management of
transport networks, optical networks, and data networks, as well as hybrid
combination networks. The ability to be managed via a standardized interface
has the advantage of working with existing equipment, saving considerably on
CAPEX and maximizing on existing network infrastructure. LightSoft supports
the standard interface southbound (MTNM V 3.5 and MTNM V 2.1).
For more information about northbound and southbound interfaces, see the
LightSoft Northbound Interface User Guide. Port information is provided in the
document Technical Note TCP/UDP Ports Used in ECI TND Management
Product Lines.
The following other management interfaces are also supported:
| SNMP adaptor, which maps alarms and events to the OSS; see the
Northbound SNMP Gateway for LightSoft Alarms Integration product
description.
| ASCII support for alarms export; see Alarm Forwarding by SMS and
Email.
| XML support, enabling you to conveniently import or export trail definition
data in batch from/to XML files; see Import/Export Traffic Syntax.
| SQL interface, enabling you to query the LightSoft database; see Report
3
Generation using SQL.

Fault Management
LightSoft features state-of-the-art Current Alarms and Event Log windows
with sophisticated filtering and sorting capabilities. The alarm management
modules and GUI have been especially designed for the era of large networks.
Netwide user-configurable alarm counters and alarm indicators (audio and/or
visual popup) are also supported.
Trail Management
LightSoft fully supports automatic end-to-end provisioning of SDH and
Ethernet over SDH (EoS) and MPLS over Transport (MoT) trails, including
sophisticated schemes such as concatenation, diverse routing, DRI, and DNI. In
addition, automatic provisioning of optical trails is performed by a user-
initiated acquisition based on the installed equipment configuration. The
pathfinder algorithm supports user configuration of up to four optimization
parameters, for example, cost, distance, and number of nodes traversed. It also
takes into account information about shared resources of links (Shared Risk
Link Group, or SRLG).
Trail lists support sophisticated sorting and filtering options. An Alarms
column lets you easily identify alarmed trails. You can also view current trail
performance, diagnose problems involving connections and ports, or switch
protection paths directly from LightSoft windows, without opening EMS
windows.
Trails may be defined from the GUI or mass configured in batch form based on
XML files. There is a mechanism for detecting, displaying, and reconciling
inconsistencies between the LightSoft trail database and that of the various
EMSs and/or MEs.
The LightSoft trail management concept is built to fully take advantage of the
converged nature of XDM-based networks. Its inherent knowledge of the
relationships between the multiple transport layers (SDH, ETH/MPLS and
Optical) is important for obtaining a clearer picture and better understanding of
complex networks.

LightSoft User Manual Introduction
Security Management
LightSoft has a fine-granularity security mechanism for defining user groups in
two planes:
| Individual or groups of user functions
| Resource domains
Domains can be defined down to the level of individual ports. Users are
authenticated on the basis of user names and passwords with expiration dates.
Service providers can partition their networks according to their organizational
and logistical needs, for example, according to regions with each regional NOC
assigned access privileges for the relevant equipment. Users are limited to
specific capabilities/operations on their allocated resources in the network,
allowing a region to safely manage its own equipment. A national NOC can
control the entire network while, in parallel, regional NOCs manage individual
regions.
LightSoft fully supports services traversing regional borders by recognizing all
resources, regardless of region, as available for trail provisioning.
Customer Network Management (CNM) enables the service provider to lease
network resources to customers, and provides the customer with the ability to
self-manage these resources.
The sophisticated scheme allows both the customer and the service provider to
perform alarm management, trouble shooting and maintenance operations on
the resources. For service provisioning purposes, the resources are exclusively
reserved for the designated customer only, i.e. services intended for other
customers cannot be provisioned on that resource.
The SDH Server Trail Layer View displays SDH server trails as well as
endpoints (in accordance with the user's CNM resource permissions), enabling
the CNM user to create client trails between the endpoints.
Profiles define combinations of capabilities that users in a user group may
perform on applicable resources (for example, configuring security or
provisioning trails). Resource-only profiles allow privileges to apply to a
specific resource. Multiple resource-only profiles for multiple resource
domains can be assigned to the same user group, providing in-depth control
over user access privileges to different network elements.
When using the GUI cut-through (GCT) feature on a specific ME, LightSoft-
level users are mapped to the closest possible privilege category at the EMS
level or blocked from accessing the EMS.
True multiconfigurator mode is supported. This means that users with
overlapping configuration privileges may log in and work in LightSoft
simultaneously. This applies to all but a few NMS- and EMS-level operations
on different MEs (in such cases a second LightSoft user can open the same
Shelf View with view-only privileges).

Activity and security logs monitor user operations, system accesses, and
password definitions directly from LightSoft windows without the use of UNIX
commands. A user with appropriate permissions can log out another user from
the system (force logout).
RDR Remote Database Replication (RDR) allows telecommunications network
personnel to back up management system databases, implement effective
recovery from those backups to mirror components, and return the primary
component to normal operation when possible.
The RDR scheme supports LightSoft as well as XDM and SYNCOM™ EMSs.
This means backup management hardware may be deployed in a 1:1 or 1:n
configuration. The scheme is based on replication of the various databases and
requires a data or Digital Communications Network (DCN) link between the
active and mirror sites. For more information, refer to the RDR User Manual.
Secure UNIX Environment

LightSoft's UNIX operating system environment has been hardened to protect
it from:
| Hacking and intrusions
| Unauthorized access to customers' sensitive data
| Damage to normal system functionality by mistaken or ill-intentioned users
The system can be installed in one of two security levels:
| Level 1 is compulsory and includes updated security patches, kernel
security settings, password protection for all accounts, unique UID for all
user accounts, and secured inetd services, RPC services, network
configuration, and file system configuration. It also contains some
restrictions on FTP services and disabling of unnecessary system services
(such as NFS and SNMP).
| Level 2 is optional and includes password time expirations for all users, and
disabling of PPP and sendmail functionalities.

2
Getting Started
In this chapter:
Overview ......................................................................................................... 2-1
3
Accessing LightSoft ........................................................................................ 2-1

3
Working in LightSoft..................................................................................... 2-12

3
Printing and Exporting to File ....................................................................... 2-24

Root Menu ..................................................................................................... 2-31
3
Object Status Color Coding ........................................................................... 2-32

3
GUI Cut-Through (GCT)............................................................................... 2-32

3
About LightSoft Window .............................................................................. 2-33

3
Overview
This section describes the basics of working with the LightSoft user interface,
including how to log in, how to work with its windows, and how to view
information.
Accessing LightSoft
Logging into a LightSoft client gives access to LightSoft features in accordance
with assigned security permissions and purchased optional features.
The user session at a client can be locked, either manually or automatically.
While locked, all open windows and work-in-progress are hidden from view.
The session can subsequently be unlocked, with all the windows redisplayed as
before. The user can unlock the session by entering his login details.
To avoid overloading the system, it is important that users log out at the end of
a shift. An authorized user can force a user to logout from a client, for example,
to log in another user to that client.

Getting Started LightSoft User Manual
LightSoft features single sign-on between supported layers. Once you are
logged in to LightSoft, you automatically have access to managed EMSs
through GCT, without needing to provide additional login details.
NOTE: In larger networks you can save time logging in if

you log in instead of another user who has locked the client
instead of logging out. That user should be a member of the
same user group. If these conditions are present, a "fast login"
process applies, which may reduce your login time to just
seconds. For more information, see Logging In at a Locked
Client - "Fast Login".
Starting the LightSoft Client

LightSoft is a Client-Server application comprising server and client machines
on the same or different hardware depending on, for example, the network size
and customer work style. A LightSoft client session is initiated from a client
machine (the server machine must be running), as follows:
| In the case of a dedicated Linux client machine (one client and no zones),
the LightSoft client session opens automatically when you select the "client
session" login option.
OR
| More commonly, using a Solaris remote terminal, you log in using the
console Common Desktop Environment (CDE) session and start the
LightSoft client via a root menu.
Many such installations utilize NMS Client Proxy machines where multiple
LightSoft client sessions are run from a single client machine, each user
employing a PC that uses remote display software (such as GoGlobal or
Exceed).
OR
| If you are working via an X-Terminal, log in (for example, via Telnet) to
the workstation where the LightSoft client is installed and configured), and
enter the following at the workstation's command line prompt:
/opt/NMS/client/sh/start_NMSclient.sh &
(The " &" at the end of the expression is optional. It enables LightSoft to
continue working in the background if the UNIX window is closed.)

LightSoft User Manual Getting Started
Logging In
Logging in to a LightSoft client requires a user name and password assigned by
the administrator. The password can be changed by the user; see Changing
Your Password. LightSoft uses the capability profile of your user group to
configure the topology views and the actions you can perform.
A user can be logged in at only one client at a time. The user must first log out
from one client before attempting to log in at another; see Logging Out.
Only one user at a time can be logged in at a specific client. Authorized users
may force another user to log out from a client in order to log in to that client;
see Forcing a User Logout. Alternatively, if a user has locked a client, another
user may log in to that client, effectively logging out the original user; see
Logging In at a Locked Client - "Fast Login".
Login is limited by the maximum number of users allowed (per the concurrent
logins cost option) and user group login restrictions; see User Group Login
Limit.
To log in to LightSoft:
1. In the LightSoft Login dialog box, enter your user name and password.
2. Click Login. If this is the first login since the LightSoft client was started,
the LightSoft splash screen opens; see Initial LightSoft Screen. The
LightSoft main window then opens; see Main Window.
If you started a session by mistake, or do not have a valid user name and
password, you can abort the session before completing the login.
To abort a session before logging in:

1. In the LightSoft Login dialog box, click Close. A confirmation dialog box
opens.
2. Click Yes to confirm. All LightSoft windows are closed.

A user can be logged into only one LightSoft client at a

time.
If you attempt to log in to a client while still logged in at another client, an
error message opens.
You should first log out from the original client and then try to log in again at
the current client.
NOTE: In rare circumstances a second login may be allowed

to go through (for example, as a consequence of server
shutdown in conjunction with other conditions). If this should
happen, after a short time the first client is automatically
forced to log out. Certain active processes at the first client
are aborted. For details of the active processes, see the note in
Logging Out.
At the original client terminal, a message opens.
After clicking Logout in the message window or after a

timeout period has elapsed, the active processes are closed
and a post-logout message appears.
Clicking OK opens the LightSoft Login dialog box.

Locking/Unlocking the User Client

The user session at a client can be locked, either manually by the user or
automatically. While locked, open windows and work-in-progress are hidden
from view.
LightSoft may automatically lock a user client session following a period of
inactivity. For details, see Customizing Security Preferences. The applicable
timeout period can be set on a per-user basis using the Default Inactivity
Timeout parameter.
In either case, the LightSoft Unlock dialog box will be present (see To unlock
a user session). The session can subsequently be unlocked with all the windows
redisplayed as before.
User sessions, whether locked or unlocked, can be force logged out to enable
another user to log in to the client; see Forcing a User Logout.
NOTE: When a user session is locked, GCT operation

windows are closed. While working for an extended period in
an EMS via GCT, LightSoft may sense inactivity and
automatically lock LightSoft due to timeout. A popup
message will appear one minute before the timeout is
triggered.
Clicking Continue cancels the timeout. The notice time

before timeout can be modified by changing a system file;
contact ECI Telecom customer support for assistance.

To manually lock a user session:

| Select System > Lock. All open windows are hidden and the Unlock
dialog box appears, showing the locked user name.
To unlock a user session (whether locking was manual or

due to inactivity timeout):
1. In the Unlock dialog box, enter your password.
If you are not the locked user, you can log in instead of the logged user (in
effect, logging out the locked user and possibly aborting any active
processes); see Logging In at a Locked Client - "Fast Login".
2. Click Login. Open windows and work-in-progress at the time the system
was locked are redisplayed. (This is not a "login" in the strict sense as the
user was not logged out.)

Logging In at a Locked Client - "Fast Login"

When a user session is locked - see Locking/Unlocking the User Client -
another user can log in from the same client, in effect forcing logout of the
original user and logging in instead.
In larger networks you can save time by logging in this way. If the user is a
member of the same user group and has locked the client (instead of logging
out), a "fast login" process applies. This may reduce the login time to seconds.
If the original user has certain active processes running, the action is allowed
only if the new user has Security Administration capability. For details of the
active processes, see the note in Logging Out. In that case, before the action is
implemented, the authorized new user must confirm that active processes
initiated by the original user will be aborted.
To replace the user at a locked client:

1. In the LightSoft Unlock dialog box at the locked client station, enter the
new user name and password.
2. Click Login. LightSoft checks for certain active processes initiated by the
original user.

3. At the conclusion of the processing, one of the following occurs:

If no active processes are detected, a dialog box opens.
OR
If active processes are found and the new user has Security
Administration permission, a prompt to abort the active processes
opens.
Click Yes to confirm the force logout (and abort the active
processes). After the processing is completed, the LightSoft main
window opens in a new session belonging to the new user.
OR
Click No to postpone the logout (for example, to allow active
processes to complete). The original Unlock dialog box is
redisplayed and the client remains locked with the original user.
OR
If active processes are found but the new user lacks the necessary
permission, a prompt appears.
4. Click OK. The original Unlock dialog box is redisplayed and the client
remains locked with the original user.

Logging Out
To avoid overloading the system, it is important that users log out at the end of
a shift.
Logging out closes the LightSoft main window and GCT windows and aborts
certain active processes (see note below). The Login dialog box opens. After
logging out, you can access LightSoft again by logging in as described in
Logging In, using the same or a different login name.
An authorized user can force another user to log out from a client, for example,
in order to log in a different user to that client. Logout can also occur
automatically following a period of inactivity at the user client station. For
more information, see Forcing a User Logout.
NOTE: Certain active processes running in the LightSoft

client or server cannot continue to run after logout or exit of
the user that initiated them. These active processes include:
Trail bundling; see Bundle Size in Basic Trail Parameters
Pane, and Discover Optical Trails; see Creating Optical Trails
Through Discovery. The Logout and Exit functions notify
you if any processes are still running and allow you to
postpone the Logout or Exit if needed.
To log out from LightSoft:

1. From the LightSoft main menu, select System > Logout , or from the main
toolbar, click the Logout icon. LightSoft checks for any active processes.
At the conclusion of the processing, a dialog box opens, according to

whether or not active processes were found.

2. Click Yes to confirm the logout (and abort certain active processes). The
LightSoft Login dialog box opens.
OR
Click No to postpone the logout (for example, to allow the active processes
to complete). The LightSoft main window remains open.
Exiting LightSoft
Exiting from LightSoft performs all the functions of logging out and closes all
LightSoft windows and internal processes. Subsequent access to LightSoft is as
described in Starting the LightSoft Client.
NOTE: Certain active processes - operations, running in the

LightSoft client, server, or both - cannot continue to run after
logout or exit of the user that initiated them. For details of the
active processes, see the note in Logging Out. The Logout
and Exit functions notify you if any processes are still running
and allow you to postpone the Logout or Exit if required.
To exit from LightSoft:

1. From the LightSoft main menu, select System > Exit LightSoft, or from
the main toolbar, click the Exit LightSoft icon.
2. Complete the procedure in the same way as described in Logging Out. (All
dialog boxes will relate to Exit instead of Logout.)
At the last step, all LightSoft windows are closed.

Initial LightSoft Screen

As LightSoft starts, the initial LightSoft screen opens.
This is followed by the LightSoft main window; see Main Window.
NOTE: LightSoft is a client-server application. The server

module is usually started by the system administrator and
should be running continuously. In order to start a LightSoft
client, enter the command provided by your system
administrator at the command prompt.

Working in LightSoft
This section describes the command structures and keyboard features in
LightSoft, and the variety of operations that can be performed in LightSoft
windows.
NOTE: When you log out and log in again (even from a
different workstation), LightSoft automatically remembers
most window size settings. Column configuration changes
may also be saved automatically. See the sections below for
additional information.
CAUTION: As a matter of practice it is not advisable to

close a window while an operation is in progress, as this may
cause the application to malfunction.
Menus and Commands

LightSoft features several types of menus:
Menus and submenus

A menu may have one or more commands that you can select by moving the
mouse pointer over it. When a command is highlighted, click the left mouse
button to select it.
Submenus contain a list of choices related to a menu command. When you
select the menu item, the submenu appears. Select an item from a submenu by
clicking it with the mouse.
Toolbars
Many LightSoft windows feature toolbars for quick one-click access to
commonly used functions (which can also be accessed from submenus or
shortcut menus). Select a function in the toolbar by clicking the icon that
represents it.
Holding the mouse pointer over a toolbar icon for a brief moment opens a
tooltip that describes its function.

Shortcut menus
Shortcut menus contain the most frequently used menu and toolbar options.
They appear by clicking the right mouse button (right-clicking) on objects in
map windows and records in window lists. Select an option in a shortcut menu
by clicking it with the mouse.
NOTE: This manual describes menu and toolbar-based

operations. Shortcut menu commands are only described
when the functions do not exist in menus or toolbars.
Keyboard Options
LightSoft uses an industry-standard keyboard.
Keypad keys
Keypad keys perform standard actions in LightSoft windows. For example, tab
and arrow keys enable moving to the next/previous line in a list table, field in an
entry dialog box, option in a list box, or command in a menu (entities that are not
relevant, such as non-editable fields in an Edit dialog box, are bypassed).
Multiple object selections

You can select multiple objects in a map view by making selections as follows:
| Nonconsecutive objects - hold down the CTRL key while selecting objects.
OR
| Consecutive objects - click the first object, and then click the last while
holding down the SHIFT key.
Keyboard shortcut keys

Keyboard shortcuts are combinations of keys that allow you to access
LightSoft functions from the keyboard. For example, holding down the CTRL
key and pressing the letter A, then releasing both keys selects all objects in a
map view. The following keyboard shortcuts are available.
Keyboard shortcut key combinations
Shortcut Description
CTRL+A Selects all objects in the view.
CTRL+I Inverts the current selections, clearing objects that are currently
selected and selecting those that are not.
CTRL+F6 When multiple windows are open, jumps from window to
window.

Showing and Hiding Window Panes

Traffic Management windows typically contain a map view and grouped
information panes that can be alternately expanded or minimized.
In Tunnel and Services windows, the right-side Details view can alternately be
hidden (expanding the map view) or shown using the Show/Hide Details icon .
In Trail windows, double-clicking in the map view expands the map to fill the
horizontal view area (hiding the information detail panes). Double-clicking
again reinstates the detail panes.
Specific Trail window panes can also be hidden (expanding adjacent panes) or
shown by clicking a triangle icon on a pane border. To reinstate the hidden
panes, click a triangle icon at the map view edges, or drag the edge inwards.
You can also expand a hidden Trail pane by dragging. (Any window pane
border can be adjusted by dragging.)
The following pictures shows the Trail List window with the map view
alternately in the default sizing or expanded. The triangle icons are circled.

Showing, Hiding, and Auto-Fitting Columns

In list windows, a basic set of columns appears in a table as default, while other
columns can be added or removed. In this way, you can display the fields that
you use most often and hide others from view, creating a cleaner and simpler
display. The data in hidden columns is still maintained by LightSoft.
Column widths can automatically be set for all columns at once to fit each
column's widest text content. A horizontal scroll bar appears if the columns
exceed the table width.
All the changes are automatically saved per window type and user when the
window is closed.
For information about manual changes to column widths and column positions,
see Resizing List Columns and Moving Columns in Tables.
To change the column configuration of a Fault list window:
1. In a list window, click the Configure Columns icon in the top-right

corner of the table. The Configure Columns selection panel opens.
NOTE: In some cases, a Select Column icon is used

instead, which leads to a slightly different functionality. For
details, see the alternative procedure at the end of this section.
2. Select the checkboxes of the non-default columns that you want to show in
the table, and/or clear those that you want hidden. You can use the Select
All or Clear All icons to select/clear all the checkboxes.
(Enabled checkboxes represent non-default parameters which you can
optionally include or exclude from the table. The grayed checkboxes
represent default columns which are always present in the table.)
3. Click the Fit Column Width to Text icon to expand or shrink all the
columns to fit their widest contents.
4. Close the Configure Columns selection panel by clicking the Configure
Columns icon again.

The buttons described below affect the window contents immediately upon
selection, and are saved automatically from session to session.
The column widths do not dynamically adjust for new notifications or
subsequent table changes. The Fit Column Width to Text icon must be
clicked again.
Column Configuration dialog box icons
Icon Name Description

Fit Column Expands or shrinks each column to fit its longest
Width to Text content.
If columns extend beyond the screen, a scroll bar is
added.
If there are few columns and empty space would
result on the ri3ght side of the table, column widths
are expanded proportionately to fill the entire table
width.
This behavior does not operate automatically for
additional table changes. If a change occurs,
whether automatic (a new alarm arrival) or manual
(a column adjusted or a new column added), you
must click the icon again to realign the column
widths.
Select All Selects all the checkboxes at once.
Select None Clears all the checkboxes at once.

Select column icon in some windows

In some tables, a Select Column icon is used instead of the Configure
Columns icon . This leads to a slightly different functionality. In this case,
changes to the column display (as well as manual adjustments to column
widths) are preserved from session to session only if specifically saved.
To select which columns to show/hide:

1. In a list window, click the Select Column icon in the top-right corner
of the table. The Select Column dialog box opens showing the available
columns for that list.
2. Select the checkboxes of columns that you want shown in the list window,
or clear those you want to hide.
3. Click Set to apply the change to the current session. (Click Cancel if you
do not want to apply the changes.) The dialog box closes.
4. If you want the currently displayed columns to automatically apply to
future sessions, reopen the Select Column dialog box and click Save, then
click Close (top right) to close the dialog box. (This action additionally
preserves any changes that were made to column widths.)

Resizing List Columns

The columns in a list can be resized manually. When a column is resized, its
adjacent columns are moved sideways.
You can also automatically set all columns to fit their widest content; see
Showing, Hiding, and Auto-Fitting Columns.
To resize a column:
1. Move the mouse pointer over the border between column headings. The
pointer changes into a right-facing arrow.
2. Click and drag the column border to the required width and release the
mouse button.
If the window includes a Configure Columns icon , the manually
changed column widths are automatically saved.
NOTE: If the window includes a Select Column icon ,

you can save the changes as follows:
1. Click the Set Column icon to open the Select Column
dialog box.
2. Click Save.
3. Click Close or (top right) to close that dialog box.

Sorting List Lines

In most list windows you can sort the rows by one or more columns. When the
first column that you sort by (primary sort column) contains several lines that
are the same (for example, the ME Name column in a Current Alarms
window may have many instances of the same ME name), you may want to
sort those rows by a second column, for example, Severity. The table rows will
then be sorted by ME Name and then by Severity. Similarly, you can sort by a
third level, and so on. Any number of nested sort levels is allowed. The
indicated sorting is saved automatically from session to session.
In list windows that allow sorting, columns can also be moved relative to each
other by dragging; see Moving Columns in Tables.
To sort a list in a list window:

1. Click and release the required column's header. The column's list is sorted
in ascending or descending order. An indicator in the column header shows
the direction of the sort (ascending or descending).
2. If you want to perform a secondary column sort, press CTRL while clicking
and releasing the second column. A "2" appears in the column header along
with the sort direction arrow, indicating that this is the secondary sort
column. The rows are now sorted by the primary and secondary columns.
3. Repeat the last step to perform as many sorts as required.
The following is an example list table showing three-level sorting.

Justifying the Column Contents

In list windows that allow sorting - see Sorting List Lines – a column's contents
can be left-justified, right-justified, or centered. The revised column
justifications are saved from session to session.
To justify columns in a table:

1. Right-click a column header. The Justification dropdown list opens.
2. Click the desired justification – left, right, or center. The column contents
are justified accordingly.
Moving Columns in Tables

In list windows that allow sorting - see Sorting List Lines - columns can also be
moved relative to each other by dragging. The revised column positions are
saved from session to session.
To move columns in a table:

| Click a column header, drag it to a new position, and release to drop it in
that position.

Paginating List Windows

Some list windows with many records have a Preferences menu option or
Preferences icon that enables you to divide the records into pages. You
can then navigate the pages using the scroll icons at the bottom of the window.
(The scroll icons only appear if the number of records in the list exceeds the
selected records per page.)
To set pagination preferences:

1. In the list window, select Current Alarms (or applicable alternative) >
Preferences, or click the Preferences icon . A Preferences dialog box
opens.
2. Select the Divide Table to Pages checkbox.

3. From the Maximum Number of Rows per Page dropdown list, select the
desired number of rows per page. You can also enter a number.
4. Click OK. Scroll icons appear in the bottom-right corner of the window,
enabling you to page through the records.
Customizing Time Formats

The default date/time presentation format in LightSoft is:
dd/mm/yyyy HH:MM:SS
The format can be changed globally for your installation by changing a system
file. Contact ECI Telecom customer support for assistance.

Customizing LightSoft Object Colors

Some LightSoft windows present results with color coding. For example, in
map windows, alarm statuses of objects and links are color coded according to
the fault severity that they involve, or in the Availability Map window, links
are color coded according to the available capacity for new trails.
The color coding is often customizable on a per-user basis via a standard color
palette panel.
To customize the colors of user-customizable entities:

1. Open the color preferences window relevant for the feature you want to
customize. For example, see Customizing Fault Color Coding, or
Modifying Availability Preferences. The following are example dialog
boxes. Objects in windows like this are associated with color swatches that
have system default colors, which can be customized on a per-user basis.

2. To customize an object's color, click its color swatch.
NOTE: Only objects having a color swatch that includes a

More button to the right of the color are customizable (for
example, opposite the "Critical" object). The
color swatches without the More button are not customizable
(for example, opposite the "Connected" object).
A color selection panel opens, from which you can select a predefined color
for that status.
3. Click a color in the color selection panel.

OR
Click the More icon at the bottom of the panel to open an advanced
color selection panel.
Select a color by clicking a point inside the color wheel.

OR
Define a specific color by entering its HSB or RGB coordinates in the
fields provided.
The panel closes, and the object's color swatch is assigned the selected
color.
4. Save the color selection as described in the originating procedure, for
example, Customizing Fault Color Coding, or Modifying Availability
Preferences.

Printing and Exporting to File

You can print window lists and map views and export information via menus
and toolbars in many LightSoft windows. (Not all options are available from
every window.)
Print, print format, and export functionality
Menu Icon Description

command
Print Prints the current list or map to any Postscript network
printer or Postscript-formatted files. You can use any
page setup, printer, and appearance settings. (The
shortcut Print option is generally used for printing map
views.) For more information, see Printing.
Export to Exports the list data in a delimited format file, such as
CSV comma-separated values (CSV), for import to Microsoft
Excel or a relational database application. For more
information, see Exporting to CSV.
NOTE: Install and configure the local printer as the default

printer according to the operating system on your
workstation.
Printing
The Print option prints the current list or map view to any network printer.
The dialog box is described in detail in Print Dialog Box.
The print output format varies according to the application context; see Print
Formats.
To print a list or map view to a printer or to file:

1. If you are printing:
A table application (such as a Fault window list), on the Print menu
select Print, or click the Print icon .
Any map view, right-click in the map view and select the Print shortcut
option.
Trail List information content, select the required trails in the Trails
pane and click the Print icon .
Other window information such as a Security dialog box, click the
Print button.

2. If you are printing Trail List window information content, a dialog box
opens.
Select the desired format - List or Details. The Print dialog box opens; see
Print Dialog Box. Complete the information in each pane or tab.
3. Click Print. Printing starts and the dialog box closes.
OR
If you are printing to a Postscript file (you selected the Print to File
checkbox), the Print to File dialog box opens.
NOTE: For a technical reason, at least one printer must be

configured in your station before a file can be created (not
necessarily related to the desired file type).
Select where you want to save the file:

Look in: Select the subdirectory where you want to save the file.
File name: Enter a file name with the extension "ps" (for Postscript).
Files of Type: Leave the selection as All Files.
Click OK to print to file and close the dialog box.

Print Dialog Box

The Print dialog box contains a preview pane (on the right), a configuration
area (on the left), and a toolbar. The print configuration settings defined in the
panels are saved per user from session to session.
The Print dialog box panes, configuration options, and buttons are described in
the sections that follow.
Print Preview Pane

The Print Preview pane can show up to six pages of the printed output. The
toolbar allows you to zoom in or out using buttons or selecting a zoom ratio
from the dropdown list. Pages are laid out according to the available space in
the preview.
The Refresh button reflects any change in print settings on the preview. A
progress bar shows the progress of generating a preview.

Print Configuration
The Printer and Page Setup panes are common to all print requests.
Additional panes are application-specific. The Table Settings pane appears
when a window table is being printed.
Print configuration options
Option Description
Printer
Name Name of the network printer. The information that
appears below the Name field applies to the selected
printer.
Number of Copies Select the number of copies, max. 1000.
Print to File Only Select this checkbox to print to a Postscript (ps) file,
which you can read using a Postscript viewer (not a
text editor).
Page Setup
Orientation Position of the document on the page. Portrait prints
vertically, landscape prints horizontally.
Paper Size Choice of standard paper sizes.
Margins Default 2.54 cm on each dimension; can be changed as
needed.
Table Settings
Fit Column Width to Shrinks or expands column widths so that all columns
Page are visible within the table. If the table contains many
columns, their contents are word-wrapped. If the table
contains few columns, column widths are expanded
proportionately to fill the entire table width.
Print Row Numbers Prints row numbers as the first column.
Print Horizontal Lines Prints separation lines between the table records.
Print Vertical Lines Prints separation lines between the table columns.
Print dialog box toolbar options
Name Icon Description

Print Sends the print request to the specified printer and
closes the Print dialog box.
Refresh Reflects any changes to print settings in the Preview
pane.
Zoom out Decreases the magnification in the Preview pane.
Zoom in Increases the magnification in the Preview pane.
Zoom ratio 10% to 100%: zooms the view in/out as selected.

selector

Print Formats
The print output format varies according to the application context.
Table Information Windows

| When the selected application includes a table, such as the Fault windows,
selecting Print (from the menu or toolbar) prints the entire table, based on
the currently selected filters.
Map View Windows

| In the LightSoft main window, selecting Print (from main menu, toolbar,
or shortcut menu in the map), prints the map view. The following picture
shows a preview of the map view.
| In other map view windows, the Print shortcut menu option (selected in the
map view) previews and prints the entire screen content, including the map
view and any visible information content.
Map view windows with information content are, for example, the Trail
List or Create Trail window. Map view windows without information
content include, for example, the Availability Map window. The following
picture shows the Print Trail List map view.

| In Traffic List windows (Trail, Tunnel, or Ethernet Service), the Print

menu or toolbar option prints the information content and not the map.
The information can be printed in two formats - List or Details:
List: Prints the information from the Trail List window panes, showing
the visible attributes in the Trails pane for the currently selected trails.
The following shows an example Print List output.
Details: Additionally prints information about the trail endpoints and

resources for each selected trail. The following shows an example Print
Details output.

Exporting to CSV
You can export a window's list data to a delimited-format file for subsequent
import to Microsoft Excel or a relational database application; see Exporting
List Data to CSV.
LightSoft also enables you to export using a script; see Exporting XML Data to CSV.
Exporting List Data to CSV

The Export to CSV option available from various LightSoft windows
exports a window's list data to a delimited-format file for import to Microsoft
Excel or a relational database. Any character can serve as the delimiter. For
example, specifying a comma produces a comma-separated values (CSV) file.
NOTE: For a technical reason, at least one printer must be

configured in your station before a file can be created (not
necessarily related to the desired file type).
To export LightSoft list data to a delimited format file:

1. If you are exporting Traffic List window information content (Trail,
Tunnel, or Ethernet Service), select the required List pane lines (by
highlighting a line or selecting one or more checkboxes). If you are
exporting alarms, you can apply a filter - all the alarms displayed in the
window are exported.
2. Click the Export to CSV icon .
3. (Export Tunnels only) A dialog box opens showing the tunnels that will be
included in the CSV file. Click OK.
4. The Export dialog box opens.

5. Select the directory where you want to save the file.

6. In the Export options area Delimiter field, enter any delimiting character
as the record separator in the output file, for example, a comma ",".
7. Enter the file name in the File name field.
8. Select All Files from the Files of type dropdown list.
9. Click Export to create the delimited file and close the window.
Exporting XML Data to CSV

LightSoft allows you to export trail, tunnel, and service and event log records
to XML format; see, for example, Exporting Trails, and Exporting Excess Log
Records and Periodically Clearing Archives.
LightSoft also enables you to convert XML files to CSV using a script.
To export XML data to CSV format:

1. Ensure that you are in the directory NMSExplog.
2. Run the following script from the UNIX command line (any number of
XML files can be specified):
ParseAlm.pl file_name [file_name] [file_name] >
file_name.csv
ParseAlm.pl (This line prints the CSV file to your UNIX terminal.)
Where:
Expression Description
file_name
XML file name. Any number of XML files can be
specified.
file_name.csv
CSV output file name. All the XML files are
concatenated into a single CSV format file, with a
separation line between each file name.
Root Menu
Root menus are easy-access application menus available in some LightSoft
installations (usually when both LightSoft and EMS(s) are installed in the same
workstation). A root menu is a shortcut menu that provides access to all
relevant utilities and applications running on the server. For more information,
see Root Menus.
3

Object Status Color Coding

On LightSoft maps, the alarm and usability states of objects
(elements/links/trails) are indicated by a color, for example, representing the
severity of the alarm applicable to that object. The object alarm state and color
code is also indicated by parameters in fault management and trail window
tables. The alarm color codes are customizable. For additional information, see
Object Status Color Indications.
GUI Cut-Through (GCT)

LightSoft manages a network through EMSs which provide the information it
needs to maintain the network. Viewing windows from an EMS would normally
require you to log in to the EMS on the local terminal and find the information
manually. The LightSoft GCT feature enables you to easily and efficiently access
EMS information or perform EMS operations on selected objects without having
to start an individual EMS session. For information about how to open GCT
sessions on objects via LightSoft, see GCT Operations.

About LightSoft Window

You can view information about LightSoft in the About LightSoft window,
such as the currently installed client and server versions and the currently
licensed optional features.
To view the About LightSoft window:

| On the menu bar, select Help > About LightSoft. The About LightSoft
window opens.
About Tab
The About tab shows which client and server versions of LightSoft are
installed (bottom left of screen).
Info Tab
The Info tab shows information of specific software components. It is for the
use of ECI Telecom qualified personnel only.

Optional Features Tab

The Optional Features tab lists the cost options available from LightSoft and
indicates whether they are currently licensed to your installation. Only
functions and menu options of purchased features are activated in the
application.
Optional features are indicated in context throughout this manual.

3
LightSoft User Interface
In this chapter:
Overview ......................................................................................................... 3-1
Main Window .................................................................................................. 3-2
3
Searching and Locating Objects .................................................................... 3-22

3
Messaging in LightSoft ................................................................................. 3-35

3
LightSoft Properties ....................................................................................... 3-44

3
Overview
The LightSoft interface allows you to easily manage complex networks. The
LightSoft main window provides an overall view of the network’s topology
and its elements in a choice of topology views. You can view information
about elements, links, and trails, create network objects, and perform a variety
of operations, as allowed by your security permissions.

LightSoft User Interface LightSoft User Manual
Main Window
When you log in, the LightSoft main window opens. You access all LightSoft
functions from this window. It is the background for all other windows and
dialog boxes, and is always open unless minimized.
NOTE: The profile of the user group of which you are a

member determines the objects that appear in LightSoft views
and the functions you can perform. If an option in a window
or dialog box applies to a function not available to your user
group, the option will be unavailable.
You can open multiple windows simultaneously within the LightSoft main
window comprising different views of the network or subnetworks, with
selected topology groups or objects. Each view can display a different topology
layer independent of other layers, having its own perspective on the network
and allowing different operations. The views can be cascaded or tiled on the
view screen according to your convenience.

LightSoft User Manual LightSoft User Interface
The main window includes a map view, topology tree, and Navigator, which
enable viewing and selection of objects that you want to work with.
The map view provides a graphical representation of the network and its
objects, in terms of the selected topology or technology layer; see Topology
Layers.
The tree and navigator enable locating objects and network areas and changing
the view magnification in map view. For more information, see Topology Tree,
and Advanced Zoom and Scrolling.
Multiple physical monitors

LightSoft can also be configured to use multiple physical monitors (for
example, two or three monitors placed side-by-side, or six monitors in a 2 x 3
array) as one large virtual display - popularly known as Xinerama.

Selecting Objects in the Main Window Views

You must select or find the objects with which you want to work. Menu/toolbar
commands (for example, creating a link) are performed on the highlighted
objects in whichever window (either map or tree) was last selected (with blue
title bar).
Single objects can be selected in the map or tree view by clicking and multiple
objects by using the SHIFT or CTRL keys - see Keyboard Options. Multiple
objects can also be selected in the map view through a scope selection by
clicking and dragging with the mouse to define a rectangle. All the contained
objects will be selected.
Objects selected in the main window map or tree view are automatically
selected in other views (objects cannot be manually selected in the Navigator):
| When you select objects on the map, they are automatically highlighted in
the Navigator but NOT in the tree (any previous highlighting stays intact).
| When you select objects in the tree, they are automatically highlighted in
the map and Navigator (replacing any previous selections).
TIP: To highlight an object on the map but not in the tree,

right-click the object in the tree and select the Select on Map
option on the shortcut menu.
Objects can also be selected using the LightSoft Search feature, which
highlights the searched objects in the main window map and Tree. For more
information about the Search feature and its properties, see Searching and
Locating Objects.

Moving Elements in the Main Window

You can move elements or groups of elements on any topology layer in the
LightSoft main window. Individual LEs in any technology layer can be moved
independently of their physical objects.
To move an element, the main window must be in one of two possible states:
Move Only or Move and Save. The default option when opening new
windows can be set according to your organizational requirements. Contact
ECI Telecom customer support for assistance.
NOTE: Most often, users prefer to see LEs in technology

layers in exactly the same positions as their equivalent
physical layer objects. You can also automatically place LEs
of all or selected MEs/UMEs in all relevant technology layers
in this way; see Setting LE Location. For more information
about MEs, LEs, and UMEs, see Managing Elements and
Groups.
To move an element or group of elements in the LightSoft

main window:
1. On the View menu, select Moving and then Move Only or Move and
Save.
OR
On the toolbar, click the corresponding icon:
Lock - locks the elements so that they cannot be moved.
Move Only - enables you to drag the elements to the new position
but only for the current session.
Move and Save - enables you to drag the elements to the new
position which is saved for future sessions.
2. Click the element and/or select various elements by clicking them while
pressing the SHIFT key, and drag them to the new location.

Menu and Toolbar

You can access all LightSoft functions from the main menu bar at the top of the
window or from the toolbar icons.
For information about each menu command and its corresponding toolbar icon
(if applicable), see Summary of Menu Commands.
3
Customizing the LightSoft Main Toolbar

You can configure the main window toolbar to hide/show sets of icons.
To show/hide icons in the main toolbar:

1. Right-click anywhere in the main window toolbar. A shortcut menu opens.
2. Click the name of a specific icon or category of icons (for example, Maps,
which includes Availability, RSTP, and Timing Map) to show or hide
them in the toolbar. By default, all icons are selected in the shortcut menu.
You can also show/hide the alarm counter bar in the same way. In addition,
specific alarm counters can be shown/hidden as described in Alarm Counter
Bar.

Alarm Counter Bar

Alarm counters are filters that display the number of alarms or TCAs that meet
specified criteria. The results appear in the Counter bar on the LightSoft main
window toolbar.
The Counter bar has the following predefined alarm/TCA counters:

| Critical & Major - total of critical and major faults.
| Minor & Warning - total of minor faults and warnings.
| Disconnected EMS/ME - objects disconnected from LightSoft due to
communication problem between the EMSs and NEs, faults in the current
or another NE, or some LightSoft problem.
You can display user-defined special purpose counters in the Alarm Counter
bar. The name of a counter appears as a tooltip when the mouse is positioned
above the counter. For more information, see Using Alarm Counters.
You can choose which of the defined counters to show in the Counter bar by
right-clicking anywhere between the counters and selecting the counters in the
shortcut menu. (If all counters are hidden, right-click in the counter bar space.)
You can configure whether the Counter bar will appear in the toolbar or not;
see Customizing the LightSoft Main Toolbar.
The sigma (Σ) next to an alarm count denotes that all alarms
(acknowledged and unacknowledged) are counted. Click the counter to show
only unacknowledged alarms. Click again to toggle back to the total count. For
more information, see Acknowledging Notifications.
Double-clicking a counter for a specified severity opens the Current Alarms
window filtered with that counter's alarms; see Viewing Related Current Alarms.
Right-clicking a counter enables you to choose between Current Alarms or
TCA windows and to open a filtered list of that counter's associated records.
For more information, see Accessing Fault Management Windows.

Trail Consistency Indicator (TCI) Flag and

Counter
The Trail Consistency Indicator (TCI) counter shows the number
of trail inconsistencies. The color of the flag indicates the worst inconsistency
condition of the trails in the selected count. For information about the color
correspondences, see TCI Details Pane.
The inconsistencies are counted in terms of all trails or only in SDH + EMS
(including the SDH-based EoS and MoT trails). Clicking the counter toggles
between total and SDH + EMS inconsistency counts. (Optical inconsistencies
are not included in the partial counts as they have lesser impact on traffic
management.)
For the count behavior upon link and trail creation, see Trail Synchronization
Exceptions.
Clicking the TCI icon opens the Trail Consistency Indicator (TCI)
window, where you can view detailed information about trail inconsistencies.
For more information, see Synchronizing Trails.
The counter and icon presence on the toolbar is configurable; see Customizing
3
the LightSoft Main Toolbar.
Tunnel Segment Consistency (TSC) Counter

The Tunnel Segment Consistency (TSC) counter in the main
window toolbar shows the total number of inconsistent tunnel segments. The
color of the count box indicates the worst inconsistency condition of the
tunnels in the count. For information about the color correspondences, see
Severity Breakdown Pane.
Clicking the TSC icon (or the symbol of the counter) opens the
Tunnel Segment Consistency (TSC) window, where you can view detailed
information about tunnel inconsistencies. For more information, see
Synchronizing Tunnels.
The counter's presence on the toolbar is configurable; see Customizing the
3
LightSoft Main Toolbar.

Alarm State Mode

Network objects (NEs, topology links and trails) may experience a variety of
fault conditions leading to multiple alarms. By default, an alarmed object is
color coded in LightSoft map windows and topology trees to reflect the highest
severity of all associated alarms. (Map windows include the LightSoft main
window map and each variation of trail list window, regardless of topology
layer.)
After fault conditions have been acknowledged, you may not wish to be alerted
to the alarmed objects in the same way. (You can assign Acknowledged status
to an alarm or TCA to indicate that it is being handled; see Acknowledging
Notifications.) You can request a different color-coding scheme where all of an
object's faults are unacknowledged. In this way, new faults may be easier to
identify in crowded maps and trees.
An icon in the status bar indicates the currently active alarm state presentation
mode for your user profile; see Status Bar.
Options are:
| Actual (default): Alarmed objects are color coded according to the

highest severity of all associated alarms (whether acknowledged or not).
| Unacknowledged : Alarmed objects are color coded according to their

highest severity of unacknowledged alarms. If all of an object's alarms are
acknowledged, the object is color coded according to a different scheme;
see Customizing Fault Color Coding.
Choosing the Unacknowledged alarm state mode does not affect the color
coding of the individual alarm records listed in fault windows. These continue
to reflect their actual fault status, and alarm counters continue to reflect the
actual numbers of alarms of each severity in the system.
The following procedure enables you to change the alarm state mode directly
from the main window status bar.
OPTIONAL FEATURE: The ability to switch between

alarm state modes is a fully integrated add-on capability,
available on a cost basis. If not purchased, color coding
functions according to the Actual mode.

To change the alarm state mode:

1. Click the alarm state mode icon in the LightSoft main window status bar,
or . A popup menu opens.
2. Click the required mode. The conversion may take a few seconds. While
converting, the icon flashes. The new mode is immediately reflected in map
windows. It is saved in your user profile and is constant until changed.
You can also change the alarm state mode using the Fault Management
Preferences dialog box; see Changing the Alarm State Mode. This dialog box
also enables changing the colors associated with alarm severities, including
those associated with unacknowledged alarms; see Customizing Fault Color
Coding.

Advanced Zoom and Scrolling

You can magnify or reduce (zoom) LightSoft window map views, or scroll to
show objects of current interest, according to the detail that you want to view at
any time. These actions are performed either directly in any the map view or
using the Navigation window.
Advanced Zoom
You can magnify or reduce LightSoft window map views according to the
detail that you want to see. NE icons generally retain their size regardless of
magnification. NEs associated with local rings are painted in according to the
current magnification; see Zoom Behavior of Local Rings.
To magnify or contract the view:

1. Select a topology view.
2. To alternately decrease or increase the magnification, showing less or more
of the topology in the view, respectively:
Roll the mouse wheel up or down while holding the Ctrl key.
OR
Select the Zoom Out and Zoom In icons on the main

window toolbar.
These icons are also available from the Navigator window; see
Navigator Window.
You can also select a specific magnification from 25% to 800%
through the File > Zoom main menu option.
Use the Fit to View icon, accessed by selecting File > Zoom from
the LightSoft main menu, to fit all NEs of the current topology into the
active view at 100% magnification. This icon is also available from the
Navigator window; see Navigator Window.
OR
In the Navigator window, click and drag the corners of the View
indicator; see Navigator Window.

Zoom Behavior of Local Rings

To facilitate viewing in larger networks and improved performance, when NEs
are in “islands” of connected nodes:
| NEs and associated links are omitted from the view at lower zoom
magnifications. A “cloud” makes it easy to spot islands of connected nodes.
| As the magnification is increased, NEs and associated links are gradually
painted in, increasing in size with the zoom magnification.
NOTES:
Painting in of ring objects according to zoom is automatic and
generally does not require identification of ring objects by the
user. An exception is if the ring is straddled by not-logically-
related links (crossing from one side of the ring to the other).
In this case, the adjacent NEs may not resize uniformly with
other NEs as the zoom changes.
This is overcome by specifying a (same) ring name in the

properties of each logically-related link; see Ring Name
parameter in Properties for Link General Tab. In this way, the
straddling links will not affect the ring sizing algorithm and
the ring’s logically-related NEs will be painted in uniformly.
Painting in of ring objects according to zoom may not be
useful in less complex networks and can be turned off,
enabling all objects to be visible at all times in the same size.
For details, contact ECI Telecom customer support.

Scrolling the Map View

You can scroll the map view with the mouse to show objects of current interest.
To scroll the map view:

| Click the center mouse button while holding down the Ctrl key and drag in
any direction until the objects of interest are centered in the view.
OR
| Click and drag within the Navigator window View indicator; see
Navigator Window. The objects currently framed in the View indicator
become the current focus of the map view.
Navigator Window
The Navigator window, a small floating window by default in the lower left
corner of the Map view, provides additional ways to change the zoom and
current focus of objects in map window views.
The Navigator window shows the entire map of the currently selected network
topology. The View indicator (white box within the window) indicates the
current focus of the map view.
The window is permanently shown or hidden by the procedure below. When
selected to be “shown”, it can become temporarily hidden if another window is the
current focus. In this case, it is shown again by clicking anywhere in the map view.
To alternately show/hide the Navigator:
1. On the toolbar, click the Navigator icon.

OR
On the LightSoft main window menu bar, select View > Display > Navigator.
The Navigator becomes shown/hidden for the duration of the session.
2. When the Navigator window was selected to be “shown”, it becomes
temporarily hidden when another window is the current focus. In that case,
click anywhere in the map view to redisplay the window.

To zoom and scroll using the Navigator:

| Change the magnification in the map view by dragging in/out on the View
indicator box corners, or using:
Zoom Out to reduce the magnification.
Zoom In to increase the magnification.
Fit to View to reset the magnification to 100%.

| Change the current focus of the view by clicking within the View indicator
and dragging in any direction. The objects currently framed in the View
indicator become the current focus of the map view.

Topology Tree
The Topology Tree displays MEs/LEs and groups displayed on the map in a
clear hierarchical view of the network's physical structure. It also displays the
cards and ports in the MEs and LEs. The structure displayed in the Topology
Tree corresponds to the currently selected topology layer. For more
information, see Topology Layers.
Icons distinguish MPLS , PB , and EA-HVPLS network types.

Each LE type is represented by its own icon; see LE Icons and Direction
Representations.
Port types are represented by the following icons:
PDH
SDH
OTN aggregate
OTN tributary
Data port with UNI interface
Data port with I-NNI or E-NNI interface
All other data ports

To show/hide the Topology Tree:

| On the main window toolbar, click .
OR
On the main window menu bar, select View > Display > Tree.
Each object in the Topology Tree (except the root object) can be expanded or
collapsed. Click the Expand icon or double-click the object to expand it and
view its contents; click the Collapse icon or double-click the object to
collapse it.
The square box above a node (for example, ) indicates the object
status. The box color indicates the object’s usability state or alarm severity. If
the node is a parent, the box color indicates the most severe status of the nodes
contained by it. For more information, see Object Status Color Indications.
Object Selections and the Topology Tree

Objects selected in the tree are automatically highlighted in the map (replacing
any previous selections).
TIP: To highlight an object on the map but not in the tree,

right-click the object in the tree and select Select on Map on
the shortcut menu.
Objects selected in the main map are not highlighted in the tree (any previous
highlighting in the tree stays intact).
Menu/toolbar commands (for example, creating a link) are performed on the
highlighted objects in the window (either tree or map) last selected (has blue
title bar).
The Search feature allows you to search for objects in LightSoft. The found
objects are selected in all the main window views. For more details, see
Searching and Locating Objects.
Status Bar
The status bar at the bottom of the LightSoft window shows the current date/time.
The or icon to the left of the date indicates the alarm state presentation
mode that is currently in effect, showing alarm severity color coding in map
windows for all alarmed objects or only those that are unacknowledged.
Clicking the icon opens a selector that enables you to change the active mode.
For more information, see Alarm State Mode.

Topology Layers
Telecom networks typically comprise different types of MEs, some with cards
for different networking technologies. For example, a single ME may have
SDH and optical transmission cards. Therefore, the ME may occupy different
functional views of the network and separate but related network sections.
The LightSoft main window provides a view of the network according to the
selected topology layer:
| The Physical (Site) layer shows all the elements in the network as they are
deployed. Each ME is shown in its actual location in relation to other MEs.
Each element is represented by an icon, and topology links between the
elements are represented by lines. Multiple views of the physical topology
can be displayed at one time.
| Similarly, the Physical (EMS) layer allows you to view the physical
network from the management hierarchy point of view, showing how
elements are managed by the different EMSs.
| SDH, optical, or ETH/MPLS technology layers represent how the resources
of the network are actually used based on functional points of reference -
only the network aspects relevant to the specific technology are displayed.
For example, in the optical layer, only elements providing optical
functionality are presented along with their specifically associated links.
Each topology layer contains its own alarm indicators, enabling fault
management of each technology in the network. Elements in any view can be
moved as required.
OPTIONAL FEATURE: The SDH, optical, and

ETH/MPLS layer functionalities are fully integrated add-on
capabilities, available on a cost basis. If not purchased, the
functionality and related menu options are disabled.
NOTE: Mapping of ports to layers is not supported for

SYNCOM or Luminet equipment.

Selecting a Topology Layer

By default, the LightSoft main window provides a view of the network
according to the Physical (Site) layer, which shows all the elements in the
network as they are deployed. A different topology layer can subsequently be
displayed.
To select a topology layer:

| On the main window toolbar, select a topology view from the Topology
Layer dropdown list.
OR
On the View menu, select Layers and then the layer you want to view.
Supported Topology Layers

LightSoft supports the following topology layers:
Physical (Site)
This layer displays the network infrastructure, that is, the physical topology of
the MEs (for example, XDM and SYNCOM) and ME groups (if defined) in the
network, and the physical connections between them. You can use the Physical
(Site) layer to add, configure, and delete MEs, and to define connections
between them.
Physical (EMS)
This layer displays the network's hierarchy from a management viewpoint,
according to existing EMSs. You can use the Physical (EMS) layer to add,
configure, and delete EMSs.
While working in the EMS layer, you can show or hide unmanaged elements
(UMEs) from the view. To do this, from the LightSoft main window, select the
View > Show UMEs toggle option.
Optical (Optical Transport Network, OTN)

This layer displays all optical LEs in the network. It contains nodes that
represent logical elements of the optical layer. Links in this layer reflect
physical connections between elements. Optical trails are acquired (created)
and monitored from this layer. For more information, see Provisioning Optical
Trails.

SDH
This layer displays all SDH LEs and groups of LEs in the network. Links in
this layer reflect physical connections between elements.
The SDH view also enables you to define SDH trails. For more information,
see Provisioning SDH and EoS Trails.
SDH Server Trails

This layer allows the CNM user to view the high order VC-4 server trail
topology as virtual links. It allows a meaningful view of the SDH topology
used by low order traffic, representing the logical connectivity of the high order
VC-4 network.
The virtual links displayed are in accordance with the user's CNM resource
permissions; see VPNs and CNMs and CNM and Trail Provisioning. Flex and
incomplete/inconsistent high order trails, which cannot be servers to low order
trails, are not represented.
ETH/MPLS
This layer displays LEs representing Ethernet bridges and MPLS PEs (Layer 2
switches), and all Ethernet transport elements (Layer 1 EoS ports). Links in this
layer reflect physical connections between elements. The ETH/MPLS layer
also enables you to view Ethernet and MPLS services; see Provisioning
Ethernet Services, and define EoS trails; see Provisioning SDH and EoS/MoT
Trails.

Relationship Between Physical and

Technology Layers
The following diagram shows how physical elements are represented in their
own technology layer in a client-server architecture.

Virtual Links - Connecting Technology

Layers
LightSoft automatically recognizes the relationships between layers. The
displayed layer shows its own objects and links, as well as "virtual" link
representations of trails from an underlying technological layer. For more
information about virtual links, see Physical Links and Virtual Links.
Logical Elements (LEs)

Elements in a technology layer are referred to as LEs. They are distinct from
physical elements in the Physical views. One primary LE is automatically
created in each technology layer relevant to that NE, comprising all the ports
pertaining to that layer.
Each technology layer also displays secondary LEs, representing granular
functionality that you have split out from the primary LEs. For example, an LE
representing an ADM can be split into its ports. For more information, see
Working with LEs.
Groups
Selected elements on any layer (physical or logical) can be grouped into a
single icon that may be expanded into its components at any time. Groups may
be nested (groups of groups) to any level. Groups and group hierarchies can be
independently defined in each layer. For more information, see Working with
Groups.

Searching and Locating Objects

The Search entry panel in the main menu toolbar enables you to search individual
objects (MEs, LEs, and UMEs) or groups or locate bookmarked objects throughout
any currently open map view, whether in the main window map, or any Create
traffic entity or List window map.
The object found by a search is marked in the current window map and
topology tree. (The found object will also be the current focus in the map
window if the applicable configuration option was selected; see Configuring
the Search.)
NOTE:
The topology tree does not have to be open during a search.
The search is performed independently of the tree.
If an object is currently selected in the tree, the search starts
from that point and continues down/up the tree according to
the configured search behavior; see Configuring the Search.
After the search reaches an extremity of the tree, it wraps
around and continues to search the remaining objects.
The Navigator window, if open, does not mark the found
object, but shows it as the current focus if the applicable
configuration option was selected. For more information
about Navigator window features, see Navigator Window.
The search can be configured in the following ways; see Configuring the Search:
| Mark only the currently found object, or also all previously found objects.
| Center the view on the found object, or leave the current focus unchanged.
| When objects are searched that are within a currently contracted group,
expand the group to show the found object vs. just mark the group icon.
| When a group being searched is currently expanded, mark its components
vs. contract and mark the group icon.

A temporary bookmark (valid until logout) is automatically created in the

bookmark from the Bookmarks panel list for each searched object. The
associated objects can then be conveniently located by selecting the bookmark
instead of conducting a new search.
A temporary bookmark can be made permanent, available for use in future
sessions. Permanent bookmarks can be assigned a sharing type - private or
public (group or all users), enabling them to be used or modified by authorized
users. For more information, see Using Bookmarks.
Search Procedure
NOTE:
Back and Forward icons on the main toolbar can be
used to revert to the map positions corresponding to:
Earlier- or later-found object views, or
The view before or after Fit to View was last

selected.
Since Back and Forward refer to map positions rather than the
objects themselves, the objects may not be visible if they
were moved subsequent to being found.
To search or locate an ME/LE/UME or group:

1. Click anywhere inside any view map to make it the current focus.
2. If you know that the object you want is bookmarked (you already searched
the object during the current session, or you applied a bookmark to it; see
Using Bookmarks), click the down arrow on the Search entry panel.
The Bookmarks panel opens showing all existing bookmarks.
OR
Enter a text string (partial or exact match) in the Search entry field.
As you type, if bookmarks exist whose names include the partial string text,
the Bookmarks panel opens showing all relevant bookmarks.

a. Click the required bookmark from the list.

OR
b. Continue entering text for a closer match. When you are finished the
specification, click the Find icon.
Objects that satisfy your search criteria are located.
NOTE: The Search Configuration panel defines the

specific behavior of the search; see Configuring the Search.
3. When an object that satisfies the criteria is located, it is highlighted in both

the map view area and the tree view.
If a search is initiated using the Find icon rather than a bookmark

selection:
If no object is located, an "Object Not Found" message opens and the
search is terminated. Click OK to close the message.
Adjust the search string and click Find again, or erase the string to
discontinue the search.
If more objects are available that would satisfy the search criteria, the
Find icon changes to a Find Next icon. Click this to find the next
object that satisfies the search result.

Objects are found in their order of appearance in the tree view.

Repeat this step until no more objects match your criteria. Then, an
"Object Not Found" message appears and the search is terminated.
Click OK to close the message.
At any point, if you do not want to locate more objects, click anywhere
in the map view to discontinue the process. The search string is erased
and the Find icon is disabled until the next time a search string is
entered.
Search Entry Field and Icons

The Search entry field and icons in the main menu toolbar are used to search or
locate individual objects (MEs, LEs, and UMEs) or groups in the topology.
Search entry field and icons
Field/Icon Description
Search entry input area. Enter the name of the object you
want to find. You can enter either a partial string of
characters or an exact match. For example, entering E-7 will
find objects such as NE-72 or uNE-74. As you type the
search string, if matches are found amongst existing
bookmarked objects, a list of the relevant bookmarks
appears, from which you can choose; see Using Bookmarks.
Searches are not case sensitive.
Down arrow. Opens the following panels, according to
context:
| If the current search string matches characters in
existing bookmarks, opens the Bookmarks panel,
enabling you to locate a selected bookmarked object;
see Using Bookmarks.
| If no search string was entered yet, or the current string
does not match existing bookmarks, opens the Search
Configuration panel, enabling you to configure the
search behavior; see Configuring the Search.
Find icon, which starts the search. It is enabled when
something is typed to the Search entry field.
This becomes a Find Next icon after an object is

found and more objects exist that would satisfy the search
criteria.

Other Search related icons on the main menu bar
Field/Icon Description
Back and Forward: Reinstates a previously found object's view
and zoom map position, reverting to:
| Earlier- or later-found object views, or
| The view before or after Fit to View was last selected.

Since Back and Forward refer to map positions rather than the
objects themselves, the objects may not be visible if they were
moved subsequent to being found.
Create Bookmark: Applies a permanent bookmark to objects
selected in the map view; see Creating Permanent Bookmarks.
Configuring the Search

You can control how a search is performed:
| Search for nodes, or groups, or both.
| Search direction and whether a partial string (default) or exact match applies.
You can also configure what appears in the current view when an object is
found:
| Mark only the currently found object (default) vs. keep previous selections
marked as additional objects are found.
| Automatically shift the view to make the currently found object the central
focus (default), or leave the found object’s position in the view unchanged.
| If a searched object is part of a collapsed group, automatically expand the
group to show the object (default), vs. just mark the collapsed group icon
without disturbing the existing mapping pattern.
| If the searched object is a group that is expanded, just mark the group's
contained objects (default) to avoid disturbing the existing mapping pattern
vs. collapse the group and mark the group icon.
To open the Search Configuration panel:
1. Click the down arrow on the Search entry panel.

If no search string was typed yet, or the current string does not match
characters in existing bookmarks, the Search Configuration panel
opens.
OR

a. If the current search string matches characters of existing bookmarks,

the Bookmarks panel opens; see Using Bookmarks.
b. Click the Search Configuration toggle icon at the bottom

of the panel. The Search Configuration panel opens.
2. Set the required configuration selections – see the table below.

3. Click anywhere in the map view to close the panel.
Search Configuration panel components
Field Description
Find Objects Narrows your search by specifying the type of object you want to
of Type find: Nodes (ME/LE/UME) (default), or Groups, or both. At least
one must be selected.
Search Direction of appearance in the topology tree in which objects will
Behavior be searched.
If no object is selected in the tree, the search starts from the top or
bottom of the tree (selections Down or Up, respectively).
If an object is currently selected in the tree, the search starts from
that point and continues Down or Up the tree according to the
selection. After the search reaches an extremity of the tree, it wraps
around and continues to search the remaining objects.
The topology tree does not have to be open during a search.
Use Exact Select this checkbox if you are entering an exact name in the Find
Match field - you do not want a partial string search.
Searches are not case sensitive.

Field Description
When an | Expand to object if necessary: If selected (default)
object is automatically expands a collapsed group to show a found
found object. (The group remains expanded.) Otherwise, only the
group icon is marked.
| Collapse to object if necessary: If selected, if the searched
object is an expanded group, automatically collapses and marks
the group icon. Otherwise, the group's component objects are
marked (automatically fit within the rectangle) without
disturbing the existing mapping pattern, as shown in the picture
below (default). In either case, in the Tree view, only the group
level is marked.
| Zoom view to found objects: If selected (default), the view

automatically shifts so that the currently found object is
centered in the view. Otherwise, the found object's position in
the view is unchanged.
| Add object to selection: If selected, previously found
selections stay marked as additional objects are found.
Otherwise, only the currently found object is marked (default).
Configuration-Bookmark toggle icons, showing the Search
Configuration panel is currently open.
Clicking the Bookmarks icon opens the Bookmarks panel;


Using Bookmarks
The Bookmarks panel enables you to locate objects associated with a
bookmark by selecting the bookmark instead of initiating a new search.
To locate bookmarked objects:
1. Click the down arrow on the Search entry panel.

OR
If the Search Configuration panel is displayed, click the Bookmark
toggle icon at the bottom of the panel. The Bookmarks panel

opens.
2. Click an entry in the list. The associated objects are marked in the view.
NOTE: If the bookmarked objects are not currently

displayed (they are beyond the view limits based on the
current view magnification), the following message is
displayed:
Some objects do not exist in the current view. Add objects
to view?
Select Yes to apply the bookmark. A “fit-to-view” is
automatically performed so that the bookmarked objects
are included in the view.
If you select No, the bookmarked objects are not marked.
The current map view remains unchanged.

Bookmarks panel components
Field Description
Status Shows the temporary-permanent status of a listed bookmark:
column | Empty cell: Denotes a temporary bookmark, created
automatically by a current find operation. Temporary
bookmarks are automatically removed upon logout.
| Permanent Bookmark symbol: Denotes a user-created

permanent bookmark; see Creating Permanent Bookmarks. The
bookmark remains on the object from session to session, until it
is manually removed; see Deleting Bookmarks.
Objects Lists names of bookmarks, by default the names of the single
column objects to which they apply. When the bookmark relates to multiple
objects, the name is user assigned in the Create Bookmark or Edit
Bookmark dialog box; see Creating Permanent Bookmarks or
Editing Permanent Bookmarks.
Sharing Indicates the sharing type assigned to the bookmark:
Types | Private (no symbol): Bookmark is usable/modifiable by the
column user who created it (or who modified the bookmark to be
Private).
| User Group : Bookmark is usable/modifiable by any user

in the user group of either the bookmark’s creator (or the user
who modified the bookmark to be User Group).
| Public : Bookmark is usable/modifiable by any LightSoft

user.
Configuration – Bookmark toggle icons, showing the
Bookmarks panel is currently open.
Clicking the Search Configuration icon opens the Search

Configuration panel; see Configuring the Search.

Creating Permanent Bookmarks

A temporary bookmark is automatically created in the Bookmarks panel for
each object that is searched during the current session. Temporary bookmarks
are available in the list only during the current session and are automatically
removed upon logout.
Permanent bookmarks have the following features that are not available from
temporary bookmarks:
| Remain available from session to session, removable only manually by an
authorized user.
| Sharable with other users (for use or modification) based on the assigned
sharing type – Public, User Group, or Private; see Using Bookmarks.
| Associated with single or multiple objects.
| Same or different name from associated object, with optional description.
| Can be opened in a new view; see Opening Bookmarked Objects in a New
View.
Permanent bookmarks are created in the following ways:
| A temporary bookmark can be turned into a permanent bookmark.
| A permanent bookmark can be created directly, attached to one or more
selected objects.
To associate a permanent bookmark to objects:

1. Create the bookmark:
a. Change a temporary bookmark to permanent.
In the Bookmarks panel:
Click the empty Status cell to the left of a temporary bookmark's
name.
OR
Right-click anywhere in the bookmark line and select Store
Bookmark.
A Permanent Bookmark symbol appears opposite the name.

OR

b. Create a new permanent bookmark.

In the current window map view, select one or more objects in the
current map view and click the Create Bookmark icon in the
main window toolbar.
TIP: Multiple objects can also be selected for this purpose as

a result of a search. In this case, select the Add objects to
selection checkbox in the Search Configuration panel so
that multiple objects remain marked; see Configuring the
Search.
2. Open the Edit Bookmark dialog box.

a. If a temporary bookmark was changed to permanent:
In the Bookmarks panel:
Right-click the Status cell of a bookmark and select Edit Bookmark.
OR
Click the Permanent Bookmark symbol in the status cell.

The Edit Bookmark dialog box opens.
b. If the bookmark is being created using Create Bookmark , the

Create Bookmark dialog box opens automatically.
3. Modify the bookmark properties if required:

Name:
If the bookmark relates to a single object, the name is by default the
same as the object name. You can change the name if required.
If multiple objects were selected, the name field is initially blank.
Enter a name for the bookmark.

NOTE:
The name of a bookmark must be unique. If a bookmark
already exists for the object with the same name, you are
prompted whether you want to Cancel the action or
Overwrite the existing bookmark.
If multiple bookmarks need to be defined on the same object,
for example with different Search Configuration settings,
different names should be specified.
The bookmark properties can be revisited; see Editing
Permanent Bookmarks.
Description: Free text description of the bookmark can be entered

(optional).
Sharing Type: Bookmarks can be shared with other users based on
their assigned sharing type - Private (default), User Group, or Public;
NOTE: The bookmark’s sharing type can be modified by

any user with access rights. If the bookmark is modified to
have a more restrictive sharing type (down to User Group or
Private, you are notified about the implications to other users.
4. Click OK. A new permanent bookmark is listed in the Bookmarks panel

with a Permanent Bookmark symbol in its Status cell.
NOTE: The bookmark properties can be revisited; see

Editing Permanent Bookmarks.

Create or Edit Bookmark dialog box fields
Field Description
Bookmark If a single object was selected, the bookmark's name is the same as
Name its selected object (default). You can change the name if required.
The name of the bookmark must be unique.
If multiple objects were selected, the name is user-defined.
Description Free text description of the bookmark (optional).
Sharing Indicates the sharing type assigned to the bookmark - Private (no
symbol), User Group , or Public . See the sharing type

descriptions in Using Bookmarks.
Editing Permanent Bookmarks

The Edit Bookmark dialog box is used to view or change a permanent
bookmark's properties, which were originally defined upon bookmark creation;
see Creating Permanent Bookmarks. The dialog box content is the same as in
the Create Bookmark dialog box.
To edit a bookmark's properties:

| In the Bookmarks panel:
Right-click the Status cell of a bookmark and select Edit Bookmark.
OR
Click the Permanent Bookmark symbol in the status cell. The

Edit Bookmark dialog box opens. It has the same fields and is used in
the same way as the Create Bookmark dialog box; see Creating
Permanent Bookmarks.
Deleting Bookmarks
Bookmarks, temporary or permanent, can be deleted at any time.
To delete a bookmark:
| In the Bookmarks panel, anywhere on a bookmark line, right-click and
select Delete Bookmark.

Opening Bookmarked Objects in a New View

A bookmark's associated objects are opened by default in the current view by
clicking the bookmark in the Bookmarks panel. As well, a permanent
bookmark's objects can be opened in a new view as described below.
To open bookmarked objects in a new view:

| In the Bookmarks panel, anywhere on a permanent bookmark line, right-
click and select Open in New View.
Messaging in LightSoft
LightSoft provides a variety of ways to convey information, whether to other
users or as reminders to yourself. LightSoft enables you to:
| Post messages to LightSoft users on a bulletin board; see Posting Messages
to a Bulletin Board.
| Send messages to logged-in users; see Sending Messages to Logged-In
Users.
| Attach comments to other users within notifications in the Fault
Management system; see Viewing and Attaching Notes on Fault
Notifications.
| Write a personal Notepad note that you can save for later viewing; see
Creating Ongoing Notepad Notes.
| Post your Notepad note as a LightNote on your client desktop; see Posting
LightNotes on your Desktop.
NOTE: LightSoft also enables forwarding of alarm

notifications to remote FTP servers and to individual user
SMS and email accounts. For more information, see Alarm
Forwarding by FTP to Remote Servers and Alarm
Forwarding by SMS and Email.

Posting Messages to a Bulletin Board

The Bulletin Board allows you to post messages to other LightSoft users.
To open the bulletin board and view messages:

1. On the LightSoft main menu bar, select Tools > Bulletin Board. The
Bulletin Board window opens.
2. Select the message you want to view and click View. The BBoard
Message window opens.
3. View/read the message, using the scrollbars if necessary, and when

finished, click Close.
Authorized users can delete a message by selecting it, clicking Delete in the
Bulletin Board window and then clicking Yes in the confirmation dialog box.
Each message on the Bulletin Board occupies a line. The window columns are
described in the following table.
Bulletin Board window columns
Column Description
Date Date on which the message was posted
From User who posted the message
Subject Description of the message contents

To compose a message and post it on the Bulletin Board:

1. In the Bulletin Board window, click Compose. The Compose Bulletin
Board Message dialog box opens.
2. Enter a brief description of the message in the Subject field.

3. Type the message in the message area.
4. When you finished writing the message, click Send to post it to the Bulletin
Board.
OR
Click Close to close the Compose Bulletin Board Message dialog box
without posting the message. If you already started the message, a
confirmation window opens.
Click Yes to save the message. A line representing the message will
appear in the Bulletin Board window.
Click No to discard the message.
Click Cancel to keep the Compose Bulletin Board Message dialog
box open and continue working with the message.

Sending Messages to Logged-In Users

You can send a message to any user logged in to the system.
To send a message to a user via the Active Users window:

1. On the main menu, select Tools > Send Message. The Send Message
dialog box opens. Continue to Step 4.
OR
2. On the LightSoft main menu, select Security > Active Users. The Active
Users window opens.
3. Select a user and click Send Message (enabled if the user performing the
action is not the selected user).
4. The Send Message dialog box opens.
If you accessed the function from the toolbar, no user recipient selections
were made. If you accessed the function from the Active Users dialog box,
an initial user recipient is selected.

5. As needed, select one or more users in the Active Users pane and click
to move them to the Selected Users pane, or click to select
and move all users at once. Use the and buttons to reverse
the process. There must be at least one recipient (user) in the Selected User
pane.
6. Type the message in the note area and click Send. A "Message sent
successfully" notification appears. The Send Message dialog box closes
and the message appears on the desktop of the selected users in a
LightNote window.
Viewing and Attaching Notes on Fault

Notifications
User notes are LightNote comments that can be attached to Fault system
alarms, TCAs, and Event notifications. For more information about the Fault
notifications, see Fault Management.
3
OPTIONAL FEATURE: Alarm user notes are a fully

integrated add-on capability, available on a cost basis. If not
purchased, the feature and the related menu options are
deactivated.
More than one user note can be attached to a single notification, and a single
user note can be attached to more than one notification. User notes can be
viewed in the User Notes pane of each list window.
The total number of notes attached to the notification is indicated in the
Number of User Notes column, which is an optional column. To display
it, select Number of User Notes on the View menu of the list you are viewing.
When a selected notification has notes attached (the Number of User Notes
column shows “1” or more), they are represented by icons in the User
Note pane (at the bottom of the list window). Double-clicking a note icon
displays its contents.
By default, user notes have system-assigned names. You can give a user note a
different, more meaningful name by clicking the icon of the user note you want
to name and typing a name in the field.

To view an existing note:
1. On the toolbar, click the Show User Notes icon.

OR
Right-click any notification and select the Show User Notes shortcut menu
option. The User Notes pane appears at the bottom of the window.
2. Select a notification that has notes attached (the Number of User
Notes column shows “1” or more). The LightNote icons appear on the
bottom pane.
3. Double-click the LightNote icon whose content you want to display. The
LightNote opens.
4. To close LightNote, click the close button in the upper right-hand corner of
the window.
To create a user note:

1. Select the notification in the list window to which you want to attach a user
note.
2. On the toolbar, click .

OR
Right-click the notification and select Add Note on the shortcut menu. The
LightNote popup window opens.

3. Enter the text. Click the Save icon in the top right corner of the window.
The system prompts you to enter a title for the note (default = date:time).
4. If you want to save the LightNote under a different name, modify the name.
5. Click OK to complete the save. An icon for the new note appears in the
User Notes pane. (Or you can click Cancel to cancel the save action.)
Creating Ongoing Notepad Notes

Notepad is a useful text editor that allows you to write ongoing notes that you
can save for later viewing. Notepad notes are private and no other user can
view them. If a user is removed from the system, the Notepad contents are
removed as well. Notepad notes are ASCII text files that can be viewed in any
text editor.
Creating a Notepad note is just like using any text editor. You can cut, copy,
and paste text, save to flash memory, and restore a previously saved note. You
can also post a LightNote to your client desktop.
To create a note in Notepad:

1. On the LightSoft main menu bar, click Tools > Notepad. The Notepad
window opens.
2. Type, edit, and work on your text, using the following options to assist you:
Cut , Copy , and Paste selected text as required.
Click Save to save the current note contents.

Click Retrieve to replace the display with what was last saved.
Click New to clear the message display.

3. Post a LightNote to your client desktop using the Post Selection or

Post LightNote functions. For more information, see Posting
LightNotes on your Desktop.
4. When you finish working on the current note, on the Notepad menu bar,
select File > Close. (If you made changes since the last Save, you are asked
if you want to save the current contents. If you do not save, any previously
saved content will remain intact.)
Notepad menu and toolbar options
Menu/Toolbar option Description

File
New Clears the message display.
Retrieve Replaces the display with what was last saved.
Save Saves the current note contents. The contents last saved
are kept after you close the window, and redisplayed when
you open it next.
Edit
Cut Cuts the selected text segment and copies it to flash
memory, available for pasting.
Copy Copies the selected text segment to flash memory,
available for pasting.
Paste Pastes the current flash memory contents to the cursor
position.
Options
Post Posts a LightNote to your client desktop containing the
LightNote current message contents; see Posting LightNotes on your
Desktop.
Post Posts a LightNote to your client desktop containing the
Selection selected text segment; see Posting LightNotes on your
Desktop.

Posting LightNotes on your Desktop

You can write a note in Notepad and post it on your client desktop. Notes are
posted in the LightNote window.
To post a Notepad note as a LightNote:

1. In the Notepad window, compose your note.
2. To post the entire note as a LightNote:
On the Notepad menu bar, select Options > Post LightNote.
OR
On the toolbar, click the Post LightNote icon .

OR
3. To post only the selected text:
On the Notepad menu bar, select Options > Post Selection.
OR
On the toolbar, click the Post Selection icon .

A LightNote window opens on the desktop showing the text (all or a
selection) from the Notepad window. The status line at the bottom of the
window shows the date and time the note was created and the user who
created it.
4. To close either the Notepad window or the LightNote window, click the
Close icon in the top-right corner of the respective window.

LightSoft Properties
You can view basic information of your LightSoft application in the LightSoft
Info dialog box.
To view LightSoft information:

| On the LightSoft main menu bar, select System > LightSoft Info. The
LightSoft Info dialog box opens.
Info dialog box fields
Field Description
NMS Name Name by which LightSoft application is referred in
Created With and Modified With parameters.
NMS Main Hostname Not available.
LightSoft Server SW Version Version of the server software version running.
LightSoft Client SW Version Version of the client software version running.
Number of EMSs Number of EMSs managed by LightSoft.
Disconnected EMSs Number of EMSs currently disconnected from
LightSoft.
Number of MEs Total number of MEs from all managed EMSs.
Disconnected MEs Number of MEs currently disconnected from
LightSoft.
Number of Active Users Total number of LightSoft users currently logged
in to the system.

4
Managing Elements, Groups,
and Networks
In this chapter:
Overview ......................................................................................................... 4-1
Working with MEs .......................................................................................... 4-3
3
Working with LEs ........................................................................................... 4-9

3
Working with Groups .................................................................................... 4-29

3
Working with UMEs ..................................................................................... 4-34

3
Working with EMSs ...................................................................................... 4-53

3
Working with Ethernet Networks .................................................................. 4-62

Common Operations on Objects.................................................................... 4-86
3
Overview
LightSoft distinguishes between managed elements (MEs) that make up the
network and logical elements (LEs) corresponding to MEs. While an ME
represents a piece of equipment (typically a shelf), an LE represents a logical
element in the equipment, for example, its ports. This distinction enables true
multidimensional network management, allowing you to focus on MEs when
creating and deleting them, and separately to concentrate on the ports available
at each technology layer (SDH, optical, or ETH/MPLS) when managing trails.
LightSoft supports the objects described in the following sections:
| Working with MEs – objects in the network managed by LightSoft and an
EMS, represented as an icon in the LightSoft physical view.
| Working with LEs – objects that represent the capabilities of an ME in a
specific technology layer.
| Working with Groups - collections of objects (MEs, LEs, groups) for
managing the members of a group as a single object.

Managing Elements, Groups, and Networks LightSoft User Manual
| Working with UMEs – elements that are part of the network but not
managed by an EMS that is managed by LightSoft.
| Working with EMSs – software applications that manage elements which
may also be managed by LightSoft.
| Working with Ethernet Networks - automatically partitioned "groups"
representing LEs with the same network ID and the function they perform.
Common Operations on Objects describes how to perform operations on
objects selected from the LightSoft main window map or Tree view.
Operations on Tree-selected objects can be performed on granular objects (for
example, individual ports in any object) by drilling down in the tree. These
operations can include, for example, opening a GCT session to the shelf view
of a port. Operations on Tree-selected objects are performed from shortcut
menus.
Whenever you add an ME to the network in the physical layer, an LE is
automatically created in the relevant technology layer. If the ME contains ports
that belong to multiple technologies (as may be the case with XDM shelves),
an LE is created for each technology in its corresponding layer.
To better represent the structure and function of your network, you can group
MEs and LEs. There are icons for each ME type, LE type, and group type.
The status of the various types of objects and links is indicated on the map with
colors, as described in GUI Cut-Through (GCT) and Object Status Color
Indications.

LightSoft User Manual Managing Elements, Groups, and Networks
Working with MEs

MEs are pieces of equipment on the network, for example, a shelf managed by
LightSoft and an EMS. This section describes operations that can be performed
on MEs. Other ME operations, which are common to more than one object
type, are described in Common Operations on Objects.
Creating MEs
You can create MEs directly from the LightSoft main window Physical (EMS)
layer, using the GCT function.
To create an ME:
1. In the Topology layer dropdown list, select the Physical (EMS) layer.
2. Click the EMS for which you want to create an ME.
3. On the Configuration menu, select Create > ME. A cut-through Create
ME dialog box specific to the selected EMS opens.
4. Complete the Create action as described in the relevant EMS user manual.

Forcing an ME Upload
You can force upload an ME, with or without its internal subnetwork
connections (cross connects).
NOTE: When performing the actions described in this

section, be sure to coordinate with your workgroup to avoid
other users defining trails in the same area.
To force upload an ME:

1. In the Physical (Site) topology view, select an element.
2. On the menu bar, select System > Force Upload > ME. The ME data is
uploaded.
To force upload an ME and its internal subnetwork

connections:
1. In the Physical (Site) topology view, select an element.
2. On the menu bar, select System > Force Upload > ME & Connections.
The ME and subnetwork connections data are uploaded.
The color of the ME icon becomes blue during upload and then changes based
on its updated state.

LightSoft Aspects of SR9700 MEs

Carrier Ethernet Switch/Routers (CESR), such as ECI's SR9700 family product
line, enable operators to build a Carrier Ethernet infrastructure for IP transport
over metro networks and to provide private and business customers alike with a
variety of services including: very high bandwidth for data applications, IP-
telephony as well as IPTV and VoD, (Triple Play) with high quality of service,
in a more cost effective way than existing technologies.
The SR9700 elements are configured using internal mechanisms, with logical
ports created and enabled through the STMS (the SR9700 family EMS); For
more information, see the STMS User Guide.
The SR9700 chassis and data ports are automatically uploaded to LightSoft and
appear in the LightSoft physical and ETH/MPLS layer map view and tree. The
STMS icon is visible in the Physical (EMS) layer.
GCT
GCT from the SR9700 ME (see Starting/Closing a GCT Session) opens the
STMS main window with a focus on the specific ME. It shows the configured
ports, equipment alarms associated with the specific ME in one pane, and
equipment alarms from all MEs in another pane. For GCT to work, a user must
be manually created both in LightSoft and the STMS with the same user name
and password.
Alarms
The same port alarms can be viewed either via LightSoft or the STMS. Right-
clicking an SR9700 ME in LightSoft opens a choice of :
| Current Alarms: Opens the Current Alarms window in LightSoft,
showing alarms of the specific ME; see Viewing Related Current Alarms.
OR
| Current Alarms (EMS): Opens a GCT to alarms in the STMS; see
Viewing EMS Current Alarms for an Object.
When a LightSoft user acknowledges an alarm on an SR9700 device, the same
alarm is acknowledged in the STMS as well.
Property modifications
LightSoft-modified SR9700 object properties are not downloaded to the
SR9700 ME or STMS. They are only visible in LightSoft. Conversely,
properties modified using SR9700 mechanisms are reflected in the STMS and
are visible in LightSoft. For more information, see Viewing and Editing Object
Properties.

Security
When a user performs GCT, security levels and capabilities that apply at the
EMS level may differ from LightSoft-assigned levels. LightSoft security
definitions are not downloaded to the STMS. For more information about user
security, see Security.
Upon GCT to the STMS, regardless of a user's permissions in LightSoft, one of
the three STMS permission levels (System Operator, Network Operator, or
Monitor) may apply, depending on the permission level assigned to this user in
the STMS.
Service provisioning in mixed networks of MCSs and

SR9700s
The process of service provisioning involves the following steps:
1. Create physical links in LightSoft, between all relevant elements, including
between SR9700 MEs with a GbE rate; see Creating Topology Links.
2. Provision services between MSCs and MCSs and SR9700 MEs in the usual
way; see Creating Ethernet Services. Physical and virtual links will be
visible in the applicable topology layers.
3. Provision services between the SR9700 MEs using configuration
mechanisms in the SR9700 MEs and the STMS; see the STMS User Guide
for more information.
The services are not uploaded to LightSoft. Only the physical layer links, and
the virtual links between XDMs and SR9700s are visible. In the LightSoft
ETH/MPLS layer, virtual links between the SR9700 MEs are represented by
gaps. The Create Ethernet Service and Service List windows are not relevant
for virtual links between SR9700 MEs.

ME Properties
You can view and edit the properties of selected MEs. To access the
Properties for ME dialog box, right-click an ME in the map view and select
Properties. For other access methods, and information about how to edit
property fields, see Viewing and Editing Object Properties.
Properties for ME dialog box icons

Open Opens a GCT session for this ME; see Starting/Closing a GCT
Session.
Alarms Shows the alarms applying to this ME; see Viewing EMS
Current Alarms for an Object.
Apply Saves edit changes; see Viewing and Editing Object Properties.
Refresh Refreshes the dialog box fields.
Close Closes the properties dialog box.
Help Opens online help.

Properties for ME dialog box fields
Field Description
ME Name ME name. LightSoft allows you to keep a primary LE name in
a technology layer either aligned with or different from that of
its related ME/UME in a physical layer; for more information,
see Viewing and Editing Object Properties.
ME Type ME type.
Status Usability state of the ME (for example, OK), connection state,
or alarm state (Major, Minor, and so on) reflecting the most
severely alarmed port; see Object Status Color Indications.
System Location Location of the ME.
Main IP Address Main IP address of the ME.
Gateway Indicates whether the ME is a gateway (Yes/No).
Version Software version running on the ME.
Managed By Type of management system running the ME.
Logical Names of the LEs to which the current ME is mapped in
Elements (LEs) different technology layers.
Maintenance Indicates whether the maintenance function is ON or OFF.
Consistency Indicates the consistency between LightSoft and the respective
State EMS depending on the actual status, either Consistent or
Inconsistent.
An inconsistency for an ME occurs when an ME is deleted
from the EMS but cannot be deleted from LightSoft (for
example, when a trail passes through an ME in LightSoft but
the EMS allowed the ME to be deleted. In this case the
inconsistency reason "Deleted from EMS" is appended.
Comments Free-text field.

Working with LEs

Elements in a technology layer are referred to as LEs. An LE represents a set of
ports acting as a functional unit. When an ME is added to the network in the
physical layer, LightSoft automatically creates an LE in the corresponding
technology layer which represents the capabilities of the ME and the type of
traffic it can carry. For more information about the interconnections between
technology layers, see Topology Layers.
An LE may contain multiple ports supporting multiple technologies
represented on different layers. A port may be contained by only a single LE of
a specific layer. LEs are elements on the map that can be moved and grouped.
You can create LEs manually to represent more specific functions. This is
supported by moving ports from a primary LE that contains all the ports in the
layer into secondary LEs. For example, an LE representing a WDM
multiplexer can be split into LEs that represent the multiplexer card and the
separate transponder channels, enabling each channel to be visible and
accessible. For more information, see Creating Secondary LEs.
Selected elements on any layer (physical or logical) can be grouped in a single

icon. Groups may be nested (groups of groups) to any level. Groups and group
hierarchies can be independently defined in each layer. For more information
about groups, see Working with Groups.
The Delete option is enabled for secondary LEs. This acts only to return its
ports and any associated links to the primary LE, and to remove the secondary
LE from the view. Primary LEs cannot be deleted. For more information, see
Deleting Objects.

GCT can be performed on LEs to access the corresponding object in its EMS
system, opening the following EMS view:
| If all ports of the LE relate to the same card, the card internals view opens.
| If a split LE has ports from several cards (not a one-to-one relationship),
the shelf view opens in the same way as when an ME is opened. From there
you can navigate to the relevant card internals view.
For a description of GCT, see GCT Operations. For information about starting
GCT, see Starting/Closing a GCT Session.
LE-specific operations
Operations Description
Set LE Location Places LE on technology layer maps in the same locations as
their corresponding ME on the physical layer map; see Setting
LE Location.
Create LE Splits an LE into secondary LEs distinguished by function.
Also creates Ethernet switch LEs for RSTP map purposes; see
Creating Secondary LEs.
Show Shows all Ethernet LEs (data cards) that have the same
Network ID Network ID as a selected (automatically split) Ethernet LE; see
Viewing ETH/MPLS LEs with the Same Network ID.

LE Icons and Direction Representations

Each LE type is represented by a unique icon.
The icon direction in map views can be defined with a direction selector
, either when a secondary LE is created - Creating Secondary LEs, or using the
respective LE properties dialog box - see LE Properties. The following types of
LEs and their corresponding icons are available.
SDH LE types
Icon and directions Description Icon and directions Description
Cross Connect Splitter-Coupler

Regenerator Combiner
SDH Terminal
ETH/MPLS LE types
Icon choices Description Icon and directions Description
Client Ports Service Ports
Ethernet Ports Provider Edge
Ethernet Switch Provider Bridge

Ethernet Encryptor (such as
Terminal offered in ECI
Line Ports Telecom's Aurora
family of
encryption
solutions)
Optical LE types
Icon and directions Description Icon and directions Description
Mux/DeMux Splitter-Coupler
OADM Transponder
Optical Mux
Amplifier
Optical DeMux
Monitor
Optical Switch Combiner
Optical Generic
Terminal

The next sections describe LE-specific operations. Other LE operations which

are common to more than one object type are described in Common Operations
on Objects.
For information about the LE properties, see LE Properties.
Setting LE Location
After MEs are created and uploaded to LightSoft, they are automatically placed
on the physical layer view and related LEs are created and placed in each
supported technology layer. LEs are also automatically placed for UMEs that
you create in LightSoft. You can move the physical layer objects on the map
view according to your presentation purposes, for example, to correspond to
relative map positions; see Moving Elements in the Main Window. Individual
LEs in any technology layer can also be positioned using the same technique
independently of their physical objects.
Most often, users prefer to see LEs in technology layers in exactly the same
positions as their equivalent physical layer objects. You can automatically
place LEs of all or selected MEs/UMEs in all relevant technology layers in this
way. This action can be performed any time, but is usually a first step after
creating new MEs or UMEs. The positions of secondary LEs, which are
generally user-placed, will not be affected.
To set LEs in technology views in the same locations as

their corresponding physical layer objects:
1. In the physical topology layer, select MEs or UMEs (you can select
multiple objects by using the SHIFT key, or all objects using CTRL+A).
2. On the menu bar, select Tools > Set LE Location. All corresponding LEs
are placed in the same positions on their respective technology maps.

Creating Secondary LEs

Each LE in a technology layer can be split into secondary LEs distinguished by
function. For example, an optical element may consist of a transponder and a
multiplexer, so the link between them can be made more explicit on the map if
they are represented by separate symbols.
Similarly, an LE representing an ADM can be split into its ports, making the
links to the ports clearer. Secondary LEs can be created to any level of
granularity, up to a single port.
The LE that corresponds to an element in the physical layer is referred to as a
primary LE. The components that are split from it are called secondary LEs.
When a secondary LE is created, the corresponding ports are removed from the
source LE and any links to those ports are automatically assumed by the
secondary LE where they now reside. In the following example, the three links
between LE1 and LE2 are displayed by the corresponding secondary LEs.
This graphic representation is limited to the technology layer view. The

physical layer is not affected by manipulations on the LE and continues to
show MEs in their original form.

The default name for a secondary LE is the primary LE name with an

underscore and a suffix with a sequential number (for example, if the primary
LE is X62-49, secondary LEs will be X62-49_1, X62-49_2, and so on).
An LE name, as well as other attributes, can be changed when the LE is created

or later, through the LE properties dialog box; see LE Properties.
The ports distribution between a primary and secondary LE can be modified
using the Modify LE function; see Modifying LE Ports.
When a secondary LE is deleted, the corresponding ports and any links revert
to the primary LE; see Deleting Objects.
In the ETH/MPLS layer, "empty" primary LEs (where all associated
components were split out to secondary LEs) can be hidden from the map view
and tree using the Show Networks > Empty Primary LE feature from the
View menu. The secondary LEs remain in the view. See the option description
in Summary of Menu Commands – View Menu.
Automatic LE Creation
LEs can be created either individually with specific internal objects selected
from a source LE or automatically, with all relevant internal objects split out
into multiple secondary LEs at once. Automatic LE creation is available in the
ETH/MPLS and optical layers, as follows:
| Automatic LEs creation by Ethernet switch: PB and MPLS PE LEs are
created automatically according to the assigned card, without any user
intervention and unavoidably. Ethernet objects uploaded from the EMS are
automatically discovered and a representative LE is created. The process
also automatically assigns special attributes to the LEs, such as RSTP-
essential L2 attributes enabling the LEs to be visible in the RSTP map; for
more information, see Viewing RSTP Information.
The automatic LE creation process is applied to PB and MPLS PE objects.
Other secondary LEs can be created manually.
| Automatic LEs creation by optical component: For optical LEs,
automatic secondary LEs creation is user-triggered by setting a checkbox in
the Create LE process (see Creating a Secondary LE). According to the
type of card, either multiple secondary LEs are created or all ports are
assigned to a single secondary LE, according to EMS-defined optical object
groupings. For more information, see Automatically created optical LEs
differ according to their components.
Automatic LE creation translates AoC ADM card pairs into single LEs. The
LE name is taken from the master card slot. While the automatic split is
performed only on the top (primary LE) level, the Tree view shows two slots.

NOTE: After automatic optical LE creation is applied, other

secondary LEs can be created manually. However, this is not
recommended as adding ports may produce unexpected port
distributions – a newly added port may be automatically
allocated to the primary instead of a secondary LE.
Creating a Secondary LE
To create a secondary LE:
1. In the Topology Layer dropdown list, select a technology layer.
2. On the map, select the LE which contains the internal objects or functions
(ports or switches) that you want to split out into secondary LEs. (When
LEs are created individually, the source LE can be either a primary or
secondary LE. In the case of automatic LE creation, a primary LE must be
selected. Ports that have already been removed from the primary LE to a
secondary LE are not included in the Automatic Split.)
3. On the Configuration menu, select Create > LE. The Create Logical
Element dialog box opens. This example shows the dialog box opened
from the SDH layer.
When opened from the optical layer, the window header panel contains a
checkbox (selected by default) that enables automatic LE creation, as
described in the steps below.

4. Specify an LE name (the default is the primary LE name followed by an

underscore and a sequential suffix).
To create LEs automatically in the ETH/MPLS or optical layer,
continue to Step 5.
To create LEs individually in any technology, continue to Step 6.
5. If you are in the optical layer, you can create LEs automatically. The dialog
box header includes an Auto Create Optical LE checkbox, which allows
you to create secondary LEs for every relevant device without having to
make specific selections.
NOTE: The nature of the secondary LEs created depends on

the type of optical card. For more information, see
Automatically created optical LEs differ according to their
components.
a. Select the Auto Create Optical LE checkbox. All dialog box

components except the LE Name are predetermined. All window panes
are disabled and you cannot select ports.
b. Click Apply. The Available Automatic Split Selection Table window
opens, describing all he secondary LEs that may be created.
In this window you can do the following:

Indicate which specific ports you want represented as LEs by
ensuring their checkboxes are selected (and deselecting ones which
you do not need as LEs).
Change names of LEs by clicking the Edit icon and then typing
in the change.
c. Click OK to confirm the LEs to be created. A symbol

representing the LEs to be created appears at the tip of your cursor.

d. Move the cursor to the required location on the map and click to drop
the LEs in place. The new LEs will be distributed between the cursor
position and the master LE, with an operation succeeded message.
e. Click OK to complete the action.
NOTE: The secondary LE types and the direction of their

icons (if applicable), which are set automatically, may not
reflect the intended type and direction. (For example, a
Generic type may be assigned by LightSoft if the specific LE
type could not be identified.) These can be corrected after the
secondary LEs are created through the LE properties. For
more details, see LE Properties.
OR
6. In any technology layer, if you want to create secondary LEs selectively,
one at a time:
a. If an automatic creation option is available (selected by default), clear
the checkbox. The port selection area of the window will become
enabled.
b. Select an LE Type (options vary according to the LE's technology).
The icon that represents the LE on the map is shown next to the LE
type selection. (The following is an optical LE creation example
showing a Transponder LE type selection, and a transponder icon.)
c. Select the directionality of the icon using the directionality selector

, if applicable.
d. Select the Add to LE group checkbox if the LE is part of a group and
you want the secondary LE to be part of the same group.
e. In the main panel, move the cards, slots, or ports that will be
represented by the secondary LE from the Primary LE pane to the
Secondary LE pane by selecting them in the Primary LE pane and
clicking . (You can deselect a card/slot/port by selecting it in the
Secondary LE pane and clicking , or select/deselect all
cards/slots/ports at once by clicking or .)
f. Click Apply. The LE appears at the cursor position. Move the cursor to
the required location and click to place the new secondary LE.

g. Repeat Steps (a) through (e) for additional secondary LEs. The window
remains open to enable you to create additional secondary LEs.
7. When no more secondary LEs are needed, click Close.
8. After LEs are created, their attributes can be modified. For example:
LE type or directionality of its symbol in the map view); see LE
Properties, or
LE ports can be redistributed; see Modifying LE Ports.
Automatically created optical LEs differ according to

their components
According to the type of optical card, the automatic LE creation process either
creates multiple secondary LEs based on the EMS-supplied PTP attribute, or
assigns all the ports to a single secondary LE. In the case of multiple LEs, all
ports that share a common SNC and/or relational pointer are assigned the same
identifier distinguished by a sequential number.
Number of secondary LEs per primary LE created by optical automatic LE

creation process
LE type Which cards Multiple LEs?

Mux/DeMux All Mux, DeMux No
OADM All OADM cards No
Other Element COSC, RB, MO_ACC4RB Yes
Amplifier BACS, PACS No
Amplifier MO_OFA_PHBC OFA_2, Yes
OFA_M
Transponder TRP25_4AB Yes
COMBINER CMBR10T Yes
Splitter-coupler MO_ACC6_CP Yes
MO_ACC6_SP50
Other Element Any other card No

Modifying LE Ports
The ports distribution between a primary and secondary LE can be modified
using the Modify LE function, as described in this section.
All the ports can be reverted back to the primary LE by deleting the secondary
LE; see Deleting Objects. The LE name and other LE attributes can be changed
through the LE properties dialog box; see LE Properties.
To change the distribution of ports to a secondary LE:

1. In a technology layer, select both the primary LE and the secondary LE
between which you want to redistribute ports.
2. On the LightSoft main window, select Configuration > Modify > LEs.
3. Redistribute the cards, slots, or ports as needed, by moving them between

the Primary LE and Secondary LE panes by selecting them in the
Primary LE pane and clicking . (You can deselect a card/slot/port by
selecting it in the Secondary LE pane and clicking , or
select/deselect all cards/slots/ports at once by clicking or .)
4. Click Apply to perform the action and close the dialog box.

Viewing ETH/MPLS LEs with the Same

Network ID
The Network ID of a data card is set in the EMS to partition the Ethernet
topology into different networks.
You can view all Ethernet LEs (data cards) that have the same Network ID as a
selected Ethernet LE. This function is enabled only for automatically split LEs
created by selecting the Split by Ethernet Switch checkbox in the Create
Logical Element dialog box.
To view a list of data cards with the same Network ID:

| On the ETH/MPLS layer, right-click an Ethernet LE which has been
automatically split.
Select Show Network By ID. A new map view opens, showing only the
icons of data cards having the same Network IDs. The network ID and the
number of nodes is shown in the view header.

LE Properties
You can view and edit the properties of selected LEs. To access the Properties
for LE dialog box, right-click an LE in a technology map view and select
Properties. For other access methods and information about how to edit
The following is the properties dialog box for a selected SDH LE.
For a secondary LE, the type of port can be changed (selected from the
dropdown list). The symbol that is displayed in the technology map view also
appears. Where applicable, an additional selector allows you to choose the
directionality of the symbol.
The field composition and meaning vary according to the LE type:
| SDH LE Properties
| Optical LE Properties
| Ethernet PB LE Properties
| MPLS PE Properties
Properties for LE dialog box icons

Open Opens a GCT session for this LE; see Starting/Closing a GCT
session.
Alarms Shows the alarms applying to this LE; see Viewing EMS
Open Opens the Properties for ME dialog box for the ME
Parent ME corresponding to this LE; see ME Properties.


Close Closes the Properties dialog box.
SDH LE Properties
Properties for LE dialog box fields - SDH
Field Description
LE Name LE name. LightSoft allows you to keep a primary LE name in a
technology layer either aligned with or different from that of its
related ME/UME in a physical layer; see Viewing and Editing
Object Properties.
LE Type Type of equipment represented by a primary LE, for example,
XDM-1000, or the type of port represented by a secondary LE.
For Ethernet LEs, shows Provider Bridge (PB), Provider Edge
(MPLS), or L1 ETY.
Primary LE: The LE type is read only.
Secondary LE: The type of port can be changed (selected from
the dropdown list). The symbol that is displayed in the
technology map view also appears. Where applicable, an
additional selector allows you to choose the directionality of

the symbol.
Status Usability state of the LE (for example, OK), connection state
(from an ME), or alarm state (Major, Minor, and so on)
reflecting the most severely alarmed port; see Object Status
Color Indications.
Associated Layer Topology layer represented by the LE.
Active Timing Timing source currently in use.
Source
Active Timing Whether the active timing source is internal or external.
Source Type
Configured Timing source as configured in the EMS.
Timing Source
Configured Type of timing source; see Viewing NE Timing Sources.
Timing Source
Type
Configured Quality of timing source; see Viewing NE Timing Sources.
Timing Source
Quality
Associated ME ME to which the LE is related.
Primary LE For a primary LE, the LE Name is repeated.
For a secondary LE, the primary LE from which this secondary
LE was split is indicated.
Consistency Consistency state of the associated ME. See parameter
State definition in ME Properties.
Comment Free-text comment field. Saved in LightSoft only.

Optical LE Properties
The following is the properties dialog box for a selected optical LE.
Properties for LE dialog box fields - Optical
Field Description
LE Name See SDH LE Properties.
LE Type
Status
Associated Layer
Associated ME
Primary LE
Consistency State
Comment

Ethernet PB LE Properties
The following is the properties dialog box for a selected Ethernet PB LE.
Properties for LE dialog box fields - Ethernet PB
Field Description
LE Type
Status
Associated Layer
Network ID Network ID of the LE. Set in the EMS to partition the
Ethernet topology into different networks.
When the Show Network ID option is selected for an
Ethernet LE, a window opens listing all data cards with
the same Network ID; see Viewing ETH/MPLS LEs
with the Same Network ID.
Bridge MAC Address MAC address of the data card.
STP Type Spanning Tree Type of the data card (None, RSTP,
MSTP).
STP Bridge Priority Value 4K to 60K, in steps of 4K.
Associated ME See SDH LE Properties.
Primary LE
Consistency State
Comment

MPLS PE Properties
Properties for LE dialog box fields - MPLS PE
Field Description
LE Type
Status
Associated Layer
Network ID See Ethernet PB LE Properties.
PE ID PE ID of the MPLS PE.
Gateway PE True/False. An MPLS PE is a gateway PE if an EoS
trail has an endpoint in it.
Bridge MAC Address See Ethernet PB LE Properties.
STP Type
STP Bridge Priority
Associated ME See SDH LE Properties.
Primary LE
Consistency State
Comment

Recommendations for Creating Secondary

LEs in the Optical Layer
The following specific use of the Create LE functionality is recommended for
the optical layer. The recommended workflow includes creating secondary LEs
and then grouping sets of these LEs for maximum operational flexibility and
clarity.
1. Create LEs for each element in the optical site, such as LEs for each
transponder channel, multiplexer device (Mux, DeMux, booster, and/or
preamp), and splitter-coupler ports. For information about creating
secondary LEs, see Creating Secondary LEs.
For each multichannel transponder card, create an LE to represent the
add, drop, and line ports of each channel.
For the AUX card, create an LE for each triplet of splitter-coupler
ports.
Create LEs to represent each Mux.
The following picture shows a configuration with TRP cards, AUX cards,
and Mux devices, represented by icons generated by the LE creation
process.

2. Create the following groups according to function. For information about

grouping, see Working with Groups. The circled numbers refer to the figure
below.
Client groups hierarchy, comprising:
Individual TRP LEs
TRP LEs grouped with their corresponding splitter-coupler LEs
Single Client group (UME or other endpoint of the client service)
All Client group comprising the client groups for all channels
All Mux Devices (MD) group, comprising Mux, DeMux,
booster/preamp LEs
Site group, comprising the All Client group and the All MD group

Working with Groups

You can create groups of MEs or LEs to manage and monitor them in a way
that is consistent with your working needs. Groups allow you to organize your
network hierarchically in two mutually independent ways:
| Physical – rack, site, city, and so on.
| Technological – chain, ring, and so on.
When you create a group, you can view alarms for all objects in the group,
view all trails that are served by the MEs or LEs in the group, and manage all
group members simultaneously.
A group can contain elements on the same topology layer and can be nested by
creating groups of groups to any level. You can also add and remove elements
to/from a group.
There are two types of groups:
| Site groups in the physical layer, which allow users to classify MEs by their
physical location.
| Functional/administrative groups in the technology layers, which allow
users to classify LEs by functionality.
A variety of operations can be performed on user-defined groups. This section
describes group-specific actions. Other group actions, which are common to
more than one object type, are described in Common Operations on Objects.
For information about the properties of user-defined groups, see Group
Properties.
Objects in the ETH/MPLS layer are automatically allocated to network groups.
The groups are automatically updated according to any actions performed on
the network objects. The groups themselves cannot be manipulated using the
procedures described in this section. However, an automatic group (or a part
thereof) can be included in a user-defined group. (User-defined groups may not
include partial contents of multiple automatic groups.) For more information
about automatic groups and their properties, see Automatic Network Groups.
Group-specific operations
Operation Description
Create Group Creates a group of MEs or LEs. For details, see Creating
Groups.
Add Objects to a See Adding MEs, LEs, and Groups to a Group.
Group
Remove Objects See Removing MEs, LEs, and Groups from a Group.
from a Group

Delete Group Ungrouping a group, thereby deleting it. For details, see
Deleting Groups.
Expand, Expand in Expand a group to show its components, or collapse objects
New view, into a group. For details, see Expanding or Collapsing
Collapse Objects.
Creating Groups
This section describes how to create a user-defined group comprising any
number of MEs, LEs, and/or groups (including automatically defined network
group). User-defined groups may not include partial contents of multiple
automatic groups.
To create a group:
1. In a topology view, select the elements you want included in the group by
holding the SHIFT key and clicking each element, or by dragging the
mouse over the region where the elements are located. Each selected
element is highlighted.
2. On the LightSoft main menu bar, select Configuration > Create > Group.
The Create Group dialog box opens.
3. Enter a name for the group.

4. Select a Group Type. You can group MEs by node, region, room, building,
city, region, and country.
5. In the Comment field, enter additional details about the group.
6. Click Apply. The group is added to the topology tree. To cancel the
operation without creating a group, click Cancel.
A group icon with a group name appears on the map. Click to lock it in a
location on the map.

Adding MEs, LEs, and Groups to a Group

This section describes how to add MEs, LEs, and/or groups to an existing
group. (User-defined groups may not include partial contents of multiple
automatic groups.)
OPTIONAL FEATURE: Adding an NE group to another

NE group is a fully integrated add-on capability, available on
a cost basis. If not purchased, the feature and related menu
commands are unavailable.
To add objects to a group:

1. In a topology view, click the object you want to add to a group to select it.
2. On the LightSoft main menu bar, select Configuration > Modify > Add to
Group. The Add to Group dialog box opens.
3. If necessary, click the nodes to expand the tree and show specific groups.
4. Select the group to which you want to add the ME, LE, or group, and click
Add. To exit without adding the ME to the group, click Cancel.
Removing MEs, LEs, and Groups from a

Group
This section describes how to remove MEs, LEs, and/or groups from an
existing group.
To remove an object from a group:

1. In the topology view, click the object you want to remove from a group to
select it.
2. On the LightSoft main menu bar, select Configuration > Modify >
Remove From Group. The element is removed from the group.

Deleting Groups
Members of a group can be ungrouped, thereby deleting the group but not the
individual objects that make it up. Automatically created network groups
cannot be manually deleted.
To delete (ungroup) a group:

1. In a topology view, click the group you want to delete to select it.
2. On the LightSoft main menu bar, select Configuration > Delete. The
group is deleted, but the individual objects remain in the view.
Group Properties
You can view or edit the properties of selected user-defined groups. To access
the Properties for Group dialog box, right-click a group in the map view and
select Properties. For other access methods, and information about how to edit
Properties for Group dialog box icons

Alarms Shows the alarms applying to this group; see Viewing Related
Current Alarms.

Properties for Group dialog box fields
Field Description
Group Name Group name.
Status Status of the group (the most severe alarm status of any
contained element). Available states are OK or Alarm,
including severity (for example, Major or Minor); see
Object Status Color Indications.
Group Type Type selected when the group was created.
Parent Group Group to which the group belongs (not relevant if the root
is selected).
Number of Elements Number of elements in the group.
Contained Elements Names of the elements in the group.
Comments Free-text field.
Automatic Network Groups

LEs in the ETH/MPLS layer that have the same network ID are automatically
partitioned to a separate network "group". Network "groups" are distinct from
the user-defined groups described in Working with Groups, and cannot be
manually manipulated in any way. For example, network groups cannot be
combined within a global group, nor can a user-created group have a network
aspect. For more information, see Working with Ethernet Networks.

Working with UMEs

UMEs represent external equipment that is part of the network but not managed
by a LightSoft-managed EMS.
A UME represents one of the following:
| Client equipment that acts as a connection to the LightSoft managed
network. To create links to external equipment, an endpoint must represent
it. A UME provides the endpoint and enables you to name it.
| An element or subnetwork that is not integrated with LightSoft and is
therefore not known to it.
| Passive network equipment, more commonly part of optical networks like
multiplexers or splitters, which are generally not managed. To see the true
topology of the network, you need to represent them with UMEs.
LightSoft provides templates for UME attributes, for example, name, icon,
ports of different rates, and traffic flow pattern (the connection between one
port and another).
When a UME represents an element or subnetwork connected between two
LightSoft-managed subnetworks, you must create two trails: one from the first
subnetwork to the UME, and one from the UME to the second subnetwork. The
UME acts as a terminal to which two separate trails connect.
UMEs are particularly useful when the network has optical sections and there
are optical trails acquired from the network. If LightSoft is not aware of an ME
that acts as an endpoint to an optical trail, the trail will only be partially created.
A UME can be created to represent this endpoint.
You can perform a variety of operations on UMEs. This section describes
UME-specific operations. Other operations, which are common to more than
one object type, are described in Common Operations on Objects.
For information about the properties of UMEs, see UME Properties.
UME-specific operations
Option Description
Create UME Creates a new UME. For details, see Creating UMEs.
Modify UME After UMEs are created, you can change its values. For details,
see Modifying UME Ports.

Creating UMEs
You create UMEs in the Create UME dialog box in which you select the type
of UME and template to be used. You can also configure the template to match
your requirements. You can create a UME in any topology layer.
LightSoft provides templates to simplify the creation of UMEs. Depending on
the technology layer selected, there are several UME templates available. Each
template opens in its own dialog box with appropriate technology labeling.
You can create multiple UMEs with the same configuration at the same time.
Duplicate UMEs use the same label as the original, with additional extensions
(for example, _1, _2, and so on). You can later rename duplicate UMEs and
alter their configuration.
To create a UME:
1. On the LightSoft main menu bar, select Configuration > Create > UME;
the Create UME dialog box opens.
2. Select a technology layer (Ethernet, OTN, or SDH). (If a technology layer

is currently selected in the main menu Topology Layer dropdown list, the
relevant option selected by default.)
3. In the UME Type field, select a UME template from the ones provided for
each technology layer.
4. Enter the number of similar UMEs to be created based on the same
configuration.
5. Click the Configure UME icon . The Create UME dialog box opens
according to the template that you specified in Step 4. See an example in
SDH UME Templates.

6. Enter the necessary values. For more information about specific templates,
see the following sections:
SDH UME Templates
OTN UME Templates
Ethernet Data Equipment UME Template
TIP: When you place the mouse over an item or field, a

context-sensitive popup description appears, for example,
showing the maximum number of ports allowed.
7. When you have configured the UME, click OK (or click Cancel to close
the dialog box without saving the configuration), and continue to Step 11.
8. A UME icon appears at the cursor position. Move the cursor to the required
location on the map and click to place it. A confirmation dialog box opens.
9. Click OK; the Create UME dialog box opens again. Click Close to close
it.
If you created multiple UMEs, you can modify their configuration by opening
each one using the Modify UME Ports option. For more information, see
Modifying UME Ports.
When you create a UME, the corresponding LEs are created in the technology
layers based on the UME ports.

SDH UME Templates

The following information is common to all SDH UME templates.
SDH UME templates - common information
Selection/Field Description
UME Name Enter a name to identify the UME.
UME Location Free text field for the UME's location.
Click this button to open the UME Image window, which
describes the template's signal flow.
Comment Multiline free text for additional descriptions.
The following specific SDH UME configuration templates are available:

| Standard SDH
| Inline
| Splitter
| Coupler
| Splitter-Coupler

SDH Standard UME Template

The SDH Standard template represents unmanaged ports. SDH trails may
terminate in these ports or may go through the UME. Users define the rates and
number of ports of the UME.
SDH Standard UME template - type-specific information
Opens a description of how the element is connected in the
network.
Selections
Rate fields For each port rate, select the number of ports you want to
configure.

SDH Inline UME Template

The SDH Inline template represents unmanaged ports of inline equipment, for
example, an amplifier. Topology links can be created to these ports to depict
the network topology but no trails may use this UME. Only two ports exist for
this type of UME.
SDH Inline UME template - type-specific information
Opens a description of how the element is connected to
the network.
Selections
STM Ports Number of UME ports (always two).
SDH Splitter UME Template

The SDH Splitter template represents unmanaged ports of splitters. Topology
links can be created to these ports to depict the network topology.
SDH Splitter UME template - type-specific information
the network.
Selections
STM Ports Number of UME ports (always three).

SDH Coupler UME Template

The SDH Coupler template represents unmanaged ports couplers. Topology
links can be created to these ports to depict the network topology.
SDH Coupler UME template - type-specific information
the network.
Selections
STM Ports Number of UME ports (always three).
SDH Splitter-Coupler UME Template

The SDH Splitter-Coupler template represents unmanaged ports of splitter-
coupler objects. Topology links can be created to these ports to depict the
network topology.
SDH Splitter-Coupler UME template - type-specific information
the network.
Selections
STM Ports Number of UME ports (always six).

OTN UME Templates

The following information is common to all OTN UME templates.
OTN UME templates - common information
UME Name Enter a name for the UME.
UME Location Free text for the UME's location.
Click this button to open the UME Image window, which
describes the template's signal flow.
The following specific OTN UME templates are available:

| Terminal OTN
| Inline
| Mux/DeMux
| OADM
| Splitter
| Coupler
| Dynamic Gain Equalizer (DGE) Coupler
| Splitter-Coupler
| Regenerator

Terminal OTN UME Template

The Terminal OTN template represents unmanaged ports of terminal equipment
in the OTN layer, typically client equipment connected to the managed network.
Topology links and optical trails can be created to these ports.
Terminal OTN UME template - type-specific information
Opens a description of how the element is connected to the
network.
Selections
Rate fields For each port rate (except OCH) select the number of ports you
want to configure.
OCH Select the number of channels (None, Single, Entire Band).
OCH Band If your choice in the OCH field is Single or Entire Band, the C
Selection Band - 100 Ghz automatically applies.
Select OCH If your choice in the OCH field is Single, click the required
Frequency channel.
If you selected Entire Band, then all 40 channels of the C Band
will be selected.

Inline UME Template

The OTN Inline template represents unmanaged ports of terminal equipment in
the OTN layer, typically client equipment connected to the managed network.
Topology links and optical trails can be created to these ports.
Inline UME template - type-specific information
Selection/ Description
Field
Opens a description of how the elements connected to the network.
Selections
Fiber Ports Number of UME ports (always two).

Mux/DeMux UME Template

The OTN Mux/DeMux template represents unmanaged ports of a 40-channel
C band Mux or DeMux.
Mux/DeMux UME template - type-specific information
network.
Selections
Select UME Select whether the UME is a Mux or a DeMux.

Type
OTM Ports Number of OTM ports (always one).
OCH Band The C Band - 100 Ghz automatically applies.
Selection
OPS_1 Ports Number of OPS_1 ports (always 40).

OADM UME Template

The OTN OADM template represents unmanaged ports of an OTN OADM.
You can specify to add and drop four channels. It may be configured as either
East/West or A-B.
OADM UME template - type-specific information
network.
Selections
OADM Type Select whether the OADM is East/West (EW) or AB.

OTM Ports Number of OTM ports - 4 for East/West, 2 for A-B.
OCH Band The C Band - 100 Ghz automatically applies.
Selection
OPS_1 Ports Number of OPS_1s used for the OCH trail add/drop (always
eight).
Select OCH Select the required channels.
Frequencies

Splitter UME Template

The OTN Splitter template represents unmanaged ports of a splitter. Optical
lightpath trails may traverse this UME.
Splitter UME template - type-specific information
network.
Selections
Fiber Ports Number of UME ports (always three).
Coupler UME Template

The OTN Coupler template represents unmanaged ports of a coupler. Optical
lightpath trails may traverse this UME.
Coupler UME template - type-specific information

network.
Selections
Fiber Ports Number of UME ports (always three).

Dynamic Gain Equalizer (DGE) Coupler UME

Template
The OTN DGE Coupler template represents unmanaged ports of a coupler used
for 80 channel DGE sites. Optical lightpath trails may traverse this UME.
Coupler UME template - type-specific information
network.
Selections
Source Ports Number of source ports (always one).

(80 Channels)
Sink Ports Number of sink ports (always two).
(40 Channel)
Splitter-Coupler UME Template

The OTN Splitter-Coupler template represents unmanaged ports of a splitter-
coupler. Optical lightpath trails may traverse this UME.
Splitter-Coupler UME template - type-specific information
network.
Selections

Fiber Ports Number of UME ports (always six).
Regenerator UME Template

The OTN Regenerator UME represents unmanaged ports of an OTN
regenerator. You can specify the port type and channels.
Regenerator UME template - type-specific information
network.
Selections
Line Port OPS-1, OTU1, OTU2, OTU3.

Channel 1 The default is 0. If left as 0, the port will be available for use for
any OCH channel. If you select a specific channel, only that
channel will be allowed to be used for a new trail. You can select
any of the 40 DWDM or 8 CWDM channels (192.1 to 196.0 or
1471 to 1611).
Channel 2 Same description as for Channel 1.

Ethernet Data Equipment UME Template

The Ethernet Data Equipment template represents ETH/MPLS layer ports of
UMEs, typically client equipment connected to the managed network.
Ethernet Data Equipment UME template - type-specific information
UME Name Enter a name for the element.

UME Location Free text to describe the element’s location.
network.
Selections
Optical GbE Enter the number of optical GbE ports.
Electrical GbE Enter the number of electrical GbE ports.
Optical FE Enter the number of optical Fast Ethernet ports.
Electrical FE Enter the number of electrical Fast Ethernet ports.

Modifying UME Ports

After a UME is created, you can modify the configuration of its port
configuration, where applicable.
For information about modifying other fields, see UME Properties.
To modify a UME:
1. In the LightSoft main window map view, right-click a UME.
2. Select Modify UME Ports from the shortcut menu; the Modify UME
dialog box opens, showing the current UME values. The fields vary
according to the UME type. If the number of ports for the UME type is
fixed, the message "Cannot add ports to this type of UME" opens instead.
For information about specific fields, see Creating UMEs.
You can click to open the UME Image window, which describes the
template's signal flow.
3. Change the values. Editable fields have a white background.
4. Click OK to save the changes.

Telnetting a UME
Telnet is a user-host protocol that allows you to connect to a UME from your
UNIX station. It opens a telnet window to the equipment where you can run
CLI commands. The functions that are available depend on the equipment
characteristics.
For telnet to be accessible, the UME must have a valid IP address, and port if
needed. You code this information in the Properties for UME dialog box IP
Address field. The format is 1.1.1.1 8888 (representing equipment with the
IP 1.1.1.1 and the port 8888). For more details, see UME Properties.
NOTE: Telnet, being an external application, is not affected

by LightSoft's inactivity timeout mechanism. While working
for an extended period with telnet, LightSoft may sense
inactivity and automatic lock or logout from LightSoft due to
timeout. If this should happen, the telnet session remains
active.
(A popup message appears one minute before the LightSoft
timeout is triggered. Clicking Continue cancels the timeout.)
To start a telnet session with a UME:

1. From the Physical (Site) or EMS layer, right-click a UME on the map view
and select Telnet UME from the shortcut menu. A telnet window opens.
(If the UME does not have an IP address, or its address is invalid, a
message to that effect appears. Click OK to close the message window.
You can try again after you have added or corrected the IP details in the
Properties for UME dialog box IP Address field.)
2. Run CLI commands, as needed, in accordance with the equipment
characteristics.
3. When you have finished, return to the LightSoft environment by closing the
telnet window.

UME Properties
You can view and edit the properties of selected UMEs. To access the
Properties for UME dialog box, right-click a UME in the map view and select
Properties. For other access methods, and information about how to edit
Properties for UME dialog box icons

Refresh Reloads the contents of derived fields.
Properties for UME dialog box fields
Field Description
UME Name UME name. LightSoft allows you to keep a primary LE name in a
technology layer either aligned with or different from that of its
related ME/UME in a physical layer. For more information, see
Viewing and Editing Object Properties.
UME Type UME type, as defined in the UME creation process; see Creating
UMEs.
Location Free text for the UME's location.
Logical Elements Names of the LEs to which the current UME is mapped in
(LEs) different technology layers.

Field Description
IP Address For telnet accessibility, the UME must have a valid IP address,
and port if needed, coded in the IP Address field. The format is
1.1.1.1 8888 (representing equipment with the IP 1.1.1.1 and the
port 8888). For more details, see Telnetting a UME.
Comment Free text field.
Working with EMSs

As a network management system for large networks, LightSoft acts as an
umbrella system for multiple EMSs.
You can perform a variety of operations on EMSs. This section describes
EMS-specific operations. Other EMS operations, which are common to more
than one object type, are described in Common Operations on Objects.
For information about the properties of EMS, see EMS Properties.
EMS operations
Create EMS Creates a new EMS. For details, see Creating an EMS.
Manage/Unmanage Sets the EMS to Managed or Unmanaged status. For details, see
EMS Managing and Unmanaging EMSs.
Force Upload Forces upload of a selected EMS or its alarms. For details, see
Forcing EMS Uploads.
Accessing an EMS Opens a GCT to the EMS. For details, see Accessing an EMS.
Discover ME To expedite the ME creation process, you can concurrently
create multiple MEs by specifying the range of IP addresses to
be searched. For details, see Discovering MEs.
OPTIONAL FEATURE: The number of EMSs that

LightSoft will manage is a fully integrated add-on capability,
available on a cost basis. It is not possible to create and
manage more EMSs than the ones purchased in the license.

EMS List
The EMS List displays information about the EMSs that LightSoft is
managing.
To open the EMS List:

1. In the LightSoft main window Topology Layer dropdown list, select the
Physical (EMS) view.
2. On the menu bar select Tools > EMS List. The EMS List window opens.
EMS List window menu and toolbar
Toolbar
Menu option Description
icon
List
Print Prints information for the selected EMS as
displayed in the Properties dialog box.
Export to CSV Exports list data to a delimited format file,
such as comma-separated values (CSV),
for import to Microsoft Excel or a
relational database application; see
Exporting to CSV.
Close Closes the EMS List window.
EMS
Properties Displays information about the selected
EMS.
Open Opens a GCT to the selected EMS.
Current Alarms Opens a GCT to the Current Alarms

window filtered for all alarms on the
selected EMS.
Create EMS Opens the Create EMS window.

Toolbar
icon
Force Upload Force uploads the selected EMS.
Create ME Opens the Create ME window.
Help
Open Help Displays help topics.
EMS List window columns
Column Description
Managed Status Status of the EMS: Managed or Unmanaged.
EMS Name Name of the EMS.
Registry Name Name of the EMS in the CORBA naming service
registry.
EMS Type EMS type, for example, EMS-XDM.
EMS Host Address IP address of the EMS server.
EMS Version Version number of the EMS.
No. of MEs Number of elements managed by the EMS.
WS_ID EMS workstation ID.

Creating an EMS
You can create EMSs in LightSoft using the Create EMS dialog box.
WARNING: Consult ECI Telecom customer support before

performing any of the operations described in this section.
To add an EMS:
1. With the Physical (EMS) view selected, on the LightSoft main menu bar,
select Configuration > Create > EMS.
OR
From the EMS List window, select EMS > Create EMS, or click the
Create EMS icon . The Create EMS dialog box opens.
2. Select an EMS from the Registry Name tree.

3. Enter the details of the EMS in the fields.
4. When finished, click Apply. The new EMS is created and added to the
EMS list. Click Cancel to close the dialog box without adding an EMS.

Create EMS dialog box fields
Field Description
Registry Name EMS registry names in a tree structure.
EMS Name Name that identifies this EMS in LightSoft.
Session Login Login name for accessing the EMS. This value is
transferred to the EMS.
Note: When creating a generic EMS, specify
LSNuser as the session login.
Session Password Password for accessing the EMS with the session
login. This value is transferred to the EMS.
Note: When creating a generic EMS for GenEMS
V1.15, specify genems as the session password.
For later versions, use "1".
Managed Status Whether the EMS is managed or unmanaged.
LightSoft The name of the LightSoft workstation that
Workstation provides access to the EMS.
Managing and Unmanaging EMSs

EMSs controlled or not controlled by LightSoft are considered managed or
unmanaged respectively. You can view whether an EMS is managed or
unmanaged by checking the Managed Status column in the EMS List
window. Setting an EMS that is being repaired or maintained to Unmanaged
will prevent LightSoft from receiving unneeded notifications and changes from
the EMS during this time, for example, when the EMS is started from a
Configuration file or RDR backup.
To set the EMS to Managed or Unmanaged status:

1. On the LightSoft main menu bar, select Tools > EMS List. The EMS List
window opens. Select an EMS and click the Info icon on the toolbar.
OR
On the Physical (EMS) layer, select the EMS. Right-click, and on the
shortcut menu select Properties.
The Properties for EMS dialog box opens.
2. Change the Managed Status field from Unmanaged to Managed or vice
versa.
3. Click Apply.

Forcing EMS Uploads

You can force upload an EMS or its alarms. The color of the EMS icon is blue
during upload and then changes based on its updated state.
To force upload an EMS:

1. In the Physical (EMS) topology view, select an EMS.
2. On the menu bar, select System > Force Upload > EMS. The EMS data is
uploaded.
To force upload alarms for an EMS:

1. In the Physical (EMS) topology view, select an EMS.
2. On the menu bar, select System > Force Upload > Alarms. The alarms for
the EMS are uploaded.
Accessing an EMS
You can access an EMS directly from LightSoft without having to start a new
session via the EMS List window. You can also start a GCT session following
the general procedure described in Starting/Closing a GCT Session.
LightSoft features single sign-on between supported layers. Once you are
logged in to LightSoft, you automatically have access to managed EMSs
through GCT, without needing to provide additional login details.
To access an EMS:
1. On the LightSoft main menu bar, select Tools > EMS List. The EMS List
window opens.
2. Select the EMS you want to access.
3. On the EMS List menu bar, select EMS > Open.
OR
On the EMS List window toolbar, click . The main window of the
EMS opens. For specific EMS information, see the corresponding User
Manual.

Discovering MEs
To expedite the ME creation process, you can create multiple MEs by
specifying the range of IP addresses to be searched during the discovery
process. This procedure allows you to exclude specific IP addresses when IP
address ranges in the network are not continuous.
NOTE: This operation requires support from the EMS

managing the MEs. Not all EMSs support the discovery
mechanism.
To discover MEs:
1. From the Physical (EMS) layer, right-click an EMS in the map view or its
node in the topology tree.
2. Select Discover ME from the shortcut menu. The NE discovery window of
the EMS opens.

EMS Properties
You can view or edit the properties of EMSs. For the general procedure, see
Viewing and Editing Object Properties.
WARNING: Consult ECI Telecom customer support before

editing EMS properties.
To view/edit the properties of an EMS:

1. Select the Physical (EMS) view.
2. On the menu bar, select Tools > EMS List. The EMS List window opens.
3. Select the EMS you want to view/edit and click .

OR
In the Map view, right-click the EMS icon and select Properties. The
Properties for EMS dialog box opens.
4. Edit the fields that have a white background. For more information about
these fields, see the table at the end of this section.
5. Click the Apply changes icon to save your changes.

6. To view alarms for the selected EMS, click the Alarms icon . The
EMS Current Alarms window opens filtered for the selected EMS.
7. To open a GCT to the EMS, click the Open object icon .

Properties for EMS dialog box icons

Open Opens a GCT session for this EMS; see Starting/Closing a GCT
Session.
Alarms Shows the alarms applying to this EMS; see Viewing EMS
Properties for EMS dialog box fields
Field Description
EMS Name Name of the EMS.
Registry Name Registry name of the EMS.
Host Name Name of the EMS host.
Managing Workstation LightSoft workstation managing the EMS (relevant for
cluster configuration only).
EMS Type Type of EMS, for example, EMS-XDM.
Status Current alarms status of the EMS (displays the highest
severity status).
Connect Failure Reason Appears when there is a connection failure and the EMS
alarm color code is grey. It shows a reason for the
disconnection.
EMS Version Version number of the EMS.
EMS Host Address IP address of the EMS host.
EMS Location Location of the EMS in the network.
Number of MEs Number of elements managed by the EMS.
Number of disconnected Number of elements managed by the EMS which are
MEs disconnected.
Session Login Login to be used for initiating an EMS session.
Session Password Session password.
Managed Status Indicates whether the EMS is managed or unmanaged.
Comments Free-text field for entering other EMS attributes.

Working with Ethernet Networks

LEs in the ETH/MPLS layer are automatically partitioned into separate
network "groups" in accordance with the LE Network ID as configured by the
EMS.
Network "groups" are distinct from the user-defined groups described in
Working with Groups, and cannot be manually manipulated in any way. For
example, network groups cannot be combined within a global group, nor can a
user-created group have a network aspect.
An MPLS L2 card, such as ECI Telecom's MPLS carrier class switch (MCS)
card, can be configured to be either a Provider Bridge (PB) in a PB network or
a Provider Edge (MPLS-PE) element in an MPLS network. LEs with the same
network ID are grouped in separate Provider Bridge (PB) and MPLS

networks according to the function they perform (distinguished by icons in the
map view).
An LE is considered part of an EA-HVPLS network if all its ports are

connected to LEs of the same EA-HVPLS, which consists of at least two
different networks (PB or MPLS-PE).
You can restrict the view in the ETH/MPLS layer to show any combination of
MPLS and/or PB network types using the Show Networks feature from the
View menu. (The feature also allows you to show/hide Primary LEs in the
ETH/MPLS layer. See the option description in Summary of Menu Commands
View Menu.
For information about PB, MPLS-PE, and EA-HVPLS networks, see Network
Types.
For information about the ETH/MPLS port types, see Supported ETH/MPLS
Port Types.
NOTES:
An LE is a member of no specific network (listed under the
root) if its ports are connected to more than one EA-HVPLS
(or unrelated MPLS and PB networks), or at least one port is
not connected.
L1 SDH cards (such as DIO) are not included in a network
group.
Remote ports connected to a PB or MPLS network via EoS
trails are included in a network provided all the LE's other
ports are also allocated to the same network group.

Network Types
LightSoft manages three Ethernet/MPLS network types:
| Provider Bridge (PB) Network enables relaying Ethernet frames.
| Multiprotocol Label Switching (MPLS) Network carries MPLS data, which
can be IP packets as well as native ATM, and Ethernet frames.
| Ethernet Access Hierarchical VPLS (EA-HVPLS) comprising one MPLS
network and one or more PB networks, enabling PB networks to be
interconnected over a provider MPLS network. The following schematic shows
an EA-HVPLS network comprising an MPLS network and two PB networks.
LightSoft also supports L1 and L2 hub and spoke service networks and
connections; see Hub and Spoke Configurations.
Provider Bridge (PB) Network

A Bridged network relays Ethernet frames between the bridges over Ethernet
links using Learning. In order to prevent looping, RSTP is implemented on the
bridges.
The service entity in a single PB is referred to as a Virtual Switch Instance
(VSI), also known in generic MTNM terminology as a Flow Domain Fragment
(FDFr).
A PB network (a special case of Bridged network, used by communications
providers) relays a customer's Ethernet frames which may be C-VLAN tagged
between customer sites using Provider bridging. In this case, an S-VLAN tag,
dependent on the service, is added to the customer frames to identify the
services to which they belong.
LightSoft typically manages networks in which the provider bridges are
connected with EoS trails.
L2 cards/logical elements (such as EIS and MCS) implement provider bridges.
They are interconnected by EoS trails and the Ethernet frames are encapsulated in
GFP for transmission over the EoS trails. A PB L2 service typically interconnects
multiple Ethernet (ETY) ports. (For a description of all data port types supported
by LightSoft at the logical level, see Supported ETH/MPLS Port Types.)
In the diagram, symbols represent PBs.

A PB can also include hub and spoke-type configurations with an EoS trail
connecting an L2 bridge card and an L1 data card (such as DIO).
MPLS Network
Multiprotocol Label Switching (MPLS) networks are designed to carry a wide
variety of data traffic, including IP packets as well as native ATM, SDH, and
Ethernet frames. MPLS brings new concepts to data communication networks,
such as virtual circuit (VPN) network capabilities, traffic engineering
techniques for better QoS, Fast Reroute (FRR) protection, and reduced
performance requirements from switching equipment.
MPLS network consists of MPLS PEs (such as MCS) connected by MPLS over
Transport (MoT) trails.
Ethernet services traverse an MPLS tunnels over the MoT trails. Where
necessary, a tunnel is cross-connected through an MPLS PE.
Typically a full mesh of tunnels is required between the MPLS-PEs in an
MPLS network to implement services.
An MPLS network managed by LightSoft can include up to 256 PEs. The full
tunnel mesh connecting every two points involves a great numbers of tunnels.
LightSoft "automatons" greatly simplify the tunnel mesh creation process for
stated endpoints. Individual service creation is also guided with warnings, for
example, if there are underlying tunnels or insufficient bandwidth, and the
relevant remedial processes made available.
MPLS Networks and VPLS

MPLS PE LEs (such as MCS) use Virtual Private LAN Service (VPLS) to
implement MP2MP Ethernet services over MPLS networks.
The service entity in a single MPLS PE is referred to as a Virtual Switch
Instance (VSI), also known in generic MTNM terminology as a Flow Domain
Fragment (FDFr).
A VSI is implemented for the service for each service endpoint LE. On an
MPLS network, these endpoint LEs are interconnected by MPLS tunnels and
the Ethernet frames are encapsulated into MPLS frames using two MPLS
labels: the outer MPLS label is the tunnel label and the inner MPLS label
indicates the Ethernet service. The VSI indicates over which tunnel(s) to
transmit a frame using the Ethernet Address Learning mechanism. At the end
of tunnel, the inner label determines the VSI which should handle the frames.
In order to prevent looping, a VSI forwards such an incoming frame over an
Access Link and never over another tunnel (this is called the "Split Horizon"
mechanism).
For MP2MP Services, a full mesh of tunnels is required between the LEs which
are service endpoints.

A similar mechanism, Virtual Private Wire Service (VPWS), is used to

implement a P2P Ethernet Service over an MPLS Network. In this case,
Ethernet Address learning is not required.
The following diagram shows a MP2MP service implemented by VPLS. This
configuration involves a full tunnel mesh connecting the LEs of each service
endpoint.
In the diagram, symbols represent MPLS-PEs.
Ethernet Access Hierarchical VPLS (EA-

HVPLS) Network
An MPLS network can be connected to PB networks to form an EA-HVPLS
network. The following figure shows an EA-HVPLS network comprising an
MPLS network connected to PB networks via EoS trails.
EA-HVPLS networks overcome limitations on the number of services that can
be configured on a single PB network. The PB LEs can be divided up into
smaller subnetworks by placing an MPLS network between them. More
importantly, such a configuration allows the MPLS network to interconnect
with the PB networks.
A service is created that begins and leaves at service endpoints on PB cards
(such as EIS), traversing EoS trails between the PBs. The frames enter and
leave the MPLS part of the network through gateway PEs, traversing MPLS
tunnels over MoT trails between MPLS PEs.

In the diagram, symbols represent PBs, symbols represent MPLS-

PEs.
Typically there are two links between a PB network and an MPLS network for
protection. Dual homing is used to prevent loop formation in this situation. The
BPDU frames (used by RSTP) are carried through the MPLS network between
the ports by defining a dual homed service. This mechanism ensures that one of
the links is active and the other in a standby mode.
Hub and Spoke-Type Configurations

Hub and Spoke-type configurations typically involve customers or branch
offices being able to communicate directly only to the headquarters office and
not with each other.
L1 P2P Services
L1 devices (such as DIO) can be connected by EoS trails. This creates an L1
P2P Service between the ETY endpoints. In this case, no network is implied.
L1 Hub and Spoke Network

L1 Hub and Spoke is an Ethernet L1 network, comprising P2P connections
between an L2 device at the headquarters node (for example, an MCS,
configured as either MPLS or PB) and L1 cards (such as DIO) at branch office
nodes, connected by EoS trails. According to the L2 card configuration, either
an MPLS or a PB network is formed.

L2 P2MP Service Implemented on MPLS Network

A VPLS Hub and Spoke configuration (also known as VPLS Star) involves L2
MPLS cards (such as MCS) at all nodes, using MoT trails and tunnels to
connect the headquarters and branch office nodes. As such, the connections
comprise an MPLS network; see MPLS Network. The associated LightSoft
service is referred to as P2MP (Hub and Spoke); see Supported Ethernet
Service Types.
Network Topology Validity

Validation rules apply to trail creation, which have consequences for network
topology validity.
Typical Valid Network Topologies

The following general rules apply to network interconnections:
| An MPLS and PB network must be connected with only a single link; see
PB network cannot connect to multiple MPLS networks (except with ETY
links).
| An MPLS-PE LE may be connected to only one PB network; see MPLS-
PE LE can connect to only one PB network. The first EoS trail from a
MPLS-PE determines the PB network ID that other EoS trails to this MPLS
PE LE must be connected to.
The following are some more interconnections that yield valid network
topologies. (Trail endpoints are selected during trail creation, as described in
Selecting Trail Endpoints.)
| PB network to multiple MPLS or PB networks:
Using ETY links. ETY links are not considered transmission links. (The
service endpoint is in an ETY port and does not traverse the ETY link.)
| MPLS network to multiple MPLS networks:
Using ETY links. ETY links are not considered part of the MPLS
network. (The service endpoint is in an ETY port and does not traverse
the ETY link.)
Using EoS trails. The EoS trails are not considered part of the MPLS
network. (The service endpoint is in the EoS I-NNI ports and does not
traverse the link.)
| MPLS network to PB network:
Multiple LAG EoS trails from different MPLS-PE LEs. Multiple LAG
EoS trails are parallel EoS trails with endpoint ports being part of a
LAG group, and are considered as a single link.

Two Dual Homed links from different MPLS-PE LEs. The two-link
topology is not initially valid, but becomes so after a Dual Homing
service is created. Dual homing may use one or two MPLS PEs and one
or two PBs. If LAG also applies, multiple EoS trails still constitute a
single link.
Multiple links from the same MPLS-PE LE. RSTP must be enabled for
all ports of the MPLS-PE LE.
| L1 ports to L1 or PB/MPLS-PE port:
L1 port (for L1 Ethernet services), using an EoS trail.
PB or MPLS-PE EoS port, using an EoS trail. (Used for hub and spoke
applications. The hub and spoke service endpoint is in the L1 port but
policing is done in the PB/MPLS-PE EoS port.)
The following are representations of valid networks:
See Invalid Network Topologies for the consequences of variations from the
above.
For a restatement of the rules in terms of trail patterns, see Trail Patterns
Within/Between Networks.
Trail Patterns Within/Between Networks

For networks to be valid, trails within networks and between NEs must be
consistent with the following rules:
Within networks:
| EoS trails connect LEs of a PB network.
| MoT trails connect LEs of a MPLS network.
Between networks:
| EoS trails connect MPLS networks with each other. GbE (ETY) links may
also be used.
| EoS trail may not connect PB networks to each other. An MPLS network is
needed in between.

| EoS trails connect PB and MPLS-PE LEs.

| Multiple PB networks can connect to one MPLS network. But multiple
trails to an MPLS-PE LE must originate from the same PB network.
The port's PB network ID is determined by the PB connected to the
MPLS-PE.
An MPLS-PE's ETH ports are determined by the EoS trail.
The MPLS PE's network ID applies to all its MPLS-PE ports.
| An EoS port with no associated network ID (for example, an SDH data
card) can connect to any network with an EoS trail.
| When Dual Homing is present between PB and MPLS networks, there can
be only two links between them. Otherwise a warning is issued when
creating the EoS trail or the Dual Homing.
| Multiple links are allowed between a PB and MPLS networks.
| RSTP must be enabled. Otherwise a warning is issued for all EoS endpoints
between the networks and EoS trails created between the networks.
| No limitations for physical links (ETY) between PB and MPLS networks.
If the resulting topology is not valid, a warning is displayed before creating or
deleting EoS and MoT trails. If created, the relevant topology elements are set
to inconsistent state; see Invalid Network Topology Indications.
Configurations performed in the EMS/LCT may cause the topology to be
invalid and trigger the relevant objects to be marked as inconsistent.
Invalid Network Indications

An invalid network topology is reflected in the following parameters:
| Network Validation Status parameter, showing various fail reasons and
corresponding fail sources; see Network Properties - General Tab.
| Virtual link Consistency State showing "Inconsistent" (and corresponding
white link color); see Properties for Link - SDH - General Tab.
| Trail State indicated as Invalid; see Trail List Window - Trails Pane
Columns.

Invalid Network Topologies

The following rules describe trail connections that are either disallowed or
would yield invalid network topologies. (In the latter case, a warning is
generated.)
The type of network consistency or validity problem is noted in the Network
Status and Validation Status parameters in the Properties for Network
General Tab.
NOTE: In order to support unanticipated topologies, the

validation rule that "multiple links between MPLS network
and the same PB require RSTP to be enabled for all the
MPLS-PE LE ports" may be disabled with the assistance of
ECI Telecom customer support. A rule suspension applies to
the entire LightSoft system and not just a specific network. If
this rule is suspended, a valid trail is produced even if RSTP
is not enabled.
| PB networks cannot connect using EoS

| MPLS networks cannot connect using MoT
| PB network cannot connect to multiple MPLS networks
| MPLS-PE LE can connect to only one PB network
| MPLS network (different PE LEs) cannot have multiple links to same PB
network
| Dual Homing has two links between MPLS and PB network (or UMEs)
| Multiple links between MPLS network and same PB produce a warning
| LAG inconsistencies are not allowed
| MoT and EoS trails allowed in MPLS-PE network
PB networks cannot connect using EoS

Two PB networks cannot be interconnected with an EoS trail.
All endpoints must have the same network ID (cannot be in different PB
networks) and must be I-NNI; otherwise the trail creation is disallowed. (A PB
network is defined by a network ID established in the EMS.)
Inconsistency may arise due to network changes after a trail is created. If PB
network IDs become inconsistent:
| Virtual link is invalid – consistency state becomes not consistent.
| The containing EA-HVPLS and the two PB networks all have invalid
interconnection status.
| PF cannot use this link for Ethernet services.
| Services may be created on the rest of this PB network.

MPLS networks cannot connect using MoT

Two MPLS networks cannot be interconnected with an MoT trail.
The MoT trail endpoints cannot be in different MPLS networks; otherwise the
trail creation is disallowed.
Inconsistency may arise due to network changes after a trail is created. If
MPLS network IDs become inconsistent:
| Virtual link is invalid – consistency state becomes not consistent.
| The containing EA-HVPLS and the two PB networks all have invalid
interconnection status.
| PF cannot use this link for tunnels.
| Tunnels and services can still be created on each MPLS network.
PB network cannot connect to multiple MPLS

networks (except with ETY links)
A PB network cannot connect to multiple MPLS networks; otherwise the MoT
trail creation is disallowed.
Inconsistency may arise due to network changes after a trail is created. If
connected to multiple MPLS networks:
| PB network and the containing EA-HVPLSs have a faulty status of invalid
interconnection.
| All links besides the first valid link between the PB and other MPLS
networks are invalid – consistency state is not consistent - and PF may not
use these virtual links for services.
However, services may be created on the rest of the network.
PB network can be connected to multiple MPLS or other PB networks with
ETY links. ETY links are not considered transmission links. (The Ethernet
service endpoint is in an ETY port and does not traverse the ETY link.)
MPLS-PE LE can connect to only one PB network

The first EoS trail from a MPLS-PE determines the PB network ID that other
EoS trails to this MPLS PE LE must be connected to. Otherwise, the EoS trail
creation is disallowed.
Inconsistency may arise due to network changes after a trail is created. If the
PE LE is connected to multiple PB networks:
| The PB network and the contained EA-HVPLSs have a faulty status of
invalid interconnection.
| All links between the PB and other MPLS networks (besides the first valid
network) are invalid –consistency state is not consistent - and PF may not
use these virtual links. Services may be created on the rest of the network.

MPLS network (different MPLS-PE LEs) cannot have

multiple links to same PB network
Only one link is allowed. However, a second link can be created as it may
subsequently be used for Dual Homing, but initially the network is assigned an
invalid status. Links refer to connectivity on the EoS or MoT level and not to
LAG groups.
If the multiple links exist then:
| EA-HPLS and PB network is marked as invalid.
| Only first link may be used; other links are invalid and ignored by the
service provisioning.
Dual Homing has two links between MPLS-PE and

PB network (or UMEs)
Dual-homed ports imply that exactly two links are expected; otherwise the
topology will not be valid. EoS trail creation is allowed, but a warning is
generated. If there are not two links when one is defined as Dual Homed, then
the existing link and the containing EA-HVPLS and the PB network are
marked as invalid interconnection.
If more than two DH links exist then:
| Only the first is valid.
| If the EoS trails are not all from the same MPLS-PE LE, the network is
invalid and only the first link may be used.
Multiple links between MPLS network and same PB

produce a warning
Multiple links between an MPLS network and the same PB produce a warning
if:
| Different MPLS-PE LEs are involved.
| RSTP is not enabled for all ports of the MPLS-PE LE. (The RSTP validity
requirement can be suspended - for information, contact ECI Telecom
customer support.)
Otherwise, EoS trail creation is allowed but a warning is generated.
NOTE: If RSTP is subsequently disabled (but the rule not

suspended), the network becomes inconsistent. If the multiple
links exist then:
If all EoS trails are from the same MPLS-PE LE they fail
validation if RSTP is not enabled for all ports of the MPLS-PE.
If the EoS trails are not all from the same MPLS-PE LE then
the network is invalid and only the first link may be used.

LAG inconsistencies are not allowed

| Endpoints of EoS/MoT must match: both endpoints must be LAG or
neither may be LAG.
| Endpoints of EoS/MoT should match LAG group (i.e. master ID).
Otherwise, the trail creation is blocked.
Note: If LAG compatibility is subsequently violated, the network becomes
inconsistent.
On EoS trail creation, both endpoints are validated as being LAG compatible
(both yes or both no).
MoT and EoS trails allowed in MPLS network

MoT and EoS trails are allowed at the same time in an MPLS network.
This is a valid state but service provisioning must use only the tunnels of the
MoT links if they exist (not the EoS links).

Network Properties
The Properties for Network window is used to view and configure network
Traffic Engineering settings.
The window tabs vary according to the network type and are as follows:
| MPLS
| PB
| EA-HVPLS
To open the Properties for Network window and edit

properties:
1. In the LightSoft main window Topology Layer dropdown list, select the
ETH/MPLS view.
2. Right-click the network group icon representing the desired network, and
select Properties from the shortcut menu. The Properties for Network
window opens.
3. Enter changes to editable parameters (having white backgrounds) as
needed.
When a parameter is edited, an asterisk appears in the tab selector. The
asterisk disappears when Apply is clicked to save the changes.
4. Click the Apply icon to save the changes in all tabs.
Properties for Network window toolbar

Alarms Opens the Current Alarms window showing alarms applying to
objects associated with this network; see Accessing Fault
Management Windows.
Apply Saves edit changes in all tabs; see Viewing and Editing Object
Properties.

Network Properties - MPLS

The Properties for Network MPLS window is used to view and configure
network Traffic Engineering settings.
The window contains the following tabs:

| General Tab
| CoS Tab
| CAC Tab
| TE Other Tab
General Tab
This tab shows default general parameters of the network.

Properties for Network MPLS - General dialog box fields
Field Description
Network Name User assigned label for use in addition to the network ID. By
default, the network name is the network ID. (Editable)
Network Status Usability state of the network (for example, OK) or alarm state
(Major, Minor, and so on) reflecting the most severely alarmed
network component; see Object Status Color Indications.
Network Type MPLS.
Network ID Each PB and MPLS network element is assigned a network ID
in the EMS/LCT. LightSoft does not modify it. Networks may
span EMS domains so the same network ID assigned by
multiple EMSs refers to the same network.
Parent Network Global network to which the current network belongs (if any).
Name
Connected PB Lists the PB networks connected to the MPLS network.
Networks
Validation Status Valid (connected), or a failure reason (Fail Reason): Disjointed,
Invalid interconnection, or Dual Homing violation; see Invalid
Network Topologies.
Fail Source: For a non-valid network, ID of the object
associated with the failure.
Number of Number of elements in this specific network.
Elements
Contained List of LEs and groups (same as for user-defined groups).
Elements
Comments Text. (Editable)

CoS Tab
This tab is used to view or configure the default CoS parameters to assign to
each newly created MCS in the network on a per-CoS basis.
Changes can be made in multiple tabs. Select Apply to process all the changes
at once.
Changes in the CoS tab initiate separate processing which may be time
consuming, as settings are downloaded to every bridge in the network to apply
to new tunnel creation. A progress bar appears at the bottom of the CoS tab.
Two messages appear at the conclusion of the processing, one for CoS
parameters and another for the remaining tab changes.
While the processing is in progress, the other tabs remain active and available
for other changes. However, the CoS tab processing must be completed before
tunnels can be created.
Only one user CoS download request can be performed at a time and is
processed by the server on a first-come-first-served basis.
The CoS tab download processing may result in inconsistencies if some bridges
fail to update with the new values. In such cases, you must perform a manual
configuration via the EMS.
NOTE: During CoS configuration download to an MPLS-

PE, you cannot configure tunnels on that PE. An MPLS-PE
undergoing download is color-distinguished on the map.

Properties for Network MPLS - CoS dialog box fields
Column Description
CoS Name Values are either CoS0 to Cos7 or CoS0, CoS2, CoS4, and CoS6,
according to the card type, as indicated by the EMS.
Display Name Display name for each CoS (CoS 0 to CoS 7), for example, Gold or
Platinum in place of CoS7.
Priority Select High or Low for a single threshold CoS. All CoSs above it are
automatically assigned High, and all CoSs below it are automatically
assigned Low.
A different definition of Peak Information Rate applies to High vs.
Low priority packets; see Peak Information Rate.
Booking Factor Overbooking ratio allowed to tunnels per CoS on this network. For
example, the booking factor 2.0 implies 100% bandwidth
overbooking, a booking factor 1.0 (minimum) implies no
overbooking. This factor affects the Committed Information Rate
allowed to the specific CoS on this network. For more information,
see Overbooking and CIR.
Best Effort If enabled, the Bypass tunnel protects all assigned tunnels regardless
Protection of their bandwidth. Otherwise, the bandwidth sum of the tunnels
protected is limited by the Bypass tunnel bandwidth.
CoS Configuration buttons
Button Description
Default Resets values to factory defaults.
Store for New Automatically assigns the changed values to newly provisioned
Networks networks.

CAC Tab
This tab is used to view or configure default CAC parameters to assign to each
newly created MoT virtual link endpoint in the network. Values can be set for
endpoints associated with specific virtual links as needed; see Properties for
Link - MoT Virtual Link CAC Tab.

Properties for Network MPLS - CAC dialog box fields
Column Description
Assign % to all Assigns the indicated Res BW and Res Shared BW percentages
to the port and all CoSs. Different percentages for the port and
specific CoS cannot be selected.
Res (Reservable) Port
BW % Maximum proportion of the port's EMS-assigned bandwidth that
is reservable for working tunnel traffic only. For example, if the
port is configured at the EMS with 2 x VC-4, and Res BW is set
to 50%, BW represented by up to one VC-4 is dedicated to
working tunnel traffic and unavailable for bypass tunnel traffic.
This percentage additionally represents the upper limit to the
maximum % of port bandwidth that can be set for any CoS.
CoS 0 to CoS 7
Maximum proportion of the port's EMS-assigned bandwidth
reservable for working tunnel traffic at a particular CoS.
The percentage set for any CoS cannot exceed the Port Res BW
%. For example, if the port rate is 1000, and Port Res BW % is
50% (meaning 500), Res BW % for any CoS must not exceed
50% (500).
The actual bandwidth that can be used by a CoS is subject to the
port bandwidth limit and BW usage by other CoSs. In the
absence of demand by other CoSs, BW can be used by a CoS up
to the port maximum. Bandwidth actually used by a CoS
depends on the relative CoS priority of tunnels defined on the
link and bandwidth availability and demand at any given time.
For information about bandwidth availability, see MoT Link
Availability based on CAC Parameters.
Res As Res BW %, but representing the proportion of the port's total
(Reservable) assigned bandwidth reserved for Bypass tunnel traffic only and
Shared BW % unavailable for working tunnel traffic.
Total Total of Res + Res Shared BW, which is expected to be 100%.

(Any difference represents nonreservable BW, not available to
customer traffic. Future applications may use this for Control
traffic.)
CAC Configuration buttons
Button Description
Default Resets values to factory defaults.
Store for New Automatically assigns the changed values to newly provisioned
Networks networks.

TE Other Tab
This tab is used to view or configure default FRR and TE parameters to assign
to each newly created MoT trail endpoint in the network. Values can be set for
endpoints associated with specific virtual links as needed; see Properties for
Link - MoT Virtual Link CAC Tab.
Properties for Network MPLS - TE Other dialog box fields
Parameter Description
FRR Parameters/Buttons
FRR Mode Switching traffic from Protected to Bypass tunnels can be
applied in the following ways:
| Automatic: Switches from protected to bypass tunnel upon
failure of the protected port.
| Forced Switch: Forces switch to a bypass tunnel regardless
of the protected port’s state.
| Lockout: No automatic switch from protected to bypass
tunnels regardless of the protected port’s state. To do this,
you must set the FRR mode back to Automatic.
Reversion Switch back from Bypass to Protected tunnels upon repair of
the protected port can be applied in the following ways:
| Revertive: Automatic FRR reversion from protection after
the port is repaired.
| Non-revertive: No automatic switch back from bypass to
protected tunnel regardless of the protected port’s state. To
do this, you must set the Reversion mode back to

Revertive.
Hold-Off time Number of seconds delay (0 to 10 seconds in 0.1 second
(sec) increments (default 0 sec) before FRR switching to protection is
implemented. This avoids premature or too frequent switching,
for example, switching to protection while the underlying
physical-layer protection is also switching (such as with SDH
MS-SPRing or SNCP).
Relevant only when FRR Mode is Automatic.
Wait-to-Restore Number of minutes delay (0 to 12 minutes in 1 minute
Time (min) increments) before automatic reversion from the Bypass back to
the protected tunnels after a failure is repaired. This prevents
premature switchback.
Relevant only when Reversion is Revertive.
Default button Sets factory default values for FRR parameters.
Other
TE Metric Reference rate used in the Link TE Metric calculation to yield a
Reference Rate wider distribution of relative link costs, facilitating comparison
between them; see Link TE Metric in Properties for Link - MoT
Virtual Link TE Other Tab.
Default button Sets factory default value for TE Metric Reference Rate.
Default is 9584.64, representing the 10 Gig SDH rate (64 x VC-
4.

Network Properties - PB
The Properties for Network - PB window is used to view network settings
and to modify selected parameters.
The window contains the following tabs:

| General Tab
| CoS Tab
General Tab
This tab shows default general parameters of a network. Parameters apply
according to the type of network.

Properties for Network PB - General dialog box fields
Field Description
Network Name See Network Properties - MPLS - General
Network Status Tab.
Network Type PB.
Network ID See Network Properties - MPLS - General
Parent Network Name Tab.
Connected MPLS Networks Lists the MPLS network connected to the PB
network.
Validation Status See Network Properties - MPLS - General
Number of Elements Tab.
Contained Elements
Comments
CoS Tab
This tab shows default general parameters of a network. Parameters apply
according to the type of network.
Properties for Network PB - CoS dialog box fields
Column Description
CoS Name See Network Properties - MPLS CoS Tab.
Display Name

Network Properties – EA-HVPLS

The Properties for Network - EA-HVPLS window is used to is used to view
network settings and to modify selected parameters.
Properties for Network - EA-HVPLS - General dialog box fields
Field Description
Network Name See Network Properties - MPLS - General
Network Status Tab.
Network Type EA-HVPLS.
Validation Status See Network Properties - MPLS - General
Number of Elements Tab.
Contained Elements
Comments

Common Operations on Objects

You can perform a wide range of LightSoft and GCT operations on objects
selected in either the LightSoft main window map or in the Tree view. Most
operations can be performed from the menu bar, toolbar, or shortcut menus.
Some operations are available only from shortcut menus.
You can perform operations on secondary objects like individual ports by
drilling down in the tree. These operations include, for example, opening a
GCT session to the EMS shelf view for a port. Operations on Tree-selected
objects are performed from shortcut menus.
This section describes actions that are common to more than one object type.
Object specific actions are described in context in other sections.
LightSoft Operations
The following LightSoft operations are available for selected objects from the
LightSoft main menu, the toolbar, or from shortcut menus displayed by right-
clicking the object in the main menu map or tree view. Available options
depend on the object type and selected technology layer.
LightSoft Operations in shortcut menu
Expand, Expand in Expands an object to show the components of a group of
New View, Collapse objects or EMS or collapses objects into their group; see
Expanding or Collapsing Objects.
Properties Shows the properties of the selected object; see Viewing and
Editing Object Properties.
Show Group Shows the member objects of the group object; see Viewing
Members Group Members.
Current Alarms Shows the current alarms associated with the selected object;
see Viewing Related Current Alarms.
Show Trails Shows the trails passing through the selected object; see
Viewing Trails.
Delete Deletes the selected object from the LightSoft database; see
Deleting Objects.

Expanding or Collapsing Objects

When you expand a group of objects or an EMS, all the elements or groups that
belong to it are visible in the view as separate icons.
When you collapse an element that is associated with a group of objects or
EMS, the element, as well as all other components, are hidden and represented
in the view by a single group or EMS icon.
The Expand in New View function displays the information in a new window.
You can display the view on which it is based by clicking its header.
To expand a group of objects or EMS:

| Right-click the group or EMS you want to expand. On the shortcut menu,
select Expand to expand the group in the same window, or Expand in
New View to expand it in a new window.
To collapse an object into a group of objects or EMS:

| Right-click an element belonging to the group you want to collapse. On the
shortcut menu, select Collapse.
OR
| Click the element to select it. On the toolbar, click the Collapse Selected
Objects icon or the Collapse All Objects icon . The element
collapses into the group.

Viewing and Editing Object Properties

You can view detailed information about each ME, LE, group, UME, EMS, or
network, and edit certain fields.
When changing object names, LightSoft allows you to keep a primary LE name
in a technology layer either aligned with or different from that of its related
ME/UME in a physical layer (Physical or EMS), according to your personal
preference:
| If you wish to adopt different naming conventions for a primary LE versus
its ME/UME, change the LE name. The ME name will not be changed, so
the related objects will have different names. (Once LE and ME/UME
names are different, any further changes to the ME name are not reflected
in the LE.)
| If you wish a primary LE name to always be aligned with its corresponding
ME/UME, never change the LE name. Any change in the ME/UME name
is then automatically reflected in the primary LE.
NOTES:
A different procedure applies to EMS properties; see EMS
Properties.
LightSoft-modified object properties are not always
reflected at the EMS level. For more information, see
LightSoft Aspects of SR9700 MEs.
To view information about an ME, LE, group, or UME:

1. On the map in any topology layer, select the object whose information you
want to view.
2. On the LightSoft main menu bar, select Configuration > Properties.
OR
Right-click the object and select Properties on the shortcut menu.
OR

On the toolbar, click the Show Properties of Selected Object icon .

A dialog box opens displaying information about the selected object. See
the following sections for dialog box examples and field definitions:
ME Properties
LE Properties
Group Properties
UME Properties
EMS Properties
Network Properties
3. To edit information:
a. Edit fields that have a white background.
b. Click the Apply changes icon to save your changes. A

confirmation dialog box opens.
c. Click Yes to save the changes and end the edit session. (Clicking No
postpones the save, allowing you to make adjustments. When you are
ready, repeat from Step (b) to save the changes. Clicking Cancel ends
the edit session without saving changes.)
4. Click Close to close the Properties dialog box.

Viewing Related Current Alarms

You can view a filtered list of current alarms associated with a selected object.
For additional information, see Accessing Fault Management Windows.
To show the current alarms associated with an object:

1. Right-click the object.
2. On the shortcut menu, click Current Alarms. The Current Alarms
window opens showing the alarms on the selected object.
You can also display current alarms from an object's Properties dialog box by
clicking the Alarms icon on the dialog box toolbar. For more information
about object properties, see:
| ME Properties
| LE Properties
| User-Defined Group Properties
| UME Properties
| EMS Properties
Viewing Group Members

On the Map view you can highlight objects that are members of the same group
as the selected object.
To show objects that are members of the same group:

1. Right-click an object.
2. On the shortcut menu, select Show Group Members. The objects that are
members of the same group as the selected object are highlighted on the
Map view.

Viewing Trails
You can open the Trails List window to show the Trails pane filtered with the
trails traversing the selected object (an element or link). For more information,
see Performing Actions on Trails.
A trail type option is available when you select a single SDH or optical link
that lists only trails of the selected type. This option is not available from
Ethernet links or any multilinks or NEs. In those cases, all the associated trails
are listed, regardless of type.
To view the trails traversing an object:

1. Right-click the object (an element or a link).
2. On the shortcut menu, click Show Trails.
If the object is an individual link with SDH rates, a choice of high order
or low order trails opens. Select one.
If the object is an individual link with optical rates, a choice of optical

trail types opens. Select one.
The trails passing through the selected object (and of the selected type, if
applicable) are listed in the Trail List window Trails pane.

Deleting Objects
You can delete a selected ME or UME from the LightSoft database. The Delete
option is enabled for MEs and UMEs if there are no topology links or trails
using these objects. For more information, see Removing an Element from a
Link. The Delete function operates for MEs as allowed by the specific EMS
(see note below).
Delete is enabled for a secondary LE. This acts only to return its ports and any
associated links to the primary LE and to remove the secondary LE from the
view. Primary LEs cannot be deleted.
Deleting a group means "ungrouping" members of a group. When a group is
deleted, the individual objects that compose it are not deleted. For a specific
procedure for deleting a group, see Deleting Groups.
NOTE: An ME is deleted based on the way the Delete function

is supported by the corresponding EMS.
| If Delete through LightSoft is supported, the ME is
automatically deleted from the EMS and then from LightSoft.
| If Delete through LightSoft is not supported, or if the ME is
disconnected, LightSoft displays a message that the ME
cannot be deleted by the server. In this case, you must
manually make the delete in the EMS (by opening a GCT to
the EMS). After this is done, the ME is automatically deleted
from LightSoft.
| If a SYNCOM ME is represented in the EMS-SYNCOM
topology as linked to external elements on either side,
although the ME can be removed from links in LightSoft
using the procedure described in Removing an Element from
a Link, it may not be possible to subsequently delete it from
the topology using the LightSoft Delete command; contact
ECI Telecom customer support for assistance in such cases.
In rare circumstances, the ME will be marked as inconsistent in
LightSoft. After you remove the restricting condition, you can
perform the Delete again to deleted the ME from LightSoft.
To delete an object:
1. Select an object.
2. On the LightSoft main menu bar, select Configuration > Delete.
OR
On the toolbar, select Delete .

Retrieving Inventory Information from

LightSoft
You can print a report of equipment inventory information from LightSoft. The
report includes information about equipment corresponding to different
combinations of:
| a specific EMS
| a specific NE, or all NEs
For each NE, the report shows the NE's ID, name, and location, followed by the
associated equipment. The cards listed under an NE can either represent only
actual cards (real equipment in an NE shelf), or can also include cards with
expected type only. The report output can be formatted using your choice of
delimiter.
To retrieve inventory information:

| Run the following minimum parameters from the UNIX command line:
EqpInvnt.pl -h
EqpInvnt.pl -d X -e ems_name -n ne_name -a
EqpInvnt.pl (This final expression prints the CSV file to your UNIX
terminal.)
The following script options apply:
usage: EqpInvnt.pl [-d X] [-e ems_name]
[-n ne_name] [-a]
Where:
Command Description
-a Prints only cards with actual type (type not equal to
NONE). If this command is omitted, it will also print
cards with expected type only.
-d X The output report will use X as delimiter instead of spaces.
If this command is omitted, a CSV format is implied.
-e ems_name Prints information related to the specified EMS (for
example EMS_XDM_xx).
-n ne_name Prints information related to the specified NE (for
example, ManagedElement~~xxx). If this command is
omitted, information for all the NEs associated with the
EMS will be listed.

Example Output:
EMS EMS_XDM_910 XDM.z1-pink.60"
===================================================
NE ManagedElement~~1 "dk-XDM6"
---------------------------------------------------
"I1 SIM1_4/O " NONE "HW Undefined, SW Undefined" "N/A"
"I1 OTR1 1 " NONE "HW Undefined, SW Undefined" "N/A"
"A MXC-100 " MXC-100 "HW Undefined, SW 60.24" "N/A"
"A TMU 1 " TMU_L "HW Undefined, SW Undefined" "N/A"
"A NVM-C 2 " NVM-C "HW Undefined, SW Undefined" "N/A"
"A COM 3 " COM "HW Undefined, SW Undefined" "N/A"
"A1 SAM16_1 " NONE "HW Undefined, SW Undefined" "N/A"
"A2 SAM16_1 " NONE "HW Undefined, SW Undefined" "N/A"
GCT Operations
The following GCT operations are available for selected objects from the
LightSoft main menu, the toolbar, or from shortcut menus displayed by right-
clicking an object in the main menu map or the tree view. Actual options
available depend on the object type and the selected technology layer.
The windows that open and the associated procedure vary according to the
EMS. Not all functions are available for every EMS.
GCT operations in shortcut menu
Open Shows object windows from an EMS without having to start an
individual EMS session; see Starting/Closing a GCT session.
Current Alarms Shows current EMS alarms for an object without having to start
(EMS) an individual EMS session; see Viewing EMS Current Alarms
for an Object.
Software Enables you to update selected NEs resident software from the
Management EMS; see Updating NE Software.
Cross Connection Enables you to create or modify cross connects for a selected
ME or LE; see Creating and Modifying Cross Connects.
Ping Pings an object to determine whether it is connected to the
network and is active; see Pinging an Object.
Set Route Sets the EMS IP routing data that supervises communication
between the EMS and its managed NEs; see Setting EMS IP
Routing Data.
Set Printers Provides access to the EMS printer configuration window; see
Setting Printers.

Starting/Closing a GCT Session

You can start a GCT session without having to start an individual EMS session.
LightSoft features single sign-on between supported layers. Once logged in to
LightSoft, you automatically have access to managed EMSs through GCT
without providing additional login details.
The EMS window that is opened from LightSoft depends on the object from
which the GCT is requested. For example:
| Starting from an EMS opens the EMS main window.
| Starting from an ME or primary LE generally opens a shelf view. In some
cases, such as ECI Telecom's SR9700 family product line of Carrier
Ethernet Switch/Routers (CESR), the STMS (the SR9700 family EMS)
main window opens.
| Starting from a secondary LE (if all ports of the LE relate to the same card)
opens the card internals view. Otherwise, the shelf view opens.
When a user performs GCT to EMSs such as the STMS, security levels and
capabilities that apply at the EMS level may differ from LightSoft-assigned
levels. For more information, see Security Concepts.
NOTES:
In some EMSs, the initial GCT session may take several
seconds to start.
While working for an extended period in an EMS via
GCT, LightSoft may sense inactivity and automatic lock
or logout from LightSoft due to timeout. A popup
message appears one minute before the timeout is
triggered. Clicking Continue cancels the timeout. The
notice time before timeout can be modified by changing a
system file; contact ECI Telecom customer support for
assistance.
To view EMS information without exiting LightSoft:

| Double-click an object.
OR
From the Physical (EMS) layer, right-click an EMS on the map view or its
node in the topology tree, or in the relevant topology layer; right-click the
ME or LE in the map view or its node in the topology tree.
Select Open from the shortcut menu. The EMS main window, a shelf view,
or a card internals view appears (see details at the beginning or this
section). Work with this as described in the corresponding EMS user
manual.

You can also start a GCT session:

| From the EMS List window. For more information, see Accessing an EMS.
| From an object's Properties dialog box, by clicking the Open icon on

the dialog box toolbar. For more information about object properties, see:
ME Properties
LE Properties
User-Defined Group Properties
UME Properties
EMS Properties
To close a GCT session:

| From the System menu, select Close GCT Session.
Viewing EMS Current Alarms for an Object

You can view the EMS Current Alarms window for an object without having
to start an individual EMS session.
To view EMS current alarms:

OR
From the relevant topology layer, right-click an ME or LE in the map view
or its node in the topology tree.
2. Select Current Alarms (EMS) from the shortcut menu. The Current
Alarms window of the corresponding EMS opens. View the alarms as
described in the corresponding EMS user manual.
Updating NE Software
You can open a GCT to an EMS SW Download window to update selected NE
resident software from the EMS.
To update NE resident software:

OR
From the relevant topology layer, right-click an ME or LE in the map view
2. Select Software Management from the shortcut menu. The SW
Management window of the EMS opens. Complete the action as described
in the corresponding EMS user manual.

Creating and Modifying Cross Connects

You can open a GCT to the EMS XC Browser window where you can create
or modify cross connects for a selected ME or LE.
To create or modify cross connects:

1. From the relevant topology layer, right-click an ME or LE in the map view
2. Select Cross Connection from the shortcut menu. The XC Browser
window of the EMS opens. Complete the action as described in the
corresponding EMS user manual.
Pinging an Object
You can ping an object to determine whether it is connected to the network and
is active. As the ping executes, ping data appears in the dialog box.
To ping an object:
1. Select a topology layer.
2. Select an object on the Map view and on the menu bar, select System >
Ping.
OR
Right-click an ME or LE in the Map view or right-click its node in the
topology tree. On the shortcut menu, select Ping. A Ping dialog box opens;
the ping executes and data is posted to the dialog box.
3. To stop the operation, click Stop. To restart the operation, click Start.

Setting EMS IP Routing Data

This function opens a UNIX window and activates the Set Route script for
setting EMS IP routing data that regulates the communication between the
EMS and its managed NEs.
Contact ECI Telecom customer support for further information about this
utility.
To set EMS IP routing data:

1. Select the Physical (EMS) topology layer.
2. Select an EMS on the Map view.
3. On the LightSoft main menu, select System > Set Route.
Setting Printers
This function enables you to access the EMS Printer Configuration window,
where you can set the standard printer device.
To set printers:
1. Select the Physical (EMS) topology layer.
2. Select an EMS on the Map view.
3. On the LightSoft main menu, select System > Set Printers.

5
Topology Links and Ports
In this chapter:
Overview ......................................................................................................... 5-1
Topology Link Concepts ................................................................................. 5-1
Viewing Topology Link Information .............................................................. 5-6
3
Creating Topology Links ................................................................................. 5-9

3
Deleting Topology Links ............................................................................... 5-20

3
Managing NEs in Topology Links ................................................................ 5-20

3
Maintenance Operations on Links ................................................................. 5-34

3
Link Properties .............................................................................................. 5-34

3
Port Properties ............................................................................................... 5-51

3
Viewing Resource Availability on Links ...................................................... 5-65

3
Overview
Topology links (called topology or internal links) represent the available
transport capacity between network nodes over which trails that carry traffic
can be defined. A topology link joins two ports of different objects (MEs, LEs,
and UMEs) and an internal link joins two ports within the same object.
Topology Link Concepts

The following sections provide some key topology link concepts. Other
concepts are explained in context.
| Multilinks
| Link Direction
| Physical Links and Virtual Links
| Shared Risk Link Groups (SRLGs)

Topology Links and Ports LightSoft User Manual
Multilinks
On all LightSoft map views, lines between MEs, LEs, UMEs and/or groups
denote the presence of one or more topology links between the objects. These
lines are referred to in this manual as multilinks.
SDH multilink line widths vary according to the number of links and link rates
they represent. The actual number of links in a multilink line (when higher than
one) is indicated by a number inside a square .
Multilinks that are selected appear highlighted. When MEs are moved on a
map, the multilinks follow them to their new location.
The multilinks can be expanded to show the actual links between or within the
elements. You can also access information and functions for each specific link
within the multilink; see Viewing Topology Link Information.
The color of a multilink denotes its alarm state, indicating the most severely
alarmed port of all associated links. (Similarly, when a multilink is expanded, a
specific link's color refers to the most severely alarmed port at either end of that
link.) For a description of the alarm state colors and their meaning, see Object
Status Color Indications.
An internal multilink link symbol adjacent an object icon indicates the

presence of internal links within the object.
ASON links are identified in map windows with an icon on the multilink line
; see LightSoft ASON Support.

LightSoft User Manual Topology Links and Ports
Link Direction
Topology links may be either unidirectional or bidirectional. A unidirectional
link transports traffic in one direction; a bidirectional link transports traffic in
two directions. Typically, SDH links are bidirectional and optical links are
unidirectional, although there are exceptions. Directionality of the topology
link is determined as follows:
| If both selected endpoints are bidirectional, the link is bidirectional.
| If both selected endpoints are unidirectional (one transmit and one receive),
the link is unidirectional.
| If one endpoint is unidirectional and the other is bidirectional, the link is
unidirectional.
Physical Links and Virtual Links

Being a multitechnology layer manager, LightSoft automatically recognizes the
relationships between technology layers representing multitechnology ports on
every layer on which they appear. It is also useful that links between ports from
underlying layers on which trails are provisioned also be visible on the current
layer view. For this reason, LightSoft supports two types of links:
| Physical links: Physical views show all LightSoft- or EMS-defined
elements and their related physical links, which were either created in
LightSoft (as described in this section) or discovered automatically from an
EMS. Technology views show the objects and physical links pertaining to
the displayed view.
| Virtual links: Technology views show objects and links from their own
technology layer, as well as objects and logical connections provisioned in
underlying technological layers. These logical connections are represented
as "virtual links" in the current technology layer - a special type of
topology link that is logical, not a physical connection on the native layer.
LightSoft automatically creates virtual links in one technology layer as a
result of trail creation actions in the underlying technology layer.
For example, MoT trails (that are SDH, providing connectivity between
two MPLS ports) are the virtual links on the ETH/MPLS layer used for
tunnel creation. Similarly, LightPath (LP) trails between SDH ports may be
displayed on the SDH layer as virtual links if all criteria are met. For more
information about virtual links in the context of trails, see Trails and Virtual
Links.
For information about trails and trail creation, see the sections starting from
Managing Traffic.
You can work with virtual links in the technology layers in the same way as
you work with physical links.

Shared Risk Link Groups (SRLGs)

SRLGs refer to situations where links in a network share a common physical
attribute, such as fiber duct or equipment cage, and are exposed to the same
vulnerabilities. If an event involving the common entity should occur, all the
links of an SRLG could potentially be disrupted.
The presence of SRLGs and other types of resource sharing have implications
for LightSoft pathfinder trail and tunnel route selection processes. For details,
see SRLG and Other Shared Resource Minimization in Path Selection, and
SRLG Avoidance in Bypass Path Selection.
When SRLGs are used to define ducts, LightSoft generates a duct failure alarm
if all links associated with the same duct fail. The Alarm Correlation feature
must be installed and enabled; see Alarm Correlation.
How SRLGs are specified in LightSoft

The shared resources used by a link can manually be coded into the SRLG
parameter in the Create Topology Link dialog box or subsequently
added/removed using the SRLG parameter in the link properties; see Properties
for Link - SDH. When the same SRLG code is identified with multiple links,
these links are considered to share the associated resource.
SRLGs are also coded automatically to a link for use by MPLS tunnels
whenever an MoT trail is created that traverses the link - represented by an
"automatic SRLG" (with a unique SRLG ID) in the SRLG parameter of the link
properties. This type of SRLG is automatically removed from the link if the
MoT trail is subsequently deleted. Automatic SRLGs on a link cannot be
manually added or removed.
For virtual links, the link properties SRLG parameter is read only and displays
the accumulated SRLGs of the underlying technology links.

Viewing SRLG and Other Diversity

Information
You can view diversity in the network in a number of ways:
To view or add SRLG associations for an SDH or optical link

or MoT virtual link:
| The Link Properties window Advanced tab shows a list of SRLGs
associated with the link. User-defined SRLGs can be added or changed as
needed; see the SRLG (Ducts) parameter in Properties for Link - SDH
Advanced Tab. For MoT virtual links, manual SRLGs are added at the
physical or SDH level and viewed in the Properties for Link - MoT Virtual
Link SRLGs Tab.
To view links that share the same user-assigned SRLGs as a

selected link:
| In any layer (except Ethernet), right-click a link and select Show SRLG
from the shortcut menu. The links that share the same user-assigned
SRLGs and their associated endpoint MEs are highlighted on the map.
To view resource sharing information for a trail:

| The Trail Properties pane Protection tab shows information about each
type of resource sharing for a trail (number of shared MEs, links, SRLGs,
and cards), regardless how the trail was created. For details, see the
Protection tab parameters in Trail Properties Pane.

Viewing Topology Link

Information
Multilinks can be expanded to show the actual topology or internal links
between/within elements and their port endpoints. The specific NEs at the link
endpoints can be shown, even when they are within nested groups (regardless
of the depth of nesting that may apply). You can also access information and
functions for each link.
To view information about individual links in a multilink:

1. On any topology or technology layer, on any map view:
Right-click a multilink between two objects.
OR
Right-click an object icon showing an internal multilink icon .

2. Select Expand or Internal Links. The Actual Links between Two
Elements or Internal Links View dialog box opens with a list of the links
represented by the multilink. (You can also expand a multilink between
different objects by just double-clicking the multilink.)
The Actual Links Between Two Elements dialog box top-of-window
diagram shows the endpoints of the multilink as a whole, whether an endpoint
is an element or a group. When an endpoint is a nested group, the name of the
overall parent group is shown. If the selected multilink has an endpoint within a
group, an Element column becomes available to identify the element name of
each specific link's endpoint.
The Internal Links View dialog box top-of-window diagram shows a single
element.

Information supplied for each link or internal link in the multilink
Column Description
Element1 This column appears only if the endpoint at one end of the multilink is
a group. It shows the element name of the specific link's endpoint.
Port1 Name of a specific link's endpoint.
Link Name User-assigned link name. By default it is the name of the first and
second endpoints in alphabetical order.
Element2 This column appears only if the endpoint at the other end of the
multilink is a group. It displays the element name of the specific link's
endpoint.
Port2 Name of a specific link's endpoint.
Rate Rate of the link (may be different from the rate of the port).
Media Port media type: Electrical, Optical, Virtual, or N/A.
Protection Type of link protection (for example, MS-SPRing). On physical
topology links, the protection scheme is from the link itself. On virtual
links, it is derived from the underlying trail.
An Availability dialog box for the current topology layer (a variation of the
Actual Links between Two Elements dialog box) shows each link color coded
according to its availability, and includes an Availability column that shows the
availability in absolute terms. For more information, see Link Properties.
To access other link information and functions:

| Right-click a single link, or open the Actual Links between Two
Elements or Internal Links View dialog box of a link or multilink, right-
click a Link Name to open a shortcut menu with options listed in the
following table.
You can also access information about a link's endpoint port by right-
clicking a Port field and selecting Properties. For more information, see
Port Properties.
Topology link shortcut menu options
MS-SPRing Opens a GCT to the MS-SPRing configuration properties in the EMS

Configuration for a selected individual link (when supported by the EMS).
Show Trails Opens the Trails List window filtered with the trails passing through
the selected object (single link, multilink, or element). For more
information, see Viewing Trails.

Show (ETH/MPLS view only) Opens the following submenu options:

Tunnels | All Tunnels: Shows all tunnels associated with the selected link in
a new Tunnel List window.
| Protected Tunnels: Shows all protected tunnels associated with
the selected link in a new Tunnel List window.
| Bypass Tunnels: Shows all bypass tunnels protecting the selected
link in a new Tunnel List window.
Show Ring In the map view highlights all links that share the same ring name as
the current link, for example, all links participating in a specific MS-
SPRing scheme. (If no ring name is defined in the link properties, a
"No ring was found" message appears.)
Expand Ring In a new view shows all links that share the same ring name as the
in New View current link, whether or not those links are present in the current view.
(The current view may be composed of selected objects opened in a
new view with the Open in New View function.) The elements that
are endpoints to those links are also shown, along with any other links
extending from those elements (which might not share the same ring
name). See Ring Name in Properties for Link – SDH General Tab.
Show SRLG On the map highlights all the links that have same SRLGs as the
selected link; see Viewing SRLG and Other Diversity Information.
For more information about SRLGs, see Shared Risk Link Groups
(SRLGs).
Show Sub Opens a new view with all links that belong to the same FD network
Network and have the same subnetwork ID defined for their ports. Valid for
Ethernet links only.
Trail Opens the Trail Consistency Indicator window filtered for the
Consistency selected link. (A virtual link is filtered by the associated trail.) For
more information, see Synchronizing Trails.
Maintenance Opens the Maintenance Operations window, which enables you to
Operations perform maintenance operations on links (for example Loopback, AIS
and RDI) to diagnose network problems. For more information, see
Maintenance Operations on Links.
Delete Deletes the selected topology link. This option is available only for
LightSoft-created links and in accordance with validation rules (for
example, no trails should be present in the link to be deleted). For
more information, see Creating Topology Links.
Current Opens the Current Alarms window for the alarms affecting the link
Alarms state (its endpoints in the case of a physical link). For more
information, see Accessing Fault Management Windows. When this
option is selected from the multilink shortcut menu, LightSoft displays
alarms for all links associated with the multilink.
Properties Shows the properties of the selected topology link, see Link
Properties.

Creating Topology Links

You can create physical topology links in any topology layer (Physical, OTN,
SDH, or Ethernet). A link can join two ports of different NEs (MEs, LEs, or
UMEs) (topology link) or two ports of the same ME/LE/UME (internal link).
The link creation process also allows you to automatically provision the link
with VC-4 server trails. For example, an STM-16 link can be created with 16
VC-4 server trails.
To create a topology link, you first select two objects (MEs, LEs, or topology
groups) between which the link should span, or a single ME/LE within which
an internal link should span. Then you select the ports in the MEs/LEs that will
serve as the link's endpoints. You can optionally assign values to the link
attributes.
The link processing may take some time. For your convenience:
| You can define several topology links at a time to be processed
concurrently. The additional topology links' endpoints can be selected from
either the same MEs/LEs or other MEs/LEs in the currently selected group.
| While the Create Link processing is in progress in the background, you can
perform other, unconnected LightSoft actions. The only restriction is that
you cannot open another instance of the Create Topology Link dialog
box.
Once you have created topology links, they can be edited; see Link Properties.
In addition to creating topology links manually as described in this section,
topology links between NEs of the same EMS can be created automatically by
acquisition from the EMS during upload, or by notification when the EMS
supports links (upload and notification) in its MTNM interface. (Links between
NEs of different EMSs must be created manually from LightSoft.)
NOTES:
ASON-protected trails require topology links with STM-16 or
STM-64 rates between ASON enabled NEs. For more
information about ASON, see LightSoft ASON Support.
If a link intended for ASON is created in LightSoft, it must be
set as ASON in the EMS before use in LightSoft.
LightSoft automatically performs the link and trail
infrastructure changes consistent with port reassignments
from STM-1 to STM-4; see Link and Trail Adaptation to Port
Upgrade.

Creating a Topology Link

You create topology links in the Create Topology Link dialog box; see Create
Topology Link Dialog Box. The dialog box More button (enabled after
endpoints are selected) extends the window to include advanced fields.
To create topology links:

1. In the topology view or in the topology tree, select the object(s) that the
links should span:
Select two objects (MEs/LEs, UMEs or groups). While making the
second selection, hold the SHIFT key (if you are selecting from the
map) or the CTRL key (if you are selecting from the tree).
OR
If you are creating an internal link, select a single ME/LE.
2. On the LightSoft main menu bar, select Configuration > Create >
Topology Link.
OR
In the main toolbar, click the Create Topology Link icon . The
Create Topology Link dialog box opens. For information about the fields,
see Create Topology Link Dialog Box.

The two dialog box panes display details of the two selected objects in a
hierarchical tree structure. If only one object is selected, for example a
single ME/LE for an internal link, the two panes would both show details
of the same object.
3. Define a link:
a. In the Select Type field, select a port type. The endpoints in the panes
are filtered according to the available ports in each object that are
compatible with the selected port type.
Menu settings can be selected to help you connect ports with similar
protection types, frequencies, or other attributes. For more information
about these and the parameters for the link, see Create Topology Link
Dialog Box.
b. In the Label field, enter a link label. The default label is a
concatenation of the endpoints names.
c. Drill down in the tree and select endpoint resources/ports from each
pane.
NOTE: Endpoints are disabled for various reasons.

If you click on a disabled port, the Status field shows
why the ports cannot be connected. The most frequent
reasons are:
| Port is not compatible as to type or rate with an
already selected port.
| Port is not consistent. The Consistency State field of
port properties windows shows the consistency state
of ports; see the parameter description in Properties
for Port – SDH General Tab.
| Port is logical. Logical (nonphysical) data ports
cannot be connected; see the description of logical
ports in Supported ETH/MPLS Port Types.
| Port direction (Src or Snc ) is not
compatible with the direction of an already selected
port (a Src/Snk pair must be selected.)
d. Select the Build VC-4 Server Trail checkbox if you want the server
trail to be built automatically.

4. To set advanced parameters, click More. The Link Attributes pane opens
in the lower part of the dialog box and the More button changes to Less.
For information about the fields, see Create Topology Link Advanced
3
Attributes.
a. Click Path Trace Configuration to configure SDH path trace

parameters. The Path Trace Configuration dialog box opens. For
more information, see Path Trace Configuration Dialog Box.
To close the advanced section, click Less. When you create a link using
only the basic parameters, LightSoft automatically fills the default
values.
NOTE: The Path Trace Configuration button is available

only if both link endpoints support J0 handling for SDH and
you are creating a link of type SDH between the ports. While
you are in the Path Trace Configuration dialog box, you
can set the attributes for both endpoints by clicking Apply.
Settings are applied even if you do not click Apply in the
Create Topology Link dialog box.

b. Click Apply to set the attributes for both endpoints and create the link.
The link creation processing begins.
The Progress bar at the bottom of the dialog box indicates that processing is
in progress.
The Status field shows ongoing changes on selected ports.
NOTE: A Warning message may be displayed with a

reason, enabling you to make the required correction and
click Apply again.
In some cases a Failure message may be displayed with a

reason, requiring you to restart the process.
The following are some circumstances that may cause a
Warning or Failure:
| Protection group incompatibility; see Protection Group
Object (PGO) in Relations between Ports or Cards.
| Forward Error Correction (FEC) incompatibility; see
Forward Error Correction (FEC) in OCH Trail Endpoint
Validations.
| Frequency (Channel) incompatibility; see Channels.

5. If you want to create another link which involves the same elements, either
while or immediately after the requested link is being processed, repeat all
the substeps of the last step. You do not have to wait for a link's processing
to finish.
If you have no more links to create, you can perform unrelated LightSoft
actions while the remaining processing is going on. (The Close button is
disabled until the conclusion of processing. You can minimize the dialog
box until all processing has been completed.)
6. At the conclusion of each link's processing, a Create Link conclusion
message appears, describing the new link's endpoints and layer.
7. Click OK to close each instance of the message.

8. When all the links have been processed, the Create Topology Link dialog
box Close button becomes enabled again. You can click Close to close the
dialog box.
9. The graphical representation of the link is displayed in all the relevant
topology views. In the case of an internal link, the object is shown with an
internal link icon .

Create Topology Link Dialog Box

This section describes the Create Topology Link dialog box, used to create
topology and internal links; see Creating a Topology Link. The dialog box
panes show the details of slots and ports of two selected objects (MEs, LEs,
UMEs, or groups). To create the link, select from each panel the ports that
represent the endpoints.
In this example, one of the objects selected is a group that contains two MEs. If
only one object is selected, for example a single ME/LE for an internal link, the
two panes would both show details of the same object.
The directionality of a unidirectional endpoint is indicated in the tree with a

or depending on whether it is a transmit or receive endpoint. A
bidirectional endpoint has no indication since this is the default value.
Ports on which links are already present, so are unavailable for the current link, are
shown as grayed, with "white" icon .
Some circumstances would cause a port to be disabled and unavailable for
selection as an endpoint. (Clicking on the port shows the reason in the Status
field). For details, see Step 3 in Creating a Topology Link.
Some circumstances would cause a Warning or Failure message upon clicking
Apply, which require you to correct selections or restart the process. For
details, see Step 4 in Creating a Topology Link.
The following toggle settings are available from the dialog box View and
Settings menus. They are used to turn information about endpoints on or off in
the tree views, or to display the selected rate the next time the window is opened.

Hide/Show toggle settings in Create Topology Link dialog box
View
Show rate Displays the rate of the port.
Show Band Displays the band used by the port. Applies to OTN
multiplex section ports only.
Show Protection Group Indicates whether the port is defined as the parent of a
protection group, for example, MS-SPRing.
Show Frequency Shows the current tuned frequency of an optical port.
Settings
Save Last Selected Rate Saves the rate last used. This rate will be used when the
window is opened again.
Create Topology Link dialog box fields
Field Description
Select Type Select a type of port. This is a filter for the rates. It can be
selected and changed as required, and opens with the last
selected rate type.
If you select only MEs as endpoints, you can select a rate
which then filters out the ports that are not of the selected
rate.
Label Name of the link; by default, a concatenation of the two
port names. Can be changed as required.
Build VC-4 Server Trail When selected, VC-4 server trails are automatically built.
Status Shows information about ongoing changes on selected
ports. For example, in the link creation process, the
connection state of ports will change. As this occurs, the
message "One of the selected ports was updated: (port
name)" is indicated.
This field also shows why ports cannot be connected. For
details, see Step 3 in Creating a Topology Link.
Progress bar Indicates that processing is in progress. While this is
happening, the dialog box Close button is disabled.
However, unrelated LightSoft operations may be
performed concurrently.

Create Topology Link Advanced Attributes

Advanced attributes are displayed by clicking the More button in the Create
Topology Link dialog box. The button becomes enabled after endpoints are
selected.
Create Topology Link dialog box - More fields
Technology Technology layer of the link. Read only for all port types. A rare
Layer exception is when a selected port exists in more than one technology
layer, in which case you must select the technology layer.
Media Type The media type of the selected ports: Electrical, Fiber, or Virtual.
(Read only)
Media Subtype Selection of media subtypes from the list, according to the media type.
You can also enter your own text.
Length The length of the link in kilometers or miles. When using the Length
(km/mile) constraint, this value is used for path searching optimization to
determine the shortest path.
Protection Type of link protection, for example, MS-SPRing, MS, external
protection, or unprotected. If external protection is used, specify the
type.
SRLG (Ducts) Shared Risk Link Group. Scrollable entry fields allow you to specify
the shared resources for the link. The Pathfinder algorithm uses this
information when calculating diversity paths; see SRLGs on Links.
User-defined SRLGs can be added or removed in the link's properties;
see Properties for Link - SDH.
Ring Name Name of the ring. If the ring involves MS-SPRing protection, the ID of
the ring from the EMS is displayed. In this case the ring name is read
only.
Assigned Cost Enter a value for the cost based on your local evaluations of cost on a
(1-1000) nondenominational scale of 1-1000. A low number indicates a less
expensive link. When using the Cost constraint, this value is used for
optimizing trails; the system selects the least expensive links for the
trail.

Quality Select the quality of the link, from 1 (best quality) to 5 (worst quality).
(Best 1..5 When the Quality constraint is selected, this value is used for
Worst) optimizing trails.
Dispersion Dispersion rate in ps/nm. User-entered value, not calculated.
(ps*nm/km)
Span Loss (dB) Span loss in decibels. User-entered value, not calculated.
Comments Free-text for entering information about the link.
Path Trace Enables you to set the J0 values of endpoints of a physical connection.
Configuration For more information, see Path Trace Configuration Dialog Box.
button

Path Trace Configuration Dialog Box

The Path Trace Configuration dialog box (accessed by clicking the Path
Trace Configuration button in the advanced Create Topology Link dialog
box), enables you to set the J0 values of endpoints of a physical connection. It
is only available if you are creating a link of type SDH between the ports and
both endpoints support J0 handling.
Path Trace Configuration dialog box fields

Selection/FieldDescription
Path Trace Select whether to enable path trace monitoring or not. This is the J0
Monitor section trace (affects RS-TIM/TIM-S alarm detection).
Path Trace Actual value of the path trace (J0) as read from the element. This value
Received is not automatically updated. Click Refresh to obtain it from the ME.
Path Trace Expected path trace string:
Expected | Current Value – value presently in the element. (Read only)
| Set New Value – enables you to set a new value.
If one of the fields is shaded, it indicates the current value saved for
the link. You can enter a new value in the Set New Value field.
Modifying this value updates the Set value in the matching pane of
the other endpoint. Modifying the Expected in one port will change
the Sent in the other and vice versa.
The length of Path Trace Expected and Path Trace To Send is 15
characters.
Path Trace to | Current Value – the value presently in the ME. (Read only)
Send | Set New Value – enables you to set a new value.

Deleting Topology Links

The following procedure describes how to delete topology links that are no
longer required. The links to be deleted should be empty of trails.
Deletable links should be LightSoft- or EMS-created. In the latter case, they
should be inconsistent and show the inconsistency reason "Deleted from EMS".
This usually happens if a link with a trail in LightSoft is deleted from an EMS.
To delete a topology link:

1. In a topology view, select the multilink from which you want to delete a link.
2. Right-click the multilink. On the shortcut menu, select Expand. The
Actual Links Between Two Elements dialog box appears.
NOTE: If the selected link has an ME/LE group on one of

its sides, right-clicking and selecting Expand will display its
components. You must then right-click and expand the
specific multilink you want to delete.
3. Select the links you want to delete. Right-click and select Delete on the
shortcut menu.
Managing NEs in Topology Links

You can insert an ME or an UME into an existing topology link or seamlessly
disconnect it from a link, either in preparation for its insertion in some other
link or removal from the network. An inserted UME can be useful for
maintaining accurate network topology.
NOTES:
When performing the actions described in this section, be
sure to coordinate with your co-workers to avoid other
users defining trails in the same area.
The insert and remove processes may be traffic-affecting.
After an NE is inserted/removed to/from links, the links
that were originally created in the EMS system (one link
following the Insert procedure, or two following the
Remove procedure, which will be unnecessary), must be
manually deleted through the EMS. (EMS-created links
cannot be removed through LightSoft.)
For cases not covered by the Insert and Remove ME/UME
features, please contact ECI Telecom customer support.

Inserting Elements into SDH Links

You can insert an ME or UME into an existing SDH link. New links are
created, trails on the new link are properly configured, and the old link is
deleted. There is no need to manually delete or edit trails. XC changes
corresponding to all trails going through the link are automatically downloaded
to an ME via its EMS.
Short VC-4 server trails are automatically split (terminated) in the inserted
object. Long VC-4 server trails and other high order trails are defined as
through trails in the new object. LightSoft also enables you to split long trails.
For more information, see Splitting a Long Trail. (Short trails are trails with
termination points at adjacent objects to the one being inserted. Long trails are
trails originating in more distant elements.)
When an object is inserted into a link, LightSoft performs the following
sequence of actions:
1. Creates two new topology links to the ports of the inserted object.
2. Creates new VC-4 server trails on the new links, and downloads the XCs
on the MEs being inserted to its EMS.
New VC-4 server trails are only created if the old link has short VC-4
server trails with endpoints on the objects immediately adjacent to the one
being inserted. Long VC-4 server trails are left as transit cross connects in
the inserted element.
NOTE: For SDM-16 NEs with low order XCs, the

procedure described in this section creates high order XCs. If
low order XCs are needed, this procedure must be followed
by an additional procedure to reinstate the low order XCs. In
the case of SDM-4 and SDM-1, any low order XCs that were
present are automatically reflected and require no further
actions. For more information, see Provisioning Low Order
XCs for SDM-16 following Insert to a Link.
3. Moves existing high order (VC-4, VC-4-4c, and so on) and low order
(VC-12, VC-3) traffic from the old to the new topology links.
4. Removes the old topology link.

Insert ME Preconditions
The following conditions apply to the insert procedure:
| The selected ports for the insert must be the same rate as the intended link.
Otherwise the ports will not be enabled for selection.
| The object may be part of the LightSoft topology as long as the two ports
used as endpoints for the new links are available.
| Already-defined XCs can use these ports as long as there are no conflicts
with the new XCs to be created.
This procedure is not suitable for inserting NEs into non-MS optical links, for
example, between a transponder and a port of type SDH.
NOTE: This procedure may affect traffic. To prevent a

possible impact on traffic, it is recommended to manually
switch traffic to the alternate path:
For SNCP-protected trails, switch all trails from the link
using the Path Protection Switch window. For more
information, see Path Protection Switching.
For MS-SPRing traffic, apply EMS Force actions on the
nodes adjacent to the target link to switch traffic off the
link before inserting the ME.
The operation is non-traffic-affecting for trails that are
protected elsewhere in the network. For more information,
consult your EMS User Manual.

Insert ME/UME Procedure
To insert an element into a link:

1. Select the Physical (Site) topology layer.
2. On the topology map, select the element to insert and the link or multilink
where it will be inserted. (Click Shift while selecting the two objects.)
3. On the LightSoft main menu, select Configuration > Modify > Insert
ME/UME. An error message may appear if existing circumstances prevent
the operation.
4. If a multilink was selected, the Insert Into Link dialog box opens.
Highlight a link and click Select.

5. The Insert ME dialog box opens.

An error message may appear if existing circumstances prevent the
operation.
Ports of the neighboring connected objects are automatically selected, so

the available ports on the "to be inserted" object are filtered by rate.
6. Specify how the insert will be performed:
a. On the left and right panes, expand the trees and select a port in each
tree.
b. (Optional) The link labels (created by default) can be modified as
required.
c. (Optional) Modify the attributes of the two links.
Click More to expand the Insert ME/UME dialog box to show two
tabs with link attributes: Link1 for the link connecting the left port, and
Link2 for the link connecting the right port.
The fields are the same as the More pane in the Create Topology Link
dialog box. For a description of the fields, see Create Topology Link
Dialog Box.
Each tab initially shows the attribute values of the link to be replaced.
You can change the values for the new links.
NOTE: For MoT links, SRLG names can be removed or left

as is. New SRLGs cannot be added.

7. (Optional) In the Insert ME/UME dialog box, click Validate to verify that
the XCs can be created in the inserted element. If a warning appears, this
may indicate a precondition that was not present, such as time slot
interchange in the NE to be inserted or trails existing in the element.
8. Click Apply. Validate is also automatically performed, whether or not it
was performed before. If a warning appears, check that the link selections
are appropriate. Then click Apply again.
9. A warning appears that the operation may affect traffic. Click OK.
Depending on the volume of trails that need to be created, the operation
may take a few minutes.
The Progress bar at the bottom of the window indicates that processing is in
progress.
10. After the processing is completed, a Succeeded message appears. Click
OK.
11. Click Close to close the Insert ME/UME dialog box. The ME or UME is
now inserted in the selected link.
12. If the original link involved SYNCOM equipment at both ends (SYNCOM
- SYNCOM link), delete the original link from the link list in the EMS-
XDM in order to avoid notification to LightSoft for this link.
Other original link configurations do not require intervention at the EMS
level.
Insert Troubleshooting
If a failure is encountered, perform the following steps:
1. Reconnect all VC-4 trails. Do not start the insert if there are failures.
2. Verify that the NE to be inserted is synchronized (although the insert will
not start if not).
3. The insert can be started even if flex, incomplete, or inconsistent trails are
present, since the operation will skip these trails. However, we recommend
fixing the condition before the insert as part of normal network
maintenance.
4. If a problem occurs during the insert with any number of trails, a specific
failure message with the failed trail's ID is displayed. In that case, open the
trail list for that link and:
Look for inconsistent trails and admit them.
Look for incomplete trails and reconnect them.
Look for failed trails and reconnect them.
If reconnection fails, admit the trails.

Provisioning Low Order XCs for SDM-16

following Insert to a Link
When an SDM-16 element is inserted into a link using the automatic procedure
described in Inserting Elements into SDH Links, high order XCs are
automatically created within the NE. If low order XCs were present in the NE
prior to the insert procedure or are otherwise needed, they must be created by
an additional procedure. This involves:
1. Replacing the NE's high order XCs with appropriate low order XCs. The
low order XCs must be created in the NE with the same pattern of TU
numbering and main/protection path types as are present in the high order
trails on either side of the NE.
2. Splitting the high order pipe on the NE, creating two high order
terminations in place of the high order XCs that were previously traversing
the NE.
3. Provisioning low order XCs within the NE via the SYNCOM eEM system.
The procedure described in this section is only required for SDM-16 NEs. In
the case of SDM-4 and SDM-1, any low order XCs that were present are
automatically reflected and require no further actions.
To provision low order XCs in SYNCOM SDM-16 after insert

to a link:
1. Delete the high order trail in EMS-SYNCOM, and create two high order
trails that terminate in the new NE.
2. Create low order trails with the correct path type (protection or main),
making sure that it is consistent with other aspects of the topology
following the insertion. Use the following topology in EMS-SYNCOM:

3. If the trails in EMS-SYNCOM have their original labels (if you

used FailTrail before), do the following in order to create the correct path
(main/protection) in the NE:
a. Run the script newFixLabel -p -c with the saved configuration
file name (from Deleting the Topology Link, Step 1) and the extension
“.labels”. For example, for the saved configuration file name
XXXX.YYYY, the required script will be
newFixLabel -p -c XXXX.YYYY.labels.
b. Use the EMS-SYNCOM Trails list to check whether the labels were
updated for the reconstructed client trails.
c. Run TrailLabel2MTNMLabel and then
updateCtpMtnmUserLabel.
d. Force full upload of the relevant MEs in LightSoft.

Removing an Element from a Link

In a dynamic network, MEs and UMEs must sometimes be placed differently
in the topology or removed from service and deleted from the network. You
can seamlessly disconnect an ME and UME from a link, either in preparation
for its insertion in some other link or removal from the network. This section
describes how to automatically replace the two links on either side of an NE
with a single direct link connecting the NE's adjacent neighbors and bypassing
the NE, while still retaining all associated trails and services.
If the NE is connected by additional pairs of links, these can also be removed
by repeating the operation. After all links are removed, the NE becomes a
standalone element. The NE can then either be reconnected to the topology in
another way, or deleted from the network.
You can either automatically delete the XCs (SNCs; subnetwork connections)
associated with the old connection, or keep them intact:
| If you plan to link the element to the topology using the same ports, you
can opt to keep the old SNCs intact. The ports then remain available in the
EMS for connection to a new topology. Keeping the SNCs also allows the
process to run faster.
| If you plan to use different ports, or remove the NE from the topology, it
may be useful to automatically delete SNCs at the same time that the links
are removed from the NE. As well as freeing resources, this avoids EMS-
LightSoft conflicts and the generation of many TCIs (on SNCs that are in
the EMS and not yet admitted to LightSoft).
Before performing the procedure:
| Release maintenance operations on trails or other objects involved in the
Remove process. Maintenance operations are persistent until they are
released. For details, see Maintenance Operations.
| Remove services that terminate at the NE interfaces. As well, timing, DCC
trails, OSPF, DCC control, and DCN supporting entities (such as clear
channel) must be handled so as not to impact the network when the NE is
removed. However, trails that traverse an NE must not be deleted and the
services they supply must be preserved. These include service trails that
traverse the NE and server trails that traverse it as well as terminate at its
interfaces.
Removing an NE from MSP Linear protected links is not supported directly. If
any links are MSP Linear protected, you must first manually unprotect them
before performing the NE removal procedure.
If a SYNCOM ME is represented in the EMS-SYNCOM topology as linked to
external elements on either side, even though the ME can automatically be
removed from links in LightSoft, it may not be possible to subsequently delete
it from the topology using the LightSoft Delete command; see Deleting
Objects. Contact ECI Telecom technical support for assistance in such cases.

NOTE:
Removing an NE from a link may fail for the following
reasons:
A trail provides SNCP protection on the NE (diverging
into two paths at this NE).
A low order trail terminates on the NE.
A high order non-classified (flex) trail terminates on the
NE.
A matching high order trail on the link at the other side of
the NE is not available.
To remove an element from a link:

1. Select the Physical (Site) topology layer.
2. On the topology map, select the element to remove from links.
3. On the LightSoft main menu, select Configuration > Modify > Remove
ME/UME. The Remove ME/UME dialog box opens.
An error message may appear if existing circumstances prevent the
operation.

4. Specify how the operation is to be performed:

a. On the left and right panes, select a pair of links, one on each side of
the element, from which the element should be detached. These links
will be replaced by a single link between the neighboring elements.
In the map view, the selected links (or the multilinks that contain them)
are automatically highlighted.
b. (Optional) The new link label (created by default) can be modified as

required.
c. (Optional) Select the Delete SNC checkbox if you want the operation
also to delete the cross connects in the NE that were associated with the
former links.
d. (Optional) Modify the attributes of the combined link. Click More to
expand the Remove ME/UME dialog box to show the link attributes.
The fields are the same as the More pane in the Create Topology Link
dialog box. For a description of the fields, see Create Topology Link
Advanced Attributes.
Attribute values that are consistent with both the links that are to be
replaced are initially shown, such as the common technology layer, and
a summed Length value, and can be changed as required.
NOTE: For MoT links, SRLG names can be removed or

left as is. New SRLGs cannot be added.
e. Click Path Trace Configuration to configure SDH path trace

parameters; the Path Trace Configuration dialog box opens. For more
information, see Path Trace Configuration Dialog Box.
5. (Optional) Click Validate to verify that the operation can be performed as
indicated. If a warning appears, this may indicate a precondition that is not
present, such as security authorization or a trail rule violation.

6. Click Apply. Validate is also automatically performed, whether or not it

was performed before. If a warning appears, check that the link selections
are appropriate. Then click Apply again.
7. A warning appears that the operation may be traffic affecting; click OK.
Depending on the volume of trails that need to be handled, the operation
may take a few minutes.
The Progress bar at the bottom of the window indicates that processing is in
progress.
8. After the processing is completed, a Succeeded message appears; click OK.
9. Click Close to close the Remove ME/UME dialog box. The selected ME is
now removed from the selected links. The adjacent links are replaced by a
continuous link.
10. If the element involved more than one pair of links, you can repeat the
procedure to remove it from those links.
11. If the original link involved SYNCOM equipment at both ends (SYNCOM
- SYNCOM link), delete the original link from the link list in the EMS-
XDM, in order to avoid notification to LightSoft for this link.
Other original link configurations do not require intervention at the EMS
level.

Inserting/Removing Elements to/from

Optical Links
Inserting or removing a card into/from optical links involves the following
steps.
To insert an NE into an optical link:

1. Perform assignment of the new optical card in the EMS system. The card
and its ports will then be reflected in LightSoft.
2. Select the link to be replaced (old link) and open its Properties for Link
window; see Link Properties.
3. Set the link's Maintenance State field to Manual Maintenance to enable
creating new links on the link's ports; see Maintenance Operations.
4. Create two new links from the original ports to the new module; see
Creating Topology Links.
5. Select the old link on the map and open the Trail List window; see
Performing Actions on Trails. The trails traversing the old link appear in
the Trails pane.
6. Select all the trails and perform the following Trail Consistency actions:
Click the Trail Consistency toolbar icon, or right-click a trail and
select Trail Consistency from the shortcut menu. The Trail
Consistency Indicator window opens; see Trail Consistency Indicator
Window.
Specify the optical trail type, according to the selected trails - OMS,
OCH, or LP.
Perform trail synchronization as described in Performing Trail
Synchronization, using the Admit selected trails to database option to
readmit the trails. This causes the trails to traverse the new link.
7. Delete the unnecessary old link; see Deleting Topology Links. (The old
link is now free of trails.)

To remove an NE from an optical link:

1. Select each of the two old links to the element to be removed, and for each:
a. Open the link's Properties for Link window; see Link Properties.
b. Set the links' Maintenance State field to Manual Maintenance to
enable creating new links on each link's ports; see Link Properties.
2. Create a new link between the ports of two neighboring elements; see
3. Select the two old links on the map and open the Trail List window. The
trails traversing the old links appear in the Trails pane; see Performing
Actions on Trails.
4. Select all the trails and perform the following Trail Consistency actions:
Click the Trail Consistency toolbar icon, or right-click a trail and
select Trail Consistency from the shortcut menu. The Trail
Consistency Indicator window opens; see Trail Consistency Indicator
Window.
Specify the optical trail type, according to the selected trails - OMS,
OCH, or LP.
Perform trail synchronization as described in Performing Trail
Synchronization, using the Admit selected trails to database option to
readmit the trails. This causes the trails to traverse the new link.
5. Delete the two unnecessary old links; see Deleting Topology Links. (The
links are now free of trails.)

Maintenance Operations on
Links
Maintenance operations (for example, loopbacks, AIS, and RDI) enable you to
diagnose network problems. You can perform these operations on specific ports
and termination points used in trails and topology links managed by LightSoft.
These operations are performed in the Maintenance Operations window.
For operational instructions, see Maintenance Operations.
Link Properties
You can view or edit the properties of links.
The following is the Properties for Link dialog box for a selected SDH link.
To view or edit the properties of a link:

1. On the topology view, select a multilink and right-click. On the shortcut
menu, select Expand. The Actual Links Between Two Elements dialog
box opens. Select a link from the list and right-click the Link Name.
OR
If the multilink represents a single link, right-click the multilink.
2. Select Properties on the shortcut menu. The Properties for Link dialog
box opens. See the following sections for dialog box examples:
Properties for Link - SDH
Properties for Link - OTN
Properties for Link - EoS Virtual Link
Properties for Link - MoT Virtual Link
needed.
asterisk disappears when you click Apply to save the changes.
4. Click Apply to save the changes in all tabs.

Properties for Link Toolbar

All link types have the same toolbar icons, unless indicated.
Properties for Link dialog box icons

Alarms Shows the alarms applying to this link; Opens the Current Alarms
window showing the alarms on the selected link. You can also show
the alarms for all the links in the multilink by right-clicking the
multilink and selecting Current Alarms. See also Viewing Related
Current Alarms. For more information about alarms, see Accessing
Fault Management Windows.
Availability Shows availabilities of the link resources; see Availability for Link.
For the OTN Link type, shows the state of channels through the
OMS trail traversing this link; see Viewing Optical Channel
Availability.

Properties for Link - SDH

The parameters of SDH links are listed in two tabs:
| General Tab
| Advanced Tab
General Tab
The General tab parameters are also common to most other link types.
Exceptions are shown in context. Fields with a white background are editable
(see the parameter descriptions).
Properties for Link - SDH dialog box fields - General Tab
Field Description
Link Name Name of the link. (Editable)
Endpoints Endpoints of the link.
Trail ID ID of trails defined on this link.
Rate Rate of the link.
Status Usability state of the link (for example, OK) or alarm severity
(Major, Minor, and so on) of the port with the most severe alarm
at either end of the link; see Object Status Color Indications.

Field Description
Protection Type of link protection, for example, MS-SPRing, MSP,
unprotected.
On virtual links, the protection scheme is derived from the
underlying trail.
On physical topology links, the protection scheme is derived
through EMS port configurations, for example, MS-SPRing,
MSP.
Otherwise, Unprotected appears and the field is editable. If
some other kind of external protection applies (unmanaged by
LightSoft), you can set the protection description to External
Protection for information purposes. (Editable for physical links
where protection is not defined in the EMS.)
Ring Name Enter the name of the ring to which the link belongs. This field
displays the ring ID brought from the EMS, or any user-defined
ring name. It is read only for MS-SPRing.
When the Show Ring option is selected, all links with the same
Ring Name are highlighted in the map view; see option
description in Viewing Topology Link Information.
When the Expand Ring in New View option is selected, all
links that share the same ring name as the current link, whether
or not those links are present in the current view, are shown in a
new view; see option description in Viewing Topology Link
Information.
Service State Operational state of the link. Values are In Service or Out of
Service. The latter applies when the Maintenance State
parameter is set to Manual Maintenance or in the presence of a
fatal alarm.

Field Description
Consistency State Consistency between LightSoft and the respective EMS for a
specific link depending on the actual status. Available states:
Consistent or Inconsistent.
When the link is inconsistent, the inconsistency reason is shown
with the consistency state. There can be several reasons for
inconsistency:
| Deleted from EMS, when a link is deleted in the EMS but
cannot be deleted in LightSoft (for example, when a trail
passes through the link without the EMS being aware).
| Config Control Conflict, for example, when LightSoft
creates a link between a SYNCOM element and an XDM
element, and a different link is created via the EMS to a
different element using the previously created link's
endpoint.
| Validation Rules Conflict, for example, when a valid link
created in EMS-SYNCOM is incompatible with the rules of
LightSoft.
| Manual Out of Service, an indication that the link was
manually put out of service; see Maintenance State
parameter. This prevents the creation of new trails or receipt
on any notifications on the link.
Pre-existing traffic is not affected.
NOTE: Links that traverse inconsistent elements are also
rendered inconsistent.
Maintenance State Indicates whether the link is in service (None) or out of service
(Manual Maintenance). The latter setting prevents the creation
of any new entities or receipt of any notification on the link. Pre-
existing traffic is not affected. (Editable)
Comments Displays a comment. (Editable)

Advanced Tab
The following are Advanced parameters of SDH links. Certain fields are
editable (see the parameter descriptions).
The virtual link property definitions for SRLG, Length, Assigned Cost, and
Link Quality differ slightly from those of physical links.
Properties for Link - SDH dialog box fields - Advanced Tab
Field Description
Associated Layer Technology layer of the link - SDH.
Editable only in the (rare) case of the system being unable to
ascertain the layer of the associated ports.
Media Type Media type of the selected link.
On all layers except ETH/MPLS, Electrical or Fiber.
On ETH/MPLS layer, Physical or Virtual; see parameter
description in Properties for Link - EoS Virtual Link Advanced
Tab.
Media Subtype Select a media subtype from the list. Available options depend
on the media type. (Editable)
Length (km/mile) The length of the link in kilometers or miles. This value is used
for path searching optimization to determine the shortest path.
For virtual links, Length is an aggregation (the sum of the real
link segments that the trail traverses). (Editable)
Directionality Unidirectional or bidirectional.

Field Description
SRLG (Ducts) Shared Risk Link Group. Scrollable entry fields allow you to
specify the shared resources for the link. The Pathfinder
algorithm uses this information when calculating diversity
paths.
User-defined SRLGs can be added or removed. Automatically
assigned SRLGs are removed automatically if the MoT trail
using the link is removed. For more information, see Shared
Risk Link Groups (SRLGs).
If MoT trails currently using a link have protecting bypass
tunnels, then adding/removing SRLGs on the link is
disallowed. You must remove the bypass tunnels first. For
more information, see Deleting Tunnels.
For virtual links, this field is read only and displays the
accumulated SRLGs of the underlying technology links.
(Editable)
Assigned Cost Enter a cost value based on your local evaluations of cost on a
(1-1000) nondenominational scale of 1-1000. A low number indicates a
less expensive link. This value is used for optimizing trails; the
system selects the least expensive links for the trail path.
For virtual links, Assigned Cost is the accumulated cost across
the segments that the trail traverses. (Not applicable to Ethernet
virtual links.) (Editable)
Link Quality Select the quality of the link for QoS applications. The
(Best 1..5 Worst) available range is from 1 (best quality) to 5 (worst quality).
This value is used for optimizing trails; the system selects links
for the trail path according to the selected quality constraint.
For virtual links, Assigned Quality is the minimum quality
across servers. (Editable)
Dispersion Dispersion rate of the signal in pico seconds x nano meters per
(ps*nm/km) kilometer (ps*nm/km). User-entered value, not calculated.
(Editable)
Span Loss (dB) The span loss in decibels. User-entered value, not calculated.
(Editable)
Creation Time Date/time the link was created.
Created By Management system where this link was created (NMS or
EMS).

Properties for Link - OTN

The parameters of OTN links are listed in two tabs:
| General Tab
| Advanced Tab
General Tab
The following are General parameters of optical links.
Properties for Link - OTN dialog box fields - General Tab
Field Description
Link Name See Properties for Link - SDH General Tab parameter
Endpoints descriptions.
Trail ID
Rate
Status
Protection
Ring Name
Service State
Consistency State
Maintenance State
Comments

Advanced Tab
The following are Advanced parameters of optical links. Certain fields are
editable (see the parameter descriptions).
Properties for Link - OTN dialog box fields - Advanced Tab
Field Description
Associated Layer Technology layer of the link - OTN Editable only in
the (rare) case of the system being unable to
ascertain the layer of the associated ports.
Media Type See Properties for Link - SDH Advanced Tab.
Media Subtype
Length (km/mile)
Directionality
SRLG (Ducts)
Assigned Cost
(1-1000)
Link Quality
(Best 1..5 Worst)
Dispersion (ps*nm/km)
Span Loss (dB)
Creation Time
Created By

Properties for Link - EoS Virtual Link

The parameters of EoS trail virtual links are listed in two tabs:
| General Tab
| Advanced Tab
General Tab
The following are General parameters of EoS trail virtual links.
Properties for Link - EoS dialog box fields - General Tab
Field Description
Link Name See Properties for Link - SDH General Tab parameter
Endpoints descriptions.
Rate
Status
Protection
LAG Distribution Whether or not LAG is enabled for both endpoints. For more
information, see LAG Support. See also other LAG parameters
in Properties for Port - ETH/MPLS Tab.
STP Type Type of Spanning Tree Protection. Only for EoS virtual links.
Values may be RSTP, MSTP, or None. Derived from endpoint
PTPs. If both endpoints are not the same, both values are
indicated. For more information about RSTP protection, see
Viewing RSTP Information.

Field Description
STP Cost RSTP port cost used by the STP mechanism; see RSTP
Enabled and Cost parameter in EoS/MoT Configuration Pane.
Only EoS virtual links.
Service State See Properties for Link - SDH General Tab parameter
Consistency State descriptions.
Comments
Advanced Tab
The following are Advanced parameters of EoS trail virtual links.
Properties for Link - EoS dialog box fields - Advanced Tab
Field Description
Associated Technology layer of the link - ETH/MPLS.
Layer
Media Type Media type of the selected link. The ETH/MPLS layer has two link
types:
| Physical - real links (typically LAN links) created between
ports.
| Virtual links - "created" from EoS, MoT, or LP trails.
See also Physical Links and Virtual Links.
Directionality See Properties for Link - SDH Advanced Tab.
LCAS Enabled Indicates if LCAS is enabled on the virtual link.
Dual Homing Indicates if Dual Homing is enabled on the link (Yes or No).
Determined by LightSoft based on the ports and BPDU service. For
EoS virtual link only. For more information, see Configuring Dual
Homing Protection.
Creation Time See Properties for Link - SDH Advanced Tab.

Properties for Link – MoT Virtual Link

The parameters of MPLS over Transport (MoT) trail virtual links are listed in
the following tabs:
| General
| Advanced
| SRLGs
| CAC
| TE Other
General Tab
The following are General parameters of MoT trail virtual links.
Properties for Link - MoT dialog box fields - General Tab
Field Description
Link Name See Properties for Link - SDH General Tab.
Endpoints
Rate
Status
Protection
LAG Distribution See Properties for Link - EoS Virtual Link General Tab.
STP State
STP Cost

Field Description
Service State See Properties for Link - SDH General Tab.
Consistency State
Comments
Advanced Tab
The following are Advanced parameters of MoT trail virtual links.
Properties for Link - MoT dialog box fields - Advanced Tab
Field Description
Associated Layer Technology layer of the link - ETH/MPLS.
Media Type See Properties for Link - SDH Advanced Tab.
Directionality
LCAS Enabled See Properties for Link - EoS Virtual Link Advanced
Dual Homing Tab.
Create Time See Properties for Link - SDH Advanced Tab.

SRLGs Tab
The following are SRLG parameters of MoT trail virtual links. This tab is read
only. Manual SRLGs can only be defined and changed at the Physical layer;
see Properties for Link - SDH Advanced Tab.
The SRLG Members pane displays members of an SRLG selected in the

SRLG List pane.
Properties for Link - MoT dialog box fields - SRLGs Tab
Column Description
SRLG List
Type Auto or Manual (automatically or manually created SRLG per
physical link).
SRLG Name of the SRLG. Unique name per network.
Name | Automatic SRLGs: SRLG name is the link name.
| Manual SRLGs: User-defined name; see SRLGs parameter in
Properties for Link - SDH Advanced Tab. (For MoT virtual
links, manual SRLGs are added at the physical or SDH level.)
SRLG Members (per selection in SRLG List pane)
Type Type of link having the same SRLG as selected in the upper pane.
Member ID Link identification of link having the same SRLG as selected in the
upper pane.

CAC Tab
The following are CAC parameters of MoT trail virtual links, settable for each
endpoint port of the link. Defaults apply per network as defined in the Network
Properties - MPLS CAC Tab and can be modified on a per link-port basis as needed.
Properties for Link - MoT dialog box fields - CAC Tab
Field/Button Description
For each endpoint - Port as a whole and each CoS of the port:
Res Port level: Maximum proportion of the port's EMS-assigned
(Reservable) bandwidth that is reservable for working tunnel traffic only.
BW (%) CoS level: Maximum proportion of the port's EMS-assigned
bandwidth reservable for working tunnel traffic at a particular CoS.
The actual bandwidth that can be used by a CoS is subject to the
port bandwidth limit and BW usage by other CoSs. For more
details, see Network Properties - MPLS CAC Tab. The network
default can be changed for specific ports and CoS as needed.
Res Shared As Res BW %, but representing the proportion of the assigned
BW (%) bandwidth reserved for Bypass tunnel traffic only and unavailable
for working tunnel traffic.
Total BW Total of Reservable + Reservable Shared BW. The value can be less
(%) than 100%, the difference representing Unreservable BW. For more
details, see Network Properties - MPLS CAC Tab.
Default Sets the network default values.
button

TE Other Tab
The following are FRR parameters of MoT trail virtual links, settable for each
endpoint port of the link. Defaults apply per network as defined in the Network
Properties - MPLS TE Other Tab and can be modified on a per link-port basis
as needed.
The TE Other tab also provides pathfinding parameters per link-port.
Properties for Link - MoT dialog box fields - TE Other Tab
FRR Parameters (applying per link endpoint)
FRR Mode Sets how FRR switching from the protected tunnel is performed on
each port of the link. The default mode for the network is set in the
Network Properties - MPLS TE Other Tab and can be changed here
in the same way on a per-port basis.
Reversion Sets how reversion back to the protected tunnel is performed on
each port of the link. The default mode for the network is set in the
Network Properties - MPLS TE Other Tab and can be changed here
in the same way on a per-port basis.
Hold-Off Number of seconds delay (0 to 10 seconds in 0.1 second increments
Time (sec) (default 0 sec)) before FRR switching to protection is implemented.
The default for the network is set in the Network Properties - MPLS
TE Other Tab and can be changed here in the same way on a per-
port basis.
Wait to Number of seconds delay (0 to 12 minutes in 1 minute increments)
Restore before automatic reversion from the Bypass back to the protected
Time (min) tunnels after a failure is repaired. The default for the network is set
in the Network Properties - MPLS TE Other Tab and can be
changed here in the same way on a per-port basis.

Path Finding Parameters (applying per link)
Link TE Traffic engineering (TE) metric of this port, used by the
Metric Optimization Min Metric parameter in the Tunnel Management
Constraint Preferences Optimization Pane for tunnel pathfinding.
Applies to both link directions.
Default value is TE Reference Rate/Port Rate rounded up to the
closest legal value, where:
| TE Reference Rate is defined in Network Properties - MPLS TE
Other Tab.
| Port rate is assigned in the EMS.
For example, 9584/2500 = 4.
Link TE Metric is used in the calculation of the Tunnel Metric; see
Create Tunnel Window General Parameters Pane.
Link Length Length of this link; the sum of cable segments through which this
link traverses.
Default Sets the network default values.
button
Automatic Link Adaptation

Some NEs support automatic link and trail adaptation following port rate
upgrade. When two STM-1 ports are connected by an STM-1 link, if one port
is reassigned in the EMS to STM-4, that port and the link initially become
inconsistent. After you change the other endpoint port to STM-4, the first port
and the link become consistent again and no further user intervention is
required. LightSoft automatically performs the corresponding link
infrastructure changes - existing links are automatically upgraded to STM-4,
existing trails are automatically "moved" to the upgraded links, and internal
resource maps are automatically upgraded to reflect the STM-4 rate.

Port Properties
You can view or edit the properties of ports.
The following is the Properties for Port dialog box for a selected EoS port.
To view the properties of a port:

1. On the topology view, select a multilink and right-click. On the shortcut
menu, select Expand. The Actual Links Between Two Elements dialog
box opens.
2. In the record corresponding to the link, right-click a port name (for
example, Port 1 or Port 2) and select Properties on the shortcut menu. The
Properties for Port dialog box opens. See the following sections for dialog
box examples:
Properties for Port - SDH
Properties for Port - OTN
Properties for Port - ETH/MPLS
NOTE: You can also display the Properties for Port dialog
box by right-clicking a slot node in the topology tree (main
topology view) and selecting Properties from the shortcut
menu.

needed.
asterisk disappears when you click Apply to save the changes.
4. Click the Apply icon to save the changes in all tabs.

Properties for Port Toolbar

Properties for Port dialog boxes have the following toolbar options.
Properties for Port dialog box icons

Open Opens a GCT session for this port; see Starting/Closing a GCT
Session.
Alarms Shows the alarms applying to this object; see Viewing Related
Current Alarms.
Refresh Reloads the port properties.

Properties for Port - SDH

The parameters of SDH ports are listed in two tabs:
| General Tab
| Optics Tab
General Tab
The General tab parameters are also common to most other port types.
Exceptions are shown in context. Fields with a white background are editable
(see the parameter descriptions).

Properties for Port - SDH dialog box fields - General tab
Field Description
Port Name Port name (slot, port type, and number).
Status Usability state (for example, OK) or alarm severity (Major,
Minor, and so on) of the port. See also Object Status Color
Indications.
Assigned Port Label of the port (Editable)
Label
Port Rate Rate of the port.
Tip: LightSoft automatically performs the link infrastructure
changes consistent with port reassignments from STM-1 to STM-
4 in the EMS; see Automatic Link Adaptation.
Holder Slot number.
Topology Link(s) Topology links connected to the port.
LE(s) Names Name of the LE to which the port is related (usually a single LE,
but can be more on hybrid ports).
ME Name Name of the ME to which the LE is related.
DCC DCC configured on the port (if any).
Associated Layers Associated technology layer of the port. When the system is
unable to ascertain the port's layer, it can be set.
Directionality Unidirectional or bidirectional. In SDH it is bidirectional.
Protection Type of link protection, for example, MS-SPRing, MSP, external
protection, or unprotected.
Port Location Location of the port in a shelf. According to standard
EMS/LightSoft interface notation.
Service State Indicates whether the port is in or out of service.
Consistency State Consistency between LightSoft and the respective EMS for a
specific link. Available states: Consistent or Inconsistent.
When the link is inconsistent, the inconsistency reason is shown
with the consistency state. There can be several reasons for
inconsistency. For more information, see the Consistency State
description in Properties for Link - SDH General Tab.

Optics Tab
The following are Optics parameters of hybrid SDH-optical ports only. Certain
fields are editable (see the parameter descriptions).
Properties for Port - SDH dialog box fields - Optics tab
Field Description
Tuned Frequency Configured transmission-carrier frequency (THz). For CWDM
systems, shows the wavelength (nm).
FEC Displays the FEC (Forward Error Correction) setting (FEC,
EFEC, Disabled) from the EMS.
RZ Displays the RZ (Return to Zeros) setting (RZ, NRZ, N/A) from
the EMS.
Frequency Spacing Identifies the frequency spacing between two consecutive OCH
channels as presented in the EMS; see also Channel Frequencies
and Wavelengths.
Frequency Spread Identifies the spread of the spectrum on an OCH channel as
presented in the EMS; see also Channel Frequencies and
Wavelengths.
Client Rate Rate of the port, for example ODU1.
Paired Port For unidirectional ports, indicates the port of inverse direction.

Properties for Port - OTN

The parameters of OTN ports are listed in two tabs:
| General Tab
| Optics Tab
General Tab
The following are General parameters of optical ports.

Properties for Port - OTN dialog box fields - General tab
Field Description
Port Name See Properties for Port - SDH General Tab.
Status
Assigned Port Label
Port Rate
Holder
Topology Link(s)
LE(s) Names
ME Name
DCC
Associated Layers
Directionality
Protection
Port Location
Service State
Consistency State
Optics Tab
The following are Optics parameters of optical ports.
Properties for Port - OTN dialog box fields - Optics tab
Field Description
Tuned Frequency See Properties for Port - SDH Optics Tab.
FEC
RZ
Frequency Spacing
Frequency Spread
Client Rate
Paired Port

Properties for Port – ETH/MPLS

The parameters of ETH/MPLS layer ports are listed in three tabs:
| General Tab - Applies to all data ports.
| L1 Connectivity Tab - Applies only to EoS or MoT ports. Does not apply to
pure Ethernet ports.
| ETH/MPLS Tab - Applies to all Ethernet ports whether or not SDH-based.
Supported ETH/MPLS Port Types

ETH/MPLS ports are represented by two LightSoft layer characteristics:
| Physical layer, which include (configured at the EMS):
ETY ports (Ethernet at the physical layer).
EoS ports (Ethernet over SDH trails).
MoT ports (MPLS ports over SDH trails).
| Ethernet logical layer, which can include:
ETY and EoS physical ports, identified (by a type) as being one of the
following logical interfaces:
UNI ( ) ports (User-Network Interface), connect a user to the

network. The frames on a UNI port are either untagged or C-VLAN
tagged. Frames are associated with a Service on the basis of C-
VLAN with multiple C-VLANs defining a single Service. CoS is
assigned. Policing is performed by service.
E-NNI ( ) ports (External Network to Network Interface)

connect ports of different networks). The frames on an E-NNI port
are S-VLAN tagged; each S-VLAN denotes a service. COS
Mapping is supported. Policing is performed per service.
I-NNI ( ) ports (Internal Network to Network Interface) connect

ports of the same network. The frames on an I-NNI port are S-
VLAN tagged. The S-VLAN ID determines the Ethernet service.
Policing is not performed.
MoT ports, identified (by a type) as being MPLS I-NNI interfaces.
A port is sometimes referred to in LightSoft selection tree views by its joint
type:
| ETY - meaning ETY UNI
| ETY - meaning ETY E-NNI or ETY I-NNI
| EoS - meaning EoS UNI
| EoS - meaning EoS E-NNI or EoS I-NNI

For information about the logical interfaces used for service creation, see
Ethernet Service Endpoint Interfaces.
MPLS Network Port Types

MPLS ports supported by LightSoft are MoT ports. An MPLS network is
automatically created when MoT ports are connected. The network does not
need to be explicitly declared as a MPLS network.
Ethernet Network Port Types

A PB network uses EoS trails with endpoints in a PB LE (such as EIS card)
and/or an L1 SDH port (such as DIO card).
An L2 card (such as EIS) comprises SDH ports, a bridge, and Ethernet (ETY
physical) ports.
EoS trails and Ethernet services are created independently.
L1 Ports
The ports on L1 cards (such as DIO) connect an SDH trail termination with
Ethernet interfaces. The EoS trail is created directly to the port, entering as
SDH and leaving as Ethernet. When an EoS trail is created from an SDH
network, the L1 service already exists, encapsulated in the same port.
EoS ports enable the use of SDH cards in PB networks. The hub and spoke
remote endpoint can also be connected for GbE or FE.

General Tab
The following are General parameters of ETH/MPLS layer ports. These
parameters apply to all data ports.
Properties for Port - ETH/MPLS dialog box fields - General tab
Field Description
Port Name See Properties for Port - SDH General Tab.
Status
Assigned Port Label
Port Rate
Holder
Topology Link(s)
LE(s) Names
ME Name
DCC
Associated Layers
Directionality
Protection
Port Location
Service State
Consistency State

L1 Connectivity Tab
The following are L1 Connectivity parameters of ETH/MPLS layer ports.
They apply only to MoT, EoS, or L1 ETY ports and are not applicable for pure
Ethernet ports. The parameters available differ according to the port type. The
picture below shows the properties for EoS ports.
Properties for Port - ETH/MPLS dialog box fields - L1 Connectivity tab
Field Description
Port Type A supported ETH/MPLS port type; see Supported ETH/MPLS
Port Types. MoT, EoS, or L1 ETY ports.
Interface Type A supported ETH/MPLS interface type; see Supported
ETH/MPLS Port Types. MoT, EoS, or L1 ETY ports.
Port Enabled Enabled, Disabled. Only ports that have the EMS Port Enable
option. MoT, EoS, or L1 ETY ports.
Provisioned Server Number of VCs in the VCG (VC Group). The EMS enables
Resources allocating VC members to groups and changing the group
granularity. The VC type and the number of VCs together specify
the VCG rate. EoS, MoT ports only.
Server Layer Type Granularity of the VCs in the VCG. EoS/MoT only.
VC-4, VC-3, VC-12. EoS, MoT ports only.
Active Size Rx Indicates the number of Rx resources (VCs) that are configured as
active (Data Active) in the EMS. EoS, MoT ports only.

Field Description
Active Size Tx Indicates the number of Tx resources (VCs) that are configured as
active (Data Active) in the EMS. EoS, MoT ports only.
Encapsulation Type PPP or LAN Emulation from the EMS. Values are
HDLC_PPP, GFP_TRANSPARENT, GFP_FRAME_MAPPED,
TMPLS.
EoS, MoT ports only.
LCAS Indicates whether LCAS is enabled on the virtual link. EoS, MoT
ports only.
LCAS Type If LCAS is enabled, shows the LCAS type; LCAS, Proprietary-
LCAS, or DPC. EoS, MoT ports.
Ethernet Actual Rate limit for client in Mbps. ETY ports only.
Port Rate
OAM Enabled Enabled, Disabled. OAM enables single Ethernet link monitoring,
loopback testing and fault detection and signaling. L1 ETY, EoS
ports only.
Note: OAM Enabled is enabled/disabled in the Create Tunnel
window Advanced Parameters Pane. All the other OAM attributes
listed below are set in the EMS and provided as read-only in
LightSoft. The OAM attributes refer to the Link OAM feature
implemented according to standard IEEE 802.3 Clause 57.
OAM Active Mode Active, Passive. An Active port initiates OAM and does not
respond to an OAM remote loopback command from a Passive
peer. L1 ETY, EoS ports only.
OAM Passive Peer Yes, No, as set in the EMS. Indicates whether OAM may be
Only enabled with a peer port in Active mode. L1 ETY, EoS ports
only.
OAM Remote Enabled, Disabled. Whether the peer port is in OAM loopback
Loopback state. L1 ETY, EoS ports only.
OAM Local Enabled, Disabled. Whether the port is in OAM loopback state.
Loopback L1 ETY, EoS ports only.
CLE Address IP address of Customer-located equipment (CLE) on an Ethernet
ETY providing Ethernet Layer 2 services. L1 ETY, EoS ports
only.

ETH/MPLS Tab
The following are ETH/MPLS parameters of ETH/MPLS layer ports. Applies
to all Ethernet ports, whether or not they are SDH-based.
Properties for Port - ETH/MPLS dialog box fields - ETH/MPLS tab
Field Description
Tagging Format Q-in-Q, EIS Q-in-Q, or None, as set in the EMS. EoS only.
Double-tagging (VLAN Stacking) enables service providers to
use a single VLAN to offer IP-based service support to
customers with multiple VLANs.
Port Based VLAN Block untagged, Forward untagged, PVID for Untagged,
Mode PVID for priority tagged. For ETH port of MCS.
Port Based VLAN ID VLAN ID value. Data ports only.
Port Based VLAN ID C-VLAN priority of the PVID. Data ports only.
Priority
Dual Homing Peer LE name and port label of peer. Only ETH ports of dual
homed MPLE-PE. EoS/ETH ports only.
Gateway to PB PB network name displayed if the EoS trail has an endpoint in
a PB. MPLS-PE EoS or L1 ETY ports only.
Gateway to MPLS MPLS network name displayed if EoS trail has an endpoint in
a MPLS-PE. PB EoS ports only.
STP Type Type of Spanning Tree Protection. For more details see
Properties for Link - EoS Virtual Link General Tab. EoS port
only.

Field Description
STP Port Priority STP Port Priority. EoS port only.
STP Port Cost RSTP port cost used by the STP mechanism. Different values
may exist for each endpoint. EoS port only. For more details,
see Properties for Link - EoS Virtual Link General Tab.
LAG Configuration If LAG is enabled for the port (in LAG Distribution), then
Master or Slave. If LAG is not enabled, None. EoS/ETY ports
only.
LAG Master Port ID Name of master port (if applicable). EoS/ETY ports only.
LAG Distribution Enabled or Disabled. EoS/ETY ports only.
LAG Members List of PTP GUI labels. EoS/ETY ports only.
For more information about LAG, see LAG Support.

Viewing Resource Availability on

Links
The LightSoft Resource Availability on Links features are important tools for
network traffic planning. At a glance you can see the available capacity in the
network as a whole and on specific links/multilinks.
Two views of current link availability are provided:
| Availability Map windows show the proportions of available resources
across all or selected links based on selected parameters (SDH or optical
rate or source/CoS combination for ETH/MPLS); see Availability Map.
| Availability for Link windows show the number and percentage of
resources available for building new trails on a selected link, based on all
relevant parameters; see Availability for Link.
Resource availability is shown as of the time that the feature was selected (and
a rate was selected for the Availability map) or since the last refresh, as
indicated by the timestamp in the window footer.
Calculation requests are nonblocking for other LightSoft applications (client
and server).
NOTE: Optical Availability tables show the state of

channels through a selected DWDM or CWDM OMS trail.
For more information, see Viewing Optical Channel
Availability.
OPTIONAL FEATURE: The Availability Map and

Availability for Link functionality is a fully integrated add-on
capability, available on a cost basis. If not purchased, the
feature and related menu options are unavailable.

Availability Map
The Availability of Layer (Availability Map) window is an independent
replica of a selected technology layer with topology links/multilinks color
coded according to their available capacity for new trails. Available capacity
can be according to:
| Rate (SDH or optical) or
| Source and CoS combination (ETH/MPLS)
After parameters are selected or the window subsequently refreshed, the

availability of each link/multilink is calculated and color coded according to
five contiguous availability ranges shown in the legend in the status bar. You
can define the ranges and color associations quickly and easily through a color
palette dialog box; see Modifying Availability Preferences.
The color of a multilink or multidirectional link reflects the overall availability
of its participating links (the percentage available on the total capacity).
NOTE: Availability is depicted in terms of what can be

provisioned for a selected rate, which may be less than the
overall capacity of the SDH link. For more information, see
Link Availability Constraints.
This section contains the following topics:

| Accessing Availability Information
| Availability Map for SDH or Optical
| Availability Map for ETH/MPLS
| Viewing Availability Map Data in CSV Format
| Modifying Availability Map Preferences

Accessing Availability Information

The Availability Map window for SDH, MoT, or optical links is accessed
from the LightSoft Physical (Site) layer, or the applicable technology layer.
After the relevant parameters are selected (a rate for SDH or optical, or Source
and CoS selections for MoT), the links in the map are color coded according to
the available resources consistent with those parameters. Multiple instances of
the window may be opened at the same time, for example, based on the same
topology view but showing different parameters.
To view the resource availability of links:

1. In the LightSoft main window Topology Layer dropdown list, select a
topology view:
For an SDH or Optical map, select the Physical (Site), SDH, or Optical
layer.
For an Ethernet/MPLS map, select the ETH/MPLS layer.
2. Optionally preselect objects in the map view so that the Availability Map
opens with only selected objects and their links displayed, not all the
objects.
3. On the LightSoft main menu bar, select Tools > Availability Map.
OR
On the toolbar, click the Availability Map icon . The Availability

Map window opens:
SDH or Optical; see Availability Map for SDH or Optical.
ETH/MPLS; see Availability Map for ETH/MPLS.
4. On the menu bar:
SDH or Optical map: Select a rate from the Rate menu or dropdown
list.
ETH/MPLS map: Select a source and CoS from the respective menus
or dropdown lists.
The links/multilinks in the Availability Map window are color coded
according to the resource availability. For information about default ranges,
see Modifying Availability Preferences.

5. Click the Refresh icon or select View > Refresh at any time following
a rate selection to show the updated resource availability color coding of
the network. The progress indicator in the status bar shows the update
progress.
The Last Update field in the bottom right corner of the window shows the
date/time of the last refresh (Last Update time stamp).
To view the availability of individual links of a multilink, in the Availability
Map window, double-click the multilink (or right-click and select Expand on
the shortcut menu). An Availability dialog box for the selected topology layer
(a variation of the Actual Links between Two Elements dialog box) opens;
see Viewing Topology Link Information.
In this dialog box, each link is colored according to its own availability. An
Availability column shows the availability for each link in absolute terms. For
example, an STM-16 link is shown with "16 / 16 VC-4", indicating that 16 out
of its total 16 VC-4 resources are available.
You can also view availability in the form of pie charts by right-clicking a link
in the Availability Map window and selecting Availability from the shortcut
menu. For more information, see Availability for Link.

Availability Map for SDH or Optical

This window shows availability of links based on rate (selected from the Rate
menu or dropdown list). When accessed from the Physical (Site) layer, the
window rate choices include both SDH and optical rates. When accessed from
the SDH or optical technology layer, only rates relevant to the specific layer
can be selected, and the window is labeled according to the selected layer.
The window title reflects the relevant layer Physical (Site), SDH, or Optical,
and the rate.
Availability Map menu options
Toolbar
Menu option icon Description
Map
Preferences Enables you to change the percentages and colors
associated with availability ranges; see Modifying
Availability Preferences.
Close Closes the Availability Map window.
View
Refresh Refreshes the Availability Map window to show the
current resource availability color coding. The Last Update
time stamp in the bottom right corner of the status bar
shows the date/time of the last refresh.
A view is automatically refreshed when a different
parameter value is selected or new preferences applied.
Legend Shows or hides the status bar legend and Last Updated
time stamp.

Toolbar
Rate
Choice of SDH and/or optical rates.
Help
Help Displays the Help file.
Availability Map for ETH/MPLS

This window, accessed from the ETH/MPLS layer, shows availability of MoT
links based on selected Source and CoS parameters. (EoS links, if any, appear
in gray and are not part of the analysis.) The window title reflects the
ETH/MPLS layer and the selected parameter combination.
Availability Map menu options
Toolbar
Map
Preferences See Availability Map for SDH or Optical.
Close Closes the Availability Map window.
View
Refresh See Availability Map for SDH or Optical.
Legend See Availability Map for SDH or Optical.

Toolbar
Source and CoS

Source | CAC Unshared Bandwidth: Displays availability based
on bandwidth reserved for working tunnels (default).
For more information about reservable BW, see
Network Properties - MPLS CAC Tab.
| CAC Shared Bandwidth: Displays availability based on
bandwidth reserved for bypass tunnels. For more
information about reservable BW, see Network
Properties - MPLS CAC Tab.
| PM Current 15 Minutes: Displays availability based on
15 minute Performance Monitoring (PM) counter
intervals. For more information about PM, see
Performance Monitoring and Maintenance.
| PM Current 24 Hours: Displays availability based on
24 hour PM counter intervals. For more information
about PM, see Performance Monitoring and
Maintenance.
For multilink, availability is the average value calculated on
all the links in the multilink.
CoS Displays availability for the selected CoS - CoS 0 to CoS 7.
Help

Viewing Availability Map Data in CSV Format

You can access a file containing the current Availability Map information in
CSV format for convenient import to Microsoft Excel or a relational database.
The basic availability data for all the objects currently in the map is
automatically stored in CSV format in the path /tmp/NMSAvailMap.csv. Each
time the Availability Map is updated (opened and a rate selected or window
refreshed) the file is overwritten with the current data. (When the map is
opened with selected objects, only the availability map data for those objects is
saved in the file.)
Availability Map CSV data fields
Field Description
Link Name User-assigned link name. By default it is the name of the first
and second endpoints in alphabetical order.
Virtual Link Whether the link is an actual one in the current technology layer
(No) or a virtual representation of a trail from an underlying
technological layer (Yes).
Link Rate Rate of the link (may be different from the rate of the port).
Available Resources Total number of trails that can still be provisioned at the selected
rate on the specified link.
Total Resources Total number of trails that can potentially be provisioned on the
specified link at the selected rate.
Used Resources Indicates an OCH trail traversing OMS sections. The OCH trail
originates from at least one endpoint or passes through both.
Blocked Resources Indicates a channel is blocked at one/both endpoints by a group
OADM, a red-blue filter, or a dropped channel without OCH.
% Available Proportion of trails that can still be provisioned vs. the total that
can potentially be provisioned on the specified link at the
selected rate.

Modifying Availability Map Preferences

The Availability Preferences dialog box enables you to change the
percentages and color coding of the resource availability information in the
Availability Map window. The changes remain in effect for your user profile
until modified. The same color preferences apply in all layers.
To modify availability ranges and colors:

1. In the Availability Map menu, select Map > Preferences. The
Availability Preferences dialog box opens.
2. Change the percentages for each range in the From and To columns, as
follows:
The High (100-100) and Low (0-0) ranges in the figure denote exactly
100% and exactly 0%.
For other ranges, the upper limit extends to just below the next whole
number. For example, 51-99% denotes 51% or more, but less than
100%.
Any ranges can be defined, provided the upper and lower limits of
adjacent ranges are continuous (without gaps) and not overlapping.
AND/OR
Change the color associated with a range by customizing its color swatch
. For information about standard color customization, see
Customizing LightSoft Object Colors.
3. Click Apply to save the last changes and keep the dialog box open for
additional changes, or OK to save changes and close the dialog box. The
Availability Map window is automatically refreshed and the status bar
legend shows the new percentage and color codes. (You can click Reset to
undo the changes since the last Apply, or Cancel to close the dialog box
without saving the changes since the last Apply. You can click Defaults to
reinstate the system default percentages and colors.)

Availability preference dialog box buttons
Button Description
OK Saves the color changes to the user profile and closes the dialog
box.
Apply Saves the color changes to the user profile and keeps the dialog
box open for additional work.
Reset Reverses any changes in the dialog box since the last time
Apply or OK was used.
Cancel Closes the dialog box without saving any further changes.
Defaults Restores the system-default colors to the color swatches. (The
colors are saved to the user profile only after clicking Apply or
OK.)
Availability for Link

The Availability for Link window shows the number and percentage of
resources available for building new trails on a selected link based on all
relevant parameters (SDH or optical rates or source/CoS combinations for
ETH/MPLS).
Accessing Availability for a Link

The Availability for Link window is accessed as described in this section.
To view resource availability of a specific link:

1. In the LightSoft main window Topology Layer dropdown list, select a
topology view: Physical (Site), SDH, or Optical.
2. Right-click the required link/multilink, and select Availability from the
shortcut menu. The Availability for Link window opens.
If a multilink is selected, multiple windows open, one for each link in the
multilink.
OR
3. If you want to view availability for a single link in a multilink:
a. Double-click the multilink (or right-click it and select Expand on the
shortcut menu) to open the Actual Links between Two Elements
dialog box; see Viewing Topology Link Information.
b. Right-click the required link and select Availability for Link from the
shortcut menu. The Availability for Link window for that link opens.
You can also open the Availability for Link window from the Availability
Map window (see Availability Map) by right-clicking a link in that
window and selecting Availability from the shortcut menu.

Link Availability menu options
Toolbar
View
Refresh Refreshes the window to show the current resource
availability percentages. The Last Update time stamp in
the bottom right corner of the status bar shows the date/time
of the last refresh.
A view is automatically refreshed when a new preference is
applied.
Preferences Enables you to change the colors associated with
availability categories; see Modifying Availability
Preferences.
Legend Shows or hides the status bar legend and Last Updated
time stamp.
Print Prints the current charts.
Close Closes the window.
Help

Link Availability for SDH/Optical

The window header shows the link name and its designated rate.
When a multilink is selected, multiple Availability for Link windows are
opened, one for each link in the multilink.
When a link is symmetric in both directions, the window shows the rate
information on a single row. When a link is bidirectional, availability
information for each direction's rate is represented on a separate row.
For each possible rate of the link, a pie chart shows the percentages of available
vs. unavailable resources. The resources available vs. unavailable are listed
under each pie.
NOTE: Availability is depicted in terms of what can be

provisioned for a selected rate, which may be less than the
overall capacity of the SDH link. For more information, see
Link Availability Constraints.
The legend at the bottom of the window explains the color coding. The
available/unavailable colors are user-configurable; see Modifying Availability
Info Colors.
Blocked resources (resources already allocated at other rates or otherwise
unusable) are included within the Unavailable slices, and are not reflected
separately in the statistics. If a link's ports cannot fill the link's capacity (for
example, an STM-64 link connected to a port that can handle only 32 VC-4s),
the unusable capacity is considered blocked ("unavailable" for purposes of the
window information).
For the toolbar options, see Accessing Availability for a Link.

MoT Link Availability based on CAC

Parameters
This window is used to view bandwidth availability at the port and CoS level
based on CAC assignments; see Properties for Link - MoT Virtual Link CAC
Tab and Network Properties - MPLS CAC Tab.
The window is accessed from the Availability Map window whose
Information Source is set to CAC by double clicking a link or right-clicking it
and selecting Expand.
It can also be accessed from the link shortcut menu, by right-clicking a link and
selecting Availability > CAC.

Link CAC Availability diagram features
Option Description
BW Units Selector Enables choice of units expressed in terms of:
| Percentage of the port rate (% Port Rate), or
| Bandwidth (Mb/s)
Pie Charts and Bar Charts - Port and CoS levels
Allocated BW Portion of EMS-assigned port/CoS bandwidth reserved
for working traffic (Res BW %; see CAC Tab) that is
already allocated to tunnels.
Unreserved Portion of EMS-assigned bandwidth that is reservable
(unallocated) BW for working traffic (see Res BW % in Network
Properties - MPLS CAC Tab) at the port or CoS level
that is not yet allocated to traffic.
Allocated Shared BW Portion of EMS-assigned port/CoS bandwidth reserved
for bypass tunnels (Res Shared BW %; see CAC Tab)
that is already allocated to bypass tunnels.
Unreserved Portion of EMS-assigned port/CoS bandwidth reserved
(unallocated) Shared for bypass tunnels (see Res Shared BW % in Network
BW Properties - MPLS CAC Tab) at the port or CoS level
that is not yet allocated to traffic.
Non-Reservable BW Portion of EMS-assigned bandwidth not available for
any purpose.

MoT Link Availability based on PM Counters

This window is used to view link availability based on 15 minute or 24 hour
Performance Monitoring (PM) counter intervals. For more information about
PM, see Performance Monitoring and Maintenance.
This window is accessed from the Availability Map window, whose
Information Source is set to PM, by double-clicking a link or right-clicking it
and selecting Expand.
It can also be accessed from the link shortcut menu by right-clicking a link and
selecting Availability > PM.
Link PM Availability diagram features
Option Description
BW Units selector Enables choice between units expressed in terms of
percentage of the port rate (% Port Rate) or bandwidth
(Mb/s).
15m/24H selector Statistics based on 15-minute or 24-hour counter
collection intervals.
Overall port and per CoS Based on the counters called PortTxUtilization and
availability CosTxUtilization.

Modifying Availability Info Colors

The Preferences dialog box enables you to change the colors of specified
designations in the window pie charts and number fields. The changes remain
in effect for your user profile until modified.
To modify the availability info colors:
1. In the Availability for Link window toolbar, select Preferences , or

select View > Preferences. The Availability Info Preferences dialog box
opens. The possibilities for change vary according to the originating
window.
Following are the Preference windows for SDH, and ETH/MPLS CAC and
PM, respectively.
2. Change the color associated with a designation by customizing its color

swatch . For information about standard color customization, see
3. Click Apply to save the last changes and keep the dialog box open for
additional changes, or OK to save changes and close the dialog box. The
Availability for Link window is automatically refreshed. The status bar
legend shows the new color codes. (You can click Reset to undo the
changes since the last apply, or Cancel to close the dialog box without
saving the changes since the last apply. You can click Defaults to reinstate
the system default colors.)

Link Availability Constraints

Availability is depicted in terms of what can be provisioned for a selected rate,
which may be less than the overall capacity of the SDH link, as described
below.
Allocated and Available VC-4 Trails

The total counts of potentially available low order SDH resources (VC-12, VC-
2 and VC-3) are not calculated based on the overall capacity of the SDH link,
but on the number of VC-4 trails that are both allocated and accessible:
| Allocated VC-4 trails: Although an STM-16 link can carry 48 VC-3s (3
VC-3s on each of 16 VC-4s), the following STM-16 link Availability Chart
extract shows only 6 VC-3s as possible. This is because only 2 VC-4s are
allocated. The total resources are therefore 6 VC-3s (3 VC-3s x 2 VC-4s).
AND
| Accessible VC-4 trails: These are trails that terminate on the segment,
making add-and-drop possible, instead of just passing through. The
following STM-16 link Availability Chart extract shows 7 allocated VC-4s,
implying potentially 21 VC-3s. But the VC-3 pie total is only 18. This is
because one VC-4 just passes through the segment and therefore is not
counted.

Concatenated Trail Availability

Availability for concatenated trail rates (for example VC-4-4c) depends on how
preexisting trails are distributed within the link and the number of available
contiguous resources.
The Select Resource pane examples below show:
| VC-4 selection (first picture) - Four VC-4s are selected on an STM-16 link,
leaving 12 unoccupied resources.
| VC-4-4c selection (second picture) – Shows all resources occupied. Since a
VC-4-4c trail requires four contiguous resource grid cells starting at
specific offsets, VC-4s preexisting on any of those cells will block the VC-
4-4c trail creation.
Even though there are 12 unoccupied VC-4 resources on the link, if the
preexisting VC-4s are distributed on cells needed for the VC-4-4c creation,
availability at the VC-4-4c rate may be less than 3, and possibly nil.

6
Fault Management
In this chapter:
Overview ......................................................................................................... 6-1
Fault Management Concepts ........................................................................... 6-2
3
Accessing Fault Management Windows ......................................................... 6-8

3
Refreshing the Window ................................................................................. 6-13

3
Fault Window Parameters ............................................................................. 6-14

3
Alarm Correlation .......................................................................................... 6-24

3
Acknowledging Notifications ........................................................................ 6-31

3
Viewing Suggested Corrective Actions ......................................................... 6-32

3
Fault Management Customization ................................................................. 6-33

3
Historical Events............................................................................................ 6-37

3
Filtering Fault Lists ....................................................................................... 6-42

3
Using Alarm Counters ................................................................................... 6-61

3
Using Alarm Indicators ................................................................................. 6-67

3
Viewing Alarmed Entities ............................................................................. 6-76

3
Alarm Forwarding by FTP to Remote Servers .............................................. 6-79

3
Alarm Forwarding by SMS and Email .......................................................... 6-87

3
User Notes ..................................................................................................... 6-99

3
Overview
LightSoft supports sophisticated fault management tools that allow you to track
network faults easily and efficiently. These tools include:
| Windows displaying lists of notifications from NEs. You can sort the lists
and easily locate information.
| A sophisticated mechanism for filtering lists so that only the notifications
you want to view are displayed. Filters can be saved and reused.
| Counters that allow you to count any type of notification. Counters can be
saved and reused.

Fault Management LightSoft User Manual
| Alarm indicators (audio and/or visual popup) that alert you when LightSoft
receives selected notifications. Alarm indicators can be saved and reused.
| Color indications for states of managed objects. The color indicates
whether the object is operational and, if so, what is the highest alarm
severity affecting it.
NOTE: The capability profile of your user group determines

which operations you can perform. The resource domain of
your user group determines which objects you can manage.
Notifications from objects not within your user group's
resource domain are not listed in the Fault Management list
windows. For complete information regarding the visibility
rules of objects in LightSoft, see Managing Resource
Domains.
Fault Management Concepts

The following sections provide some key fault management concepts. Other
| Notification Types
| Object Status Color Indications
| Clearable and Nonclearable Alarms and TCAs
Notification Types
Notifications are messages generated by network components to inform the
network administrator about the status of EMSs and MEs. There are three types
of notifications:
| Alarms
| Threshold Crossing Alerts (TCAs)
| Events

LightSoft User Manual Fault Management
Alarms
Alarms indicate that something has occurred in the network that may affect
transmission or service provision. Alarms are displayed in the Current Alarms
window.
All alarms have a severity attribute, an indication of the effect of the fault that
activated the alarm. The higher the alarm severity, the greater the potential
effect on the network.
For more information about the Current Alarms window, see:
| Accessing Fault Management Windows
| Fault Window Parameters
Types of alarms include the following:
| Network alarms on objects activated by the respective EMS systems and
uploaded to LightSoft (majority of alarms activated by NEs).
| Internal alarms activated by LightSoft:
Disconnection alarm, indicating that an EMS is disconnected from
LightSoft.
Link and duct failure alarms generated as part of the Alarm Correlation
product add-on operation; see Alarm Correlation.
See also:
| Alarm Correlation
| Acknowledging Notifications
| Viewing Suggested Corrective Actions
| Fault Management Customization
| Using Alarm Counters
| Using Alarm Indicators
| Viewing Alarmed Entities
| Alarm Forwarding by FTP to Remote Servers
| Alarm Forwarding by SMS and Email

TCAs
Thresholds are configured in MEs in which threshold alerts are activated.
Threshold crossing alerts (TCAs) are listed in the Current TCAs window
when a preset PM threshold has been crossed in the ME.
In the case of a prolonged 15-min performance problem, the Current TCAs

window shows a single event with the timestamp of when the problem was first
observed, omitting intermediate events that may be issued by the EMS every
15 minutes. This enables you to conveniently know when a problem started.
Like alarms, TCAs have a severity attribute that is displayed in the Current
TCAs window.
For more information about the Current TCAs window, see:

Events
Events are generated by MEs to notify system administrators about their state.
An event is not necessarily a fault and can be purely informational. For
example, if a trail is switched to protection, the ME issues an event to notify of
the route switch. This event is non-traffic-affecting. Life cycle object creation
or deletion events are generated when objects (for example, an ME or a port)
are added to or removed from the network.
For more information about the Events window, see:

Events include the following:
| Object Creation: Provides detail of an object creation.
| Object Deletion: Provides details of an object deletion.
| State Change: Provides details of a change of ME communication state.
| Route Change: Provides details of a route change.
| Protection Switch: Provides details of a protection switch.
The Event Log window lists all these informational notifications, as well as
alarms and TCAs which remain in the Event Log after they are deleted from
their own lists. The fields displayed and their specific meanings may vary
according to the type of notification. For details, see Fault Window Parameters.
An event is removed from the Event Log window in the course of periodic
exporting to XML files, whether or not a clear notification has been received.
For more information, see Configuring Historical Event Logging, Archiving,
and Viewing.

Object Status Color Indications

The state of LightSoft objects (elements/links/trails) is indicated by color coding.
In the case of alarmed objects, the color represents the severity of the alarm
applicable to that object. The status of a group of objects is determined by the
“most severe” color of all objects that comprise it. Similarly, the color of each
single object is determined by the “most severe” color of the objects it contains.
The color coding applies to objects in all map windows except as specifically
indicated in this manual (for example, Availability, Timing, and RSTP map
windows use color coding to represent other properties). The severity of the
alarmed objects and the associated color code is also shown in various fault
management and trail window parameters.
The color codes indicated below are the system defaults. All the alarm state
colors except Cleared (green), are user-customizable; see Customizing Fault
Color Coding. The usability state colors cannot be changed.
| Alarm state color codes (applying to operational objects):
Critical (red)
Major (red)
Minor (orange)
Warning (yellow)
Indeterminate (gray)
Cleared (green)
| Usability state color codes (applying to nonoperational objects):
Unmanaged (gray)
Inconsistent (white)
Disconnected or Unknown (dark gray); see Troubleshooting Tips
Connected/not uploaded (light blue)
Uploading (blue)
Operational (at the end of the upload process, the corresponding Alarm
color appears)
The following rules determine object status:
| The alarm state propagates upwards in the hierarchy, whereas the usability
state propagates downwards.
| When an object usability state is Operational, LightSoft displays its alarm
state.
| The alarm state of an object is determined by the most severe alarmed state
of any of its components. For example, if any one component has a Critical
alarm, the object as a whole is considered critically alarmed. For more
information, see Synchronizing Trails.
| A port's alarm state is determined by alarms on that port and its CTPs.
| An alarm on any port (for example, a card-out alarm) determines the alarm
state of all ports of the card.

| A link's alarm state is determined by the two ports connected at each end.
| A virtual link's alarm state is determined by that of links that comprise it.
| A group's alarm state is determined by that of the objects it contains.
| An ME's alarm state is determined by that of the objects it contains.
| Alarm state is not reported for UMEs.
Troubleshooting Tips
The following causes and solutions apply to NE icons indicated as
Disconnected or Unknown (dark gray).
Disconnected/Unknown
Possible cause Solution

EMS problem. Use the Ping function to test communication
between the EMS and the NE; see Pinging an
Object.
NE problem - a faulty NE is Identify the last NE the EMS can communicate
obstructing the communications with and check possible obstructions. For more
channel between the EMS and NE. information, see the applicable EMS manual.
Physical NE problem - a card is not Check the cards at the NE shelf. For more
operational. information, see the applicable EMS manual.
LightSoft problem. Use the Force Upload function to upload the NE;
see Forcing an ME Upload.
Clearable and Nonclearable Alarms and TCAs

Some notifications can be associated with another notification indicating that
the condition that generated the original event no longer exists. This
notification is said to be clearable and the associated notification is called a
Clear event. Each alarm message has an attribute that indicates whether the
alarm is clearable. Normally, when the fault that generated an alarm is
resolved, a Clear event is generated. When LightSoft receives this event, the
alarms it clears are removed from the Current Alarms or Current TCA
windows. However, the alarms and their associated Clear event can still be
viewed in the Event Log window.
Some alarms and TCAs may not be clearable. They therefore have no
associated Clear event and are not included in the Current Alarms list.
Periodically, LightSoft scans the Current TCA and Current Alarms lists for
these nonclearable notifications and removes them from the list.
NOTE: Alarms and their associated Clear events can be

viewed in the Event Log window even after they are removed
from the Current TCA and Current Alarms lists.

Accessing Fault Management

Windows
Each record represents one notification in fault management windows. This
section describes how to open the Current Alarms, Current TCAs, and
Event Log windows. The Event History window requires a slightly different
procedure; see Historical Events
These windows can be filtered to display only the events you want to view. For
complete information about filters, see Filtering Fault Lists.
To open a fault management window:

| On the LightSoft main menu bar, select Faults > Current Alarms or
Current TCA or Event Log.
OR
| On the toolbar, click Current Alarms or Current TCA or

Event Log . The corresponding fault management window opens. For
examples of the Current Alarms, Current TCAs, and Event Log
windows, see Alarms, TCAs, and Events, respectively.
NOTES:
When working with alarms or TCAs, you may want to
open the window with notifications only for selected NEs
rather than showing all the objects in the current view. To
do this, select the objects in the LightSoft main window
view map. In the case of TCAs, the NE selections must be
made in a physical view.
The Current Alarms window data font size can be
modified by changing a system file; contact ECI Telecom
customer support for assistance.
The windows provide a wide range of data for selected notifications, displayed
in default window columns, in optional columns that you can add to the views,
or in the respective info dialog boxes. For more information, see Fault Window
Parameters.
The Event Log window additionally shows the following information about
the range of event records available for viewing in this window (kept in the
active Event Log database):
| Events range from/to: the date/time of the oldest and newest events.
| Maximum Capacity: the total number of records.
| Maximum Period (in days): the oldest age of records.

The records in excess of the maximum parameters are automatically exported

to XML history files based on a user-configurable predefined schedule. For
more information, see Configuring Historical Event Logging, Archiving, and
Viewing.
Common Window Elements

Alarms, TCAs, and events are viewed and managed in the following windows:
| Current Alarms: Alarms that have not yet been cleared.
| TCA: TCAs that have not yet been cleared.
| Event Log: All alarms, TCAs, and events.
| Event Log History: Imports and lists events previously exported to XML
files and stored on disk.
These windows have a common toolbar and some common menu commands.
List area
The list area is where the notifications appear. Each line or record represents
one alarm, TCA, or other event. The column headings are either textual or
represented by an icon. The first column displays a line number for each
record. You select a record by clicking it. You can also display shortcut menus
by right-clicking a record. Menu options that are not available are disabled.

NOTE: Alarms from certain network elements (such as ECI

Telecom's Aurora family) are summarized as one alarm line
in the Current Alarms window list, with a severity that
represents the worst severity traffic alarm present on the
element (minor, major, or critical). To view the detailed
alarms on the element, open a GCT session to the relevant
EMS by right-clicking the alarm line and selecting Open
Object from the shortcut menu. You can also right-clicking
the LE in the ETH/MPLS layer and selecting Open Object.
For more information, see Starting/Closing a GCT Session.
In the case of Aurora LEs, for GCT from LightSoft to be
enabled, non-Admin users must have the same user name
defined in both the EMS-Aurora and the EMS-XDM.
The window columns and their width can be customized and the records can be
sorted in ascending/descending order according to selected columns; see
Working with LightSoft.
Status bar
The status bar displays the total number of records in a list and the number of
records that match a selected filter criterion.
Column Configuration
By default, the Current Alarms, Threshold Crossing Alert, and Event Log
windows open with a basic set of columns. You can optionally include
additional columns in the windows and auto-fit the column widths to their text;
see Showing, Hiding, and Auto-Fitting Columns. For additional operations on
columns, see Resizing List Columns, Sorting List Lines, and Moving Columns
in Tables.

Menus and Toolbar

Each fault management window has a menu bar. The more popular commands
are also available on the toolbar. The following table lists the menu options and
corresponding toolbar icons (where applicable) for each fault management
window. For details about the Updates Enabled/Disabled toggle icon /
, see Refreshing the window.
Menu and toolbar options common to all fault management windows
Menu Toolbar
Description
command icon
Current Alarms, Current TCAs, Event Log, and Event Log History menu commands
Preferences Enables you to divide the records into pages and to scroll
pages using the scroll arrows in the bottom right corner of
the window. See Paginating List Windows.
Export to CSV Exports list data to a delimited format file, such as comma-
separated values (CSV), for import to Microsoft Excel or a
relational database application. See Exporting to CSV.
Print Prints the current window list.
Import Imports the history records of a selected XML file to the

Event Log History window. See Viewing Historical Log
Events. (Event Log History window only.)
Alarm, TCAs, Events, and Event menu commands
Acknowledge Acknowledges the selected notification. Acknowledgements
for network alarms are sent to the corresponding object
(EMS or ME) for handling, and the notification is marked as
acknowledged. Before acknowledgement, a Waiting for
Acknowledge icon appears in the Ack column, and
after, a checkmark appears. See Acknowledging
Notifications. (Not applicable for Event Log History
window.)
Show Affected Opens the Trails List with trails that may be affected by the
Trails selected notifications. See Viewing Trails Affected by an
Alarm. (Appears only in Current Alarms window.)
Open Object Opens the object of reference for the selected notification in
the EMS.
For link failure alarms, opens the Actual Links Between
Two Elements window; see Viewing Topology Link
Information.
Not applicable to duct failure alarms.
Show Info Shows additional attributes for the selected notification. See
Fault Info Dialog Boxes.

Menu Toolbar
Description
command icon
Corrective Opens the Suggested Corrective Actions window relevant for
Actions the selected notification, describing the alarm and recommending
steps to clear it; see Viewing Suggested Corrective Actions. (Not
applicable for Event Log History window.)
Add Note Opens a window where you can create a new user note and
save it for future reference. See User Notes. (Not applicable
for Event Log History window.)
Show/Hide (Present when Alarm Correlation is installed and enabled.)
Secondary Toggles alternately between showing secondary alarms or
Alarms hiding them (leaving only primary and uncorrelated alarms in
the table view); see Showing or Hiding Secondary Alarms.
For a detailed explanation of primary and secondary alarms,
see Alarm Correlation.
Hierarchical Present when Alarm Correlation is installed and enabled.
Sort Sorts primary and secondary alarms in a hierarchical order,
where secondary alarms are located under their root cause;
see Showing Secondary Alarms of a Primary.
Show User Displays the user notes preview panel. See User Notes. (Not
Notes applicable for Event Log History window.)
Filter menu commands
No Filter Dropdown lists from which you can select a specific filter.
Predefined Filters are grouped by their specified sharing option.
Filters Clicking a specific filter in a category applies that filter to
Public Filters the list. When the No Filter option is selected, the fault table
User Group becomes unfiltered and lists all faults.
Filters The toolbar provides the Select Filter dropdown list for this
Private Filters purpose.
For more information, see Applying a Filter.

Show Filter Opens the properties of the selected filter. See Editing a
Properties Filter, or Creating a Filter Based on an Existing One.
Create New Opens the Filter dialog box. See Creating a New Filter.
Filter
Save Filter Saves the changes to the current filter settings.
Save Filter As Saves the current filter settings as a new filter under another
name; see Editing a Filter, or Creating a Filter Based on an
Existing One.
Delete Deletes the currently selected filter; see Deleting a Filter.
Set Filter as Sets the selected filter as the default that is automatically
Default applied when the window opens; see Setting a Filter as
Default.
Help menu command
Open Help Opens the Help file.

Refreshing the Window

Each fault management window includes an Updates Enabled/Disabled
toggle icon / . While the Updates Enabled icon is visible, the
table is automatically refreshed as soon as new information is available from
the database (Current mode). Clicking the icon disables automatic updates of
the table, keeping the table information static (Freeze mode). The icon is then
replaced with the Updated Disabled icon , which can be used at any time
to reinstate automatic refreshing.
While the window is in Freeze mode, changes can continue to be performed on
records, such as:
| Clearing alarms.
| Acknowledging alarms.
| Changing alarm severity.
| Alarms becoming trail or service affecting, because a trail/service is created
on the alarmed object.
| Change in the Last Reported State by disconnecting NEs.
| Notes added/deleted/edited regarding alarms.
| Expiration of event records or their removal from the database.
Once any such change is detected for a record:
| The record is grayed-out in the list area. Additional user actions are
disallowed on it (menu and toolbar options are disabled when the alarm is
selected). Only the specific record on which a change occurred is affected.
Actions can continue to be performed on other records.
| The Refresh icon in the bottom right of the window flashes.

Information requests, such as Info, Show Corrective Action, Show User Note,
Open Object, Show Affected Trails, do not cause user actions to be disabled.
You can perform a one-time refresh of the entire window by clicking the
Refresh icon . All the grayed alarm lines are shown in regular type or are
removed from the list if applicable.
However, following the refresh action, a window that was in Freeze mode
remains static regarding subsequent changes in the database. Continuous
dynamic refreshing of the window resumes only when you click the Updated
Disabled icon .

Fault Window Parameters

Alarms and TCAs are listed in the Current Alarms and Threshold Crossing
Alert windows, respectively.
Events (informational notifications generated by MEs) are listed in the Event
Log window; for information about the event types, see Events. Alarm and
TCAs are also listed in the Event Log window, and remain there after they are
deleted from their own lists.
The Current Alarms, Threshold Crossing Alert, and Event Log window
parameters are displayed as follows:
| Default Window Columns: Basic parameters.
| Optional Window Columns: Can be added to the window table as described
in Column configuration.
| Fault Info Dialog Boxes: More information for each notification.
Parameters of link and duct failure alarms may have slightly different meaning
and behavior from EMS-generated alarms (described in context). See Alarm
Correlation for details about these alarms in the context of alarm correlation.
The Event Log History window uses the same parameters as the Event Log
window unless otherwise stated.
Certain parameters of alarms or TCAs that pertain to trails that may be deleted
do not appear in the Events windows (described in context).
The parameters displayed, their type (default, optional, or info), and their
specific meanings may vary according to the type of notification (as noted in
context).
NOTE: User-entered values to parameters of EMS-

generated alarms and Disconnection internal alarms are
generally persistent. However, user-entered values to link or
duct failure alarm parameters through LightSoft (for example
acknowledgements) are not persistent and may change to
default values following an alarm process initialization.

Default Window Columns

By default, the Current Alarms, Threshold Crossing Alert, and Event Log
windows open with the following basic columns. The order may differ
according to the notification type.
Default Fault Management window columns (when Select Default is selected)
Icon Name Description Appears in

Last reported state Alarms and TCA
The LRS symbol in the column indicates that
(LRS) before windows only
parameter values for this notification may not be
disconnection (not present in Event
current. Instead, the last reported state before
connection (to the ME or EMS that processed the windows)
notification) was lost appears.
Link and duct failure alarms: Applies if at least
one connected port, or one port alarm of the duct's
contained link, is in LRS status.
Severity Level of disruption caused by the fault. Severity All windows
levels include:
| Indeterminate - Gray
| Critical - Red
| Major - Red
| Minor - Orange
| Warning - Yellow
| Cleared - Green
These colors are the default and are user-definable;
see Customizing Fault Color Coding.
Link and duct failure alarms: Default is Major.
Can be modified by changing a system file; contact
ECI Telecom customer support for assistance.
ME Name Name of the ME that generated the notification. All windows
Not applicable to alarms that are not associated
with an NE, such as link and duct failure or EMS
disconnection.
Object Name Name of the object where the problem was All windows
identified.
Probable Cause Probable cause as reported by the EMS. All windows
For non-alarm/TCA events:
| For a State Change event, the current state of
the object.
| For a Protection Switch event, the protection
type and the reason for the switch.
Event Time Time the notification was activated/generated. All windows


Event Type Type of event: All windows
| Object Creation
| Object Deletion
| State Change
| Route Change
| Protection Switch
| Threshold Crossing Alert
| Alarm
For this parameter in Alarm and TCA windows,
see Optional Window Columns.
Optional Window Columns

The following are additional columns that can be added to the Current
Alarms, Threshold Crossing Alert, and Event Log windows. The order may
differ according to the notification type. (In the list below, "N/A to Alarm or
TCAs" means listed in non-Alarm/TCA events only.)
Optional Fault Management window columns

Cleared Whether the notification has been cleared. Event Log, Log
History window
only
Clear Time When the notification was cleared. Event Log, Log
History window
only
Granularity Time interval for which PM data is collected (15 TCA window only
Period min or 24 hrs).
Threshold Type For TCA parameters: Highest, High, Low, and TCA window only
Lowest.
Location PM parameters may relate to measurements TCA window only
taken for receive or transmit traffic, either at the
named TP (Termination Point) (near end
Rx/Tx), or at the TP at the far end of the trail
(circuit/path) connected to the named TP (far
end Rx/Tx).
Alternatively, PM parameters may be
bidirectional, for example, resulting from a
second-by-second summation and evaluation of
both far and near end TPs.


Ack Indicates whether the notification was All windows
acknowledged:
| Before acknowledgement, a Waiting for
Acknowledge icon appears in the Ack
column;
| After acknowledgement, a checkmark
appears.
Link and duct failure alarms: The Ack state is
not persistent following an alarm process
initialization.
Correlation State When Alarm Correlation is installed and Alarms window
enabled, the alarm's correlation state as: only
| Primary , representing a likely root (not present in
cause fault. Event windows)
| Secondary , the consequence of a fault

represented by another alarm.
| Not Correlated alarm (cell is empty), if it
either did not complete the correlation
evaluation processing, or completed the
processing but a distinct state could not be
determined.
For more information, see Alarm Correlation.
Trail Affecting Indicates whether the fault affects trails. If Yes, Alarm window only
use Show Affected Trails to open a Trail List (not present in
window filtered by the affected trails; see Event windows)
Viewing Trails Affected by an Alarm.
Layer Rate Transmission rate of the object that activated the All windows
notification.
Link failure alarm: Shows the rate of the
connected port.
Duct failure alarm: Shows "DUCT".
Affected Trails If a trail is affected by the current fault, shows Alarms window
the trail label for that trail. If more than one trail only
is affected, "Multiple" appears in the field. To (not present in
see details of the trails affected by this Event windows)
notification, use the Show Affected Trails option
to open a Trail List window filtered by the
affected trails; see Viewing Trails Affected by
an Alarm.
Service Affecting Whether the event affects transmission service. Alarms window
Possible values are: Yes, No, Unknown. only
Not applicable to alarms generated by LightSoft (not present in
such as link and duct failure alarms of Event windows)
Disconnection alarms.


Event Type "Alarm" for Alarm and "Threshold Crossing All windows
Alert" for TCA.
For this parameter in Event Log and Log
History, see Default Window Columns.
Ack Time Time the notification was acknowledged. All windows
Link and duct failure alarms: Time when the
alarm was acknowledged in LightSoft. Not
persistent following an alarm process
initialization.
Ack User Name Name of the user who acknowledged the All windows
notification.
Link and duct failure alarms: May be blank
following an alarm process initialization.
Additional Text Free text string that provides more information Alarms window
about the notification, for example, "Unit is only
miscounted" for a TCA.
Appears as an Event only if the notification is an
alarm or TCA.
Not applicable to alarms generated by LightSoft
such as link and duct failure alarms of
Number of User Number of user notes attached to the All windows except
Notes notification. To view the user notes in the Notes Log History
pane, select a notification, right-click, and select
Show User Notes .
General Probable General cause of the alarm, for example, Alarms window
Cause equipment. only
Note: General Probable Cause uses a generic list
of probable causes, whereas Probable Cause is
the probable cause that appears in the EMS; see
Probable Cause in Default Window Columns.
Link and duct failure alarms: Shows "TCF"
(Transport Connection Failure).
EMS Time Time the notification was generated or received All windows
by the EMS.
Not applicable to alarms generated by LightSoft,
LightSoft Time Time the notification was generated or received All windows except
by LightSoft. Log History
Not applicable to alarms generated by LightSoft,


Object Type Type of objects that generate notifications: All windows
| Subnetwork Connection
| Physical Termination Point
| Connection Termination Point
| Termination Point
| Equipment
| Unknown
| None
Type of objects that generate an alarm or event:

| EMS
| ME
| Subnetwork
| Topological Link
| Equipment Holder
| Protection Group
| Traffic Descriptor
Native EMS Name of the alarmed object as displayed in the All windows
Name EMS.
EMS Name Name of the EMS that manages the ME that All windows
generated the notification.
Unique ID Unique identifier given to an alarm during the All windows
Alarms process life cycle. Includes:
| Workstation ID of server workstation (in a
cluster configuration) that processed the
alarm.
| Sequential ID, a sequential identifier in
increasing order per alarm.
Primary ID When Alarm Correlation is enabled, shows the Alarm only
associated primary alarm ID for each secondary
alarm. (A primary alarm shows its own ID.)

Fault Info Dialog Boxes

The Current Alarm, Threshold Crossing Alert, and Event Log info dialog
boxes display information about selected notifications.
Info fields are not editable.
To view additional information for a notification:

1. In the Current Alarms, Threshold Crossing Alert, or Event Log
window, select a notification.
2. Right-click and select Info on the shortcut menu.
OR
On the toolbar, click the Info icon .

The corresponding Info dialog box opens showing attributes and values for
the selected notification.
3. Click More to display the entire contents of the dialog box. (The Less
button displays a limited range of parameters.)
4. If the info field contains text strings that exceed their field frames (showing
only the last part of the string), click the field and press Home to go to the
beginning of the string or End to go to the end of the string. You can also
scroll with the left and right arrows.

Fault Management info dialog box icons

Open Opens a GCT session for the object described in this
notification; see Starting/Closing a GCT Session.
Show Affected Displays the current alarms on trails associated with this
Trails notification; see Viewing Trails Affected by an Alarm.
Acknowledge Codes the selected alarm as acknowledged; see
this Alarm Acknowledging Notifications.
User Note Attaches a user note to the notification; see Viewing and
Attaching Notes on Fault Notifications.
Corrective Opens the Suggested Corrective Actions window relevant
Actions for the selected notification, which describes the fault and the
recommended steps to clear it; see Viewing Suggested
Corrective Actions.
The Info dialog boxes provide the same information about a selected
notification that is available from the fault management windows, plus the
following additional information. The order of the fields may differ according
to the notification type. (In the list below, "N/A to Alarm or TCAs" means
listed in non-Alarm/TCA events only.)
Additional information in Fault Management info dialog box
Field Description Appears in

LE Name Names of the LEs to which the current ME is mapped in All windows
different technology layers.
User Notes Text of the user notes attached to the notification. For more All windows
information, see User Notes.
Is Clearable If yes, a Clear event is generated when the fault is All windows
resolved. When LightSoft receives this event, the
notification it clears is removed from the Current
Alarms/TCA window.
Appears as an Event only if the notification is an alarm or
TCA.
Is Synthetic Whether this is a LightSoft-generated link or duct failure Alarms window
alarm. only
Correlation State See parameter description in Optional Window Columns. All windows
Protection Type Identifies whether the protection switch is MS or SNCP. Event windows
Appears when a protection switch event is selected. only


Switch Reason Appears when a protection switch event is selected. Event windows
Indicates the reason for a switch: only
| Not Applicable - when retrieving switch data for
nonrevertive groups if a more precise value is not
available.
| Restored - return to the normal state for revertive
groups.
| Signal Mismatch - signal is OK but is identified as
coming from an incorrect source: Trail Trace Identifies
Mismatch, Signal Label Mismatch, and so on.
| Automatic Switch - during a switch to protection
notification, or when retrieving switch data if a
protection switch is currently active and when the
exact switch reason is unknown.
| Manual - switch requested by the operator, including
forced switches.
Group Name Appears when a protection switch event is selected. Event windows
Indicates the PG that made the switch. Assigned by the only
EMS upon creation and is unique within the ME. If the
protection type is SNCP, the field is empty.
Protection TP Appears when a protection switch event is selected. Event windows
Identifies the protected TP. only
| For SNCP, always the reliable TP.
| For a two-fiber MS-SPRing ring switch notification,
the TP that is/was inactive during the switch.
| For a four-fiber MS-SPRing ring switch notification,
the working TP that is/was inactive during the switch.
| For a 1:N MSP switch notification, the working TP for
which the protection switch occurred.
| For a revertive MSP, always the working TP.
| For a non-revertive MSP switch notification, the TP
that is inactive after the switch.
Switch away from Appears when a protection switch event is selected. Event windows
TP Identifies the TP being switched away. only
| For a two-fiber MS-SPRing ring switch, the TP that
switched.
| For a four-fiber MS-SPRing span switch, one of the
TPs in the MSP 1:N groups (working or protection).
| For a four-fiber ring switch, the working TP of the
span that switched, for example, if the East span
switches to the West span, this is the East working TP.


Switch to TP Appears when a protection switch event is selected. Event windows
Identifies the TP that is the active source after the switch, only
or currently active if no protection switch is currently
active.
| For a two-fiber MS-SPRing when the state returns to
normal, the TP that switched.
| For a four-fiber MS-SPRing ring switch when the state
returns to normal, the working TP of the span that
switched, for example, if the East span switches to the
West span, this is the East working TP.
Edge Point Related For Object Creation, Object Deletion, and State change Event windows
events, "Yes" if the event relates to: only
| a PTP that is an edge point, to a CTP that is contained
in a PTP that is an edge point, OR
| a PG that contains a PTP that is an edge point
Attribute List For State Change events, list of names of state attributes Event windows
that have changed and their complete new values in the only
modified object structure.
Route Change Event For Route Change events, identifies which state the Event windows
notification is emitted against. only
Route For Route Change events, identifies the new route that is Event windows
chosen, if any. only

Alarm Correlation
Alarms can be classified into causes and effects. A specific alarm can cause a
chain of related alarms to be reported in some MEs. For example, a LOS alarm
at an object may cause an AIS alarm on a downstream (low order or high order)
transmission object.
While the conjunction of all the alarms represent the real status of the network,
concentrating on the causes may improve time response and save OPEX.
Alarm correlation enables you to quickly identify the root cause of a problem
without having to check the chain of alarms precipitated by an initial alarm.
Primary vs. secondary alarms

Alarm correlation considers all alarms and attempts to find their real root cause.
It assigns those with common root causes to single parent "primary" alarms.
You can then focus on the main problem by displaying only primary alarms in
the Current Alarms window. "Secondary" alarms, known to be the result of
faults represented by other reported alarms, can be suppressed from the table
view, reducing the clutter in fault windows and the number of alarms that
maintenance center operators need to examine.
Alarm correlation algorithms apply rules that yield accurate primary vs.
secondary classifications in many cases. For example, the most common
scenarios likely to cause an alarm avalanche, such as fiber cuts and card
malfunctions, are supported.
Correlated vs. uncorrelated alarms

"Correlated" alarms are alarms that completed correlation evaluation
processing and can clearly be classified as primary or secondary. Alarms that
did not undergo correlation processing, or completed the processing but could
not be distinctively classified, are considered "uncorrelated".
Link and duct failure alarms

When the Alarm Correlation product add-on is enabled, LightSoft generates
link failure or duct failure alarms:
| Link failure alarms: Generated when LOS alarms involving both of a
link's endpoints are received from EMSs (endpoints can be in different
EMSs), suggesting a fiber cut. (A single LOS alarm does not trigger a link
failure alarm.)

| Duct failure alarms: Generated if all the links associated with a duct
experience the same link failure alarm. The duct associations are assigned
manually to links through the SRLG parameter in the link properties; see
Link Properties.
The link failure alarms and associated LOS alarms (and any other resultant
alarms) all become secondary alarms of the primary duct failure alarm. If
the failure clears from any one of the duct's links, the duct failure alarm is
cleared and all still current link failure alarms become primary alarms of
their respective LOS alarms (and any other resultant alarms).
Link and duct failure alarms can be identified in the table list by their Probable
Cause parameter (labeled Link Failure or Duct Failure, respectively) – see the
parameter description in Default Window Columns.
Parameters of link and duct failure alarms may have slightly different meaning
and behavior from EMS-generated alarms; see Fault Window Parameters.
NOTES:
Disconnection internal alarms appear in the alarm table as
uncorrelated.
Values entered to link or duct failure alarm parameters
through LightSoft (for example, acknowledgements) are
not persistent and may change to default values following
an alarm process initialization.
OPTIONAL FEATURE: Alarm Correlation is a fully

integrated add-on capability, available on a cost option basis.
If not purchased, the associated features will not be visible in
the window.

Alarm Correlation Columns and Icons

The following Current Alarms window example shows the alarm correlation-
specific columns and icons. The columns can be shown/hidden in the standard
way described in Showing, Hiding, and Auto-fitting Columns.
Alarm Correlation-related columns
Column Description
Correlation State When Alarm Correlation is enabled, shows the correlation state
of an alarm as being:
| Primary , representing a likely root cause fault. A
primary alarm must have associated secondary alarms.
(Duct alarms are considered primary. When link alarms do
not have an associated duct alarm, the link alarms are
considered primary.)
| Secondary , the consequence of a fault represented by
another alarm. (An alarm that is the consequence of a
secondary alarm is still considered secondary to the first-
level primary.)
| Not Correlated alarm (cell is empty), if it either did not
complete the correlation evaluation processing, or did
complete the processing but a distinct state could not be
determined.

Column Description
Unique ID Unique identifier given to an alarm during the Alarms process
life cycle. Composed of:
| Workstation ID of server workstation (in a cluster
configuration) that processed the alarm.
| Sequential ID, a sequential identifier in increasing order
per alarm. Not persistent and may change following each
alarm process initialization.
Primary ID When Alarm Correlation is enabled, shows the associated
primary alarm ID for each secondary alarm. (A primary alarm's
Primary ID is its own ID.)
When alarms are hierarchically sorted, this column facilitates
distinguishing between the following alarm types which appear
together at the end of the Alarms table:
| Alarms of the last set of secondary alarms
| The bulk of uncorrelated alarms
See Showing Secondary Alarms of a Primary.
Alarm Correlation-related icons
Toolbar Name
Description
icon
Show/Hide Toggles alternately between showing or hiding
/ Secondary Alarms secondary alarms (leaving only primary and
uncorrelated alarms in the table view); see Showing or
Hiding Secondary Alarms.
Hierarchical Sort Opens a new Current Alarms window with all the
primary and secondary alarms sorted hierarchically;
see Showing Secondary Alarms of a Primary.

Showing or Hiding Secondary Alarms

Suppressing secondary alarms from the table view enables you to focus your
efforts analyzing primary alarms. By default, secondary alarms are shown.
NOTE:
When secondary alarms are hidden, uncorrelated and primary
alarms in the network remain in the alarm table.
In the case of link or duct alarms:
If a duct alarm is present (all links associated with the duct
have the same alarm type), the link alarms are considered
secondary to the duct alarm and are hidden along with the
associated LOS alarms.
If a duct alarm is not present (not all links associated with
the duct are alarmed), the link alarms are considered
primary, so only the LOS alarms (and any other resultant
alarms) are hidden.
TIP: You can filter out uncorrelated alarms, leaving only

primary alarms; see Filtering Correlated Alarms. However, it
can be useful to keep uncorrelated alarms visible with
primary alarms since uncorrelated alarms are likely to be
primary alarms, even though the correlation processing could
not distinctively classify them.
To show or hide secondary alarms:
| Click the Hide Secondary Alarms icon to show only primary alarms
and uncorrelated alarms, hiding secondary alarms. The icon changes to
a Show Secondary Alarms icon.
| Click the Show Secondary Alarms icon to show all alarms,
regardless of primary/secondary status. The icon changes to a Hide
Secondary Alarms icon.

Showing Secondary Alarms of a Primary

You can view secondary alarms associated with primary alarms. The secondary
alarms are sorted under their root cause primary alarms. As well, link failure
alarms are sorted with LOS alarms under their respective duct failure alarm.
This can be done for selected secondary alarms, or all secondary alarms at once
(Hierarchical Sort, as shown in the picture below).
NOTE: When Hierarchical Sort is indicated:

Uncorrelated alarms are listed at the end of the table.
Secondary alarms associated with primary alarms that do
not normally appear in the Current Alarms window are
listed at the end of the table. Alarms of this category
include situations where the primary alarm's object:
- Is not in the user's resource domain.
- Doesn't fit the selected filter.
These alarms can be distinguished from alarms in the last set
of secondary alarms in the table by reference to the alarm
Primary IDs.
Columns of the Current Alarms window can also be sorted either individually
or in nested multiple groupings in the same way as in other LightSoft window
tables. For more information, see Sorting List Lines.
To show secondary alarms of selected primary alarms:

| Select one or more primary alarms, right click, and select Show
Secondary. A new Current Alarms window opens listing the selected
primary alarms with their secondary alarms sorted under them.

To show secondary alarms of all primary alarms in a window:
| Click the Hierarchical Sort icon on the toolbar. All primary and
secondary alarms are hierarchically sorted.
NOTES:
When the window is filtered beforehand, only sorting
involves only the alarms that are currently filtered in.
When hierarchical sort is performed, the alarm
correlation-specific columns are automatically displayed
in the window (if they were not already present).
Showing Primary Alarms of a Secondary

You can view the primary alarm associated with a selected secondary alarm in
a separate Current Alarms window.
To show the primary alarm of a selected secondary alarm:

| Select a secondary alarm, right-click and select Show Primary. A new
Current Alarms window opens with the selected alarm and its associated
primary alarm.
Filtering Correlated Alarms

All correlated and uncorrelated alarms appear in the table view (are filtered in)
by default. The Hide Secondary Alarms icon can be used to "filter out"
secondary alarms, leaving only primary and uncorrelated alarms in the table
view – see Showing or Hiding Secondary Alarms. As well, filters can be
defined to filter out either correlated or uncorrelated alarms.
TIP: When secondary alarms are hidden - see Showing or

Hiding Secondary Alarms - any uncorrelated alarms remain in
the view along with primary alarms. Keeping uncorrelated
alarms visible together with primary alarms can be useful
since these alarms are likely also primary, even if the
correlation processing could not distinctively classify them.

Acknowledging Notifications
Notification acknowledgement is a powerful tool in fault management. It
enables you to mark the alarms/events that are already handled. Filtering out all
acknowledged notifications then lets you focus on those that have not yet been
handled. You can acknowledge multiple notifications at the same time.
Acknowledgements for network alarms are sent to the EMS for handling and
then marked in the EMS as acknowledged.
The Counter bar in the LightSoft main toolbar shows you the number of
unacknowledged alarms of each category. For more information, see Alarm
Counter Bar.
NOTES:
Acknowledgements entered to link/duct alarms and
internal alarms (such as Disconnect) generated by
LightSoft are not sent to an EMS and are not persistent
following an alarm process initialization.
Acknowledging a primary alarm does not acknowledge its
secondary alarms. For information about primary vs.
secondary alarms, see Alarm Correlation.
To acknowledge a notification:
1. In the Current Alarms, Current Threshold Crossing Alerts, or Event
Log window, select a notification.
2. From the Alarm, TCAs or Events menu (according to the window), select
Acknowledge.
OR
On the toolbar, click Ack . A checkmark appears in the Acknowledged

( ) column.
OR
In the Current Alarms, Current Threshold Crossing Alerts, or Event
Log window, right-click a notification and select Acknowledge on the
shortcut menu.
OR
From the info window relating to that notification, click the Ack toolbar
icon .

Viewing Suggested Corrective

Actions
Suggested corrective actions for clearing a fault condition are available for
most notifications. These can be accessed for a selected notification either
directly from a fault management window or from the associated Info dialog
box. The Suggested Corrective Actions dialog box is accessed for one
notification at a time, but consecutively accessed dialog boxes can be left open
in the view for reference.
To view suggested corrective actions:

1. In any notification list window, select a notification.
2. From the Alarm, TCAs, or Events or Event Log History menu (according
to the fault management window), select Corrective Actions.
OR
On the toolbar, click .

OR
Open the notification's associated Info dialog box - see Fault Info Dialog
Boxes - and click . The Suggested Corrective Actions dialog box
opens.
If no corrective action is available, an Information dialog box to that effect

is displayed.
You can open Suggested Corrective Actions dialog boxes for additional
notifications by repeating the above steps for each one. The dialog boxes
remain open in the view until they are individually closed.

Fault Management Customization

You can customize the following aspects of alarm indication presentation.
| Customizing Fault Color Coding
| Changing the Alarm State Mode
Customizing Fault Color Coding

The Fault Management Preferences dialog box enables you to customize the
color coding that characterizes the standard alarm statuses of objects in
LightSoft. The alarm statuses Critical, Major, Minor, Warning, and
Indeterminate are customizable.
The colors you assign are applied to:

| Alarmed objects in the LightSoft main window map, the topology tree, and
each variation of trail list window, regardless of topology layer. The color
reflects the most severe fault involving the object.
| Severity column of line records in all fault management windows.
A separate set of colors can be assigned to acknowledged faults, shown when
the Unacknowledged alarm state mode is selected; see Changing the Alarm
State Mode. In the dialog box, these statuses have the suffix
"(Acknowledged)".

Usability state colors and the Cleared (green) alarm status are not user-
customizable. These are shown in the dialog box for reference purposes only.
For more information about alarm and usability states, see Object Status Color
Indications.
To customize the color of fault severities:

1. On the LightSoft main menu, select Faults > Fault Management
Preferences. The Fault Management Preferences dialog box opens.
2. In the Object Status Colors area, change the color associated with a status
by customizing its color swatch (color swatches that have a
More button are customizable). For information about standard color
customization, see Customizing LightSoft Object Colors.
NOTES:
The Restore System Defaults button returns all swatch
colors in the dialog box to their system defaults.
The Set System Defaults button is visible only to
authorized users. It is used to redefine the system default
colors for all LightSoft users who have not saved custom
colors to their user profiles, according to the color scheme
that the authorized user has currently defined. A
confirmation prompt appears before the action goes into
effect.
3. Click Apply to save the current settings. The dialog box remains open for
additional definitions if needed.
NOTE: Clicking Reset reverses any changes in the dialog

box since Apply or OK was used.
4. Click OK to close the dialog box. This also saves any last changes as when
clicking Apply.
Changes to the object color scheme are saved per user, and are constant from
session to session until they are changed again. The changes are immediately
reflected in map windows and the topology tree.

Fault Management Preference dialog box buttons
Button Description
Set System Defaults Redefines the system default colors available to all users
(Available to authorized according to the colors currently indicated in the dialog
users only) box. The action affects only users who have not saved
customized alarm colors to their user profile. To complete
the action, you must additionally click Apply or OK.
Restore System Defaults Restores system-default colors to all the color swatches in
the dialog box. The colors are saved to the user profile
only after clicking Apply or OK.
OK Saves the color changes to the user profile, and closes the
dialog box.
Apply Saves the color changes to the user profile, and keeps the
dialog box open for additional work.
Reset Reverses any changes in the dialog box since the last time
Apply or OK was used.
Cancel Closes the dialog box without saving any further changes.
Changing the Alarm State Mode

The Fault Management Preferences dialog box enables you to change the
alarm state presentation mode. This determines whether objects with all alarms
acknowledged should be separately color coded in map windows. (Map
windows include the LightSoft main window map and each variation of trail
list window, regardless of topology layer.)
The status bar at the bottom of the LightSoft window indicates the alarm state
mode that is currently active for your user profile.
| Actual icon (default) indicates that alarmed objects will be color coded
according to the highest severity of all associated alarms (regardless of
whether alarms are acknowledged).
| Unacknowledged icon indicates that alarmed objects will be color

coded according to the highest severity of only unacknowledged alarms. If
all of an object's alarms are acknowledged, the object will be color coded
according to a different scheme; see Customizing Fault Color Coding.
Separate color coding of objects with acknowledged alarms enables you to
identify new alarms on crowded maps more easily. The rationale and a method
for changing the alarm state mode is described in Alarm State Mode. Another
method is described in the procedure below.

Choosing the Unacknowledged alarm state mode does not affect the color
coding of the individual alarm records listed in fault windows - these continue
to reflect their actual fault status. In addition, alarm counters continue to reflect
the actual numbers of alarms of each severity in the network.
OPTIONAL FEATURE: The ability to switch between

alarm state modes is an optional feature. If not purchased,
color coding functions according to the Actual mode.
To change the alarm state mode:

1. On the LightSoft main menu, select Faults > Fault Management
Preferences. The Fault Management Preferences dialog box opens, as
shown in Customizing Fault Color Coding.
2. In the Alarm State Mode dropdown list, select the required mode from the
two options:
Actual Alarms
Unacknowledged Alarms
3. Click Apply to save the new setting. The dialog box remains open for
additional definitions if needed; see also Customizing Fault Color Coding.
NOTE: Clicking Reset reverses any changes in the dialog

box since the last time Apply or OK was used.
4. Click OK to close the dialog box. This also saves any last changes as when
clicking Apply.
Changes to the alarm state mode are saved per user. The changes are
immediately reflected in map windows and the topology tree.

Historical Events
LightSoft periodically exports the contents of Event logs so that they do not
become too large. This also enables you to keep a backup record of all events
in the network.
Exported logs are called Event Log History files and are stored as XML files.
For more information, see Exporting Excess Log Records and Clearing
Archives.
| Viewing Historical Events
| Configuring Event Logging, Archiving, and Historical Viewing
Viewing Historical Events

Event log history files are displayed in the Event Log History window, which
contains the same information and menu/toolbar options as the Event Log
window. The Event Log History window can be sorted and filtered. You can
view multiple event log histories by opening an Event Log History window
for each history file.
You can also export records data to a CSV file for viewing with other
applications.
To view an Event Log History file:

1. On the LightSoft main menu bar, select Faults > Event Log History; the
Import Log History Files dialog box opens.
2. Select one or more history files.

3. Click Import; the historical records appear in the Event Log History
window.
OR
Click Close to close the window without importing or exporting.
Configuring Event Logging, Archiving, and

Historical Viewing
The Event Log Configuration window enables you to:
| Archive excess or older records, view archived events, and periodically
clear archived files. For more information, see Exporting Excess Log
Records and Periodically Clearing Archives.
| Set the types of object-action combinations that will trigger the logging of
an event. For more information, see Setting Log Triggering Events.
To open the Event Log Configuration window:

| On the LightSoft main menu bar, select Faults > Event Log
Configuration. The Event Log Configuration window opens; see Setting
Log Triggering Events.
Exporting Excess Log Records and Clearing

Archives
The Event Log Configuration window Event Log Parameters tab enables
you to:
Set the maximum number and age of event records available for
viewing in the Event Log window (kept in the active Event Log
database).
Periodically remove excess/older records from the active database,
export them to XML files (at user-specified intervals), and save them.
Additional exports of excess records can be triggered manually.
The exported records are removed from the active database even if a
Clear event was not received for a particular alarm.
Exported events can no longer be viewed in the Event Log window.
They can be viewed with the Event Log History window; for more
information, see Viewing Historical Log Events.
Optionally delete older history files from a specified path, either
according to a schedule and/or manually. Deleted files are no longer
accessible from the Event Log History window.
Event log records in XML format can subsequently be converted to CSV for
viewing in a relational database program; for details, see Exporting to CSV.

To archive event records, view archived events, and

periodically clear archived files:
1. Open the Event Log Configuration window. The window opens with the
Event Log Parameters tab selected.
2. In the Configure Event Log parameters pane, set the maximum number
and age of records to be kept:
Database Event Log maximum capacity: maximum number of entries
that limits the size of the Event Log (that is, the number of records in
the database).
Database Event Log maximum period (in days): the age of the event in
the Event Log that limits the length of time (up to 10 calendar days) an
event can remain in the log.
3. In the Configure export to Event Log history files parameters pane, set
the export schedule and path:
How many times a day an export will be performed: select the daily
frequency (1 to 6); for example 3 indicates three times each day.
Starting at: enter this in HH:MM:SS format; for example, 13:00:00
indicates an export performed at 1 p.m..
If the daily frequency is 3, this implies that two additional exports will
be performed each day, at 8 p.m. and 3 a.m. respectively (that is, at
24/3 = 8 hour intervals).
Exported files directory path: enter a path to which the XML file will
be exported.
You can export files at any time between scheduled exports by clicking the
Force Export button and answering Yes in the confirmation dialog box.
Automatic exports continue to be performed according to schedule. The
exported files are listed in the list pane. However, the action is not final
until you click Apply.

4. In the Exported Event Log History files deletion policy pane, set when
the export files should be deleted:
Select the Do not Delete radio button to not automatically delete any
files.
OR
Select the Delete files older than radio button and the number of days
(5, 10, 20, or 30) to automatically delete files older than the specified
age. (The files are deleted according to the schedule defined in Step 3.)
You can manually delete selected files by clicking the Force Delete button
and answering Yes in the confirmation dialog box. This does not affect
scheduled removal of older files if the Delete files older than radio button
was selected. Deleted files are removed from the database and can no
longer be accessed from the Event Log History window.
5. If you made changes to the settings, click Apply.
NOTE: The Force Export to a file and Force Delete

actions are implemented immediately - they do not require to
be applied. The Force Export to file may take some time.
6. Click Close to close the window.

Setting Log Triggering Events

The Event Log Configuration window Event Types to Log tab enables you
to set the types of events that trigger the logging of an event. This is generally
set according to company policy.
To access the Event Types to Log tab:

1. Open the Event Log Configuration window and select the Event Types to
Log tab.
2. Select the checkboxes of object-action combinations corresponding to the

types of events that you want logged.
3. Click Apply to save your settings.
4. Click Close to close the window.

Filtering Fault Lists

By default, list windows display all alarms, TCAs, and events. LightSoft
enables you to filter lists so that a single list window displays only the
notifications that meet the filter criteria.
Each filter can be used to filter any number of list windows.
NOTE: You can display multiple views of a list, each with

its own filter and in its own window.
This section describes how to apply and define filters, as follows:

| Applying a Filter describes how to apply a filter to a notification list
window.
| Setting a Filter as Default describes how to set a filter so that it is
automatically applied each time the fault management window is opened.
| Filter Panel describes the various filter criteria and options.
| Creating a New Filter
| Editing a Filter, or Creating a Filter Based on an Existing One
| Deleting a Filter
| Filter Criteria
Filters are either user-defined or predefined.
User-defined filters
User-defined filters are created by LightSoft users. You can create them either
from scratch or using a predefined filter as a starting point, modifying its
parameters and saving it under a new name.
You can share filters with other users based on the following sharing options:
| Public - accessible to all users.
| User Group - accessible only to members of the same user group.
| Private - accessible only to the user who created it.
You can access filters from any workstation. Access privileges depend on
security settings. For more information, see Security.

OPTIONAL FEATURE: The save and publish user-

defined filter operations are optional features. If not
purchased, the features and related menu commands are
unavailable.
NOTE: A new filter with Public or User Group sharing

status is not visible to users who are already logged in when
the filter is created. To access the filter, these users must log
out and log in again.
Predefined filters
Predefined filters are supplied by LightSoft. They cannot be changed, but you
can use them as the basis for creating user-defined filters. LightSoft includes
the following predefined filters:
| No filter - shows all notifications.
| Critical/Major - shows only alarms with severity Critical or Major.
| Equipment - shows only equipment notifications.
| Optical - shows only optical-related notifications.
| SDH - shows only SDH-related notifications.
| Unacknowledged - shows only notifications not yet acknowledged.

Applying a Filter
You can apply user-defined or predefined filters to any notification list
window, either manually or automatically applying the current default filter.
The notifications that meet the filter criteria will be listed in the window.
Alternatively, you can apply a "temporary" filter by preselecting the objects of
interest before opening a fault management window. The temporary filter
overrides the current default filter.
To apply a filter to a fault management window:

1. If you want to see notifications pertaining to specific objects, select those
objects in the main window map. Otherwise, do not select any objects.
2. Open the notification list window that you want to filter (for example, the
Current Alarms window).
If any objects were preselected, the list automatically includes only notifications
pertaining to those objects. The filter selection list shows the following:
If no objects were preselected, the list is initially filtered according to the

current default filter.
3. If you want to use another existing filter:
Select a filter from the Filter Selection dropdown list on the window's
toolbar.
OR
On the Filter menu, select a filter category (Predefined Filter, Public
Filter, User Group Filter, or Private Filter) and select a specific
filter. The filter is applied to the list.
The Total statistic in the list window's status bar shows the total number of
records and the number of records that meet the filter criteria.
Filters can also be applied on a test basis (without saving) while creating new
filters or editing filters. Select criteria in the Filter pane and then click the
Apply icon ; see Filter Panel.

Setting a Filter as Default

When a fault management window is opened, its entries are initially filtered
according to the current default filter (unless objects were selected before
opening the window).
The current default filter is the filter with the Default symbol alongside (in
the Filter Selection dropdown list and filter selector on the menu bar).
Any filter can be set as the default filter in a specific fault management
window. Different defaults will continue to apply to other fault management
windows.
To set a filter as default:

1. Select an existing filter:
Select a filter from the Filter Selection dropdown list on the window's
toolbar.
OR
On the Filter menu, select a filter category (Predefined Filter, Public
Filter, User Group Filter, or Private Filter), and select a specific
filter. The filter is applied to the list.
2. To set this filter as the default filter, on the toolbar, click .

OR
On the menu bar, select Filter > Set filter as default. The symbol
appears alongside the selected filter in the filter selection lists.
When the window is next opened, its entries will initially be filtered according
to the current default filter.

Filter Panel
You create and configure filters for the fault management list windows in the
Filter panel. It is opened from any fault management window as described
below. It provides access to numerous criteria that can be selected for a filter,
organized within criteria categories.
To open or close the filter panel:

| From the fault management menu, select Filter > Show Filter Properties,
or select the Show/Hide Filter Properties toolbar icon . The Filter
panel opens.
The example shows all the filter criteria categories.

You can selectively show or hide categories according to your specific filter
requirements; see Showing and Hiding Filter Criteria Categories.
When a category is available in the panel, you can select specific criteria for the
filter; see Selecting Criteria for a Filter.
For information about the criteria included in each filter category, see Filter
Criteria.
Filter panel icons

Add/Remove Filter Adds or removes filter categories from which criteria
Items can be selected.
Apply Filter Applies the currently selected filter criteria to the fault
table.
Save Filter Saves a new filter or changes to an existing user-defined
filter under its current name.
Save Filter As Saves changes to a filter under a new name.


Delete Filter Deletes a selected user-defined filter.
Clear All Selections Clears all selections present in a selected filter. (The
same symbol in a category title is used to clear only the
selections of that category.)
Expand All Expands all the filter categories available for a filter at
once.
Collapse All Collapses all the filter categories available for a filter.
Hide Panel Hides the filter panel.
Showing and Hiding Filter Criteria Categories

You can show only those criteria categories relevant for the filter you are
working on. Categories can be displayed or hidden as needed.
NOTE: Only categories that are visible will be included in a

filter. Hiding a category from the filter panel clears any
criteria selections that were made in that category.
To show or hide filter criteria categories:
1. Click Add/Remove Filter Items on the filter panel toolbar. The

criteria categories selection panel opens.
2. Select or clear the checkboxes of categories you want shown/hidden for the
current filter.
3. Click Add/Remove Filter Items again to close the window.
You can also hide a category by clicking the Hide Panel icon .

Selecting Criteria for a Filter

A filter is built by expanding categories of criteria and selecting criteria as
needed.
To select or clear criteria for a filter:

1. With the Filter panel open, click the Expand criteria icon at the left
of a criteria category, for example, Severity, below. The criteria available in
that category are shown. (The icon changes to a Collapse criteria icon
for later use.)
You can also:
Expand all the categories at once by clicking Expand All , or

collapse them all at once by clicking Collapse All .
Expand a category while collapsing all other categories by clicking the
category title bar with the middle mouse button.
Resize an expanded category panel (with dynamic size content, such as
a list or tree) by dragging its lower edge.
2. Click the criterion you want to select for a filter. You can select multiple
criteria using the SHIFT or CTRL keys.
After a criterion is selected in a category, a Clear all selections icon

appears on the category header, indicating that selections have been made.

A Clear all selections in this panel icon also appears in the filter
panel header, indicating selections are present for the filter as a whole.
3. You can clear criteria selections, as follows:
a. Clear individual selections by clicking them again.
OR
b. Clear all selections within a category by clicking the Clear all
selections in this panel icon on the category header.
OR
c. Clear all selections for the filter as a whole by clicking the Clear all
selections icon in the filter panel header.
Creating a New Filter

This section describes how to create a new filter from scratch.
To create a new filter:

1. Open a notification list window, for example, the Current Alarms
window.
2. On the menu bar, select Filter > Create New Filter. The Filter panel
opens with the Filter Details category expanded.
3. Enter the new filter's name and description. (This can be done now or when
saving.)
4. Expand other categories and make selections as needed; see Selecting
Criteria for a Filter. If a required category is not shown, enable it as
described in Showing and Hiding Filter Criteria Categories.

5. Use the following options to help you create the filter (optional):
Click Apply to test the current filter settings in the list window.
The Total statistic in the list window's status bar shows the total number
of records and the number of records that meet the filter criteria.
Fine-tune the filter with additional settings and click Apply again to
retest it.
Click Clear to clear the current selections of a category or the filter
as a whole, and restart the filter criteria selection; see Selecting Criteria
for a Filter.
Click to close the filter panel without saving the settings.
6. Click Save Filter to save the filter. The Save Filter dialog box opens.
a. Enter or modify the filter name.

b. Select a sharing type. For details, see the User-defined filters section in
Filtering Fault Lists.
c. Click Save to save the filter and close the Save Filter dialog box.
7. Click to close the filter panel. The new filter is applied to the current
table. It is added to and can be retrieved from the filter list, under the
sharing type that you selected.

Editing a Filter, or Creating a Filter Based on

an Existing One
You can edit a filter or create a new filter based on an existing one. Predefined
filters can be edited and saved under a different name.
To edit a filter or create a filter based on an existing one:

window.
2. On the Filter menu or the filter selector dropdown list, select the filter you
want to edit or use as a base for a new filter. The filter is applied to the
table.
3. Click to open the Filter panel. The categories with selected criteria for
this filter appear and are expanded.
NOTE: You can also create a new filter based on the

existing filter called "No Filter", which has no criteria
selected.
4. Modify the criteria selections for the new filter. Expand other categories
and make selections as needed; see Selecting Criteria for a Filter. If a
required category is not shown, enable it as described in Showing and
Hiding Filter Criteria Categories.

5. (Optional) Use the following options to help you modify the filter:
Click Apply to test the current filter settings in the list window.
The Total statistic in the list window's status bar shows the total number
of records and the number of those meeting the filter criteria.
Fine-tune the filter with additional settings and click Apply again to
retest it.
Click Clear to clear the current selections of a category or the filter
as a whole, and restart the filter criteria selection; see Selecting Criteria
for a Filter.
If you want to discontinue the current work on the filter, click to

close the filter panel without saving the changes.
6. Click Save Filter to save the changes under the same name.
OR
Click Save Filter As to save a new filter, conserving the base filter
intact. The Save Filter dialog box opens.
If the base filter is user-defined, the name appears in the name field.
If the base filter is predefined, the name field is blank since the
modifications cannot be saved under the original filter name.
a. If you are editing a filter, keep the name as is.
OR
If you are creating a new filter, enter a new name.
NOTE: Filter names are case-sensitive.
b. Correct the sharing type if needed. For details, see the User-defined
filters section in Filtering Fault Lists.
c. Click Save to save the filter and close the Save Filter dialog box.
When a different name is entered for a filter, the changes are immediately
saved under the new name.

When the same name is entered for a filter:

If the original filter is user-defined:
"Save" will ask you to confirm the change to the existing filter.
Click Yes to complete the action and close the Save Filter dialog
box.
"Save As" will warn you that the name already exists and that you
must enter a different one.
If the original filter is predefined, both operations warn you that the
name already exists and that you must provide a different one.
(Predefined filters cannot be modified or deleted.)
7. Click to close the Filter panel. The new filter is applied to the current
table. It is added to the filter list and can be retrieved under the sharing type
that you selected.
Deleting a Filter
You can delete a user-defined filter that is no longer used. Deleting a filter does
not affect any notification. A list window filtered by the deleted filter will
return to a nonfiltered state. Predefined filters cannot be deleted.
NOTE: Deleting a filter requires appropriate user

permissions.
To delete a filter:
window.
2. On the Filter menu or the filter selector dropdown list, select the filter you
want to delete. The filter is applied to the table.
3. Click to open the Filter panel. The categories with selected criteria for
this filter appear and are expanded.
4. On the fault management menu bar, select Filter > Delete.
OR
From the Filter panel toolbar, click Delete Filter . A confirmation

dialog box appears.
5. Click Yes. The filter is deleted.

Filter Criteria
The filter panel includes the following criteria categories:
Notifications that have all the selected criteria in common are filtered into the
fault management window table. The filtering criteria must be simultaneously
met for a notification to be listed.
In all cases, you can select multiple objects using the CTRL or SHIFT keys.
Filter Details
The Filter Details category is used to identify a filter.
Filter Details information
Field Description
Name Name of the filter. Enabled only when a new filter is being
created; see Creating a New Filter.
Description Description of the filter.
The name of the user who performs actions on a filter (create, modify, or
delete) is recorded in the Activity Log window; see Activity Log Window.

Object Instance
The Object Instance category allows you to select the instances (for example,
ports, slots, or elements) where notifications will be filtered. Notifications from
the selected objects are displayed in the list window.
Select the topology layer in which the objects you want to filter are located. For
more information, see Topology Layers.
The tree structure below the Layer field shows the object structure as it appears
in the Topology Tree in the LightSoft main window. In this tree, select the
objects whose notifications you want LightSoft to display.
When a tree branch is selected, all objects beneath that branch are selected as
well.
Object Type
You can select individual or multiple objects by type (for example, EMS or
ME). When individual objects are selected, the object type limits the
notifications to those from the selected object types.

Severity
You can filter notifications according to severity level of the fault that caused
the alarm. Multiple severity levels can be selected. For details about the
Severity parameter, see Default Window Columns.
Probable Cause
You can filter notifications by probable cause as reported to the EMS. Multiple
causes can be selected. For details about the Probable Cause parameter, see
Default Window Columns.
Event Type
This category is only relevant from the Event or Event log History windows
and enables you to specify the type of event from the selected object you want
displayed in the list window. Multiple event types can be selected.

Rate
The Rate category defines the trail rate and/or the layer rates for which
notifications should be filtered.
The trail rate is the rate supported by LightSoft for a trail.
The layer rate is the transmission rate of an object.
When a trail rate is selected, all supported object layer rates (one or more) are
automatically selected in the Layer Rate area.
Alternatively, you can select one or more layer rates independently of the trail
rate.
General Probable Cause

You can filter notifications by a generic list of probable causes. Multiple causes
can be selected. For details about the General Probable Cause parameter, see
Optional Window Columns.

Event Time
Notifications can be filtered according to their arrival time in two ways:
| By Time Duration - notifications that arrived during the last X minutes,
hours, or days.
| By Time Range - notifications that arrived within a specified time range
(from date/time to date/time).
To filter notifications by their time of arrival:

1. Select the Time Duration radio button to filter notifications that arrived
during the past X minutes/hours/days. The Time Duration options open.
2. Select the age of the oldest required notification:

a. In the During the Last field, select a time quantity (up to 100) based
on the time unit you will choose in (b).
b. From the Minutes/Hours/Days dropdown list, select a time unit.
OR
3. Select the Time Range radio button to filter in notifications that arrived
within a specified date/time range. The Time Range options open.
4. Select the ages of the oldest and newest notifications:

a. In the From fields, enter the date (dd/mm/yyyy) and time (hh/mm/ss)
from which the range will span (defining the oldest possible record).
b. In the To fields, enter the date/time up to which the range will span
(defining the newest possible record).
The dates can either be entered directly to the date fields or via a calendar
accessed via the Calendar icons.

General Attributes
This category has options that vary according to the notification type. It also
enables filtering by a specified acknowledging user, or by an ME or EMS.
Notifications can be filtered by the following fields:

| Ack User Name: Allows you to filter a list by the users who acknowledged
the notifications.
| EMS/ME Name: Allows you to filter a list by an EMS or ME name.
Any portion of an object name (including any consecutive characters) can be
specified.
The following table describes additional attributes for filtering notifications,
selected by checking the checkbox.
Filter dialog box - More Properties tab options
Option Filter action when selected Applicability

Show Acknowledged All acknowledged notifications are filtered
in.
Show All notifications that were not
Unacknowledged acknowledged are filtered in.
Show Last Reported Notifications that cannot be updated are Alarms, TCAs
State Alarms filtered in. This means the ME (or EMS
managing it) that generated the notification
is disconnected from the network and
cannot update the notification status.
Show Current State Notifications that can be updated are Alarms, TCAs
Alarms filtered in. This means the ME (or EMS
managing it) that generated the notification
is connected.
Show Trail Affecting Alarms determined to be trail-affecting are Alarms only
filtered in. For a definition of this term, see
Optional Window Columns.
Show Non Trail Alarms that are determined to be non-trail- Alarms only
Affecting affecting are filtered in.

Option Filter action when selected Applicability

Show Service Alarms reported as non-service-affecting Alarms, Events
Affecting Only are filtered in. For a definition of this term,
see Optional Window Columns.
Show Correlated Shows all secondary alarms, in addition to Alarms only
Alarms primary alarms; for more information, see
Filtering Correlated Alarms.
Note: At least one of Show Correlated
Alarms or Show Non Correlated Alarms
must be selected.
Show Non Correlated Shows all non-correlated alarms - alarms Alarms only
Alarms which the correlation evaluation processing
could not distinctively identify as being
primary or secondary (or did not yet
undergo correlation processing); for more
information, see Filtering Correlated
Alarms.
Show Clearable Clearable notifications are filtered in. TCAs, Events
Events These events have an associated clear
event. For a definition of this term, see
Clearable and Nonclearable Alarms and
TCAs.
Filters Events only if the notification is a
TCA.
Show Non Clearable Notifications that are not clearable are TCAs, Events
Events filtered in. These events do not have an
associated clear event.
Filters Events only if the notification is a
TCA.
Show Cleared Events Notifications that were cleared are filtered Events only
in.
Show Non Cleared Notifications that were not cleared are Events only
Events filtered in.

Using Alarm Counters

Counters are a type of filter that displays the number of notifications that meet
specific criteria. The results appear on the Alarm Counter bar on the LightSoft
main toolbar; see Alarm Counter Bar.
The Alarm Counter bar has the following predefined alarm counters:
| Critical & Major - total of critical and major faults.
| Minor & Warning - total of minor faults and warnings.
| Disconnected EMS/ME - objects disconnected from LightSoft due to
communication problem between the EMSs and NEs, faults in the current
or another NE, or some LightSoft problem.
Double-clicking a counter for a specified severity opens the Current Alarms
window filtered for that counter's alarms. Right-clicking a counter allows you
to choose between Current Alarms or TCA windows, opening a filtered list
of the associated records. For more information, see Accessing Fault
Management Windows.
User-defined special-purpose counters can also be displayed in the Counter bar.
You can either create new counters or use a predefined or other counter as a
starting point, modify its parameters, and save the counter under a new name.
You can share any counter that you create with other users. The counter can be
set with the following sharing options:
You can access counters to which you are entitled from any workstation.
Access entitlements depend on security settings. For more information, see
Security.
NOTE: A new counter with Public or User Group sharing

status is not available to users who are already logged in
when the counter is created. To access the counter, these users
must log out and log in again.

defined counters operations are optional features. If not
purchased, the features and related menu commands are
unavailable.

Viewing Counter Information

Counters information appears in the Alarm Counters window.
Counters are created or configured in the Counter Properties dialog box,
which is accessed via the Alarm Counters window.
For general information about counters, see Using Alarm Counters.
To open the Alarm Counters window:

| On the LightSoft main menu bar, select Faults > Alarm Counters.
OR
On the toolbar, click . The Alarm Counters window opens.
When a counter is selected, the lower part of the window shows a graphical
breakdown of the total and unacknowledged alarms.
Alarm Counters window menu and toolbar options
Toolbar
Menu command Description
icon
Counter menu
Create New Creates a new counter; see Creating or Editing a
Counter.
Open Counter Opens the Counter Properties dialog box for the
selected counter; see Creating or Editing a Counter.
Delete Deletes the selected alarm counter; see Deleting a
Counter.
Close Closes the Alarm Counters window.
Help menu

Alarm Counters window columns
Column Description
Name Name of the counter.
Creator name Name of the user who created the counter.
Description Optional description of the counter.
Total Total number of alarms (acknowledged or not) that meet the
counter's criteria.
Unacknowledged Number of unacknowledged alarms.
Creating or Editing a Counter

You create or edit a counter in the Counter Properties dialog box in the same
way as the Filter dialog box when working with a filter.
Predefined counters cannot be edited unless saved under a different name.
You can add any counter's icon to the LightSoft main window
Counter bar.
To create or edit a counter:

1. If you are creating a new counter, in the Alarm Counters window:
Select Counter > Create New.
OR
Click the Create New icon . An empty Counter Properties dialog

box opens.
OR

2. If you are editing a counter or creating a new counter based on an existing

one, in the Alarm Counters window:
a. Select a counter.
b. Select Counter > Open Counter.
OR
Click the Open Counter icon . The Counter Properties dialog

box opens with the counter details.
3. Create or edit the counter in the same way as you would a filter, as
described in Creating a New Filter or Editing a Filter or Editing a Filter, or
Creating a Filter Based on an Existing One, with the following exceptions:
The More Properties tab includes Counter-specific options. For
details, see More Properties Tab for Counters.
The Filter dialog box contains Apply and Delete buttons, which are
not relevant for counters.
To display a counter on the LightSoft main window toolbar:

| In the main window toolbar, right-click in the Alarm Counter bar area to
open the counter checkboxes, and select the one corresponding to your
counter.

More Properties Tab for Counters

The More Properties tab is unique to the Counter Properties dialog box. It
allows you to select specific options.
The Counter Color Chooser enables you to select the color of the counter icon
on the LightSoft main toolbar. You can choose the color swatch from the
Swatches tab or select specific color values from the HSB or RGB tabs.
More Properties tab options
Option Filter action when selected

Count Last Reported State Alarms that cannot be updated (that is, the ME or EMS
Alarms managing the ME that generated the notification is
disconnected from the network and cannot update the
status of the notification) are counted.
Count Current State Alarms Alarms that can be updated (that is, the ME or EMS
managing the ME that generated the notification is
connected to the network) are counted.
Count Affecting Trails Alarms that are determined to be trail-affecting are
Alarms counted. For a definition of this term, see Optional
Window Columns.
Count Non Affecting Trails Alarms that are determined to be non-trail-affecting are
Alarms counted.


Count Clearable Alarms Clearable alarms are counted. These events have an
associated clear event.
Count Non Clearable Alarms that are not clearable are counted. These events
Alarms do not have an associated clear event. For a definition of
this term, see Clearable and Nonclearable Alarms and
TCAs.
Count Service Affecting Alarms that are reported as non-service-affecting are
Alarms Only counted. For a definition of this term, see Optional
Window Columns.
Count Non Updated Events Notifications that cannot be updated (when the ME or
EMS managing the ME that generated the notification is
disconnected from the network and cannot update the
status of the notification) are counted.
Count Updated Events Notifications that can be updated (where the ME or EMS
managing the ME that generated the notification is
connected to the network and can update the status of the
notification) are counted.
Deleting a Counter
You can delete a user-defined counter that is no longer useful. Predefined
counters cannot be deleted.
To delete a user-defined counter:

1. In the Alarm Counters window, select the counter you want to delete.
2. On the Counter menu, select Delete Counter.
OR
Click the Delete icon .

OR
Right-click the counter and select Delete from the shortcut menu.
The counter is deleted.

Using Alarm Indicators

Alarm Indicators (AIs) are a type of filter that triggers an audio and/or visual
notification when an alarm or TCA meeting the selected criteria is reported:
| Visual notification: Alarms can be notified on screen in an Alarm
Indicator popup. This feature is useful for operators interested in tracking
occurrences of certain (or all) alarms while they are away from the console,
without the need to track alarm counters.
The popup opens when conditions defined in an AI (that is set for visual
notification) are triggered. Additional alarms on the same AI are reflected
in the same dialog box as they arrive. When the conditions relate to a
different AI (involving same or different resources), another popup opens.
Each popup remains visible until it is closed by clicking the Close button.
The dialog box has the following features:
The title color reflects the currently received alarm with the highest
severity, the number of alarms, and the time of the most recent alarm.
You can scroll through the alarms using the arrows.
The Show Info button displays information about the currently visible
alarm. This is similar to the dialog box described in Fault Info Dialog
Boxes, but without an Acknowledge option (the alarms must be
acknowledged through the Current Alarms window).
| Audio notification: When an alarm of a specific type occurs, a sound file
can be played. In addition, if visual notification is configured, you can set
the audio notification to automatically sound intermittently until the Alarm
Indicator popup closes. Each alarm filter definition can be associated with
a different WAV sound file.
AIs, being a type of filter, enable you to view/hear only those alarms that are
currently relevant and need to be dealt with to ensure maximum system
performance. The criteria for a specific AI can include any attributes, such as
severity, layer type, or any combination of network resources (groups, MEs,
and even ports).

An AI can be enabled or switched off. When an AI is not enabled, it gives no

indication; see Enabling and Disabling an AI. When an AI is enabled, the
nature of its notification depends on how it is configured; see Configuring an
AI's Audio/Visual Behavior. Enabling/disabling an AI and configuring its
audio/visual behavior applies per user, regardless of whether the AI is shared
across users. The settings per AI are carried over to future user sessions.
AIs are either user-defined or predefined.
User-defined AIs
User-defined AIs are created by LightSoft users. You can create them using a
predefined AI as a starting point, modifying its parameters, and saving it under
a new name. Alternatively, you can create an AI from the beginning.
You can share AIs that you create with other users. The AIs can be set with the
following sharing options:
You can access any AIs to which you are entitled from any workstation. Access
entitlements depend on security settings. For more information, see Security.
Predefined AIs
The following predefined AIs are included in LightSoft:
| Critical - recognizes alarms whose severity is Critical.
| Major - recognizes alarms whose severity is Major.
| Minor - recognizes alarms whose severity is Minor.
| Warning - recognizes alarms whose severity is Warning.
Predefined AIs cannot be edited but can be used as the basis for creating user-
defined AIs.

defined AI operations are optional features. If not purchased,
the features and related menu commands are unavailable.
NOTE: A new AI with Public or User Group sharing status

is not available to users who are already logged in when the
AI is created. To access the AI, these users must log out and
log in again.

Viewing AI Information
You can view already-defined alarm indicators (AIs) in the Alarm Indicators
window. Each record in the list represents an AI and displays its properties.
For general information about AIs, see Using Alarm Indicators.
To open the Alarm Indicators window:

| On the LightSoft main menu bar, select Faults > Alarm Indicators.
OR
On the main toolbar, click the Alarm Indicators icon . The Alarm
Indicators window opens.
You can view the properties of an AI by selecting it and then selecting Alarm
Indicators > Open Alarm Indicator; see Creating and Editing an AI.

Alarm Indicators window menu and toolbar options
Toolbar
Menu command Description
icon
Alarm Indicators menu
Create New Creates a new AI; see Creating and Editing an AI.
Open Alarm Opens the Alarm Indicator Properties dialog box

Indicator for the selected AI; see Creating and Editing an AI.
Delete Deletes the selected AI; see Deleting an AI
Close Closes the Alarm Indicators window.

Help menu
Audio Indications window columns
Column Description
Enabled When selected, the AI is enabled and will sound/display when an
event matching the indicator criteria is received. The AI's specific
behavior is set in the Audio Indicator Properties dialog box
More Properties tab.
Name Name of the AI from the Name field in the Alarm Indicator
Properties dialog box.
Description Description of the AI from the Description field in the Alarm
Indicator Properties dialog box.
Creator name Name of the user who created the AI.

Creating and Editing an AI

You create or edit an AI in the Alarm Indicator Properties dialog box in the
same way as in the Filter dialog box when working with a filter.
Predefined AIs cannot be edited unless saved under a different name.
To create or edit an AI:

1. If you are creating a new AI, in the Alarm Indicators window:
Select Alarm Indicators > Create New.
OR
Click the Create New icon . An empty Alarm Indicator

Properties dialog box opens.
OR
2. If you are editing an AI or creating a new AI based on an existing one, in
the Alarm Indicators window:
a. Select an AI.
b. Select Alarm Indicators > Open Alarm Indicator.
OR
Click the Open Alarm Indicator icon . The Alarm Indicator

Properties dialog box opens with the AI details.

3. Create or edit the AI in the same way as you would a filter, as described in
Creating a New Filter or Editing a Filter, or Creating a Filter Based on an
Existing One, with the following exceptions:
The More Properties tab includes AI-specific options. For details, see
More Properties tab for AIs.
The Audio Indicator Properties dialog box does not have Apply and
Delete buttons, which are not relevant for AIs.
More Properties Tab for AIs

The More Properties tab is where you configure the AI itself. You decide
whether to enable operation of the Alarm Indicator popup window and/or
audio notification, and select the audio file. You can also set the audio
notification to automatically repeat every several minutes until the Alarm
Indicator popup window is closed. The Object Instance tab allows you to
select the type of alarm for which the AI will be activated.
You can define the AI's behavior and select the audio file that plays when an
AI is generated in the Indication Type pane.
Indication Type pane options

Audio File Name
Type an audio file path or click to browse for the
file you want. If no file is selected, the default ding.wav
sound file applies.
Click Test Audio to play the currently applicable file via
the console's speaker.
Play Sound on Alarm Select to play the audio file when alarm conditions arise
Arrival (default for a new AI).
Show Visual Indicator Select to display the Alarm Indicator popup when alarm
Window conditions arise.


Play Audio Reminder Every Select to sound the audio notification at periodic
intervals when the Alarm Indicator popup opens until it
closes. Enabled only when the Show Visual Indicator
Window checkbox is selected.
xx Minutes If Play Audio Reminder Every is selected, determines
time interval between audio notifications until the popup
window is closed. For example, 5 means five minutes
between reminders (minimum is 1).
AI filter options

Indicate Acknowledged Notifications that are acknowledged are alerted.
Alarms
Indicate UnAcknowledged Notifications that are not acknowledged are alerted.
Alarms
Indicate Updated Alarms Notifications that can be updated are alerted (the ME or
EMS managing the ME that generated the notification is
connected to the network and can update the status of the
notification).
Indicate Non Updated Notifications that cannot be updated are alerted (the ME
Alarms or EMS managing the ME that generated the notification
is disconnected from the network and cannot update the
status of the notification).
Indicate Trail Affecting Notifications that are determined to be trail-affecting are
Alarms alerted. For a definition of this term, see Optional
Window Columns
Indicate Non Trail Affecting Notifications that are determined to be non-trail-
Alarms affecting are alerted.
Indicates Clearable Alarms Clearable notifications are alerted. These events have an
associated clear event. For a definition of this term, see
Clearable and Nonclearable Alarms and TCAs
Indicate Non Clearable Notifications that are not clearable are alerted. These
Alarms events do not have an associated clear event.
Indicate Service Affecting Alarms that are reported as non-service-affecting are
Alarms Only alerted. For a definition of this term, see Optional
Window Columns.
NOTE: Audio indicators will only play on GUI clients

running on Sun workstations and not on remote sessions (for
example, on X-sessions or remote logins).

Enabling and Disabling an AI

An AI can be enabled or switched off. When not enabled, no indication is given
by the AI. Enabling or disabling an AI applies per user, regardless of whether
the AI is shared across users.
When an AI is enabled, the nature of its notification depends on how it is
configured. For more information, see Configuring an AI's Audio/Visual
Behavior.
To enable or disable an AI:

| In the Alarm Indicators window, select or clear the Enabled checkbox of
an AI to enable or disable its operation.
Configuring an AI's Audio/Visual Behavior

You can configure the nature of the notification given by an AI when it is
enabled. You can configure:
| The Alarm Indicator popup window that will be displayed.
AND/OR
| The audio notification that will be played when an alarm first arrives.
If the popup window is configured to appear, the audio notification can be
defined to play every few minutes until the popup window is eventually closed.
You can also choose and test the audio indication sound. Disabling the audio or
visual behavior does not delete the AI.
To configure an AI's behavior:

1. In the Alarm Indicators window, select the AI for which you want to
configure audio/visual notifications.
2. On the Alarm Indicators menu, select Open Alarm Indicator. The
Alarm Indicator Properties dialog box opens displaying the properties of
the selected AI.
3. On the More Properties tab, select or clear the checkboxes:
Play Sound on Alarm Arrival: Enables/disables the AI's audio
indication when an alarm first arrives.
Show Visual Indicator Window: Enables/disables the AI's Alarm
Indicator popup window.

4. Select an audio file. Type a file path or click to browse for the file
you want. (If no file is selected, the default ding.wav sound file applies.)
You can click Audio Test to play the audio file via the console's speaker.
5. If the Show Visual Indicator Window checkbox is selected:
a. Select or clear the Play Audio Reminder Every checkbox.
b. If selected, define the number of minutes between audio reminders
(default 1 minute, max. 99).
c. Click Save to save the AI. Click Clear to remove your selections and
begin again. Click Close to close the dialog box.
Deleting an AI
You can delete a user-defined AI that is no longer useful. Predefined AIs
cannot be deleted.
To delete an AI:
1. In the Alarm Indicators window, select the AI you want to delete.
2. Select Alarm Indicators > Delete.
OR
Click the Delete icon . The AI is deleted.

Viewing Alarmed Entities

| Viewing Traffic Entities Affected by an Alarm
| Viewing Alarms for Selected Traffic Entities
| Viewing EMS Current Alarms
Viewing Traffic Entities Affected by an Alarm

An alarm may affect one or more traffic entities. You can view a list of the
trails, tunnels, or services affected by a selected alarm. (These are actually
alarms on physical layer objects, not on the traffic entities themselves.)
NOTE: Rules determine whether an alarm is considered trail

affecting, especially in the case of link or duct failure alarms.
For more information, see the Trail Affecting column
description in Optional Window Columns.
To view trails, tunnels, or services affected by an alarm:

1. Open the Current Alarms window.
2. Select alarms where the Trail Affecting column shows (indicating that
the fault is trail-affecting).
Notice that the Affected Trails column shows either the trail label of the
affected trail or "Multiple" if more than one trail is affected.
3. Right-click and on the shortcut menu, select:
Show Affected Trails, OR
Show Affected Tunnels, OR
Show Affected Services.
You can also click the Show Affected Trails toolbar icon.
The associated List window opens showing the traffic entities affected by
the selected alarms.

Viewing Alarms for Selected Traffic Entities

You can view all the alarms that affect selected trails, tunnels, or services.
These alarms are displayed in the Current Alarms window.
You can also view the trails affected by a selected alarm; see Viewing Trails
Affected by an Alarm.
To view alarms for selected trails, tunnels, or services:

1. Open relevant traffic List window (Trail, Tunnel, or Service List),
ensuring that the required main map window objects are preselected and the
desired filter is set as the default; see:
Accessing the Trail List Window
Accessing the Tunnel List Window
Accessing the Ethernet Service List Window
2. In the Trails, Tunnels, or Services pane, select the checkboxes of the
traffic entities whose alarms you want to view.
3. Click the corresponding Show Current Alarms toolbar icon (for Trails
, Tunnels , or Services ). The Current Alarms window opens
showing the alarms on the selected tunnels.
4. (Optional) From the Current Alarms window, select one or more alarms
(these are actually alarms on physical layer objects, not on the traffic
entities themselves), right-click and choose:
Show Affected Trails, OR
Show Affected Tunnels, OR
Show Affected Services.
You can also click the Show Affected Trails toolbar icon.
The associated List window opens showing the traffic entities affected by
the selected alarms.

Viewing EMS Current Alarms

You can view all the alarms pertaining to a selected EMS-managed object, as
generated by the EMS. These alarms can also be viewed as reported by
LightSoft. In this case, the alarms are not filtered by object (you can use the
toolbar Filter function for this purpose).
To view the Current Alarms window of an EMS:

1. In the LightSoft main window, select the Physical (EMS) topology layer.
2. Right-click an EMS, or expand the EMS, right-click one of its managed
icons and select Current Alarms (EMS). The EMS Current Alarms
window for the selected object opens with alarms filtered for that object.
To view EMS alarms via the LightSoft Current Alarms

window:
1. In the LightSoft main window, select the Physical (EMS) topology layer.
2. Select Faults > Current Alarms.
OR
Select Configuration > Properties to open the Properties for EMS dialog
box and click Alarms .
EMS layer alarms are displayed in the LightSoft Current Alarms window.

Alarm Forwarding by FTP to

Remote Servers
LightSoft's Alarm Forwarder product add-on enables Netwide current alarms
export to remote FTP servers, providing a seamless interface with external fault
monitoring systems. The export uses an ASCII format, compatible with alarm
export applications of legacy EMS systems, and satisfies the requirement for
frequent network status reporting to central alarm centers.
The Alarm Forwarder additionally enables alarm notification by SMS (short
messaging service) or email to operator/technician cell phones and email
accounts. For details, see Alarm Forwarding by SMS and Email.
New alarms export

At periodic intervals, alarm details are automatically written to a LightSoft
local file, and the accumulated information records (since the last successful
export by FTP) are appended to target files at one or more FTP remote host
systems. If a target file does not exist, a new one is created. For information
about the file format, see FTP Export File Format.
After each successful export, the local file is cleared so that each cycle includes
new alarms. The target files maintain their cumulative notifications in
accordance with applicable record retention policies.
The file contents include regular alarm notifications as well as Clear indications
on previously reported alarms (not normally visible in the Current Alarms
window). TCA records are not included in the export process.
Snapshot export
LightSoft can also be configured to periodically back up (snapshot) all
notifications in the Current Alarms window to the same local file as new
alarms exports. The snapshot is automatically appended to the file at the remote
FTP host systems. In addition to snapshots at the configured frequency (if any),
a snapshot export is automatically performed each time the alarms export
feature is re-enabled. As with new alarm exports, the local file is cleared
following successful export to all remote hosts.
Snapshot exports are useful for redundancy and data consistency purposes, for
example, to resynchronize the remote database with the present alarm situation
in the network.
When Alarm Forwarder product add-on features are enabled, any user with
Fault Management administration capability can change the current export
configuration. No special UNIX security requirements apply.

NOTE: The remote file may contain duplicate notifications.

In such cases, timestamps can assist your analysis.
OPTIONAL FEATURE: Alarm Forwarder is a fully

purchased, the associated features will be disabled.
Alarm Forwarding by FTP Workflow

Once configured, alarm export by FTP operates in the background. It does not
require a user to be logged-in or a client to be currently running.
The configuration involves the following overall actions:
1. Enable the product add-on and configure new alarm export and snapshot
action frequencies; see Alarm Forwarding by FTP Configuration.
2. Configure the remote FTP servers to which the local file is exported; see
Remote Host Setup.
For information about the export file formats, see FTP Export File Format.
Alarm Forwarder Configuration Window

The Alarm Forwarder Configuration window is used to implement the
Alarm Forwarder product add-on features - both Alarm Export by FTP to
Remote Servers described in this section, and Alarm Forwarding by SMS and
Email. The window panels are described in context in this section.
To use the Alarm Forwarder Configuration window:

1. From the Faults menu, select Alarm Forwarder Configuration. The
Alarm Forwarder Configuration window opens.
2. On the selector pane, select the required functionality according to the
Alarm Forwarder configuration workflow step; see:
Alarm Forwarding by FTP Workflow or
Alarm Forwarding by SMS/Email Workflow
3. Complete the pane setups for the displayed Alarm Forwarder
Configuration window variation; see the descriptions in the table below.
4. Click OK to save the settings in the current panel and close the Alarm
Forwarder Configuration window. Other possible actions are described in
the functions list table below.

Alarm Forwarder Configuration window variations
Window variation Description

Alarm Export Enables the alarm export feature for FTP and configures its action
frequencies; see Alarm Export Panel.
Export Hosts Configures the remote FTP servers to which the local file is
exported; see Export Hosts Panel.
SMS/Email Specifies system-wide operational parameters for SMS/email
export; see SMS/Email Panel.
Alarm Forwarder Configuration window functions
Button Description
OK Saves the settings in the current panel and closes the Alarm
Forwarder Configuration window.
Reset Reinstates the last saved settings in the current window variation.
Apply Saves the settings in the current panel and keeps the window open
for more changes.
Cancel Closes the window without saving the current changes.

Alarm Forwarding by FTP Configuration

This section describes the Alarm Export panel and how it is used to enable the
alarm export feature for FTP and configure its action frequencies – the first step
of the Alarm Forwarding by FTP Workflow.
Alarm Export Panel

The Alarm Forwarder Configuration window Alarm Export panel is used
to enable the alarm export feature and configure its action frequencies.
The Alarm Export panel contains the following configuration options:

| Enable Export checkbox: When selected, enables the feature operation
(new alarm and snapshot writing to the local file and export to remote FTP
servers). When cleared, the feature is disabled.
A snapshot export is automatically performed whenever the checkbox is
newly selected and the revised settings are saved.
| Export File (Full Path): Name and path of the export file on the local
station. The same file is used for both new current alarm and snapshot
export purposes.
| Generate Snapshot Every X Hours: Sets the interval in hours between
scheduled snapshot actions, with values from 0 to 24 (in one-hour
increments). Default is 0, meaning no periodic snapshot exports are
performed.
Regardless of how this field is specified, a snapshot export is automatically
performed whenever the Enable Export checkbox is newly selected (see
parameter description above).
| Export Every X Minutes: Sets the interval in minutes between scheduled
new alarm exports to all defined remote hosts. Default is 5. "0" indicates no
exports are performed.

| Write to File Every X Minutes: Sets the interval in minutes between

writing new records in the Current Alarms window in the local file.
"0" indicates real-time mode, with new notifications recorded in the local
file immediately as they occur. Real-time mode enables alarms that are
quickly cleared to be recorded in the local file, so potentially more alarms
are forwarded. (Alarms occurring and clearing within a same interval are
not recorded.)
| Write Header Interval X Minutes: When Write to File Every is set to
"0", (real-time mode), the header line is normally suppressed. If no new
alarms occur over a protracted time, only a header line can be printed in the
local file at the set interval to signal that alarms are actually being
monitored. (This parameter is enabled only in real-time mode operation.)
Setting Up Alarm Export by FTP

The following procedure describes how to enable the feature and configure its
action frequencies.
To configure alarms export by FTP:

1. Open the Alarm Forwarder Configuration window; see Alarm Forwarder
Configuration Window.
2. Select Alarm Export. The Alarm Export panel opens.
3. Modify the parameters in the Export Configuration pane, including
selection of the checkbox to enable the feature if needed; see Alarm Export
Panel for parameter descriptions.
4. Click OK to save the current settings and close the window, or use Reset,
Apply or Cancel; see Alarm Forwarder Configuration Window.

Remote Host Setup

This section describes the Export Hosts panel and how it is used to configure
the remote FTP servers to which the local file is exported – the second step of
the Alarm Forwarding by FTP Workflow.
Export Hosts Panel

The Alarm Forwarder Configuration window Export Hosts panel is used to
configure the remote FTP servers to which the alarm records in the local file
are exported.
The top of panel list shows the currently defined hosts. The Host Details pane
(bottom of window) displays information about the selected host, as follows:
| Host Name: Name of the FTP remote host system. A host can be defined
by name or by IP address.
| User Name: User name used for remote FTP session access purposes.
| Password: Password used for remote FTP session access purposes.
| Remote File (Full Path): Name and path to the FTP remote file.
These fields can be edited; see Setting Up Remote Hosts.
The Host Details pane contains the following buttons:
| Add: Adds a new FTP host; see Add procedure see Setting Up Remote
Hosts.
| Delete: Deletes the currently selected FTP host; see Delete procedure in
Setting Up Remote Hosts.
| Replace: Saves edit changes to parameters of the currently selected host;
see Edit procedure in Setting Up Remote Hosts.

Setting Up Remote Hosts

Any number of remote hosts can be configured to receive exported alarm
notifications by FTP.
To add a remote host to the FTP distribution list:

1. Open the Alarm Forwarder Configuration window; see Alarm Forwarder
Configuration Window.
2. Select Export Hosts. The Export Hosts panel opens; see Export Hosts
Panel.
3. Enter the parameter values in the Host Details pane.
4. Click Add. The host details are added to the list of hosts at the top of the
panel.
5. Click OK to save the change in the distribution list and close the window,
or use Reset, Apply or Cancel; see Alarm Forwarder Configuration
Window.
To edit host information in the distribution list:

1. In the Export Hosts panel, select the host whose information you want to
change. The information appears in the Host Details pane.
2. In the Host Details pane, modify the information as needed.
3. Click Replace. The new information appears in the list (top of panel).
4. Click OK to save the change to the host profile and close the window, or
use Reset, Apply or Cancel; see Alarm Forwarder Configuration Window.
To delete a host from the FTP distribution list:

1. In the Export Hosts panel, select the host that you want to remove and
click Delete. The host is removed from the list at the top of the dialog box.
2. Click OK to save the change and close the window, or use Reset, Apply or
Cancel; see Alarm Forwarder Configuration Window.

FTP Export File Format

The export file uses a fixed file format compatible for customers using similar
alarm reporting at the EMS level. The exported content includes a header and
alarm records, as follows:
Header - Each new set of exported records starts with the following header
information:
| Export time: Default dd/mm/yyyy hh:mm:ss. The date/time format is
configurable; see Customizing Time Formats.
| Column headers: Event Time, Severity, Object, and Probable Cause.
Records - Each alarm record consists of one line with the following attributes
(internal format of fields may differ from EMS formats):
| Time: Date/time of the alarm as recorded by the EMS. Default
dd/mm/yyyy hh:mm:ss. The format is configurable; see Customizing Time
Formats. (Begins in column 2. A time format longer than 19 characters is
truncated.)
| Severity: Severity of the alarm - Critical, Major, Minor, Warning, or
Cleared. (Begins in column 21, 11 characters.)
| Object: Name of the alarmed object - NE name followed by the native
name from the EMS system (usually a port), separated by “:” (for example,
NE-1:PTP-2). A name longer than 40 characters is truncated.
(Begins in column 34. A name longer than 40 characters is truncated.)
| Probable cause: Probable cause of the alarm. (Begins in column 76. A
name longer than 42 characters is truncated.)
A snapshot export appends all Current Alarms window information in the
same file as new alarm records, with an indication (FULL-LIST or #####)
before the header to identify the nature of the data.
In the remote file, each writing action is followed by a blank line.
If no changes occurred in the Current Alarms window since the last export, only
the export time and a header record are sent. If real-time mode applies, the header
is normally not sent. However, sending the header at periodic intervals can be
forced by setting the Write Header Interval parameter; see Alarm Export Panel.
The following is an example of FTP file content:

Alarm Forwarding by SMS and

Email
LightSoft's Alarm Forwarder product add-on provides alarm notification by
SMS (short messaging service) and email to operator/technician cell phones
and email accounts. This is especially useful to service providers not manning
network operations centers (NOCs) 24 hours a day.
Alarm notification thresholds (alarm count per time interval) determine how
the information is delivered. If the number of alarms is under the threshold, the
alarms are delivered individually. Otherwise, a statistical summary is sent.
Separate thresholds are maintained for SMS and email purposes.
The Alarm Forwarder also enables alarm export by FTP to remote clients. For
details, see Alarm Forwarding by FTP to Remote Servers.
When Alarm Forwarder features are enabled, any user with Fault Management
administration capability can change the current export configuration. No
special UNIX security requirements apply.
NOTE: LightSoft SMS delivery relies on an email-to-SMS

or HTTP-to-SMS gateway to convey email messages to SMS
devices. It does not operate with native SMS devices directly.
OPTIONAL FEATURE: Alarm Forwarder is a fully

Alarm Forwarding by SMS/Email Workflow

Once configured, alarm export by SMS/email operates in the background. It
does not require a user to be logged-in or a client to be currently running.
Messages of new alarms are sent to a user's SMS and/or email account once the
following overall actions are performed:
1. Specify system-wide operational parameters for SMS/email export; see
Setting Up Alarm Export by SMS/Email.
2. Enable the feature on a per user basis and specify a valid cellular phone
number (for SMS) and/or email address for the user; see SMS/Email Export
Per User Setup.
3. Define filters per user (at least one SMS and/or email filter); see Setting
SMS/Email Notification Filters.
For information about the export file formats, see SMS and Email Alarm
Format.

Alarm Export by SMS/Email Configuration

This section describes the SMS/Email panel and how it is used to specify
system-wide operational parameters for SMS/email export – the first step of the
Alarm Forwarding by SMS/Email Workflow.
SMS/Email Panel
The Alarm Forwarder Configuration window SMS/Email panel contains
parameters governing SMS and email export system-wide (for example,
threshold levels that determine whether alarms are delivered individually or as
statistical summaries).
The example window shows the default settings. The following information is
provided for SMS and email, respectively:
SMS Settings pane:
| Max Notifications per Interval: Alarm count (within the specified time
interval) which triggers sending a statistical summary of alarms by SMS
instead of individual alarms.
| Interval Size X Minutes: Time interval between scheduled SMS export
actions.
| Max Message Size: Maximum size of an SMS alarm notification. If
exceeded, the message is split into several SMS messages (split on a field
separator).
| SMS Gateway: Address of SMS Gateway:
For email-to-SMS gateway:
Enter the SMS Gateway hostname or IP address.
For HTTP-to-SMS gateway:
Enter the URL to be sent to SMS Gateway.

HTTP-to-SMS gateway example (enter as one continuous string):

http://sms.cellphonecompany.com/scripts/
smsgate.asp?
username=myusername&
password=mypassword&
target={target}&
source=mysourcenumber&
message={message}
{target} and {message} do not require manual intervention. LightSoft
automatically replaces {target} with the user phone number shown in the
Number field in the Configure SMS/Email dialog box, and {message}
with the actual alarm notification message.
NOTE: You need to have access to the company's SMS

server from the LightSoft server.
Email Settings pane:

| Max. Notifications per Interval: Alarm count (within the specified time
interval) which triggers sending a statistical summary of alarms by email
instead of individual alarms.
| Interval Size X Minutes: Time interval between scheduled email export
actions.
NOTE: Email must be configured through the operating

system (not via LightSoft). Use your company's SMTP server
address for the email messaging protocol. The email address
would be:
<user>@<companyname.com>.

Setting Up Alarm Export by SMS/Email

The following procedure describes how to set up the alarm export feature for
SMS/email and specify its system-wide operational parameters.
To set up alarm export by SMS/email:

1. From the Faults menu, select Alarm Forwarder Configuration. The
Alarm Forwarder Configuration window opens.
2. Select SMS/Email. The SMS/Email panel opens.
3. Modify the parameters as needed for SMS and/or email purposes; see
SMS/Email Panel.
4. Click OK to save the current configuration and close the Alarm
Forwarder Configuration window. Click Apply to save the current
changes and keep the window open for more changes. Click Reset to
reinstate the last saved settings. Click Cancel to close the window without
saving the current changes.
5. Configure which LightSoft station to send:
Email; see Enabling a LightSoft Station to Send Email.
SMS; see Enabling a LightSoft Station to Send SMS.

SMS/Email Export per User Setup

This section describes the SMS/Email dialog box and how it is used to specify
the SMS/email addresses to which notifications are sent. This feature is enabled
on a per user basis – the second step of the Alarm Forwarding by SMS/Email
Workflow. The dialog box is accessed from the Add User or Edit User dialog
box for each user – see Managing User Accounts.
Configure SMS/Email Dialog Box

The Configure SMS/Email dialog box is used to specify the SMS/email
addresses to which notifications are sent, to enable the feature on a per user
basis, and to access the Filter dialog box for specifying filters.
The dialog box contains the following components for SMS and email
specification, respectively:
SMS:
| Enabled checkbox: Select to enable SMS notification for the selected user.
By default, initially disabled.
| Number: Cellular phone number to which the SMS notifications should be
sent.
| Filter button: Opens the Filter dialog box where you can define filters for
SMS notifications (at least one must be defined for the feature to operate
for the user); see Setting SMS/Email Notification Filters.

Email:
| Enabled checkbox: Select to enable email notification for the selected user.
By default, initially disabled.
| Address: Email address to which the email notifications should be sent.
| Filter button: Opens the Filter dialog box where you can define filters for
email notifications (at least one must be defined for the feature to operate
for the user); see Setting SMS/Email Notification Filters.
TIP: Sending alarm notifications can be disabled temporarily

for a user, for example, at vacation time.
Configuring SMS/Email Alarm Export per

User
The following procedure describes how to enable the feature on a per user basis
and specify a cellular phone number for SMS and/or email address.
To enable/disable the SMS/email feature per user and to

specify addresses:
1. Open the Add User or Edit User dialog box for the relevant user – see
Managing User Accounts.
2. Click the Configure SMS/Email button. The Configure SMS/Email
dialog box opens; see Configure SMS/Email Dialog Box.
3. Modify the parameters as needed for SMS and/or email purposes, as
described in the section above.
4. Click OK to save the changes and close the dialog box.
5. In the Add User dialog box (which remains open), click Save to save the
changes.

Enabling a LightSoft Station to Send Email

You must perform the following configuration procedure to enable a LightSoft
UNIX station to send email.
To enable a LightSoft station to send emails:

1. Define the name of the mail server by updating the file
/etc/mail/sendmail.cf to include the following line:
DSmailhost.mycompany.com
(substitute your own mail server name in place of "mycompany.com".
Consult your network administrator for details.)
2. In the mail server, define the IP address and the name of the LightSoft
station (in the case of zones, the IP address and name of LightSoft zone).
3. The DNS services in the LightSoft UNIX station must be currently
operating. If the DNS client is disabled, enable it as follows:
Obtain the relevant DNS client IP addresses from your network
administrator.
Edit the file /etc/resolv.conf to include the following lines:
domain mycompany.com (substitute your own domain name)
nameserver xxx.xxx.xxx.x (substitute a DNS server IP
address)
nameserver xxx.xxx.xxx.x (substitute a DNS server IP
address)
Then run the following command:
svcadm enable sendmail
4. Check the configuration by using the following command to send an email:
mailx –v firstname.lastname@ecitele.com
Subject: Type the subject <ENTER>
Type the mail content <ENTER>
. (dot) <ENTER>

Enabling a LightSoft Station to Send SMS

You must perform the following configuration procedure to enable a LightSoft
UNIX station to send SMS.
To enable a LightSoft station to send SMS:

1. Define the name and IP address of the SMS mail server in the /etc/hosts file
of NMS zone. For example, sms.mycompany.com.
(Substitute your own mail server name in place of "mycompany.com".
2. Ensure that LightSoft has access to the SMS mail server.
3. Ensure that the name and IP address of the LightSoft station (in the case of
zones, the name and IP address of NMS zone) has firewall access enabled.
4. Verify the mail sending, using the command:
nms(z1-csl-18) /tmp > echo "Test" | sendmail <PHONE_NUMBER>@<
SMS server > example: PHONE_NUMBER@sms.mycompany.com
(Substitute your own mail server name in place of "mycompany.com".

Setting SMS/Email Notification Filters

This section describes how to define SMS/Email notification filters – the third
step of the Alarm Forwarding by SMS/Email Workflow. At least one
notification filter per user has to be defined for this feature to be operational.
Disabling alarm notifications temporarily for a user (for example, for vacation)
has no effect on the user's defined filters. Once re-enabled, the same filters
apply as before.
SMS/Email Filter Dialog Box

The SMS Filter (shown below) and Email Filter dialog boxes are used to set
filters for SMS and/or email alarm export for the current user.
Multiple filters can be defined with different criteria or all alarms can be
filtered in. Specific filters can be removed. At least one filter must be defined
per user for SMS or email export to work.
When no filters have yet been defined, the filter window opens with one
column including criteria for a filter "A". When multiple filters are defined the
criteria for each filter are arranged in columns. The example above shows two
filters defined for the user.

The SMS Filter and Email Filter dialog boxes include the following filter
categories for each filter. You can select one or more filter criteria for a specific
filter. The available categories are similar to those defining fault filters; see
Filter Criteria:
| Severity: Filters alarms according to severity level of the fault that caused
the alarm. Multiple severity levels can be selected.
| Object Instance: Specifies the network resources (ports, slots, or elements)
from which alarms will be filtered in. Multiple objects can be selected.
| General Probable Cause: Specifies the probable cause (equipment or
other) as reported to the EMS for which alarms will be filtered in.
General Probable Cause uses a generic list of probable causes, whereas
Probable Cause is the probable cause that appears in the EMS; see Probable
Cause in Default Window Columns.
The SMS Filter and Email Filter dialog boxes include the following buttons:
SMS/Email Filter dialog box functions
Button Description
OK Saves the current filter and closes the filter dialog box.
Add Filter Item Adds a new column, enabling another filter to be defined.
Remove Filter Item Removes the currently selected filter.
Cancel Closes the window without saving the current changes.

Setting SMS/Email Alarm Notification Filters

At least one filter must be defined in order for the feature to function for the
current user.
To set alarm notification filters:

1. Open the Configure SMS/Email dialog box; see Configuring SMS/Email
Alarm Export per User.
2. Click the Filter button. The SMS/Email Filter dialog box opens.
If filters have already been defined for the user, the dialog box opens with a
separate column for each filter (labeled "A", "B", and so on), with specific
criteria selections for each filter. To modify, remove, or add another
specific filter, go to Step 4.
If no filters have yet been defined, the dialog box opens with a single
column of filter criteria (labeled "A" for Filter A), with no selected criteria.
3. If you want all alarms filtered in, do not select any criteria. Go to Step 5.
OR
If you want to define specific filters:
Select one or more criteria for the current filter; see the parameter
descriptions in the section mentioned above. A Clear all selections
in this panel icon appears on the category header after a
criterion is selected. (You can clear all selections in a category by
clicking this icon.)
If you want another specific filter, click the Add Filter Item
button. A new column of filter criteria opens. Select one or more
criteria for the additional filter, as described above. Repeat this step
for as many specific filters as required.
OR
4. Modify, remove, or add another specific filter, as follows:
To modify a filter:
Change the criteria selections in the filter's column. (To remove all the
selections in a specific filter category, click the Clear all selections in
this panel icon on the category header.)
To remove a filter:
Select the filter by clicking anywhere in the filter column and click the
Remove Filter Item button.
To add another filter:
Click the Add Filter Item button. A new column of filter criteria
opens. Define the additional filter as described in Step 3 above.

NOTE: The Add Filter Item button is not enabled if all

alarms are already set to be filtered in.
5. Click OK to save the filters and close the dialog box.
SMS and Email Alarm Format

Every SMS and email starts with the subject line "ECI".
SMS Alarm Format

The alarm notification message includes the following information and format:
<severity> <object name> <alarm type> <time>, <service affecting>
where:
Severity One of Critical, Major, Minor, Warning, or Cleared.
Object name Name of the alarmed object - displaying the names of the object
hierarchy from NE to alarmed object (e.g. NE-1:PTP-2). Objects
in the hierarchy are separated by “:”. Slot number is provided
when possible.
Alarm type Type of the alarm, for example, Card Out.
Time Event date/time (default - dd/mm/yyyy HH:MM:SS).
Affected trails List of affected trail labels.
Cleared "Cleared" appears in the case of a Clear notification.
Clear time Date/time the alarm was cleared (default - dd/mm/yyyy
HH:MM:SS).
Maximum size of an SMS alarm notification is set according to the Max

Message Size parameter; see SMS/Email Panel. Any excess size is truncated.
Email Alarm Format

The email format is similar to the FTP notification format; see FTP Export File
Format. No maximum size applies for email notifications.
Statistical Summary Message Format

The alarm summary message for both SMS and email includes the following
information:
ECI alarms summary: critical – NC, major – NMA, minor – NMI, warnings –
NW, cleared - NCL,
where NC, NMA, NMI, NW, NCL are the current alarm counts of the
corresponding severity.

User Notes
User notes are comments to other users that can be attached to notifications.
For more information, see Viewing and Attaching Notes on Fault Notifications.


7
Managing Traffic
In this chapter:
Overview ......................................................................................................... 7-1
3
Transport Architecture ..................................................................................... 7-3

3
Traffic Management Preferences ..................................................................... 7-5

3
Overview
LightSoft features extremely powerful optical transport-based traffic
management capabilities with full trail support for all technology layers. The
technologies include direct optical layer topologies, SDH high order and low
order topologies, and SDH-based Ethernet topologies. The latter include EoS
trails and MPLS trails and tunnels, and a range of corresponding Ethernet
services.
This section provides an overview of traffic management, including how to set
the optimization constraints that the pathfinder (PF) algorithm should consider
when determining new trail, MPLS tunnel, and Ethernet service paths.
Subsequent sections describe trail, MPLS tunnel, and Ethernet service concepts
and creation procedures.
Provisioning
These sections describe how to create the traffic infrastructure:
| Provisioning SDH and EoS/MoT Trails describes how to create SDH and
SDH-based Ethernet trails with the Create Trail window and planned
trails with the Plan Trail window, involving a variety of trail creation
options and protection mechanisms.
| Provisioning MPLS Tunnels describes how to create MPLS tunnels, the
infrastructure for Ethernet services.

Managing Traffic LightSoft User Manual
| Provisioning Ethernet Services describes how to create MPLS and VPLS

L1 and L2 carrier class E2E Ethernet services.
| Provisioning Optical Trails describes how to create OMS, OCH, and LP
optical trails using various methodologies.
Operations on Traffic Entities

These sections describe the List windows used to view and manipulate the
traffic infrastructure information:
| Performing Actions on Trails describes the trail management interface and
trail-related operations.
| Provisioning MPLS Tunnels describes the tunnel management interface
and tunnel-related operations.
| Performing Actions on Ethernet Services describes the service management
interface and service-related operations.
Synchronization
These sections describe how to reconcile differences between traffic entity
definitions in LightSoft and an EMS, or acquire traffic entities defined at the
EMS level:
| Synchronizing Trails describes how to use the Trail Consistency
Indicator window to reconcile differences between trail definitions in
LightSoft and an EMS, or acquire optical trails defined at the EMS level.
| Synchronizing Tunnels describes how to reconcile tunnel differences.
The capability profile of your user group determines the functions you may
perform. The resource domain of your user group determines the objects you
may manage. For complete information regarding the visibility rules of objects
in LightSoft, see Managing Resource Domains.

LightSoft User Manual Managing Traffic
Transport Architecture
LightSoft is a multidimensional technology manager. The section Relationship
Between Physical and Technology Layers shows how physical elements are
represented in their own technology layer in the client-server architecture. The
possible transport architecture configurations are represented in the diagram
below.
The following types of trail - tunnel - service layering are supported by

LightSoft and described in the sections that follow:
| Ethernet services traverse:
MPLS tunnels (VPLS services) (1a)
EoS trails (L1 and L2 services) (1b)
For details about the variety of Ethernet services supported by LightSoft
and how they are managed, see Provisioning Ethernet Services.
| MPLS tunnels (infrastructure for Ethernet services) traverse:
MoT trails (2a)
For details about MPLS tunnel management, see Provisioning MPLS
Tunnels.

| SDH trails (high order and low order) (including EoS and MoT high order
and low order) traverse:
OTN layer (3a)
Physical optical fiber directly (3b)
For details about SDH and EoS/MoT trail management, see Provisioning
SDH and EoS/MoT Trails.
| EoS trails (infrastructure for L1 and L2 Ethernet services) also traverse:
Optical layer directly (3c) in the case of some combiners
For details about EoS trails that traverse the optical layer, see Provisioning
Optical Trails.
| OTN trails traverse:
Physical (such as optical fiber) directly (1a)
For details about optical trail management, see Provisioning Optical Trails.
The topology configuration decisions (for example, SDH over optical vs.
physical) are based on the network architecture. The transport infrastructure
that different services traverse involves trail and tunnel client-server layering
according to their technologies. For example:
| A topology that includes an optical layer can have SDH (3a) or Ethernet
services (3a, 3c) traversing it, benefiting from optical layer rate flexibility.
| If an optical layer is unavailable, traffic can be carried over SDH rings,
directly traversing the physical optical fiber (3b).
| Ethernet traffic usually traverses SDH rings (EoS) (1b), but can also
traverse the optical layer directly (3b). MoT trails must traverse the SDH
layer (2a).
Ethernet Services
Ethernet services comprise L1 and L2 services, as follows:
| Ethernet L1 P2P service (EPL).
| Ethernet L2 services of types MP2MP, P2P, Routed Multipoint, and P2MP.
For more information, see Supported Ethernet Service Types.

LightSoft User Manual Managing Traffic
Traffic Management Preferences

Traffic preferences define how trails, tunnels, and Ethernet services are created
in LightSoft, and which fields are visible in various parameter windows. The
preferences are grouped in panes of the User Preferences window, described
in detail in the following sections:
| Trail Creation Management
| Tunnel Creation Management
| Service Creation Management
The preferences are applied and saved on a per-user basis.
Setting Traffic Preferences

Trail, tunnel, and Ethernet service configuration preference settings are
implemented in the User Preferences window. The window panes are
described in context in this section.
To set traffic preferences:

1. On the System menu, select Preferences.
OR (for Trails or Tunnels)
From the Trail Properties pane or Tunnel Parameters Tab User Selection
view, click the Configure Attributes List icon . The User Preferences
window opens.
2. Select the required window variation in the selector pane.
3. Complete the pane definitions, as described in the following sections:
Trail Creation Management
Tunnel Creation Management
Service Creation Management
4. Click OK to save the settings in the current window variation and close the
User Preferences window. Other possible actions are described in the
functions list tables below.

User Preferences window variation - specific functions
Button Description
Apply Saves the settings in the current window variation panes and keeps
the window open for more changes.
Reset Reinstates the last saved settings in the current window variation.
Defaults Restores the system default settings to the panes in the current
window variation.
Current Alarms Export window overall functions
Button Description
OK Saves the current settings in the window as a whole and closes the
User Preferences window.
Cancel Closes the window without saving the current changes in panes of
any window variation.
NOTE: Trail, tunnel, and service management preference

settings are saved per user, while trail and tunnel constraint
settings are saved system wide, applying to creation activities
of all users.

8
Provisioning SDH and
EoS/MoT Trails
In this chapter:
Overview ......................................................................................................... 8-1
Trail Concepts.................................................................................................. 8-3
3
Trail Creation Management ........................................................................... 8-12

3
Trail Creation Options ................................................................................... 8-18

3
Creating SDH and EoS/MoT Trails ............................................................... 8-20

3
Create Trail Window ..................................................................................... 8-32

3
Ring Interworking Protection ........................................................................ 8-59

3
Planned Trails ................................................................................................ 8-65

3
Overview
This section describes how to create SDH and SDH-based Ethernet trails with
the Create Trail window and planned trails with the Plan Trail window,
involving a variety of trail creation options and protection mechanisms.
SDH-based Ethernet trails comprise:
| Ethernet over SDH (EoS) trails, which are SDH (high order and low
order) trails and are the infrastructure for L1 and L2 Ethernet services.
| MPLS over Transport (MoT) trails, which are SDH (high order and low
order) trails and are the infrastructure for MPLS tunnels.

Provisioning SDH and EoS/MoT Trails LightSoft User Manual
NOTE: Creating EoS trails that traverse the OTN layer (as
needed in the case of certain data combiners) is done in one of
the following ways:
By Discovery using the Discover Optical Trails feature.
The EoS trail that traverses the optical layer is created in
addition to the optical trails. For details, see Creating
Optical Trails Through Discovery.
By admitting the high order SDH trail using the Trail
Consistency Indicator window; see Performing Trail
Synchronization.
Optical trail creation is described in Provisioning Optical Trails.

Trails have a rate and a payload based on their endpoints (for example, a rate of
VC-3 and a payload of E3). For a list of supported trail rates and payloads, see
Supported Rates and Payload Types.
OPTIONAL FEATURE: The SDH and EoS trail

provisioning mechanism is subject to the SDH layer being
enabled. This is an optional feature. If not purchased, the
functionality and related menu options are unavailable.

LightSoft User Manual Provisioning SDH and EoS/MoT Trails
Trail Concepts
The following sections provide some key trail concepts. Other concepts are
explained in context.
| Trails and Virtual Links
| SRLG and Other Shared Resource Minimization in PF Trail Path Selection
| CAC for MoT Trails
| LAG Support
| CNM and Trail Provisioning
| LightSoft ASON Support
| ASON Protection Schemes
Trails and Virtual Links

Trails that provide a logical connection for a client technology layer are
displayed as virtual links in the client layer - a special type of topology link
which is logical, not a physical connection on the native layer. For basic
information about virtual links, see Physical Links and Virtual Links.
Virtual links are created either automatically or with some user intervention.
The following are some examples.
SDH as Client of Optical Automatic Virtual Links

SDH networks can include path segments where direct physical connections
are impractical because of distance or need for aggregation. In such cases,
optical WDM segments are introduced into the SDH network. When an optical
Lightpath (LP) trail with SDH payload type is created, a virtual link is created
automatically in the SDH layer if the LP is bidirectional and has both endpoints
in the SDH layer. This allows a consistent logical SDH link, even where there
is an underlying WDM network, and allows easy navigation between the SDH
network and the underlying WDM network.
Ethernet Layer as Client of SDH Virtual Links for L1 and

L2 (EoS) Endpoints
When EoS (Ethernet over SDH) trails are defined in the SDH layer, virtual
links can be created in the ETH/MPLS layer, assisting users to visualize data
services between data ports:
| Layer 2 (EoS and MoT) ports endpoints - a virtual link is created
automatically.
| Layer 1 EoS port endpoints - virtual links are user-driven. You may create
a virtual link by selecting the EoS trail's View on ETH/MPLS Layer
checkbox; for details, see EoS/MoT Configuration Pane.

Ethernet as Client of Optical Optional Virtual Links

When an LP trail with GbE or other non-SDH payload type is defined, virtual
links are user-driven. You may create a virtual link in the ETH/MPLS layer by
selecting the LP trail's View on ETH/MPLS Layer checkbox; for details, see
LP Trail Provisioning.
NOTE: The View on ETH.MPLS Layer checkbox can be

selected in the Create Trail window in the course of
individual LP trail creation, or selected later by opening the
trail in the Trail List window's Basic Trail Parameters Pane
Standard View.
The option cannot be selected using the trail Edit window.
SRLG and Other Shared Resource

Minimization in Path Selection
LightSoft promotes diversity paths in route selection. For example, wherever
possible, the pathfinder algorithm (PF) avoids routing protection paths on
resources with the same SRLGs (as well as other shared network resources -
MEs, cards, or links) as the paths they would protect. When this is unavoidable,
you are notified of the unprotected area. PF similarly avoids setting diverse
routes on VCAT trails that traverse the same network resources. Resource
sharing avoidance rules are applied in the same way for both protection path
and diverse route selection.
SRLGs refer to situations where links in a network share a common physical
attribute, such as fiber duct or equipment cage, and are exposed to the same
vulnerabilities. If an event involving the common entity should occur, all the
links of an SRLG could potentially be disrupted. For details about how SRLGs
are specified in LightSoft, see Shared Risk Link Groups (SRLGs).
The presence of SRLGs and other types of resource sharing have implications
for LightSoft pathfinder trail route selection processes, as described in this
section. For tunnel PF implications, see SRLG Avoidance in Bypass Path
Selection.
Resource sharing avoidance rules are not enforced in the case of trail
acquisition or manual path selection. However, information about each type of
resource sharing that a trail involves can be viewed, regardless of how the trail
was created; see the Number of Shared MEs, Links, SRLGs, and Cards
parameters in the trail parameters Trail Properties Pane.
For various methods of viewing diversity in the network, see Viewing SRLG
and Other Diversity Information.

Protected Trail SRLG Intersection

Minimization
When evaluating potential protection paths, the PF algorithm first looks for
routes with the lowest SRLG intersections with the main path, then those that
reduce other protection-affecting attributes, then those that satisfy user-defined
criteria, as follows:
1. PF first looks for a subset of paths that minimize SRLG. In the following
example, the topmost route 1-2-3-4-5 is the Main path, while the other two
routes are possible protection paths. The route 1-6-7-8-5 has two SRLG
intersections with the main path (S1 and S2). Route 1-9-10-11-12-5 has
only one SRLG intersection (S1). The latter, having less SRLG
intersections, is preferred at the cost of extra hops.
2. If potential protection paths are equivalent in terms of SRLG intersections,

the algorithm minimizes intersections in other protection-affecting
attributes, in the following order of priority:
Segments
Server trails
MEs
Optical segments (optical trails if searching for SDH trails)
Card locations (ports in different cards preferred over ports in the same
card)
If paths in a characteristic are equivalent, the next characteristic is checked
until the preferred paths are identified. The characteristics and their order of
priority always apply in the indicated order.
3. After a subset of least-intersection paths is identified, the paths are then
checked against user-specified criteria and their associated tolerances, until
the optimal path that PF uses for the trail is identified; see Trail
Management Constraint Preferences.

Connection Admission Control (CAC)

Connection Admission Control (CAC) mechanisms ensure effective QoS
delivery by MPLS networks. For details, see CAC for MPLS Tunnels and CAC
for Ethernet Services.
At the MoT trail level, CAC ensures that SRLG diversity-increasing
operations, or bandwidth-decreasing operations that would leave insufficient
bandwidth for existing tunnels on the virtual link, are avoided. As well,
potentially CAC-affecting actions on MoT links (including indirect actions
such as changes to a server trail used by the link) protected by bypass tunnels
are always disallowed; the bypass tunnels must be deleted first.
TIP: The bypass tunnels can be deleted as a batch operation

through export to XML, then reimported after the potentially
CAC-affecting action is completed. For details about
exporting and importing tunnel data, see Batch Tunnel
Operations.

LAG Support
Link aggregation group (LAG) configuration enables higher bandwidth
connectivity between data cards. LAG can be assigned to EoS ports in the
EMS. LightSoft LAG support allows users to understand the LAG aspects of
the network:
| LightSoft indicates if a data port is a member of a LAG group, the name of
that group, as well as all the ports belonging to the same LAG group; see
the LAG parameters in ETH/MPLS Port Types ETH/MPLS Tab.
| An MPLS network and a PB network can be linked by multiple local EoS
trails provided they are all members of the same LAG group. For this
purpose, the trails are considered a single link and the topology is valid; see
Typical Valid Network Topologies.
Multiple LAG trails are parallel EoS trails with endpoints being part of a LAG
group, and are considered as a single link. However, in LightSoft map views, a
link involving LAG is represented as a multilink (with a label showing the
number of trails involved) even though the link behaves like a single link.
EoS and MoT trails are created from individual member ports of a LAG group.
The master port is used for the endpoint of services.
LAG General Conditions

Provisioning EoS or MoT trails as a link aggregation group (LAG) requires
pre-configuration of ports with LAG settings (master and slave) in the EMS
before starting to create trails in LightSoft.
The following general conditions apply to LightSoft trail and service creation
with LAG:
| LAG inconsistencies are not allowed; see LAG inconsistencies are not
allowed.
| Both trail endpoints must be members of LAG groups (LAG compatibility).
| A service can only be defined on the LAG master port, not on slave ports
LAG and Dual Homing

If the LAG will be in the context of Dual Homing protection:
| Only EoS-NNI ports can be used. (LAG using MoT ports is not supported
for Dual Homing.)
| LAG master ports must be connected before slave ports.
For information about LAG configuration in a dual homing network topology,
see Internetwork Dual Homing.

CNM and Trail Provisioning

The CNM feature provides an infrastructure that meets the needs of both SP
and CNM users, as reflected in the view and mode of operation in various
LightSoft modules; see VPNs and CNMs and Provisioning Mode.
CNM users have access to an SDH Server Trail topology layer, which
provides a graphically convenient view of the high order VC-4 server trail
topology as virtual links consistent with CNM resource permissions; see SDH
Server Trails in Supported Topology Layers. The SDH Server Trail layer
allows a more meaningful view of the SDH topology used by low order traffic,
as it represents the logical connectivity of the high order VC-4 network. This is
useful when the CNM user plans new trails or edits trails.
For example, suppose the SP user creates a high order trail between the CNM's
elements A and B that traverses a non-CNM element Z.
In the SDH layer, the CNM user sees only the two elements, A and B, with no
connecting link since the element Z is not part of the CNM. Although the CNM
user can create a client trail by selecting A and B endpoints, specific resources
cannot be chosen since the link is not visible.
In the SDH Server Trails, CNM user sees the A and B endpoints and virtual
link between them.
The CNM user is then able to create a client trail over A and B. Specific
segments and resources can be selected on the virtual link, exactly as when the
SP creates a trail. Although the CNM user does not have permissions over
element Z, he is able to create a client trail between elements A and B since
client trails only need permissions over endpoints.

LightSoft ASON Support

An Automatically Switched Optical Network (ASON) is a dynamic signaling-
based policy-driven control over OTN and SDH networks via a distributed (or
partially distributed) control plane, which provides auto-discovery and dynamic
connection set-up. An ASON network provides:
| Improved support for current end-to-end provisioning, re-routing and
restoration.
| New transport services such as bandwidth on demand, rapid service
restoration for disaster recovery, and switched connections within a Private
Network.
| Support for a wide range of narrowband and broadband clients signals such
as: SDH, IP, Ethernet, ATM, Frame Relay, ESCON, FICON, Fibre
Channel, and Audio/Video.
The XDM ASON card enables the configuration of advanced traffic protection
and reactive restoration that takes into account the current state of the transport
network.
LightSoft’s ASON implementation enables the configuration of LightSoft-
provisioned trails with ASON protection schemes. LightSoft displays the
ASON domain in the physical layer topology, and provides an variety of
monitoring tools.
An example of an ASON implementation scenario is displayed in the following
figure.

Aspects of LightSoft ASON support are described in the following sections:

| ASON Protection Schemes
| ASON Trail Provisioning Notes
| ASON Provisioning Conditions
| Basic Trail Parameters Pane
| Monitoring the ASON Domain
| ASON Maintenance Operations
NOTE:
LightSoft's ASON implementation uses a control plane
mechanism, inherent in ASON-enabled NEs, to seamlessly
activate ASON in the network. The control plane manages
protection and restoration of ASON trails in the network.
During the time that traffic is restored via the control plane,
ASON-associated entities are controlled exclusively by
ASON, independent of EMS or LightSoft management
systems. LightSoft's role with respect to the problematic path
is then limited to being informed about the alternative path
that ASON found - monitoring and displaying reroute or other
changes (see Monitoring the ASON Domain), thereby
enabling the operator to correct the problem. After the
problem is corrected, ASON automatically frees the resources
for the alternative path, and all associated services/traffic
revert to the original LightSoft-provisioned path. During all of
this process, LightSoft's management control over all other
network objects is unaffected.
For more information about ASON, see the ASON XDM User
Guide.
ASON Protection Schemes

ASON provides the following protection schemes:
| 1+R (Mesh/Shared Restoration) Protection Scheme
| 1++ Protection Scheme
For information about how these schemes are applied in ASON trail creation,
see the Protection parameter in Basic Trail Parameters Pane.

1+R (Mesh/Shared Restoration) Protection

Scheme
This protection scheme creates an "Unprotected 1+R Bidirectional" trail. In the
event of a problem on the main path, the system dynamically finds an
alternative path on which traffic is restored in a few seconds. The recovery
paths are also protected in the same way – new recovery paths are implemented
as long as additional paths that satisfy current criteria can be found. 1+R is also
known as Re-route restoration. (1+R is an improvement over the corresponding
Unprotected option of regular SDH in that service is restored dynamically on
an alternate path within seconds, without operator intervention.)
NOTE - Future Version 1+R Preplanned Mechanism:

Future LightSoft versions will also support an extension of
1+R dynamic restoration called Preplanned Shared
Protection, which enables shared protection with
prioritization. A trail's 1+R restoration path is defined in
advance by the user in LightSoft. In the event of a problem,
traffic diverts automatically to a preplanned path, avoiding the
processing time of dynamically finding an alternative path.
When services are prioritized (set with a CoS that enables
traffic of lower priority services to be discarded first), the
preplanned path can carry low priority traffic until it is
required. Preplanned shared protection adds value to the
"unprotected" 1+R service, giving it high-level demand
protection characteristics.
1++ Protection Scheme

This protection scheme creates a "VC-4 Protected 1++ Bidirectional trail" for
high priority services. In this scheme, the main and protection paths are
explicitly user-defined in LightSoft. In the event of a problem on the main path,
traffic is switched to the protection path within 50 msec. An alternative
protection path is searched in advance, to be ready for any subsequent problem
on the same path. Sub-50 msec restoration times are maintained “forever” for
any number of failures, as long as valid restoration paths are available.
This is an extension of the traditional 1+1 path protection, with failure in the
main or protection path resulting in restoration of the failed path. Restoration is
in addition to protection at the SDH layer, which continues to be performed in
less than 50 msec.
1++ is similar to path protection with SNCP, but with the failed path restored
by the control plane to prepare for the next possible failure.
NOTE: This protection scheme is the most bandwidth-

consuming since traffic is duplicated at all times.

Trail Creation Management

You can define how trails are created in LightSoft and which fields are visible
in various parameter windows. The preferences are grouped in panes of the
User Preferences window, described in detail in the following sections:
| Trail Management: Sets trail parameter and map display preferences, and
the default technology layer for new trails.
| Trail Management Constraints: Sets the constraints and optimization
criteria that the PF applies when a new trail is built.
Trail Management Preferences

The User Preferences (Trail Management) window is used to set the fields
shown in the Trail Properties pane of the Trail List window. You can also set
map endpoint and trail display preferences and the default technology layer for
new trails. Open and work with the window as described in Setting Traffic
Preferences.

User-selected Attributes Pane

Checkboxes enable you to select the fields that are displayed in the Trail List
window Trail Properties pane.
Options Pane
The following checkbox options are available:
| Show endpoint on map: When selected, the Trail List window map
always automatically shifts to display at least one endpoint of each
displayed trail. This is useful when working with large topologies with
widely separated elements, and avoids manually scrolling to the relevant
trail endpoints. Note that the automatic shift of the map may take some
time.
| Show one trail only: When selected, and after a trail is selected
(highlighted) in the Trail List window Trails pane, only that trail and its
corresponding objects are displayed on the window map. (When the
window first opens, the window map shows either all objects or objects
consistent with main window preselections. This is subsequently replaced
with only the selected trail and its associated objects.)
| Default Provisioning Layer: Select SDH or Optical. When the Create
Trail window is opened from the Physical (Site) layer, the new trail
parameter choices are consistent with the selected default technology.

Trail Management Constraint Preferences

The User Preferences (Trail Constraints) window specifies the optimization
constraints that the PF algorithm should consider when determining the path of
a new trail. Open and work with the window as described in Setting Traffic
Preferences.
The PF algorithm is activated when a trail is completed (all trail parameters are
set and you click Complete). The constraints described in this section are
applied on a preliminary selection of potential paths that satisfy least-
intersection criteria; see Protected Trail SRLG Intersection Minimization.
The PF makes a selection from amongst potential paths according to link
quality. If the potential paths include a mixture of link qualities (the links are
not all unprotected), the pathfinder preference depends on the requested
protection type. For example, if the user requests the trail to have:
| Current protection, then paths on unprotected links have the highest
priority.
| Underlying protection, then paths on full protected links have the highest
priority.

Criteria Selection
Up to four trail management constraint criteria may be selected against which
the pathfinder algorithm evaluates potential paths for a trail. The criteria are
applied (their priorities are determined) according to their order of selection.
For example, if the first selected criterion is Distance, the lowest-distance path
is used for the trail. If the first-priority criterion is satisfied by more than one
path, those paths are evaluated against the second-priority criterion and so on,
until a single optimal path is identified.
The available criteria cause LightSoft to optimize trails as described in the
following table.
Optimization method per criteria
Number of Server Searches for the path that traverses the least number of server
Trails trails for low order trails or topology segments for high order
trails.
Number of MEs Searches for the path that traverses the least number of MEs.
Assigned Quality Searches for the path with the designated numerical trail
quality value or better - 1 (best) to 5 (worst) - as set in the link
properties.
Availability Searches for the path that satisfies indicated min. and max.
available capacity for links considered for a new trail; see
Availability.
Assigned Cost Searches for the path with the lowest cost assessment (1 to
1,000 units). Note that this value is set in the link properties.
Length Searches for the shortest path. This value is set in the link
properties.
Tolerance
You can assign a tolerance to certain criteria to avoid pathfinder segment
selections based on trivial differences. If alternative segments under
consideration for a path are within the tolerance limits (for example, distances
within 5%), they are considered as equally preferred for the criterion. In that
case, the choice between the segments is based on how they satisfy the next-
priority criterion.
Tolerances are used to compare alternative segments and not alternative end-to-
end paths. Pathfinder uses the supplied tolerances on a per-step basis, which
may mean that the effective tolerance applied is slightly different than for the
entire path.

Availability
When the trail management constraint Availability criterion is selected,
availability ranges are enabled. These are used to indicate the minimum and
maximum available capacity for which links are considered for a new trail. For
example, if you prefer to first use links that are less utilized (with more than
20% availability) and other links only when necessary, enter the following
values:
| First Choice: Max. 100% Min. 20%
| Second Choice: Max. 20% Min. 0%
Alternatively, you can direct pathfinder to exclude links below or above a

certain availability. For example:
| Not to use links that are totally unused. Then set the first choice max. to be
less than 100%, for example, 99%.
| To leave links with some spare capacity (say 15%). Then set the second
choice min. to be more than 0%, for example, 15%.
100% and 0% denote exactly 100% and 0%. For other values, the actual
percentage used is just below the next whole number. For example, 99%
denotes just under 100%.
Maximum Values
You can indicate maximum values of certain trail management constraint
parameters. If a given criterion yields a trail path that exceeds any specified
maximum value, that path is rejected. Select a parameter's checkbox to enable
the input field and enter the value that you need.
Maximum values can be specified for the following parameters:
| Cost: Maximum total cost of a trail’s path.
| Length: Maximum total distance of a trail’s path.
| Segments: Number of segments over which a trail's path can span.
To define trail creation constraints:

1. Open the User Preferences (Trail Constraints) window as described in
Setting Traffic Preferences.
2. In the Criteria Selection pane, select up to four constraints from the
Unused pane, in order of priority, and click to move them to the
Selected pane. (Click to reverse the process.)
3. (Optional) In the Tolerance pane, enter the allowed tolerance for each
criterion. The example figure shows the system default tolerances.

4. In the Availability pane (enabled when Availability is selected in the

Criteria Selection pane), enter maximum and minimum availability
percentages for the first and second choices.
5. (Optional) In the Maximum Values pane, select the checkboxes of the
maximum values for the Cost, Length, and Segments parameters and enter
the values allowed for new trails in the adjacent fields.
Additional PF Configuration Comments

| The trail management constraint settings are saved system wide, and apply
to the trail creation activities of all users.
| The user-supplied criteria described in this section are applied only after:
For protected trails: SRLG intersections are evaluated, as described in
Protected Trail SRLG Intersection Minimization.
For all trails: The path diversity and link/server trail selection are
optimized, as described in this section.
| The optimization algorithm uses user-provided criteria only after
optimizing the path protection diversity and link/server trail selection, as
follows:
Optimization of path diversity takes into consideration common
topology links, MEs, SRLGs, and cards.
Optimization of links/server trails assigns a penalty to each VC-4 server
trail that does not match the user-selected protection criteria (for
example, a fully protected server trail is the optimal selection for a low
order SDH trail if the protection layer selected is Underlying). In some
cases, the higher priority assigned to the penalty for server trails causes
the user-selected criteria to be ignored.
| By default, the pathfinder algorithm tries to avoid selection of resources in
unused higher hierarchy TUs in each segment of the trail route. This may
sometimes result in the same TU not being used all along the way - referred
to as time-slot interchange (TSI). This preference can be changed according
to your networking requirements, so that occurrences of TSI are minimized
at the expense of occupying higher hierarchy TUs. Contact ECI Telecom
customer support for further information.
OPTIONAL FEATURE: Configurable criteria for the

pathfinder algorithm is an optional feature. If not purchased,
the criteria will be fixed to Minimum Hops (minimum server
trails for low order trails and minimum topology segments for
high order trails).

Trail Creation Options

A wide range of features and granularities are available for trail creation,
including:
| Rich user-customizable pathfinder optimization criteria.
| EoS/MoT concatenated trails with VC-4, VC-3, and VC-12 granularity.
| Diverse routing for EoS/MoT trail paths, taking full advantage of Link
Capacity Adjustment Scheme (LCAS) by configuring the EoS/MoT trail to
carry traffic over different nonshared fibers.
| Extra traffic routes to select pre-emptable resources within MS-SPRing
configurations. Supported for EoS trails (all rates) and VC-4 trails.
There are several methods for creating SDH or Ethernet trails:
| Using the Create Trail or Plan Trail windows, as described in this chapter.
| Acquiring trails from the EMS
| Importing trail definitions from XML
Creating Trails Using the Create Trail Window

The Create Trail window enables you to quickly create SDH or EoS/MoT
trails. You can create a trail by just selecting trail endpoints and accepting
default values. You can also specify detailed trail parameters if needed. Many
of the parameters are retained from the previous trail creation operation, for
example, rate and protection. Other values are calculated by the system, for
example, the trail label.
The Create Trail window procedure includes the following capabilities:
| Provisioning Bundle Trails: Multiple SDH trails can be built
automatically in a single operation using endpoints on the same cards.
After you select the cards and the number of trails to be set up (Bundle
Size), LightSoft sequentially creates the trails without further operator
intervention until the series is completed, a card runs out of free ports, or a
resource runs out of free capacity (whichever comes first).
| Coupling Trails: Two more trails may be associated as a single service
using the Private ID attribute. You should assign the same ID to the trails.
When viewing the trails in the Trail List window, sort the list lines by
Private ID to group the trails that have the same Private ID; see Sorting List
Lines.

Creating Planned Trails

LightSoft enables networks to be designed ahead of time through "planned"
trail operations. The Plan Trail window enables you to fully provision new
trails for future use even while their prospective resources are still occupied.
Trails can similarly be planned for editing or removal without immediately
affecting the network. The trail definitions are exported to XML for
implementation at a later time; see Planned Trails and Exporting Trails.
Acquiring Trails from the EMS

For SDH trails, see Synchronizing Trails.
Importing Trail Definitions from XML

Trail definitions of trails to be created can be imported from an XML file that
contains the new trail parameters. The XML files can be imported either
through LightSoft or via UNIX; see Importing Trails.

Creating SDH and EoS/MoT

Trails
You can define MPLS tunnels directly from LightSoft using the Create Trail
window; see Creating a Trail. Similar windows are used for editing or viewing
existing trail parameters; see Performing Actions on Trails.
Creating a trail or trail bundle between linked elements in LightSoft consists of
the following main steps:
| Defining trail parameters
| Selecting trail endpoints
| Assigning resources
You can create a trail by simply accepting default parameter values or you can
select specific values. The new trail is built by the Pathfinder (PF) algorithm
according to the selected optimization criteria; see Setting Traffic Preferences.
New trails created using the Create Trail window are generally for immediate
implementation in the network, but can also be exported to XML to be
implemented later. However, it may be more practical to use the Plan Trail
window for network planning purposes as this allows using occupied resources
in the provisioning process; see Planned Trails.
MoT and EoS trail creation and editing may warn about or disallow actions that
would result in invalid topologies on the MPLS layer. Specific validation rules
may be disabled on a system-wide basis to support unanticipated topologies.
For more information, see Invalid Network Topologies.
A low order SDH trail is a client of a VC-4 server trail. Therefore, VC-4 server
trails must be created before you can create SDH client trails.
NOTES:
SYNCOM NEs may require links at the EMS level in
order to define trails on them.
When creating a trail, LightSoft uses only objects in
resource domains assigned to your user group (allowed by
your user group's profile).
EoS/MoT trails may require actions at the EMS level
before starting and after completing the trail creation
steps; see EoS/MoT Configuration Pane.

Before Starting EoS/MoT Trail Creation

EoS/MoT trail provisioning assumes that ports are configured correctly in the
EMS. The following are some attributes that you should verify are set up
correctly:
| Granularity (server layer type – VC-4, VC-3, VC-12): Verify that the
configured granularity is correct.
| VCs allocated: Define the number of VCs allocated (# of VCs in a VCG).
| Other: Check that the default values in LightSoft are correct for the current
circumstance. As part of EoS/MoT trail creation, the LCAS mode and
tagging format should be verified for consistency.
LCAS type (LCAS, Proprietary LCAS, or DPC) and enabled/disabled
status.
RSTP: Enabled or disabled.
Tagging format: Q-in-Q or EIS Q-in-Q.
TIP: Direct interaction with the EMS system is often not

necessary, since many attributes:
Come with defaults specifically designed for the majority
of cases and seldom do you need to implement different
values.
Are validated by LightSoft as part of the trail creation
process.
NOTE: See also ASON Trail Provisioning Notes (including

Before Starting ASON Trail Creation.)

Creating a Trail
SDH, EoS/MoT, and ASON trails are created in the Create Trail window; see
Create Trail Window.
When creating a trail, LightSoft uses only objects in resource domains assigned
to your user group (allowed by your user group's profile); see Managing User
Groups.
Conditions apply for trail creation in a LAG configuration, such as pre-
configuration of ports in the EMS as LAG. For details, see LAG Support.
Creating ASON-protected trails in LightSoft is similar to SDH trail creation,
using the same windows, with only minor differences in procedure. The
specific inputs required for ASON are set in the Basic Trail Parameters pane;
see Basic Trail Parameters Pane. ASON trails are created using the SDH or
Physical layer.
Conditions apply to ASON trail provisioning; see ASON Provisioning
Conditions.
To create a trail using the Create Trail window:

1. Select the SDH topology layer.
You can also start SDH (including ASON) or EoS/MoT trail creation from
the Physical (site) layer if the User Preferences (Trail Management)
window Default Provisioning Layer parameter is set to SDH. For more
information about determining the default technology for new trails, see
Trail Management Preferences.
2. Optionally select on the main window the objects containing the endpoints
of the intended trail. This opens the Create Trail window with those
objects and their associated links. Otherwise, the window opens with all the
objects in the current view (for example, the currently expanded group).
(When the PF algorithm searches for trails, it relates to the relevant
topology, not only to the displayed elements.)
3. On the Traffic menu, select Trails > Create Trail.
OR
On the main toolbar, click the Create New Trail icon . The Create
Trail window opens; see Create Trail Window. The first time the Create
Trail window opens in a session may take longer than it does subsequently.

4. Enter the trail parameters. In particular, check the trail rate. You can accept
the default values (for example, if the required trail rate is the same as the
previously defined trail rate), or specify other trail parameters, as follows:
Basic Trail Parameters Pane
Advanced Trail Parameters Pane
EoS/MoT Configuration Pane
NOTE: You can create additional trails with the same route
details on the same segment without having to re-enter the
trail parameters; see Step 8.
5. In the window map, select endpoints for the trail. Endpoint details are
automatically listed in the Endpoints List pane as each endpoint is
selected; see the procedure in Endpoints List Pane.
AND
(Optional) In the window map select the specific segments that you want
the trail to span (using the SHIFT key). This is useful if you are creating a
long trail that spans more than one segment. If segments are not selected,
LightSoft creates the trail according to PF optimization considerations.
6. (Optional) Select the link resources that you want the trail to use:
If you want to select protected resources, select Protection in the
Create Trail window toolbar
.
Select the resources for the trail (according to their availability):
For an high order trail, see the procedure in Select Segment Pane.
For a low order trail, see the procedure in Select Server Trail and
Services Panes.
As you select the topology links that the trail will use, they are highlighted
in the map view and listed in the Resource Tree pane; see Resource Tree
Pane. Protection trail links are listed under the Protection node.
7. (Optional) Click the Complete trail icon . LightSoft searches for a path
using your selections. When one is found, its details are displayed for you
to review. You can go back and modify the trail parameters if needed.
At the end of the Complete processing, a message window describes the
result of the operation and lists nonfatal errors. For more information, see
Performing Trail Operations.
If the Complete step fails, perform the verifications listed in Diagnosing a
Create Trail Failure, below.

8. (Optional) You can create an additional trail with similar route details on
the same segment without having to redefine the trail properties:
After completing the current trail (previous step), click the Store
current trail as template icon .
Activate or export the trail, as described in the next two steps.
Create an additional trail, as described in the final step.
NOTE: Do not close the Create Trail window before

creating the additional trails, as this erases the template.
9. If you want the new trail (or SDH trail bundle) to be implemented
immediately, click the Activate trail icon .
If you want to export to XML instead, postpone activation and go to the
next step.
Bundled trails (SDH trails): The Progress bar lists the current trail just
built and the number of trails built so far. An Abort button is available to
stop the bundle operation if needed.
At the end of the Activate processing, a message window describes the
If the Activate step fails, perform the verifications listed in Diagnosing a
Create Trail Failure.
NOTES:
If Complete Trail was not performed before or if it is
followed by any potentially path-affecting action (such as a
change of endpoint), then it is automatically
performed/repeated as part of the Activate process. (If no
such actions follow the Complete step, a fast activation
process applies that does not duplicate the Complete
processing.)
The message "Resource allocation failed after complete" may
mean:
LightSoft failed to assign concrete resources after trail
path completion.
Resources that were free at path completion became
occupied prior to activation.
Internal problem prevented LightSoft assigning the
resource.

10. If you want the new trail (or SDH trail bundle) to be exported to an XML
file for implementation in the network at a later time, click the Export icon
on the window toolbar. The Export Trails dialog box opens in Create
mode.
Continue the procedure as described in Exporting Trails at Step 4.

11. If you want to create an additional trail with the same route details (you clicked
the Store current trail as template icon after the trail was completed):
a. Select the Clear trail contents icon to clear the trail contents
(this step is required if Show Activated Trails is set to ON).
b. Click the Restore trail from template icon .
c. Select the endpoints again.
d. On the links connecting to an ME/UME, select the TUs.
e. Perform Step 4 through 10 to implement (or export) the additional trail.
The trail parameters and route selection will already be set to the
previous trail's settings. You only need to implement the differences in
settings, if any.
f. If another similar trail is required, repeat this step.

Diagnosing a Create Trail Failure

If the Create Trail operation fails, perform the following verification steps.
If the action failed at the Completion stage:
1. Verify the message shown immediately after the failure or the error
message in the Operational Results Info window.
2. Check if all the segment selections and endpoints are correct (MSP,
resources, and so on).
3. Verify that all the relevant elements and subnets are uploaded and managed
by LightSoft. This is apparent from the Usability State of the element as
reflected on the map view or in the applicable object properties window.
You can also open a UNIX window and run the NMSState utility.
4. Check the parameters selected in the Create Trail window.
If the trail failed at the Activation stage (Completion
succeeded):
1. You can customize the following aspects of alarm indication presentation
Verify the message shown immediately after the failure or the error
2. Check if all cross connects were created at the EMS level.
3. Verify that all the relevant subnets are uploaded in EMS and LightSoft. To
do this, open a UNIX window and run the NMSState utility.
4. Check the TCI flag on the LightSoft main window toolbar. If it is red,
perform trail synchronization and check the differences between LightSoft
and the EMS or a red flag in EMS-SYNCOM. The elements that the XC
failed on will be shown in the Result window, described in Performing
Trail Operations.
5. If an NE in the trail was disconnected during trail creation or a craft
connected and the resulting trail is in an incomplete state, use Reconnect to
send the missing XCs to the network.

ASON Trail Provisioning Notes

LightSoft’s ASON implementation enables the configuration of LightSoft-
provisioned trails with ASON protection schemes. For an introduction to
ASON, see LightSoft ASON Support.
Creating ASON-protected trails in LightSoft is similar to SDH trail creation,
using the same windows, with only minor differences in procedures; see
Creating a Trail.
ASON trails can only be defined on ASON topology links between ASON
enabled NEs. ASON links have an STM-16 or 64 link rate.
NOTE: If a link intended for ASON is created in LightSoft, it

must be set as ASON in the EMS before use in LightSoft.
Trails protected by any protection scheme may be routed through the ASON
domain. But those trails will not benefit from ASON protection in the event of
a failure.
Pre-existing trails can be converted to ASON by individual or batch editing;
see Converting Preexisting Trails to ASON.
When a previously non-ASON network is configured as ASON, the LightSoft
topology is affected such that topology links that qualify as ASON take on
ASON properties.
Before Starting ASON Trail Creation

Provisioning ASON protection in LightSoft must be preceded by the following
ASON network configuration steps in the EMS (refer to the EMS user guide for
detailed procedures):
| Backup the existing network configuration and confirm hardware
compatibility.
| Set EMS Preferences for ASON and connect the SCN (Signaling
Communication Network), including NE gateway configuration, if
required.
| Install and configure an ACP card in each NE that is to participate in the
control plane, including enabling the MS RDI alarm to trigger restoration.
| Define the links that the ASON authorized network is to use.
| Configure the trails that serve the traffic that you want to protect via
ASON.

NOTE: After the ACP is configured in an NE, its SIO cards

can still be used for non-ASON purposes. The NE remains a
regular NE with regular-purpose SIO cards, accommodating
regular trails.
After the ASON Trail is Activated

After an ASON trail is activated, while LightSoft manages the network, the
trail is monitored by ASON:
| If a failure occurs on any fiber/link that the provisioned path traverses (for
example a fiber cut), a new trail path is automatically found by the ASON
control plane. The ASON control plane automatically reroutes the traffic to
the new trail’s path. The new trail path becomes visible. TCI, performed in
the background, dynamically informs LightSoft about ASON-initiated
rerouted trail connections.
| After the fiber cut is repaired, the trail automatically reverts to the initial
trail path. (Reversion settings are configured in the EMS.)
LightSoft's role concerning the trail path is limited to monitoring and
displaying reroute or other changes, with a view to correcting the problem to
allow eventual reversion to the originally provisioned path. For a description of
the available monitoring tools, see Monitoring the ASON Domain.
The originally provisioned path can be changed to another path if needed.
Redefining the provisioned path may reflect a decision not to immediately
repair the originally provisioned path and to release its resources for other
purposes. For more information, see Redefining an ASON Trail’s Provisioned
Path.
Converting Preexisting Trails to ASON

Preexisting trails can be converted to ASON by checking the ASON checkbox
using the Edit Trail window; see Editing Trails. The checkbox is enabled
when a trail is set as bidirectional and with a VC-4 rate; see the ASON
checkbox description in Basic Trail Parameters Pane.
The conversion can also be performed for multiple trails at a time by XML
Export in Edit mode and Import; see Editing Trails and Batch Trail Operations.
Conditions specific to ASON must be satisfied for ASON trails to be created
successfully (see ASON Provisioning Conditions), in addition to conditions
normally applying to non-ASON trails.
Trails that fail to be activated by the batch process are listed in XML import log
file; see Batch Trail Operations. The activation failure cause must be
determined and the underlying problem resolved before conversion of those
trails is attempted again.

When the conversion is by XML import, it is advisable to also have available a

set of XML files that can be used to restore the pre-ASON trails if needed.
ASON Provisioning Conditions

The following conditions apply to ASON trail provisioning.
General ASON Trail Conditions

The following must be satisfied for an ASON trail to activate:
| The link that the ASON trail traverses must be an ASON link. A link
created in LightSoft must be configured as ASON in the EMS before use in
LightSoft. The link rate must be STM-16 or STM-64.
| At least one segment along the trail path must be ASON protected.
| If current layer 1++ protection applies, both main and protection paths must
include at least one ASON segment.
| For diverse routed data trails, each route path must include at least one
ASON segment.
ASON Server Trail Conditions

| Low order traffic carried by a server trail is indirectly protected via the
server trail over which it traverses. Low order traffic can enter through a
server trail that begins either within or outside the ASON domain.
| A server trail may be ASON protected if it includes at least one ASON
segment that is not a termination.
| Only the ASON segments which are not terminated are ASON protected.
(The unprotected segments may be protected by an underlying protection
scheme.)

The first and last STM-16 or -64 links that terminate the trail (ASON access
links) are not ASON protected. Traffic entering/leaving these links is
protected only between the penultimate links (i.e. between ports X and Y).
ASON restoration operates only between those points. (This limitation may
be lifted in a future ASON version.)
The cloud in the figure represents the ASON network through which ASON
protected traffic is redirected in the event of failure. (Presence of the cloud
is implicit in all examples.)
In the above example, the server trail begins outside ASON domain
(endpoint in non-ASON equipment). An ASON server trail can also
terminate anywhere within the ASON domain. As in the previous example,
the terminating ASON segments are not protected.
Note: In this case you can protect against failure between ports A and X
(ASON link A) by implementing a local physical loop. In this way, link A is
not considered terminating. ASON will then protect traffic from port B after
traversing the loop. Traffic coming from the B-A cross connect is protected
from A and on.

Non-ASON NEs Connecting ASON NEs

LightSoft supports a trail traversing ASON and non-ASON domains provided
the non-ASON NEs being traversed are standard SDH equipment. ASON
protection applies only on segments within an ASON domain – an ASON
domain restores only the services passing through it. (Other protection
mechanisms may apply over non-ASON segments.)
LightSoft allows ASON links to traverse DWDM network elements with J0
transparency.
MS-SPRing and ASON

MS-SPRing and ASON can coexist. Some ASON NEs in a mesh network may
also be interconnected in an MS-SPRing configuration. While services are
ASON protected end-to-end, only MS-SPRing protection will apply when the
trail traverses the MS-SPRing segment. (LightSoft downloads two ASON trails
to protect all links except MS-Spring.) This means that in the (very improbable)
case of multiple failure in the MS-SPRing segment, ASON protection will not
apply.

Create Trail Window

The Create Trail window provides a graphical representation of all or
preselected LEs in the currently active topology layer, as well as information
and configuration panes.
The Create Trail window map view provides a graphical representation of all
or preselected objects in the currently active topology layer; see Map View:
The window includes the following sets of configuration panes, organized in
two tabs:
Trail Paramaters tab
| Basic Trail Parameters: Enables configuration of trail parameters, for

example, rate, directionality, and protection characteristics.
| Advanced Trail Parameters Pane: Enables configuration of more specific
3
optional attributes of the new trail.

| EoS/MoT Configuration: Sets the parameters of EoS and MoT trails.
| Trail Properties: Displays detailed information about a selected trail after
it is completed or activated. An example is shown in the Trail Properties
pane. For detailed information about the pane contents and associated
procedures, see Trail Properties Pane in Trail List Window.

Endpoints & Path tab
| Path Completion Method: Offers a choice of automatic or manual path

completion methods.
| Endpoints List: Shows the trail endpoint selections.
| Select Segment: For selecting the segment from which trail resources are
selected.
| Select Server Trail and Services: Appears when a low order rate is
selected in the Basic Trail Parameters pane. The Select Server Trail
pane is used for selecting resources for the low order trail. The Services
pane shows the trails on the link that are not currently serving as server
trails (because they are flex or virtual concatenated trails, or in failure
state).
| Select Resource: For selecting trail resources.
| Resource Tree: Displays resources for a trail in a tree hierarchy under
Main and Protection categories.
| Resource List: Lists details of selected trail resources individually or by
category.

Create Trail Toolbar

The window includes the following toolbar components:
| Path selector - selects the type of path (route) to which the selected new
trail attributes will apply: Main, Protection, or Both.
| Toolbar icons – Commands applicable to the Create Trail process; see

table below.
| Information bar - shows your current Basic Trail Parameters pane

selections. These remain visible when the panes are scrolled. The trail
Label and Customer are shown in brackets.
| Progress bar (under the map) - lists the current trail just built and the number
of trails built so far (applicable only if bundled trails are being created).
| Abort button – in the progress bar, for stopping the bundle provisioning
operation if needed.
Create Trail window toolbar icons

Remove all resources Removes all resource selections (for example,
endpoints and trail paths), but keeps any user
changes to trail parameters (for example, Rate,
Protection, Label, Customer, and Directionality).
Clear trail contents Clears all trail selections.
Reset trail parameters to Resets the parameters of the trail to the system's
original defaults original defaults.
Export to XML Exports the trail configured in the Create Trail
window to an XML file, leading into the export
procedure described in Exporting Trails. Exported
data can be imported to create trails at a later time
if resources are available; see Importing Trails.
Show operation results Displays detailed results of the last operation; see
information Performing Trail Operations.
Store as template Stores the current trail route as a template,
enabling you to create similar additional trails
during the current session. (The template is stored
in temporary memory of the user session and is not
saved.)


Restore from template Restores a trail from a template, enabling you to
create additional trails with similar resources and
routes as the selected stored trail during the current
session.
Show activated trail If selected (toggled on), by default, the trail is
shown in the window map immediately after
activation.
Complete trail Causes the PF algorithm to search a route for the
trail based on the current selections and network
configuration. If successful, the complete path
appears on the map with its associated resources
(whether entered manually or assigned
automatically). Nothing is saved to the database at
this point or sent to the EMS, and cross connects
are not yet created.
Activate trail Causes implementation of the new trail in the
network. If Complete Trail was not yet performed,
it is included automatically in the Activate process.
Activate causes the EMS to send information to
the element itself, cross connects to be created in
the element, and trail information saved in
LightSoft and EMS databases. Live traffic can
now traverse the trail.
Map View
The map view provides a graphical representation of all or preselected LEs in
the currently active topology layer. It is used in the process of trail endpoint
selection, and assists visualization of the Create trail process.
You can also perform operations on selected objects and links in the map view
using shortcut menu options in the same way as from the LightSoft main map
view, as described in Managing Elements and Groups.

Basic Trail Parameters Pane

The Basic Trail Parameters pane enables you to configure the most basic
attributes of the trail. You can create a trail by specifying only the Label,
Customer, and Rate, and accept the default values/parameters described in the
other panes.
This pane also includes the configuration of the new trail's protection scheme.
NOTE: VC-4-4v and VC-4-16v trails do not support DNI

and/or DRI patterns. Do not select the DRI and DNI
checkboxes for them (LightSoft will find such routes but the
trail activation will be rejected).
Basic Trail Parameters pane fields
Field Description
Label Name for the trail. Enter a name or select one from the list (of recently
used labels). If no name is specified, a name is automatically assigned
that includes details from the link and endpoints. (Optional)
Customer Enter a label describing the trail customer. If no name is specified, the
name is left as blank. (Optional)
Rate Select the transmission rate of the trail. (Mandatory; default is selection
from last created trail.)
For information about the supported rates, see Supported Rates and
Payload Types.
ASON trails: Select a VC-4 trail rate (resolution of ASON trails is
always VC-4). The following trail rates are supported:
| VC-4 server trail. Special conditions apply; see ASON Server Trail
Conditions.
| VC-4 service:
VC-4-4c, VC-4-16c
EoS-VC-4 (with or without diverse routing)
MoT-VC-4 Wwith or without diverse routing)
Note: VC-12 and VC-3 trails cannot be defined directly in ASON. Low
order traffic can be delivered over ASON by uploading low order trails
over a high order server trail. The traffic then traverses the server trails.
See also ASON Server Trail Conditions.

Field Description
Protection Select the layer for the protection trail (Mandatory; default is selection
from last created trail):
| Unprotected: Trail is unprotected.
| Underlying: Trail is protected due to the layer it traverses. For
example, traffic in MS-SPRing configurations is protected. If a trail
(for example, VC-4 rate) uses this ring, the trail is protected on the
underlying (MS-SPRing) layer. Alternatively, if a link of type SDH
is protected on the OTN layer due to transponder protection, then
all trails using that link are underlying protected (protection may be
partial).
| Current: Protection exists on current layer only.
| Current and Underlying: Trail is protected on both the current and
underlying layers.
ASON Protection:
When the ASON checkbox is selected for a trail, the SDH protection
type selected for the trail implies the following ASON protection
behavior:
| Unprotected: Implies 1+R protection, as described in 1+R
(Mesh/Shared Restoration) Protection Scheme.
| Underlying: Supplements 1+R protection with the applicable
underlying Segment protection method - External or MSP 1+1.
(MS-SPRing not currently supported with ASON.)
| Current: Implies 1++ protection, as described in 1++ Protection
Scheme, together with LightSoft current SNCP-type Path protection
(i.e. unprotected over External or MSP 1+1).
| Current and Underlying: Supplements 1++ protection with
underlying or current protection, applied based on LightSoft
optimization criteria.
For more information about the ASON protection types, see ASON
Protection Schemes.
Directionality Unidirectional or Bidirectional. (Mandatory; default selection from last
created trail.)
ASON trail: Select Bidirectional. ASON does not support
unidirectional trails.
VCAT Size Virtual Concatenated paths, indicating the number of resources that can
be used on a single trail segment (EoS/MoT trails only).
Maximum VCAT size depends on the selected trail rate and protection
type; see Supported Rates and Payload Types EoS/MoT Trails.
The selected VCAT Size may limit the number of diverse routes that
can be set for a trail; see Diverse Routes At Least/Exactly parameter in
EoS/MoT Configuration pane.
If VCAT size is decreased and diverse routes are present, LightSoft
balances the reduction between the paths. Decreasing VCAT size below
what is consistent with existing diverse routes may cause some or all
diverse routes to be eliminated.

Field Description
Bundle Size Number of SDH trails that should automatically be provisioned by
LightSoft based on parameters entered for the current trail. VC-12=252,
VC-3=192, VC-4=64.
Protection Criteria
DRI When selected, DRI protection (two NEs to bridge two rings) is used.
DRI is available for trails protected on current or current and underlying
layers (fully protected trails).
Max DRI Maximum number of DRI bridges that the PF algorithm locates when
Bridges creating a trail.
DNI When selected, DNI protection (one NE to bridge two rings) is used.
DNI protection can be configured according to your requirements.
Contact ECI Telecom customer support for further information.
Extra Traffic Requests use of Extra Traffic (ET) resources within MS-SPRing
configurations. After the checkbox is selected, the system attempts to
use ET resources on a best effort basis.
A section of ET resources is enabled in the Select Server Trail and
Select Resource panes. For EoS Diverse Routes-enabled trails, the
number of non-user selected ET routes may be specified.
Important: When using ET resources, be sure to verify that the
Resource Tree pane contains the ET-marked resources you intend to
use. Unintended ET-marking can be cancelled using the Extra Traffic
shortcut menu toggle available for route (Diverse Route EoS) or path
(Main/Protection).
ASON Activates the ASON protection scheme for the current trail, whereby the
checkbox protection types assume ASON protection definitions; see Protection
parameter, above.
After it is selected, other protection criteria options are disabled.
Enabled when a VC-4 rate is selected and the trail is bidirectional; see
Rate and Directionality parameters, above.
Note: If the ASON checkbox is not selected, regular SDH-based
protections apply.
NOTES:
For MS-SPRing protection, the ring must be created in the
corresponding EMS-XDM. For details, refer to the EMS-
XDM User Manual.
If changes are made to MS-SPRing configurations
(existing rings are edited or new rings are created) in the
EMS-XDM, activate a forced upload for all MEs affected
by the change. For details, see Forcing an ME Upload.

Advanced Trail Parameters Pane

The Advanced Trail Parameters pane allows you to configure more specific
optional attributes of the new trail.
Advanced Trail Parameters pane fields
Field Description
Comments Free text about the trail.
Service Non Service, Service, Bronze, Silver, Gold. Provided for information
Indicator purposes only.
Private ID Private ID assigned to the trail. User-configurable free text
identification string, which may be downloaded to some EMSs.
The Private ID attribute may be used to associate two more trails as a
single service; see Trail Creation Options.
Alarm Master The Alarm Master Mask (AMM) determines whether faults on objects
Mask in the trail path generate alarms. Available options:
| Apply: Select to enable trail object masking in the EMS for all
trail objects regardless of any specific EMS settings (alarms are
generated on all trail objects). The option is normally enabled.
| Do not change: Select to leave the AMM on trail objects
unchanged. Alarms are received on specific objects in accordance
with current EMS settings.
The AMM can also be applied when reconnecting a trail; see
Reconnecting Trails.
User Usage Enables you to set a user-configured usage state regardless of the
State system calculated usage state, as follows:
| Idle: Sets the trail to Idle even if the actual state is Active. Idle
trails are not connected to traffic, and can therefore be deleted
from the Trails pane; see Deleting Trails (only if the system
usage state is also idle.)
| Active: Sets the trail to Active even if the actual state is Idle.
Active trails are connected to traffic and therefore cannot be
deleted.

EoS/MoT Configuration Pane

The EoS/MoT Configuration pane allows you to set parameters of Ethernet over
SDH (EoS) and MPLS over Transport (MoT) trails. The pane becomes enabled
when an EoS or MoT rate is selected in the Basic Trail Parameters pane.
EoS/MoT Configuration pane fields
Field Description
Common
View on Indicates that the trail should be visible as a virtual link on the
ETH/MPLS Layer ETH/MPLS layer. For more information about virtual links, see
checkbox Trails and Virtual Links.
Automatic and unavoidable for MoT trails and EoS trails with L2
port endpoints. These trails are always visible as virtual links on the
ETH/MPLS layer.
For EoS trails with L1 port endpoints, enabled and selected by
default at creation time and clearable if needed, or selected/cleared
later via the Trail List window's Trail Properties pane Standard
View; see Trail Properties Pane.
Note: This checkbox cannot be edited from the trail Edit window.
You can edit it from the Trail List window Basic Trail
Parameters pane; see Trail Properties Pane.
S-VLAN (EoS trails only) Automatically adds the S-VLAN registration to
Registration the virtual link as part of the EoS trail creation process and
checkbox downloads it automatically to each existing service in the PB
network for service discrimination purposes; see Service
Discrimination.
An existing EoS trail can also be S-VLAN registered through a
Trail List window option; see S-VLAN Registration for a Trail.
Performing S-VLAN registration at the trail level avoids having to
S-VLAN register each network service individually. For more
information, see S-VLAN Registration for a Service.
Activate Activates the bandwidth of the EoS trail, opening it to data traffic
Bandwidth immediately after activation. This can be postponed and the
checkbox bandwidth activated later, either specifically or during trail
reconnection; see Activating Trail Bandwidth or Reconnecting
Trails.
Bandwidth can be deactivated in the trail edit process; see Editing
Trails.

Field Description
Diverse Routes Primarily used to allow LCAS functionality, enabling configuration
checkbox of the EoS/MoT trail to carry traffic over different nonshared fibers
(diverse routes).
The checkbox is enabled when any EoS/MoT trail rate is selected,
the VCAT size is greater than 1, and protection is Unprotected or
Underlying Layer.
When the checkbox is selected, specific trail resources can be
assigned to separate route numbers using the Belongs to Route No.
field; see Select Segment Pane.
In this case, the Resource Tree pane categorizes resource
information by route number instead of by Main/Protection; see
Resource Tree Pane. (The Resource Tree pane categorization by
route applies if at least one route is labeled other than Route #1.)
If not selected, all resources are allocated to the same route or link
(Route #1).
Selecting the checkbox enables the parameters in the rest of the
Diverse Routes area.
At least/Exactly (Enabled when Diverse Routes is selected)
Minimum or exact number of diverse routes you want defined for
the EoS/MoT trail (as allowed by LightSoft according to indicated
VCAT size and EoS/MoT trail rate, with a maximum of 3).
The maximum number of separate routes that can be set depends on
the trail rate:
| EoS/MoT VC-4X = max. 3
| EoS/MoT VC-3cX = max. 16
| EoS/MoT VC-12X = max. 8
and additionally limited by the lesser of:
| Belongs To Route No. selection; see Select Segment Pane.
| VCAT size assigned to the trail/Min VC paths per route; see
VCAT Size description in Basic Trail Parameters Pane, see
Min VC paths per route description below.
Min VC paths/route (Enabled when Diverse Routes is selected)
Minimum number of VC paths (resources) you want per diverse
route. Links with lesser capacity are excluded from PF search
consideration.
Extra Traffic routes (Enabled when Diverse Routes is selected)
Number of diverse routes that use extra traffic (ET) resources on
MS-SPRing. This enables selection of ET resources in the Select
Server Trail and Select Resource panes. You can specify the
number of non-user selected ET routes for EoS Diverse Routes-
enabled trails.
Important: When using ET resources, be sure to verify that the
Resource Tree pane contains the ET-marked resources that you
intended. Unintended ET-marking can be cancelled using the Extra
Traffic shortcut menu toggle available for route (if DR EoS) or
path (Main/Protection).
Note: Extra traffic routes are set up once the trail is defined. This
parameter cannot be changed after the trail is created.

Field Description
RSTP Enabled (EoS trails only, not applicable for MoT)
If selected, the EoS trail will be controlled by the RSTP
configuration.
For more information, see Viewing RSTP Information.
(For RSTP to be operational, it must additionally be enabled at the
port level via the EMS.)
Cost Enabled when the RSTP Enabled checkbox is selected. Enter the
Cost associated with the EoS trail for RSTP purposes.
This cost is assigned automatically to both endpoint ports when the
trail is created, or the cost is modified through the Edit Trail
window.
If the costs associated with the two ports should differ (for
example, due to an EMS modification), the Cost field in LightSoft
will be blank.
Trail Properties Pane

The Trail Properties pane displays the attributes of the selected trail. It is
empty when the trail is being created and filled with information after the trail
is completed or activated.
The same pane is available in the Trail List window, showing information for
a selected trail and modifying its attributes. For detailed information about the
pane contents and procedure for editing attributes, see Trail List Window -
Trail Properties Pane.

Path Completion Method

LightSoft trail creation offers automatic (Auto-complete) or manual (Explicit
Routing) path completion methods. (Explicit Routing is not available if Diverse
Routing applies.)
When Auto-complete (default) is selected, PF automatically suggests an

optimal path for the trail based on the minimum user selections – endpoints and
the trail rate, and in accordance with applicable user preferences (see Trail
Creation Management). In this mode, you can additionally select some links
the path should include (in the Resource Tree pane), thereby limiting the trail
route alternatives considered by PF.
With Auto-complete, if all the links of the path are pre-specified, PF will still
look for an optimal path, and eventually choose the one possible (pre-specified)
path. If you want to explicitly specify the entire path, you can save processing
time by setting the path completion method to Explicit Routing. Then PF only
relies on user link specifications and does not attempt to look for a path. (If
your selections are insufficient to fully define a trail between the endpoints, an
Invalid Input message is displayed. PF does not attempt to complete the trail.
Regardless of the completion option selected, resource pre-selection remains
optional and PF automatically selects resources for the trail if needed. As well,
all regular trail validations are applied.

Endpoints List Pane

The Endpoints List pane shows the endpoints selected for the new trail. As an
endpoint is selected, its details appear in the list.
Endpoints List pane fields
Column Description
Endpoint Name Name of the endpoint, comprising three components:
| ME name
| Physical Termination Point (PTP) name
| Connection Termination Point (CTP) name
Before a trail is completed, only the ME name appears.
Mode Indicates whether the endpoint functions as Add, Drop, or Add
and Drop.
Path Indicates whether the endpoint applies to the main path,
protection path, or both.
C2V Checkbox Select to enable Contiguous Concatenation to Virtual
Concatenation (C2V) functionality on the trail endpoint.
Relevant only when a virtual concatenation trail rate is selected
making C2V functionality possible (VC-4-4v or VC-4-16v.
Note: For the checkbox to appear, the endpoint must be manually
selected at the VC level within the port and not at the port itself.
Automatic endpoint selection should not be used.
C2V allows contiguous signals that start and terminate outside the
managed network to traverse a managed network where some
elements do not support contiguous signals (such as SYNCOM
elements). When entering the network, the contiguous signal is
converted to a virtual concatenated signal for its passage through
the network, and converted back to a contiguous signal upon
leaving the network.
The Endpoints List pane in the Trail List window additionally includes a
Decrease checkbox column for decreasing the bandwidth at endpoints of
existing trails. For details, see Endpoints List Pane.

Right-click an endpoint in the Endpoints List pane for the following shortcut
menu options:
Endpoints List pane shortcut options
Option Description
Open Opens a GCT to the endpoint port's EMS card view.
Properties Opens the Properties for Port window for that endpoint port;
see Port Properties.
Remove Removes the selected endpoint, enabling you to replace it with
another.
Remove All Removes all endpoints, enabling you to restart the endpoint
selection process.
Selecting Trail Endpoints

You can select a group, element, or port as an endpoint. If a group or element is
selected, the first available resource is used.
When a bundle of trails is being created (in the Basic Trail Parameters pane,
the Bundle Size is greater than 1):
| Endpoints for each additional trail are automatically assigned based on the
next available port or termination point in the sequence.
| The number of bundled trails that are built is limited by the number of
available ports and the starting port (if any) selected for the first trail. For
example, if the first trail is manually assigned port #3, subsequent trails are
automatically allocated the ports starting with #4 - the resources #1 and #2,
even if available, remain unoccupied. If the remaining ports are
insufficient, not all the trails in the bundle are built.
NOTE: Endpoint selection is mandatory. (In most cases it is

sufficient to select an NE - the endpoint port is automatically
selected.)
To select groups or elements as endpoints for SDH trails:

| Select the groups/elements at the terminating point of the trail. (Only
elements with compatible ports are available for selection.) The specific
endpoints (ports or termination points) are found automatically.
Optimization of endpoints is not performed. (If a selected element has no
compatible ports, no selection is made.

To select specific ports or termination points as endpoints:

1. In the Create Trail window map:
a. Click an LE. The first available port consistent with the trail rate
selection is automatically selected and listed in the Endpoints List
pane.
b. Repeat for the next required endpoint (a trail needs two endpoints).
OR
2. In the Create Trail window map, right-click an LE and choose Select
Endpoint (or double-click the LE). The Select Endpoint window opens.
The available endpoints are listed in a tree structure. Double-click a node to
expand or collapse the tree.
The root of the tree is the selected ME. All available ME endpoints are
listed in the tree.
The geometric-shaped icons next to the port names are the same as used in
the Topology Tree. For the definition of each icon, see Topology Tree.
Potential endpoints (ports and termination points) in the Select Endpoint
window tree are shaded if unavailable (for example, already in use or
blocked). If an endpoint cannot be used for the selected rate of the trail, it is
not displayed in the tree. The selected endpoints are listed in the Endpoints
List pane.
NOTE: When you select endpoints for a planned trail via the
Plan Trail window, every rate-compatible resource is
regarded as available, even if it is currently occupied.

a. Select the endpoint's Add/Drop mode as follows:

For unidirectional trails, the Add and Drop radio buttons are
enabled.
For bidirectional trails, the mode is typically Add&Drop (default).
If the object selected is a termination point, all the radio buttons are
enabled and the mode may be Add, Drop, or Add&Drop.
b. Select the protection scheme for the endpoint: Main, Protection, or
Both.
c. Select an endpoint by drilling down to the endpoint node to select it and
then click Select, or double-click the node. Click Close to close the
dialog box without selecting an endpoint.
NOTE: The specific endpoint names are displayed in the

Endpoints List pane only after the trail is completed.
d. After you have finished specifying an endpoint, click Close to close the
dialog box.
e. Proceed with another endpoint, if required, by repeating from Step a.
(A trail requires two endpoints.)
EoS and MoT Endpoint Compatibility

EoS trails can be created between two Ethernet over SDH ports (EoS) ports -
with VCG and Ethernet layer in a physical or logical port. MoT trails can be
created between two compatible MPLS over SDH (MoT) ports - with VCG
(Fragment layer) and MPLS layer in a logical port. For more details, see
Typical Valid Network Topologies.
The selected endpoints must also be compatible in the following ways:
| LCAS Compatibility: Both selected endpoints must have LCAS either
enabled or disabled. If LCAS is enabled, both endpoints must have the
same type of LCAS (according to the NE support for LCAS). If not, the
trail is disallowed. (Endpoints of UMEs are not checked for compatibility.)
| LAG Compatibility: Both endpoints must be members of LAG groups.
For more details, see Invalid Network Topologies.
| Double-Tagging Format Compatibility: Both endpoints must have the
same double-tagging format (both Q-in-Q or EIS Q-in-Q or None) set in
the EMS.
| RSTP Compatibility (EoS Only): Spanning Tree mode setting must be
same for all endpoints. Values may be RSTP, MSTP, or None. (Not all NEs
support MSTP.)

| Port Type Compatibility: Port interface types must be valid and

compatible. The endpoint type is displayed and the interface compatibility
is validated.
E-NNI (external) interface type connects a service to a non-managed
network.
I-NNI (internal) interface type connects PB and MPLS networks.
NNI type ports may be used for both E-NNI and I-NNI.
For a description of these interfaces, see Supported ETH/MPLS Port Types.
You can differentiate between UNI and NNI ports through

different Select Endpoint window tree symbols. (E-NNI and I-NNI use the
same symbol.)
EoS endpoint selection rules for NNI types
Trail between: Endpoint A Endpoint B
Endpoints in same PB network I-NNI or NNI I-NNI or NNI

PB port (EoS) to PE port (EoS) I-NNI or NNI I-NNI or NNI
PE (EoS) to L1 ETY E-NNI or UNI or NNI L1 ETY
PB to L1 ETY E-NNI or UNI or NNI L1 ETY
PE port (EoS) to PE port (EoS) I-NNI I-NNI
PB port (EoS) to PB port (EoS) E-NNI E-NNI
PE port (EoS) to PE port (EoS) E-NNI E-NNI
Network Topology Validity

Validation rules apply to trail creation, which have consequences for network
topology validity. For more information, see:
| Typical Valid Network Topologies
| Trail Patterns Within/Between Networks
| Invalid Network Indications
| Invalid Network Topologies

Select Segment Pane

The Select Segment pane is used to optionally select resources for a trail.
(Selecting specific resources for a trail is optional. If no segment is selected,
LightSoft automatically selects the first available resource in the first segment
that spans the selected endpoints.) This pane shows the same fields as for
Topology Links, described in Viewing Topology Link Information.
The pane may include a Belongs to route No. selector for specifying a route
number to a selected resource for an EoS/MoT diverse routed trail (enabled if
VCAT Size is greater that 1 in the Basic Trail Parameters pane and the
Diverse Routes checkbox is selected in the EoS/MoT Configuration pane).
For more information, see the procedure below.
When a bundle of trails is being created (in the Basic Trail Parameters pane,
the Bundle Size is set greater than 1), capacity for each additional trail is
automatically assigned based on the next available resource in the matrix.
The number of bundled trails that are built is limited by the segment capacity
and the starting resource (if any) selected for the first trail. For example, when
Bundle Size = 16 is specified on an STM-16 link, if the first trail is manually
assigned the resource #3, subsequent trails are automatically allocated the
resources starting with #4, even if the resources #1 and #2 are available. The
resources #1 and #2 will remain unoccupied and only 14 trails will be
provisioned. The completion message at the end of the process states that
capacity was not available.
To select specific resources for a trail:

1. In the Create Trail window Basic Trail Parameters pane, select the
required rate:
High order rate, for example VC-4
OR
Low order rate, for example VC-12 or VC-3

2. In the Create Trail window map, right-click a topology link or multilink

and choose Select Segment on the shortcut menu, or double-click the link
or multilink.
The Select Segment pane shows the available segments in the link.
3. For a diverse routed EoS/MoT trail – do the following for each required
diverse route:
a. Select an applicable route number from the Belongs to Route No.
selector .
b. Provision resources for a selected segment, as described in Steps 4 to 7
below.
NOTE: Diverse routes are relevant for unprotected or

underlying protected EoS trails only.
You can view the new resource-to-route association in the Resource Tree
pane; see Resource Tree Pane.
Once a resource-to-route association is confirmed in the Resource Tree
pane, any new Belongs to Route No. selection applies to a following route
and does not affect previously provisioned routes. You can change an
association by deselecting it or removing it; for details, see Select Resource
Pane.
Any number of resources can be assigned to a specific route number.
The route # can be any number. For the trail to be recognized as diverse
routed, at least one route number must be other than route #1 – for more
information, see Resource Tree Pane.

The maximum number of separate routes that can be assigned depends on:
Diverse Routes parameter At Least/Exactly selection; see EoS/MoT
Configuration Pane.
VCAT Size assigned to the trail; see parameter description in Basic
Trail Parameters Pane.
If the number of separate routes selected exceeds these limits, the trail is
not completed.
4. In the Select Segment pane, click the row of a segment to highlight it.
5. In the selected segment row,
Double-click a port cell (unidirectional selection) or the link cell
between the two ports (bidirectional selection).
OR
You can right-click the required port or link cell, or from the shortcut
menu, select (default option, according to the rate selected in Step 1):
Select Resource if you are creating a high order trail.
OR
Select Server Trail if you are creating a low order trail.
Note: The small arrow represents the segment. Clicking the link cell
alternately selects/deselects both link segments (turning the arrow color on
or off ). This feature is available for high order rates only.
6. You will now select resources for the segment(s) that you want to
provision, using the applicable pane:
High order trail: use the Select Resource pane; see Select Resource
Pane.
OR
Low order trail: Use the Select Server Trail pane; see Select Server
Trail and Services Panes.
7. After you have finished selecting resources, scroll back to the Select
Segment pane. In that pane, the corresponding resource symbol/s (above
the segment name) become colored (for example, change from to )
according to the type of path selected - purple for "both", pink for Main (or
unprotected), or blue for (protection link).
8. You can view details about the segment that LightSoft will use to create the
trail in the Resource Tree pane; see Resource Tree Pane.

Select Server Trail and Services Panes

The Select Server pane is used to select resources for a low order trail -
relevant when a low order rate (for example, VC-12) is selected in the Basic
Trail Parameters pane. It lists the available server trails:
| Server trails with available resources can be selected.
| Server trails where the resources are fully occupied are grayed out.
The Services pane shows high order trails on the link which are service trails,
or otherwise cannot serve as server trails because, for example, they do not
conform to normal trail patterns (flex trails) or are virtual concatenated trails or
in a failure state. These trails are presented for informational purposes only and
cannot be selected.
To select specific resources for a low order (client) SDH

trail:
1. Complete Steps 1 to 6 of the procedure described in Select Segment Pane to
select a low order rate and select a segment. The Select Server Trail pane
now shows server trails for one or both ports of the segment.

2. Double-click a server trail (or right-click a server trail and select Select
Resource from the shortcut menu). The Select Resource pane now shows
available resources (light gray indicates availability), enabling you to select
a resource. (Resources are colored purple when selected.)
NOTES:
If you want the resource to be selected automatically, in the
Select Server Trail pane click a server trail (instead of
double-clicking). The PF will automatically choose an
appropriate TU after the trail creation procedure Complete
step.
When resource selection is being performed for a planned
trail via the Plan Trail window, every rate-compatible
resource is regarded as available, even if it is currently
occupied.
3. Select resources for the server trail(s) you want to provision, as described in
Select Resource Pane Step 2.
In the Select Segment dialog box, the corresponding resource symbol(s)
(above the port name) change from to .

4. You can view information about the segment that LightSoft uses to create
the trail in the Resource Tree pane; see Resource Tree Pane.
5. To quickly learn more about a specific server trail, right-click the server
trail path in the Resource Tree pane and select Show Trail from the
shortcut menu (or double-click its line in the Resource Tree pane).
Another instance of the Trail List window opens, showing only the
selected server trail and its path, as well as other characteristics (for
example, where it starts and ends).
Select Resource Pane

The Select Resource pane enables you to select sources for a high order trail.
To select resources for a high order trail:

1. Complete Steps 1 to 6 of the procedure in Select Segment Pane to select a
high order rate and select a segment. The Select Resource pane now shows
the available resources for one or both ports of the segment. The pane
contains a resource selection graphic, with squares representing resources,
as follows.
Purple - current new selection (as in square 3).

Lightest gray - available for selection.
Light gray - unavailable in either direction because used by other trails
(as in square 2).
Dark gray - Blocked in both directions (as in square 1). A resource may
be blocked if it is being used to provide. So the protecting resources are
blocked. User will never be able to select them.
NOTE: When resource selection is being performed for a

planned trail via the Plan Trail window, every rate-
compatible resource is regarded as available, even if it is
currently occupied.

2. Select resources for one or both directions, or separate resources for each
direction, as follows:
To choose resources for one direction: Select a specific port. The
resource selection graphic appears to the left or right side of the pane
with a directional arrow below it. Click an available resource for that
single direction (the square turns purple).
To choose resources for both ports: Select the link cell between the
ports. The graphic is centered in the pane.
To chose the same resources for both directions of the segment, just
click an available resource (the square turns purple).
If you want to choose different resources for each direction, click
the Unmerge button at the bottom of the pane. Two resource
selection graphics appear in the pane. Select the required resource
for each direction.
The Merge button can be used to subsequently remerge the
graphics if required to select the same resources for both directions.
Any asymmetrical selections that you made in the current session
will be discarded, while all symmetrical selections will be
preserved.
A confirmation window appears. The action is implemented only if
you enter OK.
To remove resources after selection:
If diverse routes apply, in the Select Segment pane, select the required
route number from the Belongs to Route No. selector.
In the Select Resource pane, click the selected resource in the graphic
to deselect it.
You can then select different resources by clicking as needed.
In the Resource Tree pane, select a resource from the required
resource category (main or protection, or the applicable route); see
Resource Tree Pane, and in the Resource List pane, right-click the
required resource and select Remove; see Resource List.
3. Continue the procedure described in Select Segment Pane Step 7.

Resource Tree Pane

The Resource Tree pane displays selected resources for a trail in a tree
hierarchy under Main and Protection categories (where applicable). (The same
pane is available in the Trail List window and displays existing trail
resources.)
In the case of concatenated trails with diverse routing, each route has a branch.
Each line contains indications of the applicable protection type.
In general, resources are categorized according to Main and Protection.

For EoS/MoT diverse routed trails, resources are categorized according to route
number (for example, Route1, Route2, and so on). This applies when the
Diverse Routes checkbox is selected; see Diverse Routes description in
EoS/MoT Configuration Pane, and at least one route number besides Route #1
is specified for a trail resource; see Select Segment Pane.
Segments with the following special statuses are identified by icons:
| DRI bridge-associated segments. The bridge number is shown under
the bridge icon. A tooltip also shows the source endpoint from which the
path-search algorithm is instructed to reach the source of the bridge link.
| Resources with Extra Traffic (ET) status.
| Segment in process of bandwidth decrease.

Resource List
The Resource List pane displays details of selected trail resources individually
or by category (All, Main, or Protection).
Resources with the following special statuses are identified by icons:

Working channel segments associated with MS-SPRing configurations.
Resources with non-preemptible Unprotected Traffic (NUT) status.
Resource List pane fields
Field Description
Resource Used resource/time slot.
Segment/Server Topology segment/trail path label.
Trail
Both topology segment and trail path have a direction icon :
| In the case of a trail path, the direction of the arrow DOES
NOT indicate the "from-to" direction of the trail but serves to
distinguish between the forward path and the backward path.
| In the case of topology segments, the direction of the arrow
DOES indicate the from-to direction of the segment with
respect to the connected elements left/right map location.
For a server trail path, if there is no information about occupied
resources, the "[N/A]" prefix is attached to the path's label.
A tooltip over the direction icon shows the direction of the
topology segment/server trail path in the format "SRC to SNK",
where SRC and SNK are termination points of the path element.
Path Main or Protected. (This column is not displayed if diverse routing
applies.)
Route If diverse routing applies, the route to which the resource is
assigned is indicated. (This column is displayed if diverse routing
applies.)

Information About a Specific Server Trail

To quickly learn more about a specific server trail, in the Resource Tree pane,
double-click the trail, or right-click it and select Show Trail from the shortcut
menu. Another instance of the Trail List window opens, showing only the
selected server trail and its entire path and other characteristics (for example,
where it starts and ends).
Right-click a server trail to open a shortcut menu with the following options.
(Options vary according to whether the menu is opened in the Create Trail,
Edit Trail, or Trail List window.)
Server trails shortcut menu options
Option Description
DRI Bridge Displays Define DRI Bridge dialog box used for
creating bridges; for more information, see Creating
DRI Trails.
Remove Low order trails: Disassociates selected server trail
from selected client trail, thereby removing the server
trail from the list.
High order trails: Disassociates selected resource from
selected link segment, thereby removing the link
segment from the list.
Remove All Low order trails: Disassociates all server trails from
selected client trail, thereby removing all server trails
from the list.
High order trails: Disassociates all resources from the
selected link segments, thereby removing all link
segments from the list.
Collapse All/ Collapses/expands the tree.
Expand All
Move to Protection/ When protection applies, these toggle options enable
Move to Main you to edit a protection trail segment to main, or a main
trail segment to protection; for more information, see
Path Protection Switching.
Add Main to Protection/ Adds the selected segment to the main/protection path.
Add Protection to Main

Ring Interworking Protection

LightSoft offers SubNetwork Connection Protection (SNCP) and Bidirectional
Path Switched Ring (BPSR) interworking using user-assisted and automatic
methods. The following ring interworking methods are supported:
| Dual Ring Interworking (DRI) with two NEs to bridge two rings.
| Dual Node Interworking (DNI) with a single NE to bridge two rings; see
Dual Node Interworking.
The method selected depends on the network topology.
NOTE:
DNI in this manual refers to node protection involving two
(virtual) rings, with “dual” denoting the number of rings and
“node” denoting the closure of the rings being performed by a
single node. This differs from ITU standard usage where DNI
suggests two nodes connecting two (virtual) rings.
DRI in this manual refers to dual (virtual) ring architecture
that uses two nodes to connect to another ring and has a
"bridge" between these nodes, for example, between mesh
and ring.
The differences in meaning with standard usage reflect the
enhanced interworking flexibility of XDM NEs.
Dual Ring Interworking

In many cases, a network is a complex mixture of interconnected elements (for
example, mesh), with several alternate protection bridging options. DRI trails
essentially create virtual rings so that the trail is capable of surviving
independent virtual ring failures. LightSoft supports two types of DRI trails:
| User-assisted DRI, where you specify DRI bridges when selecting
resources before invoking the PF algorithm. When selecting a DRI bridge,
indicate the source endpoint for each link and its role as Main or
Protection. You can select more than one link per bridge; otherwise, their
location may not be optimal.
| Automatic DRI, where the LightSoft PF mechanism selects the resources
automatically, including the bridges to use between the optimal main and
protection paths.

DRI trails are created if you select the DRI checkbox in the Basic Trail
Parameters pane. You can also indicate how many bridges you want the
system to find between the main and protection paths. For more information,
see Basic Trail Parameters Pane.

Dual Node Interworking

DNI allows you to close two (virtual) rings in a single NE. The path protection
of each virtual ring is independent of the other ring. The Create Trail operation
builds DNI cross connects in all nodes where the main and protection paths
enter and leave the NE on distinct topology links (wherever the links ports
support SNCP). The PF algorithm avoids using a single node for main and
protection routes. So to create a DNI in a specific route, you may need to select
the links/server trails manually unless the topology is such that only DNI paths
are found by the PF.
DNI trails are created automatically if you select the DNI checkbox in the
Basic Trail Parameters pane (see Basic Trail Parameters Pane), or if
LightSoft is configured to always attempt to create DNI.

Creating DRI trails

To create a DRI trail, you must first define the bridge segments for the main
and protection paths before completing and activating the trail.
To create a DRI trail:

1. Open the Create Trail window, as described in Provisioning SDH and
EoS/MoT Trails.
2. In the Basic Trail Parameters pane (in addition to other trail creation
settings):
a. Verify that the Protection field is set to Current or Current and
Underlying.
b. Verify that the DRI is selected.
c. Select a Maximum DRI Bridges: number depends on the topology and
level of protection desired.
d. Select Extra Traffic if extra traffic resources are desired in MS-
SPRing rings.
3. On the Topology Map, select the NEs that act as endpoints; for details, see
Endpoints List Pane.
From this point, the level of automation for selecting bridge segments is at
your discretion. You can either continue with Step 6, or allow the system to
select all participating bridge segments as follows:
a. In the Create Trail window, click the Complete Trail icon .

LightSoft searches for a path using your selections. When a path is
found, it notifies you with a short message in the upper right-hand
corner of the Create Trail window.
b. Check whether the results are acceptable.
c. When the trail has been completed, click the Activate Trail icon
to activate the trail in the network. (Clicking Activate Trail without
first clicking Complete Trail prompts LightSoft to search for a path.)
d. Click OK to approve.
4. In the Create Trail window, select the bridge segments by double-clicking
a link, or by right-clicking a link and selecting Select Segment on the
shortcut menu. The Select Segment pane opens; see Select Segment Pane.
5. Right-click a resource (link name or specific link segments) from the list
and then choose Select Resource (or double-click the resource). Select a
resource from the resulting panes as described in Select Resource Pane.

6. Follow the same procedure for both the Main and Protection bridges. The
link information appears in the Resource Tree pane.
NOTES:
If a trail comprises a number of contiguous links, follow
Steps 5 and 6 for all links forming the trail.
If a trail is bidirectional, you must also select the endpoint
that leads to the respective bridge since, in theory, it may
have to function in either direction.
7. In the Resource Tree pane, select the DRI bridge segment(s) for the main
path and right-click.
8. On the shortcut menu, select DRI Bridge. The Define DRI Bridge dialog
box opens.
9. In the Source Endpoint pane, select the required endpoint and click OK.
In the Resource Tree pane, the icon of the bridge appears in the
segment line and its endpoint appears in the icon's tooltip.
10. Repeat Steps 7 to 9 for the protection path (or additional bridges).
11. Click the Complete Trail icon . LightSoft searches for a path using
your selections. When a path is found, the system notifies you with a short
message in the upper right-hand corner of the Create Trail window.
12. When the trail has been completed, click the Activate Trail icon to
activate the trail in the network.

13. Click OK to approve. The trail appears on the map.

Planned Trails
The Plan Trail window enables you to design networks ahead of time by
building "planned" SDH or EoS/MoT trails. These may be new trails or edited
versions of existing trails.
For information about the Plan Trail window fields, see Create Trail Window.
In contrast with the regular work mode using the Create Trail window, you
can select ports and resources for the new trail without regard to the actual
resource state in the network. The trail can be fully provisioned even while its
prospective resources are currently occupied. The new trail (or edited details)
are exported to XML until needed and do not immediately affect the working
network.
When the new network design is ready to be implemented (and occupied
resources are free), planned trails may be imported to LightSoft as part of the
active network.
OPTIONAL FEATURE: Plan Trail operations depend on

exporting trail details to XML (optional feature). If not
purchased, menu options pertaining to Plan Trail are
unavailable.

Creating a Planned Trail

Create a planned trail by following these steps.
To create and export a planned trail:

1. Access the Plan Trail window in the same way as described in Creating
SDH and EoS/MoT Trails but using the following access options:
On the LightSoft main menu bar, select Trails > Plan Trail.
OR
On the toolbar, click the Plan Trail icon . The Plan Trail window
opens.
You can also access the Plan Trail window from the Trail List window
(the window panes show the parameters of the selected trail), as follows:
Select a trail and click Plan highlighted trail on the toolbar.

OR
Right-click a trail and select Plan highlighted from the shortcut menu.
The Plan Trail window opens.
These options are not enabled from the optical layer or from the physical
layer if the User Preferences window Trail Management preferences
Default Provisioning Layer parameter is set to optical. For more
information about default technology for new trails, see Traffic Preference
Management.
2. Follow the same procedures as described in Creating SDH and EoS/MoT
Trails. The only exceptions are as follows:
a. You can create only one planned trail at a time. (The Basic Trail
Parameters pane does not include a Bundle Size option.)
However, the Store current trail as template option can be used to
create additional trails with the same route details on the same segment
without having to redefine the trail properties. (Use the same procedure
as described in Create Trails, but omit the Complete and Activate steps.
After exporting a trail, return to the Plan Trail window to finalize the
next required trail.) Multiple planned trails can be appended in one
XML file, as described in Exporting Trails.
b. Any rate-compatible port/termination point can be selected. The
Endpoints List Pane shows each endpoint as available, even if it is
currently occupied.
c. Any resource in any segment can be selected. The Select Resource
Pane shows each resource in the segment's resource matrix as available,
even if it is currently assigned.

d. Completing the trail is not necessary. The trail is automatically

completed and activated when it is eventually imported to LightSoft. (If
the trail definition includes occupied resources, even those that appear
free for planning purposes, the Complete action will fail.)
e. The Activate button is disabled when creating a planned trail.
3. After the trail parameters are defined, export the trail as follows:
Click the Export icon on the window toolbar.

OR
Right-click a trail and select Trail Utilities > Export from the shortcut
menu. The Export Trails dialog box opens in Create mode.
4. Continue the procedure as described in Exporting Trails, from Step 4.
Importing Planned Trails

In order to import a planned trail, you must ensure that all the endpoints and
segment resources that are needed for the planned trail are currently
unoccupied; else the import will fail.
To import planned trails:

| Import the planned trails as described in Importing Trails.


9
Performing Actions on Trails
In this chapter:
Overview ......................................................................................................... 9-1
Accessing the Trail List Window .................................................................... 9-2
3
Trail List Window ........................................................................................... 9-2

3
Viewing Trail Information............................................................................. 9-21

3
Performing Trail Operations .......................................................................... 9-25

3
Filtering the Trails Pane ................................................................................ 9-26

3
Reconnecting Trails ....................................................................................... 9-36

3
Editing and Deleting SDH, Optical, and EoS/MoT Trails ............................ 9-38
3
Splitting a Long Trail .................................................................................... 9-46

3
Increasing, Decreasing, or Activating Data Trail Bandwidth ........................ 9-48

3
S-VLAN Registration from a Trail ................................................................ 9-52

3
Inserting MPLS PEs to MoT Trails ............................................................... 9-53

Removing MPLS PEs from MoT Trails ........................................................ 9-62
Redefining an ASON Trail’s Provisioned Path ............................................. 9-76
Batch Trail Operations................................................................................... 9-77
3
Overview
This section describes the trail management interface for ongoing trail-related
operations.
A full range of operations on existing trails can be performed using either Trail
List window or the LightSoft main window options, including viewing and
filtering trail information, viewing trail alarms, reconnecting trails, editing and
deleting trails, and modifying or activating trail bandwidth.

Performing Actions on Trails LightSoft User Manual
Accessing the Trail List Window

The Trail List window (see Trail List Window) opens with different object
combinations according to preselections in the LightSoft main window:
| If no objects are preselected in the main window:
The Trail List window Map view shows all objects in the network
(consistent with your user permissions); see Map View.
The Trails pane includes trails based on the default filter; see Trail
Pane.
TIP: Opening the Trail List window may take less time if
you choose "No Trails" as the default filter. You can then
select a different filter. For details, see Applying a Filter and
Setting it as Default.
| If objects are preselected in the main window:

The Trail List window map opens with only those objects and their
immediately associated links/elements.
The Trails pane shows only the associated trails. In this case, a
"Temporary" filter applies (the default filter is disregarded). If required,
you can create a new filter based on the temporary filter objects; see
Creating a Filter with Preselected Objects.
Regardless of preselections, if the Show one trail only option is selected in the
User Preferences window, after a trail is selected in the Trails pane, the Trail
List window map shows only the associated elements and links and hides all
the others; see Trail Management Preferences.
A wide range of filter options are also available; see Filtering the Trails Pane.
You can open multiple Trail List windows simultaneously, each one
displaying a selected layer and elements independently of other layers, having
its own topology layer and view of the network, and allowing different trail
operations.

LightSoft User Manual Performing Actions on Trails
To open the Trail List window:

1. Select a topology from the main window Topology Layer dropdown list.
2. (Optional) For ease of work and improved performance in larger networks,
you can open the Trail List window with links running between a limited
number of NEs and a corresponding limited number of trails. To do this:
Ensure that the appropriate trail filter is set as the default. For
information about available predefined filters and how to set one as the
default, see Filtering the Trails Pane.
OR
Select any combination of elements and links in the main window map
or elements in the topology tree. (If more than one view is open, the
most recently opened view applies.) The Trail List window map opens
with only those elements and links and the Trails pane displays only
associated trails. In this case, the default filter is overridden.
3. On the main menu bar, select Traffic > Trail List.
OR
On the toolbar, click the Trail List icon .
To open the Trail List window with trails of a single LE:

1. In the Physical or Optical layer, select an LE in the View map.
2. Right-click and select Show Trails. The Trail List window opens showing
only trails associated with the selected LE.

Trail List Window

The Trail List window enables viewing and filtering trail information and
viewing alarms on trails. It features a graphical representation of all or
preselected objects in the active topology layer, a filtered list of existing trails,
and detailed information about a selected trail.
For information about how to open the window, see Accessing the Trail List
Window.
The window’s Map view shows elements and links of the selected topology;
see Map View.
The window displays information about selected trails in the active topology
layer in the following panes and tabs:
| Trails Pane: All or a filtered set of trails from all topology layers. You can
select specific trails for various operations.
Trail Parameters tab
| Trail Properties Pane: Detailed information about a selected trail; enables
you to modify some properties.
Endpoints & Path tab
| Endpoints List Pane: Endpoints of a selected trail.
| Resource Tree Pane: Displays resources for a trail in a tree hierarchy
under Main and Protection categories.
| Resource List: Lists details of selected trail resources individually or by
category.
These panes (except the Trails pane) are parallel to the same-name panes in the
Create Trail process. You can edit some non-path-affecting parameters in the
Trail Properties pane.

Other panes from the Create Trail process (including path-affecting

parameters) can be opened for editing through the Edit Trail window; see
Editing Trails. For a description of those parameters, see the following sections
in Creating SDH and EoS/MoT Trails:
| Basic Trail Parameters Pane
| Select Segment Pane
| Select Server Trail and Services Panes
| Select Resource Pane
| Advanced Trail Parameters Pane
| EoS/MoT Configuration Pane
Trail List Toolbar

The following functions are available from the Trail List window toolbar.
(You can access some of them from a shortcut menu displayed by right-
clicking a row in the Trails pane; see Trails Pane Shortcut Menu.)
Trail List window toolbar

Path:
Selects the path (route) whose attributes are viewed
(Main, Protection, or Both).
Show highlighted Complete trail represented by the highlighted trail in
trail on map Trails pane highlighted on map. Extent of trail depends
on the Path selection.
Edit selected trail Opens the trail highlighted in Trails pane for editing.
Plan highlighted Opens Plan Trail window, which enables you to design
trail networks ahead of time based on edited versions of
existing trails; see Planned Trails.
Show clients for Opens separate Trail List window filtering the client
selected trails trails of server trails selected in Trails pane; see Viewing
Associated Client or Server Trails.
Show servers for Highlights on the map the server trails of client trails
selected trails selected in Trails pane; see Viewing Associated Client or
Server Trails.
Reconnect Reconnects Incomplete trails selected in Trails pane.
selected trails Typically required when a problem arises when creating a
trail, for example, if an NE included in a trail is disconnected.
For more information, see Reconnecting Trails.
Show current Displays current alarms on trails selected in Trails pane;
alarms on selected see Viewing Alarms for Selected Trails.
trails


Show operation Displays detailed results of the last operation, enabled
results only if not completely successful. For more information,
information see Performing Trail Operations.
Open Trail Opens Trail Consistency Indicator window to
Consistency synchronize trails selected in Trails pane. (Trail
Indicator window synchronization reconciles differences between trail
for selected trails definitions in the LightSoft database and the EMS.)
Export selected Exports trails selected in Trails pane to an XML file for
trails to file network planning or backup purposes; see Exporting Trails.
Export to CSV Exports list data to a delimited format file like CSV for
import to Microsoft Excel or a relational database
application. See Exporting to CSV.
Print selected Prints contents of Trails pane. If any trails are selected,
trails prints only those; see Print Formats.
Delete selected Deletes trails whose checkboxes are selected in the Trails
trails pane. (If no selected checkbox, deletes the highlighted
trail. If trails are selected, deletes only the selected ones.)
Select all trails Selects all trails in Trails pane.
Unselect all trails Unselects all trails in Trails pane.
Reload whole trail Reloads the Trail List window and Trails pane, showing
list newly created trails. All trails in Trails pane become
unselected. Trails continue to be listed according to the
active filter.
Filters Trails pane according to selected filter.
Edit filter Edits a filter. Enabled only if objects were preselected in
the main window before the Trail List window was
opened or a user-defined filter is selected.
Set filter as Sets a filter as default.
default
Create filter by Quickly filters trails by label and/or ID. This method defines
trail ID and label a filter for each use and does not involve a filter template. For
(Quick Filter) more details, see Creating a Quick Trail Filter.
Map View
The map view shows the elements and links of the selected topology view,
similar to the most recently opened main window map view (but without alarm
color coding).
You can perform operations on selected objects and links in the map view
view; see Managing Elements and Groups.

Trails Pane
The Trails pane lists a filtered set of trails, regardless of topology layer.
Clicking a trail in the pane makes it the focus of the information provided by
other panes. Highlighting a trail or marking the checkbox of one or more trails,
selects those trails for various trail operations.
The Alarm State column lets you easily identify alarmed trails, showing the
worst alarm state of objects participating in the trail.
The following trail statistics are shown in the status bar:

| Total trails: n/n (for example, 32/32) - number of trails filtered in/total
number of trails that can be displayed.
| Selected: n - total number of selected services (with marked checkboxes).
You can perform specific functions via the toolbar on the right.
Click the Trail List window Reload whole trail list icon to reload the
Trails pane. One-hundred filter-defined trails are displayed. You can upload
additional trails (up to a configurable limit) by clicking the Load more trails
(upper) or Load all trails (lower) buttons.
NOTE: For information how to configure the Load more trail

limits, contact ECI Telecom customer support.
When you select a trail in the Trails pane and select the Enable/Disable show
trail when selected icon , the trail and its endpoints are highlighted on the
map and information about the trail is shown in the window panes. Click the
icon again to clear this information. The icon is selected by default when
the window opens.
NOTE: You can choose which columns to show in the Trails pane;
see Showing, Hiding, and Auto-Fitting Columns.
Click the Ethernet Service List window Reload icon to reload

information for that window and the Services pane.

Trails Pane Toolbar

Trails pane toolbar

Load More Loads an additional increment of filter-defined trails up
to a configurable limit. Contact ECI Telecom customer
support for information how to configure the Load more
trail limits.
Load All Loads all filter-defined trails in the network.
Show highlighted When selected (default when the window opens) and a
trail trail is highlighted in the Trails pane, the trail and its
endpoints are highlighted on the map. Information about
the trail is shown in the window panes. Deselecting the
icon disables highlighting a selected trail's path on the
map.
When the option is not selected, the Show Highlighted
Trail on Map toolbar option can be used to identify a
selected trail in the Trail List map view; see Trail List
Toolbar.
Quick Filter Enables you to quickly filter the trails in the Trails pane
by Label, Trail ID, and/or Customer; see Creating a Quick
Trail Filter.
Trails Pane Shortcut Menu

Some functions are available from a shortcut menu displayed by right-clicking
a row in the list.
Trails pane shortcut menu options
Option Suboption/Description
Edit See icon description in Trail List Toolbar.

Highlighted
Plan
Highlighted
Delete
Reconnect
Current
Alarms
Show Show Highlighted See icon description in Trail List Toolbar.
Show Current Shows all current connections/paths of the
Connections trail in the network. If the trail was rerouted,
highlights the new parts of the route.
Otherwise, shows the provisioned path. For
details, see Monitoring the ASON Domain.

Show Clients See icon description in Trail List Toolbar.

Show Servers
Trail Trail Consistency See icon description in Trail List Toolbar.
Operations Operation Results See icon description in Trail List Toolbar.
Increase Increases the bandwidth of a selected EoS
Highlighted trail without having to recreate the trail. See
Increasing Trail Bandwidth.
Decrease Decreases the bandwidth of a selected EoS
Highlighted trail without having to recreate the trail. See
Decreasing Trail Bandwidth.
S-VLAN Adds the S-VLAN registration to an EoS
Registration trail, enabling all services of the PB network
to utilize the virtual link represented by the
trail. For more details, see S-VLAN
Registration for a Trail.
Activate Activates the bandwidth of a selected EoS
Bandwidth trail if it was not activated when the new
EoS trail was created; see Activating Trail
Bandwidth.
Split Trail Splits a "long" SDH server trail (a server
trail that spans more than a single segment)
into two server trails; see Splitting a Long
Trail.
Trail Utilities Path Protection Enables you to view and redirect traffic flow
Switch across the main and protection paths, see
Path Protection Switching.
Maintenance Diagnoses connections and ports problems;
Operations see Maintenance Operations.
Performance | Current PM: Enables you to view
Monitoring current trail performance for 15-minute
or 24-hour intervals; see Trail
Performance Monitoring.
| Multi Period PM: Opens the Multi
Period PM window, which enables
flexible reporting of historical PM
counts; see Multi Period PM.
Availability Opens the Optical Channel Availability
window for the selected OMS trail; see
Viewing Optical Channel Availability.
Export to XML See icon description in Trail List Toolbar.
Export to CSV
Print

Trails Pane Columns

You can choose which columns to show in the pane; see Showing, Hiding, and
Auto-Fitting Columns. Standard column sorting and ordering operations can
also be performed in the pane; see Working in LightSoft.
OPTIONAL FEATURE: The Trails pane Alarm State

column is a fully integrated add-on capability, available on a
cost basis. If not purchased, this feature is deactivated.
Trails pane columns
Column Description
Selects trails for various trail operations (as described in context).
The currently highlighted trail (whether or not the checkbox is
selected) is the focus of information shown in Trail List window
panes.
Label Trail label, user-defined or assigned automatically by trail creation
process; see parameter description in Basic Trail Parameters Pane.
Customer User-defined trail customer.
Trail ID System ID for the trail, for example, "36(38)", formatted as
Unique ID Number (Managed System ID), where:
| Unique ID Number – ID of the trail sequentially assigned when
creating the trail.
| Managed System ID – ID of the management system where the
trail was created (EMS or LightSoft).
Trail State State of the trail:
| OK: Trail is provisioned in the network and is consistent with
LightSoft.
| Inconsistent: LightSoft network values are different from the
values in the EMS/network. Trail consistency operations or
modification in the EMS may be required.
To resolve this problem:
1. Force upload the relevant NEs.
2. Admit the trail from the network using Synchronization.
| Failed: LightSoft was unable to set up the trail in the network
as defined due to network limitations.
To resolve this problem: Check that the parameters are correct.
Try to connect the same XCs in the failed NE from the EMS
level.
| Incomplete: LightSoft was unable to set up the trail in the
network as defined. This problem typically arises during trail
creation if an NE included in a trail is disconnected or a craft
terminal is connected, causing the resulting trail to be
incomplete.
To resolve this problem: After the NE is uploaded or the craft
is disconnected, reconnect the trail to send the missing cross
connects to the network.

Column Description
Rate Transmission rate of the trail, for example, VC-4.
Payload Payload type for the trail - a value derived from the EMS according
to the card's port. For more information, see Supported Rates and
Payload Types.
Protection Quality Type of protection, if any, configured for the trail:
| Unprotected: There is no redundant path for transmissions if
the main path fails. All resources may be shared.
| Partial: Some resources are shared between the main and
protection paths. Details of the common resources are available
from the Trail Properties Pane Statistics tab.
| Full: No trail resources are shared (full diversity) between the
main and protection paths. However, endpoints may be shared.
Service Indicator Non Service, Service, Bronze, Silver, or Gold.
Trail Purpose Whether the trail acts as a server trail:
| Yes: Trail acts as server trail for other trails.
| No: Trail acts as a client (service) trail carrying user traffic, for
example, PDH, or GbE.
Comments Free text field for trail description.
Private ID Private ID assigned to trail. A user-configurable free text
identification string that may be downloaded to some EMSs.
Directionality Direction of trail: unidirectional or bidirectional.
Trail Type | P2P - standard point-to-point trail with full connectivity
between endpoints
| X - X-pattern trail involving four endpoints
| Y - Y-pattern trail involving three endpoints
| DR - diverse routes
| Flex - multiple cross connects that do not constitute a valid trail
due to the lack of full connectivity between the endpoints
Modification Time/Date when trail was last modified.

Time
Modified Using Method used for modifying trail:
| NMS – via a different NMS
| GUI – via the LightSoft GUI
| XML – via an XML file
| Acquisition – using LightSoft to acquire cross connects created
in an EMS
| Automatic Trail – VC-4s created automatically when creating
the link
Creation Time Time/Date when the trail was created.
Created Using Method used to create the trail (see description of Modified Using
column).

Column Description
User Usage State | Idle – trail can be deleted from Trail List
| Active – trail cannot be deleted from Trail List
Protection Protection layer for the trail:
| Unprotected: Trail is unprotected.
| Underlying: Trail is protected due to the layer it traverses. For
example, traffic in MS-SPRing configurations is protected. If a
trail (for example, VC-4 rate) uses this ring, the trail is
protected on the underlying (MS-SPRing) layer. Alternatively,
if a link of type SDH is protected on the OTN layer due to
transponder protection, all the trails using that link are
underlying protected (but protection may be partial).
| Current: Protection exists on current layer only.
| Current and Underlying: Trail is protected both on current
layer and underlying layer.
Alarm State Worst alarm state of trail's objects; see Object Status Color
Indications.
VCAT Size Virtual Concatenated paths, indicating the number of resources that
can be used on a single EoS trail segment. (For data trails only.)
ETH Service Type Layer 1 or 2. An EoS trail is automatically considered a Layer 2
trail if one or both of its endpoints are Layer 2 ports. If both
endpoints are Layer 1 ports, the trail is automatically considered a
Layer 1 trail.
Channel 1 DWDM frequency or CWDM wavelength used by an optical trail;
see Optical Trail Parameters.
Channel 2 DWDM frequency or CWDM wavelength used by a bidirectional
optical trail in the return direction (if different from that used in the
forward direction); see Optical Trail Parameters.
Created By User User who created trail.
Modified By User User who last modified trail.
ASON Denotes that an ASON protection scheme applies. See the ASON
Protection checkbox in Create Trail Window - Basic Trail Parameters Pane.
See also ASON Protection Schemes.
Path State Provisioned if the path remains the main path, or Rerouted if the
protection path is being used.
For ASON Trails:
Whether the ASON trail’s working path is:
| Provisioned: The path originally provisioned through the
LightSoft new trail creation process. The label remains
associated with the originally provisioned path for the trail
unless the trail is edited to have another path as the
provisioned path.
| Rerouted: An alternative protection path (rerouted or restored
path), automatically found by the control plane.

Further about ASON Path State

If a failure occurs on the originally provisioned path and a rerouting to
protection takes place, the trail state changes from Provisioned to Rerouted.
It remains Rerouted until the trail is either:
Reverted back to its originally provisioned path (manually through
ASON maintenance operations (see ASON Maintenance Operations) or
automatic reversion when the failure is repaired).
OR
Redefined so that the current restored path is set as the provisioned
path. This is done by admitting the trail using TCI acquisition, then
editing the trail to remove the old provisioned path. For more
information, see Performing Trail Synchronization.
The redefinition is reflected in the LightSoft database and ASON is
informed of the change in the trail’s LightSoft-provisioned path.
In this case, the trail will not automatically revert back to the old
provisioned path after the failure is repaired. (It remains part of the
ASON domain and can be used as a protection path if available.)
Redefining the provisioned path may reflect a decision not to
immediately repair the originally provisioned path and to release its
resources for other purposes.
NOTE: Currently, if the trail is rerouted, the Trail State is

inconsistent because of different paths reflected in LightSoft
vs. the network.
TIP: The Show Current Connections right-click option

shows all current connections/paths of the ASON trail in the
network. If the trail was rerouted, highlights the rerouted main
and protection paths in Dark Pink and Dark Blue, respectively;
see Monitoring the ASON Domain.

Trail Properties Pane

The Trail Properties pane lists the main trail attributes defined in the Create
Trail process.
User Selection View
The User Selection view provides quick access to the most important attributes
and enables you to set trail preferences.
Click the Configure Attributes List icon (top right) to display the User
Preferences window, where you can configure the attributes included in this
list and set other trail preferences. For more information, see Trail Management
Preferences.
Standard View
The Standard view (default) displays all attributes and enables you to edit
certain parameters. Click the Edit Attributes icon (top right, enabled when
a trail is selected) to set non-trail path affecting fields in each tab to Edit mode.
The icon changes to a Save Attributes icon , enabling you to save changes.
NOTE: You can edit trails using the Edit Trail window; see
Editing Trails. You can also edit additional trail parameters
and characteristics generally present in Create Trail window
panes. Some parameters present in both the Basic Trail
Parameters tab and the Edit window may be editable only
from one or the other location.

The Trail Properties pane Standard view lists trail attributes in the following
tabs:
| Basic Tab
| Advanced Tab
| Protection Tab
| Statistics Tab
The same pane and tabs are available in the Edit Trail window; see Editing
Trails. (That window enables you to edit additional path-affecting trail
parameters and characteristics that are present in Create Trail window panes.)
Some Trail Properties pane parameters present in both the Trail List and the
Edit windows may be editable only from one or the other location.
Basic Tab
When the tab is in Edit mode, editable parameters appear white.
Trail Properties pane fields – Basic tab
Field Description
Label See descriptions in Trails Pane.
Customer
Trail ID
Directionality
Rate
Payload
Trail State
VCAT Size
Channel 1
Channel 2

Advanced Tab
When the tab is in Edit mode, editable parameters appear white.
Trail Properties pane fields – Advanced tab
Field Description
Comments See descriptions in Trails Pane.
User Usage State
Private ID
Service Indicator
Trail Purpose
ETH Service Type
Trail Type
View on ETH Layer Yes or No. Indicates whether this EoS/MoT trail is visible
as a virtual link on the ETH/MPLS layer. For more
information, see the parameter description in EoS/MoT
Configuration Pane.
Flex Reason Shows the reason for the trail having been classified as flex.
Flex trails do not conform to normal trail patterns.
Creation Time See descriptions in Trails Pane.
Created Using
Modification Time
Modified Using
Created By User
Modified By User

Protection Tab
No parameters are editable in the Protection tab.
Trail Properties pane fields – Protection tab
Field Description
Diverse Routes Whether a trail is fiber diverse. (A low order trail may be
fully diverse by VC-4s but not fiber diverse.) See the
parameter description in EoS/MoT Configuration Pane.
Number of Routes Number of diverse routes over which EoS trail is configured
to carry traffic through different nonshared fibers. Shows
"1" if diverse routes is not defined and all resources are
allocated to the same route or link.
Protection See description in Trails Pane.
Protection Quality See description in Trails Pane.
Shared MEs Number of MEs common to both main and protection paths.
Shared Links Number of links common to both main and protection paths.
Shared SRLGs Number of SRLGs common to both main and protection
paths.
Shared SRLG Names Names of SRLGs common to both main and protection
paths. Shown as a comma-separated string.
Shared Cards Number of cards common to both main and protection
paths.
DNI Nodes Number of DNI nodes (applicable only to trails in which
DNI applies).

Field Description
DRI Bridges Number of DRI bridges (applicable only for trails in which
DRI applies).
Current Layer SNCP SNCP switching points at the same layer as the trail.
Underlying Layer SNCP switching points on an underlying layer. For
SNCP example, a trail with rate VC-12 may be protected by an
underlying SNCP layer if it uses a protected VC-4 server
trail.
MS-SPRing Links Number of MS-SPRing-protected links.
MSP Links Number of MSP-protected links.
Extra Traffic Resources Number of pre-emptable links.
ASON Protection Denotes that an ASON protection scheme applies. See the
ASON checkbox in Create Trail Window - Basic Trail
Parameters Pane. See also ASON Protection Schemes.
Path State Provisioned if the path remains the main path, or Rerouted
if the protection path is being used. See more information
in Trails Pane - Trails Pane Columns.

Statistics Tab
This example shows the tab in Edit mode. No parameters are editable in this tab.
Trail Properties pane fields – Statistics tab
Field Description
Length of Shortest Length of shortest EoS trail between diverse routes - sum of
the lengths of all links through which it passes, in the unit of
measure recognized by the system (for example, km or
miles).
Route ID of Shortest Route ID of the shortest EoS trail.
Length of Longest Length of the longest EoS trail between diverse routes.
Route ID of Longest Route ID of the longest trail.
Min. Hops Number Fewest number of hops of an EoS trail between diverse
routes.
Route ID of Min. Hops Route ID of the trail with the fewest hops.
Max. Hops Number Highest number of hops of an EoS trail between diverse
routes.
Route ID of Max. Hops Route ID of the trail with the most hops.
Cost of Min. Cost Lowest cost of an EoS trail between diverse routes - the sum
of the lengths of all links through which it passes. Link cost
assessments are set in the link properties when it is created.
Route ID of Min. Cost Route ID of the lowest cost trail.
Cost of Max. Cost Highest cost of an EoS trail between diverse routes - the
sum of the lengths of all links through which it passes. Link
cost assessments are set in the link properties when it is
created.
Route ID of Max. Cost Route ID of the highest cost trail.
Worst Link Quality Lowest quality of link a trail may traverse. Link quality is
set in the link properties when it is created.

Endpoints List Pane

The Endpoints List pane lists the endpoints of a selected trail. The Endpoints
List pane fields are the same as described in Endpoints List Pane.
3
Resource Tree Pane

The Resource Tree pane lists the selected trail resources. For detailed
information about the pane contents and associated procedures, see Resource
Tree Pane in Create Trail window section.
Resource List
The Resource List pane displays details of selected trail resources individually
or by category (All, Main, or Protection). For detailed information about the
pane contents and associated procedures, see Resource List in Create Trail
window section.

Viewing Trail Information

Selecting a trail in the Trails pane makes it the focus of the detailed
information provided in other panes. In addition, associated trails can be
highlighted in the map view, or associated alarms can be displayed.
Viewing Information Detail

The Trail List window opens with several information panes, one of which is
the Trails pane; see Trails Pane.
When you click to select a trail in the Trails pane list, the trail becomes the
focus of the information provided by other panes.
When one or more trails are selected in the Trails pane, associated objects and
links are highlighted in the Trail List window map.
To view information about a trail:

1. In the Trail List window, select a trail filter that filters the trails you want
listed in the Trails pane. For information about trail filters, see Filtering the
Trails Pane.
2. Click to select a trail in the Trails pane. By default, the Show icon on
the toolbar on the right is selected and:
The other information panes immediately show detailed information
about the selected trail.
The trail's associated elements and links are highlighted in the Trail
List window map.
NOTE: When you select trails in the Trails pane and the
Show one trail only option is selected in the Preferences
dialog box, the Trail List window map shows only the
associated elements and links, hiding all the others. For more
information, see Trail Management Preferences.
You can select trails in the Trails pane in two ways:

| Click and highlight the trail (as described in the previous procedure). Only
one trail at a time can be selected.
| Select (or deselect) the checkboxes of any number of trails. This method is
used for operations such as delete, export, reconnect, show current alarms,
TCI, print, and some others. See Performing Trail Operations for more details.
In this section, "selecting a trail" means selecting its checkbox.

Viewing Associated Client or Server Trails

You can view which client and/or server trails are associated with the specific
trail you are working on.
The Show clients for selected trails function opens a separate Trail List
window filtering the client trails of server trails selected in the Trails pane,
according to one of the following topology layers:
| Low order SDH/EoS trails traversing selected high order trails.
| High order trails traversing selected LP trails.
| LP trails traversing selected OCH trails.
| OCH trails traversing selected OMS trails.
The Show servers for selected trails function highlights on the map the
server trails of client trails selected in the Trails pane, according to one of the
following topology layers:
| High order SDH trails through which selected Low order SDH/EoS trails
are traversing.
| LP trails through which selected high order trails are traversing.
| OCH trails through which selected LP trails are traversing.
| OMS trails through which selected OCH trails are traversing.
You can also view other traffic entities associated with selected trails:
| MoT trails associated with a tunnel; see Viewing Tunnel Information -
Show Associated Trails, Services, or Protected Tunnels.
| Trails associated with selected services; see Viewing Service Information -
Viewing Associated Traffic Entities.
To view associated client or server trails:

1. In the Trail List window Trails pane, select the checkboxes of the trails
for which you want to view associated trails.
2. On the window toolbar:
Click the Show clients for selected trails icon or Show servers
for selected trail icon .
OR
Right-click the trail and select Show Clients or Show Servers from the
shortcut menu.
A new Trail List window opens. The Trails pane lists the server or
client trails associated with the selected trails.
Viewing Alarms for Selected Trails

You can view all the alarms that affect selected trails. These alarms are
displayed in the Current Alarms window; see Viewing Alarms for Selected
Traffic Entities. You can also view the trails affected by a selected alarm; see
Viewing Traffic Entities Affected by an Alarm.

Monitoring the ASON Domain

ASON domain trails and elements trails can be monitored in a variety of ways.
ASON links can be identified in map windows with an icon on the link line.
LightSoft provides the following means for ASON-monitoring:

| Show Trails function: Opens the Trail List window showing the trail path
in the network; for more details, see Viewing Trail Information. (Right-
click a link in any map view and click Show Trails.)
| Show Highlighted: Shows the trail path for a selected trail in the Trail
List window. (In the Trail List window, right-click any link in the map
view and select Show Highlighted.)
| Show Current Connections: Shows the current paths/routes/connections
of an ASON trail in the Trail List window. Enabled only for ASON trails.:
Originally provisioned Main path highlighted in Pink.
Rerouted Main path highlighted in Dark Pink (formerly not
highlighted).
Originally provisioned Protection path highlighted in Blue.
Rerouted Protection is shown as Dark Blue (formerly not highlighted).
(In the Trail List, right-click any link in the map view and select Show
Current Connections.)

| Show ASON Domain: Marks all ASON-based entities (elements and links)
in the current map view. (Right-click any ASON object in the view and select
Show ASON Domain.)
NOTE: When two ASON “domains” are connected by non-

ASON equipment, while the entire topology is visible in the
view, only the ASON objects are marked. Currently multiple
ASON “domains” are viewed as part of a single domain. In
future versions, they will be differentiated by serial numbers.
| Expand ASON Domain in New View: Same as Show ASON Domain,

but opens the objects in a new window.
| ASON Maintenance Operations: Reverts the trail path to either the
provisioned or protection path, or reroutes the current main or protection
path to an alternate route found by ASON, and allowing/inhibiting these
actions on specified ASON trails; see ASON Maintenance Operations.
| Availability Map and Availability for Link: Show the link utilization
status and extent of spare resources in the ASON domain; see Viewing
Resource Availability on Links. It is important that ASON networks
consistently maintain spare capacity over and above ordinarily required
resources, sufficient to overcome multiple failures with heavy bandwidth.
ECI recommends a threshold spare capacity consistent with operator
priorities and policy on a case-by-case basis via Network Design Platform
(NDP) planning tool. The link utilization tools enable monitoring the current
spare capacity and ensuring that the policy threshold level is maintained.

Performing Trail Operations

This section describes how to perform trail-related operations and view
operational results.
To perform a trail operation:

1. Select the trails by selecting their checkboxes in the Trails pane.
2. Select a Trail List window toolbar option or right-click a trail in the Trails
pane and select a shortcut menu option.
3. Continue the operation as described in the corresponding procedure in this
section. At the conclusion of the operation:
At the conclusion of the operation, a message window opens showing the
operation results. If any part of the operation was not successful,
information is shown about the failed operations. If multiple trails were
involved, the window includes results for each trail.
The Operational Results Info icon in the Trail List window toolbar
becomes enabled when an operation is not completely successful. You can
revisit the last results message window by clicking this icon.
The icon remains enabled until another operation is performed. If the
second operation is completed successfully, the icon is disabled. If it is
partially successful, it displays the detailed results for that operation.

Filtering the Trails Pane

You can filter the Trails pane (determine the trail records that are displayed)
according to any combination of trail attributes and objects activated from
either predefined or created filters. You can also filter client or server trails
associated with specified trails.
The "Total trails" statistic (number/number) in the status bar is the number of
trails filtered into the view vs. the total number of trails that can be displayed.
(The status bar also shows the total of trails having checkboxes selected.)
LightSoft supports the following predefined trail filters:
| All: All trails are displayed (no filter is applied).
| No Trails: No trails are filtered in. (When this is the default filter, the Trail
List window initially opens quickly without any trails. Another filter should
then be applied; see Applying a Filter and Setting it as Default.)
| High Order: High order SDH trails are filtered in.
| Low Order: Low order SDH trails are filtered in.
| EoS/MoT Trails: Ethernet EoS/MoT trails are filtered in.
| Optical Trails: Optical OMS, OCH, and LP trails are filtered in; see
Optical Trails.
| Data over WDM: Optical EoS trails are filtered in; see Optical Trails.
Filter options from the main window and Trail List

Filter options can be activated from either the LightSoft main window or the
Trail List window.
From the LightSoft main window:

You can use the Traffic menu Trails > Trail Filters option (or Trail Filters
icon ) to:
| Create or edit a new filter according to any combination of trail attributes or
objects; see Creating and Editing Advanced Filters.
| Edit, rename, or delete a filter that you created, or set it as the default
(which automatically activates it when the Trail List window opens); see
Rename, Delete, Set Default Filter Actions.

The Trails pane can automatically be opened with trails corresponding to

preselected objects in the LightSoft main window; see Creating SDH and
EoS/MoT Trails.
From the Trail List window:

You can:
| Use the Quick Filter icon to quickly filter by label, customer, and/or
trail ID; see Creating a Quick Trail Filter.
| Use the Filter selector dropdown list to activate

any filter. You can also use the Set Filter as Default toolbar icon to
set the current filter as the default (automatically activated when the Trail
List window opens); see Applying a Filter and Setting it as Default.
(The icon is disabled if the currently applied filter is already the default.)
| Use the Edit Filter icon to:

Create a new filter with preselected objects; see Creating a Filter with
Preselected Objects.
Edit a user-defined filter; see Another Way to Edit a Filter.
Creating a Quick Trail Filter

The Quick Filter function enables you to quickly filter the trails either currently
in the Trails pane, or throughout the database, by Trail ID, Label, and/or
Customer. This method does not involve a filter template and is defined per use.
To quickly filter trails by trail ID, label, and/or customer:

1. Open the Trail List window, as described in Accessing the Trail List
3
Window.
2. In the Trails pane, click the Quick Filter icon . A quick filter field bar
opens at the top of the pane.

3. Enter a text string to the relevant fields to filter in trails with field values
that include this text. See the field descriptions in Trails Pane Columns.
3
You can enter partial strings to identify all trails with this text anywhere in
the fields. For example, enter xy to find all trails with xy anywhere in the
field value. (Wildcard character is not used.)
NOTE: The text field filter is case sensitive.
The table immediately adjusts to show trails previously in the table that
satisfy the filter criteria.
OR
To filter the entire database (instead of the current table contents), enter
a string to each relevant field and then click Force Filter .
TIP: You can filter incrementally:

First perform a Force Filter search of the entire database.
Then apply multiple incremental filters to the current table
contents, adjusting the filter criteria on-the-fly to change the
composition of trails displayed.
Click Info to display an Info Tip describing the use of this filter type.
Click Clear Filter to clear the current quick filter selections. (You can
also backspace to empty a filter field.)
4. Click Close Filter to close the quick filter field bar.

After the field bar is closed:
If Force Filter (database search) had been used, the list reverts to its
contents before the filter was applied.
Otherwise, if a table search was performed, the latest filtered contents
are retained in the list.
TIP: In the case of a table search (no force filter), a

temporary filter is automatically created (in the same way as
when objects are pre-selected before opening the Trail List
window) which you can use as a base for other filter actions;
see Creating a Filter with Preselected Objects.

Working with Advanced Trail Filters

Advanced filters enable you to view a subset of the trails in the Trail List
window according to any combination of:
| Trail attributes (like specific rates)
| Selected objects (all trails traversing specific objects)
| Only trails that terminate at or go through objects
New filters can be created from scratch or based on an existing user-defined
filter. A new filter can be created that uses preselected map window objects.
You can also edit, rename, or delete the filters that you create.
Saving a filter after a create or edit operation automatically applies the filter
settings to the open Trail List window. Any other filter can be applied as
needed at any time.
Applying a Filter and Setting it as Default

Any filter (predefined or user-defined) can be applied, immediately changing
the trails listed in the Trails pane. In addition, the currently applied filter can
be set as the default, defining the trails that the Trail List window
automatically display in a new session.
TIP: Opening the Trail List window may be time

consuming if many trails are filtered in. If you choose "No
Trails" as the default filter, the window quickly opens initially
without any trails in the Trails pane.
You can then apply a different filter.
To apply a filter and (optionally) set it as default:

1. Open the Trail List window.
2. Select a filter from the Filter dropdown list
.
The filter is immediately applied, reflected in trails listed in the Trails
pane.
3. You can optionally set the current filter as the default by clicking the Set
filter as default icon . The Trail List window now automatically
opens any new session with this filter.

Creating and Editing Advanced Filters

Advanced filters are used to search the database for trails that satisfy the filter
criteria. The following describes how to create or edit a filter that includes
advanced criteria combinations.
NOTE: The procedure includes a resource object-selection

step. In this case, objects preselected in a map window are not
relevant. For information about how to create a filter with
object preselections in the LightSoft main window map, see
To create or edit an advanced filter:

1. In the Traffic menu, select Trails > Trail Filters.
OR
On the main toolbar, click the Open Trail Filters icon . The Trail
Filters dialog box opens. (You can view a summary of parameters for an
existing filter by selecting the filter in the Filters pane.)

2. Click New to create a new filter.

OR
Select a user-created (non-predefined) filter that you want to modify in the
Filters pane and click Edit (enabled when a user-created filter is selected).
The Create Filter or Edit Filter dialog box opens.
Click the Show Tree button to open the Topology Tree pane (as shown
in the example). The button changes to a Hide Tree button for hiding
the tree if not required. This is used for filtering by selected objects in Step
5.
3. In the Filter Name field, type a name for the new filter (for example,
MyFilter).
OR
If you are editing, this field is disabled. You can save the modified filter as
a different name, if needed.
4. If you want to filter by parameters:
a. In the Filter By area, select the parameter checkbox.
b. Specify the required value. While a parameter is highlighted, the Value
area shows either:
Text entry field (see the note about the text field entry below)
Dropdown list of possible values
From/To date/time entry fields

Radio buttons

c. If multiple dropdown list selections are required for a parameter, open

the list again and select additional values. The multiple selections are
displayed in the Value area.
d. Repeat the above for as many parameters as needed. (You can remove a
selected value by selecting it again.)
NOTE ABOUT TEXT FIELD ENTRY:

Text filters are case sensitive.
If filtering by Label and Customer text entry fields, use the
wildcard character * to filter in all trails where the field value
includes a specified string, for example:
xy* to filter in all trails with the field value starting with
xy
*xy* to filter in all trails with xy anywhere in the field
value
*xy to filter in all trails with the field value ending with xy
(this pattern is not recommended).
OR
If filtering by any other text fields, or if any resource objects
are selected in the Topology Tree area (see next step), enter
xy to find all trails with xy anywhere in the field value.
(Wildcard character is not supported.)
Click the Info button to display an Info Tip summarizing

these rules.
5. If you want to filter by selected resource objects to which trails are

associated, move objects from the Topology Tree area to the Topology
tab, as follows:
a. In the Topology Tree area:
Select the topology layer for the filter: Physical (Site), SDH,
Optical, or ETH/MPLS (double-click the root of the tree to refresh
its elements).
Select the objects for which you want to filter trails (drill down in
the tree). To select multiple objects, press SHIFT and click.
b. In the Topology pane, use the button to move selected objects from
the Topology Tree area to the Topology tab (use the button to
remove objects not required for the filter).
NOTE: If you are filtering with text entry fields as well as

resource object selections, see the note in the previous step
for the entry rules that apply.

6. If you want to filter by trail type, in the Trail Type dropdown list, select:
All Trails (default): If you want to filter in trails that either end in or
traverse the selected objects.
Terminating: If you want to filter in only trails that end in the selected
objects.
Through: If you want to filter in only trails that traverse the selected
objects.
7. To save the new filter (or save the edited filter under the same name), click
Save.
OR
To save the edited filter under a different name, click Save As. A Save As
dialog box opens where you can enter a new name for the filter. Click OK
to complete the operation.
The Create Filter dialog box closes. The new filter is automatically
activated and included in the Filter selector dropdown list.
8. Click Close to close the Trail Filters dialog box.
Another Way to Edit a Filter

You can also select a user-defined filter for editing via the Trail List window.
To edit a filter via the Trail List window:

1. Open the Trail List window.
2. In the Filter dropdown list, apply a user-defined filter
3. Click the Edit Filter icon . The Edit Filter dialog box opens with the
criteria for the selected filter.
4. Continue to edit the filter as described in Creating and Editing Advanced
Filters, from Step 3.

Creating a Filter with Preselected Objects

You can create a new trail filter with objects selected from the LightSoft main
window map. This avoids having to select the elements again when creating the
filter. Those objects are automatically reflected in the Trail List window map
and in a "Temporary" filter which you can build on.
To create a filter with preselected objects:

1. In the LightSoft main window map, with the desired topology layer
selected, select any objects that you want to include in a new trail filter.
2. Open the Trail List window: From the Traffic menu, select Trails > Trail
List, or on the toolbar click the Trail List icon .
The Trail List window opens with the selected objects and with the
Temporary filter preselected in the Filter selector
dropdown list.
3. Click the Edit Filter icon (enabled only if objects were preselected in
the main window before the Trail List window was opened). The Edit
Filter dialog box opens with the preselected objects already selected in the
Topology pane.


Rename, Delete, Set Default Filter Actions

This section describes how to rename a filter, delete a filter, or set a filter as
default (automatically applied when the Trail List window opens).
To rename or delete a filter, or set a filter as default:

1. From the Traffic menu, select Trails > Trail Filters.
OR
On the main toolbar, click the Open Trail Filters icon . The Trail
Filters dialog box opens.
2. Select a filter and click one of the following options:

Rename to rename a non-predefined filter. A Rename Filter dialog
box opens. Enter the new name and click OK to complete the action.
Delete to delete a non-predefined filter. A Confirm dialog box appears.
Click OK to complete the action.
Set Default to set any selected filter as the default. Another method is
described in Applying a Filter and Setting it as Default.
The New and Edit buttons are used to create and edit filters; for details, see
Creating and Editing Advanced Filters.
3. Click Close to close the Trail Filters dialog box.

Reconnecting Trails
You may sometimes need to reconnect a trail. This is typically required if a
problem arises during the trail creation process. For example, if an NE included
in a trail is disconnected at the time it is created, the resulting trail is left in an
incomplete state. In this case, reconnecting the trail sends the missing cross
connects to the network.
The Reconnect dialog box includes two checkboxes for the following
exceptional cases:
| Enable Alarm Master Mask (AMM) checkbox (default unselected):
Select to ensure that trail object masking is enabled in the EMS for all trail
objects regardless of any specific EMS settings (alarms are generated on all
trail objects). Enabling AMM operates in the same way as when you select
Alarm Master Mask "Apply" option when the trail is created in the Create
Trail window Advanced Parameters pane; see Advanced Trail
Parameters Pane. If the AMM settings for specific objects was changed for
troubleshooting or maintenance purposes, Enable AMM avoids having to
return to each object to manually reinstate its AMM setting before the trail
is brought back into service.
If the checkbox is not selected (default), the current AMM settings are left
unchanged for all objects in the trail path. Any adjustments to settings that
were manually performed in the EMS are retained.
| Activate Bandwidth checkbox (EoS/MoT trails only - default unselected):
Select to activate the trail bandwidth (if it is not already activated), in the
same way as the Activate Bandwidth feature; see Activating Trail
Bandwidth.
If the checkbox is not selected (default), the trail's bandwidth state is
unaffected.
Bandwidth can be deactivated in the trail edit process; see Editing Trails.

To reconnect a trail:
1. On the LightSoft main menu bar, select Trails > Trail List. The Trail List
window opens.
2. Select the checkboxes of the trail/s you want to reconnect.
3. Click the Reconnect icon . The Reconnect Trail dialog box opens.
4. Select the Enable Alarm Master Mask checkbox if you want to enable the
feature. For more information, see Advanced Trail Parameters Pane.
5. (EoS/MoT trails only) Select the Activate Bandwidth checkbox if you
want to activate the trail bandwidth (if it is not already activated). For more
information, see Activating Trail Bandwidth.
6. Click Yes to continue. A completion message appears, describing the
operation result and listing nonfatal errors. For more information, see

Editing and Deleting SDH,

Optical, and EoS/MoT Trails
This section describes how to edit or delete selected trails. The actions can be
implemented in the network either immediately or postponed to a later time.
When the actions are for future use, their details are exported to an XML file
and are put into effect by importing the file into LightSoft.
NOTE:
Edit or Delete operations may fail due to one of the following
circumstances:
LightSoft network values are different from the values in
the EMS/network. Trail consistency operations or
modification in the EMS may be required.
2. Admit the trail from the network using
Synchronization.
LightSoft is unable to set up the trail in the network as
defined. This problem typically arises during trail creation
if an NE included in a trail is disconnected or a craft
terminal is connected, causing the resulting trail to be
incomplete.
To resolve this problem: After the NE is uploaded or the
craft is disconnected, reconnect the trail to send the
missing cross connects to the network.

Editing Trails
The Edit Trail window described in this section provides extensive trail
editing options, including access to path-affecting parameters and
characteristics present in Create Trail window panes. Trails can be edited for
either immediate or future effect in the network.
Trail parameters can be edited provided the correct user capabilities are
present. Trails can be edited even if the edit operation is traffic-affecting.
Server trail endpoints cannot be edited.
NOTE:
Certain non-path-affecting parameters can be edited from
either the Edit window or the Trail List window panes, for
example, using the Trail Properties pane Edit Attributes
function, available from both windows; see Trail Properties
Pane.
Some parameters that are present in the Trail Properties
pane in both the Trail List and Edit windows may be enabled
for editing only from one or the other location (for example,
certain EoS trail parameters).
You can edit trails for either immediate or future effect in the network. When the
editing is for future application, the edit changes are exported to an XML file and
put into effect by importing the file into LightSoft; see Exporting Trails.

NOTES:
When a trail is edited, the Activate Bandwidth checkbox
is automatically cleared. If needed, select it to ensure
bandwidth remains activated. Bandwidth can also be
activated as described in Activating Trail Bandwidth and
Reconnecting.
The View on ETH/MPLS Layer checkbox cannot be
selected using the trail Edit window. You can select it
instead through the Trail List window's Trail Properties
Pane Standard View.
Moving endpoints and changing the route of an
unprotected trail are always traffic-affecting.
The user security capability required to perform traffic-
affecting trail edits is not the same as that for normal trail
editing.
It is sometimes possible to change equipment endpoint configurations without

editing the trail from LightSoft, for example, from GbE to FC-1G, or to modify
the rate setting of the TRP_C. In such cases the payload type, calculated when
the trail was created in LightSoft, is not updated automatically. You must
perform Edit Trail with activation to invoke the attribute completion to assign
the new payload type. (You do not have to actually change any trail parameter.)
Editing an MoT trail is disallowed if it:
| Has tunnels traversing it and the editing affects the trail's resources
(endpoints).
| Is protected by bypass tunnels and the new trail path uses different path.
The tunnels must be removed first.
Editing a VC-4 server trail that has client trails with tunnels traversing it or
bypass tunnels protecting it is disallowed. The tunnels must be removed first.
Editing VC4 server trails that have clients may take some time.

To edit a trail:
1. You may want to open the Edit Trail window with only selected NEs of
the view and the links running between them, rather than showing all the
objects in the current view. To do this, select the MEs or LEs on the
LightSoft main window view map.
2. Select the required topology layer, as described in Step 1 of the Creating a
Planned Trail procedure.
3. From the Traffic menu, select Trails > Trail List. The Trail List window
opens.
4. In the Trails pane:
Select a trail and click Edit highlighted trail on the toolbar.

OR
Right-click a trail and select Edit highlighted from the shortcut menu.
The Edit Trail window opens, showing the trail path.
TIP: When a Protected trail is selected, the

Main/Protection/Both selectors enable you to identify and
select the main or protection trail segments or the combined
main and protection trail.
5. Make the required changes to trail parameters, topology segments, and/or

endpoints. The window contains essentially the same panes and parameters
as the Create Trail window. For details, see Create Trail Window.
NOTES:
When Protection applies, you can change a Protection trail
segment to Main or a Main trail segment to Protection. Do
this by right-clicking the server trail path or topology segment
in the Resource Tree pane and selecting the Move to Main
or Move to Protection menu option.
You can edit trails from Unidirectional to Bidirectional
without first clearing the previous selections. The endpoints
are automatically changed from Add or Drop to Add&Drop.

6. If you are editing a DRI trail, perform the following actions:

a. Remove all bridge segments.
b. Change the protection layer to Current & Underlying.
c. Select all main TUs manually (starting from the main direction).
d. Select all protection TUs manually (starting from the protection
direction).
e. Define all main bridge segments as Bridge (with the correct direction)
and EP (ensure that the number of bridges in that window is always 1).
f. Define all protection bridge segments as Bridge (with the correct
direction) and EP (ensure that the number of bridges in that window is
always 1).
7. (Optional) Click the Complete trail icon . LightSoft searches for a path
using your selections. When a path is found, the details are displayed for
you to review. You can go back and modify the path if required.
A completion message appears, describing the result of the operation and
listing nonfatal errors. For more information, see Performing Trail
Operations. If the Complete step encounters a problem, see Diagnosing a
Create Trail failure in Creating SDH and EoS/MoT Trails.
8. If you want to activate the edit changes on the network immediately, click
the Activate trail icon .
The Progress bar shows the progress of bundle trail processing (if
applicable). An Abort button is included to stop the operation if needed.
At the conclusion of the Activate processing, a message appears describing
the result of the operation and listing nonfatal errors. For more information,
see Performing Trail Operations. If the Activate step encounters a problem,
see Diagnosing a Create Trail failure in Creating SDH and EoS/MoT
Trails.
NOTE: If Complete Trail was not previously performed or if

it was followed by any potentially path-affecting action (like
a change of endpoint), it will automatically be
performed/repeated before the trail is activated on the
network.
OR

9. If you want to implement the edited trail in the network only at a later time,
perform the following to export the edit details to an XML file:

OR
menu. The Export Trails dialog box opens in Edit mode.
Continue the procedure as described in Exporting Trails, from Step 4.

For information about how to eventually implement the edited trail in the
network, see Importing Trails.

Deleting Trails
You can delete trails in the Trail List window. You can delete several trails at
the same time by selecting them all simultaneously. All trails are deleted the
same way, whether they were created in LightSoft or created in the EMS and
later uploaded to LightSoft using trail synchronization.
When a trail is deleted, all cross connects defined for each NE in the trail are
also automatically deleted. If this does not occur (for example, if one of the
NEs was disconnected at the time the trail is deleted), the trail remains in the
Trail List window in an Incomplete or Failed state. The trail is removed from
the list when all resources are deleted.
You can delete trails for either immediate or future effect in the network. When
the deletion is for future application, its details are exported to an XML file and
put into effect by importing the file into LightSoft at a later time; see Exporting
Trails.
NOTE: A server trail cannot be deleted if client trails are

still traversing it - client trails must be deleted before their
server trails. When deleting client and server trails in the
same operation (whether for immediate or future effect), first
sort the Trails pane records so that the client trails come
before the server trails. This ensures that the trails that you
select for deletion are processed in the right order.
NOTE: MoT trails cannot be deleted if:

Tunnels use virtual links resulting from the MoT trail.
Bypass tunnel protection applies (next hop or next-next-
hop).You must first remove the tunnels or bypass tunnels.
EoS trails can be deleted even if Ethernet services are defined on the resulting
EoS virtual links. In this case, the related services become incomplete (they are
not deleted). It is the user's responsibility to ensure that any remaining services
on the trail are not required.
When the EoS trail carries S-VLAN or C-VLAN registered services, a
confirmation is required before the trail is deleted.
The EoS or MoT trail delete processing may take some time as the network
topology and status may be changed.
To delete a trail:
1. From the Traffic menu, select Trails > Trail List. The Trail List window
opens.
2. If client and server trails are to be deleted, sort the client trails to come first.

3. In the Trails pane, select the checkboxes of the trail/s you want to delete.
4. If you want the delete action to take effect immediately:
Click the Delete Selected Trails toolbar icon.

OR
Right-click any selected line in the Trails pane and select Delete.
a. When the EoS trail carries services where S-VLAN Registration or C-
VLAN Registration has been configured at either end, a warning
message opens:
"This action may result in Traffic Disconnection or may be Traffic
Affecting". Do you want to continue".
Select Yes to continue.
b. A confirmation window opens.
Click OK to confirm. A completion message appears, describing the
operation result. For more information, see Performing Trail
Operations.
OR
5. If you want the trail deletion to be implemented in the network at a later
time, save the action in an XML file, as follows:

OR
Right-click one of the selected trails and select Trail Utilities > Export
from the shortcut menu. The Export Trails dialog box opens in Delete
mode.
Continue the procedure as described in Exporting Trails, from Step 4.

For information about how to eventually implement the deletion in the
network, see Importing Trails.

Splitting a Long Trail

You can automatically split a "long" SDH server trail (a server trail that spans
more than a single segment) into two server trails. The trail is split at the point
where it traverses a selected ME. All the low order trails passing through the
VC-4 trails are also handled, enabling them to use both server trails. Cross
connects at low order level are created in both the split server trails via spanned
elements. This enables extending the trail from the segment that is common to
both original trails to the new segment.
This feature applies only to server (non-service) trails. The Trail List window
Trail Purpose parameter identifies a trail as either Server or Service. Service
trails include low order trail, concatenated trails, and flex trails (not having a
pattern that LightSoft recognizes - a flex trail is a service regardless of its rate).
The long trail can include UMEs, but the element at which the trail is split must
be an ME.
To split a long trail:

1. In the Trail List window Trails pane, click a long trail to highlight it in the
list. Click Show Trail to highlight its segments in the map view.
2. In the map view, select the element where the long trail should be split.
3. Right-click the ME in the map view.

OR
Right-click the trail in the Trails pane and select Trail Operations > Split
Trail.
4. A warning appears that the operation may be traffic-affecting. Click OK.
Depending on the volume of trails, the operation may take a few minutes.
The Progress bar indicates that processing is in progress.

5. After the processing is completed, a Confirm message appears, indicating

that the split succeeded. If you want to reload the Trail List window to
observe the result, click Yes. (Reload may be time-consuming. You can
click No to postpone reloading at this time.)
When the Trail List window is reloaded (now or later), observe that the
original trail is now listed as two trails in the Trails pane, having the same
label as the former unsplit trail but with a "Split" suffix.
You can click one of the trails in the Trails pane and observe its segment(s)
and termination points in the map view.
You can now drop low order trails traversing the long server trail in the ME
where it was split.

Increasing, Decreasing, or
Activating Data Trail Bandwidth
You can increase or decrease the bandwidth of an existing EoS or MoT trail
without having to recreate it. You can also activate the bandwidth of an
existing EoS trail, opening it to data traffic for the first time. (When a new EoS
trail is created, bandwidth activation can be postponed by not selecting the
Activate Bandwidth checkbox in the Create Trail window EoS/MoT
Configuration pane. For more information, see EoS/MoT Configuration pane).
Increasing Trail Bandwidth

This section describes how to increase the bandwidth of an EoS/MoT trail.
Increasing an MoT trail's bandwidth is disallowed if:
| The trail is protected with bypass tunnels. The bypass tunnels must be
removed first.
| The action results in additional topology links or routes being used. If
SRLG diversity increases, the operation is disallowed. (Changes to shared
bandwidth are otherwise allowed.)
NOTE: Before starting the LightSoft procedure, ensure at

the EMS level that LCAS has been enabled and the number of
allocated VCs has been increased for the relevant ports.
To increase the bandwidth of an EoS/MoT trail:

1. From the Trails pane of the Trail List window, right-click an EoS or MoT
trail and select Trail Operations > Increase. The Increase Trail
Bandwidth window opens (on top of the Trail List window) showing the
Basic Trail Parameters pane.

2. In the Basic Trail Parameters pane, select a VCAT Size multiple (greater
that the current VCAT size). The maximum allowed multiple depends on
the currently applicable Rate. (The Protection field is also enabled for
changes if needed.)
3. In the EoS/MoT Configuration pane, select the Activate Bandwidth
checkbox if you want the additional bandwidth to be available and
operational immediately. (This can be postponed to a later time.)
4. Click the Complete icon to simulate the change. If a Trail Completion

Failed error message appears:
a. Evaluate the resources on the segment - they may be insufficient for the
increase in VCAT size. To see the state of free resources in a segment,
select the segment in the Resource Tree pane and view the associated
resources in the Resource List pane. For information about adding
resources to a trail, see Select Resource Pane.
b. Evaluate the routing configuration. Consider configuring (or expanding
the configuration of) diverse routes. If diverse routing is not defined, all
resources are allocated to the same route or link (Route #1). The diverse
routing options are enabled when the Diverse Routes checkbox is
selected. For details, see EoS/MoT Configuration Pane.
c. Click the Complete icon to simulate the change again. If the

completion still fails, reevaluate the resource allocation and diverse
routing configuration.
5. Click the Activate icon to save the new settings to the database and
download the new bandwidth to the EMS. If the Trail Completion Failed
error appears, perform (or repeat) the remedial procedures listed in Step 2.
NOTE: The increased bandwidth is not operational unless it

is activated. If you did not select the Activate Bandwidth
checkbox (in Step 3), make sure to activate the new
bandwidth later; see Activating Trail Bandwidth. (If not, only
the previous bandwidth level will be operational.)

Decreasing Trail Bandwidth

This section describes how to decrease the bandwidth of an EoS trail.
NOTE: Decreasing trail bandwidth may require additional

actions at the EMS level:
Before starting the LightSoft procedure, ensure that LCAS
has been enabled for the relevant ports.
After completing the LightSoft procedure, you may wish
to decrease the number of allocated VCs for the relevant
ports.
To decrease the bandwidth of an EoS trail:

1. From the Trails pane of the Trail List window, right-click an EoS trail and
select Trail Operations > Decrease. The Decrease Trail Bandwidth
window opens (on top of the current Trail List window) showing the Basic
Trail Parameters pane.
2. In the Basic Trail Parameters pane, select a VCAT Size multiple (less
than the current VCAT size, but at least "1").
3. (Optional) Specify exactly the resources you want to decrease:
a. Select the endpoints of the trails from which you want to decrease
resources. If one endpoint is selected, the pair of endpoints is
automatically regarded as selected.
OR
b. Highlight a path in the Resource Tree pane, and select the
corresponding resources (timeslots used by the trail) to be decreased in
the Resource List pane.
OR

c. Right-click a path in the Resource Tree pane and select Decrease. The
corresponding resources are automatically selected for decrease.
There is a one-to-one relation between pairs of endpoints and resources.

When an endpoint or resource is selected, the corresponding
resource/endpoint is implicitly selected.
If no endpoints/resources are selected (or if the ones selected are not
sufficient to achieve the VCAT reduction you indicated), LightSoft
automatically decreases additional resources. If Diverse routing is used,
LightSoft balances the reduction between the paths.
If too many endpoints/resources are selected for the indicated reduction in
VCAT size, an error message appears.
4. (Optional) Click the Complete icon to simulate the change. The

endpoints and corresponding resources are reduced according to your
selections and/or completed by LightSoft. If a Trail Completion Failed
error message appears, verify that your endpoint/resource selections are
logical.
5. Click the Activate icon to activate the decreased bandwidth and save
the new settings to the database. If a Trail Completion Failed error message
appears, verify that your endpoint/resource selections are logical.
The portion of bandwidth that is decreased is automatically deactivated.
The bandwidth that is left remains activated.

Activating Trail Bandwidth

This section describes how to activate the bandwidth of an EoS trail if it is not
done when creating the trail, or when bandwidth has been increased.
Bandwidth can also be activated, if needed, in the process of reconnecting a
trail; see Reconnecting Trails. Bandwidth can be deactivated in the trail edit
process; see Editing Trails.
To activate the bandwidth of a data trail:

1. From the Trails pane of the Trail List window, highlight an EoS or MoT
trail, or select checkboxes of multiple trails.
2. Right-click and select Trail Operations > Activate Bandwidth. A
confirmation prompt appears.
3. Click Yes.
S-VLAN Registration from a Trail

S-VLAN registration at the trail level enables all services of the PB network to
utilize the virtual link represented by a trail. Adding the S-VLAN registration
to an EoS trail downloads it automatically to each existing service in the PB
network. This same action can also be implemented as part of the EoS trail
creation process by selecting the S-VLAN Registration checkbox in the
EoS/MoT Configuration Pane.
Performing S-VLAN registration at the trail level avoids having to S-VLAN
register network services individually. For information about S-VLAN
registration at the service level, see S-VLAN Registration for a Service.
To add S-VLAN registration at the trail level:

1. In Trail List window Trails pane, right-click an EoS trail and select Trail
Operations > S-VLAN Registration. A confirmation window opens.
2. Click Yes. The action is performed.

Inserting MPLS PEs to MoT Trails

The Insert PE option inserts an MPLS PE to an existing MoT trail. The
process is not traffic affecting provided the applicable tunnels are bypass tunnel
protected. The process does the following:
| Splits the MoT trail into two trails, each terminating on the inserted PE.
The old trail (for example, which traversed trail AB) is shortened (AZ),
now spanning from PE A to the inserted PE (Z) (AZ). The trail label is
the old trail label with "SplitMot_1" appended.
A new trail (ZB) is created, from PE B to the inserted PE (Z). The trail label
is the same as the old trail before the split with "SplitMot_2" appended.
Traffic is diverted to the applicable bypass tunnel (for example, AY-YB)

while the PE is inserted.
| Updates the MoT trail's tunnels to the new path (AZ-ZB). After this is
done, traffic reverts to the new main path.
| Invalidates and deletes all bypass tunnels protecting tunnels on the trail into
which the PE is inserted (AY-YB). (Any affected bypass tunnels that fail to
be deleted become irrelevant and must be deleted manually.)
For a detailed description of the actions executed by the Insert PE process, see
What Insert PE Does.
The process is subject to constraints – see the conditions described in Insert PE
Results Summary Status area.
After the process is completed, for each of the two new trails, you must
manually create new bypass tunnels and perform FRR Update, in order to
reinstate the intended tunnel protection. For example:
| For new trail AZ, the new bypass tunnel may traverse trails AY-YB-ZB.
| For new trail ZB, the new bypass tunnel may traverse trails AZ-AY-YB.
These manual procedures are described in detail within the Insert procedure;
see Insert PE Procedure.

TIP: If the replaced trail (AB) happened to be part of a

bypass tunnel protecting another unrelated trail (say YB was
protected by a bypass tunnel on AB-AY), a new bypass
tunnel on valid trails will be assigned automatically (for
example, YB would now be protected by a bypass tunnel on
ZB-AZ-AY). No further manual intervention is required.
Insert PE Procedure
NOTE: Insert PE must be performed only after the PE's

associated ME is already inserted to the corresponding
physical link (Failure to follow this sequence can yield
unexpected results.) For details about the Insert ME process,
see Inserting Elements into SDH Links.
To insert an MPLS PE to an MoT trail:

1. Ensure that the ME corresponding to the PE is inserted to the required
physical link; see Inserting Elements into SDH Links.
2. Select the ETH/MPLS topology layer.
3. On the topology map, select the PE to insert and the MoT trail where it
should be inserted. (Click Shift while selecting the two objects.)
4. On the LightSoft main menu, select Configuration > Modify > Insert PE
(enabled when a PE and MoT trail are selected).
5. The Insert PE dialog box opens; see Insert PE Window.
6. In the Ports Selection area, choose the two ports through which the
selected MoT trail will be inserted. (Click Shift while selecting the two
ports.)
Ports are enabled for selection if they are available and have granularity
compatible (not less than) the MoT trail rate. Ports that are inadequate or
not relevant to the selection are disabled.

7. (Recommended) After two ports are selected:
a. Select the Show carried tunnels to be updated icon to open the

Tunnel List window showing the tunnels traversing the MoT trail.
(The process will automatically recreate these tunnels to traverse the PE
over new trails.)
Note the number of tunnels present on the old trail that will be updated
(bottom-left corner of the window). At the end of the process you
would be able to verify that the same number of tunnels were created
on the new trails.
b. Select the Show Bypass Tunnels to Invalidate and Delete icon

to open the Tunnel List window showing underlying bypass tunnels
that will be invalidated and deleted by the Insert PE process.
Print out a listing of the bypass tunnels to be deleted, in order to be able
to manually restore them after the process is completed.
NOTE: This information will not be available in the same

form after the process is completed; see the icon description
in Insert PE Results Summary.
8. Click the Start icon (enabled after two ports are selected). The
process may take some time. It includes the automatic steps described in
What Insert PE Does. The Operation Progress pane indicates the progress.
You can use the Stop Insert PE Operation icon to stop the process
before it completes. This is not recommended, as some changes already
performed would not be rolled back and the affected tunnels would have to
be corrected manually.

9. When process is completed, the Insert PE Results window opens

displaying summary results; see Insert PE Results Summary.
Failure messages may appear in the Status area; see Insert PE Results
Summary.
NOTE: The window icons assume different meanings after

activation:
shows the tunnels that were updated.
shows the bypass tunnels that failed to delete.

For more information, see the icon descriptions in Insert PE
Results Summary.
10. Close the Insert PE window.

11. The Insert PE process automatically invalidated/removed all bypass tunnels
that protected tunnels on the MoT trail where the PE was inserted.
On each of the two new MoT trails, create new bypass tunnels manually to
reinstate link or node protection according to your network configuration.
Refer to the details you noted in Step 7. For information about tunnel and
bypass tunnel creation, see Provisioning MPLS Tunnels.
12. Tunnels on the two new trails (formerly Fully or Node protected) now have
Protection Actual: Partially protected or Unprotected. Update the tunnel
protection as follows:
a. Select the two new MoT trails in the ETH/MPLS Map view.
b. Right-click and select Show Tunnels > All Tunnels. The Tunnel List
window opens with the tunnels on these MoT trails.
c. Select the checkboxes of all the tunnels whose protection needs to be
updated.
d. Right-click and select Edit > Protection > Update FRR Protection.

Insert PE Window
The Insert PE window is used to insert a PE into a selected MoT trail, as
described in Insert PE Procedure.
Insert PE window toolbar icons

Start Insert PE Starts the Insert PE process. Enabled when two
Operation endpoints are selected.
Stop Insert PE Stops the Insert PE process. Not recommended, as some
Operation changes already performed are not rolled back and
affected tunnels would have to be corrected manually.
Show Carried Opens the Tunnel List window showing the underlying
Tunnels to be tunnels traversing the MoT trail. The Insert PE process
Updated automatically creates these tunnels again to traverse the
inserted PE. This option assumes a different meaning
after the process completes; see Insert PE Results
Summary.
Show Bypass Opens the Tunnel List window showing the underlying
Tunnels to bypass tunnels that would be invalidated and deleted by
Invalidate and the Insert PE process. After the process finishes, the user
Delete must create new bypass tunnels manually.
This option assumes a different meaning after the
process completes; see Insert PE Results Summary.

Insert PE window fields
Field Description
PE Name of PE to be inserted.
MoT trail MoT trail where PE will be inserted.
Ports Ports of the selected MoT trail into which the selected PE will be
inserted. Indicated only after two MoT ports are selected.
Insert PE Results Summary

At the conclusion of the Insert PE process, the Insert PE window includes a
Results Summary pane where the process results are displayed.
Results Summary toolbar icons
Icon Icon Name Description

Show Updated Opens the Tunnel List window showing the
Carried Tunnels underlying tunnels that were updated.
(The icon has a different meaning before and after
activation. Before activation, this icon shows the
underlying tunnels to be updated by the process.)
Show Bypass Opens the Tunnel List window showing the bypass
Tunnels not tunnels that failed to be deleted completely from
Deleted network. (Enabled only if some bypass tunnels were
not deleted.)
(The icon has a different meaning before and after
activation. Before activation, the icon shows the
bypass tunnels to be deleted by the process.)

Status area
This area contains information about process failures.
| Validation/Pre-config: Shows operation failure reasons as follows:
Validation failed due to:
Selected PE being an endpoint of the MoT trail: The PE must not
already be part of the MoT trail to which it should be inserted.
Inconsistent MoT trail state: The process is not allowed if the trail
state is not OK.
Selected PE and MoT trail belong to different MPLS networks: The
PE and MoT trail cannot belong to MPLS networks with different
MPLS IDs.
MoT trail main path not traversing the ME: The ME must be on the
main path of the protected trail, and not on the protected path.
Diverse routed MoT trail with route not traversing the ME: All the
routes of the trail must traverse the ME to which the PE belongs.
Operation terminated due to:
Failure to remove protection from MoT trail: The Insert PE process
failed to remove bypass tunnels.
Failure to force FRR switching on MoT trail endpoints: The Insert
PE process failed to switch the working path of the tunnel to the
bypass tunnel in preparation for deleting the original tunnel.
Before deleting the bypass it goes to FRR switch, can do insert to
PE, then switches FRR back.
Internal error: For example, a loss of connection occurred.
Failure to update database: Some tunnels traversing the MoT trail
failed to update.
| DB Update: Result of the automatic update to the LightSoft database,
described in Step 3 of What Insert PE Does. Values are OK, Failed, or Not
Applicable (if the process was not performed).
| Download to network: Result of the automatic download to EMS process,
described in Step 4 of What Insert PE Does. Values are OK, Failed, or Not
Applicable (if the process was not performed).

Details area
| Invalidated Tunnels:
Total bypass tunnels invalidated by LightSoft: Verify that this
corresponds to the number noted in the Insert PE procedure at Step 7 b.
Total bypass tunnels deleted successfully from the network.
Total bypass tunnels failed to be deleted from the network: To view
details, click the Show Bypass Tunnels not Deleted icon.
| Updated Tunnels:
Total tunnels downloaded successfully: To view details, click the Show
Updated Carried Tunnels icon.
What Insert PE Does

The Insert PE process executes the following detailed actions.
1. Validation of preconditions:
Selected PE must have two configured free ports, each with matching
VC-n granularity and same/larger number of VCs as the selected MoT
trail.
Selected trail must have its endpoint in the selected PE.
Main path of physical link traverses the ME to which the PE belongs.
MoT trail and PE belong to the same MPLS network.
MoT trail path traverses the inserted PE.
If the MoT trail is diverse routed, all of the routes traverse the ME to
which the PE belongs.
MoT trail state is consistent (OK or Incomplete); see Trail State in
Trails Pane Columns.
2. Automatic pre-configuration actions:
If Protection Desired: Current Protection applies to the MoT trail:
Force FRR Switch is applied on both MoT trail endpoints.
The protection path is removed – the trail becomes Protection
Actual: Unprotected or Partially Protected at LightSoft and EMS
(even if the operation should fail at a subsequent step).
If Underlying protection applies, no action is performed.
Failure of this step prevents the Insert PE from proceeding.
The actions cannot be roll backed, even if any subsequent steps fail.

3. Updates performed on the LightSoft database (description refers to diagram

in Inserting MPLS PEs to MoT Trails):
Old MoT trail (traversing from A to B): Endpoint at B is released and a
new endpoint defined on the PE to be inserted (Z). The trail now
extends from A to Z.
New MoT trail created (traversing from Z to B) with:
One endpoint on the PE to be inserted (Z), second on the released
endpoint (B).
Trail label set automatically with the default value.
Affected bypass tunnels are deleted:
Paths of tunnels of the MoT trail are updated with new expected cross
connects on the inserted PE.
This step must be fully successful for Insert PE to proceed. Full rollback
applies to any intermediate failure. If successful, all relevant objects in the
LightSoft database are updated and have appropriate inconsistency state.
4. Downloads of relevant parameters to the EMS are performed. This step
involves multiple operations, since XC downloads are executed separately
for each trail/tunnel. Failure on an individual object does not cause the
whole operation to fail.
Steps 3 and 4 may take some time. A progress indicator shows the operation
progress. A Stop option is available to abort the operation if needed.
Data regarding the whole operation is accumulated in a Results Summary
window. Intermediate results are indicated if a failure occurs. For more
information, see Insert PE Results Summary.

Removing MPLS PEs from MoT

Trails
The Remove PE function automatically removes a selected PE from the paths
of two adjacent MoT trails, and merges those paths into one trail. As a result:
| Transit tunnels (working or bypass) and P2MP subtunnels traversing the
selected links have their transit MPLS XC removed from the selected PE.
| Terminated (Head/Tail) tunnels(working or bypass) and P2MP subtunnels
traversing the selected links are deleted.
When the adjacent links are multilinks, the procedure must be performed for
one link pair at a time.
After the process is completed, bypass tunnels must be manually applied to the
newly created tunnels.
The following additional actions may be required after Remove PE is
performed:
| If the process finishes successfully, but errors are observed, the
incompletely processed entities must be corrected manually; see Process
Finished Successfully But With Some Errors.
| If the process fails or is stopped before completion, according to the step at
which the process halted, the process must either be completed manually or
network-affecting process steps that were already executed may need to be
rolled back manually; see Manual Roll Back or Continue Upon Failure.
| If manual roll back is performed, then, the preexisting condition in the
topology that caused the failure must be resolved in order for Remove PE
to succeed if tried again; see Reconstructing the Topology.
NOTE:
Remove PE is a traffic-affecting operation. Working transit
tunnels also undergo Remove PE and experience traffic losses
during the procedure. Services are disconnected from tunnels
traversing the selected links and terminating at the selected
PE. Remove PE is minimally traffic affecting to node
protected tunnels.
Shared BW along network does not have to be updated.

Remove PE Procedure
The Remove PE function is enabled when a PE and two adjacent links are
selected in the map view, where:
| The selected links have endpoints in the selected PE.
| The far endpoint of each selected link must belong to different PEs.
The Remove PE process is subject to the following constraints:
| The selected PE and links must not be state Inconsistent.
| The selected links must have:
Endpoints on the selected PE are both unprotected or both protected.
Matching VCn granularity and total number of VCs (VCAT size).
No LCAS diverse routes, or all the routes have identical capacities
(e.g., 3-2-2 VC4s for both links).
Both link ends residing in the same MPLS network.
| All transit tunnels and subtunnels must switch between the selected links
(meaning, no transit tunnel switches to an unselected link).
The process will not complete if a constraint is not satisfied.
To remove a PE from a link:

1. Select the ETH/MPLS topology layer.
2. On the topology map, select:
PE to remove and
Two adjacent links from which the PE will be removed. (When the
selected link is a multilink, the operation will be performed for one
component link at a time.)
Click Shift while selecting the three objects.
3. On the LightSoft main menu, select Configuration > Modify > Remove
PE (enabled when a PE and two MoT links are selected).

4. If one or both of the required links is part of a multilink, the Select Link
dialog box opens, listing the links in each multilink.
(If no multilink is involved, the Remove PE window opens; continue to the
next step.)
a. Select one specific link on each side of the PE that should be removed.
NOTES:
If one adjacent side has only one link, that link is selected
automatically. You must select only the other-side link.
If both adjacent sides are multilinks, select one link from each
adjacent side. (If more than one link pair needs to be removed
from the PE, the entire procedure must be repeated for each
link pair.)
b. Click Select and Continue to Remove PE.

5. The Remove PE window opens; see Remove PE Window.
6. (Recommended) Print out traffic List windows with details about entities
that will be changed by Remove PE:
Show Transit Tunnels to Update shows tunnels traversing this

path that will be updated.
Show Tunnels to Delete shows tunnels that will be deleted.
Show Traffic-Affected Transit Tunnels shows working transit

tunnels that will temporarily go down.

Show Services to Disconnect shows services that will be

permanently disconnected.
For more details, see the icon descriptions in Remove PE Window.
NOTE: It is strongly recommended to print out and reserve

these reports showing the pre-operation topology state. This
information will not be available after Remove PE is started.
In the event of a failure, certain process steps are not rolled
back automatically and it is the user’s responsibility to do so
as needed (see Manual Roll Back or Continue Upon Failure).
These reports will assist knowing what specific entities need
to be reinstated manually. The reports available after the
process completes (or is halted) will reflect the post-
processing state; see the icon descriptions in Remove PE
Results Window.
7. Click the Start icon . A warning message opens that the operation is
traffic affecting.
8. Click Yes. The process begins and may take some time. Progress text and
indicators appear in the window.
The Progress panel shows the specific process step being performed. An
error message appears if a validation is not satisfied; see the conditions
listed at the top of this section. Upon a Stop action or a fatal failure, the
currently displayed process step is halted and Remove PE terminates.

NOTE:
The Stop Remove PE Operation icon can be used to

stop the process before it completes. A message appears
warning that stopping Remove PE may cause reversible
topology changes. Click Yes to continue.
Stop should be used only in rare cases, for example, if it
becomes apparent that a fault is causing the process not to end.
If the process is stopped in this way (or is otherwise halted due
to a failure), already executed network-affecting process steps
are not rolled back and must be reverted manually. For details
about the required manual roll back or continue steps, see
Manual Roll Back or Continue Upon Failure.
9. At the conclusion of the processing, the Remove PE Results window

opens showing the summary process results. For the full window example,
see Remove PE Results Window.

A popup window will accompany the Remove PE Results window:

a. When the process completes successfully or did not encounter fatal
errors, a successful completion message is displayed. Click OK to
continue.
This message denotes that the PE was removed and the link
reconstructed between the two adjacent PEs.
However Remove PE Results window Status and Details areas may
show that some entities did not process completely. In this case, you
must identify the entities that failed to process and perform manual
actions on them; see Process Finished Successfully But With Some
Errors.
OR
b. If the operation failed, or was stopped by the user, a message to that
effect is displayed. Click OK to continue.
In this case the process did not complete. Depending on the stage
the processing reached, some network-affecting actions may
already have been performed which are not automatically reverted.
Then the process must either be rolled back or continued manually
to completion. For details, see Manual Roll Back or Continue Upon
Failure.
AND
If manual rollback actions are performed (rather than complete
actions) the preexisting conditions in the topology that caused the
failure must then be resolved so that Remove PE will succeed if
tried again. For details, see Reconstructing the Topology.
10. Close the Remove PE and Remove PE Results windows.
11. If the process completed successfully (as described in Step 9.a), bypass
tunnel protection must be manually reapplied to the newly updated tunnels:
Create new bypass tunnels if required; see Creating a Tunnel.
Apply bypass tunnel protection to the newly updated tunnels; see
Updating FRR Protection.

Remove PE Window
The Remove PE window shows the selected PE and the selected links from which
the PE will be removed.
Remove PE window toolbar

Start Starts the Remove PE process.
Stop Stops the Remove PE process. It is used in rare cases,

for example, if it becomes apparent that a fault occurred
that is causing the process not to end.
Note: This option should be used with caution, as
network-affecting changes already performed are not
rolled back. Affected tunnels and services must be
reverted manually. For more information, see Manual
Roll Back or Continue Upon Failure.
Show Transit Opens the Tunnel List window showing tunnels
Tunnels to Update traversing this path that will be updated by Remove PE.
Show Tunnels to Opens the Tunnel List window showing tunnels that
Delete will be deleted by Remove PE.
Show Traffic- Opens the Tunnel List window showing working
Affected Transit transit tunnels that will temporarily go down during
Tunnels Remove PE.
Show Services to Opens the Service List window showing services that
Disconnect will be permanently disconnected by Remove PE.
Remove PE window information fields
Field Description
PE PE to be removed from the selected links.
MoT trail 1 Trail Label and Trail ID of the trail to be disconnected

from one side of the PE. (The virtual link contains one
MoT trail.)
MoT trail 2 Trail Label and Trail ID of the trail to be disconnected
from the other side of the PE.

Remove PE Results Window

The Remove PE Results window displays the operation results. In the event of
a failure, the Status section shows which categories of processing actions were
involved. Only Download to Network failures require manual roll back actions
before Remove PE can be attempted again. The Details area shows the number
of each entity for which network processing failed. The specific entities that
were affected can be deduced by comparing pre- and post-process list window
printouts.
All failure types require resolving the underlying cause of the failure before in
order for Remove PE to be successful when it is attempted again.
Remove PE Results toolbar

Show Updated Opens the Tunnel List window showing tunnels traversing
Tunnels this path that were updated by Remove PE.
Show Tunnels Opens the Tunnel List window showing tunnels that failed to
not Deleted delete completely from the network in the following cases:
| The tunnels are not in the DB and are not admittable.
| The tunnels have FRR Type = Undefined in the DB and
are not admitable or imposable.


In both cases, the tunnels should be manually deleted from
the network.
Show Non- Opens the Service List window showing services that
Conformant became non-conformant due to Remove PE.
Services These services may be corrected through manual editing or
reconnection; see Reconnecting Services.
Show Non- Opens the Tunnels List window showing the transit tunnels
Conformant or subtunnels that failed to be switched between the selected
Transit links. This icon is available only if transit tunnels failed
Tunnels validation.
Remove PE Results window information fields
Field Description
Operation PE and MoT trail details, repeated from Remove PE window, see
Parameters Remove PE Window.
Status Shows the state of categories of Remove PE processing:
| Validation/Pre-config: Validations are performed before the
process start to ensure that Remove PE will not fail for feasibility
reasons.
Messages are OK or Failed (usually with a reason to assist
troubleshooting).
| DB Update: Indicates if LightSoft database updates were performed
successfully.
Messages are OK, Failed (usually with a reason), or Not Applicable (if
Validation/Pre-config could not be completed).
| Download to network: Indicates if network updates were
performed successfully.
Messages are OK, Failed (usually with a reason), or Not
Applicable (if DB Update could not be completed).
Details Shows the number of tunnels and services successfully or
unsuccessfully dealt with by the Remove PE process.
If the Remove PE process finished successfully, but failures are
observed in some Details area categories, entities will need to me
corrected manually; see Process Finished Successfully But With Some
Errors.
If the process failed or was stopped before completion, manual rollback
or completion actions will be required; see Manual Roll Back or
Continue Upon Failure.

Process Finished Successfully But With

Some Errors
If the Remove PE process finished successfully, but some failures are observed
in Details area categories, you should identify the entities on which the
processing failed and perform remedial actions on them, as follows:
| Disconnected services that failed to disconnect:
Click Show Non-Conformant Services to list the services that

became non-conformant due to Remove PE.
Reconnect the services; see Reconnecting Services.
| Invalidated bypass tunnels that failed to delete from the network:
Click Show Tunnels not Deleted to list tunnels that failed to

delete completely from the network.
Delete the invalid bypass tunnels; see Deleting Tunnels.
Create new bypass tunnels in their place; see Creating a Tunnel.
Update FRR protection on working tunnels that lost their protecting
bypass tunnels when the latter were invalidated; see Updating FRR
Protection.
| Deleted terminated tunnels that failed to be deleted from the network:
Click Show Tunnels not Deleted to list tunnels that failed to

delete completely from the network.
Delete the terminated tunnels; see Deleting Tunnels.
Create new tunnels in their place; see Creating a Tunnel.
Update FRR protection on working tunnels that lost their protecting
bypass tunnels when the latter were invalidated; see Updating FRR
Protection.
| Updated transit tunnels that failed to download:
Click Show Updated Tunnels to list tunnels traversing this path

that were updated by Remove PE.
Compare this with the list of tunnels to be updated (that you generated
at Step 6 using Show Transit Tunnels to Update ).
For the tunnels identified as not updated, impose the tunnels from
LightSoft to the EMS; see Performing Tunnel Synchronization.
Click Show Non-Conformant Transit Tunnels to list the transit

tunnels or subtunnels that failed to be switched between the selected
links.

Release FRR protection by either:

Making the tunnel unprotected; see Make Unprotected in
Modifying Tunnel Protection,
OR
Leaving the tunnel’s desired protection as Protected but remove
bypass assignments to it; see Remove FRR Protection in Modifying
Tunnel Protection.
Reconnect the services; see Reconnecting Services.
Impose the tunnels from LightSoft to the EMS; see Performing Tunnel
Synchronization.
NOTE: If the process failed or was stopped before

completion, manual rollback or completion actions will be
required. The above instructions should be performed in the
context of the actions described in Manual Roll Back or
Continue Upon Failure.
Manual Roll Back or Continue Upon Failure

The Remove PE operation changes the LightSoft database and the network. In
the event of a failure or manual Stop action while Remove PE is in progress,
any network-affecting process steps that were already executed must be
cumulatively rolled back manually. For example, tunnels that were removed or
services disconnected by Remove PE must be annually recreated or reactivated.
(LightSoft DB-affecting process steps are rolled back automatically and do not
require user intervention.)
The Remove PE window progress bar displays the specific process step
currently being performed during the Remove PE process. According to the
step at which the process failed or was stopped, the network-affected steps
must either be rolled back manually or the process completed manually; see
Manual Roll Back or Continue Requirements.
Reconstructing the Topology

After manually rolling back changes following a failed process, the preexisting
condition in the topology that caused the failure must be resolved in order for
Remove PE to succeed if tried again.
The cause of the failure can be deduced from the progress bar message of the
process step in progress when the failure occurred, as well as the Results
window Status messages and Detail statistics. Routine remedial actions should
be applied.

Manual Roll Back or Continue Requirements

The table below shows the Remove PE process steps and the manual rollback
or continue actions that should be performed in the event of a failure or Stop
action at any given step.
| Number column: Indicates the order in which a process step is performed.
| Process Step and Description columns: Show the action performed by
Remove PE in a step. The description also shows the required manual
actions that must be performed if the process fails/stops:
Manual rollback if the process stopped during Steps 2 to 9.
This thereby reverts all Remove processing already.
Manual completion if the process stopped during Step 10 or later.
| Affected Location column: Shows the entity affected by a step (Network,
LightSoft DB, or GUI).
Process steps and manual roll back requirements
# Process Remove PE action and corresponding Affected

Step Manual Rollback / Continue actions upon Location
failure or Stop at each step
1. Select User selects PE to remove, pair of links to merge. GUI
2. Validate Verifies that prerequisites are met. DB
3. Force FRR Forces FRR switching on far-end endpoints of the Network
selected links. Only applicable with Node
protection.
Manual roll back action required:
| Making the tunnel unprotected; see Make
Unprotected in Modifying Tunnel Protection,
OR
| Leaving the tunnel’s desired protection as
Protected but remove bypass assignments to
it; see Remove FRR Protection in Modifying
Tunnel Protection.
4. Disconnect Disconnects services from Head or Tail tunnels. Network
Services Manual roll back actions required:
| Reconnect the services; see Reconnecting
Services.
| Also perform Step 3 manual rollback action.
5. Delete Deletes transit MPLS XCs at the selected PE. Network

Transit Manual roll back action required:
MPLS XCs | Impose the tunnels from LightSoft to the
EMS; see Performing Tunnel
Synchronization.
| Also perform Step 3-4 manual rollback
actions.


6. Delete Deletes the head-tail tunnels. Network
Terminated Manual roll back actions required:
Tunnels | Impose the tunnels from LightSoft to the
EMS (as in Step 5); see Performing Tunnel
Synchronization.
| Also perform Step 3-4 manual rollback
actions.
7. Invalidate Invalidates the node-protecting bypass tunnels DB
Bypass (FRR Type becomes Undefined).
Tunnels Manual roll back actions required:
| Perform Step 3-6 manual rollback actions.
8. Merge Links Deletes endpoints of the selected links at the DB

selected PE.
Creates an endpoint for the merged link at the
ME of the selected PE.
Updates SRLG list for the link as the union of the
SRLG lists of the selected links.
Assigns the merged link with auto TE metric.
Manual roll back actions required:
9. Update Deletes MPLS XC from selected PE. DB

Transit Repeats for all other transit tunnels.
Tunnels Manual roll back actions required:
10. Delete Deletes the invalidated Bypass tunnels. Network

Invalid Manual continue actions required:
Bypass | Delete the invalid bypass tunnels; see
Tunnels Deleting Tunnels.
| Create new bypass tunnels in their place; see
Creating a Tunnel.
| Update FRR protection on working tunnels
that lost their protecting bypass tunnels when
the latter were invalidated; see Updating FRR
Protection.
| Also perform Steps 11-12 continue actions.
11. Impose Link Imposes the merged link. Network

Manual continue actions required:
| Impose the merged link; see Performing Trail
Synchronization.
| Also perform Step 12 continue action.


12. Release Releases FRR switching at the merged link Network
FRR endpoints.
Manual continue action required:
| Making the tunnel unprotected; see Make
Unprotected in Modifying Tunnel Protection,
OR
| Leaving the tunnel’s desired protection as
Protected but remove bypass assignments to
it; see Remove FRR Protection in Modifying
Tunnel Protection.
13. Results Provides results summary. GUI
Summary

Redefining an ASON Trail’s

Provisioned Path
After an ASON trail is activated, while LightSoft manages the network, the
trail is monitored by ASON. If a failure occurs on any fiber/link that the
provisioned path traverses (for example a fiber cut), a new trail path is
automatically found by the ASON control plane and ASON automatically
reroutes the traffic to the new trail’s path, restoring the trails that traverse the
fiber. After the fiber cut is repaired, the trail automatically reverts to the
initially provisioned trail path. For more information, see ASON Trail
Provisioning Notes.
The originally provisioned path can be changed to specify the ASON-found main
path as the new provisioned path, if needed. Redefining the provisioned path may
reflect a decision not to immediately repair the originally provisioned path and to
release its resources for other purposes.
NOTE: ASON Maintenance Operations Reroute functions

are not useful for this purpose as they do not change the path
state. They perform a controlled reroute, temporarily rerouting
a trail that is to undergo repair/testing. The reroute happens in
the same way as reroute upon failure, but is performed
manually. For more information, see ASON Maintenance
Operations.
To change an ASON trail’s provisioned path:

| Admit the trail through TCI acquisition. The path and XCs are accepted and
activated by TCI in the same way as for SDH trails, but based on control
plane provisioning; see Synchronizing Trails.
| Modify the trail path to the desired route using the Edit Trail window; see
Editing Trails.
The redefinition is reflected in the LightSoft database and ASON is informed
of the change in the trail’s LightSoft-provisioned path. The trail will not revert
back to the old provisioned path after failure is repaired. (It remains part of the
ASON domain and can be used as a protection path if available.)

Batch Trail Operations

This section describes how to perform Create, Edit, and Delete trail operations
in a batch by exporting and importing trail definitions to/from an XML file:
| The Export operation enables you to save the data of selected trails into an
XML file for either network planning or backup purposes.
| The Import operation translates the data stored in the XML file and sends
this information to LightSoft according to the requested operation for each
trail in the file.
Records in the XML file specify the commands and parameters of actions. For
information about the XML syntax, see Import/Export Traffic Syntax.
LightSoft automatically generates a log file documenting the import or export
process. You can find this log file in the ~nms/NMSTrails directory. The log
file name is the same as the XML file, with the .log extension.
A Document Type Declaration (DTD) file defines the rules by which the XML
file is structured, the applicable keywords, and how to parse the file. If
required, the names of the tags in the DTD file can be changed (for additional
information, contact ECI Telecom customer support).
OPTIONAL FEATURE: XML trail operations are fully

integrated add-on capabilities, available on a cost basis. If not
purchased, menu options pertaining to exporting and
importing trail definitions are unavailable.
Exporting Trails
This section describes how to export trail definitions to an XML file for
network contingency planning and design or backup purposes.
Exported trails are automatically implemented in the network by the Import
function according to the settings that were used to export them to XML.
You can export trails either to a new XML export files or accumulate (append)
them at the end of an existing XML export file.
Trail definitions either from the Trail List window or in XML file format can
be converted to CSV for viewing in a relational database program. For details,
see Exporting Trails to CSV.

Exporting for network planning purposes

Exporting trails to XML for network planning purposes is performed in
conjunction with the creation of "planned" new trails, changes to trails, or
removal of trails:
| Planned new trails are created using the Plan Trail window, where an
individual new trail can be fully provisioned even while its prospective
resources are currently occupied - they must be freed only when the new
trail is actually implemented; see Planned Trails.
Trails for future use can also be created singly or in bundles using the
Create Trail window, by exporting after Complete (before the Activate
step). However, in this case, the resources selected for the trails must be
currently unoccupied; see Creating SDH and EoS/MoT Trails.
In both these cases, in the process of exporting the trails to XML, you will
use the Export Trails window's Export for Create mode.
| Planned changes to an existing trail are created using the Edit Trail
window; see Editing Trails. For this purpose the trails are exported to XML
using the Export Trails window's Export for Edit mode.
| Planned removal of existing trails is performed using the Trail List
window; see Deleting Trails. For this purpose the trails are exported to
XML using the Export Trails window's Export for Delete mode.
In each case, the planned entities do not immediately affect the working
network. They are exported to XML until they are needed. When the new
network design is ready to be implemented, the planned trails may be imported
to LightSoft as part of the active network.
Exporting for backup purposes

You can export trails so that they can be restored later though an import if
inadvertently deleted or corrupted. For this purpose the original trail must have
been previously exported - selected from the Trail List or Edit Trail window,
and an export file created using the Export Trails window using the correct
export mode:
| To restore a trail that was deleted from the network, the original export file
needs to have been prepared using the Export for Create mode.
| To restore an existing trail that become corrupted, the original export file
needs to have been prepared using the Export for Edit mode.

Export Trails Procedure

The Export functionality differs according to the trail window from which it is
requested and the selected Export For option in the Export Trails window.
NOTES:
XML records are exported in the order that they are displayed
in the Trail List window, and are eventually imported
serially, in the same order.
It is therefore important that the records be sorted prior to
export in the right order for the intended import action since,
records for which a prerequisite action was not performed
will not be imported. For example, when importing for
Create, if a low order trail record is encountered before its
high order trail, the low order trail is not created, even if the
high order record appears later in the file.
In order to avoid this problem, before exporting, be sure to
sort the Trail List window records by rate, as follows:
If the XML file will be used for Create, sort all high order
trails to appear first before the low order trails.
If the XML file will be used for Delete, sort the low order
trails to appear first before the high order trails.
You can also export separate files for low order and high
order trails. Then make sure to import the high order trail file
first when creating trails and the low order trail file first when
deleting them.
To export trails to XML:

1. If you are exporting trails for backup purposes:
From the Trail List window, select one or more trails; see Performing
Trail Operations.
OR
From the Edit Trail window, select a trail (and optionally edit it, but do
not activate the changes); see Editing Trails.
OR
2. If you are exporting trails for network planning purposes:
Creating a trail: From the Create Planned Trail or Create Trail
window, complete (but do not activate) a new trail; see Creating a
Planned Trail or Creating SDH and EoS/MoT Trails.
OR
Editing a trail: From the Edit Trail window, edit a trail and complete
(but do not activate) it; see Editing Trails.

OR
Deleting trails: From the Trail List window, select one or more trails
that should be deleted (but do not click Delete); see Deleting Trails.
Ensure the trails are sorted according to the intended action - Create or
Delete - see the previous note.
3. Click the Export icon on the window toolbar.

OR
menu. The Export Trails dialog box opens.
4. Type a file name or select an existing one from the dropdown list.
NOTE: The following characters (separated by commas) are

not allowed in the file name:
*, ?, !, |, \, /, ', ", {, },<, >, ;, <comma>, ^, (, ), $, ~, #, @,
<space>, +, =, &
5. If the file already exists, the Append checkbox is enabled:

Select the checkbox to add the selected trails at the end of the existing
file (preserving its previous contents).
OR
Leave the checkbox unselected to overwrite the existing file.
6. Select the appropriate Export As option:
If the window was opened from the Create Trail or Plan Trail
window, the Export for Create option is automatically applied.
If the window was opened from the Trail List or Edit Trail window,
select:
Edit if the export is for network planning purposes (they include
changes to be applied later) or will serve as backup in case the
existing trails must be replaced (for example, because of a needed
routing change).
Create if the export is for backup purposes (in case the existing
trails that are deleted need to be restored).
Delete if the trails being exported are slated for deletion from the
network at a future time.

7. Click Export. The trail definitions are saved as an XML file.

Clicking Abort at any time causes the operation to stop after the current
trail is processed. An Exporting Failed message opens. An export file will
be produced containing definitions of the trails that completed processing
up to that point.
Export Trails to CSV

LightSoft provides an application that allows you to export Trail List window
data to a delimited-format CSV file for subsequent import to Microsoft Excel
or a relational database application. LightSoft also enables you to export trails
in XML files to CSV using a command line application.
To export trails to CSV:

| See the generic procedures in Exporting to CSV.
To export XML data to CSV:

| See the generic procedure in Exporting XML Data to CSV.

Importing Trails
This section describes trail definition import from XML using LightSoft menu
options. (You can also import trail XML files via UNIX; see
Exporting/Importing Traffic Entities via UNIX.)
NOTES:
Before importing trails, ensure that all the required
endpoints and resources are free and available. If any are
occupied, the Complete action, which is performed
automatically by the import, will fail.
The records to be imported must be in the right order for
the intended action, since records for which a prerequisite
action was not performed will not be acted upon. For
details, see the note in Exporting Trails.
To import trail definitions from XML files via LightSoft:

1. On the LightSoft main menu bar, select Trail > Import Trails.
OR
On the main toolbar, select Import Trails . The Import Trails dialog
box opens.
2. In the Files pane, select the file you want to import.

3. Select one of the following options, according to the required action:

Check Syntax: Checks the XML file structure validity for trail import..
Complete: Checks syntax and finds a path for the trails (like Complete
in the Create Trail procedure).
Activate/Delete: Checks syntax, finds a path, and activates the trail in
the network (like Activate in the Create Trail procedure). In the case of
a Delete mode XML file, checks syntax and deletes the specified trails.
4. Click Import. After the processing is completed:
If Activate/Delete was selected, the file is imported and appears as a
trail in the Trail List window (Create/Edit) or is removed (Delete).
For Activate/Delete or Complete, the Status pane shows the total
number of trails processed and the number that processed successfully
or failed.
For Check Syntax, refer to the XML log file for the operation results.
trail is processed. An Importing Failed message opens. The trails that
completed processing up to that point will be imported.
Exporting/Importing Traffic Entities via

UNIX
This section describes a simplified trail, tunnel and service definition
export/import to/from XML via UNIX.
This may include prescheduling using the UNIX crontab command.
NOTES:
The import or export external application must be run from
the server side.
The import trail, tunnel or service files must reside in the
fixed directory ~nms/NMSTrails, ~nms/NMSTunnels, and
~nms/NMSServices, respectively.
After the import command line application is run, an output
log file is created within ~nms/NMSTrails,
~nms/NMSTunnels, or ~nms/NMSServices, where the user
can check the success of the process.
The TrafficXMLUtility function described in this section
supersedes the old TrailExpImpUtility function formerly used
for trail export/import.

To export/import trail definitions from XML files via UNIX:

| You can import XML files with the SetCrontab utility. The following is an
example UNIX command line:
TrafficXMLUtility -import file_name -user user_name -passwd
user_password
The following usage and options apply:
TrafficXMLUtility [-export output_file_name]
[-import input_file_name]
[-trail] [-tunnel] [-service]
[-user user_name] [-passwd user_password]
(The minimum specification includes, besides the user name and password, one
of [-import file_name] [-export file_name] and one of [-trail] [-tunnel] [-service]).
Where:
Command Description
-export output_file_name Indicates that the requested operation is export of all trails,
tunnels, or services.
Trails, tunnels and services each have their own directory:
~nms/NMSTrails, ~nms/NMSTunnels, or
~nms/NMSServices.
-import file_name Indicates that the requested operation is import of all
trails, tunnels, or services.
-service Indicates that the operation is performed on all services.
-trail Indicates that the operation is performed on all trails.
-tunnel Indicates that the operation is performed on all tunnels.
-user user_name User name required to run this application. Must be a
defined LightSoft user.
-passwd user_password Password required to run this application. Must be a
defined password.
Examples:
| To import a service stored in the service.xml from a filename:
TrafficXMLUtility -imp filename.xml -service
| To export a tunnel to a filename in tunnel.xml:
TrafficXMLUtility -exp filename.xml -tunnel

10
Synchronizing Trails
In this chapter:
Overview ....................................................................................................... 10-1
Trail Synchronization Concepts .................................................................... 10-1
4
Performing Trail Synchronization ................................................................. 10-4

4
Trail Consistency Indicator Window ............................................................. 10-9

4
Trail Synchronization Window ................................................................... 10-14

4
Trail Consistency Indicator Use Cases ........................................................ 10-21

4
Overview
This section describes the trail synchronization process which reconciles
differences between trail definitions in LightSoft and trail definitions in an
EMS. It is also used to acquire optical trails that are defined at the EMS level.
For more information, see Trail Acquisition by Synchronization.
Trail Synchronization Concepts

Inconsistencies between the LightSoft database and EMSs can develop over
time for a number of reasons, such as:
| Trails were created in LightSoft while the EMS was down.
| Trails connecting NEs in two different sites are managed by different
EMSs. Each EMS uses an external element to connect with the other site,
but LightSoft shows this trail as a direct connection between the sites
without external elements.
| Cross connects were defined or changed at the EMS or craft terminal level.

Synchronizing Trails LightSoft User Manual
New trail inconsistencies should generally be dealt with as they occur and their
causes investigated. The number of outstanding inconsistencies in the system at
any time should be kept low. See Accessing Trail Inconsistency Information.
Synchronization can be performed either in an automated fashion for all the
trails under consideration, or manually, on a per-trail basis:
| Automatically for all selected trails using the Trail Consistency Indicator
(TCI) window. You either:
Impose (reconnect) trails from the DB (LightSoft) to the network
(EMS), or
Admit (acquire) trails from the network to the DB (causes the trails to
be acquired to LightSoft).
| Alternatively, display inconsistencies in the TCI window and then perform
synchronization manually in the Trail Synchronization window on
selected trails, deciding whether to impose, admit, or delete them. After
completing and activating the changes, you can refresh the information
displayed in the TCI window to confirm that the inconsistencies were
resolved, thereby indicating that the synchronization process was
successful.
As a general rule, SDH layer inconsistencies should always be synchronized.
However, optical layer inconsistencies may not require synchronization as they
may be caused by unused channels for which cross connects have been defined
automatically at the EMS level.
The synchronization process is used to admit trails that do not conform to
normal trail patterns (flex trails) to LightSoft's Trail Management subsystem.
Accessing Trail Inconsistency Information

Inconsistency information can be accessed using the following LightSoft main
window indication and icon:
| The Trail Consistency Indicator (TCI) counter in the main
window toolbar shows the number of inconsistencies in all trails or in SDH
trails only (clicking the counter toggles between total and SDH + EMS
counts). The color of the flag indicates the worst inconsistency condition of
the trails in the selected count. For the count behavior upon link and trail
creation, see Trail Synchronization Exceptions.
| The Trail Consistency Indicator (TCI) icon opens the TCI window,
where you can view detailed inconsistency information.
The Trail Synchronization feature is composed of the following windows:
| TCI window: Begins the trail synchronization process, providing warning
flags with colors according to the type of detected inconsistencies and
counters that add up the number of inconsistencies on each layer. See Trail
Consistency Indicator Window.

LightSoft User Manual Synchronizing Trails
| Trail Synchronization window: Performs various synchronization actions,

both directly and via several floating windows displayed with it. See Trail
Synchronization Window.
Trail Synchronization Exceptions

Trail synchronization functionality is available in accordance with user
permissions.
Trail synchronization functionality is not available for CNM users; see VPNs
and CNMs.
SDH and optical inconsistencies are treated in the following ways:
| SDH trails: Both link and SNC inconsistencies are flagged.
| Optical trails: By default, only detected link inconsistencies are flagged.
Flags are not created for SNCs as these are not generally relevant to optical
trail management. (Should flagging of optical SNCs be needed, the default
can be changed. Please contact ECI Telecom customer support for
assistance.)
The LP flag shows the aggregation of all LP link inconsistencies.
Changes to the path type in OCH trails are not included in the TCI Details
pane inconsistency counts as these trails are not protected.
When a topology link is created in LightSoft between OTN ports, a TCI
inconsistency count is generated (rises by 1).
When the created link is between ports that terminate two trail layers (OCH and
LP), the inconsistency is generated only for the LP layer (not the OCH). The
inconsistency is cleared after an optical trail is created between the ports. If the
created trail happens to be unidirectional, the counter is still reduced by 1 (as if
a bidirectional trail had been created).
Admitting a trail from the EMS to LightSoft is disallowed if:
| An MoT trail is traversed by tunnels or is protected by bypass tunnels. The
tunnels must be removed first.
| A high order VC-4 server trails has low order MoT trails.
TCI does not remove an MoT trail if it has tunnels or bypass protecting it. To
remove the MoT trail, you must manually remove the tunnels.
AoC and ROADM-related trail inconsistencies are not reflected in the TCI
window counters or listed in the window’s Selected Objects pane.

Performing Trail Synchronization

Trail synchronization can be performed for trail inconsistencies associated with
selected multilinks or objects (MEs, LEs, UMEs, groups, EMSs), links in a
multilink, or specific trails.
Automatic impose and admit actions apply only to "non-match" trails, with no
overlap/part match relations with any trail in a counterpart window:
| If a trail exists only in the network, Auto Admit causes it to be acquired to
the DB.
| If a trail exists only in the DB, Auto Impose reconnects it to the network.
If any relation exists between the trails, a manual impose or admit action is
required. Manual operations are also useful if you want to examine trails before
performing an operation. For more information about trail relations, see Color
Indications in Database and Network Trails Sequence Windows.
Since Impose (reconnect) actions are traffic-affecting, Auto-Impose is enabled
only if Monitor mode is not selected (that is, Master mode applies). (Admit
actions, which acquire trails to the DB, are not traffic-affecting and are not
limited by mode.)
NOTE: The number of network trails that can undergo

synchronization operations at one time (impose from the DB
to the network, whether automatic or manual, or delete from
the network) is limited to 64 for system performance reasons.
If more are needed, multiple cycles of the TCI process should
be performed. It is also possible to configure a different limit.
For more information, contact ECI Telecom customer
support. (LightSoft DB operations are not limited.)

Trail Synchronization Procedure

Only one LightSoft client can perform trail synchronization at any given time.
To perform trail synchronization:

1. In the LightSoft main window, select the required technology layer.
2. Open the Trail Consistency Indicator (TCI) window showing all trail
inconsistencies associated with:
a. Selected multilinks and/or objects:
Select specific multilinks and/or objects on the main window map.
OR
Do not select anything in order to display all inconsistencies for the
current layer.
On the main menu bar, select Trails > Trail Consistency.
OR
On the main toolbar, click .
OR
b. Selected links in a multilink:
Right-click a topology link and select Expand to display the
Actual Links between Two MEs dialog box.
Select the links.
Right-click the Link Name cell of any link and select Trail
Consistency.
OR
c. Specific trails:
In the Trail List window Trails pane:
Select the trails (the checkboxes) which you want to synchronize.
OR
Click the single trail (to highlight it) that you want to synchronize.
On the Trail List window toolbar, click .
OR
Right-click either the highlighted trail or one of the selected (check
marked) trails, and select Trail Operations > Trail Consistency
from the shortcut menu.
The Trail Consistency Indicator window opens; see Trail Consistency
Indicator Window.
3. Use the flags and counters in the TCI Details pane to determine which
layers have inconsistencies that need synchronization. Select the layer from
the dropdown list at the top of the Parameters pane.

4. Click Show Selected Objects to show a list of the trails; see Selected
Objects Pane. To close the pane, click .
5. In the Parameters pane, make your selections for Automatic trail
synchronization operation; see the Parameters Pane description options.
NOTE: Manual operations can be specified on a per-trail

basis at a later step.
6. To synchronize only some of the inconsistencies, select the checkboxes in

the list of trails. Otherwise, leave all checkboxes blank. You can select all
checkboxes by clicking Select All or clear all by clicking Clear All
.
7. Click Start . A confirmation dialog box opens.
8. Click Yes. The process begins. This may take several minutes. Progress
indicators appear in the right pane of the window.
NOTE:
Selecting Stop discontinues processing after the current

trail is checked, providing results for only trails processed up to
that point and enabling decision-making concerning inconsistent
trails in that group.
Selecting Abort discontinues the entire operation and no

results are provided.
When the process is completed (it may take some time), the Trail
Synchronization window opens; see Trail Synchronization Window.
9. (Optional) On the Trail Synchronization toolbar:
a. Click Monitor Mode to switch from Monitor to Master mode (the

icon changes to Master Mode , ready to switch back if required).
Use Master mode to impose trails on or delete trails from the EMS. A
warning appears that this step is traffic-affecting.
b. Click OK to confirm.

10. In the DataBase Trails Sequence and Network Trails Sequence

windows, select one or more trail checkboxes.
TIP: You can select a trail in the Database or Network
window and click on Show on Map to open a Create

Trail window in read-only mode, where the trail is
highlighted on the window map and the trail parameter values
are indicated; see the icon description in Trail
11. Select one of the following manual synchronization operations, if needed:

In the DataBase Trails Sequence window, click:
Impose selected trail to Network icon, to impose the trail on

the EMS (Master mode only).
OR
Delete selected trail from Database icon, to delete the trail

from the LightSoft database.
OR
In the Network Trails Sequence window, click:
Admit selected trails to Database icon, to admit the trail from

the EMS to LightSoft.
OR
Delete selected trails from Network icon, to delete the trail

from the EMS (Master mode only).
The selected trails are moved to the Queue window; see Queue Window.
An icon in each row indicates the synchronization option applicable to the
trail.
12. Review the list of trails and actions in the Queue window. If required,
select the checkbox next to a trail and click to return it to its original
window.

13. When you have completed the list of trails for synchronization, click
Activate . The trails in the Queue window are synchronized according
to the selected actions. When the operations are complete, an icon appears
next to each trail:
- operation successful
- operation failed
- operation already been performed

14. To clear the Queue window, select one of the following toolbar icons:
- to clear successfully synchronized trails
- to clear unsuccessfully synchronized trails
- to clear all trails

As successfully synchronized trails are cleared from the Queue window,
imposed trails are displayed in the Imposed Trails List window and
admitted trails are displayed in the Admitted Trails List window.
15. Return to the Trail Consistency Indicator window and click Reload. The
flag for the layer that was synchronized appears green and the counter is
reset to 0.

Trail Consistency Indicator

Window
The trail synchronization process begins in the Trail Consistency Indicator
window. The window displays warning flags with colors according to the type
of detected inconsistencies and counters that total the number of
inconsistencies at each layer. The color of the flag reflects the worst
inconsistency condition in that layer. For more details, see Trail Consistency
Indicator Use Cases.
Trail Consistency Indicator toolbar

Start Starts process on selected trails.
Stop Stops process. The operation continues on the trails

processed up to that point, providing results for these and
enabling decisions to be taken concerning inconsistent
trails in that group.
Abort Aborts process. The entire operation stops at once and no
Show Selected Opens Selected Trails pane that lists the trails selected
Objects when the TCI window was opened for consideration for
the Synchronization process.
Close Show Closes Selected Trails pane.
Selected Objects


Refresh Reloads the trails in the list of trails.
Select all trails Selects (checkmarks) all the trails in the currently selected
window.
Unselect all trails Clears all the trails in the currently selected window.
Close Closes the Trail Consistency Indicator window.
TCI Details Pane

The TCI Details pane displays the number and severity of inconsistencies
between the LightSoft DB and the network, and includes counters for
inconsistencies in each layer including the optical layer (OMS, OCH, and LP)
and SDH layer server and client trails.
The EMS counter shows red flags displayed in an EMS because of an
inconsistency between the EMS and the NE it manages. Any inconsistency
flagged should be resolved in the corresponding EMS.
Each layer counter has an associated flag with the following color coding:
| Red: Critical inconsistency.
| Yellow: Warning - less severe inconsistency, such as cross connects
existing in the network that are not used by the trails managed by
LightSoft.
| Green: No inconsistency.
The following are the possible indications of each flag color. For more specific
use cases applicable to each topology layer, see Trail Consistency Indicator
Use Cases.
Indications of warning flags
Color Possible indications

SDH trails
Red Any of the following:
| Inconsistency of timeslots in Subnetwork Connections (SNCs)
| Trail SNCs existing only in LightSoft
| Not all SNCs were created successfully in the EMS
| Inconsistency of termination mode of VC-4
| Red flag in EMS-SYNCOM
Yellow Any of the following:

| Mismatch of path types (main or protection)
| SNCs existing in the network/EMS but not in LightSoft, or in the
EMS but not in LightSoft


Optical trails
Red Topology links exist in the OTN layer but have no trails defined on
them.
Yellow All other cases related to SNC inconsistencies. This includes SNCs
existing only in the network.
Parameters Pane
The Parameters pane enables you to define the synchronization process. Select
the layer in which to perform synchronization from the dropdown list or click
the flag. Then select one or more of the following checkboxes:
| Auto Admit Classified: Automatically adds standard pattern network trails
not previously in the database to LightSoft.
| Auto Admit Flex: Automatically adds network trails that have a
nonstandard pattern to LightSoft.
| Auto Impose Classified: Automatically imposes to the network LightSoft-
standard pattern trails not previously in the network. Available only when
Monitor Mode is not selected.
| Auto Impose Flex: Automatically imposes to the network trails whose
pattern is not supported by LightSoft. Available only when Monitor Mode
is not selected.
| Auto Impose Trail Attributes: Automatically imposes to the network
changes to trail attributes defined in LightSoft. Available only when
Monitor Mode is not selected. These changes are considered minor and are
not traffic-affecting.
| Use Connectivity Only:
When selected, builds trails according to connectivity only. This is

generally recommended for TCI on most trails as it results in better
performance and does not require rigorous trail management.
When not selected, builds trails according to connectivity and also
merges by trail ID. This is useful when multiple cross connects share
the same trail ID and do not have connectivity with all parts of the trail.
Trails with no connectivity (for example, protected trails with no SNCP
point) as well as some optical trails/X diverse protected trails, should be
run with an acquisition process by deselecting this option.
| Monitor Mode: When selected, prevents trails from being imposed on the
network. Trails can, however, be imported (admitted) from the network
into LightSoft.

Selected Objects Pane

The Selected Objects pane of the Trail Consistency Indicator window lists
the trails that had been selected in the Trail List window when the Trail
Consistency Indicator window was opened from that window. Trails that you
now select in the Selected Objects pane will be considered by the
synchronization process. The Selected Objects pane is opened by clicking the
Show Selected Objects icon on the Trail Consistency Indicator
window toolbar. (Close the pane using the Hide Selected Objects icon .)
The full range of column information is described below. The columns

displayed can be varied as required. For more information, see Showing,
Hiding, and Auto-Fitting Columns.

Selected Objects pane of Trail Consistency Indicator window
Column Description
# Ordinal number of trail in the list.
Trail selection checkbox, used to select trails for synchronization.
Trail ID System ID for the trail, for example, "36(38)", formatted as:
| Unique ID Number – ID of the trail, sequentially assigned in the
trail creation process.
| Managed System ID – ID of the management system in which
the trail was created (EMS or LightSoft).
Description Free text description of the trail.
Object Name of the object that generated the inconsistency condition.
Severity Level of disruption that could result from the inconsistency:
| Indeterminate - Gray (initial value when inconsistencies are not
yet indicated for this layer)
| Critical - Red
| Minor - Orange
| Warning - Yellow
| Cleared - Green
Cause Probable cause of the inconsistency.

Detected At Time that the inconsistency was detected.
Comments Free text description of the trail.

Trail Synchronization Window

The operations that you can perform in the Trail Synchronization window
depend on the current mode. By default, the window opens in Monitor mode,
allowing trails to be admitted to LightSoft but preventing them from being
deleted from the network or imposed on it. This is done to prevent accidental
traffic-affecting changes to functioning trails.
Trail Synchronization window toolbar

Path:
Selects the path (route) type whose attributes will be
viewed: Main, Protection, or Both.
Tool Windows Opens a dropdown list of page arrangement options, as
well as options to hide/show specific floating windows.
Show highlighted Opens a new Create Trail window in read-only mode
trail on map where the trail that you selected in the Database or
Network window is highlighted in the window map and
the trail parameter values are indicated.


Master mode Switches from Monitor to Master mode (the icon changes
to Master Mode ready to switch back, if required).
Use Master mode to impose trails on or delete trails from
the EMS.
Impose selected Imposes the trails selected in the Database Trails
trail to Network Sequence window on the EMS (Master mode only).
Delete selected Deletes the trails selected in the Database Trails
trails from Sequence window from the LightSoft database.
Database
Admit selected Admits the trails selected in the Network Trails Sequence
trail to NMS window from the EMS to LightSoft.
Delete selected Deletes the trails selected in the Network Trails Sequence
trail from Network window from the EMS (Master mode only).
Select all trails Selects (checkmarks) all the trails in the currently selected
window.
Unselect all trails Clears all the trails in the currently selected window.
Activate Synchronizes the trails in the Queue window according to

the selected actions.
Undo trails from Removes selected trails from the Queue window to the
queue window that it came from.
Clear all ok trails Clears successfully synchronized trails from the Queue
from the queue window.
Clear all error Clears unsuccessfully synchronized trails from the Queue
trails from the window.
queue
Clear queue Clears all trails from the Queue window.

Floating Windows
The Trail Synchronization window includes floating windows used in the
synchronization procedure. These are accessed using the Tool Windows icon
. The icon opens a dropdown list of page arrangement options and other
options to hide or show specific floating windows. To display a window, select
its checkbox in the dropdown list.
Information about listed trails shown in the floating windows (except the
Events List window) is described in the following table.
Trail Synchronization floating window columns
Column Description
Trail selection checkbox for selecting trails for some operations
(described in context). Other trail operations apply only to
highlighted trails. A highlighted trail is the focus for information
shown in the Trail List window panes.
NMS ID Trail identifier.
Trail ID System ID for the trail, for example, 36(38), formatted as:
| Unique ID Number – ID of the trail, sequentially assigned in the
trail creation process.
| Managed System ID – ID of the management system in which
the trail was created (an EMS or LightSoft).
Label User-defined label for the trail.
Customer Customer associated with the trail.
Type | P2P - standard point-to-point trail with full connectivity between
endpoints.
| X - "X" pattern trail, involving four endpoints.
| Y - "Y" pattern trail, involving three endpoints.
| DR - diverse routes.
| Flex - multiple cross connects that do not constitute a valid trail
due to the lack of full connectivity between endpoints.

Database and Network Trails Sequence

Windows
Two windows contain information about inconsistencies:
| The DataBase Trails Sequence window (DB window) displays trails
found in the LightSoft database. The network may have similar or
overlapping trails.
| The Network Trails Sequence window (Network window) displays trails

found in the network. LightSoft may have similar or overlapping trails.
In general, when a trail exists in one window but not in the other:
| If the network trail is missing, the DB trail should be imposed.
| If the DB trail is missing, the network trail should be admitted.
In these cases, automatic impose and admit operations are possible; see
Performing Trail Synchronization.
If a trail is present in both the network and the DB, and the trails are not exactly
equivalent (see Color Indications in Database and Network Trails Sequence
Windows), they must be synchronized through manual impose and admit
actions.

Color Indications in Database and Network Trails

Sequence Windows
Trails in the DB window may have counterparts in the network window which
are exactly matching, partially matching, or overlapping. When you select a
trail in one window (DB or network), the corresponding trail in the other
window is highlighted with a color that indicates the relation between the trails.
Different treatment is required according to the condition implied by the color.
| Green: The trails are exactly equivalent, exactly matching in all their cross
connects and no synchronization action is needed.
| Yellow: The DB trail has more XCs than the network trail ("Part match"
relation) and should be imposed on the network. (The XCs that are
common to the trail in DB and network are otherwise exactly matching,
with the same port configurations.)
The example in Database and Network Trails Sequence windows show a
selected DB trail and the corresponding network trail with a yellow
indication, suggesting that the DB trail should be imposed.
NOTE: When XCs of a network trail are missing from one

NE and not the other, the trail must be imposed manually. (In
this case the Automatic Impose action will not impose the
trail.)
| Blue: Some XCs common to the trail at both network and DB are
configured differently ("Overlap" relation), for example, having different
ports. The number XCs in each trail is not relevant. Blue may also mean
the DB trail has less XCs than the network trail.
In this case, the user must investigate further to determine which version of
the trail is preferred (for example, whether one trail is classified), and to
impose admit, accordingly.

Queue Window
The Queue window is used for the synchronization process itself. It displays
the trails selected in the DataBase Trails Sequence and Network Trails
Sequence windows which you want to synchronize.
Imposed and Admitted Trails List Windows

The Imposed Trail List and Admitted Trails List windows contain
information about the results of trail synchronization.
The Imposed Trail List window displays trails imposed on the network by
LightSoft.
The Admitted Trail List window displays trails admitted by (acquired into)
LightSoft from the network.
NOTE: When using the automatic admit and impose options

in the Trail Consistency Indicator window, no additional
synchronization operations are needed. The results of these
automatic actions can be confirmed in the Imposed Trails
List and Admitted Trails List windows.

Events List Window

The Events List window displays information about problems that may be
encountered in the synchronization process.
Events List window fields
Field Description
Type Type of event: Info, Warning, or Error (includes a graphical
representation of the respective type).
Date Date of the event.
Time Time of the event.
Info Short description of the event, for example, "Completion Aborted".
Description Detailed information of the event (when available), for example,
"Insert element into topology link" or "Create group <Group
Name>".
NOTE: The completion message windows which appear at

the end of an operation (whether successful or not), provide
detailed operational results information. The Operational
Results Info button in the Trail List window toolbar
enables you to revisit these results for operations that were
not completely successful. For more information, see

Trail Consistency Indicator Use

Cases
This section describes TCI inconsistency use cases applicable to all topology
layers.
The Trail layer represents the type of cross connect. To switch layers, select the
relevant Parameters pane dropdown list option.
When a red or yellow flag appears in the TCI window TCI Details pane, click
the flag (the applicable layer is automatically selected in the Parameters pane
dropdown list) and click the Show Selected Objects icon to display the
associated objects in the Selected Objects pane; see Trail Consistency
Indicator Window.
The following table shows the possible inconsistency causes and their
corresponding use cases.
Trail consistency use cases - optical trail layer
Use case Flag Suggested

color action
Inconsistency source: SNC
All or some XCs are in the LightSoft DB but not in the Red Reconnect
EMS DB.
There are XCs in both the EMS(s) and LightSoft DBs but Yellow Reconnect
with different path types (main, protection, or both).
Inconsistency source: Link
Link is not synchronized. Yellow Acquisition
Trail consistency use cases - SDH trail layer

color action
Inconsistency source: SNC
All XCs are in the EMS(s) DB but not in the LightSoft DB. Yellow Acquisition
All or some XCs are in the LightSoft DB but not in the Red Reconnect
EMS(s) DB.
The EMS DB contains more/different XCs than the Red Acquisition
LightSoft DB.
There are XCs in both the EMS(s) and LightSoft DBs but Yellow Reconnect
with different path types (main, protection, or both).
There are XCs in both the EMS(s) and LightSoft DBs but Red Reconnect
with different VC-4s.


color action
Inconsistency source: CTP
There are XCs in both the EMS(s) and LightSoft DBs but Red Reconnect
with different VC-4s.
The endpoint XCs exist in both the EMS(s) and LightSoft Yellow Reconnect
DBs but with different path types (main, protection, or
both).
The endpoint XCs exist in both the EMS(s) and LightSoft Red Reconnect
DBs but with different terminations (termination mode:
sink, source, or both).
Trail consistency use cases - unidentified trail layer

color action
Inconsistency source: EMS
EMS is not synchronized. Red In EMS-
SYNCOM, run
Trail
Reconstruction

11
Provisioning MPLS Tunnels
In this chapter:
Overview ....................................................................................................... 11-1
MPLS Tunnel Concepts................................................................................. 11-2
4
Tunnel Creation Management ..................................................................... 11-16

4
Tunnel Creation Options ............................................................................. 11-22

4
Creating Tunnels.......................................................................................... 11-22

4
Create Tunnel Window ................................................................................ 11-32

4
Automatic Multi-tunnel Creation ................................................................ 11-46

4
Overview
This section describes how to create MPLS tunnels, which are the
infrastructure for Ethernet services. The procedures and features described
specifically pertain to an MPLS networking using the MCS card.
OPTIONAL FEATURE: The Tunnel provisioning

mechanism is subject to the ETH/MPLS layer being enabled,
which is an optional feature. If not purchased, the
functionality and related menu options are unavailable.

Provisioning MPLS Tunnels LightSoft User Manual
MPLS Tunnel Concepts

LightSoft supports MPLS tunnels as part of its Virtual Private LAN Service
(VPLS) management package. VPLS enables connectivity between
geographically dispersed customer Ethernet sites across a provider as if they
were connected with a LAN. The interconnected customer sites form an MPLS
VPN.
The figure below shows three customer edge (CE) sites connected via a
provider's MPLS VPLS network comprising Provider edge (PE) sites and
Provider (P) transit equipment within the MPLS-PE perimeter. The CEs
communicate among themselves using standard Ethernet bridging and MAC
learning as if they all were on a single LAN.
Packet forwarding is enabled by a full mesh of MPLS label switched paths

(LSPs) or tunnels between the PE sites. The forwarding over the tunnels is
facilitated by label switching.
Label Switching
Two MPLS labels are added to each customer's Ethernet packet by the
source PE upon entry to a tunnel.
| VC-label , representing the VPN to which the packet belongs.
| Tunnel label , representing the tunnel to which the packet is mapped.
The two labels are swapped at each transit P along the tunnel path. Finally,
based on the labels, the Destination PE determines that it is the tunnel
destination (Tunnel label) and finds out the packet VPN (VC label). It then
looks in the MAC DA of the packet for the destination Ethernet port, removes
the two MPLS labels and forwards the packet to the CE port(s).

LightSoft User Manual Provisioning MPLS Tunnels
Tunnel Types – P2P and P2MP

Tunnels can be point-to-point (P2P) or point-to-multipoint (P2MP).
A P2P tunnel originates at a source PE, traverses defined transit Ps, and
terminates at a destination PE. The figure illustrates the label switching that
facilitates the packet forwarding along the tunnel path.
A P2MP tunnel is comprised of subtunnels, each starting at the same source PE

and ending at different destination PEs. It involves a tree-and-branch structure
where packet replication occurs at branching points along the tree (here P1).
The subtunnels may share a branch (a link), enabling forwarding only one
packet copy to that link. This scheme can achieve high multicast efficiency
since only one copy of each packet ever traverses an MPLS link.
The P2MP tunnel in the figure shows the source PE (PE1), transit equipment
(PE2 and P1), and destinations (PE3 and PE4).
This tunnel has three subtunnels, to PE2, PE3, and PE4, respectively, all sharing
the link from PE1 to P1. Therefore only one packet copy is sent on that link.

FRR Tunnel Protection

The Fast Reroute (FRR) protection mechanism protects a tunnel against link or
node failure along its path. A predefined Bypass tunnel goes around the failed
link/node and remerges with the original tunnel path at a downstream MCS.
The following figures show a tunnel from PE1 to PE2 to PE3, with node
protection at PE1 (Link and node protection are described in detail below). The
standard label switching mechanism described in Label Switching is extended -
switching to a bypass tunnel involves pushing a third MPLS tag (called FRR
label ) into the packet, and removing it when the bypass tunnel remerges
with the original tunnel path.
Link, Node, and Dual FRR protection are described in detail in the sections that
follow.
A main advantage of FRR over other protection schemes (such as end-to-end
protection) is speed of repair: predefined Bypass tunnels and fast physical
layer-based failure detection enable FRR to provide sub-50 msec switching
time, comparable to SDH protection mechanisms.
Any number of tunnels can be protected by one bypass tunnel – limited only by
resource CAC considerations; see CAC for MPLS Tunnels. This bypass tunnel
scalability is also known as Facility FRR.
Switching from protected to bypass tunnels and reversion back to protected
tunnels can be configured to apply automatically upon failure of the protected
port, and/or forced. For details, see the FRR Mode and Reversion parameters in
MoT Link Properties - TE Other Tab.
The timing of FRR switching to protection or back to the protected tunnel can
be configured to avoid premature or too frequent switching. For details, see the
Hold-off time and Wait-to-restore time parameters in MoT Link Properties -
TE Other Tab.

FRR Protection Types

FRR is configured with respect to links and/or nodes. The MCS upstream from
the failure reroutes the protected tunnel traffic to a bypass tunnel, which then
merges with the original tunnel at the next hop (NH) and/or the next next hop
(NNH) MCS, as follows:
| Link protection: Merges at the MCS at the NH node; see FRR Link
Protection.
| Node protection: Merges at the MCS at the NNH node; see FRR Node
Protection.
| Dual FRR protection: In a P2MP environment, merges at the NNH (or
another node) to provide Node protection, then hops back to the NH node
to provide Link protection. In a P2P environment, Dual FRR provides
simple Link protection. For more information, see Dual FRR for Link and
Node Protection.
FRR Link Protection

The following figure show a tunnel through the MCSs P1 to P2 to P3, where
link protection is applied between P1 and P2.
If P1 detects that the link to P2 failed, it switches the tunnel traffic to the link-
protecting bypass tunnel. The bypass tunnel remerges with the protected tunnel
at the next hop (NH) node P2. If a link fails (say on subtunnel S1), the MCS
upstream from it (P1) redirects traffic through a bypass tunnel whose
destination is the NH (P2).
A bypass tunnel may be shared by both P2P and P2MP tunnels. The figure
below shows a P2MP tunnel with link protection from P1 to P2, where the
traffic continues towards tail destinations PE3 and PE4.

FRR Node Protection

The following figure show a tunnel through the MCSs P1 to P2 to P3, where
link protection is applied between P1 and P2.
If P1 detects that the link to P2 failed, it switches the tunnel traffic to the link-
protecting bypass tunnel. The bypass tunnel remerges with the protected tunnel
at the next hop (NH) node P2. If a link fails (say on subtunnel S1), the MCS
upstream from it (P1) redirects traffic through a bypass tunnel whose
destination is the NH (P2).
A bypass tunnel may be shared by both P2P and P2MP tunnels. The figure
below shows a P2MP tunnel with link protection from P1 to P2, where the
traffic continues towards tail destinations PE3 and PE4.
NOTE: Node protection also provides link failure

protection. If node protection is selected, LightSoft tries to
protect every node (MCS) along the tunnel path. When this is
not possible (for example, on the last link of the tunnel if the
destination PE fails), LightSoft tries to provide link
protection. Thus, a tunnel may have node protection at some
hops and link protection at others.

Simple Node and Link Protection

A tunnel cannot be assigned both link and node protection at the same hop (i.e.
link protection from P1to P2 and node protection from P1 to P3. The following
configuration is not allowed:
An exception occurs for P2MP tunnels when dual FRR protection is applied.
Dual FRR can be used to provide standard link protection for P2P tunnels
(from P1 to P2), and in this case is permitted with standard node protection
from P1 to P3.
However, the general use case for Dual FRR is to provide node and link
protection to P2MP tunnels; see Dual FRR for Link and Node Protection.

Dual FRR for Link and Node Protection

IPTV applications are characterized by P2MP tunnel “drop-and-continue”
nodes, where termination and through tunnels coexist on overlapping links.
Link or node protection alone are insufficient to protect against interruption to
through traffic.
Link protection can be defined to protect subtunnel S1, finishing at P2. In the
event of a break on the link P1 to P2, the continuing traffic on the through
tunnel S2 is not protected. Similarly, Node protection alone at P3 will not
protect the through traffic interrupted between P1 and P2. Two bypass tunnels
protecting the same link is not supported.
For P2MP tunnels, the Dual FRR feature enables you to define a "point to dual
point" bypass tunnel:
| A transit drop point at the penultimate hop (P3).
| A tail drop point at the ultimate hop (P2).
The bypass tunnel effectively provides link protection to subtunnel S1, and
node protection to subtunnel S2.
NOTE: Dual FRR is generally used to provide node and link

protect to P2MP tunnels, but yields only simple link protection
in the case of P2P tunnels. Used in this way, Dual FRR can
provide link protection together with standard node protection
from the same Head node. This is generally not allowed with
regular link and node protection. For more information about
this technique, see Simple Node and Link Protection.

CAC for MPLS Tunnels

Connection Admission Control (CAC) for MPLS tunnels ensures there is
enough bandwidth on an MPLS link to create a further tunnel and still provide
the expected QoS for all connections. Tunnel CAC supplements Ethernet
service CAC mechanisms to facilitate effective QoS delivery by MPLS
networks. For details, see CAC for Ethernet Services.
At the MoT trail level, CAC ensures that SRLG diversity-increasing
operations, or bandwidth-decreasing operations that would leave insufficient
bandwidth for existing tunnels on the virtual link, are avoided. As well,
potentially CAC-affecting actions on MoT links (including indirect actions
such as changes to a server trail used by the link) protected by bypass tunnels
are always disallowed; the bypass tunnels must be deleted first.
TIP: The bypass tunnels can be deleted as a batch operation

through export to XML, then reimported after the potentially
CAC-affecting action is completed. For details about
exporting and importing tunnel data, see Batch Tunnel
Operations.
The changes that would trigger tunnel CAC evaluation include:

| Creating a new tunnel.
| Changing parameters of an existing tunnel or an MoT trail having tunnels
traversing it (for example, bandwidth).
| Changing parameters that are resource-limited.
CAC is performed on all outgoing ports of all equipment along the tunnel path.
As a result, the tunnel provides the declared end-to-end QoS parameters.
CAC consists of resource and BW-specific checks:
Resource CAC
Resource CAC checks requests against available quantity-related resources:
| Network level: Limits the number of P2MP tunnels (≤40), and PEs per
P2MP tunnel (≤128).
| Card level: Limits the number of P2P SNCs + P2MP Subtunnels, outgoing
tunnels, and Bypass SNCs.
| SPI Interface level: Limits the number of CoSs containing high bandwidth
tunnels (≥256 Mbps).
| CoS at the Port level: Limits the number of low vs. high BW outgoing
tunnels (high being ≥256 Mbps) excluding those of Bypass SNCs.

BW CAC
Bandwidth CAC checks requests against available BW-related resources.
Tunnel Level
Limits the total bandwidth of all tunnels protected by a Bypass tunnel (see
Allocated BW in Tunnel Parameters Status Parameters Pane) to the configured
BW for the bypass tunnel (see BW (Mbps) in Tunnel Parameters Basic
Parameters Pane).
This limit does not apply for a CoS configured for Best Effort protection (see
Network Properties - MPLS CoS Tab).
The Unreserved BW parameter indicates the bandwidth free for use per Bypass
tunnel. It is calculated as BW minus Allocated BW; see Create Tunnel Window
Status Parameters Pane.
Port and COS Levels

The bandwidth assignable per port or for any CoS per port is limited. Separate
configurable limits apply for tunnels (Res BW %) and bypass tunnels (Res
Shared BW %) per port and per CoS per port; see Res BW % in Network
Properties - MPLS CAC Tab.
The combined BW limit (tunnel + bypass tunnel) per port or per CoS per port
can be up to the port rate (100%). (While the BW limit for any one CoS cannot
exceed the port rate, the sum of the eight separate CoSs is not limited.)
Basic BW allowed for additional configurations per port (or per COS per port)
is this limit minus any already allocated bandwidth.
Bandwidth per COS can be "overbooked" whereby the sum of defined service
bandwidth can exceed a link's bandwidth capacity; see Service Overbooking.
The basic bandwidth allowed is adjusted by a multiple per COS; see
Overbooking Factor in the Network Properties - MPLS CoS Tab.
For example, "1" denotes 100% coverage (no overbooking), 2 denotes 100%
more bandwidth allowed than strictly available, and so on. Traffic that exceeds
the overbooked bandwidth at any one time is dropped according to applicable
criteria.
Bandwidth sharing among Bypass tunnels is allowed; see Bandwidth Sharing.

Tunnel Pathfinding
The tunnel pathfinder calculates an optimal path for a tunnel subject to tunnel
constraints, such as bandwidth and explicit path, and topology constraints
(including CAC). Pathfinding occurs when a new tunnel is set up or parameters
of an existing tunnel are changed (for example, bandwidth).
Pathfinding tries to find an explicit path containing all MCS cards and links
through which the tunnel should traverse - the shortest path (minimal sum of
weights) from source to destination in a weighted graph, considering multiple
other constraints to which the tunnel may be subject.
The pathfinder considers:
| Current Network Topology: MCS cards and MCS links.
| Available Resources: CAC Constraints on MCS cards and links, and
existing tunnels.
| Required Tunnel Parameters: Bandwidth, Protection, Explicit Path, and
others.
Pathfinding comprises two basic steps:
| Pruning links or link directions that do not meet tunnel requirements,
including FRR constraints.
| Calculating the shortest path from source PE to destination PE in the
pruned topology. The path may be subject to user optional explicit path
constraints.
SRLG Avoidance in Bypass Path Selection

Shared Risk Link Groups (SRLGs) refer to situations where links in a network
share a common physical attribute, such as fiber duct or equipment cage, and
are exposed to the same vulnerabilities. For more information, see Shared Risk
Link Groups (SRLGs).
SRLGs have implications for PF tunnel path selection and tunnel CAC validity.
For trail path implications, see SRLG and Other Shared Resource Minimization
in Path Selection.
In the figure in FRR Node Protection, if the links from P2 to P3 and the link
4
from P2 to P4 belonged to the same SRLG (for example, same fiber duct),
Bypass tunnel 2 would be of no use if that fiber failed.
The PF's Bypass tunnel path selection disallows links that share any SRLGs
with the link they are protecting. If the protected link then fails, the Bypass
tunnel does not automatically fail too (assuming single physical failure and no
XDM failures).
The SRLG Diverse field shows the SRLG status of the bypass path; see
Protection Parameters Pane. True indicates that the bypass tunnel path has no
SRLG in common with the protected link/node.

The "no shared SRLGs" rule is suspended if the Common SRLG Penalty
checkbox is selected in the User Preferences (Tunnel Constraints) window;
see Tunnel Management Constraint Preferences. In this case, paths that share
SRLGs with the protected path are not automatically disqualified. Those paths
are subject to other optimization criteria, like other prospective paths. If
needed, some impact of SRLGs can then be factored into the PF decision by
specifying a penalty per shared SRLG to be added to the metric or hops
associated with each path (according to the optimization criterion that applies).
However, if a Bypass tunnel is node-protecting (rather than link-protecting),
the protected node and all its links are automatically disqualified from PF
consideration regardless of SRLG assignments.
Tunnel Traffic Engineering and QoS

Network traffic engineering facilitates best use of network infrastructure by
offering QoS guarantees, such as bandwidth and latency, without the need for
dedicated lines. This section describes aspects of traffic engineering supported
by LightSoft.
Class of Service (CoS) per Tunnel

Each P2P or P2MP tunnel is assigned a user-configurable CoS value (0 to 7);
see BW parameter in Basic Parameters Pane. In general, services traversing a
tunnel with a higher CoS receives better treatment than one with a lower CoS.
The CoS value affects both the tunnel's throughput and latency performance.
See also CoS for Ethernet Services.
Bandwidth Sharing
Each P2P or P2MP tunnel is assigned a user-configurable bandwidth in the
range 1-2560 Mbps; see BW parameter in Basic Parameters Pane.
Multiple Bypass tunnels can automatically share bandwidth on common links.
The sharing mechanism is applied either on a best-effort basis, or require that
the sum of protected bandwidth not exceed the protecting bypass tunnel
bandwidth. Bandwidth sharing is implemented in the MPLS network properties
on a per-CoS basis; see CoS Tab.
Bandwidth can be shared without compromising QoS if the bypass tunnels
protect against independent SRLGs (only one carrying traffic at any given
time).

Additional Information in PF Decision

Traditional IP routing-based networks forward IP packets based on the shortest
or cheapest path to a destination. Traffic engineering allows additional
information in routing decisions, enabling additional control over routes that
MPLS packets take to a given destination.
Load Sharing Across Unequal Paths

In this example, large site A and B routers are connected directly by a high BW
link (cost 10), while smaller site C is connected to A and B with low BW links
(cost 20 each).
In traditional IP routing, the traffic between A and B is always routed over the
cheapest or least hop link even when alternative links are largely unused.
MPLS traffic engineering allows load balancing over the low BW link based on
traffic analysis. Two tunnels can be created (low BW and high BW), with
router A configured to pass one flow to B over the low BW tunnel for each
three over the high BW tunnel. In this case, unequal paths are utilized in
relation to their BW.
Routing Based on Bandwidth Requirements

Similarly, MPLS traffic engineering can route flows according to application
BW requirements. For example, the three routers (above) can be connected
with a 100 Kbps link or combined 200 Kbps + 200 Kbps links. Tunnels can be
built for 100 Kbps vs. 200 Kbps traffic and routers routing traffic according to
application BW requirements.
Operations Administration and Maintenance

(OAM) per Tunnel
Tunnel OAM enables verifying a tunnel has correct connectivity and delivers
the required availability and QoS; see Tunnel OAM in Advanced Parameters
Pane.

Traffic Management in MCS

The MCS Traffic Manager (TM) ensures that each tunnel gets its assigned
bandwidth and other QoS parameters. The TM works on the egress port, that is,
after packet classification and right before packets are transmitted into the MoT
line. Each tunnel undergoes the following TM functions:
| WRED at Tunnel, Class, and Port levels: Provides buffering and TCP-
friendly congestion management. Each tunnel is assigned a dedicated
queue to ensure that the traffic of one tunnel does not affect another tunnel
(the basis for tunnel bandwidth guarantees in the MCS). Each queue is
assigned a WRED drop profile that consists of two WRED curves, one for
Green and one for Yellow-marked packets.
| Shaping at the Class level: Each Class is assigned two rate limits,
committed (CIR) and peak (PIR). The CIR is automatically configured as:
Class CIR = Sum(Tunnel User BW)/CoS Booking Factor
where Tunnel User BW is the bandwidth configured by the user for the
tunnel and CoS Booking Factor is a user-configurable value per Class per
MCS to allow overbooking.
For example, if a Class in port contains 10 tunnels of 1 Mbps and the CoS
Booking Factor is 2, then
CIR = (10 x 1)/2 = 5 Mbps.
Overbooking and CIR

Overbooking (use of a Booking factor > 1.0) enables statistical multiplexing,
with which the total reserved BW is less than the sum of the tunnel BW. This is
useful, for example, for Internet traffic where customers do not all demand
their BW simultaneously.
In this scheme, the bandwidth that has to be reserved per CoS is defined as:
Committed Information Rate (CIR) = Sum (Tunnel BW)/Booking Factor
where:
| Tunnel BW = maximum bandwidth configured per tunnel, see BW (Mbps)
in Basic Parameters Pane.
| Booking Factor = Overbooking factor configured per CoS; see Network
Properties - MPLS CoS Tab.
For example, at a Booking factor of 2.0, instead of having to reserve 100 Mbps
for a CoS, only 100 Mbps/2.0 = 50 Mbps needs to be reserved. If the CoS
includes 100 tunnels of 1 Mbps, 0.5 Mbps is guaranteed per tunnel. (When all
tunnels do not use BW simultaneously, each tunnel can be as large as 50 Mb.)

Peak Information Rate

Peak Information Rate (PIR) is used to protect low priority packets. Bandwidth
allocation based on PIR reduces the likelihood of lower priority packets being
starved out by high priority traffic. A threshold CoS is assigned as high
priority; see Network Properties - MPLS CoS Tab, making all CoSs above it
considered high priority and those below it low priority. Bandwidth is then
allocated to CoSs according to their PIR, where:
| High Priority CoSs: PIR = CIR (the same calculation as described above)
| Low Priority CoSs: PIR = BW limited only by the port rate.
Thus, each low CoS tunnel can reach the port rate (default) if no other tunnel
transmits in that port, with high CoS packets limited to avoid starvation to low
CoS packets.

Tunnel Creation Management

You can define how tunnels are created in LightSoft and which fields are
visible in various parameter windows. The preferences are grouped in panes of
the User Preferences window, described in detail in the following sections:
| Tunnel Management: Sets tunnel parameter and map display preferences.
| Tunnel Management Constraints: Sets the constraints and optimization
criteria that the PF applies when a new tunnel is built.
| Tunnel Management Consistency Preferences: Sets the color coding used to
indicate the severity of inconsistencies between the LightSoft and EMS
databases in tunnel management windows.
| Tunnel Management Appearance Preferences: Sets the kinds of messages
and warnings will appear in the course of the tunnel management process,
as well as the colors of objects in the process window map views. You can
also set map endpoint and tunnel display preferences.
Tunnel Management Preferences

The User Preferences (Tunnel Management) window sets the fields shown in
the Tunnel Parameters tab of the Tunnel List window. For details of the
tunnel parameters, see Tunnel Parameters.

Tunnel Management Constraint Preferences

The User Preferences (Tunnel Constraints) window specifies the
optimization constraints and SRLG penalties that the PF algorithm should
consider when determining the path of a new tunnel.
The PF algorithm is activated when a tunnel is completed (all tunnel

parameters are set and you click Complete). The PF applies the constraints
described in this section.
Optimization Pane
This pane displays the optimization constraints that can be defined for PF
consideration when determining new tunnel paths:
| Optimization Criterion: Select the parameter the pathfinder should
optimize; see General Parameters Pane:
Min Metric: Minimum tunnel cost (sum of costs of all links through
which the tunnel traverses); see Link TE Metric parameter in Properties
for Link - MoT Virtual Link TE Other Tab.
Min Hops: Minimum number of hops.
Min Length: Minimum tunnel length (sum of the lengths of all links
through which tunnel traverses).
| Tunnel Hop Limit: The maximum number of PEs (up to 255) that a tunnel
can traverse, including the Source and Destination PEs.
| Link vs. Node Protection Penalty: Enter a value (up to 1000000) to add to
the cost of a "Link protected" link direction (meaning the more robust
"Node protected" links are preferred). 0 means Node protection has no
preference over Link protection. Relevant when an FRR Guarantee applies;
see parameter description in Create Tunnel Window - Advanced
Parameters Pane.

| Promote Sharing Among P2MP Subtunnels checkbox: Select the

checkbox to encourage the sharing of links used by subtunnels with the
same Tunnel ID. LightSoft accomplishes this by considering the link's cost
(metric, length, or hops) to be zero, thereby favoring such links in path
selection.
SRLGs Pane
This pane determines how SRLGs should be considered by PF in the Bypass
path selection decision. For more information about SRLGs and how the PF
considers them, see SRLG Avoidance in Bypass Path Selection.
| Common SRLGs Penalty checkbox: When the checkbox is not selected
(default), PF automatically disqualifies paths that share any SRLGs with
the protected path from being considered as a Bypass path. When selected,
those paths are not automatically disqualified and are considered in path
selection based on how they satisfy other optimization criteria.
| Penalty amount selector: When the Common SRLGs Penalty checkbox
is checked (paths that share SRLGs with the protected path are not
automatically disqualified by PF), you can, if needed, factor some impact
of shared SRLGs into the PF decision by entering a penalty to be added to
the metric or hops (according to the selected optimization criterion)
associated with each path that shares SRLGs with the protected path. ("0"
means shared SRLGs do not influence the PF decision at all.)
NOTE: If a Bypass tunnel is node-protecting (rather than

link-protecting), the protected node and all its links are
automatically disqualified from PF consideration regardless
of SRLG assignments.

Tunnel Management Consistency

Preferences
Color coding is used to indicate the severity of inconsistencies between the
LightSoft and EMS databases in tunnel management windows.
| For the default color correspondences per severity, see Severity Breakdown
Pane. The colors can be customized according to your needs, with system-
wide application. A standard customization procedure is used; see

Tunnel Management Appearance

Preferences
You can define which kinds of messages and warnings will appear in the
course of the tunnel management process, as well as the colors of objects in the
Create Tunnel and Tunnel List window map views. You can also set map
endpoint and tunnel display preferences.
Messages Pane
The checkboxes enable the kinds of messages and warnings will appear in the
course of the tunnel management process (enabled by default).

Behavior Pane
The checkboxes set map endpoint and tunnel display preferences in the Create
Tunnel and Tunnel List window map views (enabled by default):
| Show endpoint on map: When selected, the Tunnel List window map
always automatically shifts to display at least one endpoint of each
displayed tunnel. This is useful when working with large topologies having
widely separated elements, avoiding manually scrolling to the relevant
tunnel endpoints. Note that the automatic shift of the map may take some
time.
| Show PEs and Links Only Where Tunnel Traverses: When selected and
after a tunnel is selected (highlighted) in the Tunnel List window Tunnels
pane, only that tunnel and its corresponding objects are displayed on the
window map. (When the window first opens, the window map shows either
all objects or objects consistent with main window preselections. This is
subsequently replaced with only the selected tunnel and its associated
objects.)
This is the same behavior as the Show One Trail Only option, but applies
instead to tunnels; for details see that parameter in Trail Management
Preferences.
Colors Pane
The checkboxes set the colors of objects in the Create Tunnel and Tunnel
List window map views.

Tunnel Creation Options

You can create tunnels in several ways:
| Using the Create Tunnel window, as described in this section.
| Acquisition from the EMS, see Synchronizing Tunnels.
| Importing tunnel definitions from an XML file that contains the parameters
of the tunnels to be created. The XML files can be imported either through
LightSoft or via UNIX; see Importing Tunnels.
| Automatic multiple bypass tunnel creation and full mesh provisioning as
described in Automatic Multi-Tunnel Creation.
Creating Tunnels
You can define MPLS tunnels directly from LightSoft using the Create
Tunnel window; see Creating a Tunnel. Similar windows are used for editing
or viewing existing tunnel parameters; see Performing Actions on Tunnels.
Creating tunnels between linked MCSs in LightSoft presupposes that the MoT
trails the tunnels should traverse already exist and have sufficient bandwidth to
accommodate the new tunnels. Creating tunnels consists of the following main
steps:
| Defining parameters
| Selecting endpoints
| Assigning path inclusions and exclusions (optional)
You can create a tunnel by simply accepting default parameter values or you
can select specific values. The new tunnel is built by the Pathfinder (PF)
algorithm according to the selected optimization criteria; see Tunnel
Management Preferences.
As part of the creation process, you can export the new tunnel to an XML file
for backup purposes or for automatic assignment of bypass tunnels.
You can optionally modify the tunnel pathfinder parameters (and thereby the
resultant tunnel paths) via tunnel constraint preferences; see Tunnel
Management Constraint Preferences.

Creating a Tunnel
MPLS tunnels can be created manually using Create Tunnel window; see
Create Tunnel Window. Automated tunnel creation is also available; see
Automatic Multi-tunnel Creation.
When creating a tunnel, LightSoft uses only objects in resource domains
assigned to your user group (allowed by your user group's profile); see
Managing User Groups.
Many parameters can be left blank. LightSoft enters default values or the last
used parameters. See the pane descriptions for mandatory parameters.
The sequence in which you create tunnels and FRR protecting bypass tunnels is
important:
| First create FRR bypass tunnels.
| Then create the tunnels to be protected.
LightSoft will then automatically assign the best-protecting bypass tunnel that
is available to each protected tunnel.
NOTE: If a protected tunnel is created before an FRR

bypass tunnel is available for it, or if a bypass tunnel is
removed (whether manually or as a result of an automated
process) the protected tunnel's Protection Actual may become
Unprotected. In this case, you should update the protection of
those tunnels. For details, see Updating FRR Protection.
To create a tunnel in the Create Tunnel window:

1. (Optional) On the main window select the objects containing the endpoints
of the intended tunnel. This opens the Create Tunnel window displaying
those objects and any associated MoT virtual links, rather than all the
objects in the current view. (When the PF algorithm searches for tunnels, it
relates to the relevant topology, not only to the displayed elements.)
2. On the Traffic menu, select Tunnels > Create Tunnel.
OR
On the main toolbar, click the Create Tunnel icon . The Create
Tunnel window opens; see Create Tunnel Window.
The selected (or all) objects and associated MoT virtual links appear in the
window map, including MPLS-relevant LEs, automatically split out from
their respective MCS MEs. The first time the Create Tunnel window
opens in a session it may take longer than it does subsequently.

3. In the Tunnel Parameters tab panes, enter the tunnel parameters.

(For P2MP tunnels, the same parameters are used by all subtunnels of the
tunnel.)
Enter the Protection Desired.
Enter the FRR Type (Bypass tunnel only).
If you require Dual FRR protection, select Link protection here. This
will make available the Dual FRR radio buttons in the Advanced
Parameters pane.
For other parameters, you can accept default parameter values or you
can select specific values. Defaults are the last tunnel entry values. See
the parameter descriptions in Tunnel Parameters.
Click the Reset tunnel parameters to defaults icon to reset

tunnel parameters to default values.
4. Select the tunnel endpoint PEs:
NOTE: This step is applicable for all tunnel types, including

bypass. A Protected tunnel can be created either before or
after the Bypass tunnel.
a. Set the Select mode to Endpoints.
b. Select the Head endpoint PE - Click the intended source PE to select it

as the Head endpoint.

c. Select the Tail endpoint PE - Click the intended destination PE(s) to

select it/them as the Tail endpoint(s) (A P2MP tunnel may have
multiple tails):
For Bypass tunnels:
For link protection: Select a next hop (NH) PE on the subtunnel to
be protected.
For node protection: Select a next next hop (NNH) PE.
For Dual FRR protection, select the NH PE of the protected tunnel

(in the same way as link protection). Then do the following,
according to the desired Dual FRR use case:
To implement the standard Dual FRR use case where the protection
path is “point to dual point”, you must also explicitly include the
bypass tunnel’s penultimate hop to correspond with another node
(either the protected tunnel’s NNH PE or some other node that would
achieve the desired purpose).
For a description of the standard use case, see Simple Node and Link
Protection.
For details about how to explicitly include a PE in the tunnel path, see
step 6.
To implement Dual FRR to provide simple link protection, no
further node selection is needed. For the rationale of implementing
simple link protection with Dual FRR, see Simple Node and Link
Protection.
(Do not double-click. Double-clicking opens a GCT to the LE's slot
view in the EMS.)
The endpoint elements are highlighted on the map and listed in the
Endpoints pane.

You can locate a PE on the map with the main toolbar Search utility
; see Searching and Locating Objects.

You can deselect endpoints by:
Clicking the already selected element on the map again, OR
Right-clicking an endpoint in the Endpoints pane and selecting
Remove (or Remove All to remove all endpoints), OR
Clicking the Clear All Endpoints and Path toolbar icon.
NOTES:
If the tunnel you are creating spans one or more PEs (as in
the Node protection example above) and a specific path is
required, it is recommended to specify which PEs the
current tunnel path should explicitly include; see Step 6.
A tunnel can span only a single MPLS network. After you
select one endpoint for the tunnel, all PEs belonging to
other MPLS networks become unavailable for selection.
5. If this is a Bypass tunnel (Protection Desired is Bypass, to protect a

separately created tunnel having Protection Desired = Protected), a
message to select a protected port opens.
a. Click OK to close the message.

b. Click the link outgoing from the source PE that is to be protected.
This example demonstrates the selection when Link protection applies.
If node protection applies, the same link is selected.

c. The protected link is highlighted in white and the Select Protected

Port dialog box opens. In that dialog box, select the direction of the
icon outgoing from the source PE.
Click anywhere in the map to close the Select Protected Port dialog
box.
If link or Dual FRR protection apply, the protected link is highlighted
in black on the map.
If node protection applies, the protected link and node are highlighted
in black on the map.
The protected node is displayed in the Source PE row in the Endpoints

pane, in the Protection column.
NOTE: The black color on the protected link (and node)

implies that it is "excluded" from PF consideration as the
bypass tunnel path. (PF prunes the link when any FRR
protection applies. It additionally prunes the node when Node
protection applies. For information about the Link and Node
FRR protection types, see FRR Protection Types.
4

6. (Optional) If you want to explicitly include PEs or links in the tunnel path:
a. Set the Select mode to Exp. Path Include.
b. Include PEs and links in the order that they should appear in the path (if
you select PE1 before PE2 then the tunnel must traverse PE1 before
PE2):
Include PEs by clicking it. The selected PE appears in white on the
map and is listed in the Endpoints and Path tab Inclusions pane.
AND/OR
Include links by clicking them in the order they should appear in the
path. The Include Link dialog box opens. Specify the link direction
to be included. (Picture shows direction from Port 2 as included.)
Then click anywhere in the map to close the dialog box.
c. To change the order of a PE in the Inclusion pane list, highlight it in

the pane and use the Move Up or Move Down button to move it up or
down.
NOTE: For P2MP tunnels, multiple Tail endpoint selections

are allowed only if all Tail endpoints have identical explicit
path Include lists (the same link/node IDs and order). The
selected PEs and links are included in the path to Tail
endpoints highlighted in the Endpoints pane.

7. (Optional) If you want to explicitly exclude PEs or links in the tunnel path:
a. Set the Select mode to Exclusions.
b. Exclude PEs or links from the tunnel path by clicking them, in the same
way as described for inclusions. The selected PEs appear in black on
the map and are listed in the Endpoints and Path tab Exclusions pane.
In the case of links, an Exclude Link dialog box opens, where you
select a link direction to be excluded.
The link appears in black on the map and one or both of its directions
are listed in the Explicit Path Exclude tab.
NOTE: For P2MP tunnels, multiple Tail endpoint selections

are allowed only if all Tail endpoints have identical explicit
path Exclude lists. The selected PEs and links are excluded
from the path to Tail endpoints highlighted in the Endpoints
pane.
You can perform the following actions concerning Bypass tunnels from the
Path pane after a tunnel is completed, or through the Tunnel List window
on an existing tunnel; see Actions on Bypass Tunnels.
View/hide bypass tunnel assignment per hop.
Remove bypass tunnel assignments.

8. (Optional) Click the Complete Tunnel icon . LightSoft calculates the

entire path and displays a completion message with the operation results
and any nonfatal errors. For more information, see Performing Tunnel
Operations.
The path is highlighted on the map (in pink for unprotected links/nodes,
and violet for protected links/nodes) and listed in the Path pane. You can go
back and modify the path if desired.
P2MP tunnels: If selected subtunnels have different explicit path lists, no
path is highlighted on the map.
Create Tunnel Failure.
9. Click the Activate Tunnel icon to activate the tunnel on the network.
LightSoft computes the entire path and displays a completion message with
the operation results and any nonfatal errors. For more information, see
Performing Tunnel Operations.
The window panes are updated with the tunnel information.
The path is highlighted on the map (in pink for unprotected links/nodes,
and violet for protected links/nodes) and listed in the Path pane.
P2MP: You can highlight a specific subtunnel on the map by selecting its
Tail endpoint in the Path pane.
If you unassigned Bypass tunnels following Complete operation, the
associated tunnel hops will not be assigned bypass tunnels.
NOTE: If Complete Tunnel was not performed before, or if

it was followed by any potentially path-affecting action (such
as a change of endpoint), then it will automatically be
performed/repeated as part of the Activate process. (If no
such actions followed the Complete step, a fast activation
process applies, which does not duplicate the Complete
processing.)

10. You can export the new tunnel to an XML file for various future purposes:
Update FRR Protection: If this is a protected tunnel, the XML file that
is produced by the Export process can later be imported to LightSoft,
triggering bypass tunnel assignment.
Create: The XML file that is produced can be used for backup
purposes, imported to LightSoft as the need arises.
Click the Export icon on the window toolbar (enabled after the tunnel
has been activated). The Export Tunnels dialog box opens.
Continue the procedure as described in Exporting Tunnels, from Step 3.
Diagnosing a Create Tunnel Failure

If the Create Tunnel operation fails, perform the following verification steps.
2. Check if all the explicit path selections and endpoints are correct.
4. Check the parameters selected in the Create Tunnel window.
If the tunnel failed at the Activation stage (Completion
succeeded):
2. Check if all tunnel segments were created at the EMS level.
4. Check the TSC counter background color on the LightSoft main window
toolbar; see Tunnel Segment Consistency (TSC) Counter. Check the color
correspondences in to Severity Breakdown Pane and perform the action
recommended in Tunnel Consistency Use Cases. For example, perform
tunnel synchronization and check the differences between LightSoft and the
EMS. The elements that the tunnel segment failed on will be shown in the
Result window described in Performing Tunnel Operations.
5. If an NE in the tunnel was disconnected during tunnel creation or a craft
terminal connected, and the resulting tunnel is in an incomplete state, use
Reconnect to send the missing tunnel segments to the network.

Create Tunnel Window

The Create Tunnel window provides a graphical representation of all or
preselected objects and their associated MoT virtual links, as well as
information and configuration panes.
The Create Tunnel window includes the following sets of configuration panes,
organized in two tabs:
| Map View: Graphical representation of all or preselected objects and their
associated MoT virtual links, with the relevant Ethernet LEs automatically
split out; see Map View.
| Tunnel Parameters tab: Tunnel parameter entry panes. For detailed
information about the pane contents, see Tunnel Parameters.
| Endpoints and Path tab: List of selected tunnel endpoints, the tunnel
resources along its entire path, and explicit path user selections comprising
excluded and included nodes and links. For detailed information about the
pane contents, see Endpoints and Path.

Create Tunnel Menu and Toolbar

Below are the functions available from the Tunnel List window menu and
equivalent toolbar icons. Other functions are available from additional toolbar
icons and selectors; see Other Create Tunnel Options.
Create Tunnel menu and toolbar icons
Menu Toolbar Description

option icon
Select menu and radio buttons
For tunnel path definition purposes, enables selection from the window map of
nodes as endpoints or links/nodes to be explicitly included or excluded from the
tunnel path.
Endpoints Enables selection of endpoints by clicking elements in

the map. For Bypass tunnels, can select the protected
port (allowed after endpoints have been selected).
Exp. Path Enables selection of nodes and/or links to be explicitly
Include included in the tunnel path by clicking in the map.
Exp. Path Enables selection of nodes and/or links to be explicitly
Exclude excluded from the tunnel path by clicking in the map.
Paint menu and radio buttons
Highlights on the map either the tunnel path or specific link/port inclusions and
exclusions, or both.
Path Highlights in violet the nodes/links in the tunnel path

(following the last successful Complete or Activate
action).
Explicit Highlights any nodes and links that had been explicitly
Path included or excluded in the tunnel path (exclusions in
black, inclusions in white).
Path & Highlights both the nodes/links traversed by the path
Explicit and those explicitly included/excluded (exclusions in
Path black, inclusions in white, the remainder of the tunnel
path in violet).


option icon
Action menu
Clear Removes all endpoint selections (including explicit path
Endpoints inclusions/exclusions) but keeps any user changes to
and Path tunnel parameters.
Clear Clears all endpoint selections (including explicit path
Settings inclusions/exclusions) and restores all tunnel parameters
to the system defaults.
Reset Restores the tunnel parameters to the system defaults.
Parameters
Export to Exports the tunnel configured in the Create Tunnel
XML window to an XML file, leading into the export
procedure described in Exporting Tunnels. Exported
data can be imported to create tunnels at a later time.
See Importing Tunnels.
Show Info Displays detailed results of the last operation; see
Complete Causes the PF algorithm to search a route for the tunnel
based on the current selections and network
configuration. If successful, the complete path is
highlighted on the map. Nothing is saved to the
database at this point or sent to the EMS.
Activate Causes implementation of the new tunnel in the
network. This option can be used even if Complete
tunnel was not performed.
If successful, the NMS sends information to the EMS,
which creates MPLS SNCs in the elements, and tunnel
information is saved in LightSoft and EMS DBs. Live
traffic can now traverse the tunnel.
Help menu

Other Create Tunnel Options

The following functions are available from additional toolbar icons and
selectors.
Other Create Ethernet Service toolbar options
Toolbar icon Name Description

Show Activated If selected (toggled on), by default, the
Tunnel service is shown in the window map
immediately after activation.
Show On Demand Some tunnel parameters (for example,
Parameters Tunnel Length) show "On Demand" as
their value when a tunnel is first loaded or
configured. Clicking this icon initiates a
calculation process which displays current
values for all such parameters. (The
process may take some time.)
Show Details Panel Alternately hides the left-side details
panes, leaving only the Tunnels pane and
the window map, or reinstates the details
panes. For more details, see Showing,
Hiding, and Auto-Fitting Columns.
Map View
The map view provides a graphic representation of all or preselected objects
and their associated MoT virtual links, with the relevant Ethernet LEs
automatically split out. It is used in the process of tunnel endpoint selection,
and assists visualization of the Create tunnel process.
view, as described in Managing Elements, Groups, and Networks.

Tunnel Parameters
The Tunnel Parameters tab provides tunnel parameter entry panes.
| Basic Parameters: Enables configuring the basic tunnel parameters.

| Advanced Parameters: Enables configuring more specific optional tunnel
attributes.
| Protection Parameters: Shows the tunnel FRR parameters.
| Status Parameters: Shows operational, alarm, bandwidth, and protection
state-related parameters.
| General Parameters: Shows the general tunnel parameters.
Basic Parameters Pane

The Basic Parameters pane enables you to configure the most basic tunnel
attributes. Protection Desired (and FRR Type for Bypass tunnels) are
mandatory fields - defaults are the last entry values. You can accept default
parameter values for other parameters in this or other panes or you can enter
specific values.

Basic Parameters pane fields
Field Description
Protection Protection desired for this tunnel (mandatory, default is selection
Desired from last created tunnel):
| Unprotected: Tunnel is unprotected.
| Protected: Tunnel is FRR protected by a bypass tunnel.
| Bypass: Tunnel provides FRR protection to another tunnel.
For more information about the FRR protection mechanism, see FRR
Tunnel Protection.
FRR Type FRR protection mode applying to this bypass tunnel (relevant only if
the Protection Desired is Bypass):
| Node protection: Protects against failure of a node and its
subsequent link. The diverted traffic remerges with the original
tunnel at the next next hop (NNH) MPLS PE downstream from
the failure.
| Link protection: Protects against failure of a link. The diverted
traffic remerges with the original tunnel at the next hop (NH)
MPLS PE downstream from the failure.
Note: If your bypass tunnel definition needs to provide Dual FRR
protection, select Link protection here. This will make available the
Dual FRR radio button in the Advanced Parameters panel.
For more information about the FRR protection modes, see FRR
4
Protection Types.
Tunnel Name Name of the tunnel (not unique). Enter a name or select one from the
list (of recently used labels). If no name is specified, a name is
automatically assigned showing endpoint details and a timestamp.
(Optional)
Customer Customer associated with this tunnel (not unique). If no name is
specified, the name is left as blank. (Optional)
CoS Class of service, CoS0 to CoS7 (subject to equipment support
limitations); see Class of Service (CoS).
BW (Mbps) Maximum bandwidth allowed to this tunnel. Select 1 to 2560.
Comments Free text about the tunnel.

Advanced Parameters Pane

The Advanced Parameters pane allows you to configure more specific
working tunnel attributes and to enable/disable OAM and alarms for the tunnel.
Advanced Parameters pane fields
Field Description
Working Tunnel
P2P/P2MP radio Type of tunnel (mandatory):
buttons | P2P (point-to-point)
(Bypass tunnels are automatically P2P).
| P2MP (point-to-multipoint).
See Tunnel Types.
Single Service When selected, tunnel restricted to only one service (VPN),
Only checkbox regardless of service type. Relevant for P2P tunnels.
P2P Service Only When selected, tunnel restricted to P2P VPNs (one or more,
checkbox subject to bandwidth considerations). Relevant for P2P tunnels.
Guaranteed FRR When selected, PF considers only tunnel paths having predefined
Desired bypass tunnels available to protect each node and link.
checkbox Relevant only when the Protection Desired is Protected.
When adding subtunnels, this parameter applies only to the new
subtunnels (i.e., path of existing subtunnels does not change).
Bypass Tunnel
Dual FRR Enable and Disable radio buttons either enable or disable Dual
FRR operation. The radio buttons are available only when Link
Protection is selected in the Basic Parameters pane. For more
information about Dual FRR protection, see Dual FRR for Link
and Node Protection.

Field Description
Tunnel OAM and General Tunnel Alarms
Tunnel OAM Enable/disable. Tunnel OAM (Operations Administration and
(CV) Maintenance) enables P2P tunnel operational state monitoring,
ensuring that the tunnel has correct connectivity and delivers the
required availability and QoS.
A continuity control verification (CV) packet is sent over the
tunnel, which the tail expects to receive at periodic intervals.
Otherwise the operational state of the tunnel becomes Down. If
the failure condition relates to the specific tunnel, an alarm is
raised. If the failure condition relates to some other failure
which affects multiple tunnels, for example a link failure, the
alarm is masked.
Generate Tunnel Activates/deactivates generation of alarms on this tunnel in the
Alarms same way as Alarm Master Mask in trails. For details, see
Advanced Trail Parameters Pane.
MPLS Label You can optionally set the MPLS Label value for the trail. If
you do not do this (or if the provided label is out of the valid
range), LightSoft automatically selects an available MPLS label
(as indicated in brackets in the example).
For the tunnel to complete, the assigned label must not be used
by another tunnel. (The ID must be unique per network.) You
can confirm this before completing the tunnel by clicking the
button. (Endpoints must be selected
before this step. Otherwise the message appears: At least one
endpoint should be selected.)
The MPLS Network ID is displayed in the Network and
Database floating windows of the Tunnel Synchronization
window; see Tunnel Synchronization Floating Window
Columns.
Note: One purpose of manual MPLS label assignment is to
enable the tunnel to traverse multiple MPLS networks.
In that case, after the tunnel is created, an EMS procedure must
be performed to “stitch” the elements where the MPLS
networks connect; see the relevant EMS user manual.

Protection Parameters Pane

This pane shows the tunnel FRR parameters. It is empty when the tunnel is
created and filled with information after the tunnel is completed or activated.
Protection Parameters pane fields
Field Description
Protected Tunnel
Protection Actual Quality of protection actually applying to a protected tunnel.
This may differ from Protection Desired, for example, if a
bypass tunnel is not currently assigned to the protected
tunnel. For P2MP, denotes the weakest protection applying
to any associated subtunnel.
| Protected Full Node: Node protection on entire path,
with link protection applying on the last hop.
| Protected Full: Node protection on entire path, with link
protection applying on some hops (not the last).
| Protected Partial: Not all hops are protected.
| Unprotected: Tunnel currently not protected.
| Bypass: Tunnel is bypass.
Dual FRR (P2MP Whether the bypass tunnel is enabled to provide Dual FRR
Tunnel) protection.
Bypass Tunnel
Protected Port Name of the port protected by a bypass tunnel.
Protected Node Next hop node name (when the FRR Type is Link
Protection), or next next hop node name (when the FRR
Type is Node Protection).
SRLG Diverse True indicates the bypass tunnel path has no SRLG in
common with the protected link/node; see SRLG Avoidance
in Bypass Path Selection.
PHOP (Dual FRR) If Dual FRR protection applies, PE ID of node which is the
penultimate (second to last) hop of the protecting bypass
tunnel.

Status Parameters Pane

This pane shows operational, alarm, bandwidth, and protection state-related
parameters. It is empty when the tunnel is created and filled with information
after the tunnel is completed or activated.
Status Parameters pane fields
Field Description
Tunnel State Synchronization state for this tunnel:
| OK: Tunnel provisioned and consistent with LightSoft.
| Inconsistent: Tunnel provisioned but not consistent with
LightSoft.
| Incomplete: Tunnel provisioning is partial or nonexistent,
due to, for example, NE disconnection from LightSoft.
Tunnel Reconnect action may be required.
Allocated BW Bandwidth allocated (reserved) for this tunnel. Relevant for:
(Mbps) | Bypass tunnels: Sum of BW of the protected tunnels.
| P2P Services Only tunnels: Sum of BW of services directed
to this tunnel.
Unreserved BW Unreserved bandwidth for the tunnel = BW minus Allocated
(Mbps) BW. Relevant for:
| Bypass tunnels where the protection BW for this CoS is
Best Effort; see Best Effort Protection in Network
Properties – MPLS CoS Tab.
| P2P Services Only tunnels.
Expandable BW Maximum BW that this tunnel can be increased to without

(Mbps) violating CAC constraints at any hop; see CAC for MPLS
Tunnels BW CAC.
Tunnel Usage Bypass: Number of underlying protected tunnels.
Protected or unprotected: Number of underlying VPNs.

General Parameters Pane

This pane shows the general tunnel parameters. It is filled with information
after the tunnel is completed or activated.
General Parameters pane fields
Field Description
NMS Tunnel ID LightSoft tunnel identifier for this tunnel, a unique value in
LightSoft, for example, "36(38)", formatted as:
Unique ID Number (Managed System ID),
where:
| Unique ID Number – ID of the tunnel, sequentially
assigned in the tunnel creation process.
| Managed System ID – ID of the management system in
which the tunnel was created (an EMS or LightSoft).
MPLS Label MPLS label for this tunnel, a unique value per network.
Relevant only for P2MP tunnels.
MPLS Network ID MPLS Network ID of network where this tunnel traverses.
Actual No. of Hops Actual number of hops for this tunnel.
For P2MP, maximum amongst its subtunnels.
Tunnel Metric Cost of tunnel (sum of costs of all links through which this
tunnel traverses).
For P2MP, maximum among the subtunnels.
Based on the Link TE Metric parameter in Properties for Link -
MoT Virtual Link TE Other Tab.
Tunnel Length Length of this tunnel, the sum of the lengths of all links through
which this tunnel traverses.
For P2MP, max among the subtunnels.
Created By User Tunnel creator.
Created With Application the tunnel was created with - GUI (the LightSoft
GUI), XML (import from XML), or TSC (acquisition from the
EMS).

Field Description
Creation Time Tunnel creation date and time.
Modified By User Tunnel modifier.
Modified With Application the tunnel was modified with - GUI (the LightSoft
EMS).
Modification Time Tunnel modification date and time.
Endpoints and Path

This tab lists the selected tunnel endpoints, details of each node along the entire
tunnel path, and path user selections comprising explicitly included and
excluded path characteristics.
| Endpoints: Shows the tunnel endpoint selections.

| Path: Lists details of each node along the entire tunnel path.
| Inclusions: Lists the selected explicitly included path characteristics.
| Exclusions: Lists the selected explicitly excluded path characteristics.
Endpoints Pane
The Endpoints pane lists details of the tunnel endpoints. A P2P tunnel has two
endpoints while a P2MP tunnel can have up to 128 endpoints.
Endpoints pane fields
Field Description
PE PE ID of the PE that contains the endpoint.
Role Endpoint's SNC role: Head, Transit, or Tail.
Port Details of Out Port in Head and In Port in Tail.
Protected Port Name of the protected port of a bypass tunnel.

Path Pane
The Path pane lists details of each node along the tunnel path. For P2MP
tunnels, applicable only if one Tail endpoint is specified. If multiple Tail
endpoints are selected, no information is shown.
You can view bypass tunnel assignments per hop or you can remove bypass
tunnels; see Actions on Bypass Tunnels.
Path pane shortcut options

Option Description
Show Bypass Displays bypass tunnel paths for the selected hops (blue in map).
Enabled for protected tunnel segments with bypass assignments.
See Actions on Bypass Tunnels.
Hide Bypass Clear bypass tunnel color coding from the map.
Remove FRR Removes bypass tunnel assignments from the selected tunnel
Protection segment. Enabled for protected tunnel segments with bypass
assignments.
Path pane fields
Field Description
# Relative position of the node/link within the path (lower values are
the hops that the tunnel must traverse first).
PE PE ID of the PE representing the node.
Role Endpoint's SNC role: Head, Transit, or Tail.
In Port Tunnel entry port.
Out Port Tunnel termination port.
Protection Type Protection Desired values (see Basic Parameters Pane), but on a
per hop basis (taken from the EMS) as follows:
| Unprotected tunnel: Unprotected
| Bypass tunnel: Bypass
| Protected tunnel: Protected if hop is protected, otherwise
Unprotected
FRR Type FRR protection mode applying to this bypass tunnel (Node or Link
protection). See description in Basic Parameters Pane.
Bypass Tunnel ID NMS Tunnel ID of the associated bypass tunnel.
Bypass Tunnel Name Name of the associated bypass tunnel.
Bypass Out Port Associated bypass tunnel termination port.
FRR In Use Whether the bypass tunnel at the port is currently carrying traffic
as a result of main tunnel failure.

Inclusions Pane
This pane lists the selected explicitly included path characteristics. Manually
defined inclusions/exclusions are reflected only in LightSoft. They are not
saved to the EMS.
The order in which a row is displayed specifies its order in the path. The order
can be changed using the Move Up and Move Down buttons. (In this pane,
manual sorting by clicking column headers does not apply.)
Inclusions pane fields
Field Description
# Relative position of the node/link within the path (lower values
are the hops that the tunnel must traverse first).
Type Node or link.
ID Node or link user label.
Exclusions Pane
This pane lists the path user selections comprising explicitly excluded path
characteristics. Manually defined inclusions/exclusions are reflected only in
LightSoft. They are not saved to the EMS.
Exclusion pane fields
Field Description
Type Node or link.
ID Node or link user label.

Automatic Multi-tunnel Creation

An MPLS network can include up to 256 PEs. The full tunnel mesh connecting
every two points can involve a great numbers of tunnels. In addition, creating
bypass tunnels for comprehensive protection to multiple nodes and links can be
a daunting task. LightSoft "automaton" functions greatly simplify the tunnel
mesh any multiple bypass tunnel creation processes.
Many parameters can be left blank. LightSoft enters default values or the last
used parameters. See the pane descriptions for mandatory parameters.
NOTE: The automaton functions are recommended for use only by

advanced users or with the assistance of ECI Telecom customer
support.
To automatically create a tunnel mesh (or multiple bypass

tunnels):
1. (Optional) On the main window select the objects containing the endpoints
of the intended tunnels. This opens the Create Tunnel window displaying
those objects and any associated MoT virtual links, rather than all the
objects in the current view. (When the PF algorithm searches for tunnels, it
relates to the relevant topology, not only to the displayed elements.)
2. From the Traffic menu, select Tunnels > Create Tunnel Mesh (or Create
Multiple Bypass).
OR
On the Create Tunnel window toolbar, click the Create Tunnel Mesh
icon (or the Create Multiple Bypass icon).
A window resembling the Create Tunnel window opens with the title
Create Tunnel Mesh (or Create Multiple Bypass Tunnels).

3. Enter tunnel parameters that are common to all the required tunnels.
Enter the Protection Desired (Protection or Unprotected for Working
tunnels). The Multiple Bypass selection is automatically Bypass.
Enter CoS values (multiple values are possible - see Basic Parameters Pane.
Enter the FRR Type (Bypass tunnel only).
For other parameters, you can accept default parameter values or you
can select specific values. Defaults are the last tunnel entry values. See
the parameter descriptions in Tunnel Parameters.
The Reset tunnel parameters to defaults icon resets tunnel

parameters to default values.
For a description of the relevant panes, the valid parameter selections per
automaton option, and special behavior of some parameters, see:
4. Select PEs in the Create Tunnel window map:
Full Mesh: Select PEs amongst which to create the full tunnel mesh.
Multiple Bypass: Select PEs or links for which to create Bypass
tunnels, according to whether Link Protection or Node Protection
applies. Select PEs for which to create node protecting Bypass tunnels.
a. You can select objects in two ways:
Select objects one at a time, while holding down the SHIFT key.
Or
Select all the objects in a rectangle area of the map by clicking and
dragging. (Only objects relevant to your current action are used.)
Then right-click any object and select Select Nodes or Select Links
(according to parameters selected in the window panes).
The main toolbar Search utility can help you

to locate a PE on the map; see Searching and Locating Objects.
The selected objects are listed in the Selected Elements pane.
To clear selections:
Click a selection on the map or right-click a selection in the
Selected Elements pane and select Remove (or Remove All to
clear all selections).
To clear all selections, click the Clear all endpoints and path icon .
NOTE:
Nodes must reside within the same MPLS network.
Secondary LEs that contain the endpoint ports should
be selected, not their source primary LEs.

b. Check the order in which the objects are listed in the Selected
Elements pane. Tunnels are built in the listed order. You can change
the order of the objects by selecting an object and clicking the Up or
Down buttons to promote or demote them as needed. For more
information, see Selected Elements Pane.
NOTE: There may be a residue of tunnels that are not

created automatically due to CAC compliance issues. Deal
with these manually after the automaton process is completed.
5. Start the automaton tunnel creation processing by clicking the Start

Tunnel Creation icon .
The process may take several minutes. A progress bar opens at the bottom
of the window indicating the number of tunnels processed at any point out
of the total number defined by your selections.
The progress bar includes a Stop icon , which enables you to abort the
processing if required. The processing is aborted after the tunnel currently
in process is built.
6. When the tunnel building process is completed, a Results pane opens
showing the tunnels that were processed (succeeded or failed).
Select tunnel lines in this list (by highlighting one or selecting multiple
ckeckboxes or using the Select All icon) and click the Show Tunnel icon.
The Tunnel List window opens, displaying those tunnel(s). You can also
perform other operations on the listed tunnels; see Results Window.
7. Close the Full Tunnel Mesh Results (or Multiple Bypass Results)
window.

Automaton Windows
The Create Tunnel Mesh and Create Multiple Bypass window (also referred
to as Automaton windows) display information for tunnels corresponding to the
selected nodes. These windows are used during Tunnel Mesh and Multiple
Bypass tunnel setup.
The Create Tunnel Mesh window is shown below. The Create Multiple
Bypass window has the same layout but with different parameters enabled.
Create Tunnel Mesh and Multiple Bypass window toolbar icons

Open
Create Tunnel Mesh Opens a Create Tunnel Mesh window in
another view.
Create Multiple Bypass Opens a Create Multiple Bypass window in
another view.
Actions
Clear all settings Clears all PE or link selections and restores
all parameters to the system defaults.
Reset tunnel parameters Restores all parameters to the system defaults.
to defaults
Clear all endpoints and Removes all PE or link selections, but keeps
path any user changes to tunnel parameters.
Start Tunnels Creation Starts tunnel path finding on the selected PEs
or links and implements the new tunnels on
the network. (Automatic tunnel creation does
not include a Complete step. The Start
processing immediately implements tunnels
in the network.)


List
Select All Actions related to tunnels listed in the Results
Deselect All list. Enabled when results are generated and at
Show Tunnel least one tunnel is selected. For details, see
Results Window.
Show Selected
Show Info
Export to CSV
Print List
Help
Map View
The Map view is used to select elements for the relevant automaton operation.

The Basic Parameters pane enables you to configure the most basic tunnel
attributes. The panel parameters are the same as in the Create Tunnel window;
see Basic Parameters Pane. (The CoS parameter is different, as described
below.)
Automaton window Basic Parameters pane fields
Field Description
Protection Protection desired for all the tunnels being created by the automaton
Desired operation. As described in Create Tunnel Window Basic Parameters
Pane.
Select the required protection desired:
| Tunnel Mesh: Unprotected or Protected.
| Multiple Bypass: Bypass (other options disabled).
FRR Type FRR protection mode applying to all the bypass tunnels being

Field Description
created by the automaton operation. As described in Create Tunnel
Window Basic Parameters Pane.
Select the required FRR type:
| Tunnel Mesh: not relevant (disabled).
| Multiple Bypass: Node Protection or Link Protection.
Tunnel Name Enter a prefix string to represent all the tunnels being created by the
automaton operation. The remainder of the name is set
automatically, unique per tunnel. As described in Create Tunnel
Window Basic Parameters Pane.
Customer Enter the customer that applies to all the created tunnels. Can be left
blank. See Create Tunnel Window Basic Parameters Pane.
CoS Class of service for single tunnels is described in Create Tunnel
Window Basic Parameters Pane (mandatory for each request cycle).
Unlike the CoS for single tunnels, multiple CoS values can be
selected, as well as the order in which they should be applied.
LightSoft thereby calculates paths for each listed CoS values
according to their specified order. In the example below, a first
iteration is performed using CoS1 on the links/nodes specified in
the Selected Elements pane, then a second iteration using CoS3 on
the same links/nodes, according to BW availability and dictated by
CAC.
Click the field selector to open a dropdown list of CoS values and
select the required values, one at a time. The selected values are
marked in the list and entered to the field in the order they are
selected. You can deselect a value by clicking its value in the
dropdown list again.
BW (Mbps) As described in Create Tunnel Window Basic Parameters Pane.

Enter values that apply to all the created tunnels.
Comments Free-text comments.


The Advanced Parameters pane allows you to configure more specific
working tunnel attributes and to enable/disable OAM and alarm functions for
the new tunnel. The panel parameters are the same as in the Create Tunnel
window (except that Dual FRR is not relevant); see Advanced Parameters
Pane.
Automaton window Advanced Parameters pane fields
Field Description
Working Tunnel (not applicable for Multiple Bypass)
Tunnel Type P2P/P2MP radio buttons. As described in
Advanced Parameters Pane.
P2P option automatically applies.
Single Service Only checkbox As described in Advanced Parameters Pane.
P2P Service Only checkbox Applicable to Create Tunnel Mesh only.
Guaranteed FRR Desired
checkbox
Tunnel OAM and General Tunnel Alarms
Tunnel OAM (CV) As described in Advanced Parameters Pane.
Generate Tunnel Alarms

Selected Elements Pane

This pane lists the PEs or links across which tunnels or bypass tunnels are built.
(Tunnels already existing among the PEs are not shown in the list.)
Tunnels are built for each CoS listed in the Basic parameters pane and for
each node or link in the order listed in the Selected Elements pane:
| Create Tunnel Mesh: For each CoS, LightSoft creates tunnels for the first-
listed node bidirectionally to/from all other nodes in the mesh. LightSoft
then continues to the next-listed node, and so on.
| Create Multi Bypass: For each CoS, LightSoft creates:
For listed links - Next hop bypass tunnels bidirectionally to protect the
first-listed link; then continues to the next-listed link, and so on.
For listed nodes - Next next hop bypass tunnels bidirectionally to
protect the first-listed node over each combination of links that
traverses it. It then continues to the next-listed node, and so on.
The process continues as permitted by BW limitations and CAC. Objects at the
bottom of the list may therefore not be handled successfully because of
insufficient BW. Set the order of the objects according to required priority. You
can change the order by selecting an object and clicking the Up or
Down buttons to promote or demote them as needed.
Automaton window Selected Elements pane fields
Field Description
# Number indicating the priority of the nodes or links for which
PF is creating tunnels or bypass tunnels. PF handles the nodes
or links in this order, as permitted by BW limitations and CAC.
Link/Node Link or node.
ID Link or node user label.

Progress Bar
The progress bar appears at the bottom of the window when Start Tunnel
Creation processing is started. It indicates the number of tunnels processed at
any point out of the total number defined by your selections.
The progress bar includes a Stop icon , which enables you to abort the
processing if required. The processing is aborted after the tunnel currently in
process is built.
Results Window
The Full Tunnel Mesh Results window displays pathfinding results for the
selected tunnels. The Multiple Bypass Results window displays pathfinding
results for the selected Bypass tunnels. This window opens at the end of the
automaton Create Tunnel process, or it can be exposed by pulling up the
progress bar at the bottom of the window.
Full Tunnel Mesh or Multiple Bypass Results toolbar icons

Select All Selects all tunnels in the Results window.
Deselect All Deselects all tunnels in the Results window.
Show tunnel in Opens a Show Tunnel window in a different

another window view showing the specific tunnel in map view and
its parameters in the panes; see Show Tunnel in
Another View.
Show tunnel in Opens a Tunnel List window showing the
Tunnel List window selected tunnels; see Tunnel List Window.
Show Result Info for Displays detailed results for the selected tunnel
selected items line. See Performing Tunnel Operations.
Export tunnels to CSV Exports list data to a delimited format file like
CSV for import to Microsoft Excel or a relational
database application. See Exporting to CSV.
Print List Prints the contents of the Results pane. If tunnels
are selected, prints only these tunnels; see Print
Formats.

Full Tunnel Mesh or Multiple Bypass Results window contents
Column Notes
Selection checkbox. List menu options and the pane
icons are enabled when at least one tunnel is selected.
NMS Tunnel ID LightSoft tunnel identifier for this tunnel; see
description in General Parameters Pane.
Tunnel State Synchronization state for this tunnel (OK, Inconsistent,
or Incomplete). See Status Parameters Pane.
CoS Class of service; see Basic Parameters Pane.
Source PE PE at the Head of the tunnel.
Dest. PE Destination PE at the Tail of the tunnel.
LightSoft Result Result of the operation in LightSoft, for example Tunnel
Created.
EMS Result Result of the operation in the EMS, for example, All
XCs created in EMS.


12
Performing Actions on
Tunnels
In this chapter:
Overview ....................................................................................................... 12-1
Accessing the Tunnel List Window............................................................... 12-2
4
Tunnel List Window ...................................................................................... 12-4

4
Viewing Tunnel Information ....................................................................... 12-18

4
Performing Tunnel Operations .................................................................... 12-22

4
Actions on Bypass Tunnels ......................................................................... 12-23

4
Filtering the Tunnels Pane ........................................................................... 12-24

4
Reconnecting Tunnels ................................................................................. 12-35

4
Updating FRR Protection ............................................................................ 12-36

Modifying Tunnel Protection ...................................................................... 12-37
Editing and Deleting Tunnels ...................................................................... 12-38
4
Batch Tunnel Operations ............................................................................. 12-46

4
Overview
This chapter describes the tunnel management interface for ongoing tunnel-
related operations. A full range of operations on existing tunnels can be
performed using either the Tunnel List window or LightSoft main window
options.

Performing Actions on Tunnels LightSoft User Manual
Accessing the Tunnel List

Window
The Tunnel List window (see Tunnel List Window) opens with different
object combinations according to preselections in the LightSoft main window:
Tunnel List window map shows all objects and associated MoT virtual
links appear in the window map, including MPLS-relevant LEs,
automatically split out from their respective MCS MEs (consistent with
your user permissions) and their associated MoT virtual links.
Tunnels pane includes tunnels based on the default filter.
TIP: Opening the Tunnel List window may take less time if
you choose "No Tunnels" as the default filter. You can then
select a different filter. For details, see Applying a Filter and
Setting it as Default.
| If objects are preselected in the main window:

The Tunnel List window map opens with only those objects and their
immediately associated links/elements.
The Tunnels pane shows only the associated tunnels. In this case, a
User Preferences options also affect how tunnels appear in the Tunnel List
window view; see Options Pane in Tunnel Management Preferences).
A wide range of additional filter options are also available; see Filtering the
Tunnels Pane.
A variety of utilities are available from the Tunnel List window. These are
described in the button descriptions in Tunnel List Window.
You can open multiple Tunnel List windows simultaneously, each displaying
selected elements and view of the network, and allowing different tunnel
operations.

LightSoft User Manual Performing Actions on Tunnels
To open the Tunnel List window:

1. (Optional) For ease of work and improved performance in larger networks,
you can open the Tunnel List window with links running between a
limited number of PEs and corresponding limited tunnels in the Tunnels
pane. To do this:
Ensure that the appropriate tunnel filter is set as the default. For
information about available predefined filters and how to set one as the
default, see Filtering the Tunnels Pane.
OR
Select any combination of specific virtual links (MoT trails), physical
links, MEs, PEs, and EMSs for which to display tunnels in the main
window map or elements in the topology tree. (If more than one view is
open, the selections in the most recently opened view apply.) The
Tunnel List window map opens with only those elements and links,
and the Tunnels pane displays only associated tunnels. In this case, the
default filter is overridden.
2. From the Traffic menu, select Tunnels > Tunnel List.
OR
On the toolbar, click the Tunnel List icon .
Similar windows are used for creating and synchronizing tunnels; see
Provisioning MPLS Tunnels and Synchronizing Tunnels.
Tunnel List Utilities

You can perform the following tunnel procedures.
To view a tunnel route in the map view:

1. Select a tunnel in the Tunnels pane.
2. Click the Show highlighted tunnel on map icon or right-click and

select Show > Show Tunnel.
To show/hide the Tunnel Parameters/Endpoint/Path

panes:
| Click the Show/Hide Details toolbar icon.
To recalculate tunnel parameters:

| Some tunnel parameters (for example, Tunnel Length) show "On Demand"
as their value when first loaded. Click the Show On Demand Parameters
icon to calculate the current values.

Tunnel List Window

The Tunnel List window enables viewing and filtering tunnel information. It
features a graphical representation of all or preselected MPLS objects in the
ETH/MPLS topology layer, a filtered list of existing tunnels, and detailed
information about a selected tunnel.
For information about opening the window, see Accessing the Tunnel List
Window.
You can view parameters, endpoints, and paths of tunnels belonging to

multiple MPLS networks.
The window includes the following panes:
| Map View: Shows the elements and MoT links of the selected topology
view.
| Tunnels pane: Lists all or a filtered set of tunnels, and enables you to
select specific tunnels for various operations.
| Tunnel Parameters tab: Displays detailed information about a selected
tunnel, and enables you to modify some information.
Basic Parameters: Configures basic tunnel parameters.
Advanced Parameters: Configures more specific tunnel parameters.
Protection Parameters: Shows tunnel FRR parameters.
Status Parameters: Shows status-related parameters.
General Parameters: Shows general tunnel parameters.

| Endpoints & Path tab: Displays the endpoints of a selected tunnel.

Endpoints pane: Lists details of a tunnel's endpoints.
Paths pane: Lists details of each node along the tunnel path.
Inclusions pane: Lists explicitly included path characteristics.
Exclusions pane: Lists explicitly excluded path characteristics.
These panes are parallel to the same-name panes in the Create Tunnel process.
Some parameters from that process can be modified directly through the
Tunnel Parameters tab Edit Attributes function; see Tunnel Parameters
Tab. Tunnel bandwidth, protection, and P2MP service endpoints can be
modified; see Editing and Deleting Tunnels. For the parameter descriptions, see
the applicable sections in Creating Tunnels.
Tunnel List Menu and Toolbar

The following functions are available from the Tunnel List window menu and
equivalent toolbar icons.
You can select additional functions from other toolbar icons and selectors; see
Other Tunnel List Options.
Some functions are available from a shortcut menu, displayed by right-clicking
a row in the Tunnels pane; see Tunnels Pane Shortcut Menu.
Tunnel List menu and toolbar icons
option icon
Paint menu
Path Highlights the tunnel path on the map.

Explicit Highlights specific link/port inclusions or exclusions
Path on the map.
Path & Highlights both the tunnel path and specific link/port
Explicit inclusions or exclusions.
Path
List menu
Select All Selects all tunnels in the Tunnels pane.
Deselect All Deselects all tunnels in the Tunnels pane.
Load More Loads an additional increment of filter-defined

tunnels, up to a configurable limit. For information
about configuring the Load more tunnel limits,
contact ECI Telecom customer support.
Load All Loads all filter-defined tunnels in the network.


option icon
Refresh List Reloads the Tunnel List window and Tunnels pane,
showing newly created tunnels. All tunnels in the
Tunnels pane become unselected. Tunnels continue
to be listed according to the active filter.
Export to Exports the tunnels selected in the Tunnels pane to
XML an XML file for network planning or backup
purposes; see Exporting Tunnels.
Export to Exports list data to a delimited format file like CSV
CSV for import to Microsoft Excel or a relational database
application. See Exporting to CSV.
Print List Prints the contents of the Tunnels pane. If tunnels
are selected, prints only these tunnels; see Print
Formats.
Tunnel menu
Edit
Add Adds a subtunnel to a P2MP tunnel; see Adding
Subtunnel P2MP Tunnel Tail Endpoints.
Remove Removes a subtunnel from a P2MP tunnel; see
Subtunnel Removing P2MP Tunnel Tail Endpoints.
Edit Modifies the bandwidth of selected tunnels
Bandwidth regardless of their original specific bandwidths, to a
common value; see Modifying Tunnel Bandwidth.
Protection | Remove FRR Protection: Removes bypass
tunnel assignments from the selected protected
tunnels.
| Update FRR Protection: Assigns bypass
tunnels to the selected protected tunnels.
| Make Protected: Changes the Protection
Desired of the selected unprotected tunnels from
Unprotected to Protected.
| Make Unprotected: Changes the Protection
Desired of the selected protected tunnels from
Protected to Unprotected.
| Unassign: Unassigns the selected bypass tunnels
from all their protected tunnels.
For more information about Update FRR, see
Updating FRR Protection.
For more information about other functions, see
Modifying Tunnel Protection.
Delete
Delete Deletes the tunnels whose checkboxes are selected in
Tunnels the Tunnels pane from all databases (LightSoft and
from DB EMS). (If no tunnels are selected, deletes the
and highlighted tunnel. If tunnels are selected, deletes
Network only the selected ones.) For more details, see


option icon
Deleting Tunnels.
Delete Deletes tunnels from the LightSoft database only,
Tunnels leaving it intact in the EMS database; for more
from DB details, including purposes of this option, see
Only Deleting Tunnels.
Show
Show Shows selected tunnels and their associated objects
Tunnel by themselves in a new Show Tunnel window; see
Show Tunnel in Another View. This differs from the
function of the Show Tunnel icon in the Tunnels
pane toolbar, which highlights the currently selected
tunnel's path in the Tunnel List map view.
Show On Some tunnel parameters (for example, Tunnel
Demand Length) show "On Demand" as their value when a
Parameters tunnel is first loaded or configured. Clicking this icon
initiates a calculation process which displays current
values for all such parameters. (The process may take
some time.)
Show Opens the Service List window showing the services
Services defined on the selected tunnel; see Viewing
Associated Traffic Entities.
Show Trails Opens the Trail List window showing the trails that
the selected tunnel traverses; see Viewing Associated
Traffic Entities.
Show Opens a list of tunnels protected by a selected Bypass
Protected tunnel. This includes all the tunnels to which the
Tunnels selected Bypass tunnel was assigned, not only those
actively using the tunnel; see Viewing Associated
Traffic Entities.
Utilities menu
Performance | Current PM: Enables you to view current
Monitoring tunnel performance for 15-minute or 24-hour
intervals; see Trail Performance Monitoring.
| Multi Period PM: Opens the Multi Period PM
window, which enables flexible reporting of
historical PM counts; see Multi Period PM.
Other
Reconnect Reconnects incomplete tunnels selected in the
Tunnel(s) Tunnels pane. This operation may be required if
Tunnel State is Incomplete, for example if a PE was
disconnected while a tunnel is established in the
network; see Reconnecting Tunnels.
Current Opens the Current Alarms window showing alarms
Alarms that would affect the selected tunnels; see Viewing
Alarms for Selected Tunnels.


option icon
Synchronize Opens the Tunnel Segment Consistency (TSC)
Tunnels window for the tunnels selected in the Tunnels pane.
Tunnel synchronization is the process of reconciling
the differences between tunnel definitions in the
LightSoft database and the EMS. For more details,
see Synchronizing Tunnels.
4
Filter menu
Edit Filter Edits a filter. Enabled only if objects were
preselected in the main window before the Tunnel
List window was opened, or a user-defined filter is
selected.
Set Current Sets a filter as default.
as Default
Help menu
Other Tunnel List Options

selectors.
Other Tunnel List toolbar options
Toolbar Name Description

icon
Show Last Displays detailed results of the last operation.
Result Info Enabled only when the last-performed operation was
not completely successful. For more information, see
Hide/Show Alternately hides the left-side details panes, leaving
Tunnel Details only the Tunnels pane and the window map, or
reinstates the details panes. For more details, see
Filter selector Filters the Tunnels pane according to the selected
tunnel filter. For more information about tunnel
filters, see Filtering the Tunnels Pane.

Map View
The map view provides a graphic representation of all or preselected objects
and their associated MoT virtual links, with the relevant Ethernet LEs
automatically split out. When a tunnel is selected in the Tunnels pane, its path
is highlighted in the map view.
view, as described in Managing Elements, Groups, and Networks.
Tunnels Pane
The Tunnels pane lists a filtered set of tunnel records.
When the pane first opens, it displays up to 100 filter-defined tunnels. You can
use the Load more tunnel and Load all tunnels icons to load more
tunnels (see the toolbar icon descriptions below).
Click the Tunnel List window Reload whole tunnel list icon to reload the
Tunnels pane.
Clicking a tunnel in the pane makes it the focus of the information provided by
other panes. Highlighting a tunnel, or marking the checkbox of one or more
tunnels, selects those tunnels for various tunnel operations.
The Show highlighted tunnel icon enables viewing a selected tunnel's

path on the map; see the toolbar icon descriptions in Tunnels Pane Toolbar.
The following tunnel statistics are shown in the status bar:
| n/n (for example, 6/6): Number of tunnels filtered in/total number of
tunnels that can be displayed.
| n items selected: Total of selected tunnels (with marked checkboxes).

Tunnels Pane Toolbar

Tunnels pane toolbar

Load More Loads an additional increment of filter-defined tunnels;
see parameter in Tunnels Show menu in Tunnel List
Menu and Toolbar.
Load All Loads all filter-defined tunnels in the network; see
parameter in Tunnels Show menu in Tunnel List Menu
and Toolbar.
Show highlighted When selected (default when the window opens), and a
tunnel tunnel is highlighted in the Tunnels pane, the tunnel and
its endpoints are highlighted on the map. Information
about the tunnel is shown in the window panes. Deselect
the icon to disable this feature. This differs from Show
Tunnel List window toolbar option and the Tunnels
pane right-click option (see Tunnel List Menu and
Toolbar and Tunnels Pane Shortcut Menu), which shows
selected tunnels and their associated objects by
themselves in a new Show Tunnel window; see Show
Tunnel in Another View.
Show On Some tunnel parameters (for example, Tunnel Length)
Demand show "On Demand" as their value when a tunnel is first
Parameters loaded or configured. Clicking this icon initiates a
calculation process which displays current values for all
such parameters. (The process may take some time.)
Quick Filter Opens Quick Filter fields at the top of the pane, enabling
you to quickly filter the tunnels by Tunnel ID, name
and/or customer; see Creating a Quick Tunnel Filter.
Tunnels Pane Shortcut Menu

a row in the list.
These are the same options as in the Tunnel List window Tunnel menu, listed
under Edit, Delete, Show, Utilities, and Other submenus; see Tunnel List Menu
and Toolbar.

Tunnels Pane Columns

You can choose which columns to show in the Tunnels pane; see Showing,
Hiding, and Auto-Fitting Columns. Standard column sorting and ordering
operations can also be performed in the pane; see Working in LightSoft.
Tunnels pane columns
Column Description
Selection checkbox. Marking the checkbox of one or more

tunnels selects those tunnels for various trail operations (as
described in context).
The currently highlighted tunnel (whether or not the checkbox
is selected) is the focus of the information shown in the Tunnel
List window panes.
NMS Tunnel ID LightSoft tunnel identifier for this tunnel; see description in
General Parameters Pane.
Tunnel Name Name of the tunnel. For more details, see Basic Parameters
Pane.
Customer Customer associated with this tunnel. For more details, see
Basic Parameters Pane.
CoS Class of service. For more details, see Basic Parameters Pane.
BW (Mbps) Bandwidth of this tunnel. For more details, see Basic
Parameters Pane.
Protection Desired Protection desired for this tunnel (Unprotected, Protected, or
Bypass). For more details, see Basic Parameters Pane.
Protection Actual Actual protection applying to a protected tunnel. For more
details, see Protection Parameters Pane.
Dual FRR Value: Enabled/Disabled, or not applicable:
| For a bypass tunnel: Whether or not the bypass tunnel is
set to provide Dual FRR protection, based on the Dual FRR
radio button selection in the Advanced Parameters pane.
OR
| For a P2MP tunnel: Whether or not a dual FRR-enabled
bypass tunnel is assigned to the tunnel.
For details about Dual FRR, see Dual FRR for Link and Node
Protection.
Tunnel State Synchronization state for this tunnel (OK, Inconsistent, or
Incomplete). For more details, see Status Parameters Pane.
Tunnel Type Type of tunnel (P2P or P2MP). For information about these
tunnel types, see Tunnel Types.
MPLS Network ID MPLS Network ID of network where this tunnel traverses.
Source PE PE at the head of the tunnel.
Dest. PE Destination PE at the tail of the tunnel.

Column Description
Tunnel Usage Bypass tunnel: Number of underlying protected tunnels.

Protected or unprotected tunnel: Number of underlying VPNs.
Tunnel OAM (CV) Enabled/disabled state of Tunnel OAM. For more details, see
Single Service Only Whether this tunnel is restricted to a single VPN. For more
details, see Advanced Parameters Pane.
P2P Service Only Whether this tunnel is restricted to P2P VPNs. For more details,
see Advanced Parameters Pane.
Generate Tunnel Activation/deactivation status of alarm generation on this
Alarms tunnel. For more details, see Advanced Parameters Pane.
Actual No. of Hops Actual number of hops for this tunnel. For more details, see
General Parameters Pane.
Guaranteed FRR Whether FRR is guaranteed along the whole path of the
Desired protected tunnel. For more details, see Advanced Parameters
Pane.
Allocated BW Bandwidth allocated (reserved) for this tunnel. For more details,
(Mbps) see Status Parameters Pane.
Unreserved BW Unreserved bandwidth for the tunnel = BW minus Allocated
(Mbps) BW. For more details, see Status Parameters Pane.
FRR Type FRR protection mode applying to this bypass tunnel (Node or
Link protection). For more details, see description in Basic
Parameters Pane.
Protected Port Name of the port protected by a bypass tunnel.
Protected Node Next-hop node name (when the FRR Type is Node Protection).
PHOP If Dual FRR protection applies, PE ID of node which is the
penultimate (second to last) hop of the protecting bypass tunnel.
MPLS Label MPLS label for this tunnel. For more details, see General
Parameters Pane.
Comments Free text about the tunnel. For more details, see description in
Created By User Tunnel creator.
Created With Application the tunnel was created with - GUI (the LightSoft
EMS).
Creation Time Tunnel creation date and time.
Modified By User Tunnel modifier.
Modified With Application the tunnel was modified with - GUI (the LightSoft
EMS).
Modification Time Tunnel modification date and time.

Column Description
SRLG Diverse True indicates that the bypass tunnel path has no SRLG in
common with the protected link/node. For more details, see
Protection Parameters Pane.
Tunnel Parameters Tab

The Tunnel Parameters tab lists the main tunnel attributes defined in the
Create Tunnel process.
The All Parameters view (default) enables you to edit certain non-path
affecting parameters (see the enabled fields in the figures in the next sections).
Click the Edit Attributes icon (top right, enabled when a tunnel is
selected) to set the editable fields to Edit mode (white). The icon changes to a
Save Attributes icon , enabling you to save changes.
NOTE: Editing is restricted to non-path-affecting

parameters. You can also:
Add or remove tail endpoints of P2MP tunnels using the
Edit Tunnel window; see Adding or Removing P2MP
Tunnel Tail Endpoints.
Change tunnel bandwidth; see Modifying Tunnel
Bandwidth.

The User Selection view provides quick access to the most important attributes
and enables you to set tunnel preferences.
Click the Configure Attributes List icon (top-right) to display the User
Preferences window, where you can configure the attributes included in this
list and set other tunnel preferences. For more information, see Tunnel
The Tunnel Parameters tab information is provided in the following panes:
| Basic Parameters Pane
| Advanced Parameters Pane
| Protection Parameters Pane
| Status Parameters Pane
| General Parameters Pane

The Basic Parameters pane enables you to edit/view the most basic tunnel
attributes. For parameter descriptions, see the Create Tunnel Basic Parameters
Pane.


The Advanced Parameters pane allows you to view more specific working
tunnel attributes and to enable/disable OAM and alarm functions for a tunnel.
For parameter descriptions, see the Create Tunnel Advanced Parameters Pane.
Protection Parameters Pane

This pane shows the tunnel FRR parameters. For parameter descriptions, see
the Create Tunnel Protection Parameters Pane.
Status Parameters Pane

This pane shows operational, alarm, bandwidth and protection state-related
parameters. For parameter descriptions, see the Create Tunnel Status
Parameters Pane.

General Parameters Pane

This pane shows the general tunnel parameters. For parameter descriptions, see
the Create Tunnel General Parameters Pane.
Endpoints and Path Tab

The Endpoints and Path tab provides information about the tunnel route in
four panes. The parameters can only be viewed here.
The Endpoints and Path tab information is provided in the following panes:
| Endpoints pane
| Path pane
| Inclusions pane
| Exclusions pane
Endpoints Pane
This pane lists details of the tunnel endpoints. For parameter descriptions, see
Endpoints Pane.
TIP: P2MP tunnels - selecting a tail endpoint in the

Endpoints pane highlights the path represented by the
associated subtunnel in the map view. As well, any
inclusions/exclusions that the path involves are highlighted in
the Inclusions and Exclusions panes. (Not applicable to a
Head endpoint selection.)

Path Pane
This pane lists details of each node along the tunnel path. For parameter
descriptions, see Path Pane.
You can view bypass tunnel assignments per hop, or remove bypass tunnel
assignments; see Actions on Bypass Tunnels.
Inclusions Pane
This pane lists the path user selections comprising explicitly included path
characteristics. For parameter descriptions, see Inclusions Pane.
Exclusions Pane
This pane lists the path user selections comprising explicitly excluded path
characteristics. For parameter descriptions, see Exclusions Pane.

Viewing Tunnel Information

Selecting a tunnel in the Tunnels pane makes it the focus of the detailed
information provided in other panes. In addition, associated tunnels and other
traffic entities can be identified and associated alarms can be displayed.
Viewing Tunnel Information

The Tunnel List window opens with several information panes. One of these is
the Tunnels Pane, listing a filtered set of tunnel records.
When you click to select a tunnel in the Tunnels pane list, the tunnel becomes
the focus of the information provided by other panes.
When one or more tunnels are selected in the Tunnels pane, associated objects
and links are highlighted in the Tunnel List window map.
To view information about a tunnel:

1. In the Tunnel List window, ensure that a tunnel filter is selected, filtering
the tunnels you want listed in the Tunnels pane. For information about
tunnel filters, see Filtering the Tunnels Pane.
2. Click to select a tunnel in the Tunnels pane. By default, the Show icon
on the toolbar on the right is selected and:
about this tunnel.
The tunnel's associated elements and links are highlighted in the
Tunnel List window map.
NOTE: When you select tunnels in the Tunnels pane and

the Show one tunnel only option is selected in the
Preferences dialog box, the Tunnel List window map shows
only the associated elements and links, hiding all the others.
For more information, see Tunnel Management Preferences.
You can select tunnels in the Tunnels pane in two ways:

| Click and highlight the tunnel (as described in the previous procedure).
Using this method, you can select only one tunnel at a time.
| Select (or deselect) the checkboxes of any number of tunnels. This method
is used for operations such as delete, export, reconnect, show current
alarms, TCI, print, and so on. This procedure is described in more detail in
In this section, "selecting a tunnel" means selecting its checkbox.

Showing Tunnels Associated with a Link

You can show tunnels of a specified type associated with an MoT virtual link,
as follows:
| All tunnels, regardless of protection status.
| Protected tunnels (whether or not a bypass tunnel is defined)
| Bypass tunnels
To view tunnels associated with a link:

1. In the main window, select the ETH/MPLS view.
2. Select an MoT virtual link.
3. Right-click and select Show Tunnels.
4. Select the required option from the submenu:
All Tunnels
Protected Tunnels
Bypass Tunnels
The Tunnel List window opens, showing the relevant tunnels in the Trails
pane and the relevant associated objects in the map view.

Viewing Associated Traffic Entities

You can view which services, trails, or protected tunnels are associated with
the specific tunnel you are working on.
Show Tunnel in Another View

A selected tunnel can be opened in a separate Show Tunnel view, similar to
the Create Trail window but with read-only parameters.
This differs from the functioning of the Show Tunnel icon in the Tunnels pane
toolbar, which highlights the currently selected tunnel's path in the Tunnel List
map view; see Tunnels Pane Toolbar.
To view a tunnel associated with a link:

1. In the Tunnel List window, select a tunnel in the Tunnels pane.
2. Click the Show Tunnels in another window icon.

Or
Right-click a tunnel and select Show Tunnel. The Show Tunnel window
opens.

Show Associated Trails, Services, or

Protected Tunnels
You can view the following tunnel-related entities in their connected list
windows:
| Underlying services for a selected non-bypass tunnel.
| MoT Trails associated with a tunnel.
| Protected tunnels associated with a bypass tunnel.
You can also view the tunnels associated with selected services; see Viewing
Service Information - Viewing Associated Traffic Entities.
To view traffic entities associated with a tunnel:

1. In the Tunnel List window, select the checkboxes of the tunnels (or select
a single tunnel) for which you want to view associated traffic entities.
2. Select the following icon or right-click option:
Show services associated with this tunnel(s) icon, or right-click

and select Show Services. The Service List window opens showing the
associated services.
Show trails associated with this tunnel(s) icon, or right-click and

select Show Trails. The Trail List window opens showing the
associated trails.
Show Protected Tunnels icon, or right-click and select Show

Protected Tunnels.
A separate Tunnel List window opens showing the protected tunnels
associated with the selected bypass tunnels.
Viewing Alarms for Selected Tunnels

You can view all the alarms that affect selected tunnels. These alarms are
Traffic Entities.
You can also view the tunnels affected by a selected alarm; see Viewing Traffic
Entities Affected by an Alarm.

Performing Tunnel Operations

This section describes how to perform tunnel-related operations and view the
results.
To perform a tunnel operation:

1. Select the tunnels by selecting their checkboxes in the Tunnels pane.
2. Select a Tunnel List window toolbar option, or right-click a tunnel in the
Tunnels pane and select a shortcut menu option.
If the operation succeeded, an appropriate message opens.
If any part of the operation did not succeed, a results window opens,
giving information about the failed operations. If multiple tunnels are
involved, the window includes results for each tunnel.
Each time an operation is performed that is not completely successful,

the Operational Results Info icon in the Tunnel List window
toolbar becomes enabled. After you close the message window (here a
Tunnel successfully completed window), you can revisit the results by
clicking this icon.
The icon remains enabled until another operation is performed. If the second
operation is completely successful, the icon is disabled. If it is partially
successful, it displays the detailed results for that operation.

Actions on Bypass Tunnels

The following actions can be performed through the Path pane after a tunnel is
completed, or on an existing tunnel from the Tunnel List window:
| View/hide bypass tunnel assignment per hop.
| Remove bypass tunnel assignments.
NOTES:
Unassigning a bypass tunnel from a subtunnel, also
unassigns it from all subtunnels that share the bypass
tunnel.
Protection Desired is not affected by removal of bypass
tunnel assignments or failure to assign bypass tunnels.
(This is different from Trails, where a protected trail
means the main path is already protected by a protection
path. For tunnels, you create the protected tunnel
(protection desired), but it is not actually protected until a
bypass tunnel is assigned.)
To view/hide bypass tunnel assignment per hop:

1. Highlight one or more rows in the Path pane that represent tunnel segment
hops.
2. Right-click. The shortcut menu opens with the relevant options enabled.
3. Select Show Bypass.
Bypass tunnel paths for the selected hops are displayed on the map in blue
(this color overrides the pink and violet of the tunnel path in overlapping
links/nodes).
4. To clear bypass tunnel color coding, right-click the relevant rows and select
Hide Bypass.
To remove bypass tunnel assignments:

1. Highlight one or more rows in the Path pane, representing tunnel segment
hops with assigned bypass tunnels.
2. Right-click. The shortcut menu opens with the relevant options enabled.
3. Select Remove FRR Protection.
The Bypass tunnel information is removed from the corresponding row in the
Path pane. This option is relevant when Protection Desired is Protected AND
Bypass tunnel was assigned to that hop.

Filtering the Tunnels Pane

You can filter the Tunnels pane (determine the tunnel records that are
displayed) according to any combination of tunnel attributes and objects
activated from either predefined or created filters.
The following tunnel statistics are shown in the status bar:

| n/n (for example, 6/6): Number of tunnels filtered in/total number of
tunnels that can be displayed.
| n items selected: Total number of selected tunnels (with marked
checkboxes).
LightSoft supports the following predefined tunnel filters:
| All Tunnels: All tunnels are displayed (no filter is applied).
| No Tunnels: No tunnels are filtered in. After the Tunnel List window
uploads, you can apply a filter. (When this is the default filter, the Tunnel
List window initially opens quickly without any tunnels. Another filter
should then be applied; see Applying a Filter and Setting it as Default.)
| Unprotected (Desired): Tunnels where the Protection Desired is
Unprotected; see the parameter description in Basic Parameters Pane.
| Protected: Tunnels where Protection Desired is Protected.
| Bypass: Tunnels where Protection Desired is Bypass.
| Unprotected (Actual): Protected tunnels where Protection Actual is
Unprotected; see parameter description in Protection Parameters Pane.
| Full Node Protected: Tunnels where FRR Type Actual is Full Node; see
the parameter description in Protection Parameters Pane.
| Fully Protected: Tunnels where FRR Type Actual is Full Node Link.
| Partially Protected: Tunnels where FRR Type Actual is Partial.
| Bypass w/Node Protection: Bypass tunnels where FRR Type is Node
Protection.
| Bypass w/Link Protection: Bypass tunnels where FRR Type is Link
Protection.
| High CoS: Tunnels with high priority CoS; see Network Properties -
MPLS CoS Tab.

Filter options from the Tunnel List vs. main window

Tunnel List window.
You can use the Traffic menu Tunnels > Tunnel Filters option (or Tunnel
Filters icon ) to:
| Create or edit a new filter according to any combination of tunnel attributes
or objects; see Creating and Editing Advanced Filters.
| Edit, rename, or delete a filter that you created, or set it as the default
(which automatically activates it when the Tunnel List window opens); see
Rename, Delete, Set Default Filter Actions.
The Tunnels pane can automatically be opened with tunnels corresponding to
preselected objects in the LightSoft main window; see Accessing the Tunnel
List Window.
From the Tunnel List window:
| Use the Quick Filter icon to quickly filter by Tunnel ID, Name,
and/or Customer; see Creating a Quick Tunnel Filter.
any filter. You can also use the Set Filter as Default toolbar icon to set
the current filter as the default (automatically activated when the Tunnel
(The icon is disabled if the currently applied filter is already the default.)

| Show traffic entities associated with the selected tunnel(s):
Show Tunnels icon: Opens a selected tunnel in a Show Tunnel

view; see Show Tunnel in Another View.
Show Services Associated with this Tunnel icon: Filters tunnels
associated with specific services; see Show Associated Trails, Services,
or Protected Tunnels.
Show Trails Associated with this Tunnel icon: Filters tunnels
associated with specific trails; see Show Associated Trails, Services, or
Protected Tunnels.
Show Protected Tunnels icon: Filters tunnels protected by a
selected bypass tunnel; see Show Associated Trails, Services, or
Protected Tunnels.

Creating a Quick Tunnel Filter

The Quick Filter function enables you to quickly filter the tunnels in the
Tunnels pane, or throughout the database, by NMS Tunnel ID, Tunnel Name,
and/or Customer. This method does not involve a filter template and is defined
per use.
To quickly filter tunnels by NMS Tunnel ID, Tunnel Name,

and/or Customer:
1. Open the Tunnel List window, as described in Accessing the Tunnel List
Window.
2. In the Tunnels pane, click the Quick Filter icon . A quick filter field
bar opens at the top of the pane.
3. Enter a text string to the relevant fields to filter in tunnels with field values
that include this text.
NMS Tunnel ID; see parameter description in General Parameters
Pane.
Tunnel Name; see parameter description in Basic Parameters Pane.
Customer; see parameter description in General Parameters Pane.
You can enter partial strings to identify all tunnels with this text anywhere
in the fields. For example, enter xy to find all tunnels with xy anywhere in
the field value. (Wildcard character is not used.)
NOTE: The filter search is case sensitive.
The table immediately adjusts to show tunnels previously in the table

that satisfy the filter criteria.
OR


composition of tunnels displayed.
also backspace to empty a filter field.).


4

Working with Advanced Tunnel Filters

Advanced filters enable you to view a subset of the tunnels in the Tunnel List
| Tunnel attributes (like specific rates)
| Selected objects (all tunnels traversing specific objects)
settings to the open Tunnel List window. Any other filter can be applied as
needed at any time.

the tunnels listed in the Tunnels pane. In addition, the currently applied filter
can be set as the default, defining the tunnels that automatically appear when
the Tunnel List window opens in a new session.
TIP: Opening the Tunnel List window may be time

consuming if many tunnels are filtered in. If you choose "No
Tunnels" as the default filter, initially the window opens very
quickly without any tunnels in the Tunnels pane.
To apply a filter and (optionally) set it as default:

1. In the Tunnel List window, select a filter from the Filter dropdown list
.
The filter is immediately applied, reflected in tunnels listed in the Tunnels
pane.
2. Optional. You can set the current filter as the default by clicking the Set
filter as default icon . The Tunnel List window now automatically
opens with this filter in any new session.


Advanced filters are used to search the database for tunnels that satisfy the
filter criteria. The following describes how to create or edit a filter that includes

relevant. For information about how to create a filter with the
objects preselected in the LightSoft main window map, see
To create or edit a filter:

1. In the Traffic menu, select Tunnels > Tunnel Filters.
OR
On the main toolbar, click the Open Tunnel Filters icon . The Tunnel
Filters dialog box opens. (You can view a summary of parameters and
topology elements for an existing filter by selecting the filter in the Filters
pane.)


OR
Click the Show Tree button to open the Topology Tree pane (as shown in
the example). The button changes to a Hide Tree button for hiding the
tree if not required. This is used for filtering by selected objects in Step 5.
3. In the Filter Name field, type a name for the new filter (for example,
MyFilter).
OR
If you are editing, this field is disabled. You can save the changes for the
modified filter as a different name, if needed.
a. Select a parameter's checkbox in the Filter By area.
b. Specify the required value in the Value area. While a parameter is
highlighted, options are:

Radio buttons
displayed in the Value area .


If filtering by any text entry field, use the wildcard character *
to filter in all tunnels where the field value includes a
specified string, for example:
xy* to filter in all tunnels with the field value starting with
xy
*xy* to filter in all tunnels with xy anywhere in the field
value
*xy to filter in all tunnels with the field value ending with
xy (this pattern is not recommended).
OR
If any resource objects are selected in the Topology Tree area
(see next step), enter xy to find all tunnels with xy anywhere
in the field value. (Wildcard character is not used.)

these rules.
5. If you want to filter by selected resource objects with associated tunnels,

move objects from the Topology Tree area to the Topology tab, as
follows:
Select the topology layer for the filter: ETH/MPLS (default). The
Physical layer can also be selected, enabling you to select physical
nodes. Double-click the root of the tree to refresh its elements.
Select the objects for which you want to filter tunnels (drill down in
the tree). To select multiple objects, press SHIFT and click them
one by one.


Save.
OR
7. Click Close to close the Tunnel Filters dialog box.

You can also edit a user-defined filter via the Tunnel List window.
To edit a filter via the Tunnel List window:

1. Open the Tunnel List window as described in Accessing the Tunnel List
Window.


You can create a new tunnel filter with objects selected from the LightSoft
main window map. This avoids having to select the elements again when
creating the filter. These objects are automatically reflected in the Tunnel List
window map and in a "Temporary" filter which you can build on.

1. In the LightSoft main window map, select any objects that you want to
include in a new tunnel filter.
2. Open the Tunnel List window: From the Traffic menu, select Tunnels >
Tunnel List. Or, on the toolbar, click the Tunnel List icon .
(The icon is enabled only when the Tunnel List window opens with the
objects selected and the Temporary filter preselected in the Filter selector
dropdown list.)
the main window before the Tunnel List window was opened). The Edit
Topology pane. (The filter name is "Temporary" until you click Save As to
save under a different name.)


Rename, Delete, and Set Default Filter

Actions
This section describes how to rename, delete, or set a filter as default
(automatically applied when the Tunnel List window opens).

1. From the Traffic menu, select Tunnels > Tunnel Filters.
OR
On the main toolbar, click the Open Tunnel Filters icon . The Tunnel

(The New and Edit buttons are used to create and edit filters; for details,
see Creating and Editing Advanced Filters.)
3. Click Close to close the Tunnel Filters dialog box.

Reconnecting Tunnels
You may sometimes need to reconnect a tunnel. This is typically required if a
problem arises while you are creating one. For example, if a PE included in a
tunnel is disconnected at the time it is created, the resulting tunnel is left with
the Tunnel State being Incomplete. In this case, reconnecting the tunnel sends
the missing tunnel segments to the network.
To reconnect a tunnel:
1. Open the Tunnel List window, ensuring that the required main map
window objects are preselected and the desired filter is set as the default, as
described in Accessing the Tunnel List Window.
2. Select the checkboxes of the tunnel/s you want to reconnect by highlighting
a tunnel or selecting one or more tunnels by checking their checkboxes.
NOTE: Tunnel State should be Incomplete or Failed in order

for the operation to be meaningful.
3. Click the Tunnel Reconnect icon . A confirmation dialog box opens.
4. Click Reconnect Tunnels to continue. A completion message appears,

describing the operation result and listing nonfatal errors. For more
information, see Performing Tunnel Operations.

Updating FRR Protection

The Update FRR Protection option assigns bypass tunnels to the selected
protected tunnels. LightSoft searches for appropriate bypass tunnels and
assigns them to the selected tunnels.
You can also export selected tunnels to an XML file, defining that the import
of this file at a later time will automatically trigger bypass tunnel assignment
on these tunnels; see Exporting Tunnels.
The sequence in which you create tunnels and FRR protecting bypass tunnels is
important. You should first create FRR bypass tunnels, then create the tunnels
to be protected. LightSoft will then automatically assign the best-protecting
bypass tunnel that is available to each protected tunnel.
If a protected tunnel is created before an FRR bypass tunnel is available for it,
or if a bypass tunnel is removed (whether manually or as a result of an
automated process) the protected tunnel's Protection Actual may become
Unprotected. In this case, you should update the protection of those tunnels as
described below.
For information about FRR protection, see FRR Tunnel Protection.
For information about other FRR functions, see Modifying Tunnel Protection.
To update FRR protection:

1. Ensure that bypass tunnels of the intended type exist along the path to be
protected.
2. In the Tunnel List window, select the checkboxes of all protected tunnels
whose protection needs to be updated.
3. Right-click and select Edit > Protection > Update FRR Protection.
Only the options consistent with the tunnel selections are enabled. If the
selected tunnels include multiple types, no options are enabled.
An action window opens.
4. Click the action button. A completion window opens.
5. Click OK.

Modifying Tunnel Protection

You can modify the protection of existing tunnels without having to recreate
the tunnels. For example, you can assign bypass tunnels to one or more
selected tunnels.
To modify tunnel protection:

2. Highlight a tunnel or select the checkboxes of multiple tunnels on which
you want to perform the same operation.
3. From the shortcut menu, select Edit > Protection > and a protection
option:
Remove FRR Protection: Removes bypass tunnel assignments from
the selected protected tunnels. (In this case, Desired protection remains
protected, but Actual protection will be unprotected.) This is permitted
only if a bypass tunnel is not currently carrying traffic (FRR In Use is
No); see the FRR In Use parameter in Path Pane.
Make Protected: Changes the Protection Desired of the selected
unprotected tunnels from Unprotected to Protected.
Make Unprotected: Changes the Protection Desired of the selected
protected tunnels from Protected to Unprotected.
Unassign: Unassigns the selected Bypass tunnels from all their
protected tunnels. (Desired protection of those tunnels remains
protected, but Actual protection will be unprotected.)
For information about the Update FRR option, see Updating FRR
Protection.
Only the options consistent with the tunnel selections are enabled. If the
selected tunnels include multiple types, no options are enabled.

Editing and Deleting Tunnels

This section describes how to edit certain aspects of a tunnel, or to delete
selected tunnels:
| Adding or Removing P2MP Tunnel Tail Endpoints
| Modifying Tunnel Bandwidth
| Deleting Tunnels
NOTE:
Operations to add or remove a P2MP tunnel endpoint or
delete a tunnel may fail due to one of the following
circumstances:
LightSoft network values are different from the values in
the EMS/network. Tunnel consistency operations or
modifications in the EMS may be required.
2. Admit the tunnel from the network using
Synchronization.
LightSoft is unable to set up the tunnel in the network as
defined. This problem typically arises during tunnel
creation if an NE included in a tunnel is disconnected or a
craft terminal is connected, causing the resulting tunnel to
be incomplete.
To resolve this problem: After the NE is uploaded or the
craft is disconnected, reconnect the tunnel to send the
missing tunnel segments connects to the network.
Adding or Removing P2MP Tunnel Tail

Endpoints
This section describes how to add or remove subtunnels to/from P2MP tunnels.
Details of the Add or Remove P2MP Subtunnel action can be exported to an
XML file for backup purposes or to automatically assign bypass tunnels to
protected tunnels.
Changes to other tunnel parameters can be performed via the Tunnel List
window Tunnel Parameters tab Edit Attributes function. For details, see
Tunnel Parameters Tab.

Adding P2MP Tunnel Tail Endpoints
NOTE: Before beginning, ensure that the Show PEs and

Links Only Where Tunnel Traverses and Show endpoint
on map options are not selected in the Preferences dialog
box. If they are, no additional endpoints will appear in the
Tunnel List window map. For more information, see Tunnel
To add P2MP tunnel tail endpoints:

2. In the Tunnels pane, select a P2MP tunnel:
Select the tunnel and click Add Subtunnel on the toolbar.

OR
Right-click the tunnel and select Edit > Add Subtunnel from the
shortcut menu. The Add Subtunnel window opens. The tunnel path is
shown on the map, and the window panes are updated with the tunnel
information.
TIP: The Paint selectors enable you to identify and select the
endpoints or explicit path tunnel elements (segments or
nodes).

3. Select one or more additional tail endpoint LEs. Their details are reflected
in the Endpoints pane list.
Add Tail endpoints with or without Explicit Path Include/Exclude as
described in Creating a Tunnel.
4. (Optional) Click the Complete tunnel icon . LightSoft searches for a

path using your selections. When a path is found, the details are displayed
for you to review. You can go back and modify the path if required.
listing nonfatal errors. For more information, see Performing Tunnel
5. Click the Activate tunnel icon . LightSoft activates the changes on the
network.
At the conclusion of the Activate process, a message appears describing the
result of the operation and listing nonfatal errors. For more information, see
Performing Tunnel Operations. If the Activate step encounters a problem,
see Diagnosing a Create Tunnel Failure.
NOTE: If Complete Tunnel was not performed before or if

as a change of endpoint), it will automatically be
performed/repeated before the tunnel is activated on the
network.
6. You can export the edited tunnel to an XML file for backup purposes or to
automatically assign bypass tunnels to protected tunnels, as follows:
a. Click the Export icon on the window toolbar. The Export

Tunnels dialog box opens.
b. Continue the procedure as described in Exporting Tunnels, from Step 3.
For information how to eventually implement the edited tunnel in the
network, see Importing Tunnels.

Removing P2MP Tunnel Tail Endpoints

Follow these steps to remove P2MP tunnel tail endpoints.
To remove P2MP tunnel tail endpoints:

2. In the Tunnels pane, select a P2MP tunnel:
Select the tunnel and click Remove Subtunnel on the toolbar.
OR
Right-click the tunnel and select Edit > Remove Subtunnel from the
shortcut menu. The Remove Subtunnel window opens. The tunnel
path is shown on the map, and the window panes are updated with the
tunnel information.
TIP: The Paint selectors enable you to identify and select the
endpoints or explicit path tunnel elements (segments or
nodes).
3. Select one or more tail endpoint LEs to remove. Their details are removed
from the Endpoints pane list.

4. (Optional) Click the Complete tunnel icon . LightSoft examines the

remaining path after the endpoints are removed for bypass tunnel validity
and to ensure that any applicable FRR guarantees are satisfied. New bypass
tunnel assignments may be applied. The details are displayed for you to
review.
listing nonfatal errors. For more information, see Performing Tunnel
5. Click the Activate tunnel icon . LightSoft activates the changes on the
network.
At the conclusion of the Activate process, a message appears describing the
result of the operation and listing nonfatal errors. For more information, see
Performing Tunnel Operations. If the Activate step encounters a problem,
see Diagnosing a Create Tunnel Failure.
NOTE: If Complete Tunnel was not performed before or if

as a change of endpoint), it will automatically be
performed/repeated before the tunnel is activated on the
network.
6. You can export the edited tunnel to an XML file for backup purposes or to
automatically assign bypass tunnels to protected tunnels, as follows:
a. Click the Export icon on the window toolbar. The Export
Tunnels dialog box opens.
For information how to eventually implement the edited tunnel in the

Modifying Tunnel Bandwidth

You can modify the bandwidth of existing tunnels, regardless of their original
specific bandwidths, to a common value without having to recreate the tunnels.
To modify tunnel bandwidth:

2. Highlight a tunnel or select the checkboxes of multiple tunnels, right-click,
and select Edit > Edit Bandwidth from the shortcut menu.
The Edit Bandwidth dialog-box opens.
3. Enter a new bandwidth value to apply to all the selected tunnels. Enter the
value either directly or select it from the dropdown list.
4. Click Edit Bandwidth. A confirmation window opens.
5. Click OK to close the window.

Deleting Tunnels
This section describes how to delete tunnels. You can delete several tunnels at
the same time.
You can delete tunnels for either immediate or future effect in the network.
When the deletion is for future application, its details are exported to an XML
file and put into effect by importing the file into LightSoft at a later time; see
Exporting Tunnels.
All tunnels are deleted the same way, whether they were created in LightSoft or
created in the EMS and later uploaded to LightSoft using tunnel
synchronization.
Tunnels are generally deleted from all databases (both the LightSoft database
and the EMS network database). You can optionally delete a tunnel from only
the LightSoft database, leaving it intact in the EMS database. This may be
useful, for example, to perform repair or upgrade of the LightSoft database
without affecting traffic. In addition, this option has the effect of forcing a
tunnel segment inconsistency and causing the tunnel to appear in the TSC
window; see Synchronizing Tunnels.
Deleting a P2MP tunnel causes deletion of all its subtunnels.
When a tunnel is deleted, all tunnel segments defined for each PE in the tunnel
are also automatically deleted. If this does not occur (for example, if one of the
PEs is disconnected at the time the tunnel is deleted), the tunnel remains in the
Tunnel List window in an Incomplete or Failed state. The tunnel is removed
from the list when all tunnel segments are deleted from the network.
NOTES:
You cannot delete a tunnel as long as services still
traverse it. Services must be deleted before their tunnels.
You cannot delete bypass tunnels assigned to protect
working tunnels.
To delete a tunnel:
2. In the Tunnels pane, select a tunnel by highlighting it or select one or more
tunnels by checking their checkboxes.


a. If you want to delete the tunnels from all databases, click the Delete
Tunnel icon, or right-click any selected line in the Tunnels pane
and select Delete > Delete Tunnels from DB and Network. A
confirmation window opens.
Click the Delete Tunnels from DB and Network button to complete

the action.
OR
b. If you want to delete the tunnels from only the LightSoft database
(leaving them intact in the EMS database), right-click any selected line
in the Tunnels pane and select Delete > Delete Tunnels from DB
Only). A confirmation window opens.
Click the Delete Tunnels from DB Only button to complete the action.
NOTES:
If Bypass tunnels are assigned to protected tunnels, they
are unassigned and deleted.
Bypass tunnels that are actively protecting traffic are not
deleted.
A completion message appears, describing the operation result. For more

information, see Performing Tunnel Operations.
OR

4. If you want the tunnel deletion to be implemented in the network at a later

a. Click the Export icon on the window toolbar.

OR
Right-click one of the selected tunnels and select Utilities > Export
Tunnels from the shortcut menu. The Export Tunnels dialog box
opens.
Batch Tunnel Operations

This section describes how to perform Create, Update FRR, and Delete tunnel
operations in a batch by exporting and importing tunnel definitions to/from an
XML file.
| The Export operation enables you to save the data of selected tunnels in an
XML file for either network planning or backup purposes.
| The Import operation translates the data stored in the XML file and sends
this information to LightSoft according to the requested operation for each
tunnel in the file.
Records in the XML file specify the action commands and parameters. Both
import and export records coexist in the same XML file. For information about
the XML syntax, see Import/Export Traffic Syntax.
process. You can find this log file in the directory ~nms/NMSTunnels. The log
file name is the same as the XML file, with the extension .log.
You can also export/import service XML files via UNIX, which may include
prescheduling using the UNIX crontab command; see the generic trail, tunnel
and service export/import procedure in Exporting/Importing Traffic Entities via
UNIX.
OPTIONAL FEATURE: XML tunnel operations are

fully integrated add-on capabilities, available on a cost basis.
If not purchased, menu options pertaining to exporting and
importing tunnel definitions are unavailable.

Exporting Tunnels
This section describes how to export tunnel definitions to an XML file for
either network contingency planning and design purposes or backups in case of
system failure.
Exported tunnels are automatically implemented in the network by the Import
Tunnel definitions either from the Tunnel List window or in XML file format
can be converted to CSV for viewing in a relational database program. For
details, see Exporting Tunnels to CSV.

| For planned addition/removal of P2MP tunnel endpoints, see Adding or
Removing P2MP Tunnel Tail Endpoints. For this purpose the tunnels are
exported to XML using the Export Tunnels window's Export for Edit
mode.
| For planned deletion of existing tunnels; see Deleting Tunnels. For this
purpose the tunnels are exported to XML using the Export Tunnels
window's Export for Delete mode.
network. They are exported to XML until needed. When the new network
design is ready to be implemented, the planned tunnels may be imported to
LightSoft as part of the active network.

You can export tunnels so that they can be restored if inadvertently deleted or
corrupted:
| Tunnels that were deleted from the network can be restored by importing.
For this purpose the original tunnels must be selected from the Tunnel List
or Add/Remove Subtunnel window, and the export must be performed
using the Export Tunnels window's Export for Create mode.
| Existing tunnels that become corrupted can be restored by importing. For
this purpose the original tunnels must be selected from the Tunnel List or
Add/Remove Subtunnel windows, and the export must be performed
using the Export Tunnels window's Export for Edit mode.

Export Tunnels Procedure

You can export tunnels to an XML file for a variety of purposes:
| For backup or future planning, to be imported later to LightSoft as needed.
| To automatically delete selected tunnels at a future time.
| To automatically assign bypass tunnels to selected protected tunnels at a
future time.
NOTES: XML records are exported in the order that they

are displayed in the Tunnel List window, and are eventually
imported serially, in the same order.
To export tunnels to XML:

1. If you are creating an XML file for:
Backup purposes or automatic bypass tunnel assignment: From the
Tunnel List window, select one or more tunnels; see Performing
Tunnel Operations.
You can also perform this action from the Create Tunnel or Add
Subtunnel or Remove Subtunnel window on the current tunnel that
has just been activated; see Creating a Tunnel, or Adding P2MP Tunnel
Tail Endpoints, or Removing P2MP Tunnel Tail Endpoints.
OR
Deleting tunnels: From the Tunnel List window, select one or more
tunnels for deletion (but do not click Delete); see Deleting Tunnels.


OR
(If you are in the Tunnel List window) In the Tunnels pane, right-click a
tunnel and select Utilities > Export Tunnels from the shortcut menu. The
Export Tunnels dialog box opens.
3. Type the file name to which you want to export the tunnels, or select an
existing one from the dropdown list.
NOTE: The following characters (separated by commas)

are not allowed in the file name:
*, ?, !, |, \, /, ', ", {, },<, >, ;, <comma>, ^, (, ), $, ~, #, @,
<space>, +, =, &
4. If the file already exists, two radio buttons are enabled:

Select Overwrite file to overwrite the existing file, or
Select Append to file to add the tunnels to the existing file (preserving
its previous contents).

5. Select the Batch Operation to be applied on all the tunnels to be exported:

Backup purposes: Select Create.
Automatic bypass tunnel assignment: Select Update FRR.
Delete purposes: Select Delete.
6. Click Export. The tunnel definitions are saved as an XML file.
tunnel is processed. An Exporting Failed message opens. An export file
will be produced containing definitions of the tunnels that completed
processing up to that point.
Export Tunnels to CSV

You can export Tunnel List window data to a delimited-format CSV file for
subsequent import to Microsoft Excel or a relational database application.
LightSoft also enables you to export tunnels in XML files to CSV using a
command line application.
To export tunnels to CSV:

| See the generic procedure in Exporting to CSV.


Importing Tunnels
This section describes tunnel definition import from XML using LightSoft
menu options.
NOTE: Before importing tunnels, ensure that all the

required endpoints and resources are free and available. If any
are occupied, the Complete action, which is performed
automatically by the import, will fail.
To import tunnel definitions from XML files via LightSoft:

1. On the Traffic menu, select Tunnels > Import Tunnels.
OR
On the main toolbar, select Import Tunnels . The Import Tunnels

dialog box opens.

3. Select one of the following radio button options:

Check Syntax: Checks the syntax of the XML file.
Complete: Checks syntax and finds a path for the tunnels (like
Complete in the Create Tunnel procedure).
Activate/Delete: Checks syntax, finds a path, and activates the tunnels
in the network (like Activate in the Create Tunnel procedure). In the
case of a Delete mode XML file, checks syntax and deletes the
specified tunnels.
The mode defined when the XML file is exported determines the nature of
the action performed by the Import (Create, Update FRR, or Delete).
4. The file is imported and corresponding tunnels are reflected in the Tunnel
List window.
The Import Status pane shows the total number of tunnels in the import
and how many tunnels imported successfully or not.
tunnel is processed. An Importing Failed message opens. The tunnels that

13
Synchronizing Tunnels
In this chapter:
Overview ....................................................................................................... 13-1
Performing Tunnel Synchronization.............................................................. 13-3
4
Tunnel Segment Consistency (TSC) Window ............................................... 13-7

4
Tunnel Synchronization Window ................................................................ 13-10

4
Tunnel Consistency Use Cases .................................................................... 13-13

4
Overview
This section describes the tunnel synchronization process which reconciles
differences between tunnel definitions in LightSoft and tunnel definitions in an
EMS.
In general, new tunnel inconsistencies should be dealt with as they occur and
their causes investigated. The number of outstanding inconsistencies in the
system at any time should be kept to a minimum.
Inconsistencies between the LightSoft database and EMSs can develop over
time for a number of reasons, such as:
| Tunnels were created in LightSoft while the EMS was down.
| Tunnel segments were defined or changed at the EMS or craft terminal
level.
Tunnel synchronization functionality is available in accordance with user
permissions. It is not available for CNM users; see VPNs and CNMs.

Synchronizing Tunnels LightSoft User Manual
Viewing Tunnel Segment Consistency Status

Inconsistency information can be accessed using the following LightSoft main
window indication and icon:
When a red or yellow flag appears in the TSC window, click the flag and
then Show to display the cause of the failure. The window expands to
show the details of the failure, including the inconsistency cause. See Tunnel
Segment Consistency (TSC) Window.
Tunnel Segment Consistency (TSC) counter

flag of the counter
| The Tunnel Segment Consistency (TSC) counter in the main

window toolbar shows the total number of inconsistent tunnel segments.
The color of the counter indicates the worst condition of the inconsistencies
in the count. For information about color correspondences, see Severity
Breakdown Pane.
| The Tunnel Segment Consistency (TSC) icon opens the Tunnel

Segment Consistency window, where you can view detailed information
about inconsistencies.
The Tunnel Synchronization feature is composed of the following windows:
| Tunnel Segment Consistency (TSC) window: Begins the trail
synchronization process, providing warning flags colored according to the
type of detected inconsistencies, and counters that add up the number of
inconsistencies on each layer. See Tunnel Segment Consistency (TSC)
Window.
| Tunnel Synchronization window: Performs various synchronization
actions, both directly and via several floating windows. See Tunnel
You can perform synchronization in the TSC window in an automated fashion,
either by imposing tunnels defined in LightSoft on the EMSs, or by admitting
(acquiring) tunnels from the EMSs to LightSoft.
Alternatively, you can display inconsistencies in the TSC window but perform
synchronization manually in the Tunnel Synchronization window, where you
can select individual tunnels and decide whether to impose, admit, or delete
them. After completing and activating your changes, you can refresh the
information displayed in the TSC window to confirm that the inconsistencies
have been resolved, thereby indicating that the synchronization process was
successful.
The synchronization process is used to admit tunnels that do not conform to
normal trail patterns (flex trails) to LightSoft's Tunnel Management subsystem.

LightSoft User Manual Synchronizing Tunnels
NOTE: The TSC window opens with only tunnel segments

that involve inconsistencies, unlike the TCI window for trails
that can display consistent trails as well. You can force a
tunnel segment to be inconsistent in order to view it in the
TSC window. An easy way to do this is to delete the tunnel
from the LightSoft database using the Delete Tunnels from
DB Only option, leaving it intact in the EMS database. See
Deleting Tunnels.
Performing Tunnel
Synchronization
Tunnel synchronization can be performed for tunnel inconsistencies associated
with selected multilinks or objects, links in a multilink, or specific tunnels.
Only one LightSoft client can perform tunnel synchronization at any given
time.
To perform tunnel synchronization:

1. Open the Tunnel Segment Consistency (TSC) window, showing tunnel
inconsistencies associated with:
a. Selected multilinks and/or objects:
Select specific multilinks and/or objects on the main window map.
OR
Do not select anything in order to display all tunnel inconsistencies.
On the main menu bar Traffic menu, select Tunnels > Tunnel
Consistency.
OR
On the main toolbar, click .

OR
b. Selected links in a multilink:
Right-click a topology link and select Expand to display the
Actual Links between Two MEs dialog box.
Select the links.
Right-click the Link Name cell of any link and select Tunnel
Consistency. The TSC window opens.
OR

c. Specific tunnels:
In the Tunnel List window Tunnels pane:
Select the tunnels (checkboxes) you want to synchronize.
OR
Click and highlight the single tunnel you want to synchronize.
On the Tunnel List window toolbar, click .

OR
Right-click either the highlighted tunnel or one of the selected
(check marked) tunnels, and select Tunnel Operations > Tunnel
Consistency from the shortcut menu.
The TSC window opens; see Tunnel Segment Consistency (TSC) Window.
If you selected specific links or PEs on the map, the right pane of the
window displays a list of inconsistent tunnel segments related to all the
inconsistent tunnels connected with the preselections. Otherwise, all the
inconsistencies in the network are displayed. Select the tunnel segments
you want to synchronize by checking their checkboxes.
You need to select only one inconsistent tunnel segment per tunnel in order
to synchronize the whole tunnel.
You can select all checkboxes by clicking Select All or clear all by
clicking Clear All .
2. Click the Start icon .
NOTE:
Select Stop to discontinue processing after the current

tunnel is checked. Results are provided only for tunnels
processed up to that point and enable you to make decisions
about inconsistent tunnels in that group.
Select Abort to discontinue the entire operation. No

When the process is completed, the Tunnel Synchronization window

opens; see Tunnel Segment Consistency (TSC) Window.
It shows the inconsistent or incomplete tunnels associated with the segment
selections of the previous window, in two floating windows:
Inconsistent/Incomplete Tunnels – DataBase window: Shows the
tunnels that appear in the LightSoft database.
Inconsistent/Incomplete Tunnels – Network window: Shows the
tunnels that appear in the EMS.
A third floating window (Synchronization Results window) display
results of the process.

3. In the Inconsistent/Incomplete Tunnels – DataBase and Network

windows, select tunnels that you want to synchronize:
NOTE:
Window elements and relevant icons are enabled when the
associated window header (Database or Network) is
selected.
When a trail exists in both the Database and Network,
only one operation in one window can be assigned to the
tunnel per synchronization cycle.
Database window (listing tunnels in the LightSoft database):

a. Select checkboxes of tunnels that you want to synchronize.
b. For each selected tunnel, highlight the tunnel and select the
synchronization operation toolbar icon you want:
Reconnect: Reconnects the tunnel.
Impose to Network: Imposes the tunnel from the LightSoft

database into the EMS.
Delete from DB: Deletes the tunnel from the LightSoft

database.
AND/OR
Network window (listing tunnels in the EMS):
a. Select checkboxes of tunnels that you want to synchronize.
b. Set the order in which the tunnels are processed - promote or demote a
tunnel by highlighting it and clicking the and
buttons. The tunnels at the top of the window list are processed first.
This is significant when applying CAC on Classified tunnels, when the
first admitted tunnels are the first to be reserved BW resources.
c. For each selected tunnel, highlight the tunnel and select the
synchronization operation toolbar icon you want:
Admit to DB: Admit the tunnel from the EMS to the LightSoft
database.
Delete from Network: Delete the tunnel from the EMS

database.
As you select an action for a highlighted tunnel, the Selected Operation
column shows the operation name. For recommended actions, see
Tunnel Consistency Use Cases.

You can select all checkboxes of the window that is the current focus by
clicking Select All or clear all by clicking Unselect All .
TIP: You can select a tunnel in the Inconsistent Tunnels -

Database or Network window and click on Show on Map
to open a Show Tunnel window, where the tunnel is

highlighted on the window map and the tunnel parameter
values are indicated. For more information, see the icon
description in Tunnel Synchronization Window Toolbar.
4. Click Activate . The tunnels are synchronized according to the selected

options.
Select Stop to discontinue processing after the current tunnel is

checked; results are provided only for tunnels processed up to that point.
After the operation completes for each tunnel, the relevant row is removed
from the relevant Inconsistent/Incomplete Tunnels windows and a row is
added to the Synchronization Results window, displaying information in
the Operation Result column.
5. Close the Tunnel Synchronization window by clicking Close .
6. Return to the TSC window and click Refresh . The window is updated
with the new information.

Tunnel Segment Consistency

(TSC) Window
The tunnel synchronization process (see Performing Tunnel Synchronization)
begins in the TSC window, which displays information about tunnel segment
inconsistencies.
The window displays the total number of inconsistent segments and a
breakdown of the number of inconsistent segments per severity.
TSC window toolbar

Start Starts tunnel synchronization on the selected tunnels.
Stop Stops tunnel synchronization. The operation continues on

the tunnels processed up to that point, providing results for
these and enabling decisions to be taken concerning
inconsistent tunnels in that group.
Abort Aborts tunnel synchronization. The entire operation stops
at once and no results are provided.
Refresh Reloads the tunnels in the list of tunnels.
Select all tunnels Selects (checkmarks) all the tunnels in the currently
selected window.
Unselect all tunnels Clears all the tunnels in the currently selected window.
Close Closes the TSC window.

Severity Breakdown Pane

This pane displays the total number of SNC inconsistencies and a breakdown
of inconsistencies per severity level.
The following are the default color correspondences per severity. The colors
can be customized according to your needs; see Tunnel Management
Consistency Preferences.
For a description of the inconsistency types and corresponding possible
remedial actions, see Tunnel Consistency Use Cases.
Indications of warning flags

Red Critical - Non-editable parameters. Synchronization might be
traffic affecting.
Red Major - Editable parameters. Synchronization might be traffic
affecting.
Tan Minor - Editable parameters. Synchronization is not traffic
affecting.
Yellow Warning - Names-related. Synchronization is not traffic
affecting.
Gray Incomplete - Segment missing in network.

Selected Objects Pane

The Selected Objects pane of the TSC window lists the tunnel segments
involving inconsistencies in the system (or based on preselected objects). The
segments you select will be considered by the synchronization process.
The columns displayed can be varied as required. For more information, see
Selected Objects pane of TSC window
Column Description
# Ordinal number of the tunnel in the list.
Tunnel selection checkbox, used to select tunnels for
synchronization.
NMS Tunnel ID LightSoft tunnel identifier for this tunnel; see description in
Create Tunnel Window - General Parameters Pane.
Tunnel Name Name of the tunnel.
Customer Customer associated with the tunnel.
Incon. Severity Severity of the inconsistency, as described in Severity
Breakdown Pane.
Protection Type Protection Desired associated with the tunnel; see parameter
in Create Tunnel Window - Basic Parameters Pane.
PE Name PE ID of a PE endpoint associated with the tunnel; see PE in
Create Tunnel Window - Endpoints Pane.
CoS CoS associated with the tunnel; see parameter in Create
Tunnel Window - Basic Parameters Pane.
EMS Tunnel ID Number allocated by the EMS, uniquely identifying the SNC
within the EMS.
Detected At Time when the inconsistency was detected.

Tunnel Synchronization Window

This window opens after you click the Start icon in the TSC window to
start the Synchronization procedure (see Performing Tunnel Synchronization).
The Tunnel Synchronization window includes floating windows used in the

synchronization procedure. It shows the inconsistent or incomplete tunnels
associated with segment selections in the TSC window:
| Database window: Shows inconsistent/incomplete tunnels present in the
LightSoft database for which one or more segments were selected in the
TSC window.
| Network window: Shows inconsistent/incomplete tunnels present in the
EMS database for which one or more segments were selected in the TSC
window.
| Synchronization Results window: Synchronization results, whether
successful or failed.
When a tunnel is represented in both the database and the network, when you
select the tunnel line in one window, the same tunnel is highlighted in the other
window.
NOTE:
Window elements and relevant icons are enabled when the
associated window header (Database or Network) is
selected.
When a trail exists in both the Database and Network,
only one operation in one window can be assigned to the
tunnel per synchronization cycle.

Tunnel Synchronization Window Toolbar

Tunnel Synchronization window toolbar

Activate Activates synchronization on the tunnels with the Selected
Operation column not empty. When clicked, the following
confirmation prompt opens: "This operation may be traffic-
affecting. Are you sure you want to continue ?"
Stop Stops the synchronization process.
Reconnect Reconnects a tunnel (relevant for tunnels listed in the

Database window).
Impose to Imposes a tunnel from the LightSoft database into the EMS
Network (relevant for tunnels listed in the Database window).
Delete from DB Deletes the tunnel from the LightSoft database (relevant
for tunnels listed in the Database window).
Admit to DB Admits the tunnel from the EMS to the LightSoft database
(relevant for tunnels listed in the Network window).
Delete from Deletes the tunnel from the EMS (relevant for tunnels
Network listed in the Network window).
Select all tunnels Selects (checkmarks) all the tunnels in the currently
selected window.
Unselect all Clears all the tunnels in the currently selected window.
tunnels
Show highlighted Opens a new Show Tunnel window view, where the
tunnel on map tunnel that you selected in the Database or Network
window is highlighted in the window map, and the tunnel
parameter values are indicated. For the Fragment or
Unclassified inconsistency types, the tunnel or subtunnel
path may not be displayed, or displayed only partially. For
a description of the inconsistency types, see Tunnel
Consistency Use Cases.
Close Closes the Tunnel Synchronization window.

Tunnel Synchronization Floating Window

Columns
The following information columns are present in the floating windows, as
indicated.
Tunnel Synchronization floating window columns
Column Description
Tunnel selection checkbox for selecting tunnels for some
operations (described in context). Other tunnel operations apply
only to highlighted tunnels. A highlighted tunnel is the focus for
information shown in the Tunnel List window panes.
(DB and Network windows)
Selected Operation Operation selected by user: Impose, Admit, Reconnect, Delete.
(DB and Network windows)
Operation Applied Impose, Admit, Reconnect, Delete from Network, Delete from DB
(Results window)
Operation Result Succeeded or Failed.
(Results window)
Tunnel State Synchronization state: OK, Inconsistent, or Incomplete.
(DB and Results windows)
Inconsistency Inconsistency condition: Classified, Classified+, ClassifiedNet,
Type Unclassified, or Fragment. See Tunnel Consistency Use Cases.
(Network and Results windows)
NMS Tunnel ID Tunnel identifier. (All windows)
MPLS Label MPLS Tunnel Identifier assigned to enable a tunnel to traverse
multiple networks; see MPLS Label parameter in Advanced
Parameters Pane. (DB and Network windows)
Tunnel Name User-defined label for the tunnel. (All windows)
Customer Customer associated with the tunnel. (All windows)
CoS CoS associated with the tunnel. (DB and Results windows)
BW Tunnel bandwidth. (DB and Results windows)
Description Provides reason why operation failed.
(Results window)

Tunnel Consistency Use Cases

This section describes the main characteristics of each tunnel inconsistency
type for inconsistent or incomplete tunnels, and the corresponding possible
actions to resolve the problem. For example:
| A tunnel is considered Classified+ if it is in the LightSoft database and
classified in the EMS database, and the highest inconsistency level of any
component SNC is Warning or Minor (for a description of the possible
indications, see Severity Breakdown Pane).
| For tunnels with inconsistency type Classified+, possible actions to resolve
the inconsistency are to impose the tunnel to the EMS, admit the tunnel to
LightSoft, or delete it from the network.
Tunnel Inconsistency types and possible remedial actions
Tunnel In DB? Classified SNC inconsistency Unrecognized Possible Remedial

inconsistency in EMS? level segments? Actions
type
Inconsistent tunnels
Classified+ Y Y Warning or Minor N/A Impose, Admit, or

Delete from Net
Classified Y Y Major or Critical N/A Impose, Admit, or
Delete from Net
Unclassified Y N Major or Critical N/A Impose, or
Delete from Net
ClassifiedNet N Y Critical Y Admit, or
Delete from Net
Fragment N N Critical Y Delete from Net
Incomplete tunnels
Unclassified Y N Incomplete N/A Reconnect; see

or N/A Reconnecting
Tunnels
Additional comments
| LightSoft uniquely identifies a tunnel by its NMS Tunnel ID; see Create
Tunnel Window - General Parameters Pane. Connectivity can identify a
tunnel only if NMS Tunnel ID = Null, in which case LightSoft assigns an
NMS Tunnel ID during admission.
| New services can only be mapped to tunnels with Tunnel State = OK.
| CAC and SRLGs: MPLS SNCs created/edited in network are taken into
account in CAC calculations only if admitted by LightSoft.

NOTE: A bypass tunnel can be admitted whether or not it is

SRLG Diverse (SRLG Diverse means its path has no SRLG in
common with the protected link/node); see SRLG Diverse
parameter in Create Tunnel Window - Protection Parameters Pane.
| Protected Tunnel:
LightSoft may admit a protected tunnel without some or all of its
assigned Bypass tunnels. In this case, the Tunnel State of the Protected
tunnel is inconsistent.
LightSoft does not impose or admit a Bypass tunnel assignment for a
Protected tunnel, unless the Bypass tunnel:
Is in NMS DB and has Tunnel State = OK.
NOTE: It is therefore recommended to first Impose/Admit

the Bypass tunnels.
Meets node or link protection conditions.
Inconsistency types
When a tunnel state is Inconsistent, the tunnel is characterized by one of the
following Inconsistency Types, according to the nonconformance with the
Classification rules:
| Classified: Classified trail that fails admission due to CAC violation.
| Classified+: Classified trail whose synchronization is non-traffic-affecting,
for example, a Tunnel Name mismatch.
| ClassifiedNet: Classified in EMS but not in LightSoft (Network Only
Classified).
| Unclassified: Not meeting a combination of the above, or some other
classification criteria.
| Fragment: Group of one or more segments with identical unallocated
NmsTunnelId or Null, that do not form a Classified tunnel.

14
Provisioning Ethernet
Services
In this chapter:
Overview ....................................................................................................... 14-1
Ethernet Service Concepts ............................................................................. 14-2
Service Creation Management..................................................................... 14-12
Creating Ethernet Services .......................................................................... 14-13
Create Ethernet Service Window................................................................. 14-20
Managing Policer Profiles ........................................................................... 14-59
Overview
LightSoft provides network operators with end-to-end top-down provisioning
capabilities of carrier class Ethernet services.
LightSoft enables an operator to configure various types of Ethernet L1 and L2
services by configuring the attributes of the service and its endpoints -
LightSoft configures all the network provisioning parameters required
automatically.
Services are implemented over VCG trails in VC-12, VC-3, and VC-4
granularity, as the physical layer for any Ethernet service type. Each interface
is configured separately to provide maximum flexibility.
For example, in an MPLS network, a customer’s Ethernet traffic is transported
over MPLS tunnels that can be either shared or dedicated per customer. The
supported L2 services are P2P (VPWS), MP2MP (VPLS), P2MP (hub and
spoke or partial VPLS), and Rooted-MP IPTV-oriented services carried
efficiently by P2MP MPLS tunnels, all of which utilize advanced QoS and
traffic engineering mechanisms. For more specific information, see Supported
Ethernet Service Types.

Provisioning Ethernet Services LightSoft User Manual
For information about service provisioning in mixed networks of MCSs and

SR9700s, see LightSoft Aspects of SR9700 MEs.
OPTIONAL FEATURE: Ethernet services and RSTP

map functionality is subject to the ETH/MPLS layer being
enabled. This is a fully integrated add-on capability, available
on a cost basis. If not purchased, the functionality and related
menu options are unavailable.
Ethernet Service Concepts

The following sections provide some key Ethernet service concepts. Other
| Supported Ethernet Service Types
| Ethernet Transport Networks
| Services per Network Type
| Ethernet Service Endpoint Interfaces
| CoS for Ethernet Services
| Policing
| Service Discrimination
| S-VLAN Registration for a Service
| Pseudowire
| CAC for Ethernet Services
| Dedicated Tunnel Services
| Dual Homing
| Service Acquisition
| Service Non-Conformancy

LightSoft User Manual Provisioning Ethernet Services
Supported Ethernet Service Types

Ethernet services are provided in the following configurations:
L1 P2P Service
Point-to-point service between a pair of L1 Ethernet ports over an SDH trail
(also known as Ethernet Private LAN service, or EPL). Creating a trail between
the L1 Ethernet ports automatically creates the L1 Ethernet service.
L2 Services
| MP2MP (also known as Ethernet Virtual Private LAN service, or
EVPLAN): Multipoint-to-Multipoint service in which frames from each
service endpoint can be delivered to any other endpoint or can be multicast
to a set of endpoints. It is supported on PB Networks, on MPLS networks,
and on EA-HVPLS. It is implemented by VPLS on an MPLS network.
| P2P (L2) (also known as Ethernet Virtual Private Line service, or EVPL):
Implemented by VPWS on an MPLS network, associating exactly two
UNIs.
A UNI cannot be added to a P2P service to convert it to a MP2MP
service.
Services with two endpoints on a PB network may be defined as
MP2MP services. In this case endpoints can be added.
| P2MP (hub and spoke): Each service endpoint is either a hub or a spoke.
Hub and spoke service includes one to four hubs. Frames are delivered
from spoke to hub and hub to spoke. No frames are delivered directly
between two spokes. It is implemented by configuring tunnels in each
direction (or bidirectionally) between each spoke and the hub. Only
supported when all endpoints are on a single MPLS network.
| Rooted Multipoint (Rooted MP): A service typically used for multicast
service between a root and multiple leaves (for IPTV or E-Learning
services). A service endpoint is either a root or a leaf, with frames delivered
from roots to leaves and leaves back to roots. It is implemented in an
MPLS network by configuring a P2MP tunnel between the root and all
leaves. (As there is no multicast in EIS/MCS/BG-based PB Networks,
multicast is implemented by broadcast.)
LightSoft assumes that the networks and tunnels required to handle the service
are configured before the service is configured.

Ethernet Transport Networks

LightSoft supports Ethernet services on the following networks:
| Provider Bridge networks, using Bridge LEs connected with Ethernet I-
NNI (internal network to network interface) links; see Provider Bridge
(PB) Network.
| MPLS networks, using VPLS LEs connected with MPLS links; see MPLS
Network.
| Ethernet-Access Hierarchical VPLS (EA-HVPLS) networks; see Ethernet
Access Hierarchical VPLS (EA-HVPLS) Network.
For more information, see Supported Ethernet Service Types.
NOTE: EVC AND ESI SERVICE VIEWS

While specific L2 Ethernet service views are implementation-
/technology-independent, they involve different
implementation details according to the LightSoft-managed
network type. A service is generally called Ethernet Virtual
Connection (EVC) without its implementation details, or
Ethernet Service Instance (ESI) with all details required for
implementation. The "Ethernet services" addressed in this
User Manual refer to the latter. All details of the service
following configuration of the EVC parameters are
automatically completed.
Services per Network Type

The following service types are supported according to network type.
Service types supported by network type
Service type PB MPLS EA-HVPLS network

P2P service No Yes No
MP2MP service Yes Yes Yes
Rooted MP service No Yes Yes - Rooted MP in MPLS network
component with MP2MP in PB Access
components.
P2MP (hub and spoke) No Yes Yes - P2MP in MPLS component with
service MP2MP in PB Access component.

Ethernet Service Endpoint Interfaces

LightSoft supports L2 Ethernet service endpoints on the following interfaces.
(For a description of all data port types supported by LightSoft at the logical
level, Supported ETH/MPLS Port Types.)
ETY UNI
Comprising direct ETY UNI interfaces.
Ethernet remote UNI interfaces

On EoS trail creation between an Ethernet EoS UNI bridge or MPLS-PE
interface and an L1 Ethernet port (possibly on a UME), the L1 Ethernet port
becomes an ETY UNI remote interface to the Ethernet network, which can be
selected as a service endpoint.
ETY E-NNI interfaces

An ETY E-NNI interface can be selected as the service endpoint when a
prospective Ethernet service spans multiple provider networks. Frames on this
interface are double-tagged with the S-VLAN ID indicating the frame's
Ethernet service.
A network polices this service endpoint on ingress for each CoS. CoS support
in adjacent networks is likely to be different, so operators agree on a CoS
mapping for frames (for the MCS, mapping is by port).
E-NNI support differs between MPLS and PB networks, as follows:
| MPLS network: Since the MPLS network does not carry S-VLAN IDs,
multiple E-NNI endpoints to a specific service are handled and S-VLAN
IDs on different endpoints are independent. In effect, the network performs
S-VLAN ID switching between E-NNI pairs.
| PB network (implemented by EIS or MCS): S-VLAN ID at the E-NNI
must be the S-VLAN ID characterizing the service and is retained in all
frames for this purpose. There is no S-VLAN ID switching. This reduces
the flexibility of the E-NNI interface. This port type is supported by the
EISMB Bridge but not by the EIS.
Remote UNI (over EoS)

When an EoS trail connects a EoS UNI port to an L1 Ethernet port, the L1 port
acts as a UNI interface to the Network. Lightsoft supports configuration of
Service endpoints on such (Remote) ports.
Remote E-NNI (over EoS)

On EoS trail creation between an EoS E-NNI logical port and an L1 Ethernet
port (possibly on a UME), the L1 Ethernet port serves as an ETY UNI physical
interface to the Ethernet network and can be selected as a service endpoint.

Supported logical interfaces per physical port
Physical
Direct Over SDH
Logical
ETY EoS MoT
UNI
(remote UNI)
I-NNI (not currently supported

for MCS by Lightsoft) (remote I-NNI)
E-NNI
(remote E-NNI)
CoS for Ethernet Services

The frames of a service are assigned a Class of Service (CoS). The service
provider commits to provide a certain level of performance for each CoS. It has
two aspects:
| Priority for forwarding frames that exist at the switch, with some frames
having priority over other frames for forwarding.
| Priority for dropping, providing a criteria for dropping frames when non-
dedicated bandwidth is overbooked; see Service Overbooking.
Higher CoS values afford dependable bandwidth to more sensitive services
such as VoIP or IPTV. (High priority is less essential for HS Internet service
support.)
An Ethernet service classifies ingress frames to CoS categories of the network
carrying the traffic. The CoS categories may be from CoS0 (lowest) to CoS7
(highest), or represented by free-text display names configured for the network,
such as Gold or Platinum in place of CoS7 (for example, see Network
Properties – MPLS- CoS Tab). Ingress policing is performed separately for
each CoS. The C-VLAN Priority attribute is used to classify incoming frames
by CoS; see CoS Mapping Pane. The classification is per service and may take
into account the Ethernet (C-VLAN) priority of the frames.
Many services assign all traffic to a single CoS. Other services assign traffic to
multiple CoSs:
| Most prevalently, a port belongs to a single customer with the same CoS
(e.g., Silver) applying to all the frames (priorities are irrelevant).
| Alternatively, customer frames may be assigned to different COSs (for
example, HS Internet and VoIP) according to the required priority.
Frames carried over an MPLS network use a tunnel having the required CoS. In
this way, CoSs for services on this network are supported via the tunnel CoS.

Frames carried over a PB network implement CoS by assignment of S-VLAN

Priority (Priority0 to Priority7).
Services on an EA-HVPLS normally use the same CoS names for the MPLS
(core) network and PB Access networks. By default, MCS maps frames on an
I-NNI with S-VLAN Priority(n) to MPLS CoS(n) at a "gateway" MCS
(configured/viewed via the EMS). In this way, coherent CoS is easily
configured over the EA-HVPLS network. (Other modes of operation
concerning CoS coherence are possible.)
Policing
Each CoS of a service endpoint can be associated with a rate-enforcing policer,
which determines which frames of an incoming frames sequence should be
transmitted and which dropped (or possibly marked). Policer profiles
encapsulate all relevant bandwidth parameters at an Ethernet service endpoint.
For information about assigning policer profiles to CoS instances of a service
endpoint, see Policers Pane.
A service as a whole can be associated with a rate-enforcing policer profile for
BSC purposes; see Assigning a Policer Profile to a Service for BSC.
Service Overbooking
Overbooking (also known as oversubscription) usefully enables statistical
multiplexing whereby the sum of defined service bandwidth can exceed a link's
bandwidth capacity. For example, a 10 Mbps link can be allocated to 20
customers, each with a Committed Information Rate (CIR) of 1 Mbs. This is
accomplished by assigning less-than-maximal Class of Service (CoS) values to
services, in accordance with applicable Service Level Agreements (SLAs). This
is useful, for example, for Internet traffic where customers do not all demand
their bandwidth simultaneously.
To configure overbooking for a service:

1. Define Policer Profiles with parameters that would achieve transmission
performance in accordance with applicable customer SLAs; see Managing
Policer Profiles.
2. Define services with the required CoSs, in accordance with SLAs; see
Configuring the CoS Mapping.
3. Assign the policer profile that would achieve the contemplated level of
service to CoSs applicable to that service; see Assigning Policer Profiles to
CoSs of an Endpoint.

NOTE: For MPLS networks, a Booking Factor assignable to

each CoS sets a ceiling on the CIR that can be defined for a
policer profile. For more information, see:
Booking Factor parameter in Network Properties - MPLS
CoS Tab
Overbooking and Committed Information Rate (CIR)
Service Discrimination
A customer may have several services, where specific services may be
accessible by different internal department users (such as Development,
Marketing, Finance) or collaborating partners (such as system or component
manufacturers). Thus endpoints for multiple services can exist on the same
UNI or E-NNI interfaces. An secure and efficient mechanism is needed to
distinguish between frames belonging to each service. Hence:
| C-VLAN (C=Customer) tags on a frame (or the absence of a tag - untagged
frames) enable discrimination between services on a UNI interface. In
service endpoint configuration, LightSoft supports the definition of a list of
C-VLAN IDs at an endpoint to be associated with this service.
| S-VLAN (S=Service) tag on a frame enable discrimination between
different customers/services on an E-NNI interface, This is the same S-
VLAN Tag/ID used to discriminate between Services in a PB Network; see
Create Ethernet Service Window VLANs Pane.
S-VLAN Registration for a Service

Services on a PB Network must be S-VLAN registered on some or all of the
EoS links. LightSoft will typically register the S-VLAN on all links of the
Network when an individual service is created (see Automatic S-VLAN
Registration checkbox in Provider Bridge Networks Pane) or edited (see
Editing Services). When an individual service is registered in this way, the PB
network ports are configured with registration information, enabling all the
virtual links for the service.
S-VLAN registration is performed on I-NNI ports. Configuration of the ports
on which the S-VLAN is registered is performed in the EMS.
Links and connected nodes are normally color coded according to the most
severe alarm affecting any of their associated components, both link and node
indicating the same color; see Object Status Color Coding. However, a service
that it is not S-VLAN registered is shown in the map view in gray. (Only S-
VLAN registered services have the same color as their associated nodes. For
more information, see Create Ethernet Service Window Map View.
You can view the S-VLAN registered links in the system using the Show S-
VLAN Registered Links option; see Other Create Service Options.

NOTE: S-VLAN registration can also be performed at the trail

level when an EoS trail is created or edited. This avoids having to
manually register the S-VLAN at each of many services
individually so that they will be accommodated by the trail's ports.
This adds the S-VLAN registration to the virtual link, downloading
it automatically to each existing service in the network. For more
information, see the S-VLAN parameter in EoS/MoT Configuration
Pane and also S-VLAN Registration from a Trail.
Pseudowire
A single tunnel can carry multiple services. The Ethernet frames are
encapsulated in MPLS frames with a tunnel outer label (MPLS label) and an
inner label (VC label) indicating the service to which the frame belongs. The
traffic flow between a pair of VSIs for a specific flow can be regarded as a
pseudowire between these VSIs.
CAC for Ethernet Services

Connection Admission Control (CAC) for Ethernet services ensures that a
tunnel has sufficient bandwidth to allow the addition of an additional specified
service to the service while still providing the expected QoS. Service CAC
supplements MoT trail CAC mechanisms to facilitate effective QoS delivery by
MPLS networks. For details, see CAC for MPLS Tunnels.
Services are configured at each UNI with a policer profile. The policer CIR
specifies the overall Ingress bandwidth per CoS over all destinations. The
bandwidth between endpoint pairs is not configured.
LightSoft performs service CAC only for P2P services, based on a service
policer's CIR. The CIR specifies the bandwidth required by a P2P service to the
other service endpoint.
Service CAC is performed by segregating P2P services into tunnels that carry
only P2P services (the P2P Service Only checkbox is selected); see Create
Tunnel Window Advanced Parameters Pane. LightSoft automatically assigns
P2P services to dedicated tunnels.
LightSoft checks that the sum of service CIRs assigned to a P2P Service Only
tunnel does not exceed the tunnel bandwidth when:

| Adding a service to an existing tunnel.

| Increasing the CIR for an existing Ethernet service.
| Reducing the bandwidth of an existing tunnel.
Dedicated Tunnel Services

The operator can ensure bandwidth capacity for a MP2MP service between
given endpoints, by defining that the service uses dedicated tunnels. In this case
the whole bandwidth of the tunnel is dedicated to this particular service. Tunnel
CAC can then ensure the required QoS.
LightSoft facilitates this scheme via the following tunnel and service parameter
selections:
| Only one service uses a tunnel with Single Service Only selected; see
Create Tunnel Window Advanced Parameters Pane.
| A service with Dedicated Tunnel Only selected is assigned to Single
Service Only tunnels; see Create Ethernet Service Window Advanced
Parameters Pane.
Dual Homing
Dual Homing protects a pair of PE ports in an MPLS network that are each
connected to:
| Customer access equipment (CE) UMEs (Access Link Dual Homing)
OR
| PBs in a PB network (Internetwork Dual Homing)
For more information, see Configuring Dual Homing Protection.
Service Acquisition
This chapter describes service creation through the LightSoft interface.
Services can also be created at the EMS level, or modified using the EMS
regardless how they were originally created.
The EMS-created or modified services are automatically acquired to the
LightSoft database and are available for viewing and changes in the Service
List window, in the same way as LightSoft-created services; see Performing
Actions on Ethernet Services.
Acquired services (either newly created or involving EMS-initiated
modifications) are automatically assigned "Unacknowledged modification"
status, thereby flagging the service for review. The flag remains until the
modifications associated with the service are acknowledged; see
Acknowledging Service Modifications.

Acquired services or service modifications may be deemed to be non-

conformant; see Service Non-Conformancy.
Service Non-Conformancy
Acquired services or EMS-initiated service modifications may sometimes be in
conflict with LightSoft capabilities. Discrepancies may also arise when a
LightSoft-configured service is download to the EMS and possibly not all the
expected EMS-actions are correctly performed. In these cases service is
deemed to be non-conformant - similar in concept to trails that do not conform
to normal patterns (non-classified, or flex trails). For example:
| Acquired services may have different BSC parameter values at different
bridges. Actual BSC Policer Profiles and Thresholds may differ from the
default by EMS configuration. In this case, the service is considered
Nonconformant.
| An acquired service may be non-conformant with different CoS mappings
at different UNI endpoints. In this case, actual mappings are shown by
endpoint.
If a service's Actual Traffic State is Non-conformant, its Non-conformancy
Reason attribute provides the reason for the status; see Service Status Pane.
(These parameters contain information following service completion.)
You can convert the service to be conformant through appropriate editing; see
Editing Services. (In this case, services are handled differently than trails and
tunnels, where a synchronization process is used.)
When an existing service with non-conformant parameters is edited, the
modified value is configured for all LEs. The service then becomes conformant
on this parameter.

Service Creation Management

The User Preferences (Service Management) window determines how
LightSoft selects the tunnels on which prospective new Ethernet services are
built. Open and work with the window as described in Setting Traffic
Preferences.
The Tunnel Selection Criteria pane provides the following options:

| With Service CAC (applies to services where Service CAC is calculated;
see CAC for Ethernet Services):
Most residual bandwidth: PF prefers tunnels that have the greatest
amount of BW available, thereby enabling more services to be built
later on the same tunnels.
Min. residual bandwidth: PF prefers tunnels that have the least BW
available after the service is assigned, thereby minimizing unused
bandwidth in tunnels.
| Without Service CAC (applies to services where Service CAC is not
relevant):
Min. configured services: PF prefers tunnels that have the least
number of services already configured, thereby spreading out services
amongst available tunnels.
Max. configured services: PF prefers tunnels that have the greatest
number of services already configured, thereby concentrating services
on fewer tunnels.

Creating Ethernet Services

You can define Ethernet services directly from LightSoft using the Create
Ethernet Service window; see Creating a Service. Similar windows are used
for editing or viewing existing services; see Performing Actions on Ethernet
Services.
On PB networks, the operator need only configure general service
characteristics and the endpoints with their attributes. LightSoft then selects the
S-VLAN ID and determines how to implement the service on the PB network
using S-VLAN registration; see S-VLAN Registration for a Service.
In a similar fashion, in an MPLS network, the operator need only configure the
service endpoints. LightSoft can automatically determine the tunnels to be used
for the service and the inner tunnel labels used by the service; see Provisioning
MPLS Tunnels, and Provisioning Ethernet Services.
As part of the creation process, you can export the new service to an XML file
for backup purposes.
If Ethernet services and endpoints are provisioned through the respective EMS,
LightSoft acquires the associated information.
Creating a Service
Ethernet services can be created in the Create Ethernet Service window; see
Create Ethernet Service Window.
When creating a service, LightSoft uses only objects in resource domains
assigned to your user group (allowed by your user group's profile); see
Managing User Groups.
Conditions apply for service creation in a LAG configuration, such as pre-
configuration of ports in the EMS as LAG. For details, see LAG Support.
To create an Ethernet service:

1. (Optional) On the main window select the LEs containing the endpoints of
the intended service. This opens the Create Service window displaying
those objects and their associated links, rather than all the objects in the
current view.
2. From the Traffic menu, select Services > Create Service.
OR
On the toolbar, click the Create ETH Service icon . The Create
Ethernet Service window opens; see Create Ethernet Service Window.
The first time the window opens in a session may take longer than it does
subsequently.

3. If you want to create the new service based on saved global template
details:
a. Click the Load Global Template icon. The Load Global

Template dialog box opens.
b. Select an existing global template and click OK. The parameters and
path details from the template are applied to the current service. You
can change them if needed according to the steps below.
For information about creating (storing) new global templates, see Creating
a Global Service Template.
4. Enter the required service attributes. In particular, check the Type. You can
accept the default values or specify other service parameters; see Service
Details Tab:
Basic Parameters pane configures the service's identification, type,
and enabled status.
Advanced Parameters pane configures the service's vFIB quota, BSC
policer profile, tunnel type associations, and dual homing definition.
(Default values may be acceptable in most cases.)
(The Service Status pane shows the service's implementation and
operational status after it is completed. It does not require any inputs.)
5. Select and configure the service endpoints using the Endpoints Tab:
Endpoint List pane lists the selected endpoints for the service.
Select endpoints as described in Selecting Service Endpoints. To
configure the attributes of a specific selected endpoint, highlight it in
this pane.
CoS Mapping pane is used to map UNI or E-NNI endpoints of the
service to CoSs.
Policers pane is used to assign policer profiles to the selected endpoints.
VLANs pane used to maintain VLANs for the currently selected endpoint.
Multicast pane is used to specify multicast parameters for each Rooted
MP Leaf endpoint on a MPLS-PE.
TIP: For NNI ports, after two endpoints are selected, and
you fully configure one of the endpoints, you can copy and
paste the configuration to the other endpoint. For more
details, see Selecting Service Endpoints.
6. Configure network-related service parameters using the Networks tab. The

MPLS Network pane or Provider Bridge Networks pane in the Networks
tab are relevant when the service is configured on a network of the
appropriate type. An input is generally required only in the case of manual
tunnel selection.

7. (Optional) Click the Complete service icon . LightSoft makes a

selection from amongst the candidate tunnels using your selections. Its
details are displayed for you to review. You can go back and modify the
service parameters if needed.
At the end of the Complete processing, a message window describes the
Performing Service Operations.
Create Service Failure.
8. (Optional) You can create additional services with similar service details on
the same endpoints without having to redefine the service properties, as
follows:
NOTE: This procedure is based on a local template stored in

temporary memory of the user session. For information about
using global templates stored in the database, see Using
Global Service Templates.
a. Click the Store Local Template icon . The service details are
stored in temporary memory of the user session for use during the
current session only.
b. Activate or export the service, as described in the next two steps.
c. Create an additional service, as described in the final step.
NOTE: Do not close the Create Service window before

creating the additional services, as this erases the local
template.
9. If you want the new service to be implemented immediately, click the

Activate service icon .
If you want to export to XML instead, postpone Activation and go to the
next step.
At the end of the Activate processing, a message window describes the
Create Service Failure.

NOTE: If Complete Service was not performed before, or if

it was followed by an action that would change the links used
by the service (such as a change of endpoint), it will
automatically be performed/repeated as part of the Activate
process.
10. You can export the new service to an XML file for backup purposes. The
XML file that is produced can be imported to LightSoft as the need arises.
Click the Export icon on the window toolbar (enabled after the
service has been activated). The Export Services dialog box opens.
Continue the procedure as described in Exporting Services, from Step 3.
11. If you want to create an additional service with the same service details as
the current service based on the local template (you clicked the Store Local
Template icon after the service was completed):
a. Select the Clear and Reset icon to clear the service contents
(this step is required if Show Activated Services is set to ON).
b. Click the Restore Local Template icon .

c. Select the endpoints again.
d. Perform Step 4 through 10 to implement (or export) the additional
service. The service parameter and endpoint selections will already be
set to the previous service's settings. You only need to implement the
differences in settings, if any.
e. If another similar service is required, repeat this step.

Using Global Service Templates

Global service templates can be used to streamline the service creation process.
New services with similar parameters and path details can be set up using a
template stored in the database. Once created, the template details can be
applied to the Create Service window and only specific parameters changed as
needed for a new service.
This supplements the Local service templates functionality, which saves
service information in flash memory to use for creating services based on a new
service defined in the current session only.
To create a global service template:

1. Perform the new service creation procedure (see Creating a Service) up to
the point of Completing the service.
2. Click the Save Global Template icon. The Save Global Template
dialog box opens.
3. Enter a name for the template.

4. Click OK. The template is saved.
To create a new service based on a global template:

1. Open the Create Ethernet Service window (see Creating a Service).
2. Click the Load Global Template icon. The Load Global Template
dialog box opens.
3. Select an existing global template from the list.

4. Click OK. The parameters and path details from the template are applied to
the current service.
5. Change details as needed and Complete and Activate the service as
described in the generic service creation procedure (see Creating a Service).

Diagnosing a Create Service Failure

If the Create Service operation fails, perform the following verification steps.

2. Check if all the endpoints are correct, if tunnels exist between all endpoints
with available bandwidth, and if the selected tunnels are appropriate.
4. If completion fails due to one or more required tunnels being unavailable,
verify that the configurations of tunnels selected by LightSoft for the
service are compatible with the intended service's attributes; see Networks
Tab - MPLS Network Pane.
5. Check the parameters selected in the Create Service window.
If the service failed at the Activation stage (Completion

succeeded):
2. Check if all VSIs/FDFrs were created at the EMS level.
3. Verify that all the relevant networks are uploaded in EMS and LightSoft.

Actions Performed by Complete and Activate

Complete
The Complete operation does the following (parameters set manually or
calculated by LightSoft during configuration are not changed):
| Derives the MPLS and PB networks on which the service is implemented.
| Selects an appropriate tunnel.
| Selects S-VLAN ID for each PB network.
| Performs automatic S-VLAN ID registration on all links of Ethernet
networks where the service is defined.
The Networks and the tunnels selected for a Service are displayed in the
Networks pane. At this point the service has not yet been saved to the database
or downloaded to the EMS.
Activate
The Activate operation configures the EMSs for the services as follows:
Service creation (MPLS network):
| Selects a VC label.
| Creates a VSI at each PE for the service in the network.
| Creates a UNI or E-NNI service endpoint, where required.
| Attaches the service to the selected tunnels.
Service creation (PB network):

| Selects a VC label.
| Creates a VSI for each LE in the network for each MTNM-defined service.
| Transmits flow points of the VSI as attributes of the VSI creation
transaction.
| Creates policers on the Bridge point where Ethernet Remote UNIs are
connected.
Other:
Adds/deletes/modifies a service endpoint by updating the VSI for the LE at
which the endpoint is defined.
For each bridge and MPLS-PE on which the service is defined, on service
enable/disable, sets the service's Administrative State to Enable/Disabled.
At this point the service is saved to the database and downloaded to the EMS.
EMS implementation depends on the module type.

Create Ethernet Service Window

The Create Ethernet Service window provides a graphical representation of
all or preselected LEs in the currently active topology layer, as well as
information and configuration panes.
The Create Ethernet Service window includes the following service

configuration panes and tabs:
| Map View: Provides a graphical view of service-relevant objects in the
network.
| Service Summary Pane: Provides excerpted summary details of service
parameters.
| Service Details Tab: Configures the service identification, type, and
applicable quota, policer profiles, tunnel types, dual homing type, and
service status parameters.
| Endpoints Tab: Configures the services endpoints, and associated CoS
mappings, VLANs, policer profile assignments, and multicast parameters.
| Networks Tab: Enables viewing and in some cases setting of network-
related service parameters.

Create Service Menu and Toolbar

Below are the functions available from the Service List window menu and
equivalent toolbar icons. Other functions are available from additional toolbar
icons and selectors; see Other Create Service Options.
Create Ethernet Service window menu and toolbar icons
Menu option Toolbar Description

icon
Actions menu
Clear Endpoints Clears selected endpoints, but keeps any
user changes to service parameters.
Reset Parameters Restores service parameters to system
defaults.
Clear Endpoints and Clears endpoints and resets parameters to
Reset Parameters system defaults.
Show Info Displays detailed results of the last
operation; see Performing Service
Operations.
Show RSTP Map Opens the RSTP Map window. This shows
the parts of the tree used by traffic between
the endpoints of an Ethernet service,
enabling you to understand current traffic
flow; see Viewing RSTP Information.
Export to XML Exports the service configured in the
Create Service window to an XML file,
leading into the export procedure described
in Exporting Services. Exported data can be
imported to create tunnels at a later time;
see Importing Services.
Complete Service LightSoft makes a selection from amongst
the candidate tunnels using your selections
and network configuration. If successful,
the all links carrying selected tunnels or
EoS links for which S-VLAN registration is
performed are highlighted on the map.
Nothing is saved to the database at this
point or sent to the EMS.
Activate Service Causes implementation of the new service
in the network. This option can be used
even if Complete service was not
performed.
If successful, the NMS sends information to
the EMS, which saves service information
in LightSoft and EMS databases. Live
traffic can now traverse the service.


icon
Templates menu
Store Local Template Stores current service parameters and
endpoints as a template in flash memory,
for use to create a similar service during the
current Create Service session; see Creating
a Service.
Restore Local Restores service details from the template
Template in flash memory to the Create Service
window, enabling you to create additional
services with similar parameters and
endpoints as the stored service; see Creating
a Service.
Save Global Template Saves a service template in the database for
later use (in this or another session) to
create new services with similar parameters
and path details; see Using Global Service
Templates.
Load Global Loads details of a saved service template to
Template the Create Ethernet Service window in the
process of creating a similar service; see
Using Global Service Templates.
Help menu
Other Create Service Toolbar Options

selectors.
Other Create Ethernet Service toolbar options

Show Activated If selected (toggled on), the service is
Service shown in the window map immediately
after activation by default.
Show S-VLAN ID Shows the S-VLAN registered links in
Registered Links the system. For information about S-
VLAN registration, see S-VLAN
Registration for a Service.

Map View
The map view provides a graphical representation of all or preselected LEs in
the currently active topology layer. It is used in the process of service endpoint
selection, and assists visualization of the Create service process.
When viewing a service the Map view shows the following:
| Bridges and MPLS-PEs represented by differing icons.
| All Ethernet I-NNI links and MPLS I-NNI links.
| Remote Ethernet UNI links.
| Service endpoints, including ETY UNI and E-NNI ports.
| Highlighted service-related objects, including:
MPLS-PEs used by the service.
I-NNI MPLS links bearing tunnels used by the service, as well as any
associated aggregated link.
I-NNI links on which the service is S-VLAN ID registered.
Bridges terminating an S-VLAN ID registered link.
NOTE: Links and connected nodes are normally color coded

according to the most severe alarm affecting any of their
associated components, both link and node indicating the
same color; see Object Status Color Indications. In some
cases the link or node are shown in gray:
A link is gray if it is not S-VLAN registered. (S-VLAN
registered links have the same color as their associated
nodes.)
A node is gray if it has an endpoint in a UME. (Nodes
containing service endpoints have the same color as their
associated links.)
Service Summary Pane

The Service Summary pane provides summary details of the service
parameters. The parameters appear in the pane after Complete or Activate is
performed.

Create Ethernet Service - Service Summary pane fields
Field Description
EthVPN ID Integer assigned sequentially by LightSoft on Complete or
Activate that uniquely identifies the Layer 2 service; see
parameter in Trail List Window - Services Pane Columns.
Label Name of the service; see parameter in Basic Parameters Pane.
Customer Customer associated with this service; see parameter in Basic
Parameters Pane.
Type Type of service; see parameter in Basic Parameters Pane.
Endpoints Concatenated endpoint names; see parameter in Endpoint List
Pane.
Actual Traffic State Value assigned by LightSoft when the service is activated; see
parameter in Service Status Pane.
Service State LightSoft indicates if the service is considered Up, Down, or
Unknown; see parameter in Service Status Pane.
Service Details Tab

The Service Details tab enables configuration of the service identification,
type, and applicable quota, policer profiles, tunnel types, dual homing type, and
service status parameters.
The tab includes the following panes:

| Basic Parameters pane, used to configure the service's identification, type,
and enabled status.
| Advanced Parameters pane, used to configure the service's vFIB quota,
BSC policer profile, tunnel type associations, and dual homing definition.
(Default values may be acceptable in most cases.)
| Service Status pane, which shows the service's implementation and
operational status after it is completed. It does not require any inputs.


This pane is used to configure the service's identification, type, and enabled
status.
Service Details tab – Basic Parameters pane fields
Field Description
Label Name of the service (need not be unique). Enter a name or select one
from the list (of recently used labels). If no name is specified, a name
is automatically assigned showing endpoint details and a timestamp.
(Optional)
Customer Customer associated with this service (need not be unique). If no
name is specified, the name is left blank. (Optional)
Type Type of service, selected from the dropdown list:
| P2P
| MP2MP - default for a new type
| Rooted MP
| P2MP (hub and spoke)
For descriptions of the service types, see Supported Ethernet Service
Types.
Service type support varies according to network type; see Service
Types per Network Type.
Administrative When selected (default), the service is enabled in the network when
Service Enable it is successfully activated. When cleared, all Virtual Switch
checkbox Instances (VSIs) of the service are initially configured as disabled.
The service can be enabled or disabled after activation using the
same checkbox in the Service List window.


This pane is used to configure the service's vFIB quota, BSC policer profile,
tunnel type associations, and dual homing definition. (Default values may be
acceptable in most cases.)
Service Details tab – Advanced Parameters pane fields/checkboxes
Field Description
vFIB Quota Maximum number of MAC addresses that can be learnt per VSI
supporting the service. Not relevant for P2P services.
Default is the value for the previously configured service, or 100.
LightSoft configures this quota at all LEs for this service.
LightSoft verifies that the quota does not exceed the vFIB quota
of the associated bridge (defined in the EMS system). If it does,
the service configuration is disallowed.
For bridges not supporting vFIB quota, EMS ignores the setting.
The vFIB quota for an existing service can be edited using the
same field in the Service List window.
For MCS cards, up to 65,535 entries are allowed for VSI.
BSC (Broadcast Storm Policer profile that applies to this service for BSC purposes. For
Control) Policer information about this concept and how to assign a BSC policer
Profile profile to a service, see Assigning a Policer Profile to a Service
for BSC.
For information how to create or edit policer profiles, see
Managing Policer Profiles. As well as for BSC, policer profiles
are also used to monitor bandwidth at each CoS instance of a
service endpoint; see Policers Pane.
Dedicated Tunnels Ensures that the service will be carried on Single Service Only
Only checkbox tunnels with bandwidth specifically configured for this service.
Enables Service CAC to be performed for a MP2MP service.
Relevant for multipoint services (MP2MP and Rooted MP).
(Default is not selected.)
Protected Tunnels Ensures that the service can only use protected tunnels. (Default
Only is not selected.)
Dual Homed Service Enables a choice of dual homed service type for configuring a
checkbox dual homed service. Option is available when the current service

Field Description
uses protected and nondedicated tunnels.
Select a dual homed service type radio button:
| Dual Homed Access Link Service
| Dual Homed Internetwork Link Service
For information about the Dual Homing concept, see Dual
Homing.
For details how to implement dual homing, see Configuring Dual
Homed Protection.
For Dual-homed services, the service type is always P2P and the
frame selection is always BPDU (not C-VLAN ID).
Advanced Parameters pane valid checkbox combinations
Advanced Parameters pane checkboxes to select

per scenario
Valid Use Cases Dedicated Protected Access Inter-
Tunnels Only Tunnels Only Link network
Link
Regular Service
Unprotected Tunnels
Protected Tunnels
MP2MP Dedicated Service
Unprotected Tunnels
Protected Tunnels
Dual Homed Service
Access Link
Internetwork Link

Assigning a Policer Profile to a Service for BSC

A Broadcast Storm is a condition where a large number of broadcast frames are
propagated across the (provider) network, thereby causing network overload.
Most bridges support Broadcast Storm Control (BSC), where incoming frames
not handled as unicast are metered by the assigned BSC policer profile for the
service. When the number of broadcast frames exceeds a threshold, the frames
are discarded.
When BSC is configured for the service, LightSoft configures its traffic
parameters and thresholds at all bridges at which the service is defined and which
support BSC. (If a bridge does not support BSC, the BSC parameter is ignored.)
When BSC is not enabled for a service (default), LightSoft disables BSC at all
bridges for this service.
BSC parameters for acquired services (not configured by LightSoft) may take
different values at different bridges. Actual BSC Policer Profiles and
Thresholds may differ from the default by EMS configuration. In this case,
LightSoft regards the service as Non-conformant.
When editing an existing service with non-conformant parameters, the
configured value is configured for all NEs. The service then becomes
conformant on this parameter.
BSC TCA is then a per PE TCA on the Ethernet service. LightSoft indicates
whether the BSC TCA is raised on any Bridge supporting the service. When
the entry threshold is exceeded, a BSC TCA (alarm) is generated on the service
and this lasts until the exit threshold is reached.
For information how to create or edit policer profiles, see Managing Policer
Profiles. Policer profiles are also used to police bandwidth at each CoS instance
of a service endpoint; see Policers Pane.
To assign a policer profile to a service for BSC:

1. In the Service Details tab Advanced Parameters, click the BSC Policer
Profile selector . The Select Policer window opens.
2. Select an existing policer profile and click Apply. The selection is reflected
in the BSC Policer Profile field.

Configuring Dual Homing Protection

Dual Homing protects a pair of PE ports in an MPLS network that are each
connected to:
| Customer access equipment (CE) UMEs (Access Link Dual Homing)
OR
| PBs in a PB network (Internetwork Dual Homing)
The protection scheme comprises:
| Two links between the MPLS network and CEs or the PB network.
| A dual homed P2P service configured between different MPLS-PEs (peer
dual homed ports). The dual homed service carries RSTP Bridge Protocol
Data Unit (BPDU) service frames rather than regular Customer traffic
frames.
If a link between the MPLS and CE/PB networks fails, traffic can be diverted
across the dual homed link and is not affected.
Configuring dual homing protection for a PE port pair involves a different
procedure according to the configuration that applies:
| Configuring Access Link Dual Homing
| Configuring Internetwork Dual Homing
NOTES: After the dual homed service is created:

Properties of the participating ports of the MPLS-PE LEs
(connected to the CEs or PBs) show the peer dual homed
port; see Dual Homing Peer in Properties for Port -
ETH/MPLS ETH/MPLS Tab.
Properties of the topology links participating in dual
homing show if dual homing applies; see Dual Homing
parameter in Properties for Link - EoS Virtual Link
Advanced Tab.
The dual homed pair may be a pair of LAG ports comprising multiple EoS trail
virtual links.
Dual Homing General Restrictions
| One CoS can be configured.
| Frame selection is BPDU by default. Other values are not relevant.
| It is recommended to select a protected tunnel for the Dual Homed service.

Access Link Dual Homing

Access Link Dual Homing is supported for Customer Network to MPLS
network access. It comprises:
| Two links, each connecting a PE in the MPLS network and a CE.
| A dual homed service carrying RSTP Bridge Protocol Data Unit (BPDU)
(dashed line in the figure below) between the service endpoints. Typically
this results in one of the two links being active while the other is in inactive
standby state.
The PE endpoints outgoing to the customer access equipment (CEs) are ETY
UNI or E-NNI ports. RSTP must operate in the client network.
To protect regular Customer services over the protected interface, service
endpoints must be defined on both of the Dual Homed ports. Typically the
attributes of these service endpoints are identical (VLANs, CoS Mapping,
Policers) since they are handling the same customer frames.
To facilitate setting up such a protected service, LightSoft automatically
proposes configuration of endpoint attributes for a service on the Dual Homed
peer port after selection of one member of the pair.
To define an Access Link dual homed service:

1. Ensure that two EoS trails are defined between MPLS-PEs and CEs, and a
mesh of tunnels exists in the MPLS network, including the PEs to be
protected by dual homing.

2. Define a P2P service across the two PEs, including the following special
dual homed service settings:
a. In the Advanced Parameters pane:
Select the Dual Homed Service checkbox; see Advanced
Parameters Pane,
Select the Dual Homed Access Link Service radio button.
b. Select the endpoints for the service on the respective PEs and configure
policer profiles in the normal way; see Selecting Service Endpoints.
You may use the default BSC policer.
Choice of endpoints include:
First endpoint from ETY UNI or E-NNI ports only.
Second endpoint from ports of the same MPLS network.
LightSoft automatically makes compatible endpoints available for
selection.
NOTE: It is recommended to select a protected tunnel for

the dual homed service. RSTP must operate in the client
network.
c. Complete and activate the service in the normal way; see Creating a
Service.
3. Definition of a Customer service which will not typically be a P2P service.
a. Select one endpoint of the dual homing service of the previous step and
configure a policer profile in the normal way; see Selecting Service
Endpoints.
LightSoft recognizes that this endpoint is intended for the second
service of the dual homed pair, and automatically suggests the second
(peer) endpoint with the same parameters and policer profile, in order
for dual homed protection to apply. (Two endpoints appear in the
Endpoints List pane.)
You are not obliged to accept the suggested second port for the service.
(You can cancel it from the Endpoints List pane.) However, Dual
Homing protection will not apply unless the service endpoint is defined
on both PE endpoints on the links connecting the CE and PE.
b. Configure other customer service endpoints.
c. Complete and activate the customer service of the dual homed pair.
LightSoft automatically configures the customer service with dual homing on
the peer Dual-Homed ports.

Internetwork Dual Homing

Internetwork Dual Homing protects all Services between a PB Network and an
MPLS Network. It comprises:
| Two links, each connecting a PE in the MPLS network and a PB in the PB
network.
NOTE: Creating two EoS trails between a PB network and a

PE network generally results in a problematic topology. A
warning to that effect is displayed upon activation, but the
action is allowed. However, after the dual homed service is
defined, the topology is automatically recognized as valid.
| A dual homed P2P service pair configured between the VPLS-PEs to be

protected (peer dual homed ports). The dual homed service pair comprises
a Dual Homed Service carrying RSTP Bridge Protocol Data Unit (BPDU)
(dashed line in the figure below) between the Service endpoints. Typically
this results in one of the two links being active while the other is in inactive
standby state.
The PE endpoints outgoing to the PB network are EoS I-NNI ports. (This is an
exception to the rule that services should not be set up between I-NNI ports.)

To define an Internetwork link dual homed service:
NOTES:
Conditions apply for LAG configuration in a dual homed
network topology, such as pre-configuration of ports in the
EMS as LAG. For details, see LAG Support.
LAG is not currently supported for EIS cards (only for MCS
cards). Dual homing can be configured on PBs which are EIS
cards. However, LAG cannot be implemented on EIS cards.
LAG is supported only on MCS cards.
1. In the Create Trail window, create EoS and MoT trails between MPLS-
PEs and PBs:
a. Create EoS trails with the following dual homing settings:
Clear the RSTP Enabled checkbox in the EoS/MoT
Configuration pane. By default it is enabled in LightSoft,
regardless how it is set in the EMS. However, this is incompatible
with dual homing, and must be disabled.
If you are configuring a LAG, ensure that the EoS trails are pre-set
as LAG, and comprise two legs of a dual homing configuration (see
the diagram in this section) with each leg being a LAG of two EoS
trails.
NOTE: Ensure to connect the LAG master ports first, before

the slave ports. Starting with the slave ports is not allowed.
This is required for LAG in a Dual Homing context only. (It
is not required for other LAG contexts.)
b. Create the MoT trail that will serve as server for the two uni-directional
tunnels to be created in the next step.
At this point an MPLS network and PB network are connected via:
If LAG was selected: Two LAG EoS trails (total of four EoS trails).
Without LAG: Two EoS trails.
The MPLS and PB (and EA-HVPLS) network icons are white (inconsistent
since dual homing is not yet active).

2. Create a mesh of uni-directional tunnels in opposite directions in the MPLS

network, including the PEs to be protected by dual homing. This can be
done individually using the Create Tunnel window or automatically with
the Create Tunnel Mesh window.
NOTE: The tunnel selected for the dual homed service

should be protected (select Protection desired = Protected; see
Create Tunnel Basic Parameters Pane) if full protection over
the entire path is desired. Otherwise, weaker protection will
apply where, if traffic must be diverted to the dual homing
protection path, no additional path will be available in the
event of a subsequent failure.
3. Define a P2P service across the two PEs, including the following special
dual homed service settings:
a. In the Advanced Parameters pane (see Create Service Advanced
Parameters Pane):
Select Protected Tunnels Only.
Select the Dual Homed Service checkbox.
Select the Dual Homed Internetwork Link Service radio button.
b. Select the endpoints for the service on the respective PEs and configure
policer profiles in the normal way; see Selecting Service Endpoints.
Choice of endpoints:
First endpoint from EoS NNI ports only.
Second from ports of same Ethernet network.
LightSoft automatically makes compatible endpoints available for
selection.
Other service creation procedure requirements also apply, for example, that
the service CoS matches the tunnel CoS.
At this point the MPLS and PB (and EA- HVPLS) network icons become
green/red and the inconsistency is resolved.
All services created by LightSoft between PB Network and the MPLS are
Dual-Homing protected. Services created by EMS are dual-homing protected
provided that S-VLAN Registration is performed on the Dual-Homed Links.

Service Status Pane

This pane shows the service's implementation and operational status, as
determined by LightSoft. The parameters are read-only, and contain values
after a service has been completed.
Service Details tab – Service Status fields
Field Description
Actual Traffic State Enabled, Disabled, or Partial.

Enabled if all FDFRs are enabled (or enable is not supported).
Disabled if all FDFRs are disabled (or enable is not supported)
Otherwise state is partial.
Service State Incomplete, Non Conformant, or OK.

Incomplete when LightSoft does not succeed in configuring all
FDFrs for Service.
A check is made on acquistion of a new or modified service,
which may result in the attribute being set to non-conformant
with a non-conformancy reason.
Non-Conformancy Reason for the non-conformancy, if applicable. Non-Conformant

Reason is equivalent to Flex for trails. (L1 service shows the trail value.)
For more information, see Service Non-Conformancy.

Endpoints Tab
The Endpoints tab enables configuration of the services endpoints and their
associated CoS mapping, policer profile, and multicast parameters.
This pane consists of a List of Service Endpoints defining the Service and four
sub-panes which display attributes associated with a specific selected endpoint
- CoS Mapping, Endpoint Policers, Endpoint VLANs, and Multicast.
The tab includes the following panes:

| Endpoint List pane, which lists endpoints as they are defined.
| CoS Mapping pane, used to map UNI or E-NNI endpoints of the Ethernet
service to CoSs.
| Policers pane, used to assign policer profiles to the service endpoint
selected in the Endpoints List pane (after CoS mapping was performed).
| VLANs pane used to maintain VLANs for the currently selected endpoint.
| Multicast pane, used to specify multicast parameters for each Rooted MP
Leaf endpoint on a MPLS-PE.

Endpoint List Pane

The Endpoint List pane displays a list of UNI and E-NNI service endpoints
selected for the specified service.
An Ethernet Service endpoint can be at an:

| Ethernet UNI of a bridge
| VPLS LE (MCS)
| Ethernet remote UNI interface
For the endponts selection procedure, see Selecting Service Endpoints.
Endpoints can be added, edited (existing endpoints replaced), or deleted later
using the Service List window options; see Editing and Deleting Services.
Endpoints tab – Endpoint List pane fields
Column/Field Description
Name Port ID of the endpoint.
Port Type ETY-UNI, ETY ENNI, Remote ETY-UNI, or Remote ETY-
ENNI; see Supported ETH/MPLS Port Types.
Role Multicast role: Root or leaf. Valid for Rooted MP services.
P2MP Role: Hub or spoke. Valid for P2MP services.
PVID When the PVID is configured, the untagged ingress frames are
assigned a C-VLAN value of the PVID.
Port Rate Port rate in Mbps.
Dual Homed Peer Dual homed peer port corresponding with this port; see Dual
Homing.

Selecting Service Endpoints

The Complete action becomes sensitive for a service after two or more
endpoints are defined. A port becomes a configured service endpoint after
Activate/Deployment of the trail.
To define the service endpoints:

1. In the Create Ethernet Service window map view, select an LE or group,
right-click, and select Select Endpoint from the shortcut menu. A filtered
version of the port tree is displayed, which includes slots of the relevant ports.
2. Expand the tree and select a port for the endpoint.

3. Click Select to complete the selection. The port details are listed in the
Endpoints tab Endpoint List pane.
NOTE: To unselect an endpoint (in order to replace it with

another), repeat all the above steps to "select" it again. The
endpoint is cleared.
4. Repeat all the above steps for each required endpoint.

5. Configure the endpoints, one at a time, as described in the following
sections: CoS Mapping Pane, Policers Pane, VLANs Pane, Multicast Pane.
TIP: For NNI ports, after two endpoints are selected, and you
fully configure one of the endpoints, you can copy and paste the
configuration to the other endpoint. In the Endpoint List pane:
Right-click the line of the configured endpoint and select
Copy Details.
Then right-click the endpoint line that you want to configure
and select Paste Details.

Other comments
Rooted MP services: Each endpoint is configured as either Root or Leaf
(default is Root for the first selection and Leaf thereafter). An LE can be either
a root or a leaf (not both). A Rooted MP service must:
| Have at least one root (up to two).
| Be configured on a single MPLS Network.
P2MP services: Each endpoint is configured as Hub or Spoke (default is Hub
for the first selection and Spoke thereafter). The default for an endpoint is
Spoke. A P2MP service must:
| Have at least one Hub (up to four).
| Be configured on a single MPLS Network.
Dual Homed services: On selecting a service endpoint for which a dual-homed
peer has been configured, LightSoft, by default, adds the dual-homing peer as
an additional service endpoint; see Configuring Dual Homing Protection.
| Policer Profiles and C-VLAN list are copied by default to the Dual-Homing
peer.
| The dual-homing peer UNI ID is displayed for each UNI
| After initial configuration, LightSoft allows modification of the policer
profile and the C-VLAN list without requiring equality between the values.
For UNIs connecting to a UME, selection of the UME is equivalent to selection
of the LE.
For LAG ports, the service can only be defined on the Master port – not on
Slave ports.
Port-based UNI interfaces on which a service is already defined and Bridge
EoS UNI interfaces connected (by EoS) to Remote Access Points are not
sensitive for selection.
Ethernet service endpoints can be defined on Ethernet UNI interfaces. A single
service can be defined on a Port-based UNI interface.

CoS Mapping Pane

The CoS Mapping pane is used to configure the CoS mapping at UNI or E-
NNI endpoints, thereby enabling frames of Ethernet services to be mapped to
CoSs.
One CoS Ingress mapping is defined for a new service, which applies to all
UNI endpoints.
At ENNI endpoints a CoS mapping is configured separately for each endpoint.
It consists of both an Ingress CoS mapping and an Egress CoS mapping. The
Egress mapping translates the Network CoS of a frame to the S-VLAN Priority
assigned to the frame on egress.
When a Service is acquired, the Ingress CoS mapping at different endpoints
may be different.
An acquired service may be non-conformant with different mappings at
different UNI endpoints. In this case, actual mappings are shown by endpoint.
Mappings may differ between endpoints at different E-NNIs for the same
service.
Mappings for an E-NNI on a PB are not configurable.
The CoS mapping for an existing service can be edited; see Editing a Service.
UNI endpoints
UNI endpoints require a CoS mapping per priority in the Ingress. The CoS
Mapping pane opens displaying the Ingress Mapping scheme.
UNI ports use an incoming frame's priority field to decide the CoS to apply to
the frame within an MPLS network, based on the supplied Ingress mapping.
(The CoS indication is deleted at the UNI egress port only upon egress from the
network.) Since the priority with which a frame arrives is the same on egress
from the network as on ingress, only Ingress mappings need to be defined for
UNI ports.

E-NNI endpoints
E-NNI endpoints require a CoS mapping per priority for both Ingress and
Egress. The CoS Mapping pane opens with a left-side pane for Ingress
mapping, and right-side pane for Egress mapping.
E-NNI ports connect two MPLS networks over an Ethernet link. The network
at the opposite E-NNI endpoint typically belongs to another provider and uses
CoS names and applications that differ from the Ingress mapping. Thus an
Egress mapping must be supplied to indicate the CoS that should apply in the
other network (upon egress from the link). The Egress mapping values are
generally decided by consultation between providers, with the service provider
organization (rather than a network provider) usually leading the determination.

Endpoints tab – CoS Mapping pane fields - Ingress pane
The Restore Default Mappings icon can be used to reinstate the factory
defaults.
All Priorities checkbox Maps all the listed priorities to a single CoS value that you
specify.
Priority 0 - 7 Specific S-VLAN priorities of frames incoming to the port
by Ingress VLAN Priority.
CoS 0 - 7 (or free-text Select a CoS value for each priority. (Not applicable if All
identifiers) Priorities checkbox is checked.)
Specific CoS value per S-VLAN priority that should be
assigned to a frame incoming to the UNI or E-NNI port:
| UNI port: Upon ingress to the PB network.
| E-NNI port: Upon ingress to a link originating in an
MPLS network on the way to an E-NNI port at another
MPLS network.
Valid values are either CoS0 to Cos7 or CoS0, CoS2, CoS4,
and CoS6, according to the card type as indicated by the
EMS. These may be represented by free-text display names
configured for the network properties CoS tab, for example,
Gold or Platinum in place of CoS7; see CoS Tab.
A Discard option is also available, which causes packets
traversing that endpoint to be always discarded instead of
passed, used for troubleshooting purposes.
Endpoints tab – CoS Mapping pane fields - Egress tab
All CoSs checkbox Maps all CoSs in the destination network to a single S-
VLAN priority value from the originating network, which
you specify.
CoS 0 – 7 (or free-text Specific CoS values used in the destination network. See
identifiers) Ingress tab parameter for valid values.
Priority 0 - 7 S-VLAN Priority value selected per CoS that should be
applied to a frame incoming to the E-NNI port at the
destination network.

Configuring CoS Mapping

Follow these steps to configure CoS mapping.
To configure CoS mapping:

1. Select an endpoint in the Endpoints pane. Its CoS mappings are shown in
the CoS Mapping pane.
2. In the CoS Mapping pane, assign a CoS value to each S-VLAN priority of
the endpoint. (For an E-NNI endpoint, do this in the Ingress left-side of the
pane). All priorities are initially mapped to CoS 0. (This step applies to
both UNI and E-NNI endpoints.)
You can select the All Priorities checkbox

to apply the same CoS value to all priorities at once.
You can click the Restore Default Mappings icon to reinstate the
default mappings.
NOTE: The selected CoS must be compatible with the

assigned tunnel CoS. Otherwise the service activation will
fail. See Create Tunnel Window Basic Parameters Pane.
3. For an E-NNI endpoint (on an MPLS-PE), in the Egress, specify an S-

VLAN priority for each CoS.
4. Repeat the above steps for every endpoint of the service.

Policers Pane
The Policers pane is used to assign policer profiles to each CoS of a selected
endpoint (including external NNI service endpoints).
For each endpoint selected in the Endpoints pane and its assigned CoS
mapping, the Policers pane is used to set:
| the corresponding policer profile name assigned to each relevant CoS.
| the policing status of that policer profile.
CoSs are enabled for policer profile assignment if they have been assigned
priorities in the CoS Mapping pane; see CoS Mapping Pane. COSs that were
not assigned priorities (or otherwise not relevant to the endpoint) are grayed.
This is an example CoS Mapping pane with all priorities set to CoS 7.
The corresponding Policers pane then shows CoS 7 initially with the policing
status Blocked (default), meaning no traffic will traverse the service on this
CoS. (If CoSs were assigned to specific priorities, the Policer's pane, the
Blocked status appears opposite each CoS, as well as the CoS 0.)
If no policer profile is assigned to a CoS, the status may be changed to No Rate

Limit, meaning traffic can flow on this CoS without policing restriction.
Alternatively, you can assign a policer profile to govern the traffic flow on that
CoS.
You can change the policer profile as needed. If the CoS mapping is changed,
the policer profile for the row is removed and the row becomes insensitive. For
more details, see the procedure in CoS Mapping Pane.
For information how to create or edit policer profiles, see Managing Policer
Profiles. Policer profiles are also assigned to a service for BSC purposes; see
Assigning a Policer Profile to a Service for BSC.

Endpoints tab – Policers pane fields
CoS instance List of CoS instances, enabled or disabled as described above.
Name Name of the policer profile assigned to a CoS instance. (Blank if
no policer is assigned yet.)
Policing status Policing status of the currently assigned policer profile (if any).
When the pane first opens, the status of all mapped CoSs is
Blocked, meaning no traffic is allowed to flow on the specified
CoS.
Each CoS status can be changed as follows:
| No Rate Limit: The rate is not restricted by policers.
| Policing: Denotes that a policer profile is defined for the
CoS instance. This is done for each CoS instance as
described in Assigning Policer Profiles to CoSs of an
Endpoint.
No Rate Limit and Blocking may not be supported at the EMS
level for some L2 cards.
Assigning Policer Profiles to CoSs of an Endpoint

transmitted and which dropped (or marked in the case of a Two Rate Policer).
To assign policer profiles to CoSs of an endpoint:

1. Select a service endpoint in the Endpoints pane (see Endpoint List Pane)
for which CoS assignments were already made in the CoS Mapping pane
(see CoS Mapping Pane). The Policers pane shows the CoSs that have been
assigned priorities in the CoS Mapping pane as enabled (available for
policer profile assignment). The policing status at each CoS instance is
initially Blocked.

2. In the Policers pane, click the Select Policer Profile icon. The Select
Policers window opens. The upper part of the pane lists the mapped CoS
instances available for policer profile assignments. (The Create Policer Profile
icon is used to create a new policer; see Creating a Policer Profile.)
3. Assign a policer profile to each CoS of the current endpoint, as follows:

a. Select a CoS in the upper pane.
b. Select a profile in the lower pane.
c. Click Assign. In the upper pane, the policer is reflected in the Policer
column for that CoS.
d. Repeat the above steps for each CoS requiring a policer assignment.
OR
If you selected All Priorities in the CoS Mapping pane, only CoS 7
appears in the upper pane. Assigning a policer profile to that line applies
the policer to all CoSs.
4. Click Apply to save the assignments and close the window. The
assignments are reflected in the Policers pane.
The default value for a Policer Profile is the last configured profile for this CoS.
5. Set the profile status as needed, for example, to Policing.
The status of the Bandwidth Profile selection on an existing endpoint can be
edited.

VLANs Pane
The VLANs pane is used to configure and view VLANs for the currently
selected endpoint. For information about VLANs, see Service Identification.
| VLANs Pane for UNI Interfaces is used to maintain a list of C-VLAN IDs
(for UNI endpoints) which define the frames belonging to the Service
| VLANs Pane for E-NNI Interfaces is used to maintain the single S-VLAN
ID which defines the frames belonging to the Service.
VLANs Pane for UNI Interfaces

This pane is used to manage a list of C-VLAN IDs which define the frames
mapped to the service for this UNI.
Endpoints tab – VLANs for UNI pane fields
Show VLANs in Opens the VLANs List window, showing the VLANs currently in
use.
Use List
button
C-VLAN ID List C-VLAN ID for the service. Consisting of C-VLAN-ID List

elements separated by commas. A C-VLAN ID list element is
specified as either:
| C-VLAN ID (in range 0 to 4094), OR
| C-VLAN ID range consisting of C-VLAN ID lower and upper
values (separated by "-"). Multiple ranges should not overlap.
All/Other Selects all frames at the endpoint other than those selected by
VLAN as belonging to another service terminating at the same
endpoint.
Untagged Frames not including either an S-VLAN or C-VLAN tag.

List entries can appear in only one service endpoint defined at any UNI.
(Duplication of entries over services at a UNI is not allowed.) At service
completion, if duplication is found, an error message appears and service
activation cannot proceed until the duplication is removed.
On Complete, LightSoft does not allow an empty C-VLAN ID list.
C-VLAN IDs can be removed from the list by editing.
C-VLANs can be added to or deleted from an existing service endpoint.
Configure Port Attributes
UNI ports may have a Port VID (Pvid) configured on them. In this case,
untagged frames are tagged with Pvid as C-VLAN ID and then with a second
S-VLAN ID tag.
If Pvid is used, tagged frames are discarded in the MCS and BG-xx interfaces.
LightSoft supports only this case. The following considerations apply:
| The tab has a shortcut to the Port Attribute edit window (see list of
LightSoft configurable parameters in Appendix) to facilitate Pvid
configuration during Service Endpoint configuration.
| When PVID is configured, LightSoft enters the PVID value into the C-
VLAN ID list and does not allow the list to be edited.
| LightSoft enforces the constraint that when Pvid is configured on a port
only a single service can be configured on that port – the service to which
Pvid is mapped.
VLANs Pane for E-NNI Interfaces

This pane is used to configure/edit/view the single S-VLAN ID which defines
the frames belonging to the service on an E-NNI.
Endpoints tab – VLANs for E-NNI pane fields
Show VLANs in Opens the VLANs List window, showing the VLANs currently in use.
Use List
button

S-VLAN ID S-VLAN ID for the service. Consisting of S-VLAN-ID List
elements separated by commas. An S-VLAN ID list element is
specified as either:
| S-VLAN ID (in range 0 to 4093), OR
| S-VLAN ID range consisting of S-VLAN ID lower and upper
values (separated by "-"). Multiple ranges should not overlap.
On an Ethernet service endpoint on an External NNI interface, the Operator
configures a single S-VLAN ID defining the service over this interface.
(The C-VLAN ID List is not used.)
Multiple E-NNI Service endpoints are supported for a Service.
The S-VLAN ID is a Service endpoint variable and may take different values at
different endpoints, i.e. S-VLAN translation is performed over the MPLS
network.
Multiple Service endpoints may be configured on a single E-NNI. At
Complete, LightSoft checks that the configured S-VLAN IDs are all different.
In the case of duplication, an error is returned.
LightSoft uses the previously configured value of S-VLAN ID of a Service as
default for the next endpoint. As a result, when multiple E-NNI endpoints are to
be configured with a single S-VLAN ID, the S-VLAN ID is configured once.
Configuration of S-VLAN depends on whether the endpoint terminates on an
MPLS-PE or a Provider Bridge:
| On a Provider Bridged Network, the S-VLAN ID must be identical to the
Service S-VLAN for the PB Network.
| Policing is not performed on E-NNIs to PB Networks.
| There is no configurable CoS Mapping at an E-NNI on a PB Network.

Multicast Pane
The Multicast pane is used to specify multicast parameters for each Rooted MP
Leaf endpoint on a MPLS-PE. It only appears when a leaf endpoint is selected.
Viewing Multicast Parameters

Multicast parameters for each Rooted MP leaf endpoint on a MPLS-PE (not on
a bridge) in the service is supported as described in the following table.
Endpoints tab – Multicast pane fields
IGMP Snooping Enable When IGMP is enabled, Multicast Addresses are learnt through
checkbox IGMP Snooping. The default is IGMP Snooping disabled.
Membership Interval IGMP Group Membership Interval. The time to wait per
access interface before deciding that there are no members for
a group. 0 means unlimited time.
LMQT Interval Last Member Query Time (LMQT). The time to wait per
access interface before deciding that there are no members for
a group, after an IGMPv2 leave message is received. 0 value
disables LMQT processing.
Forward All MC This is one alternative for when IGMP Snooping is not enabled.
Addresses checkbox Alternatively, an MC Address can be entered and deleted by
the operator as a multicast IP Address. LightSoft also displays
the corresponding MAC MC Address:
| Up to 200 static configured IP MC addresses can be
configured per MCS port
| LightSoft ensures that no more than 800 MC addresses
are configured per MCS LE.
| The operator enters a Multicast IP Address and LightSoft
translates it to a Multicast MAC Address.
LightSoft does not support IGMP Snooping on Gateway Elements in services on a

EA-HVPLS network. These parameters may be configured using the EMS.
The user must ensure that parameters for all leaves of a specific service are identical.

Networks Tab
The Networks tab enables viewing and in some cases setting of network-
related service parameters. An input is generally required only in the case of
manual tunnel selection.
The Networks tab contains panes for MPLS or Provider Bridge Networks
(relevant when the service is configured on a network of the appropriate type).
| MPLS Network pane: Shows the tunnels used to implement the service on
a network.
| Provider Bridge Networks pane: Shows the S-VLAN ID assigned to the
service per network.
MPLS Network Pane

This pane is mainly used for viewing the tunnels selected by LightSoft for a
service. It can also be used for manual tunnel selection. It is not relevant for a
service entirely within a single PB network.
TIPS:
If service completion fails due to one or more required
tunnels being unavailable, check that the configurations of the
tunnels listed in this pane (selected by LightSoft for the
service) are compatible with the service attributes.
If Service completion shows that there are no acceptable
tunnels between one or more endpoint pairs, the manual
tunnel selection mechanism can be used to identify the pairs
between which no acceptable tunnels are available; see
Selecting Tunnels Manually for a Service.

The MPLS Network ID is derived from the selected endpoints.

The tunnel list at the bottom of the tab shows all the endpoint pairs implied by
your service endpoint selections, for which tunnels must be selected. (A P2P
service involves two endpoint pairs, a P2MP service with two tail endpoints
will involve 2x3=6 endpoint pairs, one with three tail endpoints will involve
2x3x4=24 endpoint pairs, and so on.)
The endpoint pair lines include tunnel information columns, which are filled in
after tunnels have been assigned (one per endpoint pair), either manually or
automatically:
| Before service completion, you can manually match some or all the
endpoint pairs to specific tunnels of your choice; see Selecting Tunnels for
the Service, OR
| At service completion LightSoft automatically looks for the "best" tunnels
for any endpoint pairs which were not manually matched to tunnels. (You
can allow LightSoft to assign all the tunnels without any user intervention.)
The table contains:
| MP2MP services: A row representing a P2P tunnel for each PE as head and
PE as tail, and the CoS for which a Policer Profile is configured at the head.
| Rooted MP services: A P2MP tunnel row for each required CoS.
| P2MP services: A row representing a P2P tunnel for each PE as head and
PE as tail, and a CoS for each direction between each hub PE and each
spoke PE.
If an endpoint is deleted in the process of service editing, LightSoft may delete
an MPLS-PE from the list, removing the appropriate rows from the table.
TIP: Selecting an endpoint pair highlights the corresponding

link in the Map view.

Networks tab - MPLS Network pane
Field Description
MPLS Network Determined by LightSoft based on service endpoints defined on MPLS

ID LEs.
VC Label LightSoft-selected value for the service upon Complete, distinct from
other LightSoft-managed MPLS services. This is the inner label used
to distinguish between services using the same tunnel.
Tunnel list columns
Head End Head and tail of the tunnel, as defined in Create Tunnel Window -
Tail End Endpoints and Path.
Tunnel Type P2P or P2MP, as defined in Create Tunnel Window - Advanced
Parameters Pane.
CoS CoS assignment, as defined in Create Tunnel Window - Basic
Parameters Pane.
Tunnel ID NMS Tunnel ID, Configured by LightSoft on Complete; see Create
Tunnel Window - General Parameters Pane.
Tunnel BW Mb/s Tunnel BW; see Create Tunnel Window - General Parameters Pane.
Occupied Sum of CIR for service endpoints on Tunnel. (Relevant when P2Pt
BWMb/s Only is Yes.)
Available Tunnel BW minus Occupied BW. (Relevant when P2Pt Only is Yes.)
BWMb/s
P2Pt Only If Yes is indicated, P2P Services Only is set, restricting the tunnel to
P2P VPNs; see Create Tunnel Window - Advanced Parameters Pane.
VPN Dedicated If Yes is indicated, Single Service Only is set, restricting the tunnel to a
single VPN; see Create Tunnel Window - Advanced Parameters Pane.
Protection Protection Desired for the tunnel - Unprotected or Protected (only
these values for selected tunnels); see parameter in Create Tunnel
Window - Basic Parameters Pane.

More about Automatic Tunnel Selection for a

Service
LightSoft automatically selects dedicated tunnels when the service has the
Dedicated Tunnels Only checkbox selected; see Create Ethernet Service
Window Advanced Parameters Pane. Then the only tunnels considered by
LightSoft will have the Single Service Only checkbox selected; see Create
Tunnel Window Advanced Parameters Pane. If unused dedicated tunnel(s) are
available for the service, LightSoft assigns the service to those tunnels. The
tunnel bandwidth of the service is used only for P2P services.
LightSoft selects tunnels with Protection Desired (Protected or Unprotected)
in accordance with the service's Protected Tunnels Only parameter selection
status; see parameter in Advanced Parameters Pane.
| If Protected Tunnels Only is selected, only protected tunnels are
considered for the service. (The service cannot be created if protected
tunnels are unavailable.)
| If the parameter is not selected, either protected or unprotected tunnels may
be selected, according to availability.
The selected tunnels are never bypass tunnels.
The head and tail end MPLS-PEs and the CoS are determined according to the
invocation.
Tunnel bandwidth is the CIR for P2P services, or Undefined for all other
services.
Deleting a MPLS-PE deletes any attachments to associated tunnels.
Tunnels attached to MPLS-PE pairs cannot be deleted.
When the MPLS Network pane is selected (in either the Create or Edit
Service or Service List window), the map view displays only MPLS network
elements and highlights objects as follows:
| All links with tunnels of the service are highlighted.
| When a specific tunnel (selected or candidate) is selected, the links on
which it is routed are highlighted.

Selecting Tunnels Manually for a Service

The MPLS Network pane can also be used to manually select tunnels for some
or all endpoint pairs of a service. Tunnels will be automatically selected for
endpoints for which no manual selections are made.
To select tunnels for the service:
1. In the MPLS Network pane, before the service is completed, click the
Select Tunnels icon. In the Tunnel Assignment List pane, it shows the
same endpoint pairs from the MPLS Network pane.
2. In the Tunnel Assignment List pane, select an endpoint pair. All the
possible tunnels available for it are shown in the Available Tunnels pane.
3. In the Available Tunnels pane, select the tunnel you want associated with
the endpoint pair.

4. Click Assign. The endpoint pair is highlighted in the Tunnel Assignment

List pane. The details of the tunnel you selected for it are shown in its
tunnel columns.
You can choose a different tunnel for the endpoint by clicking Unassign to
unassign the first selection, selecting another tunnel, and clicking Assign.
5. Repeat the steps from Step 2 for each additional endpoint for which you
want to manually assign a tunnel.
Networks tab – Assign Tunnels window fields
Field Description
Tunnel Assignment List pane
Contains same fields as the Tunnel list in MPLS Network Pane.
Available Tunnels pane
Contains the same fields as the Tunnel list in MPLS Network Pane., but excluding
Head End, Tail End, and CoS. It additionally includes the following parameters:
No. Services Number of services already associated with the selected tunnel.
Protection Protection Desired applying to this tunnel; see Create Tunnel

Provider Bridge Networks Pane

The Provider Bridge Network pane is relevant when the service is configured
on a PB network or EA-HVPLS network. LightSoft updates the PB networks in
the list based on the applicable service endpoints that are configured.
LEs in the ETH/MPLS layer are automatically partitioned into separate

network "groups" in accordance with the LE Network ID as configured by the
EMS.
PB networks are automatically configured by LightSoft; see Working with
Ethernet Networks.
Networks tab - PB Network pane fields
Field Description
PB Network Determined by LightSoft based on service endpoints defined on PB
LEs.
S-VLAN ID Shows the S-VLAN ID for the service on each listed PB network.
For different customer services to be properly identified on a PB
network, services must be S-VLAN registered on all of a PB
network's virtual links. This can be done by selecting the Automatic
S-VLAN Registration Enabled checkbox (see below). See also
Service Identification and S-VLAN Registration for a Service.
| A service on an EA-HVPLS network has an S-VLANs for each
different PB networks.
| When S-VLAN ID is not configured, on Complete LightSoft
selects a default value for S-VLAN ID for each PB Network
(different from S-VLAN IDs for any existing services in each
network).
LightSoft assigns the lowest S-VLAN available in all Ethernet
Networks used by the Ethernet Service. If no such S-VLAN is
available, the service is rejected with reason No available S-
VLAN in some networks.
| The operator can configure the S-VLAN ID value either before
Complete or between Complete and Activate. This need not be
different from the S-VLAN ID for other services. In this case,
LightSoft warns the operator that multiple services in the same
PB Network use the same S-VLAN ID.
| The S-VLAN ID for an existing service cannot be updated.
| LightSoft displays an empty cell for the S-VLAN ID until
configured either by the operator or by LightSoft.

Field Description
Gateway#1 For Overall Networks (including a MPLS Network and one or more
Gateway#2 PB Networks), at least one MPLS-PE interfaces the MPLS network
to each Ethernet network. Multiple MPLS-PEs occur when Gateway
Protection is implemented:
| The Gateway MPLS-PE IDs appear as attributes of the PB
networks.
| LightSoft determines the Gateway MPLS-PEs on the basis of
configuration in the LightSoft Ethernet Topology Management.
For a Service Network consisting of a single Ethernet Provider
Network, the Gateway MPLS-PE ID appears as N/A.
Automatic S- When selected, the LightSoft performs S-VLAN Registration for this
VLAN Service on all PB network ports. This enables all existing virtual
Registration links in the network for this service. This option can also be set
Enabled through the Edit Service window; see Editing Services.
checkbox For more information about S-VLAN registration, see S-VLAN
Registration for a Service.
When a single PB network is selected on either Create/Edit or View, the

topology map shows only the selected PB network and serves to manage S-
VLAN registration.
| The topology map displays the Bridges in the network and the Ethernet
NNI links between them.
| The links and aggregated links on which the service is registered are
highlighted.
| The toolbar has an RSTP Map icon. Clicking this icon displays the
Active/Blocked links with respect to RSTP/MSTP in color on the map.
(For MSTP domains, the active/blocked links are S-VLAN dependent.)
The View display allows display of the list of registered links for the selected
PB network (if there is one).
In the view topology display, aggregated links are marked as being registered
on all/some/no component links.

Managing Policer Profiles

The Policer Profiles List window is used to create, edit, or delete policer
profiles; see Policer Profiles List.
transmitted and which dropped (or possibly marked). For information about
assigning policer profiles to CoS instances of a service endpoint, see Policers
Pane.
A service as a whole can be associated with a rate-enforcing policer profile for
BSC purposes.
For information about assigning policer profiles to a service for BSC purposes,
see Assigning a Policer Profile to a Service for BSC.
Policers are either Single Rate or Two Rate:
| Single rate Policer Profiles are characterized by two traffic parameters:
CIR (Committed Information Rate); see Overbooking and CIR.
CBS (Committed Burst Size)
| Two rate Policer Profiles are characterized by the above parameters, and
by:
EIR (Excess Information Rate)
EBS (Excess Burst Size)

Policer Profiles List

The Policer Profiles List window is used to create, edit, or delete policer
profiles. Up to 1000 profiles can be defined.
LightSoft supports a default set of list entries which includes the grid of BW
parameters defining the MCS policer profiles.
For general information about policer profiles, see Managing Policer Profiles.
To open the Policer Profiles List window:

| On the main window menu bar Traffic menu, select Services > Policer
Profiles List. The Policer Profiles List window opens.
Policer Profiles List Menu and Toolbar

Policer Profiles List window menu and toolbar
option icon
Policer Profile
Refresh Loads profiles from server.
Print Profiles Prints the list contents.
New Profile Creates a new profile; see Creating a Policer Profile.
Edit Selected Edits the selected profile; see Editing a Policer Profile.
Profile
Delete Profile Deletes the selected profile; see Deleting a Policer Profile.
Show Show the services for which this Policer Profile is configured as
Services one of the service endpoints or is the BSC Policer for the service;
see Viewing Services Associated with a Policer Profile.
Help

Policer Profiles List Columns

Policer Profiles List window columns
Column Description
Profile Name Name of the policer profile (unique in the list).
Type Single rate (when EIR and EBS are zero) or Two rate policer if EIR
and EBS have positive values.
CIR (kBits/s) Committed Information Rate. The overall Ingress bandwidth for this
service over all destinations which the Provider has guaranteed to
carry without dropping or marking as low priority. Values may be 0,
or 66 to 10G bits/sec.
CBS (KB) Committed Burst Size. Maximum burst of data that the provider
agrees to transfer without dropping or marking (associated with the
CIR value). Values from 0 to 524 bits/sec. (For technical reasons, the
value should not be set to 0 or 1.)
EIR (KBits/s) Excess Information Rate. Additional Ingress bandwidth which the
provider agrees to carry after marking the frames as lower priority.
Such frames are carried end-to-end when congestion conditions in
the network permit. Values may be 0, or 66 to 10G bits/sec. Not
applicable for EIS cards. Displayed as N/A for Single Rate.
EBS (KB) Excess Burst Size. Maximum burst size associated with EIR. Values
from 0 to 524 bits/sec. Not applicable for EIS cards. Displayed as
N/A for Single Rate.
NOTE: Minimums, maximums, and applicability

limitations apply for specific hardware which is not
validated by LightSoft. Refer to the relevant hardware user
manual for more information.

Creating a Policer Profile
NOTE: Each policer profile name must be unique in the list. No

two profiles can have precisely the same values for all attributes.
To create a policer profile:
1. Click the Create Policer Profile icon . The Create Profile window opens.
2. Enter values in the fields.

3. Click Save (enabled when all required fields contain values). The new
profile is reflected in the Policer Profiles List window.
Editing a Policer Profile

Only the name of an existing Policer Profile can be edited in LightSoft. Editing
a Policer Profile name does not result in updating the endpoint.
The bandwidth associated with an endpoint is edited by selecting another
Profile. This results in transmission of the appropriate data to the EMS.
To edit a policer profile name:

1. Select a policer profile in the Policer Profiles List window and click the
Edit Selected Profile icon . The Edit Profile window opens.

2. Change the profile name as needed.

3. Click Save. The new name is reflected in the Policer Profiles List window.
Deleting a Policer Profile

LightSoft can delete a policer profile only if it is not used by any endpoint.
To delete a policer profile:

1. Select one or more policer profiles in the Policer Profiles List window
(hold the CTRL key for multiple selections).
2. Click the Delete Selected Profile icon . A confirmation window

opens.
3. Click Yes to confirm. The profile(s) are removed from the Policer Profiles
List window.
NOTE: Different Bridges (MCS, EIS, ESW) handle profiles
differently. LightSoft does not control these differences. If an
invalid profile is configured, the EMS rejects the endpoint.
Some reasons may be:
| Bridge or PE does not support two-rate profile.
| Profile attributes out of range for the bridge or PE.
| Maximum number of profiles already configured at the
bridge or PE.
Acquisition of Policer Profiles

The EMS maintains a name for each Policer Profile. On configuration of an
endpoint from the EMS, the LightSoft Policer Profile name is used.
When an endpoint is acquired from the EMS, the EMS includes the Policer
Profile Name in its upload (as well as other parameters):
| If the uploaded attribute set appears in the Policer Profile list, the profile is
not added. Reference is made to the existing LightSoft name.
| If the uploaded attribute set does not appear in the Policer Profile list:
If the name exists, the profile is added with a new name (EMS name
and suffix).
If the name does not exist, the profile is added with the EMS name.
In this way, profiles generally have a single name throughout the system.
However, different EMSs may have their own local names for some profiles
which are different from the LightSoft names.


15
Performing Actions on
Ethernet Services
In this chapter:
Overview ....................................................................................................... 15-1
Accessing the Ethernet Service List Window ............................................... 15-2
Ethernet Service List Window ....................................................................... 15-4
Viewing Service Information ...................................................................... 15-15
Viewing RSTP Information ......................................................................... 15-17
Performing Service Operations ................................................................... 15-20
Filtering Ethernet Services .......................................................................... 15-21
Reconnecting Services ................................................................................. 15-33
Editing and Deleting Services ..................................................................... 15-34
Acknowledging Service Modifications ....................................................... 15-40
Batch Service Operations ............................................................................ 15-42
Overview
The Ethernet Service List window, which is similar to the Trail List window
for SDH and optical trails, enables you to conveniently manage data services in
the network.
The Ethernet Service List window allows you display a list of services, print
them, and modify attributes, and includes advanced sorting and filtering
capabilities. It allows display of a selected service on the Ethernet Service
List window map.
Ethernet services are also provisioned and modified via the respective EMSs.
LightSoft automatically acquires the information, and makes it available for
viewing and changes in the Service List window, in the same way as
LightSoft-created services; see Service Acquisition.

Performing Actions on Ethernet Services LightSoft User Manual
Acquired services (either newly created or involving EMS-initiated

modifications) are automatically assigned "Unacknowledged modification"
status, thereby flagging the service for review. The flag remains until the
modifications associated with the service are acknowledged; see
Acquired services or EMS-initiated service modifications may sometimes be in
conflict with LightSoft and deemed to be non-conformant - similar in concept
to flex trails; see Service Non-Conformancy. They can be made conformant by
editing; see Editing Services.
This section also describes the RSTP Map window, which enables you to view
the RSTP configuration that controls frame forwarding on PB networks. You
can convert the service to be conformant by appropriate editing. For more
information, see Service Non-Conformancy.
Accessing the Ethernet Service

List Window
The Ethernet Service List window opens with different object combinations
according to preselections in the LightSoft main window:
The Service List window's map view shows all objects in the network
(consistent with your user permissions).
The Services pane includes Ethernet services based on the default
filter; see Services Pane.
TIP: Opening the Ethernet Service List window may take

less time if you choose "No Services" as the default filter.
You can then select a different filter. For details, see
Applying a Filter and Setting it as Default.
| If objects are preselected in the LighSoft main window:

The Service List window's map view shows only those objects and
their immediately associated links/elements.
The Services pane shows only the associated tunnels. In this case, a

LightSoft User Manual Performing Actions on Ethernet Services
A wide range of additional filter options are available; see Filtering Ethernet
Services.
You can open multiple Ethernet Service List windows simultaneously, each
one displaying selected layer and elements independently of other layers,
having its own topology layer and view of the network, and allowing different
service operations.
To open the Ethernet Service List window:

1. If you want to open the Ethernet Service List window showing only
selected NEs and not the entire topology, select the NEs in the most
recently opened Topology View map.
2. On the LightSoft main menu bar, select Traffic > Services > ETH Service
List. No specific Topology Layer selection is required.
OR
On the toolbar, click the ETH Service List icon . The Ethernet
Service List window opens.
To open the Ethernet Service List window with a single PE:
To open the Ethernet Service List window with services of a

single PE:
1. In the ETH/MPLS layer, select a PE in the View map.
2. Right-click and select Show Services. The Ethernet Service List window
opens showing only services associated with the selected PE.

Ethernet Service List Window

The Ethernet Service List window enables you to conveniently view
information of Layer 2 Ethernet services. It provides a graphical map of all or
preselected Ethernet service endpoints, as well as panes showing selected
service and endpoint parameters. You can open multiple Ethernet Service List
windows simultaneously. For information about how to open the window, see
Accessing the Ethernet Service List Window.
The window displays information about selected services. The Services pane
lists a filtered set of services and provides a wide range of information about
each.
When you click a service in the Services pane list, it becomes the focus of the
information provided by other panes. At the same time, the associated objects
and links are highlighted in the window map.
NOTE: Changes to Ethernet services in the EMS (for

example, new endpoints) are reflected in LightSoft
immediately when it opens or when clicking Refresh. There
is no prenotification of expected changes or information about
original configurations. By contrast, changes to SDH or
optical trails are alerted by a TCI flag icon on the LightSoft
main window toolbar and are reflected in LightSoft only after
synchronization.

The window includes the following panes:

| Map View: Shows the elements and links of the selected topology view.
| Services pane: Lists the Ethernet services that satisfy the criteria for the
active filter.
| Service Summary pane: Provides summary details of a service selected in
the Services pane.
| Service Details tab: Makes available service parameters of a service for
viewing and editing purposes.
| Endpoints tab: Makes available endpoint-related parameters of a service
for viewing and editing purposes.
| Networks tab: Makes available network-related parameters of a service for
viewing and editing purposes.
These panes are parallel to the same-name panes in the Create Service process.
Some parameters from that process can be modified directly through the
Service List window panes. Others can be opened for editing or viewing
through the Edit Service window; see Editing a Service. For descriptions of
those parameters, see the applicable sections in Create Ethernet Service
Window.

Service List Menu and Toolbar

Below are the functions available from the Service List window menu and
equivalent toolbar icons.
Other functions are available from additional toolbar icons and selectors; see
Other Service List Options.
a row in the Services pane; see Services Pane Shortcut Menu.
Ethernet Service List menu and toolbar icons

icon
List menu
Export to XML Exports the services selected in the Services pane
to an XML file for network planning or backup
purposes; see Exporting Services.
Export to CSV Exports list data to a delimited format file like
comma-separated values (CSV) for import to
Microsoft Excel or a relational database
application; see Exporting to CSV.
Print Selected Prints the contents of the Services pane; see
Services Printing.
Select All Selects all services in the Services pane.
Services
Unselect All Unselects all services in the Services pane.
Services
Delete Services Deletes the services whose checkboxes are
selected in the Services pane from all databases
(LightSoft and EMS). (If no services are selected,
deletes the highlighted service. If services are
selected, deletes only the selected ones.) For more
details, see Deleting Services.
Refresh List Reloads the Ethernet Service List window
showing newly created services. The map view
continues to show services according to the active
filter.
Service menu
Edit Service Enables you to edit service and endpoint
parameters via LightSoft using the Ethernet
Service List panes; see Editing Services.
Show RSTP Map Opens the RSTP Map window. This shows the
parts of the tree used by traffic between the
endpoints of an Ethernet service, enabling you to
understand current traffic flow; see Viewing
RSTP Information.


icon
Show Tunnels Opens the Tunnel List window showing the
tunnels that the selected services traverse; see
Show MoT Trails Opens the Trail List window showing the MoT
trails associated with the selected services; see
Note: You can use the Show EoS Trails shortcut
option to show EoS trails associated with the
selected services; see Services Pane Shortcut
Menu.
Reconnect Reconnects Incomplete services selected in the
Service Services pane; see Reconnecting Services.
Current Alarms Opens thew Current Alarms window showing
alarms that would affect the selected services; see
Viewing Alarms for Selected Services.
Show Info Displays detailed results of the last operation.
Enabled only when the last-performed operation
was not completely successful. For more
information, see Performing Service Operations.
Filter menu
Edit Filter Edits a service filter. Enabled only if objects were
preselected in the main window before the Service
List window was opened, or a user-defined filter
is selected. For more information, see Another
Way to Edit a Filter.
Set Default Sets the selected service filter as the default; see
Applying a Filter and Setting it as Default.
Help menu

Other Service List Toolbar Options

selectors.
Other Ethernet Service List toolbar options

Show RSTP Map for See option description in Create
Registered Links Service Menu and Toolbar.
Hide/Show Service Alternately hides the left-side details
Details panes, leaving only the Tunnels pane
and the window map, or reinstates
the details panes. For more details,
see Showing and Hiding Window
Panes.
Maximize Service List Expands the Map view by hiding the
Services pane. To reinstate the
Services pane, drag up on the lower
border of the window.
Filter selector Filters the Ethernet Service List
window map view according to the
selected service filter. For more
information about service filters, see
Filtering Ethernet Services.
Map View
See details in Create Service window panes and tabs Data Network Map Pane.
When the MPLS network is opened and a service is selected, the service is
displayed on the map.

Services Pane
The Services pane at the bottom of the Ethernet Service List window lists the
Ethernet services that satisfy the criteria for the active filter. It can be moved
and resized as needed.
When you click a service in the Services pane list, it becomes the focus of the
information provided in the other panes. At the same time, the associated
objects and links are highlighted in the window map.
When the pane first opens, it displays up to 100 filter-defined services. You can
use the Load more services and Load all services icons to load more
services.
Click the Ethernet Service List window Reload icon to reload

information for that window and the Services pane.
The following service statistics are shown in the status bar:
| n/n (for example, 6/6): Number of services filtered in/total number of
services that can be displayed.
| n items selected: Total number of selected services (with marked
checkboxes).
Services Pane Toolbar

Services pane toolbar

Load More Loads an additional increment of filter-defined services
up to a configurable limit. For information about
configuring the Load more services limits, contact ECI
Telecom customer support.
Load All Loads all filter-defined services in the network.
Show highlighted When selected (default when the window opens) and a
service service is highlighted in the Services pane, the service, its
endpoints, and the links carrying tunnels used by the
service are highlighted on the map. Information about the
service is shown in the window panes. Deselecting the
icon disables highlighting the service on the map.


Show S-VLAN ID Highlights links associated with selected services which
Registered Links are S-VLAN registered; see S-VLAN Registration for a
Service.
Quick Filter Opens Quick Filter fields at the top of the pane, enabling
you to quickly filter the services by EthVPN ID, type,
label and/or customer; see Creating a Quick Service Filter.
Services Pane Shortcut Menu

a row in the list.
Services pane shortcut menu options
Edit Service See icon description in Service List Menu and
Delete Service Toolbar.
Reconnect Service
Current Alarms See the Show Service Alarms icon description in
Service List Menu and Toolbar.
Show
Show RSTP Map Opens the RSTP Map regarding selected services;
see Viewing RSTP Information.
Show Tunnels See icon description in Service List Menu and
Show MoT Trails Toolbar.
Show EoS Trails Shows EoS trails associated with the selected
services; see Viewing Associated Traffic Entities.
Service Operations
Acknowledge Modifications Acknowledges all modifications associated with the
selected services; see Acknowledging Service
Modifications.
View Modifications Opens the Unacknowledged Modifications window,
where you can view and acknowledge individual
modifications for the selected services; see
Service Utilities
MAC Address Learning This query lists the PBs and MPLS-PEs at which an
Query operator-configured MAC address has been learnt.
vFIB Utilization This query lists the vFIB usage at each PB and
MPLS-PE at which the service is implemented.
Export to XML See icon description in Service List Menu and
Export to CSV Toolbar.
Print Selected Services

Services Pane Columns

You can choose which columns to show in the pane; see Showing, Hiding, and
Auto-Fitting Columns. Standard column sorting and ordering operations can
also be performed in the pane; see Working in LightSoft.
Services pane columns
Field Description
Selection checkbox. Check to select services for various
operations (as described in context).
The currently highlighted service (whether or not the
checkbox is selected) is the focus of information shown in
the Service List window panes.
EthVPN ID Sequential number assigned by LightSoft on Complete or
Activate that uniquely identifies the Layer 2 service.
Integer in Decimal Format.
Assigned by LightSoft and not user-configurable. It must
differ from the EthVPN ID of any other Ethernet service
supported by the LightSoft station. Checking uniqueness
is performed at both Complete and Activate action phases.
Not modifiable for an existing service.
Type L1, P2P, MP2MP, RootedMP, P2MP.
Label Ethernet service label. (L1 service shows the trail label.)
Customer Customer for this service. (L1 service shows the trail
customer label.)
Administrative Denotes if the service is enabled or disabled; see
Service Enable parameter in Basic Parameters Pane.
vFIB Quota Maximum number of learnt MAC Adresses allowed per
VSI supporting the service; see parameter description in
BSC Policer Profile Policer profile that should apply to this service for
Broadcast Storm Control; see parameter description in
Dedicated Tunnels Assigned only to Single Service Only tunnels.
Only
Protected Tunnels Use Protected tunnels only in MPLS Network.
Only
Dual Homing Indicates a Dual Homed Service.
Created By User Name of LightSoft operator (or EMS) (L1 service shows
the trail value.)
Created With Application with which the service was created: LightSoft
or EMS (for acquired services).
Creation Time Creation time. (L1 service shows the trail value.)
Modified By User Name of LightSoft user. (L1 service shows the trail value.)
Modified With Application with which the service was modified

Field Description
(LightSoft) or the modified service acquired (EMS).
Modification Time Modification time. (L1 service shows the trail value.)
Unacknowledged If true, means that the service has been acquired from
Modification EMS and the LightSoft operator has not yet
acknowledged the acquired modification. (L1 service
shows the trail value.) For more information, see
Actual Traffic State Enabled, Disabled or Partial.
If all FDFrs are enabled, the value is enabled (or disable is
not supported), the value is Enabled. If all FDFrs are
disabled, the value id Disabled. If some FDFrs are enabled
and others disabled, the value is partial. See parameter
description in Service Status Pane.
Service State Incomplete, Non-Conformant or OK.
Incomplete when LightSoft does not succeed in
configuring all FDFrs for Service.
A check is made on acquisition of a new or modified
service, which may result in the attribute being set to non-
conformant with a non-conformancy reason.
Otherwise the value is OK.
See parameter description in Service Status Pane.
Non-Conformancy Reason for the non-conformancy, if applicable; see
Reason parameter description in Service Status Pane.

Service Summary Pane

The Service Summary pane provides excerpted summary details of a service
selected in the Services Pane. The same pane appears in the Create Service
window. For the parameter descriptions, see Service Summary Pane.
Service Details Tab

The Service Details tab enables you to view and edit service parameters
originally defined in the Create Ethernet Service window. For the parameter
descriptions, see the Creating Ethernet Services.

Endpoints Tab
The Endpoints tab enables you to edit service parameters originally defined in
the Create Ethernet Service window. For the parameter descriptions, see
Endpoints Tab in the Creating Ethernet Services section.
Networks Tab
The Networks tab enables you to edit service parameters originally defined in
the Create Ethernet Service window. For the parameter descriptions, see the
Creating Ethernet Services.

Viewing Service Information

Selecting a service in the Services pane makes it the focus of the detailed
information provided in other panes. In addition, associated services and other
traffic entities can be identified and associated alarms can be displayed.
Viewing Information Detail

The Service List window opens with several information panes, one of which
is the Services Pane that lists a filtered set of service records.
When you click and select a service in the Services pane list, the service
becomes the focus of the information provided by other panes.
When one or more services are selected in the Services pane, associated objects
and links are highlighted in the Service List window map.
To view information about a service:

1. In the Service List window, ensure that a service filter is selected to filter
the services you want listed in the Services pane. For information about
service filters, see Filtering Ethernet Services.
2. Click to select a service in the Services pane. By default, the Show icon
on the toolbar on the right is selected and:
about the selected service.
The service's associated elements and links are highlighted in the
Service List window map.
You can select services in the Services pane in two ways:
| Clicking and so highlighting the service (as described in the previous
procedure). Using this method, you can select only one service at a time.
| Selecting (or unselecting) the checkboxes of any number of services. This
method is used for operations such as delete, export, reconnect, show
current alarms, print, and some others. This procedure is described in more
detail in Performing Service Operations.
In this section, "selecting a service" means selecting its checkbox.

Viewing Associated Traffic Entities

You can view the following service-related entities in their connected list windows:
| Tunnels associated with selected services.
| Trails associated with selected services.
You can also view the underlying services for a selected non-bypass tunnel; see
Viewing Tunnel Information - Show Associated Trails, Services, or Protected Tunnels.
To view traffic entities associated with a service:

1. In the Service List window, select the checkboxes of the services (or select
a single service) for which you want to view associated traffic entities.
2. Select the following icon or right-click option:
To show associated tunnels: Click the Show tunnel(s) icon, or

right-click and select Show > Show Tunnels. The Tunnel List window
opens showing the associated tunnels.
To show associated MoT Trails: Click the Show MoT trails
associated with this service(s) icon, or right-click and select
Show > Show MoT Trails. The Trail List window opens showing the
associated MoT trails.
To show associated EoS Trails: Right-click and select Show > Show EoS
Trails. The Trail List window opens showing the associated MoT trails.
Viewing Alarms for Selected Services

You can view all the alarms that affect selected services. These alarms are
Traffic Entities.
You can also view the services affected by a selected alarm; see Viewing
Traffic Entities Affected by an Alarm.
Viewing Services Associated with a Policer

Profile
You can view the services for which a selected policer profile is configured as
one of the service endpoints or is the BSC Policer for the service.
To view services associated with a policer profile:

1. Selecting a policer profile from the Policer Profile List window; see
Policer Profiles List.
2. Selecting Policer Profiles > Show Services, or clicking the Show Services
toolbar icon. The list of services for which this policer profile is
configured as one of the service endpoints or is the BSC Policer for the
service is displayed.

Viewing RSTP Information

A bridged Ethernet network must operate in a loop-free fashion even though
the Ethernet topology itself contains loops in order to provide redundancy.
The Rapid Spanning Tree Protocol (RSTP) automatically creates a "spanning"
tree of links connecting all the bridges (when this is possible). The spanning
tree is always loop-free. Links in the tree are active (used by Ethernet traffic),
while those not in the tree are inactive. Whenever changes in the network are
detected (new/removed links or elements, or failed/restored links), the RSTP
dynamically updates the spanning tree.
The ETH/MPLS layer may have several unconnected Ethernet networks, each
with its own RSTP tree.
RSTP Map Window

LightSoft's RSTP map feature shows the parts of the tree used by traffic
between the endpoints of an Ethernet service and enables you to understand
current traffic flow. This section describes how to view the active RSTP tree in
the RSTP for Ethernet window.
The RSTP map comprises the following color-coded elements (default colors
are indicated):
| RSTP-relevant LEs (yellow): One Ethernet switch is defined by the
protocol as the root bridge of a tree.

| RSTP-relevant links (with arrows showing link directionality):

Light blue (or same as main trail) - active RSTP links, which allow the
flow of Layer 2 Ethernet traffic.
Purple (or same as protection trail) - RSTP-enabled links with inactive
standby status, which may switch to become active RSTP links if
required by the RSTP algorithm.
Gray - RSTP-disabled links (for a port or bridge) or links not running
through EIS cards.
The default colors are configurable via the RSTP Map Preferences dialog
box. For details, see Modifying RSTP Map Preferences.
NOTES:
The RSTP for Ethernet window only operates with LEs that
have been created as Ethernet switches by selecting the Split
by an Ethernet Switch checkbox in the Create LE dialog
box. For more information, see Creating Secondary LEs.
The RSTP map shows the RSTP state of single links only.
In the case of links in a multilink (including LAG link
representations), please refer to the applicable EMS.
To view RSTP information:

1. Select the Ethernet topology view from the LightSoft main window
Topology Layer dropdown list.
2. If you want to open the RSTP Map window with only selected LEs and the
links running between them, select the LEs in the LightSoft main window
view map.
3. On the main menu bar, select Tools > RSTP.
OR
On the toolbar, click the RSTP Map icon . The RSTP for Ethernet
window opens, showing an updated view of the RSTP schemes that are in
use.
4. While viewing, the message "RSTP map has changed" may appear at the
bottom of the window, signifying that the underlying spanning tree has
changed due to changes in relative costs of links or link availability. Click
View > Refresh to refresh the display. The Last Update time stamp at the
bottom right-hand corner of the window shows the date/time of the last
refresh.

RSTP Map window options
Menu/Toolbar Description
option
Map
Preferences Enables you to change the colors associated with RSTP
information; see Modifying RSTP Map Preferences.
Close Closes the RSTP Map window.
View
Refresh Refreshes the RSTP Map window to show the latest RSTP color
coding on trails. The Last Update time stamp at the bottom right
corner of the window shows the date/time of the last refresh. The
RSTP Map window automatically refreshes when it opens.
Legend Shows or hides the status bar legend and Last Update time
stamp.
Help
Help Displays the help file.
Modifying RSTP Map Preferences

The RSTP Map Preferences dialog box enables you to change the color of the
RSTP information in the RSTP for Ethernet window.
To change the RSTP color coding:

1. In the RSTP for Ethernet window, select Map > Preferences or the
Preferences icon . The RSTP Map Preferences dialog box opens.
2. Change the color associated with a timing quality by customizing its color
swatch . For information about standard color
customization, see Customizing LightSoft Object Colors.
OR
Revert to the default colors by clicking Defaults. This changes the colors in
the RSTP Map Preferences dialog box to the system default values.

3. Click Apply to save the changes to the database. The RSTP Map
Preferences dialog box closes. The selected view of the RSTP Map
window is automatically refreshed reflecting the new preferences. The
legend on the status bar indicates the color correspondence for each quality.
The changes remain in effect for your user profile until you change them.
OR
Click Cancel to close the dialog box without saving changes.
Performing Service Operations

This section describes how to perform service-related operations and view
operational results.
To perform a service operation:

1. Select the service by selecting its checkbox in the Services pane.
2. Select a Service List window toolbar option or right-click a service in the
Services pane and select a shortcut menu option.
If the operation succeeded, an operation succeeded message opens.
If any part of the operation was not successful, a Results window
opens, showing information about the failed operations. If multiple
services were involved, the window includes results for each service.
Whenever an operation is not completely successfully, the Operational
Results Info icon in the Service List window toolbar becomes
enabled. After you close the message window, you can revisit the
results by clicking this icon.
The icon remains enabled until another operation is performed. If the second
operation is completely successful, the icon is disabled. If it is partially
successful, it displays the detailed results for that operation.

Filtering Ethernet Services

You can filter the Services pane (determine the service records that are
displayed) according to any combination of service attributes and objects
activated from either predefined or created filters.
The "Total services" statistic (number/number) in the status bar shows the
number of services filtered into the view vs. the total number of services that
can be displayed.
(The status bar also shows the total number of services with checkboxes
selected.)
LightSoft supports the following predefined service filters:
| Customer Services: Filters in all except Dual Homing services. (This is the
factory default filter and can be changed by the user as required.)
| All Services: Filters in all services (no filtering is applied).
| No Services: No services are filtered in. (When this is the default filter, the
Service List window initially opens quickly without any services. Another
filter should then be applied; see Applying a Filter and Setting it as Default.)
| Dual-Homing Services: Filters in dual homing services only.
| Unacknowledged Modifications: Filters in services and service
modifications acquired from the EMS which are not yet acknowledged.

Filter options from Service List vs. main window

Service List window.

You can use the Traffic menu Services > Service Filters option (or Service
Filters icon ) to:
| Create or edit a new filter according to any combination of service
attributes or objects; see Creating and Editing Advanced Filters.
| Edit, rename, or delete a filter that you created, or set a filter as the default
(which automatically activates it when the Service List window opens);
see Rename, Delete, Set Default Filter Actions.
The Services pane can automatically be opened with services corresponding to
preselected objects in the LightSoft main window; see Accessing the Ethernet
Service List window.
From the Service List window:

You can:
| Use the Quick Filter icon to quickly filter by Service ID, Name,
and/or Customer; see Creating a Quick Service Filter.

any filter. You can also use the Set Filter as Default toolbar icon to set
the current filter as the default (automatically activated when the Service
The icon is disabled if the currently applied filter is already the default.

| Use the Show Tunnels or the Show MoT Trails icon to show the
tunnels or MoT trails associated with selected services; see Viewing
Associated Traffic Entities.

Creating a Quick Service Filter

The Quick Filter function enables you to quickly filter the services in the
Services pane, or throughout the database, by Service ID, Name, and/or
Customer. This method does not involve a filter template and is defined per
use.
To quickly filter services by label, service ID, and/or

customer:
1. Open the Service List window, as described in Accessing the Ethernet
Service List Window.
2. In the Services pane, click the Quick Filter icon . A quick filter field
bar opens at the top of the pane.
3. Enter a text string to the relevant fields to filter in services with field values
that include this text. See the field descriptions in Services Pane Columns.
(For the Type (service type), select P2P, MP2MP, Rooted MP, P2MP, or
L1from the dropdown list.)
You can enter partial strings to identify all services with this text anywhere
in the fields. For example, enter xy to find all services with xy anywhere in
the field value. (Wildcard character is not used.)
NOTE: The text field filter is case sensitive.
The table immediately adjusts to show services previously in the table

that satisfy the filter criteria.
OR


composition of services displayed.
also backspace to empty a filter field.)


4

Working with Advanced Service Filters

Advanced filters enable you to view a subset of the services in the Service List
| Service attributes (like specific rates)
| Selected objects (all services traversing specific objects)
settings to the open Service List window. Any other filter can be applied as
needed at any time.

the services listed in the Services pane. In addition, the currently applied filter
can be set as the default, defining the services that the Service List window
automatically opens with in a new session.
TIP: Opening the Service List window may be time

consuming if many services are filtered in. If you choose "No
Services" as the default filter, the window initially opens
quickly without any services in the Services pane.
To apply a filter, and (optionally) set it as default:

1. In the Service List window, select a filter from the Filter dropdown list
.
The filter is immediately applied, reflected in services listed in the Services
pane.
2. You can optionally set the current filter as the default by clicking the Set
filter as default icon . The Service List window now automatically
opens with this filter in any new session.


Advanced filters are used to search the database for trails that satisfy the filter
criteria. The following describes how to create or edit a filter that includes

relevant. For information how to create a filter with object
preselections in the LightSoft main window map, see
To create or edit a filter:

1. In the Traffic menu, select Services > ETH Service Filters.
OR
On the main toolbar, click the Open Service Filters icon . The Service
Filters dialog box opens. (You can view a summary of parameters and
topology elements for an existing filter by selecting the filter in the Filters
pane.)


OR
Click the Show Tree button to open the Topology Tree pane (as shown
in the example). The button changes to Hide Tree for hiding the tree if
not required. This is used for filtering by selected objects in Step 5.
3. In the Filter Name field, type a name for the new filter.
OR
If you are editing, this field is disabled. You can save as a different name
for the modified filter, if needed, when saving the changes.
a. In the Filter By area, select a parameter's checkbox.
b. Specify the required value. While a parameter is highlighted, the Value
area shows either:

Radio buttons


displayed in the Value area .


If filtering by Label and Customer text entry fields, use the
wildcard character * to filter in all services where the field
value includes a specified string, for example:
xy* to filter in all services with the field value starting
with xy
*xy* to filter in all services with xy anywhere in the field
value
*xy to filter in all services with the field value ending with
xy (this pattern is not recommended).
OR
If filtering by any other text fields, or if any resource objects
are selected in the Topology Tree area (see next step), enter
xy to find all services with xy anywhere in the field value.
(Wildcard character is not supported.)

these rules.
5. If you want to filter by selected resource objects to which services are

associated, move objects from the Topology Tree area to the Topology
tab, as follows:
Select the topology layer for the filter: ETH/MPLS (default). The
Physical layer can also be selected, enabling you to select physical
nodes. Double-click the root of the tree to refresh its elements.
Select the objects for which you want to filter services (drill down
in the tree). To select multiple objects, press SHIFT and click.


Save.
OR
7. Click Close to close the Service Filters dialog box.

You can also edit a user-defined filter via the Service List window.
To edit a filter via the Service List window:

1. Open the Service List window.
.


You can create a new service filter with objects selected from the LightSoft
main window map. This avoids having to select the elements again when
creating the filter. These objects are automatically reflected in the Service List
window map and in a "Temporary" filter which you can build on.

1. In the LightSoft main window map, select any objects that you want to
include in a new service filter.
2. Open the Service List window: From the Traffic menu, select Services >
ETH Service List. Or, on the toolbar, click the Service List icon .
The Service List window opens with the selected objects and with the
Temporary filter preselected in the Filter selector dropdown
list.
the main window before the Service List window was opened). The Edit
Topology pane. (The filter name is "Temporary" until Save As is used to
save under another name.)


Rename, Delete, Set Default Filter actions

This section describes how to rename a filter, delete a filter, or set a filter as
default (automatically applied when the Ethernet Service List window opens).

1. From the Traffic menu, select Services > ETH Service Filters.
OR
On the main toolbar, click the Open Service Filters icon . The Service

The New and Edit buttons are used to create and edit filters; for details, see
Creating and Editing Advanced Filters.
3. Click Close to close the Service Filters dialog box.

Selectable Service Filter Attributes

If no selections are made, all services are included.
Configurable selection criteria for the overall service attributes
Ethernet Svc Attribute Selection Criterion Configuration

Actual Traffic State Enabled, Disabled, and/or Partial, selected from the list.
Multiple values can be
selected.
Administrative Service Yes or No.
Enable
BSC Policer Profile String with wildcard characters.
Created By User Name of LightSoft operator. String with wildcard
characters.
Created With GUI, XML, or Acquisition, selected from the list.
Creation Time Date/time range selected using From and To selector
fields.
Customer Label string including wild cards denoted by *.
Dedicated Tunnels Only Yes or No.
Dual-Homing Not Dual Homing, Access Link, or Internetwork Link.
EthVPN ID Date/time range selected using From and To selector
fields.
Label Service label string including wild card denoted by *.
Modification Time Date/time range selected using From and To selector
fields.
Modified By User Name of LightSoft operator. String with wildcard
characters.
Modified With GUI, XML, or Acquisition, selected from the list.
Policer Profile Name of policer profile. String with wildcard characters.
Note: Service appears in the filtered list if the policer
appears at any endpoint or is the BSC policer profile for
the service.
Protected Tunnels Only Yes or No.
Service State OK, Incomplete, or Non-conformant, Inconsistent, or
Failed.
Type Service type. P2P, MP2MP, RootedMP, P2MP, and/or L1
selected from the list. Multiple values can be selected.
Unacknowledged Yes or No.
Modification
vFIB Quota Ranges of vFIB quota separated by commas.
You can also select a list of ports, LEs, or groups from the Ethernet layer
Topology tree, which adds them as an additional selection criterion.

Entity Selection Criterion Comment

Port List of Ports Services with any endpoint in the list are
included.
LEs List of LEs Services with any endpoint on the LE are
included.
Groups List of Groups Services with any endpoint in the list are
included.
Other Service "Filters"

You can also generate Service lists from other entities in LightSoft:
| Tunnels: Services for which a tunnel is one of the primary tunnels for the
service on the MPLS Network; see Show Associated Trails, Services, or
Protected Tunnels.
| Policer Profiles: Display the list of services for which a selected policer
profile is configured as one of the service endpoints or is the BSC Policer
for the service; see Viewing Services Associated with a Policer Profile.
Reconnecting Services
You may sometimes need to reconnect a service. This is typically required if a
problem arises during the service creation process. For example, if an NE
included in a service is disconnected at the time it is created, the resulting
service is left in an incomplete state. In this case, reconnecting the service
sends the missing VSIs to the LEs.
To reconnect a service:
1. On the LightSoft main menu bar, select Services > Service List. The
Service List window opens.
2. Select the checkboxes of the service/s you want to reconnect.
3. Click the Reconnect icon (enabled when non-L1 incomplete services

are selected). A confirmation window opens.
4. Click OK to continue. A completion message appears, describing the

operation result and listing nonfatal errors. For more information, see

Editing and Deleting Services

This section describes how to edit or delete selected services. The actions can
be implemented in the network either immediately or postponed to a later time.
When the actions are for future use, their details are exported to an XML file
and are put into effect by importing the file into LightSoft.
NOTE: Edit or Delete operations may fail due to LightSoft

being unable to set up the service in the network as defined.
This problem typically arises during service creation if an NE
included in a service is disconnected or a craft terminal is
connected, causing the resulting service to be incomplete.
To resolve this problem: After the NE is uploaded or the craft
is disconnected, reconnect the service to send the missing
VSIs to the LEs.
Editing Services
The Edit Service window provides extensive service editing options, including
access to parameters and characteristics present in Create Service window
panes. Services can also be edited for either immediate or future effect in the
network.
Service modification in LightSoft does not cause service interruption.
Service attributes can be edited provided the correct user capabilities are
present. Services can be edited even if the edit operation is traffic-affecting. A
Service can be modified by the addition or deletion of endpoints; Service
endpoints cannot be edited.
NOTE:
You can also edit certain service attributes directly from
Service List window panes using the Edit Attributes
function, as described in Service Details Tab.
Some parameters that are present in both the Service
Properties pane and the Edit window may be enabled for
editing only from one or the other location (for example,
certain EoS service parameters).

When using the Edit Service window, you can edit services for either
immediate or future effect in the network. When the editing is for future
application, the edit changes are exported to an XML file and put into effect by
importing the file into LightSoft; see Exporting Services. In this context, the
Export operation provides the following mode possibilities:
| Export for Edit mode: Creates an edited service on XML which Import uses
to replace the existing service.
| Export for Create mode: Creates a backup service that the Import uses to
reinstate a deleted service.
If an existing P2P service is modified by configuring an alternate Policer
Profile where the CIR is greater than the existing profile, and if the Support
automatic increase of tunnel bandwidth Preference variable is true, LightSoft
does the following:
| The currently selected tunnels are used if their bandwidth is sufficient for
the CIR increase.
| Otherwise, another tunnel with sufficient bandwidth is selected.
| If no such tunnel exists, LightSoft verifies if it is possible to increase the
bandwidth of the current tunnel to support the modified service. If so,
perform the tunnel bandwidth modification.
It is sometimes possible to change equipment endpoint configurations without
editing the service from LightSoft, for example, from GbE to FC-1G, or to
modify the rate setting of the TRP_C.

Editing a Service
To edit a service:
1. From the Traffic menu, select Services > Service List. The Service List
window opens.
2. In the Services pane:
Select a service and click Edit service on the toolbar.

OR
Right-click a service and select Edit Service from the shortcut menu.
The Edit Service window opens, showing the links used by the
selected service.
3. Make the required changes to service parameters and/or endpoints. The

window contains essentially the same panes and parameters as the Create
Service window. For details, see Creating Ethernet Services.
4. (Optional) Click the Complete service icon . LightSoft determines how

to implement the service and displays the details in the Network pane.
listing nonfatal errors. For more information, see Performing Service
Create Service Failure in Creating Ethernet Services.

5. Click the Activate service icon to activate the edit changes on the
network.
The Progress bar shows the progress of bundle service processing (if
applicable). An Abort button is included to stop the operation if needed.
At the conclusion of the Activate processing, a message appears describing
the result of the operation and listing nonfatal errors. For more information,
see Performing Service Operations. If the Activate step encounters a
problem, see Diagnosing a Create Service Failure in Creating Ethernet
Services.
NOTE: If Complete Service was not performed before, or if

it was followed by an action that would change the links used
by the service (such as a change of endpoint), then it will
automatically be performed/repeated before the service is
activated on the network.
6. If you want to create an XML file with the edit changes for backup
purposes, perform the following to export the edit details to an XML file,
click the Export to XML icon on the window toolbar.
For information about how to eventually implement the edited service in the
network, see Importing Services.

Deleting Services
You delete services in the Service List window. You can delete several services
at the same time by selecting all of them simultaneously. All services are
deleted the same way, whether they were created in LightSoft or created in the
EMS and later acquired by LightSoft.
When a service is deleted, all VSI/FDFrs defined for the service are also
automatically deleted. If this does not occur (for example, if one of the NEs
was disconnected at the time the service is deleted), the service remains in the
Service List window in an Incomplete or Failed state. The service is removed
from the list when all resources are deleted.
You can delete services for either immediate or future effect in the network.
When the deletion is for future application, its details are exported to an XML
file and put into effect by importing the file into LightSoft at a later time; see
Exporting Services.
Service deletion – Activate does the following:
Deletes a service by deleting:
| VSIs for the service at all PEs in the MPLS network.
| VSIs of the service for all LEs for which the service is defined in the PB
network.
To delete a service:
1. From the Traffic menu, select Services > Service List. The Service List
window opens.
2. In the Services pane, select the checkboxes of one or more service/s you
want to delete.
a. Right-click any selected line in the Services pane and select Delete.
OR
Select List > Delete Service.
OR
Click the Delete Service toolbar icon.
A confirmation window opens.
b. Click OK to confirm. A completion message appears, describing the
operation result. For more information, see Performing Service
Operations.
OR

4. If you want the service deletion to be implemented in the network at a later

Click the Export to XML icon on the window toolbar.

OR
Right-click one of the selected services and select Utilities > Export
from the shortcut menu. The Export Services dialog box opens.
network, see Importing Services.

Acknowledging Service
Modifications
EMS-created or modified services acquired to LightSoft are automatically
assigned "Unacknowledged modification" status, thereby flagging the service's
modifications for review. Details of unacknowledged modifications associated
with a service are provided, enabling the LightSoft user to verify each
modification's validity.
If a modification is determined to be valid, it can be acknowledged and the
unacknowledged modification status lifted. Alternatively, the unacknowledged
modification status is removed by modifying the service from LightSoft.
The Unacknowledged Modification = Yes status remains with the service until
all its modifications are acknowledged. You can acknowledge modifications
either individually for a service, or for services as a whole without reviewing.
Irrespective of its current status, the service still continues to carry traffic in the
normal way.
To acknowledge service modifications without reviewing:

1. In the Service List window Services pane, select service lines (highlight a
line, or select checkboxes) where the Unacknowledged Modification
column shows Yes. (It is helpful to perform a column sort; see Sorting List
Lines.)
2. To acknowledge modifications without reviewing:
Right-click and select Service Operations > Acknowledge
Modifications. The modifications associated with the selected services
are acknowledged. The Unacknowledged Modification column for
those services changes to No.
OR
3. To view and acknowledge modifications individually:
a. Right-click and select Service Operations > View Modifications. The
Unacknowledged Modifications window opens; see Unacknowledged
Modifications Window.
b. Select a service in the Service Details pane. Its associated
unacknowledged modifications are listed in the Unacknowledged
Modifications List pane.
c. Select one or more modification lines and click Acknowledge. Those
modifications are removed from the list.
Once all modifications for a service are acknowledged in this way, the service
is considered to have the status Unacknowledged Modification = No.

Unacknowledged Modifications Window

The Unacknowledged Modifications window is used to view services with
Unacknowledged modification status, and enables acknowledging them.
It shows the services selected from the Services pane in the Service Details
pane and, for a unacknowledged modifications You acknowledge
modifications
It contains the following panes:

| Service Details: Lists the unacknowledged services selected from the Trail
List window Services pane.
| Unacknowledged Modifications List: For a service selected in the Service
Details pane, lists the associated modifications that are not yet
acknowledged.
You acknowledge a modification by selecting it and clicking
Acknowledge. It is removed from the list.
Unacknowledged Modifications window fields
Field Description
Service Details
EthVPN ID See Basic Parameters Pane.
User Label See Label in Basic Parameters Pane.
Customer See Basic Parameters Pane.
Service Type See Type in Basic Parameters Pane.
Unacknowledged Modifications List
Modification Date/time the modification was done at the EMS.
Time
LE Associated LE.
ME Associated ME.

Field Description
Change Type Create, Edit or Delete.
Record Type Endpoint or FDRr.
Endpoint ID Associated ME.
Batch Service Operations

This section describes how to perform Create, Edit, and Delete service
operations in a batch by exporting and importing service definitions to/from an
XML file. The Export operation enables you to save the data of selected
services into an XML file for either network planning or backup purposes. The
Import operation translates the data stored in the XML file and sends this
information to LightSoft according to the requested operation for each service
in the file.
Records in the XML file specify the commands and parameters of actions. Both
import and export records coexist in the same XML file. For information about
the XML syntax, see Import/Export Traffic Syntax.
process. You can find this log file in the directory ~nms/NMSServices. The log
file name is the same as the XML file, with the .log extension.
You can also export/import service XML files via UNIX, which may include
prescheduling using the UNIX crontab command; see the generic trail, tunnel
and service export/import procedure in Exporting/Importing Traffic Entities via
UNIX.
OPTIONAL FEATURE: XML service operations are

If not purchased, menu options pertaining to exporting and
importing service definitions are unavailable.

Exporting Services
This section describes how to export L2 Ethernet service definitions to an XML
file for either network contingency planning and design purposes or backups in
case of system failure.
Details of services can be exported to an XML file for backup purposes.
Exported services are automatically implemented in the network by the Import
Service definitions either from the Service List window or in XML file format
can be converted to CSV for viewing in a relational database program. For
details, see Exporting Services to CSV.

Exporting services to XML for network planning purposes is performed in
conjunction with changes to services or removal of services:
| Planned changes to an existing service are created using the Edit Service
window; see Editing Services. For this purpose the services are exported to
XML using the Export Services window's Export for Edit mode.
| Planned removal of existing services is performed using the Service List
window; see Deleting Services. For this purpose the services are exported
to XML using the Export Services window's Export for Delete mode.
network. They are exported to XML until they are needed. When the new
network design is ready to be implemented, the planned services may be
imported to LightSoft as part of the active network.

You can export services so that they can be restored if inadvertently deleted or
corrupted:
| Services that were deleted from the network can be restored by importing.
For this purpose the original services must be selected from the Service
List or Edit Service window, and the export must be performed using the
Export Services window's Export for Create mode.
| Existing services that become corrupted can be restored by importing. For
this purpose the original services must be selected from the Service List or
Edit Service window, and the export must be performed using the Export
Services window's Export for Edit mode.

Export Services Procedure

You can export services to an XML file for backup purposes.
NOTE: XML records are exported in the order that they are
displayed in the Service List window, and are eventually
imported serially, in the same order.
To export services to XML:

1. If you are creating an XML file for:
Backup purposes: From the Service List window, select one or more
services; see Performing Service Operations.
You can also perform this action from the Create Service or Edit
Service window on the current service that has just been activated; see
Creating Ethernet Services, or Editing Services.
OR
Deleting services: From the Service List window, select one or more
services that should be deleted (but do not click Delete); see Deleting
Services.

OR
If you are in the Service List window - In the Services pane, right-click a
service and select Service Utilities > Export Services from the shortcut
menu. The Export Services dialog box opens.

3. Type the file name to which you want to export the services, or select an
existing one from the dropdown list.
NOTE: The following characters (separated by commas)

are not allowed in the file name:
*, ?, !, |, \, /, ', ", {, },<, >, ;, <comma>, ^, (, ), $, ~, #, @,
<space>, +, =, &
4. If the file already exists, two radio buttons are enabled:

Select Overwrite file to overwrite the existing file, or
Select Append to file to add the services to the existing file (preserving
its previous contents).
5. Select the Batch Operation to be applied on all the services to be exported:
Backup purposes or Create to be applied at a future time: Select Create.
Editing to be applied at a future time: Select Edit.
Delete to be applied at a future time: Select Delete.
6. Click Export. The service definitions are saved as an XML file.
service is processed. An Exporting Failed message opens. An export file
will be produced containing definitions of the services that completed
processing up to that point.
Export Services to CSV

You can export Service List window data to a delimited-format CSV file for
LightSoft also enables you to export services in XML files to CSV using a
command line application.
To export services to CSV:

| See the generic procedure in Exporting List Data to CSV.


Importing Services
LightSoft supports import of an XML File of L2 Ethernet Services and
activation of the contained services. This section describes service definition
import from XML using LightSoft menu options.
To import service definitions from XML files via LightSoft:

1. On the Traffic menu, select Services > Import Services.
OR
On the main toolbar, select Import Services . The Import Services
dialog box opens.

3. Select one of the following radio button options:
Check Syntax: Checks the syntax of the XML file.
Complete (Create/Edit only): Checks syntax and finds a path for the
services (like Complete in the Create Service procedure).
Activate/Delete: For Create/Edit, checks syntax, finds a path, and
activates the services in the network (like Activate in the Create Service
procedure). For Delete, checks syntax and deletes the services.
The mode defined when the XML file was exported determines the nature
of the action performed by the Import (Create, Edit, or Delete).
4. Click Import. The file is imported, and corresponding services are
reflected in the Service List window.
The Import Status pane shows the total number of services in the import,
and the numbers that imported successfully or failed to import.
service is processed. An Importing Failed message opens. The services that

16
Provisioning Optical Trails
In this chapter:
Overview ....................................................................................................... 16-1
Optical Trail Concepts ................................................................................... 16-2
Optical Trail Creation Options .................................................................... 16-10
Additional Cases .......................................................................................... 16-11
Initial System Setup ..................................................................................... 16-18
Creating Optical Trails Through Discovery ................................................ 16-19
Optical Trail Parameters .............................................................................. 16-23
Individual Optical Trail Provisioning .......................................................... 16-25
OMS Trail Provisioning .............................................................................. 16-27
OCH Trail Provisioning............................................................................... 16-34
LP Trail Provisioning .................................................................................. 16-42
Trail Acquisition by Synchronization .......................................................... 16-48
Other Actions on Optical Trails................................................................... 16-55
Viewing Optical Channel Availability ........................................................ 16-56
Overview
This section describes how to create and manage optical trails using various
methodologies.
LightSoft supports optical trails in a multi-layer hierarchy:
| Optical Multiplex Section (OMS) trails
| Optical Channel (OCH) trails
| LightPath (LP) trails
| EoS trails that traverse the optical layer
See Optical Trails for descriptions of the optical trail types.

Provisioning Optical Trails LightSoft User Manual
Optical Trail Concepts

The following sections provide some key optical trail concepts. Other concepts
are explained in context.
| Optical Devices
| Optical Links and Ports
| Optical Trails
| Optical Trail Protection
| Channels
| Relations between Ports or Cards
| Alarms Master Mask (AMM)
Optical Devices
The following is an example optical network showing representative elements
and a pattern of optical trails.
The devices are separated by fiber of varying length - in the range of meters
within a site, or kilometers between sites. In the above graphic, distance fibers
are indicated with a loop .

LightSoft User Manual Provisioning Optical Trails
Optical devices may include the following:
Client Equipment at the Network Edge

"U" in the diagram, including UMEs and managed ports such as EIS and DIO.
Line Cards
T" in the diagram, including:
| SDH card with bidirectional ports (for example, SIO) - aggregates client
signals to an optical channel.
| Transponder - transmits the signal over a specific channel.
| Combiner - combines multiple input signals into a higher bitrate,
aggregates different clients into a specific optical channel, and transmits the
signal over that channel. Combiners comprise three families and utilize
EoS or high order SDH trails, as follows:
Data combiners - using GbE/FC/FICON input, their traffic traversing
EoS trails (with payload type as described earlier in the Data over
WDM section).
SDH-OTN combiners - using STM-16 inputs, STM-64 or OTU-2
outputs, their traffic traversing VC-4 trails.
4 x STM-16 transparent combiner (CMBR10T card) - transparently
aggregating four STM-16 input streams into one OTU2 output, their
traffic traversing up to four LP trails.
For more about combiners, see Combiners in Optical Networks.
| Regenerator ("R" in the diagram) - a transponder used in a regeneration
site, which regenerates an optical channel through optical 3-R regeneration.
A regenerator generally causes an OCH trail to terminate, as shown in the
diagram. An exception to this is ODU regenerators (such as
TRP25_4REG0), which yield end-to-end OCH trails; see Regenerators in
Optical Networks in Additional Cases.

Multiplexing Devices
These include:
| Terminal multiplexer/demultiplexers ("M" and "D" in the diagram).
| Optical Fixed Add/Drop Multiplexers (OADM) and Reconfigurable
OADMs (ROADM).
Amplifiers
"A" in the diagram, including:
| According to network position:
Boosters - in close proximity to a Mux.
Pre-amplifiers - in close proximity to a DeMux.
Inline amplifiers - for distance amplification, either standalone sites, or
in close proximity to an OADM. (Inline amplifiers cannot be used in
conjunction with a ROADM. Similarly to a Mux or DeMux, a ROADM
is only used in conjunction with a pre-amplifier or booster).
| According to technology:
Single amplifiers (a single game block).
Dual amplifiers, with two game blocks acting independently of each
other. Dual amplifiers are, for example, OFA_2, OFA_M,
MO_OFA_PHBC, and MO_OFA_HBC.
Dual-stage amplifiers with two game blocks acting in tandem, and
including a mid-stage Dispersion Compensation Fiber (DCF). A DCF
uses a negative dispersion index to compensate for dispersion along the
fiber. The OFA_M is a dual-stage amplifier.
C band Optical Supervisory Channels (COSC, also known

as OSC filter)
Enable transfer of management information via an outband signal between sites
in the optical network (in conjunction with MECP card inband signal transfer
in SDH networks). These should not be connected using topology links. See
Additional Cases for special configuration recommendations.
Unmanaged Elements (UMEs)

"U" in the diagram, but may be any element in the topology. Usually describe
either customer terminals or DCFs, but may be transponders, OADMs, or any
other element in the topology.

Optical Links and Ports

LightSoft optics uses the following main categories of links and ports:
| OTM links between OTS ports, and OPS links between OPS ports.
| OPS1 or OTU links between TRPs/CMBRs and multiplexing devices.
| OPS or OTU links connecting the clients (for example, UMEs and SIOs) to
transponders, combiners, and similar cards.
| Virtual links, the link representation of trails in an underlying technology
layer, such as SDH virtual links resulting from an LP trail in the optical
technology layer. For example, when a trail connects two SDH cards to an
optical network, the LP is represented in the SDH layer as a virtual link
between the two SDH ports.
NOTE: OTM links in LightSoft are indicated as OTS links

in the EMS-XDM.
Optical Trails
LightSoft supports the following types of optical trails:
Optical Multiplex Section (OMS) Trails

OMS trails are optical trails between multiplexing devices (MDs). They can be
unidirectional or bidirectional. They behave as server trails that carry multiple
OCH trails in fixed groups - typically CWDM - 4 or 8 channels, and DWDM -
16, 32, or 40 channels. Amplifiers may be in the path of an OMS trail.
Multiple OMSs, connected in tandem, cause alarms to be reported only with
respect to the directly associated OMS trail segments, and not at other segments
along the path. For more information, see COSCs in Optical Networks.

Optical Channel (OCH) Trails

OCH trails are client trails of an OMS trail, and use the channels of the OMS
trail. An OCH trail carries the LP client input signal trails, one or more LPs per
OCH trail. For example, combiner cards receive and combine multiple client
signals (mostly SDH or Gigabit Ethernet) into one 2.5 Gigs or 10 Gigs
aggregate that can traverse one channel.
In general both ends of an OCH trail terminate in a transceiver
(transmitter/receiver) at the network edge. In cases where a transponder is
connected as regenerator between a pair of MDs (two OADMs and/or
Mux/DeMux), the OCH trail terminates in the regenerator, entering it on one
trail segment and leaving it on another (as shown in the diagram).
LightPaths (LPs)
LP trails are end-to-end optical trails representing the client input signal. LP
trails typically traverse from UME to UME - end to end, irrespective of any
regenerators in their paths. If not connected to client equipment, the LP
terminates in the client port of the transponder.
LightSoft differentiates between types of LP trails through the payload
parameter, for example, STM-n for SDH clients, GbE for GbE clients, and FC-
2G for DSR (Digital Signal Rate) clients. An OCH trail can have multiple LP
client trails (see OCH trail description above). The same LP trail may be the
client of multiple OCH trails.
High Order, including SDH or EoS - Data over WDM

Trails
For certain Data combiners, the client traffic is categorized as SDH or EoS -
Data over WDM trails (due to the SDH fabric of CMBR cards). The payload
type of the trail indicates the specific value "ETH over WDM".
These trails are acquired through trail synchronization or Discovery. In the
Trail Consistency Indicator window, specify HO SDH as the trail rate that
you want to acquire.
The trail filtering mechanism includes a Data over WDM trail filter.

Optical Trail Protection

The following protection is available according to the trail type:
| LP trails may be protected using the PGO mechanism of line cards; see
Relations between Ports or Cards. The protection path is the path that uses
the standby card.
| OCH trails can be unprotected, underlying protected, current protected, or
current and underlying protected.
Underlying protection can derive either from external protection by the
user (the user declaring a link protected), or from OMSP protection.
Current protection derives automatically if the line ports from
transponders are associated by a protection group (PG) object.
For more information, see OCH Protection and and Protection Group
Object (PGO) in Relations between Ports or Cards.
| OMS trails may be specified as protected by underlying links, meaning, if
the links that they traverse are protected, the OMS trails are protected.
OMS protection may be derived from the network according to the
presence of OMSP cards and their "Protection groups" and/or the state of
the underlying links (you can set them to be "externally protected").
Channels
Dense Wavelength Division Multiplexing (DWDM) and Coarse Wavelength
Division Multiplexing (CWDM) technologies, supported by LightSoft optics,
describe the carriers over which optical signals are transmitted. DWDM uses a
grid of 40 or 80 frequencies from 192.05 THz to 196.0 THz. CWDM uses a
grid of four or eight channels denominated in wavelengths, from 1471 nm to
1611 nm. For detailed frequency, wavelength, and channel spacing
information, see Channel Frequencies and Wavelengths.
In this manual, we refer to the wavelength or frequency carriers generically as
"channels". (Other terms that may be present in the literature, like "channel
frequency" or "tuned frequency", are avoided.)
Channels as defined here should not be confused with OCH (Optical Channel)
trails, which are also sometimes referred to in the literature as channels. In this
manual we refer to such trails as "OCH trails".
For more information about optical channels, see Optical Trail Parameters.

Relations between Ports or Cards

The following types of relations between ports or cards facilitate protection or
bidirectional recognition:
Bidirectional relation between ports

Unidirectional ports on the same card that share the same rate automatically
acquire certain bidirectional properties. A relational pointer between them
creates a Snk/Src relation, allowing them to act as a single bidirectional port.
When Discover Optical Trails or individual trail creation is performed, all ports
with the relational pointer on at least one end of the trail are treated as
bidirectional. This association enables you to create a bidirectional trail by
selecting only a single port - the other port is automatically located by the
pathfinder.
This feature is present through hard-coded modeling in the card and requires no
user intervention to implement.
Protection Group Object (PGO) (optical protection

group)
In order to achieve a LP trail protection configuration, line cards such as TRP
or CMBR must be installed in pairs. For example, two TRP cards (main and
standby), using splitter and coupler accessories, convey the same information
from the network to the same client port along two different paths, with the
standby card transmitting in place of the main in the case of a breakdown.
For this functionality to operate, you must perform a configuration between the
two cards in the EMS (called "association of cards"), which creates a Protection
Group Object (PGO) in the main card. If splitters and couplers are connected,
but this configuration was not performed at one or both ends, the PGO
relationship will not be present in the cards and the trail will be invalid.
For more information, see Optical Trail Protection and OCH Protection.

Alarms Master Mask (AMM)

When optical cards wake up following assignment, the AMM is set to
"monitored", that is, the alarms severity is as defined by default. You can
change the severity profile and have a different set of alarms reported or not
reported. When the AMM is set to "not monitored", all the alarms of the object
are set to nonreported. When the AMM is set again to "monitored", the
reported state is restored.
On trail creation, the system sets the AMM to ON to all the objects
encapsulated within the port that holds the trail endpoints and have reported
alarms, as follows:
| AMM to OMS trails include the OTS objects in which the OMS endpoints
are encapsulated.
| AMM to OCH trails include the OPS and the OCH objects in all OCH trail
endpoints.
In trails where the OPS port encapsulates higher layers like OTU/ODU,
they are dealt with as well.
| AMM to LP trails include the line card client ports and the objects that are
encapsulated in them (e.g. OPS_0 in a TRP25_2S or OPI in a
TRP25_4AD). Note that these ports are not necessarily the trail endpoints.
On trail deletion the AMM state is set to not monitored.

Optical Trail Creation Options

Optical (and optical-based SDH) trails can be created in the following ways:
Automatic Discovery
The Discover Optical Trails feature can be used to automatically acquire all
OMS, OCH, LP, and EoS trails in a single operation. This method is especially
useful when the system is first installed. For more information, see Creating
Individual Trail Provisioning

You can create individual OMS, OCH, and LP trails using an interface very
similar to that used for SDH trail creation. This allows control over trail
attributes such as the trail label and the Alarm Master Mask. If a new LP trail is
requested and the corresponding OCH and/or OMS trails do not yet exist, they
are created automatically. If a new OCH trail is requested and the
corresponding OMS trails do not yet exist, they are created automatically. For
more information, see Individual Optical Trail Provisioning.
Acquisition by Synchronization
Trails can also be acquired directly through the Trail Synchronization
window. This method synchronizes the trails to be carried by a selected link or
the entire network, importing the trail information from the EMS to the
LightSoft database. Trails that do not meet predetermined classification rules
can be created only through synchronization. For details, see Trail Acquisition
by Synchronization.
EoS Trails that Traverse the Optical Layer

EoS trails that traverse the optical layer (as needed in the case of certain data
combiners) are created by the Discover Optical Trails feature, in addition to the
requisite optical trails; see Creating Optical Trails Through Discovery. These
EoS trails can also be created by admitting the high order SDH trail using the
Trail Consistency Indicator window; see Performing Trail Synchronization.
Other Optical Topology Actions

Optical trail parameters can be edited and optical trails can be deleted. Optical
components can be inserted or removed from links, with existing trails
automatically arranged to accommodate the changes. Multiple LP trails can
also be associated as a single service. For details, see Other Actions on Optical
Trails.

Optical LEs may be created either before or after optical trails are created.
OPTIONAL FEATURE: The optical trail provisioning

mechanisms are subject to the optical layer being enabled,
which is a fully integrated add-on capability, available on a
cost basis. If not purchased, the functionality and related
Additional Cases
This section describes some network planning issues which should be
considered prior to system setup and trail creation:
| LP Without Client Equipment Termination
| COSCs in Optical Networks
| Combiners in Optical Networks
| Regenerators in Optical Networks
| Optical Performance Monitoring (OPM)
LP Without Client Equipment Termination

LPs can have endpoints in a transponder or in a port of the client (such as SDH
port, UME, or data card). If the endpoint is on a transponder without client
equipment connected to it, as in the example below, then individual trail
provisioning cannot be performed using the Create Trail window. In this case,
the procedures described in Creating Optical Trails Through Discovery or Trail
Acquisition by Synchronization can be used instead.

COSCs in Optical Networks

Construct the optical topology so that each COSC is combined in the same LE
as the element (fiber amplifier, Mux, or DeMux) that precedes or succeeds it.
This enables a single OMS trail to span the entire path, and avoids alarm
reporting problems caused by intermediate OMS trail terminations and multiple
OMSs in tandem. If you ensure that the OMS trail is end-to-end in this way, all
alarms are displayed regardless of where the alarmed devices are positioned.
OMS trails would otherwise terminate at each separate COSC LE, causing a
string of OMS trails to be formed rather than a single continuous OMS trail.
Alarms would then be reported only with respect to the directly associated
OMS trail segments, or only on downstream segments, as follows:
| Card out alarms on a specific COSC are only seen on the directly adjoining
OMS trails, and not on other OMSs along the same path.
| Loss of Signal on an amplifier is seen only on the directly associated OMS
segment, and not on other segments along the same path.
To create OMS trails that are not fragmented:

1. In the optical layer, for each COSC, create a secondary LE that combines
the ports of both the COSC and the adjacent fiber amplifier, Mux, or
DeMux; see Creating Secondary LEs.
2. Create internal links within the LE to continue the path between the ports
(except for the COSC ports) in the same way as existed before the
secondary LEs were created; see Creating Topology Links.
Although the ports of the different devices continue to be serially connected
by multiple links, they are visually represented in LightSoft by a single
(amplifier, Mux or DeMux) LE icon. The COSC will not be explicitly
visible in the optical layer map view.
This enables the Discover Optical Trails process to create a single OMS trail
that spans the entire path between MDs. It additionally enables the links
between the sites to have the correct alarm status, since the alarm status is
derived from the amplifier rather than from the COSC.

Combiners in Optical Networks

When the optical path includes combiners, a LightSoft feature enables virtual
links to be correctly reflected in the SDH layer for pathfinder purposes. Certain
actions must be performed in the EMS or LCT for this feature to be
implemented, as described in the following use case.
The diagram below shows a typical configuration of SDH-OTN combiners (at
A and B), connected as follows:
| On the client side, to SDH ports, with four STM-16 ports as endpoints.
| On the network side, to an ODU1 or ODU2 (optionally traversing a WDM
network).
This configuration yields an OCH trail, 3 LP trails, and 16 VC-4 trails per
client port (visible as the VC-4 virtual links on the SDH layer).
NEs with SDH bidirectional ports (non-UME endpoints)

The SDH layer may be a typical SDH ring/mesh network, including NEs with
SDH ports where the endpoints are not UMEs. The LP virtual link is already
visible with 16 VC-4s traversing it.
For older combiners, the following additional steps are required:
1. Perform one of the following actions using the EMS or LCT (procedure
differs according to whether this part of the network is intended to support
high order or low order traffic):
For high order traffic: Create high order XCs manually in the SDH
network.
For low order traffic: Terminate the VC4s at the point where they enter
the SDH network (the SDH ports connected to the combiner client
ports).

2. Create the end-to-end trail:

High order trail: Create the trail using either the Discover Optical Trails
or Trail Synchronization methods; Creating Optical Trails Through
Discovery and Trail Acquisition by Synchronization.
Low order trail: Create the trail using only the individual trail creation
method via the Create Trail window accessed from the SDH layer; see
Creating SDH and EoS/MoT Trails.
The resulting topology on the SDH layer is shown in the following diagram:
CMBR 1+1 Topologies

In the specific case where protected combiners are used, the virtual links are
not directly visible on the SDH layer. You must instead create two independent
topologies - the optical topology is independent of the SDH topology.
Two options are available (with or without the use of splitter couplers):
| Place splitter couplers, having the OTN UME with the SDH port as an
endpoint. Then, further to the example in Combiners in Optical Networks,
64 x VC-4 trails will have endpoints at the UME.
OR
| No splitter coupler connections. Then, further to the example in Combiners
in Optical Networks, 64 x VC-4 trails will have their endpoint in client
ports.

To accommodate protected combiners for pathfinder

purposes:
1. Perform trail synchronization. The VC-4 trails will then be protected VC-4
X trails with endpoints in the client ports of the CMBR10.
2. On the SDH layer, connect the SDH cards directly to each other.
SDH OTN Combiners

Combiner connection with trails to a splitter-coupler is supported only for the
CMBR10T. In the case of other combiner types, the trails between the
combiner and the UME will not be classified. The following configurations,
which do not involve splitter-couplers, are suggested:
For an integrated SDH-optical network, a single link between the main CMBR
port and the UME, as follows:

For an independent optical network, a configuration with two links is

suggested, one for the main CMBR port, one for the standby port, to a UME
that has two ports defined.
Other CMBR Topologies

In CMBR10_T and OMCM25_4 topologies, the combiners are characterized
by multiple ports, each connecting to a UME. The OCH spans the combiners.
The LP traverses from UME to UME.
In CMBR_D, CMBR10_D, and OMCD25_2 topologies, OCH and LP trails

have their endpoints in the same ports in the combiners.

Regenerators in Optical Networks

For ODU regenerators, the OCH trail traverses the regenerator and forms a
single end-to-end trail in the regenerator ports, as shown in the picture below.
Other regenerator types terminate the OCH trail and result in multiple OCH
trails in tandem, as shown in the general example in Optical Trail
Configurations.
Optical Performance Monitoring (OPM)

OPM is a monitoring tool placed next to a card (such as a Mux or OFA) that
can be used to monitor ports of different other cards. It is best configured in
LightSoft as an LE together with the monitored card. It is not part of the trail,
but should be associated with the group.
Double-clicking the icon opens the OPM mechanism.

Initial System Setup

The trail creation methodologies described in this section can be used after the
network is configured using the LCT or EMS, and necessary links have been
set up in LightSoft.
LightSoft can create topologies only after the cards and their ports are fully
configured by the EMS, especially the channel of OCH card ports.
The channel of an OPS port in an OCH line card (transponder) must be
synchronized with the channel of the add-port in an ROADM.
The hardware can be installed and configured first using the LCT, but the EMS
must later be set to recognize the NEs.
NOTE: OTM links in LightSoft are indicated as OTS links

in the EMS-XDM.
To perform initial setup of the system:

1. Configure all possible elements and cards in the network, using the EMS
and/or LCT (slot assignment and setup of cards, as described in the EMS or
XDM user manual), to enable them to accommodate traffic.
2. Upload all ports and OTM links (OTS in EMS) to LightSoft through the
EMS (using Link Discovery), or create links using the LightSoft Create
Link feature; see Creating Topology Links. These links can be internal
between ports in a single NE, and/or between ports in different NEs,
depending on the network topology.
NOTE:
Using Functional Topology Map (FTM) in the EMS creates
OTM and OPS links and saves that step in LightSoft.
FTM is an EMS-XDM feature that sets up a functional
topology map. In the process, it assists card configuration and
automatically receives the OTM and OPS links from the EMS.
In addition, FTM is a prerequisite for running the EMS-XDM
Enhanced Automatic Power Control (Enhanced APC) feature,
also known as Power Equalization of Optical Links (PELES).
For more information, see the EMS-XDM User Manual.
Exception: The channel of an OPS port in an OCH line card
(transponder) must be synchronized with the channel of the
add-port in an ROADM. This can be done in the EMS by
linking the TRP to the ROADM port in FTM.
3. Complete the minimum necessary elements and links in LightSoft, such as

the UMEs and links to transponders or combiners.

Creating Optical Trails Through

Discovery
The Discover Optical Trails feature automatically acquires all optical trails
associated with (selected or all) optical links that do not already have trails
configured, in a single operation. The process automatically acquires optical
trails, as follows:
| For each selected OMS link, it creates an OMS trail, as well as client OCH
and LP trails (if any of these do not already exist).
| For each selected OCH link (provided the prerequisite OMS trail exists), it
creates an OCH trail, as well as the client LP trail (if any of these do not
already exist).
| For each selected LP link (provided the prerequisite OCH trail exists), it
creates an LP trail (if this does not already exist).
The process additionally acquires all associated high order trails (EoS-VC-4,
VC-4, and so on) that meet predetermined classification rules (end in valid
endpoints). The various types of traffic carried by an LP trail is depicted by the
payload type field (STM-n, GbE, and FC-2G).
NOTE: In each case, for a trail to be created on the selected

link, the prerequisite trails must already exist. The individual
trail creation process described later in this section uses a top-
down approach whereby only the indicated trail type is
created, but any missing prerequisite trails are automatically
created. For example, when an OCH link is selected, the
associated trail is created, as well as the underlying OMS trail
if this doesn't already exist. For more information, see
Individual Optical Trail Provisioning.
Discover Optical Trails is especially useful when the system is first installed -
more efficient than individual trail creation because of fixed filters and routings
in the network. Default trail parameter values are assigned; see Optical Trail
Parameters. After the basic trails are created, the individual optical trail
provisioning methodology affords greater control over the individual trail
creation process.

Discover Optical Trails is generally performed as part of an iterative process, as

follows:
| Use of Discover Optical Trails to acquire a bulk of trails at a time.
| Trail synchronization to diagnose the trails that fail.
| Subsequent correction of the problems interfering with the acquisition
process.
| Repetition of the cycle until all the possible trails are acquired.
After the Discover Optical Trails is performed in a system, trail creation
activities can be typically limited to individual OCH and LP trails. OMS trails
can also be created if needed.
Discover Optical Trails only creates valid end-to-end trails that meet
predetermined classification rules.
NOTES:
The steps described in Initial System Setup must be
completed before Discover Optical Trails can be performed.
If Discover Optical Trails is stopped before completion, the
process is aborted only after trails already in progress are
created.
If logout occurs before Discovery is completed, the process is
aborted only after your confirmation; see Logging Out.
PRE-PROCEDURE IN EMS:
Before creating a trail involving AoC or 4xAny
(OMCM25_4) cards in LightSoft, you must first create cross
connects in the EMS. (XC-creation is not an automatic part of
the Create Trail process for these cards.) If the XCs are not
already present in the EMS, individual trail creation or Trail
Discovery processes will not find a path, or an acquired trail
(TCI acquisition) will be created as flex.

To create optical trails through discovery:

1. Optionally select on the main window map an area containing the links
over which trail will be created. Selecting an area limits trail creation to
links in that area, affording greater control over the network building
process. All trails in the selection that meet predetermined classification
rules (that end in valid endpoints) are acquired. When no selections are
made, the operation relates to all links in the entire network.
NOTE: For optimal results, a selection should include OTM

links and not just the links from the MD to the Line card.
2. From the LightSoft main menu, select Trails > Discover Optical Trails.
The Discover Optical Trails window opens.
3. Click Start. A confirmation message opens.
4. Click Yes. Trails are acquired, in the order: OMS, then OCH, then LP, then
EoS - Data over WDM.
The Discover Optical Trails Result window shows the number of
acquired and failed trails sorted according to their rates - OMS, OCH, LP,
and high order SDH (for EoS-VC-4, VC-4, and so on). SDH, GbE, DSR are
summarized as LP, the difference between reflected in the Payload type
trail parameter.
Click Show to open the Trail List window filtered on the trails that were
just created.

5. Diagnose the optical acquisition problems by performing trail

synchronization using the Trail Consistency Indicator window; see
Synchronizing Trails.
a. In the TCI window, attempt to synchronize one type of optical trails at
a time - OMS, OCH, and/or LP trails. The order of the analysis depends
on the trails that failed. For example, OCH and LP acquisition failures
are often a result of OMS problems, so OMS trails may generally be
checked first. However, if the OMS trail was created but the LP or
OCH trails fail, the OCH trail should be checked.
Trails that are already acquired are not reflected in the TCI window,
since trail synchronization only relates to links.
b. Failed trails are seen in the Network window as flex. For each failed
trail, perform corrective actions as follows:
Verify that the EMS card setups and configurations are correct.
Verify that the connections in LightSoft are correct.
The cause of failure is often an absent or wrong connection. For
example, if an LP trail is requested and combiners at opposite ends
involve different channels, the OCH trail between them will be created
but the LP trail will fail. (The TCI indicates that an LP failed at specific
endpoints.)
6. After corrections are completed, perform Discover Optical Trails again
from Step 1, to try to acquire the previously failed trails.
7. If some trails still fail, repeat the cycle of trail synchronization and
correction described in Step 5, and perform Discover Optical Trails again.
Perform as many iterations as needed until all possible trails are acquired.

Optical Trail Parameters

Most optical trail parameters have the same usage and meaning as SDH and
EoS trails; see the parameter descriptions in Create Trail Window. The
parameters described in this section may differ in meaning for optical trails.
The following parameters are either defined by the Discovery process, or are
user-definable during trail creation or subsequent editing (except as indicated).
(The default values shown are assigned by the Discovery process or when
values are not specified in individual trail creation.)
Optical trail parameters definable in LightSoft
Label Name for the trail. If the trail label exists in the EMS, Discover
Optical Trails uploads it to LightSoft as the default value. Otherwise
the process assigns the trail endpoints.
Customer Label describing the trail customer. If the customer name exists in
the EMS, Discover Optical Trails uploads it to LightSoft as the
default value. Otherwise the process assigns "NMS".
Rate Transmission rate of the trail - LP (LP trail), OCH (OCH trail), or
OTM (OMS trail).
The rate is not editable after a trail is defined.
Protection Protection layer for the trail. Possible values are: Unprotected,
Current layer, Underlying layer, and Current and underlying layers.
For definitions of these values, see the parameter description in
Trails Pane Columns. For the protection types applicable to each trail
type, see Optical Trail Protection.
Protection is editable for all trails except OMS.
Directionality Possible values are Unidirectional and Bidirectional.
Directionality is editable for all trails except OMS.

The following parameters are derived from the EMS system or set
automatically by LightSoft, and are not user-definable or editable.
Optical trail parameters that are not user-definable
Channel For a bidirectional trail where the two transmission directions have
different channels, both values are displayed (as Channel 1 and
Channel 2).
The OCH trail's channel is also relevant to LP trails since, if the
OCH does not yet exist, it is created automatically with the LP trail.
Channel is not relevant for OMS trails.
Channel is relevant at the transmitter only. Entering zero ("0") is
equivalent to "no" channel, meaning the transmitter should not
transmit.
The receiver inherits the transmitter's channel (zero at the receiver
means "any" channel at the receiver).
Values are:
| DWDM: 0, 192.1 to 196.0 THz
| CWDM: 0, 1471 to 1611 nm
Trail ID Unique integer, or uploaded from the EMS where it can be user-
defined.
Payload Type The payload type for optical trails is a value derived from the EMS
according to the applicable card ports. For details, see Supported
Rates and Payload Types. Two payload types may be indicated for a
trail. In this case, the user must verify their compatibility for the
trail. For more information, see OCH Trail Endpoint Validations.
Trail State Possible values are: OK, Inconsistent, Failed, and Incomplete. For
definitions and troubleshooting suggestions, see the Trail State
description in Trails Pane Columns.
NOTES:
The VCAT size of high order trails is not editable following
creation or acquisition.
The DRI, Max DRI bridges, DNI, and Extra traffic protection
criteria are not applicable for optical trails.

Individual Optical Trail

Provisioning
You can create OMS, OCH, and LP trails using an interface very similar to that
used for SDH trail creation.
The individual optical trail provisioning methodology described in this section

affords control over the specification of trail parameters, such as the trail label
and AMM. After specifying the trail parameters and endpoints of the path on
which the required service is to be set. LightSoft automatically performs all the
provisioning operations.
Unlike SDH trail creation, individual LP and OCH trails can be created before
their underlying server trails exist:
| If a new LP trail is requested and the corresponding underlying trails (OCH
and/or OMS) are not present, they are created automatically with the
requested trail. (An OCH trail can also be created by itself if an LP is not
needed.)
| If a new OCH trail is requested and the underlying OMS trail is not present,
it is created automatically with the requested trail.

OMS trails may be created individually as needed.

If equipment along the path is unconfigured or missing, the PF will not find the
trail path and a warning will appear. You should configure the equipment and
then repeat the provisioning request.
Certain endpoint validations are performed by the Create Trail process. For
details, see OMS Trail Endpoint Validations, OCH Trail Endpoint Validations,
and LP Trail Endpoint Validations.
Individual trail creation only creates valid end-to-end trails that meet
predetermined classification rules.
See Initial System Setup for optical trail creation prerequisites. Additional
prerequisites apply for each type of trail, as described in the sections that
follow.
NOTE: The EMS configurable I/O OADM has fixed filters.

On assignment, all the SNCs are pass-through even though
the signal cannot pass through the installed module
designated channels. This means that the LightSoft user will
not be aware that the configuration is faulty and may try to
create OCH trails through it.
NOTE: See Pre-Procedure in EMS described in Creating


OMS Trail Provisioning

OMS trails are optical trails between multiplexing devices (MDs). For more
information, see Optical Trails. OMS trails can be created individually using
the procedure in this section. Typically, OMS trails are created using Discover
Optical Trails. OMS trails are created implicitly when a LP or OCH trail is
requested.
In addition to general prerequisites for optical trail creation described in
Individual Optical Trail Provisioning, OMS trail creation also requires that the
photonic layer cards with OTS ports (such as Mux, DeMux, OFA, and OADM)
were installed, configured in the EMS, and linked.
To create individual OMS trails:

1. Select the Optical topology layer.
Alternatively, you can start optical trail creation from the Physical (site)
layer if the Preferences dialog box Trails tab Default Provisioning Layer
parameter is set to Optical. For more information about determining the
default technology for new trails, see Trail Management Preferences.
2. Optionally select on the main window the objects containing the endpoints
of the intended trail. This will open the Create Trail window with those
objects and their associated links, rather than all the objects in the current
view. (When the Pathfinder searches for trails, it relates to the relevant
topology, not only to the displayed elements.)
3. On the main menu bar, select Trails > Create Trail.
OR
On the toolbar, click the Create New Trail icon . The Create Trail
window opens. (The first time that the Create Trail window opens in a
session may take longer than it does subsequently.)
The map contains only the selected objects and the links between them. If
nothing was preselected in the main map view, the map will show all the
objects.

4. Enter basic trail parameters, as needed:
Label and customer name (optional); see the parameter description in

Basic Trail Parameters Pane.
Rate: OMS.
Protection: Unprotected, Current Layer, Underlying Layer, or
Current and Underlying; see Optical Trail Protection and the
Protection type definition in Trails Pane Columns.
Directionality: Unidirectional or Bidirectional.
5. Enter advanced trail parameters, as needed:
Comments, Service Indicator, Private ID, and User Usage State; see the
parameter descriptions in Advanced Trail Parameters Pane.
Alarms Master Mask (of the endpoint ports): Set to "Apply" or "Do not
change"; see Alarms Master Mask (AMM) and the parameter
description in Advanced Trail Parameters Pane.
On some equipment, AMM is set to "Apply" by default, in which case
setting the parameter to "Do not change" will leave the equipment
AMM as monitored.
6. Select endpoints to define the path on which the service should be created
(function is enabled only after a trail rate is selected):
Right-click an LE on the map and select Select Endpoint from the
shortcut menu. The Endpoint Selection window opens. The ports that
are free and conform to the selected trail rate are available for selection.
The window and procedure is similar to that for SDH trail creation,
described in Select Segment Pane.
Select endpoint ports. Typically one endpoint is sufficient. See OMS
Trail Endpoint Selection for specific instructions concerning
directionality and the number of endpoints needed in specific cases.
The selected endpoints are reflected in the Endpoints List pane.

7. Optionally select in the window map the specific segments that you want
the trail to span (using the Shift key). This is useful if you are creating a
LightSoft will create the trail according to PF optimization considerations.
8. Click Complete trail and Activate trail . LightSoft does the

following:
a. Finds the path between the endpoints.
b. Derives the protection state of the trail from the network and the
underlying links state. If the derived state is different from the selected,
a message is generated and the state is set as derived from the network.
c. Validates the compatibility of the endpoints; see OMS Trail Endpoint
Validations.
d. Downloads to EMS (according to trail rate):
Label and customer, if set differently in Step 4
AMM state
e. Creates the trail.
Clicking Complete finds and verifies the path and shows the results on the
map, but does not create the trail until Activate is performed. If a path between
the endpoints is not found, a failure message is generated.
If trail parameters are not specified, LightSoft sets default values; see Optical
Trail Parameters.

OMS Trail Endpoint Selection

OMS trails can be configured to be either unidirectional or bidirectional:
| Unidirectional OMS trails
| Bidirectional OMS trails
Unidirectional OMS Trails

For a unidirectional OMS trail, you must have selected Unidirectional as the
trail directionality.
Select the OTS-Src and/or the OTS-Snk at the extremities of the trail. You can
select one or both endpoints.
The "add" and/or the "drop" of a bidirectional endpoint can also be used as
endpoints to create a unidirectional trail.
LightSoft automatically creates the trail based on the selections.
A single endpoint selection is sufficient to define the trail path in most cases.
Bidirectional OMS Trails

For a bidirectional OMS trail, you must have selected Bidirectional as the trail
directionality.
One or two endpoints are needed to define an optical trail. (Selecting more
endpoints is not allowed.)
| One Endpoint
| Two Endpoints
One Endpoint
In a configuration where elements at opposite ends of the path both include
pairs of Src/Snk endpoint ports (so are bidirectionally related), only a single
endpoint selection is needed to uniquely identify the bidirectional OMS trail.
For information about bidirectional relations between ports on the same card,
see Relations between Ports or Cards.

Examples
In this example, a Mux and DeMux reside on the same card with
bidirectionally related ports. The path extends to an OADM, which also
includes related ports on the same card. (Amplifiers in the path do not affect the
OMS trail.) Selecting any one of the four possible endpoints is sufficient to
define the bidirectional OMS trail.
Similarly, in a 3-card configuration, for example, an OADM with Snk/Src

bidirectionally related ports on same card on one side, and 40-channel Mux and
DeMux on separate cards (no bidirectional relation) on the other side, a single
endpoint selection (one of the related ports) is sufficient to define the trail.

Two Endpoints
If the bidirectional relation is absent on both sides of the directional path (for
example, four cards, with 40-channel Mux and DeMux on each side), two
endpoints must be selected - one endpoint in each directional path.
NOTE: Each of the two selected endpoints must be in a

different directional path. If the endpoints are selected on the
same unidirectional path, a unidirectional trail will result,
regardless of whether a Bidirectional was specified as the
required trail type.
OMS Trail Endpoint Validations

The following endpoint compatibility validations are performed when an OMS
trail is created:
| When connecting OTS/OMS ports, the endpoints must have some channels
in common.
| CWDM and DWDM endpoints cannot be connected.
These anomalies are not included in the TCI Details pane inconsistency counts.

OMS Trail Use Cases

OMS trails can be unprotected or protected.
Unprotected OMS Trail

This diagram shows a simple unidirectional OMS trail.
Protected OMS Trails

OMS trail protection is derived from the network according to the presence of
OMSP cards and their "Protection groups" and/or the state of the underlying
links (you can set them to be "externally protected").
The following cases show MSP 1+1 configurations, called OMS Section
Protection (OMSP), where the OMS trail (spanning from Mux to DeMux) is
considered "partially" protected. It is not fully protected because short fiber
segments between MD and OMSP cards are unprotected. Only the in-line
distance span between two OMSP cards is protected.
An alternative protection option is for an OMS trail to be protected by

underlying links. In this case one or more links used by the OMS trail are
specified as being external protected topology links. The resulting OMS trail
will then be called an OMS trail with underlying protection.
The difference between the two cases is the location of the amplifiers and their
configuration - single point of failure vs. Optical Fiber Amplifier (OFA) 4-fiber
connection double amplifiers. The connections differ but result in the same set
of trails and nature of protection.

OCH Trail Provisioning

OCH trails are client trails of an OMS trail, and use the channels of the OMS
trail. An OCH trail carries the LP client input signal trails, one or more LPs per
OCH trail. For more information, see Optical Trails.
OCH trails can be created individually using the procedure in this section.
Their prerequisite OMS are created implicitly or may previously have been
created though individual provisioning or some other mechanism; see OMS
Trail Provisioning. An OCH trail can be created independently of LP trails.
The optical channels used by OCH trails are defined in the EMS or configured
in the NE. They are not set in LightSoft.
General prerequisites for optical trail creation are described in Individual
Optical Trail Provisioning. OCH trail creation requires the following additional
preconditions:
| Line cards that start and end the OCH trail have been installed, configured
and linked to the respective MD ports.
| OADM and ROADM cards must be preconfigured with the desired
channels.
To create individual OCH trails:

1. Open the Create Trail window for optical trails, as described in Steps 1 to
3 of the procedure in OMS Trail Provisioning.

Rate: OCH.
Protection Type definition Trails Pane Columns.
Directionality: Unidirectional or Bidirectional. (OCH trails are
typically bidirectional.)

AMM as monitored.
Select endpoint ports. Typically one endpoint is sufficient. See OCH
Trail Endpoint Selection for specific instructions concerning
directionality and the number of endpoints that need to be selected.
The selected endpoints are reflected in the Endpoints List pane.
LightSoft will create the trail according to PF optimization considerations.
6. Click Complete and Activate. LightSoft does the following:
c. Validates the compatibility of the endpoints; see OCH Trail Endpoint
Validations.


Label and customer, if set differently in Step 4.
AMM state
e. Creates the trail
Trail Parameters.
OCH Trail Endpoint Selection

OCH trails are generally bidirectional, but may also be unidirectional (for
example, for video, where transmission is in only one direction).
Select the endpoint ports according to trail directionality, as follows:
| Select one LE that resides at the end of the planned OCH trail.
| Select one (or two) endpoints of the OCH trail according to endpoint
selection and trail directionality.
| Select either the unidirectional ports Src ports at both ends of the planned
trail, or the bidirectional ports (e.g. SPIO) at both ends.
If the selected endpoint is a unidirectional OPS, LightSoft finds the related
endpoint.
If a selected endpoint has no bidirectionally related port, LightSoft rejects the
operation. When both ports are selected at the same endpoint, LightSoft finds
the path to the other end and creates the trail (whether or not the ports at the
other end are related).
Unidirectional OCH Trails

For unidirectional OCH trails (for example, for video, where transmission is in
only one direction), it is important that the ports selected be Src at one end and
Snk at the other end.
Bidirectional OCH Trails

The endpoint selection will vary according to whether the SDH cards at the
path extremities have pairs of unidirectional ports (Snk and Src) or single
bidirectional ports.

Card with Two Unidirectional Ports

This section relates to endpoint selection when cards at the path extremities are
line cards with unidirectional (Snk and Src) ports.
This example shows four potential endpoints, two at each transponder over
which the OCH trail will span.
One Endpoint
When each pair of ports resides in a card having a bidirectional relation, only
one endpoint is usually needed - any one of the four potential endpoints, as
shown in the above figure (similar to endpoint selection for OMS trails).
OCH Trails in Complex Networks

In networks with many complex connections, it may be desirable to select two
endpoints, thereby explicitly specifying the intended trail path. In this way, if a
wrong connection is present, the trail will fail rather than creating a trail with
an unintended path.
The additional endpoint selection (two instead of one in the previous examples)
should include a port at both ends of the trail. (It doesn't matter which port on
each side is selected.)
SDH Card with Single Bidirectional Ports

SDH cards may have single bidirectional ports to which Snk and Src ports in
another device are connected. In this case, a single port selection is sufficient to
define the bidirectional OCH trail.

OCH Trail Endpoint Validations

The following endpoint compatibility validations are performed when an OCH
trail is created:
Forward Error Correction (FEC)

The FEC type at both endpoints should be equal. The possible values are: No-
FEC, FEC, and EFEC. There is no warning of incompatibility. The trail is still
created even if an incompatibility is present.
Payload type
Payload type of the two endpoints should be equal. A warning that different
payloads are present at the endpoints if the trail is created using Create Trail
window. (No warning appears if the trail is created using Optical Trail
Discovery.) The trail is still created even if an incompatibility is present.
Channels
Channels at both ends of the trail should be compatible. If not, the trail is not
created; see OCH Trail Channel Issues.
NOTE: For certain optical cards, automatic validations of

trail endpoints compatibility are limited. For example, for
continuous bitrate cards, compatibility of bitrate settings at
each end is not verified. The user should view the trail
Payload Type attribute that is determined by the trail
endpoints' client type setting to ensure that the settings are
consistent.
OCH Trail Channel Issues

OCH trails may have multiple channels, either a different channel in each
direction or a longitudinal split in one direction, with one channel up to a point,
then continuing on another channel. If a trail is created with a single continuous
channel from end to end in a direction, it must have the same channel along the
whole path. Otherwise, what is transmitted will not pass through the filter.
The channel in use at the input of a receiver (TRP or CMBR) is assigned the
channel value "zero", meaning its channel is determined by the transmitter.
SDH cards have single bidirectional ports (not having two related
unidirectional ports) and connect to two ports in the MD (Snk and Src). As the
transmitter and receiver are in the same port (a transceiver port), the same (non-
zero) channel is indicated for both transmitting and receiving.
Thus a "zero" channel is indicated only on receive (Snk) ports, never on
transmit (Src) ports or bidirectional ports. If this is not the case, or if any other
channel mismatch is present, the trail will not be created.

OCH Protection
Current protection for OCH trails derives automatically if the line ports from
the transponders (to a multiplexer, certain types of combiners, an AoC, or
another transponder) are associated by a protection group object (PGO) created
in the EMS (inherited feature from the EMS); see Protection Group Objects
(PGO) in Relations between Ports or Cards. See also Optical Trail Protection.
The OCH trail is created as protected OCH with main and protection paths.
NOTE: Only newly created OCH trails are protected. OCH

trails preexisting from an earlier LightSoft release are
independent, even if a PGO is present. Those trails retain their
old style, where only the LP is protected and the OCH trail is
not Current protected. (To achieve OCH protection, those
trails can be deleted and recreated.)

OCH Trail Use Cases

Optical devices accommodate two directions of transmission (bidirectional
OCH trail), using either unidirectional or bidirectional ports.
Transponders and combiners are pure optical cards with unidirectional ports
where the Snk and Src are in different objects. In the diagram below, each
transponder uses OPS_Src and OPS_Snk ports to separately connect the
westside Mux and DeMux.
In the diagram below, the card's related unidirectional ports OPS_Src_1 and
OPS_Snk_2 connect to the westside Mux and DeMux, while the unidirectional
ports OPS_Snk_1 and OPS_Src_2 connect to the client equipment.

SDH cards with bidirectional ports having Snk and Src in a single object
connect to both the input of a Mux and the output of a DeMux. In the diagram
below, each SDH card uses a single port to connect to both the westside Mux
and DeMux.
In the diagram below, the card's bidirectional port OPS_1 connects to the west
Mux and DeMux, while the bidirectional port OPS_2 connects to the client
equipment.

LP Trail Provisioning
LP trails are end-to-end optical trails representing the client input signal. For
more information, see Optical Trails. The LP may coincide with the OCH trails
path, except that endpoints will be on the client port of the line card.
LP trails can be created individually using the procedure in this section. Their
prerequisite OMS and OCH trails are created implicitly, or may previously
have been created though individual provisioning or some other mechanism;
see OMS Trail Provisioning.
Multiple LPs can be defined on the same OCH (useful in the case of
combiners). The first LP implicitly creates the OCH, subsequent LPs use the
same path.
LP trails can be coupled. The Private ID attribute may be used to associate two
more trails as a single service; see Trail Creation Options.
General prerequisites for optical trail creation are described in Individual
Optical Trail Provisioning.
NOTE: If the endpoint is on a transponder without client

equipment connected to it, then individual trail provisioning
cannot be performed using the Create Trail window; see LP
Without Client Equipment Termination. In this case, the
procedures described in Creating Optical Trails Through
Discovery or Trail Acquisition by Synchronization can be
used instead.
To create individual LP trails:

1. Open the Create Trail window for optical trails, as described in Steps 1 to
3 of the procedure in OMS Trail Provisioning.

Rate: LP.
Protection type definition in Trails Pane Columns.

Directionality: Unidirectional or Bidirectional. (LP trails are typically

bidirectional.)
AMM as monitored.
4. If the LP trail has payload type GbE, select the View on Ethernet Layer
checkbox if the trail should be visible as a virtual link on the Ethernet layer;
see Trails and Virtual Links.
Select endpoint ports. Typically one endpoint is sufficient. See LP Trail
Endpoint Selection for specific instructions concerning directionality
and the number of endpoints that need to be selected.
LightSoft will create the trail according to pathfinder optimization
considerations.
LightSoft finds the related endpoints where needed according to endpoints
selection and trail directionality. The selected endpoints are added in the
Endpoint List pane.

7. Click Complete and Activate. LightSoft does the following:

c. Validates the compatibility of the endpoints; see LP Trail Endpoint
Validations.
Label and customer, if set differently in Step 4
AMM state
e. Creates the trail.
Trail Parameters.
LP Trail Endpoint Selection

Select the endpoint ports according to trail directionality, as follows:
| Protected Bidirectional LP: Select the UME or client line card (e.g.
noncolored SIO) ports that should be the LP endpoints and are connected
through splitter-couplers to line card client ports.
| Unprotected Unidirectional LP: Select the unidirectional endpoint either
the Src at one end or the Snk at the other. Ensure that the endpoints do not
connect to OCH line cards that are associated for protection, and are not
connected through splitter-coupler fibers.
Essentially the same conditions as the OCH case apply - see OCH Trail
Endpoint Selection, but with the endpoints on TRPs (UMEs) at the ends of the
path instead of MDs.
LP trails can be created with any of the following endpoint possibilities:
| UME, SIO (non-colored) or data card ports for protected or unprotected
LP; see Protected LP with Endpoints in UMEs.
| Client ports of transponders or combiners with or without protection
association (PGO present); see Unprotected LP Without UME and
Protected LP Without Splitter-Coupler or UME.

LP Trail Endpoint Validations

The following endpoint compatibility validations are performed when an LP
trail is created:
Forward Error Correction (FEC)

The FEC type at both endpoints should be equal. The possible values are No-
FEC, FEC, and EFEC. There is no warning of incompatibility. The trail is still
created even if an incompatibility is present.
Payload type
Payload type of the two endpoints should be equal. If the trail is created using
Create Trail window, a warning appears if different payloads are present at the
endpoints. (No warning appears if the trail is created using Optical Trail
Discovery.) The trail is still created even if an incompatibility is present.
NOTE: For certain optical cards, automatic validations of

trail endpoints compatibility are limited. For example, for
continuous bitrate cards, compatibility of bitrate settings at
each end is not verified. You should view the trail Payload
Type attribute determined by the trail endpoints' client type
setting to ensure that the settings are consistent.

LP Trail Use Cases

| Unprotected LP Without UME
| Protected LP with Endpoints in UMEs
| Protected LP Without Splitter-Coupler or UME
Unprotected LP Without UME

Client ports of transponders or combiners without protection association (PGO
present).
In this example there is no splitter and coupler, and the LP ends in the ingress
and egress objects of the transponders.
Protected LP with Endpoints in UMEs

UME, SIO (noncolored), or data card ports for protected or unprotected LP.
The example shows the LP trail traversing from UME to UME and protected
by the OCH trail.

Protected LP Without Splitter-Coupler or

UME
Client ports of transponders or combiners with or without protection
association (PGO present).

Trail Acquisition by
Synchronization
Individual trails can also be acquired directly through the Trail
Synchronization window. This method synchronizes the trails to be carried by
a selected link, importing the trail information from the EMS to the LightSoft
database.
Acquisition by synchronization should be considered a last resort procedure,
for use when normal trail creation procedures (the Discovery process or
individual optical trail provisioning from LightSoft) are ineffective with the
resulting trail not meeting the classification rules.
This process involves first creating the links between the relevant ports, either
through link discovery from EMSs or from LightSoft; see Creating Topology
Links. These links can include internal links between ports in a single NE, links
between ports in two different NEs, or a combination of the two, depending on
the network topology. Creation of optical LEs may be performed before or after
the creation of the optical trails.
You then synchronize, or acquire, the trails to be carried by these links. This
involves importing the trail information to the LightSoft database, as described
in the following sections:
| Creating OMS Trails with TCI
| Creating OCH Trails with TCI
| Creating LP Trails with TCI
NOTE: This procedure assumes you have already made the

corresponding slot assignments and card setup (especially the
channel and the client bitrate), as described in the
corresponding EMS documentation.
In certain cases, it may be necessary to create UMEs to
represent UMEs in the optical layer. These UMEs are
connected to MEs via topology links.
NOTE: See Pre-Procedure in EMS described in Creating


Workflow for Acquiring Trails by

Synchronization
The following workflow describes the process of creating optical trails through
synchronization:
1. Split the LEs in the optical layer into more granular secondary LEs
distinguished by function; see Creating Secondary LEs.
2. Define internal optical links between components (OADMs, Mux/DeMux,
OFAs); see Creating Topology Links.
3. Define optical links between NEs; see Creating Topology Links.
4. Define OMS trails between components in the NEs; see Creating OMS
Trails with TCI.
5. Define internal Optical Physical Section (OPS) links between transponders
and OADMs and Mux/DeMuxes.
6. Define OCH trails between transponders in the NEs; see Creating OCH
Trails with TCI.
7. Perform trail synchronization; see Synchronizing Trails.
8. Build LP trails, connecting transponders to STM-16 cards from either ECI
Telecom or a third party (UME); see Creating LP Trails with TCI.
9. Perform trail synchronization again.

Creating OMS Trails with TCI

This section describes how to create OMS trails between a multiplexer or an
Optical Add/Drop Multiplexer (OADM) and a demultiplexer or OADM.
Amplifiers and other aggregate cards may be in the path of an OMS trail.
To create an OMS trail:

1. Select the physical or optical layer of the participating NEs. The physical
layer is recommended when creating trails on hybrid networks, which
combine optical and SDH elements.
2. Create internal links between the relevant ports in each NE as follows:
a. On the LightSoft main menu bar, select Configuration > Create >
Topology Link. The Create Topology Link dialog box opens; see
b. Select an OTN link type and then select the corresponding Snk and Src
ports on the NE.
3. Create a link between the NEs as follows:
a. In the Create Topology Link dialog box, select the two elements
between which you want to create the link, and select the corresponding
sinks and sources of the elements. The required rate is OTN.
b. Click Apply. A Link Created message appears on screen, and the map
shows the newly created link.
4. In the Topology Segments window, right-click the link between the NEs
and select Expand from the shortcut menu. A window similar to the Self
Links View window in Step 2 appears.
5. Select the links to be included in the acquisition process. Only one link is
required per OMS trail. You can acquire more than one OMS trail at a time
(the recommended maximum is five).

6. On the LightSoft main menu bar, select Trails > Trail Consistency.
OR
On the main toolbar, click Trail Consistency .

OR
Double-click the link to display the Multi Link window, right-click the
link and select Trail Consistency. The Trail Consistency Indicator
window opens.
7. In the Parameters pane, select the OMS level (OMS OTN) and the Use
Connectivity Only checkbox.
NOTE: It is recommended to deselect the Auto Admit to

Database - Classified checkbox.
8. Click Start. The acquisition process begins. When it finishes, the Trail
Synchronization window opens with several floating windows: Network
Trails Sequence, DataBase Trails Sequence, and Queue. For more
information, see Trail Synchronization Window.

9. In the Network Trails Sequence window, select the checkbox for the trail
and click the Trail Admit icon . The trail is transferred to the Queue
window.
10. Select the trail in the Queue window and click the Activate icon . An
“operation successful” message appears at the top right-hand corner of the
window, and a green checkmark appears next to the trail.
NOTE: It is recommended to change the default name given

to the trail by the system. For more information, see Editing
Trails.

Creating OCH Trails with TCI

This section describes how to create OCH trails, client trails of the OMS.
Typically, the OCH trail has its endpoints in the network side of transponders.
A regenerator (a transponder used in a regeneration site) is also an endpoint of
an OCH trail. An OMS trail can contain one OCH trail for each available
channel. For example, an OMS trail with 40 channels can contain up to 40
OCH client trails.
To create an OCH trail:

1. Create links at both ends of the trail (for example, between the transponder
and the multiplexer/OADM on one side, and between the
demultiplexer/OADM and transponder on the other). These may be internal
links in one NE, or links between ports on different NEs, depending on the
network topology. For more information, see Steps 2 and 3 in Creating
OMS Trails with TCI.
TIP: In the Create Topology Link dialog box, select OPS_1

as the Select Type; see Creating Topology Links. Only the
relevant ports will then be displayed as selection possibilities.
2. In the Topology Segments window, select one of the OCH links as

follows:
a. Select one NE containing internal OCH links, right-click the NE, and
select Internal Links from the shortcut menu.
OR
Select two NEs connected by an OCH link, right-click and select
Expand from the shortcut menu.
b. In the window displayed, select an OCH link.
OR
On the main toolbar, click . The Trail Consistency Indicator window

opens.
4. Repeat Steps 7 through 10 of the procedure in Creating OMS Trails with
TCI, but selecting the OCH level (OCH OTN) from the Trail Consistency
Indicator window dropdown list.

Creating LP Trails with TCI

This section describes how to create LPs. The endpoint of the LP is the client
port connected to the transponder (in the case of SDH or other clients that are
connected to a transponder), or the client port of the transponder. Each OCH
trail can have only one LP client. However, an LP may be the client of multiple
OCH trails. (LightSoft does not differentiate between LPs for SDH or data
clients. This information is reflected in the trail's payload type parameter.)
To create an optical trail at the LP level:

1. In the Trail List window, select a link with LP rate related to the trail. If
the LP has UMEs, you can select a link between the UME and a
transponder.
OR
On the main toolbar, click . The Trail Consistency Indicator window

opens.
3. In the Parameters pane of the TCI window, select LP DSR from the
dropdown list.
4. Click Start to begin the acquisition process.
5. Repeat Steps 9 and 10 of the procedure in Creating OMS Trails with TCI.
When the process is complete, rename the trail.
Once the new optical trail is acquired, you can view it as follows: Open the
Trail List window, right-click the trail in the Trails pane, and view the
attributes in the Trail Properties pane (the Enable/Disable show trail when
selected icon should be selected).

Other Actions on Optical Trails

This section describes additional actions that you can perform on optical trails.
Editing Optical Trail Parameters

You can modify the Trail label and Customer parameters in all trail types,
using the general procedure described in Editing Trails.
A trail's Directionality and Protection can be modified indirectly as follows:
| Two unidirectional trails can be converted to one bidirectional trail as
follows:
Delete the unidirectional trail in one direction.
Edit the unidirectional trail in the other direction to be bidirectional.
| A bidirectional trail can be converted to a unidirectional trail as follows:
Edit the bidirectional trail to be a single unidirectional trail.
Create the trail in the other direction.
Deleting Optical Trails

You can delete trails using the general procedure described in Deleting Trails.
You cannot delete a trail that has clients traversing it or where the "User Usage
State" is active.
When an optical trail is deleted, the AMM of the endpoint ports is reset to the
nonreported state.
Inserting and Removing Optical Components

For information about inserting, deleting, and replacing OTM layer
components to/from links, see Managing NEs in Topology Links.
Coupling LP Trails
Two or more LP trails can be associated as a single service using the Private ID
attribute; see Trail Creation Options.

Viewing Optical Channel

Availability
Optical Availability tables show the state of channels through a selected
DWDM or CWDM OMS trail. As well as occupied (In-use) or blocked
channels, the tables show channels that are both free and can be added and
dropped at the trail end sites.
The availability table menu and toolbar options offer easy navigation to OMS
trails, OCH trails, and alarms.
NOTE: The LightSoft Resource Availability on Links

features are important tools for network traffic planning. At a
glance you can see the available capacity in the network as a
whole and on specific SDH links/multilinks. For more
information, see Viewing Resource Availability on Links.
Optical Availability Tables

Optical channel availability can be analyzed for single or multiple OMS trails
(unidirectional or bidirectional). (Two unidirectional trails with related
endpoints are considered as a single bidirectional trail.)
The following window opens in the case of a single trail selection
(unidirectional or bidirectional). The title bar displays the OMS trail label.
In this bidirectional trail example, the cell for channel 194.6 is

, meaning In-use in one direction and Free in the other
direction. The color coding possibilities are described in detail below.

The following window opens in the case of a multiple trail selection.
DWDM tables show cells for 40 or 80 channels, represented in frequencies,

each identified by its channel value from an MD port. CWDM tables show
cells for eight channels, with the channel represented by wavelength values.
(See also Channel Frequencies and Wavelengths.)
In both tables, each channel cell represents an intersection set of channel states
per represented direction/trail, color coded as follows:
The first three legend colors imply the same state in all directions/trails per
channel:
| (white) indicates a channel is not in-use, blocked, or disconnected
in a ROADM (configurable SNCs).
| (dark blue) indicates a channel where an OCH trail traverses
OMS sections. The OCH trail originates from at least one endpoint or
passes through both.
| (black) indicates a channel is blocked at one/both endpoints by
a group OADM, a red-blue filter, or a dropped channel without OCH. The
Connection state of OCH CTPs of the blocked channels in a grouped
OADM is set to Blocked. In single trail availability examples, the C band
eight middle channels are blocked to use.
The last two legend colors imply different states between directions/segments
per channel (not applicable to single unidirectional trail selection):
| (light blue) indicates a channel is in use in one direction
or trail and free in the other direction or other trails.
| (gray) indicates a channel is blocked in one direction or
trail and either in use or free in the other direction or other trails. (Any
multiple-state channel that includes the Blocked state is considered
Blocked-mixed.)

The summary at the bottom of the table shows the number of channels in each
state. In the case of bidirectional trail selections, two numbers are shown for
each state, separated by a slash (for example, ), showing the number
of channels having that state per trail direction.
The Split Table icon is enabled for single bidirectional trail selections (or
unidirectional trails with related endpoints). Clicking this opens individual split
tables for each direction. The table headers show the direction of each segment.
Notice that the channel 194.6, described as "In-use mixed" in the intersection
table, is shown in the split tables as in use in one direction and free in the other.
Notice that the channel 194.6, described as "In-use mixed" in the intersection
table, is shown in the split tables as in use in one direction and free in the other.
Compare this with the original table.

Utilization Table menu and toolbar options
Menu/Toolbar option Description

View
Split Table Enabled for bidirectional trail selections (or unidirectional
trails with related endpoints). Opens individual split tables for
each direction.
Refresh Refreshes the optical availability table window to show the
current resource availability information and color coding.
The Last Update time stamp in the right corner of the status
bar shows the date/time of the last refresh.
The window is automatically refreshed when new preferences
are applied.
Preferences Enables you to change the colors representing Available and
Unavailable statuses; see Modifying Availability Map
Preferences.
Legend Shows or hides the status bar legend and Last Updated time
stamp.
Print Prints the current list or map to any Postscript network
printer, as well as to Postscript-formatted files; see Printing
and Exporting to File. For information about the report
format, see Printing and Exporting Availability Information.
Export to CSV Exports the data to a delimited format file, such as comma-
separated values (CSV), for import to Microsoft Excel or a
relational database application. See Exporting to CSV. For
information about the report format, see Printing and
Exporting Availability Information.
Close Closes the Optical Availability Table window.
Alarms
Show OMS Opens the Current Alarms window showing the alarms on
Alarms the selected OMS trail.
Show OCH Opens the Current Alarms window showing the alarms on
Alarms all OCH trails traversing the selected OMS trail.
Trails
Show OMS Opens the Trail List window showing the selected OMS trail.
Trails
Show All OCH Opens the Trail List window showing all OCH trails
Trails traversing the selected OMS trail.
Help

Opening Availability Tables

Optical Availability tables can be opened for OMS trails from the optical layer
or the physical layer. You can open multiple independent tables at the same
time.
You can refresh an open table without reselecting the OMS trail set.
To open an availability table:

1. From the Physical or optical layer, select one or more links or trails:
Underlying link(s) of OMS trail(s) from the LightSoft main window or
Trail List window map.
OR
OMS trail(s) in the Trails pane of the Trail List window.
OR
OTM (= OTS) link(s) in the Create Trail or Availability Map
window.
Selected multiple links cannot include a mixture of external and internal
links (between and within LEs). Multiple internal links must relate to the
same LE (must be selected from the same expanded internal links window).
Other conditions apply to multiple trail selection, for example, that the two
selections involve the same technology.
2. Select Availability from the shortcut menu. The appropriate Optical
Availability table opens:
Selecting a unidirectional OMS trail yields the availability table of the
channels carried by the trail.
Selecting two or more OMS trails yields the intersections of the
channels carried by all the selected trails.
If one or more of the selected links carry no OMS trail, an error message is
displayed that prompts you to create the OMS trail.
Only OTM links are recognized for purposes of optical channel availability.
The Availability option works differently according to the link rate type. If
a SONET link is selected, resource availability on those links is displayed;
see Viewing Resource Availability on Links.
NOTE: Meaningful availability tables require appropriate

trail set selections. (For example, for a bidirectional OMS
table, select the two unidirectional trails going in both
directions.) When using area select, ensure not to include
links that may introduce OMS trails that are foreign to the
required path, causing an invalid intersection.

Examples of OMS trail selections

The following examples show the links that should be selected to view
unidirectional or bidirectional trail availability:
| Unidirectional availability when a single OMS trail spans the MDs at both
ends - select the connecting link.
| Bidirectional availability - select any two links, one in each direction.
| Bidirectional availability between multiple LEs - select one link for each
unidirectional OMS of the links that form the entire path. For example,
between three LEs, select four links, one for each unidirectional OMS.
Navigating from the Availability Table

You can perform the following navigations from the availability table:
1. Open the following windows directly from the availability table:
Trail List window with the OMS trail(s) filtered in.
Current Alarm window with notifications involving the trails filtered
in.
2. Select an in-use channel in the availability table and ask to open:
Trail List window with the OCH trail filtered.
From the Trail List window, open a GCT on an MD to access:
Internal view of MD that starts or ends the tandem chain of trails
(accessible through the OTS_Src or OTS_Snk that bound the chain
of trails).
Internal or setup view of the OCH line card connected to the drop
or add SNC of the respective channel at the ends of the path.
3. Select one or several in-use channels in the availability table view (use Ctrl
or Shift keys to select several) and ask to open the Trail List window
filtered to show the trails related to the selected channels.

4. Open the Trail List window from the availability table view without
selecting any channel - All OMS or All OCH.
The filter shows all the trails that relate to the in-use channels in the table.
Printing and Exporting Availability

Information
You can generate reports of optical availability information, either as a printout
or exported to a delimited format file (such as CSV), for import to Microsoft
Excel or a relational database application.
To generate availability reports from the Optical Availability

Table window:
| Printout: From the Optical Availability Table window, select the Print
option.
| Export to file: From the Optical Availability Table window, select the
Export to CSV option.
For detailed procedures, see Printing and Exporting to CSV.
Report Format
The report title shows the OMS trail ID and its endpoints. A list of underlying
links is provided. The Optical Availability table information columns are:
| Channel value (for DWDM channels, 192.1 to 196)
| Channel state (Free, In-use, or Blocked)
| OCH payload type (DSR, ODU1, or N/A)
If the table is the intersection of two or more OMS trails, the report title shows:
"Intersection of N OMS trails". The list of trails is provided with their
underlying links (Optical Availability columns listed after each).

Channel Frequencies and Wavelengths

Dense Wavelength Division Multiplexing (DWDM) and Coarse Wavelength
Division Multiplexing (CWDM) technologies, supported by LightSoft optics,
describe the carriers over which optical signals are transmitted. DWDM and
CWDM use grids of frequencies and wavelengths, as described in the
following sections:
| DWDM Frequencies and Wavelengths
| CWDM Wavelengths
For more information about the channel terminology, see Channels.
DWDM Frequencies and Wavelengths

DWDM uses a grid of 40 or 80 channels on the C band, from 192.05 THz to
196.0 THz (spaced at 100 or 50 GHz, respectively), as listed in the following
table.
DWDM Frequencies and Wavelengths
ITU T Channel Channel Channel spacing Channel spacing

channel frequency wavelength (nm) 100 GHx 50 GHz
number (THz)
20.5 192.05 1561.01

21 192.10 1560.61
21.5 192.15 1560.20
22 192.20 1559.79
22.5 192.25 1559.39
23 192.30 1558.98
23.5 192.35 1558.58
24 192.40 1558.17
24.5 192.45 1557.77
25 192.50 1557.36
25.5 192.55 1556.96
26 192.60 1556.55
26.5 192.65 1556.15
27 192.70 1555.75
27.5 192.75 1555.34
28 192.80 1554.94
28.5 192.85 1554.54
29 192.90 1554.13


number (THz)
29.5 192.95 1553.73

30 193.00 1553.33
30.5 193.05 1552.93
31 193.10 1552.52
31.5 193.15 1552.12
32 193.20 1551.72
32.5 193.25 1551.32
33 193.30 1550.92
33.5 193.35 1550.52
34 193.40 1550.12
34.5 193.45 1549.72
35 193.50 1549.32
35.5 193.55 1548.91
36 193.60 1548.51
36.5 193.65 1548.11
37 193.70 1547.72
37.5 193.75 1547.32
38 193.80 1546.92
38.5 193.85 1546.52
39 193.90 1546.12
39.5 193.95 1545.72
40 194.00 1545.32
40.5 194.05 1544.92
41 194.10 1544.53
41.5 194.15 1544.13
42 194.20 1543.73
42.5 194.25 1543.33
43 194.30 1542.94
43.5 194.35 1542.54
44 194.40 1542.14
44.5 194.45 1541.75
45 194.50 1541.35


number (THz)
45.5 194.55 1540.95

46 194.60 1540.56
46.5 194.65 1540.16
47 194.70 1539.77
47.5 194.75 1539.37
48 194.80 1538.98
48.5 194.85 1538.58
49 194.90 1538.19
49.5 194.95 1537.79
50 195.00 1537.40
50.5 195.05 1537.00

51 195.10 1536.61
51.5 195.15 1536.22
52 195.20 1535.82
52.5 195.25 1535.43
53 195.30 1535.04
53.5 195.35 1534.64
54 195.40 1534.25
54.5 195.45 1533.86
55 195.50 1533.47
55.5 195.55 1533.07
56 195.60 1532.68
56.5 195.65 1532.29
57 195.70 1531.90
57.5 195.75 1531.51
58 195.80 1531.12
58.5 195.85 1530.72
59 195.90 1530.33
59.5 195.95 1529.94
60 196.00 1529.55

CWDM Wavelengths
CWDM uses a grid of four or eight channels denominated in wavelengths,
from 1471 nm to 1611 nm (8-channel) or 1511 to 1571 (4-channel), as listed in
the following table.
CWDM Wavelengths
Nominal central wavelengths 8-channel 4-channel

(nm) for spacing of 20 nm system system
1471
1491
1511
1531
1551
1571
1591
1611

17
Performance Monitoring and
Maintenance
In this chapter:
Overview ....................................................................................................... 17-1
Trail Performance Monitoring ....................................................................... 17-3
Multi Period PM .......................................................................................... 17-10
Maintenance Operations .............................................................................. 17-41
Path Protection Switching ........................................................................... 17-48
Viewing NE Timing Sources ....................................................................... 17-62
ASON Maintenance Operations .................................................................. 17-54
Overview
You can apply maintenance operations to selected trails directly from LightSoft
windows, as follows:
| Trail Performance Monitoring window allows you to view and manage
current trail performance counters.
You can also perform flexible reporting of historical PM counts; see Multi
Period PM.
| Maintenance Operations window allow you to diagnose problems with
connections and ports using the maintenance capabilities of the NEs.
| Path Protection Switching window allows you to view current traffic flow
and perform protection switches for SNCP-protected trails.

Performance Monitoring and Maintenance LightSoft User Manual
This Timing Map window is also described, which allows you to conveniently
monitor the timing sources in the SDH topology for troubleshooting purposes.
In order for SDH signals to pass error-free between NEs, all systems must be
synchronized. A color-coding scheme allows you to view a range of network
timing source information. For more information, see Viewing NE Timing
Sources.
NOTES:
Trail PM, maintenance operations, and path protection
switching can be performed on up to 300 trails at a time.
The functions described in this chapter are not available for
UMEs. Although UMEs participating in trails are shown as
TPs, performance parameters are unavailable for them.
These operations are conveniently performed in LightSoft, without having to

open EMS windows and drill down to internal objects. Each feature enables
GCT to a selected TP within the EMS card view. In LightSoft, these operations
are executed by selected trails, removing the cumbersome process of
identifying the termination points of a trail through NE-centric EMS windows.
Requested commands are automatically relayed to the appropriate EMSs.
NOTE: GCT is enabled according to user permissions.
Topics in Performance Monitoring and Maintenance:

| Trail Performance Monitoring
| Multi Period PM
| Maintenance Operations
| Path Protection Switching
| Viewing NE Timing Sources

LightSoft User Manual Performance Monitoring and Maintenance
Trail Performance Monitoring

The Trail Performance Monitoring window allows you to view and manage
current trail performance counters.
You can view performance counters for selected trails for 15-minute or 24-hour
intervals. PM counters for endpoints, intermediate termination points (TPs),
and incoming PM of endpoints are all supported. Incoming counters reflect the
quality of the signal entering the network.
LightSoft PM data is the same as the data collected and reported by the EMS,
but more useful for network management purposes as it is organized by trail
TPs rather than by NE TPs.
To further assist in troubleshooting, you can reset counters and enable or
disable PM for TPs.
Viewing Trail Performance Data

The Trail Performance Monitoring window lists trail termination points and
associated PM data for selected trails.
Trail PM is not available for UMEs. Although UMEs participating in trails are
shown as TPs, performance parameters are unavailable for them.
OPTIONAL FEATURE: The trail PM functionality is a

fully integrated add-on capability, available on a cost basis; if
not purchased, the feature and related menu options are
unavailable.
To open the Trail Performance Monitoring window:

1. In the Trails pane of the Trail List window, select checkboxes of the
relevant trails.

2. Right-click, and select Trail Utilities > Performance Monitoring >

Current PM. The Trail Performance Monitoring window opens listing
the TPs associated with the selected trails in two time period tabs - 15M
Current (15 Minute) and 24H Current (24 Hour).
The window provides a record for each TP associated with the selected trails and
shows trail timestamp and count information. For details, see the table below.
The rightmost columns in the table represent the time counters. Each TP has its
own counters. Cells where the counter is not relevant to the TP are empty.
A TP record will not have counts if PM is not enabled in the NE, or if there is some
loss of connectivity between the LightSoft and the NE, or if an equipment problem.
In such cases the timestamp cell may be empty or a reason may be provided.
TP records can be filtered according to a variety of criteria. For details, see
Filtering Performance Monitoring Data.
Trail Performance Monitoring window toolbar
Reset PM Data Resets all counters of the selected TPs to zero. Refreshes
only after PM counters are reset to display current values.
Enable PM Sets the selected TPs to PM enabled. Sent to the NE as a
Counters request to monitor the TP.
Disable PM Sets selected TPs to PM disabled. Sent to the NE as a
Counters request to stop monitoring the TP. However, any counters
that are present will remain unchanged.
Select All Selects all TP records.
Clear All Deselects all TP records.
Refresh PM Data Reloads PM information for all TPs related to the selected
trails, reflecting any changes in the network since the
window was last displayed. The time of last refresh is
shown at the bottom of the window. Refresh should be
performed after PM counters are reset.


Show Filter Filters the TP records listed in the Trail Performance
Monitoring window.
Open Selected Opens a GCT to the EMS card view for the selected TP.
Termination
Points
Export to CSV Exports Trail Performance Monitoring window data to a
File CSV file.
Print Out PM Data Prints the Trail Performance Monitoring window data.
Most toolbar options are available as well by right-clicking a TP record. The

shortcut menu also includes the following options only available from this menu.
Trail Performance Monitoring window shortcut options
Option Suboption Description
Selections Add Current Trail Adds all records that share the same trail with
the selected record to the selection.
Remove Current Removes all records that share the same trail
Trail with the selected record from the selection.
Trail Performance Monitoring window fields
Column Description
# Number of the TP in the list.
Trail Label User-defined label for the associated trail.
Trail ID System ID for the associated trail.
ME Name ME in which the TP resides.
LE Name LE where the TP resides in the current topology layer.
TP Name Name of the TP.
Role Role of the TP in the trail:
| Incoming: PM counters of the traffic coming into the network
| Endpoint: PM counters for the TPs of the network PM
| Intermediate: PM counters for intermediate TPs
Path Type Main, Protection, Both, or Mixed.
Timestamp Time the last period started counting. If counts are unavailable (PM is
not enabled in the NE, there is some loss of connectivity between the
LightSoft and the NE, or there is an equipment problem), the
timestamp cell may be empty or a reason may be provided.
Counter names, A separate column for each counter. The counter name has two parts,
in multiple for example, "BBENE VC-4/AU-4", where:
columns | The left part (BBENE) is the counter ID, as shown in the EMS
Current PM Chart window including a near end (NE) or far
end (FE) suffix.
| The right part (VC-4/AU-4) is the associated TP rate.

The Total statistic on the status bar shows the number of records filtered into
the view out of the total number of records that can be displayed.
Enabling or Disabling PM Counters

For some NE types, PM must be enabled for specific termination points.
Otherwise, these TPs will not monitor data and no counters will be retrieved
from the NE.
NOTE: For some NE types (including XDM), the Enable

PM command sets the Monitor Active attribute of the TP to
Yes. In addition to enabling PM counters, the overhead will
now be monitored. The monitoring results in SNCP/N
(instead of SNCP/I) and certain overhead-related alarms will
now be detected.
To enable or disable PM counters for selected TPs:

1. In the Trail Performance Monitoring window, select the TPs. (You can
click the Select All icon to select all at once.)
2. Click the Enable PM Counters icon (or Disable PM Counters icon

). A confirmation prompt opens.
3. Click Yes to continue. The progress bar at the bottom of the window shows
the percentage completion and an Operation Succeeded message appears at
the conclusion. You can stop the process by clicking Abort.
If the operation failed or was partially successful (it could not be applied to
one or more TPs), click Details to view the reasons.
4. When you close the Trail Performance Monitoring window, the
following confirmation message opens if changes to the enable state were
performed.
Click Yes to confirm the actions and close the window. Clicking No will leave
the window open so you can return the enabled mode to its desired state.

Resetting Counters
You can reset all the counters of selected TPs to zero. This can be done at any
time, according to your performance analysis purpose.
To reset the PM counters of selected TPs:

1. In the Trail Performance Monitoring window, select the TPs. (You can
click the Select All icon to select all at once.)
2. Click the Reset PM Counters icon . A confirmation prompt open.
the percentage completion. If the operation failed or was partially
successful (for example, it could not be applied to one or more TPs), click
Details to view the reasons.
4. Click the Refresh PM Data icon to reflect the new values in the Trail
Performance Monitoring window.

Filtering Performance Monitoring Data

You can filter the records that appear in the Trail Performance Monitoring
window.
To filter TPs in the Trail Performance Monitoring window:

1. In the Trail Performance Monitoring window, click the Show Filter icon
. The Performance Monitoring Trail Filter dialog box opens.
2. Select the network objects you want included in the filter. Initially all are
selected.
3. Select the checkboxes to activate the filters you want to apply.
4. If you selected Period Filtering, the Period Filtering panel options are
enabled. Set the From and To dates and times for the filter. These can be
entered either manually or selected using the calendar and the up/down
selectors.
5. Click OK. The Trail Performance Monitoring window is filtered
according to your selections. Click Default to reset the selections to the
system defaults.

Performance Monitoring Trail Filter dialog box components
Option Description
Checkbox Panel
Show N/A Records Filters TPs in which the counters are not functioning, for
example, due to an equipment problem. The counter cell
will be empty. Counter cells may also be empty if the
counter does not apply to the specified TP.
Period Filtering Enable the Period Filtering panel options.
Endpoints Only Filters only the TPs that represent endpoints, omitting any
Incoming or Intermediate.
Period Filter Panel
From Starting date and time for the filter. These can be entered
either manually or selected using the calendar and up/down
selectors.
To Ending date and time for the filter.
Path Type
Main Filters TPs that are on main paths.
Protection Filters TPs that are on protection paths.
Both Filters TPs that are on either path.
NOTE: The Mixed path type cannot be filtered. TPs with

that path type are always listed in the Trail Performance
Monitoring window.

Multi Period PM
The Multi Period PM feature is a report generator providing historical 24-hour
interval PM reporting on a selection of PM counters of interest over an
aggregation of count intervals. Current PM reporting, described in Trail
Performance Monitoring, provides a quick undifferentiated snapshot that shows
all counters for the most recent interval only (15-minute or 24-hour).
The counters are configured in the PM setup of the EMS. While Current PM
draws data directly from the EMS, Multi Period PM collects the EMS data via
an intermediate PM History server database (PMH database). The PMH
database is separate from the LightSoft database and is synchronized with it at
default intervals, generally daily at midnight. The default can be changed as
needed; contact ECI Telecom customer support.
NOTE:
For Multi Period PM purposes new user groups and their
associated users are recognized after the PMH database is
synchronized. For a new user to be able to use Multi Period
PM immediately, the user should temporarily be assigned to a
pre-existing user group.
This feature operates with EMS-XDM version 7.15 or later.
OPTIONAL FEATURE: Multi Period PM is a fully


Producing Multi Period PM Reports

The Multi Period PM window may be opened from either the main menu or
the Trail List window, where traffic records can be preselected.
The procedure involves either applying a template or providing detailed
parameters and filters. A template can also be used as a base and parameters
refined from there. You can preview an abridged version of the report online
for format evaluation purposes before the final report generation is requested.
To create a Multi Period PM report:

1. From the Trail List window:
a. Select the checkboxes of the relevant trail records.
b. Right-click and select Trail Utilities > Performance Monitoring >
Multi Period PM. The Multi Period PM wizard window opens.
OR
2. Click the main window toolbar Multi Period PM icon, or from the
Traffic menu, select Multi Period PM. The Multi Period PM wizard
window opens.
A slightly different window opens according to the selection method; see
Multi Period PM Window. The differences in parameters are described in
context.
3. Enter parameters to the wizard window panes, navigating between them
using the Next and Back buttons.
a. Step 1: Traffic and Template:
Add traffic entities to the reporting process, if needed; see Adding
Traffic Entities.
Apply a template, if needed; see Working with Templates.
Specify filter criteria.
b. Step 2: Report Definitions:
Set the aggregation of the reported counts per TP, and the period
over which they are reported.
Clicking Next after Step 2 starts a query of the PM History database. If
more than a threshold number of records are defined by the query, a
"too many records" message opens; see Large Report Mode.

c. Step 3: Counter List:

Select parameters and counters for the report; see Selecting
Parameters and Counters.
Fine-tune the data records that will be presented; see Narrowing the
Report Content.
Select the report content (Table or Chart).
Select whether all or only out-of-range counts will be listed (in
accordance with threshold settings).
Select the units of the results (raw units or percentages).
4. Perform additional configuration as described in the following sections:
Configuring Thresholds: Configures values and rules that would
identify counts for a counter as "out of range" if they are below/above a
specified threshold.
Advanced Formatting: Configures the report titles and logo, and the
color assigned to out-of-range counts. It also configures how charts will
appear in the report and the color coding of charts per counter.
Report Output Setup: Sets the output format and page size of the report,
as well as its file name and save path.
5. Preview the multi period PM report, as described in Previewing the Report.
Fine-tune parameters as needed.
6. Generate the report; see Generating the Report.

Multi Period PM Window

The Multi Period PM wizard window is used to configure PM reports. It
comprises three wizard panes, between which you can navigate using Forward
and Back buttons:
| Step 1: Traffic and Templates Pane: Adds traffic entities to the reporting
process, applies a template, and specifies Network operator and Customer
filter criteria.
| Step 2: Report Definitions Pane: Sets the aggregation of the reported counts
per TP and the period over which they are reported.
| Step 3: Counter List Pane: Selects parameters and counters for the report,
enables narrowing the range of report records and various report format
selections.
Upon opening, the Template field at the top of the window shows No
Template Selected. After a template is selected, its name is shown. Once any
change is introduced in the window, "modified" is added to the Template field.
A slightly different window opens according to whether the window was
opened from the main menu or from a traffic List window. The differences are
described in context.

Multi Period PM dialog box toolbar and buttons
Preview Report Produces a sample report with a limited

number of report lines for format evaluation
purposes before the final report generation is
requested; see Previewing the Report.
Save Template Creates a new template based on the currently
selected settings; see Working with Templates.
Configure Threshold Configures values and rules that would identify
counts for a counter as "out of range" if they
are below/above a specified threshold; see
Configuring Thresholds.
Advanced Formatting Configures the report titles and logo and the
color assigned to out-of-range counts. It also
configures how charts appear in the report and
the color coding of charts per counter; see
Advanced Formatting.
Report Output Setup Sets the output format and page size of the
report, as well as its file name and save path;
see Report Output Setup.
Export Report to CSV Exports Multi Period PM data to a delimited-
Format format CSV file for subsequent import to
Microsoft Excel or a relational database
application; see Exporting PM Data to CSV.
Open Filter Filters in only records involving trails assigned
specific CoSs; see Filtering by CoS.
Close Closes the window.
Buttons
Generate Produces the report after all settings have been
configured; see Generating the Report.
Back Navigates to the previous wizard step.
Next Navigates to the next wizard step.

Step 1: Traffic and Template

This step is used to:
| Add trails to the reporting process, if needed; see Adding Trails.
| Apply a template, if needed; see Working with Templates.
| Specify Network operator and Customer filter criteria, if needed.
The Add Traffic pane shows the selected trails on whose trail TPs
performance is monitored. It differs according to how the application was
opened:
| When accessed from the Trail List window, the list initially contains the
trails selected in the List window. Trail records can be added if needed; see
Adding Trails.
| When accessed from the main window Multi Period PM icon or the
Traffic menu Multi Period PM option, all trails are initially retrieved.

Multi Period PM - Step1: Traffic and Template pane
Field/Option Description
Traffic Type Trail (default).
Add Traffic
ID Exact System ID for a trail selected for inclusion in the
reporting process; see Trail ID in Trail List Window
Trails Pane Columns.
Label Label of a trail selected for inclusion in the reporting
process. For example, see Label in Create Trail Window
Exact Match is indicated only if TPs are included that
have the trail label in their identification exactly
matching. Exact Match is assigned automatically to
records selected from a List window, or to a record
added via the Add dialog box with the Exact Match
checkbox selected.
Otherwise, TPs are filtered into the reporting process if
the label string is represented in any part of their
identification (for example, "XDM" identifies TP
identifications such as XDM-1, XDM-2, and so on).
Add button Opens the Add Trail dialog box, enabling you to
include more trails to the reporting process.
Remove button Enabled when a record is selected in the list. Removes
the selected trail from the reporting process.
Filter Criteria
Note: You can also filter in only records involving trails assigned specific CoSs; see
Filtering by CoS.
Network Operator Exact Network operator associated with a trail to be
included in the reporting process; see Managing
Network Operators.
Customer Customer associated with a trail to be included in the
reporting process. For example, see Label in Create
Trail Window Basic Trail Parameters Pane.
Exact Match may apply; see description of Label, above.
Template
Summary Report Used to configure a report format that presents PM
checkbox information by trail, with a single summary record line
per TP representing the count for the whole requested
period; see Report Format.
Use Template checkbox Used to base the current report on an existing template;
see Working with Templates.

Adding Trails
If you access the application from the main window Multi Period PM
icon or the Traffic menu Multi Period PM option, all trails are initially
retrieved.
If you access the application from the Trail List window, the list initially
contains the trails selected in the Trail List window. Trail records can be added
if needed; see Adding Trails.
To add trails:
1. Open Step 1: Traffic and Template.
2. Click the Add button. The Add Trail dialog box opens.
3. Enter the following parameters as needed:

ID: Enter the exact trail ID.
Label: Enter the exact label or a partial string. If an exact label is
intended, select the Exact Match checkbox.
4. Click OK to save the entry. The dialog box remains open for more entries.
5. Click Cancel to close the dialog box.
Multi Period PM Step1: Add Trail dialog box fields
Trail ID Exact System ID; see ID description in Step 1: Traffic
and Template.
Label Label, exact or a partial string. If a partial string is
specified, all records that include this sting in their label
are selected for the report; see Label description in Step
1: Traffic and Template.
Exact Match checkbox When selected, the reporting process considers only TPs
with the exactly matching trail label.
Buttons
OK Adds a line to the Add Traffic pane with the indicated
ID/label string.
Clear Clears the field contents.
Cancel Closes the dialog box ignoring any current entries.

Step 2: Report Definitions

This step sets the aggregation of the reported counts per TP, and the period
over which they are reported.
These counts can be reported in the following possible aggregations:
| No aggregation. Each count is presented separately per TP.
| Weekly, monthly or yearly subtotals per TP.
| Whole Period - the daily counts are presented as a single summary total per
TP.
The time period over which the counts are drawn from the count history
maintained in the LightSoft PM History database is set using a time/date filter.
In general, count records are retained (remain available for reporting) for the
last 12 months. The retention period is configurable; contact ECI Telecom
customer support.

Multi Period PM - Step2: Report Definitions pane
24 Hour Aggregation Setting
Aggregated by The counts of each last day's (24 hours) activity are
aggregated according to the selected Aggregated By
option per TP:
| None: No aggregation. Each daily count is
presented separately per TP.
| Week, Month, or Year: The daily counts are
presented as weekly, monthly, or yearly subtotals
per TP.
| Whole Period: The daily counts are presented as a
single total per TP.
Time/Date Filter
Last and Report Period Select Last or Report Period.
radio buttons If Last is selected, select a Period option: Week, Month,
or Year.
If report Period is selected, select From and To dates,
either entered directly to the respective selectors - date
and time (if Hours
granularity applies), or selected from a calendar which
appears by clicking the Calendar icon.

Step 3: Counter List

In this step, the Report Data pane shows a record for each trail TP-and-
timestamp according to the trail and aggregation selections in Steps 1 and 2.
This is the data that the generated report will potentially present (aggregated
according to selections in Step 2: Report Definitions).
This step enables you to:
| Select Parameters and Counters for the Report.
| Choose a narrower range of report records; see Narrowing the Report
Content.
| Specify report formatting by selections in this pane (see the table below):
Report content - Table or Chart format.
All or only out-of-range counts.
Units of the results as raw units or percentages.
The statistics at the bottom of the pane show:

| n/n (for example, 1000/1000): The number of records shown based on
granular selections vs. the total of records currently retrieved. The number of
records shown may be less if a CoS filter is defined; see Filtering by CoS.
| Total: The total number of records potentially available from the database
based on the trail and aggregation selections.

Multi Period PM - Step3: Counter List pane - Report Configuration panes
Report Content radio buttons
Table or Chart radio The Table option presents the report data as only table
buttons data.
The Chart option presents the report data as charts and
summary data (with an option of accompanying table
data).
Charts represent a summary of counts for the selected
time period.
More chart formatting options are available from
Advanced Formatting, including:
| Chart Type: Line, Bar, or Area.
| Chart Appearance: A separate chart per counter, or a
chart per unit (meaning all counters with the same
units are summarized on one chart).
| Charts per line: Number of charts displayed per report
line (subject to page width).
| Add Chart Data: Include detailed report data record
table before each chart graphic.
| Chart Colors: Separate color for each counter
reflected in the charts.
Data Arrangement radio buttons
Show radio buttons Options are:

| All counters data: All counts are included in the
report.
| Only out of range: Only counts which are
determined to be out of range, based on definitions in
Configuring Thresholds are included in the report.
Result Units radio Options are:
buttons | Raw Units: Results denominated in Integer units.
| Percentages: For counters denominated in seconds,
the results are expressed as percentages of the
monitored time.

Large Report Mode

Clicking Next after Step 2 starts a query of the PM History database. If more
than a threshold number of records are defined by the query (configurable in
system defaults), a "too many records" message opens.
Clicking Yes opens Step 3 in a Large Report mode (

appears in the window header). This means that in Step 3 you need to load to
each following set of records from the database by clicking Load Next
and Load Prev arrow buttons. Each set of records is presented as a
retrieved page. The following restrictions apply:
| When you narrow the record set for reporting (see Narrowing the Report
Content), your right-click menu selections apply only to records of the
currently loaded retrieval.
| When the Step 3 report records are sorted by a column, the sorting applies
only to the currently retrieved page. (Any sorting that is performed is not
reflected in the printer report.)
Selecting Parameters and Counters

Parameters and counters of the report are set using the Configure Columns
icon in the top right-hand corner of the table; see Showing, Hiding, and
Auto-Fitting Columns.
The number of parameters/counters that you can select for a report depend on
the report's defined page orientation and width; see Report Output Setup.
Counter availability depends on the technology. See the applicable EMS user
manual for more information.
The following table shows the parameters that can be selected for Multi Period
PM reports involving trails.

Multi Period PM - Step3: Counter List pane - Report Data
Report Data
Label User-defined label for associated trail.

Customer Customer of associated trail (default is descriptor,
printed in the report header).
Operator Network operator of associated trail.
Trail ID System ID of trail.
Trail Rate Rate of trail (default descriptor, printed in the report
header).
Protection Quality Type of protection, if any, configured for trail; see
parameter in Trails Pane Columns.
Path Whether trail is associated with a main or protection
path.
TP Role Role of TP in trail; see Role Label in Viewing Trail
Performance Data.
Layer Rate Layer rate of TP.
CoS CoS applying to associated MoT trail.
ME Name ME in which TP resides.
LE Name LE in which TP resides in the current topology layer.
TP Name Name of the TP (default descriptor, printed in the
report header).
DN An internal object representation.
Time Stamp Timestamp of the specific interval (default
descriptor, printed in the report header).
Monitoring Time Time interval of monitoring - 24 Hour.
Status State of the associated trail TP in the specific time
span; see Trail State in Trails Pane Columns.

Narrowing the Report Content

The Report Data pane shows a record for each trail TP-and-timestamp
according to the trail and aggregation selections in Steps 1 and 2 and which the
generated report will potentially present.
You can choose to report a narrower range of records from this subset,
associated with (or excluding) specific trails or TPs.
NOTE: If the number of potential report records exceeds the

retrieval threshold (see Large Report Mode), when any
records are selected for inclusion/exclusion in the report (as
described below), only the applicable records which appear in
the currently loaded page (for example, the currently
uploaded 1000 records) are considered by the process. Any
applicable records on other pages are not reported.
To narrow the report content:

1. Open Step 3: Counter List which shows the potential report content.
2. If you want count information of only specific trails or TPs to be addressed
by the report (no other trails/TPs should be reported):
a. Right-click to display shortcut menu options and select Deselect All to
clear any record selections, if needed.
b. Select record lines (by clicking and dragging) which include those trails
or TPs. (At least one line mentioning each required trail/TP needs to be
selected.)
c. Right-click to display shortcut menu options, and select:
Add Current Traffic: Reports all records associated with the
specific trails cited in the records that you selected.
OR
Add Current TP: Reports all records associated with the specific
TPs cited in the records that you selected (therefore yields fewer
records than Add Current Traffic).

All the applicable records are highlighted.

OR
3. If you want the report to consider all count information except specific
trails or TPs to be addressed by the report (all other trails or TPs should be
reported):
a. Right-click to display shortcut menu options and select Select All.
b. Select record lines (by clicking and dragging) which show the trails or
TPs to be ignored by the report.
c. Right-click to display shortcut menu options, and select:
Remove Current Traffic: Removes from report consideration all
records associated with the specific trails cited in the records that
you selected.
Remove Current TP: Removes from report consideration all
records associated with the specific TPs cited in the records that
you selected.
All the applicable records are highlighted.
When the report is generated (see Generating the Report), it will include the
specified record content. For more information about the global reporting
procedure, see Performing Multi Period PM.
Working with Templates

Templates can be defined that store the parameter, counter, and filter set for
frequently requested reports. The Template pane in Step 1: Traffic and
Template enables you to select a template and apply its values to the current
report. You can delete a selected template using the button.
You can save the current settings to a new template (or update the settings of an
existing template) using the Save Template toolbar icon.
A template does not address trail selections, which need to be selected for each
report. When a new filter is applied, any pre-existing settings are replaced. As
well, any trail/TP selections are cleared and have to be selected again.
The Summary Report checkbox is used to configure a report format that
presents PM information by trail, with a single summary record line per TP
representing the count for the whole requested period; see Summary Report in
Step 1: Traffic and Template and Report Format.

To apply an existing template:

| In Step 1: Traffic and Template, select Use template checkbox and select
an existing template from the Select Template dropdown list. The template
settings are applied to the current report request.
To delete a template:
| In Step 1: Traffic and Template, select an existing template from the Select
Template dropdown list. A confirmation window opens. Click Yes to
confirm.
To create a new template:

1. If needed apply a template as a base for your new template.
2. Enter or change parameters as required.
3. Click the Save Template toolbar icon. The Save Template dialog box
opens.
4. Enter a name for the template and click OK. If the name already exists (you
want to update the template with different settings), a confirmation window
opens. Click Yes to confirm.

Configuring Thresholds
This dialog box is used to configure values and rules that identify counts for a
counter as "out of range" if they are below/above a specified threshold. The
counters in the Configure Thresholds list are selected for reporting using the
Configure Columns icon in Step 3: Counter List Pane. (The list is empty if
counters have not yet been selected.)
Out-of-range counts can be color coded in the report; see Out of range Color
in Advanced Formatting.
The report can be restricted to out-of-range counts; see the Only out of range
radio button in Step 3: Counter List Pane.
To open the Configuring Thresholds dialog box:

| From the Multi Period Performance Monitoring window, select the
Report Output Setup toolbar icon.
Multi Period PM : Configure Thresholds dialog box columns and options
Column/Option Description
Counter Name Name of the counter, as selected for reporting in Step 3:
Counter List Pane.
Threshold Value Reference threshold value. Double-click in the field to
open it for editing.
Threshold Rule Select an option from the dropdown list:
| Above: A count is out of range if it exceeds the
threshold value.
| Below: A count is out of range if it is less than the
threshold value.
| Ignore: No rule applies. Out of range counts are not
identified.

Column/Option Description
Buttons
Apply Applies the current settings and keeps the dialog box
open for more changes.
Reset Returns system defaults, clearing input values.
Close Closes the dialog box. (Any changes since the last Apply
are not saved.)
Advanced Formatting
This dialog box is used to configure the report titles and logo, and the color
assigned to out-of-range counts. It also configures how charts will appear in the
report and the color coding of charts per counter.
To open the Advanced Formatting dialog box:

Advanced Formatting toolbar icon.

Multi Period PM: Advanced Formatting dialog box fields
Report Titles
Report Title Title for first page of report.
Page Title Title for subsequent pages.
Report Logo
Add Logo checkbox and Logo that can appear on the top-right side first report
Browse button pages. User may browse and select a logo. No logo
appears until one is selected.
(The ECI Telecom logo appears on the top-left side of
first report pages.)
Threshold Color
Out of Range Color Color in which out-of-range records (as defined in
selector Configuring Thresholds) appear in reports.
The color selector is opened by clicking a counter's
color swatch. The color selection procedure is similar to
that described in Customizing LightSoft Object Colors.
Chart Arrangement
Available when the Report Content - Chart radio button is selected in Step 3:
Counter List Pane.
Chart Type Options are:
| Line Chart
| Bar Chart
| Area Chart
Chart Appearance Information can be presented per counter or in summary

form, as follows:
| Chart/Counter: A separate chart shown for each
counter.
| Chart/Unit: If the same units apply, all counters are
summarized on one chart.
Chart Per Line Number of charts displayed per report line, entered
directly to the field or selected using the arrow keys.
Note: The number is limited by the report's page width.
If too many charts per line are specified, the report will
not generate. The page width is based on the Report
Output Setup.
Add Chart Data checkbox When selected, includes the corresponding detailed
report data record table before each chart graphic. Else
only the charts are shown.

Chart Colors
Available when the Report Content - Chart radio button is selected in Step 3:
Counter List Pane.
Counter name Name of a counter.
Chart Color Separate color for each counter reflected in the charts.
The color selector is opened by clicking a counter's
color swatch. The color selection procedure is similar to
that described in Customizing LightSoft Object Colors.
Buttons
OK Saves the specified color configuration.
Default Returns the factory defaults.
Cancel Closes the dialog box. (Any changes since the last OK
are not saved.)
Report Output Setup

This dialog box enables you to set the output format and page size of the report,
as well as its file name and save path.
The report can also be exported to a CSV format; see Exporting PM Data to
CSV.
NOTE: The number of columns and/or charts allowed for a

report is limited by the page width, as defined by Paper Size
and Orientation.
To open the Report Output Setup dialog box:

Report Output Setup toolbar icon.

Multi Period PM: Report Output Setup dialog box fields
Saving Setup
Print to File checkbox When selected, enables a File Format dropdown list,
which allows a choice of PDF, RTF, or Web page (htm
or html) format.
The report can also be exported to a CSV format; see
Exporting PM Data to CSV.
File Name and Save Path When printing to file, you must specify a file name and
browser save path. Otherwise the report will not generate
(warning "Output report file is not defined" is
displayed).
Click the Browser icon to open a standard Browse
window where you can enter name the file and specify
the save path.
Open in Viewer checkbox After the report is generated, it is opened in a pdf
viewer.
Printing Setup
Printer name Enables a choice of system printer. (Not available if
Print to File checkbox is selected.)
Paper Size Enables a choice of standard paper sizes.
Orientation radio buttons Select Landscape or Portrait.
Buttons
OK Saves the current settings and closes the dialog box.
Cancel Closes the dialog box ignoring any current entries.
Exporting PM Data to CSV

You can export Multi Period PM data to a delimited-format CSV file for
To open the Report Output Setup dialog box:

1. From the Multi Period Performance Monitoring window, select the Report
Output Setup toolbar icon. An Export To File dialog box opens.
2. Continue as described in the generic procedure in Exporting to CSV.

Filtering by CoS
You can choose to filter in only records involving trails assigned specific CoSs.
For the filter to operate, the CoS parameter must be selected. The Step 3:
Counter List displays a subset of the records retrieved from the PMH that
satisfy the CoS filter.
Network Operator and Customer filter options are available from the Filter
Criteria pane; see Step 1: Traffic and Template. (These filters work slightly
differently than the CoS filter in that they act directly on the record set
retrieved from the PMH.)
To filter by CoS:
1. Ensure that the CoS parameter is selected in Step 3: Counter List; see
Selecting Parameters and Counters.
2. From the Multi Period Performance Monitoring window, select the
Open Filter toolbar icon. The Filter dialog box opens.
3. Select the CoSs to be filtered into the report.

4. Click Apply to save the settings, and Close to close the dialog box.
Multi Period PM : Open Filter options
Icon/Option Description
Icons
Selects the checkboxes of all CoS options (default,
Check All meaning there is no limitation to the reporting based on
CoS).
Deselects all checkboxes.
Uncheck All
CoS Filter
CoS 0 to 7 Filters in records associated only with trails having CoS
designations whose checkboxes are selected.
Undefined CoS Filters in records associated only with trails having no
CoS designations, for example, non-MoT trails.

Icon/Option Description
Buttons
Apply Applies the current settings without closing the dialog
box.
Close Closes the dialog box. (Any changes since the last Apply
are not saved.)
Previewing the Report

Before you generate the final report, you can preview an abridged version
online in order to evaluate its format. This report has the same format as the
final generated version, but with, for example, up to 100 report lines. The
number of lines is configurable; contact ECI Telecom customer support.
The report view window provides a variety of toolbar options for saving,
printing, scrolling, and changing the view; see Preview Window Options.
To preview the report:

Preview Report toolbar icon. The report is generated and opens in a
view window.

Preview Window Options

The Preview window provides the following toolbar options.
Multi Period PM Preview window toolbar options

Save Saves the report in a PDF, HTML, or CSV
format.
Print Prints the current report to a system printer.
Refresh Refreshes the report contents.
Scroll Back Scrolls the report back to the first or previous

page, respectively.
Scroll Forward Scrolls the report forward to the next or last
page, respectively.
Page Number Shows the page number of the currently
displayed report page.
100% Resizes the report page to 100%.
Fit to Screen Resizes the report page to fit the screen.
Fit to Width Resizes the report page to fit the screen width.
Magnify/Reduce Magnifies or reduces the page view by one step.
Magnification Shows the current magnification (range 50%-

% 100%).

Generating the Report

You can preview an abridged version of the report online in order to evaluate
its format; see Previewing the Report. When you are satisfied with the report
settings, you can generate the report.
Longer reports (exceeding a threshold number of records; see Step 3: Counter
List) may take more time to generate. The process can be cancelled at any point
before its conclusion.
Any column sorts performed on Step 3 records are not reflected in reports.
For details about the report format, see Report Format.
To generate the report:

1. When printing to file, ensure that a file name and save path are specified.
Otherwise the report will not generate (warning "Output report file is not
defined" is displayed); see Report Output Setup.
2. From the Multi Period Performance Monitoring window, click the
Generate button; see Multi Period PM Window. A confirmation window
opens showing the current report settings.

3. Examine the settings. If you are satisfied, click Yes to produce the report.
If you selected Open in Viewer in Report Output Setup, the report opens in
the default viewer.
Report Format
Multi Period PM reports include the following elements:
| Report header: Applies to all reports.
| Subtitle per TP: Applies to all reports.
| Detailed Count Table: Applies to all reports except Summary.
| Summary Report Detailed Count Table: Applies to Summary report only.
| Overall Statistics per TP: Applies to all reports.
| Chart Graphics: Applies to Chart reports only.
Report Header
All Multi Period PM report variations show report headers similar to the
following:

Multi Period PM: Report Header
Report element Description

Logo Logo displayed at the top of the first page, as defined in
Report Title Title displayed at the top of the first page, as defined in
Generated Date/time report was generated or preview requested.
Report Period Report time span as defined in Step 2: Report
Definitions Pane.
Thresholds If Thresholds were defined (see Configuring
Thresholds), shows the configured threshold value for
each applicable counter.
Page Title Title defined in Advanced Formatting displayed directly
before the report content and repeated at the top of each
subsequent page.
Subtitle per TP
In regular reports (non-Summary), PM information is presented per TP and
according to the aggregation specified in Step 2: Report Definitions. The PM
information for a TP is preceded by the following subtitle captions. The
captions are repeated at the top of each new page.
Summary reports are requested by clicking the Summary checkbox in Step 1:

Traffic and Template. Summary reports present PM information by trail, with a
single summary record line per TP representing the count for the whole
requested period. The TP name is therefore included in the report columns
(instead of the subtitle); see Summary Report Detailed Count Table.
Multi Period PM: Subtitle caption per Information Segment

Customer Customer associated with the trail/TP, as defined in Step
1: Traffic and Templates Pane.
Trail Label Trail associated with the TP.
Trail Rate Associated trail rate.
TP Name TP name. Not applicable to Summary reports (see
Summary checkbox in Step 1: Traffic and Template).
For Summary reports, the TP name is shown in the
column information.

Detailed Count Table

A table of detailed counts per counter specified for a TP is displayed when:
| Table is selected as the Report Content in Step 3: Counter List Pane.
| Chart is selected as the Report Content in Step 3: Counter List Pane and
Add Chart Data is selected in Advanced Formatting. The detailed counts
table is presented first, before the charts (see Charts below).
Multi Period PM: Detailed count per counter table

Table Columns Parameters and counters, as selected in Step 3: Counter
List Pane.
The Timestamp column appears by default. It provides
the date/time of the first 24-hour measurement within an
aggregation. If the aggregation period is None, it
provides the date/time at each measurement interval.
The applicable aggregation is defined in Step 2: Report
Definitions Pane.
Table Rows One measurement line per aggregation defined in Step 2:
Report Definitions Pane.
Summary Report Detailed Count Table

The Summary report includes a detailed count table which presents the count
information by trail instead of by TP. The TP name is included as a table
parameter instead of the subtitle. The same table definitions apply as for
Detailed_Count_Table.

Overall Statistics per TP

All reports (except the Summary report) include an Overall Statistics table after
each TP's detailed count table and before charts. This table shows various
aggregations of the TP counters.
Multi Period PM: Overall Statistics per TP

Table Columns Parameters and counters, same as described for Detailed Count
Table.
Table Rows The following aggregation statistics are provided for each counter
specified for the TP:
| Summary: Sum of measurements for each column parameter
over the entire reporting period.
| Average: The Summary divided by the number of aggregate
measurements.
| W. Average: Sum of (count x monitoring time) / Sum of
monitoring times.
| Max: Maximum observed aggregation measurement.
| Min: Minimum observed aggregation measurement.
Chart Graphics
If Chart is selected as the Report Content in Step 3: Counter List Pane,
graphical charts are displayed for each TP.
The following chart settings are set in the Chart Arrangement pane in
Advanced Formatting:
| Chart type - line, bar, or area.
| Chart appearance - single summary chart per TP or separate charts per
counter.
| Charts per line - number of charts per report line.
| Add chart data - whether a detailed count table should be included before
the charts.
The charts for each TP are preceded in the report by:
| TP identification (see Subtitle per TP).
| Overall TP statistics (see Overall Statistics per TP).
| Detailed count table (see Detailed Count Table) if Add Chart Data is
selected in Advanced Formatting.

Other Multi Period PM Configurations

Certain Wizard as well as PMH server default values can be modified
according to your Multi Period PM reporting needs, with the assistance of ECI
Telecom customer support. For example:
| EMS type: XDM, or BG. You can omit configuration of EMS types
relating to non-relevant equipment to save communication.
| EMS: You can collect counts from only specific EMSs, or from all except
specific EMSs.
| Preview Maximum Records: Default is 100. You can set the number of
records to be included in the Preview report; see Previewing the Report.
| Last Week aggregation: You can define the week to start on a certain day,
for example, Monday.
| Maximum records per retrieval (see Retrieval Threshold): Default is 10000.
You can set this in accordance with Client memory capability limits.
| Retention period: Records are removed from the PMH database after this
time: Default is one year of 24-hour counts. This may be modified as
needed.
| Synchronization of PMH with LightSoft database: By default automatically
performed once per day at midnight. The time and frequency of
synchronization can be changed as needed. Before synchronization, Multi
Period PM reporting uses the data in the PMH database to that point. The
PMH database is not be aware of current changes to trails.
| PMH Root File path: You can set where the raw data files sent by sftp to
the PMH are stored. The retention of raw data files after a parsed version of
the data is created can be set according to troubleshooting needs.

Maintenance Operations
Maintenance operations enable diagnosis of problems in the network. This
feature enables you to apply these actions to specific ports and TPs that are
used by trails and topology links managed by LightSoft.
Maintenance Operations Window

The Maintenance Operations window enables you to manage (view and
apply) maintenance operations on trails and topology links. It lists the TPs and
associated maintenance information for selected trails or links for which TP
maintenance operations should be carried out.
These functions are traffic-affecting and should be used only by experienced
operators.
OPTIONAL FEATURE: The Maintenance Operations

functionality is a fully integrated add-on capability, available
on a cost basis; if not purchased, the feature and the related
To open the Maintenance Operations window showing TPs

of selected trails:
| In the Trails pane of the Trail List window, right-click the trail/s and select
Trail Utilities > Maintenance Operations. The Maintenance Operations
window opens showing the TPs associated with the selected trails.

To open the Maintenance Operations window showing TPs

of selected links:
| In the Actual Links between Two MEs dialog box, select the links, right-
click, and select Maintenance Operations on the shortcut menu. The
Maintenance Operations window opens showing the TPs associated with
the selected links.
The Maintenance Operations window provides one or more records for each
TP associated with the selected trails or links, one for each layer rate of the TP
or port that supports maintenance operations in the NE.
NOTE: LightSoft presents all potential layers that support

maintenance operations. Some layer rates may not be
applicable for some ports of some NE types. See the EMS
manual to see which operations are supported by the NE.
The Operations column shows the applied operations on the indicated TP since
the last refresh.
The TP records can be filtered according to a variety of criteria. For details, see
Filtering Maintenance Operation Data.
Maintenance Operations window toolbar

Force RDI Forces a Remote Defect Indication (RDI) to test proper
reception at the other endpoint of the path.
Forced AIS Forces an Alarm Indication Signal (AIS) downstream or
Facility sends an AIS upstream to an object in the adjacent node in a
network. The target port is the (near end) port that exits the
NE. AIS actions are traffic-affecting.
Forced AIS Same as Forced AIS Facility, but with the target port being
Terminal in the (far end) external NE.
Loopback Combination of Loopback and Forced AIS, with the target
Facility and port being the (near end) port that exits the current NE.
Force AIS


Loopback Combination of Loopback and Forced AIS, with the target
Terminal and port being in the (far end) external NE.
Force AIS
Loopback Performs a loopback with the target port being the (near
Facility end) port that exits the NE - indicates if the traffic from the
I/O card is returned to the card, thereby validating the
internal connection.
Loopback actions are traffic-affecting.
Loopback Performs a loopback with the target port being in the (far
Terminal end) external NE - indicates if the traffic from the line is
returned to the line, thereby validating the full path of the
connection.
Release All Removes any maintenance operations applied to the
Operations selected records. (Maintenance operations are persistent
until they are released.)
Show Lists the higher order trails used as server trails of the
underlying selected trails.
trail for trail Each individual trail can have several listed server trails.
A trail built as a concatenation of consecutive high order
trails (connecting multiple NEs through XCs in the
intermediate NEs) is shown as having multiple separate
underlying high order trails.
Several selected trails may have the same or different
underlying high order trails, for example 8 E1s contained
in 3 VC-4s.
Show Lists the higher level trail flowing from the selected TPs
underlying trail without regard to flows beyond the next TP. This function
for TPs limits the listed trails to those specifically related to the
selected TP. This is useful when a problem is known to
involve only the specific section of a trail.
Show entire When the Maintenance Operations window is opened for
path TPs selected trails, only the endpoint TPs are listed. The Show
entire path TPs option also lists intermediate TPs.
Records can be removed from the visual display by
filtering.
Select all Selects all TPs records at once.
Clear all Deselects all TP records at once.
Open Opens a GCT to the EMS card view for the selected
endpoint or intermediate TP.
Refresh Reloads the maintenance information for all TPs related to
the selected trails, reflecting any changes in the network
since the window was last refreshed or opened. If the Show
entire path TPs option is used, intermediate TP records are
also reloaded. The time of last refresh is shown at the
bottom of the window.


Filter Filters the TP records listed in the Maintenance
Operations window.
Export to CSV Exports the Maintenance Operations window data to a
CSV format file.
Print Prints the Maintenance Operations window data.
Most toolbar options are available as well by right-clicking a TP record. The

shortcut menu also includes the following options only available from this menu.
Maintenance Operations shortcut menu options
Option Description
Add Current Trail Adds all the records that share the same trail with the right-
clicked record to the current selected records.
Remove Current Trail Removes all the records that share the same trail with the right-
clicked record from the current selected records.
Maintenance Operations window fields
Column Description Applies to

# Number of the TP in the list.
Trail ID System ID for the related trail. TPs of trails
Trail Label User-defined label for the trail. TPs of trails
LE Name LE where the TP resides on the current topology TPs of trails
layer.
Link Name Name of the related link. TPs of a link
ME Name ME in which the TP resides.
TP Name Name of the TP.
Layer Rate Transmission rate of the record.
Role Add, Drop, Add & Drop.
Path Type Main, Protection, Both, or Mixed.
Operations Values of Yes or No. The current state of
maintenance operations applied to the TP. It
indicates if any maintenance commands have
been applied. To see the exact operation, the GCT
to the EMS is required. This field is up to date as
of the last refresh.
The Total statistic at the bottom of the list shows the number of records filtered
into the view out of the total number of records that can be displayed.

Performing Maintenance Operations

Maintenance operations may be traffic-affecting. The maintenance operations
performed on a TP/port are persistent until they are cleared/released from
LightSoft or from the EMS or LCT.
To perform maintenance operations:

1. In the Maintenance Operations window, select the list records of the TPs
and select an option. A warning appears reminding you that the action may
be traffic-affecting.
the percentage completion, and an Operation Succeeded message appears at
the conclusion. You can stop the operation by clicking Abort.
For each selected TP in which the operation succeeded, the Operations
column in the Maintenance Operations window shows the operation and
its result.
one or more TPs), click the Details button to view the reasons.

Filtering Maintenance Operation Data

You can filter the TP records listed in the Maintenance Operations window.
To filter TPs in the Maintenance Operations window:

1. In the Maintenance Operations window, click the Filter icon. The Filter
dialog box opens.
2. Select the options by which you want to filter the list.

3. Click OK. The Maintenance Operations window is filtered according to
your selections. Click Default to reset the selections to the system defaults.

Maintenance Operations Filter dialog box menu options
Option Description
Resource Filter
Layer Topology layer containing the required network objects.
Tree Shows the network objects for the selected trails and their
respective slots, cards, and ports (PTPs) in a hierarchical
structure. Allows you to filter the specific branches in
elements for which TPs should be listed. Only selected
resources are filtered.
Operation
Loopback Terminal Filters in the Maintenance Operations window only TPs in
Loopback Facility which the selected operations are present. For more
Forced AIS Facility information, see Maintenance Operations.
Forced AIS Terminal
Forced RDI
Endpoints Only
Endpoints only Filters the TPs that represent endpoints, filtering out
intermediate ones.
Path Type
Main Filters TPs on main paths.
Protection Filters TPs on protection paths.
Both Filters TPs on both main and protection paths.

Path Protection Switching

LightSoft enables you to view current traffic flows and apply protection switch
commands on SDH-protected subnetwork connections (SNCPs) residing in
NEs, thereby redirecting the traffic flows across the main and protected routes.
Each SNCP switch comprises three termination points that define the flow of
data through the NE:
| Main TP - receives traffic from the main path.
| Protection TP - receives traffic from the protection path.
| Switch (or Protected) TP - receives traffic from either the main or
protection TP, according to the application. In normal operational
conditions traffic is received from the main TP. If the main path is alarmed,
traffic is received from the protection TP. When the alarm clears, the traffic
switches back to the main TP only if SNCP is configured to "revertive
mode". The reversion mode must be configured from an EMS or LCT.
The Path Protection Switch feature enables you to impose a different

main/protection flow according to network requirements. The functions are
parallel to those offered by the EMS, with the advantage that they are presented
from the trail's perspective. LightSoft views and manages all path switches of a
trail, even those not at the trail endpoints.
LightSoft supports the following protection switching actions:
| Manual switch - causes the switch TP to receive traffic from the selected
(main or protection) TP. This is performed only if the selected switch's trail
source is not alarmed. The flow automatically reverts back to the other
switch if the selected switch trail source becomes alarmed.
| Force switch - same as Manual switch, but with the imposed flow
remaining in effect regardless of current or subsequent alarms.
| Lock on switch - causes the switch TP never to receive traffic from the
selected TP, regardless of current or subsequent alarms.
The above commands remain in effect until Clear All is used to remove them
from any SNCPs to which they have been applied.

NOTE: Path Protection Switch commands may be traffic-

affecting.
OPTIONAL FEATURE: The Path Protection Switch

functionality is a fully integrated add-on capability, available
on a cost basis. If not purchased, the feature and the related
Path Protection Switch Window

For SNCP-protected trails, the Path Protection Switch window lists trail
SNCPs (one or more, each listed as a record), and provides information about
the SNCP's associated main, protection, and switch TPs. When the trail's SNCP
is performed by the underlying layer VC-4 server trails, you have to open the
Protection Switch window from the Trail List window for the protected VC-4
server trails.
To open the Path Protection Switch window:

| In the Trails pane of the Trail List window, right-click SNCP-protected
trails and select Trail Utilities > Path Protection Switch. The Path
Protection Switch window opens, showing the SNCPs associated with the
selected trails.
NOTE: The Path Protection Switch window opens only if

SNCP trails are selected. You can view whether the trails are
SNCP-protected by clicking the Details button.

Path Protection Switch window toolbar

Lockout of Causes the switch TP to always receive traffic from the
Protection (use main TP and never from the protection TP, regardless of
Main) alarms.
Lockout of Main Causes the switch TP to always receive traffic from the
(use Protection) protection TP and never from the main TP, regardless of
alarms.
Force to Main Causes the switch TP to receive traffic from the main TP,
regardless of alarms.
Force to Causes the switch TP to receive traffic from the protection
Protection TP, regardless of alarms.
Manual to Main Causes the switch TP to receive traffic from the main TP if
there are no alarms.
Manual to Causes the switch TP to receive traffic from the protection
Protection TP if there are no alarms.
Release All Clears all commands applying to any of the listed SNCPs.
Enabled if commands have been applied to one or more
SNCPs (Applied appears in the User Command column).
Select All Selects all listed SNCPs.
Unselect All Unselects all listed SNCPs.
Refresh Reloads SNCP protection information from the network

for the trails for which it was opened since the window was
first opened or since the last refresh. The time of last
refresh is shown at the bottom of the window.
The status bar shows the progress of the refresh (or initial
load) operation. If SNCP information cannot be loaded for
the requested trails, a Partially Succeeded message
appears. Click Details for information about trails that
could not be loaded.
Open Filter Opens a filter dialog box where you can filter SNCP
window records in the Path Protection Switch window.
Open Switch TP Opens a GCT to the EMS card view for the switch TP of
the selected SNCP.
Export to CSV file Exports Path Protection Switch window data to a CSV
file.
Print Prints the Path Protection Switch window data.
The command function icons are enabled only when applicable (for example,
they are disabled for SNCPs that reside in a UME). Most toolbar options are
also available by right-clicking an SNCP record.

The shortcut menu also includes the following options that are only available
from this menu.
Path Protection Switch shortcut menu options
Option Description
PS Commands Lists all available commands, as from the window toolbar.
Selections - Adds all records that share the same trail with the selected record to
Add Current the current selection.
Trail
Selections - Removes all records that share the same trail with the selected record
Remove from the current selection.
Current Trail
Port Properties Shows the port properties of the switch TP (switch port properties).
For more information, see Port Properties.
Path Protection Switch window fields
Column Description
# Number of the SNCP in the list.
Trail Label User-defined label for the associated trail.
Trail ID System ID for the trail.
Layer Rate Transmission rate of the trail, for example, VC-4.
Role Role of the SNCP in the trail: Intermediate or Endpoint.
ME ME where the SNCP resides.
LE LE where the SNCP resides.
Main TP Identification of the main TP in the SNCP, comprising the
corresponding Slot, Port, and CTP IDs.
The switch TP is currently receiving the signal from the main TP (not
applicable if SNCP resides in a UME).
Switch TP Identification of the switch TP in the SNCP, comprising the
The switch TP is currently receiving the signal from the protection TP
(not applicable if the SNCP does not reside in an ME).
Protection TP Identification of the protection TP in the SNCP, comprising the

Column Description
User command | Applied: A user command is in effect.
| None: No user command is in effect. The switch TP receives
traffic according to normal operating conditions.
| Unmanaged: The SNCP resides in a UME and the user command,
if applicable, is not known to LightSoft.
| N/A: A refresh operation was aborted before all data records
could be filled with information.
| A failure reason, for example:
- Synchronization error (inconsistency, possibly temporary)
between LightSoft and the respective EMS)
- EMS Disconnected
- EMS Failure
- NE Disconnected
- Operation Not Supported
- Unknown Error
The status bar shows the number of records filtered into the view out of the
total number of records that can be displayed.
Applying Path Protection Switch Commands

Path Protection Switch commands are persistent. You must click Release all to
remove them from SNCPs to which they have been applied. This can also be done
from the EMS or LCT. Path Protection Switch actions may be traffic-affecting.
To apply path protection switching commands:

1. In the Path Protection Switch window, select the list records representing
the required SNCPs and click the required option. A warning appears,
reminding you that the action may be traffic-affecting.
2. Click Yes to continue. The progress bar at the bottom of the window
indicates the process status. An Operation Succeeded message appears at
the conclusion. You can stop the processing by clicking Abort.
For each selected SNCP where the operation succeeded, the User command
column shows Applied.
one or more SNCPs), click the Details button to view the reasons. (This
button appears only in the event of a failure.)

Filtering Path Protection Switch Data

You can filter the SNCP records displayed in the Path Protection Switch
window.
To filter SNCPs in the Path Protection Switch window:
1. In the Path Protection Switch window, click the Show Filter icon .
The Path Protection Switch Filter dialog box opens.
2. Select the options according to which you want to filter the list.
3. Click OK. The Path Protection Switch window is filtered according to
your selections. Click Default to reset the selections to the system defaults.
Path Protection Switch Filter dialog box options
Option Description
Resource Filter
TP Type Select the type of TPs shown in the tree of the filter dialog
box: Switch, Main, Protection, or All.
Layer Only the SDH layer is relevant for SNCP purposes.
Selecting either SDH or Physical (Site) gives the same filter
choices but uses ME grouping instead of LE grouping.
Tree Shows network objects associated with the selected SNCP
trails and their respective slots, cards, and ports in a
hierarchical structure. Allows you to filter the specific
branches in elements for which SNCPs should be listed.

Option Description
Active Path
Main Filters SNCPs in which the switch TP receives traffic from
the main TP.
Protection Filters SNCPs in which the switch TP receives traffic from
the protection TP.
Both Filters SNCPs irrespective of the signal source.
User Command
Filters into the Path Protection Switch window only SNCP records in which the
selected operations are present:
Applied Filters records that have a protection switch action applied.
None Filters records that have no protection switch actions
applied.
Data Retrieval Failed Filters records that have a data retrieval failure.
N/A Filters records that have N/A for the user command.
Unmanaged Filters records for UMEs.
ASON Maintenance Operations

ASON Maintenance operations enable you to apply the following actions to
ASON trails:
| Revert the current trail paths (main, protection, or both) to the provisioned
paths, or
| Reroute the current trail paths (main, protection, or both) to an alternate
route found by ASON, and
| Allow/inhibit these actions on the related ASON trails
The ASON Maintenance Operations window enables you to manage (view

and apply) maintenance operations on selected ASON trails.
NOTE: Reroute of 1+R trails is traffic affecting and should be

used only by experienced operators. Reroute of 1++ trails may
cause a traffic hit (less than 50 ms interruption). Other ASON
Maintenance operation functions are not traffic-affecting.

OPTIONAL FEATURE: The ASON Maintenance

Operations functionality is a fully integrated add-on capability,
available on a cost basis; if not purchased, the feature and the
related menu options are unavailable.
Opening the ASON Maintenance

Operations Window
To open the ASON Maintenance Operations window showing
TPs of selected ASON trails:
| In the Trails pane of the Trail List window, right-click the trail/s and
select Trail Utilities > ASON Maintenance Operations. The ASON
Maintenance Operations window opens showing the selected trails. (If
there is no data to display on the selected trails, an error message appears.
Click OK to close the window.)
NOTE: There are two “Maintenance” shortcut options:

- Maintenance Operations for regular trails, and
- ASON Maintenance Operations for ASON trails.
The Maintenance Operations option will be enabled for an
ASON trail if one of the trail TPs is a regular port. For more
information about regular LightSoft trail maintenance
operations, see Maintenance Operations.

Performing ASON Maintenance

Operations
ASON Maintenance operations may be traffic-affecting. The maintenance
operations performed on a trail are persistent until they are cleared/released
from LightSoft or from the EMS or LCT.
NOTE:
After you reroute a trail, unless revert is inhibited, the trail
automatically revert to the provisioned path after the wait to
restore (WTR) time elapses (assuming the provisioned path
links are not faulty). This will occur even if no revert
operation was committed.
WRT is the stabilization delay following repair before traffic
is switched back to the originally provisioned path - 6 minute
default can be changed). WTR is defined per node, with the
Head End node of each trail governing the switchback
behavior. (The terminating node WTR is not relevant.)
To perform ASON maintenance operations:

1. In the ASON Maintenance Operations window, select the required trail
by clicking to highlight it (hold the Ctrl key while clicking to select
multiple trails).
2. Select an option. A warning appears reminding you that the action may be
traffic-affecting.
the percentage completion, and an Operation Succeeded message appears at
the conclusion. You can stop the operation by clicking Abort.
For each selected trail in which the operation succeeded, the Operations
column in the ASON Maintenance Operations window shows the
operation and its result in the window footer.
one or more trails), a message appears in the window footer. Click the
Details button for more information. (This button appears only in the event
of a failure.)

ASON Maintenance Operations Window

and Options
ASON maintenance operations can be performed on selected ASON trails and
are provided either separately for Main and Protection Path, or for both
simultaneously. (For the latter, select the options via the shortcut menu Main
and Protection category.) Multiple command selections are supported.
When trail lines are selected, the switch commands are enabled. (Operations that were
inhibited are disabled.) Selected commands are executed if the trails otherwise suit the
selected commands and as user permissions allow. Otherwise, the action fails and no
data is received.
The window generally provides one row of information per selected trail. If a trail has
several head ends (because it traverses several ASON domains), a row appears for
each head end.
NOTE: The user-requested changes and command status are

reflected in the table only after Refresh is performed to reload
the table content.
ASON Maintenance Operations window toolbar

Revert Manual Reverts the selected trail main paths to the provisioned
Main Path main route.
Revert Manual Reverts the selected trail protection paths to the
Protection Path provisioned protection route.
Revert Force Reverts the selected trail main paths to the provisioned
Main Path route regardless of the path status (for example, even if
the action is traffic affecting).
Revert Force Reverts the selected trail protection paths to the
Protection Path provisioned protection route regardless of the path status
(for example, even if the action is traffic affecting).


Reroute Manual Switches the main path of selected trails to an alternate
Main Path route automatically found by ASON.
Reroute of 1+R trails is traffic affecting and should be
used only by experienced operators. Reroute of 1++ trails
may cause a traffic hit (less than 50 ms interruption). If
no operational route is available, the action is not
performed. In this case traffic is not affected.
Note: Reroute functions do not change the path state.
They perform a controlled reroute, temporarily rerouting
a trail that is to undergo repair/texting, in the same way
as reroute upon failure, but performed manually.
Changing the provisioned path requires editing the trail
and performing TCI. For details, see Redefining an
ASON Trail’s Provisioned Path.
Reroute Manual Switches the protection path of selected trails to an
Protection Path alternate route automatically found by ASON.
Select all Selects all trail records at once.
Clear all Deselects all trail records at once.
Refresh Reloads the maintenance information for all the listed

trails, reflecting any changes in the network since the
window was last refreshed or opened. The time of last
refresh is shown at the bottom of the window.
Filter Filters the trail records listed in the ASON Maintenance
Operations window.
Print Prints the ASON Maintenance Operations window
data.

ASON Maintenance Shortcut Options

The toolbar functions are also available right-clicking a trail record.
The shortcut options are set up so they can be performed either:
| Individually on the main or protection path, or
| Simultaneously on both paths
The shortcut menu also includes the following options only available from this
menu.
ASON Maintenance Operations shortcut menu options
Option Description
Inhibit Inhibits restoration of the selected ASON trail or trail path.
Restoration Forces a path to stay on it current path route even if failure
has occurred.
Allow Allows restoration of the selected ASON trail or trail path
Restoration (default).
Inhibit Inhibits reversion of the selected ASON trails. Forces the
Reversion rerouted trail to stay on its current route even if the
provisioned path routes have recovered.
Allow Allows reversion of the selected ASON trails (default).
Reversion
Add Current Used to select multiple trails in the ASON Maintenance
Traffic Operations list in the same way as holding the Ctrl key while
clicking.
Remove Used to deselect multiple trails in the ASON Maintenance
Current Traffic Operations list in the same way as holding the Ctrl key while
clicking.
According to the option selected, the window’s Restoration Allowed and

Reversion Allowed columns indicate trail paths for which the operations are
allowed (Main, Protection or Both). Otherwise Inhibited is displayed, meaning
the operation is not allowed for either path.
NOTE: The user-requested changes and command status are

reflected in the table only after Refresh is performed to reload
the table content.

ASON Maintenance Operations window fields
Column Description
# Number of the trail in the list.
Trail ID System ID for the trail.
Trail Label User-defined label for the trail.
ME Name Head-end ME which the trail traverses.
Path State Whether the trail working path is currently the main path
(Provisioned) or the Protection path (Rerouted). For more
information, see parameter in Trails Pane Columns.
Restoration Reflects whether and on which path types restoration is allowed
Allowed to be performed:
| Both or Main or Prot: Indicates that restoration is allowed
for both paths or only the specified path type.
| Inhibited: Indicates that restoration is not allowed for any
path.
Reversion Reflects whether and on which path types reversion is allowed
Allowed to be performed:
| Both or Main or Prot: Indicates that reversion is allowed
for both paths or only the specified path type.
| Inhibited: Indicates that reversion is not allowed for any
path.
The Total statistic at the bottom of the list shows the number of records filtered
into the view out of the total number of records that can be displayed.

Filtering ASON Maintenance Operation

Data
You can filter the trail records listed in the ASON Maintenance Operations
window.
To filter trails in the ASON Maintenance Operations window:

1. In the ASON Maintenance Operations window, click the Filter icon. The
Filter dialog box opens.
2. Select the options by which you want to filter the list.

3. Click OK. The ASON Maintenance Operations window is filtered
according to your selections. Click Default to reset the selections to the
system defaults.
ASON Maintenance Operations Filter dialog box menu options
Option Description
Resource Filter
Layer Topology layer containing the required network objects.
Tree Shows the network objects for the selected trails and their
respective slots, cards, and ports in a hierarchical structure.
Allows you to filter the specific branches in elements for
which trails should be listed. Only selected resources are
filtered.
Operation
Allow Restoration Main Filters in the ASON Maintenance Operations window
Allow Restoration Prot only trails in which the selected statuses are present. For
Allow Reversion Main more information, see ASON Maintenance Operations.
Allow Reversion Prot

Viewing NE Timing Sources

The timing sources for each NE are configured via the respective EMS.
Timing Map Window

The Timing Map window enables you to conveniently monitor the network's
timing topology. A color-coding scheme allows you to view a wide range of
network timing information. For purposes of Timing Map representation, if an
NE is represented by multiple LEs, the LEs behave in the same way as
described for NEs.
OPTIONAL FEATURE: The Timing Map functionality

is a fully integrated add-on capability, available on a cost
basis; if not purchased, the feature and the related menu
options are unavailable.
The Timing Map window displays two representations of timing sources:

| Timing for SDH - Active view (accessed by selecting Map > Active
Map), shows the timing sources that are in use.
| Timing for SDH - Configure / First Priority view (accessed by selecting
Map > Configured Map), shows the timing sources configured in the
EMS.

The views display the following attributes:

| Quality of a timing source: indicated by the color of the link flowing
from a timing source NE (also color coded) to another NE. Quality – color
code correspondences are shown in the Legend on the status bar. Available
qualities are defined by the SDH protocol:
NA Invalid, cannot be selected for a timing source.
PRC Primary Reference Clock (10-11), such as an atomic clock.
SSUT Synchronization Source Unit - Transit (5 x 10-9).
SSUL Synchronization Source Unit - Local (10-7).
SEC SDH Equipment Clock (4.6 x 10-6). The NE Internal clock is
defined to be of SEC quality.
DNU Do Not Use. Cannot be selected for a timing source.
SSM Synchronization Status Message (relevant to the Configure view
only).
Ext/Int/Trib External, internal, or tributary timing source.
Line/NA Line source or not applicable.
Other Other.
Not all qualities apply to each equipment type; consult the relevant EMS
user manual for more information.
The colors corresponding to each quality are configurable via the Timing
Preferences dialog box. For details, see Modifying Timing Display
Preferences.
| Timing directionality: indicated by arrows at the edge of a link. For
example, on a link between NE-1 and NE-2, an arrow pointing to NE-2
denotes that NE-2 is receiving its timing from NE-1.
| Whether the active timing source is the originally configured one:
indicated by the color of an LE, as follows:
Red - active timing source not as configured, implying that a better
quality timing source was detected and implemented. The color of a
group will be red if any of its member MEs is red.
Green - active timing source same as configured. The color of a group
will be green if at least one member is green and none are red.
Dark Gray (SYNCOM elements only) - timing source for the element
configured as Line, passing through a specific port, and always taking
its timing from a certain trail.
Light Gray - only UMEs.
The system recognizes a view that has become out of date and displays
"Configure map has changed" or "Active map has changed" on the status bar in
any of the following cases:
| A configuration change is made to an element in the EMS.
| A different timing source becomes active.
| The quality of a timing source changes.

Accessing Timing Source Information

This section describes how to view active or configured timing source
information.
To view timing source information:

1. Select the SDH topology view from the LightSoft main window Topology
Layer dropdown list.
2. For ease of work and improved system performance, you may want to open
the Timing Map window with only selected NEs of the view and the links
running between them, rather than showing all the objects in the current
view. To do this, select the LEs in the main window view map.
3. On the main menu bar, select Tools > Timing.
OR
On the toolbar, click the Timing Map icon . The Timing for SDH -
Active view window opens. It shows a current view of the timing sources
in use according to the Legend at the bottom of the window.
4. Select Map > Configured to display the Timing Map - Configure/First
Priority view, showing the timing sources as configured in the EMS.
OR
Select Map > Active to redisplay the Timing for SDH - Active view.
5. If the map shows "Configure map has changed" or "Active map has
changed", select Map > Refresh Map to refresh the view. The Last Update
time stamp at the bottom right corner of the window shows the date/time of
the last refresh.
Timing Map menu options
option
Map
Active Map Shows the timing sources in use.
Configured Shows the timing sources as configured in the EMS.
Map
Preferences Enables you to change the color coding on links (denoting timing
source qualities) in the open view; see Modifying Timing Display
Preferences.
Close Closes the Timing Map window.

option
View
Refresh Refreshes the Timing Map window views to show the most
current timing source information. The Last Update field at the
bottom left corner of the window shows the date/time of the last
refresh.
The Timing Map window must be refreshed per view. For
example, if you refreshed the Active view, you must refresh the
window to obtain updated Configured information.
Both views are automatically refreshed when the Timing Map
window is first opened, or when new preferences are applied.
Legend Shows or hides the status bar legend and Last Updated time
stamp.
Help
Viewing Timing Data in CSV Format

You can access a file containing the current Timing Map information in CSV
format for convenient import to Microsoft Excel or a relational database. Each
time the timing map is updated (opened or refreshed) the file is overwritten
with basic timing data for all the objects currently in the map. The file is stored
in:
/tmp/NMSTiming.csv
When the map is opened with selected objects, only the timing map data for
those objects is saved in the file.
Timing Map CSV data fields
Field Description
NE Name Name of an NE in the timing map.
Timing The timing information. For Syncom NEs, this is presented in
two rows in the table, for East and West directions,
respectively.
Active Qual Quality of the timing source as represented in the Active
view.
Active Source Nature of the timing source (External, Internal, Line, or
Tributary) as represented in the Active view.
Configured Qual Quality of the timing source as represented in the
Configured/First priority view.
Configured Source Nature of the timing source (External, Internal, Line, or
Tributary) as represented in the Configured/First priority
view.

Modifying Timing Display Preferences

The Timing Preferences dialog box enables you to change the color of the
timing source quality information in the Timing Map window view.
A different color coding scheme can be applied to the Timing Map - Active
view vs. the Timing Map - Configure / First Priority view. (The latter contains
SSM quality, which is not present in the Timing Map - Active view.)
To change the timing source quality color coding:

1. In the Timing Map menu, select Map > Preferences or the Preferences
icon . The Timing Preferences dialog box opens.
2. Change the color associated with a timing quality by customizing its color
swatch . For information about standard color customization, see
OR
Revert to the default colors by clicking Defaults. This changes the colors in
the Timing Preferences dialog box to the system default values.
3. Click Apply to save the changes to the database; a confirmation message
appears and the Timing Preferences dialog box closes. The selected view
of the Timing Map window is automatically refreshed reflecting the new
preferences. The legend on the status bar indicates the color
correspondence for each quality. The changes remain in effect for your user
profile until you change them.
OR
Click Cancel to close the dialog box without saving changes.

18
Security
In this chapter:
Overview ....................................................................................................... 18-1
Security Concepts .......................................................................................... 18-3
Workflow for the Security Structure ............................................................. 18-9
Security Configuration Dialog Box ............................................................. 18-10
Managing Resource Domains ...................................................................... 18-14
Managing Profiles........................................................................................ 18-22
Managing Network Operators ..................................................................... 18-31
Managing User Groups ................................................................................ 18-36
Managing User Accounts ............................................................................ 18-42
Customizing Security Preferences ............................................................... 18-47
Changing Your Password ............................................................................ 18-50
Viewing Active Users .................................................................................. 18-51
Forcing a User Logout ................................................................................. 18-52
Activity and Security Logs .......................................................................... 18-54
Overview
In today's networks, user security is of extreme importance to network
administrators and operators. LightSoft supports a rich set of security (user
management) features, including:
| User capability profiles defined to a high level of granularity.
| Resource domains defined to a high level of granularity (down to the CTP
level).
| User groups.
| Sophisticated multiconfigurator feature.
| Password reuse management.
| Activity and security logs.
| Extended Virtual Private Network (VPN) capabilities.

Security LightSoft User Manual
| Customer Network Management (CNM).

| Resource profiles.
LightSoft supports two main types of security functions:
| User security.
| System security.
LightSoft security features restrict users in two ways:
| What they can do (capability profiles).
| Where they can do it (resource domains).
User security controls the users that have access to the system (user groups),
the operations they can perform (capability profiles), and the elements of the
network on which these operations can be performed (resource domains).
NOTE: When a user performs GCT, security levels and

capabilities that apply at the EMS level may differ from
LightSoft-assigned levels. For more information, see
LightSoft Aspects of SR9700 MEs.
All users are assigned to user groups, each of which is then paired with a
capability profile and a defined number of domains. Users in a particular group
can perform only the functions stipulated in their capability profile, and only on
those domains assigned to the group.
Furthermore, LightSoft enables partitioning a network into many different
VPNs (either sharable or exclusive), each with its own capability profile.
Changing the security configuration of logged-in users (including your own
configuration) is not allowed. This includes:
| Changing a user's user group, or the profile of a user group.
| Adding or removing domains to/from a user group or network operator.
| Editing resource domains or profiles.
You can force log out a user. For more information, see Forcing a User Logout.

LightSoft User Manual Security
Security Concepts
The following sections provide some key security concepts. Other concepts are
| VPNs and CNMs
| Security Building Blocks
| Provisioning Mode
| CNM Restrictions
VPNs and CNMs

LightSoft's comprehensive VPN capabilities enable multi-regional SP operators
to have one centralized network management system, but with autonomous
VPNs (for example, regional administrations) managing their assigned
resources. The SP operator can limit a region to specific capabilities/operations
on their allocated resources in the network, allowing a region to safely manage
its own equipment. The region's resources are "shareable" by the SP and every
other regional VPN, each one able to routinely use the VPN resources. The
pathfinder considers all network resources as trail path possibilities.
LightSoft's extended VPN capability, Customer Network Management (CNM),
additionally enables the overall owner of the network (SP operator), a carrier of
carriers, to lease out portions of the network to its own VPN service provider
customers (CNM operators). The SP assigns capabilities and specific resources
to the CNM operator. CNM operators manage their own network resources on
an exclusive basis, which means:
| An exclusive resource domain assigned to the CNM operator cannot be
assigned to another CNM operator.
| Server trail creation by CNM users is limited unless the exclusive resources
comprise at least entire ports. Otherwise, CNM users can provision only
client trails, on server trails provided by the SP operator. (Trail
provisioning comprises operations defined by the capability Trail
Provisioning - Create, edit, delete SDH and optical trails.)
| PF is prevented from automatically constructing a path that uses another
CNM's resources.
Exclusivity pertains to SDH and optical trail operations only. Exclusivity
does not apply to data trails, tunnels and services.
CNM configuration involves setting up Network Operators and Resource
Domains of type "Exclusive", rather than "Shareable" for regular VPNs. When
resource domains are being assigned to a network operator, LightSoft lets you
select only resource domains of the appropriate type.

When an exclusive resource domain is created and resources assigned to it,

those resources are considered reserved and "resource reservation" applies:
| Reserved resources are unavailable for any use until the exclusive resource
domain is assigned to an exclusive network operator.
| Once the resource domain is assigned to an exclusive network operator, the
reserved resources are available for that operator's exclusive use.
| SP users may intervene in an CNM system if needed, temporarily
suspending the exclusivity of a resource domain assigned to an exclusive
operator. This is useful to enable assistance in trail provisioning , or to
allow the pathfinder to relate to a wider scope of resources; see
Provisioning Mode.
The CNM feature provides an infrastructure that meets the needs of both SP
and CNM users. For example, CNM users have access to an SDH Server Trail
topology layer, which provides a graphically convenient view of the high order
VC-4 server trail topology as virtual links consistent with CNM resource
permissions; see SDH Server Layer in Supported Topology Layers. This
facilitates trail creation by CNM users; see CNM and Trail Provisioning.
OPTIONAL FEATURE: CNM is a fully integrated add-

on capability, available on a cost basis. If not purchased, the
associated features will be disabled.

Security Building Blocks

The LightSoft security structure comprises the following building blocks:
| Network operators define the network segments (subnetworks) where user
group members (users) can operate. There may be of two types:
Shareable: VPN operators that can share resource domains. They are
typically administrative regions but possibly representing some other
network subdivision.
One sharable network operator is the Service Provider (SP) owner of
the network, with super-user capabilities and overriding access to
network resources, as described further below.
Exclusive: CNM operators that lease resources from the SP.
| Resource domains (one or more) assigned to each network operator,
dividing the system's resources containing combinations of network
resources (CTPs, ports, MEs, UMEs, and EMSs), into as many
combinations as required, each sufficiently granular to be assigned to
individual user groups according to their responsibilities. User group
members (users) are authorized to work with a selection of the network
operator's resource domains. Resource domains may be of two types:
Shareable resource domain: Including resources that may be assigned
to any number of sharable network operators.
One sharable resource domain, the AllResourceDomain, includes all
network resources. It is assigned by default to the SP network operator,
but may be assigned to any sharable network operator, for associated
user groups requiring to act on any shared resource in the network.
Exclusive resource domain: Including resources that may be assigned
to only one exclusive network operator at a time.
A resource can exist in two types of resource domain at the same time - a
shareable resource domain (to belong to a region) and an exclusive resource
domain (for use by a CNM) . But it can be assigned to only one resource
domain of a type at a time (belong to only one region and CNM operator).

| Profiles define combinations of capabilities that can be performed by users

in a user group on applicable resources (for example, configuring security
or provisioning trails). Profiles may be of two types:
General profile: Assigned to a user group as a whole, applying to all
assigned resources not governed by Resource Only profiles.
One general profile is the SP profile, assigned by default to the SP
network operator. This profile permits an SP network operator user to
temporarily override CNM resource exclusivity; see Provisioning Mode.
Resource Only profile: Assigned to a specific resource domain within
a user group, overriding the General profile for the user group. (Since
multiple resource domains can be assigned to a user group, multiple
resource profiles can also be assigned, one for each assigned resource
domain.)
| User groups whose members will share common permissions are defined
within each network operator. Each user group is assigned:
A general profile with specific capabilities (for example, configuring
security or provisioning trails) that group members can perform.
A subset of the network operator's resource domains, thereby limiting
the resources on which member users can act. A Resource Only
profile may be attached to specific resource domains, overriding the
general profile if needed.
| Users are given permission to perform functions on resources by being part
of a particular user group in a selected network operator jurisdiction.
The multiconfigurator feature enables users from the same or different network
operators and user groups to work simultaneously on the same network
resources.

Provisioning Mode
Exclusive resource domains can be created that would reserve specific
resources for CNM operators, enabling them to provision trails using their own
network resources on an exclusive basis, with implications also for trail
pathfinding; see VPNs and CNMs. The SP operator may intervene in the CNM
system if needed, for example, to facilitate CNM requests for SP assistance in
creating trails or troubleshooting. SP server trail creation sometimes requires
PF reference to CNM resources.
The provisioning mode is by default None, meaning resource domains are
under exclusive CNM management. An SP user can override the Exclusive
provisioning mode, enabling the use of resources from all or specific exclusive
resource domains for trail provisioning.
| None (default): Reverts back to exclusive CNM management.
| All: Enables SP users to perform trail operations involving all resource
domains in the network.
| Specific network operator selection: Enables SP users to perform trail
operations involving a selected exclusive network operator's resources.
This would avoid the PF constructing a path which traverses another
CNM's resources.
After the required task is completed, the SP user can revert to Exclusive CNM
management by changing the provisioning mode back to None. Reversion to
None is automatic after logout.
The Provisioning mode exclusivity suspension applies to only one operator at a
time. If the provisioning mode window is used to select another operator,
LightSoft automatically reinstates the first operator's exclusive CNM
management.
To adjust the Exclusive trail provisioning mode:

1. From the Traffic menu, select Trails > Use Exclusive Resources. The
Provisioning Mode dialog box opens.
2. Select the required radio button option - None, All, or a specific resource
domain selection.
3. Click OK to implement the new provisioning mode.

CNM Restrictions
Trail or tunnel synchronization are not available for CNM users.
SP can provision trails over CNM resources only in according to the
provisioning mode; see Provisioning Mode.
Shareable operator cannot provision over resources assigned to an Exclusive
operator.
A resource may belong to at most one domain of the same type - shareable or
exclusive:
| Only one Shareable domain (i.e. only in North, not also in Central).
| In only one Exclusive domain (i.e. only in one IPS).
However, sharable and exclusive domains can overlap. For example, the SP
may have sharable domains for administrative regional needs - North, Center,
South. The SP may also lease out part of the network to an ISP, creating an
exclusive domain that includes selected resources from one/more regions (e.g.
North and Center). The resources assigned to the ISP remain under their
former regional administration.
VPN functionality applies to CNM users in the same way as shareable users.
The VPN or CNM users see only their own resources and related alarms, and
perform trail management only using those resources.

Workflow for the Security

Structure
The following is a recommended workflow, building the security objects in the
order required for assignment to other objects (for more details see Security
Building Blocks, and specific sections cited below):
1. Build resource domains; see Adding New Resource Domains.
2. Build profiles; see Adding New Profiles.
3. Define Network operators that manage subnetworks - Shared (typically
geographic regions) and Exclusive (specific CNM operators) where group
members can operate. Each network operator is assigned one or more
resource domains. For details, see Adding Network Operators.
4. Define user groups whose members will share common permissions. Each
user group is defined with a network operator, a profile, and a subset of
the network operator's resource domains. For details, see Adding New
User Groups.
5. Define users. Each user is assigned a network operator and a user group.
For details, see Adding New User Accounts.
Rich defaults are provided. For most VPN applications, only user group and
user definition are required.
The appropriate combination of capabilities (View User Security AND
Security Configuration) is needed to perform actions on security objects. For
more information about the profile combination required for different security
actions, see Managing Profiles.

Security Configuration Dialog

Box
All LightSoft security functions are performed in the Security Configuration
dialog box.
NOTES:
Panes can be maximized or minimized by clicking the
triangle icons on the panel borders.
By default, list windows open with a basic set of columns.
You can optionally include additional columns to the
windows and auto-fit the column widths to their text; see
Showing, Hiding, and Auto-Fitting Columns. For
additional operations on columns, see Resizing List
Columns, Sorting List Lines, and Moving Columns in
Tables.

To access the Security Configuration dialog box:

1. On the LightSoft main menu, select Security > Security Configuration.
The Security Configuration dialog box opens with the Users tab
displayed.
2. The Details icon or button appear next to object cells or dropdown
lists. Click them to open a Details dialog box with information about a
selected security object. For more information, see Viewing Security
Configuration Object Details.
3. If you want to print the main table of a selected tab, click Print. The button
is disabled when the tab does not have a printable table.
4. To close the dialog box, click Close.
Security Configuration dialog box tabs
Tab Description
Users Manages user account information; see Managing User Accounts.
User Groups Manages groups to which users can be assigned to share common
permissions; see Managing User Groups.
Network Operators Manages the subnetworks to which user groups may be assigned;
see Managing Network Operators.
Resource Domains Manages sets of resources on which user group members can
perform functions; see Managing Resource Domains.
Profiles Manages sets of capabilities that user group members can
perform; see Managing Profiles.
Preferences Manages system configurations and defaults for security
management; see Customizing Security Preferences.

Viewing Security Configuration Object

Details
A Details dialog box enables you to view information about selected security
objects.
To access a Details dialog box:

| Click a Details icon or button in a Security Configuration dialog
box tab, or in an Add or Edit dialog box. The corresponding Details dialog
box opens.
Descriptions of the information fields in Details dialog boxes appear later in

this section.
The Edit button (if editing is allowed) enables you to edit an object.
The Used By button appears in Resource Domain or Profile Details dialog
boxes. When selected, it shows which user groups or network operators are
using the objects. For more information, see Viewing Used by Information.

Viewing Used by Information

Resource domains and profiles can be used within the definition of any number
of user groups or network operators. The Profiles and Resource Domains tabs
and corresponding Detail dialog boxes have a Used By button that opens a list
of user groups and network operators using the selected profile/resource
domain.
NOTE: A resource domain or profile that is used by a user

group or network operator cannot be deleted.
To access Used by information:

| In the Profiles or Resource Domains tabs, or in a Details dialog box, select
a profile or resource domain and click Used By. The Used By dialog box
appears.
Profile and Resource Domain Used By dialog box columns
Column Description
User Group User group that uses the profile or resource domain.
Network Operator Network operator to which the user group belongs.
Resource Profile Profile assigned to the user group (in the Resource
Domain Used By dialog box only).

Managing Resource Domains

Resource domains enable you to partition the network and restrict user actions
and visibility to resources that are allowed to the user group. If granular user-
defined resource domains are not required, you can assign the default
AllResourcesDomain to the user groups, allowing all members to work on any
resources in the network.
NOTE: A specific resource may be assigned to only one

resource domain. The same resource domain may be assigned
to multiple network operators and user groups, each having a
different profile (different capabilities).
The following types of network resources can be assigned to a resource

domain:
| CTPs
| Ports (physical termination points or PTPs)
| MEs
| UMEs
| EMSs
OPTIONAL FEATURE: The ability to define resource

domains down to the port level is a fully integrated add-on
capability, available on a cost basis. If not purchased, only
NE-level granularity is supported.
Resource assignment and LightSoft layers

A single port may exist in several topology views:
| In the physical view, it is contained within an ME.
| In the OTN, Ethernet, and SDH layers, it is contained within an LE.
When a port is assigned to a resource domain, the port and its parent objects are
visible in all the layers where they exist. Moreover, assigning an ME to a
domain gives access to its LEs and to the groups that contain the ME.

Resource visibility
The resource domain assigned to a user group determines the objects and
resources that can be viewed. This includes the resources shown in the
Resource Tree, the alarms in the Current Alarms list, the TCAs in the TCA list,
and trails in the Topology Views and Trails list. The following rules control
what a user can view:
| A user that has access to at least one resource within an object (for
example, a site group) can view the parent object.
| A user that has access to a port has access to all Connection Termination
Points (CTPs) contained within that port.
| Trails and links are visible only if all endpoints are in the user’s assigned
resource domain.
| A user can perform operations only on resources that are part of the user-
assigned resource domains, for example:
A user cannot delete or edit a trail if some resources are not assigned to
him, even if both endpoints are.
Display of card alarms is limited to users that have at least one PTP in
the alarmed card.
Service alarms are shown on subnetwork connections only if the latter
participate in a trail whose endpoints are in the user’s resource domain.
| A user can view detailed trail and link information if their endpoints are in
the user’s assigned domains. However, a user can determine which trail or
link is using a resource if the resource is within the user's domain, even if
the trail/link is not managed by the user (such as when some of the
trail/link resources are outside the user’s domain). For example, if a PTP is
connected to a link whose other endpoint is not in the user’s domain, the
user cannot see the name of the link that uses the PTP.
Creating and deleting resources

LightSoft enables you to dynamically create and delete resources. Typically,
LightSoft receives these operations as a notification from an EMS.
When an object is created or deleted, LightSoft receives an Object Creation
Notification (OCN) or an Object Deletion Notification (ODN) and logs it in the
Event Log. This provides an audit trail enabling users with the proper
capability to identify new objects and assign them to resource domains.
Any new resource (for example, a port) added to the system is automatically
added to the default domain AllResourcesDomain. When a new resource is
added to an ME, UME, or EMS that already belongs to a resource domain, the
new resource is automatically assigned to the same resource domain.
When a resource is removed from LightSoft, it is removed from all resource
domains. If a resource is in use (for example, by a trail or link), it may not be
removed. Therefore, an EMS ODN notification will not always result in the
removal of an object from the system. An object is removed from the resource
domains only when LightSoft completely deletes it.

Resource Domains Tab

Resource domains are managed in the Resource Domains tab of the Security
Configuration dialog box.
The upper area of the tab lists all resource domains. Click a resource domain to
view all resources assigned to the domain (or unassigned nodes, which are
parents of assigned resources) in the Resource Domain Details area. Resources
are shown by topology layer in a tree format.
After you select a layer, the tree shows all the resources in that layer that are
assigned to the resource domain:
| Fully colored nodes denote that the node resource and all its subresources
are assigned to the resource domain.
| Shaded nodes denote that the node resource is not assigned to the resource
domain, but that some or all of its subresources are assigned. Drill down to
see specific assigned nodes - they are fully colored.
| Nodes that have no resources assigned to the current resource domain are
not shown in the tree at all.
NOTE: The Used By button lists the user groups and

network operators that are using the selected resource
domain. For details, see Viewing Used by Information.

Information shown for each resource domain
Component Description
Column
Name Resource domain name.
Description Free-text description of the resource domain.
Resource Domain SP: Assigned by default to the AllResourceDomain (global
Type domain with all possible resources)
Shareable: Reusable, assignable to any number of sharable
network operators.
Exclusive: Assignable to only one exclusive network operator
at a time.
Resource Domain Details
Layer Layer for which resource domain information is required.
Resource Tree A hierarchical tree that shows the network's MEs, UMEs,
EMSs, and PTPs assigned to the selected resource domain and
their parents. Elements can be expanded or collapsed by
clicking “+” or “-”.
Built-In Resource Domain

There is one built-in resource domain, the default AllResourcesDomain. It
includes all LightSoft resources that may be assigned to a domain. This domain
cannot be edited or deleted and is used when there is no need to subdivide
network resources into different resource domains.

Adding New Resource Domains

The Add button is enabled only when AllResourcesDomain is selected. (A new
domain must be a subdomain of an existing domain and only the
AllResourcesDomain allows this.)
Specific resources can exist in both a shareable resource domain (to belong to a
region) and an exclusive resource domain (for use by a CNM) at the same time.
Specific resources can be assigned to only one resource domain of a type at a
time (belong to only one region and one CNM operator).
Only PTPs, MEs, UMEs, or EMSs can be assigned to a domain. In that
process, you can select any object in the tree, including LEs, groups, or slots.
However, only the ports, MEs, UMEs, or EMSs within the selected object's
hierarchy become assigned.
When an ME, UME, or EMS is added to a resource domain, all its assignable
resources are also assigned. If your profile permits, you can edit both the parent
resource and its subresources. When an ME, UME, or EMS is assigned, all
future subresources are automatically added to the same resource domain.
However, if only the subresources (some or all) of an ME, UME, or EMS are
assigned to a domain, the parent resource itself is not assigned but it is visible.
Future subresources of the ME, UME, or EMS are not automatically added
(they must be added manually). In this case, edit permissions apply only to the
subresources. View permissions apply to the parent resource.
NOTES:
LEs or groups cannot be assigned to a domain (only their
child objects can). You can assign child objects of an LE
or group to a resource domain by moving the LE/group to
the Selected Resource pane. This shortcut avoids having
to select each child object individually. The LE/group is
not itself assigned to the resource domain and is shaded in
the Resource Tree view.
The ME, UME, and EMS resource node can only be
added from a physical layer. If an LE in a technology
layer is added to a resource domain (to assign all its child
resources), the corresponding parent resource in the
physical layer (ME, UME, or EMS) remains unassigned.

To create a new resource domain:

1. In the Security Configuration dialog box, select the Resource Domains
tab. (Select AllResourcesDomain so that the Add button is enabled.)
2. Click Add. The Add Resource Domain dialog box opens.
3. Enter the Name and Description in the relevant fields.

4. Select the Resource Domain Type: Shareable or Exclusive.
5. In the Resource Allocation area:
a. Select the topology layer from whose resources you want to create the
domain. The elements in the layer are displayed in the Available
Resources pane in a tree structure with the following colors:
Fully colored when the node and its resources are available for
assignment. LEs, groups, and slots are also fully colored if their
subresources are all available. However, the LEs, groups, or slots
themselves are not assignable.
Fully colored nodes with an icon when at least one subresource
in the node is not available. The parent resource is unavailable if
any of its subresources is unavailable, or if the parent node is an LE
or group. You can drill down to see which specific resources in the
parent node are available. They will be fully colored.
Shaded subnodes amongst colored subnodes denote that the
associated subresources are already assigned to other resource
domains.
Shaded nodes denote that the parent resource and its subresources
are not available.

b. In the Available Resources pane:

Select the resources that will be part of the resource domain
(expand the nodes and use the Ctrl or Shift keys to choose multiple
elements).
Click to move the selected resources to the Selected
Resource Domains side. Click to reverse the process. Click
to unselect all the resources at once.
6. Click Save to create the resource domain. The new resource domain is
added to the Resource Domains list.
Add Resource Domain dialog box components
Name Name of the resource domain. The name must be unique within
the network operator to which the resource domain is assigned.
Resource Domain Select Shareable or Exclusive.
Type
Description Free-text description of the resource domain.
Resource Allocation
Layer Topology layer whose elements are used to create the new
resource domain.
Available Resources All resources (available and unavailable) in the selected
topology layer in a tree structure.
Selected Resources Resources assigned to the resource domain. For purposes of
clarity, LightSoft displays the parent structure associated with
assigned resources. Unassigned objects in the structure are
shaded. Branches with no selected objects are omitted.

Editing Resource Domains

All resource domains can be edited except for the default AllResourceDomain
and resource domains of your own user group under a second-level network
operator. These can only be edited by the SP network operator.
You cannot edit resource domains of a logged-in user (including your own).
To edit an existing resource domain:

tab.
2. Select the resource domain you want to edit and click Edit. The Edit
Resource Domain dialog box opens. For details, see Adding New
Resource Domains.
3. Change the information as needed.
4. Click Save to save the changes.
Deleting Resource Domains

You can delete a resource domain (except the default AllResourcesDomain)
unless it is assigned to a user group or network operator. You must first remove
it from both. If the resource domain you want to delete is still assigned, an error
message appears.
To delete resource domains:

tab.
2. Select the resource domains you want to delete and click Delete. (Use Shift
or Ctrl keys to select multiple resource domains.)
3. A confirmation dialog box opens. Click Yes. The resource domains are
deleted from the list.
If the deletion of any selected resource domains failed, a result dialog box
opens specifying the reason for each failure.

Managing Profiles
A profile is a set of capabilities assigned to a user group to define the functions
that group members are allowed to perform on resources in resource domains
assigned to the user group. There are two kinds of profile:
| General profile: Applies by default to resources of resource domains
assigned to the user group, where specific resource profiles do not apply.
| Resource Only profile: Applies to resources of specific resource domains
assigned to the user group, overriding the general profile. (Since multiple
resource domains can be assigned to a user group, multiple resource
profiles can also be assigned, one for each assigned resource domain.)
A capability is a distinct group of operations that a user can perform in
LightSoft. The following capabilities are applicable to security objects:
| View User Security: Opens the Security Configuration dialog box.
| Security Configuration: Enables you to add, edit, save, or delete security
objects (View User Security must also be selected).
| Security Extended Admin: Enables you to access all resource domains of
all network operators and all profiles in the entire network, only for
assignment to a new user group (View User Security and Security
Configuration must also be selected).
The resource domains that can or must be assigned to a user group depend on
the profiles of the assigning user and of the user group being added/edited:
| Users generally see only the resource domains of their own user group in
the Resource Domains tab and Add User Group dialog box. Users with
Security Extended Admin capability see all the domains of their own
network operator.
| When adding or editing a user group, if a Security Extended Admin user
selects a network operator other than its own for the user group, the list of
available resource domains is that of the selected network operator
(regardless of whether the user group being created/edited has Security
Extended Admin capability).
| When a Security Extended Admin user adds a user group with Security
Extended Admin capability (or edits its profile to include that capability),
the group must be assigned all resource domains of the applicable network
operator. If not, an error message appears after clicking Save.
EMS Configuration and Trail Synchronization capabilities in profiles assigned
to user groups under second-level network operators will be inactive (the
capabilities grayed out in the Capability Tree). Users assigned these profiles
will not be able to perform the operations defined by those capabilities.

Profiles Tab
Profiles are managed in the Profiles tab of the Security Configuration dialog box.
The upper area of the tab lists all defined profiles.

The Profile Details area lists details of a selected profile. Click a profile to
view its capabilities, and then click a capability or a capability category to view
its description in the Capability Description pane.
NOTE: The Used By button lists the user groups that are
currently using the selected profile. For details, see Viewing
Used by Information.
Information shown for each profile

Column
Name Profile name. Unique within a network operator (under which the
profile can be assigned to several user groups).
Description Free-text description of the profile.
Profile Type General or Resource Only; see Managing Profiles.
Network Operator Service Provider or a second level CNM or VPN network operator.
Profile Details
Capability Tree A hierarchical tree that shows the capabilities assigned to the
selected profile. Capability nodes can be expanded or collapsed by
clicking “+” or “-”.
Capability When a capability or capability category in the tree is selected, its
Description description appears here.

Built-in Profiles
In addition to profiles that you can create, LightSoft provides built-in profiles
with capabilities for typical categories. Built-in profiles cannot be edited or
deleted. The Built-in user groups (see Built-in User Groups) are based on these
built-in profiles.
The following table shows the operations you can perform on built-in profiles
(when supported by the EMS), including GCT permissions to applicable EMS
windows. For more information, see Available capabilities.
Built-in profiles
Name Description
Admin Super user capabilities - can perform all operations (except

Northbound session).
Includes EMS Operations - EMS Admin capability.
Security Can configure security and basic LightSoft administration but
Administrator cannot perform network management.
Includes EMS Operations - EMS Admin capability.
Configuration Topology and trail management capabilities.
Includes EMS Operations - Configurator capability.
Provisioning Can perform trail management operations.
Includes EMS Operations - Provisioning capability.
Maintenance Read-only access to topology and trail management. Can perform
alarm acknowledgement, maintenance, and PM.
Includes EMS Operations - Maintenance capability.
Observer Read-only access to topology and trail management. Can
acknowledge alarms.
Includes EMS Operations - Observer capability.
Northbound Can accept an open or closed session for ENI/MTMN operations
Session from an upper layer NMS, for defining the session login and
password of an upper layer manager.
Level 1 Group Read-only access to topology and trail management. Can
acknowledge alarms and perform maintenance and PM operations.
Includes EMS Operations - Level 1 capability.
Level 2 Group Read-only access to topology and trail management. Can
acknowledge alarms and perform maintenance and PM operations.
Includes EMS Operations - Level 2 capability.
CNM_Admin Super user capabilities for CNM users.
CNM_Provisioning Provisioning capabilities for CNM users.
CNM_Monitoring Monitoring capabilities for CNM users.

Available Capabilities
This section describes the sets of capabilities that can be assigned to profiles
(when supported by the EMS).
Capabilities are designated as either Global (G) or Resource (Rsc):
| A Global (G) capability applies only in a general profile. For example, the
View Active Users capability allows the user to open the Active Users
window. A Global capability is not resource related.
| A Resource (Rsc) capability can be used:
In a resource profile, attached to specific network resources, For
example, Acknowledge Alarms can be applied to specific MEs or PTPs
on which an alarm is raised.
AND/OR
In a general profile, governing actions on specific resources where a
resource profile was not assigned.
If a Rsc capability is assigned to both the general profile and a resource
profile, the resource profile governs actions allowed on the associated
resources. For example, if the general profile includes Acknowledge
Alarms, but the applicable resource profile does not, then users will not be
able to acknowledge alarms on the indicated resources.
Both Rsc and G capabilities can be selected for a general profile, but only
Rsc capabilities are available for selection for a resource profile.
Capabilities are designated as either Log Y or N, according to whether
activities involving a capability recorded in the Activity log.
Available capabilities
Name Description Rsc/G Log

EMS Management
EMS Administration Upload, manage/unmanage an EMS and access to top Rsc Y
level EMS operations. (Applies to EMS objects.)
EMS Configuration Create and configure an EMS session. (Applies to EMS Rsc Y
objects. SP only.)
EMS Operations
Admin of EMS All operations. (Applies per EMS.) Rsc N
Configurator All configuration operations except EMS system tasks G N
such as shutdown (exit).
Provisioning Same as Configurator, but does not allow to create, edit, G N
or delete cross connects.
Maintenance Perform maintenance operations, alarm G N
acknowledgement, alarm severity and masking settings,
change object attributes, save PM log.
Observer View all windows. G N


Level_1 Category may be configured in the EMS. G N
Level_2 Category may be configured in the EMS. G N
None No EMS GCT allowed for this user. G N
Fault Management
Acknowledge Alarms Acknowledge alarms from Current Alarms and Event Rsc Y
Log windows.
Alarm Counters Configure alarm counters. G Y
Alarm and Log Filters Configure fault management filters. G N
Alarm Indications Configure alarm indications. G Y
Fault Management Alarm management feature administration (for example, G Y
Administration configuring the event log size, alarm export and SMS).
Manage User Notes Create, edit, delete user notes. G Y
View User Notes View existing user notes. G N
LightSoft Operations
LightSoft Configuration Several LightSoft configuration actions, including closing G Y
a client.
Northbound Session CORBA commands from an OSS. G Y
Miscellaneous
Export to XML Export of topology and security. G Y
Maintenance Operations - Perform maintenance operations. Rsc Y
Perform
Maintenance Operations - View maintenance operations. Rsc Y
View
Monitoring Operations
EMS Monitoring View EMS list and perform ping. G N
General Common monitoring commands. G N
Inter-user communication Send messages to other users. G N
PM History Allows access to PM history. G N
Trail Consistency View the Trail Consistency Indication flag and window. G N
Monitoring
Security Management
Activity Log View and manage the activity log. G N
Security Administration Configure and customize security. G Y
Security Extended Admin Allows a security administrator to assign capabilities to G
users and to create profiles using capabilities not currently
assigned to the administrator. For non-SP only resource
profiles can be extended beyond the administrator’s
assigned capabilities.
Security Log View and manage the security log. G N
View Active Users View a list of currently active users. G N


View User Security View the list of defined Users, Groups, Profiles, and G N
Resource Domains.
Topology Management
Attribute Editing - Allows updating Path Trace and other network affecting Rsc Y
Advanced attributes. (Not for CNM use.)
Change Topology Modify the network topology (create/delete topology G Y
elements).
Move Topology Object Move and save objects on the topology map. G N
Topology Objects Edit the attributes of topology objects. Rsc Y
Properties
Upload ME Force upload data from an ME. Rsc Y
Traffic Management
Advanced Trail All supplementary trail operations, such as editing a G Y
Operations server trail with clients.
Ethernet Service - Admin Create public templates, save global templates, create G Y
public profiles.
Ethernet Service - Create private templates, save/restore local templates, G Y
Provision load global template, create, edit, delete Ethernet Service
and Export to XML/CSV.
Ethernet Services - View View Ethernet service list and RSTP map. G N
Import XML Traffic File Import trails, tunnels and services from XML files. G Y
Traffic PM - Enable Enable/disable PM counters for trails, tunnels and Rsc Y
Counters services.
Traffic PM - Reset Reset PM counters for trails, tunnels and services. Rsc Y
Counters
Traffic PM - View View PM counters for trails, tunnels and services. Rsc N
Trail Synchronization Acquire network trails and impose LightSoft trails even G Y
when conflicts exist. (Not for CNM use.)
Trail Consistency Display the TCI in the main window. (Not for CNM use.) G N
Indicator
Trail Protection Switch - Perform protection switch commands on SNCP protection G Y
Perform trails.
Trail Protection Switch - View the Trail Protection Switch window. G Y
View
Trail Provisioning Create, edit, delete trails. G Y
Tunnel - Admin Allows performing tunnel automaton operations. G Y
Tunnel - Provision Create, edit, delete, and export tunnels. G Y
Tunnel - View Allows viewing tunnels. G N
View Management
View Application Maps View the Timing map and Availability map. G N


View Ethernet Layer View the Ethernet layer. G N
View OTN Layer View the OTN layer. G N
View Physical Layer View the physical layer. G N
View SDH Layer View the SDH layer. G N
Adding New Profiles

You can create profiles tailored to the specific needs of your users.
To add a profile:
1. In the Security Configuration dialog box, open the Profiles tab.
2. Click Add. The Add Profile dialog box opens.
3. Enter a Name, Profile Type, and Description (see the following table).

4. In the Capability Allocation area, Available Capability pane:

a. Select the capabilities for the profile (expand the nodes as required and
use the Ctrl or Shift keys to select multiple elements). A brief
description of the last selected capability appears in the Capability
Description area.
b. Click to move the selected capabilities to the Selected
Capability side. Click to reverse the process. Click to
unselect all capabilities.
The minimal EMS Operation Observer and General Monitoring capabilities
are preselected, and can be removed if required. For information about
available capabilities, see Available Capabilities.
5. Click Save to create the profile. The new profile is added to the Profiles
list.
Add Profile dialog box components
Name Profile name. The name must be unique within a network
operator (under which the profile can be assigned to several user
groups).
Profile Type General or Resource Only; see Managing Profiles.
Description Free-text description of the profile.
Capability Allocation
Available Capability Lists in a tree structure all available capabilities assignable to the
profile.
When a capability is selected, its description is shown in the
Capability Description area.
Selected Capability Lists the capabilities assigned to the profile.
When a capability is clicked, its description is shown in the
Capability Description area.

Editing Profiles
Any profile (except built-in profiles) can be edited. All fields are editable,
including the profile name.
Editing the profile associated with a logged-in user (including your own) is not
allowed.
To edit a profile:
2. Select the profile you want to edit and click Edit. The Edit Profile dialog
box opens with the same information as the Add Profile dialog box. For
details, see Adding New Profiles.
Deleting Profiles
Profiles (except built-in profiles) can be deleted when no longer needed.
NOTE: If a profile is assigned to a user group, it must first

be removed from the user group before it can be deleted. If
the profile you want to delete is still assigned, an error
message appears.
To delete profiles:
2. Select the profiles you want to delete and click Delete. (Use Shift or Ctrl
keys to select multiple profiles.)
3. A confirmation dialog box opens. Click Yes. The profiles are deleted from
the list.
If the deletion of any selected profile fails, a dialog box opens specifying the
reason for each failure.

Managing Network Operators

The system as a whole is managed by an overall network operator called
Service Provider (SP). User groups (and their users) are assigned to specific
network operators. In this way, the VPN defined by a user group is a subset of
the VPN defined by its network operator.
LightSoft extends the VPN capability of user groups by placing them in
subnetworks under second-level network operators according to your business
needs. The subnetworks can be defined as either Shared (typically regional
VPNs) or Exclusive (representing CNM operators); see VPNs and CNMs.
Network operators are assigned resource domains.
The SP is assigned the default AllResourcesDomain, which entitles its "super
user" group members to perform actions on any system resources (as defined
by the assigned profile).
Second-level network operators can be defined with any subset of the service
provider's resources, according to user requirements in each network operator's
jurisdiction.
Network operators enable resources to be assigned to user groups according to
their users responsibility.

Network Operators Tab

Network operators are managed in the Network Operators tab of the Security
The upper area of the tab lists all network operators. Click a network operator
to view specific details in the Network Operator Details area.
Information shown for each network operator
Column
Name Name of the network operator.
Description Free-text description of the subnetwork managed by the network
operator.
Network Type SP: Service provider owner of the overall network.
Shareable: Regular VPN operators, typically representing
regional subdivisions of the network.
Exclusive: CNM operators.
Owner The owner of all second-level network operators is the Service
Provider. (Future LightSoft versions will offer additional
nestings of network providers.)
Network Operator Details
Resource Domain Resource domains assigned to the selected network operator.
Resource Profile Not applicable - for future use.

Adding Network Operators

You can partition the network into subnetworks according to business needs by
creating network operators that work under the owner SP. Only resource
domains assigned to the network operator are assignable to user groups of the
network operator.
To add a new network operator:

1. In the Security Configuration dialog box, select the Network Operator
tab.
2. Click Add. The Add Network Operator dialog box opens.
3. Enter a Name, Network Type, and Description.

a. Select the resource domain (use the Ctrl or Shift keys to select multiple
domains). LightSoft lists only resource domains of the appropriate type
- Shared or Exclusive.
b. Click to move the selected domains to the Selected Resource
Domains side.
Click to reverse the process. Click to unselect all the
domains.
5. Click Save to create the network operator. The new network operator is
added to the Network Operators list.

Add Network Operator dialog box components
Name Name of the network operator, unique in the system.
Network Type Select Sharable or Exclusive; see VPNs and CNMs.
Description Free-text description of the network operator's subnetwork.
Resource Allocation
Available Resource domains that can be assigned to the network operator.
Resource LightSoft lists only resource domains of the appropriate type -
Domains Sharable or Exclusive.
Selected Resource Resource Domain: Resource domains (one or more) selected for
Domains the network operator.
Resource Profile: Not applicable - for future use.
Editing Network Operators

You can edit any network operator (except the SP network operator).
To edit a network operator:

1. In the Security Configuration dialog box, select the Network Operators
tab.
2. Select the network operator you want to edit and click Edit. The Edit
Network Operator dialog box opens displaying the same fields as the Add
Network Operator dialog box. For more information, see Adding Network
Operators.
4. Click Save to save the change.

Deleting Network Operators

Network operators (except SP) can be deleted when they are no longer needed.
NOTE: All user groups must be removed from a network

operator to be deleted. If user groups are still assigned to the
network operator you want to delete, a warning message
appears.
To delete network operators:

1. In the Security Configuration dialog box, open the Network Operators
tab.
2. Select the network operators you want to delete and click Delete. (Use Shift
or Ctrl keys to select multiple network operators.)
3. A confirmation dialog box opens. Click Yes. The network operators are
If the deletion of any selected network operator fails, a dialog box opens
specifying the reason for each failure.

Managing User Groups

User groups provide a way of effectively managing many users according to
the functions they perform in LightSoft. Groups can be created for every type
of user who can access only certain LightSoft functions and resources in
specific areas of the network.
A user group is assigned:
| A network operator that defines the subnetwork (typically a geographic
region) where group members may operate.
| Resource domains (one or more), which enumerate the sets of specific
network resources - individual ports (PTPs), MEs, UMEs, and EMSs - that
group members may operate on. The assigned resource domains are a
subset of those defined for the selected network operator.
| A profile that describes the specific functions or capabilities that group
members can perform (for example, creating trails). The profile applies to
all resource domains assigned to the user group.
The resource domains that can or must be assigned to a user group depend on
the profiles of the assigning user and of the user group being added/edited:
| Users generally see only the resource domains of their own user group in
the Add or Edit User Group dialog boxes. Users with Security Extended
Admin capability see all the domains of their own network operator. For
more information about capability issues, see Managing Profiles.
| When adding or editing a user group, if a Security Extended Admin user
selects a network operator other than their own for the user group, the list
of available resource domains is that of the selected network operator
(regardless of whether the user group being created/edited has Security
Extended Admin capabilities).
| When a user adds a user group with the Security Extended Admin
capability (or edits its profile to include that capability), the group must be
assigned all the resource domains of the applicable network operator.
Otherwise, an error message appears after clicking Save.
The number of simultaneous logins allowed to specific user groups can be
constrained; see User Group Login Limit.

User Groups Tab

User groups are managed in the User Groups tab of the Security
The upper area of the tab lists all user groups, including built-in ones. Built-in
user groups.
Click a user group to view information about that group in the User Group
Details area.
User group information
Column
Name User group's name.
Description Free-text description of the user group.
Profile General profile assigned to the user group, which determines
what functions group members can perform on resources in
assigned resource domains not governed by specific resource
profiles.
Network Operator Network operator (subnetwork) to which the user group is
assigned.
User Group Details fields
Users Users assigned to the user group.
Resource Domain Resource domains on which members of the group can operate.
Resource Profile Shows the applicable profile - either the General profile assigned
to the user group, which governs actions on all assigned
resources by default, or a specific Resource Only profile which
overrides the general profile for the indicated resource domain.

Built-in user groups

In addition to user groups that you can create, LightSoft provides built-in user
groups. These are set with the default resource domain AllResourcesDomain
and built-in profiles.
Built-in user groups cannot be edited or deleted. For details about the built-in
profiles associated with the available built-in user groups, see Built-in profiles.
Built-in user groups correspondence
Built-in user group name Associated built-in profile

Admin Group Admin
Security Administrator Group Security Administrator
Configuration Group Configuration
Provisioning Group Provisioning
Maintenance Group Maintenance
Observer Group Observer
Northbound Session Group Northbound Session
Level 1 Group Level 1
Level 2 Group Level 2

Adding New User Groups

You can create user groups according to the common resource and capability
permissions required for each user.
To add a new user group:

1. In the Security Configuration dialog box, open the User Groups tab.
2. Click Add. The Add User Group dialog box opens.
If the User Group

3. Enter a Name, Description, Network Operator, and General Profile.
4. If the User Group Login Limit option is enabled, a Concurrent Users field
will be available. Select the maximum number of simultaneous logins to be
allowed; see User Group Login Limit.
a. Select the resource domains (use the Ctrl or Shift keys to select
multiple domains).
b. Click to move them to the Selected Resource Domains side.
Click to move all the domains. Click or to
reverse the process.
NOTE: If the selected profile has Security Extended Admin

capability, the security operator can assign capabilities
beyond those of the user, but limited to resources allocated to
the network operator.

6. If a Resource Only profile is required for a selected resource domain (to

override the General profile for that specific domain), open the dropdown
list of available resource profiles and select one.
7. Click Save to create the new user group. The new group is added to the
User Groups list.
Add User Group dialog box components
Name Name of the user group. The name must be unique within its
network operator.
Description Free-text description of the user group.
Network Operator Network operator (subnetwork) to which the user group is
assigned. The dropdown list shows all network operators.
General Profile Profile representing the capabilities allowed to group members.
The dropdown list shows all existing profiles (built-in or added)
for user groups in the selected network operator. For example, if
the network operator is not an SP, the available profiles do not
contain EMS Configuration and Trail Synchronization.
Concurrent Users Number of simultaneous logins allowed to to this user group.
Present only when the User Group Login Limit option is
enabled. For details, see User Group Login Limit.
Indicates the Resource Allocation
Available Resource | Resource Domain: Available resource domains assignable to
Domains the user group.
| Resource Profile: General profile is initially shown.
Selected Resource | Resource Domain: Resource domains (one or more) selected
Domains for the user group.
| Resource Profile: General profile, or a selected Resource
Only profile attached to the specific resource domain; see
Adding New Profiles.

User Group Login Limit

A User Group Login Limit option may be enabled to limit the number of
simultaneous logins allowed to specific user groups. For details about enabling
this option, please consult ECI Customer Support.
When the option is enabled, the Add (and Edit) User Group dialog box
includes a Concurrent Users selector field.
The default value in the Add User Group dialog box is “1” for the Admin
profile or “0” for other profiles (that is, no users may log in). You must change
this to the desired number of users for each user group. The selector maximum
value is limited to the maximum users allowed (per the concurrent logins
allowed cost option) less the sum of concurrent users already allocated to other
user groups.
After the number of concurrent users is defined for a user group, users
attempting to log in who are in excess of the specified number will receive an
error message at login; see Logging In.
Editing Existing User Groups

You can edit any user group (except built-in user groups).
All fields are editable except the network operator selection. To change the
network operator, the user group record must be deleted and added again.
Editing the user group associated with a logged-in user (including your own) in
order to add resource domains or change its profile is not allowed.
To edit a user group:

1. In the Security Configurator dialog box, select the User Groups tab.
2. Select the group you want to edit and click Edit. The Edit User Group
dialog box opens displaying the same fields as the Add User Group dialog
box. For details, see Adding New User Groups.

Deleting User Groups

You can delete user groups (except built-in user groups) when they are no
longer needed.
NOTE: Before deletion, all users must be removed from the

user group. If users are still assigned as members of the group
you want to delete, a warning message appears.
To delete user groups:

1. In the Security Configuration dialog box, open the User Groups tab.
2. Select the groups you want to delete and click Delete. (Use Shift or Ctrl
keys to select multiple user groups.)
3. A confirmation dialog box opens. Click Yes. The selected user group is
If the deletion of any selected groups failed, a result dialog box opens
specifying the reason for each failure.
Managing User Accounts

When you log in to LightSoft, you enter your user name and password in the
Login dialog box, then click Login or press Enter. LightSoft opens with your
user account privileges. What you see in topology views (for example, the
Topology Tree and the Navigator), as well as in list windows, depends on your
user account permissions, the user group of which you are a member, and
resource limitations of the user group. You can only perform tasks and see
resources that are assigned to your user group.
Changes made to the LightSoft user account database (users added or deleted,
or changes to user information) and changes to passwords are automatically
downloaded to the supported EMS. If the EMS was disconnected when these
changes occurred, they are downloaded to the EMS when reconnecting. (Note
that, depending on the integration implementation, this may not be supported
for all types of managed EMSs.)
OPTIONAL FEATURE: The number of users with

configurator privileges that are allowed to log in to LightSoft
at any one time is an optional feature. Clients beyond the
number for which the configurator license is purchased will
not be able to log in.

Users Tab
User accounts are managed in the Users tab of the Security Configuration
dialog box.
The upper area of the tab lists all user accounts. Click an account to view
specific details in the User Details area.
Information shown for each user
Column
Name User name.
Full Name Full name of user.
User Group Group to which user is assigned.
Network Operator Network operator (subnetwork) to which the user's group is
assigned.
User Details
Password Expires At Expiration date of the user’s password.
Inactivity Timeout The system automatically locks a user out of the system after
(min) the indicated time period has expired.
Description Description of the user account.

Adding New User Accounts

To provide access to LightSoft, you create a user account for each new user.
To add a new user account:

1. In the Security Configuration dialog box, open the Users tab.
2. Click Add. The Add User dialog box opens.
3. Enter the user information.

4. If alarm notifications should be transmitted by SMS or email to this user,
click Configure SMS/Email. The Configure SMS/Email dialog box
opens, where you can enable this feature for the user, specify the cell phone
number and/or email address, and define filters for the alarms that should
be transmitted. For more information about this dialog box and the
SMS/email configuration process, see Alarm Export by SMS/Email
Configuration.
5. Click Save to create the user account. The new account is added to the
Users list.

Add User dialog box components
Name User’s name for logging in to LightSoft and accessing its
functions. User names must be unique in the system.
Network Operator Network operator (subnetwork) in which the user's user
group will be selected. The dropdown list shows all available
network operators.
User Group User group to which the user will be assigned. The dropdown
list shows all user groups under the selected network
operator.
Full Name Full name of the user.
Password User’s password. The password can include any characters. It
is subject to Strong Password Enforcement restrictions (if
applicable) and Minimum Password Length; see parameter
descriptions in Customizing Security Preferences.
Confirm Password Enter the password again, for verification purposes.
Password Expires At Date when the user’s password will expire. Format is
dd/mm/yyyy. The default password expiration date is
configured in the Preferences tab of the Security
Configuration dialog box. You can enter a different value
for individual users.
Description Free-text description of the user account.
Inactivity Timeout The system automatically locks a user out of the system after
(min) the indicated time has expired. When users are locked out,
they must log in again. The default is defined in the
Preferences tab of the Security Configuration dialog box.
For information, see Customizing Security Preferences.
You can specify one of two different timeouts for the current
user:
| Select the Unlimited radio button to deactivate the
timeout for the user. The user will never be locked out.
| Select the second radio button and enter up to 1000
minutes.
Configure SMS/Email Opens the Configure SMS/Email dialog box, where you can
enable transmission of alarm notifications to the user by SMS
or email, specify a cell phone number or email address for
that purpose, and define filters for the alarms that should be
transmitted. For more information about this dialog box and
the SMS/email configuration process, see Alarm Export by
SMS/Email Configuration.

Editing User Accounts

All user accounts can be edited. All fields are editable except for the Name. To
change a name, you have to delete the user record and add it again.
Changing the user group of a logged-in user (including your own user account)
is not allowed.
To edit a user account:

2. Select a user and click Edit. The Edit User dialog box opens displaying the
same fields as the Add User dialog box. For details, see Adding New User
Accounts.
Deleting User Accounts

User accounts (except Admin) can be deleted when the user is not logged in.
Logged-in users are listed in the Active Users window. For details, see
Viewing Active Users.
Bulletin Board items and all user-specific data like LightNotes are not deleted
with a user account.
To delete user accounts:

2. Select the users you want to delete and click Delete. (Use Shift or Ctrl keys
to select multiple users.)
3. A confirmation dialog box opens. Click Yes. The users are deleted from the
list.
If the deletion of any selected user fails, a dialog box opens specifying the
reason for each failure.

Customizing Security
Preferences
SP users can set system configurations and defaults for security management.
This customization is performed in the Preferences tab of the Security
NOTE: All selections in the Security Preferences tab apply

to all user accounts, including administrator accounts.
To set security preferences:

1. In the Security Configuration dialog box, open the Preferences tab.
2. Select your preferences (see the following table).
3. Click Apply (enabled after a change is made). The Security Configuration
dialog box is not closed and all selections take effect immediately. The
changes apply to new users vs. existing users, as described for each
preference.

Security Preferences tab options and button
Option Description
Minimum Password Length Shortest acceptable length (in characters) for an account
password. Changing this parameter does not affect
already defined passwords of existing users. It applies
upon a change of password.
Default Password Number of days after which user passwords expire and a
Expiration (days) new password must be chosen before the user is allowed
to log in.
The resulting default expiration date appears in the Add
User dialog box and can be changed for individual users
as required; see Adding New User Accounts. this
parameter does not affect already defined passwords of
existing users. It applies upon a change of password.
Password Reuse History Minimum number of times that a password must be
changed before an old password may be reused.
Max. Unsuccessful Login Number of consecutive invalid login attempts permitted
Attempts to any user before the account is locked. (The counter is
(1-5) reset after each successful login.) To re-enable the
possibility to log in, the password for the user may be set
by a user with Security Administration capabilities.
Alternatively, you can wait until the “Delay Until User
Re-enable” period expires.
Available options:
| From 1 to 5 – the user can make the selected number
of login attempts. If all attempts are unsuccessful, the
account is locked.
| Unlimited – allows a user to make an unlimited
number of login attempts and the account is never
locked.
Login Reactivation Time in minutes that must elapse until a user account is
(2-1440 minutes) automatically reactivated after being locked out because
of too many unsuccessful login attempts. Available
options:
| From 2 to 1440 – the user must wait the specified
number of minutes before attempting to log in again.
| Unlimited – the password is permanently
deactivated. In this case, an administrator must
assign the user a new password.

Option Description
Default Inactivity Timeout LightSoft automatically performs the action described in
(10-1000 minutes) Inactivity Timeout Action if no activity is detected at a
client station over the time period specified here.
Available options:
| Select the second radio button and enter up to 1000
minutes.
| Unlimited - deactivates the timeout. Users are never
automatically locked or logged out.
This field sets the Default Inactivity Timeout that
appears in the Add User dialog box, and can be changed
on a per-user basis. For details, see Adding New User
Accounts. Existing users are unaffected.
Inactivity Timeout Action LightSoft automatically either locks a user client session
or logs a user out of a client if no activity is detected at
the client station over the time period indicated by the
user's inactivity timeout.
| When the user client is locked, the user can unlock
the session by entering his login details; see
Locking/Unlocking the User Client. Another user
can also log in instead of the locked user, in effect
forcing logout; see Logging In at a Locked Client -
"Fast Login".
| When a user is logged out, all active processes that
he initiated are automatically aborted.
Available options:
| Lock (default); see Locking/Unlocking the User
Client.
| Logout; see Logging Out.
Strong Password Available options:

Enforcement Enabled means the password must:
| Include both letters and digits.
| Not be the user login ID or full name (or include
these with a prefix or suffix added).
| Not be three or more consecutive letters or numbers.
For example, 123afd, efgh9, abc456 are not valid.
| Not be three or more repeated characters. For
example, 1111a89a, qqq9, 888jjjj, q;;;1 are not valid.
Disabled means pattern checks are not performed.
Changing this parameter does not affect already defined
passwords of existing users. It applies upon a change of
password.

Changing Your Password

LightSoft enables you to change your password for security reasons or when it
expires.
Changes to passwords are automatically downloaded to the supported EMS.
(Depending on the integration implementation, this may not be supported for
all types of managed EMSs.)
NOTE: The password can include any characters. It is

subject to Strong Password Enforcement restrictions (if
applicable) and Minimum Password Length; see parameter
descriptions in Customizing Security Preferences.
To change your password:

1. On the LightSoft main menu bar, select Security > Change Password. The
Change Password dialog box opens.
2. Change your password and click Save to confirm.

Viewing Active Users

You can view a list of users currently logged in to LightSoft in the Active
Users window. The list includes logged-in users belonging to the current user's
network and its subnetworks. For example, a user belonging to the Service
Provider network operator will see all logged-in users since all other network
operators are subnetworks of the Service Provider. A user belonging to another
network operator will see only the logged-in users of that operator's network.
To access the Active Users window:

| On the LightSoft main menu bar, select Security > Active Users. The
Active Users window opens.
The Send Message button allows you to write and send a message to any
combination of the users currently shown in the Active Users window. For
more information, see Sending Messages to Logged-In Users.
The Force Logout button forces the selected user/s to log out of the system.
For more information, see Forcing a User Logout.
Fields and buttons in the Active Users window
Field Description
User User name of the user account
Network Operator Name of the applicable network operator
User Group Name of the applicable user group
Login Time Date/time when the user logged in to the system
Client Host Name of the host the user logged in to
Client Name Name of the client

Forcing a User Logout

An authorized user can force another user to log out from a client for system
administration purposes or to log in another user to that client. Only one user at
a time can be logged in at a specific client.
Security Administration capability is needed to perform force logout. The
target user is notified of the action and immediately logged out. Certain active
processes initiated by that user are aborted. For details of the active processes,
see the note in Logging Out. Another user can then log in at that client.
LightSoft may automatically log out a user following a period of inactivity at
the user client station. For details, see Customizing Security Preferences. The
applicable timeout period can be set on a per-user basis using the Default
Inactivity Timeout parameter. See "At the target user's terminal" below for the
sequence of windows at the target user upon an automatic logout.
When a user session is locked - see Locking/Unlocking the User Client -
another user can log in from the same client, in effect forcing logout of the
original user. For details, see Logging In at a Locked Client - "Fast Login".
NOTE: When a user session is logged out, all open

windows, including GCT operation windows, are closed.
While working for an extended period in an EMS via GCT,
LightSoft may sense inactivity and automatic logout from
LightSoft due to timeout. A popup message appears before
the timeout is triggered:
Clicking Continue will cancel the timeout. The notice time

before timeout is configurable with the assistance of ECI
Telecom customer support.
To force a user logout:

1. In the Active Users window (see Viewing Active Users), select the user
you want to force to log out.
2. Click Force Logout (enabled if the user performing the action has Security
Administration capability and is not the selected user).

At the authorized user's terminal:

3. A general warning appears.
4. Click Yes to proceed with the force logout. After the action is completed,
the following confirmation message appears:
5. Check the Active Users dialog box to verify that the user was logged out.
Another user can now log in to the client; see Logging In.
At the target user's terminal:

6. When force logout (or automatic logout after a period of inactivity) is
initiated, the following consecutive in-progress notices appear. The second
message appears if active processes are detected. The third message
informs the target user of the force logout.

7. Click OK to open the Login dialog box.
Activity and Security Logs

You can monitor user actions in LightSoft through the following logs:
| Activity log: Monitors user operations, including both trail management
(for example, creating a trail) and security operations (for example,
creating a user or a resource domain).
| Security log: Monitors user system accesses and password definitions.
The Activity Log and Security Log windows list a filtered set of the log
records that are saved in the database. For more information about filtering the
records, see Filtering the Activity and Security Logs. This is an example of
Activity Log window. Log records are accessed directly from LightSoft
windows without using UNIX commands.
At periodic intervals, the oldest accumulated log records over a specified

number and age are automatically removed from the database and archived -
exported to XML files. The number and age over which log records will be
archived is configurable; see Configuring the Export of Excess Log Records.
You can view the archived records in a user-friendly format with Microsoft
Excel 2007; see Viewing Exported Log XML Data.

To access the Activity Log or Security Log window:

| From the LightSoft main menu, select Security > Activity Log or Security
Log. The window opens (the following is the Activity Log window).
The following information about the range of records is shown in the window
header and footer (set independently for each window).
Log record range information
Field/Column Description
Top of window
Dates range from/to Time/date of the oldest and newest records currently in the
database.
Left after export You can adjust the limits of the records kept in the database:
| Records: maximum number of records allowed in the database
| Days: maximum age of records allowed in the database
The automatic export process removes the oldest records over
these limits at periodic intervals. For more details, see Configuring
the Export of Excess Log Records.
Bottom of window
Total Number of records filtered into the view out of the total number of
records that can be displayed.
NOTE: The maximum number of log records in the database

at any one time will be the lesser of the Maximum Capacity
and Maximum Period constraints. If the constraints are
modified upwards, incremental records will start to
accumulate only from that time. Previously deleted records
are not reinstated.
The following menu options are common to both the Activity Log and
Security Log windows.
Activity Log and Security Log menu options
Menu option Toolbar icon Description
Activity (or Security) Log menu
Print Prints the log window data.
Refresh Reloads the log information from the server,

reflecting any changes in the database since the
window was first opened.
Close Closes the log window.
Filter menu
Select Filter Filters the log records according to a selected
filter.

Menu option Toolbar icon Description

Create New Filter Creates a new filter. For more information, see
Filtering the Activity and Security Logs.
Filter Properties Edits or creates a new filter based on an existing
one. For more information, see Filtering the
Activity and Security Logs.
Help Menu
Help Displays online help.
Activity Log Window

The Activity Log window is used to monitor user operations, including both
topology (for example, creating a trail) and security operations (for example,
creating a user or a resource domain). For the capabilities for which actions are
recorded in this window, see Available Capabilities.
For information about monitoring system access-related actions (log in and log
out) and password definition, see Security Log Window.
The Activity Log window displays the following log information.
Activity Log window contents
Column Description
# Number of the activity log record in the list.
Action Time Time the action was performed.
Operation Type Type of operation: topology or security.
Object Name Name of the object on which the action was performed. May
be empty if the action is not object-specific.
Operation Description Description of the action.
Result Whether the action succeeded (OK) or failed (Error).
User Name Name of the user performing the action.

Column Description
Host Name Name of the host computer where the action was performed.
Client Name System name of the computer and UNIX user where the
action was performed, in the format <display>_<UNIX
name>. (For example, if a LightSoft client runs under the
UNIX user nms with display zoom:0.0, its name will be
zoom:0.0_nms.)
Security Log Window

The Security Log window is used to monitor user system access (log in and
log out) and password definitions.
The Security Log window displays the following log information.
Security Log window contents
Column Description
# Number of the security log record in the list.
Action Time Time the action was performed.
User Name User performing the action.
Host Name Name of the host computer where the action was performed.
Client Name System name of computer and UNIX user where the action was
performed, in the format <display>_<UNIX name>. (For example, if
a LightSoft client runs under the UNIX user nms with display
zoom:0.0, its name will be zoom:0.0_nms.)
Security Event Type of action: Login, Logout, Change password.

Configuring the Export of Excess Log

Records
At periodic intervals, the oldest accumulated Activity Log and Security Log
window records over a specified number and age are automatically removed
from the database and archived - exported to XML files.
The following defaults apply:
| Log export directory /sdh_home/nms/NMSEXPLOG.
| File names identify the type of file and export date and time, for example,
ActionLogExport20081223_0300.xml.
| Scheduled daily (Activity log at default 1:00, Security log at 3:00).
The default may be customized as needed. For details, contact ECI Telecom
customer support.
To configure the export of excess log records:

| Set the maximum number and age of records allowed in the database for
each log window by selections in the Left after export fields of each log
window:
Records: Number of log records over which the oldest ones will be
removed and archived.
Days: Age of log records over which the oldest ones will be removed
and archived.
Viewing Exported Log XML Data

You can view the contents of exported Activity or Security Log XML files in a
user-friendly format with Microsoft Excel 2007.
To view exported log records:

First time preparation:
1. Define a directory from which you will view log files in a convenient
location.
2. Open the installation directory /opt/NMS/server/etc/skel.
3. Copy the files ActionLogStyleSheet.xsl and SecurityLogStyleSheet.xsl
files to your viewing folder.
These files describe the XML file schema to Excel and determine the
presentation of the applicable report. They must be present in the directory
from which files are viewed.

Whenever you want to view files:

1. Open the log export directory /sdh_home/nms/NMSEXPLOG.
2. Copy the Activity or Security Log XML export files that you want to view
from the NMSEXPLOG folder to the viewing folder.
3. Open a file in the viewing folder with Excel 2007. The Import XML
window is displayed.
4. Specify the nature of the import, as follows:

a. Select the Open the file with the following stylesheet applied radio
button.
b. In the drop down list, select:
ActionLogStyleSheet.xsl to view an Action log file.
OR
SecurityLogStyleSheet.xsl to view a Security log file.
c. Click OK.
5. The following message is displayed.
6. Click Yes. Excel 2007 now displays the exported Activity or Security Log
XML file in a user- friendly format.

Filtering the Activity and Security Logs

You can filter the log records listed in the Activity Log or Security Log
windows by selecting from a number of predefined system filters. You can also
create your own special purpose filters and edit them. You can define new
filters or base them on existing ones. User-created filters that are no longer
needed can be deleted.
To filter the records in the Activity or Security Log window:

| In the Activity or Security Log window, select the filter from the Filter
selector or select Filter > Select Filter, and choose the filter.
The Log window is filtered according to that filter.
To create a new filter, edit an existing filter, or use an

existing filter as the basis for a new filter:
1. In the Activity or Security Log window, click the Filter Properties icon
or select Filter > Create New Filter. The Filter dialog box opens, as
the following example of Activity Log Filter window. (Match field filters,
and Show Actions checkboxes are only in the Activity Log Filter window.)

2. In the Name dropdown list:

Select the name of the filter you want to edit, or the filter you want to
use as the basis for a new filter. The filter is opened for editing.
OR
Select No Filter if you want to create a new filter. A filter template
with no selections opens for editing.
3. Enter or modify the description.
4. Enter or edit the filters in each category.
5. Click Apply to filter the log window using the current settings.
6. You can also:
Fine-tune the filter by adding or changing settings and clicking Apply
as many times as needed.
Click Clear to clear all settings.
Click Delete to delete the current filter. A Deletion Warning appears.
Click Yes to delete the filter.
Click Close to close the filter dialog box without saving changes.
A Close Warning dialog box appears, reminding you to save if
required. Click No to close without saving.
7. Click Save to save the settings. The Save Filter dialog box appears.
8. Choose a filter name, as follows:

If are creating a new filter from the beginning, enter a unique name and
click OK. The filter is saved.
OR
If you are saving an existing filter under another name, enter the new
name and click OK. The filter is saved.
OR
If you are editing an existing filter, keep the displayed name as is and
click OK. The following warning appears. Click Yes to save the changes.
9. Click Close to close the filter window.

NOTES:
Changes to system-predefined filters, for example the No
Filter template, must be saved under another name.
Filter names are case-sensitive.
Activity Log Filter dialog box options
Option Description
Current Filter Details
Name Filter name.
Created by Either system-predefined or a user name. (Read only)
Description Filter description.
Log Record Parameters
User Name Select one or more of the choices in each parameter
Operation Type (or category as required. The filtered log records are limited
Security Event) to the selected choices. For more information about each
Host Name parameter, see Activity Log Window or Security Log
Window.
Client Name
Action Time
Filter by Action Time Select to enable time filtering options.
Time Duration Select to enable the time duration filtering options. Select
the number of time units and Hours or Days from the
dropdown lists.
Time Range Select to enable the time range filtering options. Enter the
From and To date (dd/mm/yyyy) and time (hh/mm/ss).
Match Object Name (Activity Log Filter dialog box only)

String entry field Enter a string which all the required records should
contain in their Object Name field.
Match Operation Description (Activity Log Filter dialog box only)
String entry field Enter a string which all the required records should
contain in their Operation Description field.
Checkboxes (Activity Log Filter dialog box only)
Show Successful Actions Filters successful actions only.
Show Failed Actions Filters failed actions only.

A
Summary of Menu
Commands
In this appendix:
Overview ........................................................................................................ A-1
View Menu ..................................................................................................... A-2
4
Faults Menu .................................................................................................... A-4

4
Configuration Menu ....................................................................................... A-5

4
Traffic Menu ................................................................................................... A-6

4
Security Menu ................................................................................................ A-8

4
Tools Menu ..................................................................................................... A-8

4
System Menu .................................................................................................. A-9

4
Window Menu .............................................................................................. A-10

4
Help Menu .................................................................................................... A-10

4
Overview
You can access all LightSoft functions from the LightSoft main menu bar at the
top of the window or from the toolbar icons.
The following sections describe each menu option and its corresponding
toolbar icon (where applicable).
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary A-1

Summary of Menu Commands LightSoft User Manual
View Menu
Toolbar
Open in New View Displays selected objects in a new Map window.

See Expanding or Collapsing Objects.
Expand Displays individual objects that are members of the
selected groups in the current view. See Expanding
or Collapsing Objects.
Expand in New View Displays individual objects that are members of the
selected groups in a new view. See Expanding or
Collapsing Objects.
Expand All Displays individual objects that are members of all
existing groups in the current view. See Expanding
or Collapsing Objects.
Collapse Displays selected objects as members of their
respective groups by showing the group icons on
the map instead of the individual object icons. See
Collapse All Displays all objects as members of their respective
groups by showing the group icons on the map
instead of the individual object icons. See
Zoom
| Fit to View : Fits the active Topology
View so that you can see all selected NEs.
| 25% to 800%: Zooms the view in/out to the
selected magnification percentage.
The toolbar Zoom Out and Zoom In
icons can also be used for this purpose.

See Advanced Zoom and Scrolling.
4
NOTE: The main toolbar also provides powerful
Search and Back and

Forward navigation functions; see Main
Toolbar Navigation Functions.
Create Bookmark Applies a permanent bookmark to objects selected
in the map view; see Creating Permanent
Bookmarks.
Select All Selects all the elements in the current topology
layer.
Inverse Selection Selects all the elements in the current topology
layer that are not currently selected, and deselects
those that are currently selected.
A-2 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual Summary of Menu Commands
Toolbar
Print Prints the contents of the current list or map

window. See Printing.
Close View Closes the additional open map view.
Layers Enables you to select a topology view: Physical
(Site), Physical (EMS), Optical (OTN, Optical
Transport Network), SDH, or Ethernet.
Moving Specifies the applicable Move option:
| Lock: Locks the elements so that they cannot
be moved.
| Move Only: Enables you to drag the elements
to the new position. The action is only valid for
the current session.
| Move and Save: Enables you to drag the
elements to the new position, and LightSoft
saves the new location for future sessions.
See Moving Elements in the Main Window.
Display Alternate clicks on an option (Status Bar,
Toolbar, Tree, or Navigator) show/hide that item.
| Show/Hide Tree icon: Alternately
shows/hides a hierarchical tree structure of the
network.
| Show/Hide Navigator icon: Displays/hides a
miniature representation of the entire map for
easy navigation.
Show Network Shows/hides the selected combination of
components from the map view and tree (enabled
when the ETH/MPLS layer is selected):
| MPLS: Shows/hides MPLS network topology
components and their associated links.
| PB: Shows/hides PB network topology
components and their associated links.
| Empty Primary LE: Shows/hides empty
primary LEs (where all associated components
were split out to secondary LEs are hidden).
Their split secondary LEs remain in the view.
For information about secondary LEs, see
Creating Secondary LEs.
Show UMEs Shows/hides UMEs in the Physical (EMS)
topology view.

Main Toolbar Navigation Functions

The main toolbar also provides powerful navigation functions:
| Search entry panel enables you to search individual objects (MEs, LEs, and
UMEs) or groups or locate bookmarked objects throughout any currently
open map view, whether in the main window map, or any Create traffic
entity or List window map; see Searching and Locating Objects.
| Back and Forward icons can be used to revert to the map positions
corresponding to earlier- or later-found object views, or the view before or
after Fit to View was last selected; see Search Procedure.
Faults Menu
Toolbar
icon
Current Alarms Displays the Current Alarms list. See Accessing
Fault Management Windows.
Current TCA Displays the Current Threshold Crossing Alert
(TCA) list. See Accessing Fault Management
Windows.
Event Log Displays the Event Log. See Accessing Fault
Management Windows.
Event Log History Displays the Event Log History window. See
Historical Events.
Event Log Allows you to archive excess or older records,
Configuration view archived events, and periodically clear
archived files. You can also set the types of events
that will trigger the logging of an event. See
Configuring Historical Event Logging, Archiving,
and Viewing.
Alarm Counters Displays the Alarm Counters window. See Using
Alarm Counters.
Alarm Indicators Displays the Alarm Indications window. See
Using Alarm Indicators.
Fault Management Allows you to customize the color coding of alarm
Preferences statuses and change the alarm state mode; see
Customizing Fault Color Coding, which
determines if objects with all alarms acknowledged
should be separately color coded in map windows;
see Changing the Alarm State Mode.

Toolbar
icon
Alarm Forwarder Implements the Alarm Forwarder features, as
Configuration described in Alarm Forwarding by FTP to Remote
Servers and Alarm Forwarding by SMS and Email.
Configuration Menu
Toolbar
icon
Open Opens a GCT session for the selected EMS. See
Starting/Closing a GCT Session.
Properties Displays the properties of a selected item. The
information displayed depends on the type of item
selected. There are info windows for MEs, UMEs,
EMSs, LEs, groups, ports, alarms, events, and for
LightSoft itself.
Create Creates the object indicated by the selected option:
ME, UME, EMS, LE, Topology Link, or Group.
See:
| Creating MEs
| Creating UMEs
| Creating an EMS
| Creating Topology Links
| Creating Groups
| Creating Secondary LEs
Trails are created using a Trails menu option. See
Trails Menu.
Modify Enables actions on selected objects:
| LEs: Changes the name of an LE.
| Add to Group: Adds an object to a group. See
Adding MEs, LEs, and Groups to a Group.
| Remove from Group: Removes an object
from a group; see Removing MEs, LEs, and
Groups from a Group.
| Insert: Inserts an element into a topology link;
see Inserting Elements into SDH Links.
| Remove ME/UME: Removes an element from
a topology link; see Removing an Element
from a Link.
Delete Deletes a selected object; see Deleting Objects.

Traffic Menu
The Traffic menu comprises the following submenus:
| Trails Submenu
| Tunnels Submenu
| Services Submenu
| Multi Period PM Option
Trails Submenu
icon
Create Trail Displays the Create Trail window; see Creating
SDH and EoS/MoT Trails.
Trail List Displays the Trail List window; see Accessing the
Trail List Window.
Trail Filters Displays the Trail Filters dialog box; see Filtering
the Trails Pane.
Trail Consistency Opens the Trail Consistency Indicator (TCI)
window, where you can view details of trail
inconsistencies for selected trails; see
Synchronizing Trails.
4
Discover Optical Automatically acquires all optical trails associated

Trails with selected or all optical links that do not already
have trails configured, in a single operation; see
Creating Optical Trails Through Discovery.
Use Exclusive Enables an SP user to temporarily change the
Resources Exclusive status of CNM resource domains to
allow trail provisioning using those resources, for
example, to facilitate CNM requests for SP
assistance in creating trails or troubleshooting; see
Provisioning Mode.
Import Trails Enables importing trails from an XML file; see
Importing Trails.
Plan Trails Enables you to design networks ahead of time by
fully provisioning "planned" trails even while
prospective resources are currently occupied and
exporting them to XML until needed. When the
new network design is ready to be implemented,
planned trails may be imported to LightSoft as part
of the active network. See Planned Trails.

Tunnels Submenu
icon
Create Tunnel Displays the Create Tunnel window; see
Provisioning MPLS Tunnels.
4
Tunnel List Displays the Tunnel List window; see Performing

4
Actions on Tunnels.
Tunnel Filters Displays the Tunnel Filters dialog box; see
Filtering the Tunnels Pane.
Create Tunnel Mesh Opens the Create Tunnel Mesh window, which
connects each two points of a set of PEs with
tunnels; see Automatic Multi-Tunnel Creation.
Create Multiple Opens the Create Multiple Bypass window, which
Bypass creating bypass tunnels for comprehensive
protection to multiple nodes and links; see
Automatic Multi-Tunnel Creation.
Tunnel Consistency Opens the Tunnel Segment Consistency (TSC)
window, where you can view details of tunnel
inconsistencies for selected tunnel segments; see
Synchronizing Tunnels.
4
Import Tunnels Enables importing tunnels from an XML file; see

Importing Tunnels.
Services Submenu
icon
Create ETH Services Displays the Create Ethernet Service window;
see Creating Ethernet Services.
ETH Service List Displays the Ethernet Service List window; see
Performing Actions on Ethernet Services.
4
ETH Service Filters Displays the Service Filters dialog box; see
Filtering Ethernet Services.
Import ETH Services Enables importing services from an XML file; see
Importing Services.
Policer Profile List Opens the Policer Profiles List window, which is
used to manage policer profiles; see Managing
Policer Profiles.
Multi Period PM
icon
Multi Period PM Opens the Multi Period PM window, which
enables flexible reporting of historical PM counts;
see Multi Period PM.

Security Menu
Toolbar
icon
Security Configures the various aspects of user access
Configuration security. See Security.
4
Change Password Changes the system access password for your user
name. See Changing Your Password.
Active Users Displays the users that are connected to the server
to send a message or force a logout, if required.
See Viewing Active Users.
Activity Log Enables you to monitor user operational activities.
See Activity and Security Logs.
Security Log Enables you to monitor user system access (login
and logout) and password definition. See Activity
and Security Logs.
Tools Menu
Toolbar
icon
Notepad Opens the Notepad text editor. See Creating
Ongoing Notepad Notes.
Bulletin Board Opens the Bulletin Board for posting messages to
LightSoft users. See Posting Messages to a Bulletin
Board.
Send Message Sends a message to any user logged in to the
system; see Sending Messages to Logged-In Users.
EMS List Opens the EMS List window for viewing or
creating EMSs. See EMS List.
Availability Opens the Availability Map window, which shows
available resources for each link at various rates.
See Viewing Resource Availability on Links.
RSTP Opens the RSTP Map window, which shows the
currently active RSTP configuration. See Viewing
RSTP Information.
Timing Opens the Timing Map window, which allows you
to monitor the network's timing topology. See
Viewing NE Timing Sources.
Maps Explorer Function not currently available.
Set LE Location Places LEs on the corresponding SDH or Optical
topology map views. See Setting LE Location.

System Menu
Toolbar
icon
Preferences Opens the User Preferences window for
determining the parameters available in traffic list
windows and aspects of Create traffic entity
behavior; see Traffic Management Preferences.
LightSoft Info Displays basic information about your LightSoft
application; see About LightSoft Window.
Ping Pings an ME to determine whether it is connected
to the network and the quality of the connection;
see Pinging an Object.
Set Route Opens a UNIX window and activates the Set Route
script for setting EMS IP routing data that regulates
the communication between the EMS and its
managed NEs; see Setting EMS IP Routing Data.
Set Printers Enables you to access the EMS printer
configuration window where you can set the
standard printer device; see Setting printers.
Force Upload Forces uploads according to the selected option:
EMS, ME, ME & Connections, or Alarms; see
Forcing an ME Upload and Forcing EMS Uploads.
Upload New Map Function not currently available.
Close GCT Session Closes GCT sessions to all EMSs, closing all open
EMS windows; see Starting/Closing a GCT
Session.
Lock Locks the client station, closing only EMS
windows. Your user name and password are
required to unlock the station; see
Locking/Unlocking the User Client.
Logout Logs out the current user, closing all windows.
Your user name and password are required to log
in again; see Logging Out.
Exit LightSoft Exits the client; see Exiting LightSoft.

Window Menu
Toolbar
icon
Cascade Displays all open windows, one on top of the other,
including their title bars.
Tile Horizontally Tiles all open windows horizontally.
Tile Vertically Tiles all open windows vertically.
Views Shows which additional window views are

currently open, and enables you to select one as the
primary view.
Help Menu
Toolbar
icon
Help Displays a PDF file of this manual.
What’s This This option is not currently available.

About LightSoft Displays information about your LightSoft
installation, including the licensed optional
features.

B
Import/Export Traffic
Syntax
In this appendix:
Overview ........................................................................................................ B-1
XML Export/Import Concepts........................................................................ B-2
4
Trail Syntax and Examples ............................................................................. B-6

4
Tunnel Syntax and Examples ....................................................................... B-39

4
Service Syntax and Examples....................................................................... B-55

4
Overview
LightSoft imports/exports trail, MPLS tunnel and Ethernet service definition
data in a batch from/to XML files. For additional information, see:
| Batch Trail Operations
| Batch Tunnel Operations
| Batch Service Operations
This appendix describes the structure of an XML file and provides a command
reference and examples of XML syntax.
OPTIONAL FEATURE: XML traffic operations are

If not purchased, all menu options pertaining to this feature
are unavailable.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary B-1

Import/Export Traffic Syntax LightSoft User Manual
XML Export/Import Concepts

The following sections provide some key XML concepts. Other concepts are
| XML Structure and DTD
| XML File Components
| XML File Structure
XML Structure and DTD

XML is a markup language (much like HTML) designed to describe data,
where the data is described using XML tags.
XML tags are not predefined - you must define your own tags. One of the ways
to define your own tags is by using a Document Type Definition (DTD) file.
The DTD is predefined, and there is no need for user intervention.
The XML file has a specific structure and a number of elements it can and
should contain.
XML File Components

The building blocks of an XML file are XML elements. Each element
comprises:
| An opening XML tag, with the format "<NAME>".
| Content (values and/or child elements).
| A matching closing XML tag, with the format "</NAME>".
For example, the simple element:
<body>Reboot your PC</body>
XML elements are related as parent and child within an XML file. The opening
XML element (root element) can have any number of nested child elements
under it, with each set of child elements sharing a parent element on the
directly preceding level. (Child elements that share the same parent are called
siblings.)
B-2 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual Import/Export Traffic Syntax
Simplified Examples
The following are much simplified example XML files for trails, tunnels, and
services containing nested elements:
Trails Example
The following is a much simplified example Trails XML file containing nested
elements.
<XML_TRAILS>
<TRAIL OPERATION="CREATE_TRAIL" ID=1:780>
<INFO>...</INFO>
<ENDPOINTS>...</ENDPOINTS>
<RESOURCES>...</RESOURCES>
</TRAIL>
<TRAIL OPERATION="EDIT_TRAIL" ID=1:781>
<INFO>...</INFO>
</TRAIL>
</XML_TRAILS>
Where:
| <XML_TRAILS> is the root element.
| Each instance of Trail is a child element of <XML_TRAILS>.
(OPERATION and ID are attributes of a Trail instance.)
| <INFO>...</INFO>, <ENDPOINTS>...</ENDPOINTS>, and
<RESOURCES>...</RESOURCES> are child elements of the
corresponding parent element Trail. (They are siblings because they
share the same parent.)
For examples of actual Trail XML files, see Example XML Files for Trails.
Tunnels Example
The following is a much simplified example Tunnels XML file containing
nested elements.
<XML_TRAFFIC>
<TUNNEL OPERATION="CREATE" ID=1:780>
<INFO>...</INFO>
<ENDPOINTS_LIST>...</ENDPOINTS_LIST>
<BRANCHES>...</BRANCHES>
</TUNNEL>

<OPERATION="EDIT_ATTRIBUTES" ID=1:781>
<INFO>...</INFO>
</TUNNEL>
</XML_TRAFFIC>
Where:
| <XML_TRAFFIC> is the root element.
| Each instance of TUNNEL is a child element of <XML_TRAFFIC>.
(OPERATION and ID are attributes of a TUNNEL instance.)
| <INFO>...</INFO>, <ENDPOINTS_LIST>...</ENDPOINTS_LIST>,
and <BRANCHES>...</BRANCHES> are child elements of the
corresponding parent element TUNNEL. (They are siblings because they
share the same parent.)
For examples of actual XML files, see Example XML File for Tunnels.
Services Example
The following is a much simplified example Services XML file containing
nested elements.
<XML_TRAFFIC>
<SERVICE OPERATION="CREATE" ID=1:780>
<INFO>...</INFO>
</SERVICE>
<SERVICE OPERATION="EDIT_ATTRIBUTES" ID=1:781>
<INFO>...</INFO>
</SERVICE>
</XML_TRAFFIC>
Where:
| <XML_TRAFFIC> is the root element.
| Each instance of SERVICE is a child element of <XML_TRAFFIC>.
(OPERATION and ID are attributes of a SERVICE instance.)
| <INFO>...</INFO>, <ENDPOINTS>...</ENDPOINTS>, and
<ENDPOINTS_LIST>...</ENDPOINTS_LIST> are child elements of
the corresponding parent element SERVICE. (They are siblings because
they share the same parent.)
For examples of actual XML files, see Example XML File for Services.

XML File Structure

An XML file has a header and a body:
Header
Contains two important pieces of information:
| Root of the file, for example:
<XML_TRAILS>, as described in Trails Example.
<XML_TRAFFIC>, as described in Tunnels Example and Services
Example.
| DTD file full path, for example:
Trails: /opt/NMS/server/etc/TEIMTrail.dtd
Tunnels: /opt/NMS/server/etc/TEIMXMLStruct.dtd
Services: /opt/NMS/server/etc/TEIService.dtd
The Trails example is represented as:
<?xml version="1.0"?>
<!DOCTYPE <XML_TRAILS> SYSTEM /opt/NMS/server/etc/TEIMTrail.dtd>
The Tunnels example is represented as:

<!DOCTYPE <XML_TRAFFIC> SYSTEM /opt/NMS/server/etc/TEIMXMLStruct.dtd>
The Services example is represented as:

<!DOCTYPE <XML_TRAFFIC> SYSTEM /opt/NMS/server/etc/TEIService.dtd>
Body
Contains the information you wish to convey, as described in XML File
Components.

Trail Syntax and Examples

The following sections show the tags used in LightSoft for trails as predefined
by the DTD, and example XML files for trails.
| Trail Syntax Details
| Example XML Files for Trails
Trail Syntax Details

The structure of an XML file is determined in the DTD file. The DTD file is
designed so that the XML file provides full information of a LightSoft trail and
of the operations that you can perform on it (create, edit, and so on).
The following sections show the tags used in LightSoft for trails, as predefined
by the DTD.
NOTE:
The Child Elements section in each tag table, below, shows
the child elements that can be used under each parent tag, in
the order required in the DTD file. For example, for the
<INFO> tag, <RATE>...</RATE> must occur before
<DIRECTION>...</DIRECTION>.
In each table, the applicable child elements are listed by their
tag names (for example, "Trail"). This should be understood
as a shorthand for the full element content (for example,
Trail...</TRAIL>).
<XML_TRAILS>
<XML_TRAILS>
Description Root element of the trail file.

Attributes None.
Data None.
Child elements Trail.
This tag is the root of an XML file. Therefore, it must appear at
Constraints the beginning of the body, right after the header. It must contain
at least one child element.
<XML_TRAILS>
Trail...</TRAIL>
Example
Trail...</TRAIL>
<XML_TRAILS>

<TRAIL>
Description
The beginning of an XML trail. It contains all the trail's data, the operation that will
be performed on the trail, and the trail's ID.
Attributes
OPERATION
Description The operation that will be performed on the trail.
Preset optional operation values:

COMPLETE_TRAIL
CREATE_TRAIL
EDIT_ATTRIBUTES
Expected values
DELETE_TRAIL
RECONNECT
EDIT_TRAIL
COMPLETE_FOR_EDIT
ID
Description The NmsID of the handled trail.
Expected values A string of structure “station id:trail id”. Example: “1:2”
Data
None.
Child elements
<INFO><ENDPOINTS><RESOURCES>
<SEARCH_PARAMETERS>
Constraints
The Operation attribute must be included.
If the operation is edit, complete, reconnect, or delete, the “id” attribute must be
included.
No child elements must be used. This depends on the operation made on the trail and
the information you wish to operate with.
Example
<TRAIL OPERATION="EDIT_TRAIL" ID="1:1">
<INFO>...</INFO>
<SEARCH_PARAMETERS>...</SEARCH_PARAMETERS>
</TRAIL>

<INFO>
<INFO>
Description General information about the trail.

Attributes None.
Data None.
<RATE><DIRECTION><PROTECTION>
<DRI><DNI><ASON><USAGE_STATE>
<SERVICE_LEVEL><SERVICE_INDICATOR>
Child elements <USER_LABEL><CUSTOMER><MASTER_MASK>
<COMMENT><VPNID><VIEW_ON_ETH_LAYER>
<EOS_ATTRIBUTES>
Keep the order of the child elements in the file. All child elements
are mandatory except for:
Constraints <DRI><DNI><ASON><CUSTOMER><COMMENT>
<VPNID> <SERVICE_INDICATOR>
<VIEW_ON_ETH_LAYER> and <EOS_ATTRIBUTES>
<INFO>
<RATE>...</RATE>
<DIRECTION>...</DIRECTION>
<PROTECTION>...</PROTECTION>
<DRI>...</DRI>
<DNI>...</DNI>
<ASON>...</ASON>
<USAGE_STATE>...</USAGE_STATE>
<SERVICE_LEVEL>...</SERVICE_LEVEL>
Example <USER_LABEL>...</USER_LABEL>
<CUSTOMER>...</CUSTOMER>
<COMMENT>...</COMMENT>
<VPNID>...</VPNID>
<MASTER_MASK>...</MASTER_MASK>
<SERVICE_INDICATOR>...</SERVICE_INDICATOR>
<VIEW_ON_ETH_LAYER>…<VIEW_ON_ETH_LAYER>
<EOS_ATTRIBUTES>…<EOS_ATTRIBUTES>
</INFO>

<RATE>
<RATE>
Defines the trail rate; see parameter description in Create Trail
Description
Window – Basic Trail Parameters Pane.
Attributes None.
Data Values:
VC4
VC4_4C
VC4_16C
VC4_4VC
VC4_16VC
VC12
VC2
VC3
EoS_VC4_X, EoS_VC3_X, EoS_VC12_X
MoT_VC4_X, MoT_VC3_X, MoT_VC12_X
eTR_OMS
eTR_OCH
eTR_LP_GbE
eTR_LP_DSR
eTR_LP_STM
eTR_RS_MS
eTR_STS1
Child elements None.

Constraints None.
Example <RATE>VC4</RATE>
<DIRECTION>
<DIRECTION>
Directionality of the trail; see parameter description in Create
Description
Trail Window – Basic Trail Parameters Pane.
Attributes None.
Values:
Data UNIDIRECTIONAL
BIDIRECTIONAL

Constraints None.
Example <DIRECTION>BIDIRECTIONAL</DIRECTION>

<PROTECTION>
<PROTECTION>
Indicates on which layer the protection is implemented, and
whether it is on the same layer as the trail being defined or on an
Description
underlying layer; see parameter description in Create Trail
Window – Basic Trail Parameters Pane.
Attributes None.
Values:
UNPROTECTED
Data UNDERLYING
CURRENT
CURRENT_UNDERLYING
Constraints None.
Example <PROT_LAYER>CURRENT</PROT_LAYER>
<DRI>
<DRI>
Indicates whether DRI search should be performed. If this tag
does not exist , no DRI protection will be performed on the
Description
current trail; see parameter description in Create Trail Window –
Attributes None.
Values:
Data ON
OFF
Constraints This tag is optional in the <INFO> tag.
Example <DRI>OFF</DRI>

<DNI>
<DNI>
Indicates whether DNI search should be performed. If this tag
does not exist, no DNI protection will be performed on the
Description
current trail; see parameter description in Create Trail Window –
Attributes None.
Values:
Data ON
OFF
Example <DNI>OFF</DNI>
<PROT_LAYER>
<PROT_LAYER>
Protection Layer indicates on which layer the protection is
Description implemented, and whether it is on the same layer as the trail
being defined or on an underlying layer.
Attributes None.
Values:
Data eTPS_UNDERLYING
eTPS_CURRENT
eTPS_CURRENT_UNDERLYING
This XML tag is supported for XML files inherited from previous
Constraints
LightSoft versions.
Example <PROT_LAYER>eTPS_CURRENT</PROT_LAYER>

<PROT_EFFORT>
<PROT_EFFORT>
Protection Effort indicates whether LightSoft path search must
Description
meet the protection criteria (layer and quality).
Attributes None.
Values:
Data EFFORT_SAME_OR_WORSE
EFFORT_SAME
This XML tag is supported for XML files inherited from previous
Constraints
LightSoft versions.
Example <PROT_EFFORT>EFFORT_SAME</PROT_EFFORT>
<USAGE_STATE>
<USAGE_STATE>
Usage State is a user-managed attribute that indicates whether the
trail is in use. Used to prevent deletion of active trails; see User
Description
Usage State in Create Trail Window - Advanced Trail Parameters
Pane.
Attributes None.
Values:
Data IDLE
ACTIVE
Constraints None.
Example <USAGE_STATE>IDLE</USAGE_STATE>

<SERVICE_LEVEL>
<SERVICE_LEVEL>
User-managed attribute that allows you to assign a priority level
Description to a trail; see Service Indicator in Create Trail Window -
Advanced Trail Parameters Pane.
Attributes None.
Values:
NON_SERVICE
Data SERVICE
BRONZE
SILVER
GOLD
Constraints None.
Example <SERVICE_LEVEL>SERVICE</SERVICE_LEVEL>
<USER_LABEL>
<USER_LABEL>
Trail's display name; see Label in Create Trail Window – Basic
Description
Trail Parameters Pane.
Attributes None.
Data Free string.
Constraints None.
Example <USER_LABEL>LABEL</USER_LABEL>
<CUSTOMER>
<CUSTOMER>
Customer associated with the trail; see Create Trail Window –
Description
Attributes None.
Data Free string.
Example <CUSTOMER>NODE_A</CUSTOMER>

<COMMENT>
<COMMENT>
Comment associated with the trail; see Comments in Create Trail
Description
Window - Advanced Trail Parameters Pane.
Attributes None.
Data Free string.
Example <COMMENT>CREATED_BY_AAA</COMMENT>
<VPNID>
<VPNID>
Description VPN ID.
Attributes None.
Data VPN string.
Example <VPNID>VPNSTR</VPNID>
<MASTER_MASK>
<MASTER_MASK>
Determines whether faults on objects in the trail path generate
Description alarms; see Create Trail Window - Advanced Trail Parameters
Pane.
Attributes None.
Values:
Data OFF
ON
Constraints None.
Example <MASTER_MASK>ON</MASTER_MASK>

<SERVICE_INDICATOR>
<SERVICE_INDICATOR>
Indicates whether this trail is a service trail or not; see Create
Description
Trail Window - Advanced Trail Parameters Pane.
Attributes None.
Values:
Data SERVICE_TRAIL
NOT_ SERVICE_TRAIL
Constraints None.
<SERVICE_INDICATOR> SERVICE_TRAIL</SERVICE_INDICATOR>
Example
<VIEW_ON_ETH_LAYER>
<VIEW_ON_ETH_LAYER>
Indicates that the trail should be visible as a virtual link on the
Description ETH/MPLS layer; see Create Trail Window - EoS/MoT
Configuration Pane.
Attributes None.
Data Values: ON, OFF

Constraints None.
Example <VIEW_ON_ETH_LAYER>ON</VIEW_ON_ETH_LAYER>

<EOS_ATTRIBUTES>
<EOS_ATTRIBUTES>
Contains all attributes regarding EoS trail; see Create Trail
Description
Window - EoS/MoT Configuration Pane.
Attributes None.
Data None.
<DIVERSE_ROUTES_NUMBER><VCAT_SIZE>
Child elements <LCAS><ETH_SERVICE_TYPE><LAYER2_PARAMS>
<DIVERSE_ROTE_INFO>
Constraints None.
<EOS_ATTRIBUTES>
Example <DIVERSE_ROUTES_NUMBER>1
</DIVERSE_ROUTES_NUMBER>
<VCAT_SIZE>1</VCAT_SIZE>
<LCAS>ON</LCAS
<ETH_SERVICE_TYPE>Layer2_Ethernet
</ETH_SERVICE_TYPE>
<LAYER2_PARAMETERS
<RSTP>STP_ENABLED</RSTP
<RSTP_COST>1</RSTP_COST
<ACTIVATE_BANDWIDTH>ON
</ACTIVATE_BANDWIDTH>
</LAYER2_PARAMETERS>
<DIVERSE_ROUTE_INFO>
<DIVERSE_ROUTE_ID>1</DIVERSE_ROUTE_ID
<EXTRA_TRAFFIC>OFF</EXTRA_TRAFFIC
</DIVERSE_ROUTE_INFO
</EOS_ATTRIBUTES>
<DIVERSE_ROUTES_NUMBER>
<DIVERSE_ROUTES_NUMBER>
Minimum or exact number of diverse routes defined for the

Description EoS/MoT trail; see Create Trail Window - EoS/MoT
Configuration Pane.
Attributes None.
Data Number of diverse routes.
Constraints None.
<DIVERSE_ROUTES_NUMBER> 2
Example
</ DIVERSE_ROUTES_NUMBER>

<VCAT_SIZE>
<VCAT_SIZE>
Virtual Concatenated paths, indicating the number of resources

Description that can be used on a single EoS/MoT trail segment; see Create
Trail Window – Basic Trail Parameters Pane.
Attributes None.
Data VCAT size.
Constraints None.
Example <VCAT_SIZE>4</VCAT_SIZE>
<LCAS>
<LCAS>
Indicates if LCAS is activated; see LCAS Enabled in Trails Pane

Description
- Protection Tab.
Attributes None.
Values:
Data OFF
ON
Constraints None.
Example <LCAS>ON</LCAS>
<ETH_SERVICE_TYPE>
<ETH_SERVICE_TYPE>
Description Indicates the Ethernet service type; see Trails Pane Columns.
Attributes None.
Values:
Data eUndefinedEthService
Layer1_Ethernet
Layer2_Ethernet
Constraints None.
<ETH_SERVICE_TYPE>Layer2_Ethernet
Example
</ETH_SERVICE_TYPE>

<LAYER2_PARAMETERS>
<LAYER2_PARAMETERS>
Description Contains information from the Layer 2 Parameters section in
Create Trail Window - EoS/MoT Configuration Pane.
Attributes None.
Data None.
Child elements <RSTP><RSTP_COST><ACTIVATE_BANDWIDTH>
Constraints None.
Example <LAYER2_PARAMETERS>
<RSTP>STP_ENABLED</RSTP>
<RSTP_COST>1</RSTP_COST>
<ACTIVATE_BANDWIDTH>ON
</ACTIVATE_BANDWIDTH>
<RSTP>
<RSTP>
Description Indicates whether RSTP is enabled; see Create Trail Window -
Attributes None.
Data STP_ENABLED
STP_DISABLED
Constraints None.
Example <RSTP>STP_ENABLED</RSTP>
<RSTP_COST>
<RSTP_COST>
Description Indicates the RSTP cost assigned to the trail; see Create Trail
Attributes None.
Data RSTP COST
Constraints None.
Example <RSTP_COST>1</RSTP_COST>

<ACTIVATE_BANDWIDTH>
<ACTIVATE_BANDWIDTH>
Description Indicates if bandwidth is activated; see Create Trail Window -
Attributes None.
Data Values:
ON
OFF
Constraints None.
Example <ACTIVATE_BANDWIDTH>ON</ACTIVATE_BANDWID
TH>
Description Contains diverse route general information; see Create Trail
Attributes None.
Data None.
Child elements <DIVERSE_ROUTE_ID><EXTRA_TRAFFIC>
Constraints None.
Example <DIVERSE_ROUTE_INFO>
<DIVERSE_ROUTE_ID>1</DIVERSE_ROUTE_ID>
<EXTRA_TRAFFIC>OFF</EXTRA_TRAFFIC>
</DIVERSE_ROUTE_INFO>
<DIVERSE_ROUTE_ID>
<DIVERSE_ROUTE_ID>
Description Indicates the route number; see Create Trail Window - Select
Segment Pane.
Attributes None.
Data Diverse route number.
Constraints None.
Example <DIVERSE_ROUTE_ID>1</DIVERSE_ROUTE_ID>

<EXTRA_TRAFFIC>
<EXTRA_TRAFFIC>
Description Indicates if extra traffic is enabled; see Create Trail Window -
Attributes None.
Data Values: ON, OFF
Constraints None.
Example <EXTRA_TRAFFIC>OFF</EXTRA_TRAFFIC>
<ENDPOINTS>
<ENDPOINTS>
Contains trails endpoints data divided into paths according to

Description the main or protection paths; see Create Trail Window -
Resource Tree Pane.
Attributes None.
Data None.
Child elements Path
Constraints Must contain at least one child element.
<ENDPOINTS>
Path...</PATH>
Example
Path...</PATH>
</ENDPOINTS>

<PATH>
<Path>
Contains information about the endpoints of a trail path, in one

Description
direction; see Create Trail Window - Selecting Trail Endpoints.
TYPE
Attributes
Description Protection type of current path
Expected values MAIN or PROTECTION
Data None
Child elements <A_ENDPOINT><Z_ENDPOINT>
Must contain the “TYPE” attribute.

Constraints
Must contain at least one of each child element.
<PATH TYPE="MAIN">
<A_ENDPOINT>...</A_ENDPOINT>
Example
<Z_ENDPOINT>...</Z_ENDPOINT>
</PATH>

<A_ENDPOINT>
<A_ENDPOINT>
“Add” or “Source” endpoint of a path (trail or segment). Contains

Description
the information required to create the identifier of an endpoint.
C2V_NUMBER
Description Group index of concatenated TPs.
Expected values An integer, which is the index number.

Note: C2V takes a contiguous signal of 4 or 16 VC-4s and breaks
Attributes it into individual VC-4 signals. When you create a trail, you can
configure the endpoint to perform C2V for you.
DRI_SOURCE_NUMBER
A trail's source TPs can contain an index
Description number to which a DRI segment can relate
as a source point.
Expected values An integer which is the index number.
Data None.
Child elements
<SEARCH_PARAMETERS>
No attribute is mandatory. Options for endpoint child elements:
<LE> if the endpoint should be selected from an LE,
or
Constraints
<LE><PTP> if the endpoint is a specific PTP,
or
<LE><PTP><CTP> if the endpoint is a specific CTP.
<A_ENDPOINTS DRI_SOURCE_NUMBER="2">
<LE>...</LE>
Example
<PTP>...</PTP>
</A_ENDPOINT>

<Z_ENDPOINT>
<Z_ENDPOINT>
“Drop” or “Sink” endpoint of a path (trail or segment). Contains

Description
the information required to create the identifier of an endpoint.
C2V_NUMBER
Attributes
Description Group index of concatenated TPs.
Expected values An integer, which is the index number.

Data None.
Child elements
<SEARCH_PARAMETERS>
No attribute is mandatory. Options for endpoint child elements
are:
<LE> if the endpoint should be selected from an LE,
Constraints or
<LE><PTP> if the endpoint is a specific PTP,
or
<LE><PTP><CTP> if the endpoint is a specific CTP.
<Z_ENDPOINTS>
<LE>...</LE>
Example
<PTP>...</PTP>
</Z_ENDPOINT>
<RESOURCES>
<RESOURCES>
Contains resources data divided into segments according to main
Description
or protection paths; see Create Trail Window - Resource List.
Attributes None.
Data None.
Child elements <SEGMENT>
Constraints None.
<RESOURCES>
<SEGMENT>...</SEGMENT>
Example
<SEGMENT>...</SEGMENT>
</RESOURCES>

<SEGMENT>
<SEGMENT>
Contains information on one segment (unidirectional topology

Description
connection).
TYPE
Attributes
Description Protection type of the current segment.
Expected values MAIN or PROTECTION.

Data None.
<A_ENDPOINT><Z_ENDPOINT><TIME_SLOT>
Child elements
<BRIDGE_NUMBER><BRIDGE_SOURCE_EP_NUMBER>
Must contain a “TYPE” attribute.
Must contain one <A_ENDPOINT> and one <Z_ENDPOINT>.
The child elements <TIME_SLOT>, <BRIDGE_NUMBER>,
Constraints and <BRIDGE_SOURCE_EP_NUMBER> are optional.
May contain more than one <TIME_SLOT>. In this case, the
segment is duplicated and sent in as many segments as possible
within one time slot.
<SEGMENT TYPE="MAIN"<
<A_ENDPOINT>...</A_ENDPOINT>
<Z_ENDPOINT>...</Z_ENDPOINT>
<TIME_SLOT>...</TIME_SLOT>
Example
<BRIDGE_NUMBER>...</BRIDGE_NUMBER>
<BRIDGE_SOURCE_EP_NUMBER>...
</BRIDGE_SOURCE_EP_NUMBER>
</PATH>

<TIME_SLOT>
<TIME_SLOT>
Description Exact resource used by the segment.

Attributes None.
Data None.
Child elements <I><J><K><L><M>
This tag is optional in the <SEGMENT> tag.

Must have child elements. Options for timeslot child elements are:
<I> if the resource is optic (exported only),
or
<J> if the resource is STM,
Constraints or
<J><K> if the resource is TU3,
or
<J><K><L> if the resource is TU2,
or
<J><K><L><M> if the resource is TU12.
The child elements <I><J><K><L><M> may contain only one
integer, which is the number of the resource in its hierarchy.
Examples
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
<TIME_SLOT>
<J>1</J>
<K>2</K>
<L>3</L>
</TIME_SLOT>
<TIME_SLOT>
<J>1</J>
<K>2</K>
</TIME_SLOT>

<BRIDGE_NUMBER>
<BRIDGE_NUMBER>
This tag is the index number of a DRI protection group to which

Description
the current segment belongs.
Attributes None.
Data An integer which is the index number.
Constraints This tag is optional in the <SEGMENT> tag.
Example <BRIDGE_NUMBER>12</BRIDGE_NUMBER>
<BRIDGE_SOURCE_EP_NUMBER>
<BRIDGE_SOURCE_EP_NUMBER>
Contains the index of a source endpoint (attribute

Description DRI_SOURCE_NUMBER in <A_ENDPOINT> of Path), which
will be the source indicator to the current segment in the bridge.
Attributes None.
Data An integer which is the index number.
Constraints This tag is optional in the <SEGMENT> tag.
<BRIDGE_SOURCE_EP_NUMBER>1
Example
</BRIDGE_SOURCE_EP_NUMBER>
<LE> <PTP> <CTP>

<LE> <PTP> <CTP>
These tags contain the relative distinguishable name of an

Description
endpoint in the database.
Attributes None.
Data A string which is the relative distinguishing name.
Constraints None.
<A_ENDPOINT>
<LE>XDM_23825</LE>
Example <PTP>15:1</PTP>
<CTP>/sts3c_au4-j=1</CTP>
</A_ENDPOINT>

<LE>
<LE>
Description User label of an LE.

Attributes None.
Data A string which is the label.
Constraints None.
<Z_ENDPOINT>
Example <LE> XDM_23888</LE>
</Z_ENDPOINT>
<SEARCH_PARAMETERS>
<SEARCH_PARAMETERS>
Description Defines a trail path search preference.

Attributes None.
Data None.
Child elements <PRIORITIES><LOAD_UTILIZATION>
Constraints None.
<SEARCH_PARAMETERS>
Example <PRIORITIES>...</PRIORITIES>
</SEARCH_PARAMETERS>

<PRIORITIES>
<PRIORITIES>
Defines optimization priorities for searching a path. May
contain up to four (4) child elements with the desired priority.
Description
The order of these priorities in the record is the order used by
the optimization algorithm.
Attributes None.
Values of <PRIORITY> child element(s):
eTPC_NUMBER_LINKS
eTPC_NUMBER_ELEMENTS
eTPC_DIRECTIONALITY_TYPE
Data eTPC_USER_ASSIGNED_QUALITY
eTPC_USER_ASSIGNED_COST
eTPC_DISTANCE
eTPC_LOCATION_CARD
eTPC_LOAD_UTILIZATION
Child elements <PRIORITY>
Constraints Must include at least one child element.
<PRIORITIES>
<PRIORITY>eTPC_NUMBER_ELEMENTS</PRIORIT
Example
Y>
<PRIORITY>eTPC_DISTANCE</PRIORITY>
</PRIORITIES>

<LOAD_UTILIZATION>
<LOAD_UTILIZATION>
If one of the priorities is eTPC_LOAD_UTILIZATION, this tag
will define the desired load boundaries.
When selecting link resources, <LOW> to <MIDDLE> is the
Description first load choice, and <MIDDLE> to <HIGH> is the second
load choice.
Resources that are not between the <LOW> and <HIGH>
values are excluded from the path search.
Attributes None.
Each child element should contain an integer, which will be the
Data
load value.
Child elements <LOW><MIDDLE><HIGH>
Constraints None.
<PRIORITIES>
<PRIORITY>eTPC_NUMBER_ELEMENTS</PRIORITY>
<PRIORITY>eTPC_LOAD_UTILIZATION</PRIORITY>
</PRIORITIES>
Example <LOAD_UTILIZATION>
<LOW>60<LOW>
<MIDDLE>75<MIDDLE>
<HIGH>85<HIGH>
</LOAD_UTILIZATION>

Example XML Files for Trails

The following sections show examples of XML files for trails:
| Example 1 shows an XML file that will create a unidirectional trail with no
protection. The trail's endpoints are PTPs and no segment is supplied.
| Example 2 shows an XML file with DRI protection.
| Example 3 shows an XML file with a protected EoS trail.
Example 1 for Trails

The following is an example of an XML file that will create a unidirectional
trail with no protection. The trail's endpoints are PTPs, and no segment is
supplied.
<!DOCTYPE XML_TRAILS SYSTEM "/opt/NMS/server/etc/TEIMTrail.dtd">
<XML_TRAILS>
<TRAIL OPERATION="CREATE_TRAIL">
<INFO>
<RATE>VC4</RATE>
<DIRECTION>UNIDIRECTIONAL</DIRECTION>
<PROTECTION>UNPROTECTED</PROTECTION>
<DRI>OFF</DRI>
<DNI>OFF</DNI>
<ASON>OFF</ASON>
<USAGE_STATE>IDLE</USAGE_STATE>
<SERVICE_LEVEL>NON_SERVICE</SERVICE_LEVEL>
<USER_LABEL>XDM_50-XDM_46</USER_LABEL>
<MASTER_MASK>ON</MASTER_MASK>
<SERVICE_INDICATOR>NOT_SERVICE_TRAIL</SERVICE_INDICATOR>
</INFO>
<ENDPOINTS>
<PATH TYPE="MAIN">
<A_ENDPOINT> <LE>XDM_50</LE> <PTP>I7-STM-n#1 </PTP> </A_ENDPOINT>
<Z_ENDPOINT> <LE>XDM_46</LE> <PTP>I11-STM-16#1 </PTP> </Z_ENDPOINT>
</PATH>
</ENDPOINTS>
<RESOURCES></RESOURCES>
</TRAIL>
</XML_TRAILS>


This is an example of an XML file with DRI protection.
<!DOCTYPE XML_TRAILS SYSTEM /opt/NMS/server/etc/TEIMTrail.dtd">
<XML_TRAILS>
<INFO>
<RATE>EoS_VC4_X</RATE>
<DIRECTION>BIDIRECTIONAL</DIRECTION>
<PROTECTION>CURRENT</PROTECTION>
<DRI>OFF</DRI>
<DNI>OFF</DNI>
<ASON>OFF</ASON>
<USER_LABEL>XDM_50-XDM_777</USER_LABEL>
<VIEW_ON_ETH_LAYER>ON</VIEW_ON_ETH_LAYER>
<EOS_ATTRIBUTES>
<DIVERSE_ROUTES_NUMBER>1</DIVERSE_ROUTES_NUMBER>
<VCAT_SIZE>1</VCAT_SIZE>
<LCAS>ON</LCAS>
<ETH_SERVICE_TYPE>Layer2_Ethernet</ETH_SERVICE_TYPE>
<LAYER2_PARAMETERS>
<RSTP>STP_ENABLED</RSTP>
<RSTP_COST>1</RSTP_COST>
<ACTIVATE_BANDWIDTH>ON</ACTIVATE_BANDWIDTH>
</DIVERSE_ROUTE_INFO>
</EOS_ATTRIBUTES>
</INFO>
<ENDPOINTS>
<PATH TYPE="MAIN">
<A_ENDPOINT>
<LE>XDM_50</LE> <PTP>I6-GEoS-1 </PTP> <CTP>I6-VC4-1 </CTP>

</A_ENDPOINT>
<Z_ENDPOINT>
<LE>XDM_777</LE> <PTP>WAN-VC4:11</PTP>
</Z_ENDPOINT>
</PATH>
<PATH TYPE="MAIN">
<A_ENDPOINT>
<LE>XDM_777</LE> <PTP>WAN-VC4:11</PTP>
</A_ENDPOINT>
<Z_ENDPOINT>
</Z_ENDPOINT>
</PATH>
<PATH TYPE="PROTECTION">
<A_ENDPOINT>
</A_ENDPOINT>
<Z_ENDPOINT>
<LE>XDM_777</LE> <PTP>WAN-VC4:11</PTP> </Z_ENDPOINT>
</Z_ENDPOINT>
</PATH>
<A_ENDPOINT> <LE>XDM_777</LE> <PTP>WAN-VC4:11</PTP> </A_ENDPOINT>
<Z_ENDPOINT>
</Z_ENDPOINT>
</PATH>
</ENDPOINTS>
<RESOURCES>
<SEGMENT TYPE="MAIN">
<Z_ENDPOINT> <LE>despair</LE> <PTP>MS_STM1:1</PTP> </Z_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<A_ENDPOINT> <LE>despair</LE> <PTP>MS_STM16:1</PTP> </A_ENDPOINT>
<Z_ENDPOINT> <LE>XDM_777</LE> <PTP>MS_STM16:1</PTP> </Z_ENDPOINT>
<TIME_SLOT>

<J>1</J>
</TIME_SLOT>
</SEGMENT>
<Z_ENDPOINT> <LE>XDM_46</LE> <PTP>I4-STM-n#1 </PTP> </Z_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<SEGMENT TYPE="PROTECTION">
<Z_ENDPOINT> <LE>XDM_49_1</LE> <PTP>I4-STM-n#1 </PTP> </Z_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<A_ENDPOINT> <LE>XDM_49_2</LE> <PTP>I10-STM-n#10 </PTP> <A_ENDPOINT>
<Z_ENDPOINT> <LE>toval</LE> <PTP>MS_STM1:1</PTP> </Z_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</RESOURCES>
</TRAIL>
</XML_TRAILS>


This is an example of an XML file with a protected EoS trail:
<!DOCTYPE XML_TRAILS SYSTEM "/opt/NMS/server/etc/TEIMTrail.dtd">
<XML_TRAILS>
<INFO>
<RATE>VC4</RATE>
<DIRECTION>BIDIRECTIONAL</DIRECTION>
<PROTECTION>CURRENT</PROTECTION>
<DRI>ON</DRI>
<DNI>OFF</DNI>
<ASON>OFF</ASON>
<USER_LABEL>pt-XDM_50</USER_LABEL>
</INFO>
<ENDPOINTS>
<PATH TYPE="MAIN">
<A_ENDPOINT DRI_SOURCE_NUMBER="1">
<LE>pt</LE> <PTP>MS_STM16:1</PTP>
</A_ENDPOINT>
<Z_ENDPOINT>
<LE>XDM_50</LE> <PTP>I3-STM-n#1 </PTP> <CTP>I3-MS-1</CTP>
</Z_ENDPOINT>
</PATH>
<PATH TYPE="MAIN">
</A_ENDPOINT>
<Z_ENDPOINT>
<LE>pt</LE> <PTP>MS_STM16:1</PTP> <CTP>MS_STM16:1:0:1</CTP>
</Z_ENDPOINT>
</PATH>

</A_ENDPOINT>
<Z_ENDPOINT>
</Z_ENDPOINT>
</PATH>
<LE>XDM_50</LE> <PTP>I3-STM-n#2 </PTP> <CTP>I3-MS-2 </CTP>
</A_ENDPOINT>
<Z_ENDPOINT>
</Z_ENDPOINT>
</PATH>
</ENDPOINTS>
<RESOURCES>
<A_ENDPOINT> <LE>pt</LE> <PTP>MS_STM16:1</PTP> </A_ENDPOINT>
<Z_ENDPOINT> <LE>tg1117</LE> <PTP>MS_STM16:1</PTP> </Z_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<A_ENDPOINT> <LE>XDM_49_1</LE> <PTP>I4-STM-n#1 </PTP> </A_ENDPOINT>
<TIME_SLOT>
<J>1</J>

</TIME_SLOT>
</SEGMENT>
<A_ENDPOINT> <LE>toval</LE> <PTP>MS_STM16:1</PTP>
</A_ENDPOINT>
<Z_ENDPOINT> <LE>pt</LE> <PTP>MS_STM16:2</PTP> </Z_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<A_ENDPOINT> <LE>XDM_49_2</LE> <PTP>I10-STM-n#10 </PTP> /A_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
<BRIDGE_NUMBER>1</BRIDGE_NUMBER>
<BRIDGE_SOURCE_EP_NUMBER>3</BRIDGE_SOURCE_EP_NUMBER>
</SEGMENT>
<A_ENDPOINT> <LE>tg1117</LE> <PTP>MS_STM16:3</PTP> </A_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<A_ENDPOINT> <LE>tg1117</LE> <PTP>MS_STM16:2</PTP> </A_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>

</SEGMENT>
<TIME_SLOT>
<J>2</J>
</TIME_SLOT>
</SEGMENT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<A_ENDPOINT> <LE>toval</LE> <PTP>MS_STM16:3</PTP>
</A_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>
<A_ENDPOINT> <LE>toval</LE> <PTP>MS_STM16:2</PTP> </A_ENDPOINT>
<TIME_SLOT>
<J>1</J>
</TIME_SLOT>
</SEGMENT>

<TIME_SLOT>
<J>2</J>
</TIME_SLOT>
</SEGMENT>
</RESOURCES>
</TRAIL>
</XML_TRAILS>

Tunnel Syntax and Examples

The following sections show the tags used in LightSoft for tunnels as
predefined by the DTD, and an example XML file for tunnels.
| Tunnel Syntax Details
| Example XML File for Tunnels
Tunnel Syntax Details

designed so that the XML file provides full information of a LightSoft tunnel
and of the operations that you can perform on it (create, edit, frr, and so on).
The following sections show the tags used in LightSoft for tunnels, as
predefined by the DTD.
NOTE:
<INFO> tag, <NAME>...</NAME> must occur before
<TYPE>...</TYPE>.
tag names (for example, "TUNNEL"). This should be
understood as a shorthand for the full element content (for
example, TUNNEL...</TUNNEL>).
<XML_TRAFFIC>
<XML_TRAFFIC>
Description Root element of the tunnel/service file.

Attributes None.
Data None.
Child elements TUNNEL
This tag is the root of an XML file. Therefore, it must appear at the
Constraints beginning of the body, right after the header. It must contain at
least one child element.
<XML_TRAFFIC>
<TUNNEL>...</TUNNEL>
Example
<TUNNEL>...<TUNNEL>
<XML_TRAFFIC>

<TUNNEL>
<TUNNEL>
Description The beginning of an XML tunnel. It contains all the tunnel's
data, the operation that will be performed on the tunnel, and the
tunnel's ID.
Attributes OPERATION
Description The operation that will be performed on the
tunnel.
Expected Preset optional operation values:
values CREATEDELETE
EDIT_ATTRIBUTES
EDIT_FRR
EDIT_BW
RECONNECT
ID

Expected A string of structure “station id:tunnel id”.
values Example: “1:2”
Data None.
Child elements <INFO><ENDPOINTS_LIST><BRANCHES>
Constraints The Operation attribute must be included.

If the operation is edit, complete, reconnect, or delete, the “id”
attribute must be included.
No child elements must be used. This depends on the operation
made on the trail and the information you wish to operate with.
Example <TUNNEL OPERATION="CREATE" ID="1:1">
<INFO>...</INFO>
</TUNNEL>

<INFO>
<INFO>
Description General information about the tunnel.

Attributes None.
Data None.
Child elements <NAME><CUSTOMER><DIRECTION>
<TYPE><PROTECTION><FRR_GUR><FRR_TYPE>
<PROTECTED_FE><PROTECTED_PORT>
<PROTECTED_NODE><VPN_DEDICATED>
<P2P_DEDICATED><COS><BW><OAM><GEN_ALARMS>
<COMMENTS><STATE><MPLS_LABEL>
Constraints Keep the order of the child elements in the file. All child
elements are mandatory except for:
<FRR_GUR><FRR_TYPE><><PROTECTED_FE><PROTECTED_PORT><P
ROTECTED_NODE><VPN_DEDICATED><P2P_DEDICATED>
Example <INFO>
<NAME>...</NAME>
<DIRECTION>...</DIRECTION>
<TYPE>...</TYPE>
<PROTECTION>...</PROTECTION>
<FRR_GUR>...</FRR_GUR>
<COS>...</COS>
<BW>...</BW>
<OAM>...</OAM>
<GEN_ALARMS>...</GEN_ALARMS>
<COMMENTS>...</COMMENTS>
<STATE>...</STATE>
<MPLS_LABEL>…</MPLS_LABEL>
</INFO>

<NAME>
<NAME>
Defines the tunnel name; see Create Tunnel Window - Basic
Description
Parameters Pane.
Attributes None.
Data None.
Child Elements None.
Constraints <NAME>Tunnel-1407</NAME>
Example
<CUSTOMER>
<CUSTOMER>
Customer associated with the tunnel; see Create Tunnel Window -
Description
Attributes None.
Data Free string.
Constraints None.
Example <CUSTOMER>customer 123</ CUSTOMER >
<DIRECTION>
<DIRECTION>
Description Directionality of the tunnel.
Attributes None.
Values:
Data UNIDIRECTIONAL
BIDIRECTIONAL

Constraints None.
Example <DIRECTION>BIDIRECTIONAL</DIRECTION>

<PROTECTION>
<PROTECTION>
Protection tag indicates the tunnel protection desired; see
Description parameter description in Create Tunnel Window - Basic
Parameters Pane.
Attributes None.
Values:
UNPROTECTED
Data
PROTECTED
BYPASS

Constraints None.
Example <PROTECTION>CURRENT</PROTECTION>
<FRR_GUR>
<FRR_GUR>
Indicates that only tunnel paths having predefined bypass tunnels
available to protect each node and link are considered by
Description
pathfinder; see parameter description in Guaranteed FRR Desired
in Create Tunnel Window - Advanced Parameters Pane.
Attributes None.
Values:
Data ENABLE
DISABLE

Example <FRR_GUR>DISABLE</FRR_GUR>

<FRR_TYPE>
<FRR_TYPE>
FRR Type protection mode applying to a bypass tunnel; see
Description parameter description in Create Tunnel Window - Basic
Parameters Pane.
Attributes None.
Values:
NA
Data NODE_PROTECTION
LINK_PROTECTION
NODE_LINK_PROTECTION

Example <FRR_TYPE> LINK_PROTECTION</FRR_TYPE>
<PROTECTED_FE>
<PROTECTED_FE>
Description Indicates the protected Managed Element.

Attributes None.
Data Free string.
Example <PROTECTED_FE>TA-1</ PROTECTED_FE>
<PROTECTED_PORT>
<PROTECTED_PORT>
Description Indicates the protected port.
Attributes None.
Data Free string
Example <PROTECTED_PORT>PTP-1</PROTECTED_PORT>

<PROTECTED_NODE>
<PROTECTED_NODE>
Description Indicates the protected node.

Attributes None.
Data Free string.
Example <PROT_EFFORT>EFFORT_SAME</PROT_EFFORT>
<VPN_DEDICATED>
<VPN_DEDICATED>
Whether the tunnel is designated as Single Service Only; see
Description parameter description in Create Tunnel Window - Advanced
Parameters Pane.
Attributes None.
Values:
Data ENABLE
DISABLE

Example <VPN_DEDICATED>IDLE</ VPN_DEDICATED >
<P2P_DEDICATED>
<P2P_DEDICATED>
Whether a tunnel is restricted to P2P VPNs only; see parameter
Description description in Create Tunnel Window - Advanced Parameters
Pane.
Attributes None.
Values:
Data ENABLE
DISABLE

Example <SERVICE_LEVEL>SERVICE</SERVICE_LEVEL>

<COS>
<COS>
Class of Service (CoS) value assigned to a tunnel; see parameter
Description
description in Create Tunnel Window - Basic Parameters Pane.
Attributes None.
Values:
COS0
COS1
COS2
Data COS3
COS4
COS5
COS6
COS7
Constraints None.
Example <COS>LABEL</COS>
<BW>
<BW>
Bandwidth assigned to a tunnel; see parameter description in
Description
Create Tunnel Window - Basic Parameters Pane.
Attributes None.
Data Free string.
Constraints None.
Example <BW>2</BW>

<OAM>
<OAM>
Whether Operations Administration and Maintenance (OAM) is
Description enabled for a tunnel; see parameter description in Create Tunnel
Window - Advanced Parameters Pane.
Attributes None.
Values:
Data ENABLE
DISABLE

Example <OAM>CREATED_BY_AAA</OAM>
<GEN_ALARMS>
<GEN_ALARMS>
The Generate Tunnel Alarms state for a tunnel; see the parameter
Description description in Create Tunnel Window - Advanced Parameters
Pane.
Attributes None.
Values:
Data ENABLE
DISABLE

Example <GEN_ALARMS>VPNSTR</GEN_ALARMS>
<COMMENTS>
<COMMENTS>
Comments attached to the tunnel; see parameter description in
Description
Create Tunnel Window - Basic Parameters Pane.
Attributes None.
Data Free string.
Constraints None.
Example <COMMENTS>xxxxx</COMMENTS>

< STATE>
< STATE>
Tunnel state; see parameter description in Create Tunnel Window -
Description
Status Parameters Pane.
Attributes None.
Values:
OK
Data NA
INCOMPLETE
INCONSISTENT
Constraints None.
Example <STATE>OK</STATE>
<MPLS_LABEL>
<MPLS_LABEL>
MPLS label of the tunnel; see parameter description in Create
Description
Tunnel Window - General Parameters Pane.
Attributes None.
Data Free string.
Constraints None.
Example <MPLS_LABEL>332</ MPLS_LABEL >

<ENDPOINTS_LIST>
<ENDPOINTS_LIST>
Contains trails endpoints data divided into paths according to the

Description main or protection paths; see Create Tunnel Window - Endpoints
and Path.
Attributes None.
Data None.
Child elements Path

<ENDPOINTS_LIST>
<ENDPOINT>...</ENDPOINT>
Example
<ENDPOINT>...</ ENDPOINT >
</ENDPOINTS_LIST>
<ENDPOINT>
<ENDPOINT>
Contains information about the endpoints of a tunnel path; see
Description
Create Tunnel Window - Endpoints and Path.
ROLE
Attributes Description Role of current endpoint
Expected values HEAD or TAIL or TRANSIT
Data None
Child elements <PE>,<IN_TP> or <OUT_TP>
Must contain the “ROLE” attribute.
Constraints
Must contain at least one of each child element.
<ENDPOINT ROLE="HEAD">
<PE>XDM_24</PE>
Example
<OUT_TP>I3-MoT-1</OUT_TP >
</ENDPOINT>

<IN_TP>
<IN_TP>
“Drop” or “Sink” endpoint of the tunnel. Contains the information
Description
required to create the identifier of an endpoint.
Attributes
Data None
Constraints
Example <IN_TP>I3-MoT-1</IN_TP >
<OUT_TP>
<OUT_TP>
“Add” or “Source” endpoint of the tunnel. Contains the
Description
information required to create the identifier of an endpoint.
Attributes None.
Data None.
Constraints None.
Example <OUT_TP>I3-MoT-1</OUT_TP >
<BRANCHES>
<BRANCHES>
Contains information on all tunnel paths; see Create Tunnel
Description
Window - Path pane.
Attributes None.
Data None.
Child elements <BRANCH>
Constraints
<BRANCHES>
<BRANCH>...</BRANCH>
Example
<BRANCH>...</BRANCH>
</BRANCHES>

<BRANCH>
<BRANCH>
Description Contains information on one tunnel path.

Attributes None.
Data None.
Child elements <DESTINATION_NODE><NODES_LIST>
Constraints
Examples <BRANCH>
<DESTINATION_NODE>XDM_25</ DESTINATION_NODE>
<NODES_LIST>
…
…
</NODES_LIST>
</BRANCH>
<DESTINATION_NODE>
<DESTINATION_NODE>
Description Indicates the "Drop" or "Sink" element of the branch.

Attributes None.
Data Free string.
Constraints
Example <DESTINATION_NODE>XDM_25</DESTINATION_NODE>

<NODES_LIST>
<NODES_LIST>
Description Contains Identifiers of all nodes in the branch.

Attributes None.
Data None.
Child elements <NODE>
Constraints
<NODES_LIST>
<NODE>
Example ..
</NODE>
</NODES_LIST>
<NODE>
<NODE>
These tags contain the relative distinguishable name of an endpoint

Description
in the database.
Role.
Attributes Description: The role of the node in the tunnel.
Values: "HEAD" or "TAIL" or "TRANSIT"
Data None.
Child elements <PE><MOT_PORT>
Constraints None.
<NODE>
<PE>XDM_23825</PE>
Example <MOT_PORT>I3-MoT-1</MOT_PORT>
</NODE>
<PE>
<PE>
Description User label of a PE.

Attributes None.
Data Free string.
Constraints None.
Example <PE> XDM_23888</PE>

<MOT_PORT>
<MOT_PORT>
Description Identifies the MoT port.

Attributes None.
Data None.
Constraints None.
Example <MOT_PORT>I3-MoT-1<MOT_PORTS>

Example XML File for Tunnels

The following is an example of an XML file for creating MPLS tunnels.
<!DOCTYPE XML_TRAFFIC SYSTEM "/opt/NMS/server/etc/TEIMXMLStruct.dtd">
<XML_TRAFFIC>
<TUNNEL OPERATION="CREATE" ID="1:2">
<INFO>
<NAME>xxxxxx</NAME>
<CUSTOMER>Bill Ind.</CUSTOMER>
<DIRECTION>UNIDIRECTIONAL</DIRECTION>
<TYPE>P2P</TYPE>
<PROTECTION>UNPROTECTED</PROTECTION>
<VPN_DEDICATED>DISABLE</VPN_DEDICATED>
<P2P_DEDICATED>DISABLE</P2P_DEDICATED >
<COS>COS0</COS>
<BW>3000</BW>
<OAM>DISABLE</OAM>
<GEN_ALARMS>DISABLE</GEN_ALARMS>
<COMMENTS>….</ COMMENTS >
<STATE>OK</STATE>
<MPLS_LABEL>16</ MPLS_LABEL >
</INFO>
<ENDPOINTS_LIST>
<ENDPOINT ROLE="HEAD">
<PE>XDM_24</PE>
<OUT_TP>I3-MoT-1</OUT_TP>
</ENDPOINT>
<ENDPOINT ROLE="TAIL">
<PE>XDM_25</PE>
<OUT_TP>I3-MoT-1</OUT_TP>
</ENDPOINT>
</ENDPOINTS_LIST>
<BRANCHES>
<BRANCH>
<DESTINATION_NODE>XDM_25</DESTINATION_NODE>
<NODES_LIST>
<NODE ROLE="HEAD">
<PE>XDM_24</PE>
<MOT_PORT>I3-MoT-1</MOT_PORT>
</NODE>

<NODE ROLE="TAIL">
<PE>XDM_25</PE>
<MOT_PORT>I3-MoT-1</MOT_PORT>
</NODE>
</NODES_LIST>
</BRANCH>
</TUNNEL>
</XML_TRAFFIC>
Service Syntax and Examples

The following sections show the tags used in LightSoft for services as
predefined by the DTD, and an example XML file for services.
| Service Syntax Details
| Example XML File for Services
Service Syntax Details

designed so that the XML file provides full information of a LightSoft Ethernet
service and of the operations that you can perform on it (create, edit, and so
on).
The following sections show the tags used in LightSoft for services, as
predefined by the DTD.
NOTE:
<INFO> tag, <NAME>...</NAME> must occur before
<TYPE>...</TYPE>.
tag names (for example, "SERVICE"). This should be
understood as a shorthand for the full element content (for
example, SERVICE...</SERVICE>).

<XML_TRAFFIC>
<XML_TRAFFIC>
Description Root element of the tunnel/service file.

Attributes None.
Data None.
Child elements TUNNEL
This tag is the root of an XML file. Therefore, it must appear at the
Constraints beginning of the body, right after the header. It must contain at
least one child element.
<XML_TRAFFIC>
<SERVICE>
...
</SERVICE>
Example
<SERVICE>
...
</SERVICE>
<XML_TRAFFIC>

<SERVICE>
<SERVICE>
The beginning of an XML trail. It contains all the trail's data, the
Description
operation that will be performed on the service, and the service's ID.
OPERATION
The operation that will be performed on the
Description
service.
Preset optional operation values:
CREATE
Expected values DELETE
Attributes
EDIT
EDIT_ATTRIBUTES
ID

A string of structure “station id:service id”.
Expected values
Example: “1:2”
Data None.
Child elements <INFO><ENDPOINTS_LIST>
The Operation attribute must be included.

If the operation is edit, edit attributes or delete, the “id” attribute must
Constraints be included.
No child elements must be used. This depends on the operation made
on the trail and the information you wish to operate with.
<SERVICE OPERATION="CREATE" ID="1:1">
<INFO>...</INFO>
Example
</SERVICE>

<INFO>
<INFO>
DescriptionGeneral information about the trail.

Attributes None.
Data None.
<NAME>,<CUSTOMER>,<ADMIN_SERVICE>,<TYPE>,<FIB_QUOTA>
Child <POLICER_NAME>,<DEDICATED_TUNNELS_ONLY>,
elements <PROTECTED_TUNNELS_ONLY>,<AUTO_SVLAN_REG>,<DUAL_HOMING>
<OPERATIONAL_STATE>
Constraints
<INFO>
<NAME>...</NAME>
<ADMIN_SERVICE>...</ADMIN_SERVICE>
<TYPE>...</TYPE>
<FIB_QUOTA>...</FIB_QUOTA>
Example <POLICER_NAME>...</POLICER_NAME>
<DEDICATED_TUNNELS_ONLY>...</DEDICATED_TUNNELS_ONLY>
<PROTECTED_TUNNELS_ONLY>...</PROTECTED_TUNNELS_ONLY>
<AUTO_SVLAN_REG>...</AUTO_SVLAN_REG>
<DUAL_HOMING>...</DUAL_HOMING>
<OPERATIONAL_STATE>...</OPERATIONAL_STATE>
</INFO>
<NAME>
<NAME>
Defines the service name; see Label in Create Service Window -
Description
Attributes None.
Data None.
Child Elements None.
Constraints <NAME>Service-1407</NAME>
Example

<ADMIN_SERVICE>
<ADMIN_SERVICE>
Indicates the service is enabled in the network; see
Description Administrative Service Enable checkbox in Create Service
Attributes None.
Values:
Data ENABLE
DISABLE
Constraints None.
Example <ADMIN_SERVICE>ENABLE</ ADMIN_SERVICE >
<TYPE>
<TYPE>
Indicates the service type; see Type in Create Service Window -
Description
Attributes None.
Values:
UNDEFINED
POINT_TO_POINT
MULTIPOINT_TO_MULTIPOINT
Data ROOTED_MULTIPOINT
HUB_AND_SPOKE
LAYER1_P2P
SHARED_LINE
SHARED_LAN
Constraints None.
Example <TYPE>POINT_TO_POINT</TYPE>

<FIB_QUOTA>
<FIB_QUOTA>
Maximum number of MAC addresses that can be learnt per VSI
Description supporting the service; see vFIB Quota in Create Service
Attributes None.
Data Free string
Constraints
Example <FIB_QUOTA>133</ FIB_QUOTA >
<POLICER_NAME>
<POLICER_NAME>
Name of the policer profile associated with the service; see
Description Profile in Create Service Window - Policer Profiles List
Columns.
Attributes None.
Data Free string.
Example <POLICER_NAME>Policer142</POLICER_NAME >
<DEDICATED_TUNNELS_ONLY>
<DEDICATED_TUNNELS_ONLY>
Indicates that the service will be carried on Single Service Only
Description tunnels with bandwidth specifically configured for this service;
see Create Service Window - Advanced Parameters Pane.
Attributes None.
Values:
Data ENABLE
DISABLE
Constraints
<DEDICTED_TUNNELS_ONLY>ENABLE</
Example
DEDICTED_TUNNELS_ONLY >

<PROTECTED_TUNNELS_ONLY>
<PROTECTED_TUNNELS_ONLY>
Indicates that the service can only use protected tunnels; see Create
Description
Service Window - Advanced Parameters Pane.
Attributes None.
Values:
Data ENABLE
DISABLE
Constraints
<PROTECTED_TUNNELS_ONLY>ENABLE</
Example
PROTECTED_TUNNELS_ONLY >
<AUTO_SVLAN_REG>
<AUTO_SVLAN_REG>
Automatically adds the S-VLAN registration to the virtual link as
part of the EoS trail creation process and downloads it
automatically to each existing service in the PB network for
Description
service discrimination purposes; see Automatic S-VLAN
Registration Enabled checkbox in Create Service Window -
Provider Bridge Networks Pane.
Attributes None.
Values:
Data ENABLE
DISABLE
Constraints
Example <AUTO_SVLAN_REG>ENABLE</AUTO_SVLAN_REG>

<DUAL_HOMING>
<DUAL_HOMING>
Indicates the choice of dual homed service type; see Dual Homed
Description Service checkbox in Create Service Window - Advanced
Parameters Pane.
Attributes None.
Values:
UNDEFINED
Data NOT_DUAL_HOMED
INTER_NETWORK
ACCESS_LINK

Constraints
Example <DUAL_HOMING>NOT_DUAL_HOMED</DUAL_HOMING>
<OPERATIONAL_STATE>
<OPERATIONAL_STATE>
LightSoft indicates if the service is considered Up, Down, or
Description Unknown; see Service State in Create Service Window - Service
Status Pane.
Attributes None.
Values:
Data ENABLE
DISABLE

Constraints
Example <OPERATIONAL_STATE>ENABLE</OPERATIONL_STATE>

<ENDPOINTS_LIST>
<ENDPOINTS_LIST>
Contains trails endpoints data divided into paths according to the
Description main or protection paths; see Create Service Window - Endpoint
List Pane.
Attributes None.
Data None.
Child elements Path

<ENDPOINTS_LIST>
Example
</ENDPOINTS_LIST>
<ENDPOINT>
<ENDPOINT>
DescriptionContains information about the endpoints of a tunnel path.
None.
Attributes ROLE (optional) LEAF,ROOT,HUB,SPOKE
Data None
<FE>,<PORT>,<VLAN_IDS>,<INGRESS_LIST>,<EGRESS_LIST>
Child ,<IGMP_SNOOPING_MODE>,<IGMP_MEMBERSHIP_INTERVAL>,
elements
<LMQT_INTERVAL>,<FWD_ALL>,<IP_ADDRESS_LIST>
Constraints

<ENDPOINT>
<ENDPOINT ROLE=LEAF>
<FE>XDM_24</FE>
<PORT>I3-MoT-1</PORT>
<VLAN_IDS>
<INGRESS_LIST>
<INGRESS>
…
</INGRESS>
…
</INGRESS_LIST>
Example <EGRESS_LIST>
…
</ EGRESS_LIST>
<IGMP_SNOOPING_MODE>DISABLE</IGMP_SNOOPING_MODE>
<IGMP_MEMBERSHIP_INTERVAL>260</IGMP_MEMBERSHIP_INTERVAL>
<LMQT_INTERVAL>10</LMQT_INTERVAL>
<FWD_ALL>ENABLE</FWD_ALL>
<IP_ADDRESS_LIST>
<IP>224.0.1.3</IP>
</IP_ADDRESS_LIST>
</ENDPOINT>
<FE>
<FE>
Description
Attributes
Data None
Constraints
Example <FE>XDM_24</FE>

<VLAN_IDS>
<VLAN_IDS>
Lists the VLAN IDs associated with frames connected to the
Description
service; see VLANs Pane
Attributes None.
Data None.
Constraints None.
Example <VLAN_IDS>321</ VLAN_IDS>
<INGRESS_LIST>
<INGRESS_LIST>
Description
Attributes None.
Data None.
Child elements <INGRESS>
Constraints
<INGRESS_LIST>
<INGRESS>...</INGRESS>
Example
<INGRESS>...</INGRESS>
</INGRESS_LIST>

<INGRESS>
<INGRESS>
Description
Attributes None.
Data None.
<POLICER_NAME>,<POLICING_STATE>,<COS>,
Child elements
<PRIORITY>
Constraints
<INGRESS>
<POLICER_NAME>policer12</POLICER_NAME>
<POLICING_STATE>POLICING</POLICING_STATE>
Examples
<COS>COS0<COS>
<PRIORITY>1</PRIORITY>
</INGRESS>
<POLICER_STATE>
<POLICER_STATE>
Policing status of the currently assigned policer profile; see
Description
Policing Status in Create Service Window - Policers Pane.
Attributes None.
Values:
UNDEFINED
Data BLOCKING
NO_RATE_LIMIT
POLICING
Constraints
Example <POLICER_STATE>POLICING</POLICER_STATE >

<COS>
<COS>
Description CoS mapping per priority in the Ingress; see CoS Mapping Pane.
Attributes None.
Values:
COS0
COS1
COS2
Data COS3
COS4
COS5
COS6
COS7
Constraints None.
Example <COS>LABEL</COS>
<PRIORITY>
<PRIORITY>
Description Priority mapping per CoS in the Egress; see CoS Mapping Pane.
Attributes
Data None.
Constraints None.
Example <PRIORITY>1</PRIORITY>

<EGRESS_LIST>
<EGRESS_LIST>
Description
Attributes None.
Data
Child elements <EGRESS>
Constraints
<EGRESS_LIST>
<EGRESS>
…
</EGRESS>
Example
<EGRESS>
…
</EGRESS>
</EGRESS_LIST>
<EGRESS>
<EGRESS>
Description
Attributes None.
Data None.
Child elements <PRIORITY>,<COS>
Constraints
<EGRESS>
<PRIORITY>…</PRIORITY>
Example
<COS>…</COS>
</EGRESS>

<IGMP_SNOOPING_MODE>
<IGMP_SNOOPING_MODE>
When enabled, Multicast Addresses are learnt through IGMP Snooping;

Description see IGMP Snooping Enable checkbox in Create Service Window -
Multicast Pane.
Attributes None.
Values:
Data ENABLE
DISABLE
Child
None.
elements
Constraints None.
Example <IGMP_SNOOPING_MODE>DISABLE</IGMP_SNOOPING_MODE>
<IGMP_MEMBERSHIP_INTERVAL>
<IGMP_MEMBERSHIP_INTERVAL>
IGMP Group Membership Interval; see Membership Interval in Create
Description
Service Window - Multicast Pane.
Attributes None.
Data Free string.
Child
None.
elements
Constraints None.
Example <IGMP_MEMBERSHIP_INTERVAL>260</IGMP_MEMBERSHIP_INTERVAL>
<LMQT_INTERVAL>
<LMQT_INTERVAL>
Last Member Query Time; see Create Service Window - Multicast
Description
Pane.
Attributes None.
Data Free string.
Constraints None.
Example < LMQT_INTERVAL>10</LMQT_INTERVAL>

<FWD_ALL>
<FWD_ALL>
Description
Attributes None.
Values:
Data ENABLE
DISABLE
Constraints None.
Example < FWD_ALL>ENABLE</FWD_ALL>
<IP_ADDRESS_LIST>
<IP_ADDRESS_LIST>
Description
Attributes None.
Data None.
Child elements <IP>
Constraints None.
< IP_ADDRESS_LIST>
Example …
</IP_ADDRESS_LIST>
<IP>
<IP>
Description
Attributes None.
Data Free string.
Constraints None.
Example <IP>224.0.1.3</IP>

Example XML File for Services

The following is an example of an XML file for creating Ethernet services.
>>
?xml version="1.0"?>>
<!DOCTYPE XML_TRAFFIC SYSTEM "/opt/NMS/server/etc/TEIService.dtd">
<XML_TRAFFIC>
<SERVICE OPERATION="EDIT" ID="54">
<INFO>
<NAME>p2mp</NAME>
<CUSTOMER>eci</CUSTOMER>
<ADMIN_SERVICE>ENABLE</ADMIN_SERVICE>
<TYPE>HUB_AND_SPOKE</TYPE>
<FIB_QUOTA>100</FIB_QUOTA>
<POLICER_NAME>policer453</POLICER_NAME>
<DEDICATED_TUNNELS_ONLY>DISABLE</DEDICATED_TUNNELS_ONLY>
<PROTECTED_TUNNELS_ONLY>DISABLE</PROTECTED_TUNNELS_ONLY>
<AUTO_SVLAN_REG>ENABLED</AUTO_SVLAN_REG>
<DUAL_HOMING>NOT_DUAL_HOMED</DUAL_HOMING>
<OPERATIONAL_STATE>UNDEFINED</OPERATIONAL_STATE>
</INFO>
<ENDPOINTS_LIST>
<ENDPOINT ROLE="HUB">
<FE>XDM_24-I3-24</FE>
<PORT>I3-ETY-o2-17</PORT>
<VLAN_IDS>457</VLAN_IDS>
<INGRESS_LIST>
<INGRESS>
<POLICER_NAME></POLICER_NAME>
<POLICING_STATE>BLOCKING</POLICING_STATE>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>

<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
</INGRESS_LIST>
<EGRESS_LIST>
<EGRESS>
<COS>COS0</COS>
</EGRESS>
<EGRESS>

<COS>COS1</COS>
</EGRESS>
<EGRESS>
<COS>COS2</COS>
</EGRESS>
<EGRESS>
<COS>COS3</COS>
</EGRESS>
<EGRESS>
<COS>COS4</COS>
</EGRESS>
<EGRESS>
<COS>COS5</COS>
</EGRESS>
<EGRESS>
<COS>COS6</COS>
</EGRESS>
<EGRESS>
<COS>COS7</COS>
</EGRESS>
</EGRESS_LIST>
<IGMP_SNOOPING_MODE>*UNDEFINED*</IGMP_SNOOPING_MODE>
<FWD_ALL>*UNDEFINED*</FWD_ALL>
</ENDPOINT>
<ENDPOINT ROLE="SPOKE">
<FE>XDM_25-I3-25</FE>
<INGRESS_LIST>
<INGRESS>

<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>

<COS>COS0</COS>
</INGRESS>
</INGRESS_LIST>
<EGRESS_LIST>
<EGRESS>
<COS>COS0</COS>
</EGRESS>
<EGRESS>
<COS>COS1</COS>
</EGRESS>
<EGRESS>
<COS>COS2</COS>
</EGRESS>
<EGRESS>
<COS>COS3</COS>
</EGRESS>
<EGRESS>
<COS>COS4</COS>
</EGRESS>
<EGRESS>
<COS>COS5</COS>
</EGRESS>
<EGRESS>
<COS>COS6</COS>
</EGRESS>
<EGRESS>
<COS>COS7</COS>
</EGRESS>
</EGRESS_LIST>

</ENDPOINT>
</ENDPOINTS_LIST>
</SERVICE>
<SERVICE OPERATION="EDIT" ID="44">
<INFO>
<NAME>
</NAME>
<CUSTOMER>
</CUSTOMER>
<ADMIN_SERVICE>ENABLE</ADMIN_SERVICE>
<TYPE>ROOTED_MULTIPOINT</TYPE>
<FIB_QUOTA>100</FIB_QUOTA>
<POLICER_NAME>shiry</POLICER_NAME>
<DEDICATED_TUNNELS_ONLY>DISABLE</DEDICATED_TUNNELS_ONLY>
<PROTECTED_TUNNELS_ONLY>DISABLE</PROTECTED_TUNNELS_ONLY>
<AUTO_SVLAN_REG>ENABLED</AUTO_SVLAN_REG>
<DUAL_HOMING>UNDEFINED</DUAL_HOMING>
<OPERATIONAL_STATE>DISABLED</OPERATIONAL_STATE>
</INFO>
<ENDPOINTS_LIST>
<ENDPOINT ROLE="ROOT">
<FE>XDM_24-I3-24</FE>
<INGRESS_LIST>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>

<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
</INGRESS_LIST>
<EGRESS_LIST></EGRESS_LIST>
<IGMP_MEMBERSHIP_INTERVAL>*UNDEFINED*</IGMP_MEMBERSHIP_INTERVAL>
<LMQT_INTERVAL>*UNDEFINED*</LMQT_INTERVAL>
</ENDPOINT>

<ENDPOINT ROLE="LEAF">
<FE>XDM_25-I3-25</FE>
<INGRESS_LIST>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>

<INGRESS>
<COS>COS0</COS>
</INGRESS>
<INGRESS>
<COS>COS0</COS>
</INGRESS>
</INGRESS_LIST>
<EGRESS_LIST></EGRESS_LIST>
<IGMP_SNOOPING_MODE>DISABLE</IGMP_SNOOPING_MODE>
<FWD_ALL>DISABLE</FWD_ALL>
</ENDPOINT>
</ENDPOINTS_LIST>
</SERVICE>
</XML_TRAFFIC>


C
Report Generation using
SQL and LightSoft
In this appendix:
Overview ........................................................................................................ C-1
Using SQL to Generate Reports ..................................................................... C-1
Using the LightSoft Report Generator .......................................................... C-82
Overview
A wide variety of queries on the LightSoft database can be performed using
standard SQL; see Using SQL to Generate Reports.
The LightSoft report generator is also available to accommodate special cases
where queries using Versant SQL may be limited by database thresholds or
other factors; see Using the LightSoft Report Generator.
Using SQL to Generate Reports

The LightSoft SQL interface enables you to perform queries in its database.
Queries may be performed in the current LightSoft database or from a copy of
the database (such as produced using RDR or another method).
Besides SQL queries that can be written, the LightSoft database supports
common on-line connectivity interface via JDBC. The proprietary Versant
utilities isql and sqldump can be used to export data using the standard SQL
query mechanism. You can otherwise write a JAVA program using the JDBC
interface and on-line access to nms_db or its offline substitute (copy of
nms_db).
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary C-1

Report Generation using SQL and LightSoft LightSoft User Manual
NOTES:
The command line of every SQL program should include the
script name RunVsql.sh followed by the program name and
program parameters. Refer to the examples in this section.
All customer utilities and other programs using the JDBC
interface (such as Link Shifter) should be run exactly in the
same way as Versant SQL utilities (see the dbdump example,
below).
Heavy queries may impact the performance of LightSoft, so a
copy of the database should be used for this purpose.
The LightSoft SQL interface is based on the Versant/VSQL object database. It

enables you to create relational views of the database and access data.
This section describes the main elements of the SQL, including its parameters,
SQL data type, and a short description of each parameter. The SQL syntax used
is Versant's DBMS.
LightSoft SQL supports three working modes:
| Online work with the misql utility.
| SQL batch requests (Versant utility using misql)
| SQL export (Versant utility using dbdump)
The SQL export produces comma-separated fields and is well suited for import
into other applications. Predefined SQL lists are available to facilitate querying
the database for reports or specific queries.
OPTIONAL FEATURE: The SQL interface is a fully integrated

add-on capability, available on a cost basis. If not purchased,
querying of the LightSoft database via SQL is not possible.
SQL online request

SQL request samples may be run in directory /opt/NMS/server/sql/sql or any
other directory with write permissions.
The command format is:
RunVsql.sh misql -u <user_Name> -a <password> <db_name>
For example:
RunVsql.sh misql -u nms -a nms_pwd nms_db
C-2 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual Report Generation using SQL and LightSoft
SQL batch request

SQL request samples may be run in directory /opt/NMS/server/sql/sql or any
other directory with write permissions.
RunVsql.sh misql -s <sql_request_file> -u <user_Name> -
a <password> <db_name>
For example:
RunVsql.sh misql -s s_ME.sql -u nms -a nms_pwd nms_db
Additional examples of SQL batch requests are installed in the directory:
/opt/NMS/server/sql/sqlSelects
SQL export
SQL dbdump samples may be run in directory /opt/NMS/server/sql/sqlDump
or any other directory with write permissions.
RunVsql.sh dbdump -f <dbdum_record_definition_file> -u
<user_Name> -a <password> <db_name>
For example:
RunVsql.sh dbdump -f d_ME.sql -u nms -a nms_pwd nms_db
Additional examples of the SQL export requests are installed in the directory:
/opt/NMS/server/sql/sqlDump
WARNING: In SQL requests read locks are granted in the

LightSoft database. These can disturb normal operation. To
prevent this, do one of the following:
When you begin working with the misql utility, execute
the command SET TRANSACTION ISOLATION
LEVEL O.
OR
After every select request in the misql utility, execute the
command COMMIT WORK. You can use either of the
above options or both. For additional details about these
commands, consult the Versant SQL Reference Manual.
OR
Query from a copy of the active LightSoft database.

SQL Tables Summary

The following are LightSoft-specific SQL tables.
NOTES:
Table names are case sensitive - all characters should be
entered using lower case only. Parameter names are not case-
sensitive and can be entered using any case combination.
Many attributes are stored in the database as enumeration
values. A query of the database will return both the
enumeration value and the text mapped to the enumeration
value. When querying the database using the Select
command, use the enumeration value, not the mapped text.
For rate, link rate, port rate, and trail rate enumeration types,
the database contains a table of the enumeration value and its
text. The database supports a query to return the entire list of
enumerated values for these enumeration types and their
associated text strings. For other enumeration types, you can
select the desired table to then find the list of values and
mapped texts currently in use.
EMS (v_ems)
Table Description
EMS (v_ems) Contains a list of all EMSs managed by
LightSoft.
Group Tables
Table Description
Topology group (v_group) Contains nested topology groups created by
the user, and a key to parent groups.
ME group (v_megroup) Joins the tables of MEs and Groups. Used to
retrieve MEs from a topology group.
Subgroup (v_subgroup) Joins the tables of subgroups and groups. Used
to retrieve subgroups that are members of a
topology group.
ME and UME Tables
Table Description
ME (v_me) Contains a list of MEs.
ME rates (v_merates) Contains a list of layered rates supported per
ME.
UME (v_ume) Contains a list of UMEs. Also used to retrieve
UME members from a topology group.

Topology Segment Tables
Table Description
Topology segment (v_tlsegment) Contains a list of topology links (segments) in
LightSoft.
SRLG (v_tlsrlg) Contains a list of Shared Risk Link Groups
(SRLGs).
Source/Sink topology link endpoints Joins the tables of endpoints and topology
(v_tlsegpoints) links.
VC-4 Group Info List
4 Contains a list of VC-4 groups per port
(v_vc4groupinfolist) (Physical Termination Point, PTP).
Ports Tables
Table Description
Ports (v_ports) Contains a list of all connected and free ports,
also called PTPs. Ethernet ports are not
included in the list.
Ports native location Retrieves the location of ports as displayed in
(v_portsnativelocation) the LightSoft tree.
SDH ports (v_sdhsonetports) Contains a list of ports that appear on the SDH
layer and are SDH ports.
WDM ports (v_wdmports) Contains a list of ports that appear on the
optical (WDM) layer.
Ethernet ports (v_ethernetports) Contains a list of ports that appear on the
Ethernet topology layer.
CTP Tables
Table Description
CTPs (v_ctp) Contains a list of all connected and free
Connection Termination Points (CTPs) in the
LightSoft.
Colored CTPs (v_coloredctp) Contains a list of colored CTPs that have
enabled FEC overhead or a tuned frequency.
Matrix FD (v_matrixfd)
Table Description
Matrix FD (v_matrixfd) table) Represents Layer 2 data switch cards which
may be PB or PE (for example MCS/M cards).

FDFr (v_fdfr)
Table Description
FDFr (v_fdfr) table Represents connectively between flow points
that are components of the Ethernet service.
Ethernet Service and MPLS Tunnel Tables
Table Description
Ethernet service (v_serviceflow) Table of Ethernet services that appear in
LightSoft's Ethernet Service list.
Ethernet service endpoints Shows endpoints of Ethernet services.
(v_serviceflowendpoints)
Ethernet service PB networks Shows the PB networks traversed by an
(v_sf_svlanlist) Ethernet service.
Ethernet service tunnels Shows the tunnels used by an Ethernet service.
(v_serviceflowovertunnel)
MPLS working tunnels Shows the working MPLS tunnels (may be
(v_wrkmplstunnel) protected or unprotected).
MPLS working tunnel P2P destination Shows the destination nodes for P2P MPLS
nodes tunnels.
MPLS working tunnel paths Shows the working MPLS tunnel paths. The
(v_wrkmplstunnelpath) tunnels may be protected or unprotected.
MoT links (v_motlinks) Shows the join table to find MoT links
traversed by working tunnels.
MPLS bypass tunnels Shows the MPLS bypass tunnels.
(v_bpsmplstunnel)
Policer Profiles (v_policerprofiles)
4 Contains the list of all policer profiles in
LightSoft and their parameters.
Burst Storming Policer Profile Services Contains the list of services using burst
4
(v_servicebspolicers) storming policer profiles with names of these

profiles.
NNI Services Ingress Traffic Mapping Contains the ingress part of the traffic
4
(v_servicennitmtableingress) mapping table for NNI services.

NNI Services Egress Traffic Mapping
4 Contains the egress part of the traffic mapping
(v_servicennitmtableegress) table for NNI services.
UNI Services Ingress Traffic Mapping Contains the ingress part of the traffic
4
(v_serviceunitmtableingress) mapping table for UNI services.

UNI Services Egress Traffic Mapping
(v_serviceunitmtableegress) table for UNI services.

Trail Tables
Table Description
Trail (v_trail) Contains a list of trails in LightSoft.
Trail endpoints (v_trailendpoints) Retrieves the endpoints of a trail.
Trail endpoints path type Contains a list of trail endpoints (CTPs).
(v_trailendpointspathtype)
Trail transit CTPs path type Contains a list of transit CTPs belonging to
(v_trailtransitctpspathtype) trails and transit CTP path types.
Forward and backward trail path Contains unidirectional resources of a trail.
connection (v_trailforwarddir,
v_trailbackwarddir)
Forward and backward trail path Contains unidirectional resources of a trail
connection lite (v_trailforwarddirlite, using an abridged format to improve
v_trailbackwarddirlite) performance in large databases.
Trail Dependency R1 Contains trail dependencies.
(v_traildependency_r1)
Trail time slots (v_trailtimeslots) Contains a list of time slots allocation per trail.
Trail in segment R1 Contains a list of high-level trails per segment.
(v_trailinsegment_r1) A high-level trail is a trail of the highest order,
which is passed in the topology segment.
Technology Layer Tables
Table Description
Primary logical elements Contains a list of all primary LEs. Also used
(v_techmasterle) to retrieve LE members from a topology
group.
Secondary logical elements Contains a list of all created secondary LEs.
(v_techsplitle) Also used to retrieve secondary LE members
from a topology group.
Logical elements PTP (v_techleptp) Retrieves ports from an LE.
Alarm Tables
Table Description
Alarm (v_alarm) Contains a list of all alarms in the database
(represents all alarms in the Event Log).
Alarm notes (v_alarmnotes) Retrieves notes attached to alarms.
Internal alarms (v_alarminternal) Contains all alarms generated by LightSoft.
External alarms (v_alarmexternal) Contains all alarms in the Event Log received
from LightSoft.
Alarm-affected TP list (v_alarmtplist) Retrieves TPs affected by an alarm as reported
by LightSoft.

Protection Group-Related Tables
Table Description
Protection Group (v_pg) Contains a list of MS Linear and MS-SPRing
protection groups.
Protection Group TP (v_tppg) Contains a list of TPs belong to protection
groups.
Protection TP for MS-SPRing protection Contains a list of protect TPs for MS-SPRing
group (v_protecttpmspringpg) protection groups.
Preemptive TP for MS-SPRing Contains a list of preemptive TPs for MS-
protection group SPRing protection groups.
(v_preemptivetpmspringpg)
Protection Group affected TP Contains a list of TPs affected by protection
(v_affectedtppg) groups.
NUT TP for MS-SPRing protection Contains a list of NUT TPs for MS-SPRing
group (v_ nuttpmspringpg) protection groups.
Help Tables
Table Description
Layer rate (t_layerrate) Contains a list of all layer rates.
Probable cause (t_probablecause) Contains a list of probable alarm causes.
Port link rate (t_portlinkrate) Contains a list of all port link rates.
Trail rate (t_trailrate) Contains a list of all trail rates.
Associated topology layer Contains a list of associated topology layers.
(t_assoctpglayer)
Flex reason (t_flexreason) Translates (or maps) Flex code to text strings.
NE type (t_netype) Contains a list of NE types.
Security operation (t_securityoperation) Contains a list of security operations.
Log Tables
Table Description
Activity log (v_activitylog) Contains a list of activity log records.
Security log (v_securitylog) Contains a list of security log records.
Security Tables
Table Description
User group capability Contains a list of user groups with profiles and
(v_vpnusergroupcapability) operations.
User (v_vpnuser) Contains a list of users per group.

Domain Tables
Table Description
Exclusive Operator Resource Domains Contains the resource domains of network
4
(v_cnmvpndomain) operators of type Exclusive (CNM).

Shareable Operator Resource Domains Contains the list of regional network operator
(v_regionvpndomain) groups with the domain list per group.
Service Provider VPN domain Contains the resource domains of the SP
(v_spvpndomain) (service provider) network operator.
EMSs of Exclusive Resource Domains Contains EMSs assigned to resource domains
(v_vpncnmresdomainems) of type Exclusive (CNM).
EMSs of Shareable Resource Domains Contains EMSs assigned to resource domains
(v_vpnregionresdomainems) of type Shareable (Regional).
MEs of Exclusive Resource Domains Contains the MEs assigned to resource
(v_vpncnmresdomainme) domains of type Exclusive (CNM).
MEs of Shareable Resource Domains contains MEs assigned to resource domains of
(v_vpnregionresdomainme) type Shareable (Regional).
UMEs of Exclusive Resource Domains Contains the UMEs assigned to resource
(v_vpncnmresdomainume) domains of type Exclusive (CNM).
UMEs of Shareable Resource Domains Contains the UMEs assigned to resource
(v_vpnregionresdomainume) domains of type Shareable (Regional).
PTPs of Exclusive Resource Domains Contains the ports (PTPs) assigned to resource
(v_vpncnmresdomainptp) domains of type Exclusive (CNM).
PTPs of Shareable Resource Domains Contains the ports (PTPs) assigned to resource
(v_vpnregionresdomainptp) domains of type Shareable (Regional).
CTPs of Exclusive Resource Domains Contains the high order CTPs assigned to
(v_vpncnmresdomainctp) resource domains of type Exclusive (CNM).
CTPs_of_Shareable_Resource_Domains Contains the high order CTPs assigned to
(v_vpnregionresdomainctp) resource domains of type Shareable
(Regional).

Functional Description of SQL Tables

The following sections describe the SQL data types and their associated
parameters.
EMS (v_ems)
This table contains a list of all EMSs managed by LightSoft.
Parameter name SQL data type Description

InstanceId VARCHAR EMS instance ID
EmsId VARCHAR Object distinguished name (DN)
UserLabel VARCHAR Operator's name for the EMS
NativeName VARCHAR Host name of EMS
EmsVersion VARCHAR EMS version
EmsType VARCHAR EMS product type
EmsIPAddress VARCHAR EMS network address in “dot” notation
Location VARCHAR NE geographical location
IsManagedCode SMALLINT EMS managed state
IsManaged CHAR EMS managed state
EmsStateCode SMALLINT EMS connection state
EmsState CHAR EMS connection state
X_pos REAL X coordinate of the EMS icon on the map
Y_pos REAL Y coordinate of the EMS icon on the map
Comment VARCHAR User free text
Number_MEs INT Number of MEs managed by the EMS
Group Tables
For information about groups in LightSoft, see Working with Groups. This
section contains the following tables:
Table Description
Topology group (v_group) Contains nested topology groups created by
the user, and a key to parent groups.
ME group (v_megroup) Joins the tables of MEs and Groups. Used to
retrieve MEs from a topology group.
Subgroup (v_subgroup) Joins the tables of subgroups and groups. Used
to retrieve subgroups that are members of a
topology group.

Topology Group (v_group)

Table of the nested topology groups created by the user. Contains a key to
parent groups. To retrieve group members, use the corresponding tables for
Subgroups, MEs, UMEs and LEs.

InstanceId VARCHAR Group instance ID
UserLabel VARCHAR Label assigned by user
GroupTypeCode INT Group type (Admin or Site)
GroupType CHAR Group type
GroupFunctionTypeCode INT Type of group function
GroupFunctionType CHAR Type of group function
IconName VARCHAR Name of the icon used for the group
X_pos REAL X coordinate of the Group icon on the
map
Y_pos REAL Y coordinate of the Group icon on the
map
Parent VARCHAR Group containing this group
ME Group (v_megroup)
This table joins the MEs and Groups tables. Use it to retrieve MEs from a
topology group.

UserLabel VARCHAR Group label
MEId VARCHAR ME object DN
MEUserLabel VARCHAR ME user label
MEInstanceId VARCHAR ME instance Id
To obtain ME data, write the SQL request as follows:

SELECT
<list of fields>
FROM
v_megroup
,v_me
WHERE
v_megroup.MEInstanceId = v_me.InstanceId;

To obtain Group data, write the SQL request as follows:

SELECT
<list of fields>
FROM
v_megroup
,v_group
WHERE
v_megroup.InstanceId = v_group.InstanceId;
Subgroup (v_subgroup)
This table joins subgroups and groups. It is used to retrieve subgroups that are
members of a topology group.

UserLabel VARCHAR User label of the subgroup
SubGroupUserLabel VARCHAR Subgroup user label
SubGroupInstanceId VARCHAR Subgroup instance ID
To obtain subgroup data, write the SQL request as follows:

SELECT
<list of fields>
FROM
v_subgroup
,v_group
WHERE
v_subgroup.SubGroupInstanceId = v_group.InstanceId;

ME and UME Tables

For information about MEs in LightSoft, see Working with MEs. For
information about UMEs in LightSoft, see Working with UMEs. This section
contains the following tables:
Table Description
ME (v_me) Contains a list of MEs.
ME rates (v_merates) Contains a list of layered rates supported per
ME.
UME (v_ume) Contains a list of UMEs. Also used to retrieve
UME members from a topology group.
ME (v_me)
This table lists MEs.

InstanceId VARCHAR ME instance ID
MEId VARCHAR Object DN
NativeName VARCHAR Name in EMS
NetworkAddress VARCHAR NE's address in “dot” notation
IsGatewayCode SMALLINT Is gateway or not
IsGateway CHAR Is gateway or not
ExistInEMSCode SMALLINT Actual existing state
ExistInEMS CHAR Actual existing state
MEVersion VARCHAR ME software/hardware version
ProductName VARCHAR NE's product/type name
SubNetName VARCHAR Name of the subnet used by the ME
UserLabel VARCHAR Operator's name for the NE
Location VARCHAR User-entered geographical location of the
NE
METypeCode INT ME type
METype CHAR ME type
X_pos REAL X coordinate of the icon on the map
Y_pos REAL Y coordinate of the icon on the map
TimingSrc VARCHAR Timing source
TimingSrcType INT Timing source type
Code
TimingSrcType CHAR Timing source type


TimingSrcWest VARCHAR West timing source
TimingSrcTypeWestCode INT West timing source type
TimingSrcTypeWest CHAR West timing source type
GroupInstanceId VARCHAR Group instance ID
GroupName VARCHAR MEs containing a site group
ME Rates (v_merates)
This table contains a list of layered rates supported per ME.

InstanceId VARCHAR ME instance ID
MEId VARCHAR ME DN
RateCode SMALLINT Supported rates of t_layerrate
Rate CHAR Supported rates
To obtain ME data, write the SQL request as follows:

SELECT
<list of fields>
FROM
v_me
,v_merates
WHERE
v_me.InstanceId = v_merates.InstanceId;
UME (v_ume)
This is the table of UMEs. It is also used to retrieve UME members from a
topology group.

InstanceId VARCHAR UME Instance ID
UMETypeCode INT UME's template type
UMEType CHAR UME's template type
Location VARCHAR User-entered geographical location of the
UME


X_pos REAL X coordinate of the icon on the map
Y_pos REAL Y coordinate of the icon on the map
GroupInstanceId VARCHAR UMEs containing group instance IDs
GroupName VARCHAR UMEs containing a group
Topology Segment Tables

For information about topology links in LightSoft, see Topology Links and
Ports. This section contains the following tables:
Table Description
Topology segment (v_tlsegment) Contains a list of topology links (segments) in
LightSoft.
SRLG (v_tlsrlg) Contains a list of Shared Risk Link Groups
(SRLGs).
Source/Sink topology link endpoints Joins the tables of endpoints and topology
(v_tlsegpoints) links.
VC-4 group info list Contains a list of VC-4 groups per port
(v_vc4groupinfolist) (Physical Termination Point, PTP).
Topology Segment (v_tlsegment)

This table lists topology links (segments) in LightSoft. The SRLG attributes of
a link are retrieved using the v_tlsrlg table. Endpoints of a link are retrieved
using v_tlsegpoints.
NOTE: This table does not include virtual links.

InstanceId VARCHAR Topological segment instance ID
TLSegPointsId VARCHAR Link to the sink/source points
(TLSegPointsId ==
TLSegPoints::InstanceId)
DirectionCode INT Direction
Direction CHAR Direction
EdgeDirectionalityCode INT Path direction
EdgeDirectionality CHAR Path direction
CreationTime_Year SMALLINT Year of creation
CreationTime_Month SMALLINT Month of creation
CreationTime_Day SMALLINT Day of creation


CreationTime_Hour SMALLINT Hour of creation
CreationTime_Minute SMALLINT Minute of creation
ProtectionQualityCode INT Protection quality
ProtectionQuality CHAR Protection quality
PathLength INT Length of the segment in km/mi
Grade_Cost INT Cost of the segment
UserDefinedQuality INT Quality of the segment
LinkProtectionQualityCode INT Link protection quality
LinkProtectionQuality CHAR Link protection quality
RateCode SMALLINT Rate t_layerrate
Rate CHAR Rate
TpgLinkId VARCHAR Physical topology link object DN
MediaTypeCode INT Media type
MediaType CHAR Media type
MediaSubType VARCHAR Additional specification of the
media type (for example, fiber type)
AssociatedLayerTypeCode INT Associated technology layer
AssociatedLayerType CHAR Associated technology layer
ExistInEMSCode SMALLINT Exists in EMS
ExistInEMS CHAR Exists in EMS
Ring Name VARCHAR Ring name
Dispersion REAL Dispersion
SpanLoss REAL Span loss

SRLG (v_tlsrlg)
This table contains a list of SRLGs. You can retrieve all SRLGs of a topology
link using tpgLinkId as a key.

InstanceId VARCHAR Topological link instance ID.
TpgLinkId VARCHAR Physical topological link object DN.
SRLGName VARCHAR SRLG/duct name inserted into LightSoft
from the GUI for a topological link. One
topology link can pass through several
SRLGs.
UserLabel VARCHAR User label.
Source/Sink Topology Link Endpoints

(v_tlsegpoints)
This table joins the endpoints and topology links tables.

InstanceId VARCHAR TLSegment instance ID
PTPInstanceId VARCHAR PTP (port) instance ID (InstanceId
TLSement::TLSegPointsId)
DirectionType CHAR Direction type (Src/Snk)
To obtain link endpoints data, write the VSQL request as

follows:
SELECT
v_tlsegpoints.InstanceId
,v_tlsegpoints.PTPInstanceId
,v_tlsegpoints.DirectionType
,RPAD(v_ports.PTPId,70) AS ‘PTP Id’
,RPAD(v_ports.NativeName,30) AS ‘Native Name’
,RPAD(v_ports.UserLabel,30) AS ‘UserLabel’
,v_ports.ConnectionStateCode
,v_ports.ConnectionState
,v_ports.DirectionalityCode
,v_ports.Directionality
,v_ports.EdgePointCode
,v_ports.EdgePoint
,v_ports.Location
,v_ports.RateCode
,v_ports.Rate
,v_ports.LOSwitchCapableCode
,v_ports.LOSwitchCapable

,v_ports.HOSwitchCapableCode
,v_ports.HOSwitchCapable
,v_ports.VirtualConcatCapableCode
,v_ports.VirtualConcatCapable
,v_ports.PortRateCode
,v_ports.PortRate
FROM
v_tlsegpoints
,v_ports
WHERE
v_tlsegpoints.PTPInstanceId = v_ports.InstanceId;
VC-4 Group Info List (v_vc4groupinfolist)

This table contains a list of VC-4 groups per port (PTP). Applicable to
SYNCOM NEs where VC-4 group information is not the same as in the AU4
timeslot.

TLSegInstanceId VARCHAR TLSeg instance ID
TpgLinkId VARCHAR DN of TpgLink
PTPInstanceId VARCHAR PTP Instance Id (InstanceId
TLSegPoints::InstanceId or
Ports::InstanceId)
PTPId VARCHAR PTPoObject DN
GroupId SMALLINT Internal VC-4 group ID
VC4Id SMALLINT VC-4 ID

Ports Tables
For information about ports in LightSoft, see Topology Links and Ports. This
section contains the following tables:
Table Description
Ports (v_ports) Contains a list of all connected and free ports,
also called PTPs. Ethernet ports are not
included in the list.
Ports native location Retrieves the location of ports as displayed in
(v_portsnativelocation) the LightSoft tree.
SDH ports (v_sdhsonetports) Contains a list of ports that appear on the SDH
layer and are SDH ports.
WDM ports (v_wdmports) Contains a list of ports that appear on the
optical (WDM) layer.
Ethernet ports (v_ethernetports) Contains a list of ports that appear on the
Ethernet topology layer.
Ports (v_ports)
This is the table of ports, also called PTPs. It contains all ports except for
Ethernet. The following tables have additional attributes that apply to specific
port types.

InstanceId VARCHAR PTP instance ID
PTPId VARCHAR Object DN
UserLabel VARCHAR Name of port
ConnectionStateCode INT Connection state
ConnectionState CHAR Connection state
DirectionalityCode INT Directionality
Directionality CHAR Directionality
EdgePointCode SMALLINT Subnetwork edge
EdgePoint CHAR Subnetwork edge
Location INT Location
RateCode SMALLINT Rate of t_layerrate
Rate CHAR Rate
UnManagedTPCode SMALLINT Unmanaged TP indicator
UnManagedTP CHAR Unmanaged TP indicator
ExistInEMSCode SMALLINT Exists in the EMS
ExistInEMS CHAR Exists in the EMS


LOSwitchCapableCode SMALLINT Is capable of low order SNCP switch
LOSwitchCapable CHAR Is capable of low order SNCP switch
HOSwitchCapableCode SMALLINT Is capable of high order SNCP
switch
HOSwitchCapable CHAR Is capable of high order SNCP
switch
VirtualConcatCapableCode SMALLINT Does port support C2V functionality
VirtualConcatCapable CHAR Does port support C2V functionality
AssocTpgLayerCode SMALLINT Associated topology layer
AssocTpgLayer CHAR Associated topology layer
PortRateCode INT Port rate of t_portlinkrate
PortRate CHAR Port rate
MediaTypeCode SMALLINT Media type
Ports Native Location (v_portsnativelocation)

This table retrieves the location of a port as displayed in the LightSoft tree.

PtpInstanceId VARCHAR PTP instance ID
NativeLocation VARCHAR Holder (Slot)
To obtain PTP data, write the SQL request as follows:

SELECT
<list of fields>
FROM
v_portsnativelocation
,v_ports
WHERE
v_portsnativelocation.PtpInstanceId = v_ports.InstanceId;

SDH Ports (v_sdhsonetports)

This table contains a list of SDH ports that appear in the SDH layer.
NOTE: Ports with AssocTpgLayer contain the substring

"SDH".

RateCode SMALLINT Rate
Rate CHAR Rate
LOSwitchCapableCode SMALLINT Is capable of low order SNCP switch
LOSwitchCapable CHAR Is capable of low order SNCP switch
HOSwitchCapableCode SMALLINT Is capable of high order SNCP switch
HOSwitchCapable CHAR Is capable of high order SNCP switch
VirtualConcatCapableCode SMALLINT Does port support C2V functionality
VirtualConcatCapable CHAR Does port support C2V functionality
PortRateCode INT Port rate
FECOverheadCode SMALLINT FEC enabled
FECOverhead CHAR FEC enabled
TunedFrequency REAL Tuned frequency

WDM Ports (v_wdmports)

This table contains the list of ports in the optical (WDM) layer.
NOTE: Ports with AssocTpgLayer contain the substring

"WDM".

NativeName VARCHAR Name in the EMS
RateCode SMALLINT PTP rate
Rate CHAR PTP rate
MAXNumberOCH INT Number of OCH channels
FrequencyBandCode SMALLINT Frequency band
FrequencyBand CHAR Frequency band
TunedFrequency REAL Tuned frequency

Ethernet Ports (v_ethernetports)

This table lists the ports that appear in the Ethernet topology layer.

RateCode SMALLINT PTP rate
Rate CHAR PTP rate
EthPortTypeCode SMALLINT Ethernet port type
EthPortType CHAR Ethernet port type
IsEnableLCASCode SMALLINT Is LCAS enabled (Y, N)
IsEnableLCAS CHAR Is LCAS enabled (Y, N)
ActiveCTPs SMALLINT Number of CTPs with payload active
TotalCTPs SMALLINT Total number of CTPs
RateGranularityCode SMALLINT Rate of CTPs: VC-4, VC-3, VC-12
RateGranularity CHAR Rate of CTPs: VC-4, VC-3, VC-12
SubnetworkID INT Subnetwork ID
RSTPEnabledCode INT RSTP-enabled state
RSTPEnabled CHAR RSTP-enabled state
RSTPCost INT RSTP cost
MatrixFDInstanceID VARCHAR MatrixFD instance ID

To obtain MatrixFD data, write the SQL request as follows:

SELECT
<list of fields>
FROM
v_matrixfd
,v_ethernetports
WHERE
v_matrixfd.EthernetPtpInstanceId = v_ethernetports.InstanceId;
CTP Tables
This section contains the following tables:
Table Description
CTPs (v_ctp) Contains a list of all connected and free
Connection Termination Points (CTPs) in the
LightSoft.
Colored CTPs (v_coloredctp) Contains a list of colored CTPs that have
enabled FEC overhead or a tuned frequency.
CTPs (v_ctp)
This table contains CTPs that are known in LightSoft.

InstanceId VARCHAR Instance ID
CTPId VARCHAR Object DN
ActualTermModeCode INT Actual termination mode
ActualTermMode CHAR Actual termination mode
ExpectedTermModeCode INT Expected termination mode
ExpectedTermMode CHAR Expected termination mode
TimeSlot_RateCode SMALLINT Time slot
TimeSlot_Rate CHAR Time slot
ExpectedConnectStateCode INT Expected connection state
ExpectedConnectState CHAR Expected connection state


EdgePointCode SMALLINT Is edge of subnetwork
EdgePoint CHAR Is edge of subnetwork
RateCode SMALLINT Rate of t_layerrate
Rate CHAR Rate
ExistInEMSCode SMALLINT Actual existing state
ExistInEMS CHAR Actual existing state
MsprProtectTypeCode INT MS-SPRing protection type of
CTP
MsprProtectType CHAR MS-SPRing protection type of
CTP
Colored CTPs (v_coloredctp)

This table contains colored CTPs that have FEC overhead enabled or a tuned
frequency (for example, a WDM transceiver).

InstanceId VARCHAR Instance ID of CTPLayerParameter
CTPInstanceId VARCHAR Instance ID of CTP
TunedFrequency FLOAT Tuned frequency

Matrix FD (v_matrixfd)
This table represents Layer 2 data switch cards which may be PB or MPLS-PE
(for example MCS/M).
Parameter Name SQL Data Type Description

InstanceId VARCHAR Instance Id of MatrixFD
MatrixFDId VARCHAR Object DN (MTNM: name)
UserLabel VARCHAR User label
NativeEMSName VARCHAR Name in EMS
Owner VARCHAR Owner (MTNM: owner)
Customer VARCHAR Associated customer
NetworkID INT Network ID
StpRootPathCost INT Spanning tree cost
StpRootPort INT Id of the root of the current
spanning tree
StpDesignatedRoot VARCHAR Spanning tree designated root
StpDesignatedBridge VARCHAR Spanning tree designated bridge
BridgeTypeCode SMALLINT
BridgeType VARCHAR Decode eLsnBridgeType
SwitchingModeCODE SMALLINT
SwitchingMode VARCHAR Decode eSwitchingMode
SpanningTreeTypeCode SMALLINT
SpanningTreeType VARCHAR Decode eSpanningTreeType
ProviderBridgeNetworkID INT PB network ID
VPLSNetworkID INT MPLS network ID
PE_ID INT MPLS PE ID
PELabel VARCHAR
HighPriorityClass INT
Flexible VARCHAR Y/N
BridgePriority INT
PolicerRateType VARCHAR Rate 1 / Rate 2
FIB_Prov_Size INT
FIB_Actual_Size INT
ActualExistingStateCode SMALLINT Whether the object exists in the
EMS
ActualExistingState VARCHAR Indicates if the object exist in EMS


BridgeAddress VARCHAR MAC address
MEInstanceId VARCHAR Points to v_ME table
FuncElemInstanceId VARCHAR Points to v_fe table
FDFr (v_fdfr)
This table represents connectively between flow points that are components of
an Ethernet service. It enables you to retrieve the containing matrix FD and
end-to-end Ethernet service.

InstanceId VARCHAR Instance ID of MatrixFragmentFD
FdfrId VARCHAR Object DN (MTNM: name)
SVLanId SMALLINT SVlan Id
EthVpnId INT Ethernet VPN Id
VCLabel INT VC label
FDFrTypeCode SMALLINT FDFr type
FDFrType VARCHAR Decode Enum eFdfrType
VFibProvisionSize INT Maximum VFib
VFibActualSize INT Actual VFib number on upload time
BscPolicerId VARCHAR Policer name
BscPolicerCIR INT CIR value
BSCPolicerCBS INT CBS value
DualHomingCode SMALLINT 0/1
DualHoming VARCHAR Y/N

MatrixFDInstanceId VARCHAR Instance ID of MatrixFd
ServiceFlowInstanceID VARCHAR Instance ID of Ethernet service

To obtain matrix FD data, write the SQL request as follows:

SELECT
<list of fields>
FROM
v_matrixfd
,v_fdfr
WHERE
v_matrixfd.InstanceId = v_fdfr.MatrixFDInstanceId;
To obtain Ethernet service data, write the SQL request as

follows:
SELECT
<list of fields>
FROM
v_serviceflow

Ethernet Service and MPLS Tunnel Tables

For information about MPLS tunnels in LightSoft, see Provisioning MPLS
Tunnels. For information about Ethernet services in LightSoft, see Provisioning
Ethernet Services.
IMPORTANT NOTE:
For a technical reason, do not use ordered select statements
such as the following using parameters of type BIGINT:
select <fields list>
from <table name>
order by MplsTunnelId
MplsTunnelId is of type BIGINT and appears in the tables:
v_wrkmplstunnel, v_wrkmplsp2pdestnodes,
v_wrkmplstunnelpath, v_bpsmplstunnel.
UnderlyingTrailId is of type BIGINT and appears in the table:
v_motlinks.
Table Description
Ethernet service (v_serviceflow) Table of Ethernet services that appear in
LightSoft's Ethernet Service list.
Ethernet service endpoints Shows endpoints of Ethernet services.
Ethernet service PB networks Shows the PB networks traversed by an
(v_sf_svlanlist) Ethernet service.
Ethernet service tunnels Shows the tunnels used by an Ethernet service.
MPLS working tunnels Shows the working MPLS tunnels (may be
(v_wrkmplstunnel) protected or unprotected).
MPLS working tunnel P2P destination Shows the destination nodes for P2P MPLS
nodes tunnels.
MPLS working tunnel paths Shows the working MPLS tunnel paths. The
(v_wrkmplstunnelpath) tunnels may be protected or unprotected.
MoT links (v_motlinks) Shows the join table to find MoT links
traversed by working tunnels.
MPLS bypass tunnels Shows the MPLS bypass tunnels.
(v_bpsmplstunnel)
4 Contains the list of all policer profiles in
LightSoft and their parameters.
Burst Storming Policer Profile Services Contains the list of services using burst
4
(v_servicebspolicers) storming policer profiles with names of these

profiles.

Table Description
NNI Services Ingress Traffic Mapping Contains the ingress part of the traffic
4
(v_servicennitmtableingress) mapping table for NNI services.

(v_servicennitmtableegress) table for NNI services.
UNI Services Ingress Traffic Mapping Contains the ingress part of the traffic
4
(v_serviceunitmtableingress) mapping table for UNI services.

(v_serviceunitmtableegress) table for UNI services.
Ethernet Service (v_serviceflow)

This table contains the Ethernet services that appear in LightSoft's Ethernet
service list.

InstanceId VARCHAR Instance Id of Ethernet service
Customer VARCHAR Customer
ServiceTypeCode INT Service type
ServiceType VARCHAR Decodes eServiceType
ServiceStateCode INT Service state
ServiceState VARCHAR Decodes eServiceOperationState
EthVpnId INT Ethernet VPN Id
VFIBQuota INT Maximum FIB Quota
IsDedicatedTunnelsOnly VARCHAR Dedicated tunnels only
IsProtectedTunnelsOnly VARCHAR Protected tunnels only
DualHomingCode SMALLINT Dual homing code
DualHoming VARCHAR Decodes eAppDualHoming
CreatedBy VARCHAR Application with which the
service was created
CreationTime_Year SMALLINT Creation year
CreationTime_Month SMALLINT Creation month
CreationTime_Day SMALLINT Creation day
CreationTime_Hour SMALLINT Creation hour
CreationTime_Min SMALLINT Creation minute
ModifiedBy VARCHAR Application with which the
service was last modified
LastModTime_Year SMALLINT Modified year
LastModTime_Month SMALLINT Modified month


LastModTime_Day SMALLINT Modified day
LastModTime_Hour SMALLINT Modified hour
LastModTime_Min SMALLINT Modified minute
Ethernet Service Endpoints

This table shows endpoints of Ethernet services.

InstanceId VARCHAR Instance ID of Ethernet service
EthVpnId INT Ethernet VPN ID
ServiceFlowUserLabel VARCHAR User assigned service name
EPInstanceId VARCHAR Instance Id of EP – Ethernet CTP
EPId VARCHAR EP DN
EPNativeName VARCHAR Ethernet CTP EMS Native name
EPVlanIds VARCHAR VLAN ID list of this EP
Ethernet Service PB Networks (v_sf_svlanlist)

This table contains the PB networks traversed by an Ethernet service.

UserLabel VARCHAR Ethernet service user label
PBNtwkInstanceId VARCHAR Instance ID PB Network
PBNLabel VARCHAR PB Network label
SVLanId INT SVLan ID in PB network
Ethernet Service Tunnels

This table contains the tunnels used by an Ethernet service.

ServiceFlowUserLabel VARCHAR Ethernet service user label
MplsTunnelInstanceId VARCHAR Instance ID of MPLS tunnel


MplsTunnelId BIGINT Tunnel ID
MplsTunnelMplsLabel INT MPLS label
TunnelName VARCHAR Tunnel label
MPLS Working Tunnels (v_wrkmplstunnel)

This table contains the working MPLS tunnels (may be protected or
unprotected).

MplsTunnelId BIGINT MPLS tunnel ID
TunnelName VARCHAR Tunnel name
TunnelCoS SMALLINT CoS (0-7)
TunnelType VARCHAR Decodes eTunnelPattern
TunnelProtCode INT This is the protection requested
TunnelProt VARCHAR Decodes eTunnelProtectionType
Directionality VARCHAR Decodes eTunnelDirectionality
TunnelStateCode SMALLINT Tunnel state code
TunnelState VARCHAR Decodes eTunnelState
Bw INT Bandwidth
AllocatedBw VARCHAR Allocated Bandwidth
UnresBw VARCHAR Unresolved Bandwidth
CreatedBy VARCHAR Application with which the tunnel was
created
CreateYear SMALLINT Creation year
CreateMonth SMALLINT Creation month
CreateDay SMALLINT Creation day
CreateHour SMALLINT Creation hour
CreateMin SMALLINT Creation minute
ModifiedBy VARCHAR Application with which the tunnel was
modified
ModYear SMALLINT Modified yead
ModMonth SMALLINT Modified month
ModDay SMALLINT Modified day
ModHour SMALLINT Modified hour
ModMin SMALLINT Modified minute
Comments VARCHAR Comments
IsOAMEnabled VARCHAR Whether OAM is enabled


IsVPNDedicated VARCHAR Y/N
IsP2PDedicated VARCHAR Y/N
SrcNodeInstanceId VARCHAR Points to v_matrixfd (Source node)
P2PDestNodeInstanceId VARCHAR Points to v_matrixfd if tunnel is P2P
(Destination node)
MPLS Working Tunnel P2P Destination Nodes

(v_wrkmplsp2pdestnodes)
This table contains the destination nodes for P2P MPLS tunnels.

IsP2PDedicated VARCHAR Y/N
SrcNodeInstanceId VARCHAR Points to v_matrixfd if tunnel is
P2P(Src point)
SrcId VARCHAR MFD DN
SrcUserLabel VARCHAR MFD user label
SrcNativeEMSName VARCHAR Name in EMS
SrcNetworkID INT Source Network ID
P2PDestNodeInstanceId VARCHAR Points to v_matrixfd if tunnel is
P2P (Destination point)
DestId VARCHAR MFD DN
DestUserLabel VARCHAR Destination user label
DestNativeEMSName VARCHAR Destination native EMS name
DestNetworkID INT Destination Network ID

MPLS Working Tunnel Paths

(v_wrkmplstunnelpath)
This table contains the working MPLS tunnel paths. The tunnels may be
protected or unprotected. For protected tunnels the protecting bypass tunnels
are defined in table v_ bpsmplstunnel.

SrcNodeInstanceId VARCHAR Points to v_matrixfd if tunnel is
P2P(Src point)
SrcId VARCHAR MFD DN
SrcUserLabel VARCHAR MFD user label
SrcNativeEMSName VARCHAR Name in EMS
SrcNetworkID INT Source Network ID
P2PDestNodeInstanceId VARCHAR Points to v_matrixfd if tunnel is
P2P(Destination point)
DestId VARCHAR MFD DN
DestUserLabel VARCHAR Destination user label
DestNativeEMSName VARCHAR Destination native EMS name
DestNetworkID INT Destination Network ID
BranchRoleCode INT Branch role code
BranchRole VARCHAR Decodes eTunnelRole
MOTLinkInstanceId VARCHAR Points to v_motlinks
MOTLinkLabel VARCHAR MoT link label
inPtpInstanceId VARCHAR Points to v_ethernetports
inPtpId VARCHAR EthernetPTP DN
inPtpLabel VARCHAR
outPtpInstanceId VARCHAR Points to v_ethernetports
outPtpId VARCHAR EthernetPTP DN
outPtpLabel VARCHAR
bpsTunnelInstanceId VARCHAR Points to v_bpstunnels
bpsTunnelId INT Bypass tunnel ID
bpsTunnelLabel VARCHAR Bypass tunnel label

MoT Links (v_motlinks)

This table contains the join table to find MoT links traversed by working
tunnels.

MOTLinkLabel VARCHAR MoT link label
UnderlyingTrailId BIGINT ID of underlying MoT trail
MPLS Bypass Tunnels (v_bpsmplstunnel)

This table contains the MPLS bypass tunnels.

InstanceId VARCHAR Instance ID of bpsmplstunnel
TunnelCoS SMALLINT CoS (0-7)
TunnelType VARCHAR Decodes eTunnelPattern
TunnelProtCode INT Tunnel protection code. Values are
Unprotected, Protected, Bypass
TunnelProt VARCHAR Decodes eTunnelProtectionType
Directionality VARCHAR Decodes eTunnelDirectionality
TunnelStateCode SMALLINT Tunnel state code
TunnelState VARCHAR Decodes eTunnelState
Bw INT Bandwidth
AllocatedBw VARCHAR Allocated Bandwidth
UnresBw VARCHAR Unresolved Bandwidth
CreatedBy VARCHAR Application with which the tunnel was
created
CreateYear SMALLINT Created year
CreateMonth SMALLINT Created month
CreateDay SMALLINT Created day
CreateHour SMALLINT Created hour
CreateMin SMALLINT Created minute
ModifiedBy VARCHAR Application with which the tunnel was
modified
ModYear SMALLINT Modified year
ModMonth SMALLINT Modified month


ModDay SMALLINT Modified day
ModHour SMALLINT Modified hour
ModMin SMALLINT Modified minute
Comments VARCHAR Comments
IsOAMEnabled VARCHAR OAM enabled for this tunnel
SrcNodeInstanceId VARCHAR Points to v_matrixfd (Source node)
DestNodeInstanceId VARCHAR Points to v_matrixfd (Destination node)
ProtectedPortID VARCHAR Points to v_ethernetports
ProtectedNodeID VARCHAR Points to v_matrixfd
NNHNodeID VARCHAR Node id of protected node for next next
hop protection
Points to v_matrixfd

This table contains the list of all policer profiles in LightSoft and their
parameters.

InstanceId VARCHAR Unique ID of policer profile
PolicerName VARCHAR Unique name of policer profile used in GUI
CIR INT Policer profile parameter
CBS INT Policer profile parameter
EIR INT Policer profile parameter
EBS INT Policer profile parameter
Burst Storming Policer Profile Services

(v_servicebspolicers)
This table contains the list of services using burst storming policer profiles with
names of these profiles.

InstanceId VARCHAR Unique ID of service
VpnId INT Ethernet VPN ID
ServiceLabel VARCHAR Name of service
PolicerId VARCHAR Unique ID of policer profile
PolicerName VARCHAR Name of policer profile

NNI Services Ingress Traffic Mapping

(v_servicennitmtableingress)
This table contains the ingress part of the traffic mapping table for NNI services.

PortId VARCHAR Unique ID of Ethernet PTP
PortLabel VARCHAR Name of of Ethernet PTP
vCoS INT CoS
PolicerName VARCHAR Unique name of policer profile

(v_servicennitmtableegress)
This table contains the egress part of the traffic mapping table for NNI services.

Priority INT Priority
CoSList INT CoS

UNI Services Ingress Traffic Mapping

(v_serviceunitmtableingress)
This table contains the ingress part of the traffic mapping table for UNI
services.

vCoS INT CoS
PolicerName VARCHAR Unique name of policer profile

(v_serviceunitmtableegress)
This table contains the egress part of the traffic mapping table for UNI services.

Priority INT Priority
CoSList INT CoS

Trail Tables
For information about trails in LightSoft, see Provisioning SDH and EoS/MoT
Trails. The following tables contain header information applying to a trail:
| Trail (v_trail)
| Trail endpoints (v_trailendpoints)
| Trail endpoints path type (v_trailendpointspathtype)
The following tables join the Trail Table to obtain the paths of a trail (for
example, for an unprotected bidirectional trail there is one forward and one
backward path):
| Forward and backward trail path connection (v_trailforwarddir,
v_trailbackwarddir)
| Forward and backward trail path connection lite (v_trailforwarddirlite,
v_trailbackwarddirlite)
Trail Dependency R1 (v_traildependency_r1) contains information about the
server trails used by a client trail.
Trail Time Slots (v_trailtimeslots) contains the time slots used for each server
trail found in the Trail Dependency Table.
Trail in Segment R1 (v_trailinsegment_r1) is used to determine the links
traversed by a trail by indicating, for each trail ID, which directed topology link
(segment) is used.
IMPORTANT NOTE:
For a technical reson, do not use ordered select statements
such as the following using parameters of type BIGINT:
select <fields list>
from <table name>
order by TrailID
TrailID is of type BIGINT and appears in the tables: v_trail,
v_trailbackwarddir, v_trailbackwarddirlite, v_trailforwarddir,
v_trailfarwarddirlite, v_trailinsegment_r1, v_trailtimeslots .

Table Description
Trail (v_trail) Contains a list of trails in LightSoft.
Trail endpoints (v_trailendpoints) Retrieves the endpoints of a trail.
Trail endpoints path type Contains a list of trail endpoints (CTPs).
Trail transit CTPs path type Contains a list of transit CTPs belonging to
(v_trailtransitctpspathtype) trails and transit CTP path types.
Forward and backward trail path Contains unidirectional resources of a trail.
connection (v_trailforwarddir,
v_trailbackwarddir)
Forward and backward trail path Contains unidirectional resources of a trail
connection lite (v_trailforwarddirlite, using an abridged format to improve
v_trailbackwarddirlite) performance in large databases.
Trail dependency R1 Contains trail dependencies.
(v_traildependency_r1)
Trail time slots (v_trailtimeslots) Contains a list of time slots allocation per trail.
Trail in segment R1 Contains a list of high-level trails per segment.
(v_trailinsegment_r1) A high-level trail is a trail of the highest order,
which is passed in the topology segment.
Trail (v_trail)
This table lists the trails in LightSoft.

InstanceId VARCHAR Unique object/instance ID
TrailFwdDirId VARCHAR Link to forward direction
(TrailFwdDirId ==
TrailPathConnection::InstanceId)
TrailBckDirId VARCHAR Link to backward direction
(TrailBckDirId ==
TrailPathConnection::InstanceId)
NmsWsId INT Workstation ID
TrailId BIGINT LightSoft identifier of the trail
Customer VARCHAR Customer name
TrailRateCode INT Rate from t_trailrate
TrailRate CHAR Rate
Payload VARCHAR Payload type
ProtLayerCode INT Protection layer
ProtLayer CHAR Protection layer
TrailStateCode INT Trail state


TrailState CHAR Trail state
CreatedBy INT Method used for creating the trail (for
example, GUI, XML)
EditedBy INT Method used for editing the trail
ServiceLevelCode INT Service level
ServiceLevel CHAR Service level
CreationTime_Year SMALLINT Year of creation
CreationTime_Month SMALLINT Month of creation
CreationTime_Day SMALLINT Day of creation
CreationTime_Hour SMALLINT Hour of creation
CreationTime_Min SMALLINT Minute of creation
LastModTime_Year SMALLINT Year of edit
LastModTime_Month SMALLINT Month of edit
LastModTime_Day SMALLINT Day of edit
LastModTime_Hour SMALLINT Hour of edit
LastModTime_Min SMALLINT Minute of edit
UserLabel VARCHAR Label of the trail
ProtectionQualityCode INT Protection quality
ProtectionQuality CHAR Protection quality
UserDefinedQuality INT Quality of the trail
IsServiceTrailCode SMALLINT Is service trail
IsServiceTrail CHAR Is service trail
VpnId VARCHAR VPN ID
EthernetServiceType SMALLINT Service type (Layer1, Layer2)
Code
EthernetServiceType VARCHAR Service type (Layer1, Layer2)
VCATSize INT VCAT size
DiverseRoutedCode SMALLINT Diverse routed (N, Y)
DiverseRouted VARCHAR Diverse routed (N, Y)
NumberOfRoutes INT Number of diverse routes
ViewOnLayer2Code SMALLINT View on Ethernet layer (N, Y)
ViewOnLayer2 VARCHAR View on Ethernet layer (N, Y)
FlexReasonCode SMALLINT Flex reason
FlexReason VARCHAR Flex reason


ProtectionCode SMALLINT Protection
Protection VARCHAR Protection
SharedMEs INT Shared MEs
SharedLinks INT Shared links
NumOfSharedSRLGs INT Number of shared SRLGs
SharedSRLGs VARCHAR List of shared SRLGs
SharedCards INT Number of shared cards
MSLinear INT MSP links
MSSPRingLinks INT MS-SPRing links
ExtraTrafficLinks INT Extra traffic links
DNINodes INT DNI nodes
DRIBridges INT DRI bridges
CurrentSNCPSwitchesCo SMALLINT Number of SNCPs in current layer
de
CurrentSNCPSwitches VARCHAR Number of SNCPs in current layer
UnderlyingSNCPsCode SMALLINT Number of SNCPs in underlying layer
UnderlyingSNCPs VARCHAR Number of SNCPs in underlying layer
LengthOfShortest INT Distance - shortest path
Route
INT Distance - shortest path ID. Value is
RouteIdOfShortestRoute {path number, Main, Protect}
LengthOfLongest INT Distance - longest path

Route
RouteIDOfLongest INT Distance - longest path ID
Route
MinHopsNumber INT Number of hops - shortest path
INT Number of hops - shortest path ID;
RouteIDOfMinHops
value is {path number, Main, Protect}
MaxHopsNumber INT Number of hops - longest path
RouteIDOfMaxHops INT Number of hops - longest path ID
CostOfMinCost INT Cost - cheapest path
INT Cost - cheapest path ID; value is {path
RouteIDOfMinCost
number, Main, Protect}
CostOfMaxCost INT Cost - most expensive path
RouteIDOfMaxCost INT Cost - most expensive path ID
WorstLinkQuality SMALLINT Worst link quality {1-5}

Trail Endpoints (v_trailendpoints)

This table retrieves the endpoints of a trail.

InstanceId VARCHAR Trail instance ID
CTPInstanceId VARCHAR Endpoint instance ID
CTPId VARCHAR Object DN
ActualTermModeCode INT Actual termination mode (for
example, AU4 terminated) in the
network
ActualTermMode CHAR Actual termination mode (for
network
ExpectedTermModeCode INT Termination mode (for example, AU4
terminated) in LightSoft
ExpectedTermMode CHAR Termination mode (for example, AU4
terminated) in LightSoft
ExpectedConnectStateCode INT Expected connection state
ExpectedConnectState CHAR Expected connection state
EdgePointCode SMALLINT Is edge of subnetwork
EdgePoint CHAR Is edge of subnetwork
RateCode SMALLINT Rate of v_layerrate
Rate CHAR Rate
DirectionType CHAR Aend/Zend

Trail Endpoints Path Type

This table contains a list of trail endpoints (CTPs).

TPConnectDataInstanceId VARCHAR TPConnectDataInstanceId
PathTypeCode INT Path type
PathType CHAR Path type
TrailInstanceId VARCHAR Trail instance ID
TrailUserLabel VARCHAR Trail user label
Trail Transit CTPs Path Type

(v_trailtransitctpspathtype)
This table contains a list of transit CTPs belonging to trails and transit CTP
path types.

TPConnectDataInstanceId VARCHAR TPConnectDataInstanceId
SncDirectionInstanceId VARCHAR
TrailInstanceId VARCHAR
Forward and Backward Trail Path Connection

(v_trailforwarddir, v_trailbackwarddir)
This table contains unidirectional resources of a trail.

TrailRateCode INT Trail rate
TrailRate CHAR Trial rate
TrailUserLabel VARCHAR User label


CTPId VARCHAR CTP object DN
ActualTermModeCode INT Actual termination mode (for
network
ActualTermMode CHAR Actual termination mode (for
example, is the AU4 terminated)
in the network
ExpectedTermMode INT Termination mode (for example,
Code AU4 terminated) in LightSoft
ExpectedTermMode CHAR Termination mode (for example,
AU4 terminated) in LightSoft
ExpectedConnectState INT Expected connection state
Code
ExpectedConnectState VARCHAR Expected connection state
Directionality VARCHAR Directionality
EdgePointCode SMALLINT Edge of subnetwork
EdgePoint CHAR Edge of subnetwork
DirectionType CHAR Direction type
TrailPathConnectionId VARCHAR Trail path connection ID

Forward and Backward Trail Path Connection Lite

(v_trailforwarddirlite, v_trailbackwarddirlite)
This table contains unidirectional resources of a trail using an abridged format
to improve performance in large databases.

TrailRate CHAR Trail rate
TrailUserLabel VARCHAR User label
DirectionType CHAR Direction type (Snk/Src)
TrailPathConnectionId VARCHAR Trail path connection ID
Trail Dependency R1 (v_traildependency_r1)

This table contains information about the server trails used by a client trail.
In V4 a new table and associated command sets are provided for better
performance. The previous table version v_traildependency and associated
commands are no longer recommended for use.

TrailUserLabel VARCHAR User-supplied label of the trail
OwnerTralInstanceId VARCHAR Trail instance ID of the containing trail (owner)
PathConnectDataInstanceId VARCHAR Path connection data instance ID
Route INT Route

To receive report or dump information, write SQL request

scripts as follows:
| For report execution, use the script described in:
s_TrailDependency_r1.sql
| For dump execution, use the scripts described in:
s_TrailDependency_r1ForDump.sql and d_TrailDependency_r1.sql (this
file is located in the Install directory path /opt/NMS/server/sql/sqlDump).
To receive report or dump results in UNIX, write UNIX

scripts as follows:
ExecSelTrailDep_r1.sh
| For dump execution, use the script described in:
ExecDumpTrailDep_r1.sh
These UNIX sh scripts are examples of query/dump execution and produce
full reports/dumps of this view.
The first time that the scripts are used, an error message such as "index
does not exist" is displayed. This error should be ignored.
Important Comments:
The v_traildependency_r1 table should be used in conjunction with the SQL
requests and UNIX sh scripts described in this section. This is because the
supplied command set contains SQL commands to remove data collected in
previous requests, produce information in additional tables, and build indexes
dynamically. Reports or dumps can be produced only after these steps are
performed. Global scripts that would select/dump information from all views
cannot be used.
If you wish to modify the provided SQL requests and UNIX sh scripts or use
them in your own requests (built on new additional tables or views), it is
important that all the original script/request commands be present and are used
in the same order. Only the requested files and parameters can be changed. In
the case of SQL commands (select, insert, delete, create index), only the
requested parameters and settings can be changed.
If you are running your own script of UNIX commands, it should be written in
the same way as the example scripts, ensuring that any data collected in
previous requests is removed at the beginning of execution.
When running a report, it is not sufficient to run misql with the script
d_TrailDependency_r1.sql (this file is located in the Install directory path
/opt/NMS/server/sql/sqlDump). You must also run dbtool as shown in the
UNIX script example ExecDumpTrailDep_r1.sql.

When running a dump, it is not sufficient to run dbdump with the script
s_TrailDependency_r1.sql. You must also run dbtool and misql commands as
shown in the UNIX script example ExecDumpTrailDep_r1.sh.
NOTE: The sh scripts described above cannot be used as

running commands of a RunVsql.sh script. For example, if
the following is run:
RunVsql.sh ExecSelTrailInSeg_r1.sh nms <password>
nms_db
An error message is displayed and the command is skipped.
s_TrailDependency_r1.sql
This SQL script is used to receive report information.
SPOOL TrailDependencyTable ON;
SET REPORT ON;
SET LINESIZE 600;
delete from t_WALeft;
commit work;
delete from t_WARight;
commit work;
insert into t_WALeft (TrInstanceId,
TrRate,
TrRateName,
TrUserLabel,
TrPathDirction,
TrPathType,
TrRoute,
TrPCDId )
select s.TrInstanceId,
s.TrRate,
s.TrRateName,
s.TrUserLabel,
s.TrPathDirction,
s.TrPathType,
s.TrRoute,
s.TrPCDId from v_TempTrailDependancyTableLeftPart s;
commit work;
insert into t_WARight (PCDInstanceId,
TrPCDInstanceId )
SELECT DBPathConnectData.SelfOID, DBTrailPath.m_OwnerPathOID

FROM DBPathConnectData JOIN DBTrailPath ON DBPathConnectData.m_OwnerOID

= DBTrailPath.SelfOID;
commit work;
create index t_WARight1_idx on t_WARight(PCDInstanceId);
commit work;
select
InstanceId
,TrailRateCode
,TrailRate
,TrailUserLabel
,DirectionCode
,Direction
,PathTypeCode
,PathType
,OwnerTrailInstanceId
,PathConnectDataInstanceId
,Route
FROM v_TrailDependency_r1;
SET REPORT OFF;
SPOOL OFF;
s_TrailDependency_r1ForDump.sql
This SQL script is used to receive dump information.
SET REPORT ON;
SET LINESIZE 600;
delete from t_WALeft;
commit work;
delete from t_WARight;
commit work;
insert into t_WALeft (TrInstanceId,
TrRate,
TrRateName,
TrUserLabel,
TrPathDirction,
TrPathType,
TrRoute,
TrPCDId )
select s.TrInstanceId,
s.TrRate,
s.TrRateName,
s.TrUserLabel,

s.TrPathDirction,
s.TrPathType,
s.TrRoute,
s.TrPCDId from v_TempTrailDependancyTableLeftPart s;
commit work;
insert into t_WARight (PCDInstanceId,
TrPCDInstanceId )
SELECT DBPathConnectData.SelfOID, DBTrailPath.m_OwnerPathOID
FROM DBPathConnectData JOIN DBTrailPath ON DBPathConnectData.m_OwnerOID
= DBTrailPath.SelfOID;
commit work;
create index t_WARight1_idx on t_WARight(PCDInstanceId);
commit work;
SET REPORT OFF;
ExecSelTrailDep_r1.sh
This UNIX script is used to receive report results in UNIX:
NOTE: $1, $2, $3 are UNIX script parameters, where:

$1 - user name
$2 - user password
$3 - data base name
#!/bin/sh
Usage()
{
echo "$0 <user_name> <passward> <db_name>"
exit 1
}
[ $# -lt 3 ] && Usage
[ $# -gt 3 ] && Usage
if [ -n "${TPEROOT:-}" ]; then
echo "ERROR: VSQL env already defined!"
exit 1
fi
dbtool -index -delete -btree t_waright pcdinstanceid $3
RunVsql.sh misql -u $1 -a $2 –s \
/opt/NMS/server/sql/sqlSelects/s_TrailDependency_r1.sql $3

ExecDumpTrailDep_r1.sh
This UNIX script is used to receive dump results in UNIX:

$1 - user name
$2 - user password
$3 - data base name
#!/bin/sh
Usage()
{
exit 1
}
[ $# -lt 3 ] && Usage
[ $# -gt 3 ] && Usage
exit 1
fi
dbtool -index -delete -btree t_waright pcdinstanceid $3
/opt/NMS/server/sql/sqlSelects/s_TrailDependency_r1ForDump.sql $3
RunVsql.sh dbdump –f \
/opt/NMS/server/sql/sqlDump/d_TrailDependancy_r1.sql -u $1 -a $2 $3

Trail Time Slots (v_trailtimeslots)

This table contains a list of time slot allocations per trail.

InstanceId VARCHAR Time slot instance ID
TrailInstId VARCHAR Trail instance ID
TrailId BIGINT LightSoft trail identifierl
I SMALLINT Time slot identification constants
J according to SDH definitions
K
L
M
RateCode SMALLINT Rate
Rate CHAR Rate
VCPath INT VC path
PathConnectDataInstanceIdVARCHAR Path connection data instance ID
Route INT Route
To get trail dependency data for a given time slot, write the
SQL request as follows:
SELECT
<list of fields>
FROM
v_traildependency
,v_trailtimesslots
WHERE
v_traildependency. PathConnectDataInstanceId = v_traildependency.
PathConnectDataInstanceId;

Trail in Segment R1 (v_trailinsegment_r1)

This table is used to determine the links traversed by a trail by indicating, for
each trail ID, which directed topology link (segment) is used. It contains a list
of high-level trails per segment. A high-level trail is a trail of the highest order,
which passes in the topology segment.
In V4 a new table and associated command sets are provided for better
performance. The previous table version v_trailinsegment and associated
commands are no longer recommended for use.

TrailRateCode INT Trail rate of t_trailrate
TrailUserLabel VARCHAR Trail label
RateCode SMALLINT Rate t_laterrate
Rate CHAR Rate
TpgLinkId VARCHAR Topological link object DN
VCPathTimeSlotListId VARCHAR Link to TimeSlotList table
(TimeSlotListId ==
TrailTimeSlots::InstanceId)
PathConnectData VARCHAR Path connection data instance ID
InstanceId
Route INT Route
To receive report or dump information, write SQL request

scripts as follows:
s_TrailInSegment_r1.sql
| For dump execution, use the scripts described in:
s_TrailInSegment_r1ForDump.sql and d_TrailInSegment_r1.sql (this file is
located in the Install directory path /opt/NMS/server/sql/sqlDump)

To receive report or dump results in UNIX, write UNIX

scripts as follows:
ExecSelTrailInSeg_r1.sh
| For dump execution, use the script described in:
ExecDumpTrailInSeg_r1.sh
These UNIX sh scripts are examples of query/dump execution and produce full
reports/dumps of this view.
The first time that scripts are used, an error message such as "index does not
exist" is displayed. This error should be ignored.
Important Comments:
The v_trailinsegment_r1 table should be used in conjunction with the SQL
requests and UNIX sh scripts described in this section. This is because the
supplied command set contains SQL commands to remove data collected in
previous requests, produce information in additional tables, and build indexes
dynamically. Reports or dumps can be produced only after these steps are
performed. Global scripts that would select/dump information from all views
cannot be used.
If you wish to modify the provided SQL requests and UNIX sh scripts or use
them in your own requests (built on new additional tables or views), it is
important that all the original script/request commands be present and are used
in the same order. Only the requested files and parameters can be changed. In
the case of SQL commands (select, insert, delete, create index), only the
requested parameters and settings can be changed.
If you are running your own script of UNIX commands, it should be written in
the same way as the example scripts, ensuring that any data collected in
previous requests is removed at the beginning of execution.
When running a report, it is not sufficient to run misql with the script
s_TrailInSegment_r1.sql. You must also run dbtool as shown in the UNIX
script example ExecDumpTrailInSeg_r1.sh.
When running a dump, it is not sufficient to run dbdump with the script
d_TrailInSegment_r1.sql (this file is located in the Install directory path
/opt/NMS/server/sql/sqlDump). You must also run dbtool and misql commands
as shown in the UNIX script example ExecDumpTrailInSeg_r1.sh.

NOTE: The sh scripts described above cannot be used as

running commands of a RunVsql.sh script. For example, if
the following is run:
RunVsql.sh ExecSelTrailInSeg_r1.sh nms <password>
nms_db
An error message is displayed and the command is skipped.
s_TrailInSegment_r1.sql
This SQL script is used to receive report information.
SPOOL TrailInSegmentTable ON
SET REPORT ON;
SET LINESIZE 600;
delete from t_TrSegWALeft;
commit work;
delete from t_TrSegWARight;
commit work;
insert into t_TrSegWALeft ( TrInstanceId,
TrWsId,
TrTrailId,
TrRate,
TrRateName,
TrUserLabel,
TrPathDirction,
TrPathType,
TrTimeSlotId,
TrPCDId,
TrRoute)
select s.WrTrInstanceId,
s.WrTrWsId,
s.WrTrTrailId,
s.WrTrRate,
s.WrTrRateName,
s.WrTrUserLabel,
s.WrTrPathDirction,
s.WrTrPathType,
s.WrTrTimeSlotId,
s.WrTrPCDId,
s.WrTrRoute from v_TempTrailInSegTableLeftPart s;
commit work;

insert into t_TrSegWARight ( PCDInstanceId,

LinkRate,
LinkRateName,
TrLinkId,
TrLinkName)
select DBPathConnectData.SelfOID
,DBPhysicalTpgLink.m_Rate
,layerrate.name
,DBPhysicalTpgLink.m_ObjectDN
,DBPhysicalTpgLink.m_NativeName
from
(((DBPathConnectData JOIN
DBTopologicalSegment
ON
DBPathConnectData.m_OwnerOID = DBTopologicalSegment.SelfOID
)
JOIN
DBPhysicalTpgLink
ON
DBTopologicalSegment.m_OwnerPathOID = DBPhysicalTpgLink.SelfOID
)
LEFT OUTER JOIN
t_layerrate layerrate
ON
DBPhysicalTpgLink.m_Rate = layerrate.code
);
commit work;
create index t_TrSegWARight_idx on t_TrSegWARight(PCDInstanceId);
commit work;
select
InstanceId
,NmsWsId
,TrailId
,TrailRateCode
,TrailRate
,TrailUserLabel
,DirectionCode
,Direction
,PathTypeCode
,PathType
,RateCode

,Rate
,TpgLinkId
,NativeName
,VCPathTimeSlotListId
,PathConnectDataInstanceId
,Route
FROM
v_TrailInSegment_r1;
SET REPORT OFF;
SPOOL OFF;
s_TrailInSegment_r1ForDump.sql
This SQL script is used to receive dump information.
SET REPORT ON;
SET LINESIZE 600;
delete from t_TrSegWALeft;
commit work;
delete from t_TrSegWARight;
commit work;
insert into t_TrSegWALeft ( TrInstanceId,
TrWsId,
TrTrailId,
TrRate,
TrRateName,
TrUserLabel,
TrPathDirction,
TrPathType,
TrTimeSlotId,
TrPCDId,
TrRoute)
select s.WrTrInstanceId,
s.WrTrWsId,
s.WrTrTrailId,
s.WrTrRate,
s.WrTrRateName,
s.WrTrUserLabel,
s.WrTrPathDirction,
s.WrTrPathType,
s.WrTrTimeSlotId,
s.WrTrPCDId,

s.WrTrRoute from v_TempTrailInSegTableLeftPart s;

commit work;
insert into t_TrSegWARight ( PCDInstanceId,
LinkRate,
LinkRateName,
TrLinkId,
TrLinkName)
select DBPathConnectData.SelfOID
,DBPhysicalTpgLink.m_Rate
,layerrate.name
,DBPhysicalTpgLink.m_ObjectDN
,DBPhysicalTpgLink.m_NativeName
from
(((DBPathConnectData JOIN
DBTopologicalSegment
ON
DBPathConnectData.m_OwnerOID = DBTopologicalSegment.SelfOID
)
JOIN
DBPhysicalTpgLink
ON
DBTopologicalSegment.m_OwnerPathOID = DBPhysicalTpgLink.SelfOID
)
LEFT OUTER JOIN
t_layerrate layerrate
ON
DBPhysicalTpgLink.m_Rate = layerrate.code
);
commit work;
create index t_TrSegWARight_idx on t_TrSegWARight(PCDInstanceId);
commit work;
SET REPORT OFF;

ExecSelTrailInSeg_r1.sh
This UNIX script is used to receive report results in UNIX:

$1 - user name
$2 - user password
$3 - data base name
#!/bin/sh
Usage()
{
exit 1
}
[ $# -lt 3 ] && Usage
[ $# -gt 3 ] && Usage
exit 1
fi
dbtool -index -delete -btree t_trsegwaright pcdinstanceid $3
/opt/NMS/server/sql/sqlSelects/s_TrailInSegment_r1.sql $3
ExecDumpTrailInSeg_r1.sh
This UNIX script is used to receive dump results in UNIX.

$1 - user name
$2 - user password
$3 - data base name
#!/bin/sh
Usage()
{
exit 1
}
[ $# -lt 3 ] && Usage
[ $# -gt 3 ] && Usage

exit 1
fi
dbtool -index -delete -btree t_trsegwaright pcdinstanceid $3
/opt/NMS/server/sql/sqlSelects/s_TrailInSegment_r1ForDump.sql $3
RunVsql.sh dbdump –f \
/opt/NMS/server/sql/sqlDump/d_TrailInSegment_r1.sql -u $1 -a $2 $3
Technology Layer Tables

For information about LEs in LightSoft, see Working with LEs. This section
Table Description
Primary logical elements Contains a list of all primary LEs. Also used
(v_techmasterle) to retrieve LE members from a topology
group.
Secondary logical elements Contains a list of all created secondary LEs.
(v_techsplitle) Also used to retrieve secondary LE members
from a topology group.
Logical elements PTP (v_techleptp) Retrieves ports from an LE.
Primary Logical Elements (v_techmasterle)

This table contains primary LEs. It is also used for retrieving LE members from
a topology group.
InstanceId VARCHAR Object/Instance ID

UserLabel VARCHAR LE label
TechnologyLayerCode INT Technology layer where the LE appears
TechnologyLayer CHAR Technology layer where the LE appears
Location VARCHAR User-supplied location
Comment VARCHAR Free text
LETypeCode INT LE type
LEType CHAR LE type
MEInstanceId VARCHAR Unique Object/Instance ID
MEID VARCHAR NE object DN - key to Underlying ME
X_pos REAL Icon X coordinate
Y_pos REAL Icon Y coordinate
GroupInstanceId VARCHAR Administrative group instance ID

Secondary Logical Elements (v_techsplitle)

This table contains created LEs. It is also used for retrieving secondary LE
members from a topology group.

InstanceId VARCHAR LE instance ID
UserLabel VARCHAR Label of the LE
TechnologyLayerCode INT Technology layer where the LE
appears
TechnologyLayer CHAR Technology layer where the LE
appears
Location VARCHAR User-supplied location
Comment VARCHAR Free text
LETypeCode INT LE type
LEType CHAR LE type
X_pos REAL Icon X coordinate
Y_pos REAL Icon Y coordinate
MasterLE VARCHAR ME user label - key to master LE
Logical Elements PTP (v_techleptp)

This table retrieves the ports of an LE.

InstanceId VARCHAR LE instance ID
UserLabel VARCHAR User-assigned label of the LE
PTPId VARCHAR PTP (port) object DN

Alarm Tables
For information about alarms in LightSoft, see Fault Management. This section
Table Description
Alarm (v_alarm) Contains a list of all alarms in the database
(represents all alarms in the Event Log).
Alarm notes (v_alarmnotes) Retrieves notes attached to alarms.
Internal alarms (v_alarminternal) Contains all alarms generated by LightSoft.
External alarms (v_alarmexternal) Contains all alarms in the Event Log received
from LightSoft.
Alarm-affected TP list (v_alarmtplist) Retrieves TPs affected by an alarm as reported
by LightSoft.
Time Attributes Formatting in Alarm Tables

The Alarm table contains several time/date attributes, such as AlarmTime,
ClearTime, and so on. The examples in this section use the AlarmTime
attribute.
Each time/date field contains a time/date value string with the format:
YYYYMMDDhhmmss.ms
Where:
YYYY - year, MM - month, DD - date, hh - hour, mm - minute, ss - second, ms
- millisecond.
To print the time/value field:

| From v_alarms, select AlarmTime.
The printed result is: 20060608140826.0
Versant SQL provides additional string formatting options. For example:
| Simple separated printing
From v_alarms, select substr(AlarmTime, 1,4), '.', substr(AlarmTime, 5,2),
'.', substr(AlarmTime, 7,2), ' ', substr(AlarmTime, 9,2), ':',
substr(AlarmTime, 11,2) ':', substr(AlarmTime, 13,2).
The printed result is: 2006.06.08 14:08:26
| American format of date/time
From v_alarms, select substr(AlarmTime, 5,2), '.', substr(AlarmTime, 7,2),
'.', substr(AlarmTime, 1,4), ' ', substr(AlarmTime, 9,2), ':',
substr(AlarmTime, 11,2) ':', substr(AlarmTime, 13,2).
The printed result is: 06.08.2006 14:08:26

| European format of date/time with time leading

From v_alarms, select substr(AlarmTime, 9,2), ':', substr(AlarmTime, 11,2)
':', substr(AlarmTime, 13,2), ' ', substr(AlarmTime, 7,2), '.',
substr(AlarmTime, 5,2), '.', substr(AlarmTime, 1,4), ' ', ;
The printed result is: 14:08:26 08.06.2006
Alarm (v_alarm)
This table contains the alarms in the database. It represents all the alarms in the
Event Log.

InstanceId VARCHAR Alarm instance ID
AlarmName VARCHAR Event name
AlarmTime VARCHAR EMS time
MEAlarmTime VARCHAR ME alarm time
EventTypeCode SMALLINT Definition of EventType
EventType CHAR Definition of EventType
ProbableCauseCode SMALLINT Definition of ProbableCause
ProbableCause CHAR Definition of ProbableCause
PerceivedSeverityCode INT Perceived severity
PerceivedSeverity CHAR Perceived severity
ObjectTypeCode INT Object type
ObjectType CHAR Object type
ObjectId VARCHAR Object DN
ServiceAffectingCode INT Service affecting
ServiceAffecting CHAR Service affecting
LayerRateCode SMALLINT Layer rate of t_layerrate
LayerRate CHAR Layer rate
IsAcknowledgedCode SMALLINT Whether alarm was acknowledged
IsAcknowledged CHAR Whether alarm was acknowledged
AckTime VARCHAR Time when acknowledged
AckUserName VARCHAR Name of user that performs
acknowledge
AdditionalText VARCHAR Additional alarm information
IsClearCode SMALLINT Whether alarm was cleared
IsClear CHAR Whether alarm was cleared
ClearTime VARCHAR Time the alarm was cleared


LastReportedStateCode SMALLINT Whether alarm state is the last
reported state or known to be the
current state
LastReportedState CHAR Whether alarm state is the last
reported state or known to be the
current state
NotifId VARCHAR Notification ID
Alarm Notes (v_alarmnotes)

This table retrieves notes attached to alarms.

InstanceId VARCHAR Note instance ID
AlarmInstanceId VARCHAR Alarm instance ID
NoteTime_Year SMALLINT Year when note was created
NoteTime_Month SMALLINT Month when note was created
NoteTime_Day SMALLINT Day when note was created
NoteTime_Hour SMALLINT Hour when note was created
NoteTime_Minute SMALLINT Minute when note was created
NoteText VARCHAR Text of the note
UserName VARCHAR Name of the LightSoft user who wrote the
note
Internal Alarms (v_alarminternal)

This table contains event log alarms generated by LightSoft.

InstanceId VARCHAR Internal alarm instance ID


LayerRateCode SMALLINT Layer rate
AckTime VARCHAR Time when acknowledged
AckUserName VARCHAR Name of user that acknowledged the
alarm
IsClearCode SMALLINT Whether alarm was cleared
IsClear CHAR Whether alarm was cleared
LastReportedStateCode SMALLINT Whether alarm state is the last reported
state or known to be the current state
LastReportedState CHAR Whether alarm state is the last reported
NmsTime VARCHAR LightSoft time
ProbableCauseQualifier VARCHAR Qualifier of the alarm used to make the
alarm; when combined with the DN,
rate, and probable cause, providing a
unique alarm identifier
External Alarms (v_alarmexternal)

This table contains alarms received from an EMS.

InstanceId VARCHAR External alarm instance ID
AlarmTime VARCHAR EMS time
MEAlarmTime VARCHAR ME alarm time


LayerRateCode SMALLINT Layer rate
AckTime VARCHAR Time when the alarm was
acknowledged
AckUserName VARCHAR Name of the user that acknowledged
the alarm
IsClearCode SMALLINT Whether the alarm was cleared
IsClear CHAR Whether the alarm was cleared
LastReportedStateCode SMALLINT Whether alarm state is the last reported
LastReportedState CHAR Whether alarm state is the last reported
NativeProbableCause VARCHAR Name of the probable cause of the
alarm in the EMS
ProbableCauseQualifier VARCHAR Qualifier of the alarm used to make the
alarm; when combined with the DN,
rate, and probable cause, providing a
unique alarm identifier
Alarm-Affected TP List (v_alarmtplist)

This table retrieves TPs affected by an alarm as reported by the EMS.

InstanceId VARCHAR Alarm instance ID
TPId VARCHAR Termination point object DN

Protection Group-Related Tables

These tables define protection groups and different types of PTPs used in
several protection cases (MSP Linear and MS-SPRing).
Table Description
Protection Group (v_pg) Contains a list of MS Linear and MS-SPRing
protection groups.
Protection Group TP (v_tppg) Contains a list of TPs belong to protection
groups.
Protection TP for MS-SPRing protection Contains a list of protect TPs for MS-SPRing
group (v_protecttpmspringpg) protection groups.
Preemptive TP for MS-SPRing Contains a list of preemptive TPs for MS-
protection group SPRing protection groups.
Protection Group affected TP Contains a list of TPs affected by protection
(v_affectedtppg) groups.
NUT TP for MS-SPRing protection Contains a list of NUT TPs for MS-SPRing
group (v_ nuttpmspringpg) protection groups.
Protection Group (v_pg)

This table contains a list of MS-Linear and MS-SPRing protection groups.

InstanceId VARCHAR PG Instance Id
PGId VARCHAR Object DN (MTNM: name)
NativeName VARCHAR Native name (MTNM: nativeName)
UserLabel VARCHAR PG user label (MTNM: userLabel)
PGTypeCode SMALLINT Value of PG type
PGType CHAR Definition of PG type mapped to
string using eProtectionGroupType
ProtSchemeStateCode SMALLINT Value of Protection Scheme state
ProtectionSchemeState CHAR Definition of protection scheme state
mapped to string using enum
eProtectionSchemeState
ReversionModeCode SMALLINT Value of Reversion Mode
ReversionMode CHAR Definition of reversion mode mapped
to sting using enum eReversionMode
RateCode SMALLINT Value of PG layer rate from TP layer
rate list


Rate CHAR Definition of PG layer rate mapped to
string using TP layer rate table
SwitchModeCode SMALLINT Value of Switch mode
SwitchMode CHAR Definition of switch mode mapped to
string using tM2A_SwitchMode
SwitchPositionCode SMALLINT Value of Switch position
SwitchPosition CHAR Definition of Switch position mapped
to string using tM2A_SwitchPosition
SpringProtocolCode SMALLINT Value of MS-SPRing protocol type
SpringProtocol CHAR Value of MS-SPRing protocol type
mapped to string using
tM2A_SPRINGProtocol
SpringNodeId INT MS-SPRing node id
WtrTime INT Wait to Restore time
NonPreEmptibleTrafficCode SMALLINT Value of non-preemptive traffic
mapped to string using
tM2A_NonPreEmptibleTraffic
NonPreEmptibleTraffic CHAR Definition of non-preemptive traffic
HoldOffTime INT HOLD off time
LODNumSwitches INT Number of LOD switches
LODDuration INT LOD duration
ActualStateCode SMALLINT PG actual existence value
ActualState CHAR PG actual existence (Y/N)
MSPRingId INT MS-SPRing Id
ServiceStateCode SMALLINT Service state value
ServiceState CHAR Service state definition mapped to
string using enum eServiceState
MEInstanceId VARCHAR ME Instance Id (points to ME table)
Protection Group TP (v_tppg)

This table contains a list of TPs belong to protection groups.

InstanceId VARCHAR PG instance Id
rate list


PtpInstanceId VARCHAR TP Instance Id (points to port table)
PtpUserLabel VARCHAR TP User Label
Protection TP for MS-SPRing Protection Group

(v_protecttpmspringpg)
This table contains a list of protect TPs for MS-SPRing protection groups.

RateCode SMALLINT Value of PG layer rate from TP layer rate list
Rate CHAR Definition of PG layer rate mapped to string using
TP layer rate table
ProtectTPId VARCHAR Protect TP DN
Preemptive TP for MS-SPRing Protection Group

This table contains a list of preemptive TPs for MS-SPRing protection groups.

rate list
PreemptiveTPId VARCHAR Preemptive TP DN

Protection Group Affected TP (v_affectedtppg)

This table contains a list of TPs affected by protection groups.

rate list
AffectedTPId VARCHAR Affected TP DN
NUT TP for MS-SPRing Protection Group (v_

nuttpmspringpg)
This table contains a list of NUT TPs for MS-SPRing protection groups.

rate list
NUTTPId VARCHAR NUT TP DN

Help Tables
These tables assist in translating attributes when querying the database.
Table Description
Layer rate (t_layerrate) Contains a list of all layer rates.
Probable cause (t_probablecause) Contains a list of probable alarm causes.
Port link rate (t_portlinkrate) Contains a list of all port link rates.
Trail rate (t_trailrate) Contains a list of all trail rates.
Associated topology layer Contains a list of associated topology layers.
(t_assoctpglayer)
Flex reason (t_flexreason) Translates (or maps) Flex code to text strings.
NE type (t_netype) Contains a list of NE types.
Security operation (t_securityoperation) Contains a list of security operations.
Layer Rate (t_layerrate)

This table contains a list of all layer rates.

Code INT Layer rate
Name CHAR Layer rate name
Probable Cause (t_probablecause)

This table contains a list of probable alarm causes.

Code INT Alarm probable cause
Name CHAR Alarm probable cause name
Port Link Rate (t_portlinkrate)

This table contains a list of all port link rates.

Code INT Port link rate
Name CHAR Port link rate name

Trail Rate (t_trailrate)

This table contains a list of all trail rates.

Code INT Trail rate
Name CHAR Trail rate name
Associated Topology Layer (t_assoctpglayer)

This table contains a list of associated topology layers.

Code INT Associated topology layer
Name CHAR Associated topology layer name
Flex Reason (t_flexreason)

This table translates (or maps) flex code to text strings. A flex code is a trail
attribute that describes why a trail is classified as a flex trail.

Code INT Flex reason
ReasonDescription CHAR Flex reason description
NE Type (t_netype)
This table contains a list of NE types.

Code INT NE type
Name CHAR NE type name
Security Operation (t_securityoperation)

This table contains a list of security operations.

Code INT Security operation code
Name CHAR Security operation name

Log Tables
For information about log tables in LightSoft, see Activity and Security Logs.
Table Description
Activity log (v_activitylog) Contains a list of activity log records.
Security log (v_securitylog) Contains a list of security log records.
Activity Log (v_activitylog)

This table contains activity log records.

InstanceId VARCHAR Activity log record instance ID
UserID VARCHAR User identifier
ObjectID VARCHAR Related object's ID
ActionDay SMALLINT Day of log entry
ActionMonth SMALLINT Month of log entry
ActionYear SMALLINT Year of log entry
ActionHour SMALLINT Hour of log entry
ActionMinute SMALLINT Minute of log entry
ActionSecond SMALLINT Second of log entry
ActionCode INT Action performed
Action CHAR Action performed
Host VARCHAR Identifier of the client host where the action
was activated
ClientName VARCHAR Client name
StatusCode SMALLINT Action status (OK or Failed)
Status CHAR Action status (OK or Failed)
Comment VARCHAR Additional text
Security Log (v_securitylog)

This table lists security log records.

InstanceId VARCHAR Security log record instance ID
UserID VARCHAR User identifier
ActionDay SMALLINT Day of log entry
ActionMonth SMALLINT Month of log entry


ActionYear SMALLINT Year of log entry
ActionHour SMALLINT Hour of log entry
ActionMinute SMALLINT Minute of log entry
ActionSecond SMALLINT Second of log entry
ActionCode INT Action performed
Action CHAR Action performed
Host VARCHAR Identifier of the client host where the
action was activated
ClientName VARCHAR Client name
Security Tables
These tables are used to retrieve all users and user-security related records.
A user belongs to a user group. To retrieve information about user groups, use
User Group Capability (v_vpnusergroupcapability).
A user group has associated resource domains. You can retrieve the names of
the resource domains associated with a user group from the Domain Tables.
Table Description
User group capability Contains a list of user groups with profiles and
(v_vpnusergroupcapability) operations.
User (v_vpnuser) Contains a list of users per group.
User Group Capability (v_vpnusergroupcapability)

This table lists user groups.

GroupName VARCHAR Group name
ProfileName VARCHAR Profile name
CategoryName VARCHAR Category name
CategoryTypeCode INT Security categories
CategoryType CHAR Security categories
MultiSelectCode SMALLINT Multiselect
MultiSelect CHAR Multiselect
OperationCode INT Operations allowed
Operation CHAR Operations allowed

User (v_vpnuser)
This table lists users defined in LightSoft.

InstanceId VARCHAR User instance ID
Name VARCHAR User login name
FullName VARCHAR User full name
Comment VARCHAR Free text comment
Expire_Year SMALLINT Password expiration year
Expire_Month SMALLINT Password expiration month
Expire_Day SMALLINT Password expiration date
GroupName VARCHAR Name of the user group to which the user
belongs

Domain Tables
These tables are used to retrieve resources allocated to resource domains. For
information about resource domains in LightSoft, see Managing Resource
Domains. This section contains the following tables:
Table Description
Exclusive Operator Resource Domains Contains the resource domains of network
4
(v_cnmvpndomain) operators of type Exclusive (CNM).

Shareable Operator Resource Domains Contains the list of regional network operator
(v_regionvpndomain) groups with the domain list per group.
Service Provider VPN domain Contains the resource domains of the SP
(v_spvpndomain) (service provider) network operator.
EMSs of Exclusive Resource Domains Contains EMSs assigned to resource domains
(v_vpncnmresdomainems) of type Exclusive (CNM).
EMSs of Shareable Resource Domains Contains EMSs assigned to resource domains
(v_vpnregionresdomainems) of type Shareable (Regional).
MEs of Exclusive Resource Domains Contains the MEs assigned to resource
(v_vpncnmresdomainme) domains of type Exclusive (CNM).
MEs of Shareable Resource Domains contains MEs assigned to resource domains of
(v_vpnregionresdomainme) type Shareable (Regional).
UMEs of Exclusive Resource Domains Contains the UMEs assigned to resource
(v_vpncnmresdomainume) domains of type Exclusive (CNM).
UMEs of Shareable Resource Domains Contains the UMEs assigned to resource
(v_vpnregionresdomainume) domains of type Shareable (Regional).
PTPs of Exclusive Resource Domains Contains the ports (PTPs) assigned to resource
(v_vpncnmresdomainptp) domains of type Exclusive (CNM).
PTPs of Shareable Resource Domains Contains the ports (PTPs) assigned to resource
(v_vpnregionresdomainptp) domains of type Shareable (Regional).
CTPs of Exclusive Resource Domains Contains the high order CTPs assigned to
(v_vpncnmresdomainctp) resource domains of type Exclusive (CNM).
CTPs_of_Shareable_Resource_Domains Contains the high order CTPs assigned to
(v_vpnregionresdomainctp) resource domains of type Shareable
(Regional).

Exclusive Operator Resource Domains

(v_cnmvpndomain)
This table contains the resource domains of network operators of type
Exclusive (CNM).

InstanceId VARCHAR Domain Instance Id
GroupInstanceId VARCHAR Group Instance Id
VpnName VARCHAR Region name
DomainName VARCHAR Domain name
Shareable Operator Resource Domains

(v_regionvpndomain)
This table contains the list of regional network operator groups with the domain
list per group.

InstanceId VARCHAR Domain instance ID
SP Operator Resource Domains (v_spvpndomain)

This table contains the resource domains of the SP (service provider) network
operator.

VpnName VARCHAR SP name

EMSs of Exclusive Resource Domains

(v_vpncnmresdomainems)
This table contains EMSs assigned to resource domains of type Exclusive
(CNM).

EMSID VARCHAR EMS object DN
EMSs of Shareable Resource Domains

(v_vpnregionresdomainems)
This table contains EMSs assigned to resource domains of type Shareable
(Regional).

EMSId VARCHAR EMS object DN
MEs of Exclusive Resource Domains

(v_vpncnmresdomainme)
This table contains the MEs assigned to resource domains of type Exclusive
(CNM).

MEID VARCHAR ME object DN

MEs of Shareable Resource Domains

(v_vpnregionresdomainme)
This table contains MEs assigned to resource domains of type Shareable
(Regional).

MEID VARCHAR EMS object DN
UMEs of Exclusive Resource Domains

(v_vpncnmresdomainume)
This table contains the UMEs assigned to resource domains of type Exclusive
(CNM).
UMEID VARCHAR UME object DN
UMEs of Shareable Resource Domains

(v_vpnregionresdomainume)
This table contains the UMEs assigned to resource domains of type Shareable
(Regional).
UMEID VARCHAR UME object DN

PTPs of Exclusive Resource Domains

(v_vpncnmresdomainptp)
This table contains the ports (PTPs) assigned to resource domains of type
Exclusive (CNM).
PTPID VARCHAR PTP object DN
PTPs of Shareable Resource Domains

(v_vpnregionresdomainptp)
This table contains the ports (PTPs) assigned to resource domains of type
Shareable (Regional).
PTPId VARCHAR PTP object DN
CTPs of Exclusive Resource Domains

(v_vpncnmresdomainctp)
This table contains the high order CTPs assigned to resource domains of type
Exclusive (CNM).
CTPID VARCHAR CTP object DN

CTPs of Shareable Resource Domains

(v_vpnregionresdomainctp)
This table contains the high order CTPs assigned to resource domains of type
Shareable (Regional).
CTPID VARCHAR CTP object DN

Using the LightSoft Report

Generator
The LightSoft report generator is available to accommodate special cases where
queries using Versant SQL may be limited by database thresholds or other
factors.
The LightSoft report generator operates independently of SQL.
The reports that can be run are listed in the [-rep ReportId] parameter
description, below.
Default values apply for parameters that are omitted from the script. The
parameters can be indicated in any order.
To use the LightSoft report generator to generate database

reports:
In the UNIX window, run the following script:
RunNmsReportGenerator.sh [-rep ReportId] [-file FileName]
[-sep SeparationSign] [-fmt csv|CSV|C|c]
Where:
[-rep ReportId] Indicates the report to be run, with ReportID values being 1,
2, 3, 4, or 5, where:
1 – Time Slot report (default)
2 – Trail Transit CTPs Path Type report
3 – Ports Table report
4 – Trail Endpoints Path Type report
5 – PDH Utilization report
Note: The PDH Utilization report can also be run using the
special script GetPdhUtilization.sh, which supplements “-rep
5” with additional standard parameters. The report default
format is CSV and default file name is pdhutilization.dat.
These defaults can be changed using the regular parameters -
fmt and -file.
This report has an additional optional parameter
“-e MELabel/MEIPAdress” used to receive a report about a
specific ME. For example:
GetPdhUtilization.sh –e 145.23.214.1
GetPdhUtilization.sh –e “Chennai 85A”
(Parentheses (“”) are needed if the label includes spaces.)

[-file FileName] File name under which the report will be generated (default
is file name defined for corresponding report or dump in
SQL).
[-sep SeparationSign] Default delimitor between data values:
| If Report output format applies, default is space
| If CSV output format applies, default is ‘,’.
Another delimitor can be specified. For example, use "-sep :"
to separate report column or CSV data values with colons.
The output format (CSV or Report) is determined by the
presence or absence of the [-fmt csv|CSV|C|c] parameter.
[-fmt csv|CSV|C|c] Use this parameter (-fmt csv, or -fmt CSV, or -fmt C, or
-fmt c) to specify the output format as CSV.
If the parameter is omitted, the default Report output format
will apply, which includes data values in columns under a
title string.
For both CSVor Report output formats, the delimitor is
determined by the command [-sep SeparationSign].


D
Root Menus
In this appendix:
Overview ........................................................................................................ D-1
Working with Root Menus ............................................................................. D-2
4
Root Menu Applications ................................................................................. D-3

4
Overview
Root menus enable you to perform various non-LightSoft functions from the
Sun desktop. Depending on the number of applications running on your server,
the LightSoft main menu options may vary. Following is a sample of various
applications and their submenus.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary D-1

Root Menus LightSoft User Manual
Working with Root Menus

The following procedures describe how to access or log out from the root
menu.
NOTE: Some of the root menu functions require that you

enter a password.
To access the root (main) menu:

| Right-click the desktop (not in an active window). The root menu opens,
from which you can log in to the LightSoft server or client.
To log out:
1. In the main root menu, select Session Control > Log Out. The system
displays a confirmation reminding you of applications that are running.
2. Close all applications and click Exit. You are logged out.
D-2 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual Root Menus
Root Menu Applications

The following are some of the applications a root menu can include.
Typical submenus of the Root menu
Menu name Description

NMS server Includes options to start, stop, and configure the LightSoft
server application.
NMS client Includes the option to start the LightSoft client application
on your workstation.
EMS The menus for each EMS may vary - consult the
corresponding EMS documentation.
Utilities Includes options to activate several applications, such as
Snapshot, Calculator, Calendar, and so on.
Files Includes the relevant options for working with files on the
workstation (File Manager, Open CD-ROM, Open Floppy).
Tools Includes options to activate several print applications or
open a UNIX window.
System Actions Includes options to activate several applications, including
Set Route, Format/Eject Floppy, and Autolocking
Enable/Disable.
Screen Saver Includes options to activate several screen functions (Lock
Display, Configure Screen Saver, Save Configuration).
Windows Includes options to activate several window-related
applications (Shuffle Up/Down, Refresh, and so on).
Help Includes options to activate the available EMS help viewers.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary D-3

Root Menus LightSoft User Manual
D-4 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

E
Backing Up and Restoring
the LightSoft Database
In this appendix:
Overview .........................................................................................................E-1
Backup and Restore Script ..............................................................................E-1
4
Overview
In addition to the replication features provided by the Remote Data Replication
(RDR) application, you can use a script to manually backup or restore the
LightSoft database on the same station, or to purge old backups. Backups may
be scheduled to run periodically using the SetCron utility.
Backup and Restore Script

The following script may be run on any LightSoft server, or, in the case of a
cluster configuration, on the main server (the one storing the database).
To back up or restore the LightSoft database:

1. Verify that LightSoft is not currently running.
2. Open a UNIX window.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary E-1

Backing Up and Restoring the LightSoft Database LightSoft User Manual
3. Under the nms user, write the following command with the required
options:
DBBackup [-backup | -restore | -purge ] [ -dir backup folder ]
Where:
-backup Backs up the database (default when no option is indicated)
-restore Restores the database
-purge Purges obsolete backups
-dir Backup folder (the directory contains backup sets; default
$HOME/.BACKUP)
NOTE: The default backup folder may also be set using the
environment variable $BACKUP_FOLDER.
E-2 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

F
Supported Rates and
Payload Types
In this appendix:
Overview ......................................................................................................... F-1
Optical Trails ................................................................................................... F-2
4
SDH Trails ....................................................................................................... F-3

4
EoS/MoT Trails ............................................................................................... F-4

4
Overview
LightSoft trails have two attributes, Trail Rate and Payload Type, which are
used to specify the traffic of a trail.
The Trail Rate reflects the transmission object rate of the trail's network
resources (for example, VC-12). This attribute is user-specified in many trail
management applications, for example, when creating a trail or performing
Trail Consistency.
The Payload Type provides more detail about the traffic of the trail. It typically
includes information about the client signal carried as the payload of the trail
(for example, unframed signals). Payload types require EMS support.
The payload types described in this section are illustrative and do not comprise
an exhaustive list; only the more common are listed.
NOTE: It is sometimes possible to change equipment endpoint

configurations without editing the trail from LightSoft, for example,
from GbE to FC-1G or to modify the rate setting of the TRP_C. In such
cases the payload type, calculated when the trail was created in
LightSoft, is not updated automatically. You must perform Edit Trail
with activation to invoke the attribute completion to assign the new
payload type. (You do not have to actually change any trail parameter.)
For more information, see Editing Trails.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary F-1

Supported Rates and Payload Types LightSoft User Manual
Optical Trails
Optical trails are provisioned when LightSoft acquires them from the network.
To build an optical trail, you must first build the topology of the optical
network, including the topology links that connect MEs and UMEs. UMEs
represent client equipment and passive elements of the network that are not
identified by an EMS.
After the topology is correctly defined, you can apply Trail Consistency to
acquire the trail into LightSoft. After acquisition, the trails may be edited to
change attributes like the trail's label and customer name.
Optical trail rates and payload types
Trail type Description Payload types

LP Lightpath, a client The following underlying values are supported
of an OCH trail (summarized in LightSoft windows as SDH, GbE, or
DSR):
| STM-n (n = 1, 4, 16, 64, 256) based on client port
configuration
| 1-GbE (for TRP-G and TRP-C), and 10-GbE (for
TRP10-LAN)
| OTN-1 - 2.666 Gbps
| Fiber Channel: FC-2G (2.12 Gbps), FC-1G
(1.0625 Gbps), FC-531M (531 Mbps), FC-266M
(266 Mbps), FC-133M (133 Mbps)
| FDDI -100Mbps
| FICON - 1.0625 Gbps
| ESCON - 200 Mbps
| FE - for Fast Ethernet -100 Mbps
| SDI - 270Mbps
| Serial Digital HDTV - 1.485 Gbps
| ADC digital video - 2.38 Gbps, 1.3 Gbps, 595
Mbps, and 148.75 Mbps
| X Bitrate, where X = 50Mbps to 2.7Gbps
| Undefined
OMS Optical Multiplex Values are:
Section trail | 80, 40, 32, 16, 8, 4,
or Unrestricted number of channels
Note: The Client displays the OMS capacity in this
parameter.
OCH Optical Channel Values are:
trail, the client of | ODU-0, ODU-1, ODU-2, ODU-3
the OMS trail, the | DSR-2.5G, DSR-10G
trail between OCH
| DSR - any type that is not explicitly one of the
termination points
above (e.g. sub 2.5G in TRP25_2C).
F-2 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual Supported Rates and Payload Types
SDH Trails
SDH trails are provisioned in LightSoft in the Create Trail window, the XML
batch file, or are acquired from the network using the Trail Consistency
function.
Supported high order rates and payload types
High order SDH tTrail rates Payload types

VC-4, VC-4-4c, VC-4-4v, VC-4-16c, | STM-n.
VC-4-16v, VC-4-64c | INDT (indeterminate) – where the payload
type is not known to LightSoft.
NOTE: The "v" rate suffix denote a virtual concatenated

trail rate. Contiguous Concatenation to Virtual Concatenation
(C2V) functionality can be applied to endpoints of trails with
such rates. For details about C2V and how to enable it for
specific trail endpoints, see the C2V parameter in Endpoints
List Pane.
Supported low order rates and payload types
Low order SDH trail rates Payload types

VC-12, VC-2, VC-3 | E1 unframed
| E1 framed
| n x 64
| Ethernet, 2 Mbps
| E3
| DS-3
| INDT
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary F-3

Supported Rates and Payload Types LightSoft User Manual
EoS/MoT Trails
Ethernet over SDH trails are created as VC-4, VC-3, VC-12-X, VC-3, VC-
3, VC-12-X, or VC-12-X trails. X represents the VCAT size.
LightSoft recognizes them as EoS/MoT trails and classifies their payload type
accordingly.
Maximum VCAT size depends on the selected trail rate (applying to all
protection types except as indicated):
| EoS/MoT-VC4-X: Max VCAT = 16
| EoS/MoT-VC3-X: Max VCAT = 48 (For current layer protected, Max
VCAT = 3)
| EoS/MoT-VC-12-X: Max VCAT = 63
EoS/MoT rates and payload types
Trail rate Payload types

EoS/MoT-VC-4-X, EoS/MoT-VC-3- Rate (for example, Fast Ethernet and GbE)
X, EoS/MoT-VC-12-X
F-4 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

G
Client Switchover Utility
In this appendix:
Overview ........................................................................................................ G-1
Switchover Procedure ..................................................................................... G-3
4
Installation Procedure ..................................................................................... G-3

4
Using the Utility ............................................................................................. G-4

4
Client List Definition Methods ....................................................................... G-5

4
Overview
A LightSoft network management system can be deployed on more than one
server. This enables redundancy and scalability purposes, and is also useful
during upgrade procedures. For example, with LightSoft’s Remote Database
Redundancy (RDR) configuration, if the LightSoft main server fails, client
workstation/proxies can connect to the backup server instead of the main
server, and in this way continue operations as normal.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary G-1

Client Switchover Utility LightSoft User Manual
The LightSoft Client Switchover Utility eases the operations in multi-server

configurations. The utility allows administrators to conveniently switch several
LightSoft clients from one server to another by automating the switchover
process, as described in the following diagram.
NOTE: The Client Switchover Utility cannot switch a client

when the client and destination server reside on the same
workstation and zone.
G-2 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual Client Switchover Utility
Switchover Procedure
You activate the LightSoft Bulk Client Switchover Utility by executing a script
on the LightSoft server.
When the script is executed, an “NMS Server Switch Alert” message is
displayed to all users, both local and remote (via Go-Global or Exceed).
You can define the list of clients to switch in several ways:

| Client list file - recommended
| Manual client list entry - recommended
| Automatic client detection
| Interactive mode
These methods are described in more detail; see Client List Definition
Methods.
Installation Procedure
You need to install Fix number NS0300-09 in the LightSoft NMS Server
zone.
The installation script creates a "switch" library in the /opt/NMS/ folder.

Using the Utility

You invoke the utility by executing NMSClientSwitch in the
/opt/NMS/switch library, as shown below:
nms(z4-mng) /opt/NMS/switch > ./NMSClientSwitch
Usage
NMSClientSwitch [from hostname/IP] to hostname/IP [-d dir] [-I] [-m method]
[-f file] [-h]
Usage Options
Option Description Type

from Current NMS main server hostname or IP Optional
to New NMS main server hostname or IP Mandatory
-d Directory containing agents (default is Optional
directory)
-l Interactive mode Optional
-m Client list method: Optional
| file – reads client list from file
| client – automatic client detection
| manual – manual entry of client list
Default: client
-f Client workstation/proxies list file Optional
-h Displays help message Optional

Client List Definition Methods

The following is a summary of the client definition methods.
Summary of Client Definition Methods
Method Execution Options Usage

Method 1 – Using a Client List File Locally or Remotely Recommended
Method 2 – Manual Client Entry Mode Locally or Remotely Recommended
Method 3 – Automatic Client Detection Locally Use with caution
Method 4 – Interactive Mode Locally Use with caution
Method 1 – Using a Client List File

This describes how you execute the [-f file] option, using a file that includes IP
addresses or hostnames of the client workstations/proxies that need to be
switched. When you use a hostname, make sure that the same hostname
appears correctly in the /etc/hosts file on the LightSoft main server.
Sample ClientList file:
nms(z4-mng) /opt/NMS/switch > vi ClientList
"ClientList" [Read only] 2 lines, 26 characters
172.30.45.12
172.30.45.42
~
Once the ClientList file is ready, you can execute the following command:
./NMSClientSwitch from z4-mng to z7-csl-14 -f ./ClientList
NOTE: Switching clients using a client list file, works both

locally and remotely. In the example above, the script can
be executed from either z4-mng or z7-csl-14. The [from
hostname/IP] option is required only for running the utility
remotely.

Method 2 – Manual Client Entry Mode

You execute the Manual Client Entry mode as follows:
./NMSClientSwitch from z4-mng to z7-csl-14 -m manual
The Client Switchover Utility prompts the user for client IP addresses or
hostnames as shown below:
NMS Client Switching Tool
Creating client hosts list for switching:
---> Enter Host name or IP address (q to end)? [?,q] 172.30.45.12
You need to type in the client IP addresses or hostnames one by one and then
type q at the end.
NOTE: The manual mode works both locally and remotely.

In the example above, the script can be executed from either
z4-mng or z7-csl-14. The [from hostname/IP] option is
required only for running the utility remotely.
Method 3 – Automatic Client Detection

This method automatically detects and switches all clients connected to the
local LightSoft server. You execute Automatic Client Detection as follows:
./NMSClientSwitch from z4-mng to z7-csl-14 -m client
NOTE: The Automatic Client Detection mode only works

locally. In the example above, the script can only be executed
from z4-mng.
You should use the Automatic Client Detection mode with
caution. This is because it uses Operating System services to
detect client connections.
In the previous example, the script can only be executed from z4-mng.

Method 4 – Interactive Mode

You activate the Interactive mode as follows:
./NMSClientSwitch from z4-mng to z7-csl-14 -I
The utility automatically detects and displays a list of all clients currently
connected to the local LightSoft server and prompts the user to select which
clients need to be switched.
NMS Client Switching Tool
Check remote hosts connectivity... DONE.
Clients Menu
# Host OS
1 csl-12 Linux
2 z6-csl-15 SunOS
Select a client to switch ("a" for all) [1-2,a,?,q] --> 1

Switching NMS client on "csl-12" to z7-csl-14...
NOTE: The Interactive mode only works locally. In the

example above, the script can only be executed from z4-mng.
You should use Interactive Mode with caution. This is
because it uses Operating System services to detect client
connections.


H
FTS and Orbix Cluster
Resilience
In this appendix:
Overview ........................................................................................................ H-1
4
Configuring Cluster Resilience ...................................................................... H-2

4
Overview
Cluster configurations are characterized by a “main” station where the database
resides and Orbix and certain other applicative services run and multiple
“plain” stations serviced in those respects by the main station.
LightSoft provides hot standby mechanisms for increased cluster resilience:
| Fault Tolerance Server (FTS) enables server high availability by running
two synchronously updated instances of database server (two databases) on
separate computers.
| Orbix cluster resilience provides similar protection to CORBA
communications processes.
Load balancing and fault tolerance implementations typically require network
stations to be in a cluster. Improved fault-tolerance capability through the
FTS/Orbix database-replica concept makes the main-plain distinction is less
significant.
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary H-1

FTS and Orbix Cluster Resilience LightSoft User Manual
In the event of failure, main operations continue transparently via the

synchronous replica. The following client behavior applies:
| Clients operating on plain stations continue working and require no user
action.
| Clients operating on the main station receive an NMS Notification Service
(INS) failure alert. In order for the INS system to operate properly, the user
must log out from the client and log in again.
FTS and Orbix cluster resilience can also provide reliable network connection
between the cluster nodes through the addition of a redundant network
connection.
OPTIONAL FEATURE: FTS and Orbix cluster

resilience are fully integrated add-on capabilities, available on
a cost basis. If not purchased, the features do not operate.
Configuring Cluster Resilience

NOTE: Aggregation network cards must be installed on both
main and plain stations before FTS and Orbix Cluster
Resilience can be configured. Otherwise the procedure below
will open a standard NMS Configuration menu which does
not deal with FTS and Orbix Cluster Resilience configuration.
To configure FTS and Orbix cluster resilience:

1. In the Unix window on the main station, enter:
ConfigureNMS.sh
The NMS Configuration menu opens.
2. Select the Configure Cluster option. You are prompted:
Do you want to set up FTS on cluster? Y/N.
3. Enter Y. The aggregation network cards are activated and FTS and Orbix
cluster resilience are configured on the station.
H-2 ECI Telecom Ltd. Proprietary 432006-2421-0H3-A00

Index
A Configuration • 6-88
File format • 6-98
About LightSoft window • 2-33
Filter setup • 6-95
Accessing
Statistical summary format • 6-98
an EMS • 4-58
User Setup • 6-91
LightSoft • 2-1
Workflow • 6-87
Acknowledging
Alarm indicators • 6-67
Fault notifications • 6-31
Configuring a time reminder • 6-74
Service modifications • 15-40
Creating and editing an AI • 6-71
Acquisition
Deleting an AI • 6-75
Policer profiles • 14-63
Enabling/disabling an AI • 6-74
Services • 14-10
More properties • 6-72
Trails • 16-48
Viewing AI information • 6-69
Activating trail bandwidth • 9-52
Alarm Master Mask (AMM) • 16-9
Activity and security logging • 18-54
Alarm state mode • 6-35
Activity log • 18-56
Alarms • 6-3
Filtering • 18-60
Alarm state mode • 3-9
Security log • 18-57
Clearable and nonclearable • 6-7
Affected trails • 6-76
SQL tables • C-62
Alarm correlation • 6-24
Viewing EMS alarms • 6-78
Alarm counters • 6-61
Viewing for selected trails • 12-21, 15-
Counter bar • 3-7 16
Creating or editing a counter • 6-63 Visual popup • 6-67
Deleting a counter • 6-66 ASON support • 8-9
Displaying on main toolbar • 6-63 Audio indications • 6-67
More properties • 6-65 Auto-fitting columns • 2-15
Viewing counter information • 6-62 Automatic
Alarm Export panel • 6-82 Link adaptation • 5-50
Alarm Forwarder Configuration window • 6- Multi-tunnel creation • 11-46
80, 7-5
Network groups • 4-33
Alarm forwarding by FTP • 6-79
Tunnel selection for services • 14-54
Configuration • 6-82
Automaton
File format • 6-86
see Automatic Multi-Tunnel Creation •
New alarms export • 6-79 11-46
Remote host setup • 6-84 Availability
Snapshot export • 6-79 Availability for link • 5-74
Workflow • 6-80 Availability map • 5-66
Alarm forwarding by SMS/email • 6-87
432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary I-1

Index LightSoft User Manual
Optical channel availability • 16-56 Logging out • 2-9

B Starting • 2-2
Client Switchover utility • G-1
Backing up the LightSoft database Cluster resilience • H-1
RDR • 1-6
CNM (Customer Network Management)
Using a script • E-1
CNM and Trail Provisioning • 8-8
Bandwidth modification
VPNs and CNMs • 18-3
Activating trail bandwidth • 9-36,
Color coding
9-52, 12-35, 15-33
Customization • 2-22, 6-33
Decreasing trail bandwidth • 9-50
Object status indications • 6-6
Increasing trail bandwidth • 9-48
Trail consistency state • 10-14, 10-21,
Modifying tunnel bandwidth • 12-43 13-10, 13-13
Bandwidth sharing • 11-12 Columns in a window
Batch Export/Import operations • 9-77, 12-
Moving column positions • 2-20
46
Resizing widths • 2-18
Service definitions • 15-42
Showing and hiding • 2-15
Trail definitions • 9-77
Combiners in optical networks • 16-13
Tunnel definitions • 12-46
Committed information rate
Bidirectional relation between ports • 16-8
see CIR • 14-61
Bridges • 8-59
Configuration menu • A-5
Bulletin board • 3-36
Configure SMS/Email dialog box • 6-91
Bypass tunnels
Filter dialog box • 6-95
Actions on • 12-23
CORBA-based interface • 1-3
Automatic multiple creation • 11-46
Corrective action suggestions • 6-32
Creating • 11-23
CoS for Ethernet services • 14-6
C COSCs in optical networks • 16-12
CAC Coupling trails
for Ethernet services • 14-9 LP • 16-55
for MPLS tunnels • 11-9 Create Ethernet Services window • 14-20
Capabilities for profiles • 18-25 Endpoint tab • 14-36
CESR • 4-5 Network tab • 14-51
Channels • 16-7 Service Details tab • 14-24
OCH channel issues • 16-38 Service Summary pane • 14-23
CIR (Committed Information Rate) • Create traffic entity failure
14-61 Create service failure diagnosis •
Class of service (CoS) • 11-12 14-18
CoS per tunnel • 11-12 Create trail failure diagnosis • 8-26
Clearable/nonclearable alarms/TCAs • 6-7 Create tunnel failure diagnosis • 11-31
Client list definition • G-5 Create Tunnel window • 11-32
Client session Endpoints and Path • 11-43
Locking/unlocking • 2-5 Tunnel Parameters • 11-36
Logging in at locked client • 2-7 CTP SQL tables • C-24
I-2 ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

LightSoft User Manual Index
Current Alarms Export Configuration ETH Service List window • 15-4

window Filtering • 15-32
Alarm Export panel • 6-82 RSTP Map window • 15-17
Export Hosts panel • 6-84 Viewing endpoints information •
SMS/Email panel • 6-88 15-13, 15-14
Customer Network Management Viewing RSTP information • 15-17
see CNM • 18-3 Event logging and archiving • 6-38
Customizing Exporting excess records • 6-38
Main window toolbar • 3-6 Setting log triggering events • 6-41
Object colors • 2-22 Events • 6-5
Time format • 2-21 Historical log events • 6-37
CWDM wavelengths • 16-66 zSee also Fault Management • 6-1
D Exiting LightSoft • 2-10
Export Hosts panel • 6-84
Dedicated Tunnel Services • 14-10 Exporting services
Discovering MEs • 4-59 Export to CSV • 15-45
Domain SQL tables • C-76 with LightSoft • 15-43
Dual Homing protection • 14-10 Exporting to CSV • 2-30
Internetwork dual homing • 14-32 Exporting traffic definitions • 9-77,
Dual node interworking (DNI) • 8-61 12-47, 15-43
Dual ring interworking (DRI) • 8-59 Syntax • B-1
DWDM frequencies and wavelengths • 16- Traffic entities via UNIX • 9-83
63 XML data to CSV • 2-31
E Exporting trails
EA-HVPLS network • 4-65 Export to CSV • 9-81
EMS SQL table • C-10 with LightSoft • 9-77
EMSs Exporting tunnels
Accessing • 4-58 Export to CSV • 12-50
Alarms • 6-78 with LightSoft • 12-47
Managing and unmanaging • 4-57 F
Endpoint compatibility • 8-47 Failure diagnosis • 8-26, 11-31, 14-18
Endpoints selection Fast login • 2-7
Services • 14-38
Fault management • 6-1
Trails • 8-45
Accessing fault windows • 6-8
Tunnels • 11-43
Acknowledging notifications • 6-31
EoS (Ethernet over SDH)
Alarm correlation • 6-24
Data over WDM trail • F-2 Alarm counters • 6-61
Ethernet service Alarm indicators • 6-67
see Service • 14-1 Alarm state mode • 3-9, 6-35
Ethernet service SQL tables • C-29
Color coding customization • 6-33
Ethernet services and endpoints • 15-1
Common window elements • 6-9
Editing parameters • 15-36

Corrective action suggestions • 6-32 Creating a new filter • 15-26

Filtering notifications • 6-42 Preselected objects • 15-30
Notes attached to notifications • 3-39 Quick filter • 15-23
Refreshing record tables • 6-13 Filtering trails • 9-26, 12-24, 15-21
Viewing trails affected by a notification Actions from main window • 9-35, 15-
• 6-76 31
Fault management concepts • 6-2 Advanced filter • 9-29
Clearable and nonclearable alarms and Creating a new filter • 9-30
TCAs • 6-7 Preselected objects • 9-34
Notification types • 6-2 Quick filter • 9-27
Object status color indications • 6-6 Filtering tunnels
Fault management parameters • 6-14 Advanced filter • 12-28
Default columns • 6-15 Creating a new filter • 12-29
Info parameters • 6-20 Preselected objects • 12-33
Optional columns • 6-16 Quick filter • 12-26
Fault notification types Finding • 3-22
Alarms • 6-3 Forcing an ME upload • 4-4
Events • 6-5 Forcing EMS uploads • 4-58
TCAs • 6-4 Forcing user logout • 18-52
Faults menu • A-4 Frequency • 16-7
Features in LightSoft FRR tunnel protection • 11-4
Optional features • 2-34 for P2MP tunnels • 11-8, 11-38
Filtering Link vs node protection • 11-5
Activity and security logs • 18-60 FTS and Orbix resilience • H-1
Ethernet services • 15-32 Functional elements
Maintenance operation data • 17-46, 17- see LEs • 4-9
61
Path protection switch data • 17-53
G
Trail PM data • 17-8 GCT (GUI cut-through) • 2-32
Trails • 9-26 GCT operations • 4-94
Tunnels • 12-24 Groups
Filtering fault lists • 6-42 in technology layers • 3-21
Applying a filter • 6-44 SQL tables • C-10
Creating a new filter • 6-49 zSee also User groups • 18-36
Creating based on existing • 6-51 H
Deleting a filter • 6-53
Help menu • A-10
Editing a filter • 6-51
Help SQL tables • C-71
Filter criteria • 6-54
Hiding
Filter panel operations • 6-46
panes • 2-14
Setting filter as default • 6-45
Hiding columns • 2-15
Filtering services
Hub and Spoke-type configurations •
Advanced filter • 15-25
4-66

I Client startup • 2-2

Importing services Exiting • 2-10
with LightSoft • 15-46 Optional features • 2-34
Importing traffic definitions • 12-51, LightSoft environment
15-46 About window • 2-33
Syntax • B-1 GCT • 2-32
Traffic entities via Unix • 9-83 Keyboard • 2-13
Importing trails Menus and commands • 2-12
Planned trails • 8-67 Object color-coding • 6-6
with LightSoft • 9-82 Printing and exporting to file • 16-62
Importing tunnels Properties • 3-44
with LightSoft • 12-51 Root menu • 2-31
Inconsistency types • 13-13 Link availability
Inserting elements see Availability • 5-65
to optical links • 16-55 Link vs node protection • 11-5
to SDH links • 5-21 Locking/unlocking a user client • 2-5
Inserting MPLS PEs Log SQL tables • C-73
to MoT Trails • 9-53 Logged-in users
Interfaces Forcing user logout • 18-52
CORBA-based • 1-3 Sending messages to • 3-38, 6-99
Northbound • 1-3 Viewing active users • 18-51
User • 1-2, 1-3 Logging in at a locked client - Fast Login •
Invalid network topologies • 4-70 2-7
Logging into LightSoft • 2-3
K Logging out • 2-9
Keyboard • 2-13 Logical elements
L see LEs • 4-9
LP trails • F-2
Label switching • 11-2
Coupling LP trails • 16-55
LAG support • 8-7
Endpoint selection • 16-44
Lambda • 16-7
Endpoint validations • 16-45
Large report mode • 17-22
Provisioning • 16-42
Layers • 3-17
Use cases • 16-46
LE icon direction representations • 4-11
Without client equipment termination •
LE properties • 4-21 16-11
LEs (logical elements)
and technology layers • 3-21
M
Creating secondary LEs • 4-13 Main window • 3-2
Working with • 4-9 Customizing toolbar • 3-6
LightNotes • 3-43 Moving elements in • 3-5
LightSoft Maintenance operations on trails • 17-41
Accessing • 2-1 FilteringTPs • 17-46, 17-61

Maintenance Operations window • Network types • 4-63

17-41 Non-conformancy • 14-11
Performing • 17-45, 17-56 Northbound interface • 1-3
Managed elements Notepad • 3-41
see MEs • 4-3 Notifications • 6-1
Management interfaces • 1-3
O
Northbound • 1-3
ME SQL tables • C-13 OAM per Tunnel • 11-13
Menus and commands • 2-12 OCH trails • F-2
Configuration • A-5 Provisioning • 16-34
Faults • A-4 Use cases • 16-40
Help • A-10 OMS trails • F-2
Security • A-8 Endpoint selection • 16-30
System • A-9 Provisioning • 16-27
Tools • A-8 User cases • 16-33
Trails • A-6 Operations Administration and Maintenance
View • A-2 see OAM • 11-13
Window • A-10 OPM (optical performance monitoring) • 16-
MEs (Managed Eements) • 4-3 17
Messaging • 3-35 OPS OPS1 optical links • 16-5
OPS optical port • 16-5
Bulletin board • 3-36
Optical
LightNotes on your desktop • 3-43
Channels • 16-7
Messages to logged-in users • 3-38
Ports and links • 16-5
Notepad notes • 3-41
Notes attached to notifications • 3-39 Optical channel availability • 16-56
User notes • 6-99 Opening tables • 16-60
Printing and exporting • 16-62
Moving
Table formats • 16-56
Columns in window tables • 2-20
Optical devices • 16-2
Elements in main window • 3-5
Optical link types
MPLS network • 4-64
OPS OPS1 • 16-5
MPLS tunnel SQL tables • C-6, C-29
MPLS tunnels OTM • 16-5
see Tunnels • 11-1 OTU • 16-5
Optical port types
Multidimensional concept • 1-2
OPS • 16-5
N OTS • 16-5
Navigator in window maps • 3-13 Optical trail concepts
Network operators • 18-31 Alarms Master Mask • 16-9
Adding • 18-33 Optical channels • 16-7, 16-63
Deleting • 18-35 Optical devices • 16-2
Editing • 18-34 Optical links and ports • 16-5
Network properties • 4-74 Optical trail protection • 16-7

Optical trails • 16-5 see PIR • 11-15

Relations between ports and cards • 16-8 Performance Monitoring
Optical trail protection • 16-7 Multi Period PM • 17-10
Optical trail provisioning Trail current PM • 17-3
LP • 16-42 PGO (Protection group object) • 16-8
OCH • 16-34 Physical vs technology layers • 3-20
OMS • 16-27 Pinging an object • 4-97
Optical trails PIR (Peak Information Rate) • 11-15
Configurations • 16-2 Planned trails • 8-65
Coupling LP trails • 16-55 Policer profiles
Creating • 16-1 Acquisition • 14-63
Deleting • 16-55 Assigning • 14-28, 14-45
Editing parameters • 16-55 Managing • 14-59
EoS - Data over WDM trails • F-2 Ports • 5-51
Initial system setup • 16-18 ETH/MPLS • 5-58
Inserting/removing components • Optical • 16-5
16-55 Ports SQL tables • C-19
Parameters • 16-23 Posting messages • 3-36
Protection • 16-7 Printing and exporting to file • 16-62
Optional features in LightSoft • 2-34 Exporting to CSV • 2-30
Orbix • H-1 Print formats • 2-28
OTM optical links • 16-5 Profiles • 18-22
OTS optical port • 16-5 Adding • 18-28
OUT optical links • 16-5 Built-in • 18-24
Overbooking • 11-14 Capabilities • 18-25
P Deleting • 18-30
Editing • 18-30
Paginating lists in windows • 2-21
Properties
Panes in a window
Alarms TCAs and events • 6-20
Showing and hiding • 2-14
LightSoft • 3-44
Password changing • 18-50
Protection group SQL tables • C-67
Path protection switching on trails • 17-48
Provider Bridge (PB) network • 4-63
Applying commands • 17-52
Provisioning mode • 18-7
Filtering SNCP records • 17-53
Provisioning traffic entities
Path Protection Switch window •
17-49 Ethernet Services • 14-1
Path trace configuration • 5-19 MPLS tunnels • 11-1
Pathfinder algorithm • 8-4 Optical trails • 16-1
Pathfinder decision for tunnels • 11-13 SDH and EoS trails • 8-1
Payload type Pseudowire • 14-9
Supported types • F-1 Q
Peak Information Rate QoS

Tunnel traffic engineering and QoS • 11- CNM restrictions • 18-8

12 Provisioning mode • 18-7
R Security building blocks • 18-5
VPNs and CNMs • 18-3
Rates supported • F-1
Security Configuration dialog box • 18-10
RDR (remote database replication) • 1-6
Network Operators • 18-32
Reconnecting
Preferences • 18-47
Services • 15-33
Profiles • 18-23
Trails • 9-36
Resource Domains • 18-16
Tunnels • 12-35
User Groups • 18-37
Refreshing fault tables • 6-13
Users • 18-43
Remote database replication
Security Log • 18-57
see RDR • 1-6
Filtering • 18-60
Removing elements
Security management • 1-5, 18-1
from optical links • 5-32
Activity and security logging • 18-54
from SDH links • 5-28
Network operators • 18-31
Internetwork Dual Homing • 14-32
Preference customization • 18-47
Resizing list columns • 2-18
Profiles • 18-22
Resource domains • 18-14
Resource domains • 18-14
Adding • 18-18
User accounts • 18-42
Built-in • 18-17
User groups • 18-36
Deleting • 18-21
Viewing security object details • 18-12
Editing • 18-21
Viewing Used By information • 18-13
Restoring the LightSoft database
Workflow • 18-9
RDR • 1-6
Security menu • A-8
Using a script • E-1
Security SQL tables • C-74
Ring interworking protection • 8-59
Service acquisition • 14-10
Creating DRI trails • 8-62
Service discrimination • 14-8
Dual node interworking (DNI) • 8-61
Service List window • 15-4
Dual ring interworking (DRI) • 8-59
Service management preferences • 14-12
Root menus • 2-31, D-1
Service non-conformancy • 14-11
Accessing • D-2
Services • 7-4
Applications • D-3
Supported service types • 14-3
Logging out • D-2
Shared Risk Link Groups (SRLGs) • 5-4
RSTP Map window • 15-17
Showing hiding auto-fitting columns •
Modifying preferences • 15-19
2-15
S Showing hiding panes • 2-14
Searching and locating objects • 3-22 SMS/Email panel • 6-88
Secondary LEs • 4-13 Snapshot alarm export • 6-79
Secure UNIX environment • 1-6 Sorting list lines • 2-19
Security concepts • 18-3 Southbound interface • 1-3
Split LEs • 4-13

Splitting long trails • 9-46 Clearable and nonclearable • 6-7

SQL data types and parameters • C-10 TCI (trail consistency indicator)
Alarm tables • C-62 Flag and counter • 10-1
CTP tables • C-24 zSee also Trail synchronization • 10-1
Domain tables • C-76 TCI flag and counter • 10-9
EMStable • C-10 Technology layer SQL tables • C-60
Ethernet service tables • C-29 Threshold crossing alerts
Group tables • C-10 see TCAs • 6-4
Help tables • C-71 Time formats • 2-21
Log tables • C-73 Timing sources for NEs • 17-62
ME tables • C-13 Accessing timing source data • 17-64
MPLS tunnel tables • C-29 Display preferences • 17-66
Ports tables • C-19 Timing data in CSV format • 17-65
Protection group tables • C-67 Timing Map window • 17-62
Security tables • C-74 Tools menu • A-8
Technology layer tables • C-60 Topology layers • 3-17
Topology segment tables • C-15 Physical vs technology • 3-20
Trail tables • C-39 Topology segments
SQL using • C-1 SQL tables • C-15
Tables summary • C-4 Topology links • C-15
SRLGs (Shared Risk Link Groups) • 5-4 Topology tree • 3-15
SRLG avoidance in bypass path Traffic entity creation options • 8-18
selection • 11-11 Optical trails • 16-10
SRLG minimization in Pathfinder • SDH-based trails • 8-18
8-4 Services • 14-1
SRLGs and other shared resource Tunnels • 11-22
minimization • 8-4
Traffic management • 7-1
Status
Ethernet Services • 7-4
Object indication colors • 6-6
Traffic management preferences • 7-5
Trail consistency • 10-9, 10-21, 13-7,
Transport architecture • 7-3
13-13
Traffic Management in MCS • 11-14
Status bar in main window • 3-16
Overbooking and Committed
S-VLAN registration
Information Rate (CIR) • 11-14
for a service • 14-8
Peak Information Rate (PIR) • 11-15
from a trail • 9-52
Traffic Management Preferences • 7-5
Switchover utility • G-1
Setting Traffic Preferences • 7-5
Synchronizing • 10-1, 13-1
Trail Management constraint
Trails • 10-1 preferences • 8-14
Tunnels • 13-1 Trail management preferences • 8-12
System menu • A-9 Tunnel Management Preferences •
T 11-16
Trail concepts • 8-3
TCAs (threshold crossing alerts) • 6-4

CNM and trail provisioning • 8-8 Trail management constraint preferences •

LAG support • 8-7 8-14
SRLG and other shared resourec Trail management preferences • 8-12
minimization • 8-4 Trail PM (performance monitoring) • 17-3
Trails and Virtual Links • 8-3 Trail provisioning
Trail Consistency Indicator window • Optical • 16-1
10-9, 13-7 SDH and EoS • 8-1
Parameters pane • 10-11 Trail rates and payload types • F-1
Selected Objects pane • 10-12, 13-9 EoS/MoT - GbE over SDH • F-4
TCI Details pane • 10-10, 13-8 Optical • F-2
Trail information viewing SDH • F-3
Alarms for selected trails • 12-21, Trail SQL tables • C-39
15-16 Trail synchronization • 10-1
Client or server trails • 15-16 Performing • 10-4, 13-3
Trails affected by alarms • 6-76 TCI flag and counter • 10-9
Trail List window • 9-4, 12-4 Trail Consistency Indicator window •
Accessing • 9-2, 12-2 10-9, 13-7
Resource Tree pane • 9-20 Trail Synchronization window •
Trail Properties pane • 9-14, 12-13 10-14, 13-10
Trails pane • 9-7, 12-9 Use cases • 10-21, 13-13
Trail management • 8-12 Trail synchronization floating windows • 10-
Bandwidth management • 9-48 16
Creating trails • 8-12 Admitted Trails List • 10-19
Deleting trails • 9-44, 12-44, 15-38 Database Trails Sequence • 10-17
Editing/deleting trails • 9-38, 9-39, Events List • 10-20
15-34 Imposed Trail List • 10-19
Exporting trail definitions • 9-77, Network Trails Sequence • 10-17
12-47, 15-43 Queue • 10-19
Filtering the Trails pane • 9-26, 12-24, Trail syntax for import/export • B-1
15-21 Examples • B-30
Importing trail definitions • 12-51, File components • B-2
15-46
File structure • B-5
Maintenance operations • 17-41
Structure and DTDs • B-2
Operational results • 9-25, 12-22,
Syntax details • B-6
15-20
Trails and virtual links • 8-3
Path protection switching • 17-48
Trails menu • A-6
Performing operations on trails • 9-25,
12-22, 15-20 Transport architecture • 7-3
Preferences • 8-12 Tree • 3-15
Reconnecting • 9-36, 12-35, 15-33 Tunnel concepts • 11-2
Splitting long trails • 9-46 CAC for MPLS tunnels • 11-9
Trail List window • 9-4, 12-4 Enter new index keyword here •
11-12

FRR tunnel protection • 11-4 Virtual links • 8-3

Label switching • 11-2 Connecting topology layers • 3-21
Tunnel pathfinding • 11-11 VLANs • 14-47
Tunnel types - P2P, P2MP • 11-3 VPN (virtual private network) • 18-1
Tunnel Creation Options • 11-22 VPNs and CNMs • 18-3
Tunnel List window • 12-4 W
Endpoints and Path tab • 12-16
Wavelength • 16-7
Tunnel Parameters tab • 12-13
Tunnels pane • 12-9 Window menu • A-10
Tunnel management Preferences • 11-16 Window operations
Tunnel synchronization • 13-1 Paginating lists in windows • 2-21
Resizing column widths • 2-18
Tunnel tail endpoint modification • 12-38
Showing hiding auto-fitting columns • 2-
Tunnel Traffic engineering and QoS •
15
11-12
Showing hiding panes • 2-14
Bandwidth sharing • 11-12
Sorting list lines • 2-19
CoS per tunnel • 11-12
Windows and dialog boxes
OAM per tunnel • 11-13
Pathfinder decision • 11-13 About window • 2-33
Traffic Management in MCS • 11-14 Activity and Security Log • 18-54
Tunnel types - P2P, P2MP2 • 11-3 Alarm Forwarder Configuration • 6-80
Create Service • 14-20
Tunnels
Create Trail (optical) • 16-25
Provisioning • 11-1
Create Trail (SDH and EoS/MoT) •
U 8-32
UMEs Create Tunnel • 11-32
UME properties • 4-52 ETH Service List • 15-4
UNIX environment security • 1-6 Event Log History • 6-37
User groups • 18-36 Initial LightSoft screen • 2-11
Adding • 18-39 Main window • 3-2
Built-in • 18-38 Maintenance Operations • 17-41
Deleting • 18-42 Path Protection Switch • 17-49
Editing • 18-41 Plan Trail • 8-65
User interface • 1-2 Print • 2-26
User notes • 6-99 RSTP Map • 15-17
Users • 18-42 Security Configuration • 18-10
Adding • 18-44 Service List • 15-4
Deleting • 18-46 Timing Map • 17-62
Editing • 18-46 Trail Consistency Indicator • 10-9
Monitoring user actions • 18-54 Trail List • 9-4
Trail Performance Monitoring • 17-3
V
Trail Synchronization • 10-14
View menu • A-2 Tunnel List • 12-4

Tunnel Segment Consistency • 13-7

Tunnel Synchronization • 13-10
Used By • 18-13
X
XML import/export trail syntax • B-1
Examples • B-30
File components • B-2
File structure • B-5
Structure and DTDs • B-2
Trail syntax • B-6
Z
Zooming the window map • 3-11

LightSoft UM ETSI A00 V4.2R1 en PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

LightSoft UM ETSI A00 V4.2R1 en PDF

Hochgeladen von

Copyright:

Verfügbare Formate

LightSoft®

Getting Started......................................................................... 2-1

432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary i

Printing and Exporting to File ......................................................................... 2-24

LightSoft User Interface .......................................................... 3-1

ii ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Managing Elements, Groups, and Networks......................... 4-1

432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary iii

Topology Links and Ports ...................................................... 5-1

Fault Management ................................................................... 6-1

iv ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Fault Window Parameters .............................................................................. 6-14

432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary v

Alarm Forwarding by SMS and Email ............................................................ 6-87

Managing Traffic ...................................................................... 7-1

Provisioning SDH and EoS/MoT Trails .................................. 8-1

vi ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Select Resource Pane .............................................................................. 8-54

Performing Actions on Trails ................................................. 9-1

432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary vii

Removing MPLS PEs from MoT Trails ........................................................... 9-62

Synchronizing Trails ............................................................. 10-1

Provisioning MPLS Tunnels ................................................. 11-1

viii ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Automatic Multi-tunnel Creation ................................................................... 11-46

Performing Actions on Tunnels ........................................... 12-1

Synchronizing Tunnels ......................................................... 13-1

432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary ix

Provisioning Ethernet Services ........................................... 14-1

Performing Actions on Ethernet Services........................... 15-1

x ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Service Summary Pane .......................................................................... 15-13

Provisioning Optical Trails ................................................... 16-1

432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xi

OMS Trail Provisioning ................................................................................. 16-27

Performance Monitoring and Maintenance ......................... 17-1

xii ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Exporting PM Data to CSV ..................................................................... 17-31

Security .................................................................................. 18-1

432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xiii

Managing Network Operators ...................................................................... 18-31

Summary of Menu Commands .............................................. A-1

Import/Export Traffic Syntax ................................................. B-1

xiv ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Trail Syntax and Examples ............................................................................... B-6

Report Generation using SQL and LightSoft ....................... C-1

Root Menus ............................................................................. D-1

Backing Up and Restoring the LightSoft Database..............E-1

Supported Rates and Payload Types .................................... F-1

Client Switchover Utility ........................................................ G-1

432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xv

FTS and Orbix Cluster Resilience ......................................... H-1

Index .......................................................................................... I-1

xvi ECI Telecom Ltd. Proprietary 432006-2421-4H3-A00

Intended Audience .......................................................................................... xvii

Document Organization ................................................................................. xviii

Document Conventions .................................................................................... xx

Related Publications ........................................................................................ xxi

Obtaining Technical Documentation ............................................................... xxi

Technical Assistance ...................................................................................... xxii

432006-2421-4H3-A00 ECI Telecom Ltd. Proprietary xvii

describes its basic concept and functions.

working with windows, and viewing information.