XDM-SYNCOM Preventive Maintenance A00 11-2009 en PDF

XDM®/SYNCOM Networks
Preventive Maintenance
November 2009
417006-2201-013-B02
XDM/SYNCOM Networks Preventive Maintenance
Catalog No: X37874
November 2009
7th Edition
© Copyright by ECI Telecom, 2004-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.
Contents
About This Manual .................................................................. xiii
Overview ........................................................................................................... xiii
Document Conventions ..................................................................................... xiv
What is New in this Version? .............................................................................. xv
Related Documentation ..................................................................................... xvi
Obtaining Technical Documentation ................................................................. xvi
Technical Assistance........................................................................................ xvii
Preventive Maintenance Procedures via EMS-SYNCOM ..... 1-1

Overview .......................................................................................................... 1-1
Saving NE Database Configuration to Hard Disk ............................................. 1-3
Checking Version Correspondence .................................................................. 1-4
Saving EMS-SYNCOM Configuration to a Backup Disk via FTP ..................... 1-5
Deleting Old System Files ................................................................................ 1-7
Viewing Login History ..................................................................................... 1-13
Viewing Log Actions ....................................................................................... 1-15
Checking Performance ................................................................................... 1-18
Viewing Trail End Points Performance ........................................................... 1-23
Current Alarms ............................................................................................... 1-25
Viewing the Alarm Log ................................................................................... 1-30
Checking the Alarm Log ................................................................................. 1-32
Using Ping to Test EMS-SYNCOM-NE Communications .............................. 1-33
Checking Management Performance ............................................................. 1-34
Preventive Maintenance Procedures via EMS-XDM ............. 2-1

Overview .......................................................................................................... 2-1
Saving NE Database Configuration to Hard Disk ............................................. 2-6
Checking Corresponding Version ..................................................................... 2-8
Deleting Old System Files .............................................................................. 2-10
Viewing Login History ..................................................................................... 2-16
Viewing Log Actions ....................................................................................... 2-19
Checking Performance ................................................................................... 2-21
Viewing PM, MS, and Optics Logs ................................................................. 2-24
Pinging the NE ............................................................................................... 2-53
Saving Current Network and Security Configurations .................................... 2-54
Exporting XCSs .............................................................................................. 2-56
Exporting Policer Information ......................................................................... 2-58
Exporting Flow Information ............................................................................. 2-58
Viewing Optical Levels and Parameters of Optical Objects ........................... 2-59
Exporting Topology Data ................................................................................ 2-60
Viewing NE Inventory ..................................................................................... 2-62
Performing Maintenance and Backup Operations Using a Script .................. 2-64
417006-2202-013-A00 ECI Telecom Ltd. Proprietary i

Contents XDM/SYNCOM Networks Preventive
Maintenance
Preventive Maintenance Procedures via LightSoft .............. 3-1

Overview .......................................................................................................... 3-1
Saving the LightSoft Database ......................................................................... 3-3
Checking Objects' Status ................................................................................. 3-4
Managing NEs in Topology Links ..................................................................... 3-5
Inserting Elements into SDH/SONET Links ..................................................... 3-6
Provisioning LO XCs for SDM-16 following Insert to a Link ........................... 3-11
Removing an Element from a Link ................................................................. 3-13
Inserting/Removing Elements to/from Optical Links ....................................... 3-17
Viewing Resource Availability on Links .......................................................... 3-19
Printing and Exporting Availability Information ............................................... 3-43
Synchronizing the LightSoft Database with the EMS Database ..................... 3-44
Synchronizing Tunnels ................................................................................... 3-45
Batch Trail Operations .................................................................................... 3-59
Batch Tunnel Operations ................................................................................ 3-70
Batch Service Operations ............................................................................... 3-77
Trail Performance Monitoring ......................................................................... 3-83
Multi Period PM .............................................................................................. 3-91
Previewing the Report .................................................................................. 3-116
Alarm Correlation ......................................................................................... 3-126
Viewing Historical Log Events ...................................................................... 3-134
Configuring Event Logging, Archiving, and Historical Viewing ..................... 3-136
Checking the LightSoft Hard Drive Capacity ................................................ 3-140
RDR Preventive Maintenance ................................................. 4-1

Overview .......................................................................................................... 4-1
Instance Discovery ........................................................................................... 4-2
Alarms Configuration ........................................................................................ 4-7
RDR Command Center Diag Mode .................................................................. 4-9
Activating an Unscheduled Backup ................................................................ 4-10
Activating an Unscheduled Archive Backup ................................................... 4-12
Viewing Crontab Entries ................................................................................. 4-13
Viewing Log Files ........................................................................................... 4-13
RDR Recovery ............................................................................................... 4-14
Hardware Preventive Maintenance ........................................ 5-1

Hardware Preventive Maintenance Table ........................................................ 5-1
ii ECI Telecom Ltd. Proprietary 417006-2202-013-A00

XDM/SYNCOM Networks Preventive Contents
Maintenance
Preventive Maintenance Checklists ....................................... 6-1

EMS-XDM Checklists ....................................................................................... 6-1
EMS-SYNCOM Checklists ............................................................................... 6-2
LightSoft Checklists .......................................................................................... 6-3
RDR Checklist .................................................................................................. 6-4
Hardware Checklists ........................................................................................ 6-4
Index .......................................................................................... I-1
417006-2202-013-A00 ECI Telecom Ltd. Proprietary iii

Contents XDM/SYNCOM Networks Preventive
Maintenance
iv ECI Telecom Ltd. Proprietary 417006-2202-013-A00

List of Figures
Figure 1-1: Typical EMS-SYNCOM main window.......................................................... 1-2
Figure 1-2: Change NE SW - Network window .............................................................. 1-3
Figure 1-3: Saving a Configuration ................................................................................ 1-6
Figure 1-4: The Log Export window ............................................................................... 1-8
Figure 1-5: Performance Monitoring Files window....................................................... 1-10
Figure 1-6: Browse File window ................................................................................... 1-11
Figure 1-7: PM Filter window ....................................................................................... 1-11
Figure 1-8: Login File Selection ................................................................................... 1-13
Figure 1-9: Login File window ...................................................................................... 1-14
Figure 1-10: Action Log File Selection ......................................................................... 1-16
Figure 1-11: Action Log View ....................................................................................... 1-17
Figure 1-12: Example of a Current Performance window ............................................ 1-18
Figure 1-13: Example of a Performance History window ............................................. 1-19
Figure 1-14: Performance Charts window ................................................................... 1-21
Figure 1-15: Current Performance Trail End Point window ......................................... 1-23
Figure 1-16: Historical Performance Trail End Point window ...................................... 1-24
Figure 1-17: Network Current Alarms window ............................................................. 1-26
Figure 1-18: Trails List for Faulty Object window ......................................................... 1-29
Figure 1-19: Example of an Alarm Log window ........................................................... 1-30
Figure 1-20: Alarm Log window ................................................................................... 1-32
Figure 1-21: The Ping window ..................................................................................... 1-33
Figure 2-1: Typical XDM-100 Shelf View ....................................................................... 2-3
Figure 2-5: Typical XDM-500 shelf view window ........................................................... 2-5
Figure 2-6: Typical XDM-1000 shelf view window ......................................................... 2-5
Figure 2-7: Typical XDM-2000 shelf view window ......................................................... 2-6
Figure 2-8: SW Management window ............................................................................ 2-7
Figure 2-9: Operation submenu options ........................................................................ 2-7
Figure 2-10: Version correspondence check ................................................................. 2-9
Figure 2-11: Version correspondence check results...................................................... 2-9
Figure 2-12: Log Export window .................................................................................. 2-11
Figure 2-13: Performance Monitoring Files window..................................................... 2-13
Figure 2-14: Typical Browse File window .................................................................... 2-14
417006-2202-013-A00 ECI Telecom Ltd. Proprietary v

List of Figures XDM/SYNCOM Networks Preventive
Maintenance
Figure 2-15: PM Filter window ..................................................................................... 2-14

Figure 2-17: Login History File Selection window ........................................................ 2-16
Figure 2-18: Login File window .................................................................................... 2-17
Figure 2-19: Action History File window ....................................................................... 2-20
Figure 2-20: PM Setup window .................................................................................... 2-22
Figure 2-22: Browse File window ................................................................................. 2-25
Figure 2-23: PM Filter window ..................................................................................... 2-26
Figure 2-24: Current PM window (tabular) ................................................................... 2-27
Figure 2-25: Current PM Chart window ....................................................................... 2-28
Figure 2-26: Typical Performance History window ...................................................... 2-29
Figure 2-27: Performance Charts window ................................................................... 2-31
Figure 2-28: Performance Charts window for objects with more than nine
counters........................................................................................................................ 2-33
Figure 2-29: PM History window .................................................................................. 2-34
Figure 2-30: OPM PM Current/History Chart window .................................................. 2-36
Figure 2-31: Current Alarms window ........................................................................... 2-37
Figure 2-32: XCS List for faulty object window ............................................................ 2-40
Figure 2-33: Alarm Log window ................................................................................... 2-41
Figure 2-34: Alarm log menu bar ................................................................................. 2-42
Figure 2-35: Alarm log toolbar...................................................................................... 2-43
Figure 2-36: Alarms list ................................................................................................ 2-43
Figure 2-37: EMS-XDM alarm log status bar ............................................................... 2-45
Figure 2-38: Alarm Record History window ................................................................. 2-46
Figure 2-39: Alarms checked-off confirmation window ................................................ 2-47
Figure 2-40: Log Filter window ..................................................................................... 2-48
Figure 2-41: Log Export window .................................................................................. 2-51
Figure 2-42: NE Ping window....................................................................................... 2-53
Figure 2-43: Save File Name window .......................................................................... 2-55
Figure 2-44: Save XCS window ................................................................................... 2-57
Figure 2-45: Optical Parameters window ..................................................................... 2-59
Figure 2-46: Save Topology window ............................................................................ 2-61
Figure 2-47: Inventory window ..................................................................................... 2-62
Figure 3-1: Typical LightSoft database backup window ................................................ 3-4
Figure 3-2: NE status check window .............................................................................. 3-5
Figure 3-3: Selected element and link ........................................................................... 3-8
Figure 3-4: Insert Into Link dialog box ............................................................................ 3-8
Figure 3-5: Insert ME dialog box .................................................................................... 3-9
vi ECI Telecom Ltd. Proprietary 417006-2202-013-A00

XDM/SYNCOM Networks Preventive List of Figures
Maintenance
Figure 3-6: Insert ME dialog box link attributes............................................................ 3-10

Figure 3-7: NE inserted into link ................................................................................... 3-11
Figure 3-8: Topology in EMS-SYNCOM ...................................................................... 3-12
Figure 3-9: Selected element in a link .......................................................................... 3-14
Figure 3-10: Remove NE dialog box ............................................................................ 3-15
Figure 3-11: Links automatically selected in the map view .......................................... 3-15
Figure 3-12: Insert ME dialog box More area .............................................................. 3-16
Figure 3-13: NE removed from the link ........................................................................ 3-17
Figure 3-14: Availability of Resource dialog box .......................................................... 3-22
Figure 3-15: Availability Map (for SDH or Optical) window .......................................... 3-23
Figure 3-16: Availability Map (for Ethernet/MPLS) window ......................................... 3-25
Figure 3-17: Availability Map Preferences dialog box ................................................. 3-28
Figure 3-18: Availability for Link widow ........................................................................ 3-31
Figure 3-19: Availability for Link/MoT window............................................................. 3-32
Figure 3-20: Link PM Availability Diagrams GUI .......................................................... 3-34
Figure 3-21: Availability info Preferences dialog box ................................................... 3-35
Figure 3-22: Intersection trail avilability table for 32 channel OMS trail ....................... 3-37
Figure 3-23: Single availability tables for 32 channel OMS trail .................................. 3-38
Figure 3-24: Link selection when single OMS trail between MDs at both ends........... 3-41
Figure 3-25: Link selection for bidirectional table between A and B ............................ 3-41
Figure 3-26: Link selection for bidirectional utilization A-B and B-C ............................ 3-41
Figure 3-27: Synchronization Results window ............................................................. 3-50
Figure 3-28: Tunnel Segment Consistency (TSC) window .......................................... 3-51
Figure 3-29: TSC window Selected Objects pane ....................................................... 3-53
Figure 3-30: Tunnel Synchronization window .............................................................. 3-54
Figure 3-31: Export Trails to XML dialog box............................................................... 3-63
Figure 3-32: Import Trails dialog box ........................................................................... 3-66
Figure 3-33: Export Tunnels dialog box ....................................................................... 3-73
Figure 3-34: Import Tunnels dialog box ....................................................................... 3-75
Figure 3-35: Export Services dialog box ...................................................................... 3-80
Figure 3-36: Import Services dialog box ...................................................................... 3-82
Figure 3-37: Trail Performance Monitoring window ..................................................... 3-84
Figure 3-38: Enable PM confirmation .......................................................................... 3-87
Figure 3-39: PM Counters Confirmation prompt upon exit .......................................... 3-88
Figure 3-40: Reset PM Data ( 24 Hr) confirmation prompt .......................................... 3-88
Figure 3-41: Performance Monitoring Trail Filter dialog box........................................ 3-89
Figure 3-42: Multi Period PM dialog box ...................................................................... 3-94
Figure 3-43: Multi Period PM dialog box – step 1 ........................................................ 3-96
Figure 3-44: Add Trails dialog box ............................................................................... 3-98
417006-2202-013-A00 ECI Telecom Ltd. Proprietary vii

Maintenance
Figure 3-45: Multi Period PM dialog box – step 2 ...................................................... 3-100

Figure 3-46: Multi Period PM dialog box – step 3 ...................................................... 3-101
Figure 3-47: Large Report Mode message ................................................................ 3-103
Figure 3-48: Report Data shortcut menu ................................................................... 3-106
Figure 3-49: Template dialog box .............................................................................. 3-107
Figure 3-50: Save Template dialog box ..................................................................... 3-108
Figure 3-51: Template Already Exists dialog box ...................................................... 3-108
Figure 3-52: Configure Thresholds dialog box ........................................................... 3-109
Figure 3-53: Advanced Formatting dialog box ........................................................... 3-110
Figure 3-54: Report Output Setup dialog box ............................................................ 3-112
Figure 3-55: CoS Filter dialog box ............................................................................. 3-114
Figure 3-56: Multi Period Performance Monitoring View Report window .................. 3-116
Figure 3-57: Generate Report Configuration window ................................................ 3-118
Figure 3-58: PMH Report window .............................................................................. 3-119
Figure 3-59: Report header for all reports.................................................................. 3-120
Figure 3-60: Report captions...................................................................................... 3-121
Figure 3-61: Report Table .......................................................................................... 3-122
Figure 3-62: Summary Report example ..................................................................... 3-123
Figure 3-63: Overall Statistics table ........................................................................... 3-124
Figure 3-64: Current Alarms window with correlation-related elements .................... 3-128
Figure 3-65: Current Alarms window showing/hiding secondary alarms ................... 3-130
Figure 3-66: Current Alarms window showing secondary alarms per primary .......... 3-131
Figure 3-67: Event Log History window ..................................................................... 3-134
Figure 3-68: Import Log History Files dialog box ....................................................... 3-135
Figure 3-69: Event Log Configuration window - Event Log Parameters tab .............. 3-137
Figure 3-70: Events Log Configuration window - Event Types to Log tab ................. 3-139
Figure 3-71: Typical hard drive capacity check window ............................................ 3-140
Figure 4-1: RDR instances ............................................................................................. 4-3
Figure 4-2: Possible RDR modes of Activity .................................................................. 4-4
Figure 4-3: RDR Discovery Menu .................................................................................. 4-4
Figure 4-4: Automatic instance discovery ...................................................................... 4-5
Figure 4-5: Manual instance discovery .......................................................................... 4-6
Figure 4-6: View Status of an Instance .......................................................................... 4-6
Figure 4-7: RDR Instance Configuration Options Menu ................................................ 4-8
Figure 4-8: RDR Alarm Notification Editor ..................................................................... 4-8
Figure 4-9: RDR Commn Actions Menu ........................................................................ 4-9
Figure 4-10: Diag Mode On.......................................................................................... 4-10
Figure 4-11: Start backup session ............................................................................... 4-11
Figure 4-12: Start archive backup ................................................................................ 4-12
viii ECI Telecom Ltd. Proprietary 417006-2202-013-A00

XDM/SYNCOM Networks Preventive List of Figures
Maintenance
Figure 4-13: Viewing the Crontab Entries .................................................................... 4-13

Figure 4-14: RDR Common Actions Menu .................................................................. 4-14
Figure 4-15: Possible RDR modes of activity .............................................................. 4-14
Figure 4-16: RDR Mirror Component Actions Menu .................................................... 4-15
Figure 4-17: Mirror Instances list.................................................................................. 4-15
Figure 4-18: RDR log file.............................................................................................. 4-16
417006-2202-013-A00 ECI Telecom Ltd. Proprietary ix

Maintenance
x ECI Telecom Ltd. Proprietary 417006-2202-013-A00

List of Tables
Table 1-1: Preventive maintenance procedures via EMS-SYNCOM............................. 1-1
Table 2-1: Preventive maintenance procedures via EMS-XDM .................................... 2-2
Table 2-2: Filtering options........................................................................................... 2-26
Table 2-3: Performance Charts window buttons .......................................................... 2-32
Table 2-4: OPM Current/History window fields ............................................................ 2-35
Table 2-5: Alarm log menu bar options ........................................................................ 2-42
Table 2-6: Alarm log toolbar icons ............................................................................... 2-43
Table 2-7: Log filtering options ..................................................................................... 2-49
Table 2-8: Optical Parameters window fields............................................................... 2-60
Table 2-9: Inventory window fields ............................................................................... 2-63
Table 2-10: ScheduleTask options .............................................................................. 2-64
Table 3-1: Preventive maintenance procedures via LightSoft ....................................... 3-2
Table 3-2: Availability Map menu option ...................................................................... 3-24
Table 3-3: Availability Map menu option ...................................................................... 3-25
Table 3-4: Availability Map CSV data fields ................................................................. 3-27
Table 3-5: Availability preference dialog box buttons .................................................. 3-29
Table 3-6: Link Availability menu options..................................................................... 3-30
Table 3-7: Link CAC Availability diagram features....................................................... 3-33
Table 3-8: Link PM Availability diagram features ......................................................... 3-34
Table 3-9: Utilization Table menu and toolbar options ................................................ 3-39
Table 3-10: TSC window toolbar .................................................................................. 3-51
Table 3-11: Indications of warning flags ...................................................................... 3-52
Table 3-12: Selected Objects pane of TSC window .................................................... 3-53
Table 3-13: Tunnel Synchronization window toolbar ................................................... 3-55
Table 3-14: Tunnel Synchronization floating window columns .................................... 3-56
Table 3-15: Tunnel Inconsistency types and possible remedial actions ...................... 3-57
Table 3-16: Trail Performance Monitoring window toolbar .......................................... 3-85
Table 3-17: Trail Performance Monitoring window shortcut options ............................ 3-85
Table 3-18: Trail Performance Monitoring window fields ............................................. 3-86
Table 3-19: Performance Monitoring Trail Filter dialog box components .................... 3-90
Table 3-20: Multi Period PM dialog box toolbar and buttons ....................................... 3-95
Table 3-21: Multi Period PM - Step1: Traffic and Template pane................................ 3-97
Table 3-22: Multi Period PM Step1: Add Trail dialog box fields ................................... 3-99
Table 3-23: Multi Period PM - Step2: Report Definitions pane .................................. 3-100
Table 3-24: Multi Period PM - Step3: Counter List pane - Report
Configuration panes ................................................................................................... 3-102
417006-2202-013-A00 ECI Telecom Ltd. Proprietary xi

List of Tables XDM/SYNCOM Networks Preventive
Maintenance
Table 3-25: Multi Period PM - Step3: Counter List pane - Report Data..................... 3-104
Table 3-26: Multi Period PM : Configure Thresholds dialog box columns and
options ........................................................................................................................ 3-109
Table 3-27: Multi Period PM: Advanced Formatting dialog box fields ....................... 3-111
Table 3-28: Multi Period PM: Report Output Setup dialog box fields ........................ 3-113
Table 3-29: Multi Period PM : Open Filter options ..................................................... 3-115
Table 3-30: Multi Period PM Preview window toolbar options ................................... 3-117
Table 3-31: Multi Period PM: Report Header ............................................................. 3-120
Table 3-32: Multi Period PM: Subtitle caption per Information Segment ................... 3-121
Table 3-33: Multi Period PM: Detailed count per counter table ................................. 3-123
Table 3-34: Multi Period PM: Overall Statistics per TP .............................................. 3-124
Table 3-35: Alarm Correlation-related columns ......................................................... 3-129
Table 3-36: Alarm Correlation-related icons .............................................................. 3-129
Table 4-1: RDR preventive maintenance procedures .................................................... 4-1
Table 5-1: Preventive maintenance inspection and checks ........................................... 5-2
xii ECI Telecom Ltd. Proprietary 417006-2202-013-A00

About This Manual
In this chapter:
Overview ......................................................................................................... xiii
Document Conventions ................................................................................... xiv
What is New in this Version? ........................................................................... xv
Related Documentation ................................................................................... xvi
Obtaining Technical Documentation ............................................................... xvi
Technical Assistance ...................................................................................... xvii
Overview
This guide describes the XDM®/SYNCOM™ preventive maintenance
procedures to be performed periodically by network administrators. The
purpose of the procedures is to ensure the optimal and uninterrupted operation
of your network. The information presented in this manual is organized as
follows:
| About This Manual (on page xiii): Provides the scope and organization of
this manual, including a brief description of the preventive maintenance
procedures.
| Preventive Maintenance Procedures via EMS-SYNCOM (on page 1-1):
Provides a description of the preventive maintenance procedures performed
via EMS-SYNCOM.
| Preventive Maintenance Procedures via EMS-XDM (on page 2-1):
via EMS-XDM.
| Preventive Maintenance Procedures via LightSoft (on page 3-1):
via LightSoft®.
417006-2202-013-A00 ECI Telecom Ltd. Proprietary xiii

About This Manual XDM/SYNCOM Networks Preventive
Maintenance
| RDR Preventive Maintenance (on page 4-1): Provides a description of the

preventive maintenance procedures for sites operating the RDR utility.
| Hardware Preventive Maintenance (on page 5-1): Provides a list of
hardware preventive maintenance inspection and checks.
| Preventive Maintenance Checklists (on page 6-1): Provides checklists for
recording preventive maintenance activities.
| Index
The procedures are software oriented and performed by the network
administration staff.
NOTE: Many of the preventive procedures outlined in this

guide may affect traffic; on-screen warnings alert you when
necessary.
Document Conventions
When applicable, this manual uses the following conventions.
Convention Indicates Example

Bold Names of windows, dialog In the Alarms menu...
boxes, menus, buttons and
most other GUI elements
Menu > Option Selection from a menu, or Select Update > View
leading to another Objects
command
Courier New Code syntax and code >>Starting default
Font examples, UNIX primary application,
commands, user-typed please wait...
information
Italics New terms and emphasized Examples in text
text
Borders around text Notes, cautions, warnings, See examples below
laser warnings, EDS
warnings, tips, and
important notes
NOTE: Text set off in this manner presents clarifying

information, specific instructions, commentary, sidelights, or
interesting points of information.
xiv ECI Telecom Ltd. Proprietary 417006-2202-013-A00

XDM/SYNCOM Networks Preventive About This Manual
Maintenance
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.
LASER WARNING: Text set off in this manner indicates

how to avoid personal injury. All personnel involved in
equipment installation, operation, and maintenance must be
aware that laser radiation is invisible. Therefore, although
protective devices generally prevent direct exposure to the
beam, personnel must strictly observe the applicable safety
precautions and, in particular, must avoid staring into optical
connectors, either directly or using optical instruments.
ESD: Text set off in this manner indicates information on

how to avoid discharge of static electricity and subsequent
damage to the unit.
TIP: Text set off in this manner includes helpful information

and handy hints that can make your task easier..
IMPORTANT: Text set off in this manner presents essential

information you must pay attention to.
What is New in this Version?

The information presented in this guide is applicable to EMS-XDM V8.1,
EMS-SYNCOM V2.1, LightSoft V4.2.2, and RDR V4.5 onwards. If you need
clarifications regarding information described in this guide, refer to the relevant
manual as listed in Related Documentation, or contact Transport Networking
Division's Professional Services Department.
417006-2202-013-A00 ECI Telecom Ltd. Proprietary xv

Maintenance
Related Documentation
Additional information regarding the XDM network and hardware maintenance
procedures can be found in the following documentation:
| EMS-XDM User Manual
| EMS-SYNCOM User Manual
| LightSoft User Manual
| RDR User Manual
| XDM IMM (Installation and Maintenance Manual)
| XDM RM (Reference Manual)
NOTE: In the above list, XDM is the generic name for the
various platforms of the XDM family.
Obtaining Technical
Documentation
To obtain technical documentation related to the XDM/SYNCOM Networks or
any other ECI Telecom product, please contact:
ECI Telecom Ltd.
Documentation Department
30 Hasivim St.
Petach Tikva 49130
Israel
Fax: +972-3-9268060
Email: techdoc.feedback@ecitele.com
xvi ECI Telecom Ltd. Proprietary 417006-2202-013-A00

XDM/SYNCOM Networks Preventive About This Manual
Maintenance
Technical Assistance
The configuration, installation, and operation of the XDM/SYNCOM Networks
and its operation in a network are highly specialized processes. Due to the
different nature of each installation, some planning aspects may not be covered
in this manual.
If you have questions or concerns about your network design or if you require
installation personnel to perform the actual installation process, ECI Telecom
maintains a staff of design engineers and highly trained field service personnel.
The services of this group are available to customers at any time.
If you are interested in obtaining design assistance or a network installation
plan from ECI Telecom's 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, please contact our central customer
support center action line at:
Telephone +972-3-9266000
Telefax +972-3-9266370
Email on.support@ecitele.com
ECI Telecom's XDM® and BroadGate® product lines are

certified to comply with MEF9 and MEF14 standards.
417006-2202-013-A00 ECI Telecom Ltd. Proprietary xvii

Maintenance
xviii ECI Telecom Ltd. Proprietary 417006-2202-013-A00

1
Procedures via EMS-SYNCOM
In this chapter:
Overview ......................................................................................................... 1-1
Saving NE Database Configuration to Hard Disk ........................................... 1-3
Checking Version Correspondence ................................................................. 1-4
Saving EMS-SYNCOM Configuration to a Backup Disk via FTP ................. 1-5
Deleting Old System Files ............................................................................... 1-7
Checking Performance .................................................................................. 1-18
Checking the Alarm Log ............................................................................... 1-32
Using Ping to Test EMS-SYNCOM-NE Communications ........................... 1-33
Checking Management Performance ............................................................. 1-34
Overview
The following table summarizes the preventive maintenance procedures
performed via EMS-SYNCOM.
Table 1-1: Preventive maintenance procedures via EMS-SYNCOM
Procedure Performed Section Comments

Save NE database Once a quarter, or following Saving NE Database
configuration to hard major changes in network Configuration to Hard
disk. topology Disk (on page 1-3)
Check version Once a quarter, or whenever Checking Version
correspondence for major changes are made to Correspondence (on
SYNCOM NEs. system configuration page 1-4)
Save EMS- Once a week, or following Saving EMS-SYNCOM
SYNCOM major changes in network Configuration to a
configuration to a topology Backup Disk via FTP
backup disk via FTP. (on page 1-5)
417006-2202-013-A00 ECI Telecom Ltd. Proprietary 1-1

Preventive Maintenance Procedures XDM/SYNCOM Networks Preventive
via EMS-SYNCOM Maintenance

Check version Once a week, or whenever Checking Version
correspondence for major changes are made to Correspondence (on
SYNCOM NEs. system configuration page 1-4)
Delete old system Once a week, or according to Deleting Old System
files. working procedures Files (on page 1-7)
Check performance. Once a week, or according to Checking Performance
working procedures (on page 1-18)
Check EMS- Once a week, or according to Using Ping to Test
SYNCOM to NE working procedures EMS-SYNCOM-NE
communications for Communications (on
SYNCOM NEs. page 1-33)
Check management Once a quarter, according to Checking Management
performance. the network administrator's Performance (on page
instructions 1-34)
NOTE: Unless otherwise specified, all preventive

maintenance procedures described in this chapter are
executed in the systems main window. The following figure
shows a typical main window.
Figure 1-1: Typical EMS-SYNCOM main window
1-2 ECI Telecom Ltd. Proprietary 417006-2202-013-A00

XDM/SYNCOM Networks Preventive Preventive Maintenance Procedures
Maintenance via EMS-SYNCOM
Saving NE Database
Configuration to Hard Disk
NOTE: This procedure is performed for SYNCOM NEs only.
This procedure should be performed once a week or whenever major changes

are made to the system configuration. The procedure takes approximately seven
minutes per NE.
To perform backup to hard disk:

1. In the main window, select System > NE SW Change > Network to
update the database of all NEs in the network. The Change NE
SW-Network window opens.
NOTE: The version number displayed in this window

depends on the embedded software version.
Figure 1-2: Change NE SW - Network window
2. Click the NE type field to select the corresponding type.

3. Click the Operation field to select Get DB from NE.

4. Click OK. This operation uploads the database from the NE NVM to the
EMS-SYNCOM hard disk. The action is automatically repeated for each
NE of the selected type. An indicator in the lower part of the window
displays the progress of the process. Wait until the process ends.
NOTE: The example above describes backing-up all NEs of

the same type in the network. You can also back up a specific
NE. To do so, select the NE in the topology view, and then
select System > SW Change > Selected NE.
5. Repeat steps 2 to 4 for each NE type.
Checking Version
Correspondence
NOTE: This procedure is performed for SYNCOM NEs only.
This procedure verifies whether the software versions stored in each network
NE (in each NVM) match the software versions stored in the EMS-SYNCOM
disk. Perform this procedure once a week or whenever major changes are made
to the system configuration.
To check version correspondence:

1. In the main window, select System > NE SW Change > Network. The
Change NE SW - Network window opens, as shown in Change NE SW -
Network window (on page 1-3).
2. Click the NE type field to select the corresponding element type.
3. Click the Operation field to select the NE-Version correspondence check
option.
4. Click OK. The system starts the version correspondence check. The action
is automatically repeated for each NE of the selected type. An indicator at
the lower part of the window displays the progress of the process. Wait
until the process ends.
5. Repeat steps 2 to 4 for each NE type.

Saving EMS-SYNCOM
Configuration to a Backup Disk
via FTP
Perform this procedure once a week. Copy the relevant files to a backup disk
on a PC using any FTP shareware application. After backing up the required
files, old system files can be deleted from the EMS-SYNCOM.
If you wish to transfer files to a PC via FTP, you must first perform the
procedure described in Preparing to Transfer Files to a Backup Disk via FTP
(on page 2-10).
NOTE: Only the administrator can use this function. It cannot

be assigned to other users.
The EMS-SYNCOM system always keeps a backup copy of the current

configuration. The backup file contains the following information:
| A list of the network elements managed by EMS-SYNCOM.
| XC related information
| Security information.
Any change made to the system configuration leads to an automatic backup of
the configuration, if the synchronization mechanism was enabled in system
startup (refer to Startup Configurtaion Options in the EMS-SYNCOM User
Manual). This overwrites the configuration saved by the previous backup
process.
You can save the current configuration whenever required. By saving the
current configuration, you create a backup copy of the configuration manually.

To save the current configuration:

1. From the Shelf View, select System Î Configuration File Î Save to File,
OR
From the main menu, select System Î Configuration File Î Save to File.
The following window opens.
Figure 1-3: Saving a Configuration
2. Accept the default name (comprised of the date and time) suggested by the
system, or enter a name for the backup file.
3. Click the OK button. The system saves the current configuration as a file
under the name entered.
4. Confirm the operation in the displayed message box.
NOTE: The configuration files you save manually can be

used later to restore a specific configuration. On the other
hand, the configuration files that are saved automatically
provide only the most recent configuration available. The
User has the opportunity to restore a manually saved
configuration during the EMS-SYNCOM startup procedure
(see Starting EMS-SYNCOM in the EMS-SYNCOM User
Manual).
For a more comprehensive backup procedure, it is
recommended to accompany the Save Configuration
operation with a Get DB from NE operation (see Updating all
Nes in a Network in the EMS-SYNMCOM User Manul for
details). This will allow restoring the entire network
configuration, even in the event of a damaged database in the
NE NVM.

Deleting Old System Files

on a PC using any FTP shareware application (see Preparing to Transfer Files
to a Backup Disk via FTP (on page 2-10)). After backing up the required files,
old system files can be deleted from the EMS-SYNCOM.
Exporting Alarm Logs

This function copies alarm log files to a floppy disk. EMS-SYNCOM keeps
track of events by storing them in log files. These files are automatically saved
to the EMS-SYNCOM hard disk periodically or whenever they reach a certain
size (whichever occurs first). The file name has a ah<yyyy><mm><dd>.<n>
format, where n designates the number of the log file saved on date
YYYYMMDD. ah stands for Alarm History.
Log files have to be deleted from time to time, otherwise the EMS-SYNCOM
disk gets full. Once the free disk capacity is down to 2%, the log files are
deleted automatically.
The system displays a warning message and prompt for log files to be exported
when 95% of the disk capacity is used. When this occurs, the following
message is displayed:
ATTENTION: DISK ALMOST FULL
Change alarm log parameters
Delete unnecessary export, configuration and NE s/w
files
Click Close to close the message window and perform the file export operation.
When 98% of the disk capacity is used, the system automatically deletes
unnecessary export, configuration and NE software files.

To delete old Alarm History files:

1. From the Shelf View, select Alarm Î Export Log,
OR
From the main menu, select Alarm Î Export Log.
The following window opens:
Figure 1-4: The Log Export window
2. Select the file to delete.

3. If you want to check the file's contents first, click the Browser button to
open it.
4. You can filter the log file from the Browser window by selecting Filter Î
User Filter from the window’s menu. A window opens, allowing you to
filter the alarms in the file. Select Filter Î No Filter from the window’s
menu to remove a filter.
5. To delete the selected file to the floppy disk, click the Delete button.

Export Alarm Via Communications
NOTE: This feature is a cost option which must be ordered

from ECI Telecom's Optical Network Division.
The Current Alarms list can be sent from the EMS-SYNCOM to external
systems or applications. This feature was designed to solve the requirement to
frequently report the current status of the network to central alarm centers that
collect alarms from a variety of sources. This feature supports exporting alarms
to multiple destinations.
To use this feature, a dedicated Ethernet port must be installed at the
EMS-SYNCOM Sun workstation. This port must be installed in addition to the
Ethernet segment used between the EMS-SYNCOM and the gateway NE, in
order to prevent congestion on that segment.
The main features of this function are:
| Information is transferred every two minutes.
| FTP (file transfer) is used to transfer the information over TCP/IP.
The Export Alarms function only transfers changes to the Current Alarms list
(i.e., new records) since the last successful information transfer.
Alarm information includes: a header record (with current time and reported
fields). Each alarm is reported with: the event time, the identity of the failed
object and an alarm description.
Every two minutes, all new alarms recorded in the Current Alarm list are
appended to a file.
The file is assigned a name of up to 8 characters according to the
EMS-SYNCOM station name and is placed in the directory of the FTP user on
the remote machine. The file receives the dat suffix.

Deleting PM Log and MS Log Files

The EMS-SYNCOM stores a list of PM data collected for the SYNCOM
endpoints of each client trail in the system and for MS transmission objects.
Performance data for a trail is saved:
| Whenever the client trail is edited.
OR
| Once after 12:00 midnight for the 24-hours period ending at 12:00
midnight.
MS logs are saved immediately after the PM log.
To display trail performance data:

1. In the main window, select Performance > PM Logs. The Performance
Monitoring Files window opens.
Figure 1-5: Performance Monitoring Files window
Each log file shows all trail performance data collected for an entire day.
The file title identifies the day in format pm <dd><mm><yyyy>. The file
prefix indicates the type of file: PM for PM logs, MS for MS logs, and TC
for TC logs.

2. Select the desired file. In the Trail Log window, click Browser to display
the contents of a trail or MS log file (Trail PM for a single day). The
Browse File window opens.
Figure 1-6: Browse File window
3. Select Filter to filter the information displayed in the window (for PM logs
only). The PM Filter window opens.
Figure 1-7: PM Filter window

4. Enter one or multiple filter criteria from the following:

Label - specific trail label
Customer - specific customer
End Point - specific trail endpoint
5. Click OK. The information in the Browse File window is displayed
according to the selected filtering criteria.
6. In the Browse File window, select Print to print the contents of the
window.
7. Click Close to close window.
To save a trail log file to a backup disk (via FTP):

1. Set up the FTP application.
2. Open the /sdh_home/PMLOGS directory in the EMS-SYNCOM pane and
select the log files for transfer.
3. Open the destination directory in the PC pane.
4. Transfer the files to the PC.
5. Check that the files were transferred successfully (a confirmation message
is displayed).
Deleting SaveBackup (Configuration) Files

SaveBackup files should be backed up once a week, and then deleted, in order
to free space on the hard disk.
To delete SaveBackup files:

1. In the main window, select System > Unix Window. A Unix window
opens with the operating system prompt.
2. Type cd ENMConfig then type ll -t. A list of all EMS-SYNCOM backup
files is displayed.
3. To delete old backup files, type rm <file name>.
4. Type cd Report and then ll -t.
5. Type rm <file name> to delete old files.

Viewing Login History

NOTE: Only the administrator can use this function.
It is possible to view the history of login and logout activities at the

EMS-SYNCOM station.
To view the login history:

| From the Shelf View, select System Î Login History,
OR
From the main menu, select System Î Login History.
The following window opens, with a list of the login history files and the size
of the file in bytes.
Figure 1-8: Login File Selection
By default, the file names listed in this window reflect the EMS-SYNCOM
station for which the log file was generated. However, the file name can also be
a name assigned by the user to a merged file.

To delete one of the login history files:

| Select the file and then File Î Delete from the Login File Selection
window menu.
To merge several files into one file:

| Select the files to merge (by Shift-clicking each one), and then select File
Î Merge from the Login File Selection window menu.
Select File Î Save the Login File Selection window menu and enter the
name of the new file.
To view one of the Login History files:

| Double click on one of the files in the Login File Selection window, or
select a file and then File Î Browse from the Login File Selection window
menu.
The following type of window opens.
Figure 1-9: Login File window
This window displays the user who logged in/out, the time and date of the
login, and the result of the log attempt.

To sort the Login File Window:

You can sort the Login History window, according to one of the following sort
orders, by selecting an option from the Sort menu.
The following sort orders are available:
| By User Sorts the window in alphabetical order, according to the
user name who registered the log activity.
| By Host Sorts the window in alphabetical order, according to the
name of the host at which log activity was registered.
| By Time Sorts the window according to the time and date on which
log activity was registered, with the most recent log actions
first.
Viewing Log Actions

It is possible to view the history of a wide range of actions performed from the
EMS-SYNCOM in an ASCII text file. Each of the actions in the log file are
listed together with the time The action log file shows the date and time of
occurrence and the user who performed the action. The following actions are
logged in the action log file:
| Exit
| Close
| Create/delete/edit/reconnect/force reconnect client trails/server trails
| Join and Split operations
| Trail reconstruction
| Save configuration
| Import
| Traffic reconfiguration
| Change EMS-SYNCOM mode
| Init PM/TC/EP counters
| Send AIS, Upstream AIS, RDI
| Send TC actions
| Loopback

| Reset
| Protection Lockout
| Switch protection
| Slot assignment
| Delete NE
| Create NE/NE group
| Change NE attributes/Card/TP
Once the file becomes larger than a preset value (pre-determined and
non-adjustable), the actionlog file is copied to a new file and a new actionlog
file is created. Once the second actionlog file becomes larger than the preset
value, the first file is erased and the new backup file is saved with that name.
To view the action log file:

6. From the Shelf View, select System Î Action Log,
OR
From the main menu, select System Î Action Log.
Figure 1-10: Action Log File Selection

7. Select the file from the list and select File Î Browse from the Action Log
File Selection window.
The following type of window opens with the contents of the action log
file.
Figure 1-11: Action Log View

Checking Performance
Perform this procedure once a week or- according to working procedures.
EMS-SYNCOM offers a series of functions to help you analyze both the
current and historical performance of networks and trail connections. The
performance is measured by counters that monitor various parameters
pertaining to the NE's quality of service. Some of these parameters can be set
by the user.
Performance Monitoring data can be obtained for transmission objects (VC12,
VC3, VC4, MS, RS, VOO SPI and PDH end points).
Viewing Current Performance

You can view the current performance of a transmission object for either of two
time intervals (15 minutes or 24 hours).
To view current performance:

1. Select the transmission object.
2. From the Card Internals View, select Performance Î Current,
OR
From the main menu, select Performance Î Current.
3. Select either the Daily or 15 Min. option, depending on your requirements.
Figure 1-12: Example of a Current Performance window

The Start Time and Window Duration fields show when the EMS-SYNCOM
started collecting data (date and time) and for which time period (one day or 15
minutes).
The contents of a Current Performance window depend on the object you
select. Performance data is collected separately for the controlled bit streams in
each respective TP.
Viewing Performance History

You can view historical data on the performance of a transmission object for
either of two time intervals.
To view the performance history:

1. From the Card Internals View, select Performance Î History,
OR
From the main menu, select Performance Î History.
2. Click either the Daily or 15 Min. option, depending on your requirements.
Figure 1-13: Example of a Performance History window
3. Click either the 15min or 1day button in the Window Duration field,
depending on the period you wish to analyze.
4. Use the From – To fields to specify the period of time for which you want
to retrieve historical data. The 15 minutes or one day interval is applied to
that time span.

5. Example: If you specify a period of three days in the From and To fields
and select the One Day option in the Window Duration field, the data
table shows three lines of PM data.
6. When you finish setting the relevant period and the window duration, click
OK to retrieve the data. The results provide the following information:
Start Time: This column displays the date and time when counting
started.
Sec: This column shows how many seconds out of the 15-minute (or
24-hour) interval have already been monitored.
CVFE: Number of Code Violations Far End accumulated.
CVNE: Number of Near End Code Violation accumulated.
ESFE: Number of Errored Seconds Far End accumulated.
ESNE: Number of Near End Errored Seconds accumulated.
OFS: Number of Out of Frame Seconds accumulated.
PJ: Number of Pointer Justifications accumulated.
SESFE: Number of Severely Errored Seconds Far End accumulated.
SESNE: Number of Near End Severely Errored Seconds accumulated.
UASNE: Number of Near End Unavailable Seconds accumulated.
UASFE: Number of Unavailable Seconds Far End accumulated.
Printing Performance History

You can print the data retrieved from the Performance History window if you
need a hard copy for administrative or other reasons.
To print the performance history:

1. Click the Print button in the Performance History window showing the
historical data you just retrieved.
2. To stop a print job, click Cancel in the print progress dialog box.

Displaying Performance Charts

This feature will be available only if it was selected as a startup option (see
Startup Configuration Options in the EMS-SYNCOM User Manual). Click the
Charts button in the Performance History window to display performance
charts. An example is shown in the following figure.
Figure 1-14: Performance Charts window
The Performance Charts window plots, for each of the PM counters, a chart
that shows how the PM values vary with time. Values that are below the
threshold are displayed in blue; above threshold values are displayed in red.
You can show different portions of each individual chart by using the vertical
or horizontal scroll bars.

The following buttons are available in the Performance Charts window.

Zoom In Zoom in; magnifies the time scale for all charts in the
window.
Zoom Out Zoom out; reduces the time scale for all charts in the
window.
Up Shifts all charts in the window up.
Left Shifts all charts in the window towards the beginning of
the time frame.
Right Shifts all charts in the window towards the end of the
time frame.
Down Shifts all charts in the window down.
Default Resets the zoom and position of all charts to the default
values.
Resetting Performance Counters

You can reset the performance counters of any transmission object whose
performance is measured.
To reset performance counters:

1. Select the desired object.
2. From the Card Internals View, select Performance Î Reset Counters,
OR
From the main menu, select Performance Î Reset Counters.
3. Click either the 15 Min or Daily button in the cascade menu.
A message window opens informing you that the action has been completed
successfully.

Viewing Trail End Points

Performance
You can display performance data for a specific end point in a client trail, if the
end point is located on a SYNCOM or μSDM-1 NE.
There are two options for monitoring the performance of end points in a client
trail, Current and Historical.
To view this data:

1. Obtain a Shelf View of the tributary card, which is an end point in a client
trail.
2. Obtain a cards internal view of the tributary card and then select the
transmission object participating in the client trail.
3. From the Shelf View, Card Internals View or main menu, select
Performance Î For Trail Endpoints.
4. Select either the Current, History, or Reset Counters option in the
cascade menu.
If you select Current, you obtain a view of the current performance of the
selected TP. An example is shown in the following figure.
Figure 1-15: Current Performance Trail End Point window

The data shown represents the material collected since the start time. The
window duration is always one day. The information shown is:
| Monitored Seconds shows the amount of times in seconds of the
evaluation period since the start time or the last Reset Counters operation.
| ESEP – Errored Seconds (end point)
| SESEP – Severely Errored Seconds (end point)
| UASEP – Unavailable Seconds (end point)
To manually reset the counter:

| From the Shelf View or main menu, select Performance Î For Trail
Endpoints Î Reset Counters. After confirmation you receive a message
that the reset was successfully performed.
Historical End Point Performance Monitoring
To view the historical performance trail end point window:

| From the Shelf View, Card Internals View or main menu, select
Performance Î For Trail Endpoints Î History.
This window summarizes the performance history for the specified time
period as entered in the From and To fields.
Figure 1-16: Historical Performance Trail End Point window

The window duration is always one day.

Click OK and wait a few seconds while the EMS-SYNCOM gathers the
information; afterwards the data is displayed in the table at the bottom of the
window.
Current Alarms
The alarms in the network are represented on the screen as LEDs on each NE.
The LED's color corresponds to the most severe alarm affecting it. The color
codes were reviewed in LEDs and Icons in the EMS-SYNCOM User Manual.
The Network Current Alarms Window
To view all current alarms in the network:

| From the Shelf View or Card Internals View, select Alarm Î Current,
OR
Click the bell icon in the EMS-SYNCOM Main window,
OR
From the main menu, select Alarm Î Current.
The Network Current Alarms window opens.

To view the current alarms in a specific NE:

| From the Shelf View, select Alarm Î Current,
OR
Select the NE with the alarm and then select Alarm Î Current from the
main menu.
The Network Current Alarms window opens.
Figure 1-17: Network Current Alarms window
NOTE: The window has an additional Section (Cleared

Alarms) if the Auto acknowledge on clear startup parameter
was set to NO (see Startup Configuration Options in the
EMS-SYNCOM User Manual).
Alarms are stamped with the time of their occurrence if the
Show event time of current alarms startup parameter was
set to YES (see Startup Configuration Options in the
EMS-SYNCOM User Manual).

The Network Current Alarms window is divided into two parts: the top part of
the window (Current Alarms) lists the objects with alarms currently in the
network (or for the objects specified in the User-defined filter). At the top of
the window, the total number of current alarms is displayed, together with the
number of filtered alarms (i.e., alarms shown after filtering). Alarm information
is listed in a table, with the following data listed for each alarm (from left to
right):
| ACK (if the alarm has been acknowledged); if the alarm has not been
acknowledged, nothing appears.
| The severity of the alarm.
| The object affected by the alarm together with the NE that the object
belongs to.
| The reason for the alarm.
The type of filter set by the User is displayed at the top left-hand side of the
current alarm window. The types of filters are:
| None - no alarms are filtered and all alarms are displayed.
| Default filter - if the default filter is set. When the default filter is applied,
alarms with the ACK status are removed automatically from the Current
Alarm List. This includes alarms acknowledged by the User and alarms
that were acknowledged automatically by the system (if the problem was
resolved).
| If a User-defined filter is set, this is indicated by a yellow icon. Filtering
Current Alarms in the EMS-SYNCOM Uer Manual explains how to set
User-defined filters for the Current Alarm window.
The bottom portion displays alarms that were acknowledged by the user when
they are cleared. The user is then informed that the acknowledged problem has
been physically resolved. However, if the Auto acknowledge on clear
parameter was set to YES during the system startup procedure (see Starting
Configuration Options in the EMS-SYNCOM User Manual), the Network
Current Alarms window opens without the Cleared Alarms list.
NOTE: In addition to viewing the Network Current Alarms

window, the User should view the Alarms Log window (see
Viewing the Alarm Log on page 1-30) to check for events
related to Quality of Service. These events, which are not
reported in the Network Current Alarms window can cause
problems in the PDH system.

Alarm Time Stamp

Alarms are stamped with the time of their occurrence if the Show event time
of current alarms startup parameter was set to YES.
An asterisk (*) can appear next to the time stamp. When an asterisk is
displayed, this means that the time registered in the Network Current Alarms
window is not the alarm’s time of occurrence, but rather the time that the alarm
was registered at the EMS-SYNCOM station. This can occur, for example,
when uploading data from an NE (in which case the alarm data is not uploaded
with the time stamp).
The asterisk can also appear in Info windows in the Event Time field. The
significance of this asterisk is identical.
Determining the Cause of an Alarm

Once an alarm appears in the current alarm list, there are several things you can
do to find out more about a specific alarm. Proceed as follows:
1. Select the specific alarm by clicking on it; the line listing the alarm is
highlighted.
2. Click the Open button. This action automatically calls up the Shelf View or
the Card Internals View, depending on the type of object affected by the
alarm. Here you can select the object and open the Information window to
see further details.
Alternately, click the Info button in the Current Alarm window to open an
Information window regarding the object with the alarm. Note that the Info
option does not display a window if there is no further information to display.
In addition, it is possible to determine whether or not a certain alarm is
affecting a trail defined in the network. Click the Server Trails or Trails
buttons to display a window similar to the following.

Figure 1-18: Trails List for Faulty Object window
This window displays the trails that are affected by the faulty object, together
with information regarding the trail. Refer to Trail Functions Chapter in the
EMS-SYNCOM User Manual for a description of trails.
You can sort this window by clicking one of the column headers.

Viewing the Alarm Log

When a new event enters EMS-SYNCOM, it is recorded at the top of the alarm
log. Therefore, when opening the alarm log window, you always see the most
recent events first. At the top of the window, the total number of current alarms
is displayed, together with the number of filtered alarms (i.e., are not shown
due to the filter setting).
Figure 1-19: Example of an Alarm Log window
Events included in the alarm log are periodically exported to a binary file. You
can export this file in ASCII format on a floppy disk.

Alarm Log Menu

The menu in the Alarm Log window offers the following options:
Refresh: This menu item is used to update the log to reflect the latest alarms.
Selecting Manual updates the window immediately. The Periodic option
causes the window to update automatically every 15 minutes.
NOTE: When using the Periodic option, heavy load is put on

EMS-SYNCOM resources. Take into account that every time
you open this window, the contents are refreshed anyway.
Filter: You can use this menu item to select the type of filter to be applied: No
Filter (all alarms listed), Default Filter (list unacknowledged alarms only), or
Set Filter (see also Filtering Alarms in the EMS-SYNCOM User Manual).
Print: You can print all alarms or selected (highlighted) ones. Bear in mind
that if you print the entire log, the printed report may be very long. It is
recommended that you use the Filter option to limit the entries to the
information required before printing the log.
Max. Time in Log: Defines the maximum amount of time that the alarm/event
appears in the Alarm Log before it is deleted automatically. Possible values are:
1, 6, 12, 24, 48 and 72 hours. The maximum time setting is displayed at the top
of the alarm log window.
Max. Alarms in Log: Defines the maximum number of alarms that can appear
in the Alarm Log. When the number of alarms exceeds this amount, alarms are
deleted on a FIFO (first-in-first-out) basis. Possible values are: five hundred,
one thousand, two thousand, three thousand, four thousand and five thousand
alarms. The maximum alarms setting is displayed at the top of the alarm log
window.
NOTE: When the Max. Time or Max. number is reached

(whichever comes first) some alarms may be deleted. The
deleted alarms can be seen in the Export Log Files (see
Exporting Alarm Logs on page1-7).
Status Bar
The status bar underneath the menu bar in the Log window shows the filter
currently active (No Filter, Default Filter, or User Defined Filter), the total
number of alarms in the log, the number of non-filtered alarms in the log, the
maximum time and maximum alarms in the log.

Checking the Alarm Log

The Alarm Log window contains a list of all alarms and other events that
occurred in the network. It can be accessed from any of the EMS-SYNCOM
windows currently displayed.
When a new event enters the EMS-SYNCOM, it is recorded at the top of the
alarm log. Therefore, when opening the Alarm Log window, you always see
the most recent events first. The total number of current alarms and the number
of filtered alarms (that is, those not shown due to the filter setting), are
displayed at the top of the window.
All historic alarms and events are displayed. The log can help you determine
exactly for how long the alarm or event lasts.
The QoS alarm is related to the severity threshold defined for each alarm.
NOTE: The terms alarm and event are used interchangeably

in this guide, in other words, the alarms list is really an events
list.
To check the alarm log:

| In the main window, select Alarm > Alarm Log. The Alarm Log window
opens.
Figure 1-20: Alarm Log window

Using Ping to Test

EMS-SYNCOM-NE Communications
The Ping function is used to initiate a signal from the EMS-SYNCOM to the
selected NE. By comparing the signal sent with the signal received in return
from the NE, the EMS-SYNCOM can evaluate the quality of its network
connection to the NE.
To use the Ping function:

1. From the Shelf View select System Î Ping,
OR
Select the NE in the topology view, and from the main menu, select System
Î Ping.
Figure 1-21: The Ping window
2. To clear the list of results from the previous Ping session, click the Clear
button.
3. To select the packet size in bytes, click on the slider in the Package Size
field. The standard value is 64 bytes.

Checking Management
Performance
This procedure should be performed once per quarter according to the network
administrator's instructions.
NOTE: This procedure takes approximately 20 seconds per

trail.
To check management performance:

1. In the main window, select System > Unix Window. A Unix window
opens with the operating system prompt.
2. Type psrinfo.
3. Make sure that all CPUs are online.
4. Type df -k.
5. Make sure that all directories are not exceeded.

2
Procedures via EMS-XDM
In this chapter:
Overview ......................................................................................................... 2-1
Saving NE Database Configuration to Hard Disk ........................................... 2-6
Checking Corresponding Version.................................................................... 2-8
Deleting Old System Files ............................................................................. 2-10
Viewing Login History .................................................................................. 2-16
Viewing Log Actions..................................................................................... 2-19
Checking Performance .................................................................................. 2-21
Pinging the NE............................................................................................... 2-53
Pinging ETY Communications .......................... Error! Bookmark not defined.
Saving Current Network and Security Configurations .................................. 2-54
Exporting XCSs ............................................................................................. 2-56
Exporting policer information ....................................................................... 2-58
Exporting flow information ........................................................................... 2-58
Checking Optical Parameters ........................................................................ 2-59
Exporting/Importing Topology Data ............................................................. 2-60
Viewing NE Inventory................................................................................... 2-62
Performing Maintenance and Backup Operations Using a Script ................. 2-64
Overview
The following table outlines the preventive maintenance procedures performed
via the EMS-XDM.

via EMS-XDM Maintenance
Table 2-1: Preventive maintenance procedures via EMS-XDM

Save the NE database Once a quarter, or following Saving NE Database
configuration to hard major changes in network Configuration to Hard
disk. topology Disk (on page 2-6)
Check corresponding Once a quarter, or whenever Checking
version. major changes are made to the Corresponding Version
system configuration (on page 2-8)
Delete old system Once a week, or following Deleting Old System
files. major changes in network Files (on page 2-10)
topology
Check login history. Once a week, or following Viewing Login History
major changes in network (on page 2-16)
topology
Check log actions. Once a week, or following Viewing Log Actions
major changes in network (on page 2-19)
topology
Check performance. Once a week, or according to Checking Performance
working procedures (on page 2-21)
Check PM history Once a week, or according to Viewing PM History
reports for OPS-M working procedures Reports for OPS-M
objects. Objects (on page 2-34)
Check alarms Once a week, or according to Viewing Current
information. working procedures Alarms (on page 2-37)
Check EMS-XDM to Once a week, or according to Pinging the NE (on
NE communication. working procedures page 2-53)
Save EMS-XDM Once a week, or following Saving Current Network
configuration to hard major changes in network and Security
disk. topology Configurations (on page
2-54)
Export Once per month, or according Exporting XCSs (on
cross-connections to the working procedures page 2-56)
data to XML files.
Export policer Once per month, or according Exporting policer
information to a file. to the working procedures information (on page
2-58)
Export flow Once per month, or according Exporting flow
information to a file. to the working procedures information (on page
2-58)
Check optical Once per month, or according Viewing Optical Levels
parameters. to the working procedures and Parameters of
Optical Objects (on
page
2-59)
Export topology data Once per month, or according Exporting Topology
to an XML file to the working procedures Data (on page 2-60)
Export card inventory Once per month, or according Viewing NE Inventory

data to an XML file. to the working procedures (on page 2-62)

Maintenance via EMS-XDM

Perform maintenance Once per month, or according Performing
and backup using a to the working procedures Maintenance and
script. Backup Operations
Using a Script (on page
2-64)
NOTE: Unless otherwise specified, all preventive

maintenance procedures described in this chapter are
implemented in the EMS-XDM Shelf View. The following
figures show a typical Shelf View of the various XDM
shelves.
Figure 2-1: Typical XDM-100 Shelf View


Figure 2-5: Typical XDM-500 shelf view window

Saving NE Database
Configuration to Hard Disk
This procedure should be performed once a quarter or whenever major changes
are made to the system configuration. The procedure takes approximately seven
minutes per NE.
The NE software resides in the Non-Volatile Memory (NVM) on the NE
xMCP card. You can save the NE software by uploading it to the EMS-XDM
disk.

To perform backup to hard disk:

1. In the Shelf View, select System > SW Management > Network. The SW
Management window opens.
Figure 2-8: SW Management window
2. Click the Operation field (see the previous figure). The Operation
submenu opens.
Figure 2-9: Operation submenu options
3. Select Get DB From NE.

4. In the SW Management window, select File > Apply; this uploads the
database from the NE NVM to the EMS-XDM for backup purposes.

NOTE: The version number displayed in this window

depends on the embedded software version.
NOTE: The example above describes backing-up all NEs of

the same type in the network. You can also back up a specific
NE. To do so, select the NE in the topology view, and then
select System > SW Management > Selected NE.
You can save the NE database to your hard disk (and perform many other
maintenance operations) using a Unix script as described in Performing
Maintenance and Backup Operations Using a Script (on page 2-64). Check that
the database resides under the /sdh_home/ems/DownLoad directory.
Checking Corresponding Version

This procedure verifies that the software versions stored in each network NE
(in each NVM) match the software versions stored on the EMS-XDM disk.
Perform the procedure once a quarter or whenever major changes are made to
the system configuration.
To check corresponding version:

1. Perform steps 1 and 2 outlined in Saving NE Database Configuration to
Hard Disk (on page 2-6).
2. In the Operation submenu, select Version Correspondence.
3. In the SW Management window, select File > Activate.

The status is indicated in the Download Status section of the window as the
check is in progress (see the following figure).
Figure 2-10: Version correspondence check
Upon completion, a message dialog box indicates the result of the check.
Figure 2-11: Version correspondence check results
4. Click Close to close the message dialog box.

Deleting Old System Files

on a PC using any FTP shareware application. After backing up the required
files, old system files can be deleted from the EMS-XDM.
(on page 2-10).
Preparing to Transfer Files to a Backup Disk

via FTP
This section provides instructions for the preparations required to transfer files
from the EMS-XDM station to a PC running an FTP application.
To prepare for transferring files via FTP:

1. Connect an Ethernet cable between the EMS-XDM station's Ethernet port
and the PC's Ethernet port.
2. Start the FTP application.
Typically, the window of an FTP application is divided into two panes (right
and left). The EMS-XDM station's hard disk directories are displayed in one
pane and the PC's hard disk directories in the other. Control and navigation
buttons enable you to operate the FTP. Operations typically available in FTP
applications include: copying files from the media in the left pane to the media
in the right and vice versa, opening and closing directories, creating new
directories, and deleting files.
Deleting Alarm Logs

The EMS-XDM tracks events and stores them in log files. These files are
automatically saved to the EMS-XDM hard disk periodically or when they
reach a certain size (whichever occurs first).
The filename format is AlarmLogHistory-yyyy.mm.ddn, where n designates
the number of the log file saved on date YYYY.MM.DD. The file is in the
sdh_home/ems/EXPLOG directory.

When 95% of the disk capacity is used, the system displays a warning message
and prompt for log files to be exported, as follows:
ATTENTION: DISK ALMOST FULL
Delete unnecessary export, configuration and NE s/w
files
Click Close to close the dialog box and perform the file export operation.
unnecessary export, configuration, and NE software files.
To transfer logs to the backup disk (via FTP):

2. Open the /sdh_home/ems/EXPLOG directory in the EMS-XDM pane and
5. Check that the files were successfully transferred (a confirmation message
is displayed).
To delete alarm log files:

1. In the Shelf View, select Alarm > Export Alarm and Event Log. The
Log Export window opens.
Figure 2-12: Log Export window

2. Select the file(s) to be deleted. If you want to check file contents first, click
Browser.
3. Click Delete. You can delete files without first saving or browsing.
Deleting Cross-Connect (XC) PM Logs, MS

Logs, GbE, and Optic Logs
The EMS-XDM stores a list of performance monitoring (PM) data collected for
the endpoints of each cross connection in the NE, and for MS/Line
transmission objects.
Depending on the startup configuration option selected, performance data for
an object is saved at the designated time of day.
MS/Line logs are saved immediately after PM.
Several options determine whether or not 24-hour PM logs, 15-minute PM
logs, MS/Line logs, GbE, or Optics logs are saved, and at what time of day
they are collected.
To save a PM log file to a backup disk (via FTP):

2. Open the /sdh_home/ems/PMLOGS directory in the EMS-XDM pane, and
5. Check that the files were successfully transferred (a confirmation message
is displayed).

To display 24-hour PM logs, 15-minute PM logs, MS/Line

logs, GEoS, or Optics logs:
1. In the Shelf View, select Performance > PM Logs. The Performance
Monitoring Files window opens.
Each log file shows all XC performance data collected for a 24-hour or
15-minute time interval, based on the PM groups defined for the NE. The
title of each file identifies the time interval and the day concerned, in the
format FileType.GroupName.Date, where Date is in the form
PM<yyyy><mm><dd>.
The file prefix indicates the type of file: PM for 24-hour PM logs, 15PM
for 15-minute PM logs, MS for MS/Line logs, OPT for optical logs, and
GB for DIO GEoS logs. Files are located in the ~/PMLogs directory.

2. To view the contents of a XC or MS/Line log file (that is, XC PM for a

single day), select the required file and click Browser. The Browse File
window opens.
Figure 2-14: Typical Browse File window
3. To filter the information displayed in the Browse File window, select File
> Filter. The PM Filter window opens.
4. Enter one or multiple filter criteria, as follows:

XC Label - to display information pertaining to a specific XC label.
Customer - to display information pertaining to a specific customer.
XCSet End Point - to display information pertaining to a specific XC
endpoint.

5. Click OK. You can refine the filter criteria by clicking one of the buttons
next to the text fields. The information in the Browse File window is
displayed according to the selected filtering criteria.
6. In the Browse File window, select File > Print to print the contents of the
window.
To delete PM log files:

1. In the Shelf View, select Performance > PM Logs. The Log Export
window opens.
2. Select the file(s) to be deleted. If you want to check file contents first, click
Browser to open.
3. Click Delete.
Deleting SaveBackup (Configuration) Files

Follow this procedure to delete SaveBackup files.
To delete SaveBackup files:

1. In the Shelf View, select System > Unix Window. A Unix window opens
with the operating system prompt.
2. Type cd ENMConfig.
3. Type ll -t.
A list of all EMS-XDM backup files is displayed.
4. Type rm <file name> to delete old backup files.

Viewing Login History

NOTE: Only the administrator can use the Login History
function. It cannot be assigned to other users.
XDM/SYNCOM Networks enables the system administrator to view the

history of login and logout activities.
To view login history:

| In the Shelf View or XDM/SYNCOM Networks main window, on the
menu bar, select System > Login History. The Login History File
Selection window opens, displaying a list of the login history files and the
size in bytes of each file, in bytes.
Figure 2-17: Login History File Selection window
By default, the file names listed in this window reflect the XDM station or
the X-terminal for which the log file was generated. However, the file name
can also be a name assigned by the user to a merged file.

Viewing Login History Files

XDM/SYNCOM Networks enables administrators to view, sort, and print login
history files.
To view a login history file:

1. In the Login History File Selection window, do one of the following:
Double-click a file.
OR
Select a file, and on the menu bar, select File > Browse. The Login
File window opens, displaying a list of users who logged in/out, the
times and dates of login, and the results of the log attempts.
Figure 2-18: Login File window

2. To sort the order of the entries listed in the Login File window, on the Sort
menu, click one of the following options:
By User: in alphabetical order, according to user name who registered
log activity
By Host: in alphabetical order, according to name of host at which log
activity was registered
By Time: according to time and date of log activity, with most recent
log actions first
3. To print a login file, on the File menu, click Print. The login file is printed.
Merging Login History Files

XDM/SYNCOM Networks enables administrators to merge several login
history files into one file.
To merge several login history files:

1. In the Login History File Selection window, select the files to merge (by
shift-clicking each one).
2. On the menu bar, select File > Merge.
3. On the menu bar, select File > Save, and type in the name of the new
merged file. The merged login history file is saved in a file with the new
name.
Deleting Login History Files

XDM/SYNCOM Networks enables administrators to delete login history files.
To delete a login history file:

1. In the Login History File Selection window, select the file.
2. On the menu bar, select File > Delete. The selected login history file is
deleted.

Viewing Log Actions

XDM/SYNCOM Networks enables administrator to view the history of a wide
range of actions performed from XDM/SYNCOM Networks in an ASCII text
file. Each of the actions in the log file is listed together with the time. The
action log file shows the date and time of occurrence and the user who
performed the action. The following actions are logged in the action log file:
| Exit
| Close
| Create/delete/edit/reconnect/force XCs
| Save configuration
| Import
| Configure traffic
| Change XDM mode
| Init PM counters
| Send AIS, Upstream AIS, RDI
| Loopback
| Reset
| Protection lockout
| Switch to protection
| Assign slots
| Delete NE
| Create NE/NE group
| Change NE attributes/Card/TP
The action log file is saved in the Home directory, under the name
ActionLog.XDM_station_name.
When the file becomes larger than a preset value (predetermined and
nonadjustable), the action log file is copied to a new file
(Actionlog~~.ems_station_name), and a new action log file is created. Once the
second action log file becomes larger than the preset value, the first file (saved
under actionlog~~.ems_station_name) is erased, and the new backup file is
saved with that name.

To view an action history log file:

1. In the Shelf View or XDM/SYNCOM Networks main window, on the
menu bar, select System > Action History. The Action History File
Selection window opens.
2. Double-click the selected file to view it. The Action History File window
opens, displaying the results.
Figure 2-19: Action History File window
3. Click Close to close the window.

Viewing, merging, printing, and deleting action history files are performed in
the same manner as for login history files (see "Viewing Login History" on
page 2-16).

Checking Performance
Perform this procedure once a week or according to working procedures.
The performance check includes the following steps:
1. Enabling PM data collection by creating PM collection groups according to
Creating PM Groups (on page 2-22).
2. Checking the PM values for transmission objects according to Viewing
PM, MS, and Optics Logs (on page 2-24). Make sure that the displayed
values do not exceed the default thresholds for each object. If the default
thresholds are exceeded, report to your system administrator.
3. Checking the network current alarms list frequently to enable a timely
response to potential and developing network failures (see Viewing Current
Alarms (on page 2-37)).
4. Checking the Alarm Log to make sure no network alarms were
inadvertently neglected (see Using the Alarm Log (on page 2-41)).

Creating PM Groups
You can create PM collection groups. The maximum number of PM collection
groups is 200. The maximum number of members per PM group is 470.
To create a PM collection group:

1. On the Shelf View menu bar, select Performance > PM Setup. The PM
Setup window opens.
Figure 2-20: PM Setup window
This window is divided into two primary areas. The upper Collection
Groups area at the top of the window displays a list of defined PM
collection groups, with the PM collection characteristics of each. The lower
area of the window is used to define groups, including their characteristics
and object members. After a group is defined, it appears in the list in the
Collection Groups area of the window.
2. On the menu bar, select Edit > Create Group.
3. Click (Create Group) to clear all fields in the lower area of the
window. This action automatically deletes any information displayed in
these fields, enabling you to define a new PM collection group.

4. In the Group Name field, type a name for the collection group. (Spaces are
not supported for the group name.)
In the Object Type dropdown list, select the object type for the group. The
following object types are available:
2M, 34/45M, MS, RS, MS-DCC, VC-3, VC-4, VC-12, AU-3, AU-4,
TU-2, TU-3, TU-12
RS-DCC, GEoS, OCH, GbE, OPS_M, Eth, LAG, Bridge, Policer,
EquipmentOPT, FC
FC, FCICON, GFP, Routing, OW, E1, MPLS
5. In the Counter Duration dropdown list, select the PM counter interval for
the group. Options are:
15M for a 15 minute PM counter
Daily for a 24 hour PM counter.
6. In the Schedule Time dropdown list, select the interval for collecting PM
data for the group:
Every 15 min
Every hour
Every 4 hours
Once a day
7. In the Start Time dropdown list, select the hour for PM collection to begin.
You can only choose 24H when collecting PM data once a day.
8. In the tree in the lower right zone of the window, select one or more objects
that you want to add as members of the group, and click to move
them to the Group Members area. Multiple objects can be selected at one
time. When selecting objects individually, repeat this process to select all
members of the group.
You can also select an NE or a card in the tree. In this case, all the TPs of
the selected class are added to the group.
All objects must be the same object type. If you select objects of an
incorrect type, an error message appears.

9. Click to remove objects from the Group Members area.

10. On the menu bar, select Edit > Apply or Edit > Create Group to save the
group. The group now appears in the Collection Groups area of the
window.
A confirmation window opens, prompting you to save the new group
without saving changes.
After a group has been defined, you can edit its membership or collection
characteristics, as required. You can also delete groups when necessary.
Viewing PM, MS, and Optics Logs

This section describes how to view and use the EMS-XDM PM, MS, and
Optics logs.
The EMS-XDM stores a list of PM data collected for the transmission objects
defined in PM collection groups.
Performance data for an object is saved at the designated time of day, which
depends on how the PM collection group is defined
To view PM logs based on PM collection groups:

1. In the Shelf View or EMS-XDM window, on the menu bar, select
Performance > PM Logs. The Performance Monitoring Files window
opens.

Each log file shows all XC performance data collected for different time
intervals, based on the PM groups defined for the NE. The title of each file
identifies the time interval and the day concerned, in the format
FileType.GroupName.Date, where Date is in the form
PM<yyyy><mm><dd>.
File names indicate the object, title, and date. Files are located in the
~/PMLogs directory.
2. To save an XC log file to an external storage device, insert the device and
select the file you want to save, and click Export.
3. To view the contents of a XC or MS log file (that is, the XC PM for a
single day), select the required file, and in the Trail Log window, click
Browser. The Browse File window opens.
Figure 2-22: Browse File window

4. To filter the information displayed in the Browse File window, on the

menu bar, select File > Filter. The PM Filter window opens.
5. Type one or multiple filter criteria, as required. You can refine the filter
criteria by clicking one of the buttons next to the text field. The following
table describes the functions of the filtering criteria available in the PM
Filter window.
Table 2-2: Filtering options
Option Description
XC Label Displays information pertaining to a specific XC
label only.
Customer Displays information pertaining to a specific
customer only.
XCSet END Point Displays information pertaining to a specific XC
endpoint only.
To print the contents of the Browse File window:

| On the menu bar, select File > Print.

Viewing Current Performance

EMS-XDM enables you to view XDM transmission object current performance
data in tabular and in chart format.
Viewing Current Performance in Tabular

Format
You can view XDM transmission object current performance for 15-minute or
24-hour time intervals.
To view a current PM table:

1. In the Card Internals View, select the transmission object.
2. On the menu bar, select Performance > Current, and on the submenu
select either Daily or 15 Min.
The Current PM window opens. The contents of a Current PM window
depend on the object you select. Performance data is collected separately
for the controlled bit streams in each respective TP.
Figure 2-24: Current PM window (tabular)

The Start Time field shows the date and time when the EMS-XDM
started collecting PM data.
The Duration field shows the PM time interval (one day or
15 minutes).
The Monitored Seconds field shows the monitored seconds.
3. To refresh the contents of the Current PM window, on the menu bar select
File > Refresh.
Viewing Current Performance in Chart

Format
EMS-XDM enables you to access current performance charts for XDM
transmission objects.
To view a current PM data chart:

| In the Current PM window, on the menu bar, select File > Chart. The
Current PM Chart window opens.
Figure 2-25: Current PM Chart window
By default, all counters are enabled and displayed in the chart.
To filter a specific counter, clear the respective option button to disable it.
You can select/clear multiple option buttons to display multiple charts on
the same scale drawing.

Viewing Performance History

EMS-XDM enables you to view historical data on the performance of an XDM
transmission object for 15-minute or 24-hour time intervals.
If you request 24-hour historical data, the EMS-XDM displays two 24-hour
intervals (the last 24-hour interval and the one previous to that).
If you request 15-minute historical data, the EMS-XDM displays the last 16
15-minute intervals.
The system displays more than 16 15-minute intervals if one or more interval
has zero results.
Viewing Performance History in Tabular

Format
You can view historical data tables of transmission object performance.
To view a historical PM data table:

1. In the Card Internals View, select the transmission object.
2. On the menu bar, select Performance > History.
OR
In the Current PM window, on the menu bar select File > History, and on
the submenu, select the required interval.
The Performance History window opens.
Figure 2-26: Typical Performance History window

3. In the Window Duration field, click either 15 Min or 24 Hours,

depending on the period you want to analyze.
4. In the From and To fields, specify the period of time for which you want to
retrieve historical data. The 15-minute or one-day interval is applied to that
time span.
For example, if you specify a period of two hours in the From and To
fields, and select the 15 Min option in the Window Duration field, the
data table shows eight lines of (nonzero) PM data.
5. When you finish setting the relevant period and the window duration, on
the toolbar, click the relevant 24Hours or 15 Min button to retrieve the
data. Results vary depending on object counters.
Viewing Performance History in Chart

Format
You can view performance history charts for up to nine PM counters
simultaneously.
When there are more than nine counters available for an object, the
Performance Charts window automatically displays the first nine counters for
that object. Alternatively, you can select which counters you want to view.
To view a performance history chart for objects with nine

counters or less:
1. In the Performance History window (see Viewing Performance History
on page 2-29), on the menu bar, select File > Charts.
The Performance Charts window opens, displaying a chart of PM values
varying with time for each PM counter. Values below the threshold are
displayed in blue; values above in red.

Figure 2-27: Performance Charts window
Use the vertical or horizontal scroll bars to view the different sections of a
chart.
2. Use the command buttons on the left side of the Performance Charts
window to perform operations as desired in the following table.

Table 2-3: Performance Charts window buttons
Button Description
Resets the zoom and position of all charts to default values.
Magnifies the time scale for all charts.

Reduces the time scale for all charts.
Shifts all charts up.
Shifts all charts towards the beginning of the time frame.
Shifts all charts towards the end of the time frame.
Shifts all charts down.
Refreshes the performance history chart.
To view performance history charts for objects with more

than nine counters:
1. In the Performance History window (see Viewing Performance History
on page 2-29), select File > Charts. A Performance Charts window
opens. The left section of the window is identical to the standard
Performance Charts window (shown in the previous figure) and displays
up to nine PM counters. The right section of the window displays a list of
counters for the object.

Figure 2-28: Performance Charts window for objects with more than nine
counters
2. In the Counters to Display list, select the relevant checkboxes of the

counters that you want to display. (You can select maximum nine
counters.)
NOTES: A warning message appears if you attempt to select

more than nine counters.
Counters that appear grayed-out apply to a different time

duration and cannot be selected.
Counter values that are very large numbers are expressed in

scientific notation.
3. Click Refresh. The individual charts for the selected counters appear in the
window.
The buttons used to display different parts of an individual chart are the
same as in the standard Performance Charts window described in the
previous table.

Viewing PM History Reports for OPS-M

Objects
The following topics describe how to view EMS-XDM PM history reports for
optical objects in a tabular or graphic format.
Viewing PM History Reports in Tabular

Format
You can view PM history reports in tabular format.
To view a history of the PM data collected for an OPM card

object (for the selected channel wavelengths) in tabular
format:
1. In the OPM Card Internals View window, select the OPS object,
right-click, and on the shortcut menu select History. The PM History
window opens.
Figure 2-29: PM History window
2. In the Window Duration field, click either 15 Min or 24 Hours, as

required.
3. Use the From and To fields to specify the period of time for which you
want to retrieve historical data. The 15-minute or one-day interval is
applied to the time span defined.

4. After selecting the time interval, on the menu bar, select File > OK to close
this window and generate the report. After a few moments (while
EMS-XDM retrieves the data), the report for the first of the specified
intervals appears. If the time period you specified includes more than one
time interval, change the time period setting to adjust the report period. The
OPM Current/History window opens.
5. View the fields shown for each OPM channel, as described in the following
table.
6. Click Refresh to refresh the fields manually.
OR
Click Refresh Every to automatically refresh every x minutes (selected in
the dropdown list).
Table 2-4: OPM Current/History window fields
Field Description
Number of Carriers Number of carriers actually on line. Expected but missing
carriers are not counted.
Gain Tilt Difference between highest and lowest peak power carrier.
OSNR Threshold OSNR threshold set for OPS_M object (line).

Line Name Line name set for OPS_M object.
Scan Time Time when scan was performed.
Index Generated number listing lines of report.
Grid Frequency Center frequency of grid slot (ITU-T G.692) calculated from
Expected Wave Length and shown accordingly.
Expected Wave Center wavelength of a grid slot (window) as per ITU-T
Length G.692 calculated from measured Actual Wave length. Given
only for valid carriers that are within grid slot. Otherwise, grid
wavelength is not shown.
Actual Wave Actual wavelength of carrier as measured by OPM.
Length
Actual Power Actual peak power of carrier as measured by OPM.
Actual OSNR Actual OSNR of carrier as measured by OPM.
Invalid Alarm Alarm generated if carrier does not fall within a grid slot
(center wavelength ± 20% of spacing).
Unexpected Carrier Alarm generated if an actual carrier is measured but had not
been set as expected.
Missing Carrier Alarm generated for a carrier that had been set as expected but
is not being measured on line.
OSNR Low Alarm generated if the carrier measured OSNR is below set
OSNR threshold.

Viewing PM History Reports in Chart Format

You can view PM history reports in chart format.
To view a history report chart for the PM data collected for

an OPM card object:
| In the PM Current/History Chart window, on the menu bar, select File >
Chart. The OPM Current/History Chart window opens.
Figure 2-30: OPM PM Current/History Chart window
Managing Alarms
EMS-XDM enables you to access most alarm management functions through
the Current Alarms window.
The EMS-XDM alarm log (see Using the Alarm Log on page 2-41) contains a
list of all significant events that occurred in the network, including events other
than alarms, and provides additional fault management capabilities. It is also
possible to perform alarm management from an upper-level management
system like LightSoft.
You can perform the alarm management operations in any order, whenever
required.

Viewing Current Alarms

Current alarms are represented on the screen as LEDs on each NE icon. The
color of the LED corresponds to the most severe alarm affecting it.
In the Current Alarms window, you can view a summary of the alarms
currently present in the network, and you can apply user-defined filters to
display custom current alarm reports.
To view all current alarms in the NE:

1. In the Shelf View or Card Internals View, select Alarms > Current
Alarms.
OR
In the EMS-XDM main window, select the NE icon, and then on the menu
bar, select Alarms > Current Alarms.
NOTE: You can only view alarms associated with NEs for
which you have configurator rights.
The Current Alarms window for the selected NE opens, displaying a list
of current alarms per NE object and summary information as follows:
Filter type
Sort order
Total: total number of current alarms displayed in the window
Filter: number of filtered alarms (number of alarms shown after
filtering)
Figure 2-31: Current Alarms window

2. In the Filter type field, select one of the following options:

None: No alarms are filtered and all alarms are displayed.
Default filter: Alarms with ACK status are automatically deleted from
current alarms list. This includes alarms acknowledged by the user and
alarms automatically acknowledged by the system (if the problem was
resolved).
User-defined filter: Select to display a yellow icon.
3. View the information displayed in the current alarms list columns, as
follows:
LRS (Last Reported State): String LRS when NE is disconnected from
EMS-XDM station. (Due to the disconnection, EMS-XDM is not
updated with the actual alarm state.) The information regarding the
alarm may not be up-to-date. When the connection state of the NE is
normal, this field is empty.
Ack: If the alarm has been acknowledged; Empty if not.
Severity of alarm.
Object affected by alarm.
Reason for alarm.
Time/date of alarm.
4. To close the Current Alarms window, select File > Close.
To view alarm source details:

| In the Current Alarms window, select a row, and select File > Open. A
window opens, displaying directly the Shelf view with the associated
card/object causing the alarm.
To view alarm object info:

| In the Current Alarms window, select a row, and select File > Info. The
Info window opens, displaying details about the selected object.
To resize the current alarms table columns:

1. In the Current Alarms window, place the cursor on either end of the
column heading (on the vertical table grid line). The cursor changes to a
double-headed arrow.
2. Drag the cursor in the required direction to increase or decrease the column
width.

To toggle the refresh state:

| In the Current Alarms window, on the File menu, click Refresh On or
Refresh Off.
When Refresh On (default) is selected, the Current Alarms window is
refreshed continuously.
When Refresh Off is selected, you must click Update to refresh the
window manually.
Refreshing Current Alarms

By default, the Current Alarms window is refreshed continuously, and a new
alarm entering the EMS-XDM station is immediately shown in the window.
If the rate of new alarms entering the system exceeds a certain threshold, the
Current Alarms window enters Burst mode indicated by the appearance of the
icon. In that case, click Update to refresh the window manually.
When the rate of new alarms entering the EMS-XDM drops below the
threshold, the Current Alarms window automatically exits Burst mode and
returns to normal mode.
Determining the Cause of an Alarm

You can determine the cause of an alarm appearing in the Current Alarms
window.
To determine the cause of an alarm:

1. In the Current Alarms window, click a specific alarm. The alarm row is
highlighted.
2. On the File menu, select Open. The Shelf View or Card Internals View
opens, depending on the type of object affected by the alarm. You can
select the object and open the Info window to see further details.
OR
On the File menu, click Info to open an Info window for the object with
the alarm. (Note that the Info option does not display a window if there is
no further information to display.)

An asterisk (*) can appear alongside the time stamp. This indicates that the
time displayed in the Info window is not when the alarm occurred, but
when it was registered at the EMS-XDM station. This can happen, for
example, when initially uploading data from an NE (in which case the
alarm data is not uploaded with the time stamp), or following
disconnection.
To determine whether a certain alarm is affecting an XC defined in the

network, select a listing from the Current Alarms window, and on the File
menu, click XC Set. The XC Set List window opens displaying the XCs
affected by the faulty object. You can sort the information displayed in this
window by clicking a column header.
Figure 2-32: XCS List for faulty object window

Using the Alarm Log

EMS-XDM enables you to view an alarm log listing all significant events that
occurred in the network.
To view the alarm log:

| In the Shelf View or EMS-XDM main window, on the menu bar, select
Alarms > Alarm and Event Log. The Alarm Log window opens,
displaying summary information and a list of alarms.
Figure 2-33: Alarm Log window
In the case of a disconnection between EMS-XDM and an NE, a new entry

appears in the alarm log for each alarm detected after reconnection. If the
alarm was previously acknowledged, it is marked as acknowledged. When
the alarm is cleared, the last entry added after the reconnection (and not the
original entry) is marked as cleared.
The following sections describe the components of the alarm log.

Alarm Log Menu Bar
Figure 2-34: Alarm log menu bar
The alarm log menu bar at the top of the Alarm Log window provides pull-
down menus. Click a menu to display its items. Some menu items are general
and some allow you to perform operations related to selected alarms in the
alarms list, as described in the following table.
Table 2-5: Alarm log menu bar options
Menu Description
option
Refresh Updates log to reflect latest alarms. Options include:
| Manual: Updates window immediately.
| Periodic: Window updates automatically every 15 minutes.
Note: A heavy load is put on EMS-XDM resources when using
Periodic option. Take into account that contents are refreshed anyway
every time you open this window.
Filter Selects type of filter. Options include:
| No Filter: All alarms listed.
| Default Filter: Only unacknowledged alarms listed.
| Set Filter: Sets the filter (see "Filtering the Alarm Log" on page
2-48).
Print Prints all alarms or only selected alarms. Entire log can be very long;
therefore it is recommended to use Filter option to limit information
before printing.
Max. Time Maximum length of time alarm/event appears in alarm log before it is
in Log automatically moved. Possible values are 1, 6, 12, 24, 48, and 72
hours. Maximum time setting appears at top of Alarm Log window.
Max. Maximum number of alarms appearing in alarm log. When this
Alarms in number is exceeded, alarms are moved on a first-in-first-out (FIFO)
Log basis. Possible values are 500, 1000, 2000, 3000, 4000, and 5000
alarms. Maximum alarm setting appears at top of Alarm Log window.
NOTE: When the Max. Time in Log or Max. Alarms in Log

number is reached (whichever comes first), some alarms may
be deleted. The deleted alarms can be seen in the export log
files (see "Exporting Alarm Logs" on page 2-50).

Alarm Log Toolbar
Figure 2-35: Alarm log toolbar
The alarm log toolbar, located beneath the alarm log menu bar, allows you to
perform various operations related to the alarms and Alarm Log, as described
in the following table.
Table 2-6: Alarm log toolbar icons
Icon Name Function

Close Closes Alarm Log window.
Info Opens Info window of selected object.
Check Off Acknowledges selected alarm.
Recurrent Opens Alarm Record History window, where you can view
Alarm recurrent alarms for an object.
Alarms List
In the alarms list, you can view information about each alarm in the NE.
Figure 2-36: Alarms list
You can sort the alarms according to any column in the alarms list by clicking
the appropriate column header. Click twice to toggle between ascending and
descending orders. You can also change the order of the columns by dragging a
column heading to a new location.
The alarms list is the main area of the Alarm Log window and displays the
current alarms. Each new alarm is added to the top of this list. Each list entry
provides the following information, from left to right:
| chk: alarm was checked off
NOTE: Checked-off alarms are not shown when the default

filter is active.

| ID number: incremented with each incoming alarm

| Date and time: when the alarm was recorded
| Severity of alarm: for example, Major or Cleared, if the situation causing
the alarm has been corrected
| Location: NE and object affected by the alarm
| Alarm/event type
| Descriptive text (probable cause)
Viewing the Alarm Log
A new event is recorded at the top of the alarm log. When you open the Alarm
Log window, you therefore see the most recent events first. The total number
of current alarms and the number of filtered alarms (alarms that are not shown
due to the filter setting) are shown at the top of the window.
Events included in the alarm log are periodically exported to a binary file. You
can export this file in ASCII format to and external storage device (see
"Exporting Alarm Logs" on page 2-50).
An asterisk (*) can appear alongside the time stamp. This indicates that the
time registered in the Alarm Log window is not when the alarm occurred, but
when it was registered at the EMS-XDM station. This can happen, for example,
when uploading data from an NE (in which case the alarm data is not uploaded
with the time stamp).
The asterisk can also appear in Info windows in the Event Time field, with the
same significance.
NOTE: You can only view alarms associated with NEs for
which you have configurator rights.

Alarm log status bar

The status bar displays the number of unacknowledged alarms in the network,
the number of alarms in each alarm category, and the alarm bell.
Figure 2-37: EMS-XDM alarm log status bar
This bar is always displayed on top of the EMS-XDM application and is

therefore always visible to network operators, even if the EMS-XDM
application is minimized or integrated under an upper-level management
system (such as LightSoft). Based on your start-up configuration, you can
display the complete or abbreviated status bar. The status bar cannot be
minimized, but it can be moved around the desktop.
The status bar can also be displayed or suppressed during run time.
To toggle the status bar on or off:

| On the Alarm menu in the Shelf view, click On Top Window.
If the EMS-XDM application is minimized, you can click the status bar to
maximize it.
To move the status bar:

1. Click Number of Alarms in the status bar to make it the active window.
2. Press Alt+F7. The status bar turns into an outline.
3. Drag the outline to the new screen location.

Viewing Recurrent Alarms

In some cases, it may be useful to view all instances of the same alarm on a
selected object. The EMS-XDM enables you to view all alarm instances of the
same alarm for a given object in a single window. This capability facilitates the
tracking of objects or cards that have a recurrent alarm or problem.
To view recurrent alarms on an object:

1. In the Alarm Log window, select an alarm.
2. Click . The Alarm Record History window opens, showing a separate

entry for each alarm instance, including the NE and object affected by the
alarm, the alarm severity and alarm type, and the time and date when each
alarm occurred.
Figure 2-38: Alarm Record History window

Checking Off Alarms

In the Alarm Log window, you can check off alarms. This operation is similar
to the Acknowledge operation for current alarms. The major difference
between Acknowledge and Check-off is that once you acknowledge an alarm in
the Current Alarms window, the acknowledgment is sent to the NE and the
other EMS-XDM stations (in multistation systems) receive notification. A
checked-off event (from the Alarm Log window) is only deleted from the local
station and does not affect other stations.
To check off a single alarm:

1. In the Alarm Log window, select the relevant alarm. It is highlighted. To
deselect, click it again.
2. Click the Check-Off icon . A confirmation window opens.
Figure 2-39: Alarms checked-off confirmation window
To check off a group of alarms:

| Use multiselect to select a group of alarms/events, and on the menu bar,
select File > Check-Off. After checking off, the system freezes for several
seconds while updating the status of alarms. It then displays a confirmation
window.

Filtering the Alarm Log

You can filter the displayed alarms log list to show only alarms meeting certain
criteria.
To filter the alarm log:

1. In the Alarm Log window, on the menu bar, select Filter and from the
submenu, select one of the options (Default Filter, No Filter, or Set
Filter). If you select Set Filter, the Log Filter window opens.
Figure 2-40: Log Filter window
2. In the Network Element area, select the NEs you want to include in the
Alarm Log window. Click Unselect NEs to deselect selected NEs. Select
multiple NEs by clicking each one. When an NE is not selected, all alarms
concerning it are filtered (that is, not shown) in the alarms log.

3. In the Objects area, select the objects you want to include in the Alarm
Log window. By default, all objects are selected. Deselect an object by
clicking it. When an object is not selected, all alarms concerning it are
filtered (that is, not shown) in the alarms log.
4. Determine additional filtering criteria by selecting checkbox options as
described in the following table.
5. When ready, click OK. The filtering operation starts and its progress is
displayed in a scale graph in a separate window. If you changed the
filtering criteria, click Undo to deletes the changes and revert to the
original settings.
The following table describes the functions of the filtering criteria available
in the Log Filter window.
Table 2-7: Log filtering options
Filtering option Description

Time (From/To) Specific time period defined by time and date. Filters out
alarms defined by this time period.
Severity Mask Alarm severity: Event, Warning, Minor, Major, Critical.
Filters out all alarms at this level. For example, if you select
Major, it filters out major alarms.
Event Mask Event types described below:
Automatic switch All path protection switching performed automatically by
to protection system is normally logged in EMS-XDM.
Alarms Communication, Equipment, Quality of Service, and Timing.
State change Notification of various states that items pass through when
connected to network (generally not significant for user).
EMS-XDM Alarms detected by EMS-XDM (for example, disconnection
internal of NE or failure of EMS-XDM operation).
Reducing the Alarm Log Size

You can reduce the alarm log size by filtering the alarm display.
To reduce the alarm log size:

| In the Alarm Log window, decrease the value of the Max. Time in Log
parameter.
For example, if you select a value of one hour, all alarms more than one
hour old (from the time received) are erased from the Alarm Log window.
This keeps the alarm log at a reasonable size.

Exporting Alarm Logs

This function copies alarm log files to an external storage device (CD, and so
on). EMS-XDM keeps track of events by storing them in log files. These files
are automatically saved to the EMS-XDM hard disk either periodically or
whenever they reach a certain size (whichever occurs first). The file name has
the format AlarmLogHistory-yyyy.mm.dd-n, where n is the number of the log
file saved on date YYYYMMDD.
Log files must be exported from time to time to prevent the EMS-XDM disk
becoming full. When the free disk capacity is down to 2%, the log files are
automatically deleted.
The system displays a warning message and prompt for log files to be exported
when 95% of the disk capacity is used, as follows:
"ATTENTION: DISK ALMOST FULL
Delete unnecessary export, configuration and NE s/w files"
Click Close to close the message window and perform the file export operation.
unnecessary export, configuration, and NE software files.

To activate the export alarm and event log function:

1. Insert an external storage device.
2. In the Shelf View or EMS-XDM main window, on the menu bar, select
Alarms > Export Alarm and Event Log. The Log Export window opens.
Figure 2-41: Log Export window
3. Select the file to export. If you want to check the file contents first, click
Browser. You can filter the log file in the Browser window by selecting
Filter > User Filter on the menu bar.
A window opens, allowing you to filter the alarms in the file (see "Filtering
the Alarm Log" on page 2-48). When a filter is applied, only the alarms
displayed in the Browser window are exported. To delete a filter, on the
menu bar, select Filter > No Filter from the menu.
4. To export the selected file, click Export.

5. To delete the file you export, click Yes in the Delete exported file? field.
Otherwise, leave the No default.

Exporting Alarms through Communications
This feature is an optional feature and can only be used if your system is
licensed appropriately.
You can export the current alarms list from EMS-XDM to an external system
or application. This enables reporting the current status of the network to
central alarm centers that collect alarms from a variety of sources.
To use this feature, a dedicated Ethernet port must be installed at the
EMS-XDM Sun workstation. This is in addition to the Ethernet segment used
between EMS-XDM and the GNE and iss in order to prevent congestion on
that segment.
The main features of this function are:
| Information is transferred every two minutes.
| FTP (file transfer protocol) is used to transfer the information over TCP/IP.
The Export Alarms function only transfers additions to the current alarms list
(new records) since the last successful information transfer.
Alarm information includes a header record with current time and reported
fields. Each alarm is reported with the event time, the identity of the failed
object, and an alarm description.
Every two minutes, all new alarms recorded in the current alarms list are
appended to a file. The file is assigned a name of up to eight characters based
on the EMS-XDM station name, and is placed in the FTP user directory on the
remote machine. The file receives a .DAT extension.
In addition to the method described here, alarm logs can be exported in real
time mode in which alarms are written continuously to an ASCII file as they
occur. This file is then written to the hard disk at midnight. A new file
containing the alarm log events for that day is created each day. The format for
the information in this file is the same as for the method described here. A
special start-up configuration option, Current Alarm Export in Real-Time, must
be activated in order to use this option. If not, the alarm logs are periodically
exported to an external storage device, as described previously.

Pinging the NE
EMS-XDM enables you to ping the NE to determine the quality of its network
connections, by comparing the transmitted and received signals.
To ping the NE:

1. In the Shelf View, on the menu bar, select System > Ping.
OR
In the EMS-XDM main window, select the NE, and on the menu bar select
System > Ping.
OR
Righ-click the selected NE, and select Ping from the shortcut menu.
The NE Ping window opens, displaying ping results, as follows.
Addresses of specific NEs and the data bytes sent at the top of the list
Number of bytes received and approximate duration of the signal cycle
in each line
Figure 2-42: NE Ping window

2. To clear the list of results from the previous Ping session, click Clean.
3. To select the packet size in bytes, click the Packet Size slider. Standard
value is 64 bytes.
4. To stop transmitting packets, click Stop (default when window opened;
toggles Start/Stop when clicked).
5. To resume the transmission of packets, click Start.
Saving Current Network and

Security Configurations
The EMS-XDM system always keeps a backup copy of the current

configuration, including the following:
| List of NEs managed by EMS-XDM
| XC-related information
| Security information
If the synchronization mechanism was enabled at system start-up, any change
made to the system configuration leads to an automatic backup of the
configuration. This overwrites the configuration saved by the previous backup
process.
You can save the current configuration whenever required. By saving the
current configuration, you create a backup copy of the configuration manually.
NOTE: Backup creation is not contingent on all NEs being

connected.

To save the current configuration:

1. In the Shelf View, on the menu bar, select System > Save Configuration
to File.
OR
In the EMS-XDM Main window, select the NE and on the menu bar,
select System > Configuration File > Save to File.
The Save File Name window opens.
Figure 2-43: Save File Name window
2. Accept the default name (which includes the date and time) suggested by
the system, or enter a name for the backup file.
3. Click OK. A confirmation message appears.
4. Click Yes to confirm.
NOTE: The configuration files you save manually can be

used later to restore a specific configuration. However,
configuration files that are saved automatically provide only
the most recent configuration available. You can restore a
manually saved configuration during the EMS-XDM start-up
procedure.
For a more comprehensive backup procedure, it is

recommended to accompany the Save Configuration
operation with a Get DB from NE operation. This enables
restoration of the entire network configuration, even in the
event of a damaged database in the NE nonvolatile memory
(NVM).

Exporting XCSs
Using the EMS-XDM Export/Import feature, you can export XCSs to an XML
file format. Once you have exported data to an XML file, it can be imported
into the system to restore traffic on an NE.
Exported XML files are placed in the ~ems/EMSXCFiles connections directory
unless the default directory was changed. Before starting EMS-XDM, change
the directory to be used for exporting by entering
setenv ENM_READ_FILES_PATH ~ems/<NEWDIRNAME>
You can use the Copy Trail ASCII File and Store Trail ASCII File (UNIX)
commands from the EMS-XDM main (CDE) menu to copy files from external
storage devices to this directory and vice versa.
NOTE: XCs are exported in the order in which they appear in

the XC list. Therefore, if you have sorted the list so that LO
XCs precede HO XCs, import of the resulting XML file may
result in some XC creation failures since the LO XCs cannot
be defined if their HO XCs have not yet been created. It is
recommended to sort the XC list so that HO XCs precede LO
XCs.

To export (save) XCSs to XML format:

1. In the XC Set List window, do the following:
To export selected XCSs, select an XC(s), and on the menu bar, select
File > Export Selected to File.
OR
To export all the XCSs listed in the XC Set List, on the menu bar, select
File > Export to File.
The Save XCS window opens.
Figure 2-44: Save XCS window
2. In the File Name field, enter the name of the XML file.
3. Click Export. A confirmation message appears. If successful, the (selected)
XCSs are saved to the XML file.
4. Click Close to close the message window.
NOTE: Whenever you edit an XCS within the XC Browser,

you can import it to an XML file by accessing the XC Set
List and following the steps described in this procedure.

Exporting Policer Information

EMS-XDM allows you to export policer information to a designated file.
To export policer information to a file:

1. In the Policer List window, do the following:
To export a selected policer(s), in the Policer List, select a policer(s)
and on the File menu, click Export Selected to File.
OR
To export the entire policer list, on the File menu, click Export to File.
A window opens for defining a file name and location.
2. In the File Name field, enter a name for the file containing the policer
information.
3. Navigate to the destination folder, and click OK.
Exporting Flow Information

EMS-XDM allows you to export flow information to a designated file.
To export flow information to a file:

1. In the Flow List window, do one of the following:
To export a selected flow(s), in the Flow List table, select a flow(s) and
on the File menu, click Export Selected to File.
OR
To export the entire flow list, on the File menu, click Export to File.
A window opens for defining a file name and location.
2. In the File Name field, enter a name for the file containing the flow
information.
3. Navigate to the destination folder, select it, and click OK. The selected
file(s) is exported to the destination folder.

Viewing Optical Levels and

Parameters of Optical Objects
EMS-XDM enables you to view the optical levels of optical objects.
NOTE: This feature may not be supported for all optical

objects due to hardware limitations.
To view optical levels of optical objects:

1. In the Card Internals View, select an optical object and on the menu bar,
select Performance > Optical Parameters. The Optical Parameters
window opens, displaying parameters relevant to the selected object.
Figure 2-45: Optical Parameters window
2. View the fields, as described in the following table.

Table 2-8: Optical Parameters window fields
Field Description
Rx Power Actual power level currently received.
Input Power Gain block power level inside card.
Laser Bias Current level of laser bias.
Laser Temp Laser temperature level.
Tx Power Actual power level currently transmitted.
Line Out Power (Relevant only for OFA-R cards) Line power output to line
(High when a module exceeds 27dBm output power. Low for
OFA-BF below 400 mW, and for OFA-RF below 450 mW).
Service Power (Relevant only for OFA-R cards) Supervisory Channel, used for
dithering, range is -4–14.
History fields Minimum and maximum values for each counter.
NOTE: Optical parameters cannot be viewed for some

module types, such as an OT1 module. Optical parameters
appear grayed-out if they are not available.
Exporting Topology Data

This feature is an optional feature and can only be used if your system is
licensed appropriately.
EMS-XDM enables you to export EMS-XDM topology and NE configuration
data to an eXtensible Markup Language (XML) file for backup purposes. This
action saves the following data:
| Topology, including all NEs displayed on the EMS-XDM desktop
| Slot assignments of each NE in the saved topology
The XML file can be imported at any time to load a specific topology and NE
configuration.

To save the NE configuration to an XML file:

1. In the Shelf View, on the menu bar, select System > Topology to XML >
Save.
OR
In the EMS-XDM main window, select System > Save Topology to XML.
The Save Topology window opens.
Figure 2-46: Save Topology window
2. Type the name of the file under which to save the NE configuration, and
click Save. There is no need to specify a file extension, since the system
automatically appends the *.XML extension to the file name you enter.
A message window opens, confirming the successful operation.

Viewing NE Inventory
EMS-XDM enables you to view a wide range of information about the NEs
managed by the system.
To view NE inventory:
1. In the Shelf View or EMS-XDM main window, on the menu bar, select
System > Inventory. The Inventory window opens.
Figure 2-47: Inventory window
2. To display all actions implemented in the NE list in the EMS-XDM main

window, select the Reflect On Map checkbox.
All group expand-and-collapse actions made in the NE List of the
Inventory window are reflected in the main window.
Clear this checkbox to avoid changes showing the EMS-XDM main

window.
3. Fill in the fields, as described in the following table.

4. To obtain a list of cards, equipment, and subequipment in the NEs
displayed in the Inventory window, click Get Cards.
The actual cards, equipment, and subequipment appear in the Cards
Inventory list on the right side of the window.

The expected cards can also be viewed in the NE list by clicking the plus
sign (+) next to the NE. The expected cards, equipment, and subequipment
appear in the tree beneath the NE.
An XML file, XDM_Inventory.YYYYMMDD.xml, is automatically

generated. This XML file contains a list of cards for a specific NE and
other card-specific information, such as the card slot number, serial
number, hardware revision number, and so on. The XML file is
automatically saved in the "\Inventory" directory, and contains the last Get
Cards action information. Generated XML files can be exported to an
external inventory management application.
NOTE: This operation is only supported when the EMS-

XDM main window is visible.
Table 2-9: Inventory window fields
Field Description
NE List All NEs managed by EMS-XDM, color coded according to alarm
severity.
NE groups are indicated by plus sign (+). Click + to expand
group. A minus sign (-) appears next to group when NEs that
belong to it are shown (expanded). Click - to collapse group. Can
also right-click anywhere in NE list and select Expand All to
reveal all NEs in list. All selections made in NE List are reflected
in main window. (Read only)
Find NE Type name of NE to search NE list. List focus moves to nearest
match of search string.
Cards Inventory List of actual cards, equipment, and subequipment. (Read only)
To filter cards list display, click . At bottom of Inventory
window, optional cards list filter area appears, enables selecting
card types. Cards list only displays cards that match the selection.
Title NE title. (Read only)
Alarm Highest severity level of alarms on selected NE. (Read only.)
Type NE type. (Read only)
Alarms Per NE Number of alarms of each severity on selected NE. (Read only)
NE Location Location of NE. (Read only)
State Current operational state of NE. (Read only)
IP Address IP address of NE. (Read only)
Gateway Address Gateway address of NE. (Read only)
NE State Click to display NE State window, where you can view NE
states.

Performing Maintenance and

Backup Operations Using a
Script
EMS-XDM enables you to perform a variety of maintenance and backup
operations using the ScheduleTask.sh UNIX script. You can run this script
from the UNIX command line, or periodically by using the Crontab utility.
The following table lists the options that can be used with this script.
Table 2-10: ScheduleTask options
Script Description
ScheduleTask -GetDB Performs GetDB operation on NE with
<ipaddress> <neType> specified IP address.
Examples:
For XDM-1000 and XDM-2000 shelves,
NE type is XMCP (01 in the script).
For XDM-100 and XDM-200 shelves, NE
type is MXC (03 in script).
ScheduleTask -GetAllDB Performs GetDB operation on all NEs in
EMS.
ScheduleTask -XmlFile Activates XCs from designated XML
<filenameToActivate> file.
ScheduleTask -XmlExport Exports XCs for designated NE to an
<filenameToExportTo> XML file.
ScheduleTask -XmlExport ALL Exports XCs of all NEs in EMS to an
XML file.
ScheduleTask -Config Saves EMS database configuration to a
<filename> file.
To view the log generated when running the script, open the .scheduleLog file.

3
Procedures via LightSoft
In this chapter:
Overview ......................................................................................................... 3-1
Saving the LightSoft Database ........................................................................ 3-3
Checking Objects' Status ................................................................................. 3-4
Managing NEs in Topology Links .................................................................. 3-5
Inserting Elements into SDH/SONET Links ................................................... 3-6
Provisioning LO XCs for SDM-16 following Insert to a Link ...................... 3-11
Removing an Element from a Link ............................................................... 3-13
Inserting/Removing Elements to/from Optical Links.................................... 3-17
Viewing Resource Availability on Links ...................................................... 3-19
Synchronizing the LightSoft Database with the EMS Database ................... 3-44
Synchronizing Tunnels .................................................................................. 3-45
Batch Trail Operations................................................................................... 3-59
Batch Tunnel Operations ............................................................................... 3-70
Batch Service Operations .............................................................................. 3-77
Trail Performance Monitoring ....................................................................... 3-83
Multi Period PM ............................................................................................ 3-91
Alarm Correlation ........................................................................................ 3-126
Viewing Historical Log Events ................................................................... 3-134
Configuring Event Logging, Archiving, and Historical Viewing ............... 3-136
Checking the LightSoft Hard Drive Capacity ............................................. 3-140
Overview
via LightSoft.

via LightSoft Maintenance
Table 3-1: Preventive maintenance procedures via LightSoft

Save LightSoft Once a week, or Saving the Twice a day if
database. following major changes LightSoft Database RDR is used
in network topology (on page 3-3)
Check the objects' Once a week, or Checking Objects'
status. whenever major changes Status (on page
are made to the system 3-4)
configuration
Check inserting a As determined by the Inserting Elements
NE into a link. network administrator; to into SDH/SONET
be performed after Links (on page 3-6)
saving the configuration
Check removing a As determined by the Removing an
NE from a link. network administrator; to Element from a
be performed after Link (on page
saving the configuration 3-13)
Check resource Once a week, or Viewing Resource
availability on following major changes Availability on
links. in network topology Links (on page
3-19)
Synchronize Once a week, or Synchronizing the
LightSoft following major changes LightSoft Database
database with in network topology with the EMS
EMS database. Database (on page
3-44)
Synchronize Once a week, or Synchronizing
tunnels. following major changes Tunnels (on page
in network topology 3-45)
Perform batch As determined by the Batch Trail
trail operations. network administrator; to Operations (on
be performed after page 3-59)
saving the configuration
of the current database
and when the trail
restoration flag is red, or
once per quarter
Check trail Once a week, or Trail Performance
performance following major changes Monitoring (on
monitoring. in network topology page 3-83)
Check Multi Once a week, or Multi Period PM
Period PM. following major changes (on page 3-91)
in network topology
Check alarms Once a week, or Alarm Correlation
correlation. following major changes (on page 3-126)
in network topology

Maintenance via LightSoft

Check historical Once a week, or Viewing Historical
log events. following major changes Log Events (on
in network topology page 3-134)
Check LightSoft's Once a week, or Checking the
hard drive according to working LightSoft Hard
capacity. procedures Drive Capacity (on
page 3-140)
Saving the LightSoft Database

The following script may be run on any LightSoft server, or, in the case of a
cluster configuration, on the main server (the one housing the database). It can
be used to backup or restore the LightSoft database, and to purge old backups.
Backups may be scheduled to run periodically using the SetCron utility.
To back up or restore the LightSoft database:

1. Ensure that LightSoft is not currently running.
2. Open a Unix window.
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 (directory contains backup sets; default
$HOME/.BACKUP).
NOTE: The default backup folder may also be set using the
environment variable $BACKUP_FOLDER..

The following figure shows a typical screen.
Figure 3-1: Typical LightSoft database backup window
Checking Objects' Status

Check objects (both EMSs and MEs) every day to verify that all are uploaded
in the LightSoft and EMS databases.
To check objects' status:

1. Open the Unix window.
2. Change the user name to su - nms.
3. Type the following command with the required options:

NMSState | & egrep "NOT|ING"
Where:
NMSState = the command
NOT|ING will display the MEs that are NOT-UPLOADED or in an
UPLOADING state

The following figure is a typical window showing the status of elements.
Figure 3-2: NE status check window
Managing NEs in Topology Links

You can insert an ME or an unmanaged element (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.
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
features, please contact ECI Telecom Customer Support.

Inserting Elements into

SDH/SONET Links
You can insert an ME or UME into an existing SDH/SONET link. An inserted
UME can be useful for maintaining accurate network topology. 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 HO 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 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 LO XCs, the procedure

described in this section creates HO XCs. If LO XCs are
needed, this procedure must be followed by an additional
procedure to reinstate the LO XCs. In the case of SDM-4 and
SDM-1, any LO XCs that were present are automatically
reflected and require no further actions.
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.

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 cross connects (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/SONET. For cases that
are not covered by the Insert feature, the procedures detailed in Inserting and
Removing MEs to/from a Link may be used.
NOTES: This procedure may be traffic-affecting. 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 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 it's 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 is displayed, showing the trail IDs that failed.
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
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.
Figure 3-3: Selected element and link
3. On the LightSoft main menu, select Configuration > Modify > Insert.
An error message may appear if circumstances exist that prevent the
operation from proceeding.
4. If a multilink was selected, the Insert Into Link dialog box opens.
Figure 3-4: Insert Into Link dialog box

5. Highlight a link and click Select. The Insert ME dialog box opens.
Figure 3-5: Insert ME dialog box
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 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. Each tab initially show the attribute
values of the link that will be replaced.

The values can be changed as required for purposes of the new links to
be created.
Figure 3-6: Insert ME dialog box 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
Dialog Box.
7. (Optional) In the Insert ME 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 be traffic affecting. 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 dialog box.

The ME or UME is now inserted in the selected link.
Figure 3-7: NE inserted into link
12. If the original link involved SYNCOM equipment at both ends (SYNCOM
- SYNCOM link), in the EMS-XDM, delete the original link from the link
list, in order to avoid notification to LightSoft for this link.
Other original link configurations do not require interventions at the EMS
level.
Provisioning LO 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 this chapter, HO XCs are automatically created within the NE. If
LO 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 HO XCs with appropriate LO XCs. The LO XCs must
be created in the NE with the same pattern of TU numbering and
main/protection path types as are present in the HO trails on either side of
the NE.
2. Splitting the HO pipe on the NE, creating two HO terminations in place of
the HO XCs that were previously traversing the NE.
3. Provisioning LO 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 LO XCs that were present are
automatically reflected and require no further actions.

To provision LO XCs in SYNCOM SDM-16 after insert to a

link:
1. Delete the HO trail in EMS-Syncom, and create two HO trails that
terminate in the new NE.
2. Create LO trails with the correct path type (Protection or Main), making
sure that it will be consistent with other aspects of the topology following
the insertion. Use the following topology in EMS-SYNCOM:
Figure 3-8: 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.
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, and still retain all associated trails and services.
If the NE is connected by additional pairs of links, these can also be removed
by repeating the operation. At the point that all links are removed, NE becomes
a standalone element. Once links are removed, the NE can either be
reconnected to the topology in another way, or deleted from the network.
The procedure additionally allows you to either automatically delete the XCs
(SNCs; sub network connections) associated with the old connection, or to
keep them intact.
| If you intend to subsequently 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 to remove the NE from the topology, it
may be useful to automatically delete SNCs at the same time as 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).

NOTES:
Maintenance operations on trails or other objects involved
in the Remove process must be released before the
procedure can be performed. Maintenance operations are
persistent until they are released. For details, see
Maintenance Operations.
Services that terminate at the NE interfaces must be
removed before the procedure is performed. 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 a MSP Linear protected links is not
supported directly. If any links from which the NE is to be
removed is MSP Linear protected, before performing the
NE removal procedure described in this section, you must
first manually configure the links to not be MSP Linear
protected.
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 this section, it may not be
possible to subsequently delete it from the topology using
the LightSoft Delete command; see Deleting objects.
Please contact ECI Telecom technical support for
assistance in such cases.
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.
Figure 3-9: Selected element in a link

3. On the LightSoft main menu, select Configuration > Modify > Remove
NE; the Remove NE dialog box opens.
Figure 3-10: Remove NE dialog box
4. Specify how the operation will 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.
Figure 3-11: Links automatically selected in the map view
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 to
also 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 NE dialog box to show the link attributes. It
initially shows attribute values that are consistent with both the links
that will be replaced, such as the common technology layer, and a
summed Length value, and can be changed as required.
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.
Figure 3-12: Insert ME dialog box More area
e. Click Path Trace Configuration to configure SDH/SONET 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 was
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 dialog box.

The selected ME is now removed from the selected links. The adjacent
links are replaced by a continuous link.
Figure 3-13: NE removed from the 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), in the EMS-XDM, delete the original link from the link
list, in order to avoid notification to LightSoft for this link.
Other original link configurations do not require interventions 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 Viewing and Editing 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 in LightSoft V4 User Manual.
Specify the optical trail type, according to the selected trails - OMS,
OCH, or LP.
Perform trail synchronization, as described in Performing Trail
Synchronization in LightSoft V4 User Manual, using the Admit
selected trails to database option to readmit the trails. This will cause
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, in turn, and
open its Properties for Link window; see Viewing and Editing Link
Properties.
2. Set the links' Maintenance State field to Manual Maintenance to enable
creating new links on each link's ports; see Viewing and Editing Link
Properties.
3. Create a new link between the ports of two neighboring elements; see
Creating Topology Links.
4. Select the two old link 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.
5. 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 in LightSoft V4 User Manual.
Specify the optical trail type, according to the selected trails - OMS,
OCH, or LP.
Perform trail synchronization, as described in Performing Trail
Synchronization in LightSoft V4 User Manual, using the Admit
selected trails to database option to readmit the trails. This will cause
the trails to traverse the new link.
6. Delete the two unnecessary old links; see Deleting Topology Links. (The
links are now free of trails.)

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 (on
page 3-20).
| 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 (on page 3-29).
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 (on
page 3-36).
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 at a selected.
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 Map Preferences (on page 3-28).
The color of a multilink or multidirection link reflects the overall availability
of its participating links (the percentage available on the total capacity).
NOTE: Availability is shown in terms of what can be

provisioned for the selected rate.
Example: If you created four VC-4 trails on an STM-16 link,

the availability for VC-4-4c trails will depend on how the
VC-4 trails are distributed within the link. If they are all next
to each other, you will still have capacity for three VC-4-4c
trails. But if they are distributed within the STM-16 link, then
the ability to create VC-4-4c trails may potentially be
blocked. This is because VC-4-4c trails need contiguous data
which may no longer be present in the link. The Availability
map will show that availability at the VC-4-4c rate is nil.

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 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 (on page
3-23).
ETH/MPLS see Availability Map for ETH/MPLS; (on page
3-25).
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 Map Preferences (on page 3-28).

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, 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 the LightSoft V4 User Manual.
Figure 3-14: Availability of Resource dialog box
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 open the Availability for Link window (see Availability for Link
on page 3-29) from the Availability Map window by right-clicking a link in
that window and selecting Availability from the shortcut menu.

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.
Figure 3-15: Availability Map (for SDH or Optical) window

Table 3-2: Availability Map menu option
Toolbar
Menu option Description
icon
Map
Preferences Enables you to change the percentages and colors
associated with availability ranges; see Modifying
Availability Map Preferences (on page 3-28).
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.
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.
Figure 3-16: Availability Map (for Ethernet/MPLS) window
Table 3-3: Availability Map menu option
Toolbar
Menu option Description
icon
Map
Preferences See Availability Map for SDH or Optical (on page 3-23).
Close Closes the Availability Map window.

View
Refresh See Availability Map for SDH or Optical (on page 3-23).
Legend See Availability Map for SDH or Optical (on page 3-23).

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. In the
LightSoft V4 User Manual.
| CAC Shared Bandwidth: Displays availability based
on bandwidth reserved for bypass tunnels. For more
information about reservable BW, Network Properties
- MPLS CAC Tab. In the LightSoft V4 User Manual.
| 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 in the
| PM Current 24 Hours: Displays availability based on
24 hour PM counter intervals. For more information
about PM, see Performance Monitoring and
Maintenance in the LightSoft V4 User Manual.
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.)
Table 3-4: 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.
Figure 3-17: Availability Map Preferences dialog box
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 in LifgtSoft V4 User Manual.

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.)
Table 3-5: 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.)
Help Opens online help.
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 in LightSoft V4
User Manual.
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 on page 3-20) by
right-clicking a link in that window and selecting Availability from the
shortcut menu.
Table 3-6: Link Availability menu options
Toolbar
Menu option icon Description
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 Map
Preferences (on page 3-28).
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.
Figure 3-18: Availability for Link widow
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.
The legend at the bottom of the window explains the color coding. The
Available/Unavailable colors are user-configurable; see Modifying Availability
Info Colors (on page 3-35).
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 (on page 3-29).

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 in LightSoft V4 User Manual.
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.
Figure 3-19: Availability for Link/MoT window

Table 3-7: Link CAC Availability diagram features
Option Description
BW Units selector Enables choice of units expressed in terms of:
| Percentage of the port rate (%PortRate), 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 (unallocated) Portion of EMS-assigned bandwidth that is reservable for
BW 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 (unallocated) Portion of EMS-assigned port/CoS bandwidth reserved
Shared BW for bypass tunnels (see Res Shared BW % in Network
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.
"Pie" diagram shows the parameters and Non-Reservable BW (=1- these
parameters)

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 in LightSoft V4 User
Manual.
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.
Figure 3-20: Link PM Availability Diagrams GUI
Table 3-8: Link PM Availability diagram features
Option Description
BW Units selector Enables choice between units expressed in terms of percentage
of the port rate (%PortRate) or bandwidth (Mb/s).
15m/24H selector Statistics based on 15-minute or 24-hour counter collection
intervals.
Overall port and per based on the counters called PortTxUtilization and
CoS 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.
Figure 3-21: Availability info Preferences dialog box

2. Change the color associated with a designation by customizing its color

swatch . For information about standard color customization, see
Customizing LightSoft Object Colors in LightSoft V4 User Manual.
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.)
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 (on
page 3-19) .

Optical Availability Tables

Optical channel availability can be analyzed for unidirectional or bidirectional
OMS trails. (Two unidirectional trails with related endpoints are considered as
a single bidirectional trail.) In both cases, a window similar to the following
opens. 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.
Figure 3-22: Intersection trail avilability table for 32 channel OMS trail
The title bar displays the OMS trail label. Each channel's cell is color coded
according to the channel state. The colors are explained in the legend at the
bottom of the window. The channel state colors are:
| Free - White: Channels that are not in-use, blocked, or disconnected in a
ROADM (configurable SNCs).
| In-use - Dark blue: Indicates an OCH trail traversing OMS sections. The
OCH trail originates from at least one endpoint or passes through both.
| Blocked - Black: Indicates the 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 the single trail availability examples, the C
band eight middle channels are blocked to use.

When a bidirectional trail (or unidirectional trails with related endpoints) is

selected for analysis, as in the example above, the table shows the intersection
set of the channel states in each trail direction. When a specific channel has
different states in the two directions, the intersection table indicates a split state
for that channel's cell, as follows:
| In-use mixed with free - Light blue: Indicates a channel is in use in one
direction and free in the other.
| Blocked mixed with any - Gray: Indicates a channel is blocked in one
direction and either in use or free in the other.
If the intersection involves more than two trails, the precedence of display is:
(1) Blocked, (2) In-use, (3) Free. Hence, a channel that involves all three states
is shown as Blocked (Gray).
Note in the example that the cell for channel 194.6 is light blue (In-use mixed).
The other cell colors imply the same channel state in both directions.
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 dash (for example, In-use: 5/4), showing the number
of channels having that state per trail direction.
The Split Table icon is enabled for 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.
Figure 3-23: Single availability tables for 32 channel OMS trail

Table 3-9: 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 Info
Colors (on page 3-35).
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 Availability Information (on page
3-43). For information about the report format, see
Printing and Exporting Availability Information (on page
3-43).
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
Trails to CSV (on page 3-64). For information about the
report format, see Printing and Exporting Availability
Information (on page 3-43).
Close Closes the Optical Availability Table window.
Alarms
Show OMS Alarms Opens the Current Alarms window showing the alarms
on the selected OMS trail.
Show OCH Alarms Opens the Current Alarms window showing the alarms
on all OCH trails traversing the selected OMS trail.
Trails
Show OMS Trails Opens the Trail List window showing the selected OMS
trail.
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).
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.
Only OTM links are recognized.
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.
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.
Figure 3-24: Link selection when single OMS trail between MDs at both ends
| Bidirectional availability - select any two links, one in each direction.
Figure 3-25: Link selection for bidirectional table between A and B
| 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.
Figure 3-26: Link selection for bidirectional utilization A-B and B-C

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 in LightSoft V4
User Manual.
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).

Synchronizing the LightSoft

Database with the EMS Database
The LightSoft database must be checked against the EMS database and
consistency verified. Check that all counters in the Trail Consistency
Indicator (TCI) window are zero. If not, use the procedures in the following
sections to synchronize the trails in LightSoft and the EMS.
Synchronizing Trails
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 through Synchronization in the
Trail Synchronization Concepts

Trail synchronization functionality is available in accordance with user
permissions. It is not available for CNM users; see VPNs and CNMs in the
For additional procedures for synchronizing the LightSoft and EMS database
refer to the LightSoft V4 User Manual.

Synchronizing Tunnels
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 in the
Viewing Tunnel Segment Consistency Status

Inconsistency information can be accessed using the following LightSoft main
window indication and icon:
| 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 the color correspondences, see Severity
Breakdown Pane (on page 3-52).
| 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 (on page 3-51).
| Tunnel Synchronization window: Performs various synchronization
actions, both directly and via several floating windows. See Tunnel
Synchronization Window (on page 3-54).

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 they should be 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.
NOTE: The TSC window opens with only tunnel segments

that involve inconsistencies, unlike the TCI window for trails
which 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. For
more details, see Deleting Tunnels in LightSoft V4 User
Manual.

Performing Tunnel Synchronization

Tunnel synchronization can be performed for tunnel inconsistencies associated
with selected multilinks or objects, links in a multilink, or specific tunnels.
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) which you want to synchronize.
OR
Click and highlight the single tunnel you want to synchronize.

2. On the Tunnel List window toolbar, click .

OR
Right-click either the highlighted tunnel or one of the selected
(checkmarked) tunnels, and select Tunnel Operations > Tunnel
Consistency from the shortcut menu.
The TSC window opens; see Tunnel Segment Consistency (TSC) Window
(on page 3-51).
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 .
3. Click the Start icon .
NOTE: Selecting Stop discontinues 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.
Selecting Abort discontinues the entire operation. No

results are provided.
When the process is completed, the Tunnel Synchronization window

opens; see Tunnel Segment Consistency (TSC) Window (on page 3-51).
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
the results of the process.

4. 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 required
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 will be 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 required
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 (on page 3-57).
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 in
5. Click Activate . The tunnels are synchronized according to the selected

options.
Selecting Stop discontinues 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.
Figure 3-27: Synchronization Results window
6. Close the Tunnel Synchronization window by clicking Close .
7. 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 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.
Figure 3-28: Tunnel Segment Consistency (TSC) window
Table 3-10: TSC window toolbar
Icon Name Description

Start Starts tunnel synchronization on the selected tunnels.
Stop Stops the 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 the 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 Clears all tunnels in the currently selected window.
tunnels
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 with system-wide application according to your needs; see
Tunnel Management Consistency Preferences in the LightSoft V4 User
Manual.
For a description of the inconsistency types and corresponding possible
remedial actions, see Tunnel Consistency Use Cases (on page 3-57).
Table 3-11: Indications of warning flags
Color Possible indications

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.
Figure 3-29: TSC window Selected Objects pane
The columns displayed can be varied as required. For more information, see
Showing, Hiding, and Auto-Fitting Columns in LightSoft V4 User Manual.
Table 3-12: 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 ID.
System ID for the tunnel, 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).
Tunnel Name Name of the tunnel.
Customer Customer associated with the tunnel.
Severity | Severity of all inconsistency, as described in Severity
Breakdown Pane (on page 3-52).
EMS Tunnel ID Number allocated by the EMS, uniquely identifying the SNC
within the EMS.
Detected At Time that 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.
Figure 3-30: Tunnel Synchronization window
The Tunnel Synchronization window includes floating windows used in the

synchronization procedure. It shows the inconsistent or incomplete tunnels
associated with the 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
succeeded 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

Table 3-13: Tunnel Synchronization window toolbar

Activate Activates synchronization on the tunnels for which the Selected
Operation column is 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 Network Imposes a tunnel from the LightSoft database into the EMS
(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 listed in the
Network Network window).
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.
Show highlighted Opens a new Show Tunnel window view, where the tunnel that
tunnel on map 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 (on page 3-57).
Close Closes the Tunnel Synchronization window.

Tunnel Synchronization Floating Window

Columns
The following information columns are present in the floating windows, as
indicated.
Table 3-14: 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 Type Inconsistency condition: Classified, Classified+, ClassifiedNet,
Unclassified, or Fragment. See Tunnel Consistency Use Cases
(on page 3-57). (Network and Results windows)
NMS Tunnel ID Tunnel identifier. (All 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
clasified 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 on page 3-52).
| 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).
Table 3-15: Tunnel Inconsistency types and possible remedial actions
Tunnel In DB? Classified in SNC Unrecognized Possible Remedial

inconsistency EMS? inconsistency Segments? Actions
type leve
Inconsistent tunnels
Classified+ Y Y Warning or N/A Impose, Admit, or
Minor Delete from Net
Classified Y Y Major or N/A Impose, Admit, or
Critical Delete from Net
Unclassified Y N Major or N/A Impose, or
Critical 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 in LightSoft
V4 User Manual

NOTES:
.LightSoft uniquely identifies a tunnel by its NMS Tunnel
ID; see Create Tunnel Window - General Parameters Pane
in LightSoft V4 User Manual. Connectivity can identify a
tunnel only if NMS Tunnel ID=Null, in which case
LightSoft assigns a NmsTunnel 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 in LightSoft V4 User Manual.
| Protected Tunnel:
LightSoft may admit a protected tunnel without some or all of its
assigned Bypass tunnels. In this case, the TunnelState of the Protected
tunnel will be 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 TunnelState=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.
| 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.
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. Both
import and export records coexist in the same XML file. For information about
the XML syntax, see Import/Export Trails Syntax in LightSoft V4 User
Manual.
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's 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 either
network contingency planning and design purposes or backups in case of
system failure.
Exported trails are automatically implemented in the network by the Import
function according to the settings that were used to export them to XML.
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 (on page 3-64).
Exporting for Network Planning Purposes

Exporting trails to XML for network planning purposes is performed in
conjunction with the creation of "planned" new 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 in LightSoft V4 User
Manual. Planned trails can also be created singly or in bundles using the
Create Trail window, but the resources selected for them must be
currently unoccupied; see Creating SDH and EoS/MoT Trails in LightSoft
V4 User Manual. In each of these cases, the trails are exported to XML
using 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 in LightSoft V4 User Manual. 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 in LightSoft V4 User Manual. 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 tunnels so that they can be restored if inadvertently deleted or
corrupted:
| Trails that were deleted from the network can be restored by importing. For
this purpose the original trails must be selected from the Trail List or Edit
Trail window, and the export must be performed using the Export Trails
window's Export for Create mode.
| Existing trails that become corrupted can be restored by importing. For this
purpose the original trails must be selected from the Trail List or Edit
Trail window, and the export must be performed using the Export Trails
window's 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.
NOTE: 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 client trail record is encountered before its server
trail, the client trail is not created, even if the server 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 server trails
to appear first before the client trails.
If the XML file will be used for Delete, sort the client trails
to appear first before the server trails.
You can also export separate files for client and server trails.
Then make sure to import the server trail file first when
creating trails and the client 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 in LightSoft V4 User Manual.
OR
From the Edit Trail window, select a trail (and optionally edit it, but do
not activate the changes); see Editing Trails in LightSoft V4 User
Manual.
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 in LightSoft V4
User Manual.
OR
Editing a trail: From the Edit Trail window, edit a trail and complete
(but do not activate) it; see Editing Trails in LightSoft V4 User Manual.
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 in
LightSoft V4 User Manual. 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
Right-click a trail and select Trail Utilities > Export from the shortcut
menu. The Export Trails dialog box opens.

Figure 3-31: Export Trails to XML dialog box
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 to 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 they became
corrupt).
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.
Exporting Trails to CSV

You can 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 script.
To export trails to CSV:

| See the generic procedures in Exporting to CSV in LightSoft V4 User
Manual.
To export XML data to CSV:

| See the generic procedure in Exporting XML Data to CSV in LightSoft V4
User Manual.

Importing Trails
This section describes trail definition import from XML using LightSoft menu
options. (You can import trail XML files via UNIX; see Exporting/Importing
Trail Definitions via UNIX (on page 3-67), and Exporting/Importing Traffic
Entities via UNIX (on page 3-69).
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 (on page 3-60).

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.
Figure 3-32: Import Trails dialog box
2. In the File Name pane, select the file you want to import.
3. Select one of the following options, according to the required action:
Check Only: Checks the syntax of the XML file.
Complete: Checks syntax and finds a path for the trails.
Activate: Activates the trails in the network.
4. Click Import. The file is imported and appears as a trail in the Trail List
window.
The Status pane shows the total number of trails in the import, and the
numbers that imported successfully or failed.

Exporting/Importing Trail Definitions via

UNIX
This section describes trail definition import from XML via UNIX. This may
include prescheduling using the UNIX crontab command.
This procedure is used only for trails. You can also export/import trails, as well
as tunnels and services, using a simplified UNIX procedure; see
Exporting/Importing Traffic Entities via UNIX (on page 3-69).
NOTE: The import or export script must be run from the

server side.
The import files must reside in the fixed directory
NMSTrails.
After the import script is run, an output log file is created
within NMSTrails, where the user can check the success of
the process.
To export/import trail definitions to/from XML files via

UNIX:
| You can import XML files with the SetCrontab utility. The following is an
example UNIX command line:
TrailExpImpUtility -import file_name -user
user_name -passwd user_passwd
The following usage and script options apply:

TrailExpImpUtility [-a] [-export output_file_name]
[-exportIds trail_ID_input_file_name] [-files]
[-help] [-import file_name]
[-s] [-v] [-user user_name] [-passwd user_password]

Where:
Command Description
-a Appends the current export operation to the given file
name.
-export Exports all the trails in LightSoft to the specified file
output_file_name name. File name is required. The exported file is placed
in the directory NMSTrails.
-exportIds Exports trails by trail ID. Requires the name of a trail ID
trail_ID_input_fil input file with specific input trail IDs in the following
e_name format:
workstation ID : trail ID (for example, 1:21).
-files Returns a list of all trails in the XML trail file list at the
server side.
This must be run from the server workstation.
-help Help on usage of this command is displayed.
-import file_name Imports trails to the specified file name. Requires an
import file name, which must exist in the fixed Import
directory NMSTrails.
-s Checks the XML trail import file syntax. Same as the
Check Syntax radio button selection in the Import
Trails window; see Importing Trails (on page 3-65).
-v Validates the XML trail import file information. Same as
the Complete radio button selection in the Import
Trails window; see Importing Trails (on page 3-65).
-passwd Password required to run this application.
user_password

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. A trail export/import procedure with richer
command set is also available; see Exporting/Importing Trail Definitions via
UNIX (on page 3-67).
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 script 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 Indicates that the requested operation is export of all
output_file_name trails, tunnels, or services.
Trails, tunnels and services each have their own
directory: NMSTrails, NMSTunnels, or NMSServices.
-import file_name Indicates that the requested operation is import of all
trails, tunnels, or services.
-trail Indicate that the operation is performed on all trails.
-service Indicate that the operation is performed on all services.
-tunnel Indicate that the operation is performed on all tunnels.
-user user_name User name required to run this application.
-passwd Password required to run this application.
user_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
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 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
tunnel in the file.
Records in the XML file specify the action commands and parameters. Both
the XML syntax, see Import/Export Tunnel Syntax in LightSoft V4 User
Manual.
process. You can find this log file in the ~nms/NMSTunnels directory. The log
file name is the same as the XML file, with the extension .log.
information, contact ECI Telecom's Customer Support).
OPTIONAL FEATURE: XML tunnel operations are fully

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 Export Tunnels to CSV(on page 3-74).

| For planned addition/removal of P2MP tunnel endpoints, see Adding or
Removing P2MP Tunnel Tail Endpoints in LightSoft V4 User Manual. For
this purpose the tunnels are exported to XML using the Export Tunnels
| For planned deletion of existing tunnels; see Deleting Tunnels in LightSoft
V4 User Manual. For this purpose the tunnels are exported to XML using
the Export Tunnels window's Export for Delete mode.
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.
displayed in the Tunnel List window, and are eventually
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 in LightSoft V4 User Manual.
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 in the
LightSoft V4 User manual.
OR
Deleting tunnels: From the Tunnel List window, select one or more
tunnels for deletion (but do not click Delete); see Deleting Tunnels in
LightSoft V4 User Manual..


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.
Figure 3-33: Export Tunnels dialog box
3. Type the file name to which you want to export the tunnels, or select an
existing one from the dropdown list.

*, ?, !, |, \, /, ', ", {, },<, >, ;, <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.
Export Tunnels to CSV

You can export Tunnel List window data to a delimited-format CSV file for
LightSoft also enables you to export tunnels in XML files to CSV using a
script.
To export tunnels to CSV:

| See the generic procedure in Exporting to CSV in LightSoft V4 User
Manual.

User Manual.

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.
Figure 3-34: Import Tunnels dialog box
2. In the Files pane, select the file you want to import.

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.
Delete Operations:
d. Check Syntax: Checks the syntax of the XML file.

e. Delete: Checks syntax and deletes the specified tunnels.
5. Click Import. The file is imported and appears as a tunnel in the Tunnel
List window.
The Import Status pane shows the total number of tunnels in the import,
and the numbers that imported successfully or failed to import.

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
the XML syntax, see Import/Export Traffic Syntax in LightSoft V4 User
Manual.
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.
information, contact ECI Telecom's Customer Support)
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 as described in Exporting/Importing
Traffic Entities via UNIX (on page 3-69).
OPTIONAL FEATURE: XML service operations are fully

importing service definitions are unavailable.

Exporting Service
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 (on page 3-81).

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 in LightSoft V4 User Manual. For this
purpose the services are exported to XML using the Export Services
| Planned removal of existing services is performed using the Service List
window; see Deleting Services in LightSoft V4 User Manual. For this
purpose the services are exported to XML using the Export Services
window's Export for Delete mode.
network design is ready to be implemented, the planned services may be
imported to LightSoft as part of the active network.


You can export trails 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 trails 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 a variety of purposes.
displayed in the Service List window, and are eventually
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 in LightSoft V4 User
Manual.
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 in LightSoft V4 User
Manual.
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 in LightSoft V4 User Manual.


OR
(If you are in the Service List window) In the Services pane, right-click a
service and select Utilities > Export Services from the shortcut menu. The
Export Services dialog box opens.
Figure 3-35: Export Services dialog box
3. Type the file name to which you want to export the services, or select an
existing one from the dropdown list.

*, ?, !, |, \, /, ', ", {, },<, >, ;, <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 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 tunnel definitions are saved as an XML file.
Exporting 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
script.
To export services to CSV:

| See the generic procedure in Exporting to CSV in LightSoft V4 User
Manual.

User Manual.

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.
Figure 3-36: Import Services dialog box
2. In the Files pane, select the file you want to import.

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.

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

Figure 3-37: Trail Performance Monitoring window
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 (on page 3-89).

Table 3-16: Trail Performance Monitoring window toolbar

Reset PM Resets all counters of the selected TPs to zero. Refreshes only
Data 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 request
Counters 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 Reloads PM information for all TPs related to the selected

Data 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 Opens a GCT to the EMS card view for the selected TP.
Selected
Termination
Points
Export to Exports Trail Performance Monitoring window data to a
CSV File CSV file.
Print Out PM Prints the Trail Performance Monitoring window data.
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.
Table 3-17: 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 Trail Removes all records that share the same trail
with the selected record from the selection.

Table 3-18: Trail Performance Monitoring window fields
Column Description
# Number of the TP in the list.
Trail Label User-defined label for the 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 A separate column for each counter. The counter name has two
names, in parts, for example, "BBENE VC-4/AU-4", where:
multiple | The left part (BBENE) is the counter ID, as shown in the EMS
columns 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.
Figure 3-38: Enable PM confirmation
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.

Figure 3-39: PM Counters Confirmation prompt upon exit
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 opens.
Figure 3-40: Reset PM Data ( 24 Hr) confirmation prompt
3. Click Yes to continue. The progress bar at the bottom of the window shows
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.
Figure 3-41: Performance Monitoring Trail Filter dialog box
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.

Table 3-19: 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 (on page 3-83), 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 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.1 or later..

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 (on page 3-93). 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 (on page 3-96):
Add traffic entities to the reporting process, if needed; see Adding
Traffic Entities in LightSoft V4 User Manual.
Apply a template, if needed; see Working with Templates (on page
3-107).
Specify filter criteria.
b. Step 2: Report Definitions (on page 3-99):
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 (on page
3-103).

c. Step 3: Counter List (on page 3-101):

Select parameters and counters for the report; see Selecting
Parameters and Counters (on page 3-103).
Fine-tune the data records that will be presented; see Narrowing the
Report Content (on page 3-105).
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 (on page 3-108): 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 (on page 3-110): 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 (on page 3-112): 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
(on page 3-116). Fine-tune parameters as needed.
6. Generate the report; see Generating the Report (on page 3-118).
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 Template (on page 3-96): Adds traffic entities to the
reporting process, applies a template, and specifies Network operator and
Customer filter criteria.
| Step 2: Report Definitions (on page 3-99): Sets the aggregation of the
reported counts per TP and the period over which they are reported.
| Step 3: Counter List (on page 3-101): 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.
Figure 3-42: Multi Period PM dialog box

Table 3-20: 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 (on
page 3-116).
Save Template Creates a new template based on the currently selected
settings; see Working with Templates (on page 3-107).
Configure Configures values and rules that would identify counts for
Threshold a counter as "out of range" if they are below/above a
specified threshold; see Configuring Thresholds (on page
3-108).
Advanced Configures the report titles and logo and the color
Formatting 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 (on page 3-110).
Report Output Sets the output format and page size of the report, as well
Setup as its file name and save path; see Report Output Setup
(on page 3-112).
Export Report to Exports Multi Period PM data to a delimited-format CSV
CSV Format file for subsequent import to Microsoft Excel or a
relational database application; see Exporting PM Data to
CSV (on page 3-113).
Open Filter Filters in only records involving trails assigned specific
CoSs; see Filtering by CoS (on page 3-114).
Close Closes the window.
Buttons
Generate Produces the report after all settings have been
configured; see Generating the Report (on page 3-118).
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 (on page
3-98).
| Apply a template, if needed; see Working with Templates (on page 3-107).
| Specify Network operator and Customer filter criteria, if needed.
Figure 3-43: Multi Period PM dialog box – step 1
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 (on page 3-98).
| When accessed from the main window Multi Period PM icon or the
Traffic menu Multi Period PM option, all trails are initially retrieved.

Table 3-21: 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
Trail Parameters Pane.
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 (on page 3-114).
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 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 (on page 3-119).
Use Template Used to base the current report on an existing template; see
checkbox Working with Templates (on page 3-107).

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 (on page 3-98).
To add trails:
1. Open Step 1: Traffic and Template (on page 3-96).
2. Click the Add button. The Add Trail dialog box opens.
Figure 3-44: Add Trails dialog box
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.

Table 3-22: Multi Period PM Step1: Add Trail dialog box fields
Trail ID Exact System ID; see ID description in Step 1: Traffic and Template
(on page 3-96).
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 (on page 3-96).
Exact Match When selected, the reporting process considers only TPs with the
checkbox 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.

Table 3-23: 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 Select Last or Report Period.
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 (on page 3-99).
This step enables you to:
| Select parameters and counters for the report, see Selecting Parameters and
Counters (on page 3-103).
| Choose a narrower range of report records; see Narrowing the Report
Content (on page 3-105).
| 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
(on page 3-114).
| Total: The total number of records potentially available from the database
based on the trail and aggregation selections.
Table 3-24: Multi Period PM - Step3: Counter List pane - Report Configuration
panes
Report Content radio buttons
Table or Chart The Table option presents the report data as only table data.
radio buttons 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 (on page 3-110), 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 (on page 3-108) 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.
Figure 3-47: Large Report Mode message
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 (on page 3-105)), 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 (on
7
page 3-112).
Counter availability depends on the applicable technology.
The following table shows the parameters that can be selected for Multi Period
PM reports involving trails.

Table 3-25: 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 (on page 3-83).
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 timespan; 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 on page 3-103),
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 (on page 3-101) 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).

Figure 3-48: Report Data shortcut menu
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 on page 3-118), it
will include the specified record content. For more information about the
global reporting procedure, see Producing Multi Period PM Reports (on
page 3-92).

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 (on page 3-96) enables you to select a template and apply its values
to the current report. You can delete a selected template using the button.
Figure 3-49: Template dialog box
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 (on page 3-96) and Report Format (on page
3-119).
To apply an existing template:

| In Step 1: Traffic and Template (on page 3-96), 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 (on page 3-96), 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.
Figure 3-50: Save Template dialog box
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.
Figure 3-51: Template Already Exists dialog box
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 (on page 3-101). (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 (on page 3-110).
The report can be restricted to out-of-range counts; see the Only out of range
radio button in Step 3: Counter List (on page 3-101).

To open the Configuring Thresholds dialog box:

| From the Multi Period Performance Monitoring window, select the Report
Output Setup toolbar icon.
Figure 3-52: Configure Thresholds dialog box
Table 3-26: 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 (on page 3-101).
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.
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:

| From the Multi Period Performance Monitoring window, select the
Advanced Formatting toolbar icon.
Figure 3-53: Advanced Formatting dialog box

Table 3-27: 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 Logo that can appear on the top-right side first report pages. User
checkbox and may browse and select a logo. No logo appears until one is
Browse button selected.
(The ECI logo appears on the top-left side of first report pages.)
Threshold Color
Out of Range Color in which out-of-range records (as defined in Configuring
Color selector Thresholds, on page 3-108) 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 LifgtSoft V4 User Manual.
Chart Arrangement
Available when the Report Content - Chart radio button is selected in Step 3:
Chart Type Options are:
| Line Chart
| Bar Chart
| Area Chart
Chart Information can be presented per counter or in summary form, as
Appearance 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 (on page
3-112).
Add Chart When selected, includes the corresponding detailed report data
Data checkbox 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 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 LifgtSoft V4 User Manual.
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 (on page 3-113).
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:

| From the Multi Period Performance Monitoring window, select the Report
Output Setup toolbar icon.
Figure 3-54: Report Output Setup dialog box

Table 3-28: Multi Period PM: Report Output Setup dialog box fields
Saving Setup
Print to File When selected, enables a File Format dropdown list, which
checkbox 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 (on page 3-113).
File Name and When printing to file, you must specify a file name and save
Save Path path. Otherwise the report will not generate (warning "Output
browser 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 After the report is generated, it is opened in a pdf viewer.
checkbox
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 Select Landscape or Portrait.
buttons
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 in

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 (on page 3-101) 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 (on page 3-96). (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(on page 3-103).
2. From the Multi Period Performance Monitoring window, select the
Open Filter toolbar icon. The Filter dialog box opens.
Figure 3-55: CoS Filter dialog box
3. Select the CoSs to be filtered into the report.

4. Click Apply to save the settings, and Close to close the dialog box.

Table 3-29: Multi Period PM : Open Filter options
Icons
Selects the checkboxes of all CoS options (default, meaning
Check All 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.
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 (on
page 3-117).
To preview the report:

| From the Multi Period Performance Monitoring window, select the
Preview Report toolbar icon. The report is generated and opens in a
view window.
Figure 3-56: Multi Period Performance Monitoring View Report window

Preview Window Options

The Preview window provides the following toolbar options.
Table 3-30: Multi Period PM Preview window toolbar options
Toolbar icon Name Description

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 (on page 3-116). 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 (on page 3-101)) 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 (on page 3-119).
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 (on page 3-112).
2. From the Multi Period Performance Monitoring window, click the
Generate button; see Multi Period PM Window (on page 3-93). A
confirmation window opens showing the current report settings.
Figure 3-57: Generate Report Configuration window

3. Examine the settings. If you are satisfied, click Yes to produce the report.
If you selected Open in Viewer in Report Output Setup (on page 3-112),
the report opens in the default viewer.
Figure 3-58: PMH Report window
Report Format
Multi Period PM reports include the following elements:
| Report Header (on page 3-120): Applies to all reports.
| Subtitle per TP (on page 3-121): Applies to all reports.
| Detailed Count Table (on page 3-122): Applies to all reports except
Summary.
| Summary Report Detailed Count Table (on page 3-123): Applies to
Summary report only.
| Overall Statistics per TP (on page 3-124): Applies to all reports.
| Chart Graphics (on page 3-125): Applies to Chart reports only.

Report Header
All Multi Period PM report variations show report headers similar to the
following:
Figure 3-59: Report header for all reports
Table 3-31: Multi Period PM: Report Header
Report element Description

Logo Logo displayed at the top of the first page, as defined in
Advanced Formatting (on page 3-110).
Report Title Title displayed at the top of the first page, as defined in
Advanced Formatting (on page 3-110).
Generated Date/time report was generated or preview requested.
Report Period Report time span as defined in Step 2: Report Definitions (on
page 3-99).
Thresholds If Thresholds were defined (see Configuring Thresholds (on
page 3-108)), shows the configured threshold value for each
applicable counter.
Page Title Title defined in Advanced Formatting (on page 3-110)
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 (on page
3-99). The PM information for a TP is preceded by the following subtitle
captions. The captions are repeated at the top of each new page.
Figure 3-60: Report captions
Summary reports are requested by clicking the Summary checkbox in Step 1:

Traffic and Template (on page 3-96). 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
(on page 3-123).
Table 3-32: Multi Period PM: Subtitle caption per Information Segment

Customer Customer associated with the trail/TP, as defined in Step 1:
Traffic and Template (on page 3-96) 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 (on page 3-96)). 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 (on page
3-101).
| Chart is selected as the Report Content in Step 3: Counter List (on page
3-101) and Add Chart Data is selected in Advanced Formatting (on page
3-110). The detailed counts table is presented first, before the charts (see
Charts below).
Figure 3-61: Report Table

Table 3-33: Multi Period PM: Detailed count per counter table

Table Columns Parameters and counters, as selected in Step 3: Counter List (on
page 3-101).
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 (on page
3-99).
Table Rows One measurement line per aggregation defined in Step 2: Report
Definitions (on page 3-99).
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 (on page 3-122).
Figure 3-62: Summary Report example

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.
Figure 3-63: Overall Statistics table
Table 3-34: Multi Period PM: Overall Statistics per TP

Table Columns Parameters and counters, same as described for Detailed Count
Table (on page 3-122).
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 (on page
3-101), graphical charts are displayed for each TP.
The following chart settings are set in the Chart Arrangement pane in
Advanced Formatting (on page 3-110):
| 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 (on page 3-121)).
| Overall TP statistics (see Overall Statistics per TP (on page 3-124)).
| Detailed count table (see Detailed Count Table (on page 3-122)) if Add
Chart Data is selected in Advanced Formatting (on page 3-110).
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
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 (on
page 3-116).
| Last Week aggregation: You can define the week to start on a certain day,
for example, Monday.
| Maximum records per retrieval (see Large Report Mode on page 3-103):
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.
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
Viewing and Editing Link Properties in LightSoft V4 User Manual.
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 in LightSoft V4 User
Manual.
Parameters of link and duct failure alarms may have slightly different meaning
and behavior from EMS-generated alarms; see Fault Window Parameters in
NOTES:
Disconnectifon 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.
Figure 3-64: Current Alarms window with correlation-related elements

Table 3-35: Alarm Correlation-related columns
Column Description
Correlation When Alarm Correlation is enabled, shows the correlation state of an
alarm as being:
State
| 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 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.
Unique ID Unique identifier given to an alarm during the Alarms process life
cycle. Composed of:
| Workstation ID of the server that processed the alarm.
| Sequential ID, a sequential identifier in increasing order per alarm
(also used for primary/secondary associations). Not persistent and
may change following each alarm process initialization.
Primary ID When Alarm Correlation is enabled, for each secondary alarm, shows
the associated primary alarm ID. (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 (on page 3-131),
Table 3-36: Alarm Correlation-related icons
Toolbar Name
Description
icon
Show/Hide Toggles alternately between showing secondary alarms, or
/ Secondary hiding them (leaving only primary and uncorrelated alarms
Alarms in the table view); see Showing or Hiding Secondary
Alarms (on page 3-130).
Hierarchical Opens a new Current Alarms window with all the
Sort primary and secondary alarms sorted hierarchically; see
Showing Secondary Alarms of a Primary (on page
3-131).

Showing or Hiding Secondary Alarms

Suppressing secondary alarms from the table view usefully enables focusing
analysis efforts on 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 (on page
3-133). 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.
Figure 3-65: Current Alarms window showing/hiding secondary alarms

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).
Figure 3-66: Current Alarms window showing secondary alarms per primary

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 in LightSoft V4 User
Manual.
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 the 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 (on page 3-130). As well,
filters can be defined to filter out either correlated or uncorrelated alarms.
For example, you may want to filter out uncorrelated alarms, leaving only
primary alarms in the table. (A variety of other non-correlation-related alarm
filters are also available, for example Show Trail Affecting, which filters in
trail affecting alarms.) For information about filtering alarms, see Filtering
Fault Lists in LightSoft V4 User Manual. For more information about specific
alarm filters, see General Attributes in LightSoft V4 User Manual.
TIP: When secondary alarms are hidden - see Showing or

Hiding Secondary Alarms (on page 3-130) - 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.

Viewing Historical Log Events

LightSoft periodically exports the contents of Event logs so that they do not
become too large. This also enable 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 periodically
clearing archived files (on page 3-136).
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.
Figure 3-67: Event Log History window

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.
Figure 3-68: Import Log History Files dialog box
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 Archived Files (on page 3-136).
| Set the types of object-action combinations that will trigger the logging of
an event. For more information, see Setting Log Triggering Events (on
page 3-139).
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 Event
log configuration window - Event log parameters tab (on page 3-139).
Exporting Excess Log Records and

Periodically Clearing Archived Files
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 (on page 3-134).
| 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 in

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.
Figure 3-69: Event Log Configuration window - Event Log Parameters tab
2. In the Configure Event Log Parameters pane, set the maximum number and
age of records to be kept:
a. 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).
b. 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:
a. 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.
b. Starting at: enter this in HH:MM:SS format; for example, 13:00:00
indicates an export performed at 1 PM.
If the daily frequency is 3, this implies that two additional exports will
be performed each day, at 8 PM and 3 AM respectively (that is, at 24/3
= 8 hour intervals).
c. 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:
a. Select the Do not Delete radio button to not automatically delete any
files.
OR
b. 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.

Setting Log Triggering Events

The Event Log Configuration window Event Types to Log tab enables you to
set the types of events that will 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.
Figure 3-70: Events Log Configuration window - 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.

Checking the LightSoft Hard

Drive Capacity
The LightSoft station hard drive must frequently be checked to verify that it is
not full.
To check the LighSoft hard drive capacity:

1. Open the Unix window.
2. Set the user name to su -nms.
3. Type the command df -h. The hard drive capacity check window opens.
Figure 3-71: Typical hard drive capacity check window
4. Check that there are no partitions fuller than 80 %. If yes, copy the relevant
files to a backup disk on a PC using any FTP shareware application.
5. After backing up the files, delete old system files from LightSoft as
follows:
All the files from ~/coresave/ can be deleted
SecurityLog and ActionLog files can be deleted from ~/NMSEXPLOG,
by using the following command :
find ~/NMSEXPLOG/ -name “*” –mtime +X –exec rm –f {} \;
where X represents a number of which files that are older than X days
will be deleted.
(on page 2-10).

4
RDR Preventive Maintenance
In this chapter:
Overview ......................................................................................................... 4-1
Instance Discovery .......................................................................................... 4-2
Alarms Configuration ...................................................................................... 4-7
RDR Command Center Diag Mode................................................................. 4-9
Activating an Unscheduled Backup............................................................... 4-10
Activating an Unscheduled Archive Backup ................................................. 4-12
Viewing Crontab Entries ............................................................................... 4-13
Viewing Log Files ......................................................................................... 4-13
Overview
for the RDR application.
Table 4-1: RDR preventive maintenance procedures

Check Instance Once a month, or Performing Instance
discovery and following major Discovery (on page
details. changes in network 4-3)
architecture
Check the list of Once a month, or Viewing the List of
hosts receiving following major Hosts Receiving
RDR alarms. changes in network Alarms (on page
architecture 4-7)

RDR Preventive Maintenance XDM/SYNCOM Networks Preventive
Maintenance

Check the Once a month, or Checking Diagnostic
diagnostic following major Information (on page
information changes in network 4-9)
collected via architecture
Command Center
Diagnostic Mode.
Activate Once a week Activating an
unscheduled Unscheduled Backup
backup. (on page
4-10)
Check the Crontab Once a month, or Viewing Crontab
entries. following major Entries (on page
changes in network 4-13)
architecture
Check the log files. Once a week Viewing Log Files (on
page 4-13)
Instance Discovery
Instance discovery is the process of the RDR tool “finding” the instances (ems,
enm, or nms) installed on the primary components.
There are two types of discovery:
| Automatic: RDR presents the instances found in the etc/hosts file.
| Manual: You manually enter the instances.
You should run instance discovery in the following cases:
| During initial RDR configuration.
| After adding a new instance to a primary component.

XDM/SYNCOM Networks Preventive RDR Preventive Maintenance
Maintenance
Performing Instance Discovery

This procedure enables the RDR to discover the instances on the primary
components.
To perform instance discovery:

1. Log in as a root user.
2. From the CDE root menu, select RDR > RDR (global) > RDR Command
Center.
The RDR tool lists the previously discovered instances.
Figure 4-1: RDR instances
If this is the first time that you are running the RDR, the tool informs you
that there are no instances that have been previously discovered.
“No discovered Primary Components data found on BSComp.”

Maintenance
The Possible RDR modes of Activity menu is displayed.
Figure 4-2: Possible RDR modes of Activity
3. Do one of the following:

c. If there are no discovered instances, enter 1.
d. If there are instances but you want to run the discovery again, enter r
and then select 1 from the RDR Common Actions menu.
The RDR Discovery Menu appears with the following options:
e. Manual RDR instances discovery: Manually enter the host names to

be configured as primary components.
f. Discover RDR instances by hosts DB: The RDR application
automatically discovers the primary components using the /etc/hosts
file.
Figure 4-3: RDR Discovery Menu

Maintenance
4. To automatically discover the instances from the /etc/hosts file, select 2

Discover RDR instances by hosts DB. The discovery process begins.
When finished, a list of the hosts and the number of found instances
appears.
NOTE: Before continuing with configuration, you must quit

and re-enter the RDR application in order for the updates to
take effect.
Figure 4-4: Automatic instance discovery
5. To manually enter each primary component, do the following:

a. Select 1 Manual RDR instances discovery.
NOTE: Enter the host name, not the IP. The hosts entered
must be listed in the etc/hosts file. If you enter a host that is
not listed, you receive an error.
b. Continue entering host names of other primary components until

completed.
c. After completing all of the host names, enter q. The RDR lists the host
names to be discovered.
d. Press ENTER, to begin the discovery process. The RDR starts the
discovery process for the listed hosts, locating all installed instances on
each. When finished, a list of the hosts and the number of found
instances appears.
NOTE: Before continuing with configuration, you must quit

and re-enter the RDR application in order for the updates to
take effect.

Maintenance
Figure 4-5: Manual instance discovery
Viewing Instance Details

You can easily view an instance’s information, such as current available
backup replicas, backup scheduling, and alarms notification settings.
To view an instance’s details:

| From the RDR Instances list, select a configured instance and then select
1-Show Instance Status. Details of the instance are displayed.
Figure 4-6: View Status of an Instance

Maintenance
Alarms Configuration
In the event of a failure, an alarm is generated and a message is sent. By
default, the messages appear on the primary component console and the RDR
backup server console. You can create a list of additional hosts to receive the
alarms as well. These hosts must run X Server to be able to display the
messages.
As explained in Alarms Notification, there are two ways to configure the hosts
that display the messages:
| Private list: A list of hosts to receive the messages from a specific RDR
instance. The list is located in the file:
opt/RDR/config/backup/RDR.displays.<instance_name>
| Common list: A list of hosts to receive the messages from all RDR
instances. The list is located in the file:
/opt/RDR/config/backup/RDR.displays
Viewing the List of Hosts Receiving Alarms

The following procedures describe how to view the list of hosts receiving
alarms.
To define the hosts to receive alarms from all instances:

1. From the RDR Instances list, enter r. The RDR Common Actions menu
appears.
2. Select 3 Set Global Alarm Notification Options. The RDR Alarm
Notification Editor menu appears.
3. Further actions are the same as defining a host to receive alarms from a
specific instance. Continue with Step 3 in the following procedure.

Maintenance
To define the hosts to receive alarms from a specific

instance:
1. Select a configured instance and then select 2 Instance Configuration
Menu. The RDR Instance Configuration Options menu appears.
2. Select 4 Setup Alarms Notification. The RDR Alarm Notification
Editor menu appears.
Figure 4-7: RDR Instance Configuration Options Menu
3. To view the list of hosts receiving alarms, Select 3 Show Current

Notification List. The hosts receiving alarms for the selected instance are
displayed.
Figure 4-8: RDR Alarm Notification Editor

Maintenance
RDR Command Center Diag

Mode
To help diagnose problems, you can activate the command center mode in
order to create a log file with the following information:
| System information, such as HostInfo, menuconf, and networking
| All configuration activities
Checking Diagnostic Information

The following procedure enables you to check the diagnostic information
collected via the Command Center Diagnostic Mode.
To activate the command center diag mode:

1. From the RDR Instances list, enter r. The RDR Common Actions menu
appears.
Figure 4-9: RDR Commn Actions Menu
2. Select 7 Turn ON/OFF RDR Command Center Diag Mode. The menu
reappears marked with Diag Mode ON and a new option, 8 Collect
Diagnostic Information, is added.

Maintenance
3. To view the information, select 8 Collect Diagnostic Information.
Figure 4-10: Diag Mode On
Activating an Unscheduled
Backup
In addition to scheduled backups, you can perform a backup at any time. For
example, an immediate backup is needed:
| After first-time configurations. After completing first-time instance
configurations, it is strongly suggested to do a full backup for each
instance.
| Before an upgrade.
To begin an unscheduled regular backup:
NOTE: Full backups may take a long time.
1. From the RDR Instances list, select a configured instance.

2. Select 3 Start Regular Backup Session. The backup session begins.

Maintenance
NOTE: Only one backup session can run on a primary

component at a time. If you try to run a backup on a primary
component that has another backup session in progress, you
receive a Backup Session Overrun error.
Figure 4-11: Start backup session

Maintenance
Activating an Unscheduled
Archive Backup
An archive backup is a static backup of the system at a specific time. Use the
archive option in order to “freeze” the system state at a specific time to ensure
additional redundancy.
NOTE: Even though archive backups ensure additional

redundancy, take into account that an archived replica uses
additional disk space.
To begin an unscheduled archive backup:

1. From the RDR Instances list, select a configured instance. The RDR
Instance Actions Menu is displayed.
2. Select 4 Start Archive Backup Session. You are prompted to give a name
to the archive backup.
3. Enter a name or accept the default (archive). The archive backup begins.
Figure 4-12: Start archive backup

Maintenance
Viewing Crontab Entries

This section describes how to view the scheduled Crontab entries of a specified
instance.
To view Crontab entries:

1. From the RDR Instances list, select a configured instance. The RDR
instance Actions Menu is displayed.
2. Select 2 Instance Configuration Menu. The RDR Instance
Configuration Options menu appears.
3. Select 3 Schedule Instance Backups to start RDR Scheduler utility. The
backups that have already been scheduled are listed.
Figure 4-13: Viewing the Crontab Entries
Viewing Log Files

The RDR creates log files for each instance. Every time the RDR backs up an
instance, it updates the log file with information such as if the backup was
successful or failed.
The RDR automatically names the log files according to the format,
<instance>@<Hostname>_<zone>.log., and stores them in the folder
/var/RDR/logs.

Maintenance
RDR Recovery
RDR recovery is an operation which should be done on the RDR backup server when the
Primary component fails. It uses the replicas that were transferred from the Primary
component to the Backup server.
Before you start:

Before starting the RDR Recovery, make sure that both Primary and Backup server
applications are down.
To start an RDR Recovery:

1. From the RDR Instances list, select “r” for RDR General Menu. The
RDR Common Actions Menu is displayed.
Figure 4-14: RDR Common Actions Menu
2. Select 5 Select Command Center Mode . The Possible RDR modes of

activity is displayed.
Figure 4-15: Possible RDR modes of activity

Maintenance
3. Select 3 Mirror Component Actions. The RDR Mirror Component

Actions Menu is displayed.
Figure 4-16: RDR Mirror Component Actions Menu
4. Select 1 Start Mirror Recovery Session, and enter the Backup Server
name or IP address. The Mirror Instances list is displayed.
Figure 4-17: Mirror Instances list
5. Select the required mirros instance on the backup server.

6. Select the RDR Instance.

Maintenance
7. Select the Replica to restore from and confirm it.

8. Once the restore has been completed successfully, exit the RDR and start
the requested application on the backup server.
The results can also be seen in the RDR log file located in /var/RDR/logs
Figure 4-18: RDR log file

5
Hardware Preventive
Maintenance
In this chapter:
Hardware Preventive Maintenance Table ........................................................ 5-1
Hardware Preventive
Maintenance Table
Preventive maintenance activities are intended to keep the XDM hardware in
good condition, and as soon as possible detect and correct any condition that
may lead to deterioration and equipment malfunction. Record the execution of
the various activities and their results in accordance with the organizational
procedures.
The following table provides a list of preventive maintenance inspection and
checks and specifies recommended intervals. The frequency of checks for
equipment installed in unprotected environments should be increased as
required.
NOTE: The listed hardware preventive maintenance checks

refer to XDM platforms only.

Hardware Preventive Maintenance XDM/SYNCOM Networks Preventive
Maintenance
Table 5-1: Preventive maintenance inspection and checks
Item Description of inspection/check Intervals

W M Q
1. Visually inspect the condition of cables and fibers. Check for X
correct routing (no sharp bends) and proper support to avoid
stress.
Avoid touching, except when necessary to correct problems.
2. Condition of rack front doors and RFI fingers. Clean as X
necessary with approved agents.
3. Check that all unused optical connectors have protective X
covers. Add covers as necessary.
4. Check that cards and modules are securely attached: all X
extractor handles must be in the storage position (parallel to the
card edge), and all module fastening screws must be tight
(tighten only by hand).
5. Check for proper operation of all the xFCU and xFCU4 units, X
without abnormal noise and vibrations.
6. Check that the xFCU and xFCU4 units are fully inserted in X
their chassis positions and their screws are tight.
7. Clean the xFCU and xFCU4 units. To avoid overheating of the X
XDM-400 shelf, do not remove its xFCU4 unit for more than 2
to 3 minutes.
When cleaning, check increase in speed of the other xFCU
units when one is removed (not applicable to xFCU4).
8. Check proper attachment of xINF and xINF4 units to the shelf. X
9. Check the DC supply voltage. X
10. Check DC power sources (main and backup) and make sure all X
RAP circuit breakers serving active equipment units are in the
ON position.
11. Check that there are no alarm indications on the cards and X
modules.
12. Check that all xRAP LEDs turn on and the buzzer sounds when X
the POWER ON pushbutton on the xRAP panel is pressed.
13. Check that all card and module LEDs turn on when the LED X
TEST pushbutton on the MECP panel is pressed.
14. Perform a visual check of LED indications in accordance with X
Chapter 5 of the XDM IMM.
Legend:
W - Weekly M - Monthly Q - Quarterly

6
Checklists
In this chapter:
EMS-XDM Checklists ..................................................................................... 6-1
EMS-SYNCOM Checklists ............................................................................. 6-2
LightSoft Checklists ........................................................................................ 6-3
RDR Checklist ................................................................................................. 6-4
Hardware Checklists ........................................................................................ 6-4
EMS-XDM Checklists
Weekly Checklist
Procedure √ Date Result
Delete old system files.
Check login history.
Check log actions.
Check performance.
Check PM history reports for OPS-M objects.
Check alarms information.
Check EMS-XDM to NE communications.
Save EMS-XDM configuration to hard disk.

Preventive Maintenance Checklists XDM/SYNCOM Networks Preventive
Maintenance
Monthly Checklist
Export cross-connections data to XML files.
Export policer information to a file.
Export flow information to a file.
Check optical parameters.
Export topology data to an XML file.
Export card inventory data to an XML file.
Check perform maintenance and backup using a
script.
Quarterly Checklist
Save NE database configuration to hard disk.
Check version correspondence.
EMS-SYNCOM Checklists
Weekly Checklist
Save EMS-SYNCOM configuration to a backup
disk via FTP.
Check version correspondence for SYNCOM
NEs.
Delete old system files.
Check performance.
Check EMS-SYNCOM to NE communications.

XDM/SYNCOM Networks Preventive Preventive Maintenance Checklists
Maintenance
Quarterly Checklist
Save EMS-SYNCOM configuration to hard disk.
Check version correspondence.
Check management performance.
LightSoft Checklists
Weekly Checklist
Save LightSoft database.
Check the objects' status.
Check resource availability on links.
Check NEs status.
Synchronize LightSoft database with EMS
database.
Synchronize tunnels
Check batch trail operation
Check trails performance monitoring
Check multi period PM
Check alarms correlation
Check historical log events.
Check LightSofts' hard drive capacity.
Quarterly Checklist
Insert a NE into a link.
Remove a NE from a link.
Perform batch trail operations.

Maintenance
RDR Checklist
Weekly Checklist
Activate unscheduled backup.
Check the log files.
Monthly Checklist
Check Instance discovery and details.
Check the list of hosts receiving RDR alarms.
Check the diagnostic information collected via
Command Center Diagnostic Mode.
Check the Crontab entries.
Hardware Checklists
Weekly Checklist
Check that all unused optical connectors are
covered.
Check proper operation of xFCUs.
Check DC supply voltage.
Check DC power sources and xRAPs.
Check alarms indications on cards and
modules.
Check operation of xRAP alarm indications and
buzzer.
Check activation of LEDs on all cards and
modules.
Perform visual check of LED indications on
cards and modules.

XDM/SYNCOM Networks Preventive Preventive Maintenance Checklists
Maintenance
Monthly Checklist
Inspect condition of rack front doors and RFI
fingers.
Quarterly Checklist
Visually inspect cables and fibers condition.
Check cards and modules attachment.
Check xFCUs attachment.
Clean xFCUs.
Check xINFs attachment.

Maintenance

Index
A alarm log • 2-10
GbE and Optic logs • 2-12
Alarm Log window • 1-32
log files • 2-10, 2-12
Alarms
MS logs • 1-10, 2-12
current • 1-25
old system files • 1-7, 2-10
determining the cause • 1-28
PM logs • 1-10
exporting via Ethernet • 1-9
SaveBackup files • 1-12, 2-15
viewing the effect on Server Trails •
1-28 XC PM logs • 2-12
Displaying
B
15-minute PM logs • 2-12
Backing up the current configuration • 1- GEoS or optic • 2-12
5
MS/Line logs • 2-12
Batch trail operations
PM logs • 2-12
Importing trail definitions • 3-75
trail performance data • 1-10
Browse file window, typical • 1-10, 2-12
XC contents • 2-12
C
E
Change NE SW-Network window • 1-3
EMS-XDM Checklist
Charts, performance • 1-21
monthly • 6-2
Checking
quarterly • 6-2
alarm logs • 1-32, 2-21
weekly • 6-1
management performance • 1-34
Exporting a log • 1-7
network current alarms • 2-21
Exporting traffic definitions
performance • 1-18, 2-21
Traffic entities via UNIX • 3-69
PM values • 1-18, 2-21
Tunnels to CSV • 3-74
version correspondence • 1-4, 2-8
Client trails F
viewing end points performance • 1- FTP of alarms • 1-9
23 FTP Transfer
Current alarms • 1-25 logs • 2-10
Current performance, viewing • 1-18 preparations for • 2-10
D trail log • 1-10
Deleting
417006-2202-013-A00 ECI Telecom Ltd. Proprietary I-1

Index XDM/SYNCOM Networks Preventive
Maintenance
H viewing current performance • 1-18

Hardware Checklist viewing performance history • 1-19
monthly • 6-5 Ping • 1-33
quarterly • 6-5 PM
weekly • 6-4 viewing data • 2-24
Hardware Inspection and Checks • 5-1 PM Filter window • 1-10, 2-12
Historical end point performance Preventive Maintenance
monitoring • 1-24 checklists • 6-1
How to hardware • 5-1
determine the cause of an alarm • 1- via EMS-XDM® • 2-1
28 Printing an alarm log • 1-31
reset PM counters • 1-22 Printing performance history • 1-20
test communications using Ping • 1- R
33 Resetting performance counters • 1-22
view the alarm log • 1-30 S

I Saving
NE database configuration • 1-3, 2-6
Importing traffic definitions • 3-75
trail log file • 1-10
Traffic entities via Unix • 3-69
XC log files • 2-12
Tunnels • 3-75
Shelf View
L typical • 2-1
Log Export window • 2-10 SW Download window • 2-6
N T
NE • 1-3, 2-6 TCP/IP • 1-9
version correspondence • 1-4, 2-8 Testing the communication • 1-33
Network ElementSee NE • 1-3, 2-6 Trail
O inconsistency checks • 1-6
opening reconstruction window • 1-6
Operation Submenu • 2-6
Trail Log window • 1-10
P Trail management
Performance monitoring Importing trail definitions • 3-75
menu options • 1-18 Trail Reconstruction window • 1-6
performance charts • 1-21 U
printing historical data • 1-20
Unix • 1-13, 1-14, 1-15
resetting performance counters • 1-22
I-2 ECI Telecom Ltd. Proprietary 417006-2202-013-A00

XDM/SYNCOM Networks Preventive Index
Maintenance
V
Viewing current performance • 1-18
Viewing performance history • 1-19
Viewing trail end points performance data
• 1-23
417006-2202-013-A00 ECI Telecom Ltd. Proprietary I-3

Index XDM/SYNCOM Networks Preventive
Maintenance
I-4 ECI Telecom Ltd. Proprietary 417006-2202-013-A00

XDM-SYNCOM Preventive Maintenance A00 11-2009 en PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

XDM-SYNCOM Preventive Maintenance A00 11-2009 en PDF

Uploaded by

Copyright:

Available Formats

XDM®/SYNCOM Networks

© Copyright by ECI Telecom, 2004-2009. All rights reserved worldwide.

Preventive Maintenance Procedures via EMS-SYNCOM ..... 1-1

Preventive Maintenance Procedures via EMS-XDM ............. 2-1

417006-2202-013-A00 ECI Telecom Ltd. Proprietary i

Preventive Maintenance Procedures via LightSoft .............. 3-1

RDR Preventive Maintenance ................................................. 4-1

Hardware Preventive Maintenance ........................................ 5-1

ii ECI Telecom Ltd. Proprietary 417006-2202-013-A00

Preventive Maintenance Checklists ....................................... 6-1

Index .......................................................................................... I-1

417006-2202-013-A00 ECI Telecom Ltd. Proprietary iii

iv ECI Telecom Ltd. Proprietary 417006-2202-013-A00

417006-2202-013-A00 ECI Telecom Ltd. Proprietary v

Figure 2-15: PM Filter window ..................................................................................... 2-14

vi ECI Telecom Ltd. Proprietary 417006-2202-013-A00

Figure 3-6: Insert ME dialog box link attributes............................................................ 3-10

417006-2202-013-A00 ECI Telecom Ltd. Proprietary vii

Figure 3-45: Multi Period PM dialog box – step 2 ...................................................... 3-100

viii ECI Telecom Ltd. Proprietary 417006-2202-013-A00

Figure 4-13: Viewing the Crontab Entries .................................................................... 4-13

417006-2202-013-A00 ECI Telecom Ltd. Proprietary ix

x ECI Telecom Ltd. Proprietary 417006-2202-013-A00

417006-2202-013-A00 ECI Telecom Ltd. Proprietary xi

xii ECI Telecom Ltd. Proprietary 417006-2202-013-A00

417006-2202-013-A00 ECI Telecom Ltd. Proprietary xiii

| RDR Preventive Maintenance (on page 4-1): Provides a description of the

NOTE: Many of the preventive procedures outlined in this

Convention Indicates Example

NOTE: Text set off in this manner presents clarifying

xiv ECI Telecom Ltd. Proprietary 417006-2202-013-A00

CAUTION: Text set off in this manner indicates that failure

WARNING: Text set off in this manner indicates that failure

LASER WARNING: Text set off in this manner indicates

ESD: Text set off in this manner indicates information on

TIP: Text set off in this manner includes helpful information

IMPORTANT: Text set off in this manner presents essential

What is New in this Version?

417006-2202-013-A00 ECI Telecom Ltd. Proprietary xv

xvi ECI Telecom Ltd. Proprietary 417006-2202-013-A00

ECI Telecom's XDM® and BroadGate® product lines are

417006-2202-013-A00 ECI Telecom Ltd. Proprietary xvii

xviii ECI Telecom Ltd. Proprietary 417006-2202-013-A00

Table 1-1: Preventive maintenance procedures via EMS-SYNCOM

Procedure Performed Section Comments

417006-2202-013-A00 ECI Telecom Ltd. Proprietary 1-1

Procedure Performed Section Comments

NOTE: Unless otherwise specified, all preventive

Figure 1-1: Typical EMS-SYNCOM main window

1-2 ECI Telecom Ltd. Proprietary 417006-2202-013-A00

This procedure should be performed once a week or whenever major changes

To perform backup to hard disk:

NOTE: The version number displayed in this window

Figure 1-2: Change NE SW - Network window

2. Click the NE type field to select the corresponding type.

417006-2202-013-A00 ECI Telecom Ltd. Proprietary 1-3

NOTE: The example above describes backing-up all NEs of

5. Repeat steps 2 to 4 for each NE type.

To check version correspondence:

1-4 ECI Telecom Ltd. Proprietary 417006-2202-013-A00

NOTE: Only the administrator can use this function. It cannot

The EMS-SYNCOM system always keeps a backup copy of the current

417006-2202-013-A00 ECI Telecom Ltd. Proprietary 1-5