LynxVISION

Element and Service Management

System

User Guide
Version 1.3.1

ii

0BImportant Notice
LynxVision EMS User Guide

Important Notice
Copyright

2001-2007 Lynx Photonic Networks, Inc.

All intellectual property rights in this publication are owned by Lynx Photonic
Networks, Inc. and protected by United States copyright laws, other applicable
copyright laws and international treaty provisions. Lynx Photonic Networks, Inc.
retains all rights not expressly granted. No part of this publication may be
reproduced in any form whatsoever or used to make any derivative work without
prior written approval by Lynx Photonic Networks, Inc.
No representation of warranties for fitness for any purpose other than what is
specifically stated in this guide is made either by Lynx Photonic Networks, Inc. or
by its agents.
Lynx Photonic Networks, Inc. reserves the right to revise this publication, and/or
make improvements or changes in the product(s) and/or the program(s) described
in this documentation at any time without prior notice.
Any software on removable media described in this publication is furnished under
a license agreement included with the product as a separate document. If you are
unable to locate a copy, please contact Lynx Photonic Networks, Inc. and a copy
will be forwarded to you.
Lynx Photonic Networks, the Lynx Photonic Networks logo, LightLEADER, and
LynxVISION are trademarks of Lynx Photonic Networks, Inc. All other
trademarks are the property of their respective owners.
Other company and brand products and service names are trademarks or registered
trademarks of their respective holders.
For further information contact Lynx Photonic Networks, Inc., your local
distributor or reseller:
USA:

Lynx Photonic Networks, Inc., 6303 Owensmouth Avenue, Woodland

Hills, CA 91367. Tel: +1-818-936-3557 Tel: +1-866-465-9697
(1-866-GO-LYNXPN) Fax: +1-818-936-3022

Israel:
Lynx Photonic Networks Ltd, 13 HaMelaha Street, Afek Industrial
Park, Rosh Haayin 48091, Israel.
Tel: +972-3-915-5000 Fax: +972-3-903-3129
Email:

[email protected], [email protected]

Web:

www.lynxpn.com

Disclaimer
The information in this document is provided in good faith, but without any
representation or warranty whatsoever, whether it is accurate, or complete or

Table of Contents
LynxVision EMS User Guide

otherwise and on express understanding that Lynx Photonic Networks shall have
no liability whatsoever to other parties in any way arising from or relating to the
information or its use.
Lynx Photonic Networks assumes no responsibility as a result of the use or
application of products. No rights, implied or assumed are furnished under any
patent or pending patent with the sale or delivery of any Lynx product.

iii

iv

1BAbout This Guide

LynxVision EMS User Guide

About This Guide

This user's guide is comprised of the following chapters:

Preface, describes the purpose of this guide and the

audience for whom it is relevant.

Glossary, provides definitions for various terms used

in this guide.

Chapter 1, Introducing LynxVISION, provides an

overview of the LynxVISION system, and its features
and benefits.

Chapter 2, Installing LynxVISION, describes the

procedure for installing LynxVISION.

Chapter 3, Starting and Shutting Down the

LynxVISION Server and Client, describes how to
start and shut down the LynxVISION server and client.

Chapter 4, Security Management, describes how

security is enforced in LynxVISION and the users
management function.

Chapter 5, Administering LynxVISION, describes

how to configure LynxVISION to suit your
requirements.

Chapter 6, Managing LightLEADERs, describes

how LightLEADER devices are discovered, added and
viewed in LynxVISION. It also describes how to use
the graphical Device View to monitor and configure
ports, APS groups, and other items.

Chapter 7, Fault Management, describes the fault

management functionality provided by LynxVISION.

Chapter 8, File Operations, describes operations for

downloading/uploading files to/from a LightLEADER.

Chapter 9, Performance Monitoring, describes how

to monitor the performance of LightLEADERs.

Chapter 10, Managing an APS, describes how to

configure and monitor APSs.

Table of Contents
LynxVision EMS User Guide

Chapter 11, Managing an APS Group, describes

how to add, configure and monitor an APS group.

Chapter 12, Tools, describes the tools that are

provided with LynxVISION. These tools together with
the LynxVISION GUI offer a complete management
solution.

vi

2BPreface
LynxVision EMS User Guide

Preface
Audience
The LynxVISION application is used for managing LightLEADER network elements
and/or the protected services carried by them.
This user guide is written for operators who will be using LynxVISION. There are four
types of operators:

Software Installer: A person who is responsible for

installing this application for the first time.

Administrator: A person who is responsible for the

management of the LynxVISION application after
installation. An administrator does not need to know
how to manage the LightLEADERs.

Privileged User: A person who configures and

monitors the LightLEADER and the protected services.

User: A person who can only monitor the state of the

LightLEADERs and the protected services. A user can
also change his own details (name, phone number,
email, etc.) and password.

Each chapter in this book indicates its target audience, which is one of the types of
operators listed above.

Purpose
The purpose of this guide is to provide the reader with all the information required to
install, run and use the LynxVISION server and client applications in order to manage a
LightLEADER network and the protection of services that it provides.

Table of Contents
LynxVision EMS User Guide

Glossary
The following describes a few of the basic terms used in this guide.
Term

Description

APS

Automatic Protection Switching: Function that automatically

switches the signal from the Working link to the Protection link
when the Working link malfunctions (and vice versa).

APS Group

Combination of the APSs on the west and on the east

LightLEADER that provide end-to-end protection to the client
service.

CAPEX

Capital expenses.

Degradation level

A user defined dBm level as a threshold. When the signal power

falls beneath the degraded threshold a notification will be
received.

Extra Traffic

A lower priority signal that is transmitted on the Protection link as

long as the Working link functions. When the Working link fails,
it is transferred to the Protection link and the extra traffic link is
cancelled.

FCAPS

Fault, Configuration, Accounting, Performance, and Security. The

LynxVISION application provides a solution for FCAPS.

LOS

Loss of signal.

Main Service

Main traffic signal. The signal that is protected by two alternative

links, called the Working and Protection links.

OPEX

Operating expenses.

Protection Link

The Main traffic signal is transmitted on the Protection link when

the Working link fails.

Protection Type:
1:n

Up to n services are protected by one Protection link. It may

support one extra traffic signal.

Protection Type
1:1

A specific case of 1:n, where n equals 1. There is one Main

service, one Working link and one Protection link. The Main
traffic is transmitted on the Working link.

Protection Type:
1+1

1+1 protection architecture has one Main service, one Working

link and one Protection link. The Main traffic is transmitted on
both the Working and Protection links.

vii

viii

3BGlossary
LynxVision EMS User Guide

Term

Description

Switching Mode:
Dual-ended

Both ends participate in the protection operation, and coordination

between them is required to enable signal routing. When one side
of a service switches to a link (Protection or Working), the other
side also switches to the same link.

Switching Mode:
Single-ended

The APS at each end of the link works independently of the other
APS. Each APS may be configured separately and the switchovers
at each either end are made independently.

Working Link

The Main traffic signal is transmitted on this link as long as it is

functional and there was no user command placed that ordered the
system to switch to protection.

Table of Contents
LynxVision EMS User Guide

Table of Contents
Important Notice .................................................................................................................... ii
Disclaimer............................................................................................................................ ii
About This Guide .................................................................................................................. iv
Preface .................................................................................................................................... vi
Audience ............................................................................................................................. vi
Purpose ............................................................................................................................... vi
Glossary ............................................................................................................................. vii
Table of Contents................................................................................................................... ix
Table of Figures ................................................................................................................... xiii

1 Introducing LynxVision .......................................................................1

Overview of LynxVISION ..................................................................................................... 2
Computing Environment...................................................................................................... 2
LynxVISION Managed Elements ......................................................................................... 2
LightLEADER ................................................................................................................. 3
Automatic Protection Switching (APS) ............................................................................... 3
LynxVISION FCAPS Capabilities........................................................................................ 5
Fault Management ............................................................................................................... 5
Configuration ....................................................................................................................... 5
Performance Monitoring...................................................................................................... 6
Security ................................................................................................................................ 6

2 Installing LynxVISION .........................................................................8

System Requirements............................................................................................................. 9
Software Installation ............................................................................................................ 11

3 Starting and Shutting Down the LynxVISION Server and Client.15

Starting the LynxVISION Server ....................................................................................... 16
Shutting Down the LynxVISION Server............................................................................ 17
Starting the LynxVISION Client ........................................................................................ 19
The Main Window ............................................................................................................. 20
Exiting the LynxVISION Client.......................................................................................... 25

4 Security Management ..........................................................................26

ix

4BTable of Contents
LynxVision EMS User Guide

User Profiles...........................................................................................................................27
Changing Your Password.....................................................................................................28
Managing Users.....................................................................................................................29

5 Administering LynxVISION .............................................................. 34

Entering License Information ..............................................................................................35
Setting System Variables ......................................................................................................36

6 Managing LightLEADERs ................................................................. 43

Adding a LightLEADER ......................................................................................................44
Auto Discovery Process......................................................................................................44
Adding a LightLEADER Manually....................................................................................45
Creating a Submap ...............................................................................................................48
Configuring Background Images.........................................................................................52
LightLEADER Operations...................................................................................................54
Using Device View to Manage a LightLEADER Device ....................................................57
The 3000 and 4000 LightLEADER Device Families ..........................................................58
Displaying Device View.........................................................................................................59
Device View Display for the 4000 Device Family................................................................60
Device View LEDs.............................................................................................................61
LightLeader-4000 Device Family Slots..............................................................................61
Configuring and Monitoring Cards ....................................................................................63
Resetting All Cards for LightLEADERs in the 4000 Device Families...............................66
Configuring and Monitoring Ports and APSs .....................................................................67
Expected Module for a Slot ................................................................................................68
Device View Display for the LightLEADER 3000..............................................................69
Controlling and Monitoring Ports.......................................................................................69
LL3000 Power Supply Operations .....................................................................................71

7 Fault Management............................................................................... 75
Overview ................................................................................................................................76
Events Severity Levels .......................................................................................................77
Color Code..........................................................................................................................78
Displaying Logs .....................................................................................................................79
Filtering Event Logs..............................................................................................................81
Filtering Alarm Logs.............................................................................................................83
Acknowledging Alarms.........................................................................................................86

Table of Contents
LynxVision EMS User Guide

Audio Indication Configuration .......................................................................................... 87

Current Alarm Graph.......................................................................................................... 88
Email Notification................................................................................................................. 89

8 File Operations .....................................................................................90

Setting Up the TFTP Server ................................................................................................ 91
Downloading Files to a LightLEADER .............................................................................. 92
Uploading Files to a LightLEADER ................................................................................... 98

9 Performance Monitoring...................................................................101
Overview ............................................................................................................................. 102
Performance History .......................................................................................................... 103
Exporting to an Excel Spreadsheet ................................................................................... 104
Time Based Samples........................................................................................................... 105
Zooming in....................................................................................................................... 106
Delta Power Samples.......................................................................................................... 107
Delta Power Settings........................................................................................................... 108
Error Seconds Table........................................................................................................... 109
Degraded Seconds Table.................................................................................................... 110
Power Monitoring............................................................................................................... 111

10 Managing an APS.............................................................................112
What Is an APS?................................................................................................................. 113
APS States ....................................................................................................................... 113
Monitoring an APS............................................................................................................. 115

11 Managing an APS Group ................................................................119

What Is an APS Group? .................................................................................................... 120
APS Group State.............................................................................................................. 120
Adding an APS Group ....................................................................................................... 122
Monitoring an APS Group ................................................................................................ 131
APS Group Monitoring Window ..................................................................................... 133
Control and Command Panel ........................................................................................... 134
Commands ....................................................................................................................... 135
Mismatched APS States................................................................................................... 136
Hovering Over the APS Group Monitoring Window ...................................................... 139
Configuring an APS Group ............................................................................................... 142

xi

xii

4BTable of Contents
LynxVision EMS User Guide

12 Tools.................................................................................................. 144
MIB Browser .......................................................................................................................145
Telnet....................................................................................................................................146

Table of Contents
LynxVision EMS User Guide

Table of Figures
Figure 1: LightLEADER Protection System.................................................................... 4
Figure 2: LynxVISION Welcome Window ................................................................... 11
Figure 3: Select Destination Directory Window............................................................ 12
Figure 4: Select Start Menu Window............................................................................. 13
Figure 5: Select Additional Tasks Window ................................................................... 14
Figure 6: Completion Window ...................................................................................... 14
Figure 7: Shutdown LynxVISION Server Window....................................................... 17
Figure 8: Shutdown Status Window .............................................................................. 18
Figure 9: Login Window................................................................................................ 19
Figure 10: Main Window............................................................................................... 23
Figure 11: Change Password Window........................................................................... 28
Figure 12: Users Management Window ........................................................................ 29
Figure 13: Phone Number Window ............................................................................... 31
Figure 14: NMS Licensing Window.............................................................................. 35
Figure 15: Enable Auto Commit Window ..................................................................... 36
Figure 16: Set Poll Interval Window ............................................................................. 37
Figure 17: Alarm Indication Configuration Window..................................................... 37
Figure 18: Server Trap Community window ................................................................. 38
Figure 19: SMTP Server Parameters window................................................................ 38
Figure 20: Discovery Configuration Window................................................................ 40
Figure 21: Map Menu .................................................................................................... 45
Figure 22: Add LightLEADER Window ....................................................................... 46
Figure 23: Map Menu .................................................................................................... 48

xiii

xiv

4BTable of Contents
LynxVision EMS User Guide

Figure 24: Add Submap Window................................................................................... 48

Figure 25: LightLEADER Menu.................................................................................... 49
Figure 26: Move LightLEADER Window..................................................................... 49
Figure 27: LightLEADER in a Submap in the LightLEADER Devices Tree................ 50
Figure 28: APS Group Split Between Two Submaps .................................................... 50
Figure 29: LightLEADER Within Submap.................................................................... 51
Figure 30: Map Menu..................................................................................................... 52
Figure 31: LightLEADER Menu.................................................................................... 54
Figure 32: Device View - Chassis of a 4000 LightLEADER Device ............................ 60
Figure 33: Hovering Over an Element on the Chassis ................................................... 60
Figure 34: Card Details .................................................................................................. 64
Figure 35: Card Files and Swap Button ......................................................................... 65
Figure 36: Performance History for a Service................................................................ 68
Figure 37: Chassis Display for a 3000 Family Device................................................... 69
Figure 38: Device View Menu for Port.......................................................................... 69
Figure 39: Port Thresholds dialog box ........................................................................... 70
Figure 40: Performance History Menu........................................................................... 70
Figure 41: Power Supply Details ................................................................................... 71
Figure 42: Power Supply Options .................................................................................. 72
Figure 43: Power Supply DC Sensors Alarms ............................................................... 72
Figure 44: Chassis Menu................................................................................................ 73
Figure 45: Fault Management Menu.............................................................................. 79
Figure 46: LightLEADER Fault Management............................................................... 79
Figure 47: Event Log Window....................................................................................... 80
Figure 48: Events Filter Window ................................................................................... 82
Figure 49: Current Alarms Window............................................................................... 83

Table of Contents
LynxVision EMS User Guide

Figure 50: Alerts Filter Window.................................................................................... 84

Figure 51: Exporting a graph to an Excel spreadsheet................................................. 104
Figure 52: Performance Monitoring Time based samples ........................................ 105
Figure 53: Zooming in ................................................................................................. 106
Figure 54: Drops and rises in the delta power samples................................................ 107
Figure 55: Delta Power Settings power supply status............................................... 108
Figure 56: Error seconds table ..................................................................................... 109
Figure 57: Degraded seconds table .............................................................................. 110
Figure 58: Power Monitoring Graph............................................................................ 111
Figure 58: LightLEADER Menu, Monitor APS Option .............................................. 115
Figure 60: APS Monitoring Window........................................................................... 116
Figure 61: APS Configuration Window, Configuration Tab ....................................... 117
Figure 62: APS Configuration Window, Ports Tab ..................................................... 118
Figure 63: Mismatched APS States ............................................................................. 121
Figure 64: LightLEADER Menu ................................................................................. 123
Figure 65: Add APS Group Wizard: Main Window.................................................... 123
Figure 66: Add APS Group Wizard: Configuration Window...................................... 125
Figure 67: APS Power Thresholds Window ................................................................ 127
Figure 68: Add APS Group Wizard, Additional Data Window................................... 129
Figure 69: APS Group in the APS Groups Tree and Map View.................................. 130
Figure 70: Selected APS Group Link .......................................................................... 131
Figure 71: APS Group Menu, Monitor APS Group Option......................................... 132
Figure 72: APS Group Monitoring Window................................................................ 133
Figure 73: Set Command List ...................................................................................... 135
Figure 74: Mismatch Error Warning Window ............................................................. 137
Figure 75: Clear and adjust both Commands............................................................... 138

xv

xvi

4BTable of Contents
LynxVision EMS User Guide

Figure 76: APS Group Monitoring Window: Displaying the Name of a Port ............. 139
Figure 77: APS Group Monitoring Window: Connection Between Two clients......... 140
Figure 78: APS Group Monitoring Window: Link Power Thresholds Window.......... 140
Figure 79: Monitoring Thresholds ............................................................................... 141
Figure 80: APS Group Configuration Window, Configuration Tab ............................ 142

5BChapter 1
Introducing LynxVISION
LynxVision EMS User Guide

Chapter 1
Introducing LynxVISION
About This Chapter
This chapter describes how the LynxVISION Element and Service Management System
can be used to manage a LightLEADER optical network.
This chapter contains the following sections:

Overview of LynxVISION, page 2, describes how

LynxVISION manages an optical network and the
computer environment in which it works.

Network Elements Managed by LynxVISION, page

2, describes the LightLEADER Automatic Protection
Switching (APS) functionality and protection types.

LynxVISION Configuration and Monitoring

Features, page 3, describes how LynxVISION graphic
features can be used to manage the LightLEADER
network.

FCAPS Model, page 5, describes the LynxVISION

fault management, configuration and security features.

Target Audience: This chapter should be read by all people who use LynxVISION.

5BChapter 1
Introducing LynxVISION
LynxVision EMS User Guide

Overview of LynxVISION
LynxVISION provides an easy to use, Java-based, client-server, scalable management
system that is based on the FCAPS model. It covers all key areas including fault
management, configuration management, performance monitoring ,security, and
administration capabilities.
LynxVISION operates as a client/server application where the software is installed on a
server computer, which can then be simultaneously accessed by numerous clients
(located either on the server or on other computers). In this architecture, the server
communicates with the network elements, using SNMP, while the client communicates
with the server.
The LynxVISION client application offers operators an easy to use, intuitive, Graphical
User Interface that covers all functions of the application.
The LynxVISION server is responsible for discovering and maintaining the inventory
(LightLEADERs and cards) and protected services within the managed network, the
collection of data from the LightLEADER using the SNMP protocol, processing the
data and storing it. All data is stored in a database that ensures that all clients have the
same view of the network. The database is automatically backed up periodically,
allowing the operator to recover the database.

Computing Environment
LynxVISION aims at minimizing the total cost of owning and operating the computing
platform on which it runs.
To achieve this goal, both the LynxVISION server and client run on the Windows
NT/XP computing platform.
Software is installed only on a single computer that is used as the LynxVISION server.
Once the server is running, operators can launch the client application from any
computer with Internet Explorer, Version 6 and JRE1.5 or higher. If it is not already
installed, JRE will be automatically installed. See Starting and Shutting Down the
LynxVISION Server and Client, page 15.

5BChapter 1
Introducing LynxVISION
LynxVision EMS User Guide

LynxVISION Managed Elements

LightLEADER
LynxVISION manages all products within the LightLEADER 3000 and LightLEADER
4000 families.
The LightLEADER 3000 is a 1RU 19 fixed system supporting one or more (depending
on the model) APS entities.
The LightLEADER 4000 is a compact modular, carrier class, stackable 1RU 19
system with redundant power supplies and plug-in hot swappable APS cards.
For more information regarding the various types of LightLEADERs and APS cards,
refer to the LightLEADER user guides.

Automatic Protection Switching (APS)

LynxVISION enables the operator to manage APS functions and APS groups.
The APS function facilitates transporting a service via more than one link. When the
Working transport entity fails, the Main signal is transported via the Protection link.
An APS function is implemented by a physical APS entity that includes the control
logic, monitoring logic, and the physical interfaces (ports). APS entities are plug-in
cards (APS cards) in the LightLEADER 4000, and fixed elements in the LightLEADER
3000.
To offer end-to-end protection, two APS entities (LightLEADERs with an APS
function) are placed at each end of the optical network segment, as depicted in the
figure below:

5BChapter 1
Introducing LynxVISION
LynxVision EMS User Guide

Figure 1: LightLEADER Protection System

In the figure above, the two APS entities are connected by the Working and Protection
links. In order to create a protected service, an APS function is provisioned at each end.
This pair of APS functions, which provides end-to-end protection, is termed an APS
Group.
For more information, refer to the LightLEADER user guides relevant to the models
that you have purchased.

5BChapter 1
Introducing LynxVISION
LynxVision EMS User Guide

LynxVISION FCAPS Capabilities

Fault Management
LynxVISION fault management provides the means to detect and correct problems in
the network with speed and accuracy.
LynxVISION fault management provides alarm handling, trap handling, polling
service, testing and diagnostics. Event and alarm logs are recorded and a current alarm
list is maintained. LynxVISION ensures that all failures in the managed network are
detected and all related data is collected and available for the user to view.
Visual indications allow the user to know of a new alarm, the number of acknowledged
and unacknowledged alarms currently in the network, and the status of each
LightLEADER and APS group.
To allow rapid isolation of the problem, all event and alarm logs can be filtered
according to the time, date, event id, source object (device/card/port) and severity.
To ensure that problems are not left unnoticed because a client is currently not running,
the user can demand to receive email notifications when an alarm is discovered, and
when it clears. Each user that is interested in receiving notifications can specify the
minimum severity (critical, major, minor) for which an email is sent to him. For further
details, refer to page 75, Fault Management.

Configuration
LynxVISION configuration management enables the user to control LightLEADERs,
LightLEADERs' resources (cards, APSs, ports, etc.), and to create and control APS
groups.
LynxVISION provides the following configuration capabilities:

Automatically discovers installed LightLEADERs in

the managed network, and maintains a record of all the
LightLEADER resources (cards, APSs, ports, etc.).

5BChapter 1
Introducing LynxVISION
LynxVision EMS User Guide

Gathers information regarding location, quantities of

equipment, model numbers, serial numbers, versions,
optical parameters (thresholds, wavelengths), etc.

Enables the user to create APS groups, using the

discovered resources, provision and control them.

Provides the ability to upload the device configuration

for backup purposes, and to restore it at a later time.

Enables upgrading the LightLEADERs by

downloading new software images.

Performance Monitoring
LynxVISIONs Performance Monitoring tools allow you to monitor the performance of
the optical network and the QoS offered to customers of the protected services.
LynxVISION periodically collects data from the managed LightLEADERs regarding
the power levels, state (FAIL, Degraded, OK), and role (active or backup) of each port.
It also collects data regarding the QoS each service received, indicating times where the
protected client did not receive a signal. Data is presented to the operator in graphs and
tables.
By monitoring the performance for each individual port, you can quickly spot problems
in the network, monitor sudden power changes in real time, as well as monitor
performance over a longer period of time for a deeper analysis of reoccurring trends,
resource degradation over time, problems and malfunctions.
For further details, see page 101, Performance Monitoring.

Security
Only authenticated users can access LynxVISION. Each user is associated with a
security profile that defines the operations that are allowed. Users are authenticated by
entering a user name and password. LynxVISION provides three types of users, who
have the following security profiles:

Administrator: User who can perform all functions.

Privileged User: User who can both view and change

configuration parameters, but cannot perform various
administrative functions, such as creating new users.

5BChapter 1
Introducing LynxVISION
LynxVision EMS User Guide

User: Basic users who can use the LynxVISION

application to view the configuration and state of the
LightLEADERs and services, without the ability to
modify them.

For further details, refer to Security Management, page 26.

6BChapter 2
Installing LynxVISION
LynxVision EMS User Guide

Chapter 2
Installing LynxVISION
About This Chapter
This chapter describes the procedure for installing LynxVISION and contains the
following sections:

System Requirements, page 9, describes the system

requirements.

Software Installation, page 11, describes how to

install LynxVISION.

Target Audience: This chapter should be read by the

person who installs LynxVISION.

6BChapter 2
Installing LynxVISION
LynxVision EMS User Guide

System Requirements
Server Requirements
The following are the system requirements for the server on which LynxVISION is to
be installed:
Workstation Requirements

IBM-compatible PC: Pentium III 1GHz with 1 Gb RAM and CD-ROM drive
minimum

Pentium 4 2 GHz or higher recommended

200 Mb of free disk space minimum, 2Gb recommended

Operating System Requirements

Windows 2000, 2003 Server, 2000 Professional SP4, or XP Professional SP1a

and SP2

All Windows platforms with Sun Java Runtime Environment 1.5.0 1 or higher

Databases

LynxVISION ships with mySQL DB

The PC used as the LynxVISION server (where the application is installed) should run
only the LynxVISION server (and optionally client) application. No other application
should be run on the same computer.

In case Java runtime environment is not installed on the workstation, it shall be installed as part
of the LynxVISION installation process.

10

6BChapter 2
Installing LynxVISION
LynxVision EMS User Guide

Client Requirements
Workstation Requirements

IBM-compatible PC: Pentium III 512 GHz with 512Kb RAM

Pentium 4, 1 GHz or higher recommended

100 Mb of free disk space minimum

Operating System Requirements

Windows 2000, 2003 Server, 2000 Professional SP4, or XP Professional SP1a

and SP2

All Windows platforms with Sun Java 2, Runtime Environment 1.5.0 2 or higher

Web browser

Internet Explorer 6.0 or higher

In case Java runtime environment is not installed on the workstation, the user shall be asked to
install it the first time the LynxVISION client is launched. The installation is done from
LynxVISION server (see Chapter 3, Installing JRE1.5).

6BChapter 2
Installing LynxVISION
LynxVision EMS User Guide

Software Installation
Installation of LynxVISION software must be performed on a server machine that
meets the requirements specified in the previous section.
Once the server is installed and started, you can run the client application, which is the
Graphical User Interface (GUI) of LynxVISION. The client can be run from any
computer with an IP connection to the server and which is capable to support the Java
Runtime Environment 1.5 or higher.
To install LynxVISION on the server:
1

Close all open applications on the server.

Insert the LynxVISION CD. If the drive is configured to Autorun, the

installation process begins automatically. If the installation window is
not automatically displayed, use Windows Explorer to run the Setup
program, which is located in the root directory of the CD (if you are
running on a PC). Otherwise, use the appropriate run command in your
system. The following window is displayed:

Figure 2: LynxVISION Welcome Window

Click Next and browse to the directory in which you want to install the
LynxVISION files, as shown below:

11

12

6BChapter 2
Installing LynxVISION
LynxVision EMS User Guide

Figure 3: Select Destination Directory Window

Click Next and browse to the Start Menu folder in which you want to
store the program's shortcuts, as shown below:

6BChapter 2
Installing LynxVISION
LynxVision EMS User Guide

Figure 4: Select Start Menu Window

Click Next and select the checkbox(s) to indicate whether you want
LynxVISION to create a desktop icon and/or a Quick Launch icon.

13

14

6BChapter 2
Installing LynxVISION
LynxVision EMS User Guide
Figure 5: Select Additional Tasks Window

Click Next. LynxVISION begins the installation process. When the

process is completed, the following window is displayed:

Figure 6: Completion Window

Click Finish to exit the installation program

The LynxVISION application is now ready to be launched from the Start menu of the
server (Start | Programs | LynxVISION | Start LynxVISION), by clicking the
desktop icon, or by clicking the Quick Launch icon.

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

Chapter 3
Starting and Shutting Down the
LynxVISION Server and Client
About This Chapter
This chapter describes how to start the LynxVISION server and client and how to shut
them down. It contains the following sections:

Starting the LynxVISION Server, page 16, describes

how to start the LynxVISION server.

Shutting Down the LynxVISION Server, page 17,

describes how to shut down the LynxVISION server.

Starting the LynxVISION Client, page 19, describes

how to log on to the client.

Exiting the LynxVISION Client, page 20, describes

how to close a LynxVISION client application.

Target Audience: The Starting the LynxVISION Server and Shutting Down the
LynxVISION Server sections should be read by an Administrator. The Starting the
LynxVISION Client and Exiting the LynxVISION Client sections should be read by an
Administrator, Privileged User and User.

15

16

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

Starting the LynxVISION Server

The LynxVISION server is responsible for the application logic, communication with
the LightLEADERs, storage of user specific data (such as map images) and storage of
the LynxVISION client applet. Before LynxVISION can be used to manage the optical
network, the server must be started.
To start the LynxVISION server:

From the Start menu of the server, select Programs | LynxVISION |

Start LynxVISION.
A command window is displayed. Wait until the following message
appears:
LynxVISION Server modules started successfully.
Please connect your client to the web server on port: 9090.

NOTE:
Port 1099 must be available prior to launching the LynxVision server
application.
Starting the server may take a few minutes.

Once this message appears, the LynxVISION server is up and running and
clients can now connect to the server.
NOTE:
When the user logs on to LynxVISION for the first time, the LightLEADERs in the
network are not automatically discovered because the Discovery settings have not
yet been configured. In addition, unless the customers license is entered,
LynxVision will not manage more than 4 LightLEADERS. Therefore, the
Administrator should first enter License information as detailed on page 35, and
afterwards configure the Discovery settings, as described in the Discovery
Configuration section in Administering LynxVISION on page 39.

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

Shutting Down the LynxVISION

Server
Shutting down LynxVISION server is required in rare cases when LynxVISION
maintenance operations are required.
Only an operator with administrator privileges may shut down the server.
NOTE:
After the server is shut down, the clients cannot perform any operations. The
LightLEADER devices continue to operate however.

To shut down the server:

1

From the Start menu, select Programs | LynxVISION | Shutdown

LynxVISION.
The Shutdown LynxVISION Server window containing the default host
name is displayed.

Figure 7: Shutdown LynxVISION Server Window

Enter an administrator user name and password, and click OK.

Wait for a message indicating that the server has shutdown.

17

18

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

Figure 8: Shutdown Status Window

Click OK.

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

Starting the LynxVISION Client

The LynxVISION client is a Java applet stored on the server.
The client application provides the operator with a GUI for the management of the
LightLEADERs and the protected services carried by them.
To start the LynxVISION client:
1

Open a Web browser.

Enter the LynxVISION server IP address and port number 9090 in the
format: http://<server_ip>:9090 and press Enter to display the Login
window, shown below. DO NOT use the http://LOCALHOST:9090
format in the client window.

Figure 9: Login Window

Enter your user name and password.

By default, only one user with administrative privileges is defined. The
default administrators user name is admin, and the default password is

19

20

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

admin. The user admin can never be deleted.

Note:
After you enter the client application using the default password, it is
recommended to change this password for security reasons.
For instructions on how to change passwords, refer to the Changing Passwords
section in Chapter 4, Security Management on page 28.

Click the Login button.

The client application is downloaded to the computer and the Main

window Topology window is displayed, as shown in Figure 1:
LightLEADER Protection System on page 4.
Note:
The first time the client is run on a computer, startup may take a few minutes
depending on the bandwidth of the communication link between Client and
Server. Subsequent executions are faster.

Installing JRE 1.5

In case JRE 1.5 is not installed on the computer on which the Client is started for the
first time, an automatic download process is started.
The following window is displayed:

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

Choose Yes to display the following window:

Choose to accept the license agreement terms and click Next to display the following:

Choose the Setup Type and click Next to complete the installation. The LynxVISION
client now opens and the Main window is displayed.

21

22

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

The Main Window

LynxVISION client opens with the Main window as shown below in Figure 10.
The Main window contains the following areas:

Main Menu Bar contains the menus that enable you to

perform various system wide and GUI related
operations.

Toolbar menu contains shortcuts for functions relevant

for the window that appears within the main frame.

LightLEADER Devices Tree is a tree-structured list of all

installed LightLEADER devices and submaps. Using this
tree, you can add or remove LightLEADERs and submaps
and perform operations on them, such as APS configuration,
fault management, performance monitoring, etc.

APS Groups Tree is a tree-structured list of all APS

Groups. Using this tree, you can remove APS Groups and
perform operations on them, such as configuration and
monitoring.

Main frame, by default, holds the Map view that

provides a graphic representation of the various
LightLEADERs installed in the system and the APS
groups between them. Background graphical maps may
be associated with a Map view.

Current alarm Count is a graph that shows the number of

current critical, major, and minor alarms as a Columns chart
(hovering over a column displays the exact number of
alarms). The display sorts the alarms according to whether
they are Acknowledged or UnAcknowledged. Doubleclicking the graph displays the Current Alarms window (see
page 79, Displaying Logs).

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide
APS Group

Submap

Device Map

LightLEADER
Devices Tree

Submap Tree
APS Group Tree

Current Alarms
Graph

Status Bar
Figure 10: Main Window
Discovery in Progress Icon

When LightLEADERs are installed in the optical network, their system names and IP
addresses are automatically displayed in the Tree and map. When alarm conditions
occur, the LED of the affected network elements and their icons in the Device Tree are
colored according to the severity of the alarm. Sub-map icons are colored according to
the most severe alarm that occurred in any element associated with the sub-map.
By double clicking on a device icon, the device view window is opened displaying a
complete graphical representation of the front view of a LightLEADER system. The
Device View enables the operator to monitor and configure the resources of the
LightLEADER. For more information on the Device View function, refer to Using
Device View to Manage a LightLEADER Device, page 57.
By double clicking on an APS Group icon on the APS Group Tree or on a line

23

Device Icon

24

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

connecting two LightLEADER, the APS Group monitoring window is opened,

displaying a complete graphical representation of the APS group, and the optical
connectivity through the managed network. The APS group monitoring enables the
operator to monitor the state of the service, and links, and configure the APS group. For
more information, see Managing an APS Group, page 119.

7BChapter 3
Starting and Shutting Down the LynxVISION Server and Client
LynxVision EMS User Guide

Exiting the LynxVISION Client

You can exit the LynxVISION client application by clicking the Close button
at the
top right of the Topology window. Close the corresponding Explorer window when
prompted.

25

26

8BChapter 4
Security Management
LynxVision EMS User Guide

Chapter 4

Security Management
About This Chapter
This chapter describes how security is enforced in LynxVISION. It describes the
various user profiles and the user-management functions, such as adding, deleting or
modifying user details.
This chapter contains the following sections:

User Profiles, page 27, describes the user profiles in

LynxVISION.

Changing Passwords, page 28, describes how to

change your own password.

Managing Users, page 29, describes how to add a new

user, modify a user's details and delete a user.

Target Audience: The User Profiles and Changing Passwords sections should be read
by all users. The Managing Users section should be read by an Administrator.

8BChapter 4
Security Management
LynxVision EMS User Guide

User Profiles
LynxVISION provides three types of users, who have various security profiles.

User: Basic users who can only view the configuration

and state of the LightLEADERs, services and the
LynxVISION application itself without the ability to
modify them.

Privileged: User who can both view and change

configuration parameters, but cannot perform various
administrative functions, such as creating new users.

Administrator: User who can perform all functions.

27

28

8BChapter 4
Security Management
LynxVision EMS User Guide

Changing Your Password

LynxVISION provides you with the ability to change your own password.
To change your password:
1

Select Change Password from the Security menu to display the

Change Password window:

Figure 11: Change Password Window

Enter the old password and enter the new password twice.

Click OK to save the new password. A notification is displayed stating

that the password has been changed successfully.

8BChapter 4
Security Management
LynxVision EMS User Guide

Managing Users
The system administrator can add users to the system, which are shown in a User tree,
and assign them user profiles and passwords. User profiles specify the type of activities
permitted to a user, as described in the User Profiles section on page 27.
To add a new user:
1

Select Users Management from the Security menu to display the Users
Management window, as shown below:

Figure 12: Users Management Window

Click the Add button to display an empty Users Management window:

29

30

8BChapter 4
Security Management
LynxVision EMS User Guide

Fill in the fields, as follows:

Field Name

Instructions

User Name

Assign a user name.

Password

Enter the initial password for this user in the Password field and in
the Confirm Password field. As long as these two are not identical
Confirm pattern is colored in red.

Expiration Date

Enter the expiration date up to which the user can log in to the
system by clicking the browse button

User Never Expires

When this is checked, the user can always log on to the system,
meaning that his/her permission to log on to LynxVISION never
expires.

Profile

Select one of the available user profiles:

8BChapter 4
Security Management
LynxVision EMS User Guide

Administrator: User who can perform all functions.

Privileged: User who can both view and change configuration
parameters, but cannot perform various administrative functions,
such as creating new users.
User: Basic user who can view configuration parameters, but cannot
modify them.
General Info Area

Enter the user details in these fields.

First Name: The user's first name.
Last Name: The User's last name.
Phone: Click the adjacent browse button
number information in the dialog box:

and enter phone

Figure 13: Phone Number Window

Email: The user's email. Alarms will be send to this address - see
Send mail on alarm below.
Job Title: The user's job title.
Remark: Any remark pertaining to the user.
Send mail on alarm: specify the severity of alarm for which you
want to receive an email notification. The user must have an email
address defined (see field above); an SMTP server must also be
defined (for details on configuring an SMTP server refer to SMTP
Server Parameters, page 38.

Click Apply for the new user to take effect. The new user is added to
the User tree under Admin.

31

32

8BChapter 4
Security Management
LynxVision EMS User Guide

NOTE:
Incorrectly entered information is highlighted in red.

To modify a user's details:

1

Select Users Management from the Security menu to display the

Users Management window.

Select the user whose details you want to modify in the User tree and
change his details in the Users Management window.

Click the Apply button to save the new information.

To Modify a user's password:

1

Select Change Password from the Security menu to display the

Change Password window:

8BChapter 4
Security Management
LynxVision EMS User Guide

Type the Old Password and in the Password box, type the new
password.

In the Confirm Password, type the new password again and click OK.

To delete a user:
1

Select Users Management from the Security menu to display the

Users Management window.

Select the user you want to delete and click the Delete button.

A confirmation message is displayed. Click OK to delete the user.

33

34

9BChapter 5
Administering LynxVISION
LynxVision EMS User Guide

Chapter 5

Administering LynxVISION
About This Chapter
This chapter describes the various administrative tasks that the LynxVISION system
administrator can perform.
This chapter contains the following sections:

Entering License Information, page 35, describes

how to enter the license information.

Setting System Variables, page 36, describes how to

set global system variables, such as the polling rate,
system commit policy and which severity of alarms
emit sounds.

Discovery Configuration, page 39, describes how to

define the IP network on which the LynxVISION Auto
Discovery process runs.

Target Audience: This chapter should be read by an Administrator.

9BChapter 5
Administering LynxVISION
LynxVision EMS User Guide

35

Entering License Information

The first action that the system administrator must perform is to enter the customer
license information. If the customer license information is not entered, the system will
manage a maximum of four LightLEADERs in the network.
To enter license information:
1

From the Admin menu, select NMS Licensing to display the NMS
Licensing window. The maximum number of LightLEADERs and
services that are supported without entering a license key is displayed,
as shown in the figure below.

Figure 14: NMS Licensing Window

Enter the license key and click Ok.

Wait for the message that acknowledges that the license was accepted. When
the license is accepted, the number of LightLEADERs that LynxVISION can
now manage, according to the license key that was entered, is shown, and will
continue to be shown, whenever this window is displayed.

36

9BChapter 5
Administering LynxVISION
LynxVision EMS User Guide

Setting System Variables

You use the Admin menu to set global system variables:

The following global system variables can be set by the system administrator using the
Admin menu:

Auto Commit: When the checkbox is selected, as

shown below, configuration changes are automatically
saved to the non-volatile memory (startup
configuration file) on the device. Otherwise,
configuration changes are saved to the volatile memory
on the device (running configuration file) and lost
when the device is shut down or restarted. When you
want to test your configuration settings before saving
them, disable Auto Commit.

Figure 15: Enable Auto Commit Window

When Auto Commit is disabled and you decide to save these settings,
you must explicitly save them to non-volatile memory for each device

9BChapter 5
Administering LynxVISION
LynxVision EMS User Guide

separately. This is done by right-clicking each device in Map view and

selecting Commit.

Polling Rates: Specifies how often LynxVISION polls

LightLEADERs to capture changes that were not
discovered due to trap loss. To change the default
polling rate, which is every 30 seconds, enter the new
interval in the window, shown below:

Figure 16: Set Poll Interval Window

You cannot enter a number smaller then 30 seconds, because this might
cause an undesirable load on the network, when a large number of
LightLEADERs is being managed.

Alarm Indication Configuration: Specifies the

severity (minor, major or critical) at which alarms emit
an audible sound, on all open clients:

Figure 17: Alarm Indication Configuration Window

For a description of these alarm levels, refer to the Alarms section in

Fault Management on page 75.

Server Trap Community: Defines the notification

message authentication pattern sent by the device

37

38

9BChapter 5
Administering LynxVISION
LynxVision EMS User Guide

(slave) to the server. The default community string is

set to public as shown below:

Figure 18: Server Trap Community window

SMTP Server Parameters: Specifies the name or

address of the server from which the user wants to
receive an alarm notification email. When the
Authentication Required check box is selected, the user
name and password as configured on the SMTP server
must be entered.

Figure 19: SMTP Server Parameters window

9BChapter 5
Administering LynxVISION
LynxVision EMS User Guide

Discovery Configuration
The Discovery Configuration window enables you to define the IP networks that are
scanned for LightLEADERs, as described in the Auto Discovery Process section in
Managing LightLEADERs on page 44. You can define that the process only scans the
server's local IP network, or you can define any group of IP networks or sections of IP
networks. In addition, you can further refine your definition of the IP networks by
specifying specific SNMP communities.

Discover Now: Choosing the Discover Now command

will start an immediate discovery as specified in the
Discovery configuration Window. The Discovery in
Progress icon
is automatically activated during the
Discovery process and will remain so until it is
completed.

Deleted devices list: This is the list of devices that

were manually removed from the list of devices
managed by LynxVISION. The deleted devices will
not be discovered during the discovery process. A
deleted device needs to be added manually in order to
be managed again by the EMS.

To define the IP network(s) which the Auto

Discovery process scans:
1 From the Admin menu, select the Discovery Configuration option to

display the Discovery Configuration window, as shown below:

39

40

9BChapter 5
Administering LynxVISION
LynxVision EMS User Guide

Parameter
block

Configured
Parameters
Display

Parameter
Configuration
Fields

Figure 20: Discovery Configuration Window

2 Enter information in the Parameter block, as follows:

Rediscovery
Interval

Frequency at which the Auto Discovery process will run (when the Auto
Discovery checkbox is selected) in hours, minutes and seconds.

Auto Discovery

Select the checkbox for this process to run automatically at the frequency set in
the Discovery Interval field.

Discover LocalNet

Select this checkbox to run the Auto Discovery process on the server's local IP
network.

3 Enter information in the IP Address Workspace, as follows:

Entire Network

Select this checkbox to specify that the entire IP network is to be scanned. When
this item is checked, the Start IP and End IP are grayed out.

Set of Nodes

Select this checkbox to determine that only a certain range of the IP addresses on
a specified sub-net is scanned for new LightLEADERs

9BChapter 5
Administering LynxVISION
LynxVision EMS User Guide

41

IP Address

IP address of the IP network that is to be included in the Auto Discovery process

NetMask

Subnet mask of the IP network that is scanned

Start IP

When Set of Nodes is checked, defines the IP address that the scan begins from
(must be within the network IP addresses)

End IP

When Set of Nodes is checked, defines the IP address that the scan ends with
(must be within the network IP addresses)

Read community

SNMP read community, which must be identically configured in LightLEADER

devices in order to be managed

Write
Community

SNMP write community, which must be identically configured in LightLEADER

devices in order to be managed.

Click the Add button to add this IP network address or set of nodes to
the IP Address Table. The Auto Discovery process scans all the IP
networks or segments specified in the IP Address Table.

Click the Apply button to save the changes.

To delete a network on which the Auto Discovery

process runs:
1

Select the Discovery Configuration option from the Admin menu to

display the Discovery Configuration window, as shown in Figure 20.

Highlight the row to be deleted in the IP Address Table.

Click the Delete button. This IP address is deleted from the IP Address Table.

Click the Apply button to save the change.

To modify a network on which the Auto Discovery

process runs:
1

Select the Discovery Configuration option from the Admin menu to

display the Discovery Configuration window, as shown in Figure 20.

Highlight the IP address to be modified in the IP Address Table. It then

appears in the IP Address Workspace.

Modify the IP address in the IP Address Workspace and click the

Modify button. The updated IP address then appears in the IP Address
Table.

42

9BChapter 5
Administering LynxVISION
LynxVision EMS User Guide

Click Apply to save the changes.

Note: LightLEADERs that are already managed by the LynxVISION
will not be deleted when deleting their range from the discovery
configuration table. It will only prevent the auto discovery from
running on this range.

To manually launch the Discovery process:

Choose the Discover Now command from the Admin

is displayed at the bottom of the
menu. An icon
window which indicates that the process is running.

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Chapter 6

Managing LightLEADERs
About This Chapter
This chapter describes how to manage LightLEADERs in the LynxVISION system.
This chapter contains the following sections:

Adding a LightLEADER, page 44, describes two

methods for adding a LightLEADER: running the Auto
Discovery process or adding LightLEADERs manually
to the Topology tree.

Creating a Submap, page 48, describes how to create

a group of LightLEADERs.

Configuring Background Images, page 52, describes

how to associate a graphical file with a map of
LightLEADERs.

LightLEADER Operations, page 54, describes

operations that can be performed on a LightLEADER.

Target Audience: All users should read this chapter although configuration operations
can be performed only by Privileged users and Administrators.

43

44

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Adding a LightLEADER
In order to configure and monitor APSs and APS Groups, the LightLEADER must first
be added to the LynxVISION system. All LightLEADERs, which are connected to the
EMS via IP network, can be added to the Topology tree and Map view in one of the
following ways:

Auto Discovery Process, described below.

Adding a LightLEADER Manually, described on page 45.

Auto Discovery Process

The Auto Discovery process scans the defined IP networks in search of LightLEADERs
that are accessible through the IP network. It adds any LightLEADER that it finds to the
Topology tree and to the Map view.
The Auto Discovery process must be initiated manually the first time that the
LynxVISION server is launched after initial installation. Before you run the process,
you must define the IP network(s) upon which it will run. After this preliminary run, it
scans the network, by default, every five hours (this frequency can be changed).
To run the Auto Discovery process:
1

Log on to the system as an administrator, as described in the Starting

the LynxVISION Client section in Starting and Shutting Down the
LynxVISION Server and Client on page 19.

Select Discovery Configuration from the Admin menu, which displays

the Discovery Configuration window shown in Figure 20.

Define the IP network and other parameters, as described in the

Discovery Configuration section in Administering LynxVISION on
page 39.

Select the Auto Discover check box. The

icon is displayed at the
bottom of the window until the process is completed.

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Adding a LightLEADER Manually

After you connect a LightLEADER to the network, you can add it manually.
Manually add a LightLEADER in the following cases:

To save time: For instance, if only one LightLEADER

was connected since the last time the Auto Discovery
process was run, it may be faster to add it manually.

A LightLEADER was previously deleted from

LynxVISION: If it is not added again, the Auto
Discovery process will ignore it.

This process is described below.

To manually add a LightLEADER:
1

Right-click the root branch or a submap in the LightLEADER Devices

tree,
- OR Right-click anywhere on the Map view to display the right-click menu,
as shown below:

Figure 21: Map Menu

Select the Add LightLEADER option and enter the IP address of the
LightLEADER to be added in the IP Address field as in the following
window:

45

46

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Figure 22: Add LightLEADER Window

Modify the read and write SNMP community strings in the Read
Community and Write Community fields, respectively. When the IP
address of a new LightLEADER is within one of the ranges already
defined in Discovery Configuration, the identical community strings
must be configured.

Click Ok to add the LightLEADER. A confirmation message is displayed.

The new network element appears in the LightLEADER Devices tree
and Map view, within a minute or so, like this:

LightLEADER
Devices Tree

Note that the IP address and System Name of the LightLEADER is

displayed in the Map view along with the LightLEADER icon.
5

Drag the network element to the desired location on the background

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

map. When communication with the LightLEADER is established, the

LightLEADER icon in the Map view turns from gray to green, yellow,
orange, or red, according to the status of the LightLEADER, as
described in the Color Code section in Fault Management on page 78.
6

After all LightLEADERs have been discovered and placed in their

locations, save the map settings to the server for future use by pressing
in the Toolbar. All other clients will then see the
the Save Map icon
same layout in the Map view.

For instructions on how to connect a pair of LightLEADERs to form an APS Group,

refer to the Adding an APS Group section in Managing an APS Group on page 122.

47

48

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Creating a Submap
A submap is a container of LightLEADERs created for the purpose of simplifying
management. For further details, refer to the Background Maps section in Configuring
Background Images, page 52.
A background image can be associated with a submap.
To add a submap and associate a background image to it:
1

Select the branch in the LightLEADER Devices tree representing either

the whole group of LightLEADERs or a submap of them and
right-click,
- OR Right-click anywhere on the main workspace. The Map menu is
displayed.

Figure 23: Map Menu

Select the Add Submap option to display the Add Submap window,
shown below. Enter the name of the submap in the Map Name field,
select the parent map (larger geographical area of the optical network)
from the Parent Map list and browse to the image file in the
Background Image field.

Figure 24: Add Submap Window

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Click Ok to create the submap and associate a background map to it.

The submap icon now appears in the Map view even though the
submap is still empty.

To move a LightLEADER into a submap:

1

Right-click the LightLEADER to be moved to the submap, either in the

LightLEADER Devices tree or in the Map view, to display the
LightLEADER menu:

Figure 25: LightLEADER Menu

Click Move LightLEADER and select the submap from the list of
submaps that is displayed, as shown below:

Figure 26: Move LightLEADER Window

The LightLEADER is then moved to the submap. The LightLEADER

disappears from the originating Map view. To view it, you must click
the submap on the parent map or in the Tree.

49

50

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

When a LightLEADER is moved into a submap, the name of the submap is displayed in
the LightLEADER Devices part of the Topology tree. For instance, in the figure below,
the LightLEADER with the IP address 10.130.0.53 was moved into the submap New
York.

Figure 27: LightLEADER in a Submap in the LightLEADER Devices Tree

When an APS Group is composed of two LightLEADERs that are located on two
different submaps, the name of the APS Group appears twice in the APS Groups part of
the Topology tree (see Monitoring an APS Group, page 131). In this example, since this
LightLEADER is part of the APS Group named Bank of America, the Bank of America
APS Group appears once as an independent APS Group and once under the submap
New York, as shown below:

Figure 28: APS Group Split Between Two Submaps

It is possible for the two LightLEADERs which comprise a single APS Group, to be
part of two different submaps. In this case, the LightLEADER within the submap which
is not displayed in the Map view, has a white arrow on it, as shown below. To open the
submap, double-click the LightLEADER or right-click to open the menu:

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

White arrow indicates

that LightLEADER is
located in another
map.

Right-click opens
the map

Figure 29: LightLEADER Within Submap

51

52

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Configuring Background Images

The background image of the Map view can be replaced in order to enhance the
visualization of the topology and deployment scheme of LightLEADERs across the
optical network.
You can use images from the set of files stored on the server in the mapbackgrounds
folder where the LynxVISION software is installed on the server (using the default
installation path c:\program files\lynxvision\ mapbackgrounds).
To add an image to the list of available image files, simply place the image file in the
folder.
To change a background map:
1

Right-click the root of the LightLEADER Devices tree or a submap.

- OR Right-click the Map view.
The Map menu is displayed, as shown below:

Figure 30: Map Menu

Select the Change Background Image option to display the Change

Background Image window:

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Browse and select an image file (.bmp or .jpg) containing the desired
background map or enter its full path and name in the Background
Image field.

Click OK to associate the graphic file with the submap.

To delete a submap:
1

Move all active devices in the submap to a different submap or to the

main topology window.

Right click the Submap to be deleted, either in the LightLEADER

Devices Tree or in the Map View and choose Delete Submap. The
submap will be deleted.

53

54

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

LightLEADER Operations
Right-clicking a LightLEADER displays the LightLEADER menu:

Figure 31: LightLEADER Menu

The following operations can be performed:

Fault: Enables you to open a Current Alarm Log, an

Alarm Log, and an Event Log, related to this
LightLEADER. For further information, refer to Fault
Management, page 75.

APS: Enables you to configure and monitor an APS.

For further information, refer to Managing an APS on
page 112.
NOTE:
The Configuration option is only available to users with at least Privileged
security level permissions.

APS Groups: Enables you to add, configure, monitor

or delete APS Groups to which this LightLEADER
belongs. For further information, refer to Managing an
APS Group on page 119.

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

NOTE:
Add, Configure and Delete options are only available to users with at least
Privileged security level permissions.

Tools: Enables the user to open a MIB browser or a

Telnet session to the device. For further information,
refer to page 144, Tools.

Commit: Relevant only when the auto-commit option

is disabled. Enables you to save changes made into the
device in non-volatile memory. For further
information, refer to page 34 Administering
LynxVISION.

Set Factory Defaults: restores all configurations to

default state as set by the manufacturer. Note: This
operation may disconnect LightLEADER device from
the server, since it resets the its IP gateway
configuration.

System Information: displays the description, SNMP

object ID (unique identifier per chassis type) and Up
Time of the management card, as well as the Contact,
System Name and Location. The last three items can
be altered by the user.

SNMP: enables defining the Community and Trap

Destinations:

Community: an information window that displays the

Read and Write community string as they were
configured in the Discovery Configuration window, or
the Add LightLEADER window.

Trap Destination: displays the IP address of the SNMP

manager to which the LightLEADER sends SNMP traps (see
Fault Management, page 75).

Move LightLEADER: Enables you to move the

LightLEADER to a submap, as described in the section

Creating a Submap on
page 48.

55

56

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Delete LightLEADER: Enables you to delete a

LightLEADER, which removes this element from the
scope of LynxVISION. This should be done in cases
where the LightLEADER IP address has changed, the
LightLEADER was physically removed and so on.
After a LightLEADER is deleted, its IP address will
not be discovered again by the Auto Discovery process,
and the only way to re-insert it into LynxVISION is by
adding it manually as described in the Adding a
LightLEADER Manually section in Managing
LightLEADERs on page 45. APS groups composed of
the deleted LightLEADER will also be deleted.

Device View: The user-friendly interface enables

monitoring, configuring and filtering the operation of
each component: port, APS, the entire device, and
more.

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Using Device View to Manage a

LightLEADER Device
Using Device View, it is possible to manage an entire LightLEADER device. Device
view provides a visual representation of the LightLEADER system, allowing you to
quickly see the system inventory (cards) and states. This means that you can configure,
monitor, or display information for a device and its ports, cards, power supply, etc.
Device View provides an intuitive way of controlling and monitoring these functions.
By allowing you to view the functions as part of an objective device and by providing a
graphical representation of the device, Device View contributes to your overall control
and monitoring of the system.
This chapter shows you how to use Device View to do the following:
Configure, provision, and monitor ports.
Filter Event and Alarm logs of each element (chassis, port, or card)
Control the LightLEADER as described in various sections of this manual,
including Configuring an APS on page 117.
Display performance history of ports.
For the LightLEADER 4000 family, you can do the following additional operations:
Configure and reset cards (APS , Controller and Power Supply cards).
Display information about a card's firmware.
Set the Expected card for a slot.
Display files of each card and swap SW image between banks.

57

58

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

The 3000 and 4000 LightLEADER

Device Families
LightLEADERs belong to either the 3000 or 4000 device families. The type of
LightLEADER affects the scope of operations that LynxVISION can perform with the
LightLEADER.
LightLEADERs belonging to the 3000 family have a chassis that includes a fixed
electronic configuration - there are no card slots and so no ability to expand or change
the configuration. LynxVISION can monitor performance, alarms for ports, etc., and
can perform certain operations such as provisioning and configuration.
LightLEADERs belonging to the 4000 family have a chassis with slots that enable
cards to be added or exchanged. LynxVISION can perform additional operations such
as swapping files between a backup bank and an active bank.

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Displaying Device View

To display Device View
In Map view, or in the Devices tree, double-click a device
icon.
- OR In Map view, or in the Device tree, right-click a device and
choose Device View:

A graphical display of the device chassis is displayed. The display

for the 3000 and 4000 device families differ and can be found in
their respective sections below.

59

60

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Device View Display for the 4000

Device Family
Upon displaying Device View for a 4000 Device family, a display showing a chassis
like the following appears:

Figure 32: Device View - Chassis of a 4000 LightLEADER Device

Hovering over the different elements (chassis, slot, card, APS, port) of the device
displays a blue frame around the element and the tool tip shows the element name:

Figure 33: Hovering Over an Element on the Chassis

In case of an alarm on any element of the Device View, a colored frame is displayed
around the failed item (note the red frame around the port in Slot 2 in the figure above).
The frame is colored according to the alarm severity.
Disabled elements are displayed with a gray frame.

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Device View LEDs

Device View displays the LEDs to match their status on the device. See LED
description in the LightLEADER User Manual.

LightLEADER 4000 Device Family Slots

As explained above, LightLEADERs belonging to the 4000 device family have slots
whose cards can be exchanged. There are four different enclosures of the
LightLEADER 4000:

AC front access enclosure

AC rear access enclosure

DC front access enclosure

DC rear access enclosure

The DC enclosures
The five leftmost slots (1-5) are of equal size and width and are all 1 U high and 72
mm wide. The rightmost slot is divided into two horizontal slots, each one-half U
high and 72 mm wide:

APS cards can be inserted into slots 1 through 5.

One management card can be inserted into slot 4 or 5.

One or two power cards can be inserted into slots 6

(bottom rightmost slot) and/or 7 (upper rightmost slot).

The AC enclosures
All six slots are equal in size and are 1 U high and 72 mm wide:

APS cards can be inserted into slots 1 through 4.

One management card can be inserted into slot 4 or 5.

One or two power cards can be inserted into slots 5

and/or 6.

61

62

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Auto-Config, Expected, and Actual Configuration

Device view enables the operator to define for each slot its expected configuration. To
do this, the operator can place a slot in auto config mode (as explained below) or
specify the exact card type that should be in the slot:
Auto-Config: When a slot is defined in auto-config state, the LightLEADER
system will allow any card to be inserted into the slot. Once a card is inserted, it
will become the expected card for this slot. A slot may be placed in auto-config
state only when it holds no card.
Specific type: Enables you to specify the exact card that should be inserted into
the slot. The LightLEADER system will then verify that the correct cards have
been inserted. If the actual card installed is not as expected, then a mismatch
alarm is raised, the card is not configured and none of the cards resources are
available for use.
This feature is extremely useful for operators when planning and installation are
completed by different people. It helps to prevent installation mistakes, such as
installing the wrong type of module in the wrong system and/or slot.
The table below the chassis gives information about each slot in the chassis:
Number

Represents the slot number from left to right on the chassis.

Status

Refers to the status of the card currently inserted in the slot.

Status can be any of the following:
Initializing, Ready, Failure, No Communication, Not Applicable, Power Out (for power
supply card only)

Actual

The type of card that is currently in the slot.

Expected

The type of card that is supposed to be in the slot.

In case of a mismatch between the Actual and Expected card types, an alarm is raised,
the Status is set to Not Applicable, and the slot is pictured as empty with a red frame.
An APS may occupy one or three slots. In case of a three slot APS (such as APS4403),
it can be set only to the two leftmost slots of the chassis.

Setting the Expected Model Type

Setting the expected model type of each slot is done through the slot menu that is
accessible when hovering over an empty slot and right clicking as explained on page

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

68, or when hovering above a card and choosing slot->expected Module from the
right click menu.
Note that changing the Expected of a slot is prohibited if it has a provisioned APS
function. Instead, the Actual and Expected fields of the table display the slot number
(1,2,3) that is occupied by the APS (for example APS4403#1). Note that in cards that
are larger than one slot, configuration of the expected card in the slot should be done
only on the leftmost slot.
See Figure 32: Device View - Chassis of a 4000 LightLEADER Device, page 60 above
(the figure does not have an APS that occupies more than one slot).

Configuring and Monitoring Cards

In the 4000 Device View display, you can configure and monitor individual cards by
simply right clicking a card slot on the graphical device chassis and choosing an option
as shown in the following sections.

Card Details
To display information about a card:
1

On the chassis, right-click the card slot and choose Module, then
Details:

The following information about the current card is displayed:

63

64

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Figure 34: Card Details

Displaying Information about Card Files

You can also display information about a card's firmware. Each card holds two "banks"
of firmware, the Current Bank that the card was booted from, and a Boot Bank from
which the card will be booted in the next reset. By holding a Boot Bank firmware
version in reserve, you can perform upgrades to the card without causing system
interruptions.
To display information about a card's firmware:
1

On the chassis, right-click the card view and choose Module, then Files:

The following information is displayed:

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Figure 35: Card Files and Swap Button

The card files display various according to the type of card: for
example, unlike an APS, a controller card displays running and startup
config files.

Swapping a Card's Firmware

The device view allows the operator to change the boot bank of the device. Changing
the boot bank of the device is required when the current bank is holding an older
software image.
To change the boot bank
In the Card Files display (see the above figure), click the Swap button.
This changes the Boot Bank and on the next reset it will become the
Current Bank.

Card Reset for 4000 Family Devices

You can also reset a card. The card will boot from the Boot Bank that was set in the
Card Files dialog.
To reset a card:
1

On the chassis, right-click the card view and choose Module, then
Reset:

65

66

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

A confirmation message is displayed.

NOTE:
if you reset a controller card the Device View will close automatically as the
communication to the LightLEADER is lost during controller reset.

Resetting All Cards for LightLEADERs

in the 4000 Device Families
You can also reset all the cards of a LightLEADER in the 4000 Device Family. The
cards will boot from the Boot Bank that is set by Card Files dialog:
To reset all cards:
1

Right-click the Chassis and choose Reset All.

A confirmation message is displayed, and the device view is closed, as
during reset the communication to the LightLEADER is lost.

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

67

Configuring and Monitoring Ports and APSs

By right-clicking an individual port, or group of ports (APS group) on the chassis, you
can display a menu that enables you to configure and monitor the item.

Configuring and Monitoring Ports

Right-clicking an individual port on the chassis displays this menu:

When the APS is disabled, you can provision and un-provision a certain port using the
Enable\Disable command.
You can set port properties such LOS & Degraded thresholds and monitoring for
degradation using the Port Properties dialog box.
You can get the Event\Alarm Log of this port only by selecting the Fault menu.
For further details, see Device View Display for the LightLEADER 3000, page 69.

Ports that Connect to a Client

For ports that connect to a client, you can monitor Service Error Seconds and Service
Degraded Seconds. Right click the port and in the Performance History menu, choose
the appropriate option as shown in the following figure:

68

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Figure 36: Performance History for a Service

Configuring and Monitoring an APS

By right-clicking an APS, and choosing the APS menu, you can display options for
monitoring and configuring the APS:

These options are discussed in Managing an APS page 112, and Fault Management,
page 75.

Expected Module for a Slot

You can set the Expected module for a slot by right clicking the slot and choosing Slot,
Expected Module:

This option is disabled whenever the APS or any of its ports is enabled. Choosing
Expected Module displays a list that you can select from:

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

Device View Display for the

LightLEADER 3000
Device View for a LightLEADER in the 3000 family displays the chassis as shown here:

Figure 37: Chassis Display for a 3000 Family Device

Hovering over the different elements (chassis, slot, card, APS, port) of the device
displays a blue frame around the element and the tool tip shows the element name
In case of an alarm on any element of the Device View (APS function or port), a
colored frame is displayed around the failed item. The frame is colored according to the
alarm severity
Disabled elements are displayed with a gray frame.

Controlling and Monitoring Ports

Right-clicking a port displays a menu for controlling and monitoring the port:

Figure 38: Device View Menu for Port

Port Properties, Power Monitoring, and performance history items appear in the menu

69

70

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

only for ports that have OPM (Optical Power Monitoring) Capabilities (such as the
working and protection)
When the APS is disabled, you can provision and un-provision a port using the
Enable\Disable command. Provisioning a port causes the LightLEADER to start
monitoring the port for failures and to start data collection for the performance
management.
Clicking Port Properties displays a dialog box in which you can view and change the
Thresholds of the port:

Figure 39: Port Thresholds dialog box

For Working and Protection ports, the Fault and Performance History options display
the following menus:

Figure 40: Performance History Menu

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

LL3000 Power Supply Operations

Hovering over the Power Supply on the chassis displays information about the element:

Right-clicking the Power Supply opens a menu that enables you to display information
about the Power Supply.
You can display information about the Power Supply by clicking on Details:

Figure 41: Power Supply Details

71

72

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

For DC power supplies, the operator can also provision (unprovision) the DC sensors to
enable (disable) monitoring of the input feeds.

Figure 42: Power Supply Options

Clicking DC Sensors allows you to set Alarms for the DC Sensors, enabling the alarm
will cause the LightLEADER to start monitoring the input power to the power supply.
In case a problem with the power feed is detected by the LightLEADER, an alarm will
be raised.

Figure 43: Power Supply DC Sensors Alarms

LL3000 Chassis Operations

By right-clicking the edge of the chassis, you can display a menu that enables
operations on the entire LightLEADER device:

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

73

Figure 44: Chassis Menu

Clicking System Information displays information about the LightLEADER, as

described in Managing LightLEADERs.
The SNMP, Tools, and Fault options display menus that are dealt with in their
respective chapters in this manual (for SNMP settings see Setting System Variables,
page 36; for Tools see MIB Browser and Telnet options in Tools, page 144; for Fault
options, see Fault Management, page 75).

Resetting a LightLEADER in the 3000 Device Family

To reset the firmware for a LightLEADER in the 3000 Device family, simply rightclick the chassis and click Reset:

Configuring and Monitoring an APS

By right-clicking an APS, you can display options for monitoring and configuring the APS:

74

10BChapter 6
Managing LightLEADERs
LynxVision EMS User Guide

These options are discussed in Managing an APS page 112, and Fault Management,
page 75.

11BChapter 7
Fault Management
LynxVision EMS User Guide

Chapter 7

Fault Management
About This Chapter
This chapter describes how to use LynxVISION fault management capabilities.
This chapter contains the following sections:

Overview, page 76, describes the type of event and

alarm logs available in LynxVISION.

Events Severity Levels, page 77, describes the various

severity levels of the LynxVISION events, as well as
their color codes.

Displaying Logs, page 79, describes how to display

the various types of logs.

Filtering Logs, page 81, describes how to filter logs

according to various criteria.

Acknowledging Alarms, page 86, describes how to

acknowledge an alarm.

Audio Indication Configuration, page 87, describes

how to define the level at which alarms become
audible.

Target Audience: All users should read this chapter.

75

76

11BChapter 7
Fault Management
LynxVision EMS User Guide

Overview
Fault management functionality enables the operator to manage failures in a complex
system comprised of the management system itself, the managed LightLEADERs and
protected services.
Each managed element is monitored for a failure status. Its status is accessible to the
user through a set of visual and audio indications, as well as a set of tables and logs.
LynxVISION monitors the status of network elements by receiving traps from them.
Traps are unsolicited messages that notify that events have occurred and raise alarms
that indicate faulty conditions. Examples of such events are LOS on the Working link,
power on the Working link falling below the degradation level and so on. When these
events occur, alarms may be raised (depending on the configuration of the system).
The LynxVISION application itself also creates alarms and notifications, such as the
discovery of a new LightLEADER (event), loss of communication to a LightLEADER
(alarm) and so on.
After a LightLEADER is added to LynxVISION, LynxVISION automatically registers
itself with the LightLEADER as one of the device's SNMP managers and starts
monitoring its traps. LynxVISION and the LightLEADERs include a special
mechanism that ensures that no trap information is lost.
LynxVISION provides the following logs that describe events and alarms that have
occurred in the system:

Event Log: A log describing all events, including

alarms, which have occurred in LynxVISION and in
the managed LightLEADERs.

Alarm Log: A log describing all alarms, currently

existing as well as historical, which have occurred in
LynxVISION and in the managed LightLEADERs.

Current Alarm Log: A table describing existing

failures (all alarms that have not been cleared ) in
LynxVISION and in the managed LightLEADERs.

Logs can be filtered according to the following criteria:

Event ID: Unique ID of the event or alarm.

11BChapter 7
Fault Management
LynxVision EMS User Guide

Time & Date: Event occurred between a specific start

Time & date and the end Time & date.

Severity Level: Severity of the event or alarm.

Source Path: LightLEADER or APS and the like on

which the event or alarm occurred.

Acknowledgment: Indicates whether the alarm has

been acknowledged (exists for the Current Alarms log
only).

NOTE:
To display the logs of a particular LightLEADER, right-click its icon in the Map
view or tree and select the Fault Management option. Only the events and
alarms for that network element are displayed.
To display the logs of a particular APS, right-click its view in the Device view
and select the Fault Management option. Only the events and alarms for that
APS are displayed.
To display the logs of a particular optical interface, right-click its view in the
Device view as described above.

Events Severity Levels

LynxVISION events and alarms have the following severity levels:

Critical: Traffic affecting failure, an example of such

an event (alarm) is client is not receiving a signal due
to the fact that both working and protection link
failed. Immediate corrective actions should be taken.

Major: An event has occurred that may lead to a

traffic affecting scenario, or prevents the system from
performing its functionality (although no traffic is
currently affected); an example of such an event
(alarm) is when a single link of an APS group fails.
Immediate corrective actions should be taken.

Minor: An event has occurred that does not affect

traffic, nor prevents the system from providing its full
functionality; however it requires the operator's
attention, and should be repaired as soon as possible.

77

78

11BChapter 7
Fault Management
LynxVision EMS User Guide

An example of such an event (alarm) is a degradation

threshold crossing event of one of the provisioned
ports.

Clear: An alarm has cleared.

Information Only: An event that does not require

attention, but is logged for informational and tracing
purposes; an example of such an event is port was
provisioned event.

Color Code
LightLEADERs and APS Groups in the Map view are colored according to the event
that has occurred on them and has raised the alarm. The color code for the alarms is:

Red: Critical

Orange: Major

Yellow: Minor

Green: Clear

White: Informational

11BChapter 7
Fault Management
LynxVision EMS User Guide

Displaying Logs
To display a log:
1 To view a specific type of log, select an option from the Fault
Management menu, as shown below:

Figure 45: Fault Management Menu

- OR Select a specific LightLEADER, right-click and choose

an option from the LightLEADER right-click menu, as
shown below:

Figure 46: LightLEADER Fault Management

-OR In Device view, right-click a port or card to display the

Fault menu.

79

80

11BChapter 7
Fault Management
LynxVision EMS User Guide

The selected log is displayed; an example of the event log is shown

below:

Figure 47: Event Log Window

If the Log was displayed by right-clicking a LightLEADER or by clicking a

port in Device view, the Log appears already filtered (see below, Filtering
Event Logs).

11BChapter 7
Fault Management
LynxVision EMS User Guide

Filtering Event Logs

You can determine which events are displayed in the Event Log according to specific
criteria that you define in the Events Filter dialog box.
To filter an Event Log:
1. Select the Event Log option from the Fault Management menu. The
Event Log window is displayed, as shown in Figure 47.
Each row in the log describes an event that has occurred and is
composed of the following information:

Event ID: Sequential number identifying the event.

Time & Date: Time and date of the event.

Severity: Severity of the event: Critical, Major, Minor, Clear

or Informational.

Description: Description of the event.

Source Path: Object on which the event occurred.

The color of each event is determined by its severity, as described in

the Color Code section on page 78.
The log can be sorted by column by clicking the column title. Clicking
the column title toggles between ascending and descending order.
2 Click the Filter button to display the following window:

81

82

11BChapter 7
Fault Management
LynxVision EMS User Guide

Figure 48: Events Filter Window

Enter information in the filter fields as required and click Ok. The
filtered list is displayed in the Event Log window.

11BChapter 7
Fault Management
LynxVision EMS User Guide

Filtering Alarm Logs

You can filter the alarms that are displayed in the Alarm Log or Current Alarms windows
according to criteria that you set in the Alarms Filter dialog box as described below.
To filter an Alarm Log:
1

Select the Alarm Log or Current Alarms Log from the Fault
Management menu. Depending on the log that you select, a window
containing that log is displayed. For example, if the Current Alarms
Log was selected, the Current Alarms window is displayed:

Figure 49: Current Alarms Window

Each row in the log describes an alarm that has occurred, or cleared,

83

84

11BChapter 7
Fault Management
LynxVision EMS User Guide

and contains the same columns as in the event log, shown in Figure 47
on page 80. In addition, the Alarm Log and the Current Alarm Log
contain the Ack column that specifies whether the alarm has been
acknowledged.
If an alarm is acknowledged, hovering on the Ack column shows the
user name of the person that acknowledged the alarm and the date and
time.
2

Click the Filter button to display the Alarms Filter window:

Figure 50: Alerts Filter Window

Enter information in the filter fields. Note that by selecting Ack you

11BChapter 7
Fault Management
LynxVision EMS User Guide

can choose to display either Unacknowledged or Acknowledged alarms

(the Ack filter is available only in current alarm log).
4

Click Apply to display the filtered alarm log or click OK to display the
filtered alarm log and exit the dialog box.

85

86

11BChapter 7
Fault Management
LynxVision EMS User Guide

Acknowledging Alarms
To acknowledge an alarm:
1

Select the Current Alarms option from the Fault Management menu.
The Current Alarms log is displayed.

In the log, highlight the alarm row(s) that you want to acknowledge and
click the Ack button.

11BChapter 7
Fault Management
LynxVision EMS User Guide

Audio Indication Configuration

Once a new alarm is discovered by the system, an audio indication on the open clients'
computers will start to sound, according to the criteria described in the Setting System
Variables section in Administering LynxVISION on page 36.
In addition, a bell icon

is displayed on the screens.

To turn off the alarm indication, click the bell icon. The alarm is turned off and the bell
icon disappears.

87

88

11BChapter 7
Fault Management
LynxVision EMS User Guide

Current Alarm Graph

At the bottom left-hand corner of the main screen (see Figure 10: Main Window, page
23) is a graph that displays the alarms current in system:

The graph shows the number of Acknowledged and UnAcknowledged alarms according
to whether they are Critical, Major, or Minor. Double-clicking the graph opens the
Current Alarms window (see Figure 49: Current Alarms Window, page 83).

11BChapter 7
Fault Management
LynxVision EMS User Guide

Email Notification
The administrator can specify that the system send an email notification to a user when
an alarm occurs. The severity of the alarm for which notification is received can also be
specified. For details, see Figure 12: Users Management Window, page 29.

89

90

12BChapter 8
File Operations
LynxVision EMS User Guide

Chapter 8

File Operations

About This Chapter

LynxVISION provides file management to and from LightLEADERs. Specifically, you
can download a new firmware version to a LightLEADER, or upload firmware from the
LightLEADER so that it can be stored or transferred to another LightLEADER device.
File operations are supported only for LightLEADERs that are part of the
LightLEADER 4000 family.
This chapter explains the following:

Setting up the TFTP Server, page 91

Downloading files to a LightLEADER, page 92

Uploading files from a LightLEADER, page 98

12BChapter 8
File Operations
LynxVision EMS User Guide

Setting Up the TFTP Server

Before you can Download/Upload files to/from a LightLEADER, you must start a
TFTP server. You must then set up a directory structure on the TFTP server with the
following hierarchical structure:

FTP Root

APS

SW Image

Controller

Config

SW Image

Files that you want to download to an APS must be first placed in the APS/SW Image
directory. Files that you want to download to a Controller card must be placed in either
the Controller/Config, or the Controller/SW Image directories.

91

92

12BChapter 8
File Operations
LynxVision EMS User Guide

Downloading Files to a LightLEADER

You can download a file to one or more LightLEADERs. For example, you can
download a file to a LightLEADER's APS cards or to a Controller card.
NOTE:
The downloaded files are placed in the card's backup bank and therefore
can be downloaded while the LightLEADER is operating. At the end of the
download operation you can swap the files from the backup and active banks.

To a download file to a LightLEADER, first make sure to place the file in the
appropriate directory on the TFTP server as described in the previous section, Setting
up the TFTP server.
To download a file:
1

On the File Operations menu, choose File Download:

The following dialog box appears:

12BChapter 8
File Operations
LynxVision EMS User Guide

Select the Card Type to which you are downloading, and the Operation

Click Next to advance to the following dialog box:

93

94

12BChapter 8
File Operations
LynxVision EMS User Guide

Select the Map where the LightLEADER(s) to which you are

downloading are located, and select the IP addresses of the
LightLEADERs to which you are downloading the files. Click the
Include button
list on the right.

to move the LightLEADER's to the download

You may repeat this operation to select more than one

LightLEADER as well as to select LightLEADERs from other
maps:

12BChapter 8
File Operations
LynxVision EMS User Guide

Press Next to advance to the next dialog box. Different

screens appear depending on the type of file and type
of card selected. If the card is an APS then the window
below is displayed; if it is a Management card, then
this window is sipped; if the file being downloaded is a
configuration file, a different window is displayed.

If you are downloading to an APS, you can view the

files and the cards to which you are downloading. You
can then choose to download the file to only some of
the cards by using the Selected checkbox, as shown in
the following figure:

95

96

12BChapter 8
File Operations
LynxVision EMS User Guide

Click Next to advance to the following dialog box:

Enter the IP of the TFTP Server and the full pathname of the file that
you are downloading. The pathname must correspond to the directory
structure described in section Setting Up the TFTP Server, page 91.

12BChapter 8
File Operations
LynxVision EMS User Guide

Click Next to advance to the following dialog box:

Click Download and wait until Bytes Transferred indicates that the file
has been downloaded.

10 The file is downloaded to the cards' Backup Banks. To swap to the

active bank, click the Swap and Reset button.

97

98

12BChapter 8
File Operations
LynxVision EMS User Guide

Uploading Files to a LightLEADER

You can upload afiles from a LightLEADER to the EMS.
To upload files:
1

On the File Operations menu, choose Upload; the following dialog box
is displayed:

Select the type of card from which you are uploading the files, and the
type of file that you want to upload: Running configuration, or Startup
configuration.

Click Next to display the following dialog box:

12BChapter 8
File Operations
LynxVision EMS User Guide

Select the map where the LightLEADER is located, and then select the
- you may
LightLEADER IP and press the Include button
repeat this operation to include more than one map and more than one
LightLEADER.

Click Next to display the following:

99

100

12BChapter 8
File Operations
LynxVision EMS User Guide

Click Upload and wait until the display indicates that the files have
been transferred (all bytes transferred).
The files are uploaded to the appropriate directory on the TFTP server
(see Setting Up the TFTP Server, page 91).

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Chapter 9

Performance Monitoring
About This Chapter
This chapter describes the various port performance monitoring options and contains
the following:

Time Based Samples, page 103, that monitor the

performance history of the port over a specific time
period.

Delta Power Samples, page 107, that record the

changes in signal properties and displays them as a
sharp drop or rise.

Error Seconds Table, page 109, that indicates the

amount of seconds the specific port was in a state of
LOS.

Degraded Seconds Table, page 110, that indicates the

amount of seconds the specific port was in a state of
degradation.

Target Audience: All users should read this chapter although the operations described
here can only be performed by Privileged users and Administrators.

101

102

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Overview
LynxVISIONs Performance monitoring tools allows you to monitor the performance
of the optical network and the QoS offered to the customers of the protected services.
LynxVISION periodically collects data from the managed LightLEADERs regarding
the power levels, state (FAIL, Degraded, OK), and role (active or backup) of each port.
It also connects data regarding the QoS each service received, indicating times where
the protected client did not receive a signal. Data is presented to the operator in graphs
and tables. By displaying a detailed chart for each individual port, you can quickly spot
problems in the network, monitor sudden power changes in real time, as well as monitor
performance over a longer period of time for a deeper analysis of reoccurring problems
and malfunctions.
The Performance Monitoring tool allows you to configure the ranges of values that will
be monitored, the power thresholds, and the sampling frequency.

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Performance History
You can monitor the performance of the optical power and error and degraded seconds
of a port over a specified time period. You can display the following types of
performance graphs or tables:

Time Based Samples

Delta Power Samples

Error Seconds Table

Degraded Seconds Table

You can also monitor the error and degraded seconds of a service (such as an APS).
To access Performance History:

In Device view, right click the port whose performance

you want to monitor, then click Performance History.
The following menu appears:

103

104

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Exporting to an Excel Spreadsheet

The graphs can also be exported as an Excel spreadsheet.
To export a graph to an Excel spreadsheet:

In any of the Graph windows, click on the Export

button at the bottom of the window. The graph is
exported to an Excel spreadsheet like the one in the
following figure:

Figure 51: Exporting a graph to an Excel spreadsheet

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Time Based Samples

The Time Based Samples screen allows you monitor the performance of a port over a
specific time period. You can configure the monitored time period according to the
current day (from midnight to present), last 24 hours, last week, or a user defined time
period. For periods of 24 hours or less, the port's performance is sampled every 5
minutes. For monitoring times greater than 24 hours, the port's performance is
monitored every 30 minutes - the sampling interval is indicated in the title of the
window (see the figure below).
The red and orange lines show the LOS and Degraded thresholds respectively. Vertical
lines show whether the port is currently in active (green) or backup (blue) state.

Figure 52: Performance Monitoring Time based samples

The thresholds for LOS and Degraded for a port can be set in Device View (see
Controlling and Monitoring Ports, page 67).
Because this is historic data, the data is not updated until the user clicks the Refresh
button.

105

106

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Zooming in
You can zoom in on a portion of the graph by simply depressing the left mouse button
and drawing a square over the area that you want to zoom in on (from left-top point to
right-bottom):

Figure 53: Zooming in

The area is magnified and displays finer time intervals. For Zooming out, use the
Refresh button.

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Delta Power Samples

The Delta Power Samples screen displays the changes in power for a port (Delta
Power), according to periodic sampling, and displays them as a sharp drop or rise in dB
as shown in the example below. The delta power helps identify sharp drops and rises in
power. This can be compared to thresholds for LOS and Degraded, as well as the actual
power (Sensor Value) which also appear on the graph.

Figure 54: Drops and rises in the delta power samples

You can configure the monitored time period according to the current day, last 24
hours, last week, or a user defined time period. In addition, as in the Time Based
Samples, you can zoom in a portion of the graph.

107

108

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Delta Power Settings

This option allows you to configure a new dBm level to be applied to all ports of a
specified device. This level determines how much delta power is needed to insert a new
record to the Delta Power table. Right-click a specific port in Device view and choose
Delta Power Settings - the following dialog box appears:

Figure 55: Delta Power Settings power supply status

The default value is 1.0 dBm. You can set it between 0.5 and 10.0 in steps of 0.5 dBm.
NOTE:
Although you open this dialog from one port, the new value will be applied to all
ports of this device.

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Error Seconds Table

The user predefines the dBm level that will be considered as the LOS threshold as
shown in Configuring an APS Group, page 142. The Error Seconds Table indicates the
amount of seconds the specific port was in a LOS state. The port is monitored
frequently and displays its findings according to the configured time period of: current
day, last 24 hours, last week, or a user defined time period.
The Start and End Date columns presents the actual period of time sampled. The
Seconds column presents the amount of seconds within the sampled time period that the
port was in a state of LOS. The Percent column calculates the percentage of time the
port was in a state of LOS within the sampled time period.

Figure 56: Error seconds table

109

110

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Degraded Seconds Table

The user predefines the dBm level that will be considered as the degraded threshold as
shown in Configuring an APS Group, page 142. The degraded Seconds Table indicates
the amount of seconds the specific port was in a state of degradation. The port is
monitored frequently and displays its findings according to the configured time period
of: current day, last 24 hours, last week, or a user defined time period.
The Start and End Date columns presents the actual period of time sampled. The
Seconds column presents the amount of seconds within the sampled time period, the
port was in a state of degraded. The Percent column calculates the percentage of time
the port was in a state of degraded within the sampled time period.

Figure 57: Degraded seconds table

13BChapter 9
Performance Monitoring
LynxVision EMS User Guide

Power Monitoring
Power Monitoring enables you to monitor the power through a port in real time. You
can set the time frame for which the port is monitored.
The following figure shows the power fluctuations, represented by the black Sensor line
as compared to the thresholds for LOS and Degradation (represented by the red and
yellow lines).

Figure 58: Power Monitoring Graph

111

112

14BChapter 10
Managing an APS
LynxVision EMS User Guide

Chapter 10

Managing an APS
About This Chapter
This chapter describes how to configure and monitor APSs. It contains the following
sections:

What Is an APS?, page 113, describes the structure of

an APS.

Monitoring an APS, page 115, describes how to

monitor an APS.

Configuring an APS, page 117, describes how to

configure an APS on a LightLEADER.

Target Audience: All users should read this chapter although the operations described
here are only allowed to Privileged users and Administrators.

14BChapter 10
Managing an APS
LynxVision EMS User Guide

What Is an APS?
The APS function facilitates transporting a service via more than one link. When the
Working transport entity fails, the Main signal is transported via the Protection link.
An APS function is implemented by a physical APS entity that includes the control
logic, monitoring logic and the physical interfaces (ports). APS entities are plug-in
cards (APS cards) in the LightLEADER 4000, and fixed elements in the LightLEADER
3000.
Important Note:
If the APS is single-ended (such as the APS4305), it can be configured separately
from the APS at the other end, as each end works independently of the other. If the
APS is a dual-ended (such as the APS4301), it is recommended to configure both
APSs at the same time through its APS Group (refer to the Adding an APS Group
section on page 122).

APS States
Each APS on a LightLEADER is either enabled or disabled. This is called its
provisioning status.
Every APS on a LightLEADER is either provisioned or not. When it is provisioned, it
can be placed in one (or more) of the following states:

Automatic: (Normal state) Signal is being transferred on the

Working link and will be switched to the Protection link if the
Working link fails.

Forced Protection: Signal has been forced to the Protection

link, irrespective of its state.

Forced Working: Signal has been forced to the Working link,

irrespective of its state.

Manual Switch to Protection: Signal has been switched to the

Protection link by the user, and will remain there, until one of the
following conditions has occurred: Protection link failure, or a
force to working command has been issued. The APS will
change its state in the previous two conditions when the user

113

114

14BChapter 10
Managing an APS
LynxVision EMS User Guide

issues a clear command (move to switch state), or to the forced

state if a force command has been issued.

Switched: Signal has been switched to the Protection

link.

These states are displayed in either the APS Group Monitoring or APS Monitoring
windows. The APS state can also be changed in these windows by clicking the
Enable/Disable button in the Monitoring window or by using the Command operation,
as described in the Commands section in Managing an APS Group on page 135.

14BChapter 10
Managing an APS
LynxVision EMS User Guide

Monitoring an APS
Each APS can be monitored separately through the APS Monitoring window. If an APS
is a part of an APS Group, it can be monitored through the APS Group Monitoring
window, as well.
To monitor an APS:
1

Right-click a LightLEADER in the LightLEADER Devices tree

- OR Right-click a LightLEADER in the Map view.
The following menu is displayed:

Figure 59: LightLEADER Menu, Monitor APS Option

Select the APS | Monitor APS option. If there is more than one APS
on the selected LightLEADER, a drop-down list of APSs is displayed.
Select the APS on the LightLEADER, which is to be monitored.

115

116

14BChapter 10
Managing an APS
LynxVision EMS User Guide

Click Ok to display the APS Monitoring window, as shown below:

APS ID
Power of Working

Name of Port

Working Link

Power of Protection

Main Signal

Protection Link

APS State

LightLEADER APS

Figure 60: APS Monitoring Window

This window enables you to monitor the Main (M) signal and the
Working (W) and Protection (P) links. It is identical to the APS Group
Monitoring window, except that it shows only one side of the APS
Group.
For a complete description of the APS Monitoring window including
the buttons in the control panel, refer to the Monitoring an APS Group
section on page 131.

14BChapter 10
Managing an APS
LynxVision EMS User Guide

Configuring an APS
After a LightLEADER has been added to the network, its APS can be configured,
including its Main signal, Working and Protection links.
To configure an APS:
1

Start a client session and log on as a Privileged user or an

Administrator as described in the Starting the LynxVISION Client
section in Starting and Shutting Down the LynxVISION Server and
Client on page 19.

Select the Configure button located on the Control and Command

panel of the APS Monitoring window.
- OR Right-click a LightLEADER in the LightLEADER Devices tree or a
LightLEADER icon in the Map view and from the right-click menu,
select APS | APS Configuration to display the following:

Figure 61: APS Configuration Window, Configuration Tab

Enter the information in the APS Configuration window as described in

Adding an APS Group in Managing an APS Group on page 122.

117

118

14BChapter 10
Managing an APS
LynxVision EMS User Guide

To set the power thresholds, click the Ports tab, as shown below:

Figure 62: APS Configuration Window, Ports Tab

Enter the information in this window as described in Adding an APS Group in

Managing an APS Group on page 122.
5

Click Apply or OK to save the changes. If the system is running in

Auto Commit mode, the changes are saved to the save configuration
file. Otherwise, a window is displayed asking whether to save the
changes on the volatile memory or the non-volatile memory.

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Chapter 11

Managing an APS Group

About This Chapter
This chapter describes what an APS Group is and how to add, monitor and configure it.
It contains the following sections:

What is an APS Group? page 120, defines an APS

Group and describes how to manage an extra traffic
service.

Adding an APS Group, page 122, describes how to

define the connection between two LightLEADER
APSs by running the Add an APS Group wizard.

Monitoring an APS Group, page 131, describes how

to monitor the state of both APSs in an APS Group and
to perform various commands, such as force protect
on both of them.

Configuring an APS Group, page 142, describes how

to change parameters, such as optical power thresholds
and wavelength, after the initial configuration of the
APS Group.

Target Audience: All users should read this chapter although the operations described
here can only be performed by Privileged users and Administrators.

119

120

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

What Is an APS Group?

To offer end-to-end protection, two APS functions are placed at each end of the optical
network segment, as depicted in Figure 1 on page 4.
Two APSs, at either end of the network, are connected by the Working and Protection
links. An APS on the eastern LightLEADER is connected to an APS on the western
LightLEADER. This group of two APSs, which provides end-to-end protection, is
termed an APS Group. There are two primary types of protection,
LightLEADERs that support 1:1 or 1:n architectures can carry extra traffic service in
addition to the Main service(s). An extra traffic service is a lower-priority service that is
transmitted on the Protection link while the Working link is active and is not
transmitted when the Working link fails. Only the 1:n or 1:1 type device can have an
extra traffic service. Devices of type 1+1 cannot have extra traffic service because the
Main service is being transmitted on both the Working and Protection links at the same
time.

APS Group State

As explained in Managing an APS on page 113, each APS has a state: Automatic,
Forced Protection, Forced Working, Manual Switched to Protection, or Switched. The
default state is Automatic. The state of a specific APS is independent of the states of the
other APSs on the LightLEADER.
For dual-ended devices, the state of both APSs in an APS Group must be identical. For
example, the following figure shows an APS Group in which only one APS was placed
in Forced Protection, causing a mismatch.

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Figure 63: Mismatched APS States

In a single-ended protection type, a mismatched state is allowed.

The APS state is displayed in either the APS Group Monitoring or APS Monitoring
windows, as shown in the above figure. The APS state can also be changed in these
windows by clicking the Enable/Disable button in the Monitoring window (as shown
in the figure below) or by using the Command operation, as described in the
Commands section in Managing an APS Group on page 135.
For further details, on how to manage mismatches in dual-ended devices, refer to the
Mismatched APS States section on page 136.

121

122

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Adding an APS Group

Creating an APS Group defines the connection between two LightLEADER APSs in
LynxVISION. To do this, use the Add APS Group wizard described below.
To add an APS Group:
1

Start a client session and log on as a Privileged user or an

Administrator, as described in the Starting the LynxVISION Client
section in Starting and Shutting Down the LynxVISION Server and
Client on page 19.

Right-click on a free place on a map or on a map name

in the tree and select Add APS Group
- OR Right-click the LightLEADER that contains the eastern
APS that is taking part in this APS Group.
- OR Select two LightLEADERs in the Map view (by pressing the control
button and clicking the two LightLEADER icons), and right-click.
The following menu is displayed (for the first option, right-clicking
directly on a map, the menu is skipped and the Add APS Group is
directly displayed):

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Figure 64: LightLEADER Menu

Select APS Group | Add APS Group to display the following

window:

Figure 65: Add APS Group Wizard: Main Window

123

124

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Enter the following information:

Field

Description

Name

Name of the APS Group. Must be filled by the operator

IP Address

The IP addresses shown by default are the IP addresses of the

LightLEADERs selected in the main window, although you can select
other IP addresses. After you select the east LightLEADER,
LynxVISION restricts the IP addresses that can be selected for the
west LightLEADER. You can select only an APS that is free (does not
belong to any APS Group) and that is of the same protection type as
the east LightLEADER.

APS

ID of the APS on each LightLEADER. When there are more than one
APS on a LightLEADER, select the required APS from the list. The
ID of the APS comprises the IP address of the device followed by the
ID of the APS within the device in the following format: IP APS
#chassis/#slot/#aps. For example: 10.130.0.1 APS 1/2/1.

Press Next to display the following window. The protection type of the
LightLEADER is displayed automatically in the Type field.

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Figure 66: Add APS Group Wizard: Configuration Window

Enter the following information:

125

126

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Field

Description

Auto Revert

Revert refers to the operation of the APS returning the

Main signal from the Protection link to the Working
link when it can be done (e.g. the Working link is
repaired or Force Protection was cleared). If the Auto
Revert checkbox is selected, the APS Group is in Autorevert mode. This means that the APS automatically
detects that the Working link is repaired, waits for a
user-defined stabilization interval (see next field, Time
to Restore, below), and then performs the revert
operation. If the Auto Revert checkbox is not selected,
then the APS Group remains on Protection link and you
need to command the devices to revert. Before
performing Revert, the system verifies that the Working
link is operational, and if it is not, it does not perform
the Revert command.

Time to Restore

When Auto Revert is checked, this field specifies the

time to wait, after the Working link is repaired, before
switching back to it. This time can be zero (immediately
returning) or specified in units of 10 seconds, for
example, 10 or 20 seconds. The time specified can be
up to 24 hours (86,400 seconds).

Extra Traffic

Specifies whether this APS Group supports an extra

traffic service. This is only relevant for 1:n or 1:1
products that support Extra traffic.

Wave Length

By default, the system assumes the signal can be

anywhere within one of the three supported bands (O, C
and L). In order to achieve higher power-monitoring
accuracy, configure the signal's specific band.

Click the Setup button to compute your network's optimal values for
the LOS and Degraded thresholds. This command is only available in
1:1 or 1:n products (for more details regarding the setup process, please
refer to the LightLEADER user guide). The Setup process must be
performed once, after the client optical signal has been connected to the
APSs at both ends and before enabling protection.

Press Next to display the APS Power Thresholds window:

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

127

Figure 67: APS Power Thresholds Window

The upper Monitoring block graphically describes the APS Group, and
specifies the following thresholds and current power for each interface.
Signals and Thresholds

From Where the Signal Enters

Thresholds (LOS and Degraded) on the client Tx

signal (when there is an OPM on the client interfaces)

Entering the APS through the Main

and Extra Traffic interfaces
(depending on the product type).

Thresholds (LOS and Degraded) on the W signal

Entering through the Working link.

128

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide
Signals and Thresholds

From Where the Signal Enters

Thresholds (LOS and Degraded) on the P signal

Entering through the Protection

link.

As you enter the thresholds in the Power Threshold block, the values in
the Monitoring block change accordingly.
NOTE:
The values set in the threshold field are in dBm units and must be entered in
the +/-XX.Y format.

Enter the power thresholds in the Power Threshold block for the west
and east LightLEADERs, as follows:
LOS

Loss of signal threshold

Degraded

Degraded signal threshold

Monitor for Degradation

Select these checkboxes to indicate whether the

link should be monitored for degradation.

Optionally, modify the default client name for each of the

LightLEADERs. When only one client is connected to a
LightLEADER, only the Main field is displayed. When extra traffic is
supported, an Extra Traffic field is displayed. Client names may be up
to 64 characters long.

Press Next to display the Additional Data window:

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Figure 68: Add APS Group Wizard, Additional Data Window

The Additional Data window allows you to specify additional data for
managing the APS group and your network links. This information is
not mandatory for the proper functioning of the APS Group, meaning
that these parameters are optional.
9

Enter the following information:

Working Link area

Enter W E Attenuation and

E W Attenuation for the Working link. Enter text
comments in the Additional Data field.

Protection Link area

Enter W E Attenuation and

E W Attenuation for the Protection link. Enter text
comments in the Additional Data field.

Service Name area

Enter a name that will help you identify the service that is
protected (for example: Contract Number, Client Name,
Equipment and so on).

10 Click Finish to complete the process. When the system is working in

Auto Commit mode, the configuration is automatically saved to the

129

130

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

startup configuration file. Otherwise, you are prompted with a window

asking whether to store the configuration in volatile memory or in both
non-volatile and volatile memory.
The new APS Group is displayed in the Map view as a line connecting
the two selected LightLEADERS. It also appears in the APS Groups
tree, as shown below:

Figure 69: APS Group in the APS Groups Tree and Map View

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Monitoring an APS Group

After an APS Group has been added, it is displayed in the Map view in
colors, which are defined by the conditions that prevail on the services and
devices, as described in the Color Code section in Fault Management on
page 78.
When there is no failure related to the line, and the line is not selected, it is
colored in gray. After it is selected, it is thicker to make it more visible
against the background image, as shown below:

Figure 70: Selected APS Group Link

To monitor the APS Group, open the APS Group Monitoring window, as
described below.
To monitor an APS Group:

Right-click a connection between two network elements

and select the Monitor APS Group option.
- OR Double-click on the APS Group name from APS Groups tree, or rightclick on it and select Monitor APS Group option.

131

132

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

- OR Right-click a network element on the map or the tree (which it is part of

APS Group) and select the APS Group | Monitor APS Group option.

Figure 71: APS Group Menu, Monitor APS Group Option

The APS Group Monitoring window is displayed:

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

APS ID

Power of Working
in East direction

133

Protection type

APS Group Name

Port ID
Main Signal Port
Power of Protection in
East Direction
East LIghtLEADER
APS

West LIghtLEADER
APS

APS State

Control and
Monitoring Panel
Figure 72: APS Group Monitoring Window

Current Status

APS Group Monitoring Window

This window provides information about the elements of an APS Group. Some of the
information is always displayed. Some information is displayed by hovering over an
element, as described in the Hovering Over the APS Group Monitoring Window section
on page 139 and some information is permanently displayed. The following describes
the information found in the APS Monitoring window:

APS Group name is displayed permanently in the window title bar.

Protection type and APS IDs are displayed across the top of the frame.

134

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Port labels as they appear on the APS card or LightLEADER chassis

(for example, M, W, P) are displayed within the rectangles
representing the interface.

The client names, as assigned by the operator, are displayed near the
client interface. When the names are longer than eight characters,
hovering over them will display the full name, as shown in Figure 76
on page 139.

Link color indicates the alarm severity that has occurred on it, black
line indicates signal OK, orange line (or dark yellow) for degraded
signal and red line with a cross on it indicates LOS.

Links through which the service is routed (Working, Protection or

both) are permanently displayed. For example, in Figure 72 on page
133, the signal passes through the working link only (the displayed
protection type is 1:1).

Provisioning state of each interface (enabled/disabled) is displayed by

its color. Provisioned interface is black while unprovisioned one is
gray. Interfaces are implicitly provisioned after protection is enabled,
and implicitly unprovisioned after protection is disabled. An interface
cannot be unprovisioned if it is a part of an enabled APS. An interface
can be explicitly provisioned even though an APS is disabled.

Power readings at the input of the Working and Protection interfaces,

and on the client interfaces (if supported in the APS being monitored)
are always displayed. If the interface is degraded, the power reading is
colored dark yellow.

Optical power thresholds of links are shown by hovering over the

links.

APS state is displayed for each APS.

Control and Command Panel

The Control and Command panel appears at the bottom of the APS Monitoring window
and enables the following actions:
Enable/Disable: This button toggles between Enable/Disable. It is used to control the
provisioning of the APS group. When the button is labeled Disable, both APSs are
currently enabled and can be disabled by clicking this button. When the button is
labeled Enable, then the APSs are currently disabled and can be enabled by clicking
this button.

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

135

Command: Opens a list of commands that can be applied to both APSs in the APS
Group in order to place them in a specific state. For further details, refer to the
Commands section on page 135.
Configure: Opens the APS Group Configuration window that enables you to control
the threshold and monitoring capabilities of the LightLEADERs (thresholds,
wavelengths and so on). For more details, refer to the Configuring an APS Group
section on page 142.
Current Status: Shows the provisioning state of the APS Group.
Auto Revert: If this checkbox is selected, it indicates that the APS is in Auto Revert
mode.
Revert Time: indicates the time it waits after the Working link is repaired before
switching back to it, when Auto Revert is checked.

Commands
The Command button, at the bottom of the APS Group Monitoring Window on page
133 enables access to the commands that can be applied to the APS in its current state.
This button is active only in Provision (enabled) mode. Clicking the Command button
displays the Set Command list:

Figure 73: Set Command List

The following commands may appear (depending on the current state of the APSs of
the APS Group):
Force Protection

Issues a command to force the APS functions on both sides to the

Protection link until a clear command is issued. This command is only
enabled when there is no Force command in place.
While in a Force state, the APS reports any detected failure, but does not
switch to the other link even when the failure is on the link to which it

136

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide
has been forced.
Force Working

Issues a command to force the service (on both sides) to pass through the
Working link until a Clear command is issued. This command is only
enabled when there is no Force command in place.

Manual Switch to Protection

Issues a command to switch the service through the Protection link.

Contrary to the Force Protection command, if the Protection link fails,
the main signal will be switched to the working link.
This command is only enabled when:
- Traffic is selected from the Working link.
- There is no Force or Manual Protect command in place.
-The Protection link is operational. Contrary to the Force
Protection command, if the Protection link fails, the main
signal will be switched to the working link.

Manual Switch to Working

Issues a command to revert and switch the service through the Working
link. This command is only enabled when:
- Traffic is selected from the Protection link.
- There is no Force or Manual Working command in place.
- The Working link is operational.

Clear

Clears the command that was in affect, and returns to automatic

protection switching mode. This command is only enabled when:
- There is a Force or a Manual Protect command in place.

Update Setting

Updates the links parameters. This command is available only in APS

groups that require the setup process.
The command must be executed each time there was a major change in
the optical links (loss of the link changed by more than 3dB).
This command is only enabled when
-

There is a force working or force protection in place.

The APS group requires the setup process.

Mismatched APS States

When creating a new APS Group, you must ensure that the two APSs that will make up
the APS Group have an identical provisioning status and revert mode. The following
states and other parameters must be identical in order to create an APS Group:

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Status

Action

Only one APS is enabled

A warning is issued and the process is terminated. The APSs must

be reconfigured to match using the APS Monitoring window.

Both APS are enabled

Both APSs must have the same Reversion Mode and Restore Time,
otherwise an APS group will not be created. To correct the
mismatch, both APSs must be disabled and reconfigured
to match".
Both APS must have the same Revert mode and Time to Revert,
otherwise an APS group will not be created. To correct the
mismatch, both APS must be disabled and reconfigured to match.

Both APS are disabled

A mismatch warning is issued and configuration resumes. At the

end of the process, both APS will be set with the specified
parameters.

For instance, if one APS is enabled and the other is disabled, the following message is
displayed:

Figure 74: Mismatch Error Warning Window

When a mismatch error warning is displayed, you must adjust one of the APSs to match
the other APS. You can do this in the APS Monitoring window shown on page 116 (to
enable/disable the APS and/or change the revert mode) or in the APS Configuration
window on page 142 (to set reversion mode and restore time).

Commands to Fix the Mismatched State

When each of the APSs in a dual ended APS Group has a different state (for example
one is in force protection while the other is in switch state) there is a mismatched
condition. Mismatch conditions occur usually as a result of human errors (i.e. working
with an APS and not the APS group, for dual ended protection schemes).
LynxVISION enables operators to solve these mismatch conditions easily by enabling

137

138

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

them to issue a command that places the APSs in the same state.
When the APS Group Monitor is open, a mismatch dialog appears, and the following
commands become available:

Figure 75: Clear and adjust both Commands

These commands clear the APSs in the APS Group and then place them both in the
same state. For example, when you choose Clear & Force Protection, both APSs are
cleared of their current state and placed in the Force Protection state. When you choose
Clear & Forced Working, both APSs are cleared of their current state and placed in
the Force Working state and so on for each state, shown above.

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Hovering Over the APS Group

Monitoring Window
To display information on various elements of the APS Group Monitoring window,
hover over the element with the cursor. The figure below is a sample of the information
that can be displayed in this way.

Figure 76: APS Group Monitoring Window: Displaying the Name of a Port

Hovering over a client port shows a line connecting the two clients with the service
name, as shown below:

139

140

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Figure 77: APS Group Monitoring Window: Connection Between Two

clients

Hovering over the Working or Protection interfaces shows the power

thresholds, as shown below:

Figure 78: APS Group Monitoring Window: Link Power Thresholds Window

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Monitoring thresholds are displayed for LightLEADER devices with 1:1 protection type
on which there APSs that support both a user threshold and a monitoring threshold
(usually APSs supporting 1:1, for more details on monitoring threshold, please refer to
the LightLEADER user guide), as shown below:

Figure 79: Monitoring Thresholds

141

142

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

Configuring an APS Group

An APS Group is configured while it is being added using the Add APS Group wizard.
Later, the configuration parameters can be changed using the APS Group Configuration
window.
To configure an APS Group:
1

Select the Configure button located on the Control and Command

panel of the APS Group Monitoring window to display the APS Group
Configuration Window.
- OR -

Select an APS Group in the APS Groups tree or right-click a

LightLEADER icon or connecting link between two LightLEADERs in
the Map view, and from the right-click menu, select APS Group | APS
Group Configuration. The APS Group Configuration window appears:

Figure 80: APS Group Configuration Window, Configuration Tab

Enter information in these fields, as described on page 124. Note that

15BChapter 11
Managing an APS Group
LynxVision EMS User Guide

elements that are grayed out cannot be modified while the APS Group
is enabled.
4

Click the Ports tab and enter information, as described on page 126.

Click the Link Attenuation and Service Name tab and enter
information, as described on page 128.

Click the Apply or the OK button to save the changes. If Auto Commit
has been enabled they are saved in the startup configuration (nonvolatile memory) file. Otherwise, you will be asked whether to save
them in the Running Configuration file (volatile memory) or in the
Startup Configuration file.

143

144

16BChapter 12
Tools
LynxVision EMS User Guide

Chapter 12
Tools

About This Chapter

This chapter describes how to access various tools through LynxVISION, which helps
with the management of LightLEADERs. It contains the following sections:

MIB Browser, page 145, describes how to open a MIB

browser and what can be performed using the browser.

Telnet, page 146, describes how to open a Telnet

command window.

Target Audience: All users.

16BChapter 12
Tools
LynxVision EMS User Guide

MIB Browser
LynxVISION provides access to a standard MIB browser that performs the following
functions:

Loads a MIB and views MIB modules in a MIB tree.

Traverses the MIB tree to view the definitions of each

node for a particular object defined in the MIB.

Walks the MIB tree to retrieve the values of all the

instances of the selected MIB object.

Views the incoming traps using Trap Viewer. It also

allows parsing of traps.

Performs the basic SNMP operations, such as GET,

GETNEXT, and SET with both single- and
multi-varbind requests.

Records the operations performed into a text file.

Views real-time plotting of SNMP data in a graph.

Both line and bar graphs are supported.

Views the SNMP table data in a separate window

called SNMP Table Panel.

To access the MIB Browser:

1

Right-click a LightLEADER on the map or the tree to display

LightLEADER menu.

2 Select Tools | MIB Browser to display the MIB browser.

- OR From menu bar select Tools | MIB Browser

145

146

16BChapter 12
Tools
LynxVision EMS User Guide

Telnet
A Telnet session can be opened from within LynxVISION. The Telnet session enables
you to enter CLI commands for the LightLEADER for which the session was opened.
To open a Telnet session:
1

Right-click a LightLEADER the map or the tree to display the

LightLEADER menu.

Select Tools | Telnet. A Telnet session is opened with the IP address of

the LightLEADER.