User Provisioning Guide

Title page
Alcatel-Lucent 1830
PHOTONIC SERVICE SWITCH 36/32/16 (PSS-36/PSS32/PSS-16) | Release 3.6.0 and 3.6.1
User Provisioning Guide
8DG60888BAAA
ISSUE 2
AUGUST 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 (p. xiii) in the section titled About this document .
Contents
About this document
Purpose
............................................................................................................................................................................................. xi
xi
Audience
.......................................................................................................................................................................................... xi
xi
Document conventions .............................................................................................................................................................. xii

xii
Related information
.................................................................................................................................................................... xii
xii
Document support ...................................................................................................................................................................... xiii

xiii
Technical support
How to order
....................................................................................................................................................................... xiii
xiii
................................................................................................................................................................................ xiii
xiii
Packaging collection and recovery requirements

Recycling/Take-Back/Disposal of Product
........................................................................................................... xiv
........................................................................................................................ xv
Safety information ....................................................................................................................................................................... xv

xv
How to comment .......................................................................................................................................................................... xv
xv
1
Safety
Overview ...................................................................................................................................................................................... 1-1
1-1
Structure of safety statements ............................................................................................................................................... 1-1
1-1
General notes on safety ........................................................................................................................................................... 1-3
1-3
Laser safety
................................................................................................................................................................................. 1-4
1-4
Electrostatic discharge .......................................................................................................................................................... 1-11

1-11
Save these safety instructions
2
............................................................................................................................................ 1-13
1-13
Security administration
Overview ...................................................................................................................................................................................... 2-1
2-1
User accounts and privileges ................................................................................................................................................ 2-2
2-2
Configuring user accounts ..................................................................................................................................................... 2-6
2-6
....................................................................................................................................................................................................................................
1830 PSS User Provisioning Guide
iii
Release 3.6.0 and 3.6.1
8DG60888BAAA Issue 2
August 2011
Contents
....................................................................................................................................................................................................................................
Procedures to configure user accounts

Login sessions
.......................................................................................................................... 2-10
2-10
......................................................................................................................................................................... 2-13
2-13
System security features
...................................................................................................................................................... 2-14
2-14
Log procedures ........................................................................................................................................................................ 2-21

2-21
Authentication
......................................................................................................................................................................... 2-22
2-22
RADIUS server procedures ................................................................................................................................................ 2-27

2-27
SNMP procedures
3
.................................................................................................................................................................. 2-29
2-29
Data communication setup

Overview ...................................................................................................................................................................................... 3-1
3-1
User interfaces
........................................................................................................................................................................... 3-2
3-2
Communications network ...................................................................................................................................................... 3-7

3-7
Gateway NE (GNE) management ....................................................................................................................................... 3-9
3-9
Data communication set-up procedures ......................................................................................................................... 3-12
3-12
Connection establishment
................................................................................................................................................... 3-17
3-17
Connection release ................................................................................................................................................................. 3-17

3-17
CIT port ...................................................................................................................................................................................... 3-17
3-17
Using the WebUI
.................................................................................................................................................................... 3-18
3-18
WebUI startup procedures ................................................................................................................................................... 3-20

3-20
4
Equipment provisioning
Overview ...................................................................................................................................................................................... 4-1
4-1
Introduction ................................................................................................................................................................................. 4-2
4-2
Provisioning system (NE) procedures ............................................................................................................................... 4-3
4-3
Equipment management ......................................................................................................................................................... 4-5
4-5
Shelf provisioning .................................................................................................................................................................. 4-25
4-25
Shelf provisioning procedures ........................................................................................................................................... 4-30
4-30
Slot/card provisioning ........................................................................................................................................................... 4-31
4-31
....................................................................................................................................................................................................................................
iv
August 2011
Contents
....................................................................................................................................................................................................................................
Slot/card provisioning procedures .................................................................................................................................... 4-46

4-46
Port/facility provisioning ..................................................................................................................................................... 4-50
4-50
Port provisioning procedures ........................................................................................................................................... 4-202
4-202
5
Alarm management
Overview ...................................................................................................................................................................................... 5-1
5-1
Description
.................................................................................................................................................................................. 5-1
5-1
Alarm management procedures ........................................................................................................................................... 5-6

5-6
6
Performance monitoring
Overview ...................................................................................................................................................................................... 6-1
6-1
Description
.................................................................................................................................................................................. 6-1
6-1
Performance monitoring procedures .................................................................................................................................. 6-8

6-8
7
Connections
Overview ...................................................................................................................................................................................... 7-1
7-1
Description
.................................................................................................................................................................................. 7-1
7-1
Connections procedures .......................................................................................................................................................... 7-6

7-6
8
Protection
Overview ...................................................................................................................................................................................... 8-1
8-1
Description
.................................................................................................................................................................................. 8-1
8-1
Protection procedures .............................................................................................................................................................. 8-8

8-8
9
Wavelength Tracker
Overview ...................................................................................................................................................................................... 9-1
9-1
Description
.................................................................................................................................................................................. 9-1
9-1
Wave keys procedures ............................................................................................................................................................. 9-6

9-6
FOADM / FOADM-TOADM procedures ..................................................................................................................... 9-11
9-11
10
Database backup and restore

Overview
................................................................................................................................................................................... 10-1
10-1
....................................................................................................................................................................................................................................
v
August 2011
Contents
....................................................................................................................................................................................................................................
Database management .......................................................................................................................................................... 10-1

10-1
Database backup ..................................................................................................................................................................... 10-6
10-6
Database restore ...................................................................................................................................................................... 10-8
10-8
Database backup/restore procedures ............................................................................................................................. 10-10
10-10
11
Routine procedures
Overview
................................................................................................................................................................................... 11-1
11-1
User preferences ...................................................................................................................................................................... 11-2

11-2
Syslog properties
.................................................................................................................................................................... 11-3
11-3
User activity logging ............................................................................................................................................................. 11-4

11-4
Date/time setting ..................................................................................................................................................................... 11-5
11-5
Loopbacks
................................................................................................................................................................................. 11-8
11-8
Power settings
....................................................................................................................................................................... 11-10
11-10
Power commissioning
........................................................................................................................................................ 11-14
11-14
Software upgrade/downgrade .......................................................................................................................................... 11-16

11-16
Glossary
Index
....................................................................................................................................................................................................................................
vi
August 2011
List of tables
2-1
User privilege levels
................................................................................................................................................. 2-3
2-3
2-2
Ports that support ACL filtering ......................................................................................................................... 2-19
3-1
Communications Network Sizing ........................................................................................................................ 3-8
4-1
1830 PSS-36 Circuit Pack Slot Allocation ..................................................................................................... 4-11
4-2
1830 PSS-32 Circuit Pack Slot Allocation
.................................................................................................... 4-14
4-3
.................................................................................................... 4-18
4-4
1830 PSS Shelf Combinations
6-1
Cards and Ports that Support PM Data
........................................................................................................................... 4-26
.............................................................................................................. 6-8
....................................................................................................................................................................................................................................
vii
August 2011
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
viii
August 2011
List of figures
1-1
Laser warning labels
.............................................................................................................................................. 1-10
1-10
1-2
Static control wrist strap
1-3
ESD warning label (barred-hand symbol)
3-1
Dual GNE configurations ..................................................................................................................................... 3-11
3-2
Equipment tree hierarchy
4-1
11STMM10 OT signal processing from client port to DWDM line port
6-1
Performance monitoring points in an 1830 PSS NE
6-2
Analog parameter TCA
11-1
Loopback Types
....................................................................................................................................... 1-12
1-12
..................................................................................................... 1-13
..................................................................................................................................... 3-19
.......................................... 4-37
.................................................................................... 6-3
........................................................................................................................................... 6-5
6-5
....................................................................................................................................................... 11-9
11-9
....................................................................................................................................................................................................................................
ix
August 2011
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
x
August 2011
About this document

About this document
Purpose
This document provides information about provisioning the Alcatel-Lucent 1830 PSS
network element. It contains the following sections:
Chapter 1, Safety
Chapter 2, Security administration
Chapter 3, Data communication setup

Chapter 4, Equipment provisioning
Chapter 5, Alarm management
Chapter 6, Performance monitoring
Chapter 7, Connections
Chapter 8, Protection
Chapter 9, Wavelength Tracker
Chapter 10, Database backup and restore
Chapter 11, Routine procedures
Audience
This document is intended for the following users of the Alcatel-Lucent 1830 PSS
documentation library:
administrators
operators
maintenance personnel
Alcatel-Lucent 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
Alcatel-Lucent 1830 PSS product documentation are intended for use by trained and
qualified personnel.
...................................................................................................................................................................................................................................
xi
August 2011
About this document

....................................................................................................................................................................................................................................
Document conventions
The following typographical conventions are used throughout this document:
Bold is used to identify WebUI menu selections and button selections.
Italic is used to identify NE messages

Computer voice is used to identify system message text displayed by the WebUI
Related information
The 1830 PSS User Provisioning Guide is part of a set of documents that support the
Alcatel-Lucent 1830 PSS System. The following items are available:
Document Number
Document Title
8DG60888AAAA
Alcatel-Lucent 1830 Photonic Service Switch 36/32/16

(PSS-36/32/16) Release 3.6.0 and 3.6.1 Product Information and
Planning Guide
8DG60888BAAA

(PSS-36/32/16) Release 3.6.0 and 3.6.1 User Provisioning Guide
8DG60888CAAA

(PSS-36/32/16) Release 3.6.0 and 3.6.1 Maintenance and
Trouble-Clearing Guide
8DG60888DAAA

(PSS-36/PSS-32/PSS-16) Release 3.6.0 and 3.6.1 Installation and
System Turn-Up Guide
8DG60888EAAA
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 3.6.0

and 3.6.1 TL1 Commands and Messages Guide
8DG60888FAAA

and 3.6.1 Command Line Interface Guide
8DG60888GAAA

Engineering and Planning Tool User Guide
8DG60888HAAA

and 3.6.1 Safety Guide
8DG60888JAAA

(PSS-36/32/16) Release 3.6.0 and 3.6.1 Quick Reference Guide
8DG60888KAAA
Alcatel-Lucent 1830 Photonic Service Switch 1 (PSS-1) Release

1.1.0 MSAH User Guide
8DG60888LAAA

1.8.0 MD4H Edge Device User Guide
....................................................................................................................................................................................................................................
xii
August 2011
About this document

....................................................................................................................................................................................................................................
Document Number
Document Title
8DG60888MAAA

(PSS-36/32/16) Release 3.6.1 GMPLS Command Line Interface
Guide
8DG60888NAAA

(PSS-36/32/16) Release 3.6.1 GMRE/GMPLS Configuration
Guide
8DG60888RAAA

(PSS-36/32/16) Release 3.6.0 and 3.6.1 Data Communication
Network (DCN) Planning Guide
3AL61336AAAA
Alcatel-Lucent 1354 RM-PhM Release 8.6 Photonic Manager

EMS Reference Guide
3KC13011AAAA

1.5.x User Guide
8DG60418LAAA

2.7.0 GBEH Edge Device User Guide
8DG60386JAAA
Alcatel-Lucent 1830 Photonic Service Switch (PSS-1) Release

1.0.0 AHP Amplifier User Guide
8DG60777KAAA
Alcatel-Lucent 1830 PSS-32 RAMAN Amplifier and EDFA Release

2.0.0 User Guide
8DG60889AAAA
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Product

Family Release 3.6.0 and 3.6.1 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).
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".
....................................................................................................................................................................................................................................
xiii
August 2011
About this document

....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
xiv
August 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.
Safety information
For your safety, this document contains safety statements. Safety statements are given at
points where risks of damage to personnel, equipment, and operation may exist. Failure to
follow the directions in a safety statement may result in serious consequences.
How to comment
To order Alcatel-Lucent documents, contact your local sales representative or use Online
Customer Support (OLCS) (https://support.lucent.com).
....................................................................................................................................................................................................................................
xv
August 2011
About this document

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xvi
August 2011
Safety
1
Overview
Purpose
This chapter provides important safety instructions for Alcatel-Lucent 1830 Photonic
Service Switch 36/32/16 (PSS-36/PSS-32/PSS-16).
Contents
Structure of safety statements
1-1
General notes on safety
1-3
Laser safety
1-4
Electrostatic discharge
1-11
1-13

Overview
Safety statements describe the safety risks relevant while performing tasks on
Alcatel-Lucent products during deployment and/or use. Failure to avoid the hazards may
have serious consequences.
General structure
Safety statements include the following structural elements:
...................................................................................................................................................................................................................................
1-1
August 2011
Safety
....................................................................................................................................................................................................................................
D
CAUTION
Lifting hazard
Lifting this equipment by yourself can result in injury

due to the size and weight of the equipment.
Always use three people or a lifting device to transport
and position this equipment.
[ABC123]
F
G
H
Item
Structure element
Purpose
Safety alert symbol
Indicates the potential for personal injury

(optional)
Safety symbol
Indicates hazard type (optional)
Signal word
Indicates the severity of the hazard
Hazard type
Describes the source of the risk of damage or

injury
Safety message
Consequences if protective measures fail
Avoidance message
Protective measures to take to avoid the hazard
Identifier
The reference ID of the safety statement

(optional)
Signal words
The signal words identify the hazard severity levels as follows:

Signal word
Meaning
DANGER
Indicates an extremely hazardous situation which, if not avoided, will

result in death or serious injury.
WARNING
Indicates a hazardous situation which, if not avoided, could result in

death or serious injury.
CAUTION
Indicates a hazardous situation which, if not avoided, could result in

minor or moderate injury.
NOTICE
Indicates a hazardous situation not related to personal injury.
....................................................................................................................................................................................................................................
1-2
August 2011
Safety
....................................................................................................................................................................................................................................

Overview
All responsible technical personnel must read this chapter before servicing the system.
Always keep the most recent issue of this document close to the equipment.
In addition to the general safety instructions in this chapter, users must also observe the
specific safety instructions in the individual chapters.
The equipment complies with the current national and international safety requirements.
It is provided with a high degree of operational safety resulting from many years of
development experience and continuous stringent quality checks.
Potential sources of danger
The equipment is safe in normal operation. However, some potential sources of danger
cannot be completely eliminated. In particular, these may arise during the following
operations:
Opening of housings or equipment covers
Manipulation of any kind within the equipment, even if it has been disconnected from
the power supply
Disconnection of optical or electrical connections
Through possible contact with live pairs, laser light, hot surfaces, sharp edges, or
components sensitive to electrostatic discharge
Special safety instructions
Laser safety and handling components sensitive to electrostatic discharge (ESD) are
vitally important to the equipment. For special safety instructions concerning laser safety
and electrostatic discharge, refer to sections Laser safety (p. 1-4) and Electrostatic
discharge (p. 1-11).
General safety requirements
In order to keep the technically unavoidable residual risk to a minimum, it is imperative

to observe the following rules.
Transport, storage, and operation of the unit/system must be under the permissible
conditions only.
See accompanying documentation and information on the unit/system.
Installation, configuration, and disassembly must be performed only by expert
personnel referring to the respective documentation.
Due to the complexity of the unit/system, the personnel performing installation,
configuration, and disassembly require special training.
Expert and authorized users are required to operate the unit/system.
....................................................................................................................................................................................................................................
1-3
August 2011
Safety
....................................................................................................................................................................................................................................
Operate the unit/system only after having read and understood the chapter on safety
and the parts of the documentation relevant to operation. For complex systems,
additional training is recommended. Any obligatory training for operating and service
personnel must be carried out and documented.
Do not operate the unit/system unless it is in perfect working order.
Immediately report any faults or errors that might affect safety.
Operate the unit/system with the proper connections and under the environmental
conditions as described in the documentation.
Only qualified Alcatel-Lucent personnel or expert personnel authorized by
Alcatel-Lucent are permitted to perform conversions or changes to the system or parts
of the system (including the software).
All changes performed by other persons lead to a complete exemption from liability.
Do not use components or spare parts that are not recommended by the manufacturer
and those not listed in the procurement documents.
Only specially qualified personnel are permitted to remove or disable safety facilities,
clear faults and errors, and maintain the equipment.
Strictly observe the respective parts of the documentation, and consult the
documentation during the selection of measuring and test equipment.
Document and archive all work related to calibrations, special tests after repairs, and
regular safety checks.
Use non-system software at your own risk. The use/installation of non-system
software can adversely affect the normal functioning of the unit/system.
Laser safety
System compliance
Alcatel-Lucent 1830 PSS complies with the following laser safety regulations and
standards:
North America Region
Telcordia GR-1089-CORE, Issue 4 Electromagnetic Compatibility and Electrical

Safety - Generic Criteria for Network Telecommunications Equipment
Telecordia GR-63-CORE, Issue 3 NEBS Requirements: Physical Protection.
CSA Certified (US and Canadian) UL 60950-1, Second Edition / CSA C22.2 No.
60950-1-07, Second Edition, Information Technology Equipment Safety Part 1 :
Generic Requirements
21 CFR 1040.10, Food and Drugs, Radiological Health, Performance Standards for
Light Emitting Products
21 CFR 1040.11, Food and Drugs, Radiological Health, Specific Purpose Laser
Products
....................................................................................................................................................................................................................................
1-4
August 2011
Safety
Laser safety
....................................................................................................................................................................................................................................
FCC Code of Federal Regulations, Title 47 Telecommunications, Part 15 Radio

Frequency Devices, Class A
ICES-003, Issue 4 Industry Canada Spectrum Management and Telecommunications
Policy, Interference-Causing Equipment Standard, Digital Apparatus, Class A
European Market
Directive 2004/108/EC, Electromagnetic Compatibility (EMC)

Directive 2006/95/EC, Low Voltage Electrical Equipment
Directive 93/465/EEC, CE Marking Directive
IEC 60950-1:2005 (2nd Edition) / EN 60950-1:2006 Information Technology

Equipment Safety Part 1 : Generic Requirements
EN 60825-1: 2007 Safety of Laser Products Part 1: Equipment Classification,
Requirements, and Users Guide
EN 60825-2: 2007 Safety of Laser Products Part 2: Safety of Optical Fiber

Communication Systems
EN 300 386 Electromagnetic compatibility and Radio spectrum Matters (ERM);
Telecommunication network equipment; Electromagnetic Compatibility (EMC)
requirements.
EN 55022: "Information technology equipment - Radio disturbance characteristics Limits and methods of measurement". Class A
ETSI ES 201 468 Electromagnetic compatibility and Radio spectrum Matters (ERM);
Additional Electromagnetic Compatibility (EMC) requirements for
telecommunications equipment for enhanced availability of service in specific
applications
EN 300 019 2-1 Environmental Engineering (EE); Environmental Conditions And
Environmental Tests For Telecommunications Equipment; Part 2-1: Specification Of
Environmental Tests; Storage
EN 300 019 2-2: Equipment Engineering (EE); Environmental Conditions And
Environmental Tests For Telecommunications Equipment - Part 2-2: Specification Of
Environmental Tests; Transportation
EN 300 019 2-3: Equipment Engineering (EE) - Environmental Conditions And
Environmental Tests For Telecommunications Equipment - Part 2-3: Specification Of
Environmental Tests - Stationary Use At Weather Protected Locations
ETS 300 753: Equipment Engineering (EE) - Acoustic Noise Emitted By
Telecommunications Equipment
General laser information
Optical fiber telecommunication systems, their associated test sets, and similar operating
systems use semiconductor laser transmitters that emit infrared (IR) light at wavelengths
between approximately 800 nanometers (nm) and 1600 nm. The emitted light is above the
red end of the visible spectrum, which is normally not visible to the human eye. Although
....................................................................................................................................................................................................................................
1-5
August 2011
Safety
Laser safety
....................................................................................................................................................................................................................................
radiant energy at near-IR wavelengths is officially designated invisible, some people can
see the shorter wavelength energy even at power levels several orders of magnitude below
any that have been shown to cause injury to the eye.
Conventional lasers can produce an intense beam of monochromatic light.
Monochromatic light is a single wavelength output of pure color that may be visible or
invisible to the eye. A conventional laser produces a small-sized beam of light, and
because the beam size is small, the power density (also called irradiance) is very high.
Consequently, lasers and laser products are subject to federal and applicable state
regulations as well as international standards for their safe operation.
A conventional laser beam expands very little over distance, or is said to be very well
collimated. Thus, conventional laser irradiance remains relatively constant over distance.
However, lasers used in lightwave systems have a large beam divergence, typically 10 to
20 degrees. Here, irradiance obeys the inverse square law (doubling the distance reduces
the irradiance by a factor of four) and rapidly decreases over distance.
Lasers and eye damage
The optical energy emitted by laser and high-radiance LEDs in the 400 to 1400-nm range
may cause eye damage if absorbed by the retina. When a beam of light enters the eye, the
eye magnifies and focuses the energy on the retina magnifying the irradiance. The
irradiance of the energy that reaches the retina is approximately 105 (or 100,000 times
more than at the cornea) and, if sufficiently intense, may cause a retinal burn.
The damage mechanism at the wavelengths used in an optical fiber telecommunications is
thermal in origin; for example, damage caused by heating. Therefore, a specific amount
of energy is required for a definite time to heat an area of retinal tissue. Damage to the
retina occurs only when one looks at the light sufficiently long that the product of the
retinal irradiance and the viewing time exceeds the damage threshold. Optical energies
above 1400 nm cause corneal and skin burns, but these optical energies do not affect the
retina. The thresholds for injury at wavelengths greater than 1400 nm are significantly
higher than that for wavelengths in the retinal hazard region.
Classification of lasers
Manufacturers of lasers and laser products in the United States are regulated by the Food
and Drug Administration's Center for Devices and Radiological Health (FDA/CDRH)
under 21 CFR 1040. These regulations require manufacturers to certify each laser or laser
product as belonging to one of four major classes: I, II, lla, IlIa, lllb, or IV.
The International Electrotechnical Commission (IEC) is an international standards body
that writes laser safety standards under IEC-60825. Classification schemes are similar and
divided into Classes 1, 1M, 2, 2M, 3B, 3R, and 4. Lasers are classified according to the
accessible emission limits and their potential for causing injury.
....................................................................................................................................................................................................................................
1-6
August 2011
Safety
Laser safety
....................................................................................................................................................................................................................................
Optical fiber telecommunication systems are generally classified as Class I/1, because,
under normal operating conditions, all energized laser transmitting circuit packs are
terminated on optical fibers which enclose the laser energy with the fiber sheath forming
a protective housing. Also, a protective housing/access panel is typically installed in front
of the laser circuit pack shelves. The circuit packs themselves, however, may be
FDA/CDRH Class I, IIIb, or IV or IEC Class 1, 1M, 3B, 3R, or 4. State-of-the-art Raman
optical amplifiers have now extended into the Class IV/4 designations.
Laser safety precautions for optical fiber telecommunications systems
In its normal operating mode, an optical fiber telecommunication system is totally

enclosed and presents no risk of eye injury. It is a Class I/1 system under the FDA/CDRH
and IEC classifications.
The fiber optic cables that interconnect various components of an optical fiber
telecommunication system can disconnect or break and may expose people to lightwave
emission. Also, certain measures and maintenance procedures may expose the technician
to emission from the semiconductor laser during installation and servicing. Unlike more
familiar laser devices, such as solid-state and gas lasers, the emission pattern of a
semiconductor laser results in a highly divergent beam. In a divergent beam, the
irradiance (power density) decreases rapidly with distance. The greater the distance, the
less energy will enter the eye and the less potential risk for eye injury. If you inadvertently
view an unterminated fiber or damaged fiber with the unaided eye at distances greater
than 5 to 6 inches, normally, it will not cause eye injury provided that the power in the
fiber is less than a few milliwatts at the near IR wavelengths and a few tens of milliwatts
at the far IR wavelengths. However, damage may occur if you use an optical instrument
such as a microscope, magnifying glass, or eye loupe to stare at the energized fiber end.
Laser Radiation
CAUTION
Laser hazard
Use of controls, adjustments, and procedures other than those specified herein may result
in hazardous laser radiation exposure.
Use controls, adjustments, and procedures specified in this document to avoid hazardous
laser radiation exposure.
....................................................................................................................................................................................................................................
1-7
August 2011
Safety
Laser safety
....................................................................................................................................................................................................................................
Laser safety precautions for enclosed systems
Under normal operating conditions, optical fiber telecommunication systems are

completely enclosed. Observe the following laser safety precautions for enclosed
systems:
Because of the potential for eye damage, do not stare into optical connectors or
broken fibers.
Do not under any circumstances perform laser/fiber optic operations before

satisfactorily completing laser safety training.
Since viewing lightwave emission directly in excess of Class I/1 limits with an optical
instrument such as an eye loupe greatly increases the risk of eye damage,
observe/follow laser safety labels. Appropriate labels must appear in plain view, in
close proximity to the optical port on the protective housing/access panel of the
terminal equipment
Laser safety precautions for unenclosed systems
During service, maintenance, or restoration, an optical fiber telecommunication system is

considered unenclosed. Observe the following laser safety precautions for unenclosed
systems:
Only authorized, trained personnel shall be permitted to do service, maintenance, and

restoration. Avoid exposing the eye to emissions from unterminated, energized optical
connectors at close distances. Laser modules associated with the optical ports of laser
circuit packs are typically recessed, which limits the exposure distance. Optical port
shutters, automatic power reduction (APR), and automatic power shutdown (APSD)
are engineering controls that are also used to limit the emissions. However, do not
stare or look directly into the optical port with optical instruments or magnifying
lenses when removing or replacing laser circuit packs. (Normal eye wear or indirect
viewing instruments, such as a Find-R-Scopes, are not considered magnifying lenses
or optical instruments.)
Only authorized, trained personnel shall use the optical test equipment during
installation or servicing since this equipment contains semiconductor lasers. (Some
examples of optical test equipment are Optical Time Domain Reflectometers
[OTDRs] and Hand-Held Loss Test Sets.)
Do not, under any circumstance, scan a fiber with an optical test set without verifying
that all laser sources on the fiber are turned off.
Only authorized personnel are permitted in the immediate area of the optical fiber
telecommunication systems during installation and service.
For guidance on the safe use of optical fiber optic communication systems in the
workplace, consult ANSI Z136.2, American National Standard for Safe Use of Optical
Fiber Communication Systems Utilizing Laser Diodes and LED Sources in the United
States or outside the United States, IEC-60825, Part 2.
....................................................................................................................................................................................................................................
1-8
August 2011
Safety
Laser safety
....................................................................................................................................................................................................................................
Laser warning labels
The following figure shows the different types of laser warning labels:
Figure 1-1 Laser warning labels (1 of 2)
1
CLASS 1 LASER
PRODUCT
HAZARD
LEVEL
1M
DANGER
INVISIBLE LASER RADIATION
WHEN OPEN AND FIBER
DISCONNECTED
Avoid direct exposure to beam
Do not view beam directly with
optical instruments
CAUTION
CLASS 1M INVISIBLE
LASER RADIATION
WHEN OPEN
AND FIBER
DISCONNECTED.
Do not view directly
with optical
instruments.
ATTENTION
RAYONNEMENT
LASER DE CLASSE
1M INVISIBLE
LORSQUE
LAPPAREIL EST
OUVERT ET QUE
LA FIBRE EST
DCONNECTE.
Ne pas regarder
directement au moyen
dun instrument optique.
848950572
MA-DMX-416
....................................................................................................................................................................................................................................
1-9
August 2011
Safety
Laser safety
....................................................................................................................................................................................................................................
Figure 1-1 Laser warning labels (2 of 2)

1
FAULT
LIHTR
CLASS 1 LASER
PRODUCT
DANGER
INVISIBLE LASER RADIATION
WHEN OPEN AND FIBER
DISCONNECTED
Avoid direct exposure to beam
Do not view beam directly with
optical instruments
MA-metro-428
Legend
1. Laser symbol
2. Laser classification labels (This label may show only the laser class or both the laser
class and the maximum output power.)
3. Laser warning labels
....................................................................................................................................................................................................................................
1-10
August 2011
Safety
....................................................................................................................................................................................................................................
Overview
Electrostatic discharge (ESD) (for example, caused by touching with the hand) can
destroy semiconductor components. The correct operation of the complete system is then
no longer assured.
ESD warning
NOTICE
ESD hazard
ESD can destroy electronic components.
Always keep circuit packs in antistatic covers. Use the original packaging if possible. Use
a static ground wrist strap whenever handling circuit packs or working on the
Alcatel-Lucent 1830 PSS system to prevent ESD damage to sensitive components.
All semiconductor components are basically sensitive to ESD. The ESD can also affect
the components indirectly.
ESD considerations
This section describes the precautions required to prevent ESD damage.

Circuit pack handling precautions
Industry experience has shown that all integrated circuit packs can be damaged by static
electricity that builds up on work surfaces and personnel. The static charges are produced
by various charging effects of movement and contact with other objects. Dry air allows
greater static charges to accumulate. Higher potentials are measured in areas with low
relative humidity, but potentials high enough to cause damage can occur anywhere.
Observe the following precautions when handling circuit packs/units to prevent ESD
damage.
Assume all circuit packs contain solid-state electronic components that can be
damaged by ESD.
When handling circuit packs (for example storing, installing, and removing) or when
working on the backplane, always wear a grounded wrist strap or wear a heel strap
and stand on a grounded, static-dissipating floor mat.
Wear working garment made of 100% cotton to avoid ESD.
Handle all circuit packs by the faceplate or latch and by the top and bottom outermost
edges. Never touch the components, conductors, or connector pins.
....................................................................................................................................................................................................................................
1-11
August 2011
Safety
....................................................................................................................................................................................................................................
Store and ship circuit packs and components in their shipping packing. Circuit packs
and components must be packed and unpacked only at workplaces suitably protected
against build-up of charge.
Observe all warning labels on bags and cartons. Whenever possible, do not remove
circuit packs from antistatic packaging until ready to insert them into slots.
If possible, open all circuit packs at a static-safe work position, using properly
grounded wrist straps and static-dissipating table mats.
Always store and transport circuit packs in static-safe packaging. Shielding is not
required unless specified.
Keep all static-generating materials such as food wrappers, plastics, and Styrofoam
containers away from all circuit packs. When removing circuit packs from a shelf,
immediately place the circuit packs in static-safe packages.
Whenever possible, maintain relative humidity above 20 percent.
Important! Ensure that any connectors on the shelf interconnection panel that are not
cabled are fitted with a plastic dust cap to provide ESD protection.
Static control wrist straps
To reduce the possibility of ESD damage, the Alcatel-Lucent 1830 PSS shelf is equipped
with an ESD grounding jack to enable personnel to ground themselves using wrist straps
[Figure 1-2, Static control wrist strap (p. 1-12)], while handling circuit packs or
working on the shelf. Check the wrist straps periodically with a wrist strap tester to ensure
that they are working properly.
Figure 1-2 Static control wrist strap
To
Ground
Connection
NC-USM-110
Important! The grounding jack is located on the front of the shelf, on the lower-right
corner. Another grounding jack is also located on the rear panel.
....................................................................................................................................................................................................................................
1-12
August 2011
Safety
....................................................................................................................................................................................................................................
Barred-hand symbol
Circuit packs containing components that are especially sensitive to ESD are identified by
warning labels bearing the barred-hand symbol. The following figure shows the
barred-hand symbol.
Figure 1-3 ESD warning label (barred-hand symbol)
MA-metro-429

READ AND UNDERSTAND ALL INSTRUCTIONS.
The exclamation point within an equilateral triangle is intended
to alert the user to the presence of important operating and
maintenance (servicing) instructions in the literature
accompanying this product.
When installing, operating, or maintaining this equipment, always follow basic safety
precautions to reduce the risk of fire, electric shock, and injury to persons, including the
following:
1. Read and understand all instructions.
2. Follow all warnings and instructions marked on this product.
3. Operate this product only from the type of power sources that are indicated on the
marking label.
4. Connect this product only to the type of power sources recommended by
Alcatel-Lucent. For information on the powering instructions, consult the
Alcatel-Lucent 1830 Photonic Service Switch 36/32/16 (PSS-36/PSS-32/PSS-16)
Release 3.6.0 and 3.6.1 Installation and System Turn-Up Guide.
5. This equipment is suitable for mounting on a concrete or other noncombustible
surface only. For information on proper mounting instructions, consult the
....................................................................................................................................................................................................................................
1-13
August 2011
Safety
....................................................................................................................................................................................................................................
6. Install only equipment identified in the Alcatel-Lucent 1830 Photonic Service Switch
36/32/16 (PSS-36/PSS-32/PSS-16) Release 3.6.0 and 3.6.1 Installation and System
Turn-Up Guide. Use of other equipment may result in improper connection of
circuitry leading to fire or injury to persons.
7. Ensure that all metallic telecommunication interfaces (traffic ports) that leave the
building premises are connected to telecommunication devices that provide primary
and secondary protection, as applicable.
8. Do not use this product near water; for example, in a wet basement.
9. Do not place this product on an unstable cart, stand, or table. The product may fall
and cause serious damage to the product.
10. Use caution when installing or modifying telecommunications lines.
11. Never install telecommunications wiring during a lightning storm.
12. Never install telecommunications connections in wet locations.
13. Never touch uninsulated telecommunications wires or terminals unless the
telecommunications line has been disconnected at the network interface.
14. Never touch uninsulated wiring or terminals carrying direct current or ringing current,
and never leave this wiring exposed. Protect and tape uninsulated wiring and
terminals to avoid risk of fire, electric shock, and injury to service personnel.
15. Never push objects of any kind into this product through slots as they may touch
dangerous voltage points or short out parts that could result in a risk of fire or
electrical shock. Never spill liquids of any kind on the product.
16. To protect the unit from overheating, slots and openings in the unit are provided for
ventilation. Do not block or cover these openings. Do not place this product in a
built-in installation unless proper ventilation is provided.
17. To reduce the risk of an electrical shock, do not disassemble this product. Service
should be performed by trained personnel only. Opening or removing covers and/or
circuit boards may expose you to dangerous voltages or other risks. Incorrect
reassembly can cause electrical shock when the unit is subsequently used.
18. Some of the Alcatel-Lucent 1830 PSS family hardware modules contain FDA/CDRH
Class IIIb/IEC Class 1M single-mode laser products that are enclosed lightwave
transmission systems.
Under normal operating conditions, lightwave transmission systems are completely
enclosed; however, the following precautions must be observed because of the
potential for eye damage:
Do not stare directly into the optical connectors terminating the cables.
Ensure that technicians have satisfactorily completed an approved training course
before performing lightwave/lightguide operations.
Do not use optical instruments such as an eye loupe to view a fiber or
unterminated connector.
....................................................................................................................................................................................................................................
1-14
August 2011
Safety
....................................................................................................................................................................................................................................
More information about laser safety can be found in the Alcatel-Lucent 1830 Photonic
Service Switch 36/32/16 (PSS-36/PSS-32/PSS-16) Release 3.6.0 and 3.6.1 Installation
and System Turn-Up Guide.
19. For a unit intended to be powered from -48 V DC voltage sources, read and
understand the following:
Use only Safety Extra Low Voltage (SELV) -48 V DC sources.
Disconnect up to two power supply connections when removing power from the
system.
Provide a readily accessible disconnect device as part of the building installation.

Ensure that there is no exposed wire when the input power cables are connected to
the unit.
Include an independent frame ground drop to building ground. Refer to the
This electrical ground symbol is marked on the product, adjacent to the ground
(earth) area for the connection of the ground (earth) conductor.
This equipment is to be installed only in Restricted Access Areas on Business and
Customer Premises Applications in Accordance with Articles 110-16, 110-17, and
110-18 of the National Electrical Code, ANSI/NFPA No. 70. Other installations
exempt from the enforcement of the National Electrical Code may be engineered
according to the accepted practices of the local telecommunications utility.
20. For a unit intended to be powered from 100-120/200-240 V AC voltage sources, read
and understand the following:
Unplug this product from the wall outlet before cleaning. Do not use liquid
cleaners or aerosol cleaners. Use a damp cloth for cleaning.
Do not staple or otherwise attach the power supply cord to the building surfaces.
Do not overload wall outlets and extension cords as this can result in the risk of
fire or electrical shock.
Install the socket outlet near the equipment so that it is readily accessible.
This product is equipped with a three-wire grounding type plug, a plug having a
third (grounding) pin. This plug is intended to fit only into a grounding type
power outlet. This is a safety feature. If you are unable to insert the plug into the
outlet, contact your electrician to replace your obsolete outlet. Do not defeat the
safety purpose of the grounding type plug. Do not use a 3-to-2-prong adapter at
the receptacle. Use of this type adapter may result in risk of electrical shock
and/or damage to this product.
Do not allow anything to rest on the power cord. Do not locate this product where
the cord may be abused by persons walking on it.
....................................................................................................................................................................................................................................
1-15
August 2011
Safety
....................................................................................................................................................................................................................................
21. Unplug this product from the wall outlet, and refer servicing to qualified service
personnel under the following conditions:
When the power supply cord or plug is damaged or frayed
If liquid has been spilled into the product

If the product has been exposed to rain or water
If the product does not operate normally by following the operating instructions
(Adjust only those controls that are covered by the operating instructions because
improper adjustment of other controls may result in damage and will often require
extensive work by qualified technician to restore the product to normal operation.)
If the product has been dropped or the cabinet has been damaged
If the product exhibits a distinct change in performance
SAVE THESE INSTRUCTIONS.
....................................................................................................................................................................................................................................
1-16
August 2011
2
Overview
Purpose
This chapter provides information on security administration procedures for the 1830
PSS-36/PSS-32/PSS-16 system. The security functions determine NE access, command
execution, and administrative control for the 1830 PSS-36/PSS-32/PSS-16.
Contents
User accounts and privileges
2-2
Configuring user accounts
2-6
2-10
Login sessions
2-13
2-14
Log procedures
2-21
Authentication
2-22
RADIUS server procedures
2-27
SNMP procedures
2-29
...................................................................................................................................................................................................................................
2-1
August 2011
....................................................................................................................................................................................................................................

The purpose of security administration is to manage user accounts (logins, passwords,
authorization levels, external links) and to monitor system security so that only valid
users can perform permitted actions and receive authorized information from the system.
The NE provides the ability to create, modify, delete, and view user profiles and
associated security levels. Each level has distinct privileges for accessing and executing
the commands and performing administrative functions on the NE. The description of
each function or command is listed in the Alcatel-Lucent 1830 Photonic Service Switch
(PSS) Release 3.6.0 and 3.6.1 Command Line Interface Guide and/or Alcatel-Lucent 1830
Photonic Service Switch (PSS) Release 3.6.0 and 3.6.1 TL1 Commands and Messages
Guide including the user levels that are able to access and execute each specific command
(see System access control (p. 2-17)).
The system does not provide an unsecure user external port. To gain access to an NE
you need a user account with login and password. The user account name, privilege level
and password is created and defined by the Admin user, and is unique for each network
element in the network.
Important! The Alcatel-Lucent 1830 PSS is delivered with two default users as part
of the factory software load: one Admin user (with administration privilege) and one
Service user (with service privilege).
The login ID and passwords are:
For Admin user: admin/admin
For Service user: service/AlcaLu-1830!
Note: The administration of all security functions is only accessible to Admin and
Service users (i.e. the system will only allow access to these security functions to
users with appropriate security administration privileges). The Service user is not
capable of creating/deleting/modifying user profiles. The NE does not allow deletion
of the default users.
....................................................................................................................................................................................................................................
2-2
August 2011
....................................................................................................................................................................................................................................
The user levels, the privileges assigned to each level, and their intended use are
summarized in Table 2-1, User privilege levels (p. 2-3).
Table 2-1
Level
Privileges and use
Service
This is the highest level, and is meant for Alcatel-Lucent

technicians. This user has all the Admin privilege (except the
ability to create/delete/modify user profiles), plus the ability to
utilize the debugging and software development tools. The
following applies:
Admin
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
The Admin user is the administrator for the NE. The Admin has all
the Provisioner privileges and can also do the following:
add users to the NE
delete users from the NE, except Service user
edit the security and privilege information of any user, except

Service user
retrieve security information about users (not password)
change the password of other users, including other Admin

users, without entering the old password (cannot change
password of Service user)
logoff a particular user (including a user with administration

privileges and users who are logged with DEBUG, WebUI and
CLI sessions)
obtain user info about the users currently logged on to the NE

(including users who are logged with DEBUG, WebUI and
CLI sessions)
inhibit and allow all users, including Service user
set system-wide user security attributes
retrieve security information about authenticated (logged on)

and unauthenticated (not logged on) sessions
execute software download and database backup and restore

commands
....................................................................................................................................................................................................................................
2-3
August 2011
....................................................................................................................................................................................................................................
Table 2-1
(continued)
Level
Privileges and use
Provisioner
The WebUI restricts access for a user with Provisioner privilege

level as follows:
A Provisioner user cannot access the following Administrative

functions: User Panel replacement, Security (with exceptions
below), SNMP, Syslog, and user activity logging.
For the following administrative functions, the Provisioner user

can view the current values, but cannot edit them:
Date/Time and Timezone
System-wide security settings
NTP settings
Database backup/restore
Software upgrade including FTP server settings
The users own user profile
List of user sessions
GMRE settings
Access Control Lists
Log file transfer
Technology Types
For the following administrative functions, the Provisioner user

can view and edit:
IP routes
OSPF areas
Change his own password
User Preferences
A Provisioner user cannot perform a system reboot.
A Provisioner user cannot perform a card-level cold reboot.
A Provisioner user cannot modify OPSA A and B port

switching attributes.
A Provisioner user cannot view the Security Log.
A Provisioner user cannot modify LD/OSCT SIG and LINE

port attributes
A Provisioner user cannot modify Power Management port

attributes
A Provisioner user cannot modify Dynamic Tilt Adjustment

attributes
A Provisioner user cannot view or modify Optical Intrusion

Detection parameters
....................................................................................................................................................................................................................................
2-4
August 2011
....................................................................................................................................................................................................................................
Table 2-1
(continued)
Level
Privileges and use
Provisioner (continued)
A Provisioner user cannot modify Per-Channel Target Power

Offset attributes
A Provisioner user cannot modify Target Power Offset

attributes
Observer
The WebUI restricts access for a user with Observer privilege

level. In addition to the restrictions defined for the Provisioner
user, the Observer user is restricted as follows:
An Observer user cannot initialize the database during NE

configuration.
An Observer user cannot access the functions under the

Test/Analysis buttons. This includes: test LED and loopback.
An Observer user cannot access the alarm configuration

functions under the Fault button.
An Observer user cannot select Alarm Cutoff on the alarm

toolbar.
For Connections:
An Observer user can view all cross-connects and details, but

cannot create, modify or delete cross-connects.
An Observer user can view all EVPL connections, but cannot

create or delete connections.
An Observer user can view the Physical Topology, but cannot

create or delete a connection.
An Observer can view the Logical Topology with no

restrictions.
The Observer user cannot create, modify or delete any

equipment-related items or perform any action on the NE that
will change its status.
For the following administrative functions, the Observer user can

view but cannot edit:
IP routes
OSPF areas
For the following administrative functions, the Observer user

cannot view or edit:
Database backup/restore
....................................................................................................................................................................................................................................
2-5
August 2011
....................................................................................................................................................................................................................................

Introduction
Login security controls access to the NE(s) by individual users. Client Authentication for
logging in and auditing on each NE requires a user ID (UID) and a complex password.
Security administration enables the system to deny a user access to the NE. The NE
authenticates the user ID against the NE's local security database. Based on this, the NE
either accepts or denies login access to the NE. Access may be denied during one of the
following points in time:
When the user first attempts to log in and the login attempt is denied.
During an active session and the user is disconnected by the NE.
After the user logs into an NE with a valid user ID and Password, user functions can be
performed based on the assigned User Access Privilege (UAP).
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), _ (underscore) !

(exclamation mark), @ (at sign), $ (dollar sign), (double quotation mark), &
(ampersand), (apostrophe), ( (left parenthesis), ) (right parenthesis), * (asterisk), and
. (period).
Note: , (comma) and : (colon) are not valid special characters.
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.
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.
....................................................................................................................................................................................................................................
2-6
August 2011
....................................................................................................................................................................................................................................
Password identifier (PID)
A PID is a case sensitive string of 8 to 32 upper-case letters [A-Z], lower-case letters

[a-z], numbers, and 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), _ (underscore) !
(exclamation mark), @ (at sign), $ (dollar sign), (double quotation mark), &
(ampersand), (apostrophe), ( (left parenthesis), ) (right parenthesis), * (asterisk), and .
(period). The first character of the PID can be any alphabetic, numeric, or valid special
character.
Note: , (comma) and : (colon) are not valid special characters.
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 continue to be used before a new password becomes
mandatory; the number of times that the existing password can continue 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-7
August 2011
....................................................................................................................................................................................................................................
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.
Adding a User
A user with appropriate security level privileges (Admin user) can add new users to the
User Security Database and to specify for each user his/her User Access Privilege (UAP).
The UAP specifies the set of commands a user can execute based on the access privilege
of the user and of the command.
Note: A maximum of only 1 Service user is allowed in the NE. Multiple users of the
other user levels are allowed.
The NE provides the ability to specify an initial password pertaining to the new user. The
user is prompted to change the password when one of the following conditions occurs:
when that user establishes a session for the first time after the initial password is
assigned
when that user establishes a session for the first time after a user password has been
reset by an administrative action.
The NE denies the session if the user does not comply.

Deleting a user
A user with appropriate security level privileges can delete existing user profiles from the
User Security Database. If the specified user is currently logged on, then the user is also
logged off. Users with security administration privileges can delete any existing user
profile except default users' profiles.
Note: A user with administration or service privileges cannot delete his/her own user
profile. The Admin user cannot delete the Service user, and the Service user cannot
delete himself.
....................................................................................................................................................................................................................................
2-8
August 2011
....................................................................................................................................................................................................................................
Retrieving and editing user privileges
The ability to edit an existing user profile entry (created when entering a user) is provided
to users with appropriate security level privileges. The following conditions apply:
Only users with appropriate administration privileges can change a user profile
database entry for another user.
Only users with administrator privileges can edit the User Security Level User
attributes that exist for each user's profile. The security level user attributes are: user
privilege level, link timeout, user provided name, and user-id status. It is not possible
to modify the UID or user security level of factory default users.
Any change to the privilege(s) granted to a user do not apply to the user if the user is
currently logged in. Any such change will take effect after the next login.
A user with security administration privileges can retrieve any or all user profile
entries.
Only those parameter values that are actually applied for the specified UID are
reported. This means that those system-wide parameters that have been modified, but
still not applied to the specified UID, are reported with their previous values.
Enabling/disabling a user
A user with appropriate security level privileges can disable existing user profiles in the
User Security Database. If the specified user is logged on, then the user is also logged off.
A user cannot disable himself/herself.
A user with appropriate security level privileges can enable existing and previously
disabled user profiles in the User Security Database for a specified user(s).
Note: The Admin user can disable and enable all users including the Service user.
....................................................................................................................................................................................................................................
2-9
August 2011
....................................................................................................................................................................................................................................

Before you begin
The following procedures are available via the WebUI after the user initially connects to
the NE and logs into the system (see Using the WebUI (p. 3-18)).
View or modify user details
Note: Appropriate privilege level is required to configure user accounts.

...................................................................................................................................................................................................
In the WebUI, select Administration > Security > Users.

...................................................................................................................................................................................................
Select the desired user and click Details.

Result: User details are displayed. You can change privilege level or password, or
enable or disable the account.
...................................................................................................................................................................................................
Modify available fields (see Configuring user accounts (p. 2-6)) and click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
Create a user
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Create.
Result: Create User screen is displayed.
...................................................................................................................................................................................................
Enter appropriate information (see Configuring user accounts (p. 2-6)) and click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
Delete a user
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2-10
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the desired user and click Delete.

E...................................................................................................................................................................................................
N D O F S T E P S
Change password
...................................................................................................................................................................................................
In the WebUI, select Administration > Security > Change Password.

...................................................................................................................................................................................................
Enter the old password and the new password, and confirm the new password. Then click
Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
View / terminate sessions

...................................................................................................................................................................................................
In the WebUI, select Administration > Security > Sessions.

Result: All active sessions are displayed.
...................................................................................................................................................................................................
To terminate a session, select the desired session and click Terminate.

E...................................................................................................................................................................................................
N D O F S T E P S
View SNMP v3 users

...................................................................................................................................................................................................
In the WebUI, select Administration > Security > SNMP v3 Users.

Result: All current SNMP v3 users are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Create SNMP v3 user

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2-11
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To create an SNMP v3 user, click Create.

Result: The Create SNMP v3 User window is displayed.
...................................................................................................................................................................................................
Enter User ID, Password, and Access Privilege information. and click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
Modify SNMP v3 user

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

...................................................................................................................................................................................................
To modify an SNMP v3 user, select the user and click Modify.

Result: The Modify SNMP v3 User window is displayed.
...................................................................................................................................................................................................
Enter the desired parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
View / modify system security attributes

...................................................................................................................................................................................................
In the WebUI, select Administration > Security > System.

Result: The System Security Administration window with current settings is
displayed.
...................................................................................................................................................................................................
To modify existing value(s), enter desired value(s) and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-12
August 2011
Login sessions
....................................................................................................................................................................................................................................
Login sessions
Overview
There is no limit to the number of simultaneous active sessions per user ID. One user ID
can log into the NE multiple times (via WebUI, TL1, CLI, and SNMP), the maximum of
which is restricted by the number of sessions supported by the NE. The NE notifies the
security administrator when a user logs into the NE indicating the UID and the
established User Session Number.
The ability to authenticate a session (i.e., activate a user session) is established with the
NE by logging in an existing user through a UID and a PID. The NE will deny the
activation of a user session if authentication for the user cannot be established (e.g. the
specified password does not match the user's password on the NE, the user profile does
not exist on the NE, etc.).
The NE allows a user to cancel a current session which was previously authenticated by a
login request by providing a logoff function for the current session.
The following applies to canceling a user session:
Only users with appropriate administration privileges are able to logoff other users.
Otherwise users can only logoff themselves.
Users with administration privileges and also the Service user can logoff other users
with administration privileges.
A command request to cancel a session will terminate a single active user session on
the addressed NE. In addition any supporting connection which after the termination
of this session is no longer supporting other sessions or connections, is also
terminated.
Session timeout
The NE supports auto log out and auto disconnect of user sessions based upon user link
inactivity (i.e. an idle user). Inactivity is defined as lack of user input. The inactivity
interval (period which triggers log out) is provisionable on a system basis. The longest
such interval allowed for an idle user is 999 minutes, with a minimum of 1 minute and a
default of 60 minutes. The system allows the ability to disable the User Session Link
Timer attribute, on a system basis, by assigning the zero value. A value of 0 implies no
idle timeout, (i.e. the user can remain idle forever).
When the session timer expires, the NE logs out and disconnects a user's session to the
NE. The session timer is reset/restarted by successful user login and user session link
communication input activity after the login occurs.
Each properly logged-in session will either be logged out by the user or by system
inactivity or by connection interruption. When a session is terminated (e.g., normal
logoff, power failure, a break in the physical or logical connection), the NE ensures that
....................................................................................................................................................................................................................................
2-13
August 2011
Login sessions
....................................................................................................................................................................................................................................
the port drops immediately and terminates the user processes running at the time of
logoff. When the next user attempts to log on to that physical or logical port, the user is
required to go through the entire login procedure including identification and
authentication.
The admin user may configure unique per user session timeout, based on the UID profile.
If provisioned, the timeout value may take on any value up to the system maximum. If
provisioned, the user-defined session timeout takes precedence over the system-wide
session timeout value provisioned.

Encrypted and normal mode
The system supports the ability to set the NE to function in an encrypted or normal mode.
Encrypted or normal mode should be set during initial commissioning. There is no default
mode. Only the administrative user can invoke the security mode on the NE. Changing
the mode from encrypted to normal, or vice versa, causes a warm reboot of the active
Main EC. All current user sessions will be logged off as a result.
The NE does not allow the encrypted mode setting if there is no SSH key initialized on
the system. Encrypted mode can only be turned on after the NE has already generated an
SSH key. The NE applies the following guidelines when setting the mode to either
encrypted or normal. These settings apply to the OAMP port only.
In encrypted mode:
SSH is enabled
telnet is disabled to ports 23, 3082, 3083
telnet is enabled to port 22 to support SSH

SNMP ports (161, 162) are allowed to be enabled
port 69 (tftp) remains open for the internal transfers from the main EC to other circuit
packs on the local NE
NTP port (123) is allowed to be enabled
SNMPv1, SNMPv2c, SNMPv3 (without authentication and privacy) requests to the

NE are disabled
SNMPv3 (with authentication and privacy) requests are allowed by the NE
In normal mode:
SSH is enabled (SSH can be used in both modes)

telnet is enabled to all ports TL1 (3082, 3083) and CLI (22, 23) ports
SNMP ports (161, 163) are allowed to be enabled

NTP port (123) is allowed to be enabled
....................................................................................................................................................................................................................................
2-14
August 2011
....................................................................................................................................................................................................................................
HTTP (Web interface available) is enabled for remote management

The port 69 (tftp) remains open for the internal transfers from the main EC to other
circuit packs on the local NE
SNMPv1, SNMPv2c requests are allowed by the NE

SNMPv3 (without authentication and privacy) requests are not allowed by the NE
SNMPv3 (with authentication and privacy) requests are allowed by the NE
CLI over the craft serial port is not encrypted
The NE supports the enabling and disabling of the following external ports: OAMP, VoIP,
E1-LAN, E2-LAN, ES1 and ES2 for extension shelves. Only an administrative user has
the ability to enable/disable these interfaces. The serial/console port cannot be disabled.
Note: The two external LAN ports, E1 and E2, connect to externally managed
devices, like RAMAN power booster amplifiers. One User Panel is supported on the
Master Shelf of an NE to provide a maximum of 2 LAN ports for external RAMAN
or Booster devices per NE.
TFTP, FTP, and SFTP
TFTP, FTP, and SFTP file transfer protocols are supported for both encrypted mode and
normal mode.
The following applies:
for PM file transfer TFTP must be used

for software download FTP or SFTP can be used
for database file transfer TFTP or SFTP can be used
for log file transfer FTP or SFTP can be used
for SSL certificate transfer FTP or SFTP can be used
SFTP (secure FTP) is a program that uses SSH to transfer files. Unlike standard FTP, it
encrypts both commands and data, preventing passwords and sensitive information from
being transmitted in the clear over the network. It is functionally similar to FTP, but
because it uses a different protocol, standard FTP client can't be used to talk to an SFTP
server, nor an FTP server can be connected with a client that supports only SFTP.
FTP and SFTP passwords are stored in the database using AES encryption.
No user interface displays the password for the FTP and SFTP server.
SFTP or TFTP are used regardless of whether the NE is in encrypted or in normal
mode.
Note: Only one tftp transfer can be initiated at a time.
....................................................................................................................................................................................................................................
2-15
August 2011
....................................................................................................................................................................................................................................
Secure Shell (SSH)
Secure Shell (SSH) is a network protocol that allows data to be exchanged using a secure
channel between two network devices. SSH is designed as a replacement for telnet and
other unsecure remote shells which send information (notably passwords) in plaintext,
leaving them open to interception. The encryption used by SSH provides confidentiality
and integrity of data over an unsecure network, such as Internet. SSH allows a trusted
path of communication between two ends (e.g., NE and EMS) using encryption of the
data stream.
The 1830 NE supports SSHv2. This applies to 1830 PSS-36/PSS-32/PSS-16 and the
1830 PSS-1 (Edge Device).
The NE supports the generation of the SSH crypto Key. This crypto key needs to be
generated before the NE is set to encrypted mode. The NE allows the generation of
the crypto key when the NE mode is normal or encrypted.
SSH Keys can be zeroized (regenerated) in encrypted mode.
The NE supports AES encryption. SSH key must be encrypted with AES before
storing in the disk.
Note: Security mode can only be changed to encypted when:
SSH key exists
Security event log
For security purposes, the system generates a security log to provide an audit trail record
that supports after-the-fact investigation of specific activities (e.g., logins, modification of
critical system resources). The security log provides a means for the Security
Administrator to investigate, audit, detect, and analyze security events in order that proper
remedial actions can be taken. Security logs are protected from unauthorized access and
no modification by any user or process, even debug tools, is allowed.
The system provides the ability to a user with sufficient security level privileges to
retrieve security event log reports that were generated by the system for a given UserID
and between a specified From Date and Time and To Date and Time.
The following applies to the security log:
The security log has a circular (or equivalent) recording mechanism (i.e., oldest
record overwritten by newest), and an appropriate administrator has the capability to
retrieve, print, copy, and upload the security log for long-term storage.
When the security log has reached 90% of its maximum size, the NE sends an
appropriate event to the security administrator.
The security event log file is protected from tampering by any user defined in the user
security database and cannot be deleted by any user defined in the user security
database.
....................................................................................................................................................................................................................................
2-16
August 2011
....................................................................................................................................................................................................................................
The security event log file is stored in non-volatile memory and survives system
restarts/resets.
The security event log file does not survive software generic upgrades and power
reset.
Security log contents
Each NE is able to log the following classes of information in the security log:
any action that changes the security attributes and services

any action that changes access controls
any action that changes configuration parameters of the device
each login attempt and its result
each logout or session termination (whether remote or console, whether requested or
due to inactivity timeout)
A security log entry contains the following information:
the identification, address and security level of the user that initiated the action that is
being logged
the actual attempted action that is being logged (the echo of the command/response
message)
an indication of the success or failure of the activity (command completion code)
the date and the time the action (i.e. the command or the message) occurred
Note: The security event log file does not record actual or attempted passwords that
are entered in as passwords.
User activity log
Alcatel-Lucent 1830 PSS supports logging of user activities. Activities are collected in a
user activity log (UAL) in a user-readable format. All user actions via the WebUI are
logged and stored in this UAL along with the time and date of the action, the source IP
address and or user name of the operator, and the action itself. One entry is captured for
each user action. The purpose of this log is to provide non-repudiation.
The administrator can also transfer the UAL log to a remote file server (RFS). The RFS
can be the management system itself, or some other server - the choice is up to the
operator. This transfer mechanism can be performed using FTP or SFTP.
System access control
System access control prevents an otherwise authenticated (valid) user from unauthorized
access. Not all system resources are available to every user, and restricting resource
availability is extremely important to securing a safe and trusted network. System access
control allows only authorized users access to the NE. Access control level is associated
with each user and is maintained through the User Security Level attribute.
....................................................................................................................................................................................................................................
2-17
August 2011
....................................................................................................................................................................................................................................
To execute any command, a user needs a User Security Level (User Access Privilege)
including the Command Security Level (Command Access Privilege) assigned to the
command being executed. If the user is denied the privilege of executing a command due
to an insufficient User Security Level, the system indicates to the user that the command
request is invalid due to insufficient privileges.
All physical ports of the NE exercise system access control. This includes direct access
serial and LAN ports (CIT, external OAMP network access, etc.) and access via an
Embedded Communications Channel (ECC) as in the case of GCC between the 1830-PSS
and the 1830-PSS1 (Edge Device).
Any failed login attempt immediately reports to the user that the login process has failed
or is invalid. Information such as invalid user ID or invalid password is not reported.
The NE performs the entire user authentication procedure even if the UID that is entered
is not valid. After a failed login attempt, the system delays for 2 seconds prior to
presenting the next login prompt. This applies to human interaction interfaces (e.g. CLI,
TL1, WebUI).
After the maximum number of consecutive invalid login attempts for a session has been
reached, the system records in the security log the IP address of the source along with the
UID and an intrusion transient condition is reported.
Access control lists (ACL)
The system supports access control lists (ACL) functions.

Filters
The WebUI supports viewing a list of all filters and their associated patterns. Each filter
may be associated with up to 500 patterns. The WebUI also supports creating a new filter.
Up to 100 filters may be defined on the system
The WebUI supports adding a pattern to an existing Filter ID. When adding a pattern, the
WebUI displays a picklist of existing patterns that are not already associated with this
filter to choose from. The user must specify a Pattern Index with each selected pattern. (If
Pattern Index = 0, the WebUI does not display the value for Pattern Index.) The WebUI
also supports deleting a pattern from an existing Filter ID. A filter can only be deleted
when all patterns have been removed for this filter.
Note: If more than one pattern is associated with a Filter ID, then the WebUI will not
display the entry for this filter. (This entry is created when the Filter is created, but has
no associated patterns.)
Patterns
The WebUI supports viewing a list of all patterns used for IP access control. The WebUI
also supports creating, modifying, deleting, and viewing of patterns. A pattern can only be
deleted if it is not associated wth a filter.
....................................................................................................................................................................................................................................
2-18
August 2011
....................................................................................................................................................................................................................................
Ports
The WebUI supports viewing a list of all port to ACL filter associations.
The WebUI allows a user to create, modify, and view an association between an ACL
filter and a specified port and direction. When creating or modifying an association, the
WebUI displays a picklist of existing filters to choose from. An association between a
filter and port/direction can also be deleted.
Note: Up to 2 filters can be associated with each port, one in the Receive direction
and one in the Transmit direction. If a filter/port association already exists in a
direction, the WebUI will not allow the creation of another association to this port in
the same direction.
The following ports support ACL filtering.
Table 2-2
Ports that support ACL filtering

Card
Port
Signal Rate
11DPE12
L{1-2}
OTU2
11DPE12E
L{1-2}
OTU2
11DPM12
L{1-2}
OTU2
11DPM12
C{1-12}
OTU1
11QPA4
L{1-4}
OTU2
11QPA4
C{1-4}
OTU2
11STAR1
L1
OTU2
11STAR1
C1
OTU2
11STMM10
C{1-10}
OTU1
4DPA4
L{1-2}
OTU1
A2325A, AHPHG, AHPLG,

ALPHG, AM2017B,
AM2325B
OSC
ALPFGT, AM2125A,
AM2318A, OSCT
OSCSFP
EC (PSS-4)
OAMP
FLC
OAMP
MT0C
E1, E2, VOIP
USRPNL
E1, E2, OAMP, VOIP
....................................................................................................................................................................................................................................
2-19
August 2011
....................................................................................................................................................................................................................................
Optical intrusion detection
The optical intrusion detection feature gives the user the ability to have an optical
intrusion alarm raised upon detection of an outside plant fiber loss. A span loss could be
due to a hacker stripping away the fiber cladding and bending the fiber to cause light
leakage.
The system allows the user the ability to set the threshold values and retrieve baseline
values and threshold values for each optical line. Provisioning of optical intrusion
detection settings is supported on the following cards: A2325A, AHPHG, AHPLG,
ALPFGT, ALPHG, AM2017B, AM2125A, AM2125B, AM2325B, and OSCT.
The WebUI allows the user to set the Optical Intrusion Loss Threshold value. The
system will raise a MAJ alarm Optical Intrusion Detected against the optical line (OTS)
if the loss detected is equal to or greater than the specified threshold limit during a given
interval. The system also allows a user to clear an optical intrusion detected alarm.
The WebUI supports modifying and viewing of the following optical intrusion detection
attributes
Monitoring Enabled
Span Loss (dB)
Baseline Span Loss (dB)

Loss Theshold (dB)
Polling Period (seconds).
....................................................................................................................................................................................................................................
2-20
August 2011
Log procedures
....................................................................................................................................................................................................................................
Log procedures
View security log
...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > Security.

Result: The Security Log is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
View all logs

...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > All Logs.

Result: The All Logs window is displayed.
Note: All Logs includes not reported alarms.

E...................................................................................................................................................................................................
N D O F S T E P S
Save a retrieved log to a file

...................................................................................................................................................................................................
When the log is retrieved (see previous procedures), click the Export to Excel symbol.
Note: To use the Export to Excel feature, Internet Explorer must be configured as
follows:
1. In the IE tools menu select Internet Options -> Connections - > LAN Settings ->
Advanced (under Proxy server options)-> Exceptions (add IP address of NE to
Exceptions)
2. Close all IE instances (windows) and re-establish the WebUI connection to the
NE.
Note: The user should also ensure the following in the Internet Browser: Under
Internet Explorer ->Tools ->Internet Options -> Security tab select the Customer
Level button; Scroll down to the ActiveX controls and plug-ins and set Initialize and
Script ActiveX controls not marked as safe for scripting to either Enable or Prompt.
Click OK, and when prompted Are you sure? click Yes. Click OK to close out the
Internet Properties window. When the Excel button is pressed from the WebUI, if
Prompt was selected in the ActiveX controls, a popup for An ActiveX control on this
page might be unsafe to interact with other parts of the page. Do you want to allow
this interaction? will appear. Click Yes and Excel will launch, opening a file with the
....................................................................................................................................................................................................................................
2-21
August 2011
Log procedures
....................................................................................................................................................................................................................................
retrieved log info.

E...................................................................................................................................................................................................
N D O F S T E P S
Authentication
Overview
Authentication is the act of verifying a claimed identity, providing a basis for setting up
private communications with full data integrity and logging management activity. The
system supports the following different methods of authentication.
RADIUS authentication
Local NE Authentication
SNMP
RADIUS authentication
RADIUS allows the user to be authenticated and authorized at the same time. The
RADIUS server is provisioned with one or more user profile or profiles. Based on the
user profile and user class definitions, the RADIUS server not only allows the user to
have access to the NE, but also grants the user the user's privilege level. The RADIUS
client works with Steel-Belted RADIUS, WinRADIUS, and FreeRadius servers. The NE
supports provisioning of up to 2 RADIUS Servers. The administrative privilege user can
add/delete the specific RADIUS server.
The administrative privilege user can Enable/Disable the RADIUS servers without
deleting their configuration.
When two servers are configured and enabled, the NE queries the second RADIUS
server (RAD2) only if the first server (RAD1) does not respond after the appropriate
timeout and retries.
Web users are authenticated from the local stored database regardless of whether
RADIUS is enabled.
SNMP users are not authenticated by RADIUS.
RADIUS functionality can be used regardless of whether the NE is in encrypted or
normal mode.
A login by the Service user is never authenticated using RADIUS for any user
interfaces (CLI, TL1, WebUI). The authentication for the Service user is always local.
....................................................................................................................................................................................................................................
2-22
August 2011
Authentication
....................................................................................................................................................................................................................................
RADIUS attributes
The NE supports configuring the following general RADIUS attributes:
Timeout: This is the timeout (in seconds) for the NE to wait for a response from the
RADIUS server. A failure is declared after the timeout is elapsed. The supported value
range for timeout is 1 to 1000. The default value is 5.
Retries: This is the number of attempts that the NE will try to contact the specified
RADIUS server that has failed to respond during the previous request(s). If there is no
response from the server after the specified tries, then the NE will try to contact the
second RADIUS server if one is provisioned. The supported value range for retries is
1 to 100. The default value is 3.
The NE supports the following RADIUS server attributes. The RADIUS attributes can be
configured, edited, deleted, and retrieved by a user with appropriate administrative
privilege. The "sharedSecret" parameter cannot be retrieved.
ServerNum: This is the AID for the RADIUS server. The acceptable values are RAD1
and RAD2.
IPAddr: This is the IP address of the specified RADIUS server.
Port: This is the authentication port of the RADIUS server. The valid value is from 1
to 65000. The default port value is 1812.
sharedSecret: This is the shared secret key between the NE and the target RADIUS
server. This key is an ascii string between 5 to 32 characters.
Status: This is RADIUS server status. The valid values are the following
Enabled - The RADIUS server is online. This is the default value.

Disabled - The RADIUS server is offline.
The NE supports configuring the following authentication ordering behavior options that
can be configured and retrieved by a user with appropriate administrative privilege.
LOCAL: Authentication is based on the local NE's security database. This is the
default.
RADIUS: Authentication is based on the RADIUS server's database.
RADIUS-THEN-LOCAL: The authentication is attempted first using the RADIUS
server's database. If the RADIUS server is not reachable then authentication is based
on local NE's security database.
Note: If the RADIUS server is reachable and the user profile does not exist in
RADIUS server's database, then the authentication fails and the user is denied access.
Local NE authentication
Local NE Authentication is accomplished via the UID and PID pair created and stored on
the local NE.
....................................................................................................................................................................................................................................
2-23
August 2011
Authentication
....................................................................................................................................................................................................................................
Note: The access to the database (for authentication) of the NE where user profiles
are stored, is allowed only on a local connection. This is for the Service user to access
locally via connection to RS232 or local CIT port.
SNMP authentication
The local NE can authenticate and authorize users based on SNMP. SNMP provides for
both security versions and security levels. A security version is an authentication strategy
that is set up for a user and the group in which the user resides. A security level is the
permitted level of security within a security version. A combination of a security version
and a security level will determine which security mechanism is employed when handling
an SNMP packet. Three security versions are available: SNMPv1, SNMPv2c, and
SNMPv3.
The following applies to SNMP:
The NE supports separate DB records for SNMPv3 users. SNMPv3 users are different
from the CLI/TL1/WebUI users. SNMPv3 users can be provisioned via 1354
RM-PhM or WebUI.
The system supports creation of a default SNMP user at initial startup with a known
password. This known password permits 1354 RM-PhM to perform auto-discovery of
NEs. The default SNMP user cannot be deleted. It can only be disabled.
The NE supports changing SNMPv3 users' authentication (auth) and privacy (priv)
passwords.
The system supports enabling and disabling SNMP users.
The NE supports sending Authentication Failure traps and supports enabling and
disabling the sending of Authentication Failure Traps.
The system allows cloning a new SNMP user from an existing user.
Even if RADIUS authentication is enabled on the system, login access to the NE via
SNMP is always based on the UID and PID pair resident on the NE.
Note: Following are two scenarios when the user must update SNMPv3 passwords:
1. Upgrading from a previous release.
After the upgrade, the authentication (auth) and privacy (priv) passwords for
SNMPv3 default user (v3DefaultUser) must be updated.
2. Following a change to the loopback IP address (including the initial loopback IP
address provisioning from its default value).
After the warm restart, the authentication (auth) and privacy (priv) passwords for
all SNMPv3 users, including the ones for SNMPv3 default user (v3DefaultUser).
must be updated.
Note: If loopback IP address change is followed immediately with clearing
database (without also clearing IP addresses), there is no need to update SNMPv3
passwords.
....................................................................................................................................................................................................................................
2-24
August 2011
Authentication
....................................................................................................................................................................................................................................
SNMP trap destinations
The system supports editing and retrieval of SNMP trap destinations. Trap destinations
are SNMP managers provisioned to listen to traps coming from the NE. These SNMP
managers may or may not also be actively managing the NE.
The following SNMP trap server attributes are supported:
ID - this is the ID of the SNMP trap server. The system supports up to 10 remote trap
servers. This value is required to discern which trap server the user is addressing.
Possible values are 1 thru 10.
Destination IP - this is the IP address of the SNMP trap server. Specifies the IP
address of the server that serves as the trap destination.
String - this is the community string sent to the SNMP trap server. It is an ascii string
from 1 to 32 characters.
Port - this is the (IP address) port of the SNMP trap server. Specifies the IP address
port of the server that serves as the trap destination.
Timeout - Specifies the time (round trip), in hundreths of a second, after which the
connection times out if no reply is received. Following a timeout, a retry is attempted,
up to the number of retries specified by the retry variable.
Retry Count - Specifies an integer value for the number of times the network element
will attempt to retry the connection in the event of a timeout.
SNMP version - the SNMP version to use when formatting the trap. Valid versions are
v1, v2c, and v3.
NMS Station Group ID - Specifies an integer value that uniquely identifies the NMS
workstation serving as the trap destination. (Use 0 for all third party SNMP trap
servers).
Note: Traps are sent in SNMPv2 or SNMPv3 format, depending on the security level
of the NE. If the NE is encrypted, then all traps are encrypted, so the traps will be in
v3 format. All SNMPv3 traps are sent with the SNMPv3 default user. In normal
mode, the version can be v2 or v3.
SNMP community strings
The system supports creation, editing, deletion, and retrieval of SNMP community
strings. Community strings are necessary for authentication (e.g. if the manager comes
into the NE via SNMPv2). Provisioning of these tasks is accomplished via CLI, WebUI,
and SNMP.
Note: If the NE is in encrypted mode, the user can still configure these community
strings, but the remote SNMP manager will connect via SNMPv3.
....................................................................................................................................................................................................................................
2-25
August 2011
Authentication
....................................................................................................................................................................................................................................
The following SNMP community attributes are supported:
SNMPComID this is the ID of the SNMP community. The system supports up to 5

pre-configured communities, one for each of the user privilege classes. Possible
values are: admin, provisioner, observer, nms, and 3rdpnms. This parameter requires a
value.
String this is the community string sent from the SNMP manager to the NE. It is an
ascii string from 1 to 32 characters. Based on the string and the privilege level
inherited from the SNMPComID, the NE will either process or deny the SNMP
request. The string must be unique (there cannot be duplicate strings) and the string
cannot start or end with a blank space.
The SNMP string is checked every time an SNMP request is processed by the NE. If
there is a match, then the NE will further check the privilege level of that string to
ensure that the request can be granted given the command privilege level. If the string
does not match any string defined in the NE, the request fails and the NE returns a
failure message. If the privilege level is inadequate for the request being asked, then
the NE returns a failure message, otherwise, the request is processed.
....................................................................................................................................................................................................................................
2-26
August 2011
....................................................................................................................................................................................................................................

Create RADIUS server
...................................................................................................................................................................................................
In the WebUI, select Security > RADIUS > Servers

Result: The RADIUS Servers screen is displayed.
...................................................................................................................................................................................................
Click Create.
Result: The Create RADIUS Server screen is displayed.
...................................................................................................................................................................................................
Enter parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
Delete RADIUS server

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

...................................................................................................................................................................................................
Select the RADIUS server and click Delete.

E...................................................................................................................................................................................................
N D O F S T E P S
View RADIUS server

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

...................................................................................................................................................................................................
Select the RADIUS server and click Details.

Result: The RADIUS server details are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-27
August 2011
....................................................................................................................................................................................................................................
Provision RADIUS properties

...................................................................................................................................................................................................
In the WebUI, select Security > RADIUS > Properties

Result: The RADIUS Properties screen is displayed.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-28
August 2011
SNMP procedures
....................................................................................................................................................................................................................................
SNMP procedures
Create trap destinations
...................................................................................................................................................................................................
In the WebUI, select Administration > SNMP > Trap Destinations

Result: The SNMP Trap Destinations screen is displayed.
...................................................................................................................................................................................................
Click Create.
Result: The Create SNMP Trap Destinations screen is displayed.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
Delete trap destinations

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

...................................................................................................................................................................................................
Select the Trap Destination and click Delete.

E...................................................................................................................................................................................................
N D O F S T E P S
View trap destinations

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

...................................................................................................................................................................................................
Select the trap destination and click Details.

Result: The Trap Destination details are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-29
August 2011
SNMP procedures
....................................................................................................................................................................................................................................
View / modify community strings

...................................................................................................................................................................................................
In the WebUI, select Administration > SNMP > Community Strings

Result: The SNMP Community Strings are displayed.
...................................................................................................................................................................................................
To modify Community Strings, enter appropriate values in the respective fields and click
Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
2-30
August 2011

3
Overview
Purpose
This chapter provides information for setting up Alcatel-Lucent 1830 PSS external
communication to/from the NE via the existing user interfaces. Management information
and control from the Operations System (OS) is carried from one NE to another over the
internal Alcatel-Lucent 1830 PSS network via the Optical Supervisory Channel (OSC).
Contents
User interfaces
3-2
Communications network
3-7
Gateway NE (GNE) management
3-9
Data communication set-up procedures
3-12
3-17
Connection release
3-17
CIT port
3-17
Using the WebUI
3-18
WebUI startup procedures
3-20
...................................................................................................................................................................................................................................
3-1
August 2011
User interfaces
....................................................................................................................................................................................................................................
User interfaces
Overview
The NE hosts LAN, serial, and debug interfaces sufficient to support EMS, local craft
terminal and serial or LAN based processor access for debug purposes. The NE supports
a single LAN IP address (Router ID) for all LAN functions. This address is provisionable
and is required when bringing up the system. This is the IP address used for all IP
communications over the OSC, GCC0, and OAMP if the OAMP port assumes the Router
ID.
A Craft Interface Terminal (CIT) interface provides access for local craft workers to
WebUI, CLI, and TL1 interfaces via local craft PCs. The WebUI interface provides a
graphical user interface to the node software using HTML, JavaScript, and Java. The
application runs on the NE and is controlled and viewed through a standard web browser
that is provided by the PC.
A local craft terminal (laptop or PC) connected either through a serial or a LAN interface
can establish TL1 or CLI connections to any NE reachable via the local NE. In addition,
the LAN interfaces can establish SNMP connections to any SNMP management system
that is reachable via the local NE.
On initial turn-up, the systems IP address (Router ID) is 172.16.0.1. The Router ID can
be provisioned via a connection to the serial craft port using the appropriate CLI or TL1
command. The Router ID can also be provisioned via the CIT port, whereby the user
simply connects his laptop to the CIT port of the master Equipment Controller (EC) and
accesses the WebUI.
Note: The following applies to the CIT:
When a user manually configures the CIT Port Admin State, the CIT Auto State is
disabled
When a user manually disables the CIT Auto State the CIT Port Admin State is
automatically set to the default value of Enabled.
Web User Interface (WebUI)
The web user interface (WebUI) provides web-based access to the network element (NE).
The WebUI interface is accessed using Internet Explorer running on a computer that is
connected via Ethernet to the NE, either directly or over a LAN. The WebUI supports
provisioning, administration, performance monitoring, and display of alarms and
conditions from the NE. It provides an intuitive, easy-to-use tool to assist in the initial
installation and troubleshooting of NEs.
....................................................................................................................................................................................................................................
3-2
August 2011
User interfaces
....................................................................................................................................................................................................................................
Command Language Interface (CLI)
The Command Line Interface (CLI) is a line-oriented user interface that runs on the NE.
A user can access the CLI using a terminal device connected to the NE. The CLI provides
commands that allow the user to configure, manage, and monitor the NE, the NE
interfaces, and the services running on the NE.
Transaction Language 1 (TL1)
TL1 is a common protocol for NE management. The Alcatel-Lucent 1830 PSS TL1
interface is a text-based command line interface that allows the operator to configure and
manage Alcatel-Lucent 1830 PSS hardware, software, and services.
Note: TL1 is functionally and structurally defined by Telcordia documents such as
GR-831, GR-199 & GR-474.
Simple Network Management Protocol (SNMP)
SNMP is used in the management of various types of networks. The SNMP

communications occur over the Alcatel-Lucent 1830 PSS control network. SNMP has two
types of entities: management network elements (managers) and managed network
elements (agents). There are instances when the agent must notify the manager of an
event it has experienced without first having received a request from the manager. The
agent does this through traps. SNMP traps, therefore, are asynchronous messages from a
network element agent to a network manager that signals an event that may require user
attention.
In an Alcatel-Lucent 1830 PSS network, the 1354 RM-PhM or other external operations
system (such as surveillance center) acts as the management network element or manager.
The Alcatel-Lucent 1830 PSS network element acts as a managed network element or
network element agent. Traps are messages that the Alcatel-Lucent 1830 PSS network
element sends to the 1354 RM-PhM or external management system on an as-needed
basis to notify the manager of events the network element has experienced. Besides
autonomous messages (such as traps), the SNMP manager can retrieve or modify the NE
configuration (using GET or SET functions).
Note: Alcatel-Lucent 1830 PSS supports SNMP versions v1, v2c, and v3 of the
protocol.
User Panel (USRPNL)
The Alcatel-Lucent 1830 PSS provides a User Panel (USRPNL) located on the main
shelf, which supports the majority of communication connections for the NE. This user
panel includes the following ports:
Craft serial connection via DB9

Craft serial connection via USB-B
OAMP LAN connection via RJ45
....................................................................................................................................................................................................................................
3-3
August 2011
User interfaces
....................................................................................................................................................................................................................................
VoIP LAN connection via RJ45

E1/E2 LAN connection via RJ45
Note: The user panel OAMP port was meant to connected to a router/switch. In a
fixed configuration. When connected to a PC/laptop, a crossover cable must be used.
In auto-negotiation mode, either straight or crossover cable can be used.
There are four (4) general purpose switched auto-sensing LAN ports (10/100BaseTX), for
connection to EMS/NMS, VoIP, and externally managed devices. The four general
purpose switched auto-sensing LAN ports on the user panel are as follows:
The OAMP port is used to connect to the External Management System (EMS) and is
the main control interface to the NE. The signaling format is 10/100BaseT. By
default, the OAMP LAN inherits the Router ID IP address when the OAMP LAN port
is enabled for service. However, the user is free to change the IP address of the
OAMP LAN port.
The VoIP port is used to connect to an IP phone. With IP phones at every site,
customers/field technicians can talk to one another simply by dialing the IP address of
the destination phone. The IP address and status of the port can be user provisioned.
There are two External LAN ports (which can be used to connect to externally
managed devices), labeled E1-LAN and E2-LAN. These ports are auto-sensing, so
either a cross-over or straight-thru Ethernet cable can be used.
The ports designated as the OAMP and Craft ports on the USRPNL, support access to the
CLI and TL1 commands. Further, the serial craft port (which is the DB-9/USB-B port)
supports only CLI and TL1, and the OAMP port also supports SNMP management. The
VoIP port on the USRPNL is disabled by default. External IP address and MAC address
remain fixed and follow the active LAN ports on the USRPNL. There is one MAC for the
OAMP port and one MAC for the VoIP port. The Alcatel-Lucent 1830 PSS NE's MAC
addresses associated with the LAN ports on the USRPNL are installed/assigned at the
factory.
Note: The USRPNL status LED reflects status of the USRPNL itself rather than shelf
status.
Attention: The OAMP port supports both fixed configuration and auto mode. It is
provisionable via CLI or WebUI. It is not recommended to have one side as auto and
other as fixed configuration. The configuration should match on either side.
The user panel OAMP port was meant to connected to a router/switch. In a fixed
configuration, when connected to a PC/laptop, a crossover cable must be used. In
auto-negotiation mode, either straight or crossover cable can be used.
User panel replacement
After an in-service replacement of the User Interface Panel, it is necessary to synchronize

the USRPNL with the Network Element database in order to avoid a "database invalid
alarm". This can be done via the WebUI using the following procedure.
....................................................................................................................................................................................................................................
3-4
August 2011
User interfaces
....................................................................................................................................................................................................................................
Synchronize the USRPNL with the Network Element database

1. From the WebUI menu, select Administration > Database > USRPNL Replacement
Update.
2. In the USRPNL Replacement Update window, select Synchronize USRPNL with
Network Element Database: and click Apply.
Note: For detailed procedure on Replacing User Panel and detailed procedure for
User Panel replacement interrupted by a restart, see the Alcatel-Lucent 1830
Photonic Service Switch 36/32/16 (PSS-36/32/16) Release 3.6.0 and 3.6.1
Maintenance and Trouble-Clearing Guide.
Craft interface
The NE supports two craft ports including a female (DB9) and a USB-B port. Both ports
support local RS-232C serial interface for connection to a CIT via serial link.
Either the DB9 port or the USB-B port can be used to connect serially to the NE.
However, only one port can be active at any given time. The NE automatically detects the
presence of a laptop (or any equivalent active device) when it is connected to the USB-B
port on the USRPNL. When both USB-B port and DB9 ports are simultaneously
connected, preference is given to the USB-B port. The USB-B port becomes active, and
the DB9 port is rendered inactive.
Note: The parity setting for the USB port must be set to Odd. The parity setting for
the DB9 interface must be set to None.
Equipment controller (EC)
Every Alcatel-Lucent 1830 PSS shelf contains one or two ECs (depending on whether
redundancy is desired). The EC provides four auto-sensing RJ45 LAN ports. The first
port (labeled CIT) located at the topmost of the EC, is dedicated for CIT connection. The
CIT port is active for ECs residing on the master shelf and disabled for ECs residing on
sub-shelves. The user may plug the CIT laptop into either of the Master ECs CIT port
and the SW will auto switch to the active EC.
Configurable attribute values on the two Master CIT ports are always the same; updating
the values on one port will automatically update the values on the other port. However,
when a newly introduced redundant EC is installed, CIT port data from the first EC would
need to be copied to the CIT port on the new EC.
The CIT port supports DHCP server. When a connection (e.g. using a laptop) is detected,
the NE provides an IP address in response to the DHCP request from the laptop. The CIT
port allows the client to connect locally to manage the NE, and it can also allow the client
to connect to any remote NE reachable by the local NE. The port also supports SNMP
(via 1354 RM-PhM) and FTP.
....................................................................................................................................................................................................................................
3-5
August 2011
User interfaces
....................................................................................................................................................................................................................................
The available addresses start at the beginning of the network address range as long as
they don't conflict with either the broadcast or local address. The DHCP server assigns the
IP to the client PC when connected to CIT port in the following manner:
If assign 192.168.5.1/24, and the dhcp_range is 5, the available addresses are

192.168.5.2,3,4,5,6

192.168.5.1,2,3,4,6
192.168.5.1,2,3,4,5
192.168.5.1,2,3,4,6
Note: The WebUI does not run the full features like the 1354 RM-PhM. The CIT port
will only provide basic NE management (for local and remote management via
SNMP). IP Routing functions in 1830 PSS-36/PSS-32/PSS-16 and 1830 PSS-1 have
to be configured so that all NEs intended to be managed, are reachable from the local
NE. In other words, IP applications from any external DCN network will work only
when there is full IP reach capability to every GNE and RNE in the network.
The bottom two ports on the EC (labeled ES1 and ES2) are used to connect to
Alcatel-Lucent 1830 PSS extension shelves (sub-shelves). The 1830 PSS-32 NE may be
comprised of multiple 1830 shelves. In order to enable protected communication between
1830 PSS-32 shelves which comprise one NE (single TID), ES1/ES2 ports on these
shelves need to be connected in a daisy-chain fashion.
Failure of any EC in a duplex controller configuration does not prohibit communication
between the affected sub-shelf and the main shelf. Likewise, failure of any EC in a
simplex controller configuration does not prohibit communication between the main shelf
and all other sub-shelves, unless the simplex EC is the controller for the master Shelf.
Note: For detailed procedure on Replacing Equipment Controller, see the
Alcatel-Lucent 1830 Photonic Service Switch 36/32/16 (PSS-36/32/16) Release 3.6.0
and 3.6.1 Maintenance and Trouble-Clearing Guide.
....................................................................................................................................................................................................................................
3-6
August 2011
....................................................................................................................................................................................................................................
The basic communications network architecture for the Alcatel-Lucent 1830 PSS includes
all LAN interfaces, OSC interfaces, and GCC interfaces. LAN interfaces include the
OAMP, VoIP, E1, E2, CIT, and Extension Shelf (ES) connections. The OSC interfaces can
vary from one up to 8, one for each degree. The OSC carries node-to-node
communication, sharing of OSPF LSAs, wavetracker keys, SCOT messages, etc.
Note: Wave key opaque LSAs can only be enabled in one OSPF Area.
Note: The external communication (Voice/data) through the LAN ports (VoIP, OAMP,
E1, E2) in the User Interface Panel (USRPNL) are lost (dropped) when the active
controller (EC) fails (by autonomous or manual switchover command). The
communication will be established again when the EC becomes active. This also
applies to OSC and GCC as well.
For the communications network, static routes or OSPF must be used.
The GCC interfaces can vary from 1 up to 32, depending on the number of supported
Optical Transponders (OT's) that are provisioned for GCC0 termination.
Note: GCC0 terminations on the Alcatel-Lucent 1830 PSS system are supported by
the following:
4DPA4 OTU1 line port
11DPE12(E) OTU2 line port

11DPM12 OTU1 client port
11DPM12 OTU2 line port
11QPA4 OTU2 client port
11QPA4 OTU2 line port

11STAR1 OTU2 client port
11STAR1 OTU2 line port
11STMM10 OTU1 client port
These ports are used for connecting with the 1830 PSS-1 (Edge Device).
For newly added GCC interfaces in new or existing installations it is highly
recommended to immediately set the interface GCC to standard mode of operation.
For existing GCC interfaces in existing installations it is highly recommended to plan
to upgrade ALL GCC interfaces to standard mode of operation. This must be a
planned action as changing the GCC standard mode of operation will cause the
interface data link to go DOWN until the GCC standard mode of operation on the
opposite end is changed to match.
Note: For newly added OSC/GCC interfaces in new or existing installations it is
highly recommended to immediately set the interface MTU size to 1500 bytes.
....................................................................................................................................................................................................................................
3-7
August 2011
....................................................................................................................................................................................................................................
For existing OSC/GCC interfaces in existing installations it is highly recommended to

plan to upgrade ALL OSC/GCC interface MTU size to 1500. This must be a planned
action as changing the MTU size on one side of the OSC/GCC interface may cause
the interface data link to go DOWN until the MTU size on the opposite end is
changed to match.
Changing the MTU size to 1500 bytes allows for the remote management of
RAMAN/EDFA boxes through an 1830 network as well as increased throughput due
to minimized packet fragmentation.
Table 3-1, Communications Network Sizing (p. 3-8) provides a communications
network sizing summary.
Table 3-1
Communications Network Sizing
Connection Type
Maximum Value
Comment
TL1 (ports 3082, 3083)
20 (see table note)
Multiple TL1 user sessions to

any NE
WebUI
16
This is for Craft Interface

Terminal (CIT) from the local
craft, or remotely connected
CLI
10
From the local craft or remote
SNMP
10
Management from 1354

RM-PhM or equivalent
SNMP manager
GCC0
32
For management connection

extension to SPB
OSC
20
Maximum of 8 fiber pairs
RNEs managed from one

GNE
128
Size of TID-IP map per GNE
256
TID to IP mapping over the

OSC and GCC0
Active users
32
Combinations of TL1,
WebUI, CLI, and SNMP users
Number of degrees supported

by one NE
52
32 GCC0 + 20 OSC
Number of NEs in one OSPF

area
256
Default OSPF area is 0
Number of provisionable
OSPF areas supported on the
NE
....................................................................................................................................................................................................................................
3-8
August 2011
....................................................................................................................................................................................................................................
Note: Once the maximum allowed count of 20 TL1 sessions are open, the user needs
to cancel the current TL1 log-in session(s) to allow any new users. A new user needs
to wait for 2 minutes to log-in after cancelling any of the already logged-in users.

Overview
A Gateway Network Element (GNE) is defined as an NE that provides user access to all
NEs within the maintenance subnetwork. Any Alcatel-Lucent 1830 PSS can function as a
gateway NE. The GNE is able to send over the ECC (OSC and GCC0) the TL1
commands which are destined for a Remote NE. The GNE routes the messages between
members of the maintenance subnetwork.
The NE maintains a Gateway mapping table which contains mapping entries for every
reachable NE on the network. Each entry in the table contains the TID of the NE and its
corresponding IP address. The table contains entries for every reachable NE (over the
OSC for the Alcatel-Lucent 1830 PSS, as well as over the GCC for the 1830 PSS-1). The
gateway mapping table is capable of holding a maximum of 128 entries.
Note: Upon reaching the maximum of 128 entries, the NE will raise an alarm to
indicate that the maximum size has been reached.
The NE supports creating and deleting system-level OSPF areas. The NE can be up to 3
OSPF areas, in addition to the default backbone area (0-0-0-0). After an OSPF Area is
created, it can then be assigned to an OAMP, VOIP, E1, E2, OSC or GCC interface.
Opaque LSAs are used to advertise/distribute association parameters.
Note: OSPF does not need to run on the CIT, since this port is meant to be local LAN
(i.e. a stub network, not one where routes need to be discovered).
When OSPF is enabled on the OAMP or GCC0 interfaces, the default area for those
interfaces is 0. When OSPF is enabled on the OSC interface, the default area for this
interface is also 0. However, the system supports configuration of different areas on
these supported interfaces.
The GNE functionality supported in the Alcatel-Lucent 1830 PSS comes in handy if a
customer does not want to enable OSPF on the OAMP interface. Without OSPF to
discover the internal network and distribute this network to the management DCN, the
EMS is not able to directly connect to any remote NE (RNE). Connection method must
then be made thru the GNE. For example, in order to connect to an RNE, the customer
must first telnet to the GNE and from there, connect to the desired RNE.
Note: If any NEs are GNEs using static IP routing and then are reconfigured as
non-GNEs, any routers on the local subnet should have their ARP entries cleared so
that re-routing may take place immediately.
....................................................................................................................................................................................................................................
3-9
August 2011
....................................................................................................................................................................................................................................
Note: In a network design where OSPF is enabled on the GNE OAMP management
ports or static routes are configured such that an alternate path for the 1830 NEs is
available via the customer DCN in addition to inter-NE paths via OSC/GCC
interfaces the following should be adhered too:
1. At the GNE NEs the Loopback IP should be provisioned with the snmp_src option
such that all SNMP requests to the NE must use only the Loopback IP of the NE
(the OAMP IP address will not be valid for SNMP requests). Likewise any SNMP
traps from the NE will contain the Loopback IP as the source IP address.
2. When OSPF is enabled at the OAMP port the OSPF metric should be provisioned
to be greater than the largest Inter-NE path cost. This will allow for NE-NE
application data messages to prefer inter-NE paths over customer DCN paths.
3. When static routes are configured at the GNE in order to provide an alternate path
for the 1830 NEs via the customer DCN in addition to inter-NE paths via
OSC/GCC interfaces - the distance value provisioned for each static route should
be greater than 110. This will allow for NE-NE application data messages to
prefer inter-NE paths over customer DCN paths.
For applications based on IP stack (i.e. SNMP, ftp, telnet), the EMS directly
communicates with the RNE, without using any translation function on the GNE. In this
case, all IP packets are routed to the appropriate destination, and the GNE does not need
to perform any association or mediation services.
To provide redundant paths between NMS and Alcatel-Lucent 1830 PSS network, dual
GNE configurations may be used (two examples of dual GNE configurations are shown
in Figure 3-1, Dual GNE configurations (p. 3-11).
....................................................................................................................................................................................................................................
3-10
August 2011
....................................................................................................................................................................................................................................
Figure 3-1 Dual GNE configurations
For NE-to-EMS messages, the GNE routes the TL1 message over an IP address to the
appropriate EMS based on the connection on which the message was received.
Note: Enabling and disabling of TL1 autonomous messaging is supported via the
WebUI. The default state is for messages to be suppressed. To enable TL1
autonomous messaging, check TL1 Autonomous Messages Enabled in the System
Properties window display.
....................................................................................................................................................................................................................................
3-11
August 2011
....................................................................................................................................................................................................................................

Before you begin
The following procedures are available via the WebUI after the user initially connects to
the NE and logs into the system (see Using the WebUI (p. 3-18)).
View network (NE name, NE IP, software release) map information
...................................................................................................................................................................................................
In the WebUI, select Reports > Network Map.

Result: The Network Map information is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
View / modify IP route metric settings
Note: The WebUI allows the user to view and/or modify the system-wide IP route
parameters for metric settings.
...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > IP Route Redistribute Metrics.
Result: The IP Route Redistribute Metric Settings screen is displayed with current
values.
...................................................................................................................................................................................................
To modify the metric settings, enter attribute values and click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
Create IP static route

...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > IP Routes.

Result: The IP Routes screen is displayed.
...................................................................................................................................................................................................
Click Create.
....................................................................................................................................................................................................................................
3-12
August 2011
....................................................................................................................................................................................................................................
Result: The Create Static IP Route screen is displayed.

...................................................................................................................................................................................................
To create the default route, select Default Route.

...................................................................................................................................................................................................
Enter attribute values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
View all IP routes

...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > IP Routes.

E...................................................................................................................................................................................................
N D O F S T E P S
Delete IP static route

...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > IP routes.

...................................................................................................................................................................................................
Select the IP Route and click Delete.

Note: For delete, a warning message is displayed to the user indicating that a loss of
communication may occur. The user can continue with the delete request or cancel.
Upon continuing with the request, the delete request will be sent to the NE for
execution.
E...................................................................................................................................................................................................
N D O F S T E P S
Create OSPF area
Note: The WebUI supports displaying all OSPF Areas configured on the NE. To help
in modifying OSPF Area ID on the USRPNL ports, the WebUI displays a picklist of
Area IDs configured. Up to 4 OSPF areas (including the default) may be configured
on the NE.
....................................................................................................................................................................................................................................
3-13
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > OSPF Areas.

Result: The OSPF Areas screen is displayed.
...................................................................................................................................................................................................
Click Create.
Result: The Create OSPF Areas screen is displayed.
...................................................................................................................................................................................................
Enter attribute values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
View OSPF areas

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

Result: The OSPF Areas are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Delete OSPF area
Note: The WebUI will not allow deletion of Area ID = 0.0.0.0.

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

Result: The OSPF Areas are displayed.
...................................................................................................................................................................................................
Select the OSPF Area and click Delete.

E...................................................................................................................................................................................................
N D O F S T E P S
Configure orderwire function
Engineering Order Wire (EOW) function is a traditional SONET/SDH function which

utilizes E1/2 channels to provide voice communication between sites. 1830 PSS offers
EOW function emulation via the VOIP port. The implementation provides a dedicated
....................................................................................................................................................................................................................................
3-14
August 2011
....................................................................................................................................................................................................................................
LAN port and IP routing in enabling VOIP communication. The only setup needed is IP
configuration on the port and properly configure the IP phone used. The following
procedure details the VOIP configuration setup between two NEs.
...................................................................................................................................................................................................
In the WebUI expand the equipment tree to select System > PSS-32 or PSS-16 Shelf >
USRPNL > VOIP
Note: On PSS-36 shelf, this is on the MT0C card: System > PSS-36 Shelf > MT0C >
VOIP
Result: In the Port Details tab, the Port Interface Settings screen is displayed.
...................................................................................................................................................................................................
Configure the first NE IP Address (e.g., 160.1.1.2) and VOIP phone IP (e.g., 160.1.1.3)
...................................................................................................................................................................................................
Configure the second NE IP Address (e.g., 170.1.1.2) and VOIP phone IP (eg: 170.1.1.3)
...................................................................................................................................................................................................
For both NEs and VOIP phones, configure the Mask as 255.255.240.0
...................................................................................................................................................................................................
For both NEs, click on the OSPF details tab and set OSPF routing to ENABLED or
REDISTRIBUTE.
...................................................................................................................................................................................................
For both VOIP phones, configure Default Gateway as the VOIP port IP of the
corresponding NEs.
...................................................................................................................................................................................................
Click on the Port Details tab and select Port Enabled for both NEs.
E...................................................................................................................................................................................................
N D O F S T E P S
To check if EOW setup is correct
Check to ensure that the following values are configured for the VOIP port for both NEs:
Present Link Speed: 100Mbps

Present Duplex Mode: Full
Link Integrity: Up
When dialed from one VOIP phone to the other (e.g., dialing 160.1.1.3 from 170.1.1.3 or
vice versa), voice communication should be heard at both ends. The communication is
point-to-point (one caller and one callee at a time) as long as the OSC is connected
....................................................................................................................................................................................................................................
3-15
August 2011
....................................................................................................................................................................................................................................
between the NEs. If five NEs are connected in different directions through OSC, then
each NE can communicate to the other four NEs (one at a time). There is no broadcast
capability.
....................................................................................................................................................................................................................................
3-16
August 2011
....................................................................................................................................................................................................................................
Connection between a GNE and RNE
The following applies to connections between the GNE and RNE:
It is not necessary that the EMS using TL1 must use a single TCP connection to a
GNE and multiplex all TL1 sessions through that GNE over that single TCP
connection. The TL1 EMS can create several TCP connections to a single GNE and
multiplex any number of TL1 sessions over each TCP connection.
The EMS can setup a separate TCP connection for each TL1 session. If the EMS does
this, there is a one-to-one mapping of EMS TCP connections to RNE connections.
The establishment of an RNE connection is triggered by the ACT-USER TL1
command with the remote NEs TID, if there does not already exist a connection to
that RNE.
Connections to a Remote NE (for GNE to Remote NE communications) are
terminated by the remote NE if it has not received valid ACT-USER within the
specified time.
Connection release
Either side of a TL1 connection (i.e., the responder side or the initiator side can
disconnect the connection at any time. When the remote side disconnects a connection or
when a connection is aborted, all resources specifically allocated for that connection are
de-allocated.
Connections to a remote NE are terminated by the RNE when a user associated with that
connection (i.e., the remote NE user, EMS user or craft interface user) logs out of the NE.
CIT port
Remote NE management via the CIT port(s) can be supported, but only if the operator
assigns unique IP addresses to these CIT ports. Either CIT port on the active EC or
standby EC (if equipped) can be used to connect to the external device (e.g. laptop).
The system allows a user (Admin or Service user) to auto-disable the CIT port status.
Disable Port Automatically can only be set to Yes if Source IP is configured (does not
equal 0.0.0.0).
Note: Configurable attribute values on the two CIT ports are always the same;
updating the values on one port will automatically update the values on the other port.
When a redundant EC is installed, CIT port data from the first EC would need to be
copied to the CIT port on the new EC.
....................................................................................................................................................................................................................................
3-17
August 2011
CIT port
....................................................................................................................................................................................................................................
Once the laptop verifies that it can talk to its gateway, then the user can run the CIT,
telnet to the TL1 port, or telnet into the CLI. From the locally connected-to-CIT-port
laptop the NE will respond as follows:
If the user runs the WebUI, the NE responds with a login screen.
If the user runs the telnet session to the TL1 port the NE responds with a TL1
command prompt.
If the user runs the telnet session to the CLI, the NE responds with a CLI login
prompt.
The SNMP function is fully supported over the CIT, so the CIT can be used to
manage the entire Alcatel-Lucent 1830 PSS network if needed.
Using the WebUI

Overview
The web user interface (WebUI) provides web-based access to the network element (NE).
You access the WebUI interface using Internet Explorer running on a computer that is
connected via Ethernet to the NE, either directly or over a LAN.
WebUI hardware requirements
Laptop or desktop computer capable of running the required software.

Ethernet card (10 Mb/s minimum, 10/100 Mb/s recommended).
It is recommended that you use a monitor capable of displaying at a resolution of

1024x768 or greater.
WebUI software requirements
Windows XP, Windows 2000, or Windows 7 updated to the most recent patch level.
Internet Explorer 6.0, 7.0, or 8.0 updated to the most recent patch level
or
Firefox 3.6.13
Note: The following functionality is not supported with the Firefox browser:
Power Commissioning page
Export to Excel
Show in separate window
J2SE Java Runtime Environment (JRE) version 5.0 or later. The supported version for
the NE software version you are running is included on the NE software CD-ROM.
Note: Vista is not supported for WebUI.
....................................................................................................................................................................................................................................
3-18
August 2011
Using the WebUI
....................................................................................................................................................................................................................................
Navigating the WebUI
The Equipment Tree allows the user to navigate through the NE equipment in a
hierarchical fashion from the system level down to the port level and select a single entity
from the hierarchy. The NE Equipment Tree provides the equipment selection mechanism
for all the NE management functions supported. The selection on the NE Equipment Tree
is always in sync with the information displayed in the Display Panel.
When navigating the equipment tree, the following applies:
Click on the plus sign (+) next to the piece of equipment to expand the tree.
Click on the minus sign (-) next to a piece of equipment to collapse the tree.
Click on a piece of equipment to select it.
Equipment tree hierarchy
Figure 3-2, Equipment tree hierarchy (p. 3-19) depicts the equipment tree hierarchy:
Figure 3-2 Equipment tree hierarchy
The user will traverse the hierarchy and select a specific equipment to access the
functions supported by that equipment.
....................................................................................................................................................................................................................................
3-19
August 2011
....................................................................................................................................................................................................................................

Log into the WebUI
...................................................................................................................................................................................................
Launch the Internet Explorer browser.

...................................................................................................................................................................................................
Enter the IP address of the network element.

Result: The WebUI interface login window is displayed.
Note: If you are logging into the NE for the first time (that is, the NE has not yet been
provisioned), see Initial NE configuration (p. 3-21)
When a user connects to an NE after the initial NE configuration, the WebUI displays
a window where the user can enter their User ID and Password and submit the login
request.
...................................................................................................................................................................................................
Enter your User ID in the User: field.

...................................................................................................................................................................................................
Enter the password associated with the User ID in the Password: field. The characters you
enter for the password are not displayed.
Note: Passwords are case sensitive. If you experience difficulty logging in, verify that
the Caps Lock key is off.
...................................................................................................................................................................................................
Click on the Login button, or press the Enter key.

Result: Upon successful login, the System Details screen is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Exit the WebUI

...................................................................................................................................................................................................
To end the WebUI session, click on Logout.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-20
August 2011
....................................................................................................................................................................................................................................
Initial NE configuration
...................................................................................................................................................................................................
When connecting to an NE for the first time, connect the Ethernet cable (RJ45) from the
PC to the EC CIT port on the NE and type in the default IP address of 172.16.0.1 in order
to connect to the NE.
Result: A window is displayed where the user can enter their User ID and Password
and submit the login request.

...................................................................................................................................................................................................
Enter your User ID in the Username: field.

...................................................................................................................................................................................................
Enter the password associated with the User ID in the Password: field. The characters you
enter for the password are not displayed.
Note: Passwords are case sensitive. If you experience difficulty logging in, verify that
the Caps Lock key is off.
...................................................................................................................................................................................................
If the login is successful, the WebUI displays a message indicating that the database needs
to be initialized. The user will be given 2 options:
OK upon selection, the WebUI sends a request to the NE to initialize the database.
Note: Initializing the database causes the NE to reboot.

Cancel upon selection, the WebUI displays the System Details screen. From here,
the user can navigate to the Admin screens to configure the NE as needed (for
example, restore a previously backed up database).
Result: The following informational text will be displayed on the screen: The
database is invalid.
...................................................................................................................................................................................................
Select one of the following:
Click OK to initialize the database. The NE will automatically restart after

initialization is complete. This will interrupt service if the NE has live traffic.
Click Cancel to bypass initialization and proceed to the WebUI. Use this option when
the NE has services that you do not want to interrupt. You will be asked to supply an
NE Name and then the NE will automatically restart without affecting service.
...................................................................................................................................................................................................
When the user logs into the NE after database initialization, the WebUI prompts the user
to enter NE information (NE Name). Enter and submit this information.
....................................................................................................................................................................................................................................
3-21
August 2011
....................................................................................................................................................................................................................................
Result: The WebUI sends the data to the NE resulting in another NE reboot. The NE
and WebUI are now ready for normal operation. The WebUI will automatically
reconnect to the NE when it is available.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
3-22
August 2011
4
Overview
Purpose
This chapter provides details for provisioning the Alcatel-Lucent 1830 PSS system
including shelves, slots/cards, and ports.
Contents
Introduction
4-2
Provisioning system (NE) procedures
4-3
Equipment management
4-5
Shelf provisioning
4-25
Shelf provisioning procedures
4-30
Slot/card provisioning
4-31
Slot/card provisioning procedures
4-46
Port/facility provisioning
4-50
Port provisioning procedures
4-202
...................................................................................................................................................................................................................................
4-1
August 2011
Introduction
....................................................................................................................................................................................................................................
Introduction
Description
Provisioning is the process of assigning values to parameters that determine the operating
characteristics of the system. The values of the provisioned parameters determine how
you interface with an NE and how the NE functions with various installed entities. Each
provisionable parameter has a factory-supplied original value when software is first
loaded onto an NE. These values become the current value upon launching the software
and are the values used by the system. All provisioned parameters and values are
preserved in the systems non-volatile memory and are protected and can be retrieved on
demand or restored upon recovering from power failure. Copies of these parameter
settings can also be used by other identical NEs.
User access to Equipment Management functions is available via all supported user
interfaces. Therefore, all externally user provisionable parameters can be set using the
WebUI, TL1, CLI, or EMS (1354 RM-PhM). Autonomous notifications are generated for
the following equipment-related events:
physical removal/insertion
failure/recovery
warm/cold restart
primary/secondary state changes
logical removal/restoration
provisioning creation/deletion/changes
....................................................................................................................................................................................................................................
4-2
August 2011
....................................................................................................................................................................................................................................

Overview
This section describes the WebUI procedures for NE-level functions.

View / modify NE parameters
...................................................................................................................................................................................................
Login to the NE and using the WebUI, select System from the equipment tree. Select the
Provision/Info function.
Result: System properties are displayed under the Details tab.
...................................................................................................................................................................................................
View or modify the System Properties fields as necessary.

Note: If the Loopback IP Address is changed, a warning message is displayed
indicating that a reboot will occur. The user can continue or cancel the request.
E...................................................................................................................................................................................................
N D O F S T E P S
Reboot NE
The user can request a manual reboot of the entire NE which reboots all applicable circuit
packs (EC, LD, OSCT, CWR, OT, OPSA, SVAC, MVAC). Both warm and cold restarts
are supported. For a cold restart, the WebUI displays a warning indicating that service
may be affected. The user is allowed to continue with the request or cancel. (USRPNL,
FAN, PF, SFC, SFD, ITLB, ITLU, and DCM have no processors and cannot be restarted.)
...................................................................................................................................................................................................
Select System from the equipment tree and select the Reboot tab.
Result: The Reboot Options screen is displayed.
...................................................................................................................................................................................................
Select either Warm Reboot or Cold Reboot and click Submit.
....................................................................................................................................................................................................................................
4-3
August 2011
....................................................................................................................................................................................................................................
Note: Cold restart of a transmission-carrying pack kills traffic, and thus cold restart is
not allowed on an in-service pack. The pack must either be in maintenance state or
out-of-service as described below:
1. Put the pack (and ports) into maintenance state before performing the cold restart.
In maintenance state the cross connects can remain in place, and transmission is
still carried.
2. Perform a cold restart of the entire NE, instead of pack-by-pack. The TL1
command "INIT-SYS" allows this without individually changing all pack/port
admin states in the system -- if the user specifies the "forced" option. The CLI
command "config admin resetne" offers an equivalent to this "forced" option.
Note: When a pack warm reboots or is cold rebooted the PM data is not available.
Similarly, pack related alarms cannot be retrieved.
E...................................................................................................................................................................................................
N D O F S T E P S
Configure firmware
The WebUI supports configuring firmware for the following card types: 4DPA2, 4DPA4,
11DPE12, 11DPE12E, 11DPM12, 11QPA4, 11STAR1, 11STGE12, 11STMM10,
43STA1P, 43SCX4, 43STX4, 43STX4P, 112SA1L, 112SCA1, 112SCX10, 112SX10L,
A2325A, AHPHG, AHPLG, ALPFGT, ALPHG, AM2017B, AM2125A, AM2125B,
AM2318A, AM2325B, CWR8, CWR8-88, MESH4, MVAC, OPSA, OSCT, RA2P,
SVAC, WR8-88A, and WTOCM. To support modification of the provisioned release, the
WebUI displays a picklist of valid values for the card type. For each card type, there is a
default firmware version.
...................................................................................................................................................................................................
Select the card from the equipment tree and click the Firmware tab.
...................................................................................................................................................................................................
Select desired Provisioned Release from the picklist and click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
View firmware
...................................................................................................................................................................................................
In the WebUI, select Reports > Firmware.
....................................................................................................................................................................................................................................
4-4
August 2011
....................................................................................................................................................................................................................................
Result: The Firmware report window is displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
Equipment discovery
Detection of physical insertion and removal (via backplane equipage leads) is supported
for the following circuit packs which reside in 1830 PSS-36/PSS-32/PSS-16 shelf slots.
EC
USRPNL
PF
FAN
A2325A/AHPHG/AHPLG/ALPHG/ALPFGT/AM2017B/AM2125A/AM2125B/
AM2318A/AM2325B
CWR8 & CWR8-88
OT
OPSA
OSCT
SFC
SFD
SVAC
MESH4
MVAC
RA2P
WR8-88A
WTOCM
pluggable SFP/XFP modules
Indirect detection of presence/absence (inferred by readability of electronic inventory

link) is supported for the following modules (when they are provisioned as managed).
These do not reside in PSS shelf slots.
DCM
ITLB
ITLU
SFD40
SFD40B
....................................................................................................................................................................................................................................
4-5
August 2011
....................................................................................................................................................................................................................................
SFD44
SFD44B
Note: To allow a customer to use these modules beyond the range of the electronic
inventory link, these modules can be also provisioned as unmanaged, indicating that
they are to be treated by the system as present without reading the electronic
inventory link.
Insertion or extraction of a module does not cause equipment faults to occur on other
equipment entities, except extraction of the FAN module may eventually cause equipment
temperature faults. However, extraction of a module may cause facility signal faults on
other modules.
Note: For PSS-32, once the fan is extracted, two minutes is the maximum
recommended time interval for fan replacement (one minute for PSS-16). Replacing
the fan unit may necessitate a database restore.
Manual restarts (reboot)
It is possible to reset a specified equipment entity or the entire NE. Different possible
levels of restart are:
Warm restart (a.k.a. soft reset and software reboot): Previous hardware state is
retained, and transmission is not affected.
Cold restart (a.k.a. hard reset, power cycle, and power-up): Hardware state is
completely reinitialized from scratch without reference to the previous state.
Transmission may be affected.
Note: Cold restart of a transmission-carrying pack kills traffic, and thus cold restart is
not allowed on an in-service pack. The pack must either be in maintenance state or
out-of-service as described below:
1. Put the pack (and ports) into maintenance state before performing the cold restart.
In maintenance state the cross connects can remain in place, and transmission is
still carried.
2. Perform a cold restart of the entire NE, instead of pack-by-pack. The TL1
command "INIT-SYS" allows this without individually changing all pack/port
admin states in the system -- if the user specifies the "forced" option. The CLI
command "config admin resetne" offers an equivalent to this "forced" option.
Manual restart can be applied individually to any of the following circuit pack types: EC,
LD, OSCT, CWR, OT, OPSA, SVAC, MVAC, (see Reboot card (p. 4-49)). Manual
restart of the entire NE performs restart of all of these circuit pack types (see Reboot
NE (p. 4-3)).
....................................................................................................................................................................................................................................
4-6
August 2011
....................................................................................................................................................................................................................................
Note: The following recommended procedures will avoid causing the wavelength
power directed towards the Line Out direction (egress of the node) from spiking when
the SVAC/MVAC is unpowered or cold reset.
The physical fiber patch cord to the C1 input of the SVAC/MVAC should be
disconnected prior to issuing a cold reset of the pack, and prior to removal of the
pack from the shelf.
The physical fiber patch cord to the C1 input of ALL the SVAC/MVAC packs
should be disconnected in a shelf that is to be cold reset.
should be disconnected prior to powering off the shelf containing the packs for an
extended period of time.
should be disconnected prior to power cycling or powering on the shelf containing
the packs.
Note: USRPNL, FAN, PF, SFC, SFD, ITLB, ITLU, and DCM have no processors and
cannot be restarted.
Mandatory equipment
Each shelf contains mandatory modules with which it must be equipped. Some of the
shelves can also be equipped with optional modules.
1830 PSS-32 and 1830 PSS-16
Mandatory equipment must be automatically provisioned whether present or not. Each

shelf includes the following mandatory equipment.
One shelf controller (EC) in either slot 1 or slot 18

Two power modules (PF)
A fan module (FAN)
User interface panel (USRPNL) mandatory on the main shelf only, and not allowed
on other shelves
Mandatory equipment is provisioned without AINS state (AINS = Automatic In Service,

which allows newly provisioned entities to be inserted at the later time without generating
alarms). See Automatic in-service (AINS) (p. 4-25). Therefore, if mandatory equipment
is not present it will be alarmed (assuming its absence is detected).
Note: Automatic provisioning of mandatory equipment differs from the
"auto-provisioning" defined for non-mandatory equipment. Mandatory equipment is
provisioned regardless of module presence detection. Non-mandatory equipment is
auto-provisioned only upon equipment detection and validation.
....................................................................................................................................................................................................................................
4-7
August 2011
....................................................................................................................................................................................................................................
1830 PSS-36
Mandatory equipment must be automatically provisioned whether present or not.

Mandatory equipment is provisioned without AINS state. Therefore, if mandatory
equipment is not present it will be alarmed if detected. Each shelf includes the following
mandatory equipment.
1 First Level Controller (FLC) only on a Master shelf in either slot 23 or slot 40. The
FLC is not allowed on Extension shelves.
1 matrix zero controller (MT0C) in either slot 11 or slot 15
2 bus termination cards (BTC)
2 power modules (PF)

1 fan module (FAN)
Equipment Controller (EC)
EC types are defined as follows:
Active EC - This EC is responsible for all run time EC operations in the system.
Standby EC - This EC is responsible for monitoring the operation of the Active EC,
access to all shared resources and for updating its own persistent storage.
Master EC - Any EC that is in a shelf with a shelf ID of one (see Shelf provisioning
(p. 4-25)). This shelf is defined as the Master shelf for the system.
Subtending EC - Any EC that is in a shelf with a shelf ID greater than one (see Shelf
provisioning (p. 4-25)). A shelf with a shelf ID greater than one is defined as a
subtending shelf.
Each shelf contains one Active EC. A standby EC is present if the shelf is redundant. If
the shelf ID is one, that shelf is designated as the Master shelf. The Active and Standby
ECs in the Master shelf are designated as Master ECs. There is always one and only one
Master shelf per node. This shelf will always contain an Active Master EC and
connectivity to the USRPNL. If the node has only one shelf, the Active Master EC
performs the functionality of both the Master and the Subtending EC. If the node consists
of multiple shelves, the Master shelf contains the Master EC and all subsequent shelves
contain Subtending ECs.
Note: The circuit pack hardware is identical for both the Master and Subtending EC.
Only the behavior of the pack changes based on the slot position and the shelf ID.
Note: For 1830 multi-shelf configuration, if one shelf is redundant, all shelves should
be redundant.
Note: Admin State for Ethernet ports cannot be independent. If a switch over from
active with Ethernet port Admin state enabled to standbywith Ethernet port Admin
state disabled, a loss of communication will occur. The admin state of Ethernet ports
must match.
....................................................................................................................................................................................................................................
4-8
August 2011
....................................................................................................................................................................................................................................
Important! One and only one shelf in each NE can have the role of Main Shelf. This
is designated by a backplane rotary dial setting of 0x81 (Shelf Role = Main Shelf,
Shelf ID = 1). When a new Universal shelf boots up and finds that its rotary dial is set
to 0x81, it automatically provisions itself with AID = SHELF-1. It automatically
provisions its shelf type according to its actual hardware: TL1 TYPEID =
UNV_SHELF_16 (if PSS-16), or UNV_SHELF (if PSS-32), or UNV_SHELF_36 (if
PSS-36). It then begins to perform the role of the main shelf. For details on how to
change the rotary dial, see Rotary dial backplane setting (p. 4-26).
The Master EC performs the following functions:
An EC behaves as a Master EC (either standby or active) if it detects that the shelf ID

is one.
The Active Master EC provides the external LAN interface for management of all
shelves in a multi-shelf node.
The Active Master EC terminates and or generates all communications with the
management system. This includes communications intended for the Subtending
shelves. It forwards information intended for a Subtending shelf to the proper EC.
The Active Master EC is responsible for maintenance of its persistent database and
configures all shelves and packs in the node using data in the persistent database.
The Active Master EC is responsible for maintaining the power state of all cards in
the same shelf and is responsible for monitoring voltage from the power filters in the
same shelf.
The Active Master EC monitors the health of all packs in the same shelf and monitors
the health of all shelves in the node.
The Standby Master EC is responsible for monitoring the operation of the Active EC,
access to all shared resources and for updating its own persistent storage.
Note: To replace the Active Master EC, it is necessary to switch the Active so it
becomes the Standby EC, and therefore can be replaced without disrupting the
system.
The Subtending EC is responsible for the following functions:
Any EC behaves as a Subtending EC (either standby or active) if it detects that the

shelf ID is any number greater than 1.
The Active Subtending EC is responsible for maintaining the power state of all cards
in the same shelf and is responsible for monitoring the voltage output from the power
filters in the same shelf.
The Active Subtending EC monitors the health of all packs in the same shelf and
forwards fault, and performance information to the Active Master EC
The Active Subtending EC monitors all services performed by a shelf and forwards
fault, and performance information to the Active Master EC
The Active Subtending EC coordinates all communication within a shelf and
communication to the Master shelf.
....................................................................................................................................................................................................................................
4-9
August 2011
....................................................................................................................................................................................................................................
The Active Subtending EC stores card application images in its local mass storage and
provides the application images from its mass storage unit to the cards in the same
shelf at boot time, if a card is reset or on request from the Master EC.
The Standby Subtending EC is responsible for monitoring the operation of the Active
EC, access to all shared resources, and for updating its own persistent storage.
Power Filter (PF) modules
Each Power Filter module is capable of sustaining the entire load of the system so that its
partner can be replaced upon failure without disrupting transmission. Each shelf has its
own power connections and is powered independently from the other shelves in the NE.
The shelf power and ground connectors are located at the front of the shelf coming into
the PF cards at the lower left and lower right of the shelf.
FAN modules
The shelf is cooled by four variable-speed fans. The fans are housed in a replaceable FAN
tray. The FAN tray contains the variable-speed fans and a controller, which communicates
with the active control card to control the FAN speed.
1830 PSS-36/PSS-32/PSS-16 supports the ability to control fan speed via the WebUI.
When the Fan module is selected in the WebUI equipment tree, the fan speed can be set to
the following values:
normal - automatic speed control
maximum - constant full speed (100% RPMs)
Non-mandatory equipment
For non-mandatory equipment, the following provisioning modes are defined:
Auto-provisioning, also referred to as Plug & Play, where the EC provisions a card
upon discovering it.
Pre-provisioning, where the slot is provisioned in advance of a card being inserted.
1830 PSS-36 universal slot(s) provisioning and validation
The supported packs and slot locations for a 1830 PSS-36 shelf are shown in Table 4-1,
1830 PSS-36 Circuit Pack Slot Allocation (p. 4-11)
....................................................................................................................................................................................................................................
4-10
August 2011
....................................................................................................................................................................................................................................
Table 4-1
Card

Description
Slot Location
Height / Number
of Slots
112SA1L
112G Single Port

Tunable Coherent
AnyRate
Transponder, XL
Band (1 client)
2-8, 12, 16-19
Full / 3
112SCA1
112G Single Port

Tunable Coherent
AnyRate Transponder
(1 client)
2-8, 12, 16-19
Full / 3
112SCX10
112G Single Port

Tunable Coherent
Mux Transponder (10
clients)
2-8, 12, 16-19
Full / 3
112SX10L
112G Single Port

Tunable Coherent
Mux Transponder, XL
Band (10 clients)
2-8, 12, 16-19
Full / 3
11DPE12
11G Dual Port

Pluggable GBE MUX
Transponder (12
clients)
2-10, 12-14, 16-21
Full / 1
11DPE12E
11G Dual Port

Pluggable GBE Mux
Transponder,
Enhanced (12 clients)
2-10, 12-14, 16-21
Full / 1
11DPM12
11G Dual Port

Pluggable Multirate
ADM Transponder
(12 clients)
2-10, 12-14, 16-21
Full / 1
11QPA4
11G Quad Port

Pluggable AnyRate
Transponder (4
clients)
2-10, 12-14, 16-21
Full / 1
11STAR1
11G Single Port

Tunable AnyRate
Transponder (1 client)
2-9, 12, 13, 16-21,

24-39
Half / 1
....................................................................................................................................................................................................................................
4-11
August 2011
....................................................................................................................................................................................................................................
Table 4-1
Card
Description
(continued)
Slot Location
Height / Number
of Slots
11STGE12
11G Single Port

Tunable GBE MUX
Transponder (12
clients)
2-10, 12-14, 16-21
Full / 1
11STMM10
11G Single Port

Tunable Multi-rate
MUX Transponder
(10 universal clients)
2-10, 12-14, 16-21
Full / 1
43STA1P
43G Single Port

Tunable AnyRate (1
client)
2-8, 12, 16-19
Full / 3
43SCX4
40G Single Port

Tunable Mux
Coherent (4 client)
2-8, 12, 16-19
Full / 3
43STX4
43G Single Port

Tunable MUX (4
clients)
2-8, 12, 16-19
Full / 3
43STX4P
43G Single Port

Tunable MUX with
P-DPSK (4 clients)
2-8, 12, 16-19
Full / 3
A2325A
+23 dBm output

power, 25 dB gain
optical amplifier with
mid-stage access
2-10, 12-14, 16-21
Full / 1
AHPHG/AHPLG
AHPHG (High Power

High Gain Line
Driver) or AHPLG
(High Power Low
Gain Line Driver)
2-10, 12-14, 16-21
Full / 1
AM2125A
+21 dBm output

power, 25 dB gain
mid-stage access
2-10, 12-14, 16-21
Full / 1
AM2125B
+21 dBm output

power, 25 dB gain
no mid-stage access
2-10, 12-14, 16-21
Full / 1
....................................................................................................................................................................................................................................
4-12
August 2011
....................................................................................................................................................................................................................................
Table 4-1
Card

Description
(continued)
Slot Location
Height / Number
of Slots
AM2318A
+23 dBm output

power, 18 dB gain
no mid-stage access
2-10, 12-14, 16-21
Full / 1
BTC
Bus Termination Card
42,43
Half / 1
CWR8
Colorless Wavelength
Router 44-channel
2-9, 12, 13, 16-20
Full / 2
CWR8-88
Router 88-channel
2-9, 12, 13, 16-20
Full / 2
EC
Equipment Controller
FAN
FAN
41
Full / 1
FLC
First Level Controller
23 or 40 Main shelf
only
Half / 1
MESH4
1x4 Splitter card with

optical amplifier
2-9, 12-14, 16-21
Full / 1
MT0C
Matrix Zero card
11 or 15
Full / 1
MVAC
Multiple port Variable

Attenuator Card
2-9, 12, 13, 16-21,

24-39
Half / 1
OPSA
Optical Protection
Switch card
2-9, 12, 13, 16-21,

24-39
Half / 1
PF
Power Filter
44, 45
Half / 1
RA2P
Raman Amplifier, 2
pumps
2-10, 12-14, 16-21
Full / 1
SVAC
Single port VOA card
2-9, 12, 13, 16-21,

24-39
Half / 1
USRPNL
User Interface Panel
WR8-88A
Wavelength Router
88-channel
2-9, 12, 13, 16-20
Full / 2
WTOCM
Wavelength Tracker
Optical Channel
Monitoring card
2-9, 12, 13, 16-21,

24-39
Half / 1
Half / 1
Full / 1
....................................................................................................................................................................................................................................
4-13
August 2011
....................................................................................................................................................................................................................................
Table 4-2
Card

Description
Slot Location
Height / Number
of Slots
112SA1L
112G Single Port

Tunable Coherent
AnyRate
Transponder, XL
Band (1 client)
2-15
Full / 3
112SCA1
112G Single Port

Tunable Coherent
AnyRate Transponder
(1 client)
2-15
Full / 3
112SCX10
112G Single Port

Tunable Coherent
Mux Transponder (10
clients)
2-15
Full / 3
112SX10L
112G Single Port

Tunable Coherent
Mux Transponder, XL
Band (10 clients)
2-15
Full / 3
11DPE12
11G Dual Port

Pluggable GBE MUX
Transponder (12
clients)
2-17
Full / 1
11DPE12E
11G Dual Port

Pluggable GBE Mux
Transponder,
2-17
Full / 1
11DPM12
11G Dual Port

Pluggable Multirate
ADM Transponder
(12 clients)
2-17
Full / 1
11QPA4
11G Quad Port

Pluggable AnyRate
Transponder (4
clients)
2-17
Full / 1
....................................................................................................................................................................................................................................
4-14
August 2011
....................................................................................................................................................................................................................................
Table 4-2
Card

Description
(continued)
Slot Location
Height / Number
of Slots
11STAR1
11G Single Port

Tunable AnyRate
2-17, 20-35
Half / 1
11STGE12
11G Single Port

Tunable GBE MUX
Transponder (12
clients)
2-17
Full / 1
11STMM10
11G Single Port

Tunable Multi-rate
MUX Transponder
2-17
Full / 1
43STA1P
43G Single Port

Tunable AnyRate (1
client)
2-15
Full / 3
43STX4
43G Single Port

Tunable MUX (4
clients)
2-15
Full / 3
43STX4P
43G Single Port

Tunable MUX with
P-DPSK (4 clients)
2-15
Full / 3
4DPA2
4G Dual Port
Pluggable AnyRate (2
clients)
2-17, 20-35
Half / 1
4DPA4
4G Dual Port
clients)
2-17, 20-35
Half / 1
A2325A
+23 dBm output

power, 25 dB gain
mid-stage access
2-17
Full / 1
....................................................................................................................................................................................................................................
4-15
August 2011
....................................................................................................................................................................................................................................
Table 4-2
Card
Description
(continued)
Slot Location
Height / Number
of Slots
AHPHG/AHPLG/
ALPHG
AHPHG (High Power

High Gain Line
Driver) or AHPLG
(High Power Low
Gain Line Driver) or
ALPHG (Low Power
High Gain Line
Driver)
2-17
Full / 1
ALPFGT
Low Power Fixed

Gain Line Driver
2-17, 20-35
Half / 1
AM2017B
High power (+20

dBm), low gain
no mid-stage access
2-17
Full / 1
AM2125A
+21 dBm output

power, 25 dB gain
mid-stage access
2-17
Full / 1
AM2125B
+21 dBm output

power, 25 dB gain
no mid-stage access
2-17
Full / 1
AM2318A
+23 dBm output

power, 18 dB gain
no mid-stage access
2-17
Full / 1
AM2325B
+23 dBm output

power, 25 dB gain
no mid-stage access
2-17
Full / 1
CWR8
Router 44-channel
2-16
Full / 2
CWR8-88
Router 88-channel
2-16
Full / 2
EC
1, 18
Half / 1
FAN
FAN
37
Full / 1
....................................................................................................................................................................................................................................
4-16
August 2011
....................................................................................................................................................................................................................................
Table 4-2
Card

Description
(continued)
Slot Location
Height / Number
of Slots
MESH4
1x4 Splitter card with

optical amplifier
2-17
Full / 1
OPSA
Optical Protection
Switch card
2-17, 20-35
Half / 1
OSCT
OSCT card
2-17, 20-35
Half / 1
PF
Power Filter
19, 36
Half / 1
RA2P
Raman Amplifier, 2
pumps
2-17
Full / 1
SFC2
2 channel static
CWDM filter
2-17, 20-35
Half / 1
SFC4
4 channel static
CWDM filter
2-17, 20-35
Half / 1
SFC8
8 channel static
CWDM filter
2-17
Full / 1
SFD5
5 channel static
DWDM filter
2-17, 20-35
Half / 1
SFD8
8 channel static
DWDM filter
2-17
Full / 1
SVAC
2-17, 20-35
Half / 1
MVAC

Attenuator Card
2-17, 20-35
Half / 1
USRPNL
40
Full / 1
WR8-88A
Wavelength Router
88-channel
2-16
Full / 2
WTOCM
Wavelength Tracker
Optical Channel
Monitoring card
2-17, 20-35
Half / 1
Slots 2-17 and 20-35 of a PSS shelf are considered universal slots (i.e., installation of any
Alcatel-Lucent 1830 PSS DWDM circuit pack is permitted) and any inserted circuit pack
is auto-provisioned.
If a single-slot card is inserted in a slot provisioned for a different type of single-slot card,
a mismatch is declared, causing a state transition against the provisioned card. Likewise
for a multi-slot card inserted into the same slots already provisioned for a different type of
multi-slot card of the same height and width.
....................................................................................................................................................................................................................................
4-17
August 2011
....................................................................................................................................................................................................................................
If a single-slot card is inserted in one of the slots provisioned for a multi-slot card, the
following changes occur:
If the single-slot card is inserted in the slot acting as reference for the multi-slot card,
a mismatch is declared, causing a state transition against the provisioned card.
If the single-slot card is inserted in the slot different from the one acting as reference
for the multi-slot card, a mismatch is declared, causing a state transition against the
slot entity for the slot of the inserted card
If more than one card is inserted in slots provisioned for the multi-slot card, the net
result in terms of state changes is the pure sum of the results for each card inserted.
If a multi-slot card is inserted into the NE and one of the slots is already provisioned for
another single-slot or multi-slot card, the following changes occur.
If the slot acting as reference for the plugged multi-slot card is also acting as reference
for a provisioned card, a mismatch is declared, causing a state transition against the
provisioned card.
If the slot acting as reference for the plugged multi-slot card is not also acting as
reference for a provisioned card, a mismatch is declared, causing a state transition
against the slot entity for the reference slot of the inserted card.
Note: For a selected slot, if a card is present (i.e. not empty) but not provisioned, the
WebUI will pre-populate the Provisioned Type attribute with the present card type.
The user can select a different card type from the pick list.
Table 4-3
Card

Description
Slot Location
Height / Number
of Slots
11DPE12
11G Dual Port

Pluggable GBE MUX
Transponder (12
clients)
3-9
Full / 1
11DPE12E
11G Dual Port

Pluggable GBE Mux
Transponder,
3-9
Full / 1
....................................................................................................................................................................................................................................
4-18
August 2011
....................................................................................................................................................................................................................................
Table 4-3
Card
Description
(continued)
Slot Location
Height / Number
of Slots
11DPM12
11G Dual Port

Pluggable Multirate
ADM Transponder
(12 clients)
3-9
Full / 1
11QPA4
11G Quad Port

Pluggable AnyRate
Transponder (4
clients)
3-9
Full / 1
11STAR1
11G Single Port

Tunable AnyRate
3-9, 13-19
Half / 1
11STGE12
11G Single Port

Tunable GBE MUX
Transponder (12
clients)
3-9
Full / 1
11STMM10
11G Single Port

Tunable Multi-rate
MUX Transponder
3-9
Full / 1
4DPA2
4G Dual Port
clients)
3-9, 13-19
Half / 1
4DPA4
4G Dual Port
clients)
3-9, 13-19
Half / 1
A2325A
+23 dBm output

power, 25 dB gain
mid-stage access
3-9
Full / 1
AHPHG/AHPLG/
ALPHG
AHPHG (High Power

High Gain Line
Driver) or AHPLG
(High Power Low
Gain Line Driver) or
ALPHG (Low Power
High Gain Line
Driver)
3-9
Full / 1
....................................................................................................................................................................................................................................
4-19
August 2011
....................................................................................................................................................................................................................................
Table 4-3
Card

Description
(continued)
Slot Location
Height / Number
of Slots
ALPFGT
Low Power Fixed

Gain Line Driver
3-9, 13-19
Half / 1
AM2017B
High power (+20

dBm), low gain
no mid-stage access
3-9
Full / 1
AM2125A
+21 dBm output

power, 25 dB gain
mid-stage access
3-9
Full / 1
AM2125B
+21 dBm output

power, 25 dB gain
no mid-stage access
3-9
Full / 1
AM2318A
+23 dBm output

power, 18 dB gain
no mid-stage access
3-9
Full / 1
AM2325B
+23 dBm output

power, 25 dB gain
no mid-stage access
3-9
Full / 1
EC
2, 12
Half / 1
FAN
FAN
21
Full / 1
OPSA
Optical Protection
Switch card
3-9, 13-19
Half / 1
OSCT
OSCT card
3-9, 13-19
Half / 1
PF
Power Filter
1, 11
Half / 1
RA2P
Raman Amplifier, 2
pumps
7-9
Full / 1
SFC2
2 channel static
CWDM filter
3-9, 13-19
Half / 1
SFC4
4 channel static
CWDM filter
3-9, 13-19
Half / 1
SFC8
8 channel static
CWDM filter
3-9
Full / 1
....................................................................................................................................................................................................................................
4-20
August 2011
....................................................................................................................................................................................................................................
Table 4-3
Card

Description
(continued)
Slot Location
Height / Number
of Slots
SFD5
5 channel static
DWDM filter
3-9, 13-19
Half / 1
SFD8
8 channel static
DWDM filter
3-9
Full / 1
SVAC
3-9, 13-19
Half / 1
MVAC

Attenuator Card
3-9, 13-19
Half / 1
USRPNL
10
Full / 1
WTOCM
Wavelength Tracker
Optical Channel
Monitoring card
3-9, 13-19
Half / 1
Provisioning hierarchy
Objects must be provisioned in order from higher level to lower level according to the
following hierarchy:
Shelf
Circuit pack
Port/facility, including SFP/XFP if applicable
Optical fiber connection
Photonic cross connection
Equipment states
The NE supports equipment Primary State (PST) values as described below:
IS (IS-NR or IS-ANR) to indicate that the provisioned equipment entity is in

in-service state. IS-NR is normal. IS-ANR is abnormal, but with no
autonomous/management events.
OOS-AU to indicate that the provisioned equipment entity is in out-of-service state

caused solely by an autonomous event.
OOS-MA to indicate that the equipment entity is in out-of-service state caused solely
by a management event.
OOS-AUMA to indicate that the equipment entity is in out-of-service state caused by
both an autonomous event and a management event.
OOS-[AU]MA, MT to indicate that the equipment entity is in maintenance state.
....................................................................................................................................................................................................................................
4-21
August 2011
....................................................................................................................................................................................................................................
The NE supports equipment Secondary State (SST) values as described below to indicate
the cause for being in a particular PST:
FLT to indicate that a failure is detected pertaining to the equipment entity.

UEQ to indicate that the equipment entity is not present in the system.
MEA to indicate that the equipment entity physically present in the system is invalid
(the inserted module is inconsistent with slot provisioning data or the inserted module
is of incompatible revision).
UAS to indicate that the equipment entity is not provisioned.
AINS to indicate that the equipment is waiting for the correction of the off-normal
condition (UEQ). Alarms will not be generated for the entity if AINS is present.
MT to indicate maintenance state.
The NE supports SST values as described below to provide additional state information.
ACT to indicate the active EC in equipment protection.

NBK to indicate no backup for EC in equipment protection.
STBY to indicate the standby EC in equipment protection.

WKG to indicate the working EC in equipment protection.
Equipment state transitions
States can be nested if they share common behavior with minor differences. Transitions
can originate and terminate from either a parent state or a child state. Transitions
originating from a parent state apply to all of its child states. The following defines four
major administrative parent states:
Unassigned State: An entity is unassigned when provisioning for it does not exist,
either because it was never provisioned, or because it was deleted.
Admin Out-of-Service State: A provisioned entity can be configured out-of-service.
In this state a card does not provide service, but does perform fault monitoring (results
of which can be retrieved). It does not generate alarms or conditions. A card cannot be
put in this state if any of its ports are admin in-service.
Admin In-Service State: A provisioned entity can be configured in-service. In this
state a card provides service, performs fault monitoring, and generates alarms and
conditions.
Admin Maintenance State: A provisioned entity can be configured in maintenance
to perform a temporary maintenance activity on it. In this state a card continues to
provide service and performs fault monitoring (results of which can be retrieved). But
it does not generate alarms or conditions. A card cannot be put in this state if any of its
ports are admin in-service.
....................................................................................................................................................................................................................................
4-22
August 2011
....................................................................................................................................................................................................................................
State transitions are determined by user operations and autonomous system processing
(e.g. fault detection). A user can perform the following operations on equipment entities:
Enter/Delete provisioning.
Edit provisioned parameter values.
Modify administrative state (logically remove or logically restore the entity).
Physically insert or physically remove the entity.
The same equipment state machine covers all modules. But for mandatory modules, some
states and transitions do not apply, due to the following rules:
Mandatory modules are automatically provisioned upon shelf creation, whether

present or not.
Mandatory modules are automatically configured to IS (in-service) upon insertion.
Mandatory modules cannot be configured to OOS (out-of-service).
Mandatory modules cannot be deleted.
Service affecting (SA) / Non-service affecting (NSA) conditions
When an equipment condition is defined as having the possibility to be either

service-affecting (SA) or non-service affecting (NSA), the following requirements apply:
An equipment condition is SA if the equipment has supported facilities below it, and
for any of its supported facilities a LOS would be service affecting.
An equipment condition is NSA if the equipment has no supported facilities below it,
and for any of its supported facilities a LOS would not be service affecting.
When an equipment condition on protected or redundant equipment is defined as having

the possibility to be either SA or NSA, the following requirements apply:
An equipment condition is SA if the protecting/redundant equipment is not IS.

An equipment condition is NSA if the protecting/redundant equipment is IS.
Equipment provisioning changes
The system supports the ability to modify the provisioned data associated with an
equipment entity. The modifications take effect immediately. This capability allows the
Primary State (PST) and Secondary State (SST) parameters to be modified for all
equipment entities except shelves and mandatory equipment. The user is able to perform
the following equipment state changes:
To administrative maintenance state

To administrative out-of-service state
To administrative in-service state
....................................................................................................................................................................................................................................
4-23
August 2011
....................................................................................................................................................................................................................................
The following system-level equipment parameters can be modified:
System SONET/SDH operation mode. This affects system-wide naming of cards and
ports. It affects the content of alarm and event text. When the mode is changed, PM is
restarted with cleared counters, new PM names, and new TCA defaults. Byte filtering
changes to conform to the specified standard. The NE clears its database and clears all
services.
Note: When switching between SDH or SONET mode, the user needs to hard reboot
(cold reset) the LC packs.
System default AINS timer value. This applies to all ports that do not have an
individual port-level AINS timer provisioned.
Deprovisioning
The following applies to deprovisioning equipment:
A Delete Equipment command is supported to delete provisioned equipment.

Deletion of an equipment entity is not allowed if that entity is not logically removed.
Deletion of mandatory equipment in a PSS shelf is not allowed: (i.e., PF, FAN,
USRPNL, active EC, FLC, MT0C, BTC).
Deletion of a PSS shelf is not allowed if it contains any provisioned modules (except
mandatory equipment).
Deprovisioning procedures on an entity do not cause equipment faults on other
equipment entities.
Pre-provisioning
A user can pre-provision any empty slot in a PSS shelf which supports non-mandatory
modules for a specific equipment type. The pre-provisioning must take into account
module height and width, and will fail if an already-assigned or invalid slot is used.
Pre-provisioning requires that the network element be equipped with a control card only.
All of the other components, including additional shelves, are assigned slots or locations
to create a virtual configuration that can be implemented at a later time. You can use all of
the provisioning commands to pre-provision a network element, including those used for
service provisioning.
Modules inserted in a pre-provisioned slot have their state determined by module fault
status, module mismatch status (comparison of actual type and pre-provisioned type), and
operator-provisioned PST value.
Note: It is possible to pre-provision equipment by downloading and activating a
previously stored database.
....................................................................................................................................................................................................................................
4-24
August 2011
....................................................................................................................................................................................................................................
Automatic in-service (AINS)
The pre-provisioning command includes specification of an AINS state value to

determine whether a card missing alarm should be generated immediately for the empty
slot, or whether no alarm should be generated until after a card is plugged into the slot for
the first time. If AINS is enabled, all alarms are suppressed for the entity while it is not
present. When the card is inserted in the shelf, the card and ports on the card that are
configured AINS are automatically set up.
For cards, AINS is automatically removed when the pre-configured card type is inserted
in the shelf. For ports, AINS remains in effect while there are alarms on the port, and for a
configurable period of time after the port is alarm free.
Auto-provisioning
Auto-provisioning, also referred to as Plug & Play, means that new non-mandatory
equipment is detected and configured automatically upon card insertion (or controller
restart), if allowed in that location, and if there is no conflict (mismatch) with other
provisioning. Auto-provisioned modules have their initial state determined by module
fault status.
Note: If a card is deleted when it is still physically present, it will not be
rediscovered and auto-provisioned until it is physically removed and reinserted, or
until the system reboots (whichever comes first).
Shelf provisioning
Overview
Ten types of shelves are supported. These shelves are 1830 PSS-36, 1830 PSS-32, 1830
PSS-16, SFD40, SFD40B, SFD44, SFD44B, ITLB, ITLU, and DCM. The maximum
number of shelves cannot be exceeded. The maximum number of 1830 PSS-32 Universal
shelves is 24, the maximum number of 1830 PSS-16 Universal shelves is 1, and the
maximum number of DCM/SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU shelves is 40.
....................................................................................................................................................................................................................................
4-25
August 2011
Shelf provisioning
....................................................................................................................................................................................................................................
Table 4-4, 1830 PSS Shelf Combinations (p. 4-26) lists the combinations of PSS-36,
PSS-32 and PSS-16 shelves that are supported in a single NE.
Table 4-4
1830 PSS Shelf Combinations
Main Shelf Type
PSS-36
Subtending
Universal Shelf
Type
Number of
Subtending
Universal Shelves
Non-Universal
Shelf Types
PSS-36 only
0 to 3 PSS-36 shelves
DCM
ITLB, ITLU
SFD44, SFD44B
PSS-36 and PSS-32

mix
0 to 23 PSS-32
shelves
DCM
0 to 2 PSS-36 shelves
SFD40, SFD40B,
SFD44, SFD44B
Maximum 23
combined
PSS-32
PSS-32 only
0 to 23 PSS-32
shelves
ITLB, ITLU
DCM
ITLB, ITLU
SFD40, SFD40B,
SFD44, SFD44B
PSS-16
PSS-32 only
0 to 23 PSS-32
shelves
DCM
ITLB, ITLU
SFD40, SFD40B,
SFD44, SFD44B
Important! Alcatel-Lucent 1830 PSS requires that filler blanks be used in all un-used
slots in a shelf to ensure proper airflow and cooling.
PSS shelf
Rotary dial backplane setting
On each PSS shelf, a shelf ID number and a shelf role can be set via a physical
mechanism (rotary dial) on the backplane. Up to 8 bits of information can be set. The
rotary dial for each shelf must be set to a valid value, and the value must be unique within
the same NE.
The values of the rotary dial are interpreted as follows:
Bits 4-3-2-1-0 code the shelf ID number, an integer in the range 1-24.
Bit 7 (the most significant bit), codes the shelf role according to the following rule:
Bit 7 = zero: Shelf Role = Not-Main Shelf
Bit 7 = one: Shelf Role = Main Shelf
....................................................................................................................................................................................................................................
4-26
August 2011
Shelf provisioning
....................................................................................................................................................................................................................................
Note: Bits 6-5 of the register must be set to 0 (zero).

If any new shelf begins to boot with an invalid or non-unique rotary dial setting, it is
prevented from completing initialization, and it is not assigned an AID. A system
PRCDRERR alarm is raised (if the main shelf is operational). The new shelf begins
blinking all its LEDs and continues until the situation is resolved.
Note: The rotary dial must not be changed after the shelf has been discovered by the
system.
Important! A unique shelf ID is required for each shelf.
Main shelf
One and only one shelf in each NE can have the role of Main shelf. This is designated by
a backplane rotary dial setting of 0x81 (Shelf Role = Main Shelf, Shelf ID = 1). When a
new PSS-32 shelf boots up and finds that its rotary dial is set to 0x81, it automatically
provisions itself with AID = SHELF-1 and TYPEID = UNV. It then begins to perform the
role of the main shelf.
Note: Two main shelves (i.e. two NEs) cannot be connected by internal LAN cable as
if they belonged to a single NE (i.e., as if one was subordinate to the other).
Not-Main shelf
A Not-Main shelf is pre-provisioned by user command specifying a unique Shelf AID and
specifying TYPEID = UNV. The shelf number of the Shelf AID should be set equal to the
expected rotary dial setting. For example, if the pre-provisioned AID is SHELF-3, the
shelf is expected to have a rotary dial setting of 0x03.
A shelf AINS mode parameter can be set to prevent immediate loss of communication
alarming against a newly pre-provisioned shelf.
When a new Not-Main shelf (with valid and unique rotary dial setting) is detected by the
system (by internal LAN discovery), it is checked against current pre-provisioned shelf
definitions. If a match is found, the new shelf is assigned the pre-provisioned shelf AID.
Match is defined as follows.
The shelf number of the pre-provisioned shelf AID must be equal to the actual value
read from the rotary dial, and the pre-provisioned shelf TYPEID value must be UNV.
When a newly detected not-main shelf (with valid and unique rotary dial setting) does not
match any pre-provisioned definition, it is auto-provisioned. The shelf number of the
shelf AID is automatically assigned the actual value read from the rotary dial. The
TYPEID is automatically set to UNV.
Note: Main shelves cannot be auto-provisioned, but Not-Main shelves can be
pre-provisioned and can be auto-provisioned.
....................................................................................................................................................................................................................................
4-27
August 2011
Shelf provisioning
....................................................................................................................................................................................................................................
SFD40, SFD40B, SFD44, SFD44B, ITLB, ITLU, and DCM shelf
SFDs multiplex and de-multiplex optical channel signals.The SFD40 100GHz Channel
Spacing Optical Multiplexer/Demultiplexer and the SFD40B with 50GHz frequency shift
are used to multiplex and to demultiplex forty optical channels in the C-Band. The SFD44
and SFD44B are passive standalone rack-mounted devices that are not slot-resident. The
SFD has an optical line-level interface to an ITLB, ITLU, or CWR circuit pack (or an LD,
in the case of an end terminal node). The SFD44 is modeled by the system as a shelf of
type SFD44, with one fixed slot containing a card of type SFD44. The SFD44B is
modeled by the system as a shelf of type SFD44B, with one fixed slot containing a
card of type SFD44B.
The ITLB/ITLU is designed to be used in combination with the SFD44 and SFD44B. The
ITLB/ITLU combines and de-muxes the odd and even sets of signals into a single group
of 88-channel group of signals with 50GHz spacing. The ITLB/ITLU is modeled by the
system as a shelf of type ITLB/ITLU, with one fixed slot containing a card of type
ITLB/ITLU.
DCM is a passive rack-mounted device that is not slot-resident. The DCM is modeled as a
shelf of type DCM, with one fixed slot containing a card of type DCM. There are 3
different sizes of DCM. Up to 16 DCMs (depending on size) can reside together in a
shelf-like housing with no backplane. DCMs provide optical line-level dispersion
compensation to LD or OSCT circuit packs. There are SMF, LEAF, and TWRS fiber
types for the DCM modules. The NE supports a fibertype attribute for DCMs to allow the
user to provision or have the NE auto provision the type (if inventoried).
Any provisioning of a new SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf
automatically provisions the contained
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM card. Deprovisioning an
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf automatically de-provisions
(deletes) the SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM card, and this is the
only way to delete an SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM card.
SFD40/SFD40B/SFD44/SFD44B/ITLB/DCM shelves have no rotary dial mechanism.
Instead, each SFD40/SFD40B/SFD44/SFD44B/ITLB/DCM shelf is identified by a
unique serial number which is stored on the RI EEPROM, and is also externally visible
on the equipment label.
Transmission association
The transmission association between an

SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM and the optical line equipment it
supports is defined solely by a topology fiber assignment between
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM and CWR (or LD or OSCT, in an
end terminal node). The transmission association and the management association must
agree; they must have the same modules as endpoints.
....................................................................................................................................................................................................................................
4-28
August 2011
Shelf provisioning
....................................................................................................................................................................................................................................
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM remote inventory data is retrieved

electronically by a CWR, LD, or OSCT pack; this is the only management access to the
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM. The first reading of
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM electronic inventory is treated as
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM detection, and this defines an
internal management association between an
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM and a CWR, LD, or OSCT. The
system must internally map the SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM AID
to the CWR, LD, or OSCT via which the
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM was first detected. This allows
subsequent data retrieval against an SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM
AID to be directed internally to the correct CWR, LD, or OSCT.
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelves can be pre-provisioned and
can be auto-provisioned. An SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf is
pre-provisioned by user command specifying a unique Shelf AID, specifying
TYPEID=SFD44/DCM, and (optionally) specifying a unique PROVSERNUM value
equal to the expected SFD/DCM serial number. This allows checking for connection of
the correct SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM.
Matching pre-provisioned values
When a new SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf is detected by the

system (by electrical inventory discovery), it is checked against current pre-provisioned
shelf definitions. If a match is found, the new shelf is assigned the pre-provisioned AID.
If there is more than one match, the one with the lowest pre-provisioned AID is used.
Match is defined as follows.
If Serial Number was pre-provisioned with a non-default value: The actual

SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM serial number must be equal to
the Serial Number value. The actual shelf type must equal the pre-provisioned
TYPEID value.
If Serial Number was pre-provisioned with the default value (i.e. has not yet been
specified): The actual shelf type must equal the pre-provisioned TYPEID value. In
this case, Serial Number is now automatically assigned the actual serial number read
from the SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM.
When a newly detected SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf does

not match any pre-provisioned definition, it is auto-provisioned. It is automatically
assigned the lowest available shelf AID. The serial number is automatically assigned the
actual serial number read from the SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM.
The TYPEID is automatically assigned the actual shelf type.
Note: The Serial Number value can be modified by the user whenever needed. For
example, when an SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM is physically
replaced without deletion of its provisioning, Serial Number must be changed from
the old serial number to the new one.
....................................................................................................................................................................................................................................
4-29
August 2011
....................................................................................................................................................................................................................................

Before you begin
The WebUI supports creation (pre-provisioning) for all shelves, except the main shelf (see
Shelf provisioning (p. 4-25)).
Create (pre-provision) a shelf
...................................................................................................................................................................................................
From the WebUI, select System > Create Shelf.

Result: The Create Shelf screen is displayed.
...................................................................................................................................................................................................
Enter shelf parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
View / modify shelf properties
Note: There are restrictions on which shelves and parameters can be modified.
...................................................................................................................................................................................................
Select the shelf from the equipment tree and select the Provision/Info function.
Result: The Shelf Properties screen is displayed.
...................................................................................................................................................................................................
Modify applicable parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
Delete a shelf
Note: The main shelf cannot be deleted.

...................................................................................................................................................................................................
Select the shelf from the equipment tree and click Delete.
Note: For an 1830 PSS-36 shelf, all cards except the active FLC, MT0C, BTC, FAN,
and PF must be manually deleted before a shelf can be deleted.
For an 1830 PSS-32 and 1830 PSS-16 shelf, all cards except the active EC, FAN,
USRPNL, and PF must be manually deleted before a shelf can be deleted.
....................................................................................................................................................................................................................................
4-30
August 2011
....................................................................................................................................................................................................................................
For SFD40, SFD40B, SFD44, SFD44B, ITLB, and ITLU shelves, the card is
automatically deleted by the NE when the shelf is deleted. The card must be in a valid
state for deletion before the shelf can be deleted.
E...................................................................................................................................................................................................
N D O F S T E P S
Test LEDs
...................................................................................................................................................................................................
Select the PSS shelf from the equipment tree and select the Test/Analysis function.
Result: The Shelf LEDs screen is displayed.
...................................................................................................................................................................................................
Select Test LEDs and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
4DPA2 OT
The 4DPA2 is a half-height, single-wide dual transponder that has two client ports with
SFP optics directly associated with two line ports. It also supports a single E-SNCP
protection group, which uses both line ports to protect one of the two client ports. With
E-SNCP only one client port is supported. The 4DPA2 is an optimized version of the
4DPA4 for application in the 1830 PSS-16.
The following client signals are supported:
OC48/STM16
1GbE
4DPA4 OT
The 4DPA4 OT, sometimes referred to as the MSC (Multi-Service Card), is a half-height,
single-wide card that accepts up to four client signals via SFP optics, and performs
non-blocking multiplexing into one or both line ports. It has dual pluggable OTU1 line
ports that support B&W, CWDM, or DWDM line signals, and supports a variety of
sub-ODU1 client signals with extremely flexible transponder mappings.
There are four pluggable client interfaces: two at the top, and two at the bottom. The
middle of the faceplate has sockets for the dual line interfaces: two eVOA SFPs and two
line port SFPs. Line transmit fibers are externally connected through the eVOA ports for
Wavetracker functionality. There is a pack status LED in the upper right corner of the
....................................................................................................................................................................................................................................
4-31
August 2011
....................................................................................................................................................................................................................................
faceplate. Each port has a dedicated port status LED, and each port also has a second
LED. The second LED is used on client ports is used to indicate dynamic Ethernet
activity, and is not used on line ports and eVOA ports.
Two card mode values are supported for 4DPA4: DualTran and FlexMux. The "Card
Mode" parameter determines the feature type of the 4DPA4 main firmware image. It
affects many fundamental aspects of card and port behavior, including:
Which client signal types are supported.

Which client ports can be used.
Which user interface commands apply.

Whether line ports are created manually or automatically.
How client ports are mapped to line ports.
Whether or not timeslots exist on the line ports.
How the near-end node reads LosProp data sent by the far-end node.
Whether or not E-SNCP protection is supported.
Provisioning the cardmode parameter is allowed only when there are no connections and
all ports are unassigned. Otherwise it is denied. As with other parameters, cardmode can
be provisioned on a card that is physically present, physically absent, or pre-provisioned.
Note: Changing the cardmode automatically clears any non-default provisioning of
firmware release (package identifier), and automatically triggers a cold restart of the
card to download the default version of the firmware line corresponding to the new
cardmode.
DualTran card mode
When cardmode=DualTran, FC400 is the only client signal type supported. Client ports
C1 and C3 can be used, but C2 and C4 cannot be used. Provisioning of C2 and C4 are
denied. FC400 commands apply to 4DPA4 only in this card mode. TL1 and CLI
commands specific to other client signal types are denied. Line ports are created
automatically. ODU1 commands are denied. Timeslots do not exist, and E-SNCP
protection is not supported.
When cardmode=DualTran, client port parameters and line port parameters behave or
apply as appropriate for the Dual Transponder FC400 feature. Examples: OPRMODE,
OTURATE, and FCMODE parameters have different values in FC400 image.
OPRMODE is read-only. TS, NETSMAP, FETSMAP, PLDTYPE, and ODU0INTERWK
parameters do not apply. Parameters specific to SONET, SDH, or 1GBE do not apply.
FlexMux card mode
When cardmode=FlexMux, all client signal types are supported except FC400. All four
client ports can be used. TL1 and CLI command specific to FC400 are denied. Line ports
are created manually. ODU1 commands apply. Timeslots exist to flexibly assign line port
....................................................................................................................................................................................................................................
4-32
August 2011
....................................................................................................................................................................................................................................
bandwidth for sub-ODU1 clients. E-SNCP protection is available. When

cardmode=FlexMux, client port parameters and line port parameters behave or apply as
appropriate for the Flexible Mux feature.
11DPE12(E) OT
The 11DPE12 and 11DPE12E (enhanced) are 12xGbE MUX OT cards, providing an
Ethernet multiplexing platform that aggregates up to twelve full-rate GbE client services
onto two 10G paths, supported by pluggable B&W/CWDM/DWDM line-side optics.
The 11DPE12(E) transponder is a single slot wide, full height card supporting a mix of 12
Ethernet interfaces and two 10G line interfaces. The 11DPE12 is also the foundation of
the Alcatel-Lucent PSS-1 GBEH device. Its use in the 1830 PSS-36/PSS-32/PSS-16
allows for complete interworking between platforms.
Note: The 11DPE12E contains major enhancements including a more sophisticated
switch device which enables advanced features such as Ethernet OAM, Provider
Bridging, Ethernet Ring Protection, and SyncE.
The 11DPE12(E) card supports the following features:
Supports FullRate, SubRate, QinQ operational mode

Note: 11DPE12E only supports QinQ operational mode
Full 88 channel C-band DWDM support
Terminal loopback and facility loopback
Supports E-SNCP protection in QinQ mode

Note: For 11DPE12 QinQ mode, packet loss occurs when traffic load is 100%.
Therefore, keep the client ingress bandwidth less than 95%.
Note: When the card Operational Mode = FullRate or QinQ, a client port is associated
with both line ports by E-SNCP protection group creation
The supported values for Direction are dependent on the card Operational Mode.
For SubRate mode, Direction = Bidirectional

For QinQ mode, Direction = Unidirectional
If the 11DPE12(E) card has an E-SNCP protection group provisioned, modifying the
Operational Mode from FullRate to SubRate or QinQ is not allowed.
Note: For the 11DPE12E card, the WebUI will display an object with the label MEP
under the card. This object will represent all MEPs (Maintenance End Points) for the
port.
....................................................................................................................................................................................................................................
4-33
August 2011
....................................................................................................................................................................................................................................
Maintenance endpont (MEP) alarm functions
TheWebUI supports MEPs for the 11DPE12E card. TheWebUI displays a list of all active
alarms for all MEPs on the selected card. The user can select a MEP and then display a
list of condition types that are applicable to the selected MEP. A refresh button is provided
so that the user can refresh the alarm list.
11DPM12 OT
The 11DPM12 transponder is a single slot wide, full height card supporting dual
pluggable line ports with flexible any-rate client signal aggregation and add/drop. With
two line ports and flexible traffic configuration, the 11DPM12 OT can provide ADM on a
blade and E-SNCP functionalities. All client signals can be transported in a bit-transparent
or character-transparent manner over OTN.
The 11DPM12 card supports the following features:
Twelve client interfaces with B&W or CWDM pluggable optics (SFPs)
Support for the following client interfaces: OC3/STM1, OC12/STM4, OTU-1

(G.709), 1Gb Ethernet, FC100/FICON, FC-200/FICON_Express,
FC400/FICON_Express4, Optical HD-SDI, Optical 3G-SDI, SD-SDI
Any service on any client port
Independent service level switching between two line ports for all types of supported
signals
Independent port level add/drop switching between any line port and any client port
Full-rate non-blocking muxing capacity into line ports: 9xGbE, 10xFC100, 5x FC200,
2x FC400, 12x OC3/STM1, 12x OC12/ STM4, 3x 3G-SDI, 6x HD-SDI 6x SD-SDI,
12xFE, 4xOTU1, 4xOC48
Two OTU2 line ports (10.709Gbps, provisionable) with EFEC (G.975.1 I.4) and RS
FEC (G.709), supported by CWDM or DWDM pluggable optics (XFPs) and tunable
DWDM XFP. DWDM XFPs DTV control function is supported at both line ports
Wavelength Tracker encoding on line-side transmit, by separate pluggable modules on
the faceplate. (Each line has a dedicated SFP VOA that supports slow eVOA for
attenuation and fast eVOA as Wavelength Tracker.)
11QPA4 OT
The 11QPA4 is a 10G, Quad port, any rate module with four client interfaces. This
module supports four independent multi-rate 10G channels. The 11QPA4A is the
temperature hardened version of this module.
The 11QPA4(A) has four pluggable client interfaces (C1, C2, C3, and C4), four pluggable
line interfaces (L1, L2, L3 and L4) and four VOA sockets (VA1, VA2, VA3 and VA4).
The pack has a status LED, but does not support status LEDs for the optical ports and
VOA ports due to physical limitations on the faceplate, but the WEBUI does support LED
status for all ports.
....................................................................................................................................................................................................................................
4-34
August 2011
....................................................................................................................................................................................................................................
The 10G pluggable line port of the 11QPA4(A) supports 88 channels when configured
with a tunable XFP. When configured with a fixed channel XFP, only 44 even channels
are supported. Fixed odd channel XFPs are not supported. The fixed channel XFPs
supported on these line ports are not wavelength locked, therefore traffic from these XFPs
may only traverse 100 GHz systems.
The 11QPA4 transponder supports four independent Multi-rate 10G channels and an 8G
Fibre channel. The following client signals are supported.
OTU2
STM-64, OC-192
10GbE WAN PHY
10GbE LAN PHY
8G Fibre Channel
The 11QPA4 and the hardened 11QPA4A support the following operational modes:
ADD_DROP mode.
In this mode, the circuit pack is processing signal in both transmission directions
(ingress, from client port towards the line side, from line side to client port). The
board supports C1 to L1 ADD_DROP. The board supports C2 to L2 ADD_DROP.
The board supports C3 to L3 ADD_DROP. The board supports C4 to L4
ADD_DROP.
CrossRegen mode
In this mode, the Line port input signal is looped towards another line port output
through 8x8 matrix. The client XFP is not necessarily provisioned or equipped, and no
alarm or performance monitoring is associated with those client port. The circuit pack
supports CrossRegen between any two line ports.
11STAR1 OT
The 11STAR1 Optical Transponder (OT) is a multi-service card that supports one client
interface (C1) and an 11G tunable line side interface (L1). It is called a multi-service card
because it supports different client signal types, configurable through a user interface. On
the client interface, the 11STAR1 OT uses an XFP pluggable module, to allow support for
different optical link applications. The user can configure the 11STAR1 OT to support
transmission of a variety of optical signal protocols (i.e., OC-192, STM-64, 10GbE LAN
PHY, 10GbE WAN PHY, 10Gb Fibre Channel, and OTU2 with G.709 FEC).
On the line side interface (L1), standard ITU-T G.709 digital structures are used. Line
side Forward Error Correction is provisionable for standard G.709 FEC (Reed-Solomon
(255, 239)) or enhanced FEC (EFEC) for higher coding gain. The L1 transmitter can be
tuned to any of the 80 channels supported by the system.
....................................................................................................................................................................................................................................
4-35
August 2011
....................................................................................................................................................................................................................................
As with all supported OTs, the 11STAR1 can be configured for different customer
applications. The following user provisioning is supported on both the C1 and L1 ports of
the 11STAR1 OT:
Port state and Automatic In-service operation

Enable/Disable Loopback (facility and terminal)
11STGE12 OT
11STGE12 Optical Transponder is a GbE multiplexing unit that allows the user to
aggregate up to 10 GbE services onto a 10G digital structure. The pack is designed in a
way that allows flexible port to service provisioning.
Note: Ports 1-10 are available for transporting GbE services while ports 11 and 12
should remain unassigned.
11STGE12 OT supports Ethernet Private Line bi-directional services for up to 10 client
ethernet signals with MAC layer transparency including transparency to client domain
VLAN tag(s). 10 GbE ports can be transported simultaneously with full throughput and
all frame sizes up to Jumbo size of 9216.
The user can enable/disable Auto-negotiation independently on all 10 client ports. Each of
the 10 client facing ports is implemented as an SFP module to allow flexible physical
layer configuration.
As with all supported OTs, the 11STGE12 can be configured for different customer
applications. The following user provisioning is supported on C1-10 and L1 ports of the
11STGE12 OT:

Enable/Disable Loopback (line/facility and terminal). Loopbacks on client ports can
be provisioned independently.
11STMM10 OT
11STMM10 Optical Transponder is a multi-protocol multiplexing unit that allows the

user to aggregate up to 10 client services onto a 10G G.709 compliant digital structure.
This pack is designed in a way that allows flexible port to service provisioning.
The following client signal types can be configured on client ports of 11STMM10 OT:
GbE -> Ethernet private line service using GFP-T encapsulation and code word
transparency for client signal.
OC3/OC12/OC48 -> Terminated SONET services (applicable for SONET system

mode).
....................................................................................................................................................................................................................................
4-36
August 2011
....................................................................................................................................................................................................................................
STM1/STM4/STM16 -> Terminated SDH services (applicable for SDH system

mode).
Note: For 11STMM10, VC3 structures in SDH mode are not supported.
CBR2G5 -> Bit transparent transport of OC48/STM16 clients (compliant with G.709)
FC100/FC200/FC400 -> Fibre channel services (either FC or FICON mode)
OTU1 -> Terminated OTU1 trail functions
Note: When used in transparent mode, the local onboard oscillator is used. PJE's may
be generated over time. This may impact transparent STM-4 working.
Each of the 10 client facing ports is implemented as an SFP module to allow flexible
physical layer configuration.
Client bit streams characteristic information is adapted to a server carrying digital
structure and mapped into contiguous bandwidth slot on a DWDM line port digital
structure. Figure 4-1, 11STMM10 OT signal processing from client port to DWDM line
port (p. 4-37) shows logical signal processing from the client port to the DWDM line
port. Line port structure consists of 4 ODU1s multiplexed into an ODU2.
Figure 4-1 11STMM10 OT signal processing from client port to DWDM line port
For the purpose of bandwidth allocation and flexible Client transport configurations,
DWDM Line port defines 64 virtual time slots (4 sets of 16). Time slots are identified as
ODU1 # followed by time slot #. ODU1 # ={1,2,3 & 4} while time slot # ={1, 4, 7, 10,
13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46}
....................................................................................................................................................................................................................................
4-37
August 2011
....................................................................................................................................................................................................................................
Each client adapted information takes fixed amount of bandwidth expressed in virtual
time slots in the following way:
OC12/STM4 4 time slots

OC3/STM1 1 time slot
GbE 7 time slots
CBR2G5 16 time slots

FC-100 6 time slots
FC-200 12 time slots
FC-400 24 time slots
OC48/STM16 16 time slots
OTU1 16 time slots
At the time of client port type provisioning, the user enters the starting time slot of the
contiguous bandwidth area on the line port which will transport client adapted
information.
Overall bandwidth required to transport client adapted information does not exceed 64
time slots. In addition to that rule the following provisioning rules apply:
1. Any port can carry any supported signal type
2. Sum of individual OC3/STM1 and OC12/STM4 plus two times sum of OC48/STM16
needs to be less than or equal to 8.
3. OC48/STM16 or CBR2G5 can start on the ODU1 boundaries (time slots 1-1, 2-1, 3-1
or 4-1)
4. OC12/STM4 can start only on the 4 time slot boundary (1-1, 1-13, 1-25, 1-37, 2-1,
)
Each 11STMM10 encodes its port and time slot map and sends it in-band to the peer
11STMM10 pack to validate provisioning match. If port number, signal type, and time
slot provisioning on the two ends doesnt match, FEPORTMISMATCH alarm is declared.
If the user reconfigures client port allocation by deleting OC3/STM1 or OC12/STM4
services in order to configure OC48/STM16 service, there is a potential that internal
Pointer Processor resources will be fragmented (2 adjacent PP sections needed for
OC48/STM16 processing may not be available). 11STMM10 SW uses optimal algorithm
for assigning internal resources so that simple service provisioning (addition) never
causes this condition. However, deletion and reconfiguration of previously configured
services may in some cases exhibit this behavior. If internal PP resources are not available
for OC48/STM16 service, provisioning will be denied. To avoid this condition the user
can either retrieve available PP sections (show resource command) prior to re-configuring
the 11STMM10 to determine which OC3/STM1, OC12/STM4 ports need to be deleted
....................................................................................................................................................................................................................................
4-38
August 2011
....................................................................................................................................................................................................................................
(to free up at least one pair of PP sections 1&2, 3&4, 5&6 or 7&8) or use transparent
OC48/STM16 option by provisioning CBR2G5 signal type (there is no PP section
allocation for CBR2G5 transport).
Note: For 11STMM10, a summary of resource allocation for Sonet/SDH or PCS can
be displayed in the WebUI by clicking on the Resources tab, selecting the Resource
Type, and clicking Retrieve.
As with all supported OTs, the 11STMM10 can be configured for different customer
applications. The following user provisioning is supported on C1-10 and L1 ports of the
11STMM10 OT:
Enable/Disable Loopback (line/facility and terminal). Loopbacks on client ports can

be provisioned independently.
Dual stage multiplexing
For this configuration, a signal is added at an OT client port and multiplexed onto the
higher bandwidth line port. The signal is then added at a second higher-rate OT, and
multiplexed to its line port. The reverse path is taken when the signal is dropped.
Dual stage multiplexing is supported in 1830 PSS-36/PSS-32/PSS-16 when an
11STMM10 OTU1 client is connected to the 4DPA4/4DPA2 and external topological
links are provisioned on the 11STMM10 client port and the 4DPA4/4DPA2 line port. The
NE IP address and shelf/slot/port of the 4DPA4/4DPA2 line port is specified in the
11STMM10 client port topological link and the NE IP address and shelf/slot/port of the
11STMM10 client port is specified in the 4DPA4/4DPA2 line port topological link. The
following applies:
An external topological link is provisioned on the 11STMM10 client port. The NE IP

address and shelf/slot/port of the 4DPA4/4DPA2 line port is specified as its external
connection.
An external topological link is provisioned on the 4DPA4/4DPA2 line port. The NE IP
address and shelf/slot/port of the 11STMM10 client port is specified as its external
connection.
The cross-connect terminates on the 11STMM10 line port. The 4DPA4/4DPA2 is not
included in a cross-connect.
There is no wave key encoding on the 4DPA4/4DPA2, so the eVOA port is not used.
There is no alarm correlation between the 11STMM10 and 4DPA4/4DPA2.
....................................................................................................................................................................................................................................
4-39
August 2011
....................................................................................................................................................................................................................................
112SCA1/112SA1L OT
The 112SCA1/112SA1L OT is a three-slot-wide full-height pack, which supports one

100GBE Hot pluggable module on the client interface. The 112SCA1/112SA1L OT also
supports one OTU4 line interface (non-pluggable), that can be tuned to any of the 99
wavelengths over the extended C-band (Freq: 191.150 THz to 196.050 THz).
The 112SCA1 operates in the optical C band with other Alcatel-Lucent 1830
PSS-32/PSS-36 OTs. The 112SA1L is an XL band version of the 112SCA1 100G OT that
supports drop shelf configurations with PSS-32/PSS-36 in support of Alcatel-Lucent
1625LX R10.
The 112SCA1/112SA1L OT supports the following functional features:
Facility and Terminal Loopbacks, Optical Performance Monitoring (OPR, OPT),

Digital Performance Monitoring (RMON, SONET/SDH, OTN - Client Side,
OTUk/ODUk Monitoring Line Side)
Hardware ready to support full ITU-T G.709 functionality, including GCC0 and TCM
Line side features:
PDM NRZ QPSK pulse format (Polarization Division Multiplexing NRZ
Quadrature Phase Shift Keying)
Line side coherent receiver, combined with a DSP to compensate for impared
linear and non-linear transmission (CD, PMD, SPM and non-linear phase noise).
Line side optics can be tuned to any of the 99 wavelengths for 112SA1L
(112SCA1 supports 88 channels) over the extended C-band (Freq: 191.150 THz to
196.050 THz)
Supports Alcatel-Lucent Enhanced FEC (~9.2 dB coding gain at 1E-15 for ~7-%
overhead)
Wave tracker supports optical power auto-management. User configurable option
to disable the WT for the interoperability application with other systems without
WT
Client side features:
Standard FEC (RS-FEC)

Supports 100 Gbe client interfaces
Note: In TOADM applications the 112SCA1 may not be connected to a CWR8 or
CWR8-88 CLS port.
Note: DWDM-DWDM single channel OEO regeneration is supported on the 100G
112SCA1 with line port operational mode configured for REGEN. For this
configuration, the channel can be different on each SFD (i.e. channel shifting is
supported). Since the regen configuration on the 100G OTs requires unidirectional
connections from the line port to different SFDs and recoloring is supported, receive
frequency (Rx) is an attribute on the line port (in addition to Tx frequency).
....................................................................................................................................................................................................................................
4-40
August 2011
....................................................................................................................................................................................................................................
112SCX10/112SX10L OT
The 112SCX10/112SX10L OT is a three-slot-wide full-height pack, that supports

multiplexing of up to ten 10G client signals into one OTU4 line interface. The
112SCX10/112SX10L OT supports one line interface (non-pluggable) and ten client
interfaces with XFP modules (B&W, CWDM). The line side optics of the
112SCX10/112SX10L OT can be tuned to 99 channels in the C-band. Each port has a
dedicated port status LED and a dynamic Ethernet activity LED. When Ethernet data is
transmitted or received, the LED blinks Green. When no Ethernet data is moving (idle),
the LED is off.
The 112SCX10 operates in the optical C band with other Alcatel-Lucent 1830
PSS-32/PSS-36 OTs. The 112SX10L is an XL band version of the 112SCX10 100G OT
that supports drop shelf configurations with PSS-32/PSS-36 in support of Alcatel-Lucent
1625LX R10.
The 112SCX10 OT supports the following functional features:
Facility and Terminal Loopbacks, Optical Performance Monitoring (OPR, OPT),

Digital Performance Monitoring (RMON, SONET/SDH, OTN - Client Side,
OTUk/ODUk Monitoring Line Side)
Line side supports the following features:
PDM NRZ QPSK pulse format (Polarization Division Multiplexing NRZ

Quadrature Phase Shift Keying)
Line side coherent receiver, combined with a DSP to compensate for linear
transmission impairments (CD & PMD) and mitigate non-linear impairments
(SPM and non-linear phase noise)
The line side optics can be tuned to any of the 99 wavelengths for 112SX10L
(112SCX10 supports 88 channels) over the extended C-band (Freq: 191.150 THz
to 196.050 THz)
Support Alcatel-Lucent Enhanced FEC (~9.2 dB coding gain at 1E-15 for ~7-%
overhead)
Wave tracker supporting optical power auto-management. User configurable
option to disable the WT for the interoperability application with other systems
without WT
Client side supports the following features:

Standard FEC (RS-FEC)
Supports OC-192/STM-64, 10 GbE and OTU2 client interfaces
....................................................................................................................................................................................................................................
4-41
August 2011
....................................................................................................................................................................................................................................
The mother board supports four key functions: client access, client signal processing,
control architecture, and power supply. Client access is through the ten XFP modules (B
& W and CWDM). Short, long, and extended reach XFP modules are supported. Client
signal processing includes: Status, Alarms, PM, FEC, and pre-mapping of the client signal
into p-ODTU24.
Note: In TOADM applications the 112SCX10 may not be connected to a CWR8 or
CWR8-88 CLS port.
Note: DWDM-DWDM single channel OEO regeneration is supported on the 100G
112SCX10 with line port operational mode configured for REGEN. For this
configuration, the channel can be different on each SFD (i.e. channel shifting is
supported). Since the regen configuration on the 100G OTs requires unidirectional
connections from the line port to different SFDs and recoloring is supported, receive
frequency (Rx) is an attribute on the line port (in addition to Tx frequency).
43SCX4 OT
The 43SCX4 is a 4x10G MUX OT with a single 43 Gb/s (OTU-3e2 = 44.583355576 Gb/s
20ppm) tunable line port and 4 client ports. It supports multiplexing of up to four 10G
client signals into the single OTU-3e2 line interface.
The 43SCX4 OT uses a Polarization Division Multiplexing NRZ Binary Phase Shift
Keying (PDM NRZ BPSK) pulse format on the line interface. A line side coherent
receiver, combined with a digital signal processor (DSP), provides compensation of linear
transmission impairments (chromatic dispersion, PMD) and reduction of intra-channel
non-linear transmission impairments (Self Phase Modulation [SPM] and non-linear phase
noise). The line side optics of the 43SCX4 OT can be tuned to any of the 99 wavelengths
in the extended C-band.
Wavetracker is supported on the line interface for optical power auto-management in
1830 PSS. For the interoperability application with LambdaXtreme, Wavetracker is
turned off.
The client interfaces support XFP pluggable modules (B&W and CWDM). The following
client signal types are supported:
OC-192/STM64
10GBE (GFP-F, GFP-P, CBR11096, CBR11049)
OTU2 (10.709, 11.049, 11.096)

FC800
43STA1P OT
The 43STA1P is a 3-slot wide, full height 43G Single Port Tunable Anyrate Add/Drop
Transponder. It contains transmit and receive optics as well as multiplexer, driver,
clock/data recovery, demultiplexer, and control functionality.
....................................................................................................................................................................................................................................
4-42
August 2011
....................................................................................................................................................................................................................................
The 43STA1P accepts a single OC-768/STM-256 client signal and an OTU3 Line
interface with full-band tunable optics. The line interface can be used to select any one of
88 channels (50 GHz spacing). Channel frequency can be provisioned automatically or
manually.
The following signals are supported on the line side:
OTU3
The following signals are supported on the client side:
OTU3
OC-768/STM-256
43STX4 OT
The 43STX4 OT is a three slot wide, full height OT that accepts up to four bi-directional
sub-43G client signals and multiplexes them into the 43G DWDM line signal. The
module has XFP pluggable modules on the client interface ports, and uses LC type optical
connectors on all interfaces.
OC192/STM64
OTU2
10GbE
Up to 4 independent client signals can be multiplexed and sent out on the line side. Any
combination of client signals is supported. On the line side, the 43STX4 OT supports
full-band tunable optics, capable of supporting all 44 even channels (100GHz spacing).
The frequency of the channel can be provisioned manually or automatically.
43STX4P OT
The 43STX4P transponder accepts up to four bi-directional sub-43G client signals and
multiplexes them into the 43G DWDM line signal. The module has XFP pluggable
modules on the client interface ports, and uses LC type optical connectors on all
interfaces.
OC192/STM64
OTU2
10GbE
Up to four independent client signals can be multiplexed and sent out on the line side.
Any combination of client signals is supported.
....................................................................................................................................................................................................................................
4-43
August 2011
....................................................................................................................................................................................................................................
On the line side, the 43STX4P OT supports full band tunable line side optics, capable of
supporting 44 even channels (at 100GHz spacing). The frequency of the channel can be
provisioned manually or automatically. It also supports eVOA management and WT
encoding functions.
MVAC
The Multiple Variable Attenuator Card (MVAC) contains an array of eight fast optical
VOA and WaveTracker encoders to condition alien wavelengths to pass through the
TOADM system.
The MVAC supports unidirectional (single-strand) connections to and from its ports. The
alien wavelength passes through the MVAC when added to the network for Wavelength
Tracker encoding and monitoring. When the wavelength is dropped from the network, it
does not go through the MVAC.
The MVAC is implemented as a half-height module that can be configured in any of the
universal slots in the 1830 PSS-36/PSS-32/PSS-16 shelves. MVAC ports do not support
bidirectional connections.
SVAC
The single port variable attenuation card is used as a bridge by the compatible wavelength
transponders into Alcatel-Lucent 1830 PSS-36/PSS-32/PSS-16 DWDM domain.
The following are the basic functions provided by SVAC as demarcation and adaptation
for so-called alien (foreign wavelength) channel:
Encodes theWavelength Tracker wave keys onto the optical channel

Automatically adjusts a variable optical attenuator (VOA) on each channel to set the
channel output optical power to the target level determined by NE SW
Monitors incoming alien wavelength optical power level and appropriate alarming.
SVAC is implemented as a half-height module that can be configured in any of the
universal slots in the universal shelves.
....................................................................................................................................................................................................................................
4-44
August 2011
....................................................................................................................................................................................................................................
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. 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.
Note: The CWR8-88 end terminals must be co-located. The loss budgets are designed
for fiber jumper loss only between the NEs and not for intervening spans.
....................................................................................................................................................................................................................................
4-45
August 2011
....................................................................................................................................................................................................................................

Overview
This section describes the WebUI procedures for slot and card-level functions. The
WebUI supports View, Modify, Create, and Delete card-level functions and the
pre-provisioning of a card in an empty slot.
Important! Alcatel-Lucent 1830 PSS requires that filler blanks be used in all un-used
slots in a shelf to ensure proper airflow and cooling.
Create card
Note: For provisioning 2-slot height cards and 2-slot width cards, adjacent slots must
be empty.
...................................................................................................................................................................................................
Select an empty slot from the equipment tree for pre-provisioning of a card and select the
Provision/Info function.
Result: The Provision Card screen is displayed.
...................................................................................................................................................................................................
Enter card parameters in the respective fields and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
View / modify card properties

...................................................................................................................................................................................................
Select the card from the equipment tree.

Result: Slot Settings and Circuit Pack Information are displayed under the Details
tab.
Note: The Primary State (PST) setting of specific cards can be provisioned from this
screen. A card cannot be placed Out of Service (OOS) if any ports on the card are in
service.
...................................................................................................................................................................................................
To modify card properties, select the Provisioning tab.

Result: Provisionable card properties are displayed.
Note: The units displayed are dependent on the value of the system setting. If set to
Celsius, the attribute values are displayed in Celsius. If set to Fahrenheit, the attribute
values are displayed in Fahrenheit.
....................................................................................................................................................................................................................................
4-46
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Enter appropriate values in the respective fields and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
View card inventory
The WebUI supports retrieving and displaying all provisioned and equipped cards in the
NE.
...................................................................................................................................................................................................
In the WebUI, select Reports > Inventory > Card.

Result: Card Inventory is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
View pluggable module inventory
Note: The following ports have pluggable modules (XFP/SFP/CFP):
OT client ports
11DPM12, 11QPA4, 11DPE12(E), 4DPA4, 4DPA2 line ports
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325A, OSC ports

AM2125A, AM2125B, AM2318A, ALPFGT and OSCT OSCSFP ports
MVAC G ports
The WebUI retrieves and displays pluggable module inventory for all applicable cards in
the NE.
...................................................................................................................................................................................................
In the WebUI, select Reports > Inventory > Pluggable Module.

Result: The Pluggable Module Inventory is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Protection switch (EC/FLC/MT0C)
Note: The controller (EC/FLC/MT0C) supports duplex mode (i.e., redundancy). If the
standby EC/FLC/MT0C is equipped, the WebUI will allow the user to initiate a
switch between the inactive and the active EC/FLC/MT0C.
....................................................................................................................................................................................................................................
4-47
August 2011
....................................................................................................................................................................................................................................
The active EC/FLC/MT0C will deny any and all requests from CLI, WebUI and
PhM when a switchover is taking place.
The active EC/FLC/MT0C will deny manual requests for a switchover when a
backup or restore is taking place.
The system will abort any backup or restore that is taking place if an automatic
switchover takes place.
Note: Protection switch lockout command or forced switch command can be used if
desired to inhibit switching of new services which are in flux during turn-up
provisioning across the network. This applies to all protection types: Y-cable, OPS,
ESNCP.
...................................................................................................................................................................................................
Select the EC/FLC/MT0C from the equipment tree and select the Protection Switch tab.
Result: The EC/FLC/MT0C Protection Switch Settings screen is displayed.
...................................................................................................................................................................................................
To manually switch to the inactive EC/FLC/MT0C, select the Force Protection Switch
option and click Submit.
Note: A switch is not allowed if:
Protection Setting of the selected card = Unequipped
For PSS-16 shelf:
The selected card is in slot 2 and slot 12 is unequipped.

For PSS-32 shelf:
The selected card is in slot 1 and slot 18 is unequipped

For PSS-36 shelf:

Note: PSS-36 shelf only: If the standby MT0C is equipped, the WebUI will allow the
user to initiate a switch between the inactive and the active MT0C (tnShelfTabletnShelfActivityMt0cSwitch). A switch is not allowed if:
Protection Setting of the selected card = unequipped

....................................................................................................................................................................................................................................
4-48
August 2011
....................................................................................................................................................................................................................................
Result: The WebUI displays a warning to the user indicating that the active and
standby EC/FLC/MT0Cs will be rebooted and all users will be logged off. The user
will be allowed to continue with the request or cancel. Upon continuing with the
request, the WebUI will logout the user.
E...................................................................................................................................................................................................
N D O F S T E P S
EC upgrade (in-service upgrade from simplex to duplex)

...................................................................................................................................................................................................
Remove any EC pack from slot 18.

...................................................................................................................................................................................................
Insert the EC pack into slot 1.

...................................................................................................................................................................................................
Download, install, and activate software.

...................................................................................................................................................................................................
Remove and re-seat the EC in slot 1. Allow to boot completely.

Result: In service upgrade to EC pack is complete.
Note: If another pack needs to be upgraded, place it in slot 1 and perform the
procedure again.
E...................................................................................................................................................................................................
N D O F S T E P S
Reboot card
Note: The user can request a manual reboot of a specific card (on cards that support
this feature). Both warm and cold restarts are supported. For a cold restart, the WebUI
displays a warning indicating that service may be affected. The user is allowed to
continue with the request or cancel. The WebUI will not allow a reboot request if the
card is not equipped (i.e., the card is pre-provisioned but is not present in the shelf
(see Manual restarts (reboot) (p. 4-6)).
...................................................................................................................................................................................................
Select the card from the equipment tree and select the Reboot tab.
Result: The Reboot Options screen is displayed.
...................................................................................................................................................................................................
Select either Warm Reboot or Cold Reboot and click Submit.
....................................................................................................................................................................................................................................
4-49
August 2011
....................................................................................................................................................................................................................................
Note: After a cold reboot, it is necessary to perform Clear bin in order to have a
clean PM collection period.
E...................................................................................................................................................................................................
N D O F S T E P S
Delete card
Note: The card must support deletion and the card must be in a valid state for
deletion.
...................................................................................................................................................................................................
Select the card from the equipment tree and select the Delete tab.
Result: The Delete Card screen is displayed.
...................................................................................................................................................................................................
Select option to Delete this Card and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
Port/facility states
Primary states applicable to port entities are:
IS, IS-NR to indicate In_Service, Normal state. The entity is capable and allowed to
provide its provisioned functions. (IS and IS-NR are used interchangeably.)
IS-ANR to indicate In_Service_Abnormal state. The entity is capable of most

functions, is allowed to provide its provisioned functions, but is operating in a
degraded or abnormal state (e.g., non-alarmed BER Signal Degrade threshold
crossing on an OCn or STS).
OOS-AU to indicate Out_Of_Service-Autonomous state. The entity is not available
for providing its provisioned functions but the entity is not intentionally suspended by
external management command (from an OS or craft interface) from performing these
functions. In general, the cause of the incapability is due to an unsolicited autonomous
event detected in the system or in the associated network (e.g., LOS detected).
....................................................................................................................................................................................................................................
4-50
August 2011
....................................................................................................................................................................................................................................
OOS-AUMA to indicate Out_Of_Service-Autonomous_and_Management state. The

entity is not available for providing its provisioned functions because an OOS-AU
state transition has occurred and the entity is intentionally suspended by external
management command (from an OS or craft interface) from performing its
provisioned functions.
OOS-MA to indicate Out_Of_Service-Management state. The entity is intentionally
suspended by external management command (from an OS or craft interface) from
performing its provisioned functions, but the entity may still be operationally capable
of performing its provisioned functions.
Secondary states applicable to port entities are:
AINS to indicate Automatic In-Service state. The facility is in a delay transition (to
IS) state. The transition to IS is pending on the correction of off-normal conditions on
the facility (such as FAF for termination point). Alarms will not be generated if AINS
is present. Once the off-normal conditions are cleared, the facility will transition to IS
according to the autonomous rules of the OOS-AU state. When using the ENT
command to provision an entity, if the requested state in the command is IS and the
required resource is not present (such as circuit pack is not present for the equipment
or valid signal is not present for the termination point), then the entity will enter the
OOS-AU state and alarms will be generated. However, if the AINS value is also
present in the SST field in the ENT command, then no alarms will be generated.
FAF to indicate Facility Failure state. The associated facility entity has failed, (e.g.,
LOS, LOF condition).
FLT applies to ports with pluggable modules and indicates pluggable module failure,
mismatch or module missing condition.
MT to indicate when a port is in maintenance. It generates traffic and monitors for
faults, but it only generates non-reported conditions.
SGEO to indicate Supporting Entity Outage. The associated supporting entity has
failed or is out-of-service due to management action (OOS-MA or OOS-AUMA).
UAS to indicate Unassigned. The entity has not been assigned with the necessary
provisioning data. No service activity or maintenance activity (including monitoring,
testing, or service recovery) is permitted in this state since the necessary data has not
been assigned.
Port/facility provisioning behavior
The following applies to port/facility provisioning:
The NE allows the client port object entity to be created and provisioned. Attribute
values identified as default are set initially unless they are explicitly defined in the
provisioning command.
The NE allows a modification of the provisioned parameters of a port object entity.
The NE allows deprovisioning of a provisioned port entity.
....................................................................................................................................................................................................................................
4-51
August 2011
....................................................................................................................................................................................................................................
The NE allows retrieving the provisioned parameters and the state of a port object
entity.
Line ODU2 and OTU2 facility are auto-created once the slot is provisioned.
Line ODU2 and OTU2 facility are auto-deleted once the slot is de-provisioned.
However, the slot cannot be de-provisioned unless the connection between OT (line
side) and SFD44/OPSA are first deleted.
11STAR1 OT port state provisioning
The states of the C1 and L1 ports are provisioned independently. The following port states
are supported:
Up - Provisioning the state to Up enables the port.

Down - Provisioning the state to Down disables the port
mt - Provision the state to mt to set the admin state to maintenance
ains - Provision the state to ains to set the admin state to Automatic In-Service. When
in this state, the port is allowed to transition to the in-service (Up) state if it is
operationally capable. That is, when all alarms on that port have cleared and the
ainstimer has expired. When in this state, the user can choose from the following:
configure the properties of the ainstimer to use either the system value, or to enter
the number of hours and minutes (1 minute to 96 hours). The default value of the
ainstimer is system.
Set ains to enabled
Set ains to disabled
11STAR1 client port provisioning
The user can provision the 11STAR1 OT for the following client signal types:
10GbE LAN
10G Fibre Channel (FC1200)
OTM-0.2 (OTU2)
OC-192
STM-64
....................................................................................................................................................................................................................................
4-52
August 2011
....................................................................................................................................................................................................................................
10GbE LAN client port provisioning
The following attributes are provisionable on the 11STAR1 C1 interface when the signal
type is provisioned to 10GbE LAN:
Provisionable
Attribute
channel
Attribute Definition
Specifies the channel frequency for the client port.
Enter this keyword to display the current setting. To change the
setting, enter this keyword followed by one of the following values:
encmode
errfrmdrop
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Encapsulation mode. This attribute is used to provision the

encapsulation mode used to map the 10GbE LAN signal. Select from
one of the following:
GFP-F - (Standard, frame-based GFP encapsulation mode)
GFP-P - (Proprietary GFP encapsulation mode, semi-transparent)
cbrlan11.049 - (Transparent mode, no GFP)
Errored Frame Drop Mode. This attribute, when enabled, will discard
all received errored frames. Select either:
Enabled - Discard all ingress errored frames.
Disabled (default) - Do not discard all ingress errored frames.
Pluggable module type. This attribute specifies the pluggable module

type expected in the socket identified by the port AID. Enter one of
the acceptable Client port moduletype values:
10GB-ZR
10GB-SR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C
Auto If this value is configured, then the network element will

accept a pluggable module from the list of modules supported by
Alcatel-Lucent.
User - If the user wants to use a pluggable module that is not on

the Alcatel-Lucent qualified list of pluggable modules, without
generating an alarm, set this attribute to user.
....................................................................................................................................................................................................................................
4-53
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
Attribute that controls the status of the client-side transmitter during
signal failures on the line port, or when a far-end failure signal is
received on the line side. Enter one of the following:
laserOn (default) transmitter stays on
laserOff turn off the transmitter
10G fibre channel (FC1200) client port provisioning
The following attributes are provisionable on the 11STAR1 C1 interface when the signal
type is provisioned to FC1200:
Provisionable
Attribute
channel
moduletype
losprop
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

10GB-SR
XI-64.1
XL-64.2C
XS-64.2C

Alcatel-Lucent.


....................................................................................................................................................................................................................................
4-54
August 2011
....................................................................................................................................................................................................................................
OC-192 or STM-64 or 10GbE WAN PHY client port provisioning
The following attributes are provisionable on the 11STAR1 C1 interface when the
provisioned signal type is either OC-192, STM-64, or 10GbE WAN PHY:
Provisionable
Attribute
channel
J0_ex
J0_fmt
trccmp
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Expected J0. Configure expected J0. Enter a value that depends on the
J0 format selected (1-byte or 16-byte):
15-character string if the format is 16-byte
byte in Hex format if the value of j0_fmt is 1_byte
J0 format Configure the J0 format. Select from one of the following:
1 - Configure J0 format to 1-byte mode.
J0 trace comparison. Choose from one of the following:
Enable - Enable J0 comparison.
Disable - Disable J0 comparison.

10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.

....................................................................................................................................................................................................................................
4-55
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
sdth
Attribute that specifies the BER threshold to declare a Signal Degrade

condition. Enter a value from the following range for the bit error rate,
expressed as 10-n.
sfth
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6
Attribute that specifies the BER threshold to declare a Signal Fault

expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
OTU2 client port provisioning
provisioned client signal type is OTU2:
Provisionable
Attribute
channelrx
Specifies the receive channel frequency. Not settable for internal
topology connections.
channeltx
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the transmit channel frequency.

CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-56
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
Forward Error Correction Type. Enter one of the following values:
NOFEC - No forward error connection (i.e., FEC is disabled)
RSFEC - Configure Reed-Solomon FEC
Note: Changing fectype while admin status is 'up' can cause loss of
traffic/data link (GCC). Changing fectype should only be made in
'down' state.
gccstat
gcctype
GCC0 Status. Enter one of the following values:
Set to enabled to enable GCC1/GCC2/GCC3 processing
Set to disabled to disable GCC0/GCC2/GCC3 processing (default)
Specifies which GCC communication channel type will be selected.

Values: GCC0; GCC1; GCC2
Default: GCC0
moduletype
losprop
ospf helloint

10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


HELLO INTERVAL of the OSPF interface. By default, the interface is

set to 10 seconds. This is the time elapsed before the next HELLO
PDU is sent.
Range: 1-65535
....................................................................................................................................................................................................................................
4-57
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf deadint
DEAD INTERVAL of the OSPF interface. By default, the Interface is

set to four times the value of the HELLOINT, so the default is 40
seconds. The dead interval is a timer used to timeout inactive
adjacencies. The dead interval value must always be greater than the
hello interval value.
ospf metric
METRIC or Cost of the OSPF interface. By default, the interface is set

to 30.
Range: 1-65535
ospf md5key
Key is used for MD5 128bit hash value key calculation. This
parameter is mandatory if md5keyid is entered. The value is 1 to 16
ASCII characters. The string can be 1 to 16 uppercase or lowercase
alphanumeric characters; the first character can not be a numeric
value. This parameter is mandatory if md5_status is enable.
Default: NUL ()
ospf md5keyid
md5keyid is used for MD5 128bit hash value key calculation. This
parameter is mandatory if md5staus is enable.
Range: 1- 255
Default: 1
ospf md5status
Set to enable - the MD5 authentication is activated on the OSPF

area.
Set to disable - the MD5 authentication is not required on the

OSPF area.
This parameter can be set to enable only if a md5key and md5keyid

have been set.
Default: disable
packettype
The packet type describes if it is standard packet or not. If it is

standard the mtu size can be configured. If the packettype is
non-standard the mtu size is default.
Default: nonstd
mtu
Maximum transmission unit. The default is 1473 Bytes.

Range: 576 - 1500
....................................................................................................................................................................................................................................
4-58
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
oturate
tti
OTU rate Specifies the client OTM0.2 rate. Enter one of the following
values:
10.709 (Gb/s) (default)
11.049 (Gb/s)
11.096 (Gb/s)
Configure Trail Trace Indentifier attributes:
exp_sapi Specifies the expected incoming Source Access Point

Identifier. Enter this keyword followed by 15 ASCII characters,
enclosed in quotation marks. Default: Null character (15 bytes
each with hex value 00)
tx_sapi Specifies the transmitted Source Access Point Identifier.

Enter this keyword followed by 15 ASCII characters, enclosed in
quotation marks. Default: Null character (15 bytes each with hex
value 00).
timmresp Optical channel Path Trace Identifier Mismatch

Response. Enter either of the following:
Set to enable to enable TIMM defect detection.
Set to disable to disable TIMM defect detection. (default)
trccmp Optical channel Trace compare. This keyword enables

and disables the comparison between the incoming sapi value and
the provisioned (i.e., exp_sapi) value.
Set to Enable to enable comparison
Set to Disable to disable comparison (default)
....................................................................................................................................................................................................................................
4-59
August 2011
....................................................................................................................................................................................................................................
ODU2 Client Port Provisioning
Provisionable
Attribute
tti


11STAR1 line port provisioning
The line interface on the 11STAR1 OT supports provisionable parameters at the OTU2
and ODU2 transport layers, as defined in the following tables.
OTU2 line port provisioning
The following OTU2 attributes are provisionable on the 11STAR1 L1 interface:

Provisionable
Attribute
channel
Attribute that configures the frequency of the tunable transponder.
Enter one of the following: {9605, 9600, 9595, 9590, 9585, 9580,
9575, 9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525,
9520, 9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470,
9465, 9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360,
9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305,
9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250,
9245, 9240, 9235, 9230, 9225, 9220, 9215, 9210, 9215, 9200, 9195,
9190, 9185, 9180, 9175, 9170}
....................................................................................................................................................................................................................................
4-60
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
Forward error correction mode. Specifies the type of forward error
correction on the interface port. Enter one of the following values:
EFEC - Enhanced FEC (default)
RSFEC - Reed-Solomon FEC
'down' state.
RegenResp
Configure OTU2 Regeneration Response for OPS configuration
Set to LaserOn Line port laser is turned on if there is no client

OTU2 LOS/LOF alarm
Set to LaserOff Line port laser is shut down if client OTU2

LOS/LOF alarm is detected
Default: LaserOn
gccstat
gcctype
Set to enabled to enable GCC1/GCC2/GCC3 processing
Set to disabled to disable GCC0/GCC2/GCC3 processing (default)
Specifies which GCC communication channel type will be selected.

Values: GCC0; GCC1; GCC2
Default: GCC0
ospf helloint

PDU is sent.
Range: 1-65535
ospf deadint

ospf metric

to 30.
Range: 1-65535
....................................................................................................................................................................................................................................
4-61
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
mtu

Range: 576 - 1500
....................................................................................................................................................................................................................................
4-62
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




Enter a string of 15 ASCII characters, enclosed in quotation
marks. Default: Null character (15 bytes each with hex value 00)
ODU2 line port provisioning
The following ODU2 attributes are provisionable on the 11STAR1 L1 interface:

Provisionable
Attribute
ptmmresp
ODU2 Payload Type Mismatch Response. Specifies whether the OT
will take a consequent action or pass the received signal. Enter one of
the following:
enabled enable the consequent action
disabled disable (turn off) the consequent action (default)
....................................................................................................................................................................................................................................
4-63
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




11STMM10 OT port state provisioning
The states of the C1-10 and L1 ports are provisioned independently. The following port
states are supported:


Set ains to enabled
11STMM10 client port provisioning
The user can provision the 11STMM10 OT for the following client signal types:
OTU1
GbE
OC3
....................................................................................................................................................................................................................................
4-64
August 2011
....................................................................................................................................................................................................................................
STM1
OC12
STM4
OC48
STM16
CBR2G5
FC100
FC200
FC400
For each of the above client signal types, the user can provision different attributes as
described in the following subsections.
GbE client port provisioning
The following attributes are provisionable on the 11STMM10 C1-10 interfaces when the
signal type is provisioned to GbE :
Port Attribute
channel
Description
Specifies the wavelength of the pluggable module.
encmode
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the encapsulation mode used to transport the 10GbE LAN

signal. Enter this keyword followed by one of the following values:
gfp-f specifies the use of the Generic Framing protocol (ITU-T

G.7041)
gfp-p Generic Framing Protocol, Proprietary, where the client

Ethernet frame preamble is preserved.
Default: previously existing value

errfrmdrop
Specifies whether inbound error frames are discarded or passed. This

attribute is only meaningful for GFP transport modes. Enter this
keyword followed by either of the following values:
....................................................................................................................................................................................................................................
4-65
August 2011
....................................................................................................................................................................................................................................
Port Attribute
losprop
moduletype
timeslot
[line | vts]
Description
Specifies how the near end client facing transmitter port reacts to a
Loss of Signal (LOS), Loss of Frame (LOF) or other defect from the
far-end client-facing receiver. Enter this keyword to display the
current setting. To change the setting, enter this keyword followed by
laserOn transmitter stays on (default)
Specifies the pluggable module type to be used on the specified

interface port. Enter this keyword to display the current setting. To
change the setting, enter this keyword followed by one of the
following:
Enter one of the acceptable Client port moduletype values:

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SL-16.2C
SS-16.1A
SS-16.2C

Alcatel-Lucent.

generating an alarm, this attribute should be set to user.
Specifies the time slot on the line port and on the ODU1. Enter this
keyword followed by the following:
Enter the keyword line to specify the ODU1 on the line port,
followed by a value from the following range:
{0-4}
Enter the keyword vts to specify the time slot of the ODU1,
Range: {0 or 1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46}
Value 0 in both cases indicates no time slot assignment
....................................................................................................................................................................................................................................
4-66
August 2011
....................................................................................................................................................................................................................................
CBR2G5 client port provisioning
signal type is provisioned to CBR2G5 :
Port Attribute
channel
Description
Specifies the wavelength of a pluggable module.
sdth
sfth
jo
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the received BER threshold required to raise a signal defect

condition. Enter this keyword followed by a value for the bit error
rate, expressed as 10-n.
Range: {10-5, 10-6, 10-7, 10-8, 10-9}
Default: 10-6
Specifies the received BER threshold for Excessive BER defect

declaration. Enter this keyword followed by a value for the bit error
Range: {10-3, 10-4, 10-5}
Default: 10-3
Configure J0 attributes:
j0_ex Expected J0. Enter this keyword followed by either one of

the following:
1-byte in Hex format if the value of j0_fmt is 1_byte
j0_fmt J0 format. Enter this keyword followed by a value for the

J0 format.
<value>=1: configure J0 format to 1-byte mode
<value>=16: configure J0 format to 16-byte mode (default)
trccmp J0 trace compare. This keyword enables and disables the

comparison between the incoming J0 value and the provisioned
(i.e., expected) value.
Set to enable to enable comparison
Set to disable to disable comparison (default)
....................................................................................................................................................................................................................................
4-67
August 2011
....................................................................................................................................................................................................................................
Port Attribute
losprop
mappingmode
moduletype
timeslot
[odu1 | vts]
Description
Specifies the type of mapping of the CBR2g5 signal into the ODU1
structure
bitsync (default)
async

following:

Sl-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1A
SS-16.2C

Alcatel-Lucent.

Specifies the time slot on the line port. Both odu1 and vts must be
entered at the same time. Enter this keyword followed by the
following:
Enter the keyword odu1 to specify the ODU1 tributary within the
line port, followed by a value from the following range: {0-4}
Enter the keyword vts to specify the STS3c time slot within the
ODU1, followed by a value from the following range: {0 or 1, 4,
7, 10, 13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46}
Value 0 indicates no time slot assignment
....................................................................................................................................................................................................................................
4-68
August 2011
....................................................................................................................................................................................................................................
OC3/OC12/OC48 and STM1/STM4/STM16 client port provisioning
signal type is provisioned to OC3/OC12/OC48 and STM1/STM4/STM16 :
Port Attribute
channel
Description
sdth
sfth
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the received BER threshold required to raise a signal defect

condition. Enter this keyword followed by a value for the bit error
Range: {10-5, 10-6, 10-7, 10-8, 10-9}
Default: 10-6
Specifies the received BER threshold for Excessive BER defect

declaration. Enter this keyword followed by a value for the bit error
Range: {10-3, 10-4, 10-5}
Default: 10-3
....................................................................................................................................................................................................................................
4-69
August 2011
....................................................................................................................................................................................................................................
Port Attribute
jo
losprop
Description

the following:

J0 format.
j0_tx Transmitted J0. Enter this keyword followed by either one

of the following:

- timmresp Optical channel Path Trace Identifier Mismatch

Response. Enter this keyword followed by either of the following:
Set to enabled to enable TIMM defect detection.
Set to disabled to disable TIMM defect detection. (default).
....................................................................................................................................................................................................................................
4-70
August 2011
....................................................................................................................................................................................................................................
Port Attribute
moduletype
timeslot
[line | vts]
Description
following:

For OC3/STM1:
SL-1.1
SL-16.2C
SS-16.1A
SS-16.2C
For OC12/STM4:
SL-4.1
SL-16.2C
SS-4.1
SS-16.1A
SS-16.2C
For OC48/STM16:
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1A
SS-16.2C

Alcatel-Lucent (default).

Specifies the time slot on the line port and on the ODU1. Enter this
keyword followed by the following:
Enter the keyword line to specify the time slot on the line port,
{0-4}
Enter the keyword vts to specify the time slot of the ODU1,
For OC-3 or STM1clients:
Range: {0 or 1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46}
For OC-12 or STM4 clients:
Range: {0,1,13,25,37}
For OC-48 or STM16 client:
Range: {0 or 1}
Value 0 indicates no time slot assignment

....................................................................................................................................................................................................................................
4-71
August 2011
....................................................................................................................................................................................................................................
FC100/FC200/FC400 client port provisioning
signal type is provisioned to 1, 2 or 4 Gb/s Fiber channel:
Port Attribute
channel
Description
fcmode
losprop
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the FC interface type (Fibre Channel compliant with INCITS

x.320 or FICON). Enter this keyword followed by:
fc (default)
ficon
....................................................................................................................................................................................................................................
4-72
August 2011
....................................................................................................................................................................................................................................
Port Attribute
moduletype
timeslot
[odu1 | vts]
Description
following:

For FC100 and FC200:
2FCLC-L
2FCSN-1
4FCLC-L
4FCSN-1
SS-16.1A
For FC400:
4FCLC-L
4FCSN-1


following:
7, 10, 13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46}
Value 0 in both cases indicates no time slot assignment
....................................................................................................................................................................................................................................
4-73
August 2011
....................................................................................................................................................................................................................................
The following attributes are provisionable on the 11STM10 C1-10 interfaces when the
Provisionable
Attribute
channelrx
channeltx
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
RSFEC - Configure Reed-Solomon FEC (default)
'down' state.
Note: When interconnecting MSC and 11STMM10, the only
configuration supported is NOFEC. GCC termination on 10xANY
when FEC is enabled is not supported.
gccstat
ospf helloint
Enabled - Configure GCC0 status to enabled.
Disabled - Configure GCC0 status to disabled (default).

PDU is sent.
Range: 1-65535
....................................................................................................................................................................................................................................
4-74
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf deadint

ospf metric

to 40.
Range: 1-65535
ospf md5key
value. This parameter is mandatory if md5_status is enable
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
mtu

Range: 576 - 1500
....................................................................................................................................................................................................................................
4-75
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
following:
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1A
SS-16.2C
Auto (default) If this value is configured, then the network

element will accept a pluggable module from the list of modules
supported by Alcatel-Lucent.

far-end client-facing receiver.
setting, enter this keyword followed by one of the following:
ospf area
Specifies the area ID for the GCC0 channel. A valid area identifier
consists of four integer values separated by periods, for example
0.0.0.5. The specified area must have been previously configured on
the NE at the system-level.
Default: 0.0.0.0
timeslot [odu1
odu1_trib vts vts]
following:
7, 10, 13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46}
....................................................................................................................................................................................................................................
4-76
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


The following attributes are provisionable on the 11STM10 C1-10 interfaces when the
Provisionable
Attribute
tti


....................................................................................................................................................................................................................................
4-77
August 2011
....................................................................................................................................................................................................................................
11STMM10 line port provisioning
The line interface on the 11STMM10 OT supports provisionable parameters at the OTU2
The following OTU2 attributes are provisionable on the 11STMM10 L1 interface:

Provisionable
Attribute
channel
9575, 9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525,
9520, 9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470,
9465, 9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360,
9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305,
9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250,
9245, 9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195,
9190, 9185, 9180, 9175, 9170}
fectype

efec - Enhanced FEC (default)
rsfec - Reed-Solomon FEC
'down' state.
tti




....................................................................................................................................................................................................................................
4-78
August 2011
....................................................................................................................................................................................................................................
The following ODU2 attributes are provisionable on the 11STMM10 L1 interface:

Provisionable
Attribute
ptmmresp
tti
the following:




11STGE12 OT port state provisioning
The states of the C1-C12 and L1 ports are provisioned independently. The following port

....................................................................................................................................................................................................................................
4-79
August 2011
....................................................................................................................................................................................................................................
Set ains to enabled
11STGE12 client port provisioning
The following attributes are provisionable on the 11STGE12 C1-12 interfaces:

Port Attribute
channel
Description
autoneg
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Attribute that controls the status of auto-negotiation. Enter this

enabled
disabled (default)
Note: Auto-negotiation can be provisioned (enabled or disabled) only

when the port state is OOS (admin state=Down). When the admin
state is Up or Maintenance, provision of the auto-negotiation attribute
is not allowed.
Note: Performance times may be adversely affected on 11STGE12
ports which have autoneg=enabled. If so, set autoneg=disabled (for
both ports on both ends).
losprop
....................................................................................................................................................................................................................................
4-80
August 2011
....................................................................................................................................................................................................................................
Port Attribute
moduletype
Description
following:

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SL-16.2C
SS-16.1A


11STGE12 line port provisioning
The line interface on the 11STGE12 OT supports provisionable parameters at the OTU2
The following OTU2 attributes are provisionable on the 11STGE12 L1 interface:

Provisionable
Attribute
channel
9575, 9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525,
9520, 9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470,
9465, 9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360,
9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305,
9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250,
9245, 9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195,
9190, 9185, 9180, 9175, 9170}
....................................................................................................................................................................................................................................
4-81
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
efec2- Enhanced FEC type 2 (default)
'down' state.
oturate
OTU rate. Specifies the line OTU2 rate. Enter one of the following
values:
Set to 11.049, for 11.049 Gb/s overclocked rate
Default: 11.096
tti




The following ODU2 attributes are provisionable on the 11STGE12 L1 interface:

Provisionable
Attribute
pldtype
Specifies the value of the Payload Type field within the ODU2
payload overhead. pldtype has a default value and is based on the
encoded client signal.
Set to a value in the following range: {0-255}
....................................................................................................................................................................................................................................
4-82
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ptmmresp
tti
the following:




11DPE12(E) OT port state provisioning
The states of the C1-C12, L1, L2, VA1, and VA2 ports are provisioned independently. The
following port states are supported:

Set ains to enabled

....................................................................................................................................................................................................................................
4-83
August 2011
....................................................................................................................................................................................................................................
Note: For 11DPE12(E), the line-side laser is shut down if the port state is provisioned
to "down". The line-side laser is turned on if the port state is set to "up" or
"maintenance".
11DPE12(E) client port provisioning
The following attributes are provisionable on the 11DPE12(E) C1-12 interfaces:

Port Attribute
channel
Description
autoneg
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Attribute that controls the status of auto-negotiation. Enter this

enabled
disabled (default)
Note: Auto-negotiation can be provisioned (enabled or disabled) only

when the port state is OOS (admin state=Down). When the admin
state is Up or Maintenance, provision of the auto-negotiation attribute
is not allowed.
Note: Performance times may be adversely affected on 11DPE12(E)
ports which have autoneg=enabled. If so, set autoneg=disabled (for
both ports on both ends).
Note: When using electric 1GbE SFP (1000BASE-T), 11DPE12E
traffic cannot be up if Auto-Negotiation is enabled against the client
port. Auto-Negotiation should be disabled against the client port
(electric SFP) for the 1GbE traffic to work normally.
losprop
....................................................................................................................................................................................................................................
4-84
August 2011
....................................................................................................................................................................................................................................
Port Attribute
moduletype
stpid
Description
following:

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SL-16.2C
SS-16.1A
SS-16.2C


SVLAN Tag Protocol Identifier (STPID) it is used for CE-VLAN

tagged packets in QinQ mode.
Stpid1 The client stpid is provisioned with global

stpid1.(default)
Stpid2 The client stpid is provisioned with global stpid2.
Note: It is applicable only when the pack is in QinQ mode.

FE client port provisioning
Port Attribute
channel
Description
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-85
August 2011
....................................................................................................................................................................................................................................
Port Attribute
losprop
moduletype
stpid
Description

following:

1000BLX10



stpid1.(default)

VTS client port provisioning
Note: Configure the C{1-12} client ports with the CE-VLAN ID map attributes on the
11DPE12(E) card. This command is only applicable when the card mode is set to
Subrate or QinQ mode.
Port Attribute
vts{1-10}
Description
Specifies the virtual time slot within the port.
The valid values are: vts1, vts2, vts3, vts4, vts5, vts6, vts7, vts8, vts9,
vts10.
....................................................................................................................................................................................................................................
4-86
August 2011
....................................................................................................................................................................................................................................
Port Attribute
cmode
Description
Classification mode, it is used to differ classification mode in Q in Q
mode. The value of the cmode can be: SVLANID, CEVLANID, and
PORT.
CEVLANID: The CEVLANID is used for CVLAN traffic.
SVLANID: SVLANID is used for SVLAN tagged traffic. .
PORT: PORT is used for the fullrate service (fullrate service is

different fullrate mode), all the port packets which includes
CE-VLAN tagged, SVLAN tagged and un-tagged packets are
mapped into the line VTS. When the PORT is provisioned, the
port parameter PVID should only be NULL..
Untagged : When the cmode is configured as untagged mode, a

CEVLAN ID is provisioned for untagged mode. then the
incoming untagged and priority tagged packet and CVLAN
tagged which the VLAN ID is same as the provision CEVLANID
will be treated as a flow , and a SVLAN will be added , when the
flow is out from a client port ,the svlan will be popped . The
cevlan id for untagged mode can only be a signal value .The
default value is NULL.
The valid value for each cmode are following:
Value of CEVLANID: ID number or ID ranges separated by

comma:
ID Range: [1-4095], null
Default: null
Note: null string (zero-length) is used to indicate that no traffic
flow is mapped into the client VTS.
Value of SVLANID unique ID number.

ID Range: [2- 4094], null
Default: null
Value of untagged:unique ID number

ID Range : [1-4094], NULL.
Default: null
Value of PORT: All, NULL.

Default: null
In Q in Q, the client VTS/cmode mapping is unidirectional. Users

must specify the map direction. The valid directions are :
Egress the mapping direction is out from the port.
Ingress the mapping direction is into the port.
11DPE12(E) line port provisioning
The line interface on the 11DPE12(E) OT supports provisionable parameters at the

OTU2, ODU2, and 10GbE transport layers, as defined in the following tables.
....................................................................................................................................................................................................................................
4-87
August 2011
....................................................................................................................................................................................................................................
The following OTU2 attributes are provisionable on the 11DPE12(E) L1,2 interface:
Provisionable
Attribute
channelrx
CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W {850, 1310, 1550}
Not set: None

channeltx
Specifies the transmit channel frequency. Not settable for internal

CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-88
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
efec2- Enhanced FEC type 2 (default)
'down' state.
gccstat
ospf helloint
Specifies the status of GCC0 signal processing.
Set to enabled to enable GCC0 processing (default)
Set to disabled to disable GCC0 processing

PDU is sent.
Range: 1-65535
ospf deadint

ospf metric

to 30.
Range: 1-65535
packettype

Default: nonstd
mtu

Range: 576 - 1500
....................................................................................................................................................................................................................................
4-89
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
interface port.
oturate
10GB-ZR
XI-64.1
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2b
XS-64.2C
Auto If this value is configured, then the network element

accepts the pluggable module. (Default)

OTU rate. Specifies the line OTU2 rate. Enter one of the following
values:
Default: 11.096
stpid


stpid1.(default)
....................................................................................................................................................................................................................................
4-90
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




The following ODU2 attributes are provisionable on the 11DPE12(E) L1,2 interface:
Provisionable
Attribute
pldtype
ptmmresp

the following:
....................................................................................................................................................................................................................................
4-91
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




10Gbe line port provisioning
The following 10Gbe attributes are provisionable on the 11DPE12(E) L1,2 interface:
Provisionable
Attribute
channelrx
CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-92
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
channeltx
CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W {850, 1310, 1550}
Not set: None

moduletype

interface port.
pvid
10GB-ZR
XI-64.1
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2b
XS-64.2C


Port VLAN ID The PVID is the CEVLAN ID for Untagged and

PriorityTagged Packets in QinQ mode. Enter this keyword followed
by an ID number.
Value range: 1 4094
Default: 1
....................................................................................................................................................................................................................................
4-93
August 2011
....................................................................................................................................................................................................................................
VTS line port provisioning
Note: Configure the L{1-2} line ports with the classification mode map attributes in
Q in Q mode on the 11dpe12e card. This command is only applicable when the card
mode is set to QinQ mode.
Port Attribute
vts{1-100}
Description
Specifies the virtual time slot within the port.
The valid values are: vts{1-100}.
cmode
Classification mode, it is used to differ classification mode in Q in Q

mode. User must enter the keyword followed by specific cmode,
cmode_value and cmode_direction.
CEVLANID: The CEVLANID is used for CVLAN traffic.
SVLANID: SVLANID is used for SVLAN tagged traffic. .
Untagged : When the cmode is configured as untagged mode, a

CEVLAN ID is provisioned for untagged mode. then the
incoming untagged and priority tagged packet and CVLAN
tagged which the VLAN ID is same as the provision CEVLANID
will be treated as a flow , and a SVLAN will be added , when the
flow is out from a client port ,the svlan will be popped . The
cevlan id for untagged mode can only be a signal value .The
default value is NULL.
The valid value for each cmode are following:
Value of CEVLANID: ID number or ID ranges separated by

comma:
ID Range: [1-4095], null
Default: null
Note: null string (zero-length) is used to indicate that no traffic
flow is mapped into the client VTS.
Value of SVLANID unique ID number.

ID Range: [2- 4094], null
Default: null
Value of untagged:unique ID number

ID Range : [1-4094], NULL.
Default: null
Note: In 11DPE12E, when we use the CCM mode for FlowCM (flow
continuity monitoring), the line port ingress VTS SVLAN ID and line
port egress VTS SVLAN ID should be same. So when the pack
FlowCM is set to CCM and the line ingress VTS#i entity COMDE
and line egress VTS#i entity COMDE are set as SVLAN tagged , the
line ingress VTS#i and line egress VTS#i entity SVLAN ID should be
same .
....................................................................................................................................................................................................................................
4-94
August 2011
....................................................................................................................................................................................................................................
11DPE12(E) VA port provisioning
Note:
11DPE12(E)/VA[1-2] cannot connect to any SFDxx Channel Out

11DPE12(E)/VA[1-2] Out cannot connect to 11DPE12(E)/VA[1-2] In
The VA port on the 11DPE12(E) OT supports the OCH attributes for the eVOA ports
(VA{1-2}) on the 11DPE12(E) card as defined in the following table.
VA port provisioning
The following OCH attributes are provisionable on the 11DPE12(E) VA interface:

Provisionable
Attribute
moduletype
change the setting, enter this keyword followed by the following:
sVOA slow VOA (Default)
fVOA fast VOA
auto If this value is configured, then the network element will

accept and provision any qualified Alcatel-Lucent pluggable
module.
11DPM12 OT port state provisioning
The states of the C[1-12], L[1-2], and VA[1-2] ports are provisioned independently. The

Set ains to enabled

....................................................................................................................................................................................................................................
4-95
August 2011
....................................................................................................................................................................................................................................
11DPM12 client port provisioning
The user can provision the 11DPM12 OT for the following client signal types:
OC-3, OC-12, OC-48 / STM-1, STM-4, STM-16

OC-3, OC-12, OC-48 / STM-1, STM-4, STM-16 LOODUK
1GbE
1GbE LOODUK
HDSDI
HDSDI LOODUK
OTU1
ODU1
OC-3, OC-12, OC-48 / STM-1, STM-4, STM-16 client port provisioning
The following attributes are provisionable on the 11DPM12 C1-12 interfaces when the
provisioned signal type is either OC-3, OC-12, OC-48 or STM-1, STM-4, STM-16:
Provisionable
Attribute
channel
container
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Select the container that will be used for client signal to ODU2
multiplexing structure.
Set to optsg proprietary mapping into sub-ODU1 time slots. The

ODU1 will be mapped into ODU2 with AMP per G.709.
Set to odu0 - mapping into ODU0 with GMP per G.709.
Set to odu1 - mapping into ODU1 with GMP per G.709
Default: NULL
Note:
Allowable containers for OC3 are optsg and odu0.
....................................................................................................................................................................................................................................
4-96
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
J0
looduk
16 - Configure J0 format to 16-byte mode.(default)
Configure the client LO ODUk attributes for ODU2 multiplexing

structure.
Note: This entry is applicable only when user selects non-optsg
container for the client port.
mappingmode
Specify the mapping mode for constant bit rate client signals OC48
into OPUk .
Set to async asynchronous mapping CBR into ODUk

information structure by the ODUkP/CBRx adaptation function.
Set to bitsync synchronous mapping CBR into ODUk

information structure by the ODUkP adaptation function. (default)
Note: This entry is applicable to OC48 only.
....................................................................................................................................................................................................................................
4-97
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
For OC-3:
SS-1.1
SL-1.1
SL-1.2
SL-16.2C
SS-16.1A
SS-16.2C
For OC-12
SS-4.1
SL-4.1
SL-4.2
SL-16.2C
SS-16.1A
SS-16.2C
For OC-48
losprop
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1A (includes SS-16.1)
SS-16.2C

Alcatel-Lucent. (default)


....................................................................................................................................................................................................................................
4-98
August 2011
....................................................................................................................................................................................................................................
OC-3, OC-12, OC-48 / STM-1, STM-4, STM-16 LOODUK client port provisioning
provisioned signal type is either OC-3, OC-12, OC-48 or STM-1, STM-4, STM-16
LOODUK. It is applicable only when the client container is ODU0/ODU1/ODUflex.
Provisionable
Attribute
ptmmresp
LO ODUk Payload Type Mismatch Response. Specifies whether the
OT will take a consequent action or pass the received signal.
state
tti
Set to enabled to enable the consequent action.
Set to disabled to disable (turn off) the consequent action.

(default)
Set the LO ODUK admin state.
up turn up the LO ODUk alarm reporting if cross-connect exists

and there is an alarm present.
down suppressing the LO ODUk alarm reporting. (default)


value 00).


....................................................................................................................................................................................................................................
4-99
August 2011
....................................................................................................................................................................................................................................
HDSDI client port provisioning
provisioned signal type is HDSDI:
Provisionable
Attribute
channel
container
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Select the container that will be used for client HD-SDI to ODU2

ODU1 will be mapped into ODU2 with AMP per G.709..
Default: NULL
looduk
Configure client HD-SDI ports LO ODUk attributes for ODU2

Note: This entry is applicable only when user select ODU1 container
for the HD-SDI port..
moduletype

the acceptable Client port moduletype values::
SS-16.1A
SS-16.2C
SL-16.2C


....................................................................................................................................................................................................................................
4-100
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
Applies to both optical and electrical interfaces.

HDSDI LOODUK client port provisioning
provisioned signal type is HDSDI LOODUK. It is applicable only when the client
container is ODU0/ODU1/ODUflex.
Provisionable
Attribute
ptmmresp
state

(default)

....................................................................................................................................................................................................................................
4-101
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


1GbE client port provisioning
provisioned signal type is 1GbE:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
For electrical SFPs, the value none should be used.

container

ODU1 will be mapped into ODU2 with AMP per G.709..
Set to odu0 mapping into ODU0 with GMP per G.709.
Default: NULL
....................................................................................................................................................................................................................................
4-102
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
looduk
Configure client 1GbE ports LO ODUk attributes for ODU2
Note: This entry is applicable only when user select ODU0 container
for the 1GbE port.
moduletype
losprop

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SS-16.1A
SS-16.2C
SL-16.2C
GE-BX20U
GE-BX20D
GE-BX40U
GE-BX40D



....................................................................................................................................................................................................................................
4-103
August 2011
....................................................................................................................................................................................................................................
1GbE LOODUK client port provisioning
provisioned signal type is 1GbE LOODUK:
Provisionable
Attribute
ptmmresp
state
tti

(default)



value 00).


....................................................................................................................................................................................................................................
4-104
August 2011
....................................................................................................................................................................................................................................
3GSDI client port provisioning
provisioned signal type is 3GSDI:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

container
Set to none no mapping method.
- Set to oduflex - mapping with BMP into ODUflex which will be

mapped into ODU2 with GMP per G.709
Default: none
looduk
Configure client 3G-SDI ports LO ODUk attributes for ODU2

Note: This entry is applicable only when user select ODUflex
container for the 3G-SDI port.
moduletype

3GSDI-SH
3GSDI-MH


....................................................................................................................................................................................................................................
4-105
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop

3GSDI LOODUK client port provisioning
provisioned signal type is 3GSDI LOODUK:
Provisionable
Attribute
ptmmresp
state

(default)

....................................................................................................................................................................................................................................
4-106
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


FC100, FC200, FC400 client port provisioning
provisioned signal type is FC100, FC200, FC400:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-107
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
container
Select the container that will be used for client signal to ODU2
Set to none no mapping method.
Set to odu0 - mapping into ODU0 with GMP per G.709.
Set to oduflex - mapping with BMP into ODUflex which will be

mapped into ODU2 with GMP per G.709
Default: none
Note:
Allowable containers for FC100 are odu0.
Allowable containers for FC200 are odu1.
Allowable containers for FC400 are oduflex.
fcmode

x.320, or FICON, or ISC3 Peer Mode). Enter this keyword followed
by:
fc
ficon
isc3peer (applies to FC200 only)
Default: fc
looduk
Configure the client LO ODUk attributes for ODU2 multiplexing

structure.
Note: This entry is applicable only when user select non-optsg
container for the client port.
....................................................................................................................................................................................................................................
4-108
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
acceptable Client port moduletype values.
For FC-100:
2FCLC-L
2FCSN-I
4FCLC-L
4FCSN-I
SS-16.1A
For FC-200:
2FCLC-L
2FCSN-I
4FCLC-L
4FCSN-I
SS-16.1A
For FC-400:
losprop
4FCLC-L
4FCSN-I



....................................................................................................................................................................................................................................
4-109
August 2011
....................................................................................................................................................................................................................................
C100, FC200, FC400 LOODUK client port provisioning
provisioned signal type is C100, FC200, FC400 LOODUK:
Provisionable
Attribute
ptmmresp
state
tti

(default)



value 00).


....................................................................................................................................................................................................................................
4-110
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
channelrx
channeltx
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
'down' state.
gccstat
Specifies the status of GCC0 signal processing. Enter one of the

following values:
....................................................................................................................................................................................................................................
4-111
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
mtu
following:
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.2C
SS-16.1A



Range: 576 1500
ospf helloint

PDU is sent.
Range: 1-65535
ospf deadint

Range: 1-65535
ospf metric

to 40.
Range: 1-65535
ospf md5key
Default: NUL ()
....................................................................................................................................................................................................................................
4-112
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf md5keyid
parameter is mandatory if md5status is enable.
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
tti


value 00).


....................................................................................................................................................................................................................................
4-113
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti



11DPM12 line port provisioning
The line interface on the 11DPM12 OT supports provisionable parameters at the OTU2,
ODU2, and ODU2 LOODUK {1-8} transport layers, as defined in the following tables.
....................................................................................................................................................................................................................................
4-114
August 2011
....................................................................................................................................................................................................................................
The following OTU2 attributes are provisionable on the 11DPM12 L1,2 interface:
Provisionable
Attribute
channelrx
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W {850, 1310, 1550}
Not set: None

channeltx

DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-115
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
efec AMCC Enhanced FEC
efec2- ALU Enhanced FEC type 2 (default)
'down' state.
gccstat
ospf helloint
Set to enabled to enable GCC0 processing (default)
Set to disabled to disable GCC0 processing

PDU is sent.
Range: 1-65535
ospf deadint

ospf metric

to 40.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
....................................................................................................................................................................................................................................
4-116
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
postfecber
Display the 1-second post-fec BER.
prefecber
Display the 1-second pre-fec BER.
mtu

Range: 576 - 1500
moduletype

interface port.
10GB-ZR
XI-64.1
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2b
XS-64.2C


....................................................................................................................................................................................................................................
4-117
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




The following ODU2 attributes are provisionable on the 11DPM12 L1,2 interface:
Provisionable
Attribute
pldtype
ptmmresp

the following:
....................................................................................................................................................................................................................................
4-118
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




....................................................................................................................................................................................................................................
4-119
August 2011
....................................................................................................................................................................................................................................
The following ODU2 attributes are provisionable on the 11DPM12 L1,2 interface:
Provisionable
Attribute
exp_looduk
Modify the exptected LO ODUk structures of HO ODU2 attributes:
To modify LO ODUk of HO ODU2, users must enter a string
containing odukType#oduid-tsMap.
When multiple looduk is needed, users must use & to separate them.
When no string is provided, system will display all expected LO
ODUk of HO ODU2 attributes.
odukType Specifies the ODUk type. Following values are the valid
ODUkTypes.
ODU0 set to ODU0 type.
oduid Specifies the unique ID assigned to the LO ODUk. It is a

single number between 1 to 8. Note: The oduid should be equal to the
smallest Number of its occupied Time slot number.
tsMap Specifies the numbers of Time Slots assigned to the LO
ODUk. It can be a single TS number or TS ranges separated by
comma. Range of TS: [1-8]
Note:
1. If ODUkType is ODU0, ODU0 occupies 1 TS.
2. If ODUkType is ODU1, ODU1 occupies 2 TSs.
Default: the default LO ODUk string for HO ODU2 is
ODU0#1-1&ODU0#2-2&ODU0#3-3&ODU0#4-4&ODU0#55&ODU0#6-6&ODU0#7-7&ODU0#8-8
looduk{1-8}
Configure attributes for a specific LO ODUK in the line ports. See

ODU2 LOODUK{1-8}below.
pldtype
ODU2 Payload Type.

setting, enter this keyword followed by a 2-digit hexadecimal value.
Must be the same on both ends.
0x21 indicate a GMP capable multiplexed ODUk structure

supporting ODTUk.ts and ODTUjk (k=2).
0x20 indicate interworking with legacy 4xODU1 to ODU2

equipment
Default: 0x21
....................................................................................................................................................................................................................................
4-120
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ptmmresp
tti
the following:




....................................................................................................................................................................................................................................
4-121
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tx_looduk
Modify the exptected LO ODUk structures of HO ODU2 attributes:
To modify LO ODUk of HO ODU2, users must enter a string
containing odukType#oduid-tsMap.
When multiple looduk is needed, users must use & to separate them.
When no string is provided, system will display all expected LO
ODUk of HO ODU2 attributes.
odukType Specifies the ODUk type. Following values are the valid
ODUkTypes.
oduid Specifies the unique ID assigned to the LO ODUk. It is a

single number between 1 to 8. Note: The oduid should be equal to the
smallest Number of its occupied Time slot number.
tsMap Specifies the numbers of Time Slots assigned to the LO
ODUk. It can be a single TS number or TS ranges separated by
comma. Range of TS: [1-8]
Note:
1. If ODUkType is ODU0, ODU0 occupies 1 TS.
2. If ODUkType is ODU1, ODU1 occupies 2 TSs.
Default: the default LO ODUk string for HO ODU2 is
ODU0#1-1&ODU0#2-2&ODU0#3-3&ODU0#4-4&ODU0#55&ODU0#6-6&ODU0#7-7&ODU0#8-8
Note: The tx_looduk structure can be changed only when the
adminState of the related LO ODUk is down, and No XC present.
ODU2 LOODUK {1-8} client port provisioning
The following attributes are provisionable on the 11DPM12 L1,2 interface: when the
provisioned signal type is ODU2 LOODUK {1-8}:
Provisionable
Attribute
state
up turn up the LO ODUk alarm reporting if there is an alarm

regardless the present of cross-connect..
....................................................................................................................................................................................................................................
4-122
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti



11DPM12 VA port provisioning
The VA port on the 11DPM12 OT supports the OCH attributes for the eVOA ports
(VA{1-2}) on the 11DPM12 card as defined in the following table.
The following OCH attributes are provisionable on the 11DPM12 VA interface:

Provisionable
Attribute
moduletype
sVOA slow VOA
fVOA fast VOA

module.
Default: auto
....................................................................................................................................................................................................................................
4-123
August 2011
....................................................................................................................................................................................................................................
11QPA4 OT port state provisioning
The states of the C[1-4], L[1-4], and VA[1-4] ports are provisioned independently. The

Set ains to enabled
Note: For 11QPA4, the line-side laser is shut down if the port state is provisioned to
"down". The line-side laser is turned on if the port state is set to "up" or
"maintenance".
11QPA4 client port provisioning
The user can provision the 11QPA4 OT for the following client signal types:
OC-192
STM-64
10GbE
OTU2
FC-10G
FC-8G
....................................................................................................................................................................................................................................
4-124
August 2011
....................................................................................................................................................................................................................................
OC-192 or STM-64 client port provisioning
The following attributes are provisionable on the 11QPA4 C1-4 interfaces when the
provisioned signal type is either OC-192 or STM-64:
Provisionable
Attribute
channel
J0
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Configure J0 attributes.
j0_ex - Expected J0. Enter this keyword followed by either one of the
following:
j0_fmt - J0 format. Enter this keyword followed by a value for the J0

format:
<value> = 1: configure J0 format to 1-byte mode
<value> = 16:configure J0 format to 16-byte mode
Default: 16
trccmp - J0 trace compare. This keyword enables and disables the
comparison between the incoming J0 value and the provisioned (i.e.,
expected) value.
Set to enabled to enable comparison
Set to disabled to disable comparison
Default: disabled
....................................................................................................................................................................................................................................
4-125
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
sdth
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.



expressed as 10-n.
sfth
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6

expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
....................................................................................................................................................................................................................................
4-126
August 2011
....................................................................................................................................................................................................................................
The following attributes are provisionable on the 11QPA4 C1-4 interfaces when the signal
Provisionable
Attribute
channel
encmode
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

cbrlan11.049
cbrlan11.096

G.7041)


errfrmdrop

....................................................................................................................................................................................................................................
4-127
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
10GB-ZR
10GB-SR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


Provisionable
Attribute
channelrx
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-128
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
channeltx
fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
'down' state.
gccstat
moduletype
losprop

following:
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C


....................................................................................................................................................................................................................................
4-129
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf helloint
PDU is sent.
Range: 1-65535
ospf deadint

ospf metric

to 30.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
postfecber
prefecber
....................................................................................................................................................................................................................................
4-130
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
mtu
Range: 576 - 1500
oturate
tti
Specifies the client OTU2 rate.
Set to 10.709 for standard OTU2 rate (default)
Set to 11.049 for 11.049 Gb/s overclocked rate
Set to 11.096 for 11.096 Gb/s overclocked rate


value 00).


....................................................................................................................................................................................................................................
4-131
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


provisioned client signal type is FC10G:
Provisionable
Attribute
channel
encmode
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

signal. Enter this keyword followed by one of the following four
values:
cbrlan11.049
cbrlan11.096

G.7041)

Default: gfp-f
....................................................................................................................................................................................................................................
4-132
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
errfrmdrop
enabled
disabled
Default: disabled
moduletype
losprop

XI-64.1
10GB-SR
10GB-ZR
XS-64.2B
XS-64.2C
XL-64.2C

Alcatel-Lucent.


....................................................................................................................................................................................................................................
4-133
August 2011
....................................................................................................................................................................................................................................
provisioned client signal type is FC8G:
Provisionable
Attribute
channel
moduletype
encmode
B&W: {1310}
Not set: None

X8FCLC-L
X8FCSN-I

Alcatel-Lucent.

Specifies the encapsulation mode used to transport the 8G- FC client

signal. Enter this keyword followed by the value of gfp-t.
Default: gfp-t
losprop

11QPA4 line port provisioning
The line interface on the 11QPA4 OT supports provisionable parameters at the OTU2 and
ODU2 transport layers, as defined in the following tables.
Note: If one line port is assigned while the other line port is unassigned, the assigned
line port is set to CrossRegen firstly, the other unassigned line port will copy the
attribute of the assigned line port including oprmode value and OTU2 rate.
....................................................................................................................................................................................................................................
4-134
August 2011
....................................................................................................................................................................................................................................
The following OTU2 attributes are provisionable on the 11QPA4 L1,2 interface:
Provisionable
Attribute
channelrx
Specifies the expected receive channel frequency or wavelength of the
pluggable module. Not settable for internal topology connections.
DWDM frequencies: {9605, 9600, 9595, 9590, 9585, 9580, 9575,
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170}
channelrxt
CWDM wavelengths: {1471, 1491, 1511, 1531, 1551, 1571, 1591,

1611}
Not set: None
Specifies the expected transmit channel frequency or wavelength of

the pluggable module. Not settable for internal topology connections.
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170}
gccstat

1611}
Not set: None
....................................................................................................................................................................................................................................
4-135
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
oprmode
following:
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2C


Operational mode of the 11QPA4. This parameter applies to all line

ports.
Set to ADDDROP In this mode pack is processing signal in both

transmission directions (ingress, from client port towards the line
side; egress, from line side to client port)
Set to CROSSREGEN In this mode the Line port input signal is

looped towards another line port output via 8x8 matrix.
Corresponding client ports cannot be used.
1) Value : L{1-4}
2) value must be different than its own port
Set to ADDONLY in this mode, pack is processing signal in

ingress direction (form client port towards the line side)
Value: C{1-4}
Set to DROPCONTINUE In this mode, pack is processing the

signal in egress direction and looping the signal from the line side
input towards the line side output.
Default: ADDDROP
ospf helloint

PDU is sent.
Range: 1-65535
....................................................................................................................................................................................................................................
4-136
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf deadint

ospf metric

to 30.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
postfecber
prefecber
mtu

Range: 576 - 1500
....................................................................................................................................................................................................................................
4-137
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
correction on the interface port:
Set to efec AMCC Enhanced FEC (Default)
Set to rsfec Reed-Solomon FEC
Set to efec2 ALU Enhanced FEC
'down' state.
oturate
values:
11.049 (Gb/s)
11.096 (Gb/s)
Note: this parameter is provisionable only when the line side oprmode
is CROSSREGEN.
tti
CrossRegPartner




Displays the CrossRegPartner port when oprmode is crossRegen

Note: When oprMode is not crossRegen, this field displays as NONE.
multicastfrom
Display the multicastfrom information when oprmode is addonly.

Value: C{1-4}, None
Note: when oprmode is not addonly, this field displays as none.
....................................................................................................................................................................................................................................
4-138
August 2011
....................................................................................................................................................................................................................................
The following ODU2 attributes are provisionable on the 11QPA4 L1,2 interface:
Provisionable
Attribute
mappingmode
pldtype
ODUkp to CBRx mapping mode. This attribute specifies the mappng
mode that wil be used when the client port signal is provisioned to
OC-192, STM-64 or 10GbE WAN.
Set to bitsync bit synchronous CBR mapping
Set to async asynchronous CBR mapping
Specifies the value of the Payload Type field of a Payload Structure

Identifier in the OTUk frame. pldtype has a default value and is based
on the encoded client signal. This attribute only applies when the
client signal is not an OTM0.2 signal.
ptmmresp
tti

the following:




....................................................................................................................................................................................................................................
4-139
August 2011
....................................................................................................................................................................................................................................
11QPA4 VA port provisioning
Note:
11QPA4/VA[1-4]] cannot connect to any SFDxx Channel Out

11QPA4/VA[1-4] Out cannot connect to 11QPA4/VA[1-4] In
The VA port on the 11QPA4 OT supports the OCH attributes for the eVOA ports
(VA{1-4}) on the 11QPA4 card as defined in the following table.
The following OCH attributes are provisionable on the 11QPA4 VA interface:

Provisionable
Attribute
moduletype
sVOA slow VOA
fVOA fast VOA

module.
Default: auto
112SA1L OT port state provisioning
are supported:

Set ains to enabled
....................................................................................................................................................................................................................................
4-140
August 2011
....................................................................................................................................................................................................................................
112SA1L client port provisioning
The user can provision the 112SA1L OT for the following client signal types:
hundredGige
HundredGige LAN client port provisioning
The following attributes are provisionable on the 112SA1L C1 interface when the signal
type is provisioned to hundredGige:
Provisionable
Attribute
errfrmdrop
moduletype
losprop
Specifies the CFP pluggable module type to be used on the specified

following:
C113G4C (100GbE only)
C113G4D (dual rate, 100GbE/OTU4)
C113G10C (10x10G)

Alcatel-Lucent.

far-end client-facing receiver. Enter one of the following:
112SA1L line port provisioning
The line interface on the 112SA1L OT supports provisionable parameters at the OTU4
....................................................................................................................................................................................................................................
4-141
August 2011
....................................................................................................................................................................................................................................
The following OTU4 attributes are provisionable on the 112SA1L L1 interface:

Provisionable
Attribute
channel
Attribute that configures the frequency of the tunable transponder. Set
to one of the following values:
DWDM frequencies: {9285, 9280. 9275, 9270, 9265, 9260, 9255,
9250, 9245, 9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200,
9195, 9190, 9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145,
9140, 9135, 9130, 9125, 9120, 9115, 9110, 9105, 9100, 9095, 9090,
9085, 9080, 9075, 9070, 9065, 9060, 9055, 9050, 9045, 9040, 9035,
9030, 9025, 9020, 9015, 9010, 9005, 9000, 8995, 8990, 8985, 8980,
8975, 8970, 8965, 8960, 8955, 8950, 8945, 8940, 8935, 8930, 8925,
8920, 8915, 8910, 8905, 8900, 8895, 8890, 8885, 8880, 8875, 8870,
8865, 8860, 8855, 8850, 8845, 8840, 8835, 8830, 8825, 8820, 8815,
8810, 8805, 8800, 8795, 8790, 8785, 8780, 8775, 8770, 8765, 8760,
8755, 8750, 8745, 8740, 8735, 8730, 8725, 8720, 8715, 8710, 8705,
8700, 8695, 8690, 8685, 8680, 8675, 8670, 8665, 8660, 8655, 8650}
oprmode
tti
Not set: None
Operation mode. Specifies the type of operation mode on the interface

port. Enter this keyword followed by one of the following values:
ADDDROP
REGEN




....................................................................................................................................................................................................................................
4-142
August 2011
....................................................................................................................................................................................................................................
The following ODU4 attributes are provisionable on the 112SA1L L1 interface:

Provisionable
Attribute
pldtype
Default: 20
ptmmresp
tti

the following:




112SCA1 OT port state provisioning
are supported:

....................................................................................................................................................................................................................................
4-143
August 2011
....................................................................................................................................................................................................................................
Set ains to enabled
112SCA1 client port provisioning
The user can provision the 112SCA1 OT for the following client signal types:
100GbE
OTU4
ODU4
The following attributes are provisionable on the 112SCA1 C1 interface when the signal
Provisionable
Attribute
errfrmdrop
moduletype

C113G4C
C113G10C

Alcatel-Lucent.

....................................................................................................................................................................................................................................
4-144
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
far-end client-facing receiver. Enter one of the following:
The following attributes are provisionable on the 112SCA1 C1 interface when the
provisioned client signal type is ODU4:
Provisionable
Attribute
tti


The following attributes are provisionable on the 112SCA1 C1 interface when the
Provisionable
Attribute
fectype
'down' state.
....................................................................................................................................................................................................................................
4-145
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
following:
C113G4C
C113G10C


tti


value 00).


....................................................................................................................................................................................................................................
4-146
August 2011
....................................................................................................................................................................................................................................
112SCA1 line port provisioning
The line interface on the 112SCA1 OT supports provisionable parameters at the OTU4
The following OTU4 attributes are provisionable on the 112SCA1 L1 interface:

Provisionable
Attribute
channel
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
fectype
Not set: None

correction on the interface port.
AFEC (Alcatel-Lucent FEC)
Note: In 100G packs, the corrected counts can increase incrementally

due to preFec errors. This is normal behavior for 100G packs.
'down' state.
cdtarget
Chromatic Dispersion target. Specifies the target received chromatic

dispersion. Enter this keyword followed by a value: {-35000 to
+35000} ps/nm. Step size is 1000 ps/nm.
....................................................................................................................................................................................................................................
4-147
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




The following ODU4 attributes are provisionable on the 112SCA1 L1 interface:

Provisionable
Attribute
pldtype
Default: 20
ptmmresp

the following:
....................................................................................................................................................................................................................................
4-148
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




112SCX10 OT port state provisioning


Set ains to enabled
112SCX10 client port provisioning
The user can provision the 112SCX10 OT for the following client signal types:
10GbE LAN
OTU2
....................................................................................................................................................................................................................................
4-149
August 2011
....................................................................................................................................................................................................................................
ODU2
OC-192
STM-64
The following attributes are provisionable on the 112SCX10 C1-10 interfaces when the
signal type is provisioned to 10GbE LAN:
Provisionable
Attribute
channel
encmode
errfrmdrop
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

GFP-F - (Standard, frame-based GFP encapsulation mode)
GFP-P - (Proprietary GFP encapsulation mode, semi-transparent)
....................................................................................................................................................................................................................................
4-150
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
10GB-ZR
10GB-SR
L-64.2
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-151
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
J0_ex
J0_fmt
trccmp
moduletype
losprop
mappingmode

10GB-ZR
10GB-SR
L-64.2
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


Specifies the mapping mode used for the SONET/SDH signal.
Set to bitsync for bit synchronous CBR mapping
Set to async for asynchronous CBR mapping
Default = previously existing value
....................................................................................................................................................................................................................................
4-152
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
sdth
expressed as 10-n.
sfth
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6

expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
Provisionable
Attribute
channel
fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
RSFEC - Configure Reed-Solomon FEC
Note: The 100G MUX OTs support the following FECTYPES on the
client interfaces: RSFEC, NOFEC, EFEC, and EFEC2.
'down' state.
....................................................................................................................................................................................................................................
4-153
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
oturate
10GB-ZR
10GB-SR
L-64.2
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


values:
11.049 (Gb/s)
11.096 (Gb/s)
....................................................................................................................................................................................................................................
4-154
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


Provisionable
Attribute
tti


....................................................................................................................................................................................................................................
4-155
August 2011
....................................................................................................................................................................................................................................
112SCX10 line port provisioning
The line interface on the 112SCX10 OT supports provisionable parameters at the OTU4
The following OTU4 attributes are provisionable on the 112SCX10 L1 interface:

Provisionable
Attribute
channelrx
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
Not set: None
channeltx
Display the transmit channel frequency of the tunable transponder.
fectype

Note: The 100G MUX OTs support the following FECTYPES on the
client interfaces: RSFEC, NOFEC, EFEC, and EFEC2.
'down' state.
....................................................................................................................................................................................................................................
4-156
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
oprmode
Operation Mode. Specifies the mode of the pack. Enter this keyword
followed by one of the following values:
add_drop
regen
Note: The 100G OTs in REGEN mode are unidirectional where Line
Input port is connected to one Line while the Line Output port is
connected to a different line.
postfecber
prefecber
tti




The following ODU4 attributes are provisionable on the 112SCX10 L1 interface:

Provisionable
Attribute
pldtype
Default: 20
....................................................................................................................................................................................................................................
4-157
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ptmmresp
tti
the following:




112SX10L OT port state provisioning

Set ains to enabled

....................................................................................................................................................................................................................................
4-158
August 2011
....................................................................................................................................................................................................................................
112SX10L client port provisioning
The user can provision the 112SX10L OT for the following client signal types:
10GbE
OTU2
ODU2
OC-192
STM-64
The following attributes are provisionable on the 112SX10L C1-10 interfaces when the
signal type is provisioned to 10GbE LAN:
Provisionable
Attribute
channel
encmode
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

GFP-F - specifies the use of the Generic Framing protocol (ITU-T

G.7041)
GFP-P - Generic Framing Protocol, Proprietary, where the client

cbrlan11.049 - specifies the use of 11.049 transparent mapping
cbrlan11.096 - specifies the use of 11.096 transparent mapping
Note: Traffic restoration takes 80-90 seconds when encmode is

changed to CBR.
errfrmdrop
....................................................................................................................................................................................................................................
4-159
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
10GB-ZR
10GB-SR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


Provisionable
Attribute
channel
J0_ex
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-160
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
J0_fmt
trccmp
moduletype
losprop
mappingmode

10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


Specifies the mapping mode used for the SONET/SDH signal.
Set to bitsync for bit synchronous CBR mapping
Set to async for asynchronous CBR mapping
Default = previously existing value

sdth

expressed as 10-n.
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6
....................................................................................................................................................................................................................................
4-161
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
sfth
expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
Provisionable
Attribute
channel
fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Set to efec Enhanced FEC
Set to efec2 ALU FEC
'down' state.
....................................................................................................................................................................................................................................
4-162
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
oturate
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


values:
11.049 (Gb/s)
11.096 (Gb/s)
....................................................................................................................................................................................................................................
4-163
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


Provisionable
Attribute
tti


....................................................................................................................................................................................................................................
4-164
August 2011
....................................................................................................................................................................................................................................
112SX10L line port provisioning
The line interface on the 112SX10L OT supports provisionable parameters at the OTU4
The following OTU4 attributes are provisionable on the 112SX10L L1 interface:

Provisionable
Attribute
channeltx
Attribute that configures the transmit frequency of the tunable
transponder. Set to one of the following values:
DWDM: {9285, 9280. 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115, 9110, 9105, 9100, 9095, 9090, 9085, 9080,
9075, 9070, 9065, 9060, 9055, 9050, 9045, 9040, 9035, 9030, 9025,
9020, 9015, 9010, 9005, 9000, 8995, 8990, 8985, 8980, 8975, 8970,
8965, 8960, 8955, 8950, 8945, 8940, 8935, 8930, 8925, 8920, 8915,
8910, 8905, 8900, 8895, 8890, 8885, 8880, 8875, 8870, 8865, 8860,
8855, 8850, 8845, 8840, 8835, 8830, 8825, 8820, 8815, 8810, 8805,
8800, 8795, 8790, 8785, 8780, 8775, 8770, 8765, 8760, 8755, 8750,
8745, 8740, 8735, 8730, 8725, 8720, 8715, 8710, 8705, 8700, 8695,
8690, 8685, 8680, 8675, 8670, 8665, 8660, 8655, 8650}
Not set: None
channelrx

DWDM: {9285, 9280. 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115, 9110, 9105, 9100, 9095, 9090, 9085, 9080,
9075, 9070, 9065, 9060, 9055, 9050, 9045, 9040, 9035, 9030, 9025,
9020, 9015, 9010, 9005, 9000, 8995, 8990, 8985, 8980, 8975, 8970,
8965, 8960, 8955, 8950, 8945, 8940, 8935, 8930, 8925, 8920, 8915,
8910, 8905, 8900, 8895, 8890, 8885, 8880, 8875, 8870, 8865, 8860,
8855, 8850, 8845, 8840, 8835, 8830, 8825, 8820, 8815, 8810, 8805,
8800, 8795, 8790, 8785, 8780, 8775, 8770, 8765, 8760, 8755, 8750,
8745, 8740, 8735, 8730, 8725, 8720, 8715, 8710, 8705, 8700, 8695,
8690, 8685, 8680, 8675, 8670, 8665, 8660, 8655, 8650}
Not set: None
....................................................................................................................................................................................................................................
4-165
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype

'down' state.
oprmode
Operation Mode. Specifies the mode of the pack. Enter this keyword
followed by one of the following values:
add_drop
regen
Note: The 100G OTs in REGEN mode are unidirectional where Line
Input port is connected to one Line while the Line Output port is
connected to a different line.
postfecber
prefecber
tti




....................................................................................................................................................................................................................................
4-166
August 2011
....................................................................................................................................................................................................................................
The following ODU4 attributes are provisionable on the 112SX10L L1 interface:

Provisionable
Attribute
pldtype
Default: 20
ptmmresp
tti

the following:




4DPA4 OT port state provisioning
The states of the C1-4 and L1-2 ports are provisioned independently. The following port

....................................................................................................................................................................................................................................
4-167
August 2011
....................................................................................................................................................................................................................................
Set ains to enabled
4DPA4 client port provisioning
The user can provision the 4DPA4 OT for the following client signal types:
GbE
OC3
STM1
OC12
STM4
OC48
STM16
FC100, FC200, FC400
DVBASI, FE, HDSDI, SDSDI
Note: For 4DPA4, available bandwidth validation is done only when timeslots are
assigned; not when the client port is created. (This is different from 11STMM10 OT
behavior.)
The following attributes are provisionable on the 4DPA4 C1-4 interfaces when the signal
type is provisioned to GbE :
Port Attribute
channel
Description
Specifies the expected wavelength of the pluggable module.
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-168
August 2011
....................................................................................................................................................................................................................................
Port Attribute
losprop
moduletype
Description

following:

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SL-16.2C
SS-16.1A
SS-16.2C
GE-BX20U
GE-BX20D
GE-BX40U
GE-BX40D

Alcatel-Lucent.

....................................................................................................................................................................................................................................
4-169
August 2011
....................................................................................................................................................................................................................................
Port Attribute
timeslot
[line | vts]
Description
Specifies the line port and the timeslot on the line port, that the client
port will be mapped to. Both line and vts parameters must be included.
Both must be zero, or both must be non-zero. Enter the keyword
timeslot followed by:
The keyword line and a linenum value as follows. Range: {0-2}

Enter 0 to unassign the client port from any line port.
Enter 1 to assign the client port to L1.
The keyword vts and a vtslist value as follows. Range: {0-2}

The value 0 unassigns the client port from any timeslots.
The value 1 assigns the client port to the timeslots of ODU0
#1: 1,3,5,7,9,11,13,15.
The value 2 assigns the client port to the timeslots of ODU0
#2: 2,4,6,8,10,12,14,16.
OC3/OC12/OC48 and STM1/STM4/STM16 client port provisioning
type is provisioned to OC3/OC12/OC48 and STM1/STM4/STM16 :
Port Attribute
channel
Description
losprop
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-170
August 2011
....................................................................................................................................................................................................................................
Port Attribute
moduletype
Description
following:

For OC3/STM1:
SL-1.1
SL-1.2
SL-16.2C
SS-1.1
SS-16.1A
SS-16.2C
FE-BX40U
FE-BX40D
For OC12/STM4:
SS-4.1
SL-4.1
SL-4.2
SL-16.2C
SS-16.1A
SS-16.2C
GE-BX20U
GE-BX20D
GE-BX40U
GE-BX40D
For OC48/STM16:
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1
SS-16.1A
SS-16.2C


....................................................................................................................................................................................................................................
4-171
August 2011
....................................................................................................................................................................................................................................
Port Attribute
timeslot
[line | vts]
Description
Specifies the line port, and the timeslot on the line port, that the client

The keyword vts and a vtslist value as follows. Range: {0-16,

vtslist}
For STM-1 clients: Enter 0, or any single timeslot from 1 to
16.
For STM-4 clients: Enter 0, or a vtslist representing four
timeslots from 1 to 16. The vtslist can include a list of
individual timeslots and/or a list of timeslot ranges. If only
one timeslot is specified, the request is for a contiguous range
of timeslots starting at that value.
For STM-16 clients: Enter 0, or 1. Timeslot 1 represents the
entire OTU1 line capacity (all 16 timeslots).
FC100, FC200, FC400 client port provisioning
type is provisioned to FC100, FC200, FC400:
Port Attribute
channel
fcmode
Description
Specifies the expected wavelength of the pluggable module. Enter this
keyword to display the current setting. To change the setting, enter this
keyword followed by one of the following values:
B&W: {850, 1310, 1550}
Not set: None

x.320, or FICON, or ISC3 Peer Mode). Enter this keyword followed
by:
fc (default)
ficon
isc3peer (applies to FC200 only)
....................................................................................................................................................................................................................................
4-172
August 2011
....................................................................................................................................................................................................................................
Port Attribute
losprop
moduletype
Description

following:

FC100, FC200, FC400:
4FCLC-L
4FCSN-1
FC100 and FC200:
SS-16.1A


....................................................................................................................................................................................................................................
4-173
August 2011
....................................................................................................................................................................................................................................
Port Attribute
timeslot
[line | vts]
Description


vtslist}
For FC100 clients: Enter 0, or a vtslist representing seven
For FC200 clients: Enter 0, or a vtslist representing fourteen
DVBASI, FE, HDSDI, SDSDI client port provisioning
type is provisioned to FE:
Port Attribute
channel
Description
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-174
August 2011
....................................................................................................................................................................................................................................
Port Attribute
hdsdirate
Description
Specifies the HD-SDI signal rate. Applies only when port type =
hdsdi.
1.485 standard rate, 1.485 Gb/s
1.485/1.001 rate compatible with existing NTSC systems
Default = 1.485/1.001
losprop
moduletype

following:

For FE:
100BLX10
FE-BX40D
FE-BX40U
For DVB ASI, HD-SDI, and SD-SDI:
SS-16.1A
SS-16.2C
SL-16.2C


....................................................................................................................................................................................................................................
4-175
August 2011
....................................................................................................................................................................................................................................
Port Attribute
timeslot
[line | vts]
Description


vtslist}
For FE clients: Enter 0, or any single timeslot from 1 to 16.
For DVB ASI and SD-SDI clients: Enter 0, or a vtslist
representing two timeslots from 1 to 16. The vtslist can
include a list of individual timeslots and/or a list of timeslot
ranges. If only one timeslot is specified, the request is for a
contiguous range of timeslots starting at that value.
For HD-SDI clients: Enter 0, or a vtslist representing ten
4DPA4 line port provisioning
Note: 4DPA4/L[1-2] cannot connect to any CWR8 CLS In.

Note: The 4DPA4 pack is used in Pt-Pt configurations to provide transport of
multiplexed FC-100/200 signals over an OTU1 structure. In egress direction, physical
layer impairments are monitored at OTU1/ODU1 layers (including FEC error counts).
Any errors that cant be corrected are counted on the line port and correspond to PCS
layer errors in Tx direction of client FC-100/200 bit stream (i.e., any error observed
on the client egress bit stream resulting from DWDM/CWDM line impairment is
detected and counted as a PM event on the associated ODU1/OTU1 line port input).
The line interface on the 4DPA4 OT supports provisionable parameters at the OTU1 and
ODU1 transport layers, as defined in the following tables.
....................................................................................................................................................................................................................................
4-176
August 2011
....................................................................................................................................................................................................................................
The following OTU1 attributes are provisionable on the 4DPA4 L1 and L2 interface:
Provisionable
Attribute
channelrx
channeltx
fectype
pluggable module. Enter this keyword to display the current setting.
To change the setting, enter this keyword followed by one of the
following values:

9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440,
9430, 9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340,
9330, 9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200, 9190, 9180, 9170}

1611}
B&W wavelengths: {850, 1310, 1550}
Not set: None
Specifies the expected transmit channel frequency or wavelength of

the pluggable module. Enter this keyword to display the current
setting. To change the setting, enter this keyword followed by one of
the following values:

9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440,
9430, 9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340,
9330, 9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200, 9190, 9180, 9170}

1611}
B&W wavelengths: {850, 1310, 1550}
Not set: None

rsfec - Reed-Solomon FEC (default)
nofec No forward error correction.
'down' state.
gccstat
enabled to enable GCC0 processing.
disabled to disable GCC0 processing (default).
....................................................................................................................................................................................................................................
4-177
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
Specifies the pluggable module type to be used on the specified line
port. Enter this keyword to display the current setting. To change the
FlexMux:
SL-16.1
SL-16.2C
SL-16.2D
SS-16.1A
SS-16.2C
DualTran:
oprmode
ospf helloint
4FC-OC
4FC-OD


Operational mode of the 4DPA4. This parameter applies to both line

ports, but it can be set only on port L1. The L2 value is read-only, and
is always equal to the L1 value.
Set to ADDDROP Add/Drop Mode. Client port signals can be

added and dropped to/from the line ports. There is no regen
function. (Default)
Set to CROSSREGEN Cross Regeneration Mode. Line-to-line

regen function is activated. Client ports cannot be used.

PDU is sent.
Range: 1-65535
ospf deadint

....................................................................................................................................................................................................................................
4-178
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf metric
to 40.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
mtu

Range: 576 - 1500
....................................................................................................................................................................................................................................
4-179
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti
Configure the OTU1 Trail Trace Indentifier attributes:




The following ODU1 attributes are provisionable on the 4DPA4 L1 and L2 interface:
Provisionable
Attribute
odu0interwk
Standard ODU0 Interworking. When disabled, ODU1 Payload Type
should be set to 0x80 and there is proprietary encoding of OPTS OH
in PSI bytes and LosProp in APS/PCC bytes. The 4DPA4 can then
interwork at 2xODU0 only with another 4DPA4 at the far end. When
enabled, ODU1 Payload Type should be set to 0x20 (ODU multiplex
structure) and there is no proprietary use of PSI or APS/PCC bytes.
The 4DPA4 can then interwork with standard 2xODU0 equipment at
the far end. Enter this keyword to display the current setting. To
following:
enabled to enable standard ODU0 interworking.
disabled to disable (turn off) standard ODU0 interworking

(default).
Important: When client signals are not GbE, the odu0interwk

parameter must be set to DISABLE. ODU0 interworking is only valid
for GbE traffic.
Note: ODU0INTERWK and PLDTYPE attributes must be
provisioned consistently (synchronized).
....................................................................................................................................................................................................................................
4-180
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
pldtype
ODU1 Payload Type. Enter this keyword to display the current
setting. To change the setting, enter this keyword followed by a 2-digit
hexadecimal value. Must be the same on both ends.
0x80 indicates a proprietary mixture of sub-ODU1 signals

(default).
0x20 indicates standard 2xODU0 interworking.
Note: ODU0INTERWK and PLDTYPE attributes must be

provisioned consistently (synchronized).
ptmmresp
tti

the following:




4DPA4 VA port provisioning
Note:
4DPA4/VA[1-2] cannot connect to any CWR8 CLS Out

4DPA4/VA[1-2] cannot connect to any SFDxx Channel Out
4DPA4/VA[1-2] Out cannot connect to 4DPA4/L[1-2] In
The VA port on the 4DPA4 OT supports the OCH attributes for the eVOA ports
(VA{1-2}) on the 4DPA4 card as defined in the following table.
....................................................................................................................................................................................................................................
4-181
August 2011
....................................................................................................................................................................................................................................
The following OCH attributes are provisionable on the 4DPA4 VA interface:

Provisionable
Attribute
moduletype
following:
fVOA


4DPA2 OT port state provisioning
The states of the C1,2 and L1,2 ports are provisioned independently. The following port


Set ains to enabled
4DPA2 client port provisioning
The user can provision the 4DPA2 OT for the following client signal type:
STM16
OC48
1GbE
....................................................................................................................................................................................................................................
4-182
August 2011
....................................................................................................................................................................................................................................
OC48 or STM16 client port provisioning
The following attributes are provisionable on the 4DPA2 C1,2 interfaces when the signal
type is provisioned to OC48 or STM16:
Port Attribute
channel
Description
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

following:

For OC48/STM16:
SL-16.1
SL-16.2C
SS-16.1A
SS-16.2C


1GbE client port provisioning
The following attributes are provisionable on the 4DPA2 C1,2 interfaces when the signal
type is provisioned to 1GbE:
Port Attribute
channel
Description
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

....................................................................................................................................................................................................................................
4-183
August 2011
....................................................................................................................................................................................................................................
Port Attribute
moduletype
Description
following:

For 1GbE:
1000B-LX
1000B-SX
1000B-T
SL-16.2C
SS-16.1A
SS-16.2C


4DPA2 line port provisioning
For 4DPA2, the line port is automatically created when the client port is created and the
line port is deleted when the client port is deleted. The L1 and L2 interface on the 4DPA2
OT supports provisionable parameters as defined in the following tables.
OC48 or STM16 line port provisioning
The following OC48 or STM16 attributes are provisionable on the 4DPA2 L1 and L2
interface:
Provisionable
Attribute
channel
Specifies the expected channel frequency or wavelength of the
following values:

9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440,
9430, 9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340,
9330, 9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200, 9190, 9180, 9170}
Not set: None
....................................................................................................................................................................................................................................
4-184
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
Enter one of the acceptable line port moduletype values:

SL-16.2D


1GbE line port provisioning
The following 1GbE attributes are provisionable on the 4DPA2 L1 and L2 interface:
Provisionable
Attribute
channel
moduletype
Specifies the expected channel frequency or wavelength of the
following values:

9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440,
9430, 9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340,
9330, 9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200, 9190, 9180, 9170}
Not set: None

Enter one of the acceptable line port moduletype values:

SL-16.2D


....................................................................................................................................................................................................................................
4-185
August 2011
....................................................................................................................................................................................................................................
43SCX4 / 43STX4(P) OT port state provisioning

Set ains to enabled
43SCX4 / 43STX4(P) client port provisioning
The user can provision the 43SCX4 / 43STX4(P) OT for the following client signal types:
FC8G
10GbE LAN
OC-192
STM-64
OTU2
FC8G client port provisioning
The following attributes are provisionable on the 43SCX4 / 43STX4(P) C1-4 interface
when the signal type is provisioned to FC8G:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-186
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
following:
X8FCLC-L
X8FCSN-I



when the signal type is provisioned to 10GbE LAN:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
4-187
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
encmode

G.7041)

Note: On 43STX4(P) boards GFP-F and GFP-P encapsulations are

available. Both modes will add delay in LFI/RFI alarm generation or
transport. When interworking with MPLS routers it is recommended
to implement link monitoring protocols on router side.
errfrmdrop
moduletype
losprop


following:
10GB-SR
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C



....................................................................................................................................................................................................................................
4-188
August 2011
....................................................................................................................................................................................................................................
when the provisioned signal type is either OC-192 or STM-64:
Provisionable
Attribute
channel
J0_ex
J0_fmt
trccmp
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Disable - Disable J0 comparison (default).

following:
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C


....................................................................................................................................................................................................................................
4-189
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
mappingmode
Mapping Mode. Specifies the mapping mode used for the

SONET/SDH signal.
async for asynchronous mapping
bitsync for bit-synchronous mapping
when the provisioned client signal type is OTU2:
Provisionable
Attribute
channel
fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Set to efec Enhanced FEC
Set to efec2 ALU FEC
'down' state.
....................................................................................................................................................................................................................................
4-190
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
tti
following:
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C





value 00).


....................................................................................................................................................................................................................................
4-191
August 2011
....................................................................................................................................................................................................................................
when the provisioned client signal type is OTU2:
Provisionable
Attribute
tti


43SCX4 / 43STX4(P) line port provisioning
The line interface on the 43SCX4 / 43STX4(P) OT supports provisionable parameters at

the OTU3 and ODU3 transport layers, as defined in the following tables.
Note: Provisioning max power on 43SCX4 OT is limited and cannot be provisioned
to 4dB on the line port of the OT.
43SCX4 OTU3 line port provisioning
The following OTU3 attributes are provisionable on the 43SCX4 L1 interface:

Provisionable
Attribute
channelrx
Attribute that configures the receive frequency.
Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515,
9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365,
9360, 9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315,
9310, 9305, 9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265,
9260, 9255, 9250, 9245, 9240, 9235, 9230, 9225, 9220, 9215,
9210, 9205, 9200, 9195, 9190, 9185, 9180, 9175, 9170, 9165,
9160, 9155, 9150, 9145, 9140, 9135, 9130, 9125, 9120, 9115}
Not set: None
....................................................................................................................................................................................................................................
4-192
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
channeltx
oprmode
Attribute that configures the transmit frequency.
Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515,
9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365,
9360, 9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315,
9310, 9305, 9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265,
9260, 9255, 9250, 9245, 9240, 9235, 9230, 9225, 9220, 9215,
9210, 9205, 9200, 9195, 9190, 9185, 9180, 9175, 9170, 9165,
9160, 9155, 9150, 9145, 9140, 9135, 9130, 9125, 9120, 9115}
Not set: None
Operation mode. Specifies the type of operation mode supported on

the interface
Set to:
ADDDROP Add/Drop mode
REGEN Regeneration mode
postfecber
prefecber
tti
Configure OTU3 Trail Trace Indentifier attributes:




....................................................................................................................................................................................................................................
4-193
August 2011
....................................................................................................................................................................................................................................
43STX4(P) OTU3 line port provisioning
The following OTU3 attributes are provisionable on the 43STX4(P) L1 interface:

Provisionable
Attribute
channel
The following applies to 43STX4:
Enter one of the following: {0, 9600, 9590, 9580, 9570, 9560, 9540,
9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430,
9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210,
9200, 9190, 9180, 9170}
The following applies to 43STX4P:
9575, 9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525,
9520, 9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470,
9465, 9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360,
9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305,
9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250,
9245, 9240, 9235, 9230, 9225, 9220, 9215, 9210, 9215, 9200, 9195,
9190, 9185, 9180, 9175, 9170}
fectype

afec ALU FEC (default)
'down' state.
....................................................................................................................................................................................................................................
4-194
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




The following ODU3 attributes are provisionable on the 43SCX4 / 43STX4(P) L1

interface:
Provisionable
Attribute
pldtype
on the encoded client signal.
Default: 20
ptmmresp

the following:
....................................................................................................................................................................................................................................
4-195
August 2011
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




43STA1P OT port state provisioning
The states of the C1-C12 and L1 ports are provisioned independently. The following port


cnfigure the properties of the ainstimer to use either the system value, or to enter
Set ains to enabled
....................................................................................................................................................................................................................................
4-196
August 2011
....................................................................................................................................................................................................................................
43STA1P client port provisioning

The following attributes are provisionable on the 43STA1P C1 interface when the signal
type is provisioned to OC-768 or STM-256:
Port Attribute
jo
Description
losprop

the following:

J0 format.

Note: When real Payload Type Mismatch and far-end OC-768/STM256 LOF are
detected simultaneously, the real Payload Type Mismatch defect will not be raised.
....................................................................................................................................................................................................................................
4-197
August 2011
....................................................................................................................................................................................................................................
The following attributes are provisionable on the 43STA1P C1 interface when the signal
type is provisioned to OTU3:
Port Attribute
losprop
Description
Note: OTU3 client port provisioning is intended for OTU3 regeneration configuration
between a pair of 43STA1P OTs. OTU3 port provisioning may not be used as NNI
port connected to third party OTN network due to lack of FEC field
termination/processing, ODU3P layer monitoring (ODU3 defects or path BIP-8
monitoring at ODUkP/T layer isnt supported) or GCC[n] channel processing. OTUk
monitoring functions, including section BIP-8 is supported.
Note: For 43STA1P pack, the regeneration mode or transparent mode refers only to
the line transmit direction.
43STA1P line port provisioning
The line interface on the 43STA1P OT supports provisionable parameters at the OTU3
....................................................................................................................................................................................................................................
4-198
August 2011
....................................................................................................................................................................................................................................
The following OTU3 attributes are provisionable on the 43STA1P L1 interface:

Provisionable
Attribute
channel
Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565, 9560,
9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515, 9510, 9505,
9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465, 9460, 9455, 9450,
9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410, 9405, 9400, 9395,
9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355, 9350, 9345, 9340,
9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300, 9295, 9290, 9285,
9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245, 9240, 9235, 9230,
9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190, 9185, 9180, 9175,
9170}
Not set: None
fectype

ufec ultra FEC (default)
'down' state.
postfecber
prefecber
tti




....................................................................................................................................................................................................................................
4-199
August 2011
....................................................................................................................................................................................................................................
The following ODU3 attributes are provisionable on the 43STA1P L1 interface:

Provisionable
Attribute
mappingmode
ODUkp to CBRx mapping mode. This attribute specifies the mappng
mode that wil be used when the client port signal is provisioned to
OC-768 or STM-256.
Set to bitsync bit synchronous CBR mapping
Set to async asynchronous CBR mapping

ptmmresp
tti

the following:




MVAC OT port state provisioning
The states of the G{1-8} ports are provisioned independently. The following port states
are supported:

....................................................................................................................................................................................................................................
4-200
August 2011
....................................................................................................................................................................................................................................
Set ains to enabled
MVAC VA port provisioning
The G port on the MVAC OT supports the OCH attributes for the eVOA ports (G{1-8})
on the MVAC card as defined in the following table.
The following OCH attributes are provisionable on the MVAC G interface:

Provisionable
Attribute
moduletype
following:
fVOA fast VOA
sVOA slow VOA

....................................................................................................................................................................................................................................
4-201
August 2011
....................................................................................................................................................................................................................................

Before you begin
The port types that can be created and deleted are:
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B OSC port

ALPFGT and AM2125A AM2125B, AM2318A, OSCSFP port
OSCT card OSCSFP port
All OT Client ports
4DPA4: L{1,2}, only when Card Mode = FlexMux
4DPA4 : VA{1,2}
11DPE12(E) : L{1,2}, VA{1,2}
11DPM12 : L{1,2}, VA{1,2}
11QPA4: L{1-4}, VA{1-4}

CWR8 and CWR8-88 CLS {1-8}
11STAR1 line port (L1)
Note: The line port is automatically created and deleted with the 11STAR1 card.
The following procedure describes how to view or modify the 11STAR1 line port
settings.
...................................................................................................................................................................................................
Expand the 11STAR1 OT in the equipment tree to show ports. Select L1 line port.
Result: OTU2 attributes are displayed under the OTU2 Details tab. For ODU2
attributes, select the ODU2 Details tab.
...................................................................................................................................................................................................
To modify line port settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
11STAR1 client port (C1)
The following procedure describes how to create, view, or modify an 11STAR1 client
port.
...................................................................................................................................................................................................
Expand the 11STAR1 OT in the equipment tree to show ports. Select C1 client port.
....................................................................................................................................................................................................................................
4-202
August 2011
....................................................................................................................................................................................................................................
Result: For an unprovisioned client port, the Unprovisioned Client Port screen is
displayed.
Note: For a client port that is already provisioned, the Client Details screen is
displayed and attributes can be viewed or modified.
...................................................................................................................................................................................................
To create the client port, specify the primary state and signal rate of the port and click
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11STMM10 line port (L1)
Note: The line port is automatically created and deleted with the 11STMM10 card.
The following procedure describes how to view or modify the 11STMM10 line port
settings.
...................................................................................................................................................................................................
Expand the 11STMM10 OT in the equipment tree to show ports. Select L1 line port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
11STMM10 client port (C1-C10)
The following procedure describes how to create, view, or modify an 11STMM10 client
port.
...................................................................................................................................................................................................
Expand the 11STMM10 OT in the equipment tree to show ports. Select the client port.
displayed.
....................................................................................................................................................................................................................................
4-203
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11STGE12 line port (L1)
Note: The line port is automatically created and deleted with the 11STGE12 card.
The following procedure describes how to view or modify the 11STGE12 line port
settings.
...................................................................................................................................................................................................
Expand the 11STGE12 OT in the equipment tree to show ports. Select L1 line port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
11STGE12 client port (C1-C12)
Note: Only ports 1-10 are provisionable. Ports 11 and 12 are not supported.
The following procedure describes how to create, view, or modify an 11STGE12 client
port.
...................................................................................................................................................................................................
Expand the 11STGE12 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-204
August 2011
....................................................................................................................................................................................................................................
11DPE12(E) line port (L1, L2)
The following procedure describes how to create, view, or modify the 11DPE12(E) line
port settings.
...................................................................................................................................................................................................
Expand the 11DPE12(E) OT in the equipment tree to show ports. Select L1 or L2 line
port.
Result: For an unprovisioned line port, the Unprovisioned Line Port screen is
displayed.
Note: For a line port that is already provisioned, the Line Details screen is displayed
and attributes can be viewed or modified.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
For OTU2 attributes, select the OTU2 Details tab. For ODU2 attributes, select the ODU2
Details tab.
...................................................................................................................................................................................................
To modify OTU2 or ODU2 line port settings, enter parameters and click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11DPE12(E) VA port (VA1, VA2)
The following procedure describes how to create, view, or modify the 11DPE12(E) VA
port settings.
...................................................................................................................................................................................................
Expand the 11DPE12(E) OT in the equipment tree to show ports. Select VA1 or VA2 port.
Result: For an unprovisioned VA port, the Unprovisioned VA Port screen is displayed.
Note: For a VA port that is already provisioned, the VA Details screen is displayed and
attributes can be viewed or modified.
...................................................................................................................................................................................................
To modify VA port settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-205
August 2011
....................................................................................................................................................................................................................................
11DPE12(E) client port (C1-C12)
The following procedure describes how to create, view, or modify an 11DPE12(E) client
port.
...................................................................................................................................................................................................
Expand the 11DPE12(E) OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11QPA4 line port (L1-L4)
The following procedure describes how to create, view, or modify the 11QPA4 line port
settings.
...................................................................................................................................................................................................
Expand the 11QPA4 OT in the equipment tree to show ports. Select L1 or L2 line port.
displayed.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Details tab.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-206
August 2011
....................................................................................................................................................................................................................................
11QPA4 VA port (VA1-VA4)
The following procedure describes how to create, view, or modify the 11QPA4 VA port
settings.
...................................................................................................................................................................................................
Expand the 11QPA4 OT in the equipment tree to show ports. Select the VA port..
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
11QPA4 client port (C1-C4)
The following procedure describes how to create, view, or modify an 11QPA4 client port.
...................................................................................................................................................................................................
Expand the 11QPA4 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
112SCA1 / 112SA1L line port (L1)
Note: The line port is automatically created and deleted with the 112SCA1/112SA1L
card.
The following procedure describes how to view or modify the 112SCA1/112SA1L line
port settings.
....................................................................................................................................................................................................................................
4-207
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the 112SCA1/112SA1L OT in the equipment tree to show ports. Select L1 line
port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
112SCA1 / 112SA1L client port (C1)
The following procedure describes how to create, view, or modify an 112SCA1/112SA1L

client port.
...................................................................................................................................................................................................
Expand the 112SCA1/112SA1L OT in the equipment tree to show ports. Select C1 client
port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
112SCX10 / 112SX10L line port (L1)
Note: The line port is automatically created and deleted with the
112SCX10/112SX10L card.
The following procedure describes how to view or modify the 112SCX10/112SX10L line
port settings.
...................................................................................................................................................................................................
Expand the 1112SCX10/112SX10L OT in the equipment tree to show ports. Select L1

line port.
....................................................................................................................................................................................................................................
4-208
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
12SCX10 / 112SX10L client port (C1-C10)
The following procedure describes how to create, view, or modify an

1112SCX10/112SX10L client port.
...................................................................................................................................................................................................
Expand the 1112SCX10/112SX10L OT in the equipment tree to show ports. Select the
client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
4DPA4 line port (L1, L2)
The following procedure describes how to create, view, or modify the 4DPA4 line port
settings.
...................................................................................................................................................................................................
Expand the 4DPA4 OT in the equipment tree to show ports. Select L1 or L2 line port.
displayed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-209
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Details tab.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
4DPA4 VA port (VA1, VA2)
The following procedure describes how to create, view, or modify the 4DPA4 VA port
settings.
...................................................................................................................................................................................................
Expand the 4DPA4 OT in the equipment tree to show ports. Select VA1 or VA2 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
4DPA4 client port (C1-C4)
The following procedure describes how to create, view, or modify a 4DPA4 client port.
...................................................................................................................................................................................................
Expand the 4DPA4 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-210
August 2011
....................................................................................................................................................................................................................................
4DPA2 line port (L1, L2)
Note: The line port is automatically created when the client port is created.
The following procedure describes how to view or modify the 4DPA2 line port settings.
...................................................................................................................................................................................................
Expand the 4DPA2 OT in the equipment tree to show ports. Select L1 or L2 line port.
Result: Attributes are displayed under the Details tab.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
4DPA2 client port (C1-C2)
The following procedure describes how to create, view, or modify a 4DPA2 client port.
...................................................................................................................................................................................................
Expand the 4DPA2 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
43SCX4 / 43STX4(P) line port (L1)
Note: The line port is automatically created and deleted with the 43SCX4 /
43STX4(P) card.
The following procedure describes how to view or modify the 43SCX4 / 43STX4(P) line
port settings.
...................................................................................................................................................................................................
Expand the 43SCX4 / 43STX4(P) OT in the equipment tree to show ports. Select L1 line
port.
....................................................................................................................................................................................................................................
4-211
August 2011
....................................................................................................................................................................................................................................
Result: 43SCX4 / 43STX4(P) line port attributes are displayed under the Port Details
tab.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Details tab.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
43SCX4 / 43STX4(P) client port (C1-C4)
The following procedure describes how to create, view, or modify a 43SCX4 /

43STX4(P) client port.
...................................................................................................................................................................................................
Expand the 43SCX4 / 43STX4(P) OT in the equipment tree to show ports. Select the
client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
43STA1P line port (L1)
Note: The line port is automatically created and deleted with the 43STA1P card.
The following procedure describes how to view or modify the 43STA1P line port settings.
...................................................................................................................................................................................................
Expand the 43STA1P OT in the equipment tree to show ports. Select L1 line port.
....................................................................................................................................................................................................................................
4-212
August 2011
....................................................................................................................................................................................................................................
Result: 43STA1P line port attributes are displayed under the Port Details tab.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Details tab.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
43STA1P client port (C1)
The following procedure describes how to create, view, or modify a 43STA1P client port.
...................................................................................................................................................................................................
Expand the 43STA1P OT in the equipment tree to show ports. Select C1 client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B LINE port
Note: The LINE port is automatically created and deleted with the
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B card.
The following procedure describes how to view or modify the
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B LINE port settings.
...................................................................................................................................................................................................
Expand the A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B in the equipment

tree to show ports. Select LINE port.
....................................................................................................................................................................................................................................
4-213
August 2011
....................................................................................................................................................................................................................................
Result: Provisionable settings are displayed under the Port Details tab.
...................................................................................................................................................................................................
To modify port settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B SIG port
Note: The SIG port is automatically created and deleted with the
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B card.
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B SIG port settings.
...................................................................................................................................................................................................

tree to show ports. Select SIG port.
Result: Provisionable settings are displayed under the Port Details tab. To display
SIG port attributes, select the SIG Details tab.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B OSC port
The following procedure describes how to create, view, or modify the

A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B OSC port settings.
...................................................................................................................................................................................................

tree to show ports. Select OSC port.
Result: For an unprovisioned OSC port, the WebUI supports creation of the OSC port
and will set the value = OTS in the create request.

Note: For an OSC port that is already provisioned, the provisionable settings can be
viewed or modified.
...................................................................................................................................................................................................
To create the OSC port, enter pluggable module type and primary state and click Submit.
....................................................................................................................................................................................................................................
4-214
August 2011
....................................................................................................................................................................................................................................
Note: If the OSC is disabled or provisioned as a 100base-FX signal at the LD at the

end of a span, and the amplifier that launches into the return direction on that span is
capable of launching powers in excess of the class 1M safety limit, then the amplifier
for the return direction will shut down.
The amplifiers that are subject to this are:
A2325A - SIG OUT port

AM2325B - SIG OUT port
AM2125A - LINE OUT port
AM2125B - LINE OUT port
The port names shown in the above list are the ports against which the APR-Active OSC Disabled condition is raised.
If the OSC is disabled or provisioned as 100base-FX at one end of a span, and OC-3
at the other end, then APR-Active- Line can result instead of APR-Active-OSC
Disabled. This applies to spans that have EDFA's, but do not have Raman amplifiers.
Disabling OSC will lead to OSC LOS at the far end of the span. If the span has a
Raman amplifier, the detection of OSC LOS will cause an APR-Line condition. The
APR-Active-OSC Disabled condition will be suppressed in this case.
E...................................................................................................................................................................................................
N D O F S T E P S
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2125A/AM2325B DCM port
Note: A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2125A/AM2325B
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2125A/AM2325B DCM port settings.
...................................................................................................................................................................................................
Expand the A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2125A/AM2325B in the

equipment tree to show ports. Select DCM port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-215
August 2011
....................................................................................................................................................................................................................................
ALPFGT/OSCT LINE port
Note: The LINE port is automatically created and deleted with the ALPFGT/OSCT
card.
The following procedure describes how to view or modify the ALPFGT/OSCT LINE port
settings.
...................................................................................................................................................................................................
Expand the ALPFGT/OSCT in the equipment tree to show ports. Select LINE port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
ALPFGT/OSCT SIG port
Note: The SIG port is automatically created and deleted with the ALPFGT/OSCT
card.
The following procedure describes how to view or modify the ALPFGT/OSCT SIG port
settings.
...................................................................................................................................................................................................
Expand the ALPFGT/OSCT in the equipment tree to show ports. Select SIG port.
Result: Provisionable settings are displayed under the Port Details tab. To display
SIG port attributes, select the SIG Details tab.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
ALPFGT/AM2125A/AM2125B/AM2318A/OSCT OSC port

ALPFGT/AM2125A/AM2125B/AM2318A/OSCT OSC port settings.
...................................................................................................................................................................................................
Expand the ALPFGT/AM2125A/AM2125B/AM2318A/OSCT in the equipment tree to

show ports. Select OSC port.
....................................................................................................................................................................................................................................
4-216
August 2011
....................................................................................................................................................................................................................................
Result: For an unprovisioned OSC port, the WebUI supports creation of the OSC port
and will set the value = OTS in the create request.

Note: For an OSC port that is already provisioned, the provisionable settings can be
viewed or modified.
...................................................................................................................................................................................................
To create the OSC port, enter pluggable module type and primary state and click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
ALPFGT/AM2125A/AM2125B/AM2318A/OSCT OSCSFP port

ALPFGT/AM2125A/AM2125B/AM2318A/OSCT OSCSFP port settings.
...................................................................................................................................................................................................
Expand the ALPFGT/AM2125A/AM2125B/AM2318A/OSCT in the equipment tree to

show ports. Select OSCSFP port.
Result: For an unprovisioned OSCSFP port, the WebUI supports creation of the
OSCSFP port.
Note: For an OSCSFP port that is already provisioned, the provisionable settings can
be viewed or modified.
...................................................................................................................................................................................................
To create the OSCSFP port, enter pluggable module type and primary state and click
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
AM2125A/AM2125B/AM2318A LINEIN port
Note: The LINEIN port is automatically created and deleted with the
AM2125A/AM2125B/AM2318A card.
AM2125A/AM2125B/AM2318A LINEIN port settings.
...................................................................................................................................................................................................
Expand the AM2125A/AM2125B/AM2318A in the equipment tree to show ports. Select

LINEIN port.
....................................................................................................................................................................................................................................
4-217
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
AM2125A/AM2125B/AM2318A LINEOUT port
Note: The LINEOUT port is automatically created and deleted with the
AM2125A/AM2125B/AM2318A card.
Note: When the cover is removed from the output port of
AM2125A/AM2125B/AM2318A equipped with a protective cover switch, the optical
amplifier will shut down. The shut down occurs within 150 ms of the time that the
cover is removed. An APR-Active Port Switch condition is raised against the :
AM2125A/AM2125B/AM2318A - LINE OUT port.
AM2125A/AM2125B/AM2318A LINEOUT port settings.
...................................................................................................................................................................................................
Expand the AM2125A/AM2125B/AM2318A in the equipment tree to show ports. Select

LINEOUT port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
CWR8/CWR8-88 SIG port
Note: The SIG port is automatically created and deleted with the CWR8/CWR8-88
card.
The following procedure describes how to view or modify the CWR8/CWR8-88 SIG port
settings.
...................................................................................................................................................................................................
Expand the CWR8/CWR8-88 in the equipment tree to show ports. Select SIG port.
....................................................................................................................................................................................................................................
4-218
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
CWR8/CWR8-88 OMD port
Note: The OMD port is automatically created and deleted with the CWR8/CWR8-88
card.
The following procedure describes how to view or modify the CWR8/CWR8-88 OMD
port settings.
...................................................................................................................................................................................................
Expand the CWR8/CWR8-88 in the equipment tree to show ports. Select OMD port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
CWR8/CWR8-88 THRU port
Note: The THRU port is automatically created and deleted with the
CCWR8/CWR8-88 card.
The following procedure describes how to view or modify the CWR8/CWR8-88 THRU
port settings.
...................................................................................................................................................................................................
Expand the CWR8/CWR8-88 in the equipment tree to show ports. Select THRU port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-219
August 2011
....................................................................................................................................................................................................................................
CWR8/CWR8-88 CLS [1-8] ports
The following procedure describes how to create, view, or modify the CWR8/CWR8-88
CLS [1-8] port settings.
...................................................................................................................................................................................................
Expand the CWR8/CWR8-88 in the equipment tree to show ports. Select the CLS port..
Result: For an unprovisioned CLS port, the Unprovisioned CLS Port screen is
displayed.
Note: For a CLS port that is already provisioned, the CLS Details screen is displayed
...................................................................................................................................................................................................
To modify CLS port settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
DCM port
Note: The DCM port is automatically created and deleted with the DCM card.
The following procedure describes how to view or modify the DCM DCM port settings.
...................................................................................................................................................................................................
Expand the DCM in the equipment tree to show ports. Select DCM port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
EC CIT port
Note: The CIT port is automatically created and deleted with the EC card.
The following procedure describes how to view or modify the EC CIT port settings.
...................................................................................................................................................................................................
Expand the EC in the equipment tree to show ports. Select CIT port.
....................................................................................................................................................................................................................................
4-220
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
EC ES1 and ES2 ports
Note: The ES1 and ES2 ports are automatically created and deleted with the EC card.
The following procedure describes how to view or modify the EC ES1 and ES2 port
settings.
...................................................................................................................................................................................................
Expand the EC in the equipment tree to show ports. Select ES1 or ES2 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
FLC CIT port
Note: The CIT port is automatically created and deleted with the FLC card.
The following procedure describes how to view or modify the FLC CIT port settings.
...................................................................................................................................................................................................
Expand the FLC in the equipment tree to show ports. Select CIT port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
FLC OAMP port
Note: The OAMP port is automatically created and deleted with the FLC card.
The following procedure describes how to view or modify the FLC OAMP port settings.
....................................................................................................................................................................................................................................
4-221
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the FLC in the equipment tree to show ports. Select OAMP port.
Result: Port Interface settings are displayed under the Port Details tab.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
To view or modify OSPF parameters for the OAMP port select the OSPF Details tab.
E...................................................................................................................................................................................................
N D O F S T E P S
MESH4 SIGIN and SIGOUT [1-4] ports
Note: The SIGIN and SIGOUT [1-4] ports are automatically created and deleted with
the MESH4 card.
The following procedure describes how to view or modify the MESH4 SIGIN and
SIGOUT [1-4] port settings.
...................................................................................................................................................................................................
Expand the MESH4 in the equipment tree to show ports. Select SIGIN or SIGOUT [1-4]
port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MT0C ES1 and ES2 ports
Note: The ES1 and ES2 ports are automatically created and deleted with the MT0C
card.
The following procedure describes how to view or modify the MT0C ES1 and ES2 port
settings.
...................................................................................................................................................................................................
Expand the MT0C in the equipment tree to show ports. Select ES1 or ES2 port.
....................................................................................................................................................................................................................................
4-222
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MT0C VOIP port
Note: The VOIP port is automatically created and deleted with the MT0C card.
The following procedure describes how to view or modify the MT0C VOIP port settings.
...................................................................................................................................................................................................
Expand the MT0C in the equipment tree to show ports. Select VOIP port.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
To view or modify OSPF parameters for the VOIP port select the OSPF Details tab.
E...................................................................................................................................................................................................
N D O F S T E P S
OPSA A and B ports
Note: The A and B ports are automatically created and deleted with the OPSA card.
The following procedure describes how to view or modify the OPSA A and B port
settings.
...................................................................................................................................................................................................
Expand the OPSA in the equipment tree to show ports. Select A or B port.
Note: The settings are view-only for users with Observer and Provisioner privileges.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-223
August 2011
....................................................................................................................................................................................................................................
Note: Switching Threshold and Switching Threshold Tolerance can only be modified
if Switching Threshold Calculation Mode = Manual and the user has Admin or
Service level privileges. These attributes are viewable by all user types.
E...................................................................................................................................................................................................
N D O F S T E P S
OPSA SIG port
Note: The SIG port is automatically created and deleted with the OPSA card.
The following procedure describes how to view or modify the OPSA SIG port settings.
...................................................................................................................................................................................................
Expand the OPSA in the equipment tree to show ports. Select SIG port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
RA2P LINEIN port
Note: The LINEIN port is automatically created and deleted with the RA2P card.
The following procedure describes how to view or modify the RA2P LINEIN port
settings.
...................................................................................................................................................................................................
Expand the RA2P in the equipment tree to show ports. Select LINEIN port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
RA2P LINEOUT port
Note: The LINEOUT port is automatically created and deleted with the RA2P card.
The following procedure describes how to view or modify the RA2P LINEOUT port
settings.
....................................................................................................................................................................................................................................
4-224
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the RA2P in the equipment tree to show ports. Select LINEOUT port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
SFC/SFD OMD port, EXP port, and Channel ports
Note: The OMD port, EXP port, and Channel ports are automatically created and
deleted with the SFC/SFD card. The EXP port is not applicable to the SFD40,
SFD40B, SFD44, SFD44B, and SFC8.
The following procedure describes how to view or modify the SFC/SFD OMD port, EXP
port, and Channel ports settings.
...................................................................................................................................................................................................
Expand the SFC/SFD in the equipment tree to show ports. Select OMD port, EXP port, or
Channel ports.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
ITLB SIG, E and O ports
Note: The SIG, E and O ports are automatically created and deleted with the
ITLB/ITLU card.
The following procedure describes how to view or modify the ITLB SIG, E and O port
settings.
...................................................................................................................................................................................................
Expand the ITLB in the equipment tree to show ports. Select SIG,E or O port.
....................................................................................................................................................................................................................................
4-225
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
ITLU SIGIN, EOUT and OOUT ports
Note: The SIGIN, EOUT and OOUT ports are automatically created and deleted with
the ITLB/ITLU card.
The following procedure describes how to view or modify the ITLU SIGIN, EOUT and
OOUTport settings.
...................................................................................................................................................................................................
Expand the ITLU in the equipment tree to show ports. Select SIGIN,EOUT or OOUT port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
SVAC L1 port
Note: The L1 port is automatically created and deleted with the SVAC card.
The following procedure describes how to view or modify the SVAC L1 port settings.
...................................................................................................................................................................................................
Expand the SVAC in the equipment tree to show ports. Select L1 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
SVAC C1 port
Note: The C1 port is automatically created and deleted with the SVAC card.
The following procedure describes how to view or modify the SVAC C1 port settings.
....................................................................................................................................................................................................................................
4-226
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the SVAC in the equipment tree to show ports. Select C1 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MVAC G [1-8] ports
Note: The G ports are automatically created and deleted with the MVAC card.
The following procedure describes how to view or modify the MVAC G [1-8] port
settings.
...................................................................................................................................................................................................
Expand the MVAC in the equipment tree to show ports. Select G [1-8] port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
USRPNL OAMP and VOIP ports
Note: The OAMP and VOIP ports are automatically created and deleted with the
USRPNL card.
The following procedure describes how to view or modify the USRPNL OAMP and
VOIP port settings.
...................................................................................................................................................................................................
Expand the USRPNL in the equipment tree to show ports. Select OAMP or VOIP port.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-227
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To view or modify OSPF parameters for the OAMP and VOIP ports, select the OSPF
Details tab.
E...................................................................................................................................................................................................
N D O F S T E P S
USRPNL E1 and E2 ports
Note: This procedure describes scenarios/configurations and procedures for setting up

the 1830 PSS DCN to manage external Raman/EDFA boxes connected to the 1830
User Panel E1/E2 ports.
The two external LAN ports, E1 and E2, connect to externally managed devices, like
RAMAN power booster amplifiers. To manage the third party Raman amplifiers, the
preferred way is to hook up the ethernet port of these to the E1/E2 ports of the
adjacent NE.
The following configuration scenarios are considered for the procedure:
1. Connecting Raman/EDFA to E1 and/or E2 of GNE/RNE.
2. Connecting Raman/EDFA to E1 and/or E2 of GNE/RNE with multiple GNEs in
the network.
3. Connecting Raman/EDFA to E1 and/or E2 via L2 Switch.
The following steps describe the DCN procedure for connecting Raman/EDFA boxes to
E1/E2 port:
...................................................................................................................................................................................................
In the WebUI expand the equipment tree to select System > PSS-32 Shelf > USRPNL > E1
or E2
Result: In the Port Details tab, the Port Interface Settings screen is displayed.
...................................................................................................................................................................................................
Assign an IP address and subnet mask to the E1/E2 port. Each E1/E2 port should be on a
unique subnet within the DCN. For example: Our GNE OAMP IP address was
192.168.5.57/20 so we configured the E1 IP to be 182.168.11.1/24 and the E2 to be
182.168.12.1/24. Ensure that the configured subnet does not overlap with any other
subnet in the DCN.
...................................................................................................................................................................................................
Click on the OSPF details tab and provision the E1/E2 port routestate to redistribute.
...................................................................................................................................................................................................
Click on the Port Details tab and provision the E1/E2 port admin state to up..
....................................................................................................................................................................................................................................
4-228
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
On the Raman/EDFA box, set the IP address in the same subnet as the E1/E2 port IP
address: for example, for the Raman connected to E1 set the Raman IP address and subnet
mask to be 182.168.11.170/24. Set the Raman/EDFA box default gateway IP address as
the IP address of the E1 port (in our case 182.168.11.1).
...................................................................................................................................................................................................
Connect the E1/E2 port of the PSS-32 to the Raman/EDFA Ethernet port. If more than
two Raman/EDFA boxes are necessary then a L2 switch may be placed between the
E1/E2 port and the Raman/EDFA boxes.
...................................................................................................................................................................................................
If using static routes to connect to the 1830 network from the customer DCN, than add
static routes for the E1/E2 subnets on all necessary customer routers. On every 1830 GNE
add a default route using the subtending router interface IP address and set the redistribute
option in the default route. If the OSPF routing protocol is used on the customer DCN
instead of static routes, then enable OSPF on all GNE OAMP ports (using cli set OAMP
port routestate to enable.
...................................................................................................................................................................................................
On all PhM servers or client PCs, it is necessary to modify the Ethernet NIC MTU size
from the default 1500 to 1491.
Note: This procedure needs to be followed for each Raman/EDFA box that is
connected to an E1/E2 port.
E...................................................................................................................................................................................................
N D O F S T E P S
WR8-88A SIG port
Note: The SIG port is automatically created and deleted with the WR8-88A card.
The following procedure describes how to view or modify the WR8-88A SIG port
settings.
...................................................................................................................................................................................................
Expand the WR8-88A in the equipment tree to show ports. Select SIG port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-229
August 2011
....................................................................................................................................................................................................................................
WR8-88A THRU port
Note: The THRU port is automatically created and deleted with the WR8-88A card.
The following procedure describes how to view or modify the WR8-88A THRU port
settings.
...................................................................................................................................................................................................
Expand the WR8-88A in the equipment tree to show ports. Select THRU port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR8-88A ADDIN [1-8] ports
Note: The ADDIN [1-8] port is automatically created and deleted with the WR8-88A
card.
The following procedure describes how to view or modify the WR8-88A ADDIN [1-8]
port settings.
...................................................................................................................................................................................................
Expand the WR8-88A in the equipment tree to show ports. Select ADDIN [1-8] port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR8-88A DROPOUT port
Note: The DROPOUT port is automatically created and deleted with the WR8-88A
card.
The following procedure describes how to view or modify the WR8-88A DROPOUT port
settings.
...................................................................................................................................................................................................
Expand the WR8-88A in the equipment tree to show ports. Select DROPOUT port.
....................................................................................................................................................................................................................................
4-230
August 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR8-88A MESHOUT [1-3] ports
Note: The MESHOUT [1-3] port is automatically created and deleted with the
WR8-88A card.
The following procedure describes how to view or modify the WR8-88A MESHOUT
[1-3] port settings.
...................................................................................................................................................................................................
Expand the WR8-88A in the equipment tree to show ports. Select MESHOUT [1-3] port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WTOCM IN port (1-4)
Note: The WTOCM IN ports are automatically created when the WTOCM pack is
provisioned.
The following procedure describes how to view or modify the WTOCM IN port settings.
An association between the WOTCM IN port and the line side port that it monitors must
be provisioned.
...................................................................................................................................................................................................
Expand the WTOCM in the equipment tree to show ports. Select IN port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-231
August 2011
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-232
August 2011
Alarm management
5
Overview
Purpose
This chapter describes the alarm management functionality supported by Alcatel-Lucent

1830 PSS.
Contents
Description
5-1
Alarm management procedures
5-6
Description
Alarm operation
An alarm is a notification of a failure and also an external visible indication of a failure

by enabling the contact closure on the alarm grid. An autonomous message is generated to
report the alarm and the FAULT LED on the circuit pack or user panel may be turned on
or made to blink depending on the severity and type of alarm.
The main focus in alarm management is to present the user with the current alarms of
Alcatel-Lucent 1830 PSS in summaries and different views, so that the user gets a quick
overview of the state of the NE. These views also support the user in analyzing fault
conditions and quickly finding a solution for the problem. The following conditions apply
to alarm operation:
Trouble notifications are provided for and distinguish between equipment failures and
incoming signal failures.
Local notifications are consistent with the remote notifications for the same trouble.
Any single failure results in only one alarmed output message.
...................................................................................................................................................................................................................................
5-1
August 2011
Alarm management
Description
....................................................................................................................................................................................................................................
The system supports two modes for alarm reporting: SONET and SDH. The mode of
alarm reporting is defined by the system level MODE parameter.
The system supports autonomous reporting and logging of alarms and conditions for
equipment and facilities. All currently existing alarmed, not alarmed, and not reported
events are retrievable via all user interfaces.
When an entity is deleted, all of its associated alarms and conditions are cleared.
When an entity is not provisioned, no alarms or conditions are set against that entity.
If a condition error is associated with a non-provisioned entity, then it is set against
the SLOT entity with the same instance of the non-provisioned entity.
When an entity is logically removed (placed in OOS-[AU]MA state), clear messages
are sent for all the outstanding conditions on that entity that were autonomously
reported, except for the off-normal conditions. However, outstanding conditions on
that entity will still be retrievable.
Alarm severity management
You can change the default alarm severity for an alarm condition on a specific entity (for
example a port) or for all entities of the same type. While alarm severity is modifiable, the
service-affectedness of the condition cannot be modified.
The NE allows default alarm severities to be modified via all supported user interfaces,
and all user interfaces provide a means of reverting to the default alarm severities. All
user interfaces provide a means of listing the severities in effect.
The NE supports the following condition severities (notification codes) which are
reported to maintenance and operations personnel responsible for the equipment:
Critical (CR)
Major (MJ)
Minor (MN)
Warning (WR)
Not-Alarmed (NA)
Alarm reporting
The system supports autonomous reporting and logging of all alarms and conditions and
management and retrieval of alarm logs is available. Each trouble requiring craftsperson
action results in an alarm condition and is reported by three concurrent methods:
Automatic output message

Visual indication at NE
Audible and visual indications under the control of the NE
A trouble not requiring craftsperson action is reported via an automatic output message.
Incoming signal failures generate alarmed trouble notifications. Transient events (e.g.,
threshold crossing alerts) generate not-alarmed notifications as the default.
....................................................................................................................................................................................................................................
5-2
August 2011
Alarm management
Description
....................................................................................................................................................................................................................................
Each automatic output message includes, as a minimum, the following information:
The time the event occurred.
The trouble type (e.g. loss of signal).

Identification of the failed NE or the NE in which the failed unit resides.
Identification of the NE's affected replaceable element.
Designation as service-affecting or non-service-affecting.

Designation as alarmed or non-alarmed.
For alarmed events, the severity of the trouble (i.e. critical, major or minor).
After an autonomously reported standing condition has been cleared, an automatic output
message is generated by the NE indicating that the alarmed condition has been cleared.
The automatic output message has the same priority as that reported in the original alarm.
The colors red, amber, yellow, cyan, and green indicating the severity of the trouble are
used on an NE's physical control/status display panel to visually represent various alarm
levels and status conditions at the NE's equipment location. The alarm LEDs for an entity
on the NE are lit according to the alarm level(s) being asserted by the NE. The level
priorities are:
Critical
Major
Minor
Warning
None
Alarm hierarchy
For non-independent failures, only the highest trouble in the alarm hierarchy will be
reported. When a higher level alarm clears and lower level problems persist that were not
alarmed, the lower level problem will be alarmed. The timestamp of the alarm will be the
detection time of the problem not that of the higher level alarm clearing.
When a lower level alarm is cleared due to a logical removal of the entity, then it can be
retrieved by the related condition retrieval command. Its timestamp will be the time of the
command that logically removed the entity. If re-raised (logically inserted again) the
timestamp will be the time of original problem detection, not the time the logical insertion
occurred.
....................................................................................................................................................................................................................................
5-3
August 2011
Alarm management
Description
....................................................................................................................................................................................................................................
Equipment/ facility alarms
Equipment and facility failures are classified as either service-affecting (SA) or non
service-affecting (NSA), depending on whether they affect the service that the equipment
transports. Detectable faults on a module that affect the operation of that module results in
an alarm generated against the failed module. An error occurring between two pieces of
equipment results in an alarm on the receiving/detecting equipment.
Audible alarms
The NE provides audible alarm dry contacts and alarm cut-off capability. The alarm
cut-off function (in the alarm area of the WebUI toolbar) removes the signal from the dry
contacts, but does not affect the internal state of the NE, nor affect any of the visual
indicators.
Environmental (housekeeping) alarms
The NE provides eight input sensors and four output controls for status and management
of customer external equipment and environment. Upon successful provisioning of the
main shelf on an NE, all External Control Output Points (CPO) and all External Control
Input Points (CPI) are automatically created. Housekeeping (HKP) alarm provisioning is
persistent and stored in the database. If customer controls are active prior to a system
reset, they remain active through the reset and maintain their prior state following the
reset. On restoration of a backup database, customer controls are restored to their state at
the time of backup .
It is possible to configure user labels for each alarm input and control output for message
purposes on all user interfaces (via the local terminal and element manager). The labels
consist of ASCII text fields up to 30 characters. It is possible to modify each label at any
time.
Input sensors
The NE can receive and process eight separate customer-defined inputs for fault
conditions arising externally to the NE. These fault conditions are processed and reported
the same as for internally detected fault conditions. It is possible to disable the reporting
from any input if not used. The inputs are normally used for site specific alarms such as
open door, high temperature, high water level, etc. The system issues a database change
event when the HKP provisioning is updated.
Output controls
The NE drives four separate output station controls for customer defined site specific
facilities external to the NE, such as air conditioning, generators, etc. Operating an
external control means that a relay is activated to control some external device. Releasing
an external control means deactivating the relay. The polarity of an external output
control determines the relationship between the control state value and the physical signal
....................................................................................................................................................................................................................................
5-4
August 2011
Alarm management
Description
....................................................................................................................................................................................................................................
The states of the control relays are persistent through a restart or protection switch. That
is, at the completion of the restart or protection switch, the state of the outputs remain the
same as before the restart or protection switch. During the time that the NE restarts or
switch activity is in process, if the control relay states cannot be maintained, then they
default to the open contact state.
....................................................................................................................................................................................................................................
5-5
August 2011
Alarm management
....................................................................................................................................................................................................................................

Display active alarm list
...................................................................................................................................................................................................
In the WebUI, select Reports > Alarm List > {Total, Critical, Major, Minor}
Note: Alarms can also be selected via the alarms display area on the WebUI toolbar.
Result: The selected alarms are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
View condition list
The WebUI displays a list of all active conditions on the NE. The WebUI will allow the
user to filter the list based on Severity.
...................................................................................................................................................................................................
In the WebUI, select Reports > Condition List.

Result: The Condition List is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Display active alarms or alarm level on a shelf or slot/card
Note: The WebUI will display a list of all active alarms on the selected shelf or
slot/card and all entities hierarchically below.
...................................................................................................................................................................................................
From the WebUI equipment tree, select the shelf or slot/card. Click the Fault function.
Result: The Alarm List/Alarm Level is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
View alarms history log
The WebUI supports the following alarms history logs: All, Critical, Major, Minor, Not
Reported, Not Alarmed, Warning.
...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > Alarms > {All Alarms, Critical Alarms, Major
Alarms, Minor Alarms, Not Reported, Not Alarmed, Warnings}.
....................................................................................................................................................................................................................................
5-6
August 2011
Alarm management
....................................................................................................................................................................................................................................
Result: The respective Alarms Log is displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
View events history log
The WebUI supports the following Event history logs: General, State Changes, User
Actions.
...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > Events > {General, State Changes, User
Actions}.
Result: The respective Events Log is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Modify alarm configuration
Note: A user may modify the shelf, card, and port level alarm severity for a selected
condition type. A user may revert to the default severity for all condition types of a
specified category.
...................................................................................................................................................................................................
In the WebUI, select System from the equipment tree and click the Fault function.
Result: Alarmable Conditions screen is displayed.
...................................................................................................................................................................................................
Select a Category and click Retrieve.

Result: The Condition Types are displayed.
...................................................................................................................................................................................................
Select Severity Level and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
Provision environmental (housekeeping) alarms
For 1830 PSS-32 and 1830 PSS-16, the WebUI supports provisioning of environmental
alarms and external controls on the USRPNL card. Once provisioned, the user can operate
or release the control(s). Attributes can be set for each port.
....................................................................................................................................................................................................................................
5-7
August 2011
Alarm management
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the WebUI expand the equipment tree to select System > PSS-32 Shelf > USRPNL and
click on the Alarm Level tab.
Result: The Alarmable Conditions screen is displayed.
...................................................................................................................................................................................................
Enter parameters and click Submit.

Note: For 1830 PSS-36, the 1830 PSS-36 PF includes:
HOUSEKEEPING input ports (16)

HOUSEKEEPING output ports (8)
The HOUSEKEEPING ports are independent on each PF, so there are total of 32
input ports and 16 output ports available on each shelf. However, the use of
HOUSEKEEPING ports is currently restricted to 8 inputs and 4 outputs, located on
the first PF (slot 44) of the 1830 PSS-36 main shelf only.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-8
August 2011
6
Overview
Purpose
This chapter describes setting the performance monitoring functionality of the

Alcatel-Lucent 1830 PSS.
Contents
Description
6-1
Performance monitoring procedures
6-8
Description
Overview
Performance monitoring (PM) refers to the in-service, non-intrusive monitoring of

transmission quality and equipment health. The Alcatel-Lucent 1830 PSS tracks the signal
quality and equipment health through continuous collection and analysis of performance
data. The user can retrieve current and past values of the system to get an overview of the
health of the system. The performance monitoring capability exists for optical lines,
channels, and equipment monitoring. Users have the ability to provision threshold
parameters to levels that might be indicative of impending performance degradation.
Responding to a performance degradation before there is a failure and system alarms are
raised is termed proactive maintenance. Responding to system alarms is termed reactive
maintenance. Crossing of a performance parameter threshold indicates a potential
network quality or performance degradation while the services being transported have not
been impacted. If a condition continues to deteriorate, then alarms are raised and
immediate attention may be required to resolve or repair the problem.
...................................................................................................................................................................................................................................
6-1
August 2011
Description
....................................................................................................................................................................................................................................
Performance monitoring statistics are gathered for all service cards and for all interface
ports that perform OEO conversions or protection switching. The statistics are grouped by
functional category. Each category has several monitored parameters for which you can
configure threshold crossing alerts (TCAs). A threshold is the mechanism for generating a
defined notification resulting from changes in PM parameter values. The Alcatel-Lucent
1830 PSS allows provisioning of performance parameter thresholds, which can be set by
the user to show degraded performance. You can configure how much data is gathered,
how it is stored, and how and when you are notified if certain thresholds levels are
crossed.
Note: The user can inhibit individual monitor type TCA messages by setting the
threshold value in a TCA profile assigned to a facility to 0 if the parameter is digital or
to -99.99dB if the parameter is analog.
How performance monitoring works
Performance monitoring (PM) statistics provide counts or measurements of significant

information that can be used to gauge the performance of the network element and the
services running on it. The statistics gathered are used primarily for the following:
to provide instant notification, via alarms, that acceptable thresholds for data such as
CPU utilization or dropped packets have been crossed.
to provide a historical view of the performance of the network element over a given
period of time.
Performance monitoring functions are performed on physical and logical points within
the Alcatel-Lucent 1830 PSS NE which represent the boundary with other NEs or
external system. This allows user to define and monitor Quality Of Service at individual
points in which local NE interacts with other network entities. Figure 6-1, Performance
monitoring points in an 1830 PSS NE (p. 6-3) gives an illustration of PM points in an
Alcatel-Lucent 1830 PSS NE.
....................................................................................................................................................................................................................................
6-2
August 2011
Description
....................................................................................................................................................................................................................................
Figure 6-1 Performance monitoring points in an 1830 PSS NE
The identified points in Figure 6-1, Performance monitoring points in an 1830 PSS NE
(p. 6-3) provide the following transport layer and PM monitoring types:
1. OTS layer -> monitored type(s): Total OPR
OCh channel within the OTS -> monitored types: (individual channel)
OPR
2. OTS layer -> monitored type(s): Total OPT
OCh channel within the OTS -> monitored types: (individual channel)
OPT
3. OPS layer -> monitored type(s): OPR & OPT
OTUk (Section Monitoring) layer -> monitored types: BBE (BIP-8), ES, SES, UAS,
FEC-EC & FEC-UBC
ODUk (Path Monitoring) layer -> monitored types: BBE (BIP-8), ES, SES & UAS
4. Client Optical -> monitored type(s): OPR & OPT
Client Digital -> refer to client specific monitored type specification in the next
section.
5. OSC Receive direction -> monitored type(s): OPR, CV, ES, SES, SEFS, Ethernet
Interface group
6. OSC Transmit direction -> monitored type(s): OPT
While digital monitoring types provide progressive accumulation of monitored
performance event counts, analog monitoring types provide watermark points (High and
Low watermarks) as well as average value of analog monitored parameter over an
accumulation period.
....................................................................................................................................................................................................................................
6-3
August 2011
Description
....................................................................................................................................................................................................................................
Bins and intervals
Data from a card or interface is continually gathered for the performance monitoring
group, or groups, that apply to the interface or card. For each group, the data is placed
into two bins that collect the data over a specified time interval. The time interval for the
interval bins is 15 minutes or 24 hours. 24-hour bins collect data from midnight to
midnight based on UTC, not local time. Performance data is also placed into a raw bin.
The statistics in the raw bin accumulate until the contents of the raw bin are cleared.
At the end of each interval, the PM data is moved to the subsequent bin at the end of the
interval period, such that the contents of bin 0 (the active bin) are moved to bin 1, bin 1 to
bin 2, and so on. The contents of the last bin are discarded. You can configure each data
collection point for cards to use up to 8 bins for one day (24-hour) data, and up to 33 bins
for 15-minute data.
Note: After a cold reboot of a card, it is necessary to perform an INIT-REG command
in order to have a clean PM collection period.
Thresholds and threshold crossing alerts (TCAs)
Threshold values are considered as crossed when the value in the Current Register is
equal to or exceeds the value in the corresponding Threshold Register. No threshold for
clearing is supported. TCAs are reported via messages upon recognition of the threshold
crossings. A TCA is not considered as a standing condition. No clearance is reported at
the end of any monitoring period.
TCA messages for digital parameters identify the monitored facility, monitored parameter
register, current threshold value, current register value, time and date of the occurrence.
TCA messages for analog parameters identify the monitored facility, monitored parameter
register, current threshold value, current register value, baselined value, time and date of
the occurrence. TCA message output contains absolute measure value for the current
register value and not the deviation from associated baselined value.
Performance parameter thresholds are set to show degraded performance. A threshold is
the mechanism for generating a defined notification resulting from changes in parameter
values. There are two types of thresholds:
counter-threshold: associated with digital parameters

gauge-threshold: associated with analog parameters
Unlike the value of a counter parameter that can only increase in value unless its value
is reset, the value for a gauge parameter can increase or decrease continuously over time.
Analog parameters have two user configurable thresholds (notifyHigh and notifyLow) as
a high threshold and low threshold associated with the parameter respectively.
....................................................................................................................................................................................................................................
6-4
August 2011
Description
....................................................................................................................................................................................................................................
These threshold values are checked against the appropriate tidemark low and tidemark
high monitors and TCA notification raised if tidemark high exceeds the defined
notifyHigh value for the parameter and time period, or if tidemark low drops below the
defined notifyLow value for the parameter and time period.
Figure 6-2 Analog parameter TCA
Note: Term exceed used with tidemark low/high monitored parameters indicates that
tidemark high value is greater than the corresponding threshold or that tidemark low
is below the corresponding threshold.
For OT physical layer OPR, OPT parameters TCA profiles contain values for positive and
negative deviation relative to established baselined analog value for that port. Baselining
of OPR/OPT values can be established automatically (at the point the input signal is
applied to the port initially or laser initially enabled) or manually by user command.
Baselining applies to OT and OSC ports but not OCh and OTS ports. OCh and OTS port
thresholds are established during the commissioning phase.
For each threshold on a Current register, only one TCA is sent during an accumulation
period, unless the Current register is reset. If the Current register is reset and subsequently
its value again reaches or exceeds the threshold value, another TCA is sent. When a
threshold is crossed, the NE does not reset the register, but continues counting to the end
of the accumulation period.
....................................................................................................................................................................................................................................
6-5
August 2011
Description
....................................................................................................................................................................................................................................
TCA profiles
As the PM data is collected, the attribute counters in the active bin (bin 0) get
incremented or updated each time an event, such as a SONET/SDH errored second,
occurs. If desired, you can configure and assign a profile to an interval to monitor the
value of each attribute in the active bin and raise a log event when a certain threshold
level is reached. When a specified threshold is crossed a log event is raised.
You can configure each PM group with up to eight profiles, all having different threshold
levels. The NE provides the ability to modify all TCA profiles. The threshold levels you
define in the profiles depend on two factors:
the interval length. For example, if you were gathering statistics for an interface over
15 minute and 24 hour intervals you would need to define two profiles, one that
defines the threshold values for the 15 minute interval and one that defines thresholds
for the 24 hour interval.
the service level of the traffic using the interface.
There are 9 instances of each profile type supported. The user can inhibit individual
monitor type TCA messages by setting the threshold value in a TCA profile assigned to a
facility to 0 if the parameter is digital or to -99.99dB if the parameter is analog. Profiles
with index 7 contain factory default data with 15-min defaults preloaded while profile
with index 8 contains 1-day defaults preloaded. Instances 1-6 are initialized with all 0
values and can be customized by the user.
Note:
1. There is no restriction in assigning profile numbers to PM intervals.
2. PM profile supports default 15 minute and default 1 day values
3. The maximum value allowed for 15 minute threshold vs 1 day are not the same.
The system supports the following TCA profile types:
OC_N (SONET port section monitoring)

STM_N (SDH port section monitoring)
DW (OTU and ODU layer PM parameters)

ETH (Ethernet group)
INF (Interface group)
PCS (PCS layer monitoring for Ethernet/FC ports)

CP (Equipment PM parameters, applicable to EC)
OPR (Optical Power Received on OT and OSC ports)
OPT (Optical Power Transmitted on OT and OSC ports)
Note: The WebUI allows the user to select one or more PM Groups (including All)
and one or more Bin types (15-Minute, 1-Day, or Raw Counts) in a single user
request.
....................................................................................................................................................................................................................................
6-6
August 2011
Description
....................................................................................................................................................................................................................................
Configuring performance monitoring
The major steps in high-level performance monitoring configuration are as follows:

1. Determine the interfaces and cards you need to configure to collect performance
monitoring data.
2. Configure the profiles to define the threshold levels at which log events are generated
for the PM groups you will be monitoring on the network element.
3. Configure each of the interfaces and cards on the network element for which you will
be collecting performance monitoring statistics. You need to define which PM
statistics are gathered, the interval period over which they are gathered, and the
profile used for each interval period.
Viewing performance monitoring data
Performance monitoring data is recorded in logs or in bins. The logs record all of the
threshold crossing events that occurred on the network element. The bins hold data
gathered on a specific card or interface over a specific interval. In addition to the interval
bins, there is a raw bin for each PM group that continues to gather data until cleared.
Note: When PM data is not available, PM attribute names are displayed with their
values as "blank".
....................................................................................................................................................................................................................................
6-7
August 2011
....................................................................................................................................................................................................................................

Before you begin
Table 6-1, Cards and Ports that Support PM Data (p. 6-8) specifies which cards and
ports support PM data.
Table 6-1

Card
Port
112SCA1
L1, C1
112SA1L
112SCX10
L1, C{1-10}
112SX10L
11DPE12
L{1,2}, VA{1,2}, C{1-12}
11DPE12E
11DPM12
L{1,2}, VA{1,2}, C{1-12}
11STAR1
L1 ,C1
11STGE12
L1, C(1-10)
11STMM10
L1, C(1-10)
11QPA4
L(1-4), VA(1-4), C(1-4)
43STA1P
L1, C1
43SCX4 / 43STX4/43STX4P
L1, C(1-4)
4DPA2
L(1,2), C(1,2)
4DPA4
L(1,2), C(1-4), VA(1,2)
(Card Mode = FlexMux)

4DPA4
L(1,2), C(1,3), VA(1,2)
(Card Mode = DualTran)

A2325A
OSC, LINE, LINE-{9170~9605}
ALPHG
AHPHG
AHPLG
AM2017B
AM2325B
AM2125A/AM2125B/AM2318A
OSCSFP, LINEIN, LINEIN-{9170~9605}, LINEOUT,

LINEOUT-{9170~9605}
ALPFGT
OSCSFP, LINE, LINE-{9170~9605}
....................................................................................................................................................................................................................................
6-8
August 2011
....................................................................................................................................................................................................................................
Table 6-1
(continued)
Card
Port
EC/FLC
No port, PM data collected for card.
OSCT
OSCSFP, LINE, LINE-{9170~9605}
MVAC
G{1-8}
RA2P
LINEIN
SVAC
L1, C1
Note: 11STMM10 hardware does not support GbE PM statistics in egress direction.
TX side PM data is not displayed for 4DPA2 client or line ports.
Ethernet counters are not supported on 112SCA1 add drop pack.
Display PM data for ECFLC card
Note: Card performance monitoring is supported for the EC/FLC card. Card-level PM
is not supported for other cards types.
...................................................................................................................................................................................................
In the WebUI, select the EC/FLC card and click the Performance function.
Result: The PM Data screen is displayed under the PM Report tab.
...................................................................................................................................................................................................
The WebUI allows a user to clear current 15-min, 1-day, and/or free running (i.e. raw
counter) bins on an EC/FLC card. This request will clear the bins for all monitored types
on the card. To clear bins, click on the Bins tab, check the appropriate box(es), and click
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
Set bins for EC/FLC card
Note: Up to fifty historical bins for 1-day and 15-min are supported.
...................................................................................................................................................................................................
In the WebUI, select the EC/FLC card and click the Performance function.
Result: The PM Data screen is displayed.
...................................................................................................................................................................................................
Select the Settings tab.
....................................................................................................................................................................................................................................
6-9
August 2011
....................................................................................................................................................................................................................................
Result: The PM Configuration screen is displayed.

...................................................................................................................................................................................................
To change settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
Display all TCA profile assignments

...................................................................................................................................................................................................
In the WebUI, select System from the equipment tree and select Reports > TCA
Assignment.
Result: The TCA Profile Assignments are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Modify TCA profile

...................................................................................................................................................................................................
In the WebUI, select System from the equipment tree and click the Performance
function.
Result: The TCA Profile Data screen is displayed.
...................................................................................................................................................................................................
Select the Profile Type and click Retrieve.

Result: Profile Data is displayed.
...................................................................................................................................................................................................
Select the Profile ID and click Details.

Result: Profile attributes are displayed.
...................................................................................................................................................................................................
To modify, enter the desired values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
Display PM data for port

...................................................................................................................................................................................................
In the WebUI, select the port and click the Performance function.
....................................................................................................................................................................................................................................
6-10
August 2011
....................................................................................................................................................................................................................................
Result: The PM Data screen is displayed under the PM Report tab.

...................................................................................................................................................................................................
Select the PM group and click Retrieve.

Result: The PM report is displayed.
...................................................................................................................................................................................................
The WebUI will allow a user to clear current 15-min, 1-day, and/or free running (i.e. raw
counter) bins on a port. This request will clear the bins for all monitored types on the port.
To clear bins, click Clear Bins.
E...................................................................................................................................................................................................
N D O F S T E P S
Set bins for port
Note: The WebUI will support setting the number of 15-min. and/or 1-day
accumulation bins on a port. Up to thirty-three 15-min historical bins and up to eight
1-day historical bins are supported.
...................................................................................................................................................................................................
Result: The PM Data screen is displayed.
...................................................................................................................................................................................................
Select Settings tab. Select the Profile Type and click Retrieve.
Result: The Port Configuration is displayed.
...................................................................................................................................................................................................
To change settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
Set baseline values for port
Note: The WebUI will allow a user to view and set a baseline value for analog
parameters (OPR, OPT) on a port. The following port types support baselining:
112SA1L, 112SCA1: L1,C1

112SCX10, 112SX10L: L1,C{1-10}
11STMM10: L1, C(1-10)

11STAR1: L1, C1
11STGE12: L1, C(1-10)
....................................................................................................................................................................................................................................
6-11
August 2011
....................................................................................................................................................................................................................................
11DPE12, 11DPE12E: L{1,2}, VA{1,2}, C{1-12}

11DPM12: L{1,2}, VA{1,2}, C{1-12}
11QPA4: L(1-4), C(1-4), VA(1-4)
4DPA4: L(1,2), C(1-4), VA(1,2) for Card Mode = FlexMux

4DPA4: L(1,2), C(1,3), VA(1,2) for Card Mode = DualTran
4DPA2: L(1,2), C(1,2)
A2325A, AHPHG, AHPLG, ALPHG, AM2017B, AM2325B: OSC

ALPFGT, OSCT: OSCSFP
AM2125A/AM2125B/AM2318A: OSCSFP
43STA1P: L1, C1
43SCX4 / 43STX4, 43STX4P: L1, C(1-4)
MVAC: G{1-8}
SVAC: L1, C1
Note: For 100G A/D, Alcatel-Lucent 1830 PSS does not support the baselining of
analog parameters for Total Power Receive/Transmit for 100GbE client port.
...................................................................................................................................................................................................
Result: The PM Configuration screen is displayed.
...................................................................................................................................................................................................
Select Baseline tab.

Result: The Port Baseline screen is displayed.
...................................................................................................................................................................................................
To set baseline values, select Establish Baseline and enter Reason. Click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6-12
August 2011
Connections
7
Overview
Purpose
This chapter describes the connection functionality supported by the 1830 PSS.
Contents
Description
7-1
Connections procedures
7-6
Description
Physical topology
The WebUI displays a physical view of the NE topology. This view includes the shelves,
cards and ports applicable to fiber connection management, as well as the existing fiber
connections between ports on the NE.
The Physical Topology view allows the user to create a new fiber connection by selecting
2 ports on the displayed shelves and clicking Connect. Only those ports that are not
already part of a fiber connection are available for creating a new fiber connection. The
connection can be made between 2 ports on the same shelf or on different shelves.
A loopback connection can be created via the Physical Topology view by selecting an
A2325A/AHPHG/AHPLG/ALPHG/AM2017B/AM2325B DCM port, clicking
Loopback, and then clicking Connect.
The Physical Topology view allows the user to create an external connection by selecting
1 port on the shelf and clicking External. Only certain ports are valid external connection
points and these are the CWR8/CWR8-88 CLS port, LD Line port, OT Line port, SFC
OMD port, SFD OMD port, SFD channel ports, MVAC ports, ITLB SIG port, OPSA SIG
...................................................................................................................................................................................................................................
7-1
August 2011
Connections
Description
....................................................................................................................................................................................................................................
port, OT client ports, and SVAC client port. Enter the IP address and shelf/slot/port of the
external NE if configuring an LD line port as external and click Connect. If connecting a
different port type as external, enter identifying information for the destination port.
The Physical Topology view allows the user to delete an existing fiber connection by
selecting the line representing the fiber connection and clicking Disconnect. A fiber
connection cannot be deleted if there is a cross-connect associated with the fiber
connection.
A physical topology connection or assignment is denied by the system if making such a
connection or assignment would result in an invalid topology.
Bidirectional / unidirectional fiber connection
The Physical Topology view allows the user to create a new fiber connection by selecting
2 ports on the displayed shelves, selecting the directionality (bidirectional or
unidirectional) and clicking Connect. The WebUI distinguishes between unidirectional
and bidirectional fiber connections on the physical topology graphical display by
displaying the unidirectional fiber connections with an arrow at the end of the line to
indicate the direction.
A bidirectional fiber connection may be made between a port and an external interface.
For this connection, the user selects one NE port and selects External. The user may
optionally enter address information for the external port.
A unidirectional fiber connection may be made between a port and an external interface.
The unidirectional connection may start on a port on the NE (i.e. the NE port is the
from port) or may end on a port on the NE (i.e. the NE port is the to port). For this
connection, the WebUI allows the user to indicate whether the internal port is the start or
end port of the connection. The user may optionally enter address information for the
external port.
Note: For a bidirectional connection, only those ports that are not already part of a
fiber connection are available for creating a new fiber connection.
For a unidirectional connection, only those ports that are not already part of a
bidirectional fiber connection, or part of a unidirectional fiber connection in the same
direction, are available for creating a new fiber connection.
For additional information on bidirectional/unidirectional fiber, see the Alcatel-Lucent
1830 Photonic Service Switch 36/32/16 (PSS-36/32/16) Release 3.6.0 and 3.6.1 Product
Information and Planning Guide. .
Bidirectional single-fiber transmission
Some applications require bi-directional transmission over a single fiber. A PSS-32

FOADM CWDM node can be configured to support such an application using CWDM
filters. Each bidirectional transmission requires different CWDM wavelengths in each
direction.
....................................................................................................................................................................................................................................
7-2
August 2011
Connections
Description
....................................................................................................................................................................................................................................
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(E)
For additional details regarding bidirectional single-fiber transmission, see the

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16 (PSS-36/32/16) Release 3.6.0 and
3.6.1 Product Information and Planning Guide.
EVPL connections
Ethernet Virtual Private Line (EVPL) connections are full-rate or sub-rate cross-connects
within an 11DPE12(E) card. The WebUI supports provisioning of EVPL connections. All
EVPL connections are modeled as unidirectional in the NE. When creating a new
connection, the WebUI allows the user to request that a 2nd ZA connection be created. If
so requested, then the WebUI automatically creates 2 unidirectional connections stored
separately in the NE. The WebUI allows EVPL connections to be deleted if the GbE client
port has AdminState = Down.
Optical cross-connect
An optical cross-connect defines the optical path a service channel takes through the NE.
Cross-connects use the provisioned NE fiber topology to traverse the path through the NE
between the two ports that define the endpoints of the cross-connect. Within an NE, a
valid cross-connect is identified by an optical channel and the two ports at the endpoints
of the cross-connect. To add/drop a service, the cross-connect terminates at an OT line
port and the NE's network ingress/egress port (typically the Line port of the LD). For an
optical pass through service, the cross-connect terminates at network ports (typically LD
Line In/Out ports) at the entry and exit point of the NE. Within the network consisting of
the connected NEs, the service is identified by an Optical Channel (OCH) trail which
consists of several cross-connects hosted by each NE.
....................................................................................................................................................................................................................................
7-3
August 2011
Connections
Description
....................................................................................................................................................................................................................................
Connection service
The connection service allows OCH Trails to be connected through ports of the network
element by means of all optical switching. Optical trails can be added or dropped at each
network element that provides the appropriate transponders for the signal type. An optical
trail is composed of a series of optical cross-connects beginning at the source with an add
connection where a wavelength tracker key is applied to the optical signal, followed by a
series of through connections that route a signal to its destination, and culminating in a
drop connection at that destination where the signal is converted back to the appropriate
client wavelength and format. Optical trails can be uni-directional or bi-directional, 1+1
protected or unprotected. Services are, for the purpose of this document Optical Channel
Trails (OCH Trails) which are composed of optical cross-connects.
The opposite direction port parameter defines the association between two uni-directional
ports so a bi-directional cross connection can be used with different uni-directional
topology connections. For the opposite direction port, the value "0" is used to unassign
the provisioned value.
For service additions to DWDM FOADM Optical Networks, or to verify the addition of
unplanned (not included in the original network design) services on TOADM or mixed
networks, (e.g., unplanned OPS protection, alien services, or 2.5G wavelengths) use the
following procedure:
1. Enter the new service (demand) into the 1830 PSS Engineering and Planning Tool
(EPT), "run design", and "verify the design". See the Alcatel-Lucent 1830 Photonic
Service Switch (PSS) Release 3.6.0 Engineering and Planning Tool User Guide, the
sub-section on "WDM Demands" under the section titled "Traffic Design".
2. Create the commissioning file(s) in the EPT for the systems which the service
traverses, to send to the PhM.
3. Provision the new cards for the service using the procedure "Provision the System" in
Part III, Section 7, of the Alcatel-Lucent 1830 Photonic Service Switch 36/32/16
(PSS-36/PSS-32/PSS-16) Release 3.6.0 and 3.6.1 Installation and System Turn-Up
Guide. This will use the EPT commissioning files, which now contain the cards for
the new service and new provisioning information.
4. Re-adjust the power of the spans along the route of the new service, if necessary. For
TOADM or DWDM FOADM lines, for each of the spans where the new service
demand is added, passing through (if any) and dropped, run Egress and Ingress
adjustments to make the new EPT values effective. Use the procedure "Complete
commissioning on a mixed TOADM/FOADM system" from the Alcatel-Lucent 1830
Photonic Service Switch 36/32/16 (PSS-36/PSS-32/PSS-16) Release 3.6.0 and 3.6.1
Installation and System Turn-Up Guide procedures in Part III, Section 7, starting with
the procedure step 1 (skip the information on commissioning services as this is for
greenfield applications), for help in this activity.
Important! The EPT design must be up-to-date with the currently deployed network
before using the procedure above to add a new service to the network.
....................................................................................................................................................................................................................................
7-4
August 2011
Connections
Description
....................................................................................................................................................................................................................................
Connecting Alcatel-Lucent 1830 PSS OT with Alcatel-Lucent 1696 ROADM
The line interface of the 1830 OTs can be fibered directly to a 1696R node for transport in
a 1696-based network. For this application, the 1830 OT provides a signal (with
WaveTracker encoding and power management) to the 1696R node. The OT itself is
installed in an 1830 shelf, and is managed by the 1830 node. This 1696R/1830
interworking application is sometimes called the dangling OT.
A dangling OT, or a group of dangling OTs, are 1830 optical transponders which are
plugged into an 1830 shelf and managed by the 1830 node. However, the dangling OT
line side optical ports (transmit and receive) are not fiber-connected to a CWR or OMD
pack in the 1830 NE. Instead, the line side ports are fibered to a 1696R node. In the CLI
user commands, there is a provisionable parameter (CONNTO) that is used to set up an
external connection (i.e., CONNTO=external) from the OT to the 1696R node. When
CONNTO=external, the user can enable wave key modulation functionality and control
the optical output power on the line side interface of the OT (see Provision wave keys on
an encoder port to support dangling OT feature (p. 9-6)). The 1696R equipment will then
receive this signal (with wave keys already encoded) from the 1830 OT.
Note: If a port is Auto power-managed, and either Tx or Rx for that port is changed
from External to NotConnected, then both Tx and Rx will be automatically changed
from Auto to Manual power management.
Connecting Alcatel-Lucent 1696 ROADM transponder with Alcatel-Lucent 1830 PSS
The system supports the configuration where the 1696R transponder is plugged into the
1696R shelf and the network port of the transponder is connected to 1830 SVAC channel
port. The SVAC itself can be part of 1830 TOADM or FOADM node. The 1830 SVAC
does encoding and power control for the 1696R transponder transmitter. The 1696R shelf
will manage the laser on and WT encoding off. The Alcatel-Lucent 1830 PSS and
Alcatel-Lucent 1696 ROADM shelf each has its own TID.
....................................................................................................................................................................................................................................
7-5
August 2011
Connections
....................................................................................................................................................................................................................................
Display NE physical topology
...................................................................................................................................................................................................
In the WebUI, select Connections > Physical Topology.

Result: NE Physical Topology is displayed.
...................................................................................................................................................................................................
Loopback, External, Disconnect, and Connect functions can be made via the display.
E...................................................................................................................................................................................................
N D O F S T E P S
Display NE logical topology

...................................................................................................................................................................................................
In the WebUI, select Connections > Logical Topology.

Result: NE Logical Topology is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Provision cross-connects
...................................................................................................................................................................................................
In the WebUI, select Connections > Cross-Connects.

Result: Cross-connects are displayed. The following cross-connect options are
available: Create, View/modify, Delete.
E...................................................................................................................................................................................................
N D O F S T E P S
Provision EVPL connections

...................................................................................................................................................................................................
In the WebUI, select Connections > EVPL > FullRate or Connections > EVPL > SubRate
and QinQ.
Result: The EVPL Connections window is displayed.
...................................................................................................................................................................................................
Select Create.
....................................................................................................................................................................................................................................
7-6
August 2011
Connections
....................................................................................................................................................................................................................................
Result: The Create EVPL Connection window is displayed.

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

E...................................................................................................................................................................................................
N D O F S T E P S
Display Cross Connect Topology
Displays a list of the ports that this cross-connect traverses on the NE in the A-Z or Z-A
direction.
...................................................................................................................................................................................................
In the WebUI, select Connections > Cross Connects.

Result: Cross-connects are displayed.
...................................................................................................................................................................................................
Select the cross-connect and click A-Z Topology or Z-A Topology.

E...................................................................................................................................................................................................
N D O F S T E P S
Display NE power trace
Note: NE power trace is not applicable for CWDM cross-connects.

For a selected cross-connect, the WebUI will graphically display the ports and associated
power levels across the NE. Two different graphs will be supported: one for A-Z direction
and one for Z-A direction.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the cross-connect and click A-Z Power or Z-A Power.

E...................................................................................................................................................................................................
N D O F S T E P S
Display network power trace
Note: Network power trace is not applicable for CWDM cross-connects
....................................................................................................................................................................................................................................
7-7
August 2011
Connections
....................................................................................................................................................................................................................................
For the OCH trail of a selected cross connect, the WebUI displays a table with a list of
ports and associated power levels across the network.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the cross-connect and click A-Z Trace or Z-A Trace.

E...................................................................................................................................................................................................
N D O F S T E P S
Connecting 1830 PSS-1 to 1830 PSS-36/PSS-32/PSS-16
On the PSS-32, the 11STAR1 client port needs to be provisioned as follows from PhM:
...................................................................................................................................................................................................
In the Inventory view:
Assign the port to = OTU2

Provision the Domain Edge = false
Provision GCC to = enable

Provision the ITU = X (one of 8 CWDM channels)
Provision FEC = g709FEC
Provision OTU Rate = otm11G096
...................................................................................................................................................................................................
In the Topology view:
provision an external connection from the 11STAR client port to the 1/7/X (where X
is 1 for line 1 and 2 for line 2)
...................................................................................................................................................................................................
Put the admin state to up, or up AINS.

...................................................................................................................................................................................................
On the PSS-1 using the WebUI:
Select the line port

Under the OTU provisioning set the gcc enabled
Set the FEC to RSFEC
Set the channel if necessary or to auto, and it will detect the CWDM wavelength.
....................................................................................................................................................................................................................................
7-8
August 2011
Connections
....................................................................................................................................................................................................................................
Provision the external topology connection to connect the Line port to the 1/X/2
where X is slot of the 11STAR
Provision the admin state to up
Result: Once this is done you should be able to ping the PSS-1 through the PSS-32s.
This would also work if the PSS-1 is the IPGNE and you would be able to ping the
PSS-32 from the PSS-1.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
7-9
August 2011
Connections
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-10
August 2011
Protection
8
Overview
Purpose
This chapter describes the protection functionality supported by the 1830 PSS.
Contents
Description
8-1
Protection procedures
8-8
Description
Y-cable protection
Y-cable protection is a line side (network side) protection mechanism which protects line
card, client side laser, network side laser, and network side fibers (assuming diverse fiber
routes). Y-cable protection is based on permanent head-end bridging and tail-end
selection, with a pair of OT cards at each end. The head-end bridge is done by employing
a 50% splitter on the Rx of the client-side ports. The incoming signal from the customer
equipment is split and received by both the working and protection OT cards. The tail-end
selection is done by having one of the working/protection OT cards turn its Tx client-side
laser on, while the other turns its laser off. This Tx signal is channelled through a joiner
(splitter in reverse direction) and sent to the customer equipment. Either the working or
the protection card can drive the signal through the joiner. The same configuration is used
in the reverse direction to provide protection in both directions.
Y-cable supports the protected OT configuration. A passive splitter/joiner (Y-cable) is
connected to a pair of client ports on redundant transponder packs (OTs) at one end of the
network, with the same arrangement at the other end of a point-to-point link across the
...................................................................................................................................................................................................................................
8-1
August 2011
Protection
Description
....................................................................................................................................................................................................................................
network. The OT line ports must be connected to diversely routed working and protection
lines across the network (no shared risk groups in common). The customer is responsible
for establishing diverse routes; there is no software verification of this.
Port numbers for Y-cable protection must match. In other words, port #1 can only be
paired in Y-cable protection arrangement with port #1 on the adjacent card. Similarly, port
#2 works with port #2 on the adjacent card, and so on.
Y-cable protection can be used with any supported type of OT, but the near-end working
OT must be connected to the far-end working OT and the near-end protection OT must be
connected to the far-end protection OT. The customer is responsible for seeing to it that
near-end and far-end OTs are the same. The ports must be provisioned for the same signal
rate and format at both ends of the network. The customer should normally configure
working and protection ports with the same threshold values.
Note: Alcatel-Lucent 1830 PSS does not support Y-cable protection on the 11STAR1
pack when the client signal type is OTU2. In this release, Y-cable protection cannot be
used with OTM0.2 signal on 11STAR1 OT.
Note: Both unidirectional and bidirectional are supported for Y-cable protection.
Note: 11DPE12 Y-cable protection is for the 1830 PSS-4 only; it is not supported on
the 1830 PSS.
Protection groups
The NE supports the definition of a Y-cable protection group. This logical object is the
basis for automatic and manual protection switching operations and notifications. A
Y-cable protection group represents the protection association between two client-side
ports of adjacent OT packs. Protection switching is performed only within an established
protection group. When there is no protection group, no protection switching can occur,
either manual or automatic.
An OT with 10 client ports can have up to 10 separate Y-cable protection groups.
Switching operations, both manual and automatic, are on a per protection group basis.
Each protection group operates completely independently of the others, with its own
protection state machine. For the first Y-cable protection group between a pair of adjacent
OT ports, the user is free to specify either port as the working port, and the other port as
the protection port. This choice designates one OT as the working card, and the other as
the protection card.
When there are multiple Y-cable protection groups between the same pair of OTs, the
working/protection port role designations must be specified consistently (i.e. all working
ports must be on one OT, and all protection ports must be on the other OT).
The WebUI supports create, modify, delete, and view functionality for protection groups
associated with a port. For Y-cable, protection groups are applicable to the following port
types: 11DPM12, 11QPA4, 11STAR1, 11STMM10, 11STGE12, 43STA1P, 43STX4(P).
....................................................................................................................................................................................................................................
8-2
August 2011
Protection
Description
....................................................................................................................................................................................................................................
Note: Y-cable performance times may not be met on MUX OTs if more than 4 ports
on each OT belong to a protection group. Under this condition, the switch time can
exceed 50ms,
Uni-directional switching
In uni-directional switching, each end makes an independent switching decision based on

defects affecting the direction of transmission received from the line side, or based on
user command. One end may select from the working line while the other end is selecting
from protection. Uni-directional protection switching can be used to protect either
uni-directional or bi-directional customer services. There is no difference in protection
group provisioning or behavior for the two types of traffic.
Bidirectional switching
In bidirectional switching, an end-to-end APS message protocol is used to guarantee that

the selectors at both ends of a circuit are always synchronized - either both on working, or
both on protection. Whether the switch is caused by a defect or a user command, both
ends always switch together.
Bidirectional protection switching can be used to protect only bi-directional customer
traffic. If a bi-directional Y-cable protection group is connected to a unidirectional Y-cable
protection group across the network, the bidirectional group will operate as a
unidirectional group for switching compatibility (the bidirectional end will raise an
alarm).
Non-revertive switching
In non-revertive switching, the protection side remains active after the working line has
recovered from the failure that caused the automatic switch to protection, or after the user
switch-to-protection command is cleared.
Note: For 43STA1P and 43STX4(P), 11QPA4, 4DPA2, and 4DPA4 OTs switching
type must be non-revertive.
Revertive switching
In revertive switching, the traffic is automatically switched back to the working line when
the working line has recovered from the failure or the user command is cleared. In the
failure-recovery case, the switch back to working is delayed until working has been
continuously good for the number of minutes specified by the WTR parameter. In the case
of clearing a user switch command, there is no delay.
Note: If Direction = Unidirectional, then Type must be Non-Revertive. For
Bidirectional, both Revertive and Non-Revertive are supported. Optical connections
must be created before a protection group, and a protection group must be deleted
before its optical connections.
....................................................................................................................................................................................................................................
8-3
August 2011
Protection
Description
....................................................................................................................................................................................................................................
OPS protection
Subnetwork Connection Protection (SNCP) is a dedicated protection mechanism

providing path-level protection for individual optical channels that are routed
independently across any network. It may be applied at any path layer in a layered
network. SNCP is a dedicated 1+1 protection architecture in which the traffic is
permanently bridged onto two SNCs at head-end, carried through any number of facilities
of any type, and selected from one of the two SNCs at the tail-end. One SNC is called the
working SNC and the other is called the protection SNC. The path selection is based on
purely local information: server layer information (SNC/I), client layer information
(SNC/N) or TC monitoring information (SNC/S).
For OPS protection of optical channels, the OPS is placed at the Optical Channel (OC)
layer, between the Optical Multiplexing layer and the Optical Channel to Optical Signal
(OCH/OS) adaptation, (i.e., the OT function).
The OPS supports two types of protected line configurations. In both cases, there is a
single unprotected OT at each end. In both cases, the working and protection lines must
be diversely routed across the network (no shared risk groups in common).
Internal OT, no SVACs - The OT line port is connected to the OPS SIG port. The OPS
A port and B port are connected to two different lines, either via SFD filter ports, or
via CWR8 colorless ports.
Alien/External OT, redundant SVACs - The alien OT is connected to the OPS SIG
port. The OPS A port and B port are connected to two different SVACs. The two
SVACs are connected to two different lines, either via SFD filter ports, or via CWR8
colorless ports.
Note: OPS protection can be used with two MVACs. For this type of protection an
OPS card is placed on the client-side optical path of the MVACs. Protection is
provided against both fiber cuts and MVAC failure.
OPS protection can be used with any supported type of OT. There is no restriction on
physical location within the NE of the associated OT, OPSA, SFD, CWR, or SVAC
circuit packs. The packs can all be in different shelves if desired. For packs in the same
shelf, there is no requirement for physical adjacency. In the receive direction (selector
function), the two SFD/CWR ports connected to the OPS A and B ports can have different
frequencies. In the transmit direction (splitter function), the two SFD/CWR ports must
have the same frequency.
Protection groups
The NE supports the definition of an OPS protection group. This logical object is the
basis for automatic and manual protection switching operations and notifications. An OPS
protection group represents the protection association between the two line-side ports (A
and B) of a single OPSA pack. Protection switching is performed only within an
....................................................................................................................................................................................................................................
8-4
August 2011
Protection
Description
....................................................................................................................................................................................................................................
established protection group. When there is no protection group, no protection switching

occurs, either manual or automatic. The user is free to specify either of the line-side ports
(A or B) as the working port, and the other port as the protection port.
Note: For OPS protection group creation, ports A and B cannot be in-service. They
must be down or in maintenance state (mt). The default OPS port state is down.
Uni-directional switching
OPS protection groups support only uni-directional protection switching. In

uni-directional protection switching, each end of an optical channel operates
independently of the other. A failure affecting only one direction of transmission will
cause a protection switch of only that direction. The unaffected direction of transmission
is not switched. OPS protection groups do not use any end-to-end APS protocol. All
switch requests are local. The two ends have no knowledge of each other.
Non-revertive switching
OPS protection groups support only non-revertive protection switching. There is no

automatic switch from protection back to working because of a recovery of working, or
because a user switch to protection is cleared.
E-SNCP protection
E-SNCP on 11DPE12(E), 11DPM12, 11QPA4, 4DPA4 and 4DPA2 OT is a line side

(network side) protection mechanism which protects against network side SFP related
failure, line signal failure caused by network side fiber disconnection or intermediate NE
nodes malfunction.
E-SNCP protection is implemented by permanent head-end bridging and dynamic tail end
selection. The E-SNCP function is realized within one 4DPA4/4DPA2 OT. Each client
port (plus the two line ports) form an independent protection group. But due to hardware
restriction, the bridging is performed at ODU1 level. As a result, all client ports assigned
to the working line are bridged simultaneously to the protection line. (From this
perspective, E-SNCP is a board level behavior.)
In the source direction, traffic from the client ports is aggregated into one ODU1 line
signal, then the ODU1 signal is bridged into two parts, one for working path and another
for protection path. Both parts are inserted with OTU1 overhead and FEC code being sent
to the lines. The optical wavelengths are then modulated with WT encoder/eVOA before
sending to the SFD or FOADM.
In the receiving direction, the OT receives two OTU1 line signals (working and
protection). After FEC error correction and OTU1/ODU1 overhead termination
respectively, client traffic is extracted independently from the two line signals according
to the OPTS mapping structure determined for the outgoing direction. Then, depending
....................................................................................................................................................................................................................................
8-5
August 2011
Protection
Description
....................................................................................................................................................................................................................................
on the external switch commands for individual protection groups, or signal quality, the
traffic for each client port is selected independently from the working or protection line
port.
Note: On a given 4DPA4/4DPA2 card, either all services are protected, or all services
are unprotected. There can be no mixing or combining protected/unprotected services.
Note: Protection is not supported on a 11DPE12(E) card if Operational Mode =
Sub-rate. For 11DPE12(E) OT both revertive and non-revertive are supported when
Direction = Unidirectional.
Protection groups
The NE supports the definition of E-SNCP protection groups on the 11DPE12(E),

11DPM12,11QPA4, 4DPA4 and 4DPA2 OT. This logical object is the basis for automatic
and external commands triggered switching operations and notifications. Each protection
group consists of one client port, plus the working line port and protection line port. Up to
4 protection groups can be created on 4DPA4 OT - one for each client port. On 4DPA2
only one client port is supported. Switching operations, both automatic switching and user
commands, are on a per protection group basis. Each protection group operates
completely independently of the others, with its own protection state machine.
Before starting the creation of protection group, at least one line port must be in IDLE
state (no client port has timeslot assignments to this line port). Otherwise, creation of
protection group is denied.
If initially both line ports are in IDLE state (no timeslot assignments), the user is free
to specify either line port as the working port and the other line port as the protection
port for the first protection group, but the subsequent protection group creations have
to follow working/protection designation by the first protection group.
If initially one line port has timeslot assignments, then all protection group creations
have to specify this line port as the working line port. Otherwise, creation of
protection group is denied.
For 11DPE12(E) and 4DPA4 OTs, if one or both of the line ports (L1 and/or L2) is
unassigned, then the protection group cannot be created. For 11DPE12(E), both line
ports must have Signal Rate = OTU2.
On the 11DPE12(E) with Operational Mode = QinQ, up to 10 protection groups may
be supported per client port, one per VTS.
For 11QPA4 OT, the line port associated with the selected client port must be assigned
and have Operational Mode = Add/Drop or DropRegen in order to create a protection
group.
Note: The switch time may exceed 50ms when the user provisions > 32 circuits.
....................................................................................................................................................................................................................................
8-6
August 2011
Protection
Description
....................................................................................................................................................................................................................................
Protection switch requests
Protection switching is implemented via automatic switch events, or from user switch
commands (override automatic switching). The WebUI allows the user to request a
protection switch and supports the following switch commands:
Clear - Clears any existing user switch command. Does not clear any existing WTR
state. In some cases a clear command can result in an immediate switch.
Lockout of Protection - Makes working active and prevents any subsequent switch to
protection for any reason until the lockout is cleared.
Forced Switch to Protection - Makes protection active.
Forced Switch to Working - Makes working active.
Manual Switch to Protection - Makes protection active.

Manual Switch to Working - Makes working active.
Note: These commands will be denied if an equal or higher priority request is already
in effect. Also, these commands will be denied if operation on the OT circuit packs is
not possible, whether due to circuit pack missing/failed, shelf or card communication
failed, or any other reason.
....................................................................................................................................................................................................................................
8-7
August 2011
Protection
....................................................................................................................................................................................................................................
Create protection group
...................................................................................................................................................................................................
In the WebUI equipment tree, select the port and click the Port Protection tab.
Result: The create APS Group screen is displayed.
...................................................................................................................................................................................................
Enter the APS group parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
View all protection groups

...................................................................................................................................................................................................
In the WebUI equipment tree, select Reports > APS Groups

Result: The Automatic Protection Switch Groups screen is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
View/modify protection group

...................................................................................................................................................................................................
Result: The create APS Group screen is displayed if the selected port is not already a
member of an APS group. The APS Group Details screen is displayed if the selected
port is a member of an APS group.
...................................................................................................................................................................................................
Enter the APS group parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
Delete protection group
Note: Deletion of a protection group will be denied if there are still cross connects
that depend on the protection group.
....................................................................................................................................................................................................................................
8-8
August 2011
Protection
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Result: The APS Group Details screen is displayed if the selected port is a member of
an APS group.
...................................................................................................................................................................................................
Select Delete this Protection Group and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
Request protection switch
Note: The WebUI does not allow the user to execute a switch command if the card is
not equipped. When a protection switch is requested, the WebUI displays a warning
message indicating that the switch could be service affecting. The user can continue
with the request or cancel.
...................................................................................................................................................................................................
Result: The APS Group Details screen is displayed if the selected port is a member of
an APS group.
...................................................................................................................................................................................................
Select the switch request for the port and click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
8-9
August 2011
Protection
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
8-10
August 2011
Wavelength Tracker
9
Overview
Purpose
This chapter describes the Wavelength Tracker technology supported by the 1830 PSS.
Contents
Description
9-1
Wave keys procedures
9-6
FOADM / FOADM-TOADM procedures
9-11
Description
Overview
Wavelength Tracker is a technology used to:
encode a unique identifier onto a signal as it enters the network

detect the identifier at various points in the network.
The Wavelength Tracker identifier consists of a pair of numbers, called wave keys, that
are assigned to a wavelength. The wave key pair assigned to a wavelength is unique in the
network. A unique wave key pair is assigned for each individual circuit, or optical trail, in
the network. Thus if there are two or more circuits in a network that use the same
wavelength, each circuit is assigned a unique pair of wave keys. A network can support
multiple occurrences of the same wavelength only if they do not share a common fiber. In
order for a wave key pair to be unique, it can share one of its wave keys with another
optical trail in the network, but not both.
...................................................................................................................................................................................................................................
9-1
August 2011
Wavelength Tracker
Description
....................................................................................................................................................................................................................................
Encoding Wavelength Tracker identifiers
The Wavelength Tracker wave keys are encoded onto the wavelength for an optical trail at
network ingress. The following cards support wave key encoding:
112SCA1
112SCX10
11DPE12(E)
11DPM12
11QPA4
11STAR1
11STMM10
11STGE12
43STA1P
43SCX4
43STX4
43STX4P
4DPA4
SVAC
MVAC
Detecting Wavelength Tracker identifiers
In order to trace a wavelength through the network, its presence at a port must be
detected. The presence or absence of a wavelength at a port is determined by equipping a
port with a Wavelength Tracker detector, which is able to detect and identify the wave
keys encoded onto a wavelength. In addition to detecting the wave keys encoded onto a
wavelength, the Wavelength Tracker detectors can also measure the optical power for
each encoded channel that passes through the port.
Associating the wave keys with an optical trail
The wave keys for an optical trail are assigned when the optical trail (service) is created.
Typically, the wave keys are automatically assigned by the NE software (ROADM rings
only) or the 1354 RM-PhM (ROADM, static, and mixed networks). Manual assignment is
also possible, though not recommended.
....................................................................................................................................................................................................................................
9-2
August 2011
Wavelength Tracker
Description
....................................................................................................................................................................................................................................
The following actions are performed when the optical trail is created:
the wave keys associated with the trail are assigned and are encoded at the service
endpoints (at a transponder or SVAC). A different wave key pair is assigned for each
direction.
the wave keys assigned to the trail are propagated to each Wavelength Tracker detect
point along the service path (as determined from the programmed fiber topology).
Each detect point is then programmed to expect to receive a certain set of wave keys.
Features provided by Wavelength Tracker
Wavelength Tracker makes it possible to check and confirm the path that a wavelength
takes through the network. This capability allows the operator to ensure that the network
connections are correct. Since the Wavelength Tracker detection points are programmed
to expect a certain set of wave keys, wave keys that are unexpectedly received at a
detection point are flagged, and typically indicate a faulty cross-connection. Wavelength
Tracker, with its multiple detection points, immediately flags and pinpoints the location of
these faulty connections, allowing them to be discovered and corrected quickly and easily.
The ability of the Wavelength Tracker detection points to measure the optical power of
each channel passing through the port allows for:
interactive power monitoring
notification of changes in the power levels for all channels in the network at all
detection points.
When a service is provisioned, the system assigns expected power levels at the detection
points along the path of the service at the Auto power managed lines using data from the
Engineering Planning Tool. If any of the lines along the path of the service are Manual
power managed lines, the user will set the expected power levels at the detection points to
the observed power levels after adjusting the optical power control points.
Adding services to a network
If the new service path through the network crosses lines whose optical power
management type is set to Auto, the service will automatically ramp up to the target
egress power at the launch node. Along the lightpath, control loops will adjust attenuation
settings to bring the services optical power level into alignment with the target points
along the lightpath. Wavelength Tracker power deviation thresholds are set up around
expected powers along the entire lightpath automatically.
For a FOADM system or mixed FOADM-TOADM system containing lines that are auto
power managed and lines that manually power managed, the user must ensure that the
service reaches the correct operational power levels and that Wavelength Tracker
monitoring points are set correctly (see Adding a service to a FOADM system or mixed
FOADM-TOADM system (p. 9-11)).
....................................................................................................................................................................................................................................
9-3
August 2011
Wavelength Tracker
Description
....................................................................................................................................................................................................................................
Reported information
Using the Wavelength Tracker information, the NE is able to identify all of the
wavelengths that pass through a Wavelength Tracker detect point. For each wavelength,
Wavelength Tracker reports the following information:
the ITU channel being used to transport the wavelength
whether the channel is expected at the port or not (based on the service topology)
the optical power of the wavelength
The information is displayed graphically in the WebUI. The 1354 RM-PhM can display
data for the entire network, for example it can display a graph showing the optical power
for a service at all of the Wavelength Tracker detect points through which the service
passes.
Long haul Wavelength Tracker
The Alcatel-Lucent 1830 PSS supports both "standard" Wavelength Tracker (WT), for
regional applications, and Long-Haul Wavelength Tracker (LH-WT), for long haul
applications. LH-WT is supported by the WTOCM card, which is connected to the
external facing LD on an optical line.
The WTOCM is supported with the following LDs:
A2325A
AHPHG
AHPLG
ALPHG
AM2017B
AM2325B
AM2125A
AM2125B
AM2318A
Each WTOCM can provide LH-WT for any 2 LDs.

Unkeyed optical channels are not supported by the WTOCM. Software will not allow the
provisioning of an unkeyed service across an LD with a WTOCM, and will not allow a
connection between a WTOCM and LD if there are unkeyed services on the LD. The
system will not allow the creation of an unkeyed connection to a span which is equipped
with WTOCM monitoring
Each line within an optical node, and each endpoint on an OMS span, must be configured
with the same WT capability, either long haul (with WTOCM), or standard (without
WTOCM).
....................................................................................................................................................................................................................................
9-4
August 2011
Wavelength Tracker
Description
....................................................................................................................................................................................................................................
The WTOCM is used on the following node types for long haul configurations:
TOADM
ROADM
Anydirection
FOADM end terminal with DGE in path
WTOCM is optional for the following node types:
2D+FOADM
FOADM end terminal, with no DGE in path
ILA
....................................................................................................................................................................................................................................
9-5
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................

Provision wave keys on an encoder port to support dangling OT feature
...................................................................................................................................................................................................
In the WebUI, from the equipment tree select the L1 port for the OT.
...................................................................................................................................................................................................
Select the Wave Keys tab.

Result: The Wave Key Encoder screen is displayed.
...................................................................................................................................................................................................
Set values for Wave Key 1 and Wave Key 2.

Note: Wave Keys can only be modified if Connection Type = External and Frequency
has been set (i.e. does not equal None). Connection Type and Frequency are displayed
on the Details page.
E...................................................................................................................................................................................................
N D O F S T E P S
Set expected network output power
Note: These operations can only be done if the port is manually managed. If the port
is auto managed, it belongs to an auto managed cross connect, and the keys can only
be modified as attributes of the cross connect. Power cannot be modified.
...................................................................................................................................................................................................
In the WebUI equipment tree, select the appropriate port, select the Wave Keys tab, and
set Expected Network Output Power.
...................................................................................................................................................................................................
Set expected output power and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
View wave keys (decoder ports)

...................................................................................................................................................................................................
In the WebUI equipment tree select the appropriate port, select Wave Keys In or Wave
Keys Out tab.
....................................................................................................................................................................................................................................
9-6
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
The Wave Keys Decoder In/Out screen is displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
Clear wave keys
Note: Wave keys can only be cleared for manually power managed ports.
...................................................................................................................................................................................................
In the WebUI equipment tree, select the appropriate port and click on the Wave Keys In or
Wave Keys Out tab.
Result: The Wave Keys Decoder In/Out screen is displayed.
...................................................................................................................................................................................................
Select the record and click Clear Wave Keys.

E...................................................................................................................................................................................................
N D O F S T E P S
Set power
Note: Expected Power can only be set for manually power managed ports.
...................................................................................................................................................................................................
Wave Keys Out tab.
...................................................................................................................................................................................................
Select the record and click Set Power.

Result: The Set Power screen is displayed.
...................................................................................................................................................................................................
Set expected power attributes and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
9-7
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................
View channel power summary

...................................................................................................................................................................................................
Wave Keys Out tab.
...................................................................................................................................................................................................
Click Power Summary.

Result: A graphical Power Summary is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
View unexpected wave keys

...................................................................................................................................................................................................
In the WebUI equipment tree, select the appropriate port and click on the Unexpected
Wave Keys tab.
Note: The following ports support unexpected wave key data when WTD is enabled.
A2325A LINE, SIG, DCM port
ALPHG LINE, SIG, DCM port

AHPHG LINE, SIG, DCM port
AHPLG LINE, SIG, DCM port
AM2017B LINE, SIG, DCM port
AM2325B LINE, SIG, DCM port

AM2125A/AM2125B/AM2318A LINEIN, LINEOUT
CWR8 SIG, THRU port
CWR-88 SIG, THRU port
MESH4 SIGIN
OPSA SIG, A, B port

WR8-88A SIG, THRU, DROPOUT
WTOCM IN{1-4} port
Result: The Unexpected Wave Keys screen is displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
9-8
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................
View wave key data at NE level
The WebUI displays wave key data for wave keys in use on the NE.
...................................................................................................................................................................................................
In the WebUI, select Reports > Wavelength Tracker > Port Wave Keys.
...................................................................................................................................................................................................
On the ensuing Wave Keys screen, select Port, Direction, Frequency, or All and click
Retrieve.
Result: The selected wave key data is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
View unexpected/missing wave keys at NE level
The WebUI displays all unexpected wave keys detected on the NE, or all missing wave
keys on the NE.
...................................................................................................................................................................................................
In the WebUI, select Reports > Wavelength Tracker > {Unexpected Wave Keys/Missing
Wave Keys}.
Result: The respective Wave Key data is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Provision optical lines monitoring (WT mode or WTOCM mode)

...................................................................................................................................................................................................
After WTOCM pack is installed and provisioned, an association to the line side port that
it monitors must be provisioned.
Note: If the node is commissioned via the commissioning process, this association is
provisioned automatically for the user.
...................................................................................................................................................................................................
After association of a WTOCM pack with a line side port, a setting must be made for the
line operation mode. This setting is made at the external Line port of the ingress LD of
the line.
....................................................................................................................................................................................................................................
9-9
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Regardless of WTOCM usage or not, a line setting needs to be made at the external Line
port now for all optical lines that defines the WT power display and OCh alarms
functionality.
Note: If the NE is provisioned by the commissioning process, these settings are made
automatically by the 1354 PhM / CPB tools which provision the EPT commissioning
file(s).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
9-10
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................

Adding a service to a FOADM system or mixed FOADM-TOADM system
A FOADM system or mixed FOADM-TOADM system contains lines that are Auto
power managed and lines that Manually power managed.
...................................................................................................................................................................................................
View the power management type by selecting the Power Management tab of the Line
port of the ingress LD of a line.
Note: If the lightpath of the service traverses only lines that are Auto power managed,
then no further steps are required by the user. If the lightpath traverses a mix or Auto
power managed lines and Manually power managed lines, the following steps must be
followed:
...................................................................................................................................................................................................
Starting at the node where the service originates:
If the egress line of the origination point of the service is Automatically optical power
managed wait for one minute for the optical power to ramp up.
If the egress line of the origination point of the service is Manually optical power
managed adjust the setpoint (target output power) of the OT or SVAC Line port to
increase the optical power. If the service is an OT protected by OPSA, change the
OPSA VOA attenuation setting instead of the OT setpoint. Iteratively adjust the power
by steps of 5 dB or less, wait for thirty seconds to observe the result and check the
WT measured power at the egress point onto the line (the reverse direction ingress LD
Line Out port). The target output power range at the egress point is the WT expected
power +/- 0.5 dB.
...................................................................................................................................................................................................
Set the Expected Network Output Power field of the Wave Keys tab for the L1 port of
the OT or SVAC or for OPSA, set the voa attenuation field of the Switch tab for the A or
B port of the OPSA.
Set the VA1 or VA2 port setpoint if the OT is a 4DPA4, 11QPA4, and 11DPE12(E) using
a fast eVOA pluggable module in the VA1 (or VA2) port. If OT does not have a VA
(variable attenuator) port, set the L1 port target output power. If the OT does have a VA
port, set the VA port target output power. If the OT is protected by an OPSA pack, set the
OPSA A or B port VOA attenuation setting to adjust the optical power.
Note: If the optical output power of the OT or SVAC Line, or OPSA A/B port fails to
increase when the setpoint is increased use the Alcatel-Lucent 1830 Photonic Service
Switch 36/32/16 (PSS-36/32/16) Release 3.6.0 and 3.6.1 Maintenance and
Trouble-Clearing Guide to clear the problem.
....................................................................................................................................................................................................................................
9-11
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................
If the WT optical output power at the egress point onto the line cannot reach within
0.5 dB of the WT expected power use the Alcatel-Lucent 1830 Photonic Service
Switch 36/32/16 (PSS-36/32/16) Release 3.6.0 and 3.6.1 Maintenance and
Trouble-Clearing Guide to clear the problem.
Changes to the power levels of existing services are expected and these services may
fall outside the range of 0.5 dB from the target power at line out. The already existing
services should remain within their WT deviation thresholds at line out.
...................................................................................................................................................................................................
If the egress line for this network element is manually power managed, set the WT
expected powers at the WT detect points through the node.
...................................................................................................................................................................................................
Note: Only follow this step if there are more than 2 NEs including the add and drop
NEs along the lightpath.
Locate the next ingress line of the lightpath.
If the ingress line of this through path is Auto optical power managed, then proceed to
the egress line.
If the ingress line of this through path is Manually optical power managed, review
whether the ingress LD gain needs to be set. View the ingress LD Sig Out target
power per channel. Select the Sig Details tab to view the Per-Channel Output Power
field. Note the value of the per channel target power.
...................................................................................................................................................................................................
View the current WT power(s) of any service(s) present at the Sig port Out. Select the
Wave Keys Out tab for the Sig port of the ingress LD to view the Wave Key power for
each channel.
...................................................................................................................................................................................................
Change the gain of the ingress LD until the WT power(s) are centered around the target
power. For example, if there is one wavelength present and its optical power is -2 dBm
and the target is 0 dBm, increase the gain setting of the LD by 2 dB. Set the value of the
Gain field of the Sig tab.
...................................................................................................................................................................................................
After each gain adjustment wait for ten seconds to ensure the reported WT power(s) fully
reflect the gain change. If this is a manually optical power managed TOADM line set the
CWR8 Sig In expected power to the measured power after completing the ingress LD gain
change.
...................................................................................................................................................................................................
Select the Wave Keys Out tab for the Sig port of the CWR8 to set the Wave Key power
for the channel.
....................................................................................................................................................................................................................................
9-12
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
10
If the egress line of this through path is Automatically optical power managed, move on
to the next line at the next NE.
If the egress line of this through path is Manually optical power managed, view the egress
point (reverse direction ingress LD Line Out port) target output power per channel. Select
the Port Details tab to view the Per-Channel Output Power field.
...................................................................................................................................................................................................
11
View the current WT power of the new service at the Line port Out. Select the Wave Keys
Out tab for the Line port to view the Wave Key power for the channel.
...................................................................................................................................................................................................
12
Calculate the difference between the WT measured power and the target power. If this is a
FOADM line, instruct the field personnel to change the attenuating pad on the path
between the ingress line and this egress line by this same amount only if the channel is
directed through the NE using the channel ports. For example, if the WT power is 2 dB
less than the target power, the attenuating pad value should be decreased by 2 dB. If the
WT power is 2 dB greater than the target power, the attenuating pad value should be
increased by 2 dB. If the WT power is within 1.0 dB of the target power, consider the
error acceptable and make no further changes. For a channel directed through the NE
using the express ports, the user should not need to change the pad value already in place.
Note that changes to the power levels of existing services are expected and these services
may fall outside the range of 1.0 dB from the target power at line out. The already
existing services should remain within their WT deviation thresholds at line out.
If this is a TOADM line, change the expected power at the Thru Out port of the CWR8
until the WT power is within 0.5 dB of the target power. Wait at least one minute before
adjusting the power set point again to allow the control loop adjust. (Note that in the case
of a TOADM line, initially the measured WT will be very low or not measurable until the
expected power of the CWR8 Thru Out port has been set for the first time).
If the NE egress line is a Manually managed TOADM line change the expected power at
the Thru Out or CLS Out port of the CWR8 until the WT power is within 0.5 dB of the
target power. (In the case of a TOADM line, initially the measured WT will be very low
or not measurable until the expected power of the CWR8 Thru Out port has been set for
the first time). Follow an iterative process until the power observed at the egress Line Out
is in range. The controller converges slowly, therefore allow up to 2 minutes after making
a change for the power to converge to a new setpoint.
...................................................................................................................................................................................................
13
Select the Wave Keys Out tab for the Thru port to set the Wave Key power for the
channel.
....................................................................................................................................................................................................................................
9-13
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
14
If the ingress or egress line for this through network element is manually power managed,
set the WT expected powers at the WT detect points through the node.
...................................................................................................................................................................................................
15
Repeat this process for every through network element along the services lightpath.
...................................................................................................................................................................................................
16
At the last NE in the services path:

If the ingress line of this through path is Manually optical power managed, review
whether the ingress LD gain needs to be set. View the ingress LD Sig Out target power
per channel. Select the Sig Details tab to view the Per-Channel Output Power field. Note
the value of the per channel target power.
...................................................................................................................................................................................................
17
View the current WT power(s) of any service(s) present at the Sig port Out. Select the
Wave Keys Out tab for the Sig port of the ingress LD to view the Wave Key power for
each channel.
...................................................................................................................................................................................................
18
Change the gain of the ingress LD until the WT power(s) are centered around the target
power. For example, if there is one wavelength present and its optical power is -2 dBm
and the target is 0 dBm, increase the gain setting of the LD by 2 dB. Set the value of the
Gain field of the Sig tab.
...................................................................................................................................................................................................
19
After each gain adjustment, wait for ten seconds to ensure the reported WT power(s) fully
reflect the gain change. If this is a manually optical power managed TOADM line, set the
CWR8 Sig In expected power to the measured power after completing the ingress LD
gain change.
...................................................................................................................................................................................................
20
Select the Wave Keys Out tab for the Sig port of the CWR8 to set the Wave Key power
for the channel.
...................................................................................................................................................................................................
21
If the ingress line of this drop path is a Manually optical power managed TOADM line
and the service uses the CLS port, set the WT expected power at the drop port to the
default drop target power. View the drop target power. Select the CLS port details of the
CWR8 to view the drop target. Set the WT expected power to the same value.
...................................................................................................................................................................................................
22
Select the Wave Keys Out tab for the CLS port of the CWR8 to set the Wave Key power
for the channel. Wait for at least two minutes for the power level to reach the target value.
....................................................................................................................................................................................................................................
9-14
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
23
If the ingress line for this drop network element is manually power managed, set the WT
expected powers at the WT detect points through the node. If the service is an OPSA
protected service the A or B port WT expected power value must be set.
...................................................................................................................................................................................................
24
Repeat the procedure steps above for the other direction of the service for a bi-directional
service.
...................................................................................................................................................................................................
25
Repeat the procedure steps above for the protection service, if applicable.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
9-15
August 2011
Wavelength Tracker
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
9-16
August 2011
10
10
Database
backup and
restore
Overview
Purpose
This chapter describes the Alcatel-Lucent 1830 PSS database management operations
including database backup and database restore.
Contents
Database management
10-1
Database backup
10-6
Database restore
10-8
Database backup/restore procedures
10-10
Database management
Introduction
An Alcatel-Lucent 1830 PSS NE maintains all of its configuration data in an active

non-volatile memory database. The NE provides mechanisms that allow a user to backup
the active non-volatile memory database to a database file on a Remote File Server (RFS)
and to restore the active database from a file on the RFS. In the database backup process,
a temporary copy of the active database is first created and then transferred to the RFS. In
the database restore process, the remote database file is first transferred to the NE where it
is validated. If the transferred database is valid, then the NE automatically restarts as part
of the installation of the newly downloaded database. After the restart, the restored
database becomes the active database.
...................................................................................................................................................................................................................................
10-1
August 2011
Database management
....................................................................................................................................................................................................................................
As a maintenance feature, the NE allows the operator to reset its active database to a
factory installed default configuration. The NE supports autonomous messages to report
all changes to the provisioning database, equipment installation or removal, equipment or
facility failure or recovery.
Database overview
Before the NE can access the software and database servers, the NE must be configured
to point at the servers. Separate commands are used to configure the databases and
software servers. The servers must reside on a computer that is accessible from the NE.
The servers can be on the same computer or they can reside on two different computers.
The active non-volatile memory database is maintained by the NE and reflects the NE
configuration and NE provisioning. A temporary copy of the active database is created by
the NE before file transfer to an RFS. A temporary database space is also the destination
for remote file transfer from the RFS. The NE supports autonomous reporting of changes
to the active database that come about as the result of provisioning and configuration
changes.
Redundancy
The NE non-volatile memory (flash memory card) is considered to be part of the active
main EC. In the case of a redundant controller configuration, the system assures
consistency of non-volatile memory contents between the active and standby main shelf
controllers.
The system is responsible for replicating any change to the NE active database on the
active Main EC to the corresponding database on the standby Main EC (if available). In
particular, the implementation of the operations for creation of a database backup and
download of a database backup to the active Main EC is expected to have the
corresponding effects on the standby Main EC.
After reboot or insertion of a standby EC, an EC LED will indicate a status of Software
Download (flashing amber) until the standby database image is synchronized with the
primary.
Note: For 1830 multi-shelf configuration, if one shelf is redundant, all shelves should
be redundant.
Local database operations
Any failures in updating the database are reported by the NE. After a power failure, or in
the cases of severe faults, the system is capable of being automatically restored from the
active non-volatile memory database to the latest stable and consistent configuration that
existed before the failure occurred.
....................................................................................................................................................................................................................................
10-2
August 2011
Database management
....................................................................................................................................................................................................................................
The system provides the ability to restore the active database (from the remote database),
and thus enable normal operations via each of the supported user interfaces. NE
software has a method for verifying the valid state of locally stored databases (e.g.,
checksum procedure).
The NE software checks to make sure that the SW database version is compatible with the
software generic. If not, or if the NE detects existence of an obsolete (i.e. no longer
supported) database, a corrupt or empty database, or a database from another system, the
database is marked as being invalid. No more than one database backup, database restore,
active and standby database synchronization, or software download operation is allowed
at the same time on the NE.
Remote database operations
The NE provides the capability to transfer database files from the local storage area on
the disk to a remote storage area on a RFS and vice-versa. Using this capability, operators
can perform remote database backup and remote database restore.
The NE supports the ability to retrieve information on a backed up database currently
existing on an RFS. Information includes the SID, NE type, and release of the NE on
which the backup took place, and the date and time at which the backup occurred. The
NE supports the ability to back up the active database to a database file on a Remote File
Server and to restore the NE database from a backup database on a Remote File Server.
The file transfer functionality works with any RFS supporting an IP connection, a
standard FTP file server, and also in an environment in which the Secure Shell transport
protocol (SSH), running on top of TCP/IP, yields a secure FTP file transport capability.
Note: The system does not automatically resume a previously started remote file
transfer operation (either direction) that was interrupted by an NE restart or Main EC
protection switch.
Database file identification data
Each database file that is created with the BackupDatabase command maintains the
following data identifiers:
SYSTYPE - System Type on which the database was created.

RLSID <1-20 CHARACTER> - Software Release identifier of the system software
the database was created with.
SID <1-20 CHARACTER SID> - System Identifier, identifies the provisioned system
identification.
NE-NAME - The value of this identifier is the SID.
BACKUP-DATE {YY-MM-DD:{08-99}-{1-12}-{1-31}} - Backup Date
BACKUP-TIME {HH:MM:SS:{0-23}:{0-59}:{0-59}} - Backup Time
....................................................................................................................................................................................................................................
10-3
August 2011
Database management
....................................................................................................................................................................................................................................
Note: the active database, and for RFS database files, the BACKUP-DATE and
BACKUP-TIME values are the date and time, as reported by the NE, when the
backup was actually done.
CRC <8 UPPER CASE HEXADECIMAL CRC CHARACTERS> - 32-bit Cyclic
Redundancy Code calculated over the backed-up data.
Database information records
The active database contains records indicating when the database has been backed up.
The following specifies initial and subsequent values of that data:
Until a database backup is first done, the BACKUP-DATE and BACKUP-TIME

values associated with a database is null.
When a database is backed up, the following records are modified:
the Remote File Server (RFS) IP address
the RFS port number to which the file transfer is to connect

the directory on the RFS to which the database is backed up. This is equivalent to
the path on the RFS, to the directory where the database file resides.
the name of the remote database file

the BACKUP-DATE and BACKUP-TIME.
The NE writes or modifies all of the data specified above before the active Main
EC-resident temporary database copy is made.
The default filename format for each remote backup database file on the RFS is:
NEname_SWgeneric_yyyy-mm-dd_hh-mm-ss.bak
Note: It is possible for the user to override the default filename format, but the .bak
file extension must be used.
Database failure and/or loss of synchronization
The following conditions apply:
A download of a database backup from the RFS (part of the database restore process)
will fail if there is not enough free space on the Active Main ECs flash memory. A
database failure condition-local (DBFL alarm) is raised.
A database backup (to an RFS database file) will fail if a copy of the active database
cannot be created because there is not enough free space on the Main ECs
non-volatile memory. If this occurs, a database failure condition-local (DBFL alarm)
is raised.
Any database failure condition that occurs during a database backup is cleared the
next time that a database backup is attempted.
....................................................................................................................................................................................................................................
10-4
August 2011
Database management
....................................................................................................................................................................................................................................
In a duplex controller environment:

If the active Main EC database fails, the NE effects an automatic switch to the
standby Main EC.
If the standby Main EC controller fails, the standby EC becomes unavailable for
automatic protection, and an appropriate alarm/condition is raised.
A database synchronization failure alarm is raised if the active EC card is unable
to synchronize its database with the standby EC card.
In a simplex controller environment, if the NE database fails, an alarm is raised

indicating the issue with the database.
Note: When switching from active Main EC to standby Main EC, OSC data link
down alarm is raised on adjacent nodes for a few seconds and then the alarms are
cleared.
Note: There is a limit of one software download at a time over OTU1 rate GCC.
Simultaneous remote software downloads should not be performed over OTU1 rate
GCC.
Secure file transfer
The database backup and restore operations support the option of encrypted file transfer,
SFTP, using SSH (see System security features (p. 2-14)). The following applies:
Database backup and restore commands using SFTP will be denied if the Network
Element SSH Key is not initialized.
When the 1830 PSS-36/PSS-32/PSS-16 database server is configured for the SFTP
protocol and the NE receives a backup database or restore database command, the NE
will establish an SSH connection with the external SSH server on the RFS over which
the encrypted file transfer can take place.
The database server protocol parameter is independent of the security mode
parameter. Regardless of the security mode of the NE (encrypted or normal), the file
transfer protocol supports provisioning as SFTP or TFTP.
At the beginning of an encrypted file transfer backup database or restore database
command execution, the command software checks whether the NE has a valid SSH
key, and denies the command if one does not exist for this NE.
....................................................................................................................................................................................................................................
10-5
August 2011
Database backup
....................................................................................................................................................................................................................................
Database backup
Overview
The system provides the capability for the user to backup the NE active database to a
Remote File Server. The process of doing a remote backup can be split into two different
phases: first, create a temporary copy of the active database on the NE; second, send this
database file to its remote storage destination. The following sequence outlines the
general principle for the backup of an NE database on a Remote File Server:
1. An initiator, often a managing system, sends a command to initiate the database
backup.
2. The NE makes a temporary copy of the active database.
3. After the temporary database has been created, the NE sends a message to the RFS
initiating the file transfer.
The following conditions apply to a database backup:
The database is updated after configuration-affecting commands have been processed,

and after any autonomous configuration changes have been performed by the NE, in
such a way as to guarantee that no configuration changes of the database changes are
lost.
Note: The NE does not maintain the current alarm situation of the system in the
database. The actual alarm situation is recovered from the NE at restart time.
Database backup operation occurs with minimal impact to normal service operations
and does not impact service.
Only one database backup, database restore, or software download is allowed on a
system at any given time. Input of a second instance of any of these commands will
be denied if the action of the previous command has not yet completed.
User commands are not rejected due to ongoing backup activity; they are instead
queued and are executed after completion of an in-progress command that is
accessing the database.
Note: This applies primarily during creation of the temporary database on the EC.
Thus new commands are allowed while transfer of a database file to the RFS is
occurring.
A database backup operation will backup the entire database content. The following
items are not part of the database and therefore are not backed up.
event logs
active alarms and conditions
site-specific data
The database backup operation writes database file identification information to
records in the active DB and the backed up database on the Remote File Server.
....................................................................................................................................................................................................................................
10-6
August 2011
Database backup
....................................................................................................................................................................................................................................
The database backup operation includes a data integrity verification of the temporary
database.
The NE accomplishes the generation of database backups in 15 minutes or less.
Database backup failure conditions
If the temporary database cannot be read (meaning that the database cannot be
transported to the RFS) , a database failure condition-local (DBFL alarm) is set
against common equipment.
If the file transfer of the database to the RFS does not succeed, a database failure
condition-transport is set against common equipment.
The NE denies a request to back up the active database when:
a database backup event is currently in progress
a database restore event is currently in progress
an in-service upgrade event is in progress

an Initialize System event is in progress (via an Initialize System request).
Each of the Database Backup Failure condition types is a standing condition declared
against the COM entity. Each such condition is cleared when a Database Backup or
Database Restore is next attempted.
....................................................................................................................................................................................................................................
10-7
August 2011
Database restore
....................................................................................................................................................................................................................................
Database restore
Overview
The system provides the capability for the user to download a previously backed up
database from a Remote File Server and to then have this database automatically
activated on the NE. The process of restoring an NEs working database is twofold - first,
download a backup from a remote location onto a target NE; second, restart the NE with
the downloaded database. The following sequence outlines the general principle for the
restoration of an NE's active database from a Remote File Server:
1. An initiator (often an OS) sends a command (RestoreDatabase) to the NE to initiate
the process of downloading a database from the RFS and then activating it on the NE.
2. The NE requests the download from the RFS and begins storing the downloaded file
as a temporary database on the active Main EC.
3. The NE marks the temporary database as the active database.
4. System software restarts the NE.
The following conditions apply to a database restore:
The NE outputs an autonomous message for each of the following database

restoration occurrences:
Database restoration has completed successfully meaning that the transfer and
data validation of the remote database file has completed successfully.
Database restoration has failed meaning that the transfer and data validation of
the remote database file has failed.
Database restoration has begun meaning that the external FTP session has begun.
The following conditions apply to SID
The NE SID is preserved in a database restoration if the database file being
restored came from the same SID (i.e. the database is being restored to the NE
from which the database was backed up)
If the restored database comes from a different NE, the SID will be changed to the
SID that is in the database being restored.
An NE's SID survives all types of NE restarts.

When the database is restored, site-specific configuration data (e.g. NE network
addresses, routing configuration) are not preserved.
Note: When the NE restarts, all active alarms and conditions are reported.
Database restoration does not interrupt or interfere with traffic on connections that are
not altered by the restoration.
Nativity check
The database restore command checks that the serial number of the User Panel is the
same as that in the database being restored. If not, the database is marked invalid after the
restore operation completion. It is possible to restore to an NE any remote database file
....................................................................................................................................................................................................................................
10-8
August 2011
Database restore
....................................................................................................................................................................................................................................
whose SID is the same as the SID of the NE that has received a database restore request.
In other words, the nativity of the database file to be restored must be that it originated
on the NE that is initiating the restore.
Note: For a User Panel replacement, the database restore operation supports a
forced option, where the restore is allowed despite failed nativity checks (see
Restore database (p. 10-10)).
Database restore failure conditions
Important! On any restart, if the database is not aligned with the SW, or is otherwise
corrupted, the database is declared invalid. It is then the user's responsibility to either
restore a proper database or to clear the database. The NE saves some parameters
(SID, OAMP IP address, etc.) to SEEPROM. In case of a database corruption, the NE
will still be reachable and will have network connectivity. This will allow the user to
attempt to restore a good known database to the NE.
The NE system will deny the Restore Database request for any of the following reasons:
When software release upgrade is in progress (via a Start In-Service Upgrade

request).
When a system restart is in progress (via an Initialize System request).
The database to be restored has a database read error or the CRC does not match the
calculated CRC on the media.
A database restore event is presently in progress.
A database backup event is currently in progress.
The remote database version number is not compatible with the software generic that
is currently on the NE.
....................................................................................................................................................................................................................................
10-9
August 2011
....................................................................................................................................................................................................................................

Note: The information here describes procedures using the WebUI. For procedures
using 1354 RM-PhM or CLI, see the Alcatel-Lucent 1354 RM-PhM Release 8.6
Photonic Manager EMS Reference Guide and Alcatel-Lucent 1830 Photonic Service
Switch (PSS) Release 3.6.0 and 3.6.1 Command Line Interface Guide.
Backup database
...................................................................................................................................................................................................
In the WebUI, select Administration > Database > Backup and Restore.
Result: The database Backup and Restore screen is displayed.
...................................................................................................................................................................................................
Enter Backup/Restore settings (Server IP Address = IP address of the PC in which the

TFTP/SFTP server is running; Directory = the path in the TFTP/SFTP server). Click
Apply, then click Backup.
Note: In encrypted mode (SFTP), User ID and Password must be entered. (See
System security features (p. 2-14) for SFTP details).
Result: A window is displayed indicating that the backup has been initiated.
...................................................................................................................................................................................................
Click OK. Next, click Refresh to display the status of the Backup.
E...................................................................................................................................................................................................
N D O F S T E P S
Restore database
...................................................................................................................................................................................................
In the WebUI, select Administration > Database > Backup and Restore.
Result: The database Backup and Restore screen is displayed.
...................................................................................................................................................................................................
Enter Backup/Restore settings (Server IP Address = IP address of the PC in which the

TFTP/SFTP server is running; Directory = the path in the TFTP/SFTP server; File Name
= the name of the file to be restored from the TFTP/SFTP server). Click Apply, then click
Restore.
Note: A forced restore can be made by clicking Force Restore. This runs the
restore despite the existence of failure conditions. A forced restore causes a bypass
of all checks that the restore operation would run before it actually executes.
....................................................................................................................................................................................................................................
10-10
August 2011
....................................................................................................................................................................................................................................
Note: In encrypted mode (SFTP), User ID and Password must be entered. (See
System security features (p. 2-14) for SFTP details).
Result: A window is displayed indicating that this may be service affecting and that
after the database has been restored, the system will automatically restart.
...................................................................................................................................................................................................
Click OK. Next, click Refresh to display the status of the restore.
Result: When the NE resets, the WebUI will be refreshed and will navigate to the
main screen. Select Administration > Database to see the status of the database
restore.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
10-11
August 2011
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
10-12
August 2011
11
Routine procedures
11
Overview
Purpose
This chapter describes Alcatel-Lucent 1830 PSS routine procedures.

Contents
User preferences
11-2
Syslog properties
11-3
User activity logging
11-4
Date/time setting
11-5
Loopbacks
11-8
Power settings
11-10
Power commissioning
11-14
Software upgrade/downgrade
11-16
...................................................................................................................................................................................................................................
11-1
August 2011
Routine procedures
User preferences
....................................................................................................................................................................................................................................
User preferences
Setting / viewing user preferences
Note: User preferences are stored on the local PC for each user and are remembered
from session to session; they are not stored on the NE.
...................................................................................................................................................................................................
In the WebUI, select Administration > User Preferences.

Result: The User Preferences screen is displayed.
...................................................................................................................................................................................................
Enter user preference parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-2
August 2011
Routine procedures
Syslog properties
....................................................................................................................................................................................................................................
Syslog properties
Setting / viewing syslog properties
...................................................................................................................................................................................................
In the WebUI, select Administration > Syslog > Properties.

Result: The Syslog Administration screen is displayed.
...................................................................................................................................................................................................
Enter syslog administration parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-3
August 2011
Routine procedures
....................................................................................................................................................................................................................................

Setting / viewing CLI user activity logging properties
...................................................................................................................................................................................................
In the WebUI, select Administration > Syslog > CLI Logging.

Result: The CLI Logging screen is displayed.
...................................................................................................................................................................................................
Select CLI logging properties and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
Setting / viewing SNMP user activity logging properties

...................................................................................................................................................................................................
In the WebUI, select Administration > Syslog > SNMP Logging.

Result: The SNMP Logging screen is displayed.
...................................................................................................................................................................................................
Select SNMP logging properties and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-4
August 2011
Routine procedures
Date/time setting
....................................................................................................................................................................................................................................
Date/time setting
Overview
The NE supports the following features:
Providing time of day setting (including both time and date) by user command.
Ability to provide time stamping accurate to within +/- 500 msec. per day.
Synchronize the NE clock from an NTP server.
Support customer provisionable time offset from UTC for all system time displays
and event time stamps.
Network Time Protocol (NTP) synchronization
The NE is capable of synchronizing its time of day via Network Time Protocol (NTP). It
is possible to provision up to three (3) NTP servers and it is also possible to delete an
NTP server. The user can retrieve the attributes and service state of all designated NTP
servers via user command. The following applies:
It is possible to enable or disable NTP synchronization. When NTP protocol is

enabled, the NE internal time of day clock uses the calculated UTC time from the
selected NTP server, as modified by the user-provisioned offset. All messages, event
reports, logs, and events that carry time stamps will use this time of day (NTP UTC
time + provisioned offset).
When NTP protocol is disabled after having been synchronized to an NTP server, the
NE internal clock adopts the last value of the NTP server time as its set time and
continues to calculate time stamps using the provisioned offset.
The NE supports the following time-of-day synchronization modes:
non-synchronized, free-running mode: NTP is not enabled, and the NE is not
synchronized to an NTP server and is instead using its own internal clock as a
source.
synchronized mode: the NE is using the NTP protocol to synchronize to an NTP

server. The NE is polling the NTP server and periodically making corrections to
its internal clock so as to maintain the same clock time as the NTP server.
The current time-of-day synchronization mode is retrievable via user command
NTP server addresses and NTP enable/disable status is able to survive a database
backup and restore.
Note: When configuring NTP servers on an NE network the provisioned NTP server
IP addresses should be that of external NTP servers and not the IP of GNE(s).
Appropriate DCN provisioning must be done such that the external NTP servers are
reachable from all NEs within the network.
....................................................................................................................................................................................................................................
11-5
August 2011
Routine procedures
Date/time setting
....................................................................................................................................................................................................................................
Manual time of day synchronization
The following apply for manual (non-NTP) Time of Day synchronization.
The NE date and time are capable of being modified via user interface command
If NTP synchronization is enabled, attempts to modify date and time are denied.
The system ensures the date/time is set and reported within the valid range supported
by the user commands. The valid date range is from 1-Jan-2005 to 31-Dec-2059.
The NE preserves the correct time and date through a restart/reboot of the processors
where there is no loss of power, and also when a module or device (hard disk) has
been replaced.
The NE internal time of day clock uses the calculated UTC time from the selected
NTP server, when enabled, as modified by the user-provisioned offset. All messages,
event reports, logs, and events that carry time stamps use this time of day.
Note: Time/date changes may cause partial or incomplete PM data, depending on the
magnitude of the time change. Time/date changes will not affect the application of
security measures such as password aging.
Create / view NTP server
Note: Up to 3 NTP servers are supported on the NE.

...................................................................................................................................................................................................
In the WebUI, select Administration > NTP > Servers.

Result: The NTP Servers screen is displayed.
...................................................................................................................................................................................................
To create an NTP server click Create.

Result: The Create NTP Server screen is displayed.
...................................................................................................................................................................................................
Enter NTP server values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
View NTP properties

...................................................................................................................................................................................................
Select Administration > NTP > Properties

Result: The Network Time Protocol Properties screen is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-6
August 2011
Routine procedures
Date/time setting
....................................................................................................................................................................................................................................
Manually setting date and time
Note: The valid range for year is 2008 to 2020. Date and time cannot be modified if
NTP synchronization is enabled.
...................................................................................................................................................................................................
In the WebUI, select Administration > Date and Time.

Result: The Date and Time Administration screen is displayed.
...................................................................................................................................................................................................
Enter date and time values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-7
August 2011
Routine procedures
Loopbacks
....................................................................................................................................................................................................................................
Loopbacks
Overview
Loopbacks are typically used in a process of installation, system maintenance and

troubleshooting. The basic idea is to allow the user to test the circuit or isolate the failure
by connecting the test equipment to the system interface and creating the loopback at
different points in the transmission path. Loopbacks aid in the process of troubleshooting
by isolating segments of the transmission path and associating the addition/removal of a
monitored segment with presence of a failure.
The two basic types of loopbacks (depicted in Figure 11-1, Loopback Types (p. 11-9))
are:
Line (Facility) loopbacks - The received optical external transmission signal on the
target facility is capable of being looped from the port function input back toward the
port function output. It is permissible to loopback the electrical signal of the optical
interfaces as opposed to the optical signal. Each interface of a multiple interface port
function is capable of being looped back independently.
Terminal loopbacks - The electrical transmission signal on an optical interface port
function is capable of being looped from the port function output back toward the port
function input. Port functions include optical interfaces at various rates. The
placement of the terminal loopback on any particular port function is a compromise
between having the loopback be as close as possible to the physical interface and
having the terminal loopback support transparent data flow.
Note: Line terminal loopback release can take several minutes for traffic to recover
(10 minute maximum).
Note: Terminal and facility loopbacks are supported on all OT line and client ports
(not VA ports) with the exception of the 43STA1P client port.
Note: When a line facility loopback is established on an 11STAR1 OT pack, there is a
30 second delay from initiating the loopback to when it comes into effect. The reason
for this delay is because establishing the loopback requires changing the line-side PLL
settings, and it takes about 30 seconds for the PLL to lock after its settings have been
changed. The same 30 second delay applies to removing the line facility loopback.
Note: 11STMM10 line facility loopback terminates OTU2 and ODU2 overhead.
There is a lack of transparency with this type of loopback.
....................................................................................................................................................................................................................................
11-8
August 2011
Routine procedures
Loopbacks
....................................................................................................................................................................................................................................
Figure 11-1 Loopback Types
Display, set, release loopbacks

...................................................................................................................................................................................................
In the WebUI, select the port in the equipment tree and select the Test/Analysis function.
Result: The Port Loopback Control screen is displayed.
...................................................................................................................................................................................................
Provision the attributes to set or release loopbacks and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-9
August 2011
Routine procedures
Power settings
....................................................................................................................................................................................................................................
Power settings
Rebalancing in-service optical power levels
In-service rebalancing of the optical powers is supported on all of the NEs in a network.
A network rebalance may be required if the network is re-engineered, or it may be
performed as a preventive maintenance exercise.
If the network has been re-engineered, the user can reset targets and re-adjust power
levels around the network. When the rebalancing is performed as a preventive
maintenance exercise, the current power targets are used to re-adjust power levels
Only NE lines that are auto power managed can be power balanced using the Ingress
Adjustment or Egress Adjustment functions found in the Power Management tab (see
Power management procedure (p. 11-11)).
Lines that are manually power managed must be manually adjusted by the user and would
include tasks such as modifying the OT or SVAC target output power, OPSA VOA
attenuation, setting the LD gain, and re-setting WT expected power levels (if necessary).
Target Power Offset
The WebUI supports viewing and setting target power offset for the following ports:
A2325A, AHPHG, AHPLG, ALPHG, AM2017B and AM2325B LINE ports

AM2125A, AM2125B, AM2318A and RA2P LINEIN ports (Ingress only)
AM2125A, AM2125B and AM2318A LINEOUT ports (Egress only)
Whether a particular card supports setting target power offset is dependent on its current
topology. The WebUI determines whether a given port supports egress, ingress, both, or
neither by the following:
For A2325A, AHPHG, AHPLG, ALPHG, AM2017B and AM2325B LINE ports:
If the LINE port Opposite Direction Port is set to itself, then both Ingress and
Egress are supported.
If the LINE port Opposite Direction Port is set to another port, then only Egress is
supported.
If the LINE port Opposite Direction Port is unassigned, then neither Ingress nor
Egress are supported.
For AM2125A, AM2125B, AM2318A and RA2P LINEIN ports:
If the LINEIN port Opposite Direction Port is set, then Ingress is supported.
If the LINEIN port Opposite Direction Port is unassigned, then Ingress is not
supported.
....................................................................................................................................................................................................................................
11-10
August 2011
Routine procedures
Power settings
....................................................................................................................................................................................................................................
For AM2125A, AM2125B and AM2318A LINEOUT ports:

If the LINEOUT Opposite Direction Port is set, then Egress is supported.
If the LINEOUT Opposite Direction Port is unassigned, then Egress is not
supported.
The WebUI supports modify and view of target power offset by technology type (see
Technology types (p. 11-11)) for each direction supported (ingress and/or egress).
Power Offset cannot be modified for technology types where OTU Bit Rate and/or
Encoding = {9001 10000}.
Per-channel target power offset
The WebUI supports modify and view of ingress and egress target power attributes per
optical channel. This is supported for the ingress and egress power adjust points. The
following applies:
A card supports modify/view of the ingress target power attributes if the card supports
ingress power adjustment.
Likewise, a card supports modify/view of the egress target power attributes if the card
supports egress power adjustment.
The WebUI does not allow modify/view of the target power attributes if the card is not
present in the shelf (i.e. the card is pre-provisioned). The WebUI displays a table of target
power data per frequency for each direction supported (ingress and/or egress).
Technology types
The WebUI supports create, modify and view of system-wide technology types (OTU Bit
Rate + Encoding).
Note: The WebUI will not allow creation of a technology type that already exists. The
WebUI will not allow modify of OTU Bit Rate Description and Encoding Description
for reserved enum values (1-1000 and 9001-10000). The WebUI will not allow
modify of WTOCM Calibration for reserved enum values (9001-10000).
The WebUI supports deletion of a technology type if it meets the following conditions:
It is not a reserved type. Reserved types have OTU Bit Rate or Encoding = {1-1000,
9001-10000}.
It is not associated with a cross-connect. OTU Bit Rate/Encoding do not match the
AZ/ZA user-settable OTU Bit Rate/Encoding nor the AZ/ZA received OTU Bit
Rate/Encoding on a cross-connect.
Power management procedure

...................................................................................................................................................................................................
Select the appropriate port from the equipment tree and click the Power Management
tab.
....................................................................................................................................................................................................................................
11-11
August 2011
Routine procedures
Power settings
....................................................................................................................................................................................................................................
Result: The Port Power Management screen is displayed.

...................................................................................................................................................................................................
Enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
Power adjustment procedure

...................................................................................................................................................................................................
The WebUI supports egress and/or ingress power adjustments for A2325A, AHPHG,
AHPLG, ALPHG, AM2017B, AM2325B, AM2125A, AM2125B, AM2318A, and RA2P
cards. Select the appropriate card from the equipment tree and click the Power
Adjustment tab.
Result: The Egress Power Adjustment or Ingress Power Adjustment screen is
displayed.
...................................................................................................................................................................................................
Select Perform Power Adjustment on this port: and click Submit.

Result: The Power Adjust Status: and Power Adjust Result: are displayed and
automatically updated with current status.

Note: Whether a particular card supports power adjustment is dependent on its
current topology. The WebUI will determine whether a given card supports an
egress power adjustment, ingress power adjustment, both or neither according to
the following:
For A2325A, AHPHG, AHPLG, ALPHG, AM2017B and AM2325B:
If the LINE port Opposite Direction Port is set to itself, then both Ingress and
Egress adjust are supported.
If the LINE port Opposite Direction Port is set to another port, then only Egress
adjust is supported.
If the LINE port Opposite Direction Port is unassigned, then neither Ingress nor
Egress adjust is supported.
For AM2125A/AM2125B, AM2318A and RA2P:
If the LINEIN port Opposite Direction Port is set, then Ingress adjust is supported.
If the LINEIN port Opposite Direction Port is unassigned, then Ingress adjust is not
supported.
If the LINEOUT Opposite Direction Port is set, then Egress adjust is supported.
If the LINEOUT Opposite Direction Port is unassigned, then Egress adjust is not
supported.
....................................................................................................................................................................................................................................
11-12
August 2011
Routine procedures
Power settings
....................................................................................................................................................................................................................................
Note: For power management alarm clearing procedures, see the Alcatel-Lucent 1830
Photonic Service Switch 36/32/16 (PSS-36/32/16) Release 3.6.0 and 3.6.1 Maintenance
and Trouble-Clearing Guide.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-13
August 2011
Routine procedures
Power commissioning
....................................................................................................................................................................................................................................
Power commissioning
Overview
To facilitate NE commissioning, the WebUI provides a screen with port power attributes
for all LD and CWR8 cards in the NE. The intent is for the user to input data from the
EPT Commissioning report directly in this screen and then initiate the necessary power
adjustments.
View / modify power commissioning values
Note: On the Power Commissioning screen, the WebUI supports modify and view of
up to 16 A2325A, AHPHG, AHPLG, ALPFGT, ALPHG, AM2017B, AM2125A
AM2125B, AM2318A, AM2325B, MESH4, OSCT, and RA2P cards, and up to 8
CWR8 or CWR8-88 cards on the NE.
...................................................................................................................................................................................................
In the WebUI, select Administration > Power Commissioning.

Result: The Power Commissioning window is displayed.
...................................................................................................................................................................................................
To modify power attributes, enter values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
Power adjustment
Note: For each LD, the WebUI supports Egress and Ingress power adjustment for
both Ring (ASE Adjust) and Linear (Forced X-Conn Reqd) topologies.
...................................................................................................................................................................................................
In the WebUI, select Administration > Power Commissioning.

Result: The Power Commissioning window is displayed.
...................................................................................................................................................................................................
Click Power Adjust.

Result: The Power Adjustment window is displayed.
...................................................................................................................................................................................................
Enter attribute values and click Submit.
....................................................................................................................................................................................................................................
11-14
August 2011
Routine procedures
Power commissioning
....................................................................................................................................................................................................................................
Note: If the power adjustment fails, check the OT line admin state and if it is down,
change it to up and rerun the adjustment.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-15
August 2011
Routine procedures
....................................................................................................................................................................................................................................
Overview
The WebUI supports the steps of an upgrade to a later release (load, activate) and any
steps needed during installation (commit), or a back out or downgrade from a newer
release.
The following actions can be performed via the WebUI with respect to a software
upgrade:
Audit
Download
Activate
Commit
Revert
Note: If software upgrade procedure is aborted, the user must wait a few minutes
before reattempting to load/audit. Otherwise a failure may occur.
Note: While performing a software release upgrade from Release OLD to Release
NEW, the Revert action may be used to return to the OLD release and database, as it
was before the software release upgrade started. After the NEW release is committed,
the Revert command has no affect and a "downgrade" procedure must be used to back
down to the OLD release.
Software upgrade procedure

...................................................................................................................................................................................................
In the WebUI, select Administration > Software > FTP Server. Enter the FTP Server
settings.
Note: PM and log (event log, security log, etc.) information will be lost as a result of
the system restart that occurs during software release upgrade. This information
should be retrieved if you would like to retain it for your records.
...................................................................................................................................................................................................
In the WebUI, select Administration > Software > Upgrade.

Result: The Software Upgrade window is displayed.
...................................................................................................................................................................................................
Enter the folder name containing the NE software in the Release Directory. Select Audit
for the Action Type and click Apply.
Note: If this is a software downgrade, check the Force Upgrade box. This field can
only be chosen after Audit has been selected for the Action Type.
....................................................................................................................................................................................................................................
11-16
August 2011
Routine procedures
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select Download for the Action Type and click Apply.

...................................................................................................................................................................................................
Select Activate for the Action Type and click Apply.

Note: When Activate is requested as part of the software upgrade process, the WebUI
displays a warning message to the user, indicating that activating the software will
cause the NE to reboot. As a result, the WebUI will lose connectivity with the NE and
the user must login after activate is complete. The user will be allowed to continue
with the Activate request or cancel.
Result: The NE will reboot and the WebUI connection will drop.
...................................................................................................................................................................................................
Wait about 2 minutes after the fan speed drops back down to normal speed and log back
into the NE.
Note: 1830 PSS-36/PSS-32/PSS-16 supports the ability to control fan speed via the
WebUI. When the Fan module is selected in the WebUI equipment tree, the fan speed
can be set to the following values:
normal - automatic speed control

maximum - constant full speed (100% RPMs)
Note: The WebUI does not reconnect automatically.

...................................................................................................................................................................................................
In the WebUI, select Administration > Software > Upgrade.

Result: The Software Upgrade window is displayed.
...................................................................................................................................................................................................
Verify the Software Status now indicates Completed, and verify the Result is
Success. Check the alarms on the system and make sure traffic is still unaffected.
Note: This is the last point where a software back out can be performed. After this a
downgrade procedure is required.
...................................................................................................................................................................................................
Select Commit for the Action Type and click Apply.

Important! A one step software back out can not be performed after the software is
committed. After commit is completed, the software downgrade is supported via a full
downgrade procedure (upgrade to a lower release).
....................................................................................................................................................................................................................................
11-17
August 2011
Routine procedures
....................................................................................................................................................................................................................................
Result: The software release upgrade is now complete. A database backup should be
performed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-18
August 2011
Glossary
...................................................................................................................................................................................................................................
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.
AHPLG
High Power Low 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-1) for definition.

AINS
Automatic in-service.
AIS
See alarm indication signal (p. GL-1) for definition.

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.
....................................................................................................................................................................................................................................
GL-1
August 2011
Glossary
....................................................................................................................................................................................................................................
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 (APR) (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.

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).
....................................................................................................................................................................................................................................
GL-2
August 2011
Glossary
....................................................................................................................................................................................................................................
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-2) 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).
...................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
GL-3
August 2011
Glossary
....................................................................................................................................................................................................................................
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-4) for definition.

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

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

BDI
See backward defect indication (p. GL-3) 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.

BOF
See band optical filter (p. GL-3) 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.
....................................................................................................................................................................................................................................
GL-4
August 2011
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
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-6) 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.

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).
....................................................................................................................................................................................................................................
GL-5
August 2011
Glossary
....................................................................................................................................................................................................................................
COF
See channel optical filter (p. GL-5) for definition.

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 EMS). 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.
CPE
See customer premises equipment (p. GL-6) 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-5) for definition.

....................................................................................................................................................................................................................................
GL-6
August 2011
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
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-7) for definition.

DHCP
See dynamic host configuration protocol (p. GL-7) 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)
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.
....................................................................................................................................................................................................................................
GL-7
August 2011
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
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-8) 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
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.

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

EMS
See Element Management System (p. GL-8) 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-8) for definition.

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

....................................................................................................................................................................................................................................
GL-9
August 2011
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
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-10) for definition.

FCC
See Federal Communications Commission (p. GL-10) 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-10) for definition.

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

FEC
See forward error correction (p. GL-11) 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
....................................................................................................................................................................................................................................
GL-10
August 2011
Glossary
....................................................................................................................................................................................................................................
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)
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.
....................................................................................................................................................................................................................................
GL-11
August 2011
Glossary
....................................................................................................................................................................................................................................
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-3) 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-12) 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)
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)
....................................................................................................................................................................................................................................
GL-12
August 2011
Glossary
....................................................................................................................................................................................................................................
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-12) 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-23) 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.
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
....................................................................................................................................................................................................................................
GL-13
August 2011
Glossary
....................................................................................................................................................................................................................................
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-13) for definition.

IPsec (Internet Protocol Security)
See Internet protocol security (p. GL-13) 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-13) 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.
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-14) for definition.

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

....................................................................................................................................................................................................................................
GL-14
August 2011
Glossary
....................................................................................................................................................................................................................................
LC
See Lucent connector (p. GL-15) 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-15) 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-15) for definition.

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.
....................................................................................................................................................................................................................................
GL-15
August 2011
Glossary
....................................................................................................................................................................................................................................
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-16) for definition.

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.

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

mean time to repair (MTTR)
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).
....................................................................................................................................................................................................................................
GL-16
August 2011
Glossary
....................................................................................................................................................................................................................................
MSA
See mid-stage access amplifier (p. GL-16) 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.

muxponder
A networking device that multiplexes and transponds GbE signals.

...................................................................................................................................................................................................................................
NE
See network element (p. GL-17) for definition.

NEBS
See Network Equipment Building System requirements (p. GL-17) 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
....................................................................................................................................................................................................................................
GL-17
August 2011
Glossary
....................................................................................................................................................................................................................................
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-17) for definition.

node
A node (or network element) is a set of one or more 1830 PSS-36/PSS-32/PSS-16 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)
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-19) for definition.

OAMP
Operations, Administration, Maintenance, and Provisioning.

OC-n
See optical carrier level-n (p. GL-19) 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-19) for definition.

....................................................................................................................................................................................................................................
GL-18
August 2011
Glossary
....................................................................................................................................................................................................................................
ODU
See optical demultiplexer (p. GL-19) 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-20) 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.
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.

....................................................................................................................................................................................................................................
GL-19
August 2011
Glossary
....................................................................................................................................................................................................................................
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 (OSC)
A designated optical channel used to carry communications related to maintenance and

operational functions of the network rather than customer traffic.
The OSC 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-28) 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.
OSC
See optical supervisory channel (p. GL-20) for definition.

....................................................................................................................................................................................................................................
GL-20
August 2011
Glossary
....................................................................................................................................................................................................................................
OSHA
See Occupational Safety and Health Administration) (p. GL-18) 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-21) for definition.

OSS
See Operations Support System (p. GL-19) for definition.

OT
See optical transponder (p. GL-20) for definition.

OTN
See optical transport network (p. GL-20) for definition.

out of frame (OOF)
A state in which the frame alignment sequence of an SDH/SONET frame has not been found for
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-22) for definition.

performance monitoring (PM)
Measures the quality of service and identifies any degrading or marginally operating systems
(before an alarm would be generated).
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 protection switch (PPS)
By provisioning of PPS cards (or optical splitters), automatic protection switch (APS) are
....................................................................................................................................................................................................................................
GL-21
August 2011
Glossary
....................................................................................................................................................................................................................................
automatically created.
physical coding sublayer (PCS)
PCS layer monitoring used for Ethernet/FC ports.

PM
See performance monitoring (p. GL-21) for definition.

PMD
See polarization mode dispersion (p. GL-22) 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
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-21) 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-21) for definition.

...................................................................................................................................................................................................................................
QoS
See quality of service (p. GL-22) for definition.

quality of service (QoS)
A set of performance parameters that characterize the transmission quality over a given virtual
connection.
....................................................................................................................................................................................................................................
GL-22
August 2011
Glossary
....................................................................................................................................................................................................................................
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 1830
PSS-36/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.
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.
....................................................................................................................................................................................................................................
GL-23
August 2011
Glossary
....................................................................................................................................................................................................................................
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-23) for definition.

RIP
See routing information protocol (p. GL-24) for definition.

RJ
See random jitter (p. GL-23) for definition.

RMON
See remote network monitoring (p. GL-23) for definition.

ROADM
See reconfigurable optical add/drop multiplexer (p. GL-23) 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-27) for definition.

SC
See shelf controller (p. GL-25) 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-26) for definition.

SDH
See Synchronous Digital Hierarchy (p. GL-28) for definition.

secure shell (SSH)
A secure method of transmitting data.

....................................................................................................................................................................................................................................
GL-24
August 2011
Glossary
....................................................................................................................................................................................................................................
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 1830 PSS-36/PSS-32/PSS-16 system, services can be offered directly to end customers
or be used internally to a network as transport infrastructure.
SFC
See static filter, CWDM (p. GL-27) for definition.

SFD44
See static filter, DWDM (p. GL-27) for definition.

SFP
See small form-factor pluggable module (p. GL-26) 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 1830 PSS-36/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 1830 PSS-36/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)
....................................................................................................................................................................................................................................
GL-25
August 2011
Glossary
....................................................................................................................................................................................................................................
SNMP is the protocol used to communicate between the 1830 PSS-36/PSS-32/PSS-16 nodes and
the NMS. The SNMP traffic is carried over the 1830 PSS-36/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.
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-25) for definition.

software control of transmission (SCOT)
System software that controls the settings of EDFA gain targets, VOAs, pack power control
targets, and updates Wavelength Tracker expected power value and power deviation thresholds.
software generic (SW generic)
The whole software and (static) data associated with a particular NE release.
SONET
See Synchronous Optical Network (p. GL-28) for definition.
....................................................................................................................................................................................................................................
GL-26
August 2011
Glossary
....................................................................................................................................................................................................................................
SONET wavelength service
The SONET wavelength service provides transport of SONET signals through the 1830
PSS-36/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.

SRG
See shared risk group (p. GL-25) for definition.

SSH
See secure shell (p. GL-24) for definition.

SSMF
See standard single-mode fiber (p. GL-27) for definition.

ST
See straight-tip connector (p. GL-27) 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 (SFD44)
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-25) for definition.

straight-tip connector (ST)
Fiber optic connector that uses a bayonet-style coupling rather than a screw-on coupling.
....................................................................................................................................................................................................................................
GL-27
August 2011
Glossary
....................................................................................................................................................................................................................................
STS, STS-n
See synchronous transport signal-n (p. GL-28) for definition.

Sub-Network Connection Protocol (SNCP)
An SDH version of UPSR. See SDH and UPSR.

SW generic
See software generic (p. GL-26) 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
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-29) 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
....................................................................................................................................................................................................................................
GL-28
August 2011
Glossary
....................................................................................................................................................................................................................................
various operating systems. Some examples are FTP, SMTP, and SNMP.
TDM
See time-division multiplexing (p. GL-29) 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
generate an alarm but is available on demand through the CIT.
TID
See target identifier (p. GL-28) 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.
....................................................................................................................................................................................................................................
GL-29
August 2011
Glossary
....................................................................................................................................................................................................................................
traps (SNMP)
SNMP traps are unacknowledged events sent from an agent to a manager. In a 1830
PSS-36/PSS-32/PSS-16 network, the agent is the node and the manager is EMS.
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-30) for definition.

UL
See Underwriters Laboratories (p. GL-30) 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-30) 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.
....................................................................................................................................................................................................................................
GL-30
August 2011
Glossary
....................................................................................................................................................................................................................................
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.
VCAT
See virtual concatenation (p. GL-31) 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-31) for definition.

VTS
See virtual time-slot (p. GL-31) 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-36/PSS-32/PSS-16network is uniquely identified by a pair of wave keys.
....................................................................................................................................................................................................................................
GL-31
August 2011
Glossary
....................................................................................................................................................................................................................................
waveguide
A material medium that confines and guides a propagating electromagnetic wave.

waveguide coupler
A coupler that transfers light between planar waveguides.

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 1830 PSS-36/PSS-32/PSS-16

which allows for the tracking of wavelengths through the 1830 PSS-36/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-31) 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-32) 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
....................................................................................................................................................................................................................................
GL-32
August 2011
Glossary
....................................................................................................................................................................................................................................
Reach (VSR) to Long Reach (LR) can also be supported.

...................................................................................................................................................................................................................................
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-33
August 2011
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
GL-34
August 2011
Index
A audience
documentation, xi
safety, 1-4
warning labels, 1-9
.............................................................
.............................................................
B barred-hand symbol, 1-13
N Node Manager
.............................................................
C conventions
documentation, xi, xii
NE Equipment Tree, 3-19

.............................................................
O optical transponder
.............................................................
112SCA1 OT, 4-40
D danger, potential sources of, 1-3
112SCX10 OT, 4-41
documentation
.............................................................
audience, xi
P potential sources of danger, 1-3
conventions, xi, xii
.............................................................
.............................................................
E electrostatic discharge, 1-3, 1-11
ESD, 1-11
S safety instructions
electrostatic discharge, 1-11

general notes, 1-3
.............................................................
important, 1-13
G ground strap, ESD, 1-11
laser, 1-4, 1-8
.............................................................
special, 1-3
information
new with this issue, xii
safety precautions (enclosed

systems), 1-8
.............................................................
.............................................................
W warning labels, laser, 1-9
L lasers
classes, 1-6
eye damage, 1-6
....................................................................................................................................................................................................................................
IN-1
August 2011
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
IN-2
August 2011

User Provisioning Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

User Provisioning Guide

Uploaded by

Copyright:

Available Formats

Title page

Interference Information: Part 15 of FCC Rules

Document conventions .............................................................................................................................................................. xii

Document support ...................................................................................................................................................................... xiii

Packaging collection and recovery requirements

Safety information ....................................................................................................................................................................... xv

Electrostatic discharge .......................................................................................................................................................... 1-11

Procedures to configure user accounts

System security features

Log procedures ........................................................................................................................................................................ 2-21

RADIUS server procedures ................................................................................................................................................ 2-27

Data communication setup

Communications network ...................................................................................................................................................... 3-7

Connection release ................................................................................................................................................................. 3-17

WebUI startup procedures ................................................................................................................................................... 3-20

Slot/card provisioning procedures .................................................................................................................................... 4-46

Alarm management procedures ........................................................................................................................................... 5-6

Performance monitoring procedures .................................................................................................................................. 6-8

Connections procedures .......................................................................................................................................................... 7-6

Protection procedures .............................................................................................................................................................. 8-8

Wave keys procedures ............................................................................................................................................................. 9-6

Database backup and restore

Database management .......................................................................................................................................................... 10-1

User preferences ...................................................................................................................................................................... 11-2

User activity logging ............................................................................................................................................................. 11-4

Software upgrade/downgrade .......................................................................................................................................... 11-16

User privilege levels

Ports that support ACL filtering ......................................................................................................................... 2-19

Communications Network Sizing ........................................................................................................................ 3-8

1830 PSS-36 Circuit Pack Slot Allocation ..................................................................................................... 4-11

1830 PSS-32 Circuit Pack Slot Allocation

1830 PSS-16 Circuit Pack Slot Allocation

1830 PSS Shelf Combinations

Cards and Ports that Support PM Data

Laser warning labels

Static control wrist strap

ESD warning label (barred-hand symbol)

Dual GNE configurations ..................................................................................................................................... 3-11

Equipment tree hierarchy

11STMM10 OT signal processing from client port to DWDM line port

Performance monitoring points in an 1830 PSS NE

Analog parameter TCA

About this document

Chapter 2, Security administration

Chapter 3, Data communication setup

Chapter 5, Alarm management

Chapter 6, Performance monitoring

Chapter 9, Wavelength Tracker

Chapter 10, Database backup and restore

Chapter 11, Routine procedures

About this document

The following typographical conventions are used throughout this document:

Bold is used to identify WebUI menu selections and button selections.

Italic is used to identify NE messages

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16

Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 3.6.0

Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 3.6.0

Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 3.6.0

Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 3.6.0

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16