PHM Manual

Title page
Alcatel-Lucent 1830
1354 RM-PhM Photonic Manager | Release 8.5
EMS REFERENCE GUIDE
3AL61307AAAA
ISSUE 1
FEBRUARY 2011
Legal notice
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2011 Alcatel-Lucent. All rights reserved.
Conformance statements
Interference Information: Part 15 of FCC Rules

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are
designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy. If the equipment is not installed and used in accordance with the guidelines in this document, the
equipment may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference,
in which case the user will be required to correct the interference at the expense of the user.
Security statement
In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such an event,
applicable tariffs require that the customer pay all network charges for traffic. Alcatel-Lucent cannot be responsible for such charges and will not make any
allowance or give any credit for charges that result from unauthorized access.
Limited warranty
For terms and conditions of sale, contact your Alcatel-Lucent Account Team.
Ordering Information
For more ordering information, refer to "How to order" in the section titled "About this document."
Contents
About this document
xix
Purpose ........................................................................................................................................................................................... xix
Audience ........................................................................................................................................................................................ xix
xix
Document conventions
Related information
.............................................................................................................................................................. xx
xx
.................................................................................................................................................................... xx
xx
Document support ...................................................................................................................................................................... xxi

xxi
Technical support
...................................................................................................................................................................... xxii
xxii
How to order ............................................................................................................................................................................... xxii

xxii
Packaging collection and recovery requirements .......................................................................................................... xxii
Recycling/Take-Back/Disposal of Product
How to comment
1
.................................................................................................................... xxiii
..................................................................................................................................................................... xxiii
xxiii
Overview
Overview ...................................................................................................................................................................................... 1-1
1-1
1354 RM-PhM server .............................................................................................................................................................. 1-1
1-1
1354 RM-PhM hardware configurations .......................................................................................................................... 1-2
1-2
1354 RM-PhM communication ........................................................................................................................................... 1-3
1-3
1354 RM-PhM release specifications ................................................................................................................................ 1-3
1-3
1354 RM-PhM engineering guidelines ............................................................................................................................. 1-4
1-4
1354 RM-PhM scaling ............................................................................................................................................................ 1-4
1-4
New features introduced in 1354 RM-PhM R8.5
......................................................................................................... 1-4
1-4
System administration
Overview ...................................................................................................................................................................................... 2-1
2-1
....................................................................................................................................................................................................................................
1354 EMS Reference Guide Release 8.5
iii
3AL61307AAAA Issue 1
February 2011
Contents
....................................................................................................................................................................................................................................
System requirements ................................................................................................................................................................ 2-3

2-3
Interfaces and protocols .......................................................................................................................................................... 2-3
2-3
1354 RM-PhM redundant servers ....................................................................................................................................... 2-7
2-7
Installing the 1354 RM-PhM
....................................................................................................................................................................................................... 2-12
2-12
Before you start ....................................................................................................................................................................... 2-12

2-12
Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform
Installing the 1354 RM-PhM on Windows
.............................................................. 2-13
2-13
................................................................................................................... 2-18
2-18
Starting and stopping the server and client

....................................................................................................................................................................................................... 2-24
2-24
1354 RM-PhM service wrapper ........................................................................................................................................ 2-24

2-24
Starting the 1354 RM-PhM server on Linux or Solaris x86/x64 .......................................................................... 2-25
2-25
Stopping the 1354 RM-PhM server on Linux or Solaris x86/x64 ........................................................................ 2-29
2-29
Starting the 1354 RM-PhM server on Microsoft Windows .................................................................................... 2-31
2-31
Stopping the 1354 RM-PhM server on Microsoft Windows .................................................................................. 2-32
2-32
Starting a client session ........................................................................................................................................................ 2-33
2-33
Stopping a client session ...................................................................................................................................................... 2-35
2-35
Configuring the 'iptables' firewall .................................................................................................................................... 2-35
2-35
Configuring the file transfer properties of the 1354 RM-PhM server ................................................................. 2-36
2-36
Configuring the NTP properties of the 1354 RM-PhM server
.............................................................................. 2-37
2-37
Configuring the NTP properties of the network elements ....................................................................................... 2-38

2-38
1354 RM-PhM database backup and restore
....................................................................................................................................................................................................... 2-39
2-39
1354 RM-PhM database backup ....................................................................................................................................... 2-40

2-40
1354 RM-PhM database restore ........................................................................................................................................ 2-42
2-42
....................................................................................................................................................................................................................................
iv
February 2011
Contents
....................................................................................................................................................................................................................................
Recovering from file corruption without having to restore from a backup
...................................................... 2-43
2-43
Performing a server switch-over ....................................................................................................................................... 2-44

2-44
1696 ROADM and 1830 PSS network element database backup and restore
....................................................................................................................................................................................................... 2-45
2-45
Performance Monitoring (PM) Archive Setting

....................................................................................................................................................................................................... 2-48
2-48
SNMP Trap Alarm Forwarding

....................................................................................................................................................................................................... 2-50
2-50
RADIUS server and user authentication

....................................................................................................................................................................................................... 2-54
2-54
1354 RM-PhM user management

....................................................................................................................................................................................................... 2-73
2-73
NE user management
....................................................................................................................................................................................................... 2-79
2-79
1354 RM-PhM login session settings

....................................................................................................................................................................................................... 2-84
2-84
1696 ROADM and 1830 PSS network element software management

....................................................................................................................................................................................................... 2-87
2-87
1354 RM-PhM management of Red-C RAMAN Amplifier & EDFA Booster

....................................................................................................................................................................................................... 2-95
2-95
Configuring and navigating the network

Overview ...................................................................................................................................................................................... 3-1
3-1
Types of network views .......................................................................................................................................................... 3-2
3-2
Discovering network elements ............................................................................................................................................. 3-6
3-6
Configuring network links
.................................................................................................................................................. 3-15
3-15
Showing topological connections ..................................................................................................................................... 3-17

3-17
....................................................................................................................................................................................................................................
v
February 2011
Contents
....................................................................................................................................................................................................................................
Configuring the network element and network fiber topology
............................................................................. 3-18
3-18
Using Wavelength Tracker monitoring capability ...................................................................................................... 3-23

3-23
Managing optical power levels .......................................................................................................................................... 3-24
3-24
Using the automatic power management interface .................................................................................................... 3-30
3-30
Managing APS groups .......................................................................................................................................................... 3-39
3-39
CLI cut-thru .............................................................................................................................................................................. 3-44
3-44
TL1 cut-thru
............................................................................................................................................................................. 3-45
3-45
WebUI cut-thru ........................................................................................................................................................................ 3-46

3-46
4
Monitoring system events and network alarms

Overview ...................................................................................................................................................................................... 4-1
4-1
Overview of network alarms
......................................................................................................................................................................................................... 4-3
4-3
Opening an alarm window for a managed object or group

......................................................................................................................................................................................................... 4-7
4-7
Acknowledging an alarm
......................................................................................................................................................................................................... 4-9
4-9
Suppressing alarms
....................................................................................................................................................................................................... 4-10
4-10
Clearing an alarm
....................................................................................................................................................................................................... 4-11
4-11
Using the 1354 RM-PhM log view

....................................................................................................................................................................................................... 4-12
4-12
Performance monitoring
....................................................................................................................................................................................................... 4-15
4-15
Starting and stopping PM collection
............................................................................................................................... 4-16
4-16
Viewing PM data and raw PM data ................................................................................................................................. 4-17

4-17
....................................................................................................................................................................................................................................
vi
February 2011
Contents
....................................................................................................................................................................................................................................
Configuring PM and TCA profiles ................................................................................................................................... 4-17

4-17
Troubleshooting Wavelength Tracker alarms
....................................................................................................................................................................................................... 4-18
4-18
Determining the source of an alarm
................................................................................................................................ 4-19
4-19
Determining the WaveKeys used for a service ............................................................................................................ 4-21

4-21
Querying the WaveKeys
...................................................................................................................................................... 4-22
4-22
Troubleshooting the WaveKey insertion failed alarm ............................................................................................... 4-23

4-23
Troubleshooting the Missing WaveKey alarm ............................................................................................................. 4-24
4-24
Troubleshooting the Unexpected WaveKey alarm ..................................................................................................... 4-26
4-26
Troubleshooting the Duplicate WaveKey alarm
......................................................................................................... 4-27
4-27
Troubleshooting the Invalid WaveKey alarm ............................................................................................................... 4-29

4-29
Troubleshooting a power out of range alarm
....................................................................................................................................................................................................... 4-30
4-30
1354 RM-PhM alarm reference
......................................................................................................................................................................................................... 5-1
5-1
A communication failure occurred

......................................................................................................................................................................................................... 5-2
5-2
ActiveAlarmResyncFailure
An attempt to resynchronize the alarms from the NE failed.
................................................................................... 5-4
5-4
AutoUpgradeFailure
......................................................................................................................................................................................................... 5-5
5-5
CardOutOfSync
......................................................................................................................................................................................................... 5-7
5-7
Communication failure
......................................................................................................................................................................................................... 5-8
5-8
....................................................................................................................................................................................................................................
vii
February 2011
Contents
....................................................................................................................................................................................................................................
COMMUNICATION_FAILURE
......................................................................................................................................................................................................... 5-9
5-9
Creation Failure
....................................................................................................................................................................................................... 5-10
5-10
Duplicate programmed wave key

....................................................................................................................................................................................................... 5-11
5-11
Equipment cache invalid

....................................................................................................................................................................................................... 5-13
5-13
Facility Retrieval
....................................................................................................................................................................................................... 5-14
5-14
Failed Auto Discovery

....................................................................................................................................................................................................... 5-15
5-15
Failed to archive
....................................................................................................................................................................................................... 5-17
5-17
Failed to register 1354 RM-PhM as trap destination

....................................................................................................................................................................................................... 5-18
5-18
Fault log archive configuration failed

....................................................................................................................................................................................................... 5-20
5-20
....................................................................................................................................................................................................... 5-21
5-21
install error
....................................................................................................................................................................................................... 5-22
5-22
Install Extension error

....................................................................................................................................................................................................... 5-23
5-23
Invalid Annotation
....................................................................................................................................................................................................... 5-24
5-24
....................................................................................................................................................................................................................................
viii
February 2011
Contents
....................................................................................................................................................................................................................................
Invalid Parameter
....................................................................................................................................................................................................... 5-25
5-25
Invalid Supervisor
....................................................................................................................................................................................................... 5-26
5-26
Invalid Table
....................................................................................................................................................................................................... 5-27
5-27
Invalid Variable
....................................................................................................................................................................................................... 5-28
5-28
Invalid XML reference

....................................................................................................................................................................................................... 5-29
5-29
Invalid XML value

....................................................................................................................................................................................................... 5-30
5-30
Inventory Retrieval
....................................................................................................................................................................................................... 5-31
5-31
JDBC Log Data Store Error

....................................................................................................................................................................................................... 5-32
5-32
Log Initialization
....................................................................................................................................................................................................... 5-33
5-33
LOGGER HALT
....................................................................................................................................................................................................... 5-34
5-34
LOGGER PURGELC
....................................................................................................................................................................................................... 5-35
5-35
Lookup Error
....................................................................................................................................................................................................... 5-36
5-36
Low Level Parsing Error

....................................................................................................................................................................................................... 5-37
5-37
....................................................................................................................................................................................................................................
ix
February 2011
Contents
....................................................................................................................................................................................................................................
Meta Change
....................................................................................................................................................................................................... 5-38
5-38
Meta Mismatch
....................................................................................................................................................................................................... 5-39
5-39
Missing XML mandatory attribute

....................................................................................................................................................................................................... 5-40
5-40
Missing XML mandatory element

....................................................................................................................................................................................................... 5-41
5-41
NE + neName + "PM retrieval failed"

....................................................................................................................................................................................................... 5-42
5-42
NE + neName + "system time out of sync with 1354 RM-PhM"

....................................................................................................................................................................................................... 5-44
5-44
NE Backup failed
....................................................................................................................................................................................................... 5-45
5-45
NEEventLogArchiveConfigFail
....................................................................................................................................................................................................... 5-46
5-46
NERequestLogArchiveConfigFail
....................................................................................................................................................................................................... 5-47
5-47
Network Connection error
.................................................................................................................................................. 5-48
5-48
New Entity
....................................................................................................................................................................................................... 5-49
5-49
1354 RM-PhM behind in performing PM tasks

....................................................................................................................................................................................................... 5-50
5-50
1354 RM-PhM failed to initialize adaptation

....................................................................................................................................................................................................... 5-51
5-51
....................................................................................................................................................................................................................................
x
February 2011
Contents
....................................................................................................................................................................................................................................
1354 RM-PhM PowerCommissionInProgress

....................................................................................................................................................................................................... 5-52
5-52
1354 RM-PhMSetNMSAsNTPServerMessage
....................................................................................................................................................................................................... 5-53
5-53
Object Lookup
....................................................................................................................................................................................................... 5-54
5-54
Object Prop Change

....................................................................................................................................................................................................... 5-55
5-55
Object removal
....................................................................................................................................................................................................... 5-56
5-56
Object Storage
....................................................................................................................................................................................................... 5-57
5-57
Parsing Exception
....................................................................................................................................................................................................... 5-58
5-58
PK Lookup
....................................................................................................................................................................................................... 5-59
5-59
REDUNDANCY
....................................................................................................................................................................................................... 5-60
5-60
Scalability Problem
....................................................................................................................................................................................................... 5-61
5-61
ServerLogArchiveConfigFail
....................................................................................................................................................................................................... 5-62
5-62
Service definition downloaded

....................................................................................................................................................................................................... 5-63
5-63
SNMP Bulk Get Error

....................................................................................................................................................................................................... 5-64
5-64
....................................................................................................................................................................................................................................
xi
February 2011
Contents
....................................................................................................................................................................................................................................
SNMP Error received

....................................................................................................................................................................................................... 5-65
5-65
SNMP Get Error

....................................................................................................................................................................................................... 5-66
5-66
SNMP GetNext Error

....................................................................................................................................................................................................... 5-67
5-67
SNMP Set Error

....................................................................................................................................................................................................... 5-68
5-68
The scheduled time for Software Load task for neName is scheduled to begin at startTime which is
in the past. It will be run immediately.
....................................................................................................................................................................................................... 5-69
5-69
The Software Activation task for getneName is scheduled to begin at getStartTime which is in the
past. Please re-schedule.
....................................................................................................................................................................................................... 5-70
5-70
The Software Activation task for " + _neName + " has been aborted due to the presence of
unacknowledged alarms."
....................................................................................................................................................................................................... 5-71
5-71
The Software Load task for neName that was scheduled to begin at getStartTime failed to initiate.
....................................................................................................................................................................................................... 5-72
5-72
TNREPLICATIONSERVICE
....................................................................................................................................................................................................... 5-74
5-74
Unavailable Annotation
....................................................................................................................................................................................................... 5-75
5-75
Unavailable NEType
....................................................................................................................................................................................................... 5-76
5-76
UnknownNEType
....................................................................................................................................................................................................... 5-77
5-77
....................................................................................................................................................................................................................................
xii
February 2011
Contents
....................................................................................................................................................................................................................................
UnknownSource
....................................................................................................................................................................................................... 5-78
5-78
Unrecognized Autonomous
....................................................................................................................................................................................................... 5-80
5-80
Unrecognized XML element

....................................................................................................................................................................................................... 5-81
5-81
Unrecognized XML attribute

....................................................................................................................................................................................................... 5-82
5-82
XML validation
....................................................................................................................................................................................................... 5-83
5-83
Managing services
Overview ...................................................................................................................................................................................... 6-1
6-1
Setting service preferences
......................................................................................................................................................................................................... 6-2
6-2
Listing and editing services

......................................................................................................................................................................................................... 6-3
6-3
Creating or editing a wavelength service

......................................................................................................................................................................................................... 6-5
6-5
Importing and exporting service definitions

....................................................................................................................................................................................................... 6-14
6-14
Discovering services in the network

....................................................................................................................................................................................................... 6-16
6-16
Unmanaging services in the network

....................................................................................................................................................................................................... 6-17
6-17
Partial services
....................................................................................................................................................................................................... 6-18
6-18
....................................................................................................................................................................................................................................
xiii
February 2011
Contents
....................................................................................................................................................................................................................................
Sub-rate service
....................................................................................................................................................................................................... 6-19
6-19
Sub-rate service creation via service wizard
................................................................................................................ 6-22
6-22
1696R and 1830 PSS interoperability

....................................................................................................................................................................................................... 6-25
6-25
Glossary
Index
....................................................................................................................................................................................................................................
xiv
February 2011
List of tables
1
Command syntax rules
.............................................................................................................................................. xx
xx
2-1
1354 RM-PhM to network element protocols and ports
2-2
NMA/Transport to GNE protocols and ports
2-3
Task list for configuring and using a RADIUS authentication server
2-4
1354 RM-PhM user role permissions
4-1
WaveKey encoding and decoding points ........................................................................................................ 4-18
............................................................................. 2-3
.................................................................................................. 2-7
................................................. 2-55
.............................................................................................................. 2-76
....................................................................................................................................................................................................................................
xv
February 2011
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xvi
February 2011
List of figures
1-1
1696 ROADM and 1830 PSS network management system
.................................................................... 1-2
2-1
1354 RM-PhM redundant servers
2-2
EMS Status window ............................................................................................................................................... 2-10

2-10
2-3
1354 RM-PhM installation wizard - last chance to cancel
...................................................................... 2-16
2-4
1354 RM-PhM installation wizard - last chance to cancel
...................................................................... 2-22
2-5
Security alert dialog
2-6
System Settings dialog
2-7
SNMP Trap Destinations table
2-8
The Add RADIUS Client dialog ........................................................................................................................ 2-57
2-9
The Add Native User dialog ................................................................................................................................ 2-58
3-1
Uni-directional light path power window
3-2
Optical power levels at a Wavelength Tracker detection point
3-3
Ingress monitor point power management window
3-4
Egress monitor point power management window ..................................................................................... 3-34
3-5
Bi-directional path power trace .......................................................................................................................... 3-36
3-6
Uni-directional light path power window
3-7
APS Views window ................................................................................................................................................ 3-40
3-8
APS Group attributes window ............................................................................................................................ 3-40
4-1
1354 RM-PhM Topology View
6-1
Wavelength service fiber endpoints
6-2
Manually power-managed service
6-3
Automatically power-managed service
....................................................................................................................... 2-7
............................................................................................................................................... 2-34
2-34
.......................................................................................................................................... 2-49
2-49
........................................................................................................................... 2-51
...................................................................................................... 3-24
.............................................................. 3-26
................................................................................... 3-33
...................................................................................................... 3-37
............................................................................................................................ 4-3
.................................................................................................................... 6-9
.................................................................................................................... 6-10
........................................................................................................... 6-11
....................................................................................................................................................................................................................................
xvii
February 2011
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xviii
February 2011
About this document

About this document
Purpose
This document provides information about accessing the 1354 RM-PhM and using it to
configure and manage the 1696 ROADM and 1830 PSS network. It contains the
following chapters:
Chapter 1, Overview
Chapter 2, System administration
Chapter 3, Configuring and navigating the network
Chapter 4, Monitoring system events and network alarms
Chapter 5, 1354 RM-PhM alarm reference
Chapter 6, Managing services
Audience
This document is intended for the following users of the 1696 ROADM and 1830 PSS
documentation library:
administrators
operators
maintenance personnel
1696 ROADM and 1830 PSS products are meant to be installed, operated, and
maintained by personnel who have the knowledge, training, and qualifications required to
safely perform the tasks assigned to them. The information, processes, and procedures
contained in the 1696 ROADM and 1830 PSS product documentation are intended for
use by trained and qualified personnel.
...................................................................................................................................................................................................................................
xix
February 2011
About this document

....................................................................................................................................................................................................................................
Document conventions
Command syntax
Table 1, Command syntax rules (p. xx) describes the command syntax rules used in
this document.
Table 1
Command syntax rules
Syntax format
Description
bold
Commands and keywords. Enter command line arguments that are

in bold exactly as written.
italics
Variables. You must substitute a value for command line

arguments that are in italics.
[ optional ]
Optional keywords or variables. Enter command line arguments

that are enclosed in square brackets, if desired.
[ optional ]
{a|b|c}
{a|b|c}
[a|b|c]
[a|b|c]
Required alternate keywords or variables. You must choose one

command line argument enclosed within the braces. Choices are
separated by vertical (OR) bars.
Optional alternate keywords or variables. Choose one command
line argument enclosed within the braces, if desired. Choices are
separated by vertical (OR) bars.
Related information
The Alcatel-Lucent 1354 RM-PhM Release 8.5 Photonic Manager EMS Reference Guide
is part of a set of documents that support the 1696 ROADM and 1830 PSS System. The
following documents are available:
1696 ROADM Documents
1830 PSS Documents
Alcatel-Lucent 1696 ROADM Technical

Information Guide
Alcatel-Lucent 1830 Photonic Service Switch

32/16 (PSS-32/16) Release 3.5.0 Product
Information and Planning Guide
Alcatel-Lucent 1696 ROADM Hardware and

Network Configuration Guide
Alcatel-Lucent 1696 ROADM Operations,
Administration, Maintenance, and
Provisioning Guide

32/16 (PSS-32/16) Release 3.5.0 User
Provisioning Guide
Alcatel-Lucent 1696 ROADM Web Interface

Reference Guide
Alcatel-Lucent 1696 ROADM Maintenance
and Troubleshooting Guide

32/16 (PSS32/16) Release 3.5.0 Maintenance
and Trouble-Clearing Guide
....................................................................................................................................................................................................................................
xx
February 2011
About this document

....................................................................................................................................................................................................................................
1696 ROADM Documents
1830 PSS Documents
Alcatel-Lucent 1696 ROADM CLI Reference

Guide

(PSS) Release 3.5.0 Command Line Interface
Guide
Alcatel-Lucent 1696 ROADM TL1 Reference

Guide

(PSS) Release 3.5.0 TL1 Commands and
Messages Guide
Alcatel-Lucent 1696 ROADM Safety and

Compliance Guide

(PSS) Release 3.5.0 Safety Guide
Alcatel-Lucent 1696 ROADM LPT Reference

Guide

(PSS) Release 3.5.0 Engineering and Planning
Tool User Guide
Alcatel-Lucent 1696 ROADM Hardware

Installation Guide

32/16 (PSS-32/PSS-16) Release 3.5.0
Installation and System Turn-Up Guide
Alcatel-Lucent 1696 ROADM Commissioning

and Turn-up Guide
Alcatel-Lucent 1830 Photonic Service Switch 4

(PSS-4) Release 1.0.0 User Guide
(PSS-1) Release 2.7.0 GBEH Edge Device
User Guide
(PSS-1) Release 1.7.0 MD4H Edge Device
User Guide
(PSS-1) Release 1.0.0 AHP Amplifier User
Guide
(PSS) Product Family Release 3.5.0 CD-ROM
Document support
Alcatel-Lucent provides a referral telephone number for document support. Use this
number to report errors or to ask questions about the document. This is a non-technical
number. The referral number is 1 (888) 727 3615 (continental United States) or +1 (630)
713 5000 (for all countries).
....................................................................................................................................................................................................................................
xxi
February 2011
About this document

....................................................................................................................................................................................................................................
Technical support
Login to OnLine Customer Support (OLCS) at http://support.alcatel-lucent.com and

select your country from the pulldown menu under "Product Technical Support - Phone
and Email Contact Information".
How to order
Contact your local sales representative, or login to OLCS at http://support.alcatellucent.com and select your product from the pulldown menu under "Technical Content
for".
Packaging collection and recovery requirements
Countries, states, localities, or other jurisdictions may require that systems be established
for the return and/or collection of packaging waste from the consumer, or other end user,
or from the waste stream. Additionally, reuse, recovery, and/or recycling targets for the
return and/or collection of the packaging waste may be established.
For more information regarding collection and recovery of packaging and packaging
waste within specific jurisdictions, please contact the Alcatel-Lucent Field
Services/Installation - Environmental Health and Safety organization.
....................................................................................................................................................................................................................................
xxii
February 2011
About this document

....................................................................................................................................................................................................................................
Recycling/Take-Back/Disposal of Product
Collect and treat electronic products bearing or referencing the following symbol, within
the European Union, at the end of their useful life in compliance with applicable
European Union and local legislation. Do not dispose of these products as part of
unsorted municipal waste. Due to materials that may be contained in the product, such as
heavy metals or batteries, the environment and human health may be negatively impacted
as a result of inappropriate disposal.
Note: In the European Union, a solid bar under the crossed-out wheeled bin indicates that
the product was put on the market after 13 August 2005.
Moreover, in compliance with legal requirements and contractual agreements, where

applicable, Alcatel-Lucent provides for the collection and treatment of Alcatel-Lucent
products at the end of their useful life. Alcatel-Lucent also provides for the collection and
treatment of existing products that have been displaced by Alcatel-Lucent equipment.
For information regarding take-back of equipment by Alcatel-Lucent, or for more
information regarding the requirements for recycling/disposal of product, please contact
your Alcatel-Lucent account manager or Alcatel-Lucent Take-Back Support at
takeback@alcatel-lucent.com.
How to comment
To order Alcatel-Lucent documents, contact your local sales representative or use Online
Customer Support (OLCS) (https://support.lucent.com).
....................................................................................................................................................................................................................................
xxiii
February 2011
About this document

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xxiv
February 2011
Overview
1
Overview
Purpose
This chapter provides an overview of the 1354 RM-PhM. It contains the following
sections:
Contents
1354 RM-PhM server
1-1
1354 RM-PhM hardware configurations
1-2
1354 RM-PhM communication
1-3
1354 RM-PhM release specifications
1-3
1354 RM-PhM engineering guidelines
1-4
1354 RM-PhM scaling
1-4
1-4
1354 RM-PhM server

The 1354 RM-PhM is a client-server system that is used to perform remote monitoring
and control of networks of 1696 ROADM and 1830 PSS equipment. Figure 1-1, 1696
ROADM and 1830 PSS network management system (p. 1-2) shows a high level view
of the 1354 RM-PhM together with 1696 ROADM and 1830 PSS network elements. The
Alcatel-Lucent 1830 PSS family includes the Alcatel-Lucent 1830 PSS-32/PSS-16, the
Alcatel-Lucent 1830 PSS-4, the Alcatel-Lucent 1830 PSS-1 GBEH Edge Device, the
Alcatel-Lucent 1830 PSS-1 MD4H Edge Device, and the Alcatel-Lucent 1830 PSS-1
AHP Amplifier.
...................................................................................................................................................................................................................................
1-1
February 2011
Overview
1354 RM-PhM server
....................................................................................................................................................................................................................................
Figure 1-1 1696 ROADM and 1830 PSS network management system
The 1354 RM-PhM supports management of both 1696 ROADM and 1830 PSS network
elements. The 1354 RM-PhM server communicates with the network elements using the
SNMP protocol. A network element is characterized by having an SNMP agent. As a
result, a network element is a managed entity.

Listed in this section are the operating system requirements for the servers and clients of a
1354 RM-PhM.
Servers
The 1354 RM-PhM server runs on either Windows Server 2008, Red Hat Enterprise
Linux Release 5.5., Solaris x64/x86. and HP-UX Itanium (HP-UX 11i v2 B.11.23).
Note: All of the supported platforms (Windows Server 2008, Red Hat Enterprise
Linux Release 5.5. and Solaris x64/x86) have built in NTP servers. It is recommended
to use the built in NTP server available on the platform.
....................................................................................................................................................................................................................................
1-2
February 2011
Overview
....................................................................................................................................................................................................................................
Clients
The 1354 RM-PhM client runs on either Windows Server 2008, Windows XP (Service
Pack 2), Red Hat Enterprise Linux Release 5.5., and Solaris x64/x86.
1354 RM-PhM communication

The 1354 RM-PhM uses the SNMP management protocol to communicate with the NEs.
The 1354 RM-PhM supports SNMPv1, SNMPv2c and SNMPv3 and the following
capabilities: adding and removing new SNMP users, changing SNMP user passwords,
and enabling/disabling SNMP users. (See the 1830 PSS-32/PSS-16 User Provisioning
Guide).
Note: The default SNMP user cannot be deleted, but can only be disabled.
In normal mode (see 1830 PSS-32/PSS-16 User Provisioning Guide), SNMP requests
(without authentication and privacy) are allowed by the NE.
Note: The user (admin level) can change the mode from normal to encrypted during
the run time (see 1830 PSS CLI Reference Guide). This will result in an NE restart.
1354 RM-PhM release specifications

Listed below are the release specifications for a 1696 ROADM and 1830 PSS network:
The 1354 RM-PhM manages only 1696 ROADM and 1830 PSS network elements. It
does not manage the routers or other communications equipment.
The recommended maximum number of network elements per 1354 RM-PhM is 250.
The framework is capable of handling much larger networks. These are not
hard-coded limits to the number of network elements; however, the system is only
tested to a network size of 250.
The maximum alarm processing throughput is 1000/sec for 10 second burst.
....................................................................................................................................................................................................................................
1-3
February 2011
Overview
....................................................................................................................................................................................................................................

The following guidelines can be used to determine the number and location of 1354
RM-PhM servers:
Ensure each ring is managed by a single 1354 RM-PhM and that no 1354 RM-PhM
manages more than 250 NEs.
No more than 100 users are permitted at one time.
Ensure that the communications between each client and the server is at least 10
Mb/sec.
Ensure that the communication link between the server and the network is at least 10
Mb/sec.
If possible, ensure that each client has connectivity to each NE. This allows users to
perform cut-thru operations to the NEs.
1354 RM-PhM scaling

The 1354 RM-PhM can be scaled to meet demand by considering the following points:
If the server is CPU bound, additional CPUs or faster CPUs may be added. No 1354
RM-PhM upgrades or configuration changes are required.
It is recommended that the 1354 RM-PhM database be installed on a disk that is

separate from the operating system and swap files.
If the server is memory bound, additional memory can be added without
reconfiguration. The server can be reconfigured by re-installing the 1354 RM-PhM
and choosing the upgrade option, or by contacting your customer support
representative.

1354 RM-PhM Release 8.5 supports 1830 PSS Release 3.5.0 and includes the following
new features
11DPM12 Dual Port Pluggable Multirate Mux (12 universal clients)

11QPA4A Quad Port Pluggable Anyrate OT (Hardened version of 11QPA4)
11DPE12E 11G Dual Port Pluggable GbE Mux (12 clients)
MVAC Multiple Variable Attenuator Card Keyed (alien wavelength manag

RA2P Long Haul - 2 pump Raman module, no mid-stage access
11DPE12 QinQ operational mode
AM2125A medium gain modular amplifier
Displaying both PreFEC counts and PreFEC BER
....................................................................................................................................................................................................................................
1-4
February 2011
Overview
....................................................................................................................................................................................................................................
Low latency DCMs for SSMF and LEAF

1830 PSS-4 support
100G Regen Support
UTF-8 support
Client performance improvements
....................................................................................................................................................................................................................................
1-5
February 2011
Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1-6
February 2011
2
Overview
Purpose
This chapter explains how to start and stop the 1354 RM-PhM server and client and how
to backup and restore the database.
Contents
2-3
System requirements
2-3
Interfaces and protocols
2-3
2-7
2-12
2-12
Before you start
2-12
Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform
2-13
2-18
2-24
2-24
1354 RM-PhM service wrapper
2-24
Starting the 1354 RM-PhM server on Linux or Solaris x86/x64
2-25
Stopping the 1354 RM-PhM server on Linux or Solaris x86/x64
2-29
Starting the 1354 RM-PhM server on Microsoft Windows
2-31
Stopping the 1354 RM-PhM server on Microsoft Windows
2-32
Starting a client session
2-33
Stopping a client session
2-35
...................................................................................................................................................................................................................................
2-1
February 2011
Overview
....................................................................................................................................................................................................................................
Configuring the 'iptables' firewall
2-35
Configuring the file transfer properties of the 1354 RM-PhM server
2-36
2-37
Configuring the NTP properties of the network elements
2-38
2-39
2-39
1354 RM-PhM database backup
2-40
1354 RM-PhM database restore
2-42
Recovering from file corruption without having to restore from a backup
2-43
Performing a server switch-over
2-44
2-45
2-45
2-48
2-48
2-50
2-50
2-54
2-54
2-73
2-73
NE user management
2-79
2-79
2-84
2-84
1696 ROADM and 1830 PSS network element software management
2-87
2-87
1354 RM-PhM management of Red-C RAMAN Amplifier & EDFA Booster
2-95
2-95
....................................................................................................................................................................................................................................
2-2
February 2011
System requirements
....................................................................................................................................................................................................................................
System requirements
The recommended system requirements for supporting a 1354 RM-PhM server or client
are listed in the release notes which can be obtained from your Alcatel-Lucent
representative.

The 1354 RM-PhM uses the following protocols and ports. These ports must not be in use
by any other application (such as an SNMP daemon).
The 1354 RM-PhM has no northbound interfaces.
The following table lists the protocols and ports used for communications between the
1354 RM-PhM and the network elements.
Table 2-1
Protocol
Stack
Action
Destination
Port
Source Port
Application
RMI
1354 RM-PhM
client to server
1099,
10999,11000,
11001,11002,
11003
Dynamic
client/server
communication
....................................................................................................................................................................................................................................
2-3
February 2011
....................................................................................................................................................................................................................................
Table 2-1

Source Port
(continued)
Protocol
Stack
Action
Destination
Port
Application
FTP
The 1354 RM-PhM

server acts as a FTP
client to browse the
contents of the NE
software server.
20, 21
NE software download,
NE database backup and
restore, archiving of
PhM logs
Same as above but

secure
Can be used to
transfer 1354
RM-PhM files to be
archived on a
remote server. This
can be performed
with:
database
backup files
archived log
file
exported
service
configuration
files
exported LPT
network
configuration
files
SFTP
Same as above but

secure
22
SNMP v1,
v2c
Request from 1354

RM-PhM
161
Dynamic
Reply from NE
Same as
request
source
161
Traps from NE
162
161
Request from 1354

RM-PhM
161
Dynamic
Reply from NE
Same as
request
source
161
Traps from NE
162
161
SNMP V3)
NE /server
communication
Secure NE /server
communication
....................................................................................................................................................................................................................................
2-4
February 2011
....................................................................................................................................................................................................................................
Table 2-1
(continued)
Protocol
Stack
Action
Destination
Port
Source Port
Application
HTTP/
TCP/IP
Request from 1354

RM-PhM client
80
Dynamic
Web interface cut-thru
Reply from NE
Same as
request
source
80
Request from 1354

RM-PhM client
80
Dynamic
Reply from 1354

RM-PhM server
Same as
request
source
80
Request from 1354

RM-PhM client
80
Dynamic
Reply from NE
Same as
request
source
80
Telnet/TCP/IP
23
Dynamic
Reply from NE
Same as
request
source
23
Secure shell
22
Dynamic
Reply from NE
Same as
request
source
22
Telnet/TCP/IP
3083
Dynamic
Reply from NE
Same as
request
source
3083
Request from NE
69
Dynamic
Reply from
software download
or backup and
restore server
Same as
request
source
69
HTTPS/
TCP/IP
HTTP/
TCP/IP
Telnet/
TCP/IP
SSH
TL1/Telnet/
TCP/IP
TFTP/
UDP/IP
Web interface cut-thru
PhM CPB web server
CLI cut-thru to NE
CLI cut-thru to NE
TL1 cut-thru to NE
TL1 cut-thru to NE
....................................................................................................................................................................................................................................
2-5
February 2011
....................................................................................................................................................................................................................................
Table 2-1
(continued)
Protocol
Stack
Action
Destination
Port
Source Port
Application
NTP/
UDP/IP
Request from NE or
1354 RM-PhM
server
123
Dynamic
time and
synchronization
Reply from NTP

server
Same as
request
source
123
Java service
wrapper to JVM
31001
32001
JVM to Java
service wrapper
32001
31001
Java service
wrapper to JVM
31002
32002
JVM to Java
service wrapper
32002
31002
Java service
wrapper to JVM
31003
32003
JVM to Java
service wrapper
32003
31003
MySQL
3306
dynamic
Request from MySQL

client to MySQL server
Same as
request
source
3306
Response from MySQL

server to MySQL client
Java
Service
Wrapper
MySQL
PhM process
management. Local
communications only.
PhM web server (CPB)

process management.
Local communications
only.
PhM netpilot process

management. Local
communications only.
Telcordia NMA/Transport to network element protocols and ports
The following table lists the protocols and ports used for communications between
Telcordia NMA/Transport and NEs.
....................................................................................................................................................................................................................................
2-6
February 2011
....................................................................................................................................................................................................................................
All communication between Telcordia NMA or Transport and the NEs uses:
TCP/IP protocol
the DCN IP addresses of the gateway NEs.

application level TCP gateways to reach non-gateway NEs
Table 2-2
NMA/Transport to GNE protocols and ports
Protocol Stack
Action
Destination Port
Source Port
TL1/TCP/IP
Request from 1354

RM-PhM
3082
Dynamic
Reply from NE
Same as request
source
3082
Request from 1354

RM-PhM
3083
Dynamic
Reply from NE
Same as request
source
3083
TL1/Telnet/TCP/IP

The 1354 RM-PhM can be configured with redundant servers to protect against server
failure. Server redundancy is an option that is specified during the installation of the 1354
RM-PhM server software.
A 1354 RM-PhM redundant server system consists of two 1354 RM-PhM servers running
on two separate computers, as seen in the following figure.
Figure 2-1 1354 RM-PhM redundant servers
....................................................................................................................................................................................................................................
2-7
February 2011
....................................................................................................................................................................................................................................
At a given moment, one of the pair is designated as the active server and the other as the
standby server. Only the active server communicates with the network elements and the
1354 RM-PhM clients. Each server has its own local copy of the 1354 RM-PhM database.
Database changes to the active database are replicated immediately to the standby
database.
To view the current state of server redundancy, choose Admin>PhM Status.
Terminology notes:
The active server is the one that currently has control of the network and is
communicating to the network elements. When a 1354 RM-PhM redundancy switch
occurs, the other server becomes the active. 1354 RM-PhM server switching is not
revertive, meaning the servers do not automatically return to their original designation
of active and standby. An active server remains as active until a manual or automatic
switch occurs.
When installing each 1354 RM-PhM server in a redundant pair, the user is asked to
supply a Server ID for that server. This can be either the number 1 or the number
2. You can specify either Server ID to either server as long as a different Server ID
is used for each server. The choice of the Server ID value has no effect on which
server becomes active or standby. When installing a redundant pair of servers, the
server that comes up first becomes active.
When a redundant 1354 RM-PhM server starts up, it is initially in the standby state.
When the server has finished initializing itself, it attempts to communicate with its
redundant mate. If it finds that the mate is already in the active state it then remains as
standby. If the mate is also in the standby state then a challenge mechanism is used to
designate one of the pair as the sole active server and the other to remain as standby. If a
server cannot communicate with its mate, it becomes active.
Due to network or configuration problems, it may occur that both servers become active.
A common scenario for this is when the network cable for one of the servers is removed.
This interrupts the communication of each server with its mate so that they then both
assert that they are active. When normal communications are restored, the servers
recognize the situation and elect one server as the active, and the other becomes standby.
This process is called the Active Challenge and proceeds as follows:
1. Each server determines the number of network elements that it is connected to. The
one with the higher number becomes active. If the number is the same then:
2. Each server determines the number of active user sessions. The one with the higher
number becomes active. If the number is the same then:
3. The server whose name alphabetically proceeds the other becomes active.
....................................................................................................................................................................................................................................
2-8
February 2011
....................................................................................................................................................................................................................................
The 1354 RM-PhM servers communicate for the purpose of redundancy at two levels:
server-to-server heartbeat - every 15 seconds (configurable), each 1354 RM-PhM

server communicates via TCP/IP with its mate to determine the mate's state and to
determine if a state change is warranted. By default, a standby server becomes active
if two heartbeats are missed.
database replication - changes to the active server's database are replicated to the
standby server's database.
Server switch-over occurs when the standby server loses communication with the active
server. Communications loss can occur because the active server has gone down, or
because the communication link between the two servers has failed. On switch-over to
active, the server registers itself as a trap destination for all network elements. All client
sessions on the former active server are shut down. Client sessions must be manually
restarted and are directed automatically to the new active server.
On switch-over to standby, the server de-registers itself as a trap destination with all
network elements.
Server switch-over can be manually initiated by choosing Admin>PhM Status, and
clicking the Switch button.
Managing redundant servers
To view and manage redundant servers, in the 1354 RM-PhM choose Admin>PhM
Status. The following window is displayed.
....................................................................................................................................................................................................................................
2-9
February 2011
....................................................................................................................................................................................................................................
Figure 2-2 EMS Status window
The fields relating to servers and redundancy are:
Active Server - the server that is currently acting as the active server
Standby Server - the server that is currently acting as the standby server
Server Configuration - the valid values are:
stand-alone - for a server that is not configured to be redundant
Redundant - ACTIVE - indicating that this is the active server in a redundant pair
Server Synchronization State - indicates whether the last heartbeat to the standby
server was successful. If the state is Synchronized then the field's background is
green. Otherwise, it is red. If this field is red then the active server is unable to
communicate with the standby 1354 RM-PhM application. Verify that:
the 1354 RM-PhM is running and operational on the standby server
communication is possible between the active and standby servers

the standby server is installed as a redundant server with the active server
Try to log into the 1354 RM-PhM application using the 1354 RM-PhM client. If
you can log in successfully then it indicates that both servers are acting a active
since neither can complete a heartbeat to the other. Verify that communications are
operational in both directions between the servers.
....................................................................................................................................................................................................................................
2-10
February 2011
....................................................................................................................................................................................................................................
Database Synchronization State (Active to Standby) - indicates whether the database

replication is operating correctly to propagate changes in the database of the active
server to the database of the standby server. If the state is Synchronized then the
field's background is green. Otherwise, it is red. If this field is red then the active
server's database is unable to communicate with the database of the standby 1354
RM-PhM. Verify that:
The SSH tunnel from the active server to the standby server is installed and
operational.
If the condition persists then perform a Database Sync.
Database Synchronization State (Standby to Active) - indicates whether the database

replication mechanism is operating correctly to propagate changes from the database
of the server currently acting standby server to the database of the active server. This
is important because if a switch was to occur then the current standby server would
become active. If the state is Synchronized then the field's background is green.
Otherwise, it is red. Verify that:
The SSH tunnel from the standby server to the active server is installed and
operational.
If the condition persists then perform a Database Sync.
The following actions can be performed:
Back up Database - create a file on the server containing the database contents. See
1354 RM-PhM database backup (p. 2-40) for information about 1354 RM-PhM
database backup and 1354 RM-PhM database restore (p. 2-42) for information
about 1354 RM-PhM database restore.
Switch - to cause the database that is currently active to become standby and the
current standby to become the new active server. If the standby is not able to become
active then the original active becomes active once more.
Server Shutdown - shut down the server that is currently active. If it is online and
operational, the standby becomes active.
....................................................................................................................................................................................................................................
2-11
February 2011
....................................................................................................................................................................................................................................

The 1354 RM-PhM is installed by an install wizard which guides you through the
process and prompts you for input as necessary. The files required for installation are
transferred to your computer through the file transfer protocol (FTP), or delivered on a
DVD. Contact your service representative for the FTP site and user ID and password or
for the DVD. This section covers the following procedures:
Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform (p. 2-13)
Installing the 1354 RM-PhM on Windows (p. 2-18)
Before you start

For Solaris systems, install the latest Recommended Solaris Patch Cluster which can be
found at:
http://sunsolve.sun.com.
....................................................................................................................................................................................................................................
2-12
February 2011
Installing the 1354 RM-PhM on a Linux or Solaris x86/x64

platform
....................................................................................................................................................................................................................................

platform
In this release, the 1354 RM-PhM can run on either of the following platforms:
Solaris x64/x86
Linux
HP-UX
There is a single installation package for the 1354 RM-PhM on Linux or Solaris x86/x64
platforms that installs either the 1354 RM-PhM server (includes the server and client
software), or only the client software. The installer asks the user to select the desired
installation.
Before installing the 1354 RM-PhM, perform the following tasks as necessary:
create account roles as required

Important! Be sure to specify the current installation's install directory when running
the installer. The installer must be pointed at the appropriate directory.
To install 1354 RM-PhM on Linux or Solaris x86/x64

...................................................................................................................................................................................................
Log in as the root user.

...................................................................................................................................................................................................
Ensure that the /etc/hosts file on the PhM server machine has a separate line containing
the primary physical interface and the hostname of the machine. Otherwise, the PhM
server will not be listening on the correct port to receive client connections from remote
machines (a local client will still be able to login to the server but not a remote one).
For example, if the PhM server hostname is 1830sim07, the following line: 127.0.0.1
localhost.localdomain localhost 1830sim07 must be changed to:
127.0.0.1 localhost.localdomain localhost
10.3.2.7 1830sim07
in the /etc/hosts file
Here, the physical interface (10.3.2.7) is identified with the hostname on a separate line in
the file.
Important! Ensure the "/etc/hosts" file defines the IPv4 loopback address as
"127.0.0.1". Failure to do this may cause the PhM application to be unable to connect
to the database. The /etc/hosts file should have a line similar to:
127.0.0.1 localhost localhost.localdomain
....................................................................................................................................................................................................................................
2-13
February 2011

platform
....................................................................................................................................................................................................................................
It is recommended that your system admin edit the /etc/hosts directly with a text
editor rather than use the Red Hat network admin tools.
...................................................................................................................................................................................................
If you are installing from files that have been FTPed to your system, change directory to
the directory where the installation files have been FTPed, and ensure that the file
setup.sh is executable.
If you are installing from a DVD, copy installation files from the DVD to a directory on
the hard drive. After that, change directory to the directory where the installation files
have been copied, and ensure that the file setup.sh is executable.
...................................................................................................................................................................................................
Set the DISPLAY environment variable to the name of the machine on which you are
working.
...................................................................................................................................................................................................
Execute the setup.bin file. Type:

cd<cdrom> (directory where the cd is located - this may be /cdrom or /
media/cdrom)
cd PhM
Note: For Solaris x86 this command is: cd phm

cd linux (or cd solarisx86)
sh setup.sh
The installation wizard starts up and guides you through the installation procedure.
...................................................................................................................................................................................................
It is recommended that you accept all of the defaults suggested by the installation wizard,
however, you can customize the following items when prompted.
the directory into which to install the 1354 RM-PhM (Do not include a space in the
installation directory name or else the installation fails.)
user name and group name to own the installed files
perform a new installation (which removes all existing data) or an upgrade (which
preserves existing data)
install a stand-alone server or redundant servers
select the file transfer protocol
specify the TFTP root directory
choose whether or not to display a banner at login time
Note: On Linux, the user is not given the option to choose whether or not to display a
banner at login time.
....................................................................................................................................................................................................................................
2-14
February 2011

platform
....................................................................................................................................................................................................................................
Note: If displayed, the user must press y or yes (not case sensitive) and the enter
key to acknowledge the logon banner before being able to continue with their session.
The login banner then displays a message indicating that unauthorized access is
prohibited.
If applicable, specify the Use PhM Administrator Role.
When all options have been specified, the installation wizard copies the 1354 RM-PhM
files into the specified directory.
...................................................................................................................................................................................................
When prompted, click Finish.

The installation wizard exits.
E...................................................................................................................................................................................................
N D O F S T E P S
To upgrade the 1354 RM-PhM on Linux or Solaris x86/x64

...................................................................................................................................................................................................
The 1354 RM-PhM upgrade procedure is the same as the installation procedure, except
that you choose the upgrade option instead of the new installation option. You do not need
to uninstall the 1354 RM-PhM to upgrade. The upgrade backs up the existing installation
files.
Important! Be sure to specify the current installation's install directory when running
the installer. The installer must be pointed at the appropriate directory.
E...................................................................................................................................................................................................
N D O F S T E P S
To cancel or back out from a 1354 RM-PhM upgrade on Linux or Solaris x86/x64
...................................................................................................................................................................................................
You can safely cancel a 1354 RM-PhM upgrade at any time during the upgrade up to and
including the window in the following illustration.
....................................................................................................................................................................................................................................
2-15
February 2011

platform
....................................................................................................................................................................................................................................
Figure 2-3 1354 RM-PhM installation wizard - last chance to cancel
If you click Cancel in this window, or in any previous window, the installation wizard
exits and you can continue to safely use the existing version of the 1354 RM-PhM.
If you click Next in this window, the installation wizard begins to overwrite the existing
1354 RM-PhM with the new version.
...................................................................................................................................................................................................
Begin a new 1354 RM-PhM installation using the installation files/DVD of the previous
version.
...................................................................................................................................................................................................
When prompted to choose between a New Installation and an Upgrade, choose New
Installation.
...................................................................................................................................................................................................
After the installation has completed, stop the PhM server.

...................................................................................................................................................................................................
Restore the PhM database from the backup file in

install_dir_backup2/bin/mysql/data/tropxnmsBackup.sql. For example:
1. cd /opt/PhM_backup2/bin
....................................................................................................................................................................................................................................
2-16
February 2011

platform
....................................................................................................................................................................................................................................
Note: For Solaris x86 this command is: cd /opt/phm_backup2/bin

2. ./dbrestore.sh ../mysql/data/tropxnmsBackup.sql
...................................................................................................................................................................................................
Start the PhM server.

E...................................................................................................................................................................................................
N D O F S T E P S
To uninstall the 1354 RM-PhM on Linux or Solaris x86/x64
In normal situations, this procedure should never be needed. The 1354 RM-PhM
installation procedure can perform an upgrade to, or an overwrite of, the existing version
of the 1354 RM-PhM.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Execute install_dir/uninstall.sh
...................................................................................................................................................................................................
After the uninstall wizard is finished, manually delete all remaining files from the
installation directory.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-17
February 2011
....................................................................................................................................................................................................................................

Attention: To install the 1354 RM-PhM on Windows, there must be a DVD drive in
the install PC.
There are two installation packages for the 1354 RM-PhM on Windows. One package
installs the 1354 RM-PhM server, which includes the server and client software, and one
package installs only the client software.
The server/client installation package also installs TFTP server software. Before installing
the server/client package, check to see if there is already a TFTP server application
running on the server. If there is, have your system administrator remove it so that there is
no conflict when the 1354 RM-PhM server is installed.
Before installing the 1354 RM-PhM ensure that the installation files are in a location that
can be accessed from the computer on which the 1354 RM-PhM is to be installed.
To install the 1354 RM-PhM server on Windows
...................................................................................................................................................................................................
Log in as a user that is a member of the Windows Administrator group.

...................................................................................................................................................................................................
If you are installing from a DVD, skip this step. If you are installing from files that have
been FTPed to your system, change directory to the directory where the installation files
have been FTPed. Ensure that you FTP the directories windows and common and
choose the correct installation directory for the type of installation that you want to
perform.
...................................................................................................................................................................................................
Execute windows/setup.exe.
...................................................................................................................................................................................................
the directory into which to install the 1354 RM-PhM

install a stand-alone server or a redundant server pair
select the file transfer protocol

specify the TFTP root directory
....................................................................................................................................................................................................................................
2-18
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
To install the 1354 RM-PhM client on Windows

...................................................................................................................................................................................................

...................................................................................................................................................................................................
If you are installing from files that have been FTPed to your system, change directory to
the directory where the installation files have been FTPed. Ensure that you choose the
correct installation directory for the type of installation that you want to perform, either
server and client, or client only.
If you are installing from a DVD, skip this step.
...................................................................................................................................................................................................
Execute the windows_client.exe file.

...................................................................................................................................................................................................
the directory into which to install the 1354 RM-PhM

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-19
February 2011
....................................................................................................................................................................................................................................
To install the 1354 RM-PhM client on Windows using a web browser
You can install a 1354 RM-PhM client by accessing the installation files on the server via
the web.
...................................................................................................................................................................................................
Configure your internet browser to retrieve the latest version of the 1354 RM-PhM web
page and client installer. In the Microsoft Internet Explorer browser, perform the
following steps:
1. Choose Tools>Internet Options....
2. In the box labeled Temporary Internet Files, click on Settings....
3. In the options for Check for newer versions of stored pages:, choose either
Every visit to the page, or
Automatically (this is the default setting and is recommended).
4. Click the OK button on the Settings window.
5. Click the OK button on the Internet Options window.
...................................................................................................................................................................................................
On the client machine, log in as a user that is a member of the Windows Administrator
group.
...................................................................................................................................................................................................
Launch Internet Explorer.

...................................................................................................................................................................................................
In the address field, type:

http://server_name:5960/global/
where server_name is the name of the server on which the 1354 RM-PhM is installed.
The 1354 RM-PhM web page is launched.
...................................................................................................................................................................................................
On the web page click Install/Upgrade PhM client.

Follow the instructions that are displayed in the web page and in the installation wizard
that is launched.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-20
February 2011
....................................................................................................................................................................................................................................
To upgrade the 1354 RM-PhM server on Windows

...................................................................................................................................................................................................
The 1354 RM-PhM upgrade procedure is the same as the installation procedure, except
that you choose the upgrade option instead of the new installation option. You do not need
to uninstall the 1354 RM-PhM to upgrade. The upgrade backs up the existing installation
files.
E...................................................................................................................................................................................................
N D O F S T E P S
To upgrade the 1354 RM-PhM client on Windows

...................................................................................................................................................................................................
There are two methods by which the client can be upgraded:
manual - The manual 1354 RM-PhM client upgrade procedure is the same as the
installation procedure, except that you choose the upgrade option instead of the new
installation option. You do not need to uninstall the 1354 RM-PhM to upgrade. The
upgrade backs up the existing installation files.
automatic - The automatic method occurs when the client recognizes that it is not at
the same version as the server. The client shuts down and then an upgrade wizard
launches and guides you through the upgrade.
E...................................................................................................................................................................................................
N D O F S T E P S
To cancel or back out from a 1354 RM-PhM upgrade on Windows

...................................................................................................................................................................................................
You can safely cancel a 1354 RM-PhM upgrade at any time during the upgrade up to and
including the window in the following illustration.
....................................................................................................................................................................................................................................
2-21
February 2011
....................................................................................................................................................................................................................................
Figure 2-4 1354 RM-PhM installation wizard - last chance to cancel
If you click Cancel in this window, or in any previous window, the installation wizard
exits and you can continue to safely use the existing version of the 1354 RM-PhM.
If you click Next in this window, the installation wizard begins to overwrite the existing
1354 RM-PhM with the new version.
E...................................................................................................................................................................................................
N D O F S T E P S
To uninstall the 1354 RM-PhM on Windows
Note: Before performing this procedure, shut down the PhM client, if it is running.
In normal situations, this procedure should never be needed. The 1354 RM-PhM
installation procedure can perform an upgrade to, or an overwrite of, the existing version
of the 1354 RM-PhM.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Shut down all 1354 RM-PhM clients that are running.
....................................................................................................................................................................................................................................
2-22
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Use the 1354 RM-PhM uninstall wizard.

...................................................................................................................................................................................................
Once the uninstall wizard is finished, restart Windows.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-23
February 2011
....................................................................................................................................................................................................................................

This section describes server startup and shutdown on the 1354 RM-PhM. It covers the
following procedures:
Starting the 1354 RM-PhM server on Linux or Solaris x86/x64 (p. 2-25)
Stopping the 1354 RM-PhM server on Linux or Solaris x86/x64 (p. 2-29)
Starting the 1354 RM-PhM server on Microsoft Windows (p. 2-31)
Stopping the 1354 RM-PhM server on Microsoft Windows (p. 2-32)
Starting a client session (p. 2-33)
Stopping a client session (p. 2-35)

Note: All these processes start automatically when 1354 RM-PhM is installed or the
server rebooted. Likewise, they stop automatically when 1354 RM-PhM is uninstalled
or shut down.
1354 RM-PhM service wrapper

The 1354 RM-PhM service wrapper monitors the status of the 1354 RM-PhM server on
both the Linux or Solaris x86/x64 and Windows platforms. If the 1354 RM-PhM server
stops unexpectedly or becomes unresponsive, then the watchdog shuts it down and then
restarts it. The 1354 RM-PhM service wrapper is installed with the 1354 RM-PhM server
software and is started automatically. It runs continuously in the background.
The 1354 RM-PhM service wrapper does not affect the 1354 RM-PhM client.
....................................................................................................................................................................................................................................
2-24
February 2011
....................................................................................................................................................................................................................................

The 1354 RM-PhM server consists of the Element Management Server (EMS), PhM Web
Server, and MySQL database. The 1354 RM-PhM server is started automatically when
the Linux or Solaris x86/x64 host on which it resides is rebooted. The EMS, PhM web
server, and MySQL database are started automatically as part of the system startup.
Startup messages can be viewed in file /var/adm/messages. Look for mysql.server,
phm.server, and ems.server entries.
To manually start the 1354 RM-PhM server or any of its components, use the following
procedures.
Note: Using a Linux window manager, you can control the 1354 RM-PhM services
like other services using the commands in Linux. For example, in gnome go to
System>Administration>Server Settings>Services and you will see mysql, phmweb,
and ems in the list of background services.
The Linux commands are:
service phm start

service phm stop
service phm restart
service phm status
service mysql start

service mysql stop
service mysql restart
service mysql status
service phmw start

service phmw stop
service phmw restart
service phmw status
service phmnetpilot stop

service phmnetpilot restart
service phmnetpilot status
You can still start and stop ems, phmweb, and mysql using the scripts in /etc/init.d
(see below): To start the database (start MySQL) on Unix (i.e. Solaris, Linux and
HP-UX) (p. 2-26),To start the PhM (PhM server) (p. 2-26), To start the PhM web
server (p. 2-27),To stop the PhM (p. 2-29), To stop the PhM web server
(p. 2-29), and To stop the database (stop MySQL) on Unix (i.e. Solaris, Linux and
HP-UX) (p. 2-29).
....................................................................................................................................................................................................................................
2-25
February 2011
....................................................................................................................................................................................................................................
To start the database (start MySQL) on Unix (i.e. Solaris, Linux and HP-UX)
...................................................................................................................................................................................................

...................................................................................................................................................................................................
At the command line type:

<installdir>/bin/mysql.sh start
Note:
replace <installdir> with the location where you installed PhM, e.g. if you
installed in /opt/PhM then enter the command "/opt/PhM/bin/mysql.sh start"
you can still run "/etc/init.d/mysql start" on Solaris or Linux if you prefer, but on
HP-UX you have to enter "/sbin/init.d/mysql start". Therefore,
<installdir>/bin/mysql.sh start" is better since it works for all Unix platforms.
This command was "/etc/init.d/mysql.server start" in some previous releases on
some platforms
on Linux you can enter "service mysql start"
E...................................................................................................................................................................................................
N D O F S T E P S
To start the PhM (PhM server)
Before you start the PhM, the database must be started first.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
To start the PhM, at the command line type:

<installdir>/bin/phm.sh start
Note:
you can run "/etc/init.d/phm start" on Solaris or Linux if you prefer, but on
HP-UX you have to enter "/sbin/init.d/phm start".
This command was "/etc/init.d/ems start" or "/etc/init.d/ems.server start" in
previous releases
on Linux you can enter "service mysql start"
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-26
February 2011
....................................................................................................................................................................................................................................
To start the PhM web server
Note: This web server supports CPB as well as other future web applications.
Before you start the phmweb, the database must be started first.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
To start the PhM web server, at the command line type:

<instlldir>/bin/phmw.sh start
Note: On Linux you can enter "service phmw start".

E...................................................................................................................................................................................................
N D O F S T E P S
To start all PhM processes

...................................................................................................................................................................................................

...................................................................................................................................................................................................

<instlldir>/bin/phmall.sh start
E...................................................................................................................................................................................................
N D O F S T E P S
To restart all PhM processes

...................................................................................................................................................................................................

...................................................................................................................................................................................................

<instlldir>/bin/phmall.sh restart
E...................................................................................................................................................................................................
N D O F S T E P S
To view PhM status

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2-27
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

<instlldir>/bin/phmall.sh status
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-28
February 2011
Stopping the 1354 RM-PhM server on Linux or Solaris

x86/x64
....................................................................................................................................................................................................................................
Stopping the 1354 RM-PhM server on Linux or Solaris x86/x64

The procedures in this section should be performed only by a system administrator.
To stop the PhM
...................................................................................................................................................................................................

...................................................................................................................................................................................................

<installdir>/bin/phm.sh stop
Note:
you can run "/etc/init.d/phm stop" on Solaris or Linux if you prefer, but on
HP-UX you have to enter "/sbin/init.d/phm stop".
This command was "/etc/init.d/ems stop" or "/etc/init.d/ems.server stop" in
previous releases
on Linux you can enter "service mysql stop"
E...................................................................................................................................................................................................
N D O F S T E P S
To stop the PhM web server

...................................................................................................................................................................................................

...................................................................................................................................................................................................

/etc/init.d/phmweb stop
E...................................................................................................................................................................................................
N D O F S T E P S
To stop the database (stop MySQL) on Unix (i.e. Solaris, Linux and HP-UX)
To stop the database, the PhM must be stopped first.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

<installdir>/bin/mysql.sh stop
....................................................................................................................................................................................................................................
2-29
February 2011
Stopping the 1354 RM-PhM server on Linux or Solaris

x86/x64
....................................................................................................................................................................................................................................
Note:
replace <installdir> with the location where you installed PhM, e.g. if you
installed in /opt/PhM then enter the command "/opt/PhM/bin/mysql.sh stop"
you can still run "/etc/init.d/mysql stop" on Solaris or Linux if you prefer, but on
HP-UX you have to enter "/sbin/init.d/mysql stop". Therefore,
<installdir>/bin/mysql.sh stop" is better since it works for all Unix platforms.
This command was "/etc/init.d/mysql.server stop" in some previous releases on
some platforms
on Linux you can enter "service mysql stop"
E...................................................................................................................................................................................................
N D O F S T E P S
To stop all PhM processes

...................................................................................................................................................................................................

...................................................................................................................................................................................................

<instlldir>/bin/phmall.sh stop
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-30
February 2011
....................................................................................................................................................................................................................................

To perform these procedures you must be logged in as an administrator, or as a member
of the Power Users group.
To start the database
...................................................................................................................................................................................................
The database is installed as a network service, and is started automatically when the
machine starts.
If the database is stopped, it can be restarted manually. In a cmd.exe window, type:
net start mysql
E...................................................................................................................................................................................................
N D O F S T E P S
To start the PhM
To start the PhM, the database must be started first.

...................................................................................................................................................................................................
To run the PhM as a service, in a cmd.exe window, type:

net start phm
To run the PhM as a process, in a cmd.exe window, type:

cd installdir\bin
where installdir is the installation directory (C:\Program Files\PhM).

Type:
phm
E...................................................................................................................................................................................................
N D O F S T E P S
To start the PhM web server

...................................................................................................................................................................................................
In a cmd.exe window, type:

net start phmw
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-31
February 2011
....................................................................................................................................................................................................................................

To perform these procedures you must be logged in as an administrator, or as a member
of the Power Users group.
To stop the PhM
...................................................................................................................................................................................................
There are several methods to stop the PhM:

1. If the PhM is running as a service, in a cmd.exe window, type:
net stop phm
2. From the 1354 RM-PhM Management Control Panel (MCP), choose Admin>PhM
Status, and then click the Server Shutdown button.
E...................................................................................................................................................................................................
N D O F S T E P S
To stop the database
To stop the database, the PhM must be stopped first.

...................................................................................................................................................................................................

net stop mysql
E...................................................................................................................................................................................................
N D O F S T E P S
To stop the PhM web server

...................................................................................................................................................................................................

net stop phmw
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-32
February 2011
....................................................................................................................................................................................................................................

The 1354 RM-PhM client consists of the Management Control Panel (MCP). Under
normal operating conditions, it should take less than 30 seconds for the client to start up.
It is recommended that you run only one client session on the 1354 RM-PhM server
machine at a time.
To start a client session on Linux or Solaris x86/x64
...................................................................................................................................................................................................

cd installdir/bin
where installdir is the installation directory (opt/Phm).

...................................................................................................................................................................................................
Start the client by typing:

mcp
...................................................................................................................................................................................................
Log into the 1354 RM-PhM.

If this is the first login after a new installation, log into the 1354 RM-PhM as an admin
user. Obtain the password from your customer support representative. You should change
the password provided to a new one as soon as possible (see To manage 1354 RM-PhM
user accounts (p. 2-74) ).
Note: If a user tries to log in six times in a row with the same user name but wrong
password, their account is locked, and can be unlocked only by an administrator.
E...................................................................................................................................................................................................
N D O F S T E P S
To start a client session on Windows
A client session can be run on the 1354 RM-PhM server machine, but it is recommended
that you run only one client session on the 1354 RM-PhM server machine at a time.
...................................................................................................................................................................................................
There are two methods to start a client session:

1. Click the Windows Start button, and choose, 1354 RM-PhM>Client.
or:
2. In a cmd.exe window, type:
cd installdir\bin
where installdir is the installation directory (C:\Program Files\PhM.
Type:
....................................................................................................................................................................................................................................
2-33
February 2011
....................................................................................................................................................................................................................................
mcp
You are prompted to enter a username and hostname.

To start the client session and log output to the console window, type:
sh_mcp
...................................................................................................................................................................................................
Log into the 1354 RM-PhM.

If this is the first login after a new installation, log into the 1354 RM-PhM as an admin
user. Obtain the password from your customer support representative. You should change
the password provided to a new one as soon as possible (see Password Rules table in
previous procedure).
Note: If a user tries to log in six times in a row with the same user name but wrong
password, their account is locked, and can be unlocked only by an administrator.
Once you log in, you may see the following window:
Figure 2-5 Security alert dialog
If you see this window, click Keep Blocking.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-34
February 2011
....................................................................................................................................................................................................................................

To log out of a client session
...................................................................................................................................................................................................
Close the main client window, or in the 1354 RM-PhM, choose File > Exit.
E...................................................................................................................................................................................................
N D O F S T E P S
Configuring the 'iptables' firewall

Note: The following information is included to assist the user, but PhM does not
require that iptables be used.
Iptables is the standard firewall that comes with Linux. It is available for Solaris and
HP-UX. Below is a sample set of iptables rules where the 1354 RM-PhM server address
is 138.120.203.13. The rules drop any traffic arriving with a destination of
138.120.203.13 (PhM Server IP) and X (range of blocked ports) port on the Ethernet
interface. These rules implicitly allow the traffic to flow on the loopback interface where
the other 3XXXX ports are used.
iptables -A INPUT -i eth0 -d 138.120.203.13 -p tcp --dport 1025:1098 -j DROP
....................................................................................................................................................................................................................................
2-35
February 2011
Configuring the file transfer properties of the 1354 RM-PhM

server
....................................................................................................................................................................................................................................
Configuring the file transfer properties of the 1354 RM-PhM

server
Use this procedure to specify the file transfer properties of the 1354 RM-PhM server:
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology View, choose Admin > Settings.
The Settings window is displayed.
...................................................................................................................................................................................................
To view/change file transfer properties, click the System Settings tab, then the File
Transfer tab.
The file transfer properties are displayed, showing the current settings, and providing an
area to change the settings.
Make changes to the properties as desired. Any changes that you make do not take effect
until the 1354 RM-PhM server is restarted. Specify the TFTP root directory.
...................................................................................................................................................................................................
Click OK to save the changes and close the window. Click Cancel to close the window
without saving changes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-36
February 2011
....................................................................................................................................................................................................................................

Use this procedure to specify whether the NEs can use this server as an NTP server. This
option causes network elements that are discovered by the 1354 RM-PhM to add the 1354
RM-PhM server address to their NTP servers list. This option does not install an NTP
server onto the 1354 RM-PhM server machine, nor does it check to see if there is a valid
NTP server already installed. To install and activate an NTP server on the 1354 RM-PhM
server machine, contact your system administrator.
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology View, choose Admin > Settings.
...................................................................................................................................................................................................
Click the System Settings tab, then the NTP tab.

The NTP properties are displayed, showing the current setting. To change the setting,
check or uncheck the Use this server as the NTP server check box.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Changes to the NTP properties do not take effect until after the 1354 RM-PhM server has
been restarted. To restart the 1354 RM-PhM server, refer to Starting and stopping the
server and client (p. 2-24)
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-37
February 2011
....................................................................................................................................................................................................................................

Use this procedure to specify the NTP servers for the NEs.
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, select the network element(s) for which you
want to specify NTP properties software, and choose Admin>NE NTP Table.
The NE NTP Settings window is displayed, with the selected network element(s) listed.
Alternatively, if you select no network elements in the topology view, the NE NTP
Settings window lists all of the network elements.
...................................................................................................................................................................................................
In the list of NEs, select the NE(s) for which you want to specify NTP settings, and then
click the magnifying-glass icon.
The NTP Details window for the selected NE(s) is displayed.
...................................................................................................................................................................................................
Add or remove an NTP server for the selected NE(s).
To add an NTP server, click Add Server.

In the pop-up box, specify the IP address of the desired NTP server, and then click
OK.
To add the NTP server on the 1354 RM-PhM server, click Add PhM as NTP Server.
To delete an NTP server, select the server in the list and click Remove Server.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-38
February 2011
....................................................................................................................................................................................................................................

This section provides procedures for backing up and restoring the 1354 RM-PhM
database on Linux or Solaris x86/x64 or Windows. The 1354 RM-PhM uses a MySQL
database.
For information on the MySQL database, and tools and commands for administering the
MySQL database, launch a browser and go to www.mysql.com.
This sections covers the following:
1354 RM-PhM database backup (p. 2-40)
1354 RM-PhM database restore (p. 2-42)

Recovering from file corruption without having to restore from a backup (p. 2-43)
Performing a server switch-over (p. 2-44)
(p. 2-45)
....................................................................................................................................................................................................................................
2-39
February 2011
....................................................................................................................................................................................................................................

Use the following procedure to back up a database on either Linux or Solaris x86/x64 or
Windows.
To back up the 1354 RM-PhM database
...................................................................................................................................................................................................
From the 1354 RM-PhM, choose Admin>PhM Status.

The PhM Status window is displayed.
...................................................................................................................................................................................................
Click the Back up Database button.

The database is backed-up according to the default attributes (see To configure 1354
RM-PhM database backup attributes (p. 2-40)).
E...................................................................................................................................................................................................
N D O F S T E P S
To configure 1354 RM-PhM database backup attributes
Use this procedure to specify where to put 1354 RM-PhM database backup files, and to
schedule recurring backups.
...................................................................................................................................................................................................
From the 1354 RM-PhM, choose Admin>Settings.

The 1354 RM-PhM Settings window is displayed.
...................................................................................................................................................................................................
Select the System Settings tab and click the 1354 Database Backup tab.
The database backup attributes are displayed.
...................................................................................................................................................................................................
Specify the backup directory. Click the folder icon and choose a directory from the
drop-down list. Click Select.
...................................................................................................................................................................................................
Specify the maximum number of backups to perform by adjusting the Maximum Number
of Backups slider bar. By sliding it all the way to the left, the maximum number of
backups is set to unlimited.
...................................................................................................................................................................................................
To turn on scheduled backups, check the Enable scheduled backup of the server
database check box.
....................................................................................................................................................................................................................................
2-40
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To edit the backup schedule, check the Change backup schedule check box, and then
specify the days and time that backups are to be performed.
To specify the current time, click the Now button.
...................................................................................................................................................................................................
Click OK.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-41
February 2011
....................................................................................................................................................................................................................................

Use the following procedure to restore a database for a server on either Linux or Solaris
x86/x64 or Windows.
Note: Before performing a database restore, shut down the PhM on both servers (in a
redundant configuration), but leave the database running. To shut down the PhM see
Stopping the 1354 RM-PhM server on Linux or Solaris x86/x64 (p. 2-29) or
Stopping the 1354 RM-PhM server on Microsoft Windows (p. 2-32).
To restore the database on a stand-alone or active server
...................................................................................................................................................................................................
Stop the PhM on the server you wish to restore.

...................................................................................................................................................................................................
From the install_dir/bin directory, run:

for Windows, dbrestore.batbackup_path_and_filename
for Linux or Solaris x86/x64, dbrestore.shbackup_path_and_filename
where backup_path_and_filename is the path to and name of the file from which to
restore.
Example for Windows:
cd "C:\Program Files\PhM\bin"
.\dbrestore.bat backup-file.sql
Example for Linux or Solaris x86/x64:
cd /opt/Phm/bin
./dbrestore.sh backup-file.sql
...................................................................................................................................................................................................
If this is a redundant server configuration, after the database is restored, synchronize the
servers' databases by executing:
On Linux or Solaris x86/x64 - ./tropxadmin.sh synctoprimaryotherserver
- where otherserver is the server that did not get restored in the previous step.
On Windows - tropxadmin.bat synctoprimaryotherserver
- where otherserver is the server that did not get restored in the previous step.
...................................................................................................................................................................................................
Restart the PhM on both servers (in a redundant configuration).
....................................................................................................................................................................................................................................
2-42
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Ensure that the 1354 RM-PhM has discovered all of the NEs. For NEs that are not
automatically rediscovered, manually rediscover them.
E...................................................................................................................................................................................................
N D O F S T E P S
Recovering from file corruption without having to restore

from a backup
The file system can become corrupted if the server is not shut down properly, such as in a
power failure, or due to hardware failure. If the system is Linux or Solaris x86/x64-based,
your system administrator can perform a fsck: fsck -y. On windows your system
administrator can perform a scandisk.
If your PhM server cannot communicate with its database, you get errors in the PhM trace
log (/opt/Phm/log/phm_trace.log) such as General error: Got error 127 from table
handler; nested exception is: java.sql.SQLException: General error: Got error 127 from
table handler. This indicates database file corruption. Contact your service
representative.
....................................................................................................................................................................................................................................
2-43
February 2011
....................................................................................................................................................................................................................................

Use this procedure to cause the standby server to become the active server. Before
performing a server activity switch, the system checks to ensure that the standby server is
in service and capable of becoming the active server. If the standby server is capable, the
switch-over is performed. If the switch-over is not capable, the switch-over is not
performed. When the servers switch activity, the following actions occur:
The standby server becomes the active and the original active becomes standby, as
verified by using the Admin>PhM Status window to view the server status on both
servers.
The new active server registers with each network elements as a trap destination.
The original active server unregisters itself as trap destination on all network
elements.
Database updates made to the new active server are replicated to the standby server.
MCP clients are logged out of the original active server and must be manually
restarted on the new active server.
To perform a server switch-over using the MCP

...................................................................................................................................................................................................
In the 1354 RM-PhM, choose Admin>PhM Status.

The PhM Status window is displayed.
...................................................................................................................................................................................................
Click the Switch button.

The servers switch activity.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-44
February 2011
1696 ROADM and 1830 PSS network element database
backup and restore
....................................................................................................................................................................................................................................
1696 ROADM and 1830 PSS network element

database backup and restore
The 1354 RM-PhM network element database backup and restore facility allows you to
backup and restore the database of 1696 ROADM and 1830 PSS network elements that
are being managed by the 1354 RM-PhM.
Before you perform a network element database backup or restore, you need to specify
the attributes which the 1354 RM-PhM uses to perform the action.
To back up a network element database
...................................................................................................................................................................................................
From the 1354 RM-PhM, select the network element(s) that you want to back up.
...................................................................................................................................................................................................
Choose Maintenance>NE Database Backup and Restore.

The Backup and Restore window is displayed with the selected network element(s) listed
along with its (their) attributes. If no network elements were selected, all of them are
listed.
...................................................................................................................................................................................................
If necessary, edit the backup attributes. Repeat this for each network element.
1. Select the network element and click the magnifying glass icon.
The Backup Properties window is displayed.
2. Specify the file transfer protocol to be used.
3. Specify the backup server. If you wish to use the 1354 RM-PhM server as the backup
host, check the Use this PhM Server As Backup Host check box.. This is the
recommended option.
If the backup server is on machine other than the 1354 RM-PhM server, make sure the
check box is unchecked, and then specify the Backup Host IP Address of the server
where the backup file is to be stored.
4. Specify the user settings. If you wish to use the default user settings, check the Use
Default User Settings check box. This is the recommended option.
If you wish to use different user settings from the default, uncheck the check box, and
specify the following attributes:
Backup File Transfer User Id
Backup File Transfer Password

TFTP root directory
NE backup root directory
....................................................................................................................................................................................................................................
2-45
February 2011
backup and restore
....................................................................................................................................................................................................................................
5. Specify the backup directory. If you wish to use the default settings, check the Use
Default Backup Directory check box. This is the recommended option.
If you wish to specify a different backup directory path from the default, uncheck the
check box, and specify the desired backup directory in the Backup Directory field.
6. Click OK.
...................................................................................................................................................................................................
To start the backup, select the network element(s) to be backed up and click
Action>Backup or click the Backup icon.
The 1354 RM-PhM initiates the backup and provides status and progress feedback in the
lower pane of the Backup and Restore window.
The backup file is stored in the specified directory with a filename in the form of:
NEName_SoftwareGenericIdentifier_YYYY-MM-DDD_HH-MM-SS.bak
For example:
NE001_01AAA-V-04.00-111_2006-01-17_13-05-12.bak
...................................................................................................................................................................................................
When you are finished, close the Backup and Restore window.
Note: Restoring a database causes the NE to reset and is service affecting.
E...................................................................................................................................................................................................
N D O F S T E P S
To schedule a back up of a network element database

...................................................................................................................................................................................................
If desired, set up the scheduled backup attributes. Repeat this step for each network
element.
1. Select the network element and click the clock icon.
The Scheduled Backup Properties window is displayed.
2. Check the Enable Scheduled Backup check box.
3. Use the calendar GUI to specify the attributes for the scheduled backup.
4. Click OK.
Note: Scheduled database backups are suspended while the NE is undergoing a
software upgrade.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-46
February 2011
backup and restore
....................................................................................................................................................................................................................................
To restore a network element database
Note: The NE must be deleted and re-added after an NE restore (see To rediscover a
network element with a new database (p. 3-10)).
Network elements must be restored individually. You cannot multi-select network
elements and restore them all with a single function. You can have multiple network
elements in the Backup and Restore window, but you must initiate the restore operation
one at a time.
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, select the network element(s) that you want to
restore.
...................................................................................................................................................................................................
Choose Maintenance>NE Database Backup and Restore.

The Backup and Restore window is displayed.
...................................................................................................................................................................................................
Select the network element to be restored and click Action>Restore or click the Restore
icon.
The Select a database backup file window is displayed.
If the Backup Server is not the 1354 RM-PhM server, then enter a FTP username and
password and click Connect.
No username and password is required if the Backup Server is the 1354 RM-PhM server.
The 1354 RM-PhM displays the file structure.
...................................................................................................................................................................................................
Locate and select the file from which you wish to restore the database.
...................................................................................................................................................................................................
Click the Select button.

The 1354 RM-PhM initiates the restore and provides status and progress feedback in the
lower pane of the Backup and Restore window.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-47
February 2011
....................................................................................................................................................................................................................................

The PM Archive Setting feature allows an external tool to process the 1354 RM-PhM
data. The 1354 RM-PhM collects PM data from the NEs every 15 minutes. If Create PM
CSV files is enabled (see Figure 2-6, System Settings dialog (p. 2-49)), the data will
also be written to a CSV file (which can be opened by spreadsheet programs such as
Microsoft Excel). One CSV file is produced for each NE every 15 minutes. A summary
1-day CSV file is produced at 12AM GMT every day. Once the CSV file is produced, the
1354 RM-PhM can zip and send it to a remote site via FTP based on the settings below.
If Create SLA CVS files is enabled (see Figure 2-6, System Settings dialog
(p. 2-49)), the PM system will produce SLA CVS (Comma Separated Value) files
containing SLA (Service Level Agreement) data. A CSV file will be produced every 15
minutes and will contain an estimate of the percentage availability for each optical
service. These files can be opened by common spreadsheet programs such as Microsoft
Excel.
Configuring the PM Archive Settings
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, choose Admin > Settings. The Settings window
is displayed.
...................................................................................................................................................................................................
In the Settings window, click the System Settings tab, and then click the PM tab (see
Figure 2-6, System Settings dialog (p. 2-49)).
....................................................................................................................................................................................................................................
2-48
February 2011
....................................................................................................................................................................................................................................
Figure 2-6 System Settings dialog
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-49
February 2011
....................................................................................................................................................................................................................................

The purpose of this feature is to convert alarms generated by the PhM to SNMP
notification traps and send the traps to a list of configured trap destinations. The feature
can be configured to send only certain types of alarms or no alarms at all:
Alarms generated for internal PhM conditions, and/or
Alarms generated based on raise and clear notification traps from network elements.
Each alarm trap can be sent to up to 10 destinations (SNMP Managers). The feature is
disabled by default upon PhM installation and requires a user in the administrators role
to enable it.
Enabling/disabling SNMP trap sending
...................................................................................................................................................................................................
is displayed.
...................................................................................................................................................................................................
In the Settings window, click the System Settings tab, and then click the SNMP Trap
Sender tab.
....................................................................................................................................................................................................................................
2-50
February 2011
....................................................................................................................................................................................................................................
Result: The SNMP Trap Destinations table is displayed (see Figure 2-7, SNMP Trap
Destinations table (p. 2-51)).

Figure 2-7 SNMP Trap Destinations table
...................................................................................................................................................................................................
Enable the desired trap sending option by checking the appropriate Enable trap sending
box.
Result: When the feature is enabled, an admin privileged user can configure the
destinations to which the traps will be forwarded. The SNMP trap destinations table
defines particular columns for each of the configuration information required to
forward Traps.
Note: The table cannot be edited if the feature is disabled.
....................................................................................................................................................................................................................................
2-51
February 2011
....................................................................................................................................................................................................................................
The columns of the SNMP Trap Destinations table are defined as follows:
Use: The traps are forwarded only to those destinations for which the Use
Destination check box is enabled. All rows are validated on clicking the OK
button. In case of any violations in the data entered against the expected data, the
user would be prompted with an error dialog box containing an appropriate error
message.
Host: Define the destination address to which a trap will be forwarded. This can
be either an IPV4 address or a destination host name. When the Use Destination
check box is checked, this address cannot be empty nor can it contain 2
consecutive colons ::.
Port: Define the destination port to which the traps are to be forwarded. By default
this column is set to port 162. When the Use Destination check box is checked,
this column must be an integer between 1 and 65535.
Severity: Select the desired minimum severity of the faults that need to be
forwarded as SNMP traps. By default, Major severity is selected. This means
when enabled, by default, all Major and Critical faults generated by the 1354
RM-PhM would be forwarded as SNMP traps.
Version: Specifies the SNMP version to use when formatting the trap. The default
is v2c. For SNMP v3, traps are always sent with both authentication and privacy
enabled.
Community: Defines the destination trap community string that the trap receiver is
expecting. By default the trap community is set to public. When the Use
Address check box is checked, this column must be a non-null string and it cannot
contain 2 consecutive colons ::. The community string is ignored if the SNMP
version is v3.
SNMP v3 configurable settings for each trap destination:
V3 UserName = User Name (default v3DefaultUser)
V3 AuthPassword = Authentication password (default v3DefAuthPass)
V3 PrivPassword = Privacy Password (default v3DefPrivPass)
SNMP v3 fixed settings (these are the same for every trap destination and cannot
be changed):
V3 AuthProtocol = Authentication Protocol (default HMAC-MD5)

V3 PrivProtocol = Privacy Protcol (default AES128)
EngineId = Engine ID: a 12 byte id structured as follows:First 8 btyes always

= 0x00001d3b000000a1Final 4 bytes = IP address of SNMP agent on PhM
server that sent the trap (e.g., EngineId=0x00001d3b000000a101020304
means that the PhM server that sent the trap has IP address 1.2.3.4.)
...................................................................................................................................................................................................
Click OK.
....................................................................................................................................................................................................................................
2-52
February 2011
....................................................................................................................................................................................................................................
Result: All the configuration changes get applied immediately upon clicking the OK
button. All these changes are applied at a System wide level. The preferences are
persistent across client and server restarts.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-53
February 2011
....................................................................................................................................................................................................................................

RADIUS (remote authentication dial-in user service) is a security protocol designed to
prohibit unauthorized access to the network. It does so by providing centralized userid
and password authentication for all of the 1354 RM-PhM servers in the network.
RADIUS uses a distributed client/server architecture. In a 1696 ROADM and 1830 PSS
network, 1354 RM-PhM servers run a RADIUS client and send authorization requests to
a central RADIUS server. The RADIUS server authenticates the data against the
authentication system it is configured to use (local database, SecurID, etc.) to determine
whether the user is authorized to use the system.
The RADIUS feature does not use an encryption key. Instead, it uses a shared secret a
text string that needs to be provisioned on both the RADIUS server and client. The shared
secret string is used to encrypt data between the RADIUS server and client. The 1354
RM-PhM installation wizard does not include a RADIUS server. To install a RADIUS
server, consult your system administrator.
How authentication works on a RADIUS-protected 1354 RM-PhM server
The following steps outline the processes that occur when a user attempts to login to a
1354 RM-PhM server on which RADIUS authentication is enabled:
1. The user is prompted to enter a username and password.
2. After the user enters a username and password, the password is encrypted and is sent,
along with the username, to the RADIUS server for authentication.
3. The RADIUS server checks that the information is correct against the authentication
system it is configured to use (local database, SecurID, etc.)
4. The RADIUS server sends a response to the RADIUS client on the 1354 RM-PhM
server.
The possible responses are as follows:
Accept: The userid and password are authenticated. In addition to the accept
response, the privilege level (admin, provisioner, or observer) associated with the
userid is also sent to the 1354 RM-PhM server. The user is logged into the 1354
RM-PhM server with the specified privileges.
Note: The service privilege role is not authenticated by RADIUS. It is always
authenticated locally by the PhM.
Reject: The userid and password is not authenticated. The user is prompted to
reenter the username and password. In some instances, access is denied.
....................................................................................................................................................................................................................................
2-54
February 2011
....................................................................................................................................................................................................................................
Configuring a RADIUS server
This section describes how to configure a RADIUS server to provide user authentication
for the 1354 RM-PhM servers in the network. Procedures are included for the
Steel-Belted RADIUS server, FreeRADIUS server, and the Windows IAS (Internet
Authentication Service) server.
Note: You can use RADIUS servers from other vendors to provide authentication.
Refer to the documentation for your RADIUS server for configuration information.
You can configure each 1354 RM-PhM server to use up to two RADIUS servers, indexed
by number (1 or 2). On 1354 RM-PhM servers on which two RADIUS servers are
configured and enabled, the server first queries the server configured with index number
1. It queries the second server (index number 2) only if the first server does not respond
after the maximum number of time-outs and retries that are configured on the server have
been exceeded.
Table 2-3
Task list for configuring and using a RADIUS authentication server
Task
Procedure
Configure the RADIUS server and specify the

1354 RM-PhM servers and users that use the
server for authentication.
Use one of the following procedures,

depending on your RADIUS server:
Configure the 1354 RM-PhM servers to use

the RADIUS server and configure its
attributes.
To configure a Steel-Belted RADIUS

server to provide RADIUS authentication
for 1354 RM-PhM servers (p. 2-55)
To configure a FreeRADIUS server to

provide RADIUS authentication for 1354
RM-PhM servers (p. 2-58)
To configure a Windows 2000 IAS server

to provide RADIUS authentication for
1354 RM-PhM servers (p. 2-66)
To configure a Windows 2003 IAS server

to provide RADIUS authentication for
1354 RM-PhM servers (p. 2-69)
To configure the 1354 RM-PhM server to use

a RADIUS server (p. 2-72)
To configure a Steel-Belted RADIUS server to provide RADIUS authentication for

1354 RM-PhM servers
...................................................................................................................................................................................................
Create a dictionary file named Tropx.dct in the same directory as the Steel-Belted
RADIUS service (usually c:\radius\service). The contents of the file are as follows:
....................................................................................................................................................................................................................................
2-55
February 2011
....................................................................................................................................................................................................................................
###################################################################
Tropx.dct - Tropx dictionary
#
# (See README.DCT for more details on the format of this file)
####################################################################
Use the Radius specification attributes in lieu of the Tropx ones
#
@radius.dct
#
# Define additional Tropx parameters
# (add Tropx specific attributes below)
MACRO Tropx-Attr(type,syntax) 26 [vid=7483 type1=%type% len1=+2 data=
%syntax%]
ATTRIBUTE
Tropx-NMS-Role
Tropx-Attr(2, integer) r
VALUE
Tropx-NMS-Role
Tropx-NMS-Observer
0
VALUE
Tropx-NMS-Role
Tropx-NMS-Provisioner
1
VALUE
Tropx-NMS-Role
Tropx-NMS-Administrator 2
###################################################################
Tropx.dct - Tropx dictionary
###################################################################
...................................................................................................................................................................................................
Edit the vendor.ini file and add the Tropx-specific information in the [Vendor-Product
Identification] section:
[Vendor-Product Identification]
vendor-product = Tropx
dictionary = Tropx
ignore-ports = no
port-number-usage = per-port-type
help-id =
...................................................................................................................................................................................................
Edit the dictiona.dcm file and add the reference to the new dictionary file at the end of the
file:
@Tropx.dct
...................................................................................................................................................................................................
Stop and start the Steel-Belted RADIUS service to load the new/edited configuration
files.
....................................................................................................................................................................................................................................
2-56
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Add the 1354 RM-PhM as a RADIUS client:

1. Launch the Steel-Belted RADIUS Administrator
2. Select RADIUS Clients and click the Add button. The Add RADIUS client dialog is
displayed.
3. Enter the attributes for the 1354 RM-PhM (Name, Description, IP Address, Shared
secret). Select Tropx as the Make/Model.
4. Click OK.
Figure 2-8 The Add RADIUS Client dialog
...................................................................................................................................................................................................
Use the Steel-Belted RADIUS Administrator to add the user accounts that are able to
access the 1354 RM-PhM added in Step 5.
1. Select Users and click the Add button. The Add Native User dialog is displayed.
2. Enter the Name, Description (optional), and Password for the user.
3. Specify the role associated with the userid in the User-specific configuration area. The
userid will be granted observer status if no role is configured:
a. Click on the Return list tab and click on the Add button
b. Select Tropx-NMS-Role in the Attributes field.
c. In the Value field, select the role to assign to the user and click the Add button.
4. Click OK.
....................................................................................................................................................................................................................................
2-57
February 2011
....................................................................................................................................................................................................................................
Figure 2-9 The Add Native User dialog
E...................................................................................................................................................................................................
N D O F S T E P S
To configure a FreeRADIUS server to provide RADIUS authentication for 1354

RM-PhM servers
...................................................................................................................................................................................................
Log in as the root user on the server where the FreeRADIUS server is installed.
...................................................................................................................................................................................................
cd /etc/raddb
...................................................................................................................................................................................................
Edit the three files listed below to integrate the contents shown for each, changing the ip
addresses, server names, userids, and passwords as required:
/etc/raddb/dictionary
#
# This is the master dictionary file, which references the
# pre-defined dictionary files included with the server.
#
# Any new/changed attributes MUST be placed in this file, as
# the pre-defined dictionaries SHOULD NOT be edited.
#
# $Id: dictionary.in,v 1.4 2004/04/14 15:26:20 aland Exp $
#
....................................................................................................................................................................................................................................
2-58
February 2011
....................................................................................................................................................................................................................................
#
# The filename given here should be an absolute path.
# $INCLUDE /usr/share/freeradius/dictionary
#
# Place additional attributes or $INCLUDEs here. They will
# over-ride the definitions in the pre-defined dictionaries.
#
# See the 'man' page for 'dictionary' for information on
# the format of the dictionary files.
#
# If you want to add entries to the dictionary file,
# which are NOT going to be placed in a RADIUS packet,
# add them here. The numbers you pick should be between
# 3000 and 4000.
#
# ATTRIBUTE My-Local-String 3000 string
# ATTRIBUTE My-Local-IPAddr 3001 ipaddr
# ATTRIBUTE My-Local-Integer 3002 integer VENDOR Tropic 7483
ATTRIBUTE Tropic-TRX-Role 1 integer Tropic
VALUE Tropic-TRX-Role Tropic-TRX-Observer 0
VALUE Tropic-TRX-Role Tropic-TRX-Provisioner 1
VALUE Tropic-TRX-Role Tropic-TRX-Administrator 2
ATTRIBUTE Tropic-NMS-Role 2 integer Tropic
VALUE Tropic-NMS-Role Tropic-NMS-Observer 0
VALUE Tropic-NMS-Role Tropic-NMS-Provisioner 1
VALUE Tropic-NMS-Role Tropic-NMS-Administrator 2
/etc/raddb/users
#
# Please read the documentation file ../doc/processing_users_file,
# or 'man 5 users' (after installing the server) for more information.
# This file contains authentication security and configuration # information for each
user. Accounting requests are NOT processed
# through this file. Instead, see 'acct_users', in this directory.
# The first field is the user's name and can be up to
# 253 characters in length. This is followed (on the same line) with
# the list of authentication requirements for that user. This can
# include password, comm server name, comm server port number, protocol
# type (perhaps set by the "hints" file), and huntgroup name (set by # the
"huntgroups" file).
# If you are not sure why a particular reply is being sent by the
# server, then run the server in debugging mode (radiusd -X), and
# you will see which entries in this file are matched.
# When an authentication request is received from the comm server,
....................................................................................................................................................................................................................................
2-59
February 2011
....................................................................................................................................................................................................................................
# these values are tested. Only the first match is used unless the
# "Fall-Through" variable is set to "Yes".
# A special user named "DEFAULT" matches on all usernames.
# You can have several DEFAULT entries. All entries are processed
# in the order they appear in this file. The first entry that
# matches the login-request will stop processing unless you use
# the Fall-Through variable.
# If you use the database support to turn this file into a .db or .dbm
# file, the DEFAULT entries _have_ to be at the end of this file and
# you can't have multiple entries for one username.
# You don't need to specify a password if you set Auth-Type += System
# on the list of authentication requirements. The RADIUS server # will then check the
system password file.
# Indented (with the tab character) lines following the first
# line indicate the configuration values to be passed back to
# the comm server to allow the initiation of a user session.
# This can include things like the PPP configuration values
# or the host to log the user onto.
# You can include another `users' file with `$INCLUDE users.other'
#
# For a list of RADIUS attributes, and links to their definitions,
# see:
# http://www.freeradius.org/rfc/attributes.html
# Deny access for a specific user. Note that this entry MUST
# be before any other 'Auth-Type' attribute which results in the user
# being authenticated.
# Note that there is NO 'Fall-Through' attribute, so the user will not
# be given any additional resources.
# lameuser Auth-Type := Reject
# Reply-Message = "Your account has been disabled."
#
# 1354 RM-PhM Users
#admin Auth-Type := Local, User-Password == "qweQWE!@
#124" Tropic-NMS-Role = Tropic-NMS-Administrator
admin2 Auth-Type := Local, User-Password == "qweQWE!@
#124" Tropic-NMS-Role = Tropic-NMS-Administrator
provisioner Auth-Type := Local, User-Password == "qweQWE!@ #124"
Tropic-NMS-Role = Tropic-NMS-Provisioner
prov2ems Auth-Type := Local, User-Password == "qweQWE!@#124"
Tropic-NMS-Role = Tropic-NMS-Provisioner
observer Auth-Type := Local, User-Password == "qweQWE!@#124"
Tropic-NMS-Role = Tropic-NMS-Observer
observer2 Auth-Type := Local, User-Password == "qweQWE!@#124"
....................................................................................................................................................................................................................................
2-60
February 2011
....................................................................................................................................................................................................................................
Tropic-NMS-Role = Tropic-NMS-Observer
# 1696 OADM Users
# admin Auth-Type := Local, User-Password == "qweQWE!@ #125"
Tropic-TRX-Role = Tropic-TRX-Administrator
admin2 Auth-Type := Local, User-Password == "qweQWE!@#125"
Tropic-TRX-Role = Tropic-TRX-Administrator provisioner Auth-Type := Local,
User-Password == "qweQWE!@#125"
Tropic-TRX-Role = Tropic-TRX-Provisioner
prov2 Auth-Type := Local, User-Password == "qweQWE!@#125"
Tropic-TRX-Role = Tropic-TRX-Provisioner
observer Auth-Type := Local, User-Password == "qweQWE!@#125"
Tropic-TRX-Role = Tropic-TRX-Observer
obs2 Auth-Type := Local, User-Password == "qweQWE!@#125"
Tropic-TRX-Role = Tropic-TRX-Observer
# Deny access for a group of users.
# Note that there is NO 'Fall-Through' attribute, so the user will not
# be given any additional resources.
#DEFAULT Group == "disabled", Auth-Type := Reject
# Reply-Message = "Your account has been disabled."
# This is a complete entry for "steve". Note that there is no Fall-Through
# entry so that no DEFAULT entry will be used, and the user will NOT
# get any attributes in addition to the ones listed here.
# #steve Auth-Type := Local, User-Password == "testing"
# Service-Type = Framed-User,
# Framed-Protocol = PPP,
# Framed-IP-Address = 172.16.3.33,
# Framed-IP-Netmask = 255.255.255.0,
# Framed-Routing = Broadcast-Listen,
# Framed-Filter-Id = "std.ppp",
# Framed-MTU = 1500,
# Framed-Compression = Van-Jacobsen-TCP-IP
# This is an entry for a user with a space in their name.
# Note the double quotes surrounding the name.
#"John Doe" Auth-Type := Local, User-Password == "hello"
# Reply-Message = "Hello, %u"
# Dial user back and telnet to the default host for that port
#Deg Auth-Type := Local, User-Password == "ge55ged"
# Service-Type = Callback-Login-User,
# Login-IP-Host = 0.0.0.0,
# Callback-Number = "9,5551212",
# Login-Service = Telnet,
# Login-TCP-Port = Telnet
# Another complete entry. After the user "dialbk" has logged in, the
....................................................................................................................................................................................................................................
2-61
February 2011
....................................................................................................................................................................................................................................
# connection will be broken and the user will be dialed back after which
# he will get a connection to the host "timeshare1".
#dialbk Auth-Type := Local, User-Password == "callme"
# Service-Type = Callback-Login-User,
# Login-IP-Host = timeshare1,
# Login-Service = PortMaster,
# Callback-Number = "9,1-800-555-1212"
# user "swilson" will only get a static IP number if he logs in with
# a framed protocol on a terminal server in Alphen (see the huntgroups file).
# Note that by setting "Fall-Through", other attributes will be added from # the
following DEFAULT entries
#swilson Service-Type == Framed-User, Huntgroup-Name == "alphen"
# Framed-IP-Address = 192.168.1.65,
# Fall-Through = Yes
# If the user logs in as 'username.shell', then authenticate them
# against the system database, give them shell access, and stop processing
# the rest of the file.
#DEFAULT Suffix == ".shell", Auth-Type := System
# Service-Type = Login-User,
# Login-Service = Telnet,
# Login-IP-Host = your.shell.machine
# The rest of this file contains the several DEFAULT entries.
# DEFAULT entries match with all login names.
# Note that DEFAULT entries can also Fall-Through (see first entry).
# A name-value pair from a DEFAULT entry will _NEVER_ override
# an already existing name-value pair.
#
# First setup all accounts to be checked against the UNIX /etc/passwd. # (Unless a
password was already given earlier in this file).
# DEFAULT Auth-Type = System Fall-Through = 1
# Set up different IP address pools for the terminal servers.
# Note that the "+" behind the IP address means that this is the "base"
# IP address. The Port-Id (S0, S1 etc) will be added to it.
#DEFAULT Service-Type == Framed-User, Huntgroup-Name == "alphen"
# Framed-IP-Address = 192.168.1.32+,
#DEFAULT Service-Type == Framed-User, Huntgroup-Name == "delft"
# Framed-IP-Address = 192.168.2.32+,
# Defaults for all framed connections.
# DEFAULT Service-Type == Framed-User Framed-IP-Address = 255.255.255.254,
Framed-MTU = 576,
Service-Type = Framed-User,
....................................................................................................................................................................................................................................
2-62
February 2011
....................................................................................................................................................................................................................................
Fall-Through = Yes
# Default for PPP: dynamic IP address, PPP mode, VJ-compression.
# NOTE: we do not use Hint = "PPP", since PPP might also be auto-detected
# by the terminal server in which case there may not be a "P" suffix.
# The terminal server sends "Framed-Protocol = PPP" for auto PPP.
# DEFAULT Framed-Protocol == PPP Framed-Protocol = PPP, Framed-Compression
= Van-Jacobson-TCP-IP
# Default for CSLIP: dynamic IP address, SLIP mode, VJ-compression.
# DEFAULT Hint == "CSLIP"
Framed-Protocol = SLIP,
Framed-Compression = Van-Jacobson-TCP-IP
# Default for SLIP: dynamic IP address, SLIP mode.
# DEFAULT Hint == "SLIP" Framed-Protocol = SLIP
# Last default: rlogin to our main server.
#DEFAULT
# Service-Type = Login-User,
# Login-Service = Rlogin,
# Login-IP-Host = shellbox.ispdomain.com
#
# Last default: shell on the local terminal server.
#
# # DEFAULT
# Service-Type = Shell-User
# On no match, the user is denied access.
/etc/raddb/clients.conf
#
# clients.conf - client configuration directives
#
# Definition of a RADIUS client (usually a NAS).
#
# The information given here over rides anything given in the
# 'clients' file, or in the 'naslist' file. The configuration here
# contains all of the information from those two files, and allows
# for more configuration items.
#
# The "shortname" is be used for logging. The "nastype", "login" and
# "password" fields are mainly used for checkrad and are optional.
#
# Defines a RADIUS client. The format is 'client [hostname|ip-address]'
#
# '127.0.0.1' is another name for 'localhost'. It is enabled by default,
# to allow testing of the server after an initial installation. If you
....................................................................................................................................................................................................................................
2-63
February 2011
....................................................................................................................................................................................................................................
# are not going to be permitting RADIUS queries from localhost, we suggest

# that you delete, or comment out, this entry.
# client 127.0.0.1 {
#
# The shared secret use to "encrypt" and "sign" packets between
# the NAS and FreeRADIUS. You MUST change this secret from the
# default, otherwise it's not a secret any more!
#
# The secret can be any string, up to 32 characters in length.
# secret = testing123
#
# The short name is used as an alias for the fully qualified
# domain name, or the IP address.
# shortname = localhost
#
# the following three fields are optional, but may be used by
# checkrad.pl for simultaneous use checks
# The nastype tells 'checkrad.pl' which NAS-specific method to
# use to query the NAS for simultaneous use.
#
# Permitted NAS types are:
# cisco
# computone
# livingston
# max40xx
# multitech
# netserver
# pathras
# patton
# portslave
# tc
# usrhiper
# other
# for all other types
# nastype = other
# localhost isn't usually a NAS...
#
# The following two configurations are for future use.
# The 'naspasswd' file is currently used to store the NAS
# login name and password, which is used by checkrad.pl
# when querying the NAS for simultaneous use.
#
....................................................................................................................................................................................................................................
2-64
February 2011
....................................................................................................................................................................................................................................
# login = !root
# password = someadminpas }
#client some.host.org {
# secret = testing123
# shortname = localhost
#}
# You can now specify one secret for a network of clients.
# When a client request comes in, the BEST match is chosen.
# i.e. The entry from the smallest possible network.
#
#client 192.168.0.0/24 {
# secret = testing123-1
# shortname = private-network-1
#}
#te
#client 192.168.0.0/16 {
# secret = testing123-2
# shortname = private-network-2
#}
# RADIUS client for the 1354 RM-PhM server
# client 138.120.203.14 {
# secret and password are mapped through the "secrets" file. secret = testingEMS
shortname = nmsx8
# checkrad.pl for simultaneous usage checks
# nastype = other
# login = !root
#password = someadminpas } client 138.120.203.10 {
# secret and password are mapped through the "secrets" file. secret = testingEMS
shortname = nmsx10
# nastype = other
# login = !root
#password = someadminpas }
# RADIUS client for the 1696 ROADM network elements
#client 10.27.0.0/16 {
# secret and password are mapped through the "secrets" file. secret = testingNE
shortname = 1696R
# nastype = other
# login = !root
....................................................................................................................................................................................................................................
2-65
February 2011
....................................................................................................................................................................................................................................
#password = someadminpas }
...................................................................................................................................................................................................
Stop radius using the following:

/etc/init.d/radiusd stop
...................................................................................................................................................................................................
Start radius using the following:

/etc/init.d/radiusd start
E...................................................................................................................................................................................................
N D O F S T E P S
To configure a Windows 2000 IAS server to provide RADIUS authentication for 1354
RM-PhM servers
...................................................................................................................................................................................................
Install the Windows 2000 IAS (Internet Authentication Service) on your Windows 2000
server. Refer to the product documentation for details.
...................................................................................................................................................................................................
Create the following three groups on the IAS server (one for each of the three privilege
levels on the 1354 RM-PhM server). Create user accounts and add them to the groups.
Note: IAS RADIUS authentication defaults account authentication to the domain that
the server is a member of. Therefore logins without an explicit domain included in the
username must have an account in the domain the server is a member of.
If you are not using an account from the server default domain (e.g. a local server
account for a stand-alone server), you must specify the domain/hostname in the
username at login (e.g. for user myaccount, enter winserv1\myaccount at login, where
winserv1 is the hostname of a stand-alone server).
Platform
Privilege level
Recommended group name
1354 RM-PhM server
Admin
1354 RM-PhM Admin
Provisioner
1354 RM-PhM Provisioner
Observer
1354 RM-PhM Observer
...................................................................................................................................................................................................
Select Start > Programs > Administrative Tools > Internet Authentication Service.
....................................................................................................................................................................................................................................
2-66
February 2011
....................................................................................................................................................................................................................................
If Administrative Tools does not show up under Programs, click Start, select Run, enter
mmc, and click OK. On the Console window that appeared, click File, select Add
Snap-in, click Add, and select Internet Authentication Service from the list. Click Add,
then OK.
...................................................................................................................................................................................................
Perform the following substeps to create a client for a 1354 RM-PhM server for which
you want to provide RADIUS authentication. Perform this step as many times as required
to create clients for each server in the network:
1. Right click on Client and select New Client. The Add Client dialog is displayed.
2. Enter the following information in the Add Client dialog:
Friendly name
Enter the NE name
Protocol
Set to RADIUS
3. Click Next. The Add RADIUS Client dialog is displayed.

4. Enter the following information in the Add RADIUS Client dialog:
Client address
Enter the IP address of the 1354 RM-PhM server
Client-Vendor
Set to RADIUS Standard
Shared secret
Enter the secret that is shared between the IAS RADIUS server
and the 1354 RM-PhM server. This is the same shared secret
that is specified on the server in its RADIUS configuration.
Confirm shared secret
Re-enter the shared secret.
5. Click Next.
...................................................................................................................................................................................................
Perform the following substeps to create a remote access policy for each of the groups
added in Step 2. You must perform these steps once for each group.
1. From the Internet Authentication Service, right click on Remote Access Policies and
select New Remote Access Policy.
2. Enter the name for the remote access policy in the Policy Friendly name field of the
New Remote Access Policy dialog. It is recommended that you use the same name as
specified for the group in Step 2, as listed below:
Platform
Privilege level
Recommended remote
access policy name
1354 RM-PhM server
Admin
1354 RM-PhM Admin
Provisioner
....................................................................................................................................................................................................................................
2-67
February 2011
....................................................................................................................................................................................................................................
Platform
Privilege level
Recommended remote
access policy name
Observer
3. Click Next. The Add Remote Access Policy dialog box is displayed.
4. Click Add in the Add Remote Access Policy dialog box. The Select Attribute dialog
box is displayed.
5. Double-click Windows-Groups in the Select Attribute dialog box. The Groups
dialog box is displayed.
6. Click Add in the Groups dialog box. The groups configured on the IAS server are
listed, including those added in Step 2. Double click on the group you want to add,
click OK to add the group and OK again to confirm.
7. Go back to the Add Remote Access Policy dialog box and click Next.
8. Select Grant remote access permission and click Next.
9. Click Edit Profile. The Edit Dial-In Profile dialog box is displayed.
10. Select the Authentication tab in the Edit Dial-in Profile dialog box and configure the
options. Select "MD5-Challenge" from EAP Methods, and check PAP as
Authentication Method.
11. Select the Advanced tab, and click Add.
12. Double-click the line beginning with Vendor-Specific in the RADIUS attributes list.
13. Click Add in the Multivalued Attribute Information dialog box and enter the
following information:
Enter vendor code
7483
Conforms to RADIUS RFC
Yes
14. Click Configure Attribute in the Multivalued Attribute Information dialog box and
enter the following information:
Vendor-assigned attribute number
2 for 1354 RM-PhM servers
Attribute format
Decimal
Attribute value
0 for observer
1 for provisioner
2 for admin
15. Click OK in the Vendor-Specific Attribute Information and Multivalued Attribute

Information dialog boxes.
16. Click Close in the Add Attributes dialog box.
17. Click OK in the Edit Dial-In Profile dialog box.
....................................................................................................................................................................................................................................
2-68
February 2011
....................................................................................................................................................................................................................................
18. Repeat Step 5 until you have added a remote access policy for each group.
19. Click Finish in the Add Remote Access Policy dialog box.
E...................................................................................................................................................................................................
N D O F S T E P S
To configure a Windows 2003 IAS server to provide RADIUS authentication for 1354
RM-PhM servers
...................................................................................................................................................................................................
Install the Windows 2003 IAS (Internet Authentication Service) on your Windows 2003
server. Refer to the product documentation for details.
...................................................................................................................................................................................................
Create the following three groups on the IAS server (one for each of the three privilege
levels on the 1354 RM-PhM server). Create user accounts and add them to the groups.
Note: IAS RADIUS authentication defaults account authentication to the domain that
the server is a member of. Therefore logins without an explicit domain included in the
username must have an account in the domain the server is a member of.
If you are not using an account from the server default domain (e.g. a local server
account for a stand-alone server), you must specify the domain/hostname in the
username at login (e.g. for user myaccount you enter winserv1\myaccount at login,
where winserv1 is the hostname of a stand-alone server).
Platform
Privilege level
Recommended group name
1354 RM-PhM server
Admin
1354 RM-PhM Admin
Provisioner
Observer
...................................................................................................................................................................................................
Select Start > Programs > Administrative Tools > Internet Authentication Service. If
Administrative Tools does not show up under Programs, click Start, select Run, enter
mmc, and click OK. On the Console window that appeared, click File, select Add
Snap-in, click Add, and select Internet Authentication Service from the list. Click Add,
then OK.
....................................................................................................................................................................................................................................
2-69
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Perform the following substeps to create a client for a 1354 RM-PhM server for which
you want to provide RADIUS authentication. Perform this step as many times as required
to create clients for each NE or server in the network:
1. Right click on Client and select New Client. The Add Client dialog is displayed.
2. Enter the following information in the Add Client dialog:
Friendly name
Enter the NE name
Client IP
Enter the IP address of the 1354 RM-PhM server
3. Click Next. The New RADIUS Client dialog is displayed.

4. Enter the following information in the Add RADIUS Client dialog:
Client-Vendor
Set to RADIUS Standard
Shared secret
Enter the secret that is shared between the IAS RADIUS server
and the 1354 RM-PhM server. This is the same shared secret
that is specified on the NE or server in its RADIUS
configuration.
Confirm shared secret
Re-enter the shared secret.
5. Do not select the Request must confirm the Message Authentication attribute
checkbox.
6. Click Finish.
...................................................................................................................................................................................................
Perform the following substeps to create a remote access policy for each of the groups
added in Step 2. You must perform these steps once for each group.
1. From the Internet Authentication Service, right click on Remote Access Policies and
select New Remote Access Policy. Do not use the wizard to create the policy.
2. Enter the name for the remote access policy in the Policy Friendly name field of the
New Remote Access Policy dialog. It is recommended that you use the same name as
specified for the group in Step 2, as listed below:
Platform
Privilege level
Recommended remote
access policy name
1354 RM-PhM server
Admin
1354 RM-PhM Admin
Provisioner
Observer
....................................................................................................................................................................................................................................
2-70
February 2011
....................................................................................................................................................................................................................................
3. Click Next. The Policy Condition dialog box is displayed. Click Add, and select
Windows-Groups from the list, click Add and enter the user group associated with the
policy. Click OK twice - Windows-Groups appears in Policy Conditions window.
4. Click Next. Permissions dialog box is displayed. Select Grant remote access
permission and click Next.
5. Click Edit Profile. The Edit Dial-In Profile dialog box is displayed.
6. Select Authentication tab.
7. Click EAP Methods and select MD5-Challenge and then click OK. Uncheck all
authentication methods except Unencrypted Authentication (PAP, SPAP) - it should be
checked.
8. Select the Advanced tab, remove all default attributes, and click Add.
9. Double-click the line beginning with Vendor-Specific in the RADIUS attributes list.
10. Click Add in the Multivalued Attribute Information dialog box and enter the
following information:
Enter vendor code
7483
Conforms to RADIUS RFC
Yes
11. Click Configure Attribute in the Multivalued Attribute Information dialog box and
enter the following information:
Vendor-assigned attribute number
2 for 1354 RM-PhM servers
Attribute format
Decimal
Attribute value
0 for observer
1 for provisioner
2 for admin
12. Click OK in the Vendor-Specific Attribute Information and Multivalued Attribute

Information dialog boxes.
13. Click Close in the Add Attributes dialog box.
14. Click OK in the Edit Dial-In Profile dialog box and click Next, then click Finish.
15. Repeat Step 5 until you have added a remote access policy for each group.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-71
February 2011
....................................................................................................................................................................................................................................
To configure the 1354 RM-PhM server to use a RADIUS server
You can configure each 1354 RM-PhM server to use up to two RADIUS servers, indexed
by number (1 or 2). The server configured with index number 1 is the active server. The
server configured with index number 2 is the backup server and is used only if server 1 is
not available.
To configure a 1354 RM-PhM server to use a RADIUS server, perform the procedure To
configure 1354 RM-PhM user authentication properties (p. 2-73).
....................................................................................................................................................................................................................................
2-72
February 2011
....................................................................................................................................................................................................................................

The 1354 RM-PhM user management capability allows the administrator to perform the
following functions:
configure 1354 RM-PhM user authentication properties

monitor 1354 RM-PhM user sessions - view which users are logged on, and
disconnect them if required
manage 1354 RM-PhM user accounts - create or delete accounts
To configure 1354 RM-PhM user authentication properties
The 1354 RM-PhM can use RADIUS to authenticate userids and passwords for all of the
1354 RM-PhM users in the network.
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, choose Admin>Settings.

...................................................................................................................................................................................................
In the Settings window, click the System Settings tab, and then click the User
Authentication tab.
The user authentication properties are displayed.
...................................................................................................................................................................................................
From the Authentication Behavior drop-down menu, choose the authentication order.
...................................................................................................................................................................................................
If you are using RADIUS, specify the RADIUS server configuration properties:
1. Check the Radius 1 Enable check box. This enables the attribute fields for RADIUS
server 1.
2. Specify the hostname or IP address of RADIUS server 1.
3. Specify the port to which to connect on RADIUS server 1.
4. Specify the shared secret.
5. Confirm the shared secret.
6. Specify the RADIUS time-out in seconds (range 1 - 30).
7. Specify the number of RADIUS retries - (range 0 - 10).
...................................................................................................................................................................................................
If you wish to specify a second RADIUS server, repeat Step 4 for RADIUS Server 2.
....................................................................................................................................................................................................................................
2-73
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the Maximum Failed Login Attempts field, specify the maximum number of failed
login attempts that are permitted before user is logged out. This field applies only to local
authentication, not to RADIUS authentication.
...................................................................................................................................................................................................
Click OK.
E...................................................................................................................................................................................................
N D O F S T E P S
To monitor or disconnect 1354 RM-PhM users

...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, choose Admin>PhM User Sessions.
The User Sessions window is displayed.
...................................................................................................................................................................................................
To refresh the view, click the Auto-Refresh button.

...................................................................................................................................................................................................
To refresh the view automatically:

1. Click the Auto-Refresh button so that it is in the depressed state.
2. Click the Auto-Refresh Interval button. A slide is displayed. Use the slider to specify
the refresh rate in seconds.
3. Click OK.
...................................................................................................................................................................................................
To disconnect a user, select the user from the list, and then click the Terminate User
button.
Click Yes in response to the prompt.
E...................................................................................................................................................................................................
N D O F S T E P S
To manage 1354 RM-PhM user accounts

...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, choose Admin>PhM User Accounts.
The User Accounts window is displayed.
....................................................................................................................................................................................................................................
2-74
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To create a new account, click the Create new user account button. The Create User
Account window is displayed. Specify the account properties as desired:
Username - specify an unique name for the user.

New password - Enter the new password (see Password Rules below).
Password Rules
Password complexity: The password complexity rules user interface can be accessed by
selecting the Settings menu item in the Admin menu. A tab appears named Password
Rules in the System Settings tab. Only users with an admin user role are able to access
this tab.
Minimum password length (default is 6)
Maximum password length (default is 32)
Minimum number of alphabetic characters (default is 0)
Minimum number of uppercase characters (default is 0)
Minimum number of lowercase characters (default is 0)
Minimum number of numeric characters (default is 1)
Minimum number of special characters (default is 0)
Permissible list of special characters - default is ! @ # $ % ^ * ( ) _ + - = [ ] { } | ; : ,
./?
Maximum number of repeating characters (default is 3)
Must start with an alphabetic character (default is false)
Must not end with a numeric character (default is false)
Non-configurable password rules:
Passwords cannot contain the username
Passwords cannot contain the reverse of the username
Passwords cannot contain white spaces (tab, space, new line, carriage return)
The new password cannot be identical to the current password.
Confirm new password - You must specify the password a second time to confirm the
password.
Change password on first login - check the box to specify that the user must change
the password on first login.
Max password age (days) - specify the number of days after which the user must
specify a new password when they log in.
Max inactivity period (days) - specify the number of days after which if the user has
not logged in, they are locked out from the 1354 RM-PhM.
Max concurrent sessions - specify the maximum number of login sessions that this
user is allowed to run at the same time.
User role - from the drop-down menu, choose the applicable role for this user. Refer
to Table 2-4, 1354 RM-PhM user role permissions (p. 2-76).
....................................................................................................................................................................................................................................
2-75
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To delete an account, select the account from the list and click the Remove user account
button. Deleting an account automatically shuts down all sessions the user is currently
running.
...................................................................................................................................................................................................
To modify an account, select the account from the list, and click the Display user account
properties button. The User Account window is displayed. Make changes to the account
properties as desired, and then click OK.
Username - specify an unique name for the user (5 to 12 characters).
New password - Enter the password (see Password Rules above).

Confirm new password - You must specify the password a second time to confirm the
password.
Account access - from the drop-down menu, choose the access status for this user:
No change - leave the access status unchanged.

Logins allowed - the user is allowed to log in. Use this after a user has been
locked out but is being reinstated.
Password change on next login - forces the user to specify a new password the
next time they log in.
Lock account and terminate all sessions - Terminates all sessions and prevents the
user from logging in.
Max password age (days) - specify the number of days after which the user must
specify a new password when they log in.
Max inactivity period (days) - specify the number of days after which if the user has
not logged in, they are locked out from the 1354 RM-PhM.
Max concurrent sessions - specify the maximum number of login sessions that this
user is allowed to run at the same time.
User role - from the drop-down menu, choose the applicable role for this user. Refer
to Table 2-4, 1354 RM-PhM user role permissions (p. 2-76).
...................................................................................................................................................................................................
To refresh the user account window, click the Refresh button.

Table 2-4
Function
Admin
PhM server database backup
PhM server shutdown
Manage 1354 RM-PhM user

accounts
Provisioner
Observer
....................................................................................................................................................................................................................................
2-76
February 2011
....................................................................................................................................................................................................................................
Table 2-4
(continued)
Function
Admin
Provisioner
Observer
View 1354 RM-PhM user sessions
Manage NE user accounts
NE backup/restore
NE software download
TCA administration
NE alarm severity administration
Create/modify/delete NEs
Create/modify/delete groups
Create/modify/delete services
View services
Modify inventory
View inventory
Modify physical topology
View physical topology
Configure log and archive settings
View logs
Export logs
Modify facility/connection
View facility/connection
Launch static network

commissioning wizard
Create/modify topological
connection
View topological connection
Configure auto discovery
Configure NTP properties
Manage APS groups
View APS groups
Launch network commissioning

wizard
Launch network alteration wizard
....................................................................................................................................................................................................................................
2-77
February 2011
....................................................................................................................................................................................................................................
Table 2-4
(continued)
Function
Admin
Provisioner
Launch power balancing wizard
Create loss report
Observer
Note: Service user is the highest level, and is meant for Alcatel-Lucent technicians.
The Service user has all the Admin privileges noted above (except the ability to
create/delete/modify user profiles), plus the ability to utilize the debugging and
software development tools. The following applies:
a maximum of one Service user per NE, created by default, as part of the SW
load. (There is no mechanism to create another Service user profile or to delete the
Service user profile). Only the Service user can change his/her password.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-78
February 2011
NE user management
....................................................................................................................................................................................................................................
NE user management
The 1354 RM-PhM NE user management capability allows the administrator to perform
the following functions:
add user accounts to the table view for a new network element
remove accounts from the table view for a network element
view the selected user account details.
create a new user account on a network element.

delete the selected user account(s) on the network element. The service account
cannot not be deleted.
update user account password on the network element. The service account cannot be
changed.
enable the selected user account(s) on the network element.
disable the selected user account(s) on the network element.
For more information, refer to the 1830 PSS-32/PSS-16 User Provisioning Guide and
1696 ROADM documentation.
To manage NE users and accounts
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, choose Admin>NE User Management.
The NE User Management window is displayed.
...................................................................................................................................................................................................
To refresh the view, click the Refresh button.

...................................................................................................................................................................................................
To add the user accounts for a network element to the table, click the Add user accounts
button.
A pop-up window prompts you to select the NE for which you want to view accounts.
Select the NE from the list, and click OK. The user accounts for that NE are added to the
NE User Management window.
...................................................................................................................................................................................................
To remove accounts from the table view for a network element, click the Remove user
accounts button.
A pop-up window prompts you to select the NE for which you want to remove accounts.
Select the NE from the list, and click OK. The user accounts for that NE are removed
from the NE User Management window.
....................................................................................................................................................................................................................................
2-79
February 2011
NE user management
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To display or modify an account's properties, select the account from the list, and click
the Display user account properties button (or double-click the account). The Modify
User Account window is displayed. Make changes to the account properties as desired,
and then click OK.
Access level- from the drop-down menu, choose the access status for this user:
administrator
provisioner
observer
Status - from the drop-down menu, choose the account status for this user:
enabled
disabled
New Password - Enter the new password (see Password Rules below).
Confirm password - You must specify the password a second time to confirm the
password.
To save the changes to the account, click Apply.
...................................................................................................................................................................................................
To create a new account, click the Create new user account button. The Create User
Account window is displayed. Specify the account properties as desired:
Username - specify an unique name for the user (see User identification and user
password definition (p. 2-81)).
Access level- from the drop-down menu, choose the access status for this user:
administrator
provisioner
observer
Session Timeout (minutes) - Enter number of minutes before session will timeout
Status - from the drop-down menu, choose the account status for this user:
enabled
disabled
Password - Enter a password (see User identification and user password definition
(p. 2-81)).
Confirm password - You must specify the password a second time to confirm the
password.
Selected NE(s) - from the list, select the NE(s) on which this account is to be created.
To complete the account creation, click Apply.
....................................................................................................................................................................................................................................
2-80
February 2011
NE user management
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To delete an account, select the account from the list and click the Remove a user account
button.
If the user is not currently logged in, a pop-up window prompts you to confirm the
account delete. Click OK. The user account is deleted from the NE.
If the user is currently logged in, you receive an error message. Verify that you are
deleting the correct user, and if so, contact the user and have them log off. Try again to
delete the account.
...................................................................................................................................................................................................
To enable a user, select the user from the list, and then click the Enable a user account
button.
A pop-up window prompts you to confirm the account enable. Click OK. The user
account is enabled on the NE.
...................................................................................................................................................................................................
To disable a user, select the user from the list, and then click the Disable a user account
button.
A pop-up window prompts you to confirm the account disable. Click OK. The user
account is disabled on the NE.
Note: Disabling an account that is logged in will not succeed.
E...................................................................................................................................................................................................
N D O F S T E P S
User identification and user password definition
Userids and passwords can contain the following characters:
Alphabetic characters in the set [az, AZ]

Numeric characters in the set [09]
Special characters % (percent sign), + (plus sign), # (pound sign), and _ (underscore).
User identifier (UID)
User identity is specified using a UID that is a unique identifier used by an NE for
security management. A UID code is a non-confidential, unique, and auditable
representation of a user such as the login name. The NE supports UIDs that are strings of
5 to 12 case-sensitive alphanumeric characters where the first character is alphabetic.
....................................................................................................................................................................................................................................
2-81
February 2011
NE user management
....................................................................................................................................................................................................................................
The following conditions apply to UIDs:
Each authorized user (a person, device or a software process having operations related
command inputs access) must have a UID. Each UID must be unique on the NE (i.e.
the system does not support 2 UIDs that are the same).
At any given instant in time, the NE internally maintains the identity of all UIDs
logged on at that time.
The NE supports a maximum of 255 unique UIDs.
Password identifier (PID)
A PID is a case sensitive string of 6 to 24 alphabetic [a-z, A-Z], numeric [0-9], or special
characters. A valid password must contain at least 1 alphabetic, 1 numeric, and 1 special
character. The following special characters are accepted as valid: % (percent sign), + (plus
sign), # (pound sign), and _ (underscore). The first character of the PID can be any
alphabetic, numeric, or valid special character.
The following conditions apply to PIDs:
The PID cannot be the same as the associated UID, nor can it be the reverse of the
associated UID.
The NE will not prevent a user from choosing an already existing password (more
than one user can have the same password).
Password administration
The NE supports the ability for a user with security administration privileges to specify
the following user password attributes: the password age (in days); the number of days
that the existing password can be continued to be used before a new password becomes
mandatory; the number of times that the existing password can be continued to be used
before a new password becomes mandatory; the password obsolescence interval that must
elapse before an obsolete password can be reused.
A user with security administration privileges can provision a system-wide password
aging interval to encourage users to change passwords periodically. The following
applies:
The default for system-wide password aging interval is 30 days. The allowed range is
from 1 to 999 days.
The system allows the ability to disable the system-wide password aging interval, by
assigning a value of 0 (zero) days.
A password grace period and number of logins allowed after password expiration can also
be provisioned. The following applies:
The default for the password grace period is 7 days.

The default for the number of logins allowed after password expiration is 3.
....................................................................................................................................................................................................................................
2-82
February 2011
NE user management
....................................................................................................................................................................................................................................
A password is expired when one of the following events occurs:
the password is expired and neither a grace period nor number of logins is permitted
after password expiration
the password is expired and either a grace period or a number of logins is permitted
after password expiration, but the provisioned value(s) is expired (i.e., the user has no
more days to use the expired password, or no more logins allowed with the expired
password).
Users have the ability to change their own password on demand. To change a password,
the user must enter the current password, the new password, and the confirmed new
password (Note: For an Admin user changing another users password, only the new
password value needs to be entered). The NE checks the password for proper length and
syntax in accordance with established password requirements. Before updating the NE's
database, the NE ensures that the current password is different from the new password
and that the new password and confirmed new password are the same. An error message
is generated to notify the user if any of the password requirements are not met.
....................................................................................................................................................................................................................................
2-83
February 2011
....................................................................................................................................................................................................................................

Administrative users can enable/disable a default login banner. Also the administrative
user can configure the text of a post-login banner and can enable/disable the post-login
banner. If it is enabled, the post-login banner is displayed after a successful login. A user
must acknowledge that they have read the banner before proceeding. Otherwise the user
is logged out.
Administrative users can enable a session time-out that applies to all users of the 1354
RM-PhM. When session time-outs are enabled, individual user sessions are assigned the
default time-out specified by the administrator. Individual users can change the default
time-out for their own session by entering a new value. The time-out value for an
individual user cannot exceed the maximum time-out value specified by the
administrative user.
The administrative user can also enable/disable the SSL Security setting.
Enable/disable login banner
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, choose Admin > Settings.
...................................................................................................................................................................................................
In the Settings window, click the System Settings tab, and then click the Login Session
Settings tab.
The session properties are displayed.
...................................................................................................................................................................................................
To enable the login banner select the box.

The login banner title and body text can be created/modified.
E...................................................................................................................................................................................................
N D O F S T E P S
Enable/disable post-login banner

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2-84
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Settings tab.
...................................................................................................................................................................................................
To enable the post-login banner select the box.

The post-login banner title and body text can be created/modified.
E...................................................................................................................................................................................................
N D O F S T E P S
To set the session time-out for all 1354 RM-PhM users

...................................................................................................................................................................................................
...................................................................................................................................................................................................
Settings tab.
...................................................................................................................................................................................................
Specify the session time-out attributes as follows:
Session Time-outs Enabled: Click this checkbox to enable session time-outs for all
1354 RM-PhM users.
Maximum time-out (minutes): The maximum value that a user can set their session
time-out to. Range: 1 - 10800 minutes (1 week). Default: 10800 minutes
Default time-out: The default time-out value for user sessions. Range: 1 minute to
max time-out value configured above. Default: 1 day (1440 minutes).
Note: Changes to this screen take effect for all subsequent user logins and do not
affect currently logged in users.
E...................................................................................................................................................................................................
N D O F S T E P S
Enable SSL security setting

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2-85
February 2011
....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
Settings tab.
...................................................................................................................................................................................................
To enable SSL, select the box under Security Settings.

E...................................................................................................................................................................................................
N D O F S T E P S
To change the default time-out for a user session

...................................................................................................................................................................................................
is displayed.
...................................................................................................................................................................................................
In the Settings window, click the User Settings tab, and then click the User Session tab.
The session time-out properties are displayed.
...................................................................................................................................................................................................
Enter a new value for the session time-out, in minutes. This value cannot exceed the
maximum time-out specified by the administrator.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-86
February 2011
1696 ROADM and 1830 PSS network element software
management
....................................................................................................................................................................................................................................
1696 ROADM and 1830 PSS network element

software management
This section describes the management of network element software from the 1354
RM-PhM. For an overview of software management, refer to the Alcatel-Lucent 1830
Photonic Service Switch 32/16 (PSS-32/16) Release 3.5.0 User Provisioning Guide.
Note: To avoid conflicting activities on a network element, ensure that you coordinate
your activities with other operators in the network.
Before you can download software to a network element, you must set up a software
server and a backup server. For an overview of software downloading and setting up
servers, refer to the Alcatel-Lucent 1830 Photonic Service Switch 32/16 (PSS-32/16)
Release 3.5.0 User Provisioning Guide.
You must then specify the database backup properties for each network element, as well
as the software server from which to download the software.
Note: Do not perform any manual or scheduled database backups while loading
software. The software loading process performs its own backups. You can perform
backups prior to loading software, but not while software loading is in progress.
The major activities involved in loading software are:
1. Phase 1 - specify the target release, audit the network element(s), and view the
software upgrade script.
2. Phase 2 - load the software onto the selected network element(s).
3. Phase 3 - activate the new software.
Before activating the software on an NE after a software download, all non-software
loading related alarms must be set to Acknowledged.
4. Phase 4 - commit the network element(s) to the new software, or back out.
This section contains the following procedures:
To perform a manual software download to a network element (p. 2-87)
To schedule a manual software download and activation (p. 2-90)
To perform an automatic software download to a network element (p. 2-92)
To perform a manual software download to a network element

...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, select the network element(s) to which you want
to download software, and choose Maintenance>NE Software Upgrade.
The Software Upgrade window is displayed, with the selected network element(s) listed.
....................................................................................................................................................................................................................................
2-87
February 2011
management
....................................................................................................................................................................................................................................
Alternatively, if you select no network elements in the topology view, the Software
Management window lists all of the network elements.
...................................................................................................................................................................................................
Specify the software server from which to obtain the software:
Choose a software server from the Software Server drop-down menu or type in its IP
address. The list of servers in this menu is composed of the default software servers
specified for each of the network elements in the list.
If the software server address you desire in not in the drop-down menu, you can type
it into the Software Server field.
It is recommended that you use the 1354 RM-PhM server as the software server.
Check the PhM is Software Server check box.
...................................................................................................................................................................................................
Specify the protocol to be used to access the software server. It is recommended that you
select Use Default file transfer settings. (You need to set up the defaults first. To set up
the defaults click the System settings button in this window.)
...................................................................................................................................................................................................
Specify the userid that is to be user to access the software server. It is recommended that
you select Use Default file transfer settings, in which case this field is not changeable.
...................................................................................................................................................................................................
Specify the Target Release Directory. Click the folder icon beside the Target Release
Directory field. If the software server is not the 1354 RM-PhM server, an FTP server
login window is displayed. Specify the login information (the FTP server address is set to
the value specified in Step 2. You can overwrite this value manually if desired) and click
Connect. No login information is required if the 1354 RM-PhM is acting as the software
server.
Locate and select the file from which you wish to load software.
The selected software server directory appears in the Target Release Directory field, and
the name of the target release within the Target Release Directory is displayed in the
Target Release field.
...................................................................................................................................................................................................
If you want to back up the database of the network element(s) as part of the software
download process, check the Backup Network Element Database check box. To specify
the database backup attributes, click the Open Backup and Restore button. The Backup
and Restore window is displayed. Refer to To back up a network element database
(p. 2-45) for information on setting backup parameters.
Note: It is recommended that you select this option.
....................................................................................................................................................................................................................................
2-88
February 2011
management
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
If you want to perform a software upgrade check to ensure compatibility between the
committed release of software on the network element(s) and the target load, check the
Check Upgrade Path check box.
Note: It is recommended that you select this option.
...................................................................................................................................................................................................
From the list of network elements, select those network elements to which you want to
download the specified software, and click the Phase 1 - Generate a New Software
Upgrade Script button.
A warning is displayed, listing the parameters specified and asking you to confirm
whether or not you want to proceed. If the parameters are correct, click Yes. Otherwise
click no, correct the settings, and try again.
The 1354 RM-PhM provides status and progress feedback in the lower pane of the
Software Upgrade window.
Once the script has been generated, you can view it by clicking the View the Software
Upgrade Script button. The script is displayed in a new window. If the script is correct,
proceed to the next step. If not, you must correct any problems before continuing.
The 1696 ROADM and 1830 PSS creates a unique script for each of the selected NEs
(each script has separate load and activate activities).
...................................................................................................................................................................................................
Load the software onto the selected network element(s). Click the Phase 2 - Load the
Target Software button.
Software Upgrade window. Once the software has been loaded onto the network
element(s), proceed to the next step.
...................................................................................................................................................................................................
10
Activate the new software. Click the Phase 3 - Activate the Target Software button.
You can perform the operation on multiple network elements by multi-selecting them
before clicking the button. This is particularly useful in this step because when you
activate the network elements they reset, which disrupts control network traffic. The 1354
RM-PhM and network elements work together to ensure that the activate message can be
successfully sent to all the selected network elements before they start resetting.
The system performs a pre-activation check to ensure that there are no unacknowledged
alarms on the network element, and that the network element is in sync with the 1354
RM-PhM.
If the pre-activation check passes, the network element begins running the new software.
....................................................................................................................................................................................................................................
2-89
February 2011
management
....................................................................................................................................................................................................................................
If the pre-activation check fails, the new software is not activated and the network
element continues to operate with the original software. Resolve the problem(s) and click
the Phase 3 - Activate the Target Software button again. If the pre-activation check fails
because of the presence of unacknowledged alarms, then an alarm browser is displayed.
To acknowledge an alarm, select it, right-click it, and select Acknowledge.
...................................................................................................................................................................................................
11
Once software has been activated, you must decide to commit the network element to the
new software, or to back out and resume using the previous software load. If you choose
to back out, the system ensures that the last database backup is valid and restores the
database. If the last database backup is not valid, as indicated by an invalid database
alarm, then the database must be restored manually.
To commit the network element(s) to the new software, click the Phase 4 - Commit
button.
To back out of the new software load and resume using the original load, click the Back
out button.
E...................................................................................................................................................................................................
N D O F S T E P S
To schedule a manual software download and activation

...................................................................................................................................................................................................
...................................................................................................................................................................................................
Choose a software server from the Software Server drop-down menu. The list of
servers in this menu is composed of the default software servers specified for each of
the network elements in the list.
...................................................................................................................................................................................................
Specify the protocol to be used to access the software server.
....................................................................................................................................................................................................................................
2-90
February 2011
management
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Specify the userid that is to be user to access the software server.

...................................................................................................................................................................................................
Specify the Target Release Directory. There are two methods:
In the Target Release Directory field, type the path to the desired software server
directory.
Locate and select the desired software server directory, as follows:
Click the folder icon beside the Target Release Directory field. If the software server
is not the 1354 RM-PhM server, an FTP server login window is displayed. Specify the
login information (the FTP server address is set to the value specified in Step 2. You
can overwrite this value manually if desired) and click Connect. No login information
is required if the 1354 RM-PhM is acting as the software server.
The selected software server directory appears in the Target Release Directory field,
and the name of the target release within the Target Release Directory is displayed in
the Target Release field.
...................................................................................................................................................................................................
It is recommended that you select this option.
...................................................................................................................................................................................................
Perform Upgrade Path Check check box.
...................................................................................................................................................................................................
download the specified software, and click the Phase 1 - Generate a New Software
Upgrade Script button.
A warning is displayed, listing the parameters specified and asking you to confirm
whether or not you want to proceed. If the parameters are correct, click Yes. Otherwise
click no, correct the settings, and try again.
Software Upgrade window.
....................................................................................................................................................................................................................................
2-91
February 2011
management
....................................................................................................................................................................................................................................
Once the script has been generated, you can view it by clicking the View the Software
Upgrade Script button. The script is displayed in a new window. If the script is correct,
proceed to the next step. If not, you must correct any problems before continuing.
...................................................................................................................................................................................................
Click the Schedule the Load Phase button.

...................................................................................................................................................................................................
10
In the Schedule Load window, check the Enable Scheduled Download Software check
box, and specify the date and time for the software download to occur. Click OK.
...................................................................................................................................................................................................
11
Click the Schedule the Activate Phase button.

...................................................................................................................................................................................................
12
In the Schedule Activate window, check the Enable Scheduled Activate Software load
check box, and specify the date and time for the software activation to occur.
The activate phase cannot begin until the load phase is complete. Ensure that when you
schedule the activation step that you leave enough time for the load to complete.
Click OK.
...................................................................................................................................................................................................
13
Once the scheduled download and activation have taken place, the network element(s)
must be committed to the new software, or backed out. Committing or backing out must
be done manually by clicking the Commit or the Backout button.
You can schedule multiple NEs at once by selecting them and clicking the Schedule
button.
You can edit the schedules of multiple NEs if their schedules are identical.
E...................................................................................................................................................................................................
N D O F S T E P S
To perform an automatic software download to a network element
Some functions of software loading can be performed automatically. If you choose the
automatic method, the system combines the database backup, audit, load, and activate
functions in one step. The commit/backout function must be performed in another,
separate step.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2-92
February 2011
management
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Choose a software server from the Software Server drop-down menu. The list of
servers in this menu is composed of the default software servers specified for each of
the network elements in the list.
...................................................................................................................................................................................................
Specify the protocol to be used to access the software server. It is recommended that you
select Use Default file transfer settings. (You need to set up the defaults first. To set up
the defaults click the System settings button in this window.)
...................................................................................................................................................................................................
Specify the userid that is to be user to access the software server. It is recommended that
you select Use Default file transfer settings, in which case this field is not changeable.
...................................................................................................................................................................................................
Specify the Target Release Directory. Click the folder icon beside the Target Release
Directory field. If the software server is not the 1354 RM-PhM server, an FTP server
login window is displayed. Specify the login information (the FTP server address is set to
the value specified in Step 2. You can overwrite this value manually if desired) and click
Connect. No login information is required if the 1354 RM-PhM is acting as the software
server.
The selected software server directory appears in the Target Release Directory field, and
the name of the target release within the Target Release Directory is displayed in the
Target Release field.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2-93
February 2011
management
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Perform Upgrade Path Check check box.
...................................................................................................................................................................................................
download the specified software, and click the Perform an Automatic Upgrade (Phase 1,
2, and 3) of the selected NEs.
The 1696 ROADM and 1830 PSS creates a unique script for each of the selected NEs
(each script has separate load and activate activities), and then loads and activates the
software.
...................................................................................................................................................................................................
Once software has been activated, you must decide to commit the network element to the
new software, or to backout and resume using the previous software load. If you choose
to backout, the system ensures that the last database backup is valid and restores the
database. If the last database backup is not valid, as indicated by an invalid database
alarm, then the database must be restored manually.
To commit the network element(s) to the new software, click the Phase 4 - Commit
button.
To back out of the new software load and resume using the original load, click the
Backout button.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-94
February 2011
Overview
1354 RM-PhM management of Red-C RAMAN Amplifier &
EDFA Booster
....................................................................................................................................................................................................................................
1354 RM-PhM management of Red-C RAMAN

Amplifier & EDFA Booster
Overview
This section provides details for the 1354 RM-PhM management of the RAMAN
Amplifier and the EDFA Booster for integration with 1830 PSS-32 network elements.
1354 RM-PhM provides basic management of the RED-C RAMAN Amplifier and EDFA
Booster as follows:
1354 RM-PhM shows each RAMAN and EDFA as separate network elements that
appear in the 1354 RM-PhM topology map
1354 RM-PhM supports cut-through to the RAMAN/EDFA Web-based user interface
for configuration of RAMAN/EDFA network elements
Discovery of RAMAN/EDFA is either manual or automatic. For manual discovery,
the user must enter an IP address for the new RAMAN/EDFA using the normal NE
creation wizard in 1354 RM-PhM.
There is a mechanism to associate a RAMAN/EDFA with a network fiber end point
on an 1830 PSS-32 (i.e. an LD external line port). This association is visible in the
1354 RM-PhM topology map.
1354 RM-PhM can retrieve alarms from RAMAN/EDFA
RAMAN/EDFA can be deleted in the same manner as other NEs.
Non-1354 RM-PhM provisioning of RAMAN or EDFA IP Address
When an IP address for a RAMAN or EDFA is provisioned via any NE interface, the
1354 RM-PhM either:
1. Initiates a discovery of the network element at that IP address using SNMP v1 and
automatically associates it with the appropriate 1830 PSS line in the topology view, or
2. If the RAMAN or EDFA network element already exists in the 1354 RM-PhM from a
previous discovery, the 1354 RM-PhM will automatically associate it with the
appropriate 1830 PSS line in the topology view.
In point 1) above, the triggering of an automatic discovery of RAMAN or EDFA network
element does not depend upon 1354 RM-PhM's Auto Discovery status. The RAMAN
or EDFA network element will be discovered even if auto discovery is disabled or if set to
discovery by traps.
....................................................................................................................................................................................................................................
2-95
February 2011
EDFA Booster
....................................................................................................................................................................................................................................
Explicit creation of RAMAN or EDFA NE in 1354 RM-PhM
RAMAN/EDFA network elements, which have been manually discovered by the user, are
not automatically assigned to any of the existing 1830 PSS network elements external
line ports. The user has to manually configure such associations. The user can get a
summarized view of all 1830 PSS Raman/EDFA associations from the Raman/EDFA
association GUI.
Manual association in 1354 RM-PhM topology map
1354 RM-PhM provides an operation via the topology view for the user to explicitly
associate a RAMAN or EDFA network element with an 1830 PSS line. If the associated
1830 PSS line supports the RAMAN and EDFA IP address attributes, then the 1354
RM-PhM automatically provisions the IP address to match the network element being
associated (which would overwrite any previous provisioned value on the 1830 PSS NE).
For 1830 PSS, the 1354 RM-PhM stores the RAMAN and EDFA IP addresses on the
1830 PSS line in the 1354 RM-PhM database only. This information is lost if the 1830
PSS is deleted from the 1354 RM-PhM and hence must be reentered manually via the
1354 RM-PhM GUI if the 1830 PSS is later recreated in the 1354 RM-PhM. The
RAMAN or EDFA IP address is restored upon discovery of the 1830 PSS NE.
Note: 1830 PSS Releases 1.x do not support the RAMAN or EDFA IP address
attribute on external ports, hence for these releases, the user should employ the
manual association operation via the topology view to explicitly associate a RAMAN
or EDFA network element with an 1830 PSS line.
To configure RAMAN and EDFA network elements
...................................................................................................................................................................................................
From the Management Control Panel, select View > RAMAN and EDFA Associations...
Result: The RAMAN/EDFA Associations GUI is displayed.
...................................................................................................................................................................................................
Select the desired external line port displayed in the association GUI. Either right click or
double click on any cell of the selected row
Result: The Configure RAMAN and EDFA IP address window is displayed.
...................................................................................................................................................................................................
Enter the desired RAMAN/EDFA IP address and click OK

Note: A user cannot enter an IP address that has been discovered by 1354 RM-PhM
and belongs to an incorrect NE type. However, a user can enter a valid IP address
belonging to an incorrect NE type, which is not yet discovered by 1354 RM-PhM. In
such a case 1354 RM-PhM tries to discover the RED-C network element, and after
discovery, raises an internal warning alarm to notify the user of a mismatch between
....................................................................................................................................................................................................................................
2-96
February 2011
EDFA Booster
....................................................................................................................................................................................................................................
the expected network element type and the actual network element type. Its the users
responsibility to correct the problem (which will trigger a rediscovery) and clear this
alarm.
Important! When a RAMAN/EDFA network element is deleted, 1354 RM-PhM sets
the corresponding IP address on the associated external line port to Not Defined.
For doing this 1354 RM-PhM checks the actual NE type of the RED-C NE to
determine which IP address (RAMAN or EDFA) to be set to Not Defined. So in
case there was a mismatch between the expected and actual NE type while
discovering the RED-C network element, then the IP address corresponding to the
actual NE type will be set to Not Defined.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-97
February 2011
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2-98
February 2011
3 onfiguring and navigating

C
the network
Overview
Purpose
This chapter explains how to navigate through the network using the 1354 RM-PhM.
Contents
Types of network views
3-2
Discovering network elements
3-6
3-15
Showing topological connections
3-17
3-18
Using Wavelength Tracker monitoring capability
3-23
Managing optical power levels
3-24
Using the automatic power management interface
3-30
Managing APS groups
3-39
CLI cut-thru
3-44
TL1 cut-thru
3-45
WebUI cut-thru
3-46
...................................................................................................................................................................................................................................
3-1
February 2011
....................................................................................................................................................................................................................................

The 1354 RM-PhM provides the following types of network and equipment views:
Topology View
Inventory View
Facility/Connection View
Physical Topology
User help in using the views is provided through mouse-over help text for icons and
attributes and by accessing online help from the Help menu. To create a new window with
the current view, click the push-pin icon.
Using the Topology View
The topology view contains locations, managed elements and links. The links provide a
physical view of the network connectivity. It is the responsibility of the user to create the
physical links manually.
The topology view provides a geographic reference for the association of locations and
network elements.
Managed elements include the following:
network elements and their components (that is, shelves, cards and ports)
locations
Links between locations are created automatically based on whether network elements in
location A are connected to network elements in location B.
The Topology View can also be used to present link connectivity. As connections and
services are created in the network, link associations are created.
Defining the background map
Users can create locations and associate a specific background image to each location.
The 1354 RM-PhM supports GIF and JPG file formats.
Users with the appropriate permission level can select View>Background Image and
specify an URL to an image.
Moving network elements into a location
A network element can be dropped into any location. The network element must be edited
from the Topology view of the 1354 RM-PhM.
It is the user's responsibility to ensure that the network elements are positioned in the
proper location.
As network elements are discovered they are placed into the Main View reference. If the
element has a location identifier and the identifier can be mapped to a current location,
the element is placed automatically into the corresponding location.
....................................................................................................................................................................................................................................
3-2
February 2011
....................................................................................................................................................................................................................................
Understanding link topology
The 1354 RM-PhM supports the following:
single fiber can support multiple links

links can support multiple services
the ability to show physical connectivity on a geographic map
the ability to show wavelength connectivity on a geographic map
Using the Inventory View
The Inventory View provides the following capabilities:
view shelf and card lists and graphics
view and edit card and port attributes

view power levels on band optical filter or OSCT WDM ports
pre-provision a card in a slot (right-click on an empty slot)
To access the Inventory view

...................................................................................................................................................................................................
From the 1354 RM-PhM Topology view, double-click on a network element, or select the
network element and choose Provision > Open Existing Inventory.
The Inventory view is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Using the Facility/Connection View
The Facility/Connection view provides the following capabilities:
list the facilities on a given network element

view and change the attributes of each facility
view, create, or disconnect cross-connections on facilities
To access the Facility/Connection view

...................................................................................................................................................................................................
From the 1354 RM-PhM Inventory view, Wavelength Tracker view, or Service Tracker
view, navigate to a port and double-click it.
The Facility/Connection view is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-3
February 2011
....................................................................................................................................................................................................................................
Using the Physical Topology
The Physical Topology view displays the fiber connections within the network element,
and to other network elements. Refer to Configuring the network element and network
fiber topology (p. 3-18).
To access the Physical Topology view
...................................................................................................................................................................................................
From the 1354 RM-PhM, choose Provision > Physical Topology

The Physical Topology view is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Using groups
The 1354 RM-PhM allows you to organize the network elements into groups. A network
element can be a member of only one group.
The following group types are supported:
Singleton - Used for a single NE that is managed independently of its Topological

Link connectivity to other NEs. It may be a member of a ring that is managed by a
number of PhMs. It is acceptable for an PhM to represent all NEs as being in
Singleton subnetworks regardless of the actual network configuration. A singleton
subnetwork does not contain internal topological links.
Chain - Used for two or more NEs that are managed by the same PhM and are
connected by Topological Links in a chain.
Path Switched Ring (PSR) - Used for two or more NEs that are managed by the same
PhM and are connected by Topological Links in a ring that is capable of supporting
Subnetwork Connection protection. (for example UPSR, SNCP Ring)
Shared Protection Ring (SPRing) - Used for two or more NEs that are managed by the
same PhM and are connected by Topological Links in a complete ring that supports
Shared Line Protection (for example BLSR).
OpenPSR - Used for two or more NEs of a PSR (but not the entire ring) that are
managed by the same PhM (for example Open UPSR).
OpenSPRing - Used for two or more NEs of a SPRing (but not the entire ring) that are
managed by one PhM (for example Open BLSR).
Mesh - Used to cover an arbitrary set of two or more NEs that are not covered by any
other type.
Note: Specifying a group type does not enforce any rules upon the network elements
or topology with that group.
....................................................................................................................................................................................................................................
3-4
February 2011
....................................................................................................................................................................................................................................
To create a group
...................................................................................................................................................................................................
In the Topology tree window, select the group in which you want the new group to be
created.
...................................................................................................................................................................................................
Choose File>New Group.

The Create a new group window is displayed.
...................................................................................................................................................................................................
Specify a name for the group.

...................................................................................................................................................................................................
From the Subnet Type drop-down menu, choose a subnet type.

...................................................................................................................................................................................................
Click OK.
The new group is added as a folder to the tree view.
E...................................................................................................................................................................................................
N D O F S T E P S
To assign a network element to a group

...................................................................................................................................................................................................
There are two methods to assign a network element to a group.
For an existing network element, in the Topology tree view, drag and drop the
network element from one group into the desired group.
For an undiscovered network element, select the desired group and then choose
File>New NE. The network element is discovered and placed into the group.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-5
February 2011
....................................................................................................................................................................................................................................

In order for the 1354 RM-PhM to manage a network element, it must first discover the
elements in the network. Use this procedure when:
starting up the first 1354 RM-PhM client with a newly installed 1354 RM-PhM server
new network elements have been added to the network
Note: A network element should be managed by only one 1354 RM-PhM server (a
1354 RM-PhM configured with redundant servers is considered to be a single server
in this case). Having a network element managed by two different servers may cause
synchronization problems between the network element and the servers.
Note: If a network element is discovered with a name of the format "NEname :
IPAddress", this means that this NE is a duplicate of a previously discovered NE (i.e.
there is already an NE with "NEname") and the newly discovered NE should be
deleted from the 1354 RM-PhM by the user. This scenario could happen when an NE
association for a given IP address is deleted by the user and then that IP address is
used to manually discover the NE via the Create NE wizard.
To discover a network element

...................................................................................................................................................................................................
From the 1354 RM-PhM Topology View, choose File > New NE.
The Create New NE window is displayed.
...................................................................................................................................................................................................
In the Keep Alives section:

1. To enable Send after connection idle for, check its check box, and then specify a
time in the field provided.
Then specify a time for the Interval between keep alives in the field provided.
2. To enable Report error after, check its check box, and then specify the number of
failures to allow before reporting an error.
...................................................................................................................................................................................................
From the Transport Layer drop-down menu (if enabled), choose the transport layer type.
For Alcatel-Lucent NEs, choose SNMP.
...................................................................................................................................................................................................
From the Protocol drop-down menu (if enabled), choose the protocol type. For
Alcatel-Lucent NEs, choose SNMP.
...................................................................................................................................................................................................
If enabled, check Show all parameters to display the parameters for the NE.
....................................................................................................................................................................................................................................
3-6
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
If enabled, check Create all associations to have the 1354 RM-PhM create all of the
associations based on the chosen parameters.
...................................................................................................................................................................................................
In the Associations Parameters section, specify the following items:

1. In the RemoteHostName field, specify the IP address of the network element. This is
either the IP address of the management port on the network element, or the loopback
IP address of the network element.
2. In the RemotePortnumber field, type the SNMP port on the network element through
which to communicate. The default value is 161.
3. In the ProtocolVersion field, from the drop-down menu choose the SNMP version to
use. For the 1696 ROADM and 1830 PSS choose v2c (SNMPv3 is supported by 1696
ROADM R5.4 and 1830 PSS R2.0.0 as well).
In the GetCommunity field, type the SNMP read community identifier of the
network element(s) you are discovering. Normally the default value is used.
Contact your service representative for the default value to use.
In the SetCommunity field, type the SNMP write community identifier of the
network element(s) you are discovering. Normally the default value is used.
Contact your service representative for the default value to use.
...................................................................................................................................................................................................
Click Finish.
The network element is added to the 1354 RM-PhM Topology View, and the system
collects the latest inventory information from the network element. This may take a few
minutes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-7
February 2011
....................................................................................................................................................................................................................................
To auto-discover a network element
Note: The auto-discovery function provides two methods for the 1354 RM-PhM to
automatically discover network elements. The 1354 RM-PhM can automatically
discover NEs:
From which it receives trap messages. When the 1354 RM-PhM receives a trap
from an undiscovered network element, it attempts to discover that NE (for the
1354 RM-PhM to receive traps from a network element, the 1354 RM-PhM must
be registered as a trap destination for the network element. To register the 1354
RM-PhM as a trap destination, refer to Alcatel-Lucent 1830 Photonic Service
Switch (PSS) Release 3.5.0 Command Line Interface Guide.
For network element loopback addresses which are detected during network
topology discovery. When the 1354 RM-PhM detects a new loopback address, it
attempts to discover that NE.
If the 1354 RM-PhM successfully discovers the new NE, it adds the network
element to the topology view and begins to manage it. If the 1354 RM-PhM
cannot successfully discover a network element, it adds the network element to a
list of network elements which it no longer tries to discover (thus saving
processing resources).
Auto-discovery by Trap is supported for SNMP v3. If the received trap is SNMP
v3 then SNMP v3 will be used to discover the NE.
The Auto-Discovery GUI allows a user to configure the SNMP v3 login parameters
for SNMP v3 login during discovery by trap. These fields are:
Username
Authentication algorithm
Authentication password
Privacy algorithm
Privacy password
When a NE is discovered by trap, then subsequently that NE is managed using the

same version of SNMP as the original trap.
Auto-discovery by topology is supported for SNMP v3. If the existing NE is being
managed by SNMP v3 then SNMP v3 will be used to discover the new NE using the
same SNMP v3 parameters as the existing NE.
When a network element, NE(x), is discovered by topology based on a topological
link to another network element, NE(y), (which must already be discovered) then
PhM will attempt to manage NE(x) using the same SNMP version as it is using to
manage NE(y).
When a NE is discovered by topology or it is manually created, the version of SNMP
that was used to create the SNMP association will be used to create a trap destination
on the NE.
....................................................................................................................................................................................................................................
3-8
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology View, choose Maintenance > Auto Discovery.
The Auto Discovery attributes window is displayed.
...................................................................................................................................................................................................
Choose one of the following auto-discovery options:
Disable auto discovery - no network elements are automatically discovered

Discover by IP
Discover by trap
Note: To discover by IP, you must first manually create at least one NE using the
procedure To discover a network element (p. 3-6). Then the 1354 RM-PhM server
will discover the other NEs in the network topology by traversing the external ports
on the initial NE.
...................................................................................................................................................................................................
Check that the network element that you want to auto-discover is not already in the
auto-discovery list. In the Test IP: field, type the IP address of the network element, or IP
address range, that you intend to add to the auto-discovery list. Click Test.
A dialog is displayed informing you whether or not the address you entered is already on
the auto-discovery list. If it is, you do not need to add it. If it is not, continue at the next
step.
...................................................................................................................................................................................................
Specify which network elements to auto-discover:
To enable auto-discovery for all network elements, leave the list blank.
To enable auto-discovery for a particular network element, click the Add button. You
are prompted to specify the IP address and mask for the network element. For the
mask, specify 255.255.255.255. Click OK. The network element's IP address is added
to the auto-discovery list.
To enable auto-discovery for a range of IP addresses, click the Add button. You are
prompted to specify the IP address and mask.
In the IP address field, type only enough of the IP address to define the range of IP
addresses to discovery, for example 12.3.1.0
In the Mask field, type 255.255.255.0
This combination allows the 1354 RM-PhM to automatically discover any network
elements with an IP address in the range of 12.3.1.xxx
...................................................................................................................................................................................................
Click OK.
....................................................................................................................................................................................................................................
3-9
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Close the Auto Discovery attributes window.

E...................................................................................................................................................................................................
N D O F S T E P S
To rediscover a network element with a new database
Use this procedure to rediscover a network element that has had its database deleted, or
restored from backup. This procedure is the same as discovering a network element,
except that in this case you must first delete the network element from the 1354
RM-PhM. Deleting a network element does not delete services that end on or traverse the
deleted network element. The services remain operational, but are no longer managed by
the 1354 RM-PhM.
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology View, select the network element.
...................................................................................................................................................................................................
Right-click on the network element and choose Delete.

A dialog box asks you to confirm the delete command.
...................................................................................................................................................................................................
Click Yes.
The network element is deleted from the 1354 RM-PhM.
...................................................................................................................................................................................................
Rediscover the network element using the procedure To discover a network element
(p. 3-6).
E...................................................................................................................................................................................................
N D O F S T E P S
To reconcile a network element
Use this procedure to reconcile previously discovered network elements. This operation is
normally performed automatically by the 1354 RM-PhM.
...................................................................................................................................................................................................
From the 1354 RM-PhM Topology View, select the network element.
...................................................................................................................................................................................................
Right-click on the network element and choose Provision > Open Existing Inventory.
The Inventory view for the selected network element is displayed.
....................................................................................................................................................................................................................................
3-10
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click the Refresh button.

The latest inventory information is retrieved from the network element's database and the
1354 RM-PhM database is updated.
E...................................................................................................................................................................................................
N D O F S T E P S
Keeping the 1354 RM-PhM in sync with the NEs

...................................................................................................................................................................................................
A network element with a black X superimposed on the NE icon in the tree window of
the topology view of the 1354 RM-PhM, indicates a communication or synchronization
failure between the 1354 RM-PhM and the network element. To clear the black X from
the network element, perform a manual resync of the NE. Select the NE, and click the
Resynchronize button.
E...................................................................................................................................................................................................
N D O F S T E P S
To change the loopback or DCN port IP address of a network element
Note: This procedure should not be used during normal operation. Changing the
loopback IP address causes the network element to undergo a warm reset.
This procedure allows you to change the loopback IP address, or the DCN port address, of
a network element without having to rediscover the network element and without
interrupting service.
...................................................................................................................................................................................................
Select the network element in the topology view, right-click and choose Properties.
The Properties window for the network element is displayed.
...................................................................................................................................................................................................
Click the Associations tab.

The associations are displayed.
...................................................................................................................................................................................................
Click the Add button.

The Create Association window is displayed.
....................................................................................................................................................................................................................................
3-11
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the RemoteHostName field, specify the new loopback or DCN port IP address, and
then click Finish.
A warning is displayed that the 1354 RM-PhM cannot communicate using this new IP
address. This is normal since the new IP address is not yet active.
...................................................................................................................................................................................................
Deselect the Reconnect on Failure check box for the old loopback or DCN port IP
address.
...................................................................................................................................................................................................
Click OK to save the properties.

...................................................................................................................................................................................................
Using the CLI, change the IP address (see the Alcatel-Lucent 1830 Photonic Service
Switch (PSS) Release 3.5.0 Command Line Interface Guide).
Changing the loopback IP address causes the network element to undergo a warm
reset.
Cross connection identifiers are automatically updated on all NEs in the network.
As the updates are occurring, duplicate wave key alarms are raised.
The 1354 RM-PhM detects the NE resetting and reconnects to it using the new IP
address.
...................................................................................................................................................................................................
On the 1354 RM-PhM, delete the old loopback or DCN port IP address by doing the
following:
1. Select the network element in the topology view, right-click and choose Properties.
The Properties window for the network element is displayed.
2. Click the Associations tab.
3. Select the old loopback or DCN port IP address in the table, and click Delete.
A dialog box asks you to confirm the delete command.
4. Click Yes.
5. Click OK to save the properties
Updates are completed and alarms are automatically cleared within several minutes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-12
February 2011
....................................................................................................................................................................................................................................
To add a network element to a protected path in an existing network
Note: Refer to the Alcatel-Lucent 1830 Photonic Service Switch 32/16

(PSS-32/PSS-16) Release 3.5.0 Installation and System Turn-Up Guide for additional
in-depth details of this procedure.
The following procedure allows for the addition of network elements to a protected path
in an existing network.
...................................................................................................................................................................................................
Export services Export services to an XML file.

...................................................................................................................................................................................................
From Wavelength services APS groups, change the working and protection paths of
protected services so that the traffic is flowing on the short leg.
...................................................................................................................................................................................................
Unmanage the protected services that will be affected from the link removal (in this case
the long leg). Traffic will still flow, but 1354 RM-PhM will not manage the services.
...................................................................................................................................................................................................
Delete the unprotected service that will be affected. This unprotected service will be
restored in the final step.
Note: This step is service impacting
...................................................................................................................................................................................................
Using the Facility/Connection View, delete cross connects associated with the external
port (LD or line) for the external topology connection on the path where the new node
will be inserted. There should be a cross connect on each node for a protected service, so
in this case you will be removing the cross connects associated with the long leg path at
each node.
...................................................................................................................................................................................................
Delete one of the external topology connections between the existing NEs on the line
where the new NE will be added (the long leg).
...................................................................................................................................................................................................
Add the new NE (this step can be done first if you want to give it time to discover).
Provision/Commission new NE. Make sure topology connections exist between the newly
added node and the existing nodes. If they are missing, service import will fail, but it will
be evident in the error message that this is the issue.
...................................................................................................................................................................................................
Import services using the XML file from Step 1.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-13
February 2011
....................................................................................................................................................................................................................................
To delete a network element
Refer to the Alcatel-Lucent 1830 Photonic Service Switch 32/16 (PSS-32/PSS-16) Release
3.5.0 Installation and System Turn-Up Guide for this procedure.
....................................................................................................................................................................................................................................
3-14
February 2011
....................................................................................................................................................................................................................................

The only type of link that can be created by the user is the fiber link. All other link types
are created and discovered automatically by the 1354 RM-PhM.
To configure a topological connection from the Topology view
Use this procedure to add a topological connection to the network.

...................................................................................................................................................................................................
In the 1354 RM-PhM Topology view, select the network elements between which you
want to create a connection.
...................................................................................................................................................................................................
Click the topological connection button.

The Create Topological Connection window is displayed.
...................................................................................................................................................................................................
For each of the network elements, use the drop-down menu to choose the port to which to
connect.
...................................................................................................................................................................................................
Click OK.
The connection is created and is displayed on the map.
E...................................................................................................................................................................................................
N D O F S T E P S
To configure a topological connection from the Physical Topology view
Use this procedure to add a topological connection to the network.

...................................................................................................................................................................................................
In the 1354 RM-PhM Physical Topology view, select a network element from the tree
view.
The cards and ports on the network element are displayed.
...................................................................................................................................................................................................
Select the fiber start point port. The port identifier is displayed in the Fiber Start Point
field.
...................................................................................................................................................................................................
In the tree view, select the next network element.

The cards and ports on the network element are displayed.
....................................................................................................................................................................................................................................
3-15
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the fiber end point port. The port identifier is displayed in the Fiber End Point
field.
...................................................................................................................................................................................................
Click the Connect Fiber Endpoints icon.

The connection is created and is displayed in the Topology view.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-16
February 2011
....................................................................................................................................................................................................................................

Use this procedure to list the topological connections for a network element. This
includes SONET wavelength, control network, and OSCT control network links.
To show topological connections
...................................................................................................................................................................................................
In the 1354 RM-PhM Topology view, select a network element.

...................................................................................................................................................................................................
Click the Display Topological Connections icon.

The Topological Connections window is displayed with the connections to that network
element listed.
E...................................................................................................................................................................................................
N D O F S T E P S
To automatically switch protected services off of a link
Use this procedure to switch protected services off of a link between two network
elements.
...................................................................................................................................................................................................
Select the link off of which you want to switch services:
In the 1354 RM-PhM Topology view, select the link off of which you want to switch
services, and click Properties.
The Topological connections window is displayed. In the Topological connections
window select the link off of which you want to switch services, and click Move
Traffic.
In the 1354 RM-PhM Physical Topology view, select the fiber off of which you want
to switch services, and click Move Traffic.
The 1354 RM-PhM displays a list of any unprotected services on the link that cannot be
moved off automatically. You must move these services manually.
...................................................................................................................................................................................................
Click Next.
The 1354 RM-PhM displays a list of protected services on the link that can be moved off
automatically.
...................................................................................................................................................................................................
Click Finish.
....................................................................................................................................................................................................................................
3-17
February 2011
....................................................................................................................................................................................................................................
The 1354 RM-PhM performs a protection switch on the protected services.

E...................................................................................................................................................................................................
N D O F S T E P S

Before you can provision services in the network, you must define the network fiber
topology. The fiber topology defines how the network element interfaces are connected
using optical fibers. The network element uses this information as follows:
to simplify service provisioning. With the topology defined, the network element
knows which ports a channel passes through as it traverses the network element. This
knowledge allows you to provision a service by specifying only the service endpoints
on each NE through which the service passes. The NE then uses the topology
definition to propagate the values to the other ports on the NE through which the
service passes.
to enable automated power management. Power management allows you to balance
channel ingress and egress powers to simplify troubleshooting.
to allow you to view the fiber connectivity remotely.
For a particular interface (shelf, slot, and port) you can specify that the interface is:
connected to another interface (shelf, slot, and port) on the network element
connected to an external interface, either within or outside of the 1696 ROADM and
1830 PSS network
unconnected
To define the network topology, you first configure the fiber topology on each of the
network elements in the network. After you have defined the topology on all of the
network elements, you connect the external interfaces on each of the network elements to
create the network.
Channel spacing rules for 10G channels adjacent to 40G channels
Channels +/- 50GHz from a 40G signal may not be used unless the 40G signal has passed
through an ITLB or a 50GhZ WSS (drop <or thru> direction of a CWR8-88). The
restrictions include the following:
1. If the 40G demand enters through a colorless port (CLS) on the CWR8-88, then the
NE will block 10G channels from being allowed on the adjacent (50GHz away)
channels for the same optical line as the 40G channel. This restriction applies to add,
mesh, and thru channels at this node only. The restriction is limited to the node at
which the 40G channel is added colorlessly. The remainder of the path is not restricted
until it possibly passes through a regeneration location. If the 40G channel is added
colorlessly at both ends, then the restriction occurs for the optical lines at each end of
the demand.
2. For 40G demands - there are no restrictions on neighbor channels 100GHz away.
....................................................................................................................................................................................................................................
3-18
February 2011
Configuring the network element and network fiber

topology
....................................................................................................................................................................................................................................
3. If the 40G demand enters through a SFD44/ITLB/CWR8-88, then there is no

restriction on neighbor (50GHz away) channels.
4. If the 40G demand enters through a SFD44/CWR8 or through a colorless port (CLS)
on the CWR8, then the NE will block channels from being allowed on the adjacent
(50GHz away) channels for the length of the demand route in the network until after it
passes thru the 50GHz WSS on the CWR8-88, or passes thru an ITLB.
If the 40G demand makes a mesh connection from a CWR8 towards a CWR8-88 (it is
a mesh add channel at the CWR8-88), then the NE will block 10G channels from
being allowed on the adjacent (50GHz away) channels for the same CWR8-88 optical
line as the 40G channel. This restriction applies to add, mesh, and thru channels at this
node. There would be no restrictions further down the route until the next
regeneration location.
Bidirectional single-fiber transmission
Some applications require bidirectional transmission over a single fiber. Bidirectional

single fiber transmission is achieved via the PhM by creating 2 unidirectional services
between the same client ports (one in the A to Z direction, one in the Z to A direction).
A PSS-32 FOADM CWDM node can be configured to support bidirectional transmission
over a single fiber using CWDM filters. Each bidirectional transmission requires different
CWDM wavelengths in each direction. This is accomplished with 2 fiber connections
(transmit and receive) from the OT to two adjacent wavelengths connections on the MUX
(in) side of the filter. The wavelengths pass between the MUX side of the filter and the
OMD out port in both the receive and transmit directions. The single fiber connected to
the OMD out port carries signals in both directions on their assigned wavelengths.
Bidirectional transmission over a single fiber is supported with any of the following
filters and OTs:
SFC-2(A, B, C, or D)
SFC-4(A or B)
SFC-8
4DPA4
11STAR1
11STMM10
11DPE12
For additional details regarding bidirectional single-fiber transmission, see the

Alcatel-Lucent 1830 PSS Product Information and Planning Guide.
Configuring the fiber topology on a network element
To configure the fiber topology on a network element, you use the physical topology view
to select and connect the interfaces. You do not need to configure any unconnected
interfaces. External interfaces are configured using the topology view (see Connecting
....................................................................................................................................................................................................................................
3-19
February 2011

topology
....................................................................................................................................................................................................................................
the network element external interfaces (p. 3-21)). If you make a mistake, or are
reconfiguring the network element, you can disconnect two previously connected
interfaces.
To connect two interfaces on the network element
Refer to the cabling diagram for the network element when performing this procedure.
...................................................................................................................................................................................................
Select the network element you want to configure and click the Physical Topology icon.
A shelf view of the network element is displayed in a new window, showing the current
configuration. Any currently configured connections are displayed in green text below the
interface name.
...................................................................................................................................................................................................
Select the two interfaces you want to connect and click on the connect icon. (To unselect
an interface, press and hold the CTRL key and click the interface).
The shelf, slot, and port of the interface to which the interface is connected is added in
green text below the interface name, and a line connecting the two points is added to the
display to represent the physical fiber.
Unidirectional connections can be configured for the following port combinations, against
the 1830 PSS NE type only:
CWR8 CLS port to 4DPA4 line port
CWR8-88 CLS port to 4DPA4 line port

SFD shelf or card channel port to 4DPA4 line port
11QPA4 card
The user can connect ports together unidirectionally by selecting the ends and then using
the Uni-Connect toolbar icon or right clicking and selecting Uni-Connect. On a port
selection that supports unidirectional topology, the green line indicates Connected To port
and the Orange line indicates the Connected From Port. Arrow mark indicates the
direction in which the light flows.
E...................................................................................................................................................................................................
N D O F S T E P S
To disconnect two interfaces on the network element

...................................................................................................................................................................................................
In the physical topology view, select the two interfaces you want to disconnect and click
on the disconnect icon.
....................................................................................................................................................................................................................................
3-20
February 2011

topology
....................................................................................................................................................................................................................................
The line representing the fiber and the green text indicating the shelf, slot, and port of the
interface to which the interface was connected is removed from the display.
E...................................................................................................................................................................................................
N D O F S T E P S
Connecting the network element external interfaces
A network element external interface can connect to another network element in the 1696
ROADM and 1830 PSS network, or it can connect to a client interface external to the
1696 ROADM and 1830 PSS network. After configuring the network element topology,
use the topology view to select and connect external interfaces on a pair of network
elements.
To connect the external interfaces on two network elements within the 1696
ROADM and 1830 PSS network
...................................................................................................................................................................................................
Choose Provision > Physical Topology and select one of the network elements you want
to connect. Hold down the CTRL or Shift key when selecting the second network
element.
...................................................................................................................................................................................................
Click on the icon that allows you to add a topological connection between two NEs.
...................................................................................................................................................................................................
Select OTS from the Rate field scroll list.

...................................................................................................................................................................................................
Select, from the scroll list for each network element, the interfaces you want to connect.
The list of available interfaces includes all unconnected interfaces that match the selected
rate.
...................................................................................................................................................................................................
Enter a label for the connection in the Label field.

E...................................................................................................................................................................................................
N D O F S T E P S
To determine the network element connectivity across the network
Double-click on the external connection.

Performing a light path trace
The 1354 RM-PhM can display the path of a selected channel through the 1696 ROADM
and 1830 PSS network.
....................................................................................................................................................................................................................................
3-21
February 2011

topology
....................................................................................................................................................................................................................................
To perform a light path trace

...................................................................................................................................................................................................
In the Physical Topology view, select an interface port on a card.

...................................................................................................................................................................................................
Click the Begin a lightpath trace icon.
If you selected a single-channel port, the light path for that channel is displayed as a
series of lines from interface to interface.
If you selected an interface that can have multiple channels, a list of all of the bands
and channels that are applicable to that interface is displayed, whether or not they are
active. Select the desired band and channel from the list and click OK. The light path
is displayed as a series of lines from interface to interface.
...................................................................................................................................................................................................
To clear the light path trace, click the Clear the lightpath trace icon.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-22
February 2011
....................................................................................................................................................................................................................................

The Wavelength Tracker capability allows you to locate and manage services and
equipment using Wave Key or band and channel information.
To use the Wavelength Tracker capability
...................................................................................................................................................................................................
From the 1354 RM-PhM, choose View > Wave Key Encoder Lookup....
The Wavelength Tracker window is displayed.
...................................................................................................................................................................................................
Specify the search criteria. You can search on Wave Keys, or you can specify the band
and channel. Click Retrieve.
Items that match the specified criteria are displayed in a list beside the search criteria. The
Wavelength Tracker window offers the following capabilities:
display the list of equipment on which keys are encoded, enabled, or detected
display WDM port in/out optical power measurements
display cross-connects on CTPs
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-23
February 2011
....................................................................................................................................................................................................................................

To display optical power levels along a service path
...................................................................................................................................................................................................
In the 1354 RM-PhM Topology View, select a network element.

...................................................................................................................................................................................................
Click the Wavelength Services icon.

The Wavelength Services window is displayed.
...................................................................................................................................................................................................
In the Wavelength Services window, select a service and click one of the following icons:
Power (A-Z)
Power (Z-A)
The power trace window is displayed similar to that shown in the following figure.
Figure 3-1 Uni-directional light path power window
Note: Each of the detection points listed in the power window are live. To open the
Facility/Connection view for a detection point, double-click it.
...................................................................................................................................................................................................
To refresh the power measurements manually, click the Refresh icon

.
....................................................................................................................................................................................................................................
3-24
February 2011
....................................................................................................................................................................................................................................
To refresh the power measurements automatically, check the Auto Refresh check box, and
use the slider to specify the refresh rate in seconds.
...................................................................................................................................................................................................
To use the automatic power management capability, refer to To manage power levels
along a light path (p. 3-35).
E...................................................................................................................................................................................................
N D O F S T E P S
To display optical power levels at a Wavelength Tracker detection point
Note: Wavelength Tracker detection points are located on the following ports:
For 1830 PSS:
ALPHG Line In, DCM To, Sig Out

AHPHG Line In, DCM To, Sig Out
CWR8/CWR8-88 CLS{1-8} In, CLS{1-8} Out, OMD In, Sig In, Sig Out, Thru
Out
OPS SP Input, SW Input 1, SW Input 2
For 1696R:
MSA - AMP IN, MSA OUT, AMP OUT

OSCT - WDM IN and WDM OUT
BOF - WDM IN and WDM OUT

BBAs - AMP IN and AMP OUT
ROADM - WDM IN and THRU OUT
WSS
PPS - A and B IN
The following 1696R Wavelength Tracker detection points are located on the WSS
card:
WDM IN
WDM OUT
BB IN
THRU OUT
ADD/DROP IN
ADD/DROP OUT
...................................................................................................................................................................................................
Right click on a power bar in the lightpath power trace window and select All channel
powers.
....................................................................................................................................................................................................................................
3-25
February 2011
....................................................................................................................................................................................................................................
Result: Optical power levels are displayed:

Figure 3-2 Optical power levels at a Wavelength Tracker detection point
Note: Each of the detection points listed in the power window are live. To open
the Facility/Connection view for a detection point, double-click it.
...................................................................................................................................................................................................
To refresh the power measurements manually, click Refresh.

...................................................................................................................................................................................................
To save the power values in this window to a file, click the Export button.
Specify a directory and filename for the file. The power values are saved to a comma
separated value (CSV) file which can be imported into a spreadsheet for easy viewing.
...................................................................................................................................................................................................
To use the automatic power adjustment capability, refer to To manage power levels at an
ingress or egress monitor point (p. 3-32).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-26
February 2011
....................................................................................................................................................................................................................................
Setting the expected power directly in the lightpath trace

...................................................................................................................................................................................................
From the lightpath trace, the expected power can be set by selecting the zed bar by left
mouse click and then dragging the zed bar to a new power level. Release the left mouse
button to set the new expected power level.
E...................................................................................................................................................................................................
N D O F S T E P S
Setting the expected power and deviation using the facility/connection view
...................................................................................................................................................................................................
Open the facility/connection view for a node by selecting the node in the topology view
of the PhM and right clicking. Then choose Provisioning > Facility / connection.
...................................................................................................................................................................................................
Select the port of interest and expand the drop down list to show the channel list. Select
the channel of interest by left mouse click.
Result: The Details box to the right shows the attributes for this channel.
...................................................................................................................................................................................................
Change the expected power by entering a new value in the Out/In Expected Power (dBm)
box.
...................................................................................................................................................................................................
Change the expected power deviation by entering a new value in the Out/In Expected
Power Dev (dB).
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
Setting the expected power navigating from the inventory view

...................................................................................................................................................................................................
Open the inventory view for a node by selecting the node in the topology view of the
PhM and right clicking. Then choose Provisioning > Open Existing Inventory.
....................................................................................................................................................................................................................................
3-27
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the pack of interest and expand the drop down list to show port list. Select the port
of interest by left mouse click and then right mouse click and select Optical Power Mgmt
> Optical Power Mgmt In/Out
Result: The WT measured power level for each channel is displayed.
...................................................................................................................................................................................................
Left mouse click the zed bar for a channel and drag it to a new power level. Release the
left mouse button to set the new power level.
Note: The same screen can be reached by right mouse clicking a power bar in the
lightpath trace and selecting All Channel Powers
Note: The expected power and deviation can only be set directly by the user for detect
points that are Manually power managed. The power management type is noted above
the power bars in the lightpath trace.
E...................................................................................................................................................................................................
N D O F S T E P S
To configure WaveKey expected power levels and Deviations along a lightpath from the lightpath
trace
...................................................................................................................................................................................................
Open a lightpath trace for a service in one direction.

...................................................................................................................................................................................................
To synchronize the expected power levels to the current measured power levels click the
icon above the lightpath trace with a key and small bars below it.
...................................................................................................................................................................................................
Confirm you want to set the expected powers and the expected powers are reset.
Note: Only the expected powers at Manually power managed detect points will be set.
Important! You should only set the expected power levels if you have adjusted the
lightpath power levels to match the planned power levels for the service. If you
synchronize the power levels before making power adjustments, you may not notice
that the service follows an incorrect power profile along its path.
...................................................................................................................................................................................................
To set expected power deviations along a service, click the icon above the lightpath trace
with a key and a small + and above and below the key, respectively.
...................................................................................................................................................................................................
Enter a value to apply to all detect points and click OK.
....................................................................................................................................................................................................................................
3-28
February 2011
....................................................................................................................................................................................................................................
Note: It is normal for the set to fail at auto power managed detect points because it is
not possible to set the deviation directly for these points. Also, the deviation should
not be set lower than 2.5 dB, normally, to avoid causing power out of range alarms
when power levels change due to normal network operations such as service
provisioning and deletion.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-29
February 2011
....................................................................................................................................................................................................................................

How power management is configured
Every port in a network element has a power management type setting. Ports connected to
external are configurable by the user, to either automatic or manual. When the external
ports are set, all of the internal port settings are set by the network element to be the same
as the external port setting, according to the intranode topology connections. Lines
connected across the through path must have matching power management types.
Therefore, when an external port is set to automatic, all ports along the network element
are automatically power managed.
Ports whose topology can be set to external and support power management type Auto
are:
1696R: OSCT pack WDM Out/In
1830: LD pack Line Out/In
Any other ports whose topology is connected to external must be set to power
management type Manual. When a port is changed to external, its power management
type setting changes to Auto if it is an 1830 LD Line port, otherwise the port power
management type remains unchanged. When a port is changed to internal, the mode
setting reverts to the correct value based on the setting of the external ports.
For 1696R, the OSCT WDM ports default to connected to external, and the default power
management type is Auto. The user can change the type to Manual.
For 1830, the LD Line ports of a pack equipped with an OSCT channel default to
connected to external, and the default power management type is Auto. The user can
change the type to Manual.
The power management type of a port connected to external can be changed in the 1354
PhM inventory view of the port.
....................................................................................................................................................................................................................................
3-30
February 2011
....................................................................................................................................................................................................................................
How auto power management operates
The goal of automatic power management is to get the power levels of all channels
entering or leaving a network element to be within a defined target range. Target power
ranges are specified at the monitor points of the network element:
1696R:
ingress monitor point ingress BBA/MSA AMP OUT port

egress monitor point last OUT port on the network element to which the
network fiber is connected (OSCT WDM Out)
1830:
ingress monitor point ingress LD SIG OUT

egress monitor point - last OUT port on the network element to which the network
fiber is connected (reverse direction ingress LD LINE OUT)
The network element power management adjusts the power levels of each channel as
necessary to achieve the target power levels at the monitor points. Adjustment of locally
added channels is automatic. Spectral equalization through WSS/CWR8 pack Thru or
CLS ports is automatic. Changes to Amp/LD gain settings must be triggered by running
the Ingress Adjustment or Egress Adjustment function. For more details on automatic
power management refer to the 1830 PSS-32/PSS-16 User Provisioning Guide and 1830
PSS-32/PSS-16 Installation and System Turn-up Guide.
The 1354 RM-PhM provides user control of the 1696 ROADM and 1830 PSS platform
power management capabilities. The 1354 RM-PhM allows the operator to:
adjust gain on ingress amps
adjust the gain on the ingress amp to calculate a new gain based on all known
wavelengths
set expected powers for detect points associated with the ingress portion of the
line
the gain can be adjusted on a manual point. On an autopower managed point, the
gain is calculated by the NE during an adjustment.
adjust the egress point

adjusts power along the path from the ROADM/WSS/CWR8 card thru port, the
egress LD/amp, to the egress point; sets the egress LD gain.
1830:
Modifies the CWR8 Thru, and mesh connected CWR8 CLS port channel powers
by adjusting the EVOA settings and expected powers.
Modifies the SVAC output power target, or OT output power target, and CWR8
Sig Out power target to achieve the target output power of the egress line.
....................................................................................................................................................................................................................................
3-31
February 2011
....................................................................................................................................................................................................................................
1696R:
Modifies the WSS/ROADM, and WSS mesh connected WSS drop port channel
powers by adjusting the EVOA settings and expected powers.
Modifies the COFs, CADs, and transponder output power target, and WSS
WDM Out power target to achieve the target output power of the egress line
manual setting of the egress LD gain, and the setpoints for the ROADM/WSS/CWR8,
and COF/CAD, OT, SVAC are allowed for a manual line.
Modify power management attributes for ingress and egress adjustment points.
The PhM provides interfaces to:
sync power at network element Wavelength Tracker detect points

syncing power sets the expected power to the present power of all detection points
on the through-path
only on manual points
modify the power management attributes for ingress LDs and egress monitor points
that are manually managed
set the target power
set the minimum and maximum gain for the amps
set the WT deviation default (1830 only)
manage spectrum at a power management point
set the expected power for an individual wavelength (only on manual)
set the default per channel expected at a single detection point (only on manual)
The power management functions for auto power managed are accessed from the
inventory and facility views under the menu option Optical Power Mgmt. Also, menus
are available on the lightpath trace charts for:
1696R:
Ingress adjustment at ingress amp pack Amp Out ports; Egress adjustment at
egress OSCT pack WDM Out ports.
1830:
Ingress adjustment at ingress LD pack Sig Out ports; Egress adjustment at egress
(reverse) ingress LD Line Out ports.
To manage power levels at an ingress or egress monitor point
Use this procedure to manage the power levels at a power management ingress or egress
point.
....................................................................................................................................................................................................................................
3-32
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Locate and select the ingress or egress monitor point at which you want to manage the
power levels:
ingress monitor point - ingress BBA AMP OUT port (1696R) / ingress LD SIG OUT
port (1830)
egress monitor point - last OUT port on the network element to which the network
fiber is connected, OSCT WDM OUT port (1696R) / LD LINE OUT port (1830)
Right-click the point and choose Optical Power Mgmt>Power Mgmt Out.
The Power Management window is displayed as seen in the following figures.
Figure 3-3 Ingress monitor point power management window
....................................................................................................................................................................................................................................
3-33
February 2011
....................................................................................................................................................................................................................................
Figure 3-4 Egress monitor point power management window
...................................................................................................................................................................................................
To view or edit the power management attributes for this monitor point, choose Ingress
Power Mgmt>Edit Ingress, or Egress Power Mgmt>Edit Egress.
The monitor point amp and gain attributes are displayed.
The ingress monitor point is always the ingress LD/amplifier for the network element,
therefore the ingress power amp and gain attributes apply to the this monitor point which
is the ingress LD/amplifier for the network element.
The egress monitor point is the last Out port prior to the fiber span. The power attributes
shown when Egress Power Mgmt>Edit Egress is selected, include the attributes for the
line and the attributes for the egress LD/amplifier, if one is present.
...................................................................................................................................................................................................
Edit the attributes if desired and click Apply. Close the window.
...................................................................................................................................................................................................
To adjust power levels based on changes made to the ingress amplifier attributes, choose
Ingress Power Mgmt>Adjust Ingress Power. The system attempts to adjust the ingress
power levels to meet the specifications. This may take a few minutes.
To adjust power levels based on changes made to the egress line attributes, choose Egress
Power Mgmt>Adjust egress Power.
...................................................................................................................................................................................................
To refresh the power measurements, click Refresh.

....................................................................................................................................................................................................................................
3-34
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
After the system has finished the power adjustment, if the adjustment was successful, the
expected powers will be updated automatically.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
To manage power levels along a light path
Note: For Wavelength Tracker detection points see To display optical power levels at
a Wavelength Tracker detection point (p. 3-25)
Use this procedure to manage the power levels along a light path.
...................................................................................................................................................................................................
Select the light path. There are two methods:

Method 1
From the 1354 RM-PhM Topology View, select the network element, right-click, and
choose Provision > Inventory.
The Inventory window is displayed.
Navigate to the Wavelength Tracker detection point for which you wish to display the
optical power levels.
Select the port, right-click and choose Optical Power Mgmt> Light path power.
A list of channels is displayed.
From the channel list, select the channel for which you which to display power levels, and
click OK.
The power chart for both directions of the light path is displayed as seen in the following
figure.
....................................................................................................................................................................................................................................
3-35
February 2011
....................................................................................................................................................................................................................................
Figure 3-5 Bi-directional path power trace
Method 2
To view all services that traverse a particular network element or set of network elements,
select the network element(s) in the 1354 RM-PhM Topology View, and click the
Wavelength Services icon.
The Wavelength Services window is displayed, listing all services on the selected network
elements.
In the Wavelength Services window, select a service and click one of the following icons:
Power (A-Z)
Power (Z-A)
The power trace window is displayed similar to that shown in the following figure.
....................................................................................................................................................................................................................................
3-36
February 2011
....................................................................................................................................................................................................................................
Figure 3-6 Uni-directional light path power window
...................................................................................................................................................................................................
To view or edit the power management attributes at this monitor point, choose Ingress
Power Mgmt>Edit Ingress or Egress Power Mgmt>Edit Egress button.
The monitor point amp and gain attributes are displayed.
The ingress monitor point is always the ingress LD/amplifier for the network element,
therefore the ingress power amp and gain attributes apply to the this monitor point which
is the ingress LD/amplifier for the network element.
The egress monitor point is the last Out port prior to the fiber span. The power attributes
shown when Egress Power Mgmt>Edit Egress is selected include the attributes for the
line and the attributes for the egress LD/amplifier, if one is present.
...................................................................................................................................................................................................
Edit the attributes, if desired, and click Apply. Close the window.
...................................................................................................................................................................................................
To adjust power levels based on changes made to the amplifier attributes, choose Ingress
Power Mgmt>Adjust Ingress Power or Egress Power Mgmt>Adjust Output Power. The
system attempts to adjust the power levels to meet the specifications. This may take a few
minutes.
...................................................................................................................................................................................................
To refresh the power measurements, click Refresh.
....................................................................................................................................................................................................................................
3-37
February 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Once complete, successfully or not, click the Retrieve button to view information about
the results of the power adjustment.
...................................................................................................................................................................................................
After the system has finished the power adjustment, if the adjustment was successful, the
expected powers will be updated automatically.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-38
February 2011
Managing APS groups
....................................................................................................................................................................................................................................
Managing APS groups

Automatic protection switch (APS) groups can be managed by the 1354 RM-PhM. APS
groups cannot be created by the 1354 RM-PhM; they are discovered automatically when
they are created by the provisioning of PPS cards or optical splitters. For more
information about APS groups, refer to the 1830 PSS-32/PSS-16 User Provisioning
Guide.
APS group Rx/Tx status behavior
The APS group Rx/Tx status follows the following qualifier rules:
Rx status:
Active - the selector is selecting this Rx port to receive traffic.

Standby - traffic received on this port is not used.
Unknown - the working and protection cards are unplugged
Tx status:
Active - traffic transmitted on this port is in use.

Standby - traffic transmitted on this port is not used.
Unknown - the Protect Line is failed, or the far end is not configured, or misfibering
has occurred (such as far end working connected to near end protection). A Tx status
of Unknown also occurs if the working and protection cards are unplugged.
Listing APS groups
There are several methods to view APS groups and their attributes:
From the Topology view, select a network element, right-click and choose Provision >
APS Groups. A list of APS groups for the selected network element is displayed.
From the Inventory view, select a port or facility that is part of an APS group (as
indicated by an identifier listed in the APS Group ID attribute field), and click the Edit
Automatic Protection Properties button. The APS attributes for that APS group are
displayed.
From the Services window, select a service and click the APS groups button. A list of
APS groups for the selected service is displayed. Alternatively, you can select a
service, click the Details button, and then click the APS Groups tab.
From a Power Management window for a service, click the APS button. A list of APS
groups for the selected service is displayed.
From a Power Management window for a service, in the column for an APS group
member component, right-click and choose Edit APS. The APS attributes for that APS
group are displayed.
The following figure illustrates the APS Views window which lists the APS groups.
....................................................................................................................................................................................................................................
3-39
February 2011
Managing APS groups
....................................................................................................................................................................................................................................
Figure 3-7 APS Views window
Editing APS group attributes

...................................................................................................................................................................................................
To edit APS group attributes, select the APS group in the APS Views window and click
the Edit button.
The APS Group attributes window is displayed, as follows:
Figure 3-8 APS Group attributes window
....................................................................................................................................................................................................................................
3-40
February 2011
Managing APS groups
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Under the Group tab you can modify the following fields:
Description - a text description of the APS group
Revertive - specifies wether the group reverts back to it original working/protection

configuration after a protection switch has taken place. This attribute operates with the
Wait to Restore attribute.
Direction - specifies whether this is a unidirectional or bidirectional APS group. APS
groups using PPS cards are always unidirectional in which case this field is
non-editable. APS groups using optical splitters can be either bidirectional or
unidirectional and can be specified in this field.
Wait to Restore (min) - specifies how long to wait after a protection switch before
attempting to revert back to the original working/protection configuration
...................................................................................................................................................................................................
To save your changes click Apply Changes.

E...................................................................................................................................................................................................
N D O F S T E P S
To perform a forced or manual protection switch
APS manual and forced protection switching is performed from the APS Group attributes
window.
...................................................................................................................................................................................................
In the APS Group attributes window, select either the Working member or the Protection
member in the APS Members list.
If you selected the Working member in the APS Members list, you can specify one of
the following protection switch types:
To perform a forced protection switch, choose Protection Switch>Force Switch to
Protection.
To perform a manual protection switch, choose Protection Switch>Manual Switch

to Protection.
If you selected the Protection member in the APS Members list, you can specify one
of the following protection switch types:
To perform a forced protection switch, choose Protection Switch>Force Switch to
Working.
To perform a manual protection switch, choose Protection Switch>Manual Switch
to Working.
...................................................................................................................................................................................................
You are prompted to confirm the protection switch. Click Yes.
....................................................................................................................................................................................................................................
3-41
February 2011
Managing APS groups
....................................................................................................................................................................................................................................
The protection switch is performed, and the APS Members list is updated.
...................................................................................................................................................................................................
Click Close.
E...................................................................................................................................................................................................
N D O F S T E P S
To prevent or re-enable automatic protection switching

...................................................................................................................................................................................................
In the APS Group attributes window, select the Protection member in the APS Members
list.
...................................................................................................................................................................................................
To prevent automatic protection switching, choose Protection Switch> Lockout of

Protection.
To re-enable automatic protection switching that was previously locked out, choose
Protection Switch> Clear Protection Switch.
...................................................................................................................................................................................................
You are prompted to confirm the action. Click Yes.

...................................................................................................................................................................................................
Click Close.
E...................................................................................................................................................................................................
N D O F S T E P S
To clear a protection switch

...................................................................................................................................................................................................
In the APS Group attributes window, select the Working or Protection member in the APS
Members list.
...................................................................................................................................................................................................
Choose Protection Switch> Clear Protection Switch.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Close.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-42
February 2011
Managing APS groups
....................................................................................................................................................................................................................................
To perform a manual protection switch of all protected services on a network fiber
Use this procedure to manually switch all protected services on a network fiber to their
alternate paths. This procedure does not switch or interrupt unprotected services.
...................................................................................................................................................................................................
In the Topology view, select the fiber for which you wish to switch all protected services.
Right-click and choose Properties.
The Topological Connection properties window is displayed.
...................................................................................................................................................................................................
Select the desired connection, and click Move Traffic.

You are prompted to confirm the protection switch. Click Yes.
The protection switch is performed, and the protected services are switched to their
alternate paths.
...................................................................................................................................................................................................
Click Close.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-43
February 2011
CLI cut-thru
....................................................................................................................................................................................................................................
CLI cut-thru
The 1354 RM-PhM provides an interface for performing a CLI cut-thru to any managed
element in the network. To perform a CLI telnet cut-thru
...................................................................................................................................................................................................
In the 1354 RM-PhM Topology View or Inventory View, select the object to which you
wish to cut thru.
...................................................................................................................................................................................................
Choose Cut Thru>CLI Cut Thru.

A CLI telnet session is launched.
Note: When a user requests CLI cut-thru, PhM will use telnet or ssh based on the
NE's settings.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-44
February 2011
TL1 cut-thru
....................................................................................................................................................................................................................................
TL1 cut-thru
The 1354 RM-PhM provides an interface for performing a TL1 cut-thru to any managed
element in the network.
To perform a TL1 cut-thru
...................................................................................................................................................................................................
In the 1354 RM-PhM Topology View or Inventory View, select the object to which you
wish to cut thru.
...................................................................................................................................................................................................
Click the TL1 Cut Thru icon and a TLI session is launched.
Note: When the NE is in secure mode, the TL1 cut thru icon is disabled in the toolbar.
Note: When a user requests TL1 cut-thru, 1354 RM-PhM will check if the NE is
encrypted mode. If it is not then a Telnet TL1 session will be launched. Otherwise, no
TL1 session will be launched
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-45
February 2011
WebUI cut-thru
....................................................................................................................................................................................................................................
WebUI cut-thru
The 1354 RM-PhM provides an interface for performing a WebUI cut-thru to the
network.
To perform a WebUI cut-thru
...................................................................................................................................................................................................
In the 1354 RM-PhM Topology View or Inventory View, Click the WebUI Cut Thru icon
and a WebUI session is launched.
Note: When the NE is in secure mode, the WebUI cut thru icon is disabled in the
toolbar.
Note: When a user requests web cut-thru, 1354 RM-PhM will check if the NE is
encrypted mode. If it is not, then an http web session will be launched. Otherwise, no
web session will be launched.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-46
February 2011
4 onitoring system events

M
and network alarms
Overview
Purpose
This chapter explains how to monitor system events and network alarms.
Contents
4-3
4-3
4-7
4-7
4-9
4-9
Suppressing alarms
4-10
4-10
Clearing an alarm
4-11
4-11
4-12
4-12
4-15
4-15
4-16
Viewing PM data and raw PM data
4-17
Configuring PM and TCA profiles
4-17
4-18
4-18
...................................................................................................................................................................................................................................
4-1
February 2011
Overview
....................................................................................................................................................................................................................................
4-19
Determining the WaveKeys used for a service
4-21
4-22
Troubleshooting the WaveKey insertion failed alarm
4-23
Troubleshooting the Missing WaveKey alarm
4-24
Troubleshooting the Unexpected WaveKey alarm
4-26
4-27
Troubleshooting the Invalid WaveKey alarm
4-29
4-30
4-30
....................................................................................................................................................................................................................................
4-2
February 2011

....................................................................................................................................................................................................................................

The 1354 RM-PhM provides a network-wide view of the 1696 ROADM and 1830 PSS
network. Events, such as alarms, are trapped and sent from the 1696 ROADM and 1830
PSS network element to the 1354 RM-PhM. The 1354 RM-PhM Topology View provides
an alarm banner and a count of current alarms that have been received by the 1354
RM-PhM. The 1354 RM-PhM Topology View presents a summary of the alarm counts
based on severity, as shown in Figure 4-1, 1354 RM-PhM Topology View (p. 4-3).
Figure 4-1 1354 RM-PhM Topology View
The alarms presented in the 1354 RM-PhM Topology View window represent only the
alarms currently stored in the 1354 RM-PhM database that have not been cleared, either
manually or automatically. The alarm count is a total count, and includes alarms that are
not displayed due to filter settings.
....................................................................................................................................................................................................................................
4-3
February 2011

....................................................................................................................................................................................................................................
Note: The 1354 RM-PhM Topology View does not maintain any connection with the
current alarm queues on the network element. NE alarms can be acknowledged from
the 1354 RM-PhM alarm view without changing the state of the alarm equipment in
the network. It is the responsibility of individual operating companies to determine
the rules and procedures for the use of the Acknowledge function.
Alarms that have been cleared can be viewed in the report manager window. For more
information see Using the 1354 RM-PhM log view (p. 4-12).
If a network element has been out of contact, or a trap has been missed, the 1354
RM-PhM attempts to retrieve any missed alarms that are present in the network element's
SNMP trap buffer.
Alarms are raised against specific pieces of equipment in the network. The 1354
RM-PhM associates incoming alarms with its persistent view of the network topology.
The topology data that represents a piece of equipment is updated with the alarm counts
for any received alarm. These alarm counts and severities are graphically represented in
the 1354 RM-PhM user interface.
The 1354 RM-PhM provides the network wide view of the 1696 ROADM and 1830 PSS
network. For actions at the nodal level the user can access the craft interface by launching
a telnet cut-thru to the NE's command line interface (CLI). Refer to CLI cut-thru
(p. 3-44) for further information about launching the CLI from the 1354 RM-PhM.
Managed object alarm counts
The managed object graphic, as seen in the topology map, contains fields indicating the
number of unacknowledged alarms as well as the total number of alarms.
The background color of the alarm count field provides a visual indication of the highest
severity level associated with the nodal alarms.
The alarm state of network elements is propagated to the parent location, where the
location is the geographic container. The alarm state of a location is also propagated to
any containing locations. The location color reflects the highest alarm severity of any of
its contained objects. The maximum severity of any alarm is critical (red). The maximum
severity of any unacknowledged alarm is information (green).
Alarm correlation
1354 RM-PhM alarms are marked as New until they have been processed by the alarm
correlation function. The 1354 RM-PhM examines the alarms that it receives to determine
if there is a root cause to the alarms. After they have been processed, their status changes
to either Root Cause or Masked. If a common root cause for multiple alarms can be
determined, and if the alarm correlation capability is enabled, the 1354 RM-PhM can
group the related alarms and display only the root alarms. 1354 RM-PhM alarm
correlation works by going through each of the alarms and finding the corresponding
....................................................................................................................................................................................................................................
4-4
February 2011

....................................................................................................................................................................................................................................
lightpath. For each alarmed lightpath it analyzes its alarms to determine which are root
causes and which are sympathetic (masked) alarms and set the status accordingly. This
reduces the number of alarms that are displayed. The related alarms can also be viewed
by specifying the view options in the Alarm window.
To enable or disable alarm correlation
Use this procedure to turn alarm correlation on or off. Alarm correlation is turned on by
default when the 1354 RM-PhM is installed.
...................................................................................................................................................................................................
In the 1354 RM-PhM, choose Admin > Settings.

...................................................................................................................................................................................................
In the Settings window, click the System Settings tab, and then click the Alarm
Correlation tab.
...................................................................................................................................................................................................
To turn alarm correlation on, check the Enable Alarm Correlation check box.
To turn alarm correlation off, uncheck the Enable Alarm Correlation check box.
E...................................................................................................................................................................................................
N D O F S T E P S
Viewing sympathetic alarms
Use this procedure to view alarms that are being masked by a root cause alarm.
...................................................................................................................................................................................................
In the Alarm panel of the 1354 RM-PhM Topology View window, select the alarm,
right-click on the alarm and choose Sympathetic alarms. (If the Sympathetic alarms menu
item is greyed-out, then there are no Sympathetic alarms related to the selected alarm.).
An alarm window is displayed, listing the sympathetic alarms.
E...................................................................................................................................................................................................
N D O F S T E P S
Alarm list filtering
The fault view can be filtered to show alarms based on severity as well as correlation
state. The filters are accessible from the fault view as buttons on the toolbar.
....................................................................................................................................................................................................................................
4-5
February 2011

....................................................................................................................................................................................................................................
The Severity filter controls the display of alarms based on the severity of the alarm:
If selected, show alarms of that severity.
If not selected, do not show alarms of the severity.
The Cause filter controls the display of alarms based on the cause of the alarm:
Root Cause and Unacknowledged

If selected, show root cause alarms that a user has not acknowledged.
If not selected, do not show unacknowledged root cause alarms.
Root Cause and Acknowledged
If selected, only show root cause alarms that have been acknowledged.
If not selected, do not show acknowledged root cause alarms.
Masked
If selected, show alarms that have a Correlation State of Correlated and are
acknowledged by the correlation service.
If not selected, do not show alarms that have a Correlation State of Correlated
and are acknowledged by the correlation service.
New
If selected, show alarms that have a Correlation State of New and are
acknowledged by the correlation service.
If not selected, do not show alarms that have a Correlation State of New and
are acknowledged by the correlation service.
1354 RM-PhM
If selected, show alarms that have been raised by the 1354 RM-PhM itself.
If not selected, do not show alarms that have been raised by the 1354 RM-PhM.
....................................................................................................................................................................................................................................
4-6
February 2011

....................................................................................................................................................................................................................................
Opening an alarm window for a managed object or

group
Use this procedure to open an alarm window for a managed object or a group. An alarm
window can be opened from any view (topology or inventory) by selecting the object or
group, right-clicking, and choosing Faults.
Fault views may also be opened based on equipment. From the main topology view a
fault view can be opened to show faults on a single NE or on a group. From the inventory
or facility view a fault view can be opened to show faults on a particular card, port, or
channel. The filters are also applied to the scoped fault view.
To open an alarm window for a managed object
...................................................................................................................................................................................................
In the 1354 RM-PhM Topology View, navigate to the desired managed object or group
and select it.
...................................................................................................................................................................................................
Right-click and choose Fault.

The Alarms window is displayed showing alarms associated only with the selected object
or group.
...................................................................................................................................................................................................
Using the Alarms Filters buttons, specify the severities and cause conditions that you wish
to view.
Root Cause - displays the alarms that are considered root alarms, or alarms which
have no correlation to other alarms
Masked - displays the alarms which are correlated to root alarms and which are not
displayed when the Root Cause option is selected
New - displays alarms that have arrived and which have not yet been processed by
alarm correlation
To view all of the alarms correlated to a root alarm, unselect the Masked view option.
Select one of the root alarms, right-click and choose Lightpath faults. A list of the alarms
along that lightpath are displayed.
...................................................................................................................................................................................................
To view details of an alarm, double-click it.
....................................................................................................................................................................................................................................
4-7
February 2011

....................................................................................................................................................................................................................................
The Alarm Details window is displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-8
February 2011

....................................................................................................................................................................................................................................
The Alarm Window displays information about and allows the acknowledgement of
received alarm-level events.
Impact
Acknowledging an alarm does not provide any corrective action. It only indicates that
someone is aware of the alarm and presumably that some action is taking place to resolve
the alarm condition.
Note: Before activating the software on an NE after a software download, all
non-software loading alarms must be set to Acknowledged.
To acknowledge an alarm
...................................................................................................................................................................................................
In the Alarm panel of the 1354 RM-PhM Topology View window, select one or more
alarms, right-click on the alarm(s) and choose Acknowledge.
A check mark appears for the alarm(s) in the ACK column of the alarm window.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-9
February 2011

Suppressing alarms
....................................................................................................................................................................................................................................
Suppressing alarms
Use this procedure to suppress alarms from a selected NE. This is useful for preventing a
flood of alarms when the selected NE is undergoing maintenance.
...................................................................................................................................................................................................
To inhibit alarms, in the 1354 RM-PhM Topology View, select the network element, and
then choose Fault > Inhibit TL1 Messages.
...................................................................................................................................................................................................
To resume receiving alarms, select the network element, and then choose Fault > Release
TL1 Message inhibition.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-10
February 2011

Clearing an alarm
....................................................................................................................................................................................................................................
Clearing an alarm
Use this procedure to clear a 1354 RM-PhM originated alarm from the 1354 RM-PhM
alarm window.
Impact
This procedure only clears the alarms from the 1354 RM-PhM alarm window that
originate from the 1354 RM-PhM. The manual action of clearing an alarm does not imply
that the original problem is fixed. It is up to the maintenance personnel to determine when
it is appropriate to clear an alarm. Alarms that originate from a network element cannot be
cleared from the alarm window. Once the cause of an NE-originated alarm is corrected,
the alarm is removed from the alarm window automatically.
To clear an alarm
...................................................................................................................................................................................................
In the Alarm panel of the 1354 RM-PhM Topology View window, right-click on the
alarm(s) and choose Clear.
The selected alarm are removed from the alarm window.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-11
February 2011

....................................................................................................................................................................................................................................

The log viewer allows you to view and configure the following types of logs:
fault logs
NE event logs
NE request logs
server logs
TCA logs
node restart log - includes controller startup and activity switch
To view the fault log
Use this procedure to view the fault log.

...................................................................................................................................................................................................
From the 1354 RM-PhM Topology View, choose Fault > Log View.
The Log View is displayed. There is a tab for each type of log. Click the applicable tab to
view the desired log type.
E...................................................................................................................................................................................................
N D O F S T E P S
Configuring log sizes and log archiving on the 1354 RM-PhM server
Use this procedure to configure the log sizes and log archiving attributes.
...................................................................................................................................................................................................
In the log view, click the Configure Log Sizes and Log Archive Settings button.
The Configure Logging and Log Archiving on the 1354 RM-PhM Server window is
displayed.
...................................................................................................................................................................................................
From the Log Type drop-down menu, choose the log type you wish to configure.
The current settings for the selected log type are displayed.
....................................................................................................................................................................................................................................
4-12
February 2011

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Configure the attributes as desired:
From the Threshold Type drop-down menu, choose one of Record, or Btye.
Record specifies that the threshold calculation is to be based on the number of

records.
Byte specifies that the threshold calculation is to be based on the size of the log
records.
In the Component Size field, specify the desired component size. The size of each log
component is measured in bytes or records, according to the Threshold Type. At any
given moment, each log (Fault, NE Event, NE Request, Server, and TCA) has a single
active component and a number of inactive components. Log records are added to the
active component. When the active component's size exceeds the Component Size,
the active component is made inactive and a new component is created to become the
active component.
In the Maximum Num Components field, specify the maximum number of
components allowed. If a new component is created thereby exceeding the maximum
number of components, then the oldest component is purged, meaning that it is
deleted and its log records are archived according to the Log Active Settings.
The Maximum Total Size field is not editable. It displays the total size of the log
which is equal to Component Size x Maximum Num Components. = Total Size
...................................................................................................................................................................................................
To configure the Log Archiving Settings, check the desired Log Archiving Mode check
box. Log Archiving Mode selections are Log archiving disabled, Archive as required,
and Archive on schedule.
The log archiving settings attribute fields become active. Configure the attributes as
desired:
Archive Directory (1354 RM-PhM Server) - the directory on 1354 RM-PhM server in
which to store archive files.
Scheduled Archiving Frequency - the scheduled archiving frequency.

Scheduled Archiving Start Date/Time - the date and time to start scheduled archiving.
Last Archive Date/Time - the date and time of the last log archive action.
Last Archive File (1354 RM-PhM Server) - The name of the last log archive file. This
file is on the 1354 RM-PhM server's file system
...................................................................................................................................................................................................
To configure the Log Archive FTP Transfer Settings, check the Enable FTP Transfer to
Remote Server check box.
....................................................................................................................................................................................................................................
4-13
February 2011

....................................................................................................................................................................................................................................
The Log Archive FTP Transfer Settings attribute fields become active. Configure the
attributes as desired:
Enable FTP Transfer to Remote Server

Remote FTP Server - specify the name or the IP address of the remote FTP server
where the log files are to be archived.
Remote FTP Username - specify the username that is to be used to log onto the
remote server.
Remote FTP Password - specify the password that is to be used to log onto the remote
server.
Remote FTP Server Directory - specify the directory path to the log archive directory
on the remote server.
...................................................................................................................................................................................................
To save the settings and close the window, click OK. Otherwise, click Cancel.
E...................................................................................................................................................................................................
N D O F S T E P S
Exporting a log file
The log file can be exported to a comma separated value (.csv) file which then can be
opened using a spread sheet, word processing, or other application. (Note: If the log file
has more than 65536 records, then it cannot be opened completed by Microsoft Excel.
This is an Microsoft Excel limitation. In this case, use a different application to view the
whole file.)
...................................................................................................................................................................................................
In the 1354 RM-PhM Log View, click the tab for the type of log that you which to export.
...................................................................................................................................................................................................
Click the Export to .CVS File button.

...................................................................................................................................................................................................
Specify the location and filename for the exported file.

...................................................................................................................................................................................................
Click OK.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-14
February 2011

....................................................................................................................................................................................................................................
The 1354 RM-PhM gathers performance monitoring data for objects on the 1696
ROADM and 1830 PSS. For a full list of objects and more details on PMs, refer to the
1830 PSS-32/PSS-16 User Provisioning Guide.
....................................................................................................................................................................................................................................
4-15
February 2011

....................................................................................................................................................................................................................................

PM collection is started and stopped for an entire network element.
...................................................................................................................................................................................................
In the 1354 RM-PhM topology view, choose Admin > PM Collection Admin.
The Performance Data Collection window is displayed, listing the discovered network
elements.
...................................................................................................................................................................................................
Select the network element in the list, right-click and choose one of:
PM Collection Start
PM Collection Stop
PM Collection Immediate
...................................................................................................................................................................................................
To automatically collect PMs for newly discovered NEs, check the Auto-start collection
for new NEs check box.
Note: It is recommended that Auto-start of PM collection should be on.
...................................................................................................................................................................................................
Specify the maximum number of days for which to store PM data.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-16
February 2011

....................................................................................................................................................................................................................................

PM data is collected and displayed in 15-minute and 24-hour bins.
...................................................................................................................................................................................................
In the 1354 RM-PhM Inventory view, select the object for which you wish to view PM
data.
...................................................................................................................................................................................................
Right-click the object and choose Performance Monitoring.

The PM window for the object is displayed.
...................................................................................................................................................................................................
To view the raw PM data for this object, click the View raw PM data button.
The Raw Performance Statistics window is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Configuring PM and TCA profiles

To configure TCA profiles from the 1354 RM-PhM, refer to the 1830 PSS-32/PSS-16
User Provisioning Guide.
....................................................................................................................................................................................................................................
4-17
February 2011

....................................................................................................................................................................................................................................

Wavelength Tracker monitors a service as it traverses the network by:
1. Encoding WaveKeys onto the service at the service endpoints.
2. Decoding the WaveKeys at various points along the service path to provide
wavelength identification, path tracing, and power-level monitoring. The WDM ports
on the decoder cards through which the service passes are programmed to expect to
see the WaveKeys for the service as it passes through the cards.
Table 4-1
WaveKey encoding and decoding points
Function
Where performed
WaveKey encoding
OTs and Channel Optical Filter (COF) cards at the service

endpoints.
WaveKey decoding
For 1830 PSS:
ALPHG Line In, DCM To, Sig Out
AHPHG Line In, DCM To, Sig Out
CWR8/CWR8-88 CLS{1-8} In, CLS{1-8} Out, OMD In,

Sig In, Sig Out, Thru Out
OPS SP Input, SW Input 1, SW Input 2
For 1696R:
MSA - AMP IN, MSA OUT, AMP OUT
OSCT - WDM IN and WDM OUT
BOF - WDM IN and WDM OUT
BBAs - AMP IN and AMP OUT
ROADM - WDM IN and THRU OUT
WSS
PPS - A and B IN
The following 1696R Wavelength Tracker detection points are

located on the WSS card:
WDM IN
WDM OUT
BB IN
THRU OUT
ADD/DROP IN
ADD/DROP OUT
....................................................................................................................................................................................................................................
4-18
February 2011

....................................................................................................................................................................................................................................
Alarm generation
Wavelength Tracker alarms are generated when there are inconsistencies in WaveKey data
along the service path, or if expected WaveKeys are missing along the service path.
Wavelength Tracker alarms are useful in detecting provisioning errors and misconnected
fibers and in determining whether or not there is light on the fiber.
Common troubleshooting tasks
This section provides instructions for performing the following tasks commonly used
when troubleshooting Wavelength Tracker alarms.
Determining the source of an alarm (p. 4-19)
Determining the WaveKeys used for a service (p. 4-21)
Querying the WaveKeys (p. 4-22)
Alarm-specific troubleshooting procedures
It also provides the following alarm-specific troubleshooting procedures for alarms

generated by Wavelength Tracker:
Troubleshooting the WaveKey insertion failed alarm (p. 4-23)
Troubleshooting the Missing WaveKey alarm (p. 4-24)
Troubleshooting the Unexpected WaveKey alarm (p. 4-26)
Troubleshooting the Duplicate WaveKey alarm (p. 4-27)
Troubleshooting the Invalid WaveKey alarm (p. 4-29)

You can determine the source of the alarm using the Source field of the alarm notification
listing in the alarm pane or you can click through the topology to pinpoint the alarmed
object.
Using the Source field of the alarm notification
The source of the alarm is displayed in the Source field using the following syntax:
node:object:rack:shelf:slot:port:ITU_channel
Parameter
Description
node
The network element name.
object
A descriptor for the alarmed object. For example, WDM_Channel.
rack
The rack containing the alarmed object. (Rack is always 1 in current

versions of 1696R and 1830.)
shelf
The shelf containing the alarmed object.
....................................................................................................................................................................................................................................
4-19
February 2011

....................................................................................................................................................................................................................................
Parameter
Description
slot
The slot containing the alarmed object.
port
The port containing the alarmed object.
ITU_channel
The alarmed channel. An integer value (19 to 60 for 1696R, 17 to 60 for

PSS-32, 1 to 8 for PSS-1) that identifies the ITU channel carried over the
port. See the Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release
3.5.0 Engineering and Planning Tool User Guide to map ITU channels to
bands, channels and wavelengths.
Note: The source field contains only enough information to uniquely identify the
alarmed object. For example, the ITU channel is not included when it is not relevant.
For example, the string Node_1:WDM_Channel:1:1:3a:1:49 refers to a channel-level
alarm on ITU channel 49 on the WDM port of a BOF card inserted in rack 1, shelf 1, slot
3a.
Drilling down through the topology hierarchy
This method is most useful when only a single alarm is active on the network element.
When an alarm is triggered, the network element and all objects in the hierarchy of the
alarmed object are colored according to the severity of the alarm, as follows:
Red. Indicates a critical alarm.

Orange. Indicates a major alarm.
Yellow. Indicates a minor alarm.
Click down through the hierarchy to locate the alarmed object.

Note: As you traverse the hierarchy, it may take several seconds to color the alarmed
objects as each new view is displayed.
....................................................................................................................................................................................................................................
4-20
February 2011

....................................................................................................................................................................................................................................

Use the Wavelength Tracker view to determine the WaveKeys used for a service. The
WaveKey values are listed in the detailed port attributes displayed when you select the
port on the card used to encode the keys.
To determine the WaveKeys used for a service
...................................................................................................................................................................................................
Choose View > Show Wavelength Services...

...................................................................................................................................................................................................
Select a service and click the Details button.

...................................................................................................................................................................................................
Select the Working Equipment tab.

...................................................................................................................................................................................................
Expand an endpoint NE and select the OT network port.

...................................................................................................................................................................................................
Scroll down the Attribute/Value list until you see the Wavekey 1 and Wavekey 2
attributes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-21
February 2011

....................................................................................................................................................................................................................................

Use the Wavelength Tracker view to query the network WaveKey configuration. The
WaveKey query allows you enter a WaveKey pair and show the ports programmed to
receive the keys, the ports that are receiving the keys, or the ports that are encoding the
keys. Before you can query the WaveKeys, you must know the values of the WaveKeys
used for the service. See Determining the WaveKeys used for a service (p. 4-21).
To query WaveKeys
...................................................................................................................................................................................................
Choose View > Wave Key Encoder Lookup...

...................................................................................................................................................................................................
Enter the WaveKeys in the WaveKey 1 and WaveKey 2 fields.

...................................................................................................................................................................................................
Click on the Retrieve button.

The Network Elements containing ports that match the WaveKey query are listed. Expand
a network element to show the ports on the network element that match the query. Expand
a port to show the channel on the port that matches the query.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-22
February 2011

....................................................................................................................................................................................................................................

This alarm indicates that the port is unable to generate the programmed WaveKey. This
alarm is active when there is no signal on the port, and therefore the port is not able to
generate the WaveKey. This alarm is accompanied by Missing WaveKey alarms for all
ports along the service path.
To troubleshoot a WaveKey insertion failed alarm
...................................................................................................................................................................................................
Determine the source of the alarm.

...................................................................................................................................................................................................
Ensure that the port is connected and that the power level of the incoming signal is within
the specified power level for the port.
E...................................................................................................................................................................................................
N D O F S T E P S
Expected result
The alarm and all associated Missing WaveKey alarms are cleared. If all of the associated
Missing WaveKey alarms are not cleared, continue troubleshooting as described in
Troubleshooting the Missing WaveKey alarm (p. 4-24).
....................................................................................................................................................................................................................................
4-23
February 2011

....................................................................................................................................................................................................................................

This alarm is generated on WaveKey decoder card ports. It indicates that one of the
WaveKeys the port is programmed to expect is not being received. Missing WaveKey
alarms usually appear as multiple alarms along a service path, since a missing WaveKey
at one port affects all downstream ports.
If Missing WaveKey alarms are reported at all ports along a service path, the likely cause
is a loss of signal resulting in a WaveKey insertion failure. See Troubleshooting the
WaveKey insertion failed alarm (p. 4-23).
If Missing WaveKey alarms are reported at several ports along the service path, the likely
cause is an unconnected or misconnected fiber along the service path. You can use the
Wavelength Tracker query or power chart to locate the bad connection. Unless there is
more than one bad connection, fixing the connection clears all of the Missing WaveKey
alarms for the service.
If a missing WaveKey alarm is reported on a single port only, the likely cause is a
configuration error, where the programmed WaveKey for the port is incorrect or not
configured. This alarm may also be due to a bad connection, if the port is the last
monitored port in the service path.
To troubleshoot missing WaveKey alarms (power chart)
...................................................................................................................................................................................................
Determine the source of the alarm. See Determining the source of an alarm (p. 4-19).
Note the ITU channel (wavelength) used for the service.
...................................................................................................................................................................................................
Choose View > Show Wavelength Services.

...................................................................................................................................................................................................
Using the ITU channel retrieved in the first step, select the service from the list of
services and click on the Power (A-Z) or Power (Z-A) icons to display an end-to-end
power graph for the service. Repeat as required until you find a chart on which one or
more power levels is zero. The bad connection is at the first port in the path where the
power level measures zero.
E...................................................................................................................................................................................................
N D O F S T E P S
To troubleshoot a missing WaveKey alarm on (WaveKey query)

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-24
February 2011

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Determine the WaveKeys used for the service. See Determining the WaveKeys used for
a service (p. 4-21).
...................................................................................................................................................................................................
Query the WaveKeys (see Querying the WaveKeys (p. 4-22)) to compare the list of
ports programmed to use the keys with the list of ports on which the keys are present. The
bad connection occurs at the first port along the service path that is programmed to use
the keys but is not receiving the keys.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-25
February 2011

....................................................................................................................................................................................................................................

This alarm is generated on WaveKey decoder card ports. It indicates that WaveKeys,
other than those the port was programmed to receive, are being received on the port. This
alarm may be caused by a provisioning error or by incorrect fibering.
To troubleshoot an unexpected WaveKey alarm
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Query the WaveKeys (see Querying the WaveKeys (p. 4-22)) to compare the list of
ports programmed to use the keys with the list of ports on which the keys are present.
...................................................................................................................................................................................................
Referring to the network plan, determine which of the Programmed Wavelength Tracker
or Present Wavelength Tracker values is correct.
If the Programmed Wavelength Tracker value is correct but the Present Wavelength
Tracker value is not, then there is a misconnected fiber. Referring to the network plan,
re-examine the fiber topology and correct the problem.
If the Present Wavelength Tracker value is correct but the Programmed Wavelength
Tracker value is not then there has been a configuration error. To correct it, synchronize
the WaveKeys across the service, as described in Troubleshooting the Missing WaveKey
alarm (p. 4-24).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-26
February 2011

....................................................................................................................................................................................................................................

This alarm indicates that two or more OT or COF ports are encoding the same set of
WaveKeys. It is likely caused by a provisioning error in the CLI, web interface, or TL1
interface. To fix this alarm, you need to reset the WaveKeys to new values for one of the
services using the duplicate WaveKey pair.
Resetting the WaveKeys is a two step process. You first change the WaveKeys encoded
by the OT/COF card at the service endpoint, and then change the decoder card WDM
ports through which the service passes to expect the new WaveKeys.
To troubleshoot a duplicate key
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Query the WaveKeys (see Querying the WaveKeys (p. 4-22)) to determine the COF
card ports that are encoding the WaveKeys.
...................................................................................................................................................................................................
Refer to the network plan and determine the OT/COF card for which you want to change
the Wave Key encoding. Select the OT/COF card you want to change. Right-click on the
card and choose Allocate WaveKey.
The Wavelength Tracker keys encoded by the OT/COF card are set to new values. Take a
note of the new values.
...................................................................................................................................................................................................
Choose View > Wave Key Encoder Lookup...

...................................................................................................................................................................................................
Enter the WaveKeys determined in Step 4 in the Service Wave Key Query form and click
Retrieve.
The service that uses the OT/COF card with the new WaveKeys is listed in the
Wavelength Tracker results pane.
...................................................................................................................................................................................................
Select the service and click on the Provision new wavelength tracker keys icon.
....................................................................................................................................................................................................................................
4-27
February 2011

....................................................................................................................................................................................................................................
Result: The WaveKey decoder cards in the service path are updated to expect the new
wavekeys.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-28
February 2011

....................................................................................................................................................................................................................................

Generated on WaveKey decoder card ports. Since the system does not allow you to
program WaveKeys that are out of range for a specific band and channel, this alarm is not
normally generated. It is seen only if expected WaveKeys are programmed for a port and
then the programmed band for the port is changed, making the previously programmed
WaveKeys invalid.
To troubleshoot an Invalid WaveKey alarm
...................................................................................................................................................................................................
...................................................................................................................................................................................................
From the Topology View, right-click on the network element containing the card and
select Provision > Facility / Connection.
...................................................................................................................................................................................................
Locate the card and port for the alarm and expand to list the channels on the port.
...................................................................................................................................................................................................
Select the alarmed channel and change the expected WaveKeys to the correct values for
the service.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-29
February 2011

....................................................................................................................................................................................................................................

Use this procedure to determine the reason for a power out of range alarm. Typically, a
power out of range alarm occurs during provisioning and installation and is cleared in the
course of configuring the network to match the network plan.
In an in-service network, a power out of range alarm occurs as a result of a kinked or
dirty fiber. The 1354 RM-PhM helps isolate the fault and focus the maintenance effort.
Impact
Depending on the root cause and severity of the power out of range alarm, traffic can be
interrupted until the fault is resolved.
To troubleshoot a power out of range alarm
...................................................................................................................................................................................................
Right-click on the alarm and select Inventory view.

...................................................................................................................................................................................................
The inventory view for the network element is opened with the alarmed port selected.
...................................................................................................................................................................................................
Expand to show the WDM channels on the port.

...................................................................................................................................................................................................
Select the alarmed channel. The attributes for the channel are displayed.
...................................................................................................................................................................................................
Refer to the network plan and confirm that the values specified in the Expected Power
and Power Deviation fields are correct:
If the values correspond to the network plan, note the WaveKeys used for the service
and proceed to Step 6.
If the values do not correspond to the network plan, correct them and then click
Apply:
If the alarm clears, you are done.
If the alarm does not clear, note the WaveKeys used for the service and proceed to
Step 6.
....................................................................................................................................................................................................................................
4-30
February 2011

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Monitor the power across the service to isolate the location and nature of the fault, and
adjust the power levels as required to remedy the fault condition.
1. Choose View > Show Wavelength Services
2. Enter the WaveKeys determined in Step 5 in the Service WaveKey Query form and
click Retrieve.
A list of services that use the specified WaveKey pair is displayed.
3. Select the service and click on the Power (A-Z) or Power (Z-A) icons to show the
channel power for the service across the network in either the A to Z direction or Z to
A direction.
4. If the provisioned power levels meet the specifications contained in network plan, the
problem is likely due to a dirty or kinked fiber. Use the power trace information for
the service to localize the fault and repair as required.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-31
February 2011

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-32
February 2011
5354 RM-PhM alarm

1
reference
This chapter provides an alphabetical listing of all of the alarms generated by the 1354
RM-PhM. The following information is provided for each alarm:
A description of the alarm that includes the possible root cause.

Alarm severity.
Whether or not the alarm is service-affecting.

The cards or systems to which the alarm applies.
The condition for the alarm.
The corrective action required to clear the alarm.
...................................................................................................................................................................................................................................
5-1
February 2011

....................................................................................................................................................................................................................................

A communication failure occurred when the 1354 RM-PhM was attempting to make a
request to the NE.
Severity
Critical - both the loopback IP address association and the DCN

port association to the NE are out of service.
Warning - one of the associations to the NE is out of service.
Service affecting?
No
Source
ASSOCIATION:NE_NAME:NE_ADDRESS
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
In the Topology view, select the NE, right-click and choose Properties.
The Properties window is displayed.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select one of the entries in the Associations window (either the loopback IP address or the
DCN port IP address) and click the Reconnect button. If the status of the selected
association changes to Active, continue at the next step. If the 1354 RM-PhM cannot
establish a successful connection, select the other association and click Reconnect.
If the status of the selected association changes to Active, continue at the next step. If the
1354 RM-PhM cannot establish a successful connection, then there is a problem with the
NE which must be fixed before communications can be re-established with the 1354
RM-PhM.
...................................................................................................................................................................................................
Launch a web browser. In the address field type the loopback or DCN port IP address of
the NE and press Enter.
....................................................................................................................................................................................................................................
5-2
February 2011

....................................................................................................................................................................................................................................
If the system prompts you to log in to the NE, then the NE is reachable from the 1354
RM-PhM and is communicating correctly. Cancel out of the login screen, close the
browser, and proceed at the next step.
If the system does not prompt you to log in to the NE, then there is a problem with either
the communication path to the NE, or else the NE is out of service.
...................................................................................................................................................................................................
Restart the server.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-3
February 2011

....................................................................................................................................................................................................................................
Severity
Major
Service affecting?
No
Source
NE_NAME
Type
PROCESSING_ERROR
Applicability
Fault
Corrective action
...................................................................................................................................................................................................
In the 1354 RM-PhM topology view, selects the NE(s) for which you want to
resynchronize the faults, and choose Maintenance>Resync Faults.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-4
February 2011

AutoUpgradeFailure
....................................................................................................................................................................................................................................
AutoUpgradeFailure
A NE failed an automatic software upgrade.
Severity
Minor
Service affecting?
No
Source
TNSWDLSERVICE
Type
PROCESSING_ERROR
Applicability
Auto Upgrade
Corrective action
...................................................................................................................................................................................................
Ensure all alarms on the NE are acknowledged.

...................................................................................................................................................................................................
Ensure that the NE is not currently being discovered. When a NE is being discovered
there is an hour-glass icon displayed on the shelf icon in the tree view in the 1354
RM-PhM.
...................................................................................................................................................................................................
Ensure that the NE database backup parameters are correct. In the 1354 RM-PhM
Topology view, select the NE, and choose Admin>NE Database Backup and Restore. The
NE Backup and Restore window is displayed in which you can examine and if necessary,
change the settings.
...................................................................................................................................................................................................
Ensure that the NE has network connectivity. Refer to the corrective action for A
communication failure occurred (p. 5-2).
...................................................................................................................................................................................................
Ensure that the NE has a route to the TFTP server. In the 1354 RM-PhM Topology view,
select the NE, and choose Cut Thru>Web Cut Thru.
A web interface session is launched. Log into the web interface.
From the menu hierarchy on the left-hand side of the web interface window, choose
Control Network>Ping. A ping window is displayed. Type the IP address of the TFTP
server into the IP Address field and click Ping.
....................................................................................................................................................................................................................................
5-5
February 2011

AutoUpgradeFailure
....................................................................................................................................................................................................................................
If the web interface indicates a successful connection, continue at the next step. If the web
interface cannot ping the TFTP server, a route must be added from the NE to the TFTP
server.
...................................................................................................................................................................................................
Verify that the TFTP root directory is configured properly.

...................................................................................................................................................................................................
Ensure that the TFTP server is running on the software server. Consult your system
administrator for this.
...................................................................................................................................................................................................
Perform a software upgrade audit of the NE using the same NE(s), software load, and
options as the failed upgrade. If the system is unable to create a valid upgrade script,
examine the script for problems and correct them.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-6
February 2011

CardOutOfSync
....................................................................................................................................................................................................................................
CardOutOfSync
The 1354 RM-PhM has identified that its data relating to that card is not in sync.
Severity
Warning
Service affecting?
No
Source
card id
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Once communication is established and verified, resynchronize the card. Access the
Inventory view for the NE, select the card, and click the Resynchronize button.
...................................................................................................................................................................................................
If the problem persists, resynchronize the entire NE. In either the Topology view or the
Inventory view, select the NE and click the Resynchronize button.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-7
February 2011

....................................................................................................................................................................................................................................
A communication failure occurred when the 1354 RM-PhM was attempting to make a
request to the NE.
Severity
Critical or Warning
Service affecting?
No
Source
CONNECTOR:SNMP:IP address
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
Refer to the corrective action for A communication failure occurred (p. 5-2).
....................................................................................................................................................................................................................................
5-8
February 2011

....................................................................................................................................................................................................................................
An error occurred attempting to save an Association to the database
Severity
Critical
Service affecting?
No
Source
SimpleConfigPolicy
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
Delete the NE from the 1354 RM-PhM. In the Topology view, select the NE, right-click
and choose Delete. Click Yes in response to the prompt.
...................................................................................................................................................................................................
Rediscover the NE. Click the Create a new NE button.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-9
February 2011

Creation Failure
....................................................................................................................................................................................................................................
Creation Failure
An error occurred when attempting to create a component. This condition is specific to
SNMP NETypes which are managed by the default SNMP service adapters.
Severity
Minor
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-10
February 2011

....................................................................................................................................................................................................................................

The same wavekey is being encoded by two different Wavelength Tracker encode points.
If the 1354 RM-PhM is managing more than one ring, and the duplicate wavekeys are on
different rings, then this alarm is not a problem unless an unexpected channel alarm is
also present. If the duplicate wave keys are on the same ring, then perform the corrective
actions.
Severity
Warning
Service affecting?
No
Source
WAVELENGTH TRACKER
Type
PROCESSING_ERROR
Applicability
Wavelength Tracker
Corrective action
...................................................................................................................................................................................................
If the 1354 RM-PhM is managing multiple rings that contain services that are keyed by
the NE then:
if the duplicate wavekey alarms are raised on disjoint networks (rings) then ignore
them unless unexpected channel alarms are present on either of the rings.
if any of the duplicate key services services are keyed by the 1354 RM-PhM, rekey
that service first. To determine if a service is keyed by the 1354 RM-PhM, perform
the following steps.
...................................................................................................................................................................................................
In the alarm window, select the alarm, right click on the alarm and choose Service View
(key).
The Wavelength Services window is displayed, with the associated services listed.
...................................................................................................................................................................................................
Select one of the displayed services, and click Details.

The Wavelength Service Properties window is displayed.
...................................................................................................................................................................................................
Click the Working Equipment tab.

The cross-connects that define the service are displayed.
....................................................................................................................................................................................................................................
5-11
February 2011

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select one of the cross-connects and click Edit.

The Edit Cross Connect window is displayed.
...................................................................................................................................................................................................
Note the value of the field Wavekeys Auto Selected. If the field is True, then the
wavekeys have been selected by the NE. If the field is False, then the wavekeys have
been selected by the 1354 RM-PhM, and you can clear the alarm by rekeying the service.
...................................................................................................................................................................................................
In the Wavelength services window, select the service again, right-click and choose Rekey
service.
The selected service is assigned new, unique, wave keys.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-12
February 2011

....................................................................................................................................................................................................................................

The cache of equipment data is invalid.
Severity
Critical
Service affecting?
No
Source
TnDiscoveryService
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
Restart the server.
....................................................................................................................................................................................................................................
5-13
February 2011

Facility Retrieval
....................................................................................................................................................................................................................................
Facility Retrieval
An error occurred attempting to retrieve inventory information from the NE.
Severity
Warning
Service affecting?
No
Source
Facility
Type
PROCESSING_ERROR
Applicability
Facility
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Resynchronize the NE. Select the NE and click the Resynchronize button.
...................................................................................................................................................................................................
If the problem persists, contact your service representative.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-14
February 2011

....................................................................................................................................................................................................................................

This alarm is raised by the AutoDiscovery service in "discover by topology" mode if the
PhM fails to properly create an association to an NE that should be discovered by known
topology.
Severity
Warning
Service affecting?
No
Source
AutoDiscovery:IP Address of failed NE
Type
Communication
Applicability
NE Communication
Corrective action
The alarm automatically clears when a valid association with the same IP address is
created and communications are established.
...................................................................................................................................................................................................
In the Topology view, select the NE, right-click and choose Properties.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select one of the entries in the Associations window (either the loopback IP address or the
DCN port IP address) and click the Reconnect button. If the status of the selected
association changes to Active, continue at the next step. If the 1354 RM-PhM cannot
establish a successful connection, select the other association and click Reconnect.
If the status of the selected association changes to Active, continue at the next step. If the
1354 RM-PhM cannot establish a successful connection, then there is a problem with the
NE which must be fixed before communications can be re-established with the 1354
RM-PhM.
...................................................................................................................................................................................................
Launch a web browser. In the address field type the loopback or DCN port IP address of
the NE and press Enter.
....................................................................................................................................................................................................................................
5-15
February 2011

....................................................................................................................................................................................................................................
If the system prompts you to log in to the NE, then the NE is reachable from the 1354
RM-PhM and is communicating correctly. Cancel out of the login screen, close the
browser, and proceed at the next step.
If the system does not prompt you to log in to the NE, then there is a problem with either
the communication path to the NE, or else the NE is out of service.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-16
February 2011

Failed to archive
....................................................................................................................................................................................................................................
Failed to archive
An attempt to write a log record to the database failed.
Severity
Warning
Service affecting?
No
Source
DAOLoggerImpl
Type
Management
Applicability
All logs
Corrective action
If this happens repeatedly, restart the server.
....................................................................................................................................................................................................................................
5-17
February 2011

....................................................................................................................................................................................................................................

The 1354 RM-PhM was unable to register as a trap destination.
Severity
Major
Service affecting?
No
Source
NE_NAME
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
After each step in this procedure, check to see if the problem has been resolved by trying
to register the 1354 RM-PhM as a trap destination on the affected NE. In the 1354
RM-PhM Topology view, select the NE and choose Admin>Register 1354 RM-PhM as a
trap destination.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Determine the SNMP community string for the NE.

1. Launch a web interface session for the NE.
2. In the navigation pane, select NE Administration>SNMP>Community Strings.
The SNMP Community Strings window is displayed. Take note of the value for the "nms"
field. The default value of this field is "nms_snmp".
...................................................................................................................................................................................................
Verify that the SNMP community string is set correctly in the 1354 RM-PhM. In the 1354
RM-PhM Topology view, select the NE, right-click and choose Properties.
1. Click the Associations tab.
...................................................................................................................................................................................................
Repeat the following steps for each entry in the Associations list.
1. Select one of the entries, and click Properties.
....................................................................................................................................................................................................................................
5-18
February 2011

....................................................................................................................................................................................................................................
The Association Properties window is displayed.

2. Check the values in the fields "SetCommunity" and "GetCommunity" and compare
them against the 1354 RM-PhM SNMP community value as seen in the web interface.
3. If the values match, click OK. If the values do not match you must delete the
association and re-create it using the correct values for "SetCommunity" and
"GetCommunity".
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-19
February 2011

....................................................................................................................................................................................................................................

An error occurred writing a Fault Log record to the database.
Severity
Warning
Service affecting?
No
Source
JDBCFaultLogMySQL
Type
Management
Applicability
Fault Log
Corrective action
Restart the server.
....................................................................................................................................................................................................................................
5-20
February 2011

....................................................................................................................................................................................................................................
Severity
Major
Service affecting?
No
Source
NE_NAME
Type
PROCESSING_ERROR
Applicability
Fault
Corrective action
...................................................................................................................................................................................................
In the 1354 RM-PhM Topology view, selects the NE(s) for which you want to
resynchronize the faults, and choose Maintenance>Resync Faults.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-21
February 2011

install error
....................................................................................................................................................................................................................................
install error
An error occurred when initializing a management service.
Severity
Major
Service affecting?
No
Source
Any service
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Startup
Corrective action
Contact your service representative.
....................................................................................................................................................................................................................................
5-22
February 2011

....................................................................................................................................................................................................................................

An error occurred when initializing a PM service.
Severity
Major
Service affecting?
No
Source
PM
Type
PROCESSING_ERROR
Applicability
PM
Corrective action
....................................................................................................................................................................................................................................
5-23
February 2011

Invalid Annotation
....................................................................................................................................................................................................................................
Invalid Annotation
The NE type description files are invalid.
Severity
Major
Service affecting?
No
Source
NEType
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-24
February 2011

Invalid Parameter
....................................................................................................................................................................................................................................
Invalid Parameter
An invalid parameter in was encountered in a message from the NE. Its ID is
"InvalidParameter", and its category is "Adaption".
Severity
Major
Service affecting?
No
Source
Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-25
February 2011

Invalid Supervisor
....................................................................................................................................................................................................................................
Invalid Supervisor
A service adapter attempted to lookup an invalid supervisor. This condition is specific to
SNMP NETypes which are managed by the default SNMP service adapters. The condition
occurs if a trap is received by an NE and the supervisor cannot be determined for the trap.
Severity
Minor
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-26
February 2011

Invalid Table
....................................................................................................................................................................................................................................
Invalid Table
A service adapter attempted to lookup an invalid SNMP table. This condition is specific
to SNMP NETypes which are managed by the default SNMP service adapters. The
condition occurs if a trap is received by an NE and the supervisor cannot be determined
for the trap
Severity
Minor
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-27
February 2011

Invalid Variable
....................................................................................................................................................................................................................................
Invalid Variable
A service adapter attempted to lookup an invalid property. This condition is specific to
occurs if a trap is received by an NE and the supervisor cannot be determined for the trap
Severity
Minor
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-28
February 2011

....................................................................................................................................................................................................................................

An invalid XML reference was detected during an XML file loading. Its ID is
"XMLReference", and its category is "File".
If the file being loaded is one of the files defining an NEType, a processing error alarm is
generated with a source set to "File". The source also contains the name of the "invalid"
NEType and the name of the file that failed to be loaded.
Severity
Major
Service affecting?
No
Source
File
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-29
February 2011

Invalid XML value
....................................................................................................................................................................................................................................
Invalid XML value

An invalid XML value was detected during an XML file loading. Its ID is "XMLValue",
and its category is "File".
Severity
Major
Service affecting?
No
Source
File
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-30
February 2011

Inventory Retrieval
....................................................................................................................................................................................................................................
Inventory Retrieval
An error occurred attempting to retrieve inventory information from the NE.
Severity
Warning
Service affecting?
No
Source
INVENTORY
Type
PROCESSING_ERROR
Applicability
Inventory
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Resynchronize the NE. Select the NE and click the Resynchronize button.
...................................................................................................................................................................................................
If the problem persists, contact your service representative.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-31
February 2011

....................................................................................................................................................................................................................................

An database error occurred
Severity
Critical
Service affecting?
No
Source
Log JDBC Storage
Type
Management
Applicability
All Logs
Corrective action
If this happens repeatedly, restart the server.
....................................................................................................................................................................................................................................
5-32
February 2011

Log Initialization
....................................................................................................................................................................................................................................
Log Initialization
An error occurred initializing a log.
Severity
Warning
Service affecting?
No
Source
Any Log
Type
Management
Applicability
All Logs
Corrective action
Restart the server.
....................................................................................................................................................................................................................................
5-33
February 2011

LOGGER HALT
....................................................................................................................................................................................................................................
LOGGER HALT
The logger is not operating, therefore log records are not being saved.
Severity
Major
Service affecting?
No
Source
Any Log
Type
Management
Applicability
All Logs
Corrective action
Restart the server.
....................................................................................................................................................................................................................................
5-34
February 2011

LOGGER PURGELC
....................................................................................................................................................................................................................................
LOGGER PURGELC
Due to database contention, an error occurred while removing old log records (which are
stored in "Log Components").
Severity
Major
Service affecting?
No
Source
Any Log
Type
Management
Applicability
All Logs
Corrective action
Monitor this alarm. If it does not clear automatically after 12 hours, restart the server.
....................................................................................................................................................................................................................................
5-35
February 2011

Lookup Error
....................................................................................................................................................................................................................................
Lookup Error
An error occurred attempting to a look up a NE, or an error occurred attempting to a look
up a connection.
Severity
Critical
Service affecting?
No
Source
SimpleConfigPolicy
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-36
February 2011

....................................................................................................................................................................................................................................

A parsing error happened at the protocol level. Its ID is "LowLevelError", and its
category is "Protocol".
Severity
Minor
Service affecting?
No
Source
Protocol
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-37
February 2011

Meta Change
....................................................................................................................................................................................................................................
Meta Change
New meta data was discovered in a message. Its ID is "MetaChange", and its category is
"Meta".
Severity
Minor
Service affecting?
No
Source
Meta
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-38
February 2011

Meta Mismatch
....................................................................................................................................................................................................................................
Meta Mismatch
A meta mismatch occurred. This is specific to SNMP NETypes which are managed by the
default SNMP service adapters. This condition occurs if a Details object is passed to a
provision method, and the type of the Details object does not correspond to a valid entity
in the NEType. Its ID is "MetaMismatch", and its category is "NEType".
Severity
Minor
Service affecting?
No
Source
NEType
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-39
February 2011

....................................................................................................................................................................................................................................

A missing mandatory XML attribute was detected during an XML file loading. Its ID is
"XMLAttribute", and its category is "File".
Severity
Major
Service affecting?
No
Source
File
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-40
February 2011

....................................................................................................................................................................................................................................

A missing mandatory XML element was detected during an XML file loading. Its ID is
"XMLElement", and its category is "File".
Severity
Major
Service affecting?
No
Source
File
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-41
February 2011

....................................................................................................................................................................................................................................

The 1354 RM-PhM was not able to retrieve the PM data.
Severity
Minor
Service affecting?
No
Source
PM:NE_NAME
Type
PROCESSING_ERROR
Applicability
PM
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
server. Use the CLI command of the CLI Reference Guide.)
...................................................................................................................................................................................................
Ping the 1354 RM-PhM server from the NE (use the CLI command of the CLI Reference
Guide.)
tools ping nms_ip_addess
If the NE cannot reach the 1354 RM-PhM server, a static route to the 1354 RM-PhM
server must be added to the NE.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
5-42
February 2011

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Verify that the TFTP server is running on the software server. Consult your system
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-43
February 2011

NE + neName + "system time out of sync with 1354 RM-PhM"
....................................................................................................................................................................................................................................
NE + neName + "system time out of sync with 1354

RM-PhM"
The time clock on the server and NE differ by more than 300 seconds (5 minutes). This
can occur if the 1354 RM-PhM and the NE derive their timing from different sources, or
if one or both of them are in free-run mode.
Severity
Minor
Service affecting?
No
Source
PM:NE_NAME
Type
PROCESSING_ERROR
Applicability
PM
Corrective action
...................................................................................................................................................................................................
Determine what the correct time is, and set both the 1354 RM-PhM and the NE to the
correct value.
To configure the NE NTP server refer to of the CLI Reference Guide.

To configure the NE time refer to of the CLI Reference Guide.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-44
February 2011

NE Backup failed
....................................................................................................................................................................................................................................
NE Backup failed
A failure occurred attempting to back up the database of an NE.
Severity
Major
Service affecting?
No
Source
Backup:NE_NAME
Type
PROCESSING_ERROR
Applicability
NE Backup
Corrective action
...................................................................................................................................................................................................
Verify that the configured backup destination is correct.

...................................................................................................................................................................................................
Verify that the communication path from the NE to the backup destination is correct.
...................................................................................................................................................................................................
Verify that the NE can ping the backup server (use the CLI command "tools ping backup
ip address").
...................................................................................................................................................................................................
Verify that the TFTP server on the backup destination is working.

...................................................................................................................................................................................................
Verify that the TFTP server on the backup destination is configured properly.
If the TFTP server is running on the local 1354 RM-PhM server, verify that the TFTP
root directory is configured properly.
If this is a Windows 1354 RM-PhM server and the 1354 RM-PhM server is being
used as the backup server, then restart the server.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-45
February 2011

....................................................................................................................................................................................................................................
An error occurred writing a NE Event Log record to the database.
Severity
Warning
Service affecting?
No
Source
JDBCNEEventLogMySQL
Type
Management
Applicability
NE Event Log
Corrective action
Restart the server.
....................................................................................................................................................................................................................................
5-46
February 2011

....................................................................................................................................................................................................................................
An error occurred writing a NE Request Log record to the database.
Severity
Warning
Service affecting?
No
Source
JDBCNERequestLogMySQL
Type
Management
Applicability
NE Request Log
Corrective action
Restart the server.
....................................................................................................................................................................................................................................
5-47
February 2011

....................................................................................................................................................................................................................................

An error occurred when communicating with a NE.
Severity
Warning
Service affecting?
No
Source
Connection
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
In the alarm window, select the alarm, right-click on it and choose Details (alternatively,
double-click the alarm). The Alarm Details window for that alarm is displayed.
Examine the Description field in the Alarm Details window. If the description refers
to an "invalid PK" then restart the server.
If the description refers to any other problem, continue at the next step.
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-48
February 2011

New Entity
....................................................................................................................................................................................................................................
New Entity
A new meta entity was discovered in a message. Its ID is "NewEntity", and its category is
"Meta".
Severity
Minor
Service affecting?
No
Source
Meta
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-49
February 2011

....................................................................................................................................................................................................................................

A PM collection request was rejected for a NE because another unfinished request is
outstanding. This can occur if the 1354 RM-PhM is heavily loaded.
Severity
Minor
Service affecting?
No
Source
PM
Type
PROCESSING_ERROR
Applicability
PM
Corrective action
None. The condition should clear automatically when load levels return to normal.
....................................................................................................................................................................................................................................
5-50
February 2011

....................................................................................................................................................................................................................................

The SNMP mapping configuration is invalid
Severity
Critical
Service affecting?
No
Source
SNMPMapping:1696 ROADM
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-51
February 2011

....................................................................................................................................................................................................................................

Power commissioning is in progress
Severity
Warning
Service affecting?
No
Source
NE_NAME
Type
PROCESSING_ERROR
Applicability
Power Commissioning
Corrective action
Redo power commissioning from the same node until the network problem is fixed and
power commissioning succeeds. This alarm will not clear if power commisioning is
launched from another node.
....................................................................................................................................................................................................................................
5-52
February 2011

....................................................................................................................................................................................................................................
An error occurred attempting to set the NTP server of the NE to be the 1354 RM-PhM
server.
Severity
Warning
Service affecting?
No
Source
NE_NAME
Type
PROCESSING_ERROR
Applicability
NTP
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Verify that the NTP server is up and operational. Contact your system administrator for
this.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-53
February 2011

Object Lookup
....................................................................................................................................................................................................................................
Object Lookup
An error occurred attempting to look the primary key of a connection or attempting to
look up a NE.
Severity
Critical
Service affecting?
No
Source
SimpleConfigPolicy
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-54
February 2011

Object Prop Change
....................................................................................................................................................................................................................................
Object Prop Change

An error occurred attempting to make a change to:
a NE association
a NE connection
a NE
Severity
Critical
Service affecting?
No
Source
SimpleConfigPolicy
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-55
February 2011

Object removal
....................................................................................................................................................................................................................................
Object removal
An error occurred attempting to:
remove a NE association
delete a NE connection
delete a NE
Severity
Critical
Service affecting?
No
Source
SimpleConfigPolicy
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-56
February 2011

Object Storage
....................................................................................................................................................................................................................................
Object Storage
An error occurred attempting to:
store a NE association
store a NE connection
create a NE
Severity
Critical
Service affecting?
No
Source
SimpleConfigPolicy
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-57
February 2011

Parsing Exception
....................................................................................................................................................................................................................................
Parsing Exception
An exception occurred while parsing a message. Its ID is "ParseException", and its
category is "Adaption". An incoming message is received by the TMS, however, the
adaption layer is not able to parse the message using the meta information.
Severity
Major
Service affecting?
No
Source
Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-58
February 2011

PK Lookup
....................................................................................................................................................................................................................................
PK Lookup
An error occurred attempting to look up the primary keys of all connections.
Severity
Critical
Service affecting?
No
Source
SimpleConfigPolicy
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-59
February 2011

REDUNDANCY
....................................................................................................................................................................................................................................
REDUNDANCY
Standby PhM server unavailable. The active PhM server cannot communicate with the
standby PhM server. This can be caused by a network connection problem, the standby
server not running, a configuration error, or a software error.
Network connection problem or server not running on host nmsx8.ca.alcatel.com.
Severity
Minor
Service affecting?
No
Source
1354 RM-PhM
Type
Management
Applicability
NE Management
Corrective action
Ensure the standby server is up and communications are operational between the active
and standby servers. Restart the standby server if necessary. Otherwise, contact your
service representative.
....................................................................................................................................................................................................................................
5-60
February 2011

Scalability Problem
....................................................................................................................................................................................................................................
Scalability Problem
An error was encountered in the configuration of the event channel. This can occur only if
the client version does not match the server version.
Severity
Minor
Service affecting?
No
Source
FaultManager
Type
PROCESSING_ERROR
Applicability
Fault
Corrective action
Upgrade the 1354 RM-PhM client software to match the 1354 RM-PhM server software.
....................................................................................................................................................................................................................................
5-61
February 2011

....................................................................................................................................................................................................................................
An error occurred writing a Server Log record to the database.
Severity
Warning
Service affecting?
No
Source
JDBCServerLogMySQL
Type
Management
Applicability
Server Log
Corrective action
Restart the server.
....................................................................................................................................................................................................................................
5-62
February 2011

....................................................................................................................................................................................................................................

This alarm is generated when a portion of the service is removed from the network,
rendering the service incomplete. The 1354 RM-PhM then deletes the incomplete service
from its database.
Example: Service '{NE_20_8/1:1:2B:1:21 (8/4)}<->{NE_20_1/1:1:13A:4:21 (8/4)}'
downloaded because required port NE_20_2/1:1:2B:1 was deleted.
Severity
Warning
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
The alarm description indicates the network resource (port, card, etc.) that is missing.
Determine why the resource is missing, and if possible restore it.
...................................................................................................................................................................................................
Once the resource has been restored, rediscover the services in the group. In the 1354
RM-PhM Topology view, select the group that the service was in (as seen in the alarm
description) right-click and choose Discover Services in Group.
...................................................................................................................................................................................................
This alarm does not clear automatically. It must be manually cleared. In the Alarm panel
of the 1354 RM-PhM Topology View window, right-click on the alarm and choose Clear.
The selected alarm is removed from the alarm window.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-63
February 2011

SNMP Bulk Get Error
....................................................................................................................................................................................................................................
SNMP Bulk Get Error

An error occurred sending an SNMP Bulk Get request. This condition is specific to
arises during data collection, if the NE returns an error to an SNMP Bulk Get request.
Severity
Minor
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-64
February 2011

SNMP Error received
....................................................................................................................................................................................................................................
SNMP Error received

One or more SNMP errors were received by a service adapter. Its ID is "SNMPError",
and its category is "ServiceAdaption".
Severity
Minor
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-65
February 2011

SNMP Get Error
....................................................................................................................................................................................................................................
SNMP Get Error

An error occurred sending an SNMP Get request. This condition is specific to SNMP
NETypes which are managed by the default SNMP service adapters. The condition arises
during data collection, if the NE returns an error to an SNMP Get request.
Severity
Minor
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-66
February 2011

SNMP GetNext Error
....................................................................................................................................................................................................................................
SNMP GetNext Error

An error occurred sending an SNMP Get Next request. This condition is specific to
arises during data collection, if the NE returns an error to an SNMP Get-Next request.
Severity
Minor
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-67
February 2011

SNMP Set Error
....................................................................................................................................................................................................................................
SNMP Set Error

An error occurred sending an SNMP Set request. This condition is specific to SNMP
NETypes which are managed by the default SNMP service adapters. The condition arises
during a set-provision, if the NE returns an error in response to an SNMP Set request.
Severity
Minor
Service affecting?
No
Source
Service Adaption
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-68
February 2011

The scheduled time for Software Load task for neName is
scheduled
to begin at startTime which is in the past. It
....................................................................................................................................................................................................................................
will be run immediately.
The scheduled time for Software Load task for

neName is scheduled to begin at startTime which
is in the past. It will be run immediately.
The scheduled time for a software load task has passed. This is likely because the 1354
RM-PhM server was not operational at the scheduled load time.
Severity
Minor
Service affecting?
No
Source
TNSWDLSERVICE
Type
PROCESSING_ERROR
Applicability
NE SW Upgrade
Corrective action
Reschedule the software load task or start the perform the load manually.
...................................................................................................................................................................................................
In the 1354 RM-PhM topology view, select the NE, and choose Admin>NE Software
Upgrade.
The NE Software Upgrade window is displayed.
...................................................................................................................................................................................................
Examine the software upgrade settings to ensure that they are valid. Change settings as
required.
...................................................................................................................................................................................................
To reschedule the software upgrade, click the Schedule the Phase 2 (Load) button and
specify a new load time.
...................................................................................................................................................................................................
To load the software immediately, click the Phase 2 - Load the Target Software button.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-69
February 2011

The Software Activation task for getneName is scheduled to
begin
at getStartTime which is in the past. Please
....................................................................................................................................................................................................................................
re-schedule.
The Software Activation task for getneName is

scheduled to begin at getStartTime which is in
the past. Please re-schedule.
The scheduled time for a software activation has passed. This is likely because the 1354
RM-PhM server was not operational at the scheduled activation time.
Severity
Minor
Service affecting?
No
Source
TNSWDLSERVICE
Type
PROCESSING_ERROR
Applicability
NE SW Upgrade
Corrective action
Reschedule the software load task or start the perform the load manually.
...................................................................................................................................................................................................
In the 1354 RM-PhM topology view, select the NE, and choose Admin>NE Software
Upgrade.
The NE Software Upgrade window is displayed.
...................................................................................................................................................................................................
Examine the software upgrade settings to ensure that they are valid. Change settings as
required.
...................................................................................................................................................................................................
To reschedule the software activation, click the Schedule the Phase 3(Activate) button and
specify a new activation time.
...................................................................................................................................................................................................
To activate the software immediately, click the Phase 2 - Activate the Target Software
button.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-70
February 2011

The Software Activation task for " + _neName + " has been
aborted
due to the presence of unacknowledged alarms."
....................................................................................................................................................................................................................................
The Software Activation task for " + _neName + "

has been aborted due to the presence of
unacknowledged alarms."
The pre-activation check failed when performing an auto-upgrade. This check is run
before a software load is activated on the NE. The checks fail if there are
unacknowledged alarms or if the NE is currently being re-discovered.
Severity
Minor
Service affecting?
No
Source
TNSWDLSERVICE
Type
PROCESSING_ERROR
Applicability
NE SW Upgrade
Corrective action
...................................................................................................................................................................................................
Wait for the NE discovery to complete (discovery in progress is indicated by an

hour-glass icon within the NE icon in the tree-view).
...................................................................................................................................................................................................
Solve/acknowledge the alarms on the NE.

...................................................................................................................................................................................................
Try to activate the software load again.

1. In the 1354 RM-PhM topology view, select the NE, and choose Admin>NE Software
Upgrade.
2. The NE Software Upgrade window is displayed.
3. Examine the software upgrade settings to ensure that they are valid. Change settings
as required.
4. Click the Phase 2 - Activate the Target Software button.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-71
February 2011

The Software Load task for neName that was scheduled to
begin
at getStartTime failed to initiate.
....................................................................................................................................................................................................................................
The Software Load task for neName that was

scheduled to begin at getStartTime failed to
initiate.
The load step of a software upgrade failed.
Severity
Minor
Service affecting?
No
Source
TNSWDLSERVICE
Type
PROCESSING_ERROR
Applicability
NE SW Upgrade
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Ping the software server from the NE (use the CLI command "tools ping backup ip
address"). It may be necessary to add a static route to the NE's CN configuration.
...................................................................................................................................................................................................
server.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
5-72
February 2011

The Software Load task for neName that was scheduled to
begin
at getStartTime failed to initiate.
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Verify that the TFTP server is running on the software server. Consult your system
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-73
February 2011

....................................................................................................................................................................................................................................
File replication failed.
Could not contact standby server to replicate PM files.
Could not contact file replication subsystem on the standby.
Corrective action
Severity
Minor
Service affecting?
No
Source
NEType
Type
PROCESSING_ERROR
Applicability
NE Management
Ensure the standby server is up and communications are operational between the active
and standby servers. Restart the standby server if necessary. Otherwise, contact your
service representative.
....................................................................................................................................................................................................................................
5-74
February 2011

....................................................................................................................................................................................................................................
An unavailable annotation occurred. This is specific to the default SNMP service
adapters. This condition occurs if a trap is received by an NE which does not have
annotation meta defined. The condition may also arise during a service poll or provision if
an NEType which previously supported annotation meta is reloaded without annotation
meta. Its ID is "MissingAnnotation", and its category is "Annotation".
Severity
Major
Service affecting?
No
Source
NEType
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-75
February 2011

Unavailable NEType
....................................................................................................................................................................................................................................
Unavailable NEType
An unavailable NEType occurred when the user tried to load an NEType that does not
exist. Its ID is "MissingNEType", and its category is "NEType".
A processing error alarm is generated with a source of "NEType". The source also
contains the name of the "unavailable" NEType.
Severity
Major
Service affecting?
No
Source
NEType
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-76
February 2011

UnknownNEType
....................................................................................................................................................................................................................................
UnknownNEType
The type of the NE is unknown.
Severity
Major
Service affecting?
No
Source
NE_NAME
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-77
February 2011

UnknownSource
....................................................................................................................................................................................................................................
UnknownSource
The 1354 RM-PhM received a SNMP trap from a NE that it is not managing.
Normally this is caused by a NE having a trap destination set to the 1354 RM-PhM server
IP address but the 1354 RM-PhM does not yet have this NE in its database. If
auto-discovery is enabled then the 1354 RM-PhM discovers the NE and clears this alarm.
However, if the source address in the trap is not reachable by the 1354 RM-PhM then the
auto-discovery fails and the alarm is not cleared.
This condition can also be caused by any other device sending a trap to the 1354
RM-PhM server.
Severity
Major
Service affecting?
No
Source
CONNECTOR:SNMP:IP address
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
...................................................................................................................................................................................................
Determine the IP address of the source with the "Remote Address" field on the alarm
details. If you wish to manage this device then ensure it is running a software version that
is supported by the version of the 1354 RM-PhM server.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Discover the NE.

...................................................................................................................................................................................................
If you wish to have supported network element types automatically discovered, then
enable auto-discovery. The next time the NE sends a trap, the 1354 RM-PhM discovers it
and the alarm is cleared.
....................................................................................................................................................................................................................................
5-78
February 2011

UnknownSource
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
If you do not wish to manage the device, then configure it so that it no longer sends traps
to the 1354 RM-PhM.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-79
February 2011

....................................................................................................................................................................................................................................
An unrecognized autonomous message was received. An autonomous message is received
by the 1354 RM-PhM from a known NE but no meta information is found for it, which
prevents it being parsed. Its ID is "UnknownAuto", and its category is "Protocol".
A processing error alarm is generated with a source set to "Protocol". The additional data
of the alarm contains the NE name and possibly the original received message.
Severity
Major
Service affecting?
No
Source
Protocol
Type
PROCESSING_ERROR
Applicability
NE Management
Corrective action
....................................................................................................................................................................................................................................
5-80
February 2011

....................................................................................................................................................................................................................................

An unrecognized XML attribute was detected during an XML file loading. Its ID is
"UnknownXMLAttribute", and its category is "File".
Severity
Major
Service affecting?
No
Source
File
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-81
February 2011

....................................................................................................................................................................................................................................

An unrecognized XML element was detected during an XML file loading. Its ID is
"UnknownXMLElement", and its category is "File".
Severity
Major
Service affecting?
No
Source
File
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-82
February 2011

XML validation
Overview
....................................................................................................................................................................................................................................
XML validation
An XML file failed to be validated during an XML file loading. Its ID is
"XMLValidation", and its category is "File".
e generated with a source set to "File". The source also contains the name of the "invalid"
Severity
Major
Service affecting?
No
Source
File
Type
PROCESSING_ERROR
Applicability
1354 RM-PhM Config
Corrective action
....................................................................................................................................................................................................................................
5-83
February 2011

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
5-84
February 2011
Managing services
6
Overview
Purpose
This chapter explains how to manage services.

Contents
6-2
6-2
6-3
6-3
6-5
6-5
6-14
6-14
6-16
6-16
6-17
6-17
Partial services
6-18
6-18
Sub-rate service
6-19
6-19
6-22
6-25
6-25
...................................................................................................................................................................................................................................
6-1
February 2011
Managing services
....................................................................................................................................................................................................................................

Use this procedure to specify the preferences you wish to use when creating or deleting
services.
To set service preferences
...................................................................................................................................................................................................
In the 1354 RM-PhM Topology View, choose Admin>Settings.

...................................................................................................................................................................................................
Select User Settings. Click the Service Attribute Provisioning tab.

...................................................................................................................................................................................................
Set the Provisioning Options:
Set service admin up- automatically sets the state of the service to admin up when
the service is created.
Set service AINS - automatically sets the state of the service to in-service when the
service is created.
Auto Keying (NE) - if selected, the Wave keys are set automatically by the NE.
Auto Keying (NMS) - if selected, the Wave keys are set automatically by the 1354
RM-PhM.
Do not show on create - To prevent the service provisioning options from being
displayed when a service is created, click this option. In this case, the service
provisioning options specified here are used.
...................................................................................................................................................................................................
Click OK.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-2
February 2011
Managing services
....................................................................................................................................................................................................................................

Services that have already been configured can be viewed or edited.
Note: 1354 RM-PhM may not route PSS-1 services using the shortest route. The
reason has to do with the fact that there are 2 line ports. If both are assigned, then
1354 RM-PhM always starts with L1 and will use a route if one is found that way. It
will only use L2 if a route with proper resources was not found on L1 (or user
responded to stop searching when prompted), or L1 is explicitly excluded or
unassigned.
To list and edit services from the 1354 RM-PhM
...................................................................................................................................................................................................
You can view all of the services within the network, or you can view the services which
traverse a particular network element.
1. To view all services in the network, ensure that no network elements are selected in
the 1354 RM-PhM Topology View, and click the Wavelength Services icon.
The Wavelength Services window is displayed, listing all services in the network.
2. To view all services that traverse a particular network element or set of network
elements, select the network element(s) in the 1354 RM-PhM Topology View, and
click the Wavelength Services icon.
The Wavelength Services window is displayed, listing all services on the selected
network elements.
...................................................................................................................................................................................................
Select the service you wish to edit.

...................................................................................................................................................................................................
Click Details.
The editing window is displayed.
...................................................................................................................................................................................................
View or edit the attributes of the service.

...................................................................................................................................................................................................
To save changes, click Save. To exit without saving changes, click Cancel.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-3
February 2011
Managing services
....................................................................................................................................................................................................................................
To view wavelength usage in the network

...................................................................................................................................................................................................
In the 1354 RM-PhM Topology View, choose Provision>Wavelength Usage Matrix.

The Wavelength Usage Matrix window is displayed, displaying the wavelengths used in
the network, and the network elements that they traverse.
The Wavelength Usage Matrix window provides the following actions:
refresh the wavelength usage data - Click the Refresh button.

change the row order so that the ring is displayed in the reverse direction. The first
row remains the same. Click the Ring button.
list wavelength services for the selected network elements. Select one or more NEs,
and click the List Wavelength Services button. The Wavelength Services window is
displayed.
save wavelength usage matrix data as a HTML web page. Click the Save Wavelength
Usage Data button. You are prompted to specify a filename and location to save the
file.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-4
February 2011
Managing services
....................................................................................................................................................................................................................................

Wavelength services are implemented in two basic scenarios:
pre-wired - all of the cards are installed, the cables connected, and
transponders/transmitters are operating, and then the service is configured.
pre-provisioned - the network element is pre-provisioned using the CLI or web
interface, the service is configured, and then the cards are inserted, the cables
connected, and the transponders/transmitters are turned on
Service protection options
Wavelength services can be transported across the network unprotected, or protected by

one of several methods. For protection options, see the 1830 PSS-32/PSS-16 User
Provisioning Guide.
Wavelength services can also have protected segments in them. The number of segments
within each service and the equipment across which each segment runs varies with each
particular service.
The 1354 RM-PhM uses the following protection definitions:
Unprotected
The service will fail if any resource in its route fails.

Partially protected
Service protection exists but has at least one shared NE or shared topological connection.
Fully protected
The service will not fail if any single managed resource along its route fails (excluding
the originating and terminating network elements for the service).
Tip: The following describes how to convert between protected and unprotected
services for PSS-1 MD4H.
To convert an unprotected service to a protected service:
...................................................................................................................................................................................................
Create an unprotected service from A to Z.

...................................................................................................................................................................................................
Unmanage the service.

...................................................................................................................................................................................................
Configure to admin maintenance state the A and Z ports.
....................................................................................................................................................................................................................................
6-5
February 2011
Managing services
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Create a protected service from A to Z.

E...................................................................................................................................................................................................
N D O F S T E P S
To convert a protected service to an unprotected service

...................................................................................................................................................................................................
Create a protected service from A to Z.

...................................................................................................................................................................................................
Unmanage the service.

...................................................................................................................................................................................................
Configure to admin maintenance state the A and Z ports.

...................................................................................................................................................................................................
Use provision APS group to delete the protection group associated to the A and the Z
ends.
...................................................................................................................................................................................................
Create an unprotected service from A to Z.

E...................................................................................................................................................................................................
N D O F S T E P S
To create a wavelength service

...................................................................................................................................................................................................
Note: The recommended method for creating a wavelength service for a pre-wired
scenario is as follows:
1. Determine your network and link requirements.
2. Install the hardware and fibers and turn on and adjust the
transponders/transmitters.
3. Using the 1354 RM-PhM provision the wavelength service according to the
network plan.
4. Verify that the hardware and transponders are operating according to the network
plan.
Perform the physical setup according to your company field installation safety
procedures. Following the shelf and fiber layout, insert the cards, connect the cables and
turn on the transponders.
....................................................................................................................................................................................................................................
6-6
February 2011
Managing services
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the 1354 RM-PhM Topology View, select the network elements on which the service
endpoints reside.
...................................................................................................................................................................................................
Click the Provision a Wavelength Service icon.

The Provision New Wavelength Service window is displayed.
...................................................................................................................................................................................................
In the Service Name field, type a name for the service.

...................................................................................................................................................................................................
In the Customer ID field, type a customer name for the service.

...................................................................................................................................................................................................
In the Layer Rate field, use the drop-down menu to choose a layer rate.
...................................................................................................................................................................................................
In the Protection field, use the drop-down menu to choose a protection type, Unprotected,
ESNCP Protected, or Fully Protected.
...................................................................................................................................................................................................
If the service is fully protected, in the Client Protection Options field, specify one of the
protection options, Unprotected, Unprotected (Splitter), or Dual Client.
...................................................................................................................................................................................................
Specify the directionality of the service:
If this is a bidirectional service, check the Bidirectional check box.

Note: When provisioning a bidirectional service, you must ensure that all ports
through which the service passes are configured as bidirectional ports. The 1354
RM-PhM does not allow you to create two unidirectional services on the same client
ports.
Note: The only exception to this rule is the case of SFC single fiber mode services
where the PhM does actually allow two unidirectional services on the same client
port.
If this is a unidirectional service, you must set the directionality of the client ports at
the ends of the service to unidirectional in order to suppress alarms on the unused
Rx/Tx ports.
....................................................................................................................................................................................................................................
6-7
February 2011
Managing services
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
10
Specify the keying mode:
Auto Keying (NE) - causes both NEs to allocate the Wavelength Tracker keys
(wavekeys) for the service. This option should be used on networks where NE-to-NE
links use Optical Supervisory Channel (OSCT) cards. This option must be used to
prevent wavekey duplication if a third-party management system is also used to
provision services and assign wavekeys.
Auto Keying (PhM) - causes the 1354 RM-PhM to allocate the Wavelength Tracker
keys for the service. This should be used on networks with no OSCT cards deployed.
1354 RM-PhM auto-keying should be avoided on networks where a third-party
management system is provisioning services and assigning wavekeys.
No Keying - Provisions cross-connects without provisioning WaveKeys on those
cross-connects.
Force XC Creation - bypassing check to ensure that lines are commissioning before
creating a service on them (only used during commissioning of the network).
Enable Full Network Search - when enabled, forces the service routing to consider all
NEs in all topology groups under Main View, and not just the groups containing the
endpoint NEs.
...................................................................................................................................................................................................
11
Click Next.
The system searches the selected network elements for valid connection termination
points for the service, and then the Select Termination Points window is displayed.
...................................................................................................................................................................................................
12
For each of the A and Z End CTPs, use the drop-down menu to select the desired end
point. The A1 and Z1 end points specify the working path endpoints. The A2 and Z2
endpoints specify the protection path end points.
To refine the list of endpoints, click the Filter check box. A list of filter criteria is
displayed. Specify the criteria on which to search and click the Search button. The list of
endpoints is refined to reflect only those which match the search criteria.
Alternatively, click the Auto-Pick Endpoints button, which automatically determines
eligible endpoint pairs.
...................................................................................................................................................................................................
13
Once the endpoints have been specified, click Next.

The system checks for an available route (or in the case of a protected service, multiple
routes), and then displays it as a series of fiber endpoints as shown in the following
figure.
....................................................................................................................................................................................................................................
6-8
February 2011
Managing services
....................................................................................................................................................................................................................................
Figure 6-1 Wavelength service fiber endpoints
...................................................................................................................................................................................................
14
Click Finish and one of two Power Management windows is displayed.

If the service require manual power management, then the following window is
displayed:
....................................................................................................................................................................................................................................
6-9
February 2011
Managing services
....................................................................................................................................................................................................................................
Figure 6-2 Manually power-managed service
If the service does not require manual power management, then the following window is
displayed:
....................................................................................................................................................................................................................................
6-10
February 2011
Managing services
....................................................................................................................................................................................................................................
Figure 6-3 Automatically power-managed service
...................................................................................................................................................................................................
15
If the service requires manual power management, use the Power (A-Z) and Power (Z-A)
buttons to launch the power management windows through which you can adjust the
service's power levels to enable the service.
If the service does not require manual power management, the Power (A-Z) and Power
(Z-A) can be used to view the power levels along the service, but no action is necessary.
Once you are finished adjusting or view the power levels along the service, Click Close.
The Provision Service attributes window is displayed (only if it was specified to be
displayed, in the Service Attribute Provisioning window).
....................................................................................................................................................................................................................................
6-11
February 2011
Managing services
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
16
In the Provision Service attributes window, enable or disable the following attributes as
desired:
Set service admin up

Set service AINS - sets the service to automatic in-service
...................................................................................................................................................................................................
17
Click OK.
The cross-connections are provisioned to the network, and the service information is
committed to the database.
E...................................................................................................................................................................................................
N D O F S T E P S
To delete a wavelength service

...................................................................................................................................................................................................
Locate the service(s) that you want to delete:
use the Wavelength Services view

click the Wavelength Services button in the 1354 RM-PhM Topology view. To list
services for a particular network element or set of network elements, select the
network element(s) and then click the Wavelength Services button. To list all services
known to the 1354 RM-PhM, select Topology View in the navigation tree, then
click the Wavelength Services button.
...................................................................................................................................................................................................
Select the service(s) to delete, and click the Delete button.

The Deprovision Service attributes window is displayed (only if it was specified to be
displayed, in the Service WaveKey Provisioning window).
...................................................................................................................................................................................................
Configure the deprovision service attributes as desired.
Disable Client Port - sets the state of the client port to down
...................................................................................................................................................................................................
Click OK.
The service(s) deletion begins.
....................................................................................................................................................................................................................................
6-12
February 2011
Managing services
....................................................................................................................................................................................................................................
Note: The service being displayed is the one being deleted, and once deletion
commences for it, it is not possible to stop it. However, pressing the Cancel button
stops deletion of any subsequent services. For example, if you are deleting five
services and click Cancel when the third service is being deleted, then the results are
that the first three services are deleted and the last two services are not deleted.
Note: During service deletion, the 1354 RM-PhM sets the transponder ports to
maintenance state for a period of time. Doing this causes the NEs to raise the
condition Manually caused abnormal condition - port in maintenance for each of the
transponder ports. This condition clears once the service deletion completes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-13
February 2011
Managing services
....................................................................................................................................................................................................................................

The 1354 RM-PhM provides the capability to export and import service definitions. This
is useful during software and database upgrades, as well as network reconfiguration, so
that you do not need to recreate your services. Service definitions are saved as XML files.
To export a service definition
...................................................................................................................................................................................................
From the Wavelength Services window, select a service.

...................................................................................................................................................................................................
Click the Export Service icon.

...................................................................................................................................................................................................
A Windows browser is displayed.

...................................................................................................................................................................................................
Specify a name for the service.

...................................................................................................................................................................................................
Specify a directory in which to save the service.

Note: Specify a directory outside of the 1354 RM-PhM directory so that the service
definitions are not overwritten when the 1354 RM-PhM software is upgraded.
...................................................................................................................................................................................................
Click Accept.
The service definition is saved as an XML file in the directory specified.
E...................................................................................................................................................................................................
N D O F S T E P S
To import a service definition

...................................................................................................................................................................................................
From the Wavelength Services window, click the Import Service icon.
...................................................................................................................................................................................................
A Windows browser is displayed.

...................................................................................................................................................................................................
Navigate to the directory which contains the service definition file that you want to
import.
....................................................................................................................................................................................................................................
6-14
February 2011
Managing services
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the desired service definition file.

...................................................................................................................................................................................................
Click Accept.
The 1354 RM-PhM imports the service definition and creates the service.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-15
February 2011
Managing services
....................................................................................................................................................................................................................................

The 1354 RM-PhM can discover services that have been created using other user
interfaces such as the CLI and the web interface. Once discovered, these services can be
managed by the 1354 RM-PhM.
To discover services in the network
...................................................................................................................................................................................................
In the 1354 RM-PhM topology view, select the group for which you wish to discover
services, right-click and choose Discover Services in Group.
The Service Upload window is displayed, showing the progress and status of service
discovery.
Note: The Service Upload window does not provide feedback on services that were
not successfully discovered.
...................................................................................................................................................................................................
To see more information on service discovery, click the Details button.

The Service upload window is expanded to include a section for service discovery details.
...................................................................................................................................................................................................
When you are finished, click Close.

The discovered services can now be managed using the 1354 RM-PhM Wavelength
Services and Wavelength Tracker capabilities. Only services that were successfully
discovered can be viewed and managed in the 1354 RM-PhM. Services that could not be
successfully discovered are not displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-16
February 2011
Managing services
....................................................................................................................................................................................................................................

The 1354 RM-PhM can stop managing a service, but leave the service active in the
network.
To unmanage a service
...................................................................................................................................................................................................
Locate the service(s) that you want to stop managing:
use the Wavelength Services view

click the Wavelength Services button in the 1354 RM-PhM Topology view. To list
services for a particular network element or set of network elements, select the
network element(s) and then click the Wavelength Services button. To list all services
known to the 1354 RM-PhM, select Topology View in the navigation tree, then
click the Wavelength Services button.
...................................................................................................................................................................................................
Select the service(s) to stop managing, right-click and choose Unmanage Wavelength
Services.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
The service is removed from the 1354 RM-PhM, but the cross-connects remain active and
the port states are left unchanged.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-17
February 2011
Managing services
Partial services
....................................................................................................................................................................................................................................
Partial services
A partial service is created by a topology change in the network that causes one (or more)
of the cross connects associated with a service to be deleted.
To repair a partial service
...................................................................................................................................................................................................
Click on the List Wavelength Services button.

The Wavelength Services window is displayed, listing all services in the network.
...................................................................................................................................................................................................
Locate and select the partial service that you want to repair, and then click the Repair
Partial Service button.
The 1354 RM-PhM attempts to recreate missing cross connects, or to learn them back if
they have been manually added at the NE, and reconstruct the service.
If the recreation attempt is successful, the status of the service is updated to Active.
If the recreation attempt fails, there is nothing more that can be done from the 1354
RM-PhM. The service must be repaired using one of the other interfaces.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-18
February 2011
Managing services
Sub-rate service
....................................................................................................................................................................................................................................
Sub-rate service
Note: Sub-rate service is supported by 1830 PSS-1 GBE beginning in 1354 RM-PhM
Release 7.0,
Configuring the operational mode of 1830 PSS-1 GBE card
The two operational modes supported by the 1830 PSS-1 GBE card are:
Fullrate Mode - Under this mode, each 1830 PSS-1 GBE client port can support only
one service with a total of 10 services (maximum) flowing through each Line port.
This is the default mode.
Subrate Mode - Under this mode, each 1830 PSS-1 GBE client port can support a
maximum of 10 services with a total of 32 services (maximum) flowing through each
Line port.
Configuring the card to subrate mode is a prerequisite for creation of a SubGigE service.
Modifying the card mode results in the following changes:
If the card mode is changed to subrate mode, then the layer rate of the client port in
1354 RM-PhM is changed to SubGigE, though the port type is still GigE.
1354 RM-PhM displays a message when attempting to change the operational mode if
there is already a service running through the card. The user is prevented from
changing the operational mode of the 1830 PSS-1 GBE card if 1354 RM-PhM has
any services using the card. Services using the card must be unmanaged or deleted
before changing the operational mode.
VTS map
The VTS map feature displays VTS map information for 1830 PSS-1 GBE client ports
via table format. The first column displays the Client VTS attribute names. Columns 2 5
display the bandwidth profile attributes associated with each VTS. The last column
displays the CE-VLANID for each client VTS.
Note: Tooltips are available for each field which displays the value for that column.
The bandwidth profile attributes (table columns 2 5) consist of four traffic parameters as
shown below:
CIR (Committed Information Rate) - CIR is the average rate up to which service
frames are delivered per the service performance objectives.
CBS (Committed Burst Size) - CBS is the maximum number of bytes allowed for
incoming service frames to still be CIR-conformant.
....................................................................................................................................................................................................................................
6-19
February 2011
Managing services
Sub-rate service
....................................................................................................................................................................................................................................
EIR (Excess Information Rate) - EIR is the average rate up to which service frames
are delivered without any performance objectives.
EBS (Excess Burst Size) - . EBS is the maximum number of bytes allowed for
incoming service frames to still be EIR-conformant
Note: Bandwidth profile attributes are provisioned on creation of a sub-rate gige
service and they are associated with the cross-connect provisioned on the NE. These
attributes are read only in the VTS Map table and cannot be modified.
The user can configure the CE-VLANID attribute (table column 6). This determines how
the packets are mapped into the client VTS. The valid CE-VLAN ID parameters for each
client VTS are:
Separate numbers in the range of 1-4095, separated by comma.
The contiguous range of VLAN IDs (valid value is 1-4095), separated by comma.
The mixed number and the VLAN ID range, separated by comma.
ALL (case sensitive): all the tagged (CE-VLANID=[1-4095], priority tagged
(CE-VLANID=0) and untagged packets are mapped into the line VTS
blank string: A blank string (i.e. zero-length) string is used to indicate that no traffic
flow is mapped into the client VTS. The default CE-VLAN ID value for each client
VTS is a blank string.
Note: CE-VLANID can be reused on different client ports but must be unique on a
given client port.
To configure/view VTS map details
...................................................................................................................................................................................................
From the Inventory View, right click on the desired 1830 PSS-1 GBE client port and
select Configure/View VTS Map . Following are the prerequisites for this menu item to be
enabled.
The 1830 PSS-1 GBE card must be provisioned in subrate mode.

The client port must be assigned in order to configure or view VTS Map details.
Result: The Configure/View VTS Map window is displayed.
...................................................................................................................................................................................................
Enter valid CE-VLANID parameters for each client VTS and click Apply .
Note: 1354 RM-PhM displays a pop up error message if valid constraints are violated.
CE-VLANID is not editable if there is a valid cross-connection on the target client
VTS.
....................................................................................................................................................................................................................................
6-20
February 2011
Managing services
Sub-rate service
....................................................................................................................................................................................................................................
Result: Packets are mapped into the client VTS according to the CE-VLANID in the
mapping table.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-21
February 2011
Managing services
Sub-rate service
....................................................................................................................................................................................................................................

A sub-rate service can be created between two 1830 PSS-1 GBE NEs provisioned in
sub-rate mode. It requires all pass through nodes to be provisioned in sub-rate mode also.
The following conditions apply to sub-rate service:
Protected services are not supported with SubGigE layer rate. A message is displayed
at the bottom of the wizard panel if the user selects any protection level other than
UNPROTECTED.
All sub-rate services are Bidirectional.
To create sub-rate service via service wizard

...................................................................................................................................................................................................
In the 1354 RM-PhM Topology View, select the two 1830 PSS-1 GBE NEs for which the
sub-rate service will be created.
...................................................................................................................................................................................................
Click the Provision a Wavelength Service icon

Result: The Provision New Wavelength Service window is displayed. The service
creation wizard lists the common layer rate supported by the two selected NEs.
...................................................................................................................................................................................................
Select SubGigE layer rate for creation of a sub-rate service. Click Next.
Note: Intermediate NEs being in sub-rate mode is not validated until the routing
portion of the wizard.
Result: The Service End Point and Connection Options selection window is
displayed. The A end and Z end client endpoints displays 10 CTPs for each client
port. If the client port is already assigned then it displays 10 SubGigE CTPs or else it
displays 10 unassigned client CTPs.
Note: 1830 PSS-1 GBE client ports can be preassigned and provisioned with client
VLANIDs prior to running the service creation wizard.
...................................................................................................................................................................................................
Provision the connection options against each VTS connection according to the following
criteria:
Committed Information Rate: Ranges from 0 1000 Mbps at 100 Mbps granularity.
Default is 100 Mbps.
Committed Burst Size: Ranges from 16 16384 Kbytes. Default is 256 Kbyte
Excess Information Rate: Ranges from 0 1000 Mbps at 100 Mbps granularity.
Default is 1000 Mbps.
Excess Burst Size: Ranges from 16 16384 Kbytes. Default is 4096 Kbyte.
....................................................................................................................................................................................................................................
6-22
February 2011
Managing services
Sub-rate service
....................................................................................................................................................................................................................................
Following are the restrictions imposed on the above values:
CIR should always be less than or equal to EIR.
CBS should always be less than or equal to EBS.

EIR cannot be zero and should always be greater than or equal to CI
EBS should always be greater than or equal to CBS.
Available Bandwidth on A end and Z End field denotes the unallocated bandwidth on
each client port. This is a read-only field which is calculated by the NE after creation of a
sub-rate service.
If the client port is unassigned, then the service creation requires the CE-VLANID to be
provisioned on the client port before creating the cross-connects on the NE. The
CE-VLANID field is automatically filled if the selected client endpoint is already
provisioned with a valid CE-VLANID using the Configure/View VTS Map menu item
in the Inventory view.
The CE-VLANID displayed in the textbox in the service creation wizard is the
CE-VLANID of the client endpoint on the NE that was selected last in the topology view
before launching the service creation wizard (i.e. the Z end NE). If the CE-VLANID
provisioned on the A End Client port mismatches with the CE-VLANID provisioned on Z
End Client port, then an error message is displayed at the bottom of the screen with the
client endpoint and its CE-VLANID details and the Next button is disabled. The user
must correct or delete the client port provisioning via the Inventory View and then restart
the wavelength service creation wizard to proceed with the creation of the service.
Result: The Next button in the Service Creation wizard is enabled if all the
requirements are satisfied. Otherwise, the Next button is disabled with an error
message displayed at the bottom of the screen.
...................................................................................................................................................................................................
Click Next.
Result: The Service Route Selection window is displayed showing Channel at Link
Start and Channel at Link End information.

...................................................................................................................................................................................................
Click Finish.
....................................................................................................................................................................................................................................
6-23
February 2011
Managing services
Sub-rate service
....................................................................................................................................................................................................................................
Result: 1354 RM-PhM provisions any required cross-connects into the network.
Unlike full-rate GigE cross-connects, the sub-rate cross-connects (with SubGigE as

the layer rate) are provisioned on the NE along with the och cross-connects. It also
provisions service attributes based on System Settings. The default service state can
be defined in the Service Attribute Provisioning tab of the Preferences panel
available under the Admin menu item from the main topology view. If desired the
service attribute dialog can be hidden or shown on each service creation (Do not
show on create option).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-24
February 2011
Managing services
....................................................................................................................................................................................................................................

Creating service for 1696R and 1830 interoperation
The following provisioning steps must be taken on an 1830 OT prior to creating a service
that will interoperate with a 1696R OT. All the provisioning described below is done
using the PhM Inventory View.
Note: If a user wants to make a topological connection between two 1696R/1830
network elements managed by the 1354 RM-PhM, the user should use the Physical
Topology view, clicking on the two ports involved in the connection, and selecting the
appropriate connect option. For 1696R and 1830 network elements, the community
string or the USM user must have an access level of NMS (see Failed to register
1354 RM-PhM as trap destination (p. 5-18)).
PSS-32 11STGE12 / 1696R 10xGE
...................................................................................................................................................................................................
Assign client port as GigE.

Note: Only the first 10 GigE clients can be used.
...................................................................................................................................................................................................
Ensure that the following is provisioned on the 11STGE12 line port:
OTU2 Rate = 11.049

OUT2 FEC Mode = RSFEC
ODU2 Payload Type = 128
E...................................................................................................................................................................................................
N D O F S T E P S
PSS-32 11STAR1 / 1696R OC192sws

...................................................................................................................................................................................................
Assign 11STAR1 client port as OC192.
....................................................................................................................................................................................................................................
6-25
February 2011
Managing services
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Ensure that the following is provisioned on the 11STAR1 line port:
OTU2 Rate = 10.709
OUT2 FEC Mode = EFEC

E...................................................................................................................................................................................................
N D O F S T E P S
PSS-32 11STAR1 / 1696R 10GigELAN

...................................................................................................................................................................................................
Assign 11STAR1 client port as 10GigE.

...................................................................................................................................................................................................
Set 10GigE client port attribute "Encapsulation Mode" to "CBRLAN11.049".

...................................................................................................................................................................................................
Ensure that the following is provisioned on the 11STAR1 line port:
OTU2 Rate = 11.049

OUT2 FEC Mode = EFEC
E...................................................................................................................................................................................................
N D O F S T E P S
PSS1-GBE / 1696R 10xGE
Note: The PSS1-GBE must operate in full-rate operational mode.

To interoperate with 1696R, PSS1-GBE Line port L1 must be facing 1696R 10xGE
line port.
...................................................................................................................................................................................................
Ensure that the following is provisioned on the PSS1-GBE line port L1 facing 1696R:
OTU2 Rate = 11.049

OUT2 FEC Mode = RSFEC
...................................................................................................................................................................................................
Assign client port as GigE.

Note: Only the 1st 10 GigE clients can be used.
....................................................................................................................................................................................................................................
6-26
February 2011
Managing services
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
The time slot assignment should follow 1696R 10xGE, i.e:
c1 <--> vts1
c2 <--> vts2
......
c10 <--> vts10
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-27
February 2011
Managing services
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-28
February 2011
Glossary
...................................................................................................................................................................................................................................
Numerics
1830 PSS
The Alcatel-Lucent 1830 Photonic Service Switch (PSS) product family provides increased
network flexibility and operational automation through zero-touch, transparent photonic
networking. Photonic networks use simplified and accelerated operations to transform wavelength
division multiplexing (WDM) into true transport networking with advanced flexibility,
performance, automation, and integration.
...................................................................................................................................................................................................................................
access identifier (AID)
A unique identifier used to address equipment slots and ports, as well as facility tributaries, that
are defined for the system architecture.
add/drop multiplexer/multiplexing (ADM)
A high-speed multiplexing function offered by SONET that allows lower-level signals to be added
to or dropped from an optical carrier channel. The connection to the add/drop multiplexer is
through a tributary channel at a lower SONET carrier rate or a specific digital speed (for example,
DS3 or DS1).
ADM
See add/drop multiplexer/multiplexing (p. GL-1) for definition.

AHPHG
High Power High Gain DWDM Amplifier. See ALPHG (p. GL-2) for related term.
AID
See access identifier (p. GL-1) for definition.

AIM
See alarm indication message (p. GL-2) for definition.

AINS
Automatic in-service.
AIS
See alarm indication signal (p. GL-2) for definition.
....................................................................................................................................................................................................................................
GL-1
February 2011
Glossary
....................................................................................................................................................................................................................................
alarm
External notification or display of a failure condition. The indication of failure is towards an

external system interface or via audible or visible indicators.
alarm indication message (AIM)
A return message sent from one network element (NE) to another NE that indicates it has received
a signal that is so degraded that it is raising an alarm.
alarm indication signal (AIS)
A signal sent downstream by an NE to indicate that its incoming signal has failed.
alarm list
A status report that lists active alarms on the NE.

alarm log
A history of setting and clearing system alarms on the NE.

alarm severity
An attribute that defines the priority of the alarm message. The method in which alarms are
processed depends on their severity.
ALPHG
Low Power High Gain DWDM Amplifier. See AHPHG (p. GL-1) for related term.
American National Standards Institute (ANSI)
A United States standards body that accredits standards for programming languages,
communications, and networking. ANSI is the U.S. representative in the International
Organization for Standards (ISO).
amplified spontaneous emission (ASE)
Optical noise generated in an erbium-doped fiber amplifier (EDFA) with and without signal input
power.
ANSI
See American National Standards Institute (p. GL-2) for definition.

APD
See avalanche photodiode (p. GL-3) for definition.

APR
See automatic power reduction (p. GL-3) for definition.

APS
See automatic protection switching (p. GL-3) for definition.

APSD
See automatic power shutdown (p. GL-3) for definition.
....................................................................................................................................................................................................................................
GL-2
February 2011
Glossary
....................................................................................................................................................................................................................................
ASE
See amplified spontaneous emission (p. GL-2) for definition.

asynchronous
Data that is transmitted without an associated clock signal.

asynchronous transfer mode (ATM)
A fast-packet, connection-oriented, cell-switching technology for broadband signals. ATM is

designed to accommodate any form of data, including voice, facsimile, computer data, video,
image, and multimedia, whether compressed or uncompressed, whether real-time or non-real-time
in nature, and with guaranteed quality of service (QoS).
ATM networks will accept or reject connections based on a user's average and peak bandwidth
requirements, providing flexible and efficient service for LAN-to-LAN, compressed video, and
other applications that involve variable bit rate (VBR) traffic.
ATM
See asynchronous transfer mode (p. GL-3) for definition.

attenuation
The decrease in signal strength along a fiber optic waveguide caused by absorption and scattering.
Attenuation is usually expressed as dB/km.
attenuator
A passive device that reduces the amplitude of a signal without distorting the waveform.
automatic power reduction (APR)
The lowering of the laser power to a limit that fits into the class 1 category for handling fiber
cables. APR replaces the full power-off feature known as ALS (automatic laser shutdown) or
APSD (automatic power shutdown).
automatic power shutdown (APSD)
A technique (procedure) to automatically shutdown the output power of optical amplifiers to

avoid exposure to hazardous levels.
automatic protection switching (APS)
A network survivability method in which traffic is automatically switched to a protection route

when a failure is detected on a working route.
autonomous message
Message sent by the system to the CIT to notify it of any state change in the system. Autonomous
messages are not responses to a CIT-initiated command. Examples of these messages include
alarms, events (non-alarmed condition), notification of connections that are added or deleted, and
changes in the system database.
avalanche photodiode (APD)
A photodetector that can be regarded as the semiconductor analog to photomultipliers. By

applying a high reverse bias voltage (typically 100-200 V in silicon), an APD shows an internal
current gain effect (around 100) due to impact ionization (avalanche effect).
....................................................................................................................................................................................................................................
GL-3
February 2011
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
back reflection
See Fresnel reflection (p. GL-12).

background block errors (BBE)
Errors identified through OTN performance monitoring.

backward defect indication (BDI)
The OT port has detected a Backward Defect Indication at the ODUk Path layer. This defect
indicates that the peer OTUk port has detected condition that is treated as Server Signal Failure.
band optical filter (BOF)
A band-dependent optical card.

bay
An aluminum steel enclosure for rack-mounted equipment. Also know as a rack.

BB
See broadband (p. GL-5) for definition.

BBA
See broadband amplifier (p. GL-5) for definition.

BBE
See background block errors (p. GL-4) for definition.

BDI
See backward defect indication (p. GL-4) for definition.

BER
See bit error rate (p. GL-4) for definition.

bidirectional line switched ring (BLSR)
A survivable SONET transport architecture that protects against cable cuts and node failures by
providing duplicate, geographically diverse paths for each service. Network elements are
interconnected in a closed fiber loop (four fibers for a four-fiber BLSR architecture or two fibers
for a two-fiber BLSR). A service can reach its destination by traveling in either direction around
the ring. Exactly one-half of the bandwidth available between adjacent nodes in each direction is
used for working traffic, with the remaining bandwidth available for protection.
bit error rate (BER)
BER measures how accurately a bitstream is transmitted through a system. It measures how many
bits are received in error, compared to how many bits are sent.
BLSR
See bidirectional line switched ring (p. GL-4) for definition.
....................................................................................................................................................................................................................................
GL-4
February 2011
Glossary
....................................................................................................................................................................................................................................
BOF
See band optical filter (p. GL-4) for definition.

broadband (BB)
A technology that refers to the always-open gateway to Internet-connected services delivered at

lightning-fast speeds.
broadband amplifier (BBA)
Optical amplifier that supports broadband technology.

...................................................................................................................................................................................................................................
CAD
See channel add/drop card (p. GL-5) for definition.

central office (CO)
A CO can be a building, a switch, or collection of switches where subscriber lines are joined to
switching equipment that connects the subscribers to each other, other subscribers, and/or long
distance subscribers.
CFR
Code of Federal Regulations.

channel
A communications path or the signal sent over that path.

channel add/drop card (CAD)
Used with automatic power management; allows setpoints for a manual transmission line.
channel optical filter (COF)
COF cards facilitate the WaveKey encoding function, employed at service endpoints.
chromatic dispersion
The effect describing the velocity dependence of light travelling through a medium, depending on
its wavelength. For optical telecommunication signals, this effect causes the light pulses to spread
out and the resulting distortion in pulse shape degrades the signal quality.
CIT
See craft interface terminal (p. GL-7) for definition.

cladding
Material that surrounds the core of an optical fiber that has a lower index of refraction compared
to that of the core. The lower index of refraction causes the transmitted light to travel down the
core.
CLEI
See common language element identifier (p. GL-6) for definition.
....................................................................................................................................................................................................................................
GL-5
February 2011
Glossary
....................................................................................................................................................................................................................................
CN
See control network (p. GL-6) for definition.

CO
See central office (p. GL-5) for definition.

coarse wavelength division multiplexing (CWDM)
CWDM is the method of combining multiple signals on laser beams at various wavelengths for
transmission along fiber optic cables. The number of channels is fewer than in dense wavelength
division multiplexing (DWDM), but more than in standard wavelength division multiplexing
(WDM).
COF
See channel optical filter (p. GL-5) for definition.

commissioning and power balance (CPB)
CPB is the web interface for commissioning and power balance operations. The system power
balancing feature is designed to re-optimize power levels throughout the system.
common language element identifier (CLEI)
CLEI codes enable you to clearly and consistently identify and track virtually every type of
telecommunications equipment. In the United States, these codes are assigned by Telecordia, and
are 10 bytes long.
connector
A mechanical or optical device that provides a demountable connection between two fibers or a
fiber and a source or detector.
connector variation
The maximum value in dB of the difference in insertion loss between mating optical connectors
(for example, with re-mating and temperature cycling). Also called optical connector variation.
control network (CN)
The portion of the network that carries control and management traffic (for example,
communications between the NEs and between the NEs and the PhM). The control network does
not carry user traffic. The control communications use the SNMP protocol.
core
The central portion of the fiber that transmits light. It is composed of material with a higher index
of refraction than the cladding.
coupler
An optical device that combines or splits power from optical fibers.

coupling ratio/loss (CR)
The ratio/loss of optical power from one output port to the total output power, expressed as a
percentage.
....................................................................................................................................................................................................................................
GL-6
February 2011
Glossary
....................................................................................................................................................................................................................................
CPB
See commissioning and power balance (p. GL-6) for definition.

CPE
See customer premises equipment (p. GL-7) for definition.

CR
See coupling ratio/loss (p. GL-6) for definition.

craft interface terminal (CIT)
A local interface between humans and a NE. It is used to issue commands to the local system or,
by way of a remote login, to another system on the same fiber as the local system.
customer premises equipment (CPE)
Terminal and associated equipment and inside wiring located at a subscriber's premises. The
equipment is connected with the carrier's communication network at the demarcation point.
CWDM
See coarse wavelength division multiplexing (p. GL-6) for definition.

...................................................................................................................................................................................................................................
data communication network (DCN)
DCN supports communications between network elements (NEs) and the network management
system (NMS).
DCM
See dispersion compensation module (p. GL-7) for definition.

DCN
See data communication network (p. GL-7) for definition.

dense wavelength division multiplexing (DWDM)
A multiplexing technique that uses close spectral spacing of individual optical carrier wavelengths
to reduce the total number of fibers needed to provide a given amount of information-carrying
capacity. The technique takes advantage of desirable transmission characteristics (for example,
minimum dispersion or attenuation) within a given fiber.
DGEF
See dynamic gain equalization filter (p. GL-8) for definition.

DHCP
See dynamic host configuration protocol (p. GL-8) for definition.

dispersion
The temporal spreading of a light signal in an optical waveguide caused by light signals traveling
at different speeds through a fiber either due to modal or chromatic effects.
dispersion compensation module (DCM)
....................................................................................................................................................................................................................................
GL-7
February 2011
Glossary
....................................................................................................................................................................................................................................
Spooled fiber used to control excess dispersion found in certain fiber types at pre- and
post-amplification.
distortion
The difference in value between two measurements of a signal (transmitted and received).
DS3
Standard for digital transmission (American National Standard for telecommunications Carrier-to-Customer Installation - DS3 Metallic Interface, ANSI T1.404- 1989).
DWDM
See dense wavelength division multiplexing (p. GL-7) for definition.

dynamic gain equalization filter (DGEF)
A filter that equalizes the gain of an optical signal.

dynamic host configuration protocol (DHCP)
DHCP allows a DHCP server to automatically assign an IP address to a computer's TCP/IP stack
software. The number is taken from a defined range of numbers for a given network.
...................................................................................................................................................................................................................................
earth
The European term for electrical ground.

EC
See equipment controller (p. GL-9) for definition.

EDFA
See erbium-doped fiber amplifier (p. GL-9) for definition.

edge node
A node that connects to external network or customer equipment, as opposed to providing an

interconnection point between other nodes. It is located at the "edge" of the network.
egress
Traffic leaving a network

EIA
See Electronic Industries Alliance (p. GL-9) for definition.

electrical variable optical attentuator (eVOA)
Works with the Tap module to provide input for Wavelength Tracker modulation and provides
optical tap for feedback signal to the Wavelength Tracker.
electromagnetic capability (EMC)
EMC is the ability of a device or system to function without error in its intended electromagnetic
environment
....................................................................................................................................................................................................................................
GL-8
February 2011
Glossary
....................................................................................................................................................................................................................................
electromagnetic interference (EMI)
EMI refers to the emissions (high-energy, electrically induced magnetic fields) from a device or
system that interfere with the normal operation of another device or system.
Electronic Industries Alliance (EIA)
Group that specifies electrical transmission standards. The EIA and TIA have developed
numerous well-known communications standards, including EIA/TIA-232 and EIA/TIA-449.
electrostatic discharge (ESD)
Static electrical energy potentially harmful to circuit packs and humans.

Element Management System (EMS)
The EMS provides an efficient means of managing the equipment and services within a network,
including creating new services, diagnosing faults, and planning for growth. It includes interfaces
to external systems to allow functions such as billing, service orders, and service level agreement
(SLA) management.
EMC
See electromagnetic capability (p. GL-8) for definition.

EMI
See electromagnetic interference (p. GL-8) for definition.

EMS
See Element Management System (p. GL-9) for definition.

EN
European Norm; a German acronym that stands for Europasche Norm.

Engineering rules
A set of rules that determine the system configuration possibilities based on fiber type, OA, rate,
and number of wavelengths. These rules also determine the maximum loss per span that can be
tolerated, the maximum distance between spans allowed, and the maximum number of spans that
can be supported.
equipment controller (EC)
EC is the equipment controller card,

erbium-doped fiber amplifier (EDFA)
A type of amplifier with a short length of fiber that has been doped with erbium and spliced into
the operating single-mode fiber (SMF) . A three-port wavelength division multiplexer (WDM) is
used, with one incoming port connected to the operating fiber carrying the primary signal in the
1550-nm window, one incoming port attached to a pump laser operating at 980 nm or 1480 nm,
and the one outgoing port connected to the operating fiber.
ESD
See electrostatic discharge (p. GL-9) for definition.
....................................................................................................................................................................................................................................
GL-9
February 2011
Glossary
....................................................................................................................................................................................................................................
Ethernet LAN
A LAN conformant to the 802.3 IEEE standard. This standard supports communications over
shared media where only one device can transmit while all other devices listen. A collision
detection and handling mechanism is incorporated into the standard. Devices on the LAN
communicate by sending Ethernet packets containing a Media Access Control (MAC) address for
the source and destination. Setting the destination MAC address to all ones supports packet
broadcast to all devices on the LAN.
ETSI
See European Telecommunications Standards Institute (p. GL-10) for definition.

European Telecommunications Standards Institute (ETSI)
Located in Sophia-Antipolis, France, ETSI is the European counterpart to ANSI. Its task is to
pave the way for telecommunications integration in the European community as part of the single
European market program. It establishes telecommunication standards for the European
community.
eVOA
See electrical variable optical attentuator (p. GL-8) for definition.

...................................................................................................................................................................................................................................
failure
Occurs when a fault cause persists for a certain period of time.

failure in time (FIT)
A unit of failure rate in reliability analysis. One FIT is equivalent to one failure per one billion
operating hours.
failure rate
The number of failures of a device per unit of time.

FC
See fiber optic connector (p. GL-11) for definition.

FCC
See Federal Communications Commission (p. GL-11) for definition.

FCS
See frame check sequence (p. GL-12) for definition.

FDA
See Food and Drug Administration (p. GL-11) for definition.

FDDI
See fiber distributed data interface (p. GL-11) for definition.

FDI
See forward defect indicator (p. GL-12) for definition.

....................................................................................................................................................................................................................................
GL-10
February 2011
Glossary
....................................................................................................................................................................................................................................
FEC
See forward error correction (p. GL-12) for definition.

Federal Communications Commission (FCC)
The U.S. federal regulatory agency responsible for the regulation of interstate and international
communications by radio, television, wire, satellite, and cable.
Ferrule
A rigid tube that confines or holds a fiber as part of a connector assembly.

fiber distributed data interface (FDDI)
A set of ANSI protocols used for sending digital data over fiber optic cable. FDDI networks are
token-passing networks and support data rates of up to 100 Mbps.
fiber optic cable
A cable containing one or more optical fibers.

fiber optic connector (FC)
A threaded optical connector for single-mode or multimode fiber and applications requiring low
back reflection.
field-programmable gate array (FPGA)
General purpose integrated chip; chip's functions can be programmed by software. FPGAs are
mostly used for rapid development and small or medium quantities production.
file transfer protocol (FTP)
A protocol used for exchanging files over the Internet. FTP uses the Internet's TCP/IP protocols to
enable data transfer. FTP is most commonly used to download/upload a file to/from a server using
the Internet.
FIT
See failure in time (p. GL-10) for definition.

FIT rate
The number of device failures in one billion device hours.

flash disk memory module (FMM)
A nonvolatile memory device used to store the installation software generic or the NE database.
flow
Usually refers to the movement of packets within the network (that is, packet flow).
FMM
See flash disk memory module (p. GL-11) for definition.

FOADM
Fixed optical add/drop multiplexer/multiplexing.

Food and Drug Administration (FDA)
....................................................................................................................................................................................................................................
GL-11
February 2011
Glossary
....................................................................................................................................................................................................................................
An agency of the United States Department of Health and Human Services and is responsible for
the safety regulation of most types of foods, dietary supplements, drugs, vaccines, biological
medical products, blood products, medical devices, radiation-emitting devices, veterinary
products, and cosmetics.
forward defect indicator (FDI)
An automatic and fully distributed capability which indicates a failure in a server networking
layer (e.g., Physical Layer). When used with other mechanisms such as CV (Connectivity
Verification), it can indicate defects such as misbranching of LSPs and errors in swapping LSP
label.
forward error correction (FEC)
A technique used for error detection and correction in which the transmitting host computer
includes some number of redundant bits in the payload (data field) of a block or frame of data.
The receiving device uses those bits to detect, isolate and correct any errors created in
transmission. FEC avoids having to retransmit information which incurred errors in network
transit.
FPGA
See field-programmable gate array (p. GL-11) for definition.

frame check sequence (FCS)
Extra characters added to a frame for error control purposes. Used in HDLC, Frame Relay, and
other data link layer protocols.
Fresnel reflection
A reflection of light that occurs at the air-glass interface at the ends of an optical fiber. See back
reflection (p. GL-4) for related term.
FTP
See file transfer protocol (p. GL-11) for definition.

...................................................................................................................................................................................................................................
gain
The increase in power and magnitude of a signal.

gateway network element (GNE)
A system node that has a physical attachment to the management system to support the access of
the remote NE. The number of remote NEs a GNE can serve is specified in terms of the number
of OSI stack associations that the GNE can support without running out of local resources.
GbE
See Gigabit Ethernet (p. GL-13) for definition.

generic framing protocol (GFP)
Provides a generic mechanism to adapt traffic from higher-layer client signals over an
octet-synchronous transport network. Client signals may be PDU oriented (e.g., PPP/IP or
Ethernet MAC), block oriented (e.g., Fiber Channel or ESCON) or a Constant Bit Rate (CBR)
....................................................................................................................................................................................................................................
GL-12
February 2011
Glossary
....................................................................................................................................................................................................................................
stream.
GFP
See generic framing protocol (p. GL-12) for definition.

Gigabit Ethernet (GBE)
A transmission technology based on the Ethernet frame format and protocol used in local area
networks (LANs) that provides a data rate of one billion bits (one gigabit) per second. Gigabit
Ethernet is defined in the IEEE 802.3 standard and is currently used as the backbone in many
enterprise networks.
glass through-connection
A pair of optical connections between two segments that terminate on the same site.
GNE
See gateway network element (p. GL-12) for definition.

graphical user interface (GUI)
A program interface that takes advantage of the computer's graphics capabilities to make the
program easier to use.
grooming
Consolidating or segregating traffic.

grooming node
A node on which incoming signals of lower rates are added (or aggregated) into a higher-rate
signal for more efficient transport.
ground
The North American term for electrical earth.

GUI
See graphical user interface (p. GL-13) for definition.

...................................................................................................................................................................................................................................
ILA
See in-line amplifier (p. GL-13) for definition.

in-line amplifier (ILA)
A repeater used in WDM technology. See repeater (p. GL-24) for related term.
ingress
Traffic entering a network.

insertion loss
The loss of power that results from inserting a component, such as a connector or splice, into a
previously continuous path.
....................................................................................................................................................................................................................................
GL-13
February 2011
Glossary
....................................................................................................................................................................................................................................
International Standards Organization (ISO)
A United Nations agency concerned with international standardization in a broad range of

industrial and technical fields.
International Telecommunications Union (ITU)
An international civil organization established to promote standardized telecommunications on a

worldwide basis.
Internet protocol (IP)
A standard protocol designed for use in interconnected systems of packet-switched computer

communication networks. The Internet Protocol provides for transmitting blocks of data called
datagrams from sources to destinations, where sources and destinations are hosts identified by
fixed-length addresses. The Internet Protocol also provides for fragmentation and reassembly of
long datagrams, if necessary, for transmission through small-packet networks.
Internet protocol security (IPsec)
A developing standard for security at the network or packet processing layer of network
communication. Earlier security approaches have inserted security at the application layer of the
communications model. IPsec is especially useful for implementing virtual private networks and
for remote user access through dial-up connection to private networks.
Internet service provider (ISP)
A company that provides individuals and other companies access to the Internet and other related
services, such as Web site building and virtual hosting.
IP
See Internet protocol (p. GL-14) for definition.

IPsec (Internet Protocol Security)
See Internet protocol security (p. GL-14) for definition.

ISO
See International Standards Organization (p. GL-13) for definition.

ISP
See Internet service provider (p. GL-14) for definition.

ITU
See International Telecommunications Union (p. GL-14) for definition

...................................................................................................................................................................................................................................
jacket
The outer, protective covering of the cable.

jitter
Small and rapid variations in the timing of a waveform due to noise, changes in component
characteristics, supply voltages, or imperfect synchronizing circuits.
....................................................................................................................................................................................................................................
GL-14
February 2011
Glossary
....................................................................................................................................................................................................................................
jumper
A short fiber optic cable with connectors on both ends.

...................................................................................................................................................................................................................................
lambda ()
The eleventh letter in the Greek alphabet. In optical fiber networking, the term lambda refers to an
individual optical wavelength. See wavelength (p. GL-32) for related term.
laser bias current (LBC)
Current that runs through the laser to make it work. LBC is monitored by performance
monitoring. If the current goes beyond a certain threshold, the circuit pack must be replaced.
LBC
See laser bias current (p. GL-15) for definition.

LBO
See line build out (p. GL-15) for definition.

LC
See Lucent connector (p. GL-16) for definition.

LD
See line driver (p. GL-15) for definition.

LGX
A SONET device that contains ports for optical fiber connections to an optical network element
(NE). An LGX is used to make and change connections to an NE without changing the cabling on
the NE itself.
line build out (LBO)
Attenuation used to simulate a load.

line driver (LD)
Functional unit (circuit pack) providing the OSI model's physical level interface between a data
link and the exchange.
link state advertisement (LSA)
A broadcast message that advertises a link's current status.

LOF
See loss of frame (p. GL-16) for definition.

long reach (LR)
An optic standard that constrains the output power of transmitters and the sensitivity of receivers
for long-haul applications (up to 80 km) without the need for regeneration.
LOS
See loss of service/loss of signal (p. GL-16) for definition.

....................................................................................................................................................................................................................................
GL-15
February 2011
Glossary
....................................................................................................................................................................................................................................
loss
The amount of a signal's power, expressed in dB, that is lost in connectors, splices, or fiber
defects.
loss of frame (LOF)
Loss of frame is detected when the OOF (out-of-frame) anomaly persists for a certain time.
loss of service/loss of signal (LOS)
A condition where the optical input power falls below a certain threshold.
LR
See long reach (p. GL-15) for definition.

LSA
See link state advertisement (p. GL-15) for definition.

Lucent connector (LC)
Designation for a small-form-factor (SFF) design based on a proven 1.25-mm ceramic ferrule.
This connector uses RJ-style latching. It facilitates high-speed applications with lower power
requirements due to lower insertion loss (0.1 dB typical) and higher return loss (55-dB single
mode).
...................................................................................................................................................................................................................................
MAC
See media access control (p. GL-17) for definition.

Management Control Panel (MCP)
The Photonic Manager user interface used to issue commands.

management information base (MIB)
A formal description of a set of network objects that can be managed using the Simple Network
Management Protocol (SNMP). The information is represented in a tree format.
margin
The allowance for attenuation in addition to that explicitly accounted for in system design.
master controller (MC)
The system's master controller (MC) card.

MC
See master controller (p. GL-16) for definition.

MCP
See Management Control Panel (MCP) (p. GL-16) for definition.

mean time between failures (MTBF)
The expected average time between failures usually expressed in hours.

mean time to repair (MTTR)
....................................................................................................................................................................................................................................
GL-16
February 2011
Glossary
....................................................................................................................................................................................................................................
The average time that it takes until a failure is repaired. MTTR is usually expressed in hours.
media access control (MAC)
The MAC address is a computer's unique hardware number. The MAC address is used by the
media access control sublayer of the data link layer of telecommunications protocols.
mesh
A type of network configuration that combines ROADMs to support mesh channel connectivity
between the ROADMs without O-E-O for transmission. It is operated as a single NE with as
many as four degrees (bidirectional DWDM interfaces) that comprise two lines for the east and
two for the west.
MIB
See management information base (p. GL-16) for definition.

mid-stage access amplifier (MSA)
An MSA has two amplifier stages between which can be fibered a DCM/DCF card or an external
dispersion compensation unit.
modulation
A process that modifies the characteristic of one wave (the carrier) by another wave (the signal).
Examples include amplitude modulation (AM), frequency modulation (FM), and pulse-coded
modulation (PCM).
MSA
See mid-stage access amplifier (p. GL-17) for definition.

MTBF
See mean time between failures (p. GL-16) for definition.

MTTR
See mean time to repair (p. GL-16) for definition.

multimode fiber
An optical fiber that has a core large enough to propagate more than one mode of light. The
typical diameter is 62.5 micrometers.
multiplexer (MUX)
A device that combines two or more signals into a single output.

multiplexing
The process that transmits two or more signals over a single communications channel. Examples
include time-division multiplexing and wavelength-division multiplexing.
MUX
See multiplexer (p. GL-17) for definition.
....................................................................................................................................................................................................................................
GL-17
February 2011
Glossary
....................................................................................................................................................................................................................................
muxponder
A networking device that multiplexes and transponds GbE signals.

...................................................................................................................................................................................................................................
NE
See network element (p. GL-18) for definition.

NEBS
See Network Equipment Building System requirements (p. GL-18) for definition.
network element (NE)
Processor-controlled entity of a telecommunications network that primarily provides switching

and transport network functions and contains network operations functions.
For 1830 PSS, a configuration of 1830 PSS equipment at a single site, addressed as a single entity,
and under the control of a single controller (NE). The types of NEs are ILA (in-line amplifier) and
ADM (add/drop multiplexer).
Network Element Management System (NMS)
The NMS provides an efficient means of managing the equipment and services within a network,
including creating new services, diagnosing faults, and planning for growth. It has interfaces to
external systems to allow functions such as billing, service orders, and service level agreement
(SLA) management.
Network Equipment Building System requirements (NEBS)
Developed by Telcordia, standards that vendors must adhere to if they want to sell equipment to
the Regional Bell Operating Companies (RBOCs) and the Competitive Local Exchange Carriers
(CLECs).
network services
Services that the network provider creates only as infrastructure to support user services. For
example, a VPN network service is used to implement an Ethernet service.
network time protocol (NTP)
Internet protocol used to synchronize time between network equipment.

NMS
See Network Element Management System (p. GL-18) for definition.

node
A node (or network element) is a set of one or more Alcatel-Lucent 1830 PSS-32/PSS-16,
Alcatel-Lucent 1830 PSS-4, and Alcatel-Lucent 1830 PSS-1 shelves that are viewed as a single
entity by the Network Management System. A node can be any of the following:
up to two single optical shelves
a single electrical shelf
a single electrical shelf and one or more optical shelves
non-service affecting (NSA)

....................................................................................................................................................................................................................................
GL-18
February 2011
Glossary
....................................................................................................................................................................................................................................
Refers to a condition that does not impact or interfere with network service.
NSA
See non-service affecting (p. GL-18) for definition.

NTP
See network time protocol (p. GL-18) for definition.

...................................................................................................................................................................................................................................
OA
See optical amplifier (p. GL-20) for definition.

OAMP
Operations, Administration, Maintenance, and Provisioning.

OC-n
See optical carrier level-n (p. GL-20) for definition.

Occupational Safety and Health Administration) (OSHA)
OSHA is the main American federal agency charged with the enforcement of safety and health
legislation.
OCHAN or OCh
See optical channel (p. GL-20) for definition.

ODU
See optical demultiplexer (p. GL-20) for definition.

ODU-k
An optical logical connection with a specific rate. The rate can be either ODU-10G or ODU-40G.
OEO
See optical-electrical-optical conversion (p. GL-21) for definition.

OOF
See out of frame (p. GL-21) for definition.

Open Systems Interconnection reference model (OSI)
A seven-layer model that pertains to the logical structure for communications networks
standardized by the International Organization for Standardization (ISO). Adherence to the
standard enables any OSI-compliant system to communicate with any other OSI-compliant
system.
Operations Support System (OSS)
A management system supporting a specific management function, such as alarm surveillance or

provisioning, in a carrier network. Many OSSs are large centralized systems running on
mainframes or minicomputers.
....................................................................................................................................................................................................................................
GL-19
February 2011
Glossary
....................................................................................................................................................................................................................................
OPR
See optical path restoration (p. GL-20) for definition.

OPS
See optical protection switch (p. GL-20) for definition.

optical add/drop multiplexer (OADM)
An OADM is a network element which allows a WDM transmission link to add or drop optical
signals, without converting the photonic stream into an electrical signal. Insertion and extraction
are done using optical filters or demultiplexers. An OADM can be either non-reconfigurable or
reconfigurable; in the latter case, optical switches need to be used.
optical amplifier (OA)
A device that amplifies an input optical signal without converting it into electrical form.
optical carrier level-n (OC-n)
A carrier rate specified in the SONET standard, where n is a numeric.

optical cell
A number of nodes connected by fiber in a predefined manner to provide route diversity to each
node. The simplest form of optical cell is a ring. Statically allocated wavelengths are assigned
within the context of one cell.
optical channel (OCHAN, Och)
An optical wavelength band for WDM optical communications.

optical demultiplexer (ODU)
Value/indicator used for an optical demultiplexer.

optical path protection (OPP)
A protection path is defined when the connection is set up. When a fault is detected on the path,
there is a switch-over from the working path to the protection path to restore the traffic.
optical path restoration (OPR)
A recovery scheme that dynamically finds a protection path when a fault is detected. This method
is usually not capable of matching SDH/SONET recovery time periods (for example, 50 ms).
optical power meter
An instrument that measures the amount of optical power present at the end of a fiber or cable.
optical protection switch (OPS)
An optical circuit pack that provides WDM protection.

optical signal to noise ratio (OSNR)
The ratio between the optical signal power of the data signal and the power of the optical noise
signal.
optical supervisory channel (OSCT)
A designated optical channel used to carry communications related to maintenance and

....................................................................................................................................................................................................................................
GL-20
February 2011
Glossary
....................................................................................................................................................................................................................................
operational functions of the network rather than customer traffic.

The OSCT supports the following communications: node-to-node, interworking, client LAN, and
orderwire communication.
optical transponder (OT)
An OT is a circuit pack that performs optical-to-electrical to optical (OEO) conversion.

OTs perform frequency adaptation between 1830 PSS equipment and external equipment that is
not optically compatible with 1830 PSS Transport. OTs also provide 3R functionality (retiming,
reshaping, reamplification) and perform fault management and performance monitoring
(non-intrusive monitoring) on the SONET/SDH and WaveWrapper signal.
optical transport network (OTN)
A fiber-optic network designed to transport customer traffic, such as an SDH or SONET network.
See Synchronous Digital Hierarchy (p. GL-28) and Synchronous Optical Network
(p. GL-29) for examples.
optical-electrical-optical conversion (OEO)
The process of converting an optical signal to an electrical equivalent and then back to optical
data.
orderwire
A section of the supervisory signal that is used for communication between sites.
OSCT
See optical supervisory channel (p. GL-20) for definition.

OSHA
See Occupational Safety and Health Administration) (p. GL-19) for definition.
OSI
See Open Systems Interconnection reference model (p. GL-19) for definition.
OSNR
See optical signal to noise ratio (p. GL-20) for definition.

OSP
See outside plant (p. GL-22) for definition.

OSS
See Operations Support System (p. GL-19) for definition.

OT
See optical transponder (p. GL-21) for definition.

OTN
See optical transport network (p. GL-21) for definition.

out of frame (OOF)
A state in which the frame alignment sequence of an SDH/SONET frame has not been found for
....................................................................................................................................................................................................................................
GL-21
February 2011
Glossary
....................................................................................................................................................................................................................................
several consecutive frames.

outside plant (OSP)
Refers to outside the central office/building premises.

...................................................................................................................................................................................................................................
PCS
See physical coding sublayer (p. GL-22) for definition.

PDL
See polarization dependent loss (p. GL-22) for definition.

PDU
See protocol data unit (p. GL-23) for definition.

performance monitoring (PM)
Measures the quality of service and identifies any degrading or marginally operating systems
(before an alarm would be generated).
PhM
See photonic manager (p. GL-22) for definition.

photonic cross-connect (PXC)
A fiber cross-connect that operates without optical-electrical-optical conversion. It can have one
or more wavelengths on each fiber or port.
photonic manager (PhM)
A client-server system that is used to perform remote monitoring and control of networks of 1696
ROADM and 1830 PSS equipment.
photonic protection switch (PPS)
By provisioning of PPS cards (or optical splitters), automatic protection switch (APS) are
automatically created.
physical coding sublayer (PCS)
PCS layer monitoring used for Ethernet/FC ports.

PM
See performance monitoring (p. GL-22) for definition.

PMD
See polarization mode dispersion (p. GL-23) for definition.

point-to-point transmission
The transmission between two designated stations.

polarization dependent loss (PDL)
Loss of optical power that occurs during the polarization process. Polarized light waves are light
waves in which the vibrations occur in a single plane. The process of transforming unpolarized
....................................................................................................................................................................................................................................
GL-22
February 2011
Glossary
....................................................................................................................................................................................................................................
light into polarized light is known as polarization (the orientation of the electric and magnetic
field vectors of a propagating electro-magnetic wave).
polarization mode dispersion (PMD)
PMD is an inherent property of all optical media. It is caused by the difference in the propagation
velocities of light in the orthogonal principal polarization states of the transmission medium. The
net effect is that if an optical pulse contains both polarization components, then the different
polarization components will travel at different speeds and arrive at different times, smearing the
received optical signal.
PPS
See photonic protection switch (p. GL-22) for definition.

protocol data unit (PDU)
A device used for the information exchange between equal protocol layers.
provisioning
Placing and configuring hardware and software required to activate a telecommunications service
for a customer. If the equipment is in place, provisioning may consist of creating or modifying a
customer record in a database to activate the services.
PXC
See photonic cross-connect (p. GL-22) for definition.

...................................................................................................................................................................................................................................
QoS
See quality of service (p. GL-23) for definition.

quality of service (QoS)
A set of performance parameters that characterize the transmission quality over a given virtual
connection.
QoS can be quantitatively indicated by channel or system performance parameters, such as
signal-to-noise ratio, bit error ratio, message throughput rate, and call blocking probability.
...................................................................................................................................................................................................................................
rack
A rack is the standardized physical framework on which network equipment such as

Alcatel-Lucent 1830 PSS-32/PSS-16 shelves are mounted. A rack can contain more than one
shelf. Also called bay frames.
random jitter (RJ)
Random jitter is caused by thermal noise and may be modeled as a Gaussian process. The
peak-to-peak value of RJ is of a probabilistic nature, and thus any specific value requires an
associated probability.
....................................................................................................................................................................................................................................
GL-23
February 2011
Glossary
....................................................................................................................................................................................................................................
receiver
A terminal device that includes a detector and signal processing electronics. It functions as an
optical-to-electrical converter.
receiver sensitivity
The minimum optical power required at a receiver to deliver traffic at a guaranteed bit error rate
(BER). This parameter is specified back-to-back (without the effects of chromatic dispersion or
OSNR degradation).
reconfigurable optical add/drop multiplexer (ROADM)
An optical network element with a configuration that can be changed remotely. The main benefit
of this remote reconfigurability is that it reduces Operating Expenditures (OPEX) when operating
a DWDM network. OPEX is reduced because the ROADM eases network provisioning and line
tuning at both the initial installation and any upgrades (to increase the capacity or re-allocate
resources to a new demand matrix).
regeneration
Electrical signal regeneration. Typically, OTUk Section regeneration and ODUk transparency is
implied in this context.
remote network monitoring (RMON)
Provides statistics for remote performance monitoring. Defined in standard RFC 2819.
repeater
A receiver and transmitter set designed to amplify attenuated signals. Repeaters are used to extend
operating range. See in-line amplifier (p. GL-13) for related term.
request for comment (RFC)
A document that describes the specifications of a technology. RFCs are used by the Internet
Engineering Task Force (IETF) and other standards bodies.
restoration domain
A part of the network where traffic restoration is provided in isolation from the rest of the
network.
RFC
See request for comment (p. GL-24) for definition.

RIP
See routing information protocol (p. GL-25) for definition.

RJ
See random jitter (p. GL-23) for definition.

RMON
See remote network monitoring (p. GL-24) for definition.
....................................................................................................................................................................................................................................
GL-24
February 2011
Glossary
....................................................................................................................................................................................................................................
ROADM
See reconfigurable optical add/drop multiplexer (p. GL-24) for definition.

routing information protocol (RIP)
RIP is an interior gateway protocol defined by the IETF (RIPv1 - RFC 1058 and RIPv2 - 2453)
that specifies how routers exchange routing table information. RIP is a routing protocol based on
the distance vector algorithm. With RIP, routers periodically exchange entire tables.
...................................................................................................................................................................................................................................
SA
See service affecting (p. GL-25) for definition.

SAN
See storage area network (p. GL-28) for definition.

SC
See shelf controller (p. GL-26) for definition.

scattering
The change of direction of light rays or photons after striking small particles. It may also be
regarded as the diffusion of a light beam caused by the inhomogeneity of the transmitting
material.
SCOT
See software control of transmission (p. GL-27) for definition.

SDH
See Synchronous Digital Hierarchy (p. GL-28) for definition.

secure shell (SSH)
A secure method of transmitting data.

segment
A pair of OSP fibers connecting two sites.

SELV
Safety extra low voltage.

service affecting (SA)
Refers to a condition that impacts or interferes with network service.

Service Level Agreement (SLA)
A contract between a network service provider and a customer that specifies, usually in
measurable terms, what services the network service provider will provide.
services
Within the Alcatel-Lucent 1830 PSS-32/PSS-16 system, services can be offered directly to end
customers or be used internally to a network as transport infrastructure.
....................................................................................................................................................................................................................................
GL-25
February 2011
Glossary
....................................................................................................................................................................................................................................
SFC
See static filter, CWDM (p. GL-28) for definition.

SFD
See static filter, DWDM (p. GL-28) for definition.

SFP
See small form-factor pluggable module (p. GL-27) for definition.

shared risk group (SRG)
A shared risk group is a group of items that are likely to be affected by a single fault. The items
therefore share the risk of experiencing the fault.
shelf
A shelf is a mechanical facility that is in general a housing for circuit packs. Shelves are housed in
Bays.
An Alcatel-Lucent 1830 PSS-32/PSS-16 node consists of one or more physical shelves equipped
with cards. The shelf provides a chassis or cage with a backplane that can contain multiple cards.
The shelf is mounted in a rack. Each shelf has a shelf controller card, plus its redundant mate.
Every node has one shelf that has its shelf controllers designated as the master controller for the
node. The node appears as a single point in the network topology to the network management
system. Connections between nodes use network links. See node (p. GL-18) for related term.
shelf controller (SC)
The SC card in a Alcatel-Lucent 1830 PSS-32/PSS-16 shelf.

signaling transfer point (STP)
A node in a common channel signalling network with the function of transferring messages from
one signalling link to another and considered exclusively from the viewpoint of the transfer
Simple Network Management Protocol (SNMP)
SNMP is the protocol used to communicate between the Alcatel-Lucent 1830 PSS-32/PSS-16
nodes and the NMS. The SNMP traffic is carried over the Alcatel-Lucent 1830 PSS-32/PSS-16
control network.
simplex
A single element (for example, a simplex connector is a single-fiber connector).

single-mode fiber (SMF)
A type of fiber which is very small in diameter and allows the light to be reflected in a single way
along the lightguide such that there is coherence in the arrival of the light signal.
site
The termination location of OSP cables. Each site can contain one or more NEs and one or more
glass-through connections.
....................................................................................................................................................................................................................................
GL-26
February 2011
Glossary
....................................................................................................................................................................................................................................
SLA
See Service Level Agreement (p. GL-25) for definition.

small form-factor pluggable module (SFP)
An optical modular, hot-pluggable transceiver (compatible with IEEE-802.3z) designed for use
with small form factor (SFF) connectors, offering high speed and physical compactness. SFP
transceivers perform at data speeds of up to 5 gigabits per second, and possibly higher.
The SFP modules can be easily interchanged, therefore, electro-optical or fiber optic networks can
be upgraded and maintained more conveniently than has been the case with traditional soldered-in
modules. Rather than replacing an entire circuit board containing several soldered-in modules, a
single module can be removed and replaced for repair or upgrading. This can result in a
substantial cost savings, both in maintenance and in upgrading efforts.
SMF
See single-mode fiber (p. GL-26) for definition.

SNCP
See Sub-Network Connection Protocol (p. GL-28) for definition.

SNMP
See Simple Network Management Protocol (p. GL-26) for definition.

software control of transmission (SCOT)
System software that controls the settings of EDFA pumps, VOAs, Raman pumps, DCM pumps,
DGEFs, and blockers in the ROADM NEs.
software generic (SW generic)
The whole software and (static) data associated with a particular NE release.
SONET
See Synchronous Optical Network (p. GL-29) for definition.

SONET wavelength service
The SONET wavelength service provides transport of SONET signals through the Alcatel-Lucent
1830 PSS-32/PSS-16 network.
span
A fiber link between NEs that can be unidirectional or bidirectional, depending on the network
design. Multiple segments in tandem are connected by glass-through connections.
span loss
Loss (in dB) of optical power due to the span transmission medium (includes fiber loss and splice
losses).
splice
A permanent connection of two optical fibers through fusion or mechanical means.
....................................................................................................................................................................................................................................
GL-27
February 2011
Glossary
....................................................................................................................................................................................................................................
SRG
See shared risk group (p. GL-26) for definition.

SSH
See secure shell (p. GL-25) for definition.

SSMF
See standard single-mode fiber (p. GL-28) for definition.

ST
See straight-tip connector (p. GL-28) for definition.

standard single-mode fiber (SSMF)
This is the most common type of fiber deployed. This fiber was designed to provide zero
chromatic dispersion at 1310 nm, to support the early long-haul transmission systems operating at
this wavelength. It has a chromatic dispersion of at most 20 ps/(nm*km) in the 1550 nm
wavelength range and usually around 17 ps/(nm*km).
static filter, CWDM (SFC)
A static filter card used with a CWDM circuit pack.

static filter, DWDM (SFD)
A static filter card used with a DWDM circuit pack.

storage area network (SAN)
A high-speed special-purpose network (or subnetwork) that interconnects different kinds of data
storage devices with associated data servers on behalf of a larger network of users.
STP
See signaling transfer point (p. GL-26) for definition.

straight-tip connector (ST)
Fiber optic connector that uses a bayonet-style coupling rather than a screw-on coupling.
STS, STS-n
See synchronous transport signal-n (p. GL-29) for definition.

Sub-Network Connection Protocol (SNCP)
An SDH version of UPSR. See SDH and UPSR.

SW generic
See software generic (p. GL-27) for definition.

Synchronous Digital Hierarchy (SDH)
A family of digital transmission rates used outside of the U.S. and Japan from 51.84 Mb/s to 40
Gb/s that allows the interconnection of transmission products around the world.
SDH is the standard technology for synchronous data transmission on optical media. It is the
international equivalent of Synchronous Optical Network (SONET). Both SDH and SONET
technologies provide faster and less costly network interconnection than traditional
....................................................................................................................................................................................................................................
GL-28
February 2011
Glossary
....................................................................................................................................................................................................................................
Plesiochronous Digital Hierarchy (PDH) equipment.

Synchronous Optical Network (SONET)
A North-American standard developed by Telecordia and adapted by ANSI for the optical
long-distance networks.
SONET is the interface standard for synchronous optical-fiber transmission, applicable to the
physical layer of the OSI reference model. SONET has a basic bit rate of 51.840 mB/s, called
OC-1, that is used to define higher rates (OC-3, OC-12, OC-48, and so on) carried as a channel on
an optical fiber.
synchronous signal
A data signal that is sent along with a clock signal.

synchronous transport signal-n (STS, STS-n)
The basic logical building block signal with a rate of 51.840 Mb/s for an STS-1 signal and a rate
of n times 51.840 Mb/s for an STS-n signal (where n is a numeric).
...................................................................................................................................................................................................................................
tap
The entry point into a system module.

target identifier (TID)
A provisionable parameter used to identify an NE within a TL1 command.

TCA
See threshold crossing alert (p. GL-29) for definition.

TCP
See Transmission Control Protocol (p. GL-30) for definition.

TCP/IP
A suite of several networking protocols developed for the Internet that provides communication
across interconnected networks, between computers with diverse hardware architectures and
various operating systems. Some examples are FTP, SMTP, and SNMP.
TDM
See time-division multiplexing (p. GL-30) for definition.

Telecommunications Management Network (TMN)
A network that interfaces with a telecommunications network at several points to receive

information from, and to control the operation of, the telecommunications network.
thermal noise
Noise resulting from thermally induced random fluctuation in the receiver's load resistance
current.
threshold crossing alert (TCA)
A condition set when a counter exceeds a user-selected high or low threshold. A TCA does not
....................................................................................................................................................................................................................................
GL-29
February 2011
Glossary
....................................................................................................................................................................................................................................
generate an alarm but is available on demand through the CIT.

TID
See target identifier (p. GL-29) for definition.

time-division multiplexing (TDM)
A multiplexing technique whereby two or more channels are derived from a transmission medium
by dividing access to the medium into sequential intervals. Each channel has access to the entire
bandwidth of the medium during its interval. This implies that one transmitter uses one channel to
send several bit streams of information.
TL1 (Transaction language 1)
An OS/NE machine-to-machine language. TL1 messages are expressed as ASCII strings. TL1
messages and syntax are defined by Telecordia.
TMN
See Telecommunications Management Network (p. GL-29) for definition.

TOADM
See tunable optical add/drop multiplexer (p. GL-30) for definition.

topology
The pattern of interconnections between nodes in a network, such as a ring or hub. A network
topology database contains information regarding each link in the network.
traffic grooming
Traffic can be consolidated, aggregated, or separated to achieve efficiencies of routing.

Transmission Control Protocol (TCP)
A protocol used with the Internet Protocol to send data in the form of message units between
computers over the Internet. While IP handles the actual delivery of the data, TCP keeps track of
the individual units of data (called packets) that a message is divided into for efficient routing
through the Internet.
traps (SNMP)
SNMP traps are unacknowledged events sent from an agent to a manager. In a Alcatel-Lucent
1830 PSS-32/PSS-16 network, the agent is the node and the manager is PhM.
tunable optical add/drop multiplexer (TOADM)
A tunable ROADM that yields the ultimate in operational flexibility, especially when used in
conjunction with transponders with tunable wavelength lasers.
...................................................................................................................................................................................................................................
UDP
See user datagram protocol (p. GL-31) for definition.
....................................................................................................................................................................................................................................
GL-30
February 2011
Glossary
....................................................................................................................................................................................................................................
UL
See Underwriters Laboratories (p. GL-31) for definition.

Underwriters Laboratories (UL)
A U.S. non-profit privately owned and operated product safety testing and certification
organization. Develops standards and test procedures for products, materials, components,
assemblies, tools and equipment, chiefly dealing with product safety.
unidirectional path-switched ring (UPSR)
A survivable, closed loop transport architecture that protects against cable cuts and node failures
by providing duplicate, geographically diverse paths for each service. Adjacent nodes on the ring
are interconnected using a single pair of optical fibers. One fiber transports traffic in one direction
(for example, clockwise), while the second fiber transports traffic in the opposite direction (for
example, counterclockwise). In a UPSR, the source node bridges its outgoing traffic along
opposite directions around the ring (on paths provided by SONET synchronous transport
channels). In contrast to BLSR, a UPSR:
is path-specific as opposed to line specific
does not allow extra traffic (because traffic is bridged)
requires less coordination from source to destination (because the destination network
element can make all its decisions without involving the source)
UPSR
See unidirectional path-switched ring (p. GL-31) for definition.

user datagram protocol (UDP)
A minimal, datagram-oriented, transport network protocol above the IP network layer that does
not guarantee data ordering or delivery. Because it is datagram-oriented, each send operation by
the application results in the transmission of a single IP datagram. This contrasts with the
Transmission Control Protocol (TCP) which is byte stream oriented and guarantees the delivery
and ordering of the bytes sent. Because it is a byte stream oriented, a single send operation may
result in a no IP datagrams (buffering), a single IP datagram, or multiple IP datagrams.
user services
Services that the network provider can sell to their customers, such as Ethernet service.
UTC
Coordinated universal time.

...................................................................................................................................................................................................................................
variable optical attenuator (VOA)
A device used to set the attenuation of the power received over a fiber to a level required by the
receiving equipment.
....................................................................................................................................................................................................................................
GL-31
February 2011
Glossary
....................................................................................................................................................................................................................................
VCAT
See virtual concatenation (p. GL-32) for definition.

very short reach (VSR)
A SONET/SDH interface that provides a low-cost interconnection solution of less than 300
meters between routers, switches, and DWDM systems.
virtual concatenation (VCAT)
Defines an inverse multiplexing procedure whereby the contiguous bandwidth is broken into
individual Virtual Containers (VC) at the source transmitter and logically represented in a Virtual
Concatenation Group (VCG). VCG members are transported as individual VCs across the
SONET/SDH network and recombined at the destination VCG receiver. While contiguous
concatenation requires concatenation functionality at each network element, virtual concatenation
do not.
virtual time-slot (VTS)
1830 PSS-1 GBE Edge Device has a fixed assignment of 10 Virtual Time Slots to each line port.
VOA
See variable optical attenuator (p. GL-31) for definition.

VSR
See very short reach (p. GL-32) for definition.

VTS
See virtual time-slot (p. GL-32) for definition.

...................................................................................................................................................................................................................................
wave division multiplexing (WDM)
WDM merges optical traffic onto one common fiber, sending several signals through one fiber
with different wavelengths of light. WDM allows flexibility in expanding bandwidth. It reduces
costly mux/demux function, and it reuses existing optical signals.See dense wave division
multiplexing (DWDM).
wave key
A component of the Wavelength Tracker monitoring capability that is used to identify individual
wavelengths through the network.
A wave key is a number between 1 and 2048. Each WDM wavelength in a 1830 PSS-32 network
is uniquely identified by a pair of wave keys.
waveguide
A material medium that confines and guides a propagating electromagnetic wave.

waveguide coupler
A coupler that transfers light between planar waveguides.
....................................................................................................................................................................................................................................
GL-32
February 2011
Glossary
....................................................................................................................................................................................................................................
wavelength
The distance between points of corresponding phase of two consecutive cycles of a wave,
typically measured in nanometers (nm). The wavelength is related to the propagation velocity and
the frequency. (Also called lambda.)
wavelength growth
A type of growth in which all eight wavelengths are added to a single line before more lines are
added.
Wavelength Tracker monitoring capability
Wavelength Tracker monitoring capability is a patented feature of Alcatel-Lucent 1830

PSS-32/PSS-16 which allows for the tracking of wavelengths through the Alcatel-Lucent 1830
PSS-32/PSS-16 network, and for the measuring of the wavelengths' optical power levels at certain
points along their paths.
WaveWrapper
WaveWrapper provides network management functions such as optical-layer performance

monitoring, error correction, and ring protection on a per-wavelength basis.
WDM
See wave division multiplexing (p. GL-32) for definition.

WDM demand
The termination points and signal type of a service that is to be carried by the WDM network.
WDM line
A contiguous series of spans terminated by a ROADM at each end. A WDM line can be a single
span or a series of spans joined by the in-line amplifiers (ILAs).
Web user interface (WebUI)
A computer interface that provides web-based access to the network element (NE).
WebUI
See Web user interface (p. GL-33) for definition.

...................................................................................................................................................................................................................................
XFP (10-gigabit small form factor pluggable module)
A pluggable optical transceiver module that combines transmitter and receiver functions in one
compact, flexible, and low cost package format. Up to sixteen XFP modules can be arranged on a
typical rack card, allowing for an unprecedented level of data density. XFP is protocol
independent, are can support OC-192/STM-64, 10 Gigabit Ethernet, 10 Gigabit Fibre Channel,
and G.709 data streams in routers, switches and network cards. Reaches ranging from Very Short
Reach (VSR) to Long Reach (LR) can also be supported.
....................................................................................................................................................................................................................................
GL-33
February 2011
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Y-coupler
A coupler that has three waveguide legs joined at the center in a "Y" shape which connects an
input port to two output ports or two input ports to a single output port.
...................................................................................................................................................................................................................................
ZIC (zero installation craft)
An NE-imbedded graphical user interface (GUI) application for local operation and maintenance.
....................................................................................................................................................................................................................................
GL-34
February 2011
Index
A alarm
reference information, 5-1

alarm troubleshooting, 4-18
Windows 2000, stopping, 2-32
N navigation
audience, xix
acknowledging, 4-9
conventions, xix, xx
clearing, 4-11
Duplicate WaveKey alarm
history, viewing, 4-12
audience
.............................................................
documentation
alarms
Wavelength Tracker, 4-18
Windows 2000, starting, 2-31
troubleshooting, 4-27
.............................................................
E events
documentation, xix
system, monitoring, 4-1
.............................................................
.............................................................
B background
map, defining, 3-2

.............................................................
C client session
information
new with this issue, xx
Invalid WaveKey alarm
logging out, 2-35
.............................................................
starting, 2-33
L links
types of, 3-2

network
alarms, 4-3
navigating, 3-1
network elements
moving, 3-2
network link
topology, showing, 3-17
Network management server, 1-1
Network Management System
(NMS)
communication, 1-3
hardware configuration, 1-2
overview, 1-1
.............................................................
command syntax
conventions, xx
conventions
command syntax, xx
documentation, xix, xx
.............................................................
O optical power levels, 3-24
topologies, 3-3
logging out
client session, 2-35
BOF WDM port, 3-25

channel path, 3-24
.............................................................
.............................................................
M Missing WaveKey alarm
P power out of range alarm
D database
backup, 2-40
....................................................................................................................................................................................................................................
IN-1
February 2011
Index
....................................................................................................................................................................................................................................
.............................................................
R reference information
alarms, 5-1
.............................................................
S server
starting, 2-24
stopping, 2-24
server and client, 2-1
servers
used for a service, 4-21

Wavelength Tracker, 3-23, 4-18
wavelength usage matrix, 6-4
WIN, 6-5
Windows 2000
database, starting, 2-31
database, stopping, 2-32
server, starting, 2-31
server, stopping, 2-32
Solaris, stopping, 2-29

Windows 2000, starting, 2-31
Windows 2000, stopping, 2-32
services
creating, 6-5
listing and editing, 6-3
managing, 6-1
WIN, 6-5
Solaris
server, starting, 2-25
server, stopping, 2-29
system
events, monitoring, 4-1
.............................................................
T Telnet
cut-thru, 3-44, 3-45, 3-46

topologies
geographical location,
topologies, 3-2
.............................................................
W WaveKey insertion failed alarm
WaveKeys
querying, 4-22
....................................................................................................................................................................................................................................
IN-2
February 2011

PHM Manual

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PHM Manual

Încărcat de

Drepturi de autor:

Formate disponibile

Title page

Interference Information: Part 15 of FCC Rules

Document support ...................................................................................................................................................................... xxi

How to order ............................................................................................................................................................................... xxii

System requirements ................................................................................................................................................................ 2-3

Before you start ....................................................................................................................................................................... 2-12

Starting and stopping the server and client

1354 RM-PhM service wrapper ........................................................................................................................................ 2-24

Configuring the NTP properties of the network elements ....................................................................................... 2-38

1354 RM-PhM database backup ....................................................................................................................................... 2-40

Recovering from file corruption without having to restore from a backup

Performing a server switch-over ....................................................................................................................................... 2-44

Performance Monitoring (PM) Archive Setting

SNMP Trap Alarm Forwarding

RADIUS server and user authentication

1354 RM-PhM user management

1354 RM-PhM login session settings

1696 ROADM and 1830 PSS network element software management

1354 RM-PhM management of Red-C RAMAN Amplifier & EDFA Booster

Configuring and navigating the network

Showing topological connections ..................................................................................................................................... 3-17

Configuring the network element and network fiber topology

Using Wavelength Tracker monitoring capability ...................................................................................................... 3-23

WebUI cut-thru ........................................................................................................................................................................ 3-46

Monitoring system events and network alarms

Opening an alarm window for a managed object or group

Using the 1354 RM-PhM log view

Starting and stopping PM collection

Viewing PM data and raw PM data ................................................................................................................................. 4-17

Configuring PM and TCA profiles ................................................................................................................................... 4-17

Determining the source of an alarm

Determining the WaveKeys used for a service ............................................................................................................ 4-21

Troubleshooting the WaveKey insertion failed alarm ............................................................................................... 4-23

Troubleshooting the Invalid WaveKey alarm ............................................................................................................... 4-29

1354 RM-PhM alarm reference

A communication failure occurred

Duplicate programmed wave key

Equipment cache invalid

Failed Auto Discovery

Failed to register 1354 RM-PhM as trap destination

Fault log archive configuration failed

Install Extension error

Invalid XML reference

Invalid XML value

JDBC Log Data Store Error

Low Level Parsing Error

Missing XML mandatory attribute

Missing XML mandatory element

NE + neName + "PM retrieval failed"

NE + neName + "system time out of sync with 1354 RM-PhM"

Network Connection error

1354 RM-PhM behind in performing PM tasks

1354 RM-PhM failed to initialize adaptation

1354 RM-PhM PowerCommissionInProgress

Object Prop Change

Service definition downloaded

SNMP Bulk Get Error

SNMP Error received

SNMP Get Error

SNMP GetNext Error

SNMP Set Error

Unrecognized XML element