User Provisioning Guide R1.0

Proprietary Use pursuant to Company instruction
Alcatel-Lucent 1830
PHOTONIC SERVICE SWITCH 32 (PSS-32) | Release 1.x.x
USER PROVISIONING GUIDE
Alcatel-Lucent Internal
PN 8DG59474 BAAA
ISSUE 2
APRIL 2009
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 2009 Alcatel-Lucent. All rights reserved.
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by
anyone outside Alcatel-Lucent without its written authorization.
Not to be used or disclosed except in accordance with applicable agreements.
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
............................................................................................................................................................................................
Audience
.........................................................................................................................................................................................
Document conventions
xii
...................................................................................................................................................................
xii
Document support
......................................................................................................................................................................
xii
Technical support
.......................................................................................................................................................................
xii
How to order
..............................................................................................................................................................................
Packaging collection and recovery requirements
xiii
........................................................................................................
xiii
.....................................................................................................................
xiv
....................................................................................................................................................................
xiv
.......................................................................................................................................................................
xiv
......................................................................................................................................................................................
1-1
Recycling/Take-Back/Disposal of Product
Safety information
How to comment
Safety
Overview
Structure of safety statements
..............................................................................................................................................
1-1
..........................................................................................................................................................
1-3
.................................................................................................................................................................................
1-4
General notes on safety

Laser safety
Electrostatic discharge
..........................................................................................................................................................
Save these safety instructions

2
xi
.............................................................................................................................................................
Related information
xi
...........................................................................................................................................
1-11
1-13
Security administration
Overview
......................................................................................................................................................................................
...............................................................................................................................................
2-2
....................................................................................................................................................
2-5
User accounts and privileges

Configuring user accounts
2-1
...................................................................................................................................................................................................................................
PN 8DG59474 BAAA
iii
Issue 2 April 2009
Contents
....................................................................................................................................................................................................................................
Procedures to configure user accounts

Login sessions
.........................................................................................................................................................................
System security features

Authentication
2-10
2-11
..........................................................................................................................................................................
2-13
..................................................................................................................................................................
2-15
Data communication set-up

Overview
......................................................................................................................................................................................
User interfaces
...........................................................................................................................................................................
Communications network
......................................................................................................................................................
Gateway NE (GNE) management
......................................................................................................................................
Data communication set-up procedures
3-2
3-6
3-7
3-10
...................................................................................................................................................
3-12
.................................................................................................................................................................
3-12
......................................................................................................................................................................................
3-13
Connection release
CIT port
3-1
........................................................................................................................
Connection establishment
Using the WebUI
....................................................................................................................................................................
WebUI start-up procedures

4
2-9
......................................................................................................................................................
SNMP procedures
3
...........................................................................................................................
.................................................................................................................................................
3-13
3-15
Equipment provisioning
Overview
......................................................................................................................................................................................
Introduction
.................................................................................................................................................................................
Provisioning system (NE) parameters

Equipment management
Shelf provisioning
4-2
..............................................................................................................................
4-3
.........................................................................................................................................................
4-4
..................................................................................................................................................................
4-14
...........................................................................................................................................
4-18
...........................................................................................................................................................
4-19
Shelf provisioning procedures

Slot/card provisioning
4-1
...................................................................................................................................
4-23
.....................................................................................................................................................
4-27
Slot/card provisioning procedures

Port/facility provisioning
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
iv
Contents
....................................................................................................................................................................................................................................
Port provisioning procedures

5
.............................................................................................................................................
4-52
Alarm management
Overview
......................................................................................................................................................................................
5-1
Description ................................................................................................................................................................................... 5-1

Alarm management procedures
6
...........................................................................................................................................
5-5
......................................................................................................................................................................................
6-1
Performance monitoring
Overview
Description ................................................................................................................................................................................... 6-1

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

Connections procedures
8
.........................................................................................................................................................
7-4
......................................................................................................................................................................................
8-1
Protection
Overview
Description ................................................................................................................................................................................... 8-1

Protection procedures
9
..............................................................................................................................................................
8-6
Wavelength Tracker
Overview
......................................................................................................................................................................................
9-1
Description ................................................................................................................................................................................... 9-1

Wave keys procedures
10
............................................................................................................................................................
9-4
Database backup and restore

Overview
....................................................................................................................................................................................
10-1
..........................................................................................................................................................
10-1
Database backup
.....................................................................................................................................................................
10-5
Database restore
......................................................................................................................................................................
10-7
Database management
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
v
Issue 2 April 2009
Contents
....................................................................................................................................................................................................................................
Database backup/restore procedures

11
...............................................................................................................................
10-9
....................................................................................................................................................................................
11-1
Routine procedures
Overview
User preferences
......................................................................................................................................................................
11-2
Syslog properties
....................................................................................................................................................................
11-3
.............................................................................................................................................................
11-4
.....................................................................................................................................................................
11-5
..................................................................................................................................................................................
11-8
User activity logging

Date/time setting
Loopbacks
Power settings
.......................................................................................................................................................................
Software upgrade (downgrade)
.......................................................................................................................................
11-10
11-11
Glossary
Index
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
vi
List of tables
2-1
User privilege levels
3-1
Communications Network Sizing
4-1
1830 PSS Circuit Pack Slot Allocation
...........................................................................................................
4-8
6-1
Cards and Ports that Support PM Data
...........................................................................................................
6-8
................................................................................................................................................
......................................................................................................................
2-3
3-6
...................................................................................................................................................................................................................................
PN 8DG59474 BAAA
vii
Issue 2 April 2009
List of figures
1-1
Laser warning labels
1-2
Static control wrist strap
1-3
ESD warning label (barred-hand symbol)
3-1
Dual GNE configurations
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-10
1-12
1-13
......................................................................................................................................
.....................................
3-9
4-20
.................................................................................
6-2
..........................................................................................................................................
6-5
......................................................................................................................................................
11-9
...................................................................................................................................................................................................................................
PN 8DG59474 BAAA
ix
Issue 2 April 2009
About this document

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

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 1830 PSS documentation
library:
administrators
operators
maintenance personnel
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
1830 PSS product documentation are intended for use by trained and qualified
personnel.
...................................................................................................................................................................................................................................
PN 8DG59474 BAAA
xi
Issue 2 April 2009
About this document

....................................................................................................................................................................................................................................
Document conventions
The following typographical conventions are used throughout this document:
Italic is used to identify NE messages
Computer voice is used to identify system message text displayed by the WebUI
Bold is used to identify WebUI menu selections and button selections.
Related information
The 1830 PSS-32 User Provisioning Guide is part of a set of documents that support
the 1830 PSS System. The following items are available:
Document Number
Document Title
8DG59474 AAAA
Alcatel-Lucent 1830 PSS-32 Product Information and

Planning Guide
8DG59474 EAAA
Alcatel-Lucent 1830 PSS-32 Maintenance and

Trouble-Clearing Guide
8DG59474 DAAA
Alcatel-Lucent 1830 PSS-32 CLI Command Guide
8DG59474 CAAA
Alcatel-Lucent 1830 PSS-32 TL1 Command Guide
8DG59474 HAAA
Alcatel-Lucent 1830 PSS-32 Safety Guide
8DG59474 GAAA
Alcatel-Lucent 1830 PSS Engineering and Planning Tool

User Guide
8DG39505 MAAA
Alcatel-Lucent 1354 RM-PhM Release 6.1 Photonic

Manager Provisioning Guide
8DG59474 MAAA
Alcatel-Lucent 1830 PSS-1 GBE Edge Device User Guide
8DG59474 KAAA
Alcatel-Lucent 1830 PSS-32 Installation and System Turn-up

Guide
8DG59475 AAAA
Alcatel-Lucent 1830 PSS Documentation 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
For technical support, contact your local customer support team. Reach them via the
web at http://alcatel-lucent.com/support at or the telephone number listed under the
Technical Assistance Center menu at http://www.alcatel-lucent.com/contact.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
xii
About this document

....................................................................................................................................................................................................................................
How to order
To order Alcatel-Lucent documents and courses, use the following websites, or the
e-mail, phone, and fax contacts linked from Contact Us on the following sites:
Documentation:
https://support.lucent.com
Training:
http://training.alcatel-lucent.com/Saba/Web/Main
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
xiii
Issue 2 April 2009
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 comment on this document, go to the Online Comment Form (http://www.

lucent-info.com/comments/enus/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
xiv
About this document

....................................................................................................................................................................................................................................
To order Alcatel-Lucent documents, contact your local sales representative or use

Online Customer Support (OLCS) (https://support.lucent.com).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
xv
Issue 2 April 2009
Safety
1
Overview
Purpose
This chapter provides important safety instructions for 1830 Photonic Service Switch
32 (PSS-32) .
Contents
1-1
1-3
Laser safety
1-4
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:
...................................................................................................................................................................................................................................
PN 8DG59474 BAAA
1-1
Issue 2 April 2009
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
1-2
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
1-3
Issue 2 April 2009
Safety
....................................................................................................................................................................................................................................
Expert and authorized users are required to operate the unit/system.

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
1830 PSS complies with the following laser safety regulations and standards:
International Electrotechnical Commission (IEC) 60825-2: 2004 rules classify 1830

PSS as a Class 1M laser product
International Electrotechnical Commission (IEC) 60825-2: 2004 rules classify 1830

PSS as a Class 1 laser product
Food and Drug Administrations Center for Devices and Radiological Health
(FDA/CDRH) 21 CFR 1040.10 and 1040.11 rules classify 1830 PSS as a Class IIIb
laser product
(FDA/CDRH) 21 CFR 1040.10 and 1040.11 rules classify 1830 PSS as a Class I
laser product
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
1-4
Safety
Laser safety
....................................................................................................................................................................................................................................
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 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
1-5
Issue 2 April 2009
Safety
Laser safety
....................................................................................................................................................................................................................................
Classification of lasers
Manufacturers of lasers and laser products in the United States are regulated by the
(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.
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 and EDFA 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
1-6
Safety
Laser safety
....................................................................................................................................................................................................................................
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.
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
1-7
Issue 2 April 2009
Safety
Laser safety
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
1-8
Safety
Laser safety
....................................................................................................................................................................................................................................
Laser warning labels
The following figure shows the different types of laser warning labels:
HAZRD
Figure 1-1 Laser warning labels (1 of 2)

1
HAZRD
CLASS 1 LASER
LEV
PRODUCT
1M
HAZARD
LEVEL
1M
HAZRD
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
1-9
Issue 2 April 2009
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
1-10
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
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
1-11
Issue 2 April 2009
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 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
1-12
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 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
6. Install only equipment identified in the Alcatel-Lucent Installation and System
Turn-up Guide. Use of other equipment may result in improper connection of
circuitry leading to fire or injury to persons.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
1-13
Issue 2 April 2009
Safety
....................................................................................................................................................................................................................................
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 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.
More information about laser safety can be found in the Alcatel-Lucent Installation
and System Turn-up Guide.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
1-14
Safety
....................................................................................................................................................................................................................................
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.
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
1-15
Issue 2 April 2009
Safety
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
1-16
2
Overview
Purpose
This chapter provides information on security administration procedures for the 1830
PSS system. The security functions determine NE access, command execution, and
administrative control for the 1830 PSS.
Contents
2-2
2-5
2-9
Login sessions
2-10
2-11
Authentication
2-13
SNMP procedures
2-15
...................................................................................................................................................................................................................................
PN 8DG59474 BAAA
2-1
Issue 2 April 2009
....................................................................................................................................................................................................................................

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 CLI Command Guide and/or
1830 PSS-32 TL1 Command Guide including the user levels that are able to access and
execute each specific command (see System access control (p. 2-12)).
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 1830 PSS is delivered with two default users as part of the factory
sofware load: one Admin user (with administration privelege) and one Service
user (with service privelege).
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/managing user profiles. The NE does not allow deletion
of the default users.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
2-2
....................................................................................................................................................................................................................................
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
User privilege levels
Level
Privileges and use
Observer
Observer level restrictions and privileges are as follows:
An Observer user cannot initialize the database during

NE configuration.
An Observer user cannot access any Administrative

functions. This includes configuring: database
backup/restore, date/time, IP routes and OSPF areas,
NTP, Users, SNMP, software upgrade, Syslog, user
activity logging.
An Observer can view and modify user preferences.
An Observer user can view alarms and conditions, but

cannot access the functions under the Fault and
Test/Analysis buttons. These include: alarm
configuration, test LED, and loopback.
An Observer user cannot select Alarm Cutoff on the

alarm display.
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 the NE Physical
Topology, but cannot create or delete a connection
An Observer can view the NE 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. If an Observer user tries
to submit such a request, the WebUI will display a
message indicating that the user does not have
permission to perform the function.
There are no restrictions for the Report menu items.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
2-3
Issue 2 April 2009
....................................................................................................................................................................................................................................
Table 2-1
User privilege levels (continued)
Level
Privileges and use
Provisioner
The Provisioner has all the Observer privileges plus the

following:
configure IO cards, ports, interfaces and circuits
run test procedures on any cards that do not contribute

to system-wide outage (e.g. COLD boot of all packs)
This user cannot provision system-wide security access, (e.g.

user profile, add or delete user account), cannot perform a
system reboot, and cannot modify OPSA A and B port
switching attributes. A Provisioner user cannot access any
Administrative functions. This includes configuring:
database backup/restore, date/time, IP routes and OSPF
areas, NTP, Users, SNMP, software upgrade, Syslog, user
activity logging.
A Provisioner can view and modify user preferences.
Admin
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
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
2-4
....................................................................................................................................................................................................................................
Table 2-1
User privilege levels (continued)
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/manage user profiles), plus the
ability to utilize the debugging and software development
tools. The following applies:
a maximum of one Service user per NE, created by

default, as part of the SW load. (There is no mechanism
to create another Service user profile or to delete the
Service user profile). Only the Service user can change
his/her password

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 NEs 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), and _

(underscore).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
2-5
Issue 2 April 2009
....................................................................................................................................................................................................................................
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.
Password identifier (PID)
A PID is a case sensitive string of 6 to 10 alphabetic [a-z, A-Z], numeric [0-9], or

special characters. A valid password must contain at least 1 alphabetic, 1 numeric, and
1 special character. The following special characters are accepted as valid: % (percent
sign), + (plus sign), # (pound sign), and _ (underscore). The first character of the PID
can be any alphabetic, numeric, or valid special character.
The following conditions apply to PIDs:
The PID cannot be the same as the associated UID, nor can it be the reverse of the
associated UID.
The NE will not prevent a user from choosing an already existing password (more
than one user can have the same password).
Password administration
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 NEs 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
2-6
....................................................................................................................................................................................................................................
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
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.
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 modify a users security level. It is not
possible to modify the UID or user security level of factory default users.
Modifications to user specific provisioned values are not allowed for a user that is
currently logged on.
A user with security administration privileges can retrieve any or all user profile
entries.
Only those parameters 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
2-7
Issue 2 April 2009
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
2-8
....................................................................................................................................................................................................................................

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-13)).
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-5)) and click Apply.
E...................................................................................................................................................................................................
ND OF STEPS
Create a user
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Create.
Result: Create User screen is displayed.
...................................................................................................................................................................................................
Enter appropriate information (see Configuring user accounts (p. 2-5)) and click
Apply.
E...................................................................................................................................................................................................
ND OF STEPS
Delete a user
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
2-9
Issue 2 April 2009
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the desired user and click Delete.

END OF STEPS
...................................................................................................................................................................................................
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 (ie. 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 users 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 14400 minutes, with a minimum
of 1 minute and a default of 10 minutes.
When the session timer expires, the NE logouts and disconnects a users 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
2-10
Login sessions
....................................................................................................................................................................................................................................
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 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.

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.
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.
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
2-11
Issue 2 April 2009
....................................................................................................................................................................................................................................
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.
System access
The NE applies the following security settings:
telnet is enabled to all TL1 and CLI ports

TFTP and FTP are enabled
HTTP is enabled for remote management
SNMPv1 and SNMPv2c requests are allowed by the NE.
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.
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).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
2-12
....................................................................................................................................................................................................................................
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 port 3083, 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.
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.
Local NE Authentication
SNMPv2
Local NE authentication
Local NE Authentication is accomplished via the UID and PID pair created and stored
on the local NE.
SNMP authentication
The local NE can authenticate and authorize users based on SNMP.

The following applies to SNMP:
The NE supports separate DB records for SNMP users. SNMP users are different
from the CLI/TL1/WebUI users. All SNMP users are provisioned via 1354
RM-PhM.
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 system allows cloning a new SNMP user from an existing user.
Login access to the NE via SNMP is always based on the UID and PID pair
resident on the NE.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
2-13
Issue 2 April 2009
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 <1-32 chars>
IPAddr
Port Timeout (format is hundreths of second); default=1500
Retry Count {0-255}; default=3

SNMP Version {v1, v2c}; default=v2c
NMS Station Group ID {0-65535; default=0
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.
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, obsever, 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 20 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
2-14
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.
...................................................................................................................................................................................................
Enter parameters and click Apply.

E...................................................................................................................................................................................................
ND OF STEPS
Delete trap destinations

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

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

E...................................................................................................................................................................................................
ND OF STEPS
View trap destinations

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

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

Result: The Trap Destination details are displayed.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
2-15
Issue 2 April 2009
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.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
2-16
3 ata communication
D
set-up
Overview
Purpose
This chapter provides information for setting up 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
1830 PSS network via the Optical Supervisory Channel (OSC).
Contents
User interfaces
3-2
3-6
3-7
3-10
3-12
Connection release
3-12
CIT port
3-13
Using the WebUI
3-13
3-15
...................................................................................................................................................................................................................................
PN 8DG59474 BAAA
3-1
Issue 2 April 2009
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 a
WebUI interface for the network element. 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.1.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.
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.
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 1830 PSS TL1 interface is a
text-based command line interface that allows the operator to configure and manage
1830 PSS hardware, software, and services.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
3-2
User interfaces
....................................................................................................................................................................................................................................
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 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 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 1830
PSS network element acts as a managed network element or network element agent.
Traps are messages that the 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: 1830 PSS supports SNMP versions v1 and v2c of the protocol.
User Panel (USRPNL)
The 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
Craft LAN connection via RJ45
OAMP LAN connection via RJ45

VoIP LAN connection via RJ45
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
3-3
Issue 2 April 2009
User interfaces
....................................................................................................................................................................................................................................
The two 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.
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 1830 PSS
NEs 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.
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 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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
3-4
User interfaces
....................................................................................................................................................................................................................................
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 ECs CIT port and the SW
will auto switch to the active EC.
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.
The CIT port supports DHCP server. When a connection (e.g. using a laptop) is
detected, the NE doles out an internal 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.
The available addresses start at the beginning of the network address range as long as
they dont 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-32 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 1830
PSS extension shelves (sub-shelves). The 1830 PSS 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
3-5
Issue 2 April 2009
....................................................................................................................................................................................................................................
The basic communications network architecture for the 1830 PSS includes all LAN
interfaces, OSC interfaces, and GCC interfaces. LAN interfaces include the OAMP,
VoIP, 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.
Even though the 1830 PSS is IP-based, there is still a concept of a GNE node if or
when a customer does not want to run OSPF on the OAMP interface, or manually add
static routes to every NE on the network. An EMS will not know how to connect to
the RNE if the RNEs IP address is not visible beyond the GNEs OAMP interface.
Thus, the GNE concept allows the locally reachable NE to proxy as a gateway
network element (GNE) for the entire network.
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 1830 PSS system are restricted to supporting only
the 11STAR1 OTU2 client port. The other end of this 11STAR1 OTU2 is the 1830
PSS-1 (Edge Device).
Table 3-1, Communications Network Sizing (p. 3-6) provides a communications
network sizing summary.
Table 3-1
Connection Type
Maximum Value
Comment
TL1 (ports 3082, 3083)
20
Multiple TL1 user sessions

to any NE
WebUI
16
This is for Craft Interface

Terminal (CIT) from the
local craft, or remotely
connected
CLI
16
From the local craft or

remote
SNMP
10
Management from 1354

RM-PhM or equivalent
SNMP manager
GCC0
32
For management
connection extension to
Alcatel-Lucent 1830 PSS-1
Edge Device
OSC
Maximum of 8 fiber pairs
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
3-6
....................................................................................................................................................................................................................................
Table 3-1
(continued)
Connection Type
Maximum Value
Comment
Size of TID-IP map per

GNE
128
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
40
32 GCC0 + 8 OSC
Number of NEs in one

OSPF area
256
Default OSPF area is 0
Number of provisionable
OSPF areas supported on
the NE
0, 1, 2, 3
Areas per area border

router
OAMP, OSC, and GCC on

the NE

Overview
A Gateway Network Element (GNE) is defined as an NE that provides user access to

all NEs within the maintenance subnetwork. Any 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 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 OSPF which runs on the OAMP, the OSC, VoIP, and the GCC0
interfaces. 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).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
3-7
Issue 2 April 2009
....................................................................................................................................................................................................................................
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 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.
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 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-9).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
3-8
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
3-9
Issue 2 April 2009
....................................................................................................................................................................................................................................

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-13)).
Create IP static route
Note: To create the default route, enter Destination Address = 0.0.0.0 and Mask =
0.0.0.0. Only one default route may be created per NE.
...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > IP Routes

Result: The IP Routes screen is displayed.
...................................................................................................................................................................................................
Click Create.
Result: The Create Static IP Route screen is displayed.
...................................................................................................................................................................................................
Enter attribute values and click Apply.
E
ND OF STEPS
....................................................................................................................................................................................................................................
View all IP routes

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

E
ND OF STEPS
....................................................................................................................................................................................................................................
Delete IP static route

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

...................................................................................................................................................................................................
Select the IP Route and click Delete.
E
ND OF STEPS
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
3-10
....................................................................................................................................................................................................................................
Create OSPF area

...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > OSPF Areas

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

E...................................................................................................................................................................................................
ND OF STEPS
View OSPF areas

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

Result: The OSPF Areas are displayed.
E...................................................................................................................................................................................................
ND OF STEPS
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.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
3-11
Issue 2 April 2009
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
3-12
CIT port
....................................................................................................................................................................................................................................
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).
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.
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 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 or Windows 2000, updated to the most recent patch level.
Internet Explorer 6.0 or Internet Explorer 7.0, updated to the most recent patch
level.
J2SE Java Runtime Environment (JRE) version 5.0. The supported version for the
NE software version you are running is included on the NE software CD-ROM.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
3-13
Issue 2 April 2009
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
The Equipment Tree hierarchy is as follows:
System
+ Shelf
+ Slot/Card
+ Port
The user will traverse the hierarchy and select a specific equipment to access the
functions supported by that equipment.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
3-14
....................................................................................................................................................................................................................................

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-16)
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 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.
...................................................................................................................................................................................................
Click on the Login button, or press the Enter key.

Result: Upon successful login, the System Details screen is displayed.
E...................................................................................................................................................................................................
ND OF STEPS
Exit the WebUI

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

E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
3-15
Issue 2 April 2009
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
3-16
....................................................................................................................................................................................................................................
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 re-connect to the NE when it is available.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
3-17
Issue 2 April 2009
4
Overview
Purpose
This chapter provides details for provisioning the 1830 PSS system including shelves,
slots/cards, and ports.
Contents
Introduction
4-2
4-3
4-4
Shelf provisioning
4-14
4-18
4-19
4-23
4-27
4-52
...................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-1
Issue 2 April 2009
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-2
....................................................................................................................................................................................................................................

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...................................................................................................................................................................................................
ND OF STEPS
Reboot NE
The user can request a manual reboot of the entire NE which reboots all applicable
circuit packs (EC, AHPHG/ALPHG, CWR, OT, OPSA, SVAC). 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, 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.

E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-3
Issue 2 April 2009
....................................................................................................................................................................................................................................
Configure firmware
The WebUI supports configuring firmware for the following card types: 11STAR1,
11STGE12, 11STMM10, AHPHG, ALPHG, CWR8, OPSA. 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. The WebUI allows this
provisioning only if the card is equipped in the NE.
...................................................................................................................................................................................................
Select the card from the equipment tree and click the Firmware tab.
...................................................................................................................................................................................................
Select desired Provisioned Release from the picklist and click Submit.
E
ND OF STEPS
....................................................................................................................................................................................................................................
View firmware
...................................................................................................................................................................................................
In the WebUI, select Reports > Firmware.

Result: The Firmware report window is displayed.
END OF STEPS
...................................................................................................................................................................................................
Equipment discovery
Detection of physical insertion and removal (via backplane equipage leads) is

supported for the following circuit packs which reside in Universal Shelf slots.
EC
USRPNL
PF
FAN
AHPHG/ALPHG
CWR8
OT
OPSA
SFC
SFD5
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-4
....................................................................................................................................................................................................................................
SVAC
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 Universal Shelf slots.
DCM
SFD44
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.
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.
Manual restart can be applied individually to any of the following circuit pack types:
EC, AHPHG/ALPHG, CWR, OT, OPSA, SVAC (see Reboot card (p. 4-26)). Manual
restart of the entire NE performs restart of all of these circuit pack types (see Reboot
NE (p. 4-3)).
Note: USRPNL, FAN, PF, SFC, SFD, and DCM have no processors and cannot be
restarted.
Mandatory equipment
The mandatory equipment in each shelf includes: one shelf controller (EC) in either
slot 1 or slot 18, two power modules (PF), and a fan module (FAN). The User Panel
(USRPNL) is mandatory on the main shelf only, and not allowed on other shelves.
Mandatory equipment is automatically provisioned whether present or not. Mandatory
equipment is provisioned without AINS state (see Automatic in-service (AINS)
(p. 4-13)). Therefore, if mandatory equipment is not present it will be alarmed
(assuming its absence is detected).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-5
Issue 2 April 2009
....................................................................................................................................................................................................................................
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-14)). 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-14)). 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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-6
....................................................................................................................................................................................................................................
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.
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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-7
Issue 2 April 2009
....................................................................................................................................................................................................................................
Universal slot(s) provisioning and validation
The supported packs and slot locations for an 1830 PSS Universal Shelf are shown in
Table 4-1, 1830 PSS Circuit Pack Slot Allocation (p. 4-8)
Table 4-1
1830 PSS Circuit Pack Slot Allocation
Card
Description
Slot Location
Height / Number
of Slots
11STAR1
11G Single Port

Tunable AnyRate
Transponder (1
client)
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 Multirate
Mux Transponder
(10 universal
clients)
2-17
Full / 1
AHPHG/ALPHG
AHPHG (High
Power High Gain
Optical Amp) or
ALPHG (Low
Power High Gain
Optical Amp)
2-17
Full / 1
CWR8
Colorless
Wavelength Router
2-16
Full / 2
FAN
FAN
37
OPSA
Bidirectional
Optical Protection
Switch
2-17, 20-35
Half / 1
PF
Power Filter
19, 36
Half / 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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-8
....................................................................................................................................................................................................................................
Table 4-1
1830 PSS Circuit Pack Slot Allocation (continued)
Card
Description
Slot Location
Height / Number
of Slots
SFD5
5 channel static
DWDM filter
2-17, 20-35
Half / 1
SVAC
Single port VOA

card
2-17, 20-35
Half / 1
USRPNL
User Interface Panel
40
Slots 2-17 and 20-35 of a Universal Shelf are considered universal slots (i.e.,
installation of any 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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-9
Issue 2 April 2009
....................................................................................................................................................................................................................................
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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-10
....................................................................................................................................................................................................................................
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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-11
Issue 2 April 2009
....................................................................................................................................................................................................................................
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
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-12
....................................................................................................................................................................................................................................
Deletion of mandatory equipment in a universal shelf is not allowed: (i.e., PF,

FAN, USRPNL, active EC).
Deletion of a universal 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 universal 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.
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 supressed 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-13
Issue 2 April 2009
....................................................................................................................................................................................................................................
Note: If a card is deleted when it is still physically present, it will not be

re-discovered and auto-provisioned until it is physically removed and re-inserted,
or until the system reboots (whichever comes first).
Shelf provisioning
Overview
Three types of shelves are supported. These shelves are Universal (UNV), SFD44, and
External DCM (DCM). The maximum number of shelves cannot be exceeded. The
maximum number of Universal shelves is 8 and the maximum number of DCM/SFD44
shelves is 24. The maximum number of total shelves is 32.
Note: SFD44 and DCM shelf ID starts at 25 and can be in the range of 25-48.
Universal shelf
Rotary dial backplane setting
On each UNV shelf, a shelf ID number and a shelf role are settable 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
Note: Bits 6-5 of the register must be set to 0 (zero).

If any new universal 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.
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 Universal 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-14
Shelf provisioning
....................................................................................................................................................................................................................................
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 universal 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 universal 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 universal 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 universal shelves can
be pre-provisioned and can be auto-provisioned.
SFD44 and DCM shelf
The SFD44 is modeled by the system as a shelf of type SFD44, with one fixed
slot containing a card of type SFD44. SFD44 is a passive stand-alone
rack-mounted device that is not slot-resident. SFD44s multiplex and de-multiplex
optical channel signals. The SFD44 has an optical line-level interface to a CWR circuit
pack (or an AHPHG/ALPHG, in the case of an end terminal node).
The DCM is modeled in the same way; as a shelf of type DCM, with one fixed
slot containing a card of type DCM. DCM is a passive rack-mounted device that is
not slot-resident. 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 AHPHG/ALPHG circuit packs.
Any provisioning of a new SFD44/DCM shelf automatically provisions the contained
SFD44/DCM card. Deprovisioning an SFD44/DCM shelf automatically deprovisions
(deletes) the SFD44/DCM card, and this is the only way to delete an SFD44/DCM
card.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-15
Issue 2 April 2009
Shelf provisioning
....................................................................................................................................................................................................................................
SFD44/DCM shelves have no rotary dial mechanism. Instead, each SFD44/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 SFD44 and the optical line equipment it
supports is defined solely by an topology fiber assignment between SFD44 and CWR
(or AHPHG/ALPHG, in an end terminal node). The transmission association between a
DCM and the optical line equipment it supports is defined solely by an OCONN fiber
assignment between DCM and AHPHG/ALPHG. The transmission association and the
management association must agree; they must have the same modules as end-points.
SFD44/DCM remote inventory data is retrieved electronically by a
CWR/AHPHG/ALPHG pack; this is the only management access to the SFD44/DCM.
The first reading of SFD44/DCM electronic inventory is treated as SFD44/DCM
detection, and this defines an internal management association between an
SFD44/DCM and a CWR/AHPHG/ALPHG. The system must internally map the
SFD44/DCM AID to the CWR/AHPHG/ALPHG via which the SFD44/DCM was first
detected. This allows subsequent data retrieval against an SFD44/DCM AID to be
directed internally to the correct CWR/AHPHG/ALPHG.
SFD44 and DCM shelves can be pre-provisioned and can be auto-provisioned. An
SFD44/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 SFD44/DCM serial number. This allows
checking for connection of the correct SFD44/DCM.
Matching pre-provisioned values
When a new SFD44/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

SFD44/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 SFD44/DCM.
When a newly detected SFD44/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 SFD44/DCM. The TYPEID is automatically assigned the actual shelf type.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-16
Shelf provisioning
....................................................................................................................................................................................................................................
Note: The Serial Number value can be modified by the user whenever needed. For
example, when an SFD44/DCM is physically replaced without deletion of its
provisioning, Serial Number must be changed from the old serial number to the
new one.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-17
Issue 2 April 2009
....................................................................................................................................................................................................................................

Before you begin
The WebUI supports creation (pre-provisioning) for all shelves, except the main shelf
(see Shelf provisioning (p. 4-14)).
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
ND OF STEPS
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
Delete a shelf
Note: The main shelf cannot be deleted.

...................................................................................................................................................................................................
Select the shelf from the equipment tree and click Delete.
Note: For a Universal shelf, all cards except the active EC, FAN, USRPNL, and PF
must be manually deleted before a shelf can be deleted.
For SFD44 and DCM 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
ND OF STEPS
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-18
....................................................................................................................................................................................................................................
Test LEDs
...................................................................................................................................................................................................
Select the Universal shelf from the equipment tree and select the Test/Analysis
function.
Result: The Shelf LEDs screen is displayed.
...................................................................................................................................................................................................
Select Test LEDs and click Submit.

END OF STEPS
...................................................................................................................................................................................................
11STAR1 OT provisioning
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, 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 44 channels supported by the system.
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)

11STMM10 OT provisioning
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-19
Issue 2 April 2009
....................................................................................................................................................................................................................................
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).
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)
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-20) shows logical signal processing from the client port to the DWDM
line port. Line port structure consists of 4 ODU1s multiplexed into an ODTU12.
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}
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-20
....................................................................................................................................................................................................................................
Each client adapted information takes fixed amount of bandwidth expressed in virtual
time slots in a 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
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 or equal than 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 (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).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-21
Issue 2 April 2009
....................................................................................................................................................................................................................................
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.
11STGE12 OT provisioning
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-22
....................................................................................................................................................................................................................................

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.
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...................................................................................................................................................................................................
ND OF STEPS
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-23
Issue 2 April 2009
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Enter appropriate values in the respective fields and click Submit.
E
ND OF STEPS
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
View SFP/XFP inventory
Note: The following ports have pluggable modules (XFP/SFP):
OT (11STAR1, 11STMM10, 11STGE12) client ports

AHPHG/ALPHG, OSC ports
The WebUI retrieves and displays XFP/SFP inventory for all applicable cards in the
NE.
...................................................................................................................................................................................................
In the WebUI, select Reports > Inventory > SFP/XFP.

Result: The SFP/XFP Inventory is displayed.
E
ND OF STEPS
....................................................................................................................................................................................................................................
Protection switch (EC only)
Note: The controller (EC) supports duplex mode (i.e., redundancy). If the standby
EC is equipped, the WebUI will allow the user to initiate a switch between the
inactive and the active EC.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-24
....................................................................................................................................................................................................................................
The following applies:
The active EC will deny any and all requests from CLI, WebUI and PhM when
a switchover is taking place.
The active EC 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 from the equipment tree and select the Protection Switch tab.
Result: The EC Protection Switch Settings screen is displayed.
...................................................................................................................................................................................................
To manually switch to the inactive EC, select the Force Protection Switch option and
click Submit.
Note: A switch is not allowed if:
Protection Setting of the selected card = Unequipped
The selected card is in slot 1 and slot 18 is unequipped
The selected card is in slot 18 and slot 1 is unequipped.
Result: The WebUI displays a warning to the user indicating that the active and
standby ECs 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...................................................................................................................................................................................................
ND OF STEPS
EC upgrade (in-service upgrade from simplex to duplex)

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

...................................................................................................................................................................................................
Insert the EC pack (8DG59241AA) into slot 1.

...................................................................................................................................................................................................
Download, install and activate R1.1 software.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-25
Issue 2 April 2009
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Telnet to the EC in slot 1 from a windows PC.

Run the debug A-code upgrade command: /pureNeApp/EC/redAcode 1 .
...................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
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-5)).
...................................................................................................................................................................................................
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.
E
ND OF STEPS
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-26
....................................................................................................................................................................................................................................
Result: The Delete Card screen is displayed.

...................................................................................................................................................................................................
Select option to Delete this Card and click Submit.

END OF STEPS
...................................................................................................................................................................................................
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).
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-27
Issue 2 April 2009
....................................................................................................................................................................................................................................
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.
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 deprovisioned.
However, the slot cannot be deprovisioned 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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-28
....................................................................................................................................................................................................................................
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 (10GFC)
OTM-0.2 (OTU2)
OC-192
STM-64
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
encmode
errfrmdrop
Attribute Definition
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)
cbrlan11.096 - (Transparent mode, no GFP)
Errored Frame Drop Mode. This attribute, when enabled, will

discard all received errored frames. Select either:
Enabled - Discard all ingress errrored frames.
Disabled (default) - Do not discard all ingress errored

frames.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-29
Issue 2 April 2009
....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
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-SR
XI-64.1
XS-64.2b
XI-64.2C
XL-64.2C
XL-64.2D
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.
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-30
....................................................................................................................................................................................................................................
10G fibre channel (10GFC) client port provisioning
signal type is provisioned to 10GFC:
Provisionable
Attribute
moduletype
losprop
10GB-SR
XI-64.1
XS-64.2b
XI-64.2C
XL-64.2C
XL-64.2D


user.

OC-192 or STM-64 or 10GbE WAN PHY client port provisioning
provisioned signal type is either OC-192 or STM-64:
Provisionable
Attribute
J0_ex
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-31
Issue 2 April 2009
....................................................................................................................................................................................................................................
Provisionable
Attribute
J0_fmt
trccmp
moduletype
losprop
sdth
J0 format Configure the J0 format. Select from one of the
following:
1 - Configure J0 format to 1-byte mode.
16 - Configure J0 format to 16-byte mode.
J0 trace comparison. Choose from one of the following:
Enable - Enable J0 comparison.
Disable - Disable J0 comparison.

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


user.

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.
Range: {10-5, 10-6, 10-7, 10-8 10-9}

Default: 10-6
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-32
....................................................................................................................................................................................................................................
Provisionable
Attribute
sfth
Attribute that specifies the BER threshold to declare a Signal
Fault condition. Enter a value from the following range for the
bit error rate, expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-
OTM0.2 client port provisioning (OTU2)
provisioned client signal type is OTM0.2 (OTU2):
Provisionable
Attribute
fectype
gccstat
moduletype
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
GCC0 Status. Enter one of the following values:
Enabled - Configure GCC0 status to enabled.
Disabled - Configure GCC0 status to disabled.

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


user.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-33
Issue 2 April 2009
....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
oprmode
Operational Mode. Enter one of the following values:
ADDDROP - Configure the operational mode to add/drop
ospf
Configure the OSPF attributes. Enter the OSPF area followed

by an IP address.
oturate
OTU rate Specifies the client OTM0.2 rate. Enter one of the
following values:
tti
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)
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 comparson (default)
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-34
....................................................................................................................................................................................................................................
OTM0.2 Client Port Provisioning (ODU2)
provisioned client signal type is OTM0.2 (ODU2):
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
9540,
9440,
9340,
9240,
fectype
oprmode
one of the following: {0, 9600, 9590, 9580, 9570, 9560,

9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450,
9430, 9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350,
9330, 9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250,
9230, 9220, 9210, 9200, 9190, 9180, 9170}
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
Operational Mode. Enter one of the following values:
ADDDROP - Configure the operational mode to add/drop
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-35
Issue 2 April 2009
....................................................................................................................................................................................................................................
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)


(default)

tx_sapi Specifies the transmitted Source Access Point

Identifier. 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
mappingmode
ODUkp to CBRx mapping mode. This attribute specifies the
mapping mode that will be used when the client port signal is
provisioned to OC-192, STM-64 or 10GbE WAN.
Set to bitsync for bit synchronous CBR mapping
Set to async for asynchronous CBR mapping
Default = previously existing value
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-36
....................................................................................................................................................................................................................................
Provisionable
Attribute
pldtype
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
Set to a value in the following range: {0-255}
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)


(default)


hex value 00)
11STMM10 OT port state provisioning
The states of the C1-10 and L1 ports are provisioned independently. The following port
states are supported:
mt - Provision the state to mt to set the admin state to maintenanc
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-37
Issue 2 April 2009
....................................................................................................................................................................................................................................
Set ains to enabled
11STMM10 client port provisioning
The user can provision the 11STMM10 OT for the following client signal types:
GbE
OC3
STM1
OC12
STM4
OC48
STM16
CBR2G5
GFC
2GFC
4GFC
For each of the above client signal types, the user can provision different attributes as
described in the following sub-sections.
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
encmode
Description
Specifies the encapsulation mode used to transport the 1GbE
Ethernet signal. Enter this keyword followed by one of the
following values:
gfp-t Generic Framing Protocol, transparent encapsulation
option (default)
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:
disabled (default)
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-38
....................................................................................................................................................................................................................................
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 one of the following:
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:

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


modules, without 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,
followed by a value from the following range:
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-39
Issue 2 April 2009
....................................................................................................................................................................................................................................
CBR2G5 client port provisioning
the signal type is provisioned to CBR2G5 :
Port Attribute
sdth
sfth
jo
Description
Specifies the received BER threshold required to raise a signal
defect condition. Enter this keyword followed by a value for
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 rate, expressed as 10-n.
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
(default)
timmresp J0 trace identifier mismatch response. This

keyword enables or disables the J0 mismatch response
Set to enabled to enable J0 mismatch response
Set to disabled to disable J0 mismatch response
(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 comparson (default)
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-40
....................................................................................................................................................................................................................................
Port Attribute
losprop
moduletype
timeslot
[line | vts]
Description

the following:

Sl-16.1
SS-16.1
SL-161
SL-162
SL-162C
SL-162D
SS-16.1A


be set to user.

{0-4}
Range: {0 or 1}
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-41
Issue 2 April 2009
....................................................................................................................................................................................................................................
OC3/OC12/OC48 and STM1/STM4/STM16 client port provisioning
the signal type is provisioned to OC3/OC12/OC48 and STM1/STM4/STM16 :
Port Attribute
sdth
sfth
jo
Description
Specifies the received BER threshold required to raise a signal
defect condition. Enter this keyword followed by a value for
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 rate, expressed as 10-n.
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.
(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 comparson (default)
- 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.e
Set to disabled to disable TIMM defect detection.
(default).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-42
....................................................................................................................................................................................................................................
Port Attribute
losprop
moduletype
Description

the following:

SS-1.1 (for oc3 clients)
SL-1.1 (for oc3 clients)
Sl-16.1 (for oc48 clients)
SL-161 (for oc48 clients)
SL-162 (for oc48 clients)
SL-162C (for oc48 clients)
SL-162D (for oc48 clients)
SS-16.1A (for oc48 clients)

will accept a plugguble module from the list of modules

be set to user.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-43
Issue 2 April 2009
....................................................................................................................................................................................................................................
Port Attribute
timeslot
[line | vts]
Description
Enter the keyword line to specify the time slot on the line
{0-4}
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: {1,13,25,37}
For OC-48 or STM16 client:
Range: {0 or 1}
GFC/2GFC/4GFC client port provisioning
the signal type is provisioned to 1, 2 or 4 Gb/s Fiber channel :
Port Attribute
encmode
Description
Specifies the encapsulation mode used to transport the 1GbE
Ethernet signal. Enter this keyword followed by one of the
following values:
gfp-t Generic Framing Protocol, transparent encapsulation
option (default)
fcmode
losprop
Specifies the fiber channel interface type (Fiber Channel or

FICON). Enter this keyword followed by either of the following
values:
FC (default)
FICON
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-44
....................................................................................................................................................................................................................................
Port Attribute
moduletype
timeslot
[line | vts]
Description
the following:

2FCSN-I
4FCSN-I
SS-16.1A
SS-16.2C


be set to user.

{0-4}
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
11STMM10 line port provisioning
The line interface on the 11STMM10 OT supports provisionable parameters at the

OTU2 and ODU2 transport layers, as defined in the following tables.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-45
Issue 2 April 2009
....................................................................................................................................................................................................................................
The following OTU2 attributes are provisionable on the 11STMM10 L1 interface:

Provisionable
Attribute
channel
transponder.
Enter
9540,
9440,
9340,
9240,
fectype
tti

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

following values:


(default)


hex value 00)
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-46
....................................................................................................................................................................................................................................
The following ODU2 attributes are provisionable on the 11STMM10 L1 interface:

Provisionable
Attribute
pldtype
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
Set to a value in the following range: {0-255}



(default)


hex value 00)
11STGE12 OT port state provisioning
The states of the C1-C10 and L1 ports are provisioned independently. The following
port states are supported:
mt - Provision the state to mt to set the admin state to maintenance
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-47
Issue 2 April 2009
....................................................................................................................................................................................................................................
Set ains to enabled
Set ains to disabled
11STGE12 client port provisioning
The following attributes are provisionable on the 11STGE12 C1-10 interfaces:

GbE client port provisioning
Port Attribute
autoneg
Description
Attribute that controls the status of auto-negotiation. Enter this
keyword followed by either of the following values:
enabled
disabled (default)
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-48
....................................................................................................................................................................................................................................
Port Attribute
moduletype
Description
the following:

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


be set to user.
11STGE12 line port provisioning
The line interface on the 11STGE12 OT supports provisionable parameters at the

OTU2 and ODU2 transport layers, as defined in the following tables.
The following OTU2 attributes are provisionable on the 11STGE12 L1 interface:

Provisionable
Attribute
channel
transponder.
Enter
9540,
9440,
9340,
9240,
fectype

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

following values:
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-49
Issue 2 April 2009
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


(default)


hex value 00)
The following ODU2 attributes are provisionable on the 11STGE12 L1 interface:

Provisionable
Attribute
ptmmresp
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-50
....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


(default)


hex value 00)
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-51
Issue 2 April 2009
....................................................................................................................................................................................................................................

Before you begin
The only port types that can be created and deleted are: AHPHG and ALPHG OSC
ports, and OT Client ports.
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 OTU Details tab. For ODU2
attributes, select the ODU2 Details tab.
...................................................................................................................................................................................................
To modify line port settings, enter parameters and click Submit.
E
ND OF STEPS
....................................................................................................................................................................................................................................
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.
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 signal rate of the port and click Submit.
E
ND OF STEPS
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-52
....................................................................................................................................................................................................................................
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...................................................................................................................................................................................................
ND OF STEPS
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.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
ND OF STEPS
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-53
Issue 2 April 2009
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
E
ND OF STEPS
....................................................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
E
ND OF STEPS
....................................................................................................................................................................................................................................
AHPHG / ALPHG LINE port
Note: The LINE port is automatically created and deleted with the
AHPHG/ALPHG card.
The following procedure describes how to view or modify the AHPHG/ALPHG LINE
port settings.
...................................................................................................................................................................................................
Expand the AHPHG/ALPHG in the equipment tree to show ports. Select LINE port.
Result: Provisionable settings are displayed under the Port Details tab.
...................................................................................................................................................................................................
To modify port settings, enter parameters and click Submit.
E
ND OF STEPS
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-54
....................................................................................................................................................................................................................................
AHPHG / ALPHG SIG port
Note: The SIG port is automatically created and deleted with the AHPHG/ALPHG
card.
The following procedure describes how to view or modify the AHPHG/ALPHG SIG
port settings.
...................................................................................................................................................................................................
Expand the AHPHG/ALPHG 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...................................................................................................................................................................................................
ND OF STEPS
AHPHG / ALPHG OSC port
The following procedure describes how to create, view, or modify the AHPHG/ALPHG
OSC port settings.
...................................................................................................................................................................................................
Expand the AHPHG/ALPHG in the equipment 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 modify settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
ND OF STEPS
AHPHG / ALPHG DCM port
Note: The DCM port is automatically created and deleted with the
AHPHG/ALPHG card.
The following procedure describes how to view or modify the AHPHG/ALPHG DCM
port settings.
...................................................................................................................................................................................................
Expand the AHPHG/ALPHG in the equipment tree to show ports. Select DCM port.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-55
Issue 2 April 2009
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
E
ND OF STEPS
....................................................................................................................................................................................................................................
CWR8 SIG port
Note: The SIG port is automatically created and deleted with the CWR8 card.
The following procedure describes how to view or modify the CWR8 SIG port
settings.
...................................................................................................................................................................................................
Expand the CWR8 in the equipment tree to show ports. Select SIG port.
...................................................................................................................................................................................................
E
ND OF STEPS
....................................................................................................................................................................................................................................
CWR8 OMD port
Note: The OMD port is automatically created and deleted with the CWR8 card.
The following procedure describes how to view or modify the CWR8 OMD port
settings.
...................................................................................................................................................................................................
Expand the CWR8 in the equipment tree to show ports. Select OMD port.
...................................................................................................................................................................................................
E
ND OF STEPS
....................................................................................................................................................................................................................................
CWR8 THRU port
Note: The THRU port is automatically created and deleted with the CWR8 card.
The following procedure describes how to view or modify the CWR8 THRU port
settings.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-56
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the CWR8 in the equipment tree to show ports. Select THRU port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
ND OF STEPS
CWR8 CLS [1-8] ports
Note: The CLS ports are automatically created and deleted with the CWR8 card.
The following procedure describes how to view or modify the CWR8 CLS port
settings.
...................................................................................................................................................................................................
Expand the CWR8 in the equipment tree to show ports. Select the CLS port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
ND OF STEPS
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.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
ND OF STEPS
EC ES1 and ES2 ports
Note: The ES1 and ES2 ports are automatically created and deleted with the EC
card.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-57
Issue 2 April 2009
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
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.
...................................................................................................................................................................................................

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
ND OF STEPS
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-58
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
ND OF STEPS
SFD44/SFC OMD port
Note: The OMD port is automatically created and deleted with the SFD44/SFC
card.
The following procedure describes how to view or modify the SFD44/SFC OMD port
settings.
...................................................................................................................................................................................................
Expand the SFD44/SFC in the equipment tree to show ports. Select OMD port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
ND OF STEPS
SFD44/SFD5/SFC Sig port, Channel ports, and EXP port
Note: The Sig port, Channel ports and EXP port are automatically created and
deleted with the SFD44/SFD5/SFC card. The EXP port is not applicable to the
SFD44 and SFC8.
The following procedure describes how to view or modify the SFD44/SFD5/SFC Sig
port, Channel ports, and EXP port settings.
...................................................................................................................................................................................................
Expand the SFD44/SFD5/SFC in the equipment tree to show ports. Select Sig port,
Channel ports, or EXP port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-59
Issue 2 April 2009
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
Expand the SVAC in the equipment tree to show ports. Select C1 port.
...................................................................................................................................................................................................
E
ND OF STEPS
....................................................................................................................................................................................................................................
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.
Result: Port Interface settings are displayed under the Port Details tab.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
4-60
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To view or modify OSPF parameters for the OAMP and VOIP ports, select the OSPF
Details tab.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
4-61
Issue 2 April 2009
Alarm management
5
Overview
Purpose
This chapter describes the alarm management functionality supported by 1830 PSS.
Contents
Description
5-1
5-5
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
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.
The system supports two modes for alarm reporting: SONET and SDH. The mode
of alarm reporting is defined by the system level MODE parameter.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
5-1
Issue 2 April 2009
Alarm management
Description
....................................................................................................................................................................................................................................
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)
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
5-2
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 NEs 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, and green indicating the severity of the trouble are used
on an NEs physical control/status display panel to visually represent various alarm
levels and status conditions at the NEs 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
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.
Equipment/ facility alarms
Equipment and facilty 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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
5-3
Issue 2 April 2009
Alarm management
Description
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
5-4
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...................................................................................................................................................................................................
ND OF STEPS
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...................................................................................................................................................................................................
ND OF STEPS
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...................................................................................................................................................................................................
ND OF STEPS
View alarms history log
The WebUI supports the following alarms history logs: Critical, Major, Minor,
Warning.
...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > Alarms > {Critical, Major, Minor, Warning}.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
5-5
Issue 2 April 2009
Alarm management
....................................................................................................................................................................................................................................
Result: The respective Alarms Log is displayed.

E
ND OF STEPS
....................................................................................................................................................................................................................................
View events history log
The WebUI supports the following Event history logs: General, State Changes, User
Actions, Persistent Events.
...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > Events > {General, State Changes, User
Actions, Persistent Events}.
Result: The respective Events Log is displayed.
E
ND OF STEPS
....................................................................................................................................................................................................................................
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.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
5-6
6
Overview
Purpose
This chapter describes setting the performance monitoring functionality of the 1830
PSS.
Contents
Description
6-1
6-8
Description
Overview
Performance monitoring (PM) refers to the in-service, non-intrusive monitoring of

transmission quality and equipment health. The 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
6-1
Issue 2 April 2009
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
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.
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 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-2) gives an illustration of PM points in an
1830 PSS NE.
Figure 6-1 Performance monitoring points in an 1830 PSS NE
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
6-2
Description
....................................................................................................................................................................................................................................
The identified points in Figure 6-1, Performance monitoring points in an 1830 PSS
NE (p. 6-2) 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 types (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.
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 50 bins (port/interfaces support up to 8
bins for 24-hour data, and up to 33 bins for 15-minute data). The use of multiple bins
allows you to maintain a historical view of the performance of a card for up to 50
days.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
6-3
Issue 2 April 2009
Description
....................................................................................................................................................................................................................................
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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
6-4
Description
....................................................................................................................................................................................................................................
Figure 6-2 Analog parameter TCA
Note: Term exceed used with tidemark low/high monitored parameters indicates
that tidemark high value is greater then 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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
6-5
Issue 2 April 2009
Description
....................................................................................................................................................................................................................................
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. Profile instance 0 is used to
disable TCAs for the group. 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.
The system supports the following TCA profile types:
OC_N (SONET port section monitoring)
STM_N (SDH port section monitoring)

DW (OTU2 and ODU2 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)
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
6-6
Description
....................................................................................................................................................................................................................................
cleared.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
6-7
Issue 2 April 2009
....................................................................................................................................................................................................................................

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
Cards and Ports that Support PM Data

Card
Port
11STAR1
L1,C1
11STGE12
L1, C1-C10
11STMM10
L1, C1-C10
AHPHG/ALPHG
OSC, LINE, LINE-{9600~9170}
EC
No port, PM data collected for card.
SVAC
L1,C1
Note: 10xAny OT hardware does not support GbE PM statistics in egress direction.
Display PM data for EC card
Note: Card performance monitoring is supported for the EC card. Card-level PM is

not supported for other cards types.
...................................................................................................................................................................................................
In the WebUI, select the EC 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 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
ND OF STEPS
....................................................................................................................................................................................................................................
Set bins for EC card
Note: Up to fifty historical bins for 1-day and 15-min are supported.
...................................................................................................................................................................................................
In the WebUI, select the EC card and click the Performance function.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
6-8
....................................................................................................................................................................................................................................
Result: The PM Data screen is displayed.

...................................................................................................................................................................................................
Select the Settings tab.

Result: The PM Configuration screen is displayed.
...................................................................................................................................................................................................
To change settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
ND OF STEPS
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...................................................................................................................................................................................................
ND OF STEPS
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...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
6-9
Issue 2 April 2009
....................................................................................................................................................................................................................................
Display PM data for port

...................................................................................................................................................................................................
In the WebUI, select the port and click the Performance function.
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
ND OF STEPS
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
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:
ALPHG and AHPHG: OSC

11STMM10: L1, C1-10
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
6-10
....................................................................................................................................................................................................................................
11STAR1: L1 ,C1
11STGE12: L1, C1-C12
SVAC: L1, C1
...................................................................................................................................................................................................
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.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
6-11
Issue 2 April 2009
Connections
7
Overview
Purpose
This chapter describes the connection functionality supported by the 1830 PSS.
Contents
Description
7-1
7-4
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.
Note: A fiber connection cannot be created between 2 ports or the same port on the
same card, with one exception: to support AHPHG/ALPHG DCM port loopback
(see below), an AHPHG/ALPHG DCM port can be connected to itself.
A loopback connection can be created via the Physical Topology view by selecting an
AHPHG/ALPHG DCM port, clicking Loopback, and then clicking Connect.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
7-1
Issue 2 April 2009
Connections
Description
....................................................................................................................................................................................................................................
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 CLS port, LD Line port, OT Line
port, SFC OMD port, OPSA Sig 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.
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 NEs network ingress/egress port (typically the Line port of
the AHPHG/ALPHG). 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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
7-2
Connections
Description
....................................................................................................................................................................................................................................
Connecting 1830 PSS OT with 1696 ROADM
Beginning in R1.1.0, 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
Feature.
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. In R1.1, 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-4)
). The 1696R equipment will then receive this signal (with wave keys already encoded)
from the 1830 OT.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
7-3
Issue 2 April 2009
Connections
....................................................................................................................................................................................................................................
Display NE physical topology
...................................................................................................................................................................................................
In the WebUI, select Connections > NE Physical Topology.

Result: NE Physical Topology is displayed.
...................................................................................................................................................................................................
Loopback, External, Disconnect, and Connect functions can be made via the
display.
E
ND OF STEPS
....................................................................................................................................................................................................................................
Display NE logical topology

...................................................................................................................................................................................................
In the WebUI, select Connections > NE Logical Topology.

Result: NE Logical Topology is displayed.
E
ND OF STEPS
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
Display NE power trace
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.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
7-4
Connections
....................................................................................................................................................................................................................................
Result: Cross-connects are displayed.

...................................................................................................................................................................................................
Select the cross-connect and click A-Z Power or Z-A Power.

E...................................................................................................................................................................................................
ND OF STEPS
Display network power trace
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.
...................................................................................................................................................................................................

Result: Cross-connects are displayed.
...................................................................................................................................................................................................
Select the cross-connect and click A-Z Trace or Z-A Trace.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
7-5
Issue 2 April 2009
Protection
8
Overview
Purpose
This chapter describes the protection functionality supported by the 1830 PSS.
Contents
Description
8-1
8-6
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
8-1
Issue 2 April 2009
Protection
Description
....................................................................................................................................................................................................................................
the 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: In this release, Y-cable protection cannot be used with OTM0.2 signal on
11STAR1 OT. 1830 PSS does not support Y-cable protection on the 11STAR1 pack
when the client signal type is OTU2.
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).
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
8-2
Protection
Description
....................................................................................................................................................................................................................................
Bi-directional switching
In bi-directional 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.
Bi-directional protection switching can be used to protect only bi-directional customer
traffic. If a bi-directional Y-cable protection group is connected to a uni-directional
Y-cable protection group across the network, the bi-directional group will operate as a
unidirectional group for switching compatibility (the bi-directional 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.
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.
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).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
8-3
Issue 2 April 2009
Protection
Description
....................................................................................................................................................................................................................................
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.
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 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 cannnot 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 nonrevertive 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
8-4
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
8-5
Issue 2 April 2009
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
ND OF STEPS
....................................................................................................................................................................................................................................
View all protection groups

...................................................................................................................................................................................................
In the WebUI equipment tree, select Reports > APS Groups

Result: The Automatic Protection Switch Groups screen is displayed.
E
ND OF STEPS
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
Delete protection group
Note: Deletion of a protection group will be denied if there are still cross connects
that depend on the protection group.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
8-6
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...................................................................................................................................................................................................
ND OF STEPS
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.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
8-7
Issue 2 April 2009
Wavelength Tracker
9
Overview
Purpose
This chapter describes the Wavelength Tracker technology supported by the 1830 PSS.
Contents
Description
9-1
9-4
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
9-1
Issue 2 April 2009
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:
11STAR1 OT
11STMM10 OT
11STGE12 OT
SVAC
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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
9-2
Wavelength Tracker
Description
....................................................................................................................................................................................................................................
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 power levels for the service are recorded and each
detection point is programmed with the expected power for the service at that point,
based on the recorded values. It is then possible to provide notification if the channel
power at any detection point varies beyond a set threshold. By setting appropriate
thresholds, it is possible to flag these power changes before they become service
affecting.
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-6)).
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
9-3
Issue 2 April 2009
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 (11STAR1,
11STGE12, 11STMM10).
...................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
View/modify wave keys (encoder ports)

...................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
View wave keys (decoder ports)

...................................................................................................................................................................................................
In the WebUI equipment tree select the appropriate port, select Wave Keys In or Wave
Keys Out tab.
...................................................................................................................................................................................................
The Wave Keys Decoder In/Out screen is displayed..
E
ND OF STEPS
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
9-4
Wavelength Tracker
....................................................................................................................................................................................................................................
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...................................................................................................................................................................................................
ND OF STEPS
Set power
Note: Expected Power can only be set for manually power managed ports.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the record and click Set Power.

Result: The Set Power screen is displayed.
...................................................................................................................................................................................................
Set expected power attributes and click Submit.

E...................................................................................................................................................................................................
ND OF STEPS
View channel power summary

...................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Power Summary.

Result: A graphical Power Summary is displayed.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
9-5
Issue 2 April 2009
Wavelength Tracker
....................................................................................................................................................................................................................................
View unexpected wave keys

...................................................................................................................................................................................................
In the WebUI equipment tree, select the appropriate port and click on the Unexpected
Wave Keys tab.
Result: The Unexpected Wave Keys screen is displayed.
E
ND OF STEPS
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
9-6
Wavelength Tracker
....................................................................................................................................................................................................................................
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.
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 Maintenance and
Trouble-Clearing Guide to clear the problem.
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 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
9-7
Issue 2 April 2009
Wavelength Tracker
....................................................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
9-8
Wavelength Tracker
....................................................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
9-9
Issue 2 April 2009
Wavelength Tracker
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
9-10
Wavelength Tracker
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
25
Repeat the procedure steps above for the protection service, if applicable.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
9-11
Issue 2 April 2009
10
10
Database
backup and
restore
Overview
Purpose
This chapter describes the 1830 PSS database management operations including
database backup and database restore`.
Contents
Database management
10-1
Database backup
10-5
Database restore
10-7
10-9
Database management
Introduction
An 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
10-1
Issue 2 April 2009
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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
10-2
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> - Site Identifiier, 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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
10-3
Issue 2 April 2009
Database management
....................................................................................................................................................................................................................................
BACKUP-TIME {HH:MM:SS:{0-23}:{0-59}:{0-59}} - Backup Time

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 RRS 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
10-4
Database management
....................................................................................................................................................................................................................................
In a duplex controller environment:

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.
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 donwload 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
10-5
Issue 2 April 2009
Database backup
....................................................................................................................................................................................................................................
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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
10-6
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 NEs 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 NEs 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
10-7
Issue 2 April 2009
Database restore
....................................................................................................................................................................................................................................
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 users
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
10-8
....................................................................................................................................................................................................................................

Note: The information here describes procedures using the WebUI. For procedures
using 1354 RM-PhM or CLI, see the 1354 RM-PhM EMS Reference Guide and
Alcatel-Lucent CLI Command Guide.
Backup database
...................................................................................................................................................................................................
In the WebUI, select Administration > Database.

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 server is running; Directory = the path in the TFTP server). Click Apply, then
click Backup.
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...................................................................................................................................................................................................
ND OF STEPS
Restore database
...................................................................................................................................................................................................
In the WebUI, select Administration > Database.

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 server is running; Directory = the path in the TFTP server; File Name = the
name of the file to be restored from the TFTP server). Click Apply, then click
Restore.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
10-9
Issue 2 April 2009
....................................................................................................................................................................................................................................
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.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
10-10
11
Routine procedures
11
Overview
Purpose
This chapter describes 1830 PSS routine procedures.

Contents
User preferences
11-2
Syslog properties
11-3
11-4
Date/time setting
11-5
Loopbacks
11-8
Power settings
11-10
11-11
...................................................................................................................................................................................................................................
PN 8DG59474 BAAA
11-1
Issue 2 April 2009
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.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
11-2
Routine procedures
Syslog properties
....................................................................................................................................................................................................................................
Syslog properties
Setting / viewing syslog properties
...................................................................................................................................................................................................
In the WebUI, select Administration > Syslog.

Result: The Syslog Administration screen is displayed.
...................................................................................................................................................................................................
Enter syslog administration parameters and click Apply.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
11-3
Issue 2 April 2009
Routine procedures
....................................................................................................................................................................................................................................

Setting / viewing CLI user activity logging properties
...................................................................................................................................................................................................
In the WebUI, select Administration > User Activity Logging > CLI.
Result: The CLI Logging screen is displayed.
...................................................................................................................................................................................................
Select CLI logging properties and click Apply.
E
ND OF STEPS
....................................................................................................................................................................................................................................
Setting / viewing SNMP user activity logging properties

...................................................................................................................................................................................................
In the WebUI, select Administration > User Activity Logging > SNMP.
Result: The SNMP Logging screen is displayed.
...................................................................................................................................................................................................
Select SNMP logging properties and click Apply.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
11-4
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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
11-5
Issue 2 April 2009
Routine procedures
Date/time setting
....................................................................................................................................................................................................................................
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
ND OF STEPS
....................................................................................................................................................................................................................................
View NTP properties

...................................................................................................................................................................................................
Select Administration > NTP > Properties

Result: The Network Time Protocol Properties screen is displayed.
E
ND OF STEPS
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
11-6
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.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
11-7
Issue 2 April 2009
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: 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 loopack.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
11-8
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.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
11-9
Issue 2 April 2009
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-10)).
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).
Power management procedure
...................................................................................................................................................................................................
Select the appropriate port from the equipment tree and click the Power Management
tab.
Result: The Port Power Management screen is displayed.
...................................................................................................................................................................................................
Enter parameters and click Submit.
E
ND OF STEPS
....................................................................................................................................................................................................................................
Power adjustment procedure

...................................................................................................................................................................................................
Select the appropriate port from the equipment tree and click the Power Adjustment
tab.
Result: The Egress Power Adjustment or Ingress Power Adjustment screen is
displayed.
...................................................................................................................................................................................................
Enter parameters and click Submit.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
11-10
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 backout 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: 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.
...................................................................................................................................................................................................
Select Download for the Action Type and click Apply.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
11-11
Issue 2 April 2009
Routine procedures
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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: 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 backout can be performed. After this a
downgrade procedure is required.
...................................................................................................................................................................................................
Select Commit for the Action Type and click Apply.

Important! A one step software backout 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).
Result: The software release upgrade is now complete. A database backup should
be performed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
11-12
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.
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.
alarm list
A status report that lists active alarms on the NE.

....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-1
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
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.

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).
ATM networks will accept or reject connections based on a users 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.

....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-2
Glossary
....................................................................................................................................................................................................................................
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 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.
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-3
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
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.

....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-4
Glossary
....................................................................................................................................................................................................................................
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.
CIDR
See classless inter-domain routing (p. GL-5) for definition.

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.
classless inter-domain routing (CIDR)
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-4) 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).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-5
Issue 2 April 2009
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 subscribers premises.
The equipment is connected with the carriers communication network at the
demarcation point.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-6
Glossary
....................................................................................................................................................................................................................................
CWDM
See coarse wavelength division multiplexing (p. GL-5) for definition.

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

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

dense wavelength division multiplexing (DWDM)
A multiplexing technique that uses close spectral spacing of individual optical carrier
wavelengths to reduce the total number of fibers needed to provide a given amount of
information-carrying capacity. The technique takes advantage of desirable transmission
characteristics (for example, minimum dispersion or attenuation) within a given fiber.
DGEF
See dynamic gain equalization filter (p. GL-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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-7
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
dynamic host configuration protocol (DHCP)
DHCP allows a DHCP server to automatically assign an IP address to a computers

TCP/IP stack software. The number is taken from a defined range of numbers for a
given network.
....................................................................................................................................................................................................................................
earth
The European term for electrical ground.

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

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

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

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

EIA
See Electronic Industries Alliance (p. GL-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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-8
Glossary
....................................................................................................................................................................................................................................
network, including creating new services, diagnosing faults, and planning for growth. It
includes interfaces to external systems to allow functions such as billing, service orders,
and service level agreement (SLA) management.
EMC
See electromagnetic capability (p. GL-8) for definition.

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

EMS
See Element Management System (p. GL-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)
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-9
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
Located in Sophia-Antipolis, France, ETSI is the European counterpart to ANSI. Its task
is to pave the way for telecommunications integration in the European community as
part of the single European market program. It establishes telecommunication standards
for the European community.
eVOA
See electrical variable optical attentuator (p. GL-8) for definition.

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

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

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

FCC
See Federal Communications Commission (p. GL-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-12) for definition.

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

fiber distributed data interface (FDDI)
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-10
Glossary
....................................................................................................................................................................................................................................
A set of ANSI protocols used for sending digital data over fiber optic cable. FDDI
networks are token-passing networks and support data rates of up to 100 Mbps.
fiber optic cable
A cable containing one or more optical fibers.

fiber optic connector (FC)
A threaded optical connector for single-mode or multimode fiber and applications

requiring low back reflection.
field-programmable gate array (FPGA)
General purpose integrated chip; chips 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 Internets 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, radiationemitting 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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-11
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
(Connectivity Verification), it can indicate defects such as misbranching of LSPs and

errors in swapping LSP label.
forward error correction (FEC)
A technique used for error detection and correction in which the transmitting host
computer includes some number of redundant bits in the payload (data field) of a block
or frame of data. The receiving device uses those bits to detect, isolate and correct any
errors created in transmission. FEC avoids having to retransmit information which
incurred errors in network transit.
FPGA
See field-programmable gate array (p. GL-11) for definition.

frame check sequence (FCS)
Extra characters added to a frame for error control purposes. Used in HDLC, Frame
Relay, and other data link layer protocols.
Fresnel reflection
A reflection of light that occurs at the air-glass interface at the ends of an optical fiber.
See back reflection (p. GL-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
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-12
Glossary
....................................................................................................................................................................................................................................
area networks (LANs) that provides a data rate of one billion bits (one gigabit) per
second. Gigabit Ethernet is defined in the IEEE 802.3 standard and is currently used as
the backbone in many enterprise networks.
glass through-connection
A pair of optical connections between two segments that terminate on the same site.
GNE
See gateway network element (p. GL-12) for definition.

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

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

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

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

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

insertion loss
The loss of power that results from inserting a component, such as a connector or splice,
into a previously continuous path.
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.

....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-13
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
Internet protocol (IP)
A standard protocol designed for use in interconnected systems of packet-switched

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

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

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

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

ITU
See International Telecommunications Union (p. GL-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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-14
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
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-33) for related term.
laser bias current (LBC)
Current that runs through the laser to make it work. LBC is monitored by performance
monitoring. If the current goes beyond a certain threshold, the circuit pack must be
replaced.
LBC
See laser bias current (p. GL-15) for definition.

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

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

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

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

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

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

long reach (LR)
An optic standard that constrains the output power of transmitters and the sensitivity of
receivers for long-haul applications (up to 80 km) without the need for regeneration.
LOS
See loss of service/loss of signal (p. GL-16) for definition.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-15
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
loss
The amount of a signals power, expressed in dB, that is lost in connectors, splices, or
fiber defects.
loss of frame (LOF)
Loss of frame is detected when the OOF (out-of-frame) anomaly persists for a certain
time.
loss of service/loss of signal (LOS)
A condition where the optical input power falls below a certain threshold.
LR
See long reach (p. GL-15) for definition.

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

Lucent connector (LC)
Designation for a small-form-factor (SFF) design based on a proven 1.25-mm ceramic

ferrule. This connector uses RJ-style latching. It facilitates high-speed applications with
lower power requirements due to lower insertion loss (0.1 dB typical) and higher return
loss (55-dB single mode).
....................................................................................................................................................................................................................................
MAC
See media access control (p. GL-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 systems 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-16
Glossary
....................................................................................................................................................................................................................................
media access control (MAC)
The MAC address is a computers unique hardware number. The MAC address is used
by the media access control sublayer of the data link layer of telecommunications
protocols.
mesh
A type of network configuration that combines ROADMs to support mesh channel

connectivity between the ROADMs without O-E-O for transmission. It is operated as a
single NE with as many as four degrees (bidirectional DWDM interfaces) that comprise
two lines for the east and two for the west.
MIB
See management information base (p. GL-16) for definition.

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

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

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

multimode fiber
An optical fiber that has a core large enough to propagate more than one mode of light.
The typical diameter is 62.5 micrometers.
multiplexer (MUX)
A device that combines two or more signals into a single output.

multiplexing
The process that transmits two or more signals over a single communications channel.
Examples include time-division multiplexing and wavelength-division multiplexing.
MUX
See multiplexer (p. GL-17) for definition.

muxponder
A networking device that multiplexes and transponds GbE signals.

....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-17
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
NE
See network element (p. GL-18) for definition.

NEBS
See Network Equipment Building System requirements (p. GL-18) for definition.
network element (NE)
Processor-controlled entity of a telecommunications network that primarily provides

switching and transport network functions and contains network operations functions.
For 1830 PSS, a configuration of 1830 PSS equipment at a single site, addressed as a
single entity, and under the control of a single controller (NE). The types of NEs are
ILA (in-line amplifier) and ADM (add/drop multiplexer).
Network Element Management System (NMS)
The NMS provides an efficient means of managing the equipment and services within a
network, including creating new services, diagnosing faults, and planning for growth. It
has interfaces to external systems to allow functions such as billing, service orders, and
service level agreement (SLA) management.
Network Equipment Building System requirements (NEBS)
Developed by Telcordia, standards that vendors must adhere to if they want to sell
equipment to the Regional Bell Operating Companies (RBOCs) and the Competitive
Local Exchange Carriers (CLECs).
network services
Services that the network provider creates only as infrastructure to support user services.
For example, a VPN network service is used to implement an Ethernet service.
network time protocol (NTP)
Internet protocol used to synchronize time between network equipment.

NMS
See Network Element Management System (p. GL-18) for definition.

node
A node (or network element) is a set of one or more 1830 PSS-32 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-18
Glossary
....................................................................................................................................................................................................................................
NSA
See non-service affecting (p. GL-18) for definition.

NTP
See network time protocol (p. GL-18) for definition.

....................................................................................................................................................................................................................................
OA
See optical amplifier (p. GL-20) for definition.

OAMP
Operations, Administration, Maintenance, and Provisioning.

OC-n
See optical carrier level-n (p. GL-20) for definition.

Occupational Safety and Health Administration) (OSHA)
OSHA is the main American federal agency charged with the enforcement of safety and
health legislation.
OCHAN or OCh
See optical channel (p. GL-20) for definition.

ODU
See optical demultiplexer (p. GL-20) for definition.

ODU-k
An optical logical connection with a specific rate. The rate can be either ODU-10G or
ODU-40G.
OEO
See optical-electrical-optical conversion (p. GL-21) for definition.

OOF
See out of frame (p. GL-22) 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-19
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
OPR
See optical path restoration (p. GL-20) for definition.

OPS
See optical protection switch (p. GL-20) for definition.

optical add/drop multiplexer (OADM)
An OADM is a network element which allows a WDM transmission link to add or drop
optical signals, without converting the photonic stream into an electrical signal. Insertion
and extraction are done using optical filters or demultiplexers. An OADM can be either
non-reconfigurable or reconfigurable; in the latter case, optical switches need to be used.
optical amplifier (OA)
A device that amplifies an input optical signal without converting it into electrical form.
optical carrier level-n (OC-n)
A carrier rate specified in the SONET standard, where n is a numeric.

optical cell
A number of nodes connected by fiber in a predefined manner to provide route diversity

to each node. The simplest form of optical cell is a ring. Statically allocated wavelengths
are assigned within the context of one cell.
optical channel (OCHAN, Och)
An optical wavelength band for WDM optical communications.

optical demultiplexer (ODU)
Value/indicator used for an optical demultiplexer.

optical path protection (OPP)
A protection path is defined when the connection is set up. When a fault is detected on
the path, there is a switch-over from the working path to the protection path to restore
the traffic.
optical path restoration (OPR)
A recovery scheme that dynamically finds a protection path when a fault is detected.
This method is usually not capable of matching SDH/SONET recovery time periods (for
example, 50 ms).
optical power meter
An instrument that measures the amount of optical power present at the end of a fiber or
cable.
optical protection switch (OPS)
An optical circuit pack that provides WDM protection.

optical signal to noise ratio (OSNR)
The ratio between the optical signal power of the data signal and the power of the
optical noise signal.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-20
Glossary
....................................................................................................................................................................................................................................
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-29) and Synchronous Optical
Network (p. GL-29) for examples.
optical-electrical-optical conversion (OEO)
The process of converting an optical signal to an electrical equivalent and then back to
optical data.
orderwire
A section of the supervisory signal that is used for communication between sites.
OSC
See optical supervisory channel (p. GL-20) for definition.

OSHA
See Occupational Safety and Health Administration) (p. GL-19) for definition.
OSI
See Open Systems Interconnection reference model (p. GL-19) for definition.
OSNR
See optical signal to noise ratio (p. GL-20) for definition.

OSP
See outside plant (p. GL-22) for definition.

OSS
See Operations Support System (p. GL-19) for definition.

OT
See optical transponder (p. GL-21) for definition.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-21
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
OTN
See optical transport network (p. GL-21) for definition.

out of frame (OOF)
A state in which the frame alignment sequence of an SDH/SONET frame has not been
found for several consecutive frames.
outside plant (OSP)
Refers to outside the central office/building premises.

....................................................................................................................................................................................................................................
PCS
See physical coding sublayer (p. GL-22) for definition.

PDL
See polarization dependent loss (p. GL-22) for definition.

PDU
See protocol data unit (p. GL-23) for definition.

performance monitoring (PM)
Measures the quality of service and identifies any degrading or marginally operating
systems (before an alarm would be generated).
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 automatically created.
physical coding sublayer (PCS)
PCS layer monitoring used for Ethernet/FC ports.

PM
See performance monitoring (p. GL-22) for definition.

PMD
See polarization mode dispersion (p. GL-23) for definition.

point-to-point transmission
The transmission between two designated stations.

polarization dependent loss (PDL)
Loss of optical power that occurs during the polarization process. Polarized light waves
are light waves in which the vibrations occur in a single plane. The process of
transforming unpolarized light into polarized light is known as polarization (the
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-22
Glossary
....................................................................................................................................................................................................................................
orientation of the electric and magnetic field vectors of a propagating electro-magnetic

wave).
polarization mode dispersion (PMD)
PMD is an inherent property of all optical media. It is caused by the difference in the
propagation velocities of light in the orthogonal principal polarization states of the
transmission medium. The net effect is that if an optical pulse contains both polarization
components, then the different polarization components will travel at different speeds
and arrive at different times, smearing the received optical signal.
PPS
See photonic protection switch (p. GL-22) for definition.

protocol data unit (PDU)
A device used for the information exchange between equal protocol layers.
provisioning
Placing and configuring hardware and software required to activate a telecommunications

service for a customer. If the equipment is in place, provisioning may consist of creating
or modifying a customer record in a database to activate the services.
PXC
See photonic cross-connect (p. GL-22) for definition.

....................................................................................................................................................................................................................................
QoS
See quality of service (p. GL-23) for definition.

quality of service (QoS)
A set of performance parameters that characterize the transmission quality over a given
virtual connection.
QoS can be quantitatively indicated by channel or system performance parameters, such
as signal-to-noise ratio, bit error ratio, message throughput rate, and call blocking
probability.
....................................................................................................................................................................................................................................
rack
A rack is the standardized physical framework on which network equipment such as

1830 PSS-32 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-23
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
receiver
A terminal device that includes a detector and signal processing electronics. It functions
as an optical-to-electrical converter.
receiver sensitivity
The minimum optical power required at a receiver to deliver traffic at a guaranteed bit
error rate (BER). This parameter is specified back-to-back (without the effects of
chromatic dispersion or OSNR degradation).
reconfigurable optical add/drop multiplexer (ROADM)
An optical network element with a configuration that can be changed remotely. The main
benefit of this remote reconfigurability is that it reduces Operating Expenditures (OPEX)
when operating a DWDM network. OPEX is reduced because the ROADM eases
network provisioning and line tuning at both the initial installation and any upgrades (to
increase the capacity or re-allocate resources to a new demand matrix).
regeneration
Electrical signal regeneration. Typically, OTUk Section regeneration and ODUk

transparency is implied in this context.
remote network monitoring (RMON)
Provides statistics for remote performance monitoring. Defined in standard RFC 2819.
repeater
A receiver and transmitter set designed to amplify attenuated signals. Repeaters are used
to extend operating range. See in-line amplifier (p. GL-13) for related term.
request for comment (RFC)
A document that describes the specifications of a technology. RFCs are used by the
Internet Engineering Task Force (IETF) and other standards bodies.
restoration domain
A part of the network where traffic restoration is provided in isolation from the rest of
the network.
RFC
See request for comment (p. GL-24) for definition.

RIP
See routing information protocol (p. GL-25) for definition.

RJ
See random jitter (p. GL-23) for definition.

RMON
See remote network monitoring (p. GL-24) for definition.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-24
Glossary
....................................................................................................................................................................................................................................
ROADM
See reconfigurable optical add/drop multiplexer (p. GL-24) for definition.

routing information protocol (RIP)
RIP is an interior gateway protocol defined by the IETF (RIPv1 - RFC 1058 and RIPv2 2453) that specifies how routers exchange routing table information. RIP is a routing
protocol based on the distance vector algorithm. With RIP, routers periodically exchange
entire tables.
....................................................................................................................................................................................................................................
SA
See service affecting (p. GL-25) for definition.

SAN
See storage area network (p. GL-28) for definition.

SC
See shelf controller (p. GL-26) for definition.

scattering
The change of direction of light rays or photons after striking small particles. It may
also be regarded as the diffusion of a light beam caused by the inhomogeneity of the
transmitting material.
SCOT
See software control of transmission (p. GL-27) for definition.

SDH
See Synchronous Digital Hierarchy (p. GL-29) for definition.

secure shell (SSH)
A secure method of transmitting data.

segment
A pair of OSP fibers connecting two sites.

SELV
Safety extra low voltage.

service affecting (SA)
Refers to a condition that impacts or interferes with network service.

Service Level Agreement (SLA)
A contract between a network service provider and a customer that specifies, usually in
measurable terms, what services the network service provider will provide.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-25
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
services
Within the 1830 PSS-32 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-28) for definition.

SFD44
See static filter, DWDM (p. GL-28) for definition.

SFP
See small form-factor pluggable module (p. GL-27) for definition.

shared risk group (SRG)
A shared risk group is a group of items that are likely to be affected by a single fault.
The items therefore share the risk of experiencing the fault.
shelf
A shelf is a mechanical facility that is in general a housing for circuit packs. Shelves are
housed in Bays.
An 1830 PSS-32 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-32 shelf.

signaling transfer point (STP)
A node in a common channel signalling network with the function of transferring

messages from one signalling link to another and considered exclusively from the
viewpoint of the transfer
Simple Network Management Protocol (SNMP)
SNMP is the protocol used to communicate between the 1830 PSS-32 nodes and the
NMS. The SNMP traffic is carried over the 1830 PSS-32 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-26
Glossary
....................................................................................................................................................................................................................................
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-26) for definition.

software control of transmission (SCOT)
System software that controls the settings of EDFA pumps, VOAs, Raman pumps, DCM
pumps, DGEFs, and blockers in the ROADM NEs.
software generic (SW generic)
The whole software and (static) data associated with a particular NE release.
SONET
See Synchronous Optical Network (p. GL-29) for definition.

SONET wavelength service
The SONET wavelength service provides transport of SONET signals through the 1830
PSS-32 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-27
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
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-26) for definition.

SSH
See secure shell (p. GL-25) for definition.

SSMF
See standard single-mode fiber (p. GL-28) for definition.

ST
See straight-tip connector (p. GL-28) for definition.

standard single-mode fiber (SSMF)
This is the most common type of fiber deployed. This fiber was designed to provide zero
chromatic dispersion at 1310 nm, to support the early long-haul transmission systems
operating at this wavelength. It has a chromatic dispersion of at most 20 ps/(nm*km) in
the 1550 nm wavelength range and usually around 17 ps/(nm*km).
static filter, CWDM (SFC)
A static filter card used with a CWDM circuit pack.

static filter, DWDM (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-26) for definition.

straight-tip connector (ST)
Fiber optic connector that uses a bayonet-style coupling rather than a screw-on coupling.
STS, STS-n
See synchronous transport signal-n (p. GL-29) for definition.

Sub-Network Connection Protocol (SNCP)
An SDH version of UPSR. See SDH and UPSR.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-28
Glossary
....................................................................................................................................................................................................................................
SW generic
See software generic (p. GL-27) for definition.

Synchronous Digital Hierarchy (SDH)
A family of digital transmission rates used outside of the U.S. and Japan from 51.84
Mb/s to 40 Gb/s that allows the interconnection of transmission products around the
world.
SDH is the standard technology for synchronous data transmission on optical media. It is
the international equivalent of Synchronous Optical Network (SONET). Both SDH and
SONET technologies provide faster and less costly network interconnection than
traditional 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-30) for definition.

TCP
See Transmission Control Protocol (p. GL-30) for definition.

TCP/IP
A suite of several networking protocols developed for the Internet that provides
communication across interconnected networks, between computers with diverse
hardware architectures and various operating systems. Some examples are FTP, SMTP,
and SNMP.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-29
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
TDM
See time-division multiplexing (p. GL-30) for definition.

Telecommunications Management Network (TMN)
A network that interfaces with a telecommunications network at several points to receive

information from, and to control the operation of, the telecommunications network.
thermal noise
Noise resulting from thermally induced random fluctuation in the receivers 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-29) for definition.

time-division multiplexing (TDM)
A multiplexing technique whereby two or more channels are derived from a transmission
medium by dividing access to the medium into sequential intervals. Each channel has
access to the entire bandwidth of the medium during its interval. This implies that one
transmitter uses one channel to send several bit streams of information.
TL1 (Transaction language 1)
An OS/NE machine-to-machine language. TL1 messages are expressed as ASCII strings.

TL1 messages and syntax are defined by Telecordia.
TMN
See Telecommunications Management Network (p. GL-30) for definition.

TOADM
See tunable optical add/drop multiplexer (p. GL-31) 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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-30
Glossary
....................................................................................................................................................................................................................................
traps (SNMP)
SNMP traps are unacknowledged events sent from an agent to a manager. In a 1830
PSS-32 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-31) for definition.

UL
See Underwriters Laboratories (p. GL-31) for definition.

Underwriters Laboratories (UL)
A U.S. non-profit privately owned and operated product safety testing and certification
organization. Develops standards and test procedures for products, materials,
components, assemblies, tools and equipment, chiefly dealing with product safety.
unidirectional path-switched ring (UPSR)
A survivable, closed loop transport architecture that protects against cable cuts and node
failures by providing duplicate, geographically diverse paths for each service. Adjacent
nodes on the ring are interconnected using a single pair of optical fibers. One fiber
transports traffic in one direction (for example, clockwise), while the second fiber
transports traffic in the opposite direction (for example, counterclockwise). In a UPSR,
the source node bridges its outgoing traffic along opposite directions around the ring (on
paths provided by SONET synchronous transport channels). In contrast to BLSR, a
UPSR:
is path-specific as opposed to line specific
does not allow extra traffic (because traffic is bridged)
requires less coordination from source to destination (because the destination network
element can make all its decisions without involving the source)
UPSR
See unidirectional path-switched ring (p. GL-31) for definition.

user datagram protocol (UDP)
A minimal, datagram-oriented, transport network protocol above the IP network layer

that does not guarantee data ordering or delivery. Because it is datagram-oriented, each
send operation by the application results in the transmission of a single IP datagram.
This contrasts with the Transmission Control Protocol (TCP) which is byte stream
oriented and guarantees the delivery and ordering of the bytes sent. Because it is a byte
stream oriented, a single send operation may result in a no IP datagrams (buffering), a
single IP datagram, or multiple IP datagrams.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-31
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
user services
Services that the network provider can sell to their customers, such as Ethernet service.
UTC
Coordinated universal time.

....................................................................................................................................................................................................................................
variable optical attenuator (VOA)
A device used to set the attenuation of the power received over a fiber to a level
required by the receiving equipment.
VCAT
See virtual concatenation (p. GL-32) for definition.

very short reach (VSR)
A SONET/SDH interface that provides a low-cost interconnection solution of less than

300 meters between routers, switches, and DWDM systems.
virtual concatenation (VCAT)
Defines an inverse multiplexing procedure whereby the contiguous bandwidth is broken

into individual Virtual Containers (VC) at the source transmitter and logically
represented in a Virtual Concatenation Group (VCG). VCG members are transported as
individual VCs across the SONET/SDH network and recombined at the destination VCG
receiver. While contiguous concatenation requires concatenation functionality at each
network element, virtual concatenation do not.
virtual time-slot (VTS)
1830 PSS-1 GBE Edge Device has a fixed assignment of 10 Virtual Time Slots to each
line port.
VOA
See variable optical attenuator (p. GL-32) for definition.

VSR
See very short reach (p. GL-32) for definition.

VTS
See virtual time-slot (p. GL-32) for definition.

....................................................................................................................................................................................................................................
wave division multiplexing (WDM)
WDM merges optical traffic onto one common fiber, sending several signals through one
fiber with different wavelengths of light. WDM allows flexibility in expanding
bandwidth. It reduces costly mux/demux function, and it reuses existing optical
signals.See dense wave division multiplexing (DWDM).
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-32
Glossary
....................................................................................................................................................................................................................................
wave key
A component of the Wavelength Tracker monitoring capability that is used to identify

individual wavelengths through the network.
A wave key is a number between 1 and 2048. Each WDM wavelength in a 1830 PSS-32
network is uniquely identified by a pair of wave keys.
waveguide
A material medium that confines and guides a propagating electromagnetic wave.

waveguide coupler
A coupler that transfers light between planar waveguides.

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-32 which

allows for the tracking of wavelengths through the 1830 PSS-32 network, and for the
measuring of the wavelengths optical power levels at certain points along their paths.
WaveWrapper
WaveWrapper provides network management functions such as optical-layer performance

monitoring, error correction, and ring protection on a per-wavelength basis.
WDM
See wave division multiplexing (p. GL-32) for definition.

WDM demand
The termination points and signal type of a service that is to be carried by the WDM
network.
WDM line
A contiguous series of spans terminated by a ROADM at each end. A WDM line can be
a single span or a series of spans joined by the in-line amplifiers (ILAs).
Web user interface (WebUI)
A computer interface that provides web-based access to the network element (NE).
WebUI
See Web user interface (p. GL-33) for definition.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
GL-33
Issue 2 April 2009
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
XFP (10-gigabit small form factor pluggable module)
A pluggable optical transceiver module that combines transmitter and receiver functions
in one compact, flexible, and low cost package format. Up to sixteen XFP modules can
be arranged on a typical rack card, allowing for an unprecedented level of data density.
XFP is protocol independent, are can support OC-192/STM-64, 10 Gigabit Ethernet, 10
Gigabit Fibre Channel, and G.709 data streams in routers, switches and network cards.
Reaches ranging from Very Short Reach (VSR) to Long Reach (LR) can also be
supported.
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
Issue 2 April 2009
GL-34
Index
A audience
documentation, xi
.............................................................
eye damage, 1-5

safety, 1-4
warning labels, 1-9
B barred-hand symbol, 1-12
.............................................................
.............................................................
N Node Manager
C conventions
documentation, xi, xi
NE Equipment Tree, 3-14

.............................................................
.............................................................
P potential sources of danger, 1-3
D danger, potential sources of,
.............................................................
1-3
documentation
audience, xi
conventions, xi, xi
S safety instructions
electrostatic discharge, 1-11

general notes, 1-3
important, 1-13
.............................................................
laser, 1-4, 1-7
E electrostatic discharge, 1-3,
special, 1-3
1-11
ESD, 1-11
safety precautions (enclosed

systems), 1-7
.............................................................
.............................................................
G ground strap, ESD, 1-11
W warning labels, laser, 1-9
.............................................................
I
information
new with this issue, xi
.............................................................
L lasers
classes, 1-5
....................................................................................................................................................................................................................................
PN 8DG59474 BAAA
IN-1
Issue 2 April 2009

User Provisioning Guide R1.0

Uploaded by

Document Information

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 R1.0

Uploaded by

Copyright:

Available Formats

Proprietary Use pursuant to Company instruction

Proprietary Use pursuant to Company instruction

Interference Information: Part 15 of FCC Rules

Packaging collection and recovery requirements

Structure of safety statements

General notes on safety

Save these safety instructions

User accounts and privileges

Procedures to configure user accounts

System security features

Data communication set-up

Gateway NE (GNE) management

Data communication set-up procedures

Using the WebUI

WebUI start-up procedures

Provisioning system (NE) parameters

Shelf provisioning procedures

Slot/card provisioning procedures

Port provisioning procedures

Description ................................................................................................................................................................................... 5-1

Description ................................................................................................................................................................................... 6-1

Description ................................................................................................................................................................................... 7-1

Description ................................................................................................................................................................................... 8-1

Description ................................................................................................................................................................................... 9-1

Database backup and restore

Database backup/restore procedures

User activity logging

Software upgrade (downgrade)

User privilege levels

Communications Network Sizing

1830 PSS Circuit Pack Slot Allocation

Cards and Ports that Support PM Data

Laser warning labels

Static control wrist strap

ESD warning label (barred-hand symbol)

Dual GNE configurations

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 set-up

Chapter 5, Alarm management

Chapter 6, Performance monitoring

Chapter 11, Routine procedures

About this document

The following typographical conventions are used throughout this document:

Italic is used to identify NE messages

Bold is used to identify WebUI menu selections and button selections.

Alcatel-Lucent 1830 PSS-32 Product Information and

Alcatel-Lucent 1830 PSS-32 Maintenance and

Alcatel-Lucent 1830 PSS-32 CLI Command Guide

Alcatel-Lucent 1830 PSS-32 TL1 Command Guide

Alcatel-Lucent 1830 PSS-32 Safety Guide

Alcatel-Lucent 1830 PSS Engineering and Planning Tool

Alcatel-Lucent 1354 RM-PhM Release 6.1 Photonic

Alcatel-Lucent 1830 PSS-1 GBE Edge Device User Guide

Alcatel-Lucent 1830 PSS-32 Installation and System Turn-up

Alcatel-Lucent 1830 PSS Documentation CD-ROM

About this document

Countries, states, localities, or other jurisdictions may require that systems be

About this document

Moreover, in compliance with legal requirements and contractual agreements, where

To comment on this document, go to the Online Comment Form (http://www.