10 - Manual Do Produto - 1830 PSS 16II

WDM product description 11G Quad-port encryption transponder (11QPEN4)
....................................................................................................................................................................................................................................
Legend:
1 LEDs “STATUS”
2 “VA1”-“VA4” interfaces
3 “L1”-“L4” interfaces
4 “C1”-“C4” interfaces
Visual Indications
For information about the LEDs on the front panel, see “Common LEDs of WDM cards”
(p. 19-12).
Location
The 11QPEN4 can be installed in Alcatel-Lucent 1830 PSS-8 slots 2 to 5, Alcatel-Lucent
1830 PSS-16II slots 3 to 10, Alcatel-Lucent 1830 PSS-16 slots 7 to 9, and Alcatel-Lucent
1830 PSS-32 slots 2 to 17.
Note: When a 11QPEN4 OT is installed in a Alcatel-Lucent 1830 PSS-32 shelf, a
high capacity fan unit (PN: 8DG59606AB) must be installed in the shelf.
....................................................................................................................................................................................................................................
18-448 Alcatel-Lucent 1830 PSS
8DG-62717-HCAA-TQZZA Release 8.2
Issue 1 January 2016
WDM product description 11G-Cost/footprint optimized transponder (12P120)
....................................................................................................................................................................................................................................
11G-Cost/footprint optimized transponder (12P120)

Overview
12P120 is a single-slot, full-height card, designed to increase 10G transport density. This
card is initially supported in Alcatel-Lucent 1830 PSS-32 and Alcatel-Lucent 1830 PSS-8
shelves; it will be supported in additional 1830 shelves like Alcatel-Lucent 1830 PSS-4 in
future release. 12P120 card has 12 programmable ports that in Release 8.0 are organized
as six line XFP and six client SFP+. Additionally six VOA SFP pluggable optics provide
options for Wavetracker encoding and integrated transmit power attenuation. It is also
hardware ready for selective Wavetracker encoding on XL-64TCW on line ports. It will
support E-SNCP/Y-Cable protections in future release. When configured as a six port
transponder, it has equivalent functions as the 11QPA4 card, but with the 50% increased
port density.
12P120 functional description

The 12P120 OT functional block diagram is as shown in the following figure:
Figure 18-160 12P120 block diagram
The 12P120 has 6 x SFP+ ports for 10G client signals, 6 x XFP ports for OTU2/OTU2e
line, and 6 x SFP eVOA ports for line optical power tuning and Wavetracker encoding
with fast eVOA (The WT signals can be selectively modulated onto XL-64TCW XFPs in
future release.). The OTN processor maps incoming 10G client signals into OTU/OTU2e
signals in ingress direction, and demaps OTU2/OTU2e into 10G client signals in egress
direction. It also provides high speed backplane connections to enable OTN XC between
OTs in N+2 slots in future release.
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS 18-449
....................................................................................................................................................................................................................................
The 6 client SFP+ ports can support the following client signal types:
Table 18-71 12P120 client signal types
Client signal Bit rate Standard

10GbE LAN 10.3125 Gb/s 10GbE (IEEE802.3e)
OC-192 9.95328 Gb/s GR-253-CORE
See 1
STM-64 9.95328 Gb/s ITU-T G.707
1
See
OTU2 10.709 Gb/s ITU-T G.709
OTU2e 11.096 Gb/s (overclocked) ITU-T G.709
Notes:
1. STM-64/OC-192 will be supported in future release.
Features
The following features are supported on the 12P120:
• 12P120 supports the following client signal mapping:
– OTU2=>OTU2
– OTU2e=>OTU2e
– 10GbE=>OTU2e
– STM-64/OC-192=>OTU2 (in future release)
– 10GbE=>OTU2 (in future release)
• Supports G.709 digital structure specification and G.798 monitoring, alarming and
consequent actions on OTN configured ports
• Supports DTV on optical line port in DWDM applications
• Supports GCC0 channel over 12x 10G client/line ports
• Supports Terminal and Facility loopbacks for each optical ports
• Supports digital performance monitoring: PCS layer, RMON, SONET/SDH (in future
release), OTUk and ODUk monitoring
• Supports NOFEC/RSFEC/EFEC/EFEC2 at both line side and client side
Note: When provisioned to EFEC or EFEC2, EFEC and EFEC2 should not be mixed
within the 4-port group:
– {C1, C2, C3, C4}
– {C5, C6, L1, L2}
– {L3, L4, L5, L6}
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
• Supports the analog monitoring functions (OPR/OPT) for all XFP/SFP+/VOA ports
• Supports WT encoding and power adjustment on fast VOA port; Hardware ready for
selective WT encoding on XL-64TCW XFP line port (in future release)
12P120 card configurations

The 12P120 card supports various configurations. The following sections describe the
card configurations supported:
Transponder card configuration
12P120 supports DWDM transponder applications for add/drop between client port - line
port, client port-line port OTU2 UNI regeneration, and line port- line port OTU2 NNI
cross-regeneration.
Figure 18-161 12P120 Transponder card configurations
12P120 physical design

The 12P120 is a single-slot full height circuit pack that provides six XFP slots for Line
ports, six SFP+ slots for client ports, and six VA slots for VOA ports.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
There is a bi-color status LED for the pack, and two LEDs for each client SFP+. The Line
XFP port and VOA SFP port have no port-level LEDs.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
12P120 front view
Figure 18-162 12P120 front view
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Legend:
1 Card status LED

2 6 SFP+ Client ports (10GbE/OTU2/OTU2e)
3 6 XFP Line ports (OTU2/OTU2e)
4 6 x VA ports configurable as VOA
Visual indications
For information about the LEDs on the front panel, see “Card Status LED” (p. 19-12).
12P120 pluggable modules

The pluggable modules (SFP+/XFP/VOA) are flush mounted in 12P120 faceplate to
improve user accessibility. See Table 18-24, “12P120 SFP/SFP+/XFPs” (p. 18-107) for
the list of pluggables supported on 12P120.
Location
The 12P120 can be installed in Alcatel-Lucent 1830 PSS-8 slots 2 to 5, and
Alcatel-Lucent 1830 PSS-32 slots 2 to 17.
....................................................................................................................................................................................................................................
WDM product description 20x10G Multirate I/O Module (20P200)
....................................................................................................................................................................................................................................
20x10G Multirate I/O Module (20P200)

Overview
20P200 is a very-high-density 10G anyrate card with 20 SFP+ ports. It is single-slot,
full-height card that acts as the client I/O card to support 1UD200 for 200G uplink
applications. It can also work as a stand-alone 10G transponder card to support 20x10G
add/drop links with ODU switching and grooming capability. With interconnected mates,
it supports up to 40x10G add/drop links.
Features
The 20P200 supports the following features:
• Supports SFP+ optical modules
• Supports the Digital Wrapper parameters (FEC/OTU/ODU) for all OTN signals
• Supports signal round trip (SFP+ optical Rx-->backplane interlocking and it's
opposite direction) latency performance value (no FEC) less than 35µs
• Supports dynamic card level power consumption monitoring function
• Supports RSFEC, EFEC, EFEC2 and NOFEC
Note: When provisioned to EFEC or EFEC2, EFEC and EFEC2 should not be mixed
within the following port groups of 20P200:
– {1,2}
– {3,4,5,6}
– {7,8,9,10}
– {11,12}
– {13,14,15,16}
– {17,18,19,20}
• Supports interworking between 10AN10GB in OCS shelf (PSS-36/PSS-64) for the
following client signal types:
– 10 GbE (GFP-F and CBR mapping)
– OTU2
– OTU2e
Note: 20P200 card is supported in R8.2 only as Muxponder configuration when
paired with one 1UD200 or Add Drop Multiplexer configuration when 20P200 is
paired with two 1UD200 modules (this configuration provides ODU2/2e switching
capability). Stand-alone transponder configuration with 20P200 is not formally
included in R8.1.
Note: GFP-F mapping option of 10GbE LAN is supported in HW but not
implemented in R8.2 SW.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
• Supports as a transponder card or 10G uplink/IO cards, interworking with
10AN10GB E-SNCP link for the following client signals types, in future release:
– OTU2/OTU2e client
– 10 GbE client
– STM-64/OC-192 client
• Supports up to 10x GCC0/1/2 channels over any of the 20 ports
• Supports the OTN Delay measurement function as a source or a destination port, in
future release
• Supports protected client card configuration over the 1UD200 E-SNCP links, in future
release
20P200 physical design

The 20P200 is a single slot wide, full height card with 20 SFP+ ports. The 20 SFP+ ports,
support OC-192/STM-64, 10GbE LAN, OTU2, OTU2e.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
20P200 front view
Figure 18-163 20P200 faceplate
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Legend:
1 Card status LED

2 SFP+ ports 1 to 6
3 SFP+ ports 1 to 6
4 SFP+ ports 7 to 12
Note: The Black/White SFP+ modules with 1.5W maximum power consumption and
maximum 85°C temperature rating can be placed in any of the 20 ports.
The high-power-consumption 2.2W CWDM modules with 85°C temperature rating
have the following placement rules:
• The maximum number is 10.
• Limit to Ports [6 ..10] and Ports [16 ..20], mixed with B/W SFP+ in other ports.
The high-power-consumption 2.2W Tunable DWDM modules with 80°C temperature
rating have the following placement rules:
• The maximum number is 10.
• Limit to Ports [6 ..10] and Ports [16 ..20], mixed with B/W SFP+ in other ports.
20P200 configurations
The 20P200 has the following two configurations:
• 20P200 client-1UD200 uplink
• Two mated 20P200 cards configuration (support in future software release)
The 20P200 provides cross-connects at ODU2, ODU2e, and ODU4 levels. The ODU
cross-connections can use the following connection points:
• OTUODU2/2e NIM and OTUODU2/2e NIM connection (unidirectional or
bidirectional)
• ODU2/2e transparent transport and OTUODU2/2e NIM connection (unidirectional or
bidirectional)
• High Order ODU4 NIM to ODU4 Termination connection (unidirectional or
bidirectional)
Unprotected client + Unprotected line configuration cross-connection model
The following figure shows the Unprotected Client + Unprotected line configuration
cross-connection model.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-164 Unprotected Client + Unprotected line configuration
LO-ODUC SNCP XC Model

The following figure shows the LO-ODUC SNCP XC Model.
Figure 18-165 ODU2(e) SNCP XC model
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
20x10G Multi-Rate I/O card, Client Line muxponder configuration
There are two configuration options when 20P200 Card is supported in pair with 1UD200
as Muxponder configuration.
1. 20x10G to 200G DWDM Line (1UD200 running 200G mode)
2. 10x10G to 100G DWDM Line (1UD200 running 100G)
Muxponder configuration between 20P200 and 1UD200 are supported in adjacent slots.
In this configuration, 20xSFP+ client modules support B&W modules and CWDM and
DWDM.
This configuration supports SFP+ client ports with the following individually
configurable interface types:
• 10GbE
• OTU2, OTU2e
• OC-192/STM64
20P200 and 1UD200 ADM network configuration

For details, see “100G ADM Client/Line configuration with ODU2/2e switching ”
(p. 17-109) and “200G ADM Client/Line configuration with ODU2/2e switching”
(p. 17-113).
20P200 and 1UD200 muxponder network configuration

One pair of 20P200 and one 1UD200 client/line configuration supports the following
configuration:
• 10x10G Clients over OTU4 line (100G Muxponder)
• 20x10G Clients over OTU4x2 line (200G Muxponder)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-166 100G/200G muxponder with 20P200 and 1UD200
The following ODU XCs support 100G muxponder configuration:

• ODU2(e) XC within the 20P200 card. Any 10 port of the 20 ports can be provisioned.
• ODU4 XC between the 20P200 backplane facility and 1UD200 L1CH1.
The following ODU XCs support 200G muxponder configuration:
• ODU2(e) XC within the 20P200 card. Any 20 ports can be provisioned.
• Two ODU4 XCs between the 20P200 backplane facility and 1UD200 L1CH1 and
L1CH2 facilities.
Visual Indications
(p. 19-12).
20P200 pluggable modules

The pluggable modules (SFP+) are flush mounted in 20P200 faceplate to improve user
accessibility. See Table 18-34, “20P200 SFP+s” (p. 18-122) for the list of pluggables
supported on 20P200.
Location
The 20P200 can be installed in Alcatel-Lucent 1830 PSS-8 slots 2 to 5, and
Alcatel-Lucent 1830 PSS-16II slots 3 to 10.
....................................................................................................................................................................................................................................
WDM product description 40G Single line Coherent Gigabit Ethernet with 1 client
(43SCGE1)
....................................................................................................................................................................................................................................
40G Single line Coherent Gigabit Ethernet with 1 client

(43SCGE1)
Introduction
The 43SCGE1 is a three-slot wide, full-height pack for use in Alcatel-Lucent 1830
PSS-32 shelves. The pack can be used in Alcatel-Lucent 1830 PSS-32 shelves. There is
one CFP supported client interface (C1) on the pack. The pack has one (non-pluggable)
line interface (L1). All ports use LC connectors. It is designed to transport one 40GbE
client by mapping/demapping the signal into and from an OTU4 on the line interface for
transmission over the Alcatel-Lucent 1830 PSS system.
The 40GbE client signal is mapped to and from the OTU4 line interface, and the line
interface supports Alcatel-Lucent’s proprietary EFEC. Full OTU4 overhead processing is
supported, which includes:
ODU4 signal:
• Complete G.709 ODU4 overhead termination/generation
• Future support for Tandem Connection Management (6 levels)
OTU4 signal:
• FAS insertion and extraction
• MFAS alignment/insertion
• Alcatel-Lucent EFEC OTU4 encoding
• G.709 scrambling/descrambling
• OTU4 AIS insertion/detection
• Line encoding/decoding
• Error generator
• Future support for GCC0
Operational modes
The 43SCGE1 OT shall support the following operational modes, as shown in the figure
below:
• ADD_DROP mode. In this mode pack is processing signal in both transmission
directions (ingress, from client port towards the DWDM line port and egress, from
DWDM line port to client port).
• REGEN mode. In this mode the DWDM line port input is looped towards the DWDM
line port output.
....................................................................................................................................................................................................................................
(43SCGE1)
....................................................................................................................................................................................................................................
Greyed-out arrows and blocks indicate transmission signals and functional blocks that
will not be processed in this mode of operation. This also means that associated
maintenance and monitoring functions are disabled in this mode, and if the physical layer
source function is not used, the associated transmitter will be permanently turned off.
In REGEN mode, the client port is not used and the pack provides unidirectional
transmission. Two 43SCGE1 OTs would be needed in a regen configuration to support
bi-directional transmission.
Client interface
The client interface is compliant with 40GBASE-LR4 specifications as specified in
IEEE802.3ba-2010, part 3, as supported by the C43G4C CFP.
The C43G4C provides a 40GBASE-LR4 compliant optical interface, XLAUI electrical
interface and MDIO module management interface. It converts 4-lane10 Gb/s electrical
data streams to 4-lane CWDM 10 Gb/s optical output signals in one direction, and
converts 4-lane CWDM 10 Gb/s optical input signals to 4-lane 10 Gb/s electrical data
streams. This 4-lane 10 Gb/s electrical signal is compatible to 802.3ba XLAUI and 4-lane
XFI specifications.
....................................................................................................................................................................................................................................
(43SCGE1)
....................................................................................................................................................................................................................................
Figure 18-167 C43G4C module (4x10 CFP)
The C43G4C client interface supports the following requirements:

• 40GbE applications with up to 10 km spans
• Compliant with application codes C4S1-2D1 and 4l1-9D1F
• Temperature range -5°C to +75°C
• Center CWDM wavelengths: 1271 nm, 1291 nm, 1311 nm and 1331 nm
• Meets Class 1 laser safety requirements of FDA/CDRH, 21 CFR1040.10 and 1040.11.
Also tested and certified as a Class 1 laser product per IEC60825-1:2007 and
IEC60825-1:2001 International standards.
In addition, the C43G4C client interface supports the following system requirements:
• Provides monitoring of per-CWDM lane analog parameters (OPR, OPT) and
detecting loss of optical power dLOS.
• Provides HW/SW control for laser ON/OFF consequent action and Y-cable support.
Note: Y-cable not supported in Release 5.0
For information on C43G4C transmission parameters see “CFP parameters” (p. 22-83)
Line interface
The 43SCGE1 OT uses the same OTU4 line interface as is used in the
43SCGE1/112SNA1 OTs. The interface has the following specifications:
• Line Interface modulation: DP-QPSK
• Line interface bit rate: OTU4 (111.8099736 Gb/s ± 20 ppm)
....................................................................................................................................................................................................................................
(43SCGE1)
....................................................................................................................................................................................................................................
• WaveKey modulation can be applied to the ingress signal
• Symbol rate: 28 Gbaud (symbols/s)
• Chromatic dispersion tolerance (no penalty) ±40000 ps (±40 ns) through electronic
compensation in the line receiver
• DGD tolerance: 90 ps (30 ps mean PMD)
The Line transmitter includes the following functions:
• Tunable laser source, laser driver, thermoelectric cooler, wavelength locker,
Mach-Zender modulators, PLL to generate the output clock rates.
• Laser Frequency controlled to within ±1.5 GHz
• Tunable to any one of 99 wavelengths (50 GHz spacing) in the C-band, from 9605 to,
and including, 9115
• Transmitter output power range: 1 +4 dBm to -20 dBm
• Support for WaveTracker encoder on the Line Interface
The Line receiver module includes the following functions:
• Optical Amplifier, delay line interferometer, differential optical front-end,
drive/control electronics with a high-speed DSP for signal processing. The optical
front-end includes the diode receivers and transimpedance amplifiers, limiting
amplifiers, clock and data recovery device. The DSP operates a coherent receiver
algorithm that provides electronic chromatic dispersion compensation, electronic
differential group delay compensation, and separates the orthogonally polarized
symbols. The DSP also compensates for the local oscillator frequency offset, and
determines the phase of each symbol. Lastly, it executes the receive side
Alcatel-Lucent EFEC algorithm to correct data errors.
• The receive input power range is +5.0 dBm to -21.0 dBm
Line interface optical specifications
See, “Optical fixed line-side WDM OT interfaces” (p. 22-72) for complete optical
specifications for the 43SCGE1.
Transmission path
The following figure depicts the transmission path of the 43SCGE1
....................................................................................................................................................................................................................................
(43SCGE1)
....................................................................................................................................................................................................................................
Figure 18-168 43SCGE1 Transmission path
Line transmit direction details:

• 11 x 11.2 Gb/s signals are converted to 4 x 28 Gb/s
• Quadrature Phase Shift Keying (QPSK) means four symbols, so have 2 bits/symbol
• Dual Polarization (DP) means two symbol streams orthogonally polarized to each
other
• Each polarization carries information at 28 Gbaud (symbols/sec)
Line receive direction details:
• There is an OA in the path to get sufficient power for downstream optical processing
• Coherent Receiver means a local oscillator (ITLA) is split to two coherent mixers that
also have the input signal split. Each generate two orthogonal optical outputs that go
to four photodiodes. The output of the four photodiodes are 2x sampled by a high
speed ADC in a DSP to create two streams of complex numbers at 2x the symbol rate.
At this point, the DSP algorithms:
- Compensate for chromatic dispersion
- Perform polarization demultiplexing and equalization
- Compensate for frequency and phase offsets of the local oscillator
- Complete symbol identification and convert to data bits
- Decode the Alcatel-Lucent EFEC to correct for bit errors
- Pass the corrected data to the Obelix FPGA for further processing
• Polarization Division Multiplex (PDM) means two symbol streams orthogonally
polarized to each other
• Each polarization carries information at 28 Gbaud (symbols/sec)
....................................................................................................................................................................................................................................
(43SCGE1)
....................................................................................................................................................................................................................................
Slot assignment
When installed in the PSS-32 shelf, the 3-slot-wide 43SCGE1 shall be addressed with the
number of the top left-most slot, as viewed from the front of the shelf.
43SCGE1 front view

The following figure provides a front view of the faceplate of the 43SCGE1.
Figure 18-169 43SCGE1 faceplate
Legend:
1 Card status LED
2 Client port Ethernet activity LED (C1 ETH)
....................................................................................................................................................................................................................................
(43SCGE1)
....................................................................................................................................................................................................................................
3 Client port status LED (C1)
4 Line port status LED (L1)

5 Line port interface
6 Client port interface

7 CFP
8 Latches
Note: To support one or more 43SCGE1 OTs installed in a 1830 PSS-32 shelf, a high
capacity fan unit (PN: 8DG59606AB) must be installed in the shelf.
Visual Indications
(p. 19-12).
Location
The 43SCGE1 can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 15.
....................................................................................................................................................................................................................................
WDM product description 43G Single Port Tunable AnyRate Mux - 4 clients (43SCX4,
43SCX4E)
....................................................................................................................................................................................................................................
43G Single Port Tunable AnyRate Mux - 4 clients (43SCX4,

43SCX4E)
Introduction
The 43SCX4 and 43SCX4E are 4x10G MUX OTs with a single 43 Gb/s (OTU3e2 =
44.583355576 Gb/s ± 20 ppm) tunable line port and 4 client ports. They support
multiplexing of up to four 10G client signals into the single OTU3e2 line interface.
The 43SCX4 and 43SCX4E OTs use a Polarization Division Multiplexing NRZ Binary
Phase Shift Keying (PDM NRZ BPSK) pulse format on the line interface. A line side
coherent receiver, combined with a digital signal processor (DSP), provide compensation
of linear transmission impairments (chromatic dispersion, PMD) and reduction of
intra-channel non-linear transmission impairments (Self Phase Modulation [SPM] and
non-linear phase noise).
Physical design
The 43SCX4 is a three-slot wide, full-height pack. The 43SCX4E is a two-slot wide,
full-height pack. The width of the 43SCX4E has been reduced by removing the receive
optical amplifier from the card. Except for this difference, the cards are identical, and can
be referred to as 43SCX4(E). 43SCX4(E) packs are for deployment in the Alcatel-Lucent
1830 PSS-32 shelf. There are four pluggable client interfaces, C1 through C4. The packs
have one (non-pluggable) line interface, L1. They have a single LED that indicates the
status of the card.
Each port has two LEDs: a dedicated port status LED, and an Ethernet activity LED. The
Ethernet activity LED is not utilized on this card.
Line port
The 43SCX4(E) OT has a single line port with line side optics that can be tuned to any of
the 99 wavelengths in the extended C-band, according to the following table:
Range Minimum Maximum

Operating wavelength 1529.163 nm 1568.362 nm
Operating frequency 191.150 THz 196.050 THz
Wavetracker is supported on the line interface for optical power auto-management in

1830 PSS. For the interoperability application with LambdaXtreme, Wavetracker is
turned off.
....................................................................................................................................................................................................................................
43SCX4E)
....................................................................................................................................................................................................................................
Client ports
The 43SCX4(E) has client ports that support up to four XFP pluggable modules to
provide interfaces to client equipment. In the add direction, the line-side signal is timed
from a client-side signal. In the event of client signal failure, the line is timed from an AIS
clock. In the drop direction, the client-side signal is timed from the line-side signal. In the
event of line-side signal failure, the client side signal is timed from the AIS clock.
The 43SCX4(E) OT has 4 client ports that support the following client signal types:

FC800 8.5 Gb/s ANSI INCITS 364-2003
OC-192 9.95328 Gb/s GR-253-CORE
STM-64 9.95328 Gb/s ITU-T G.707
10GbE WAN 9.95328 Gb/s 10GbE (IEEE802.3e)
OTU21 10.709 Gb/s ITU-T G.709
(OTU1e) 11.049 Gb/s (overclocked)
Notes:
1. Using the CLI, the client port can be set to one of the following values: OC-192, STM-64,
10GbE, OTU2 or FC800. When configured for OTN the client port is set to OTU2, and the
OTURATE parameter is configured for either 10.709, 11.049, or 11.096, where 10.709 is
OTU2, 11.049 is OTU1e, and 11.096 is OTU2e.
For details on the specific modules available to support the 43SCX4(E), see Table 18-26,
“43SCX4(E) Client XFPs” (p. 18-111).
Additional transmit and receiver parameters for these cards can be found in “Summarized
specifications for 40G and 100G optical transponders” (p. 22-17).
....................................................................................................................................................................................................................................
43SCX4E)
....................................................................................................................................................................................................................................
43SCX4(E) functional description
Figure 18-170 43SCX4(E) block diagram
Operational modes
The 43SCX4(E) OT supports the following operational modes.
• ADD_DROP: transports client signals to the line side output
• REGEN: puts the pack in regeneration mode, where the OTU3e2 line receive signal is
terminated, regenerated, and sent out the line transmit port. When in REGEN mode,
the client interfaces are not used, and XFP modules do not need to be present.
Protection
The 43SCX4(E) OT has four 10G client ports. It supports up to four Y-cable protection
groups – one for each client port. A protection group forms an association between one
client port on the working OT and one client port on the protection OT. (These are the
two ports connected by the Y-cable.) Switching is performed independently within each
protection group.
The following are protection switch triggers:
• Line OTU3 defects: LOS, LOF, LOM, TIM.
• Line ODU3 defects: AIS, OCI, LCK, TIMODU, PLM.
....................................................................................................................................................................................................................................
43SCX4E)
....................................................................................................................................................................................................................................
• Client 10GBE defects: LOS, LSS, LF, HIBER.
• Client OC192/STM64 defects: LOS, LOF, EBER.
• Client OTU2 defects: LOS, LOF, LOM, TIM.
• Equipment defects: port failed, XFP failed, XFP removed, card failed, card removed.
The 43SCX4E supports Y-cable revertive switching. In revertive switching, the traffic is
automatically switched back to the working line when: Case 1 - the working line has
recovered from the failure, or Case 2 - the User command is cleared. In the failure
recovery case, the switch back to working is delayed until the working line has been
continuously good for the number of minutes specified by the WTR (Wait-To-Restore)
parameter, to avoid oscillation. In the case of clearing a User switch command, there is no
delay.
43SCX4 and 43SCX4E front views

The following figures illustrate the front view of both 43SCX4(E) module variants:
....................................................................................................................................................................................................................................
43SCX4E)
....................................................................................................................................................................................................................................
Figure 18-171 43SCX4 faceplate
....................................................................................................................................................................................................................................
43SCX4E)
....................................................................................................................................................................................................................................
Figure 18-172 43SCX4E faceplate
Legend:
1 Status LED
2 Line port status LED (L1)
3 Line port interface (L1)
4 Client port interfaces (C1 - C4)
5 Client port status LEDs (C1 - C4)
....................................................................................................................................................................................................................................
43SCX4E)
....................................................................................................................................................................................................................................
6 Client port Ethernet activity LEDs (C1 ETH - C4 ETH)
7 Card latches
Visual Indications
(p. 19-12).
Location
The 43SCX4 can be installed in Alcatel-Lucent 1830 PSS-32 slots 2-15.
The 43SCX4E can be installed in Alcatel-Lucent 1830 PSS-32 slots 2-16.
Note: When a 43SCX4 or 43SCX4E OT is installed in a 1830 PSS-32 shelf, a high
capacity fan unit (PN 8DG59606AB) must be installed in the shelf.
....................................................................................................................................................................................................................................
WDM product description 43G Single Port Tunable Mux Transponder - 4 clients
(43STX4, 43STX4P)
....................................................................................................................................................................................................................................
43G Single Port Tunable Mux Transponder - 4 clients (43STX4,

43STX4P)
Introduction
The 43STX4/43STX4P module provides up to four multi-rate and multi-protocol client
interfaces, capable of multiplexing 10GbE, OC-192, STM-64 or G.709 OTU2 client
signal types on to the OTU3 line. The 43STX4 supports DPSK, and the 43STX4P
supports PDPSK modulation on the 40G line. This is the only functional difference
between the modules.
43STX4/43STX4P variances
The 43STX4 and 43STX4P are identical except for the following functionalities:
• The 43STX4 supports DPSK, and the 43STX4P supports PDPSK modulation on the
40G line.
• The 43STX4 line side supports 44 even channels. The 43STX4P, and all other tunable
OTs, support 88 channels. (Traffic from all tunable OTs may traverse both 50 GHz
and 100 GHz systems.)
• 43STX4P includes a NRZ-PDPSK transponder.
• 43STX4P OT supports eVOA management and WT encoding functions.
Line port
On the line side, the 43STX4 OT supports full-band tunable optics, capable of supporting
all 44 even channels (100GHz spacing). The 43STX4P OT supports full-band tunable
optics, capable of supporting all 88 C-band DWDM channels. The frequency of the
channel can be provisioned manually or automatically. It supports standard OTU3
transport overhead access, processing, and maintenance, and is hardware ready to support
GCC communication and Tandem Connection Monitoring in a future Release.
The 43STX4 OT line side receiver includes its own Optical Amplifier (OA), Tunable
Dispersion Compensator (TDC), Delay Line Interferometer (DLI), and differential
front-end and drive/control electronics. The TDC allows the 43STX4 OT to be deployed
in 1830 networks designed with Engineering Rules for 10G interfaces. Tunable dispersion
compensation, with a tuning range of -100 ps/nm to +1000 ps/nm, is implemented on a
per-channel basis. (Every 43STX4 OT has a TDC for its optical channel.) The OT uses
feedback from the uncorrected bit error rate to tune the TDC to an optimum value.
Client ports
The following client signals are supported.
• OC192/STM64 (nominal bit rate: 9.9532 Gb/s [±20ppm])
....................................................................................................................................................................................................................................
(43STX4, 43STX4P)
....................................................................................................................................................................................................................................
Full SONET/SDH maintenance capabilities are supported when the client signal type
is provisioned to OC192/STM64.
• OTU2 (nominal bit rate: 10.709 Gb/s [±20ppm])
Full OTUk section maintenance, including FEC provisioning for Reed Solomon FEC
(RSFEC) or no FEC (NOFEC) is supported when the client signal type is provisioned
to OTU2.
• 10GbE (nominal bit rate: 10.3125 Gb/s [IEEE 802.3ae])
Up to 4 independent client signals can be multiplexed and sent out on the line side. Any
combination of client signals is supported.
43STX4/43STX4P functional description

The 43STX4/43STX4P module is a full-height, 3-slot wide card the primary components
of this OT are shown in the following illustration.
Figure 18-173 43STX4/43STX4P OT block diagram
....................................................................................................................................................................................................................................
(43STX4, 43STX4P)
....................................................................................................................................................................................................................................
Within the 43STX4/43STX4P OT, a Multichannel Packet Mapper provides bi-directional
transmission and maintenance functions. In the ingress direction, the mapper receives two
independently timed signals. These signals can be either 10GbE LAN, OTU2, or
OC-192/STM-64. The Demux/mux maps incoming 10G signals into an
OPU3/ODU3/OTU3 structure in the following ways:
• 10GbE LAN clients: The four ODU2 signals from the mapper are multiplexed into
the ODU3 payload.
• OTU2 clients: RS-FEC coding/decoding are performed and the OTU2 overhead is
terminated. Then the four ODU2 signals are multiplexed into the ODU3 payload. A
non-intrusive ODU2 monitoring function is also performed in both the ingress and
egress directions.
• OC-192/STM-64 clients: The Demux/mux maps the client into the ODU2 frame with
either bit-synchronous or asynchronous CBR mapping. Then, it multiplexes the four
OUD2 signals into the ODU3 signal. An FPGA provides the forward error correcting
code and the interface to the line. The FPGA adds the Alcatel-Lucent proprietary
Enhanced FEC (EFEC).
For all types of 10G signals, the mapper acts as a serializer/deserializer, converting the
serial 10G into parallel SFI-5 interfaces.
Facility loopback and terminal loopback functions are supported at both client and line
ports.
43STX4/43STX4P front view

The following figures provides and illustration of the front view of the faceplate of the
43STX4/STX4P.
....................................................................................................................................................................................................................................
(43STX4, 43STX4P)
....................................................................................................................................................................................................................................
Figure 18-174 43STX4/43STX4P OT faceplate
Legend:
1 LEDs “STATUS”
2 “L1” interface
4 LEDs “L1”
....................................................................................................................................................................................................................................
(43STX4, 43STX4P)
....................................................................................................................................................................................................................................
5 LEDs “C1”-“C4”
For information identifying the PTMs supported on client interfaces of this OT, see Table
18-25, “43STX4(P) XFPs” (p. 18-110).
Visual Indications
(p. 19-12).
Location
The 43STX4/STX4P can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 15.
....................................................................................................................................................................................................................................
WDM product description 43G Single Port Tunable AnyRate Transponder - 1 client
(43STA1P)
....................................................................................................................................................................................................................................
43G Single Port Tunable AnyRate Transponder - 1 client

(43STA1P)
Overview
The 43STA1P is 43G Single Port Tunable AnyRate Add/Drop Transponder supported on
the Alcatel-Lucent 1830 PSS-32 in this release. It contains transmit and receive optics as
well as multiplexer, driver, clock/data recovery, demultiplexer, and control functionality.
The 43STA1P accepts a single OC-768/STM-256 client signal and an OTU3 Line
interface with full-band tunable optics. The line interface can be used to select any one of
88 channels (50 GHz spacing). Channel frequency can be provisioned automatically or
manually.
Note: An enhanced version, 43STA1PB, was introduced in Release 3.0 with the same
functionality.
Physical design
The 43STA1P is a 3-slot wide, full height 43G Single Port Tunable AnyRate Add/Drop
Transponder, illustrated in the following figure.
Line port
The 43STA1P pack supports transport in the C-band.
The following signals are supported on the line side:
• OTU3
– 43.018413 Gb/s, (±20 ppm)
– Full-band tunable optics
– P-DPSK modulation
– Supports colorless tunable dispersion compensation
– Wavelength Tracker encoding on line transmit
– Supports Ultra FEC (UFEC). See “FEC” (p. 18-483).
Client ports
The following signals are supported on the client side:
• OTU3 - 43.018413 Gb/s, (±20 ppm)
• OC-768/STM-256 - 39.8132 Gb/s (±20 ppm)
Note: The 43STA1P supports single channel regeneration for DWDM-DWDM and
CWDM-DWDM connections. CWDM-CWDM regeneration is not supported. For
regeneration, the client port rate must be OC-768/STM-256.
....................................................................................................................................................................................................................................
(43STA1P)
....................................................................................................................................................................................................................................
The client signal is transported as a Constant Bit Rate (CBR) signal, which is transparent
to the client bit stream and timing.
43STA1P functional description

The client interface is a fixed transponder. It contains transmit and receive optics as well
as multiplexer, driver, clock/data recovery, demultiplexer, and control functionality.
The pack supports ADD_DROP mode. In this mode, the OT processes the signal in the
ingress direction from client port towards the DWDM line port, and in the egress
direction from the DWDM line port to the client port.
Figure 18-175 43STA1P Block Diagram
In the ingress (add path) direction, received client data is converted to SFI-5 format and
sent to the UFEC. SONET/SDH overhead is processed, or the OTU3 format is passed.
The FPGA controls the client transponder, the line daughter board, and the UFEC device.
The UFEC then applies Ultra-FEC code and the pre-coding required for the PDPSK
format used at the line interface. The data is then sent to the line transmitter and
WaveTracker encoder. The line-side transmitter (TX on the line daughter board in the
figure), contains an 88-channel tunable laser module and a Modulator.
....................................................................................................................................................................................................................................
(43STA1P)
....................................................................................................................................................................................................................................
In the egress (drop path) direction, data received at the line receiver is passed to the
UFEC which terminates the UFEC code and processes the OTU3 overhead. The UFEC
also generates SONET/SDH overhead if required. The line-side receiver (shown as RX on
the line daughter board in the figure), contains a tunable dispersion compensator (TDC), a
delay line interferometer (DLI), and a differential optical front end (OFE). Due to the
insertion losses of these components, an optical amplifier (OA) is required on the pack.
FEC
On the line side interface, the 43STA1P supports an OTU3 signal with Ultra FEC
(UFEC).
UFEC is an FEC format that is based on the LDPC code given in Appendix I.6 of ITU-T
G.975.1. UFEC can provide a net coding gain of more than 8 dB OSNR at a BER of
E-16, for improved engineering rules.
The OT does not support FEC on the client interface when provisioned for a signal type
of OTU3. When the client is provisioned to OTU3, the FEC bytes pass to the line
interface without processing.
Protection
The 43STA1P supports Y-cable protection, but not OPS. Although there is no software
denial of protection group creation, Y-cable protection cannot be used with an OTU3
(OTM0.3) client. (The ODU3 layer is handled transparently, APS/PCC bytes are not
available for protection signaling.)
43STA1P front View

The following figure illustrates a front view of the faceplate of the 43STA1P.
....................................................................................................................................................................................................................................
(43STA1P)
....................................................................................................................................................................................................................................
Figure 18-176 43STA1P faceplate
Legend:
1 LEDs “STATUS”
....................................................................................................................................................................................................................................
(43STA1P)
....................................................................................................................................................................................................................................
3 “C1” interface
4 LEDs “C1”
5 LEDs “L1”
Visual Indications
For information about the LEDs on the front panel, see “Card Status LED” (p. 19-12) and
“Port Status LED” (p. 19-12).
Location
The 43STA1P can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 15.
....................................................................................................................................................................................................................................
WDM product description 43G Single Port Tunable Coherent AnyRate Transponder - 1
client (43SCA1)
....................................................................................................................................................................................................................................
43G Single Port Tunable Coherent AnyRate Transponder - 1

client (43SCA1)
Overview
The 43STA1P is 43 Gb/s single port tunable AnyRate coherent Add/Drop optical
transponder supported on the Alcatel-Lucent 1830 PSS-32. It contains transmit and
receive optics as well as multiplexer, driver, clock/data recovery, demultiplexer, and
control functionality. The line side optics of the 43SCA1 OT can be tuned to any of the 88
wavelengths in the C-band. The client interface supports fixed, short reach optics,
according to application code VSR2000-3R2/3/5 in ITU-T G.693. The 43SCA1 OT
supports STM-256/OC-768 client interfaces. The Wavetracker encoder is supported on
the line interface for optical power auto-management. The 43SCA1 OT is a three slot
wide, full height circuit pack supported on the Alcatel-Lucent 1830 PSS-36 and
Alcatel-Lucent 1830 PSS-32 shelf.
Physical design
The 43SCA1 is a three slot wide, full height pack. The pack is intended for deployment in
the Alcatel-Lucent 1830 PSS-32 shelf. There is one pluggable client interface: C1, and
one (non-pluggable) line interface: L1. The card has one status LED and each port has a
dedicated port status LED.
The 43SCA1 accepts a single OC-768/STM-256 client signal and an OTU3 Line interface
with full-band tunable optics. The line interface can be used to select any one of 88
channels (50 GHz spacing). Channel frequency can be provisioned automatically or
manually.
Line interface
The line side optics of the 43SCA1 OT can be tuned to any of the 99 wavelengths in the
extended C-band, according to the following table:
Table 18-72 Line interface range
Range Minimum Maximum

Operating wavelength 1529.163 nm 1568.362 nm
Operating frequency 191.150 THz 196.050 THz
....................................................................................................................................................................................................................................
client (43SCA1)
....................................................................................................................................................................................................................................
Client interface
The following client signal types are supported:
Table 18-73 Client signal supported

OC-768 39.813 Gb/s GR-253-CORE
STM-256 39.813 Gb/s ITU-T G.707
OTU3 43.018 Gb/s ITU-T G.709
43SCA1 functional description

The 43SCA1 OT supports one client port and one, single OTU3 line interface. This pack
is referred to as a “40G Add/Drop” or more simply “40G A/D” OT.
The 43SCA1 OT, like the 43SCX4, uses a pulse format with Polarization Division
Multiplexing NRZ Binary Phase Shift Keying (PDM NRZ BPSK) on the line interface. It
has a line side coherent receiver, combined with a digital signal processor (DSP), that
provide compensation for linear transmission impairments (chromatic dispersion, PMD)
and reduction of intra-channel non-linear transmission impairments (Self Phase
Modulation (SPM) and non-linear phase noise).
The client interface is a fixed transponder. It contains transmit and receive optics as well
as multiplexer, driver, clock/data recovery, demultiplexer, and control functionality.
....................................................................................................................................................................................................................................
client (43SCA1)
....................................................................................................................................................................................................................................
Figure 18-177 43SCA1 Block Diagram
FEC
On the line side interface, the 43SCA1 supports an OTU3 signal with a FEC type on the
facility of afec.
On the client interface, when provisioned for a signal type of OTU3. the FEC type on the
facility can be rsfec or nofec. Default is rsfec.
Operational modes
The card “Mode” parameter determines the feature type of the 43SCA1. It affects many
fundamental aspects of card and port behavior, including which client signal types are
supported.
The pack supports two card modes:
• SonetSdh (default: covers STM-256 and OC-768)
• OTU3
When the card mode is set to “SonetSdh,” STM-256 and OC-768 are the only client
signal types supported. STM-256 and OC-768 commands apply to 43SCA1 only in this
card mode. TL1 and CLI commands specific to other client signal types will be denied.
Line ports are created automatically.
....................................................................................................................................................................................................................................
client (43SCA1)
....................................................................................................................................................................................................................................
When the card mode is set to “Otu3,” OTU3 is the only client signal type supported.
OTU3 commands apply to 43SCA1 only in this card mode. Details are specified in
following sections.
Loopback behavior
43SCA1 Line terminal or facility loopbacks do not provide “loopback & continue”
behavior. As a result, the far-end line or/and client locations will indicate standing alarm
conditions during loopback. This applies to services with or without Regen between
end-to-end traffic.
43SCA1 front view

The following figures provides an illustration of a front view of the faceplate of the
43SCA1.
....................................................................................................................................................................................................................................
client (43SCA1)
....................................................................................................................................................................................................................................
Figure 18-178 43CSA1 faceplate
Legend:
1 LEDs “STATUS”
....................................................................................................................................................................................................................................
client (43SCA1)
....................................................................................................................................................................................................................................
4 LEDs “C1 ETH”

5 LEDs “C1”
6 LEDs “L1”
Visual Indications
(p. 19-12).
Location
The 43CSA1 can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 15.
....................................................................................................................................................................................................................................
WDM product description 112G Single Port Tunable Coherent Mux Transponder - 10
clients (112SCX10, 112SNX10)
....................................................................................................................................................................................................................................
112G Single Port Tunable Coherent Mux Transponder - 10

Overview
The 112SCX10 and 112SNX10 OTs support one line interface (non-pluggable) and ten
client interfaces with XFP modules (B&W, CWDM). The line side optics of the
112SCX10 and 112SNX10 OT can be tuned to utilize all 88 channels in the C-band. The
112SNX10 provides improved optics components that provide 15.2 dB OSNR, improved
from 16.2 dB supported on 112SCX10.
Note: To support one or more 100Gb/s coherent Add/Drop OTs and/or 10x10Gb/s
coherent Muxponder OTs installed in a 1830 PSS-32 shelf, a high capacity fan unit
(PN 8DG59606AB) must be installed in the shelf.
Physical design
The 112SCX10 and 112SNX10 OTs are three-slot wide, full-height packs, that support
multiplexing of up to ten 10G client signals into one OTU4 line interface. The 112SCX10
and 112SNX10 support one line interface (non-pluggable) and ten client interfaces with
XFP modules (B&W, CWDM). The line side optics of the 112SCX10 and 112SNX10 OT
can be tuned to utilize all 88 channels in the C-band. The 112SNX10 provides improved
optics components that provide 15.2 dB OSNR, improved from 16.2 dB supported on
112SCX10. Each port has a dedicated port status LED and a dynamic Ethernet activity
LED. When Ethernet data is transmitted or received, the LED blinks Green. When no
Ethernet data is moving (idle), the LED is off.
Note: The Ethernet activity LED is used only when the port is provisioned with an
Ethernet signal type.
112SCX10/112SNX10 functional description

The following illustration shows a block diagram of the 112SCX10/112SNX10 OT.
The 112SCX10/112SNX10 provides client access through up to ten XFP modules (B &
W, CWDM). Short, long, and extended reach XFP modules are supported. Client signal
processing includes Status, Alarms, PM, FEC, pre-mapping of the client signal into
p-ODTU24.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-179 112SCX10/112SNX10 OT block diagram
The 112SCX10/112SNX10 OT supports the following functional features:

• Facility and Terminal Loopbacks, Optical Performance Monitoring (OPR, OPT),
Digital Performance Monitoring (RMON, SONET/SDH, OTN - Client Side,
OTUk/ODUk Monitoring – Line Side)
• Hardware ready to support full ITU-T G.709 functionality, including GCC0 and TCM
• Line side supports the following features:
– DP-QPSK modulation (Dual Polarization Quadrature Phase Shift Keying)
– Line side coherent receiver, combined with a DSP to compensate for linear
transmission impairments (CD & PMD) and mitigate non-linear impairments
(SPM and non-linear phase noise)
– OTU4 facility and terminal loopbacks
– Support Alcatel-Lucent Enhanced FEC (~9.2 dB coding gain at 1E-15 for ~7-%
overhead)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
– OSNR: 16.2 db (112SCX10), 15.2 dB (112SNX10)
– Wavelength tracker supporting optical power auto-management. User
configurable option to disable the WT for the interoperability application with
other systems without WT
• Client side supports the following features:
– Standard FEC (RS-FEC)
– Supports OC-192/STM-64, 10 GbE, 8G FC, OTU1e and OTU22 client interfaces
– OC-192, OTU2, 10GbE facility and terminal loopbacks
Optical interfaces
The 112SCX10/112SNX10 supports both B&W XFPs for single-channel applications and
CWDM XFPs for multiple channel applications (up to eight channels).
Client XFPs
The 112SCX10/112SNX10 OT supports the following types of client XFPs:
• 10GB-SR (B & W, 850 nm, 10G BASE-SR)
• 10GB-ZR (B & W, 10 GBE)
• L64.2 (B & W)
• XI-64.1
• XS-64.2b
• XS-64.2c
• XL-64.2c
For more details about the XFPs available for the 112SCX10 and 112SNX10, including
ordering information, see Table 18-30, “112SCX10, 112SNX10, 130SCX10, and
130SNX10 Client XFPs” (p. 18-116).
Client signal types
The 112SCX10/112SNX10 supports the following client signal types.
Client signal type Operating bit rate Standard

OC-192 9.95328 Gb/s GR-253-CORE
STM-64 9.95328 Gb/s ITU-T G.707
1
OTU2 10.709 Gb/s ITU-T G.709
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Notes:
10GbE, OTU2 or FC800. When configured for OTN the client port is set to OTU2, and the
For more details about the XFPs available for the 130SNX10, including ordering
information, see Table 18-30, “112SCX10, 112SNX10, 130SCX10, and 130SNX10
Client XFPs” (p. 18-116).
112SCX10/112SNX10 front view

The following figure illustrates a front view of the faceplate of the
112SCX10/112SNX10.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-180 112SCX10/112SNX10 faceplate
Legend:
1 LEDs “L1”
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2 LEDs “CARD”
Visual Indications
(p. 19-12).
Location
The 112SCX10/112SNX10 can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 15.
....................................................................................................................................................................................................................................
clients (130SCX10)
....................................................................................................................................................................................................................................

clients (130SCX10)
Overview
The 130SCX10 is a second generation 10x10G MUX optical transponder, which supports
multiplexing of upto ten 10G client signals into one single OTU4 line interface. The
130SCX10 card features Alcatel-Lucent Soft Decision FEC (SD-FEC) as a user
provisionable option. Alcatel-Lucent Soft Decision FEC is a Proprietary 23% overhead
FEC providing higher error correction performance than hard-decision FEC's. SD-FEC
provides more net coding gain (11.2 dB) than previous generation FEC offered on first
generation 100G cards, which used AFEC. Although the pack is known as a “100G” pack,
the actual line rate is either 130 Gb/s (with SD-FEC) or 112 Gb/s (with AFEC).
Physical design
The 130SCX10 OT is a two-slot-wide full-height pack. The 130SCX10 supports one
bi-directional optical line interface port (L1). The line port uses fixed, non-pluggable
optics and an LC connector. It also supports ten client interfaces with XFP modules
(B&W, CWDM). The 130SCX10 card contains two LEDs, a card status LED and the line
interface LED. Each client port has a dedicated port status LED and an Ethernet LED.
The Ethernet LEDs are not utilized on this card. The behavior of the utilized LEDs is
described in, “Common LEDs of WDM cards” (p. 19-12).
130SCX10 functional description

The following illustration shows a block diagram of the 130SCX10 OT.
The 130SCX10 provides client access through up to ten XFP modules (B & W, CWDM).
Short, long, and extended reach XFP modules are supported. Client signal processing
includes Status, Alarms, PM, FEC, and pre-mapping of the client signal.
....................................................................................................................................................................................................................................
clients (130SCX10)
....................................................................................................................................................................................................................................
Figure 18-181 130SCX10 OT block diagram
Line interface
The 130SCX10 has a tunable coherent non-pluggable optical interface. The line bit rate is
OTU4 (129.280281 Gb/s ± 20 ppm) when provisioned for SD-FEC mode, and OTU4
(111.8099736 Gb/s ± 20 ppm) when provisioned for AFEC mode. See “Optical fixed
line-side WDM OT interfaces” (p. 22-72), for the full specification details of the
130SCX10 line interface.
Client interfaces
The 130SCX10 OT supports client XFPs that support the following client interfaces:
• STM-64/OC-192
• 10G LAN PHY
• OTM-0.2
• FC-800 (Fibre channel)
For more details about the XFPs available for the 130SCX10, including ordering
....................................................................................................................................................................................................................................
clients (130SCX10)
....................................................................................................................................................................................................................................
The 130SCX10 supports the following client signal types.
Table 18-74 130SCX10 Client signal types

10 GbE LAN 10.3125 Gb/s 10 GbE (IEEE802.3e)
OC-192 9.95328 Gb/s GR-253-CORE
STM-64 9.95328 Gb/s ITU-T G.707
10 GbE WAN 9.95328 Gb/s 10 GbE (IEEE802.3e)
1
OTU2 10.709 Gb/s ITU-T G.709
Notes:
10 GbE, OTU2 or FC800. When configured for OTN the client port is set to OTU2, and the
130SCX10 front view

The following figure illustrates a front view of the faceplate of the 130SCX10.
....................................................................................................................................................................................................................................
clients (130SCX10)
....................................................................................................................................................................................................................................
Legend:
1 LEDs “L1”
2 LEDs “CARD”
....................................................................................................................................................................................................................................
clients (130SCX10)
....................................................................................................................................................................................................................................
14 Card latch
Visual Indications
(p. 19-12).
Location
The 130SCX10 can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 16 and
Note: To support one or more 100 Gb/s coherent Add/Drop OTs and/or 10x10 Gb/s
coherent Muxponder OTs installed in a Alcatel-Lucent 1830 PSS-32 shelf, a high
capacity fan unit (PN: 8DG59606AB) must be installed in the shelf.
Application: Using Eight 130SCX10 cards in a Alcatel-Lucent 1830 PSS-32 shelf

The Alcatel-Lucent 1830 PSS-32 shelf can support up to eight 130SCX10 cards plus
common equipment assuming typical power consumption for all cards. Prudent
engineering practice demands some margin to accommodate component and
environmental variation. In this application note we describe the steps necessary to
operate eight 130SCX10 cards (or their equivalent) in a Alcatel-Lucent 1830 PSS-32 shelf
and the restriction imposed by that configuration on office supply voltage.
Important! If the magnitude of the office voltage at interface A (the point of
connection to the supply) falls below 44 V and one of the shelf power filters fails, the
circuit breakers on the power modules may disconnect the shelf from the main power
to protect the service wiring. Under some worse case scenarios this shelf
configuration will draw more than 70 A when the magnitude of the voltage falls below
44 V.
Note: Service wiring must be of sufficient gauge to carry more than 70 A to meet the
electrical code and UL standards.
Eight of these cards deployed in a Alcatel-Lucent 1830 PSS-32 dissipate 2640 W. This is
in addition to the shelf infrastructure of two EC cards + two PFDC70 + FAN32H +
USRPNL (if this is a single shelf system) = 3007 W The total load is greater than the
....................................................................................................................................................................................................................................
clients (130SCX10)
....................................................................................................................................................................................................................................
2730 W capacity of the power supply for the shelf which is limited to 70 A per side by the
circuit breakers on the highest capacity power entry modules available. The minimum
voltage magnitude is -39.0 V measured at the power filter card – that is where the low
voltage cut-off circuitry disconnects the system from the battery plant. When a circuit
breaker is tripped, manual intervention is needed to reset it and the system will not
recover unattended when the low voltage condition is over.
Up to seven cards can be used without any configuration changes even under worse case
conditions. Before the eighth card is inserted into the shelf certain reconfiguration steps
need to be taken to permit the eighth card to operate properly without unnecessary alarms
or put the user at elevated risk of losing some or all traffic in a shelf.
The important constraint is that the user of this configuration must guarantee that the
input voltage to the network element at interface A not fall below 44 V in magnitude
relative to the return at interface A (battery voltage is negative relative to the return).
“Interface A” is the point at which the power leads are fastened to the power entry
modules. Voltage can be measured at faceplate test points, and is measured by the system
by data acquisition at an equivalent internal location.
Since this will most likely be a multi-shelf system do not deploy the eight high power
consumption cards in the master shelf. This will allow the system to continue partial
operation and connection with the network operating system even when the office voltage
falls below what is required to support the load of the shelf full of Optical Transponders.
Note: In multi-shelf systems, the shelf requiring the floor voltage above the minimum
operating voltage should not be the master shelf of the network element to prevent
loss of all operations under low voltage conditions.
Protection
The 130SCX10 supports Y-cable revertive switching. In revertive switching, the traffic is
automatically switched back to the working line when: Case 1 - the working line has
recovered from the failure, or Case 2 - the User command is cleared. In the failure
recovery case, the switch back to working is delayed until the working line has been
continuously good for the number of minutes specified by the WTR (Wait-To-Restore)
parameter, to avoid oscillation. In the case of clearing a User switch command, there is no
delay.
The Y-cable revertive switching can be provisioned through CLI or WebUI interface.
....................................................................................................................................................................................................................................
clients (130SNX10)
....................................................................................................................................................................................................................................

clients (130SNX10)
Overview
The 130SNX10 is a second generation 10x10G MUX optical transponder, which supports
multiplexing of up to ten 10G client signals into one single OTU4 line interface. The
130SNX10 card features Alcatel-Lucent Soft Decision FEC (SD-FEC) as a user
provisionable option. Alcatel-Lucent Soft Decision FEC is a proprietary 23% overhead
FEC providing higher error correction performance than hard-decision FEC's. Compared
to the 130SCX10 card, the 130SNX10 features a modified transmit line interface for
improved transmission performance. Although the pack is known as a “100G” pack, the
actual line rate is either 130 Gb/s (with SD-FEC) or 112 Gb/s (with AFEC).
For interworking with first generation cards, the 130SNX10 can be provisioned for
AFEC.
Physical design
The 130SNX10 OT is a two-slot-wide full-height pack. The 130SNX10 supports one
optics and an LC connector. It also supports ten client interfaces with XFP modules
(B&W, CWDM). The 130SNX10 card contains two LEDs, a card status LED and one
line interface LED for each of the ten client ports. The behavior of the utilized LEDs is
described in, “Common LEDs of WDM cards” (p. 19-12).
130SNX10 functional description

The following illustration shows a block diagram of the 130SNX10 OT.
The 130SNX10 provides client access through up to ten XFP modules (B & W, CWDM).
Short, long, and extended reach XFP modules are supported. Client signal processing
includes Status, Alarms, PM, FEC, and pre-mapping of the client signal.
....................................................................................................................................................................................................................................
clients (130SNX10)
....................................................................................................................................................................................................................................
Figure 18-183 130SNX10 OT block diagram
The 130SNX10 has a tunable coherent non-pluggable optical interface. The line bit rate is
(111.8099736 Gb/s ± 20 ppm) when provisioned for AFEC mode
Line interface
The 130SNX10 has a tunable coherent non-pluggable optical interface. The line bit rate is
(111.8099736 Gb/s ± 20 ppm) when provisioned for AFEC mode. See “Optical fixed
line-side WDM OT interfaces” (p. 22-72), for the full specification details of the
130SNX10 line interface.
Client interfaces
The 130SNX10 supports the following client signal types.

....................................................................................................................................................................................................................................
clients (130SNX10)
....................................................................................................................................................................................................................................

OC-192 9.95328 Gb/s GR-253-CORE
STM-64 9.95328 Gb/s ITU-T G.707
OTU21 10.709 Gb/s ITU-T G.709
Notes:
10 GbE, OTU2 or FC800. When configured for OTN the client port is set to OTU2, and the
For more details about the XFPs available for the 130SNX10, including ordering
130SNX10 front view

The following figure illustrates a front view of the faceplate of the 130SNX10.
....................................................................................................................................................................................................................................
clients (130SNX10)
....................................................................................................................................................................................................................................
Figure 18-184 130SNX10 faceplate
Legend:
1 LEDs “L1”
2 LEDs “CARD”
....................................................................................................................................................................................................................................
clients (130SNX10)
....................................................................................................................................................................................................................................
14 Card latch
Visual Indications
(p. 19-12).
Location
The 130SNX10 can be installed in Alcatel-Lucent 1830 PSS-8 slots 2 to 4 and
Note: To support one or more 100 Gb/s coherent Add/Drop OTs and/or 10x10 Gb/s
coherent Muxponder OTs installed in a Alcatel-Lucent 1830 PSS-32, a high capacity
fan unit (PN: 8DG59606AB) must be installed in the shelf.
....................................................................................................................................................................................................................................
WDM product description 130G Single Port Tunable Coherent AnyRate Transponder – 1
client (130SCA1)
....................................................................................................................................................................................................................................
130G Single Port Tunable Coherent AnyRate Transponder – 1

client (130SCA1)
Overview
The 130SCA1 is a two-slot wide 100G Add/Drop Optical Transponder card supported in
the Alcatel-Lucent 1830 PSS-32. The 130SCA1 card offers improved transmission
performance through a configurable Soft Decision Forward Error Correction (SDFEC)
line interface.
Note: The TL1 interface is not supported on the 130SCA1 card.
Card mnemonic
The following table specifies the Card mnemonic.
Table 18-75 130SCA1 card mnemonic
130 Represents the maximum total line carrier rate (130 Gb/s)
S Single tunable line port (L1) supporting 100G of transport capacity
C Coherent. This card features a coherent transceiver on the line interface.
A Anyrate. In R8.2, the 130SCA1 supports either a 100GbE client or an
OTU4 client.
1 1 client port (C1)
Note: Although the card is known as a “100G” card, the actual line rate is either 130
Gb/s (when SDFEC is provisioned) or 112 Gb/s (when AFEC is provisioned).
The behavior of the utilized LEDs is described in, “Common LEDs of WDM cards”
(p. 19-12).
Physical design
The 130SCA1 optical transponder is a two-slot wide, full-height card. It supports one
CFP pluggable module on the client interface, and one OTU4 line interface
(non-pluggable).
130SCA1 features
The 130SCA1 supports the following features:
• Support for 100 GbE client signal type (100GBASE-LR4 and 100GBASE-SR10
applications, depending on the CFP pluggable used)
• Configurable option for Soft-Decision FEC (SDFEC) or hard-decision FEC (AFEC)
on the DWDM line interface
....................................................................................................................................................................................................................................
client (130SCA1)
....................................................................................................................................................................................................................................
• Analog (OCH layer) and Digital (PCS layer, RMON statistics) performance
monitoring
• Regeneration operation mode
• OPSB client side protection implementing O-SNCP
• Standard Loopback capabilities for testing purposes
• Full Line interface wavelength tunability (88 channels) and WaveTracker support
• Supports a test signal generator. Refer to the Alcatel-Lucent 1830 Photonic Service
Switch (PSS) Release 8.2 User Provisioning Guide and see the procedure “Test Signal
Loopback”.
In the current Release, the following additional features are supported on 130SCA1 card:
• Support on PSS-8, PSS-16II and PSS-32 shelves
• Supports OTU4 client
The following CFP pluggable modules are supported on the client interface port of the
130SCA1 when the client port is provisioned to OTU4:
– c113g4cd (100GBASE-LR4, dual rate 100GbE/OTU4)
– AUTO, USER
The OTU4 client interface on the 130SCA1 card supports the following PM groups:
– DW
– LanePwrs
– OPR
– OPT
• Supports interworking with 112SCA1/112SNA1 and 260SCX2 cards with OTU4 and
100GbE clients
• Supports 1+1 protection through the OPSA card.
• Supports OSNCP interworking through the OPSB card in networks with 112SNA1
and 130SCA1 cards
130SCA1 front view

The following figure illustrates a front view of the faceplate of the 130SCA1.
....................................................................................................................................................................................................................................
client (130SCA1)
....................................................................................................................................................................................................................................
Figure 18-185 130SCA1 faceplate
....................................................................................................................................................................................................................................
client (130SCA1)
....................................................................................................................................................................................................................................
Legend:
1 Card “Status” LED
3 “C1 ETH” LED (unused)
4 “C1” port status LED

5 “L1” port status interface
6 “C1” interface (CFP pluggable)
130SCA1 functional description

The following illustration shows a block diagram with a CFP.
Figure 18-186 130SCA1 OT block diagram
Line interface
The 130SCA1 has a tunable coherent non-pluggable optical interface. The line bit rate is
(111.8099736 Gb/s ± 20 ppm) when provisioned for AFEC mode. Refer to “100G/200G
transmitter specifications” (p. 22-18) and “100G/200G receiver specifications”
(p. 22-18) for 130SCA1 line interface specifications.
....................................................................................................................................................................................................................................
client (130SCA1)
....................................................................................................................................................................................................................................
Client interface
The 130SCA1 supports either a 100GbE client or an OTU4 on the client interface (C1).
Table 18-76 130SCA1 client signal type

OTU4 111.809 Gb/s ITU-T G.709
Loopbacks
The 130SCA1 supports facility and terminal loopbacks on the client interfaces.
Visual Indications
(p. 19-12).
Location
The 130SCA1 can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 16.
Note: Due to thermal requirement, the Alcatel-Lucent 1830 PSS-32 shelf must be
equipped with the high-power fan (FAN32H) when an 130SCA1 card is installed in
the shelf.
....................................................................................................................................................................................................................................
WDM product description 130G Single Port Tunable AnyRate Muxponder – 10 clients
(130SNQ10)
....................................................................................................................................................................................................................................
130G Single Port Tunable AnyRate Muxponder – 10 clients

(130SNQ10)
Overview
The 130SNQ10 is a second generation 100G Coherent Muxponder that aggregates up to
10x10G clients onto a 50 GHz or flexGrid DWDM line. The card hosts two QSFP+ and
two XFP faceplate pluggables modules, where the two QSFP+ modules support 10GE
only clients and the two XFP modules support multi-protocol 10G clients. The card uses a
DP-QPSK modulation format that may be provisioned for either SDFEC or AFEC (Hard
decision FEC).
Card mnemonic
Table 18-77 130SNQ10 card mnemonic
S Single tunable line port (L1) supporting 100G of transport capacity.
N eNhanced. This card provides better engineering rules compared to the
130SCX10 card.
Q Uses QSFP+ pluggables on some client ports.
10 Ten client ports {C1-C10}
Physical design
The 130SNQ10 optical transponder is a two-slot wide, full-height card. The client
interfaces on the 130SNQ10 card support hot-swappable XFP pluggable modules (C1 and
C2) and QSFP+ pluggable modules (C3-C6 and C7-C10).
130SNQ10 features
The 130SNQ10 supports the following features:
• Supports an adaptive line interface. A single carrier using DP-QPSK modulation
format, with either SDFEC or AFEC. The line rate with SDFEC is 129.280281 Gb/s
(approximately 130 Gb/s).
• Supports full C-band tunability using either 50 GHz channel spacing or 37.5 GHz
channel spacing on the line interface
• Configurable option for Soft-Decision FEC (SDFEC) or hard-decision FEC (AFEC)
• Supports Analog (OPR/OPT) and Digital (PCS layer, RMON statistics) performance
monitoring
• Supports Standard Loopback capabilities for testing purposes
....................................................................................................................................................................................................................................
(130SNQ10)
....................................................................................................................................................................................................................................
• Supports unidirectional regeneration (using only its line interface, the client ports are
not used)
• Supports a WaveTracker encoder on the line interface
• Supports interworking with the 112SCX10, 112SNX10 and 130SNX10
Note: For interworking with legacy (112SCX10, 112SNX10) cards, the asyminterwk
parameter is supported
Line interface
The 130SNQ10 has a tunable coherent non-pluggable optical interface. The line bit rate is
(111.8099736 Gb/s ± 20 ppm) when provisioned for AFEC mode.
The line interface of the 130SNQ10 support full C-band tunability using either 50 GHz
channel spacing or 37.5 GHz channel spacing. The transmit frequency and receive
frequency of the line interface are individually provisionable by NE software. The
130SNQ10 supports a WaveTracker encoder on the line interface.
Client interface
The 130SNQ10 card supports the following client signal types:
• 10 GbE (CBRLAN11.049, CBRLAN11.096, GFP-F, GFP-P encapsulation modes)
(supported on all QSFP+ and XFP client interfaces)
• OC-192/STM-64 (supported on XFP interfaces only)
Loopbacks
The 130SNQ10 supports facility and terminal loopbacks on all client and line interfaces.
130SNQ10 front view

The following figure illustrates a front view of the faceplate of the 130SNQ10.
....................................................................................................................................................................................................................................
(130SNQ10)
....................................................................................................................................................................................................................................
Figure 18-187 130SNQ10 faceplate
....................................................................................................................................................................................................................................
(130SNQ10)
....................................................................................................................................................................................................................................
Legend:
1 L1 “Status” LED
2 Card “Status” LED

3 “C1” interface (XFP)
5 “C2” interface (XFP)
6 “C3 - C6” interface (QSFP+)

7 “C7 - C10” interface (QSFP+)
Visual Indications
(p. 19-12).
Location
The 130SNQ10 can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 16.
Card capacity per shelf
The Alcatel-Lucent 1830 PSS-32 shelf supports a maximum of eight 130SNQ10 cards,
depending on the shelf configuration.
The Shelf configurations supported are:
• The number of 130SNQ10 cards in a 20 A shelf = 1
• The number of 130SNQ10 cards in a 50 A filtered shelf = 4
• The number of 130SNQ10 cards in a 70 A shelf = 8
....................................................................................................................................................................................................................................
client (112SCA1, 112SNA1)
....................................................................................................................................................................................................................................
112G Single Port Tunable Coherent AnyRate Transponder - 1

Overview
The 112SCA1 and 112SNA1 OTs support one Compatible Front panel PTM (CFP) on the
client interface, and one OTU4 line interface (non-pluggable). The 112SCA1 and
112SNA1 OTs are similar in all respects, except the 112SNA1 provides a 1 dB receive
OSNR improvement compared to the 112SCA1. RMON statistics support is provided on
100 Gb/s Add/Drop for 112SCA1 and 112SNA1 OTs.
Physical design
The 112SCA1 and 112SNA1 OTs are three-slot wide, full-height packs, that support one
pluggable Compatible Front Panel (CFP) PTM on the client interface. The 112SCA1 and
112SNA1 OTs also support one OTU4 line interface (non-pluggable). The 112SCA1 and
112SNA1 OTs are similar in all respects, except the 112SNA1 provides a 1 dB receive
OSNR improvement compared to the 112SCA1.
Line interface
The 112SCA1/112SNA1 OT line interface supports:
• DP-QPSK modulation (Dual Polarization Quadrature Phase Shift Keying)
• Line side coherent receiver, combined with a DSP to compensate for impaired linear
and non-linear transmission (CD, PMD, SPM and non-linear phase noise).
• Supports Alcatel-Lucent Enhanced FEC (~9.2 dB coding gain at 1E-15 for ~7-%
overhead)
• Wave tracker supports optical power auto-management. User configurable option to
disable the WT for the interoperability application with other systems without WT
Client interface
The 112SCA1/112SNA1 supports one Compatible Front panel Pluggable (CFP) module
on the client interface. The CFP module is a pluggable form factor designed for optical
networking applications. The CFP contains multiple transmitters and receivers and optical
multiplex/demultiplex components. This allows it to combine multiple wavelengths into a
single fiber in the transmit direction, and demultiplex several wavelengths from the fiber
in the receive direction, thus providing Wavelength Division Multiplex (WDM)
capability.
The 112SCA1/112SNA1 supports the following client interfaces:
• 100G LAN PHY
• OTM-0.4
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
112SCA1/112SNA1 functional description
The following illustration shows a block diagram of the 112SCA1/112SNA1 OT with a
CFP.
Figure 18-188 112SCA1/112SNA1 OT block diagram with CFP
The 112SCA1/112SNA1 OT supports:

• Facility and Terminal loopbacks, along with a built in test-signal generator (on the
client transmit port) to facilitate card hardware validation
• Optical Performance Monitoring
– Analog PM - OPR, OPT on the Line interface, along with CD, DGD and FOFF
– Digital PM - FEC Errored Counts, Uncorrectable blocks, BBE, ES,SES, SEFS,
UAS
– Analog PM - OPR, OPT on the client interface, along with per- lane reporting of
transmit and receive optical power levels (per-lane power level reporting is only
available on 4x25G CFP pluggables in R6.0)
– PCS level PM on the client interface, along with RMON statistics (transmit and
receive directions)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
CFP support
Currently the following CFP modules are available:
• 4x25G up to 10 km
This transceiver contain four optical transmitters nominally operating at 25 Gb/s
based on DML or EML. It also contains an optical multiplexer, an optical
demultiplexer and four optical PIN receivers. The four optical wavelengths are in line
with LAN-WDM grid. Internal ICs convert the ten parallel 10 Gb/s electrical input
lanes into four data streams at 25 Gb/s and vice versa.
• 10x10G DML up to 10 km
This transceiver contains ten optical transmitters nominally operating at 10 Gb/s
based on DML. It also contains an optical multiplexer, an optical demultiplexer, and
ten optical PIN receivers. The ten wavelengths are aligned to a 8 nm spaced grid in
third windows. The re-timing functionality on both electrical transmit and receive
lanes is implemented inside the module.
For additional information on CFPs available for 112SCA1 and112SNA1, including
ordering information, see Table 18-28, “112SCA1 and 112SNA1 Client CFPs”
(p. 18-113).
112SCA1/112SNA1 front view

The following figure illustrates a front view of the 112SCA1/112SNA1 faceplate.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-189 112SCA1/112SNA1 Faceplate
Legend:
1 LEDs “STATUS”
3 LEDs “C1 ETH”
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4 LEDs “C1”
5 LEDs “L1”
Visual Indications
(p. 19-12).
Location
The 112SCA1/112SNA1 can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 15.
Note: When a 100Gb/s coherent Add/Drop OT and/or 10x10Gb/s coherent
Muxponder OT is installed in a 1830 PSS-32 shelf, a high capacity fan unit (PN
8DG59606AB) must be installed in the shelf.
....................................................................................................................................................................................................................................
WDM product description 2 x 100G Transponder/Muxponder card - (260SCX2)
....................................................................................................................................................................................................................................
2 x 100G Transponder/Muxponder card - (260SCX2)

Overview
The 2x100G Transponder/Muxponder OT provides 200G transmission capacity in a
single card. The 260SCX2 card supports two modes of operation: 260G mode and 130G
mode.
In the 260G mode, transmission of up to two 100 GbE client signals are transported on
one DWDM line interface. Each 100 GbE client signal is mapped into an OTU4. The two
OTU4 signals are then combined together to form a 260 Gb/s carrier that is sent to the
line interface.
In the 130G mode, transmission for only one 100 GbE or OTU4 client signal (C1) is
supported on the DWDM line interface. The 100 GbE client signal is mapped into an
OTU4, and either SDFEC or AFEC can be provisioned. The line rate is then 130G (for
SDFEC) or 112G (for AFEC). For simplicity, for either FECTYPE chosen (SDFEC or
AFEC), the mode is called 130G mode.
Card mnemonic
Table 18-78 260SCX2 card mnemonic
S Single tunable line port (L1) supporting 200G of transport capacity
C Coherent
X Mux
2 2 client ports (C1, C2)
Physical design
The 260SCX2 OT is a two-slot wide, full-height pack. The 260SCX2 supports one
optics and an LC connector. It also supports two client interfaces (C1, C2) with hot
swappable CFP2 pluggable modules. The 260SCX2 card contains two LEDs, a card
status LED and the line interface LED. Each client port has a dedicated port status LEDs.
The behavior of the utilized LEDs is described in, “Common LEDs of WDM cards”
(p. 19-12).
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
260SCX2 functional description
The 260SCX2 card supports an adaptive line interface and client ports through two CFP2
faceplate pluggable modules. Two FEC’s are selectable: The high performance
Alcatel-Lucent Soft Decision FEC [SDFEC] uses 23% overhead, and Alcatel FEC
[AFEC] provides backwards compatibility to Alcatel-Lucent first generation coherent
100G cards using 7% overhead.
260G mode
In the 260G mode, the payload is transmitted on a single DP-16QAM modulated carrier
using a Soft-decision FEC (SDFEC). AFEC is not a selectable option. The line rate for
this mode is 260 Gb/s. In this Muxponder mode, up to two 100 GbE client signals (C1
and C2) are mapped into two independent ODU4/OTU4 channels/frames (L1CH1 and
L1CH2) and combined into a proprietary format with SDFEC applied.
At the 260SCX2 line receive port, the SDFEC is processed by the PSE [with FEC
corrected errors, FEC uncorrected block counts and pre/post FECBER reported to the
user]. The incoming data stream is divided into two independent OTU4/ODU4
channels/frames and overhead processing applied. Each OTU4 is further demapped into
100 GbE and forwarded to the client interface (C1, C2).
Figure 18-190 260G mode block diagram
130G mode
In 130G mode, the payload is transmitted on a single DP-QPSK modulated carrier using
either SDFEC or AFEC. This mode, also known as the transponder application, supports
only one 100 GbE client signal (from port C1). The C2 port is not used. The line rate for
this mode is either 112 Gb/s or 130 Gb/s, corresponding to the provisioned FECTYPE.
For 130G mode, the line interface is a standard OTU4. The 100 GbE client signal is
mapped to ODU4/OTU4 with FEC applied and transmitted on the DWDM line.
At the 260SCX2 line receive port, the FEC is processed by the PSE [with FEC corrected
errors, FEC uncorrected block counts and pre/post FECBER reported to the user].
Overhead processing is applied to the incoming OTU4/ODU4 channel/frames. Each
OTU4 frame is further demapped into 100 GbE and forwarded to the client interface
(C1).
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
OTU4 client is supported only on the C1 port. If C1 is configured for an OTU4 client, C2
cannot be used. OTU4 client requires use of dual rate CFP2 pluggable (APN:
3AL81820AA) when configured for “auto” mode. This CFP2 supports application codes
ITU-T 4I1-9D1F as well as IEEE 100GBASE-LR4. “User” mode is also supported, but
operation with a third party CFP2 must be confirmed locally. Either RS-FEC or no FEC
options are supported on the OTU4 client. Performance monitoring on the OTU4 client
interface includes the DW (Digital Wrapper group as defined in the Product Planning
Guide) and CFP2 Digital Diagnostic Monitoring (DDM) of TX and RX power levels.
O-SNCP through OPSB card and OCH through OPSA card with 50 ms protection
switching is certified. OTU4 interoperability with 112SCA1 and 112SNA1 is supported.
Figure 18-191 130G mode block diagram
Line interface
The 260SCX2 has a tunable coherent non-pluggable optical interface. The line bit rate is
(111.8099736 Gb/s ± 20 ppm) when provisioned for AFEC mode. Refer to “100G/200G
transmitter specifications” (p. 22-18) and “100G/200G receiver specifications”
(p. 22-18) for 260SCX2 line interface specifications.
The line port supports the following signal types:
• OTU4 (that is, 130G mode)
If L1 signal type = OTU4, then only client port C1 can be used.
• OTU4x2 (that is, 260G mode - two combined OTU4 frames)
If L1 signal type = OTU4x2 , then both client ports can be used.
The line interface of 260SCX2 card supports full C-band tunability using either 50 GHz
channel spacing or 37.5 GHz spacing.
See Table 18-33, “260SCX2 CFP2” (p. 18-121) for the list of CFP2 pluggable modules
supported by the 260SCX2.
Client interfaces
The 260SCX2 OT supports two client interfaces with labels C1 and C2.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Loopbacks
The 260SCX2 supports the Facility and Terminal loopbacks on all client and line
interfaces. The following figures show an illustration of the loopback supported on each
of the interfaces.
Figure 18-192 Client Facility loopback on C1
Figure 18-193 Line Terminal loopback in 130G mode
Figure 18-194 Line Facility loopback in 260G or 130G mode
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-195 Client Terminal loopback
Card capacity per Alcatel-Lucent 1830 PSS-32

The Alcatel-Lucent 1830 PSS-32 shelf supports the following maximum number of
260SCX2 cards:
• In a 20 Amp shelf, the maximum number of cards is 1.
• In a 50 Amp shelf, the maximum number of cards is 5 (130G/260G mode).
• In a 70 Amp shelf, the maximum number of cards is 8 (130G/260G mode).
Card capacity per Alcatel-Lucent 1830 PSS-8
The Alcatel-Lucent 1830 PSS-8 shelf supports a maximum of two 260SCX2 cards.
260SCX2 features
The 260SCX2 supports the following features:
• Supports uni-directional regeneration for both 260G mode and 130G mode (SDFEC
and AFEC)
• Supports WaveTracker encoder on the line interface
• Supports a test signal generator
Refer to the Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 8.2 User
Provisioning Guide and see the procedure ’Test Signal Loopback’.
Performance monitoring
The 260SCX2 OT supports the following type of performance monitoring.
Optical Performance Monitoring
• Analog PM - OPR, OPT on the Line interface, along with CD, DGD and FOFF
• Digital PM - FEC Errored Counts, Uncorrectable blocks, BBE, ES,SES, SEFS, UAS
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
• Analog PM - OPR, OPT on the client interface, along with per- lane reporting of
transmit and receive optical power levels (per-lane power level reporting is only
available on 4x25G CFP pluggables in R6.0)
• PCS level PM on the client interface, along with RMON statistics (transmit and
receive directions)
260SCX2 front view

The following figure illustrates a front view of the faceplate of the 260SCX2.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Legend:
1 LED “L1”
2 LED “CARD”
3 LEDs “C1, C2”
Visual Indications
(p. 19-12).
Location
The 260SCX2 can be installed in:
• Alcatel-Lucent 1830 PSS-32 slots 2 to 16.
• Alcatel-Lucent 1830 PSS-8 slots 2 to 4.
....................................................................................................................................................................................................................................
WDM product description 112G Data Center Interconnect High Capacity Ethernet
Muxponder - 11 clients (112SDX11)
....................................................................................................................................................................................................................................
112G Data Center Interconnect High Capacity Ethernet

Overview
The 112SDX11 is a high capacity Ethernet Muxponder OT that supports Data Center
Interconnections. It can multiplex up to ten 10 Gb/s Ethernet (10 GE) client signals into
an OTU4 frame for transport to the network over an OTM-0.4v4 optical interface.
Although this transponder is generically called a “100G” transponder, the OTU4 nominal
bit rate on the line interface is 111.809 Gb/s, with a bit rate tolerance of ±20 ppm. The
multiple client interfaces can all be provisioned to transport 10GE client signal types.
Line and client signals supported

The 112SDX11 supports a multi-rate and multi-protocol client interface, capable of
transporting 4/8/10/16G FC, DDR infiniband, 10 Gb LAN, 40 GbE or OTU2/2e/1f client
signal types. The following table provides the list of client signals supported.
Table 18-79 112SDX11 client signals
Client Provi- Bit Map- Number Maxi- Appli- Plug-

signal sioned Rate ping of ODU4s mum cable gable
signal (Gb/s) for client capacity port Optics
rate signal client
/type number
into line
ODU4
4G FC FC400 4.25 ODUf- 4 10 C1 ~ 16FCLC-L
lex C10 16FCSN-I
S8FLCL-L
lex C10 16FCSN-I
S8FLCL-L
10G FC FC1200 10.518 ODUf- 9 8 C1 ~ S10GB-LR
lex C10 S10GB-SR
SXI64.1
lex C10 16FCSN-I
IB-DDR DDR 5 ODUf- 4 10 C1 ~ S8FLCL-L
lex C10
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 18-79 112SDX11 client signals (continued)
Client Provi- Bit Map- Number Maxi- Appli- Plug-

signal sioned Rate ping of ODU4s mum cable gable
signal (Gb/s) for client capacity port Optics
rate signal client
/type number
into line
ODU4
10GbE 10GbE 10.31 ODU2e 8 10 C1 ~ S10GB-LR
LAN C10 S10GB-SR
SXI64.1
OTU2 OTU2 10.709 ODU2 8 10 C1 ~ SXI64.1
C10
OTU2e OTU2e 11.049 ODU2e 8 10 C1 ~ SXI64.1
C10
OTU1f OTU1f 11.27 ODU1f 9 8 C1 ~ SXI64.1
C10
40GbE 40GbE 43 ODUf- 4x8 1 C11~C14 Q40GLR4
MLD lex Q40GSR4
Features
The 112SDX11 OT supports the following features:
• Supports 4G/8G/10G/16G Fibre Channel, IB-DDR, 10 GbE LAN,
OTU2/OTU2e/OTU1f client interfaces on SFP+ pluggable modules.
• Supports 40 GbE LAN client interface on QSFP+ pluggable module.
• Supports OPR/OPT performance monitoring on SFP+ pluggable module.
• Supports 64B/66B PCS monitoring for 8G FC/10G FC/16G FC/10 GbE/40 GbE LAN
signals.
• Supports RMON Statistics monitoring for 10 GbE/40 GbE.
• Supports OTN monitoring for OTU2/OTU2e/OTU 1f.
• Supports user selectable client interfaces SFP+ and QSFP+ pluggable modules.
• Supports user-provisionable consequent action for faults. Consequent action behavior
is independently set for each client signal.
• Supports software upgrades that are non-service affecting. Firmware upgrades are
supported, but are service affecting.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
• Supports up to 11 independent client signals that can be multiplexed and sent out on
the line. The client signal types can be of any combination.
• Supports Full-band tunable line side optics, capable of supporting all 88 channels (at
50 GHz spacing) in the 1830 PSS-32/16/4 system.
• Supports Auto Power Management through MVAC, MVAC8B.
• Supports Latency measurement at ODU4 level for line OTU4 signal, and at
ODU22/ODUflex level for client 4G/8G/10G/16G FC, 10GbE, 40 GbE and IB-DDR
signals.
• Supports relative skew measurement among 20 logical lanes on line OTU4.
• Supports ISL trunking on Fibre Channel ports (8/16G FC), up to eight ports per ISL
group and within one ISL group all Fibre Channel ports are with same rate, that is, all
are 4G, 8G, or 16G rate.
112SDX11 cascade to 260SCX2

The current release supports the provisioning of both 112SDX11 and 260SCX2 in the
same NE. This feature supports 40GE and Fibrechannel rates over 100G coherent through
cascade.
The 260SCX2 client port and 112SDX11 line port must be provisioned with OTU4 signal
type and the FEC type should be aligned. An internal topological link is provisioned
between the 260SCX2 client C1 port and the 112SDX11 line port.
Note: The cross-connect terminates on the 260SCX2 line port and 112SDX11 is not
included in the cross-connect. This configuration is supported on PSS-32.
Features:
• The supported CFP type on 112SDX11 under OTU4 signal type is C113G4Cd while
the supported CFP2 type on 260SCX2 for OTU4 client side is C2CLR4d.
• The allowed module types to be provisioned on 112SDX11 under OTU4 signal type
are C113G4Cd, auto, manual.
• The 260SCX2 client works under OTU4 mode and the line rate of 260SCX2 is
OTU4.
• The L1 port of 112SDX11 is provisioned as OTU4 signal type. Once L1 has been
assigned as OTU4, L2, L3, L4 cannot be assigned to any signal type.
• FC1200, FC1600 and 40GBE are the supported client signal types for 112SDX11
cascading configuration.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
112SDX11 Physical design
The 112SDX11 circuit pack is implemented as a single slot wide pack. There is only one
code of 112SDX11 pack, capable of operating at any channel in the C band 1830
frequency grid. The circuit pack contains up to 10 SFP+ and one QSFP+ pluggable
modules on its client interfaces. The pluggable modules of this pack are designed as
non-recess on faceplate, so Mounting Brackets are used to extend shelf cover.
Note: QSFP+ client port is used for 40 GE, defined as C11.
The 112SDX11 OT faceplate contains 16 LED visual indicators. One LED is for pack
status. 14 LEDs are for client port status. One LED is for line status.
Note: As L1-L4 consist of one OTM-0.4v4 interface, they will be reflected by one
LED status.
Line interface
The 112SDX11 has one tunable transceiver CFP module in line side which has four
sub-port interfaces L1, L2, L3, and L4. An OTU4 facility is carried over four OTLC
physical ports, the first physical port in the OTLC group (L1) is designated to be the
index for facility management of OTU4 and ODU4. For full line interfaces specifications,
see Table 22-64, “Line-side parameters for tunable 4x28G CFP (C113G4T) interfaces in
112SDX11” (p. 22-78).
Note: The line-side CFP is field replaceable by the user.
See Table 18-32, “112SDX11 CFPs/QSFPs/SFP+s” (p. 18-120) for the list of CFPs
supported.
Client interface
The first 10 client interfaces of the 112SDX11 (C1-C10) can be equipped with SFP+
pluggable modules and the last client interface can be equipped with an QSFP+ pluggable
module.
See Table 18-32, “112SDX11 CFPs/QSFPs/SFP+s” (p. 18-120) for the list of SFP+s
supported.
112SDX11 functional description

The following figure shows the functional block diagram of 112SDX11 OT.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-197 112SDX11 Block Diagram
SFP+/QSFP+ modules
Up to ten SFP+ and one QSFP+ pluggable modules provide interfaces to client
equipment. In the add direction, the line-side signal shall be timed from a client side
signal. In case of all client signal failure, the line shall be timed from an AIS clock. In the
drop direction, the client side signal shall be timed from the line side signal. In case of
line side signal failure, the client side signal shall be timed from the AIS clock.
The SFP+ and QSFP+ are responsible for the following functions:
• Provides Optical-Electrical signal conversion in the ingress direction and forwards
serial bit stream to the mapper FPGA device.
• Provides Electrical-Optical signal conversion and sends optical signal towards the
client.
• Provides monitoring of analog parameters (OPR, OPT, LBC) and detects loss of
optical power dLOS.
• Provides Hardware/Software control for laser ON/OFF control.
Mapper FPGA
The mapper FPGA provides bidirectional transmission and maintenance functions. In
addition to this, the Mapper FPGA device Mux/Demux client independently timed
signals. Each of them can be either a 4/8/10/16G FC, DDR Infiniband, 10 GbE LAN,
OTU2 signal, or 40 GbE signal. On the line side, it processes OTU4 framer and converts
to OTL4.10 signal.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
CFP module
In the add direction, the CFP module receives OTL4.10 signals from the Mapper FPGA
device, converts it to Line output signals depending on the specified CFP type. In the drop
direction, the CFP module receives line signals from the Line port. It converts the signal
to an electrical OTL4.10 signal and sends the OTL4.10 signal to the Mapper FPGA
device.
FEC
The 112SDX11 OT supports RS-FEC on the line OTU4 interface.
The 112SDX11 OT supports NO-FEC for OTU2/OTU1f/OTU2e client side interface.
Loopbacks supported
The following loopbacks on the line port are supported by hardware:
• OTU4 Facility loopback
• OTU4 Terminal loopback
• C1-C14 Client Facility loopback
• C1-C14 Terminal loopback
112SDX11 front view

The following figures provides an illustration of a front view of the faceplate of the
112SDX11.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-198 112SDX11 faceplate
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Legend:
1 Card “STATUS” LED
2 “C1” - “C6” interfaces

3 “C7” - “C10” interfaces
4 “C11” - “C14” interface (QSFP+)

5 “OTU4” - “OTU1” interfaces
“L1” CFP
6 LEDs “L1”
Visual Indications
(p. 19-12).
Location
The 112SDX11 can be installed in Alcatel-Lucent 1830 PSS-32 slots 2 to 17, or
Note: Due to thermal requirement, the PSS-32 shelf must be equipped with the
high-power fan (FAN32H) when an 112SDX11 card is installed in the shelf.
Note: 112SDX11 pluggables are not recessed. When installed in a shelf usage of the
Z25 cover (bumped cover) is required.
....................................................................................................................................................................................................................................
WDM product description 100/200G Uplink Dist OTN Switch (1UD200)
....................................................................................................................................................................................................................................
100/200G Uplink Dist OTN Switch (1UD200)

Overview
The 1UD200 is a client/line compatible single-slot uplink card for PSS-8 and PSS-16II
shelves. Its backplane interface associates either one or two client cards using N+1 or
N+2 slot to slot connectivity. It accepts an OTL4.10 formatted payload from the
backplane and maps to either a 100G or 200G WDM line interface using the PSE
coherent optics engine (same as 260SCX2).
1UD200 supports uni-directional regeneration for both 260G mode and 130G mode.
The 1UD200 features a 100G/200G adaptive rate design on the DWDM line interface.
The User can select the following card modes, depending on the application:
• For long reach applications, the 1UD200 supports a 100G mode (100G of
transmission capacity), which utilizes Dual Polarization Quaternary Phase Shift
Keying (DP-QPSK)on the DWDM line interface. For this mode, either Soft Decision
Forward Error Correction (SDFEC) or Hard Decision Forward Error Correction
(AFEC) can be set by the User. In this mode, the 1UD200 is paired with one I/O card
(20P200) within a quadrant of the PSS-8/PSS-16II shelf.
• For high capacity applications with less demanding reach requirements, the 1UD200
supports a 200G mode (200G of transmission capacity), which utilizes Dual
Polarization OLD 16 Quadrature Amplitude Modulation (DP-16QAM)on the DWDM
line interface. For this mode, SDFEC is used. In this mode, the 1UD200 is paired with
one or two I/O cards (20P200) within a quadrant of the PSS-8/PSS-16II shelf.
1UD200 licensing
There are two APNs for 1UD200 with bundled Right to Use (RTU):
1. 100G Mode using DP-QPSK modulation for long haul performance
2. 100G or 200G Mode using DP-16QAM modulation for metro/regional performance
The NE software will not block provisioning when the hardware is configured for an
operational mode that is not within the RTU. However in future, the NE software may
raise a standing alarm if the card is configured in violation of the RTU.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Refer the 1830 Customer Release Notes to determine if it is necessary [and how] to
obtain a license key to clear RTU violation alarms.
Table 18-80 1UD200 licensing
Description APN Allowable Upgrade RTU Allowable

Modes Modes After
without upgrade
upgrade
1UD200 100G 8DG62549AB 100G 8DG63582AAAA 100G or 200G
Uplink Card
1UD200 100/200G 8DG62549AA 100G, 200G
Uplink Card
1UD200 card configurations

The 1UD200 card supports various network configurations as the uplink card with
20P200 provisioned as the client card. For details, refer “100G ADM Client/Line
configuration with ODU2/2e switching ” (p. 17-109).
1UD200 physical design

The 1UD200 is a single slot, full height card. It is compatible with the PSS-8/PSS-16II
Client/Line Architecture (slot-to-slot connectivity N+1 and N+2). Thus, it is supported in
the PSS-8 and PSS-16II shelves.
The 1UD200 card has one line interface (L1), with LC connectors. The card supports one
port status LED (L1) and one card status LED. The 1UD200 card should support a latch
detection function to provide a fast equipment switch protection capability.
The expansion of 1UD200 is given in the following table:
1 Represents Single tunable line port (L1) supporting up to 200G of transport

capacity
U Indicates that the card is an UpLink card
D Distributed switching
200 Represents the maximum total (200 Gb/s) payload capacity on the line
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1UD200 front view
Figure 18-199 1UD200 front view
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Legend:
1 Card status LED

2 Line port LED
3 Line interface
Visual indications
(p. 19-12).
Location
The 1UD200 can be installed in Alcatel-Lucent 1830 PSS-8 slots 2 to 5, and
Alcatel-Lucent 1830 PSS-16II slots 3 to 10.
....................................................................................................................................................................................................................................
WDM product description 500G Muxponder/Uplink (D5X500)
....................................................................................................................................................................................................................................
500G Muxponder/Uplink (D5X500)

Overview
The D5X500 is a 500G Muxponder/Uplink introduced in R8.2. This double slot card
supports two WDM line interfaces, five client CFP4 interfaces and 400G backplane
connectivity in PSS-16II and PSS-32 shelves. In R8.2, each D5X500 supports either one
or two 100GE clients over each WDM 200G PM-8QAM carrier. A maximum of six
D5X500 cards may reside on a PSS-32 shelf. Future 1830 releases expand D5X500
configurations to seven modulation formats ranging from metro 64QAM to ULH BPSK.
Note: PSS32 backplane damage may result from inserting D5X500 into slot
10/11.
D5X500 functional description

The D5X500 aggregates 100G client traffic in hybrid Muxponder/uplink applications.
The pure Muxponder configuration maps client data from the CFP4 faceplate pluggables
into OTU4 serverports. The pure uplink configuration utilizes the PSS8/16II slot to slot
backplane connectivity as shown in Figure 18-200, “D5X500 Muxponder /Uplink”
(p. 18-544) (PSS8 high backplane speed connection) to electrically mate client cards to
the D5X500. Backplane connectivity is 200G to slot N-1 and another 200G of
connectivity to slot N+2. Each 100G of backplane traffic is mapped into an OTU4
serverport.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-200 D5X500 Muxponder /Uplink
The crossbar switch connects OTU4 server ports to the Photonic Service Engine (PSE)
where the digital signal processor manages coherent transmission across two independent
optical carriers through the dual transmitter/receiver. Wavetracker modulation is added to
each of the optical carriers via the “WT” functional block.
In R8.2, the card capacity is 400G and each line is provisioned as OTU4x2 with the
modulation format PM-8QAM. This creates a static mapping of C1 and C2 to L1
(serverport L1-CH1 and L1-CH2) while C3 and C4 are statically mapped onto L2
(serverport L2-CH1 and L2-CH2). Future releases of D5X500 will support additional
modulation formats, along with flexible cross-connect options.
D5X500 physical design

The D5X500 is a 2-slot wide, full height card. This card supports up to five physical
client faceplate interfaces labeled C5, C4, C3, C2, and C1. C1 should be the last client
port utilized; it is only available for a future configuration supporting 500G mode. The
D5X500 card contains two physical line interface ports, labeled L1 and L2. The D5X500
card can be inserted in any I/O slot of the supported shelf types, with the exception of slot
10 in the PSS-32 shelf.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Note: The slot 10 backplane on the PSS-32 shelf connectors interfere with the
backplane interface connectors on the D5X500. If the D5X500 card is used in slots
10/11 of the PSS-32, it could result in card damage, shelf backplane damage or
broken pins.
The D5X500 card supports the following LEDs on the faceplate:
• 1 card status LED
• 1 port status LED for each port (5 client ports plus 2 line port for a total of 7 port
status LEDs)
The expansion of the D5X500 mnemonic is given in the following table:
D5 D represents "Dual" WDM line ports.

5 represents that the card supports five physical client ports.
X X represents support for both muxponder and uplink functionality.
500 Represents the aggregate payload capacity. For this card, the maximum
payload capacity usable through all physical ports (taken together) is 500G.
Each D5X500 line port (L1, L2) is full C-Band tunable, but R8.2 restricts adjacent
PM-8QAM carriers to 100GHz spacing. Future 1830 releases will support flexgrid 37.5
GHz, 50 GHz, or 62.5 GHz spacing dependant on modulation format and waveshaping
options.
In the current release, D5X500 card is supported in CDC-F and CWR8 configurations.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
D5X500 front view
Figure 18-201 D5X500 faceplate
Legend:
1 Card status LED

2 Line ports
3 Client ports
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
D5X500 pluggable modules
The client interfaces on the D5X500 card support the following signal types on the CFP4
client ports:
- 100GbE
Note: OTU4 client signals will be supported in a future release.
Table D5X500 CFP4 in “PTM optics for WDM optical transponders” (p. 18-55) lists the
pluggables supported on D5X500.
Figure 18-202, “400G application” (p. 18-547) and Figure 18-203, “Dual 200G
appliciation” (p. 18-547) show the configuration options available for R8.2 D5X500.
Figure 18-202 400G application
Figure 18-203 Dual 200G appliciation
....................................................................................................................................................................................................................................
WDM product description Optical Protection Switching Modules (OPSA, OPSB)
....................................................................................................................................................................................................................................
Optical Protection Switching Modules (OPSA, OPSB)

Overview
The OPS cards provide photonic protection switching in DWDM configurations for any
supported channel in the C-band, allowing users to provide 1+1 dedicated OCh protection
for any optical signal carried in the Alcatel-Lucent 1830 PSS DWDM domain. The
optical protection switch (OPS) packs (OPSA and OPSB) are implemented as half-height
modules that can be configured in any universal slots in the universal shelves.
OPS functional description

The OPS cards provide photonic protection switching in DWDM configurations for any
supported channel in the C-band, allowing user to provide 1+1 dedicated OCh protection
for any optical signal carried in the Alcatel-Lucent 1830 PSS DWDM domain. The OPS
monitors the input signal and splits it into two equal signals in the transmit direction. In
the receive direction, The OPS monitors two input signals and controls the 1x2 switch
based on LOS.
The only functional differences between the OPSA and OPSB are that OPSA has VOA
after splitter, OPSB does not.. Also, OPSB switching is non-latching, which means that if
the switch is not in the default position, it springs back to its default position when switch
power is off.
The following figures illustrate functional block diagrams of the OPSA and OPSB
Figure 18-204 OPSA functional diagram
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 18-205 OPSB functional diagram
As shown in the functional diagrams, the OPS card performs head-end bridging and
tail-end switching of an optical signal.
• At the head end of the protected link, an optical signal is split into two identical
signals and sent over a specified OCh path to another OPS card at the tail end of the
protected link. There are also electronic variable optical attenuators (eVOAs)
controlling the A and B port transmit power.
• At the tail end, the total optical power of each of the received signals is monitored. A
switch is initiated if the total optical power of one of the signals falls below a defined
threshold (according to the rules associated with OPS protection state machine).
The threshold level at which a switch is initiated, is calculated automatically by the
system on a per-port basis on port A and port B only. When the total optical power of an
input signal falls below a threshold, the OPS card performs a protection switch with
signal disturbance of less then 50 ms due to protection switching execution.
Note: LOS switch thresholds and tolerance can be also be provisioned manually, but
only an expert user should manually provision the thresholds. The commands used to
accomplish this are only available at the Admin or Service security level. (See the
Alcatel-Lucent 1830 PSS User Provisioning Guide, and Command Line Interface
Commands Guide (Vol.I) for details.)
In addition to autonomous switching based on monitoring of input LOS, OPS provides
user protection management by supporting Manual, Forced and Lockout protection
requests. OPS protection state machine supports 1+1 unidirectional, non-revertive
protection.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
OPS front view
OPSA and OPSB both have the same LED indicators and interface connections on their
faceplates. Refer to Figure 18-206, “OPS module faceplate” (p. 18-550) for an
illustration.
Figure 18-206 OPS module faceplate
Legend:
1 LEDs “STATUS”
2 LEDs “SIG”
3 “SIG” interface
4 “A” interface
5 “B” interface
6 LEDs “A”
7 LEDs “B”
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Visual Indications
For information about the LEDs on the front panel, see “Card Status LED” (p. 19-12) and
“Port Status LED” (p. 19-12).
Location
The OPS cards can be installed in Alcatel-Lucent 1830 PSS-16 slots 3 to 10 and 13 to 20,
and in Alcatel-Lucent 1830 PSS-32 slots 2 to 17 and 20 to 35.
....................................................................................................................................................................................................................................
WDM product description Control architecture
....................................................................................................................................................................................................................................
Control architecture
Overview
WDM compounds have a control architecture that consists of a single primary, and single
backup shelf controller, with some control distributed to individual application and I/O
cards in the shelf.
System control
The active Equipment Controller (EC) on Alcatel-Lucent 1830 PSS-32 and
Alcatel-Lucent 1830 PSS-16 shelves provides all node and shelf control and management
functions and handles the interfaces to management systems. The second EC card is
standby and capable to take over the role of an active EC once the formerly active EC
becomes inactive. Each EC contains a Micro-controller asset (MCA) and other devices to
support the required functionality. The MCA of the EC consists of a processor (CPU) with
interface logic and is integrated into the EC motherboard.
All system components contain a client control function (CCF) that allow them to operate
independently once configured and placed into operation. This function is used for
application configuration / reporting (where applicable), inventory control, FPGA
download (where applicable), and card status retrieval.
Figure 18-207 Control schematic
CCF Client control function

CRU Clock recovery unit
....................................................................................................................................................................................................................................
WDM product description Control architecture
....................................................................................................................................................................................................................................
LSW LAN switch board
MCA Micro-controller asset
Multi-shelf configurations
From a control architecture perspective, the WDM compound and the OCS compound are
separate sets of shelves, only interconnected through external interfaces. Also the
inter-compound TL1 communication for uplink card management runs through external
interfaces (usually through OAMP LAN). Both compounds must be connected through an
external router that allows this communication or through external LAN switch, refer to
the Alcatel-Lucent 1830 PSS Installation and System Turn-Up Guide (ITG).
Inside each compound, shelves are interconnected through dual LAN rings, refer to
“Shelf interconnection” (p. 8-207).
....................................................................................................................................................................................................................................
WDM product description External communications: ECC
....................................................................................................................................................................................................................................
External communications: ECC

ECC termination
The ECC frames are transcoded to Ethernet frames for transport between the main shelf
Equipment Controller (EC) and the line cards via the internal LAN infrastructure.
The Alcatel-Lucent 1830 PSS supports the termination of embedded communication
channels (ECC) for OTH facilities. The ECC frames are transcoded to Ethernet frames
for transport between the main shelf Equipment Controller (EC) and the line cards via the
internal LAN infrastructure.
Alcatel-Lucent 1830 PSS can manage edge NEs using IP protocols through GCC.
The ECCs provide the following data transfer bandwidth:
Table 18-81 ECC supported data transfer bandwidth
Data Data rate

OTU1 GCC 326.724 Kb/s +-20ppm
OTU2/ODU2 GCC 1312.405 Kb/s +-20ppm
OTU2e/ODU2e GCC 1359.770 Kb/s +-20ppm
OTU1f GCC 1381.143 Kb/s +-20ppm
OTU4/ODU4 GCC 13702.202 Kb/s +-20ppm
Note: The listed bandwidth values are the physical bandwidth of the raw channels.
The full physical bandwidth cannot be used for user data due to various mechanisms
inside the protocol stack, which use part of the bandwidth for their own purposes.
For Release 7.0, a single ECC will be associated with a single Network Interface
(NETIF). Up to 128 NETIFs are supported per NE, and among them only 64 NETIFs can
be associated with any given shelf.
Only one GCC Type (GCC0, GCC1, or GCC2) may be terminated on any one given port
instance (that is, only one of: OTU-1-1-1 GCC0, OTUODU2-1-1-1 GCC1,
OTUODU2-1-1-1 GCC2 can be terminated).
The ENT-NETIF, ED-NETIF and DEL-NETIF TL1 commands and config cn netif/
show cn netif CLI commands provide this functionality.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
GCC on WDM line cards
WDM optical transponder cards with the OTUk interface support the provision of the
following GCC communication channel type:
• GCC0 (default)
• GCC1
• GCC2
The following table shows the list of WDM optical transponder cards that support the
GCC channel type provisioning:
Table 18-82 GCC channel type provisioning supported OTs
Card Name AID Facility Type ECC Type MAX ECCs

per pack
4DPA4 OTU-<shelf>-<slot>- OTU1 GCC0 2
L{1-2}
4QPA8 OTU-<shelf>-<slot>- OTU1 GCC0 4
L{1-4}
11DPE12 OTU-<shelf>-<slot>- OTU2 GCC0 2
L{1-2}
ODU2-<shelf>-<slot>- HO ODU2 PTF GCC1 GCC2
L{1-2}
11DPE12A OTU-<shelf>-<slot>- OTU2 GCC0 2
L{1-2}
L{1-2}
11DPE12E OTU-<shelf>-<slot>- OTU2 GCC0 2
L{1-2}
L{1-2}
11DPM12 OTU-<shelf>-<slot>- OTU2 GCC0 2
L{1-2}
L{1-2}
11DPM4M OTU-<shelf>-<slot>- OTU2 GCC0 2
L{1-2}
L{1-2}
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 18-82 GCC channel type provisioning supported OTs (continued)

per pack
11DPM8 OTU-<shelf>-<slot>- OTU2 GCC0 2
L{1-2}
L{1-2}
11OPE8 OTU-<shelf>-<slot>- OTU2 GCC0 6
X{1-6}
X{1-6}
11QCE12X OTU-<shelf>-<slot>- OTU2 GCC0 4
X{1-4}
X{1-4}
11QPA4 OTU-<shelf>-<slot>- OTU2 GCC0 8
C{1-4}
OTU-<shelf>-<slot>- OTU2 GCC0
L{1-4}
OTUODU2-<shelf>- HO ODU2 NIM, GCC1
<slot>-L{1-4} when client =
OTU2
ODU2-<shelf>-<slot>- HO ODU2 PTF, GCC2
L{1-4} when client =
non-OTN
11QPE24 OTU-<shelf>-<slot>- OTU2 GCC0 4
X{1-4}
X{1-4}
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 18-82 GCC channel type provisioning supported OTs (continued)

per pack
11QPEN4 OTU-<shelf>-<slot>- OTU2 GCC0 8
C{1-4}
OTU-<shelf>-<slot>- OTU2 GCC0
L{1-4}
OTUODU2-<shelf>- HO ODU2 NIM, GCC1
<slot>-L{1-4} when client =
OTU2
ODU2-<shelf>-<slot>- HO ODU2 PTF, GCC2
L{1-4} when client =
non-OTN
11STAR1 OTU-<shelf>-<slot>-C1 OTU2 GCC0 1 - Client
and Line
Ports cannot
OTU-<shelf>-<slot>-L1 OTU2 GCC0 be enabled at
the same
time
11STAR1A OTU-<shelf>-<slot>-C1 OTU2 GCC0 1 - Client
and Line
Ports cannot
OTU-<shelf>-<slot>-L1 OTU2 GCC0 be enabled at
the same
time
11STMM10 OTU-<shelf>-<slot>- OTU1 GCC0 4
C{1-10}
112SDX11 OTU-<shelf>-<slot>-L1 OTU4 GCC0 11
OTU-<shelf>-<slot>- OTU1F, OTU2, GCC0
C{1-10} OTU2E
12P120 OTU-<shelf>-<slot>- OTU2, OTU2E GCC0 12
C{1-6}
OTU-<shelf>-<slot>- OTU2, OTU2E GCC0
L{1-6}
The 11STAR1/11STAR1A supports GCC0 channel enable and disable on both Line and
Client ports. 11STAR1/11STAR1A hardware only supports a single GCC channel. To
enable the Line Port GCC0 channel, the Client port GCC0 port must be disabled. To
enable the Client Port GCC0 channel, the Line port GCC0 port must be disabled.
....................................................................................................................................................................................................................................
WDM product description External communications: LAN
....................................................................................................................................................................................................................................
External communications: LAN

User service interfaces
The Alcatel-Lucent 1830 PSS provides LAN interfaces for management access and
debug, and for the access to the management communication network (MCN).
Management access is provided for Alcatel-Lucent 1830 PSS ZIC for a system with OCS
or both OCS and WDM compounds, and for WebUI for a system that is only WDM
compound.
LAN interface for Alcatel-Lucent 1830 PSS ZIC/WebUI access
The “CIT” connector is on the front panel of each Equipment Controller (EC) and is
available for WebUI or Local Craft access. CIT access is only possible in the main shelf.
OAMP interface
A single RJ-45 OAMP interface is located on the User panel.
AUX interface
An AUX interface is located on the Equipment Controller. This RJ-45 connector can be
used for a WebUI or local Craft terminal connection.
ES1/ES2 interface
The ES1 and ES2 interfaces are located on the Equipment Controller.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Network diagram
Figure 18-208 WDM Subrack connections for communications and maintenance

E1 E2 VOIP OAMP
USRPNL LAN
CIT CIT
AUX LAN LAN AUX
ES1 ES1
ES2 ES2
CPU CPU
EC_A EC_B
10/100BASE-T external LAN connection

10/100/1000BASE-T external LAN connection
FE internal LAN connection
GbE internal LAN connection
g-pipg-32net
Legend:
USRPNL Shelf User Panel

EC_A Equipment Controller at position EC_A
EC_B Equipment Controller at position EC_B
FE Fast Ethernet
GbE Gigabit Ethernet

OAMP OAMP Customer LAN
AUX AUX Customer LAN
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
VOIP VOIP Customer LAN
ES1 ES1 Multi-shelf interconnection LAN

ES2 ES2 Multi-shelf interconnection LAN
E1 E1 Customer LAN
E2 E2 Customer LAN
CIT LAN access for Alcatel-Lucent 1830 PSS ZIC
General addressing
Alcatel-Lucent 1830 PSS supports one provisionable LAN IP address for the active EC.
Addressing in WDM compounds (Alcatel-Lucent 1830 PSS )

Network connections on 1830 PSS-32/PSS-16 WDM compounds are supported by ports
on the USRPNL and Equipment Controller (EC).
USRPNL
The 1830 PSS-32/PSS-16 USRPNL supports four MAC addresses stored on its
EEPROM. The MAC addresses are installed and assigned at the factory and are
associated with the LAN ports on the USRPNL. Replacement of the USRPNL will cause
new MAC addresses to be associated with these LAN ports. External IP address and
MAC address are fixed and follow the active LAN ports on the USRPNL.
There are four ports on the user panel: OAMP, VoIP, E1 and E2. Each of these four ports
have four MAC addresses.
• OAMP: connection to management systems through an external DCN
• VoIP: connection of an IP-phone
• E1/E2: management of external equipment
Equipment Controller
Every 1830 PSS-32/PSS-16 shelf contains one EC (Equipment Controller), or two ECs if
redundancy is desired. The EC supports four unique MAC addresses stored in its
EEPROM. These are associated with four auto-sensing RJ-45 LAN ports.
The first (topmost) port on the EC faceplate, is dedicated for the CIT connection. It is
labeled CIT. The CIT ports are active for ECs residing on the main shelf. For ECs
residing on sub-shelves, the CIT ports are disabled. The CIT port is enabled by default on
the active main EC.
The CIT port supports DHCP service. When a connection (for example, using a laptop) is
detected, the NE will provide an internal IP address in response to the DHCP request from
the laptop. The CIT allows the client to connect locally to manage the NE. It is important
to note that the CIT port does not run the full set of IP features supported on the OAMP
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
port. The CIT port only provides basic NE management for local management through
SNMP. Remote NE management through the CIT port can be supported only if the
operator assigns unique IP addresses to these CIT ports.
Below the CIT port on the EC faceplate, the second port is labeled AUX which has the
same functionality as E1, E2 and VOIP. Each AUX port carries an independent IP subnet.
The bottom two ports on the EC faceplate, labeled ES1 and ES2 (ES for extension shelf),
are internal ports only and are used to connect to 1830 PSS-32/PSS-16 main/primary
shelves with extension shelves (sub-shelves). The Alcatel-Lucent 1830 PSS NE can be
comprised of multiple 1830 shelves. In order to create one NE with a single TID, these
shelves are tied together in a daisy chain fashion, using the ES1 and ES2 ports. The MAC
addresses of the ES1 and ES2 ports are not retrievable.
Both ES ports are enabled by default, but they can be provisioned as disabled. If they are
enabled with nothing is plugged in, the NE will raise an NSA condition, “Link Down,”
for the ES ports.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
19 19 operations,
WDM
administration,
maintenance, and
provisioning (OAM&P)
Overview
Purpose
This chapter provides information about the system management functions for the
administration of Alcatel-Lucent 1830 Photonic Service Switch (PSS) and describes
hardware and software interfaces used for administration, maintenance, and provisioning
activities.
Contents
Operations interfaces 19-3

LEDs of the Fan Unit 19-4
LEDs of the Power Filter Card (PFC) 19-5
LEDs of the PTPCTL card 19-7
LEDs of the Equipment Controller (EC) 19-8
LEDs of the User Panel 19-9
LEDs of the SFD40/SFD40B 19-11
Common LEDs of WDM cards 19-12
Administration 19-15
Security 19-16
Time of day synchronization 19-19
Automatic power adjustments 19-21
Maintenance 19-30
Fault detection and alarm management 19-31
Loopbacks 19-35
System diagnostics and tests 19-41
...................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Overview
....................................................................................................................................................................................................................................
Performance monitoring 19-44

Thresholding 19-68
Software management 19-72
Configuration database management 19-73
Protection 19-76
Reports 19-104
Provisioning 19-105
Equipment provisioning 19-106
Primary and secondary states of system components 19-109
Optical transponder and client/line card protection 19-116
Optical protection for 40G OTs 19-132
....................................................................................................................................................................................................................................
Operations interfaces
....................................................................................................................................................................................................................................
Overview
Purpose
This section provides information about the operations interfaces of Alcatel-Lucent
1830 Photonic Service Switch (PSS), such as Alcatel-Lucent 1830 PSS ZIC and the LEDs
on the front plates.
Contents
LEDs of the Fan Unit 19-4

LEDs of the Power Filter Card (PFC) 19-5
LEDs of the PTPCTL card 19-7
LEDs of the Equipment Controller (EC) 19-8
LEDs of the User Panel 19-9
LEDs of the SFD40/SFD40B 19-11
Common LEDs of WDM cards 19-12
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and LEDs of the Fan Unit
....................................................................................................................................................................................................................................
LEDs of the Fan Unit

Fan Unit LED 1 (PWR)
Color Function
Green Power on
The LED indicates power at least at one FAN motor (ABAB or higher).
Fan Unit LED 2 (STAT)
Color Function
Green Normal operation

Amber Local fan temperature or ambient temperature = High
Red Fan failure / local fan temperature or ambient temperature = Critical
Reference
For the location of the LEDs, see Figure 8-3, “FAN3T8 front view” (p. 8-37).
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and LEDs of the Power Filter Card (PFC)
....................................................................................................................................................................................................................................
LEDs of the Power Filter Card (PFC)
Table 19-1 PFC STATUS LED
Color Function
Switched off All battery inputs missing or voltage too low
Green All battery inputs available, no hardware failure

Amber At least one battery input missing, no hardware failure (for example
fuse blown)
Red Card failure (hardware failure, for example fuse blown)
Table 19-2 PFC SOURCE LED
Color Function
Switched off Timing interface not among synchronization sources

Green Timing source configured – no errors
Red Timing source configured – source has errors
Table 19-3 PFC BATT I LED
Color Function
Switched off Branch 1: Battery voltage < 35V

Green Branch 1: Battery voltage > 35V
Table 19-4 PFC BATT II LED
Color Function
Table 19-5 PFC BATT III LED
Color Function

The tables above describe the behavior of the LED in case SW control is available.
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and LEDs of the Power Filter Card (PFC)
....................................................................................................................................................................................................................................
During power-up state (after power on of the system and service voltage is present until
SW control is available):
• The STATUS LED will be red
• The SOURCE LED will be switched off and
• BATT LEDs will indicate presence of battery voltage
Reference
For the location of the LEDs, see Figure 8-12, “PFC front view” (p. 8-50).
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and LEDs of the PTPCTL card
....................................................................................................................................................................................................................................
LEDs of the PTPCTL card

SYNC
Table 19-6 PTPCTL SYNC LED
Color Function
Green PTP is synchronized
Amber (blinking) PTP is enabled but not synchronized

Off PTP is not enabled
Table 19-7 PTPCTL EPS LED
Color Function
Green EQPS is configured, and this card is active

Amber (blinking) EQPS is configured, and the cards are synchronizing1
Off EQPS is configured, and this card is in standby, or EQPS is not
configured.
Notes:
1. Card redundancy is not supported in R6.0, so LED2 is always OFF.
Reference
For the location of the LEDs, see: “PTPCTL front view” (p. 18-297)
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and LEDs of the Equipment Controller (EC)
....................................................................................................................................................................................................................................
LEDs of the Equipment Controller (EC)

LED 1 (STAT)
The status (STAT) LED indicates alarm and admin state information for an individual
card, unrelated to equipment protection.
Table 19-8 EC LED 1 (STAT)
Color Function
Switched off Card equipped and not provisioned or card out of service after
shutdown has been performed successfully. The operator can plug out
the card.
Green blink Card starting, autotesting, or graceful shutdown, or FPGA download

Green Card properly equipped, provisioned, and in service No alarm is
present.
Amber blink Card out of service but provisioned
Amber Minor alarm is present
Red blink Card misconfigured or card mismatch. Limited Mode (FLC) / FLC SW
Adaptation
Red Critical or major red alarm is present
LED 1 (EPS)
The Equipment Protection Switching (EPS) LED indicates the status of the equipment
protection switching function across both ECs in a shelf.
Table 19-9 EC LED 1 (EPS)
Color Function
Switched off Either EPS is configured, and this card is standby, or EPS is not
configured.
Green EPS is configured and this card is active.
Amber blink EPS is configured and the cards are synchronizing.
Reference
For the location of the LEDs, see Figure 18-22, “Front view of the 1830 PSS-8 EC”
(p. 18-181).
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and LEDs of the User Panel
....................................................................................................................................................................................................................................
LEDs of the User Panel

LED 1 (STATUS)
Table 19-10 User Panel LED 1 (STATUS)
Color Function
Switched off No power to the unit, or the LED is defective.
Green Card properly equipped, provisioned, and in service No alarm is

present.
Amber The unit is in service and has a minor alarm

Red The unit is in service and has a major or critical alarm
LED 3 (MJ/PROMPT)
Table 19-11 User Panel LED 3 (MJ/PROMPT)
Color Function
Switched off A major alarm is not present

Red A major alarm: indicates a serious disruption of service or the
malfunctioning or failure of an important NE entity. This alarm requires
the immediate attention and response of a craftsperson to restore or
maintain system capability. The urgency is less than in critical situations
because of a lesser immediate or impending effect on service or system
performance.
LED 4 (CR/PROMPT)
Table 19-12 User Panel LED 4 (CR/PROMPT)
Color Function
Switched off A critical alarm is not present

Red A critical alarm: indicates a severe, service-affecting condition has occurred
and that immediate corrective action is imperative, regardless of the time of
day or day of the week.
LED 5 (WARNING)
Not currently used.
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and LEDs of the User Panel
....................................................................................................................................................................................................................................
LED 6 (MN/DEFRD)
Table 19-13 User Panel LED 6 (MN/DEFRD)
Color Function
Switched off A minor alarm is not present
Amber A minor alarm: indicates a condition that does not have a serious effect on
service, or for a condition that is not essential to NE operation.
LED 7 (ABNORMAL)
Not currently used.
LED 8 (ATTENDED)
Table 19-14 User Panel LED 8 (ATTENDED)
Color Function
Switched off There is no standing alarm on the unit.

Red A standing alarm has been silenced by the ACO command, or button. When
the most recent alarm silenced by the ACO command is retired, this LED
will be extinguished.
Reference
For the location of the LEDs, see the USRPNL front views for the respective User Panels
in “PSS-8 Shelf panel and User panel (USRPNL)” (p. 18-193), “PSS-16II User panel
(USRPNL)” (p. 18-196) and “PSS-32/16 User panel (USRPNL)” (p. 18-200).
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and LEDs of the SFD40/SFD40B
....................................................................................................................................................................................................................................
LEDs of the SFD40/SFD40B

LED 3 (PWR A)
Table 19-15 LED 3 (PWR A)
Color Function
Switched off No power in the PWR A input, or the LED is defective.
Green Card properly equipped, provisioned, and power is present on the PWR
A input..
LED 4 (PWR B)
Table 19-16 LED 4 (PWR B)
Color Function
Switched off No power in the PWR Binput, or the LED is defective.

Green Card properly equipped, provisioned, and power is present on the PWR
Binput..
LED 5 (LOS)
Table 19-17 LED 5 (LOS)
Color Function
Switched off No alarm is present for MUX output or DEMUX input.

Red Indicates that there is at least one LOS alarm of MUX output or
DEMUX input.
LED 6 (TOR)
Table 19-18 LED 6 (TOR)
Color Function
Switched off there are no MUX or DEMUX AWG temperature alarms present.
Red Iindicates there is at least one MUX or DEMUX AWG temperature

alarm.
Reference
For the location of the LEDs, see Figure 18-40, “SFD40/SFD40B faceplate” (p. 18-216).
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Common LEDs of WDM cards
....................................................................................................................................................................................................................................
Common LEDs of WDM cards

Overview
Many WDM optical transponders, amplifiers, and other cards used in 1830 PSS shelves
share common LEDs on their faceplates, with common indications. These LEDs are
described here in the following tables.
Card Status LED
Table 19-19 Card Status LED
Color Function
Switched off The card is administratively out-of-service or in a maintenance state.

Green blink The card is in-service with boot/load in progress.
Green The card is properly equipped, provisioned, and in service. No alarm is present.
Amber blink The card is administratively in-service with a minor port alarm.
Amber The card is administratively in-service with a minor pack alarm and may have a minor
port alarm.
Red blink The card is administratively in-service with a major or critical port alarm, and may have
a minor pack alarm.
Red The card is administratively in-service with a major or critical pack alarm.
Port Status LED

LEDs associated with Line, Client, VOA (VA), OSC, and SIG ports have LEDs
associated with them that indicate the status of the PORT.
Table 19-20 Port Status LED
Color Function
Switched off The port is in an administratively out-of-service state (or LED is defective).
Green blink The port is in an administrative maintenance state.
Green The port is administratively in-service, and has no alarm.

Amber The port is administratively in-service, and has a minor alarm.
Red The port is administratively in-service, and has a major or critical alarm.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Ethernet activity LED
Several WDM cards have “Ethernet” LEDs that are associated with a dedicated Ethernet
port, or with OT client or line ports that can be configured for Ethernet application. On
the client or line ports of optical transponder cards, these LEDs provide dynamic
indication of Ethernet traffic only on 11STGE12 and 11DPE12 cards for 1 GbE
configured ports.
Table 19-21 Ethernet activity LED
Color Function
Green blink The port is provisioned for Ethernet traffic, and there is currently active movement of
Ethernet data packets on the port (either transmit or receive packets). Note on green
blinking: The LED should cycle on/off at least once (and if possible twice) during every
second in which Ethernet packet(s) are transmitted or received. However the rate of
blinking is subject to limitations of OT FPGA LED control.
Switched off In all cases not described above.
Notes:
1. When blinking green, the LED should cycle on/off at once or twice every second during
which Ethernet packet(s) are transmitted or received. Beyond this, the rate of blinking is
subject to the limitations of the transponder FPGA LED control.
Reference
For the location of the LEDs, refer to:
• “WR8-88A(F) front view” (p. 18-236)
• “OSCT front view” (p. 18-247)
• “MVAC front view” (p. 18-252)
• “MVAC8B front view” (p. 18-254)
• “WTOCM/WTOCMA front view” (p. 18-263)
• “MON-OCM front view” (p. 18-269)
• “Full-height LD front views” (p. 18-302)
• “RA2P front view” (p. 18-321)
• “MESH4 front view” (p. 18-325)
• “4DPA2 front view” (p. 18-347)
• “4DPA4 front view” (p. 18-354)
• “11STMM10 front view” (p. 18-361)
• “11QPA4 front view” (p. 18-368)
• “11STGE12 front view” (p. 18-374)
• “11DPE12(E) front view” (p. 18-386)
• “11DPM12 front view” (p. 18-402)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
• “11STAR1(A) front view” (p. 18-439)
• “11QPEN4 front view” (p. 18-446)
• “11OPE8 front view” (p. 18-433)
• “11QCE12X front view” (p. 18-427)
• “12P120 front view” (p. 18-453)
• “130SNQ10 front view” (p. 18-515)
• “1UD200 front view” (p. 18-541)
• “20P200 front view” (p. 18-457)
• “43SCGE1 front view” (p. 18-467)
• “43SCX4 and 43SCX4E front views” (p. 18-472)
• “43STX4/43STX4P front view” (p. 18-478)
• “43STA1P front View” (p. 18-483)
• “43SCA1 front view” (p. 18-489)
• “112SCX10/112SNX10 front view” (p. 18-495)
• “112SCA1/112SNA1 front view” (p. 18-520)
• “130SCX10 front view” (p. 18-500)
• “130SNX10 front view” (p. 18-506)
• “260SCX2 front view” (p. 18-528)
• “OPS front view” (p. 18-550)
• “iROADMx front view” (p. 18-273)
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
Administration
Overview
Purpose
This section describes important administration aspects of Alcatel-Lucent 1830 Photonic
Service Switch (PSS).
Contents
Security 19-16
Time of day synchronization 19-19
Automatic power adjustments 19-21
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Security
Administration
....................................................................................................................................................................................................................................
Security
Overview
The following information provides a brief overview of available security features and
information on using them. The security features and functions can be grouped into the
following:
• RADIUS server support for User Authentication
• User Login management
• Encrypted Mode and Secure Shell
• Crypto Key Management for Encrypted Data Exchange
• Encrypted File Transfer for Database Backup/Restore and SW Download
RADIUS server support for user authentication

RADIUS provides a centralized way of user login/authentication and management. A
RADIUS server is an external entity (server) that keeps a centralized Database of user
login, password and privilege information. Each NE in the network consults a configured
RADIUS server when a user attempts to gain access to the system.
The implementation in the current release, provides support for user authentication and
privilege (admin, provisioner, observer, etc.) retrieval. The RADIUS protocol does not
support changing a user login/password or adding a new user to an NE. All users must be
pre-configured on the RADIUS server. So some of the security features under User Login
Management may not be applicable (e.g. forcing a user to change a password due to
aging).
NTP server authentication

The NTPv4 protocol supports authentication using either symmetric key or public key
cryptography. Alcatel-Lucent 1830 PSS implements authentication using the symmetric
key cryptography feature. This method ensures an unbroken chain of trust between the
client system and the primary servers at the root of the timing distribution network. This
chain is known as the provenance of the client. The protocol provides the credentials to
ensure that the source of the timing signal is not being spoofed since the attacker does not
have the cryptographic key information to provide authentic credentials.
When authentication is in use, every message contains a message authentication code
(MAC) appended to the NTP header in the message. The MAC is calculated using a
cryptographic hash algorithm to produce a mathematical fingerprint that uniquely
identifies each message. Under the symmetric key method, both the server and the client
share a key, that is distributed outside this protocol. The server uses the key to create the
MAC. When the message arrives, the client uses the key to create its own version of the
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
MAC. The client then compares its calculation to the MAC inserted in the message.
When the two codes match the client concludes that the message was indeed sent from
the intended server.
Encrypted mode and secure shell (SSH)

SSH provides encrypted access to an NE. An SSH server running on the NE is
responsible for setting up an encrypted channel for each user session. A typical user
session starts with an SSH client connection and ends when the connection goes away. All
data exchanged during the session is encrypted/decrypted using an encryption key.
The user is authenticated at SSH client connection time. Upon successful authentication,
the user is allowed to connect directly to the CLI.
Configuration of encrypted or normal mode can be used to restrict access to the NE.
When the NE is placed in encrypted mode, Telnet etc. normal access is disabled. To
prevent accidental lockout, the generation of an encryption key is allowed only in normal
mode.
SSH requires an encryption key. If no key is generated, SSH cannot be used. However, an
SSH session can be established regardless of security mode, as long as encryption key is
generated.
The current SSH implementation only employs a password authentication mechanism.
The publicKey based authentication mechanism is not supported in this release.
Invalid login protection

The following two situations are considered excessive invalid login attempts by a user, or
“intrusion violations.”
• The maximum number of consecutive failed login attempts has been reached
(regardless of time period or number of sessions).
• Two consecutive failed login attempts have been reached within the minimum time
interval.
In both cases, the system will automatically lock-out the user (disable login capability),
and record the user ID, IP address, and the source IP port number in the security log .
User activity logging

Alcatel-Lucent 1830 PSS supports logging of user activities. Activities are collected in a
user activity log (UAL) in a user-readable format. All user actions via the WebUI are
logged and stored in this UAL, along with the time and date of the action, the source IP
address and or user name of the operator, and the action itself. One entry is captured for
each user action. The purpose of this log is to provide non-repudiation.
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS also allows the administrator to transfer the UAL log to a
remote file server (RFS). The RFS can be the management system itself, or some other
server, as selected by the operator. This transfer mechanism can be performed using FTP
or SFTP.
Crypto key management for encrypted data exchange

The SSH server running on an NE uses an encryption key to encrypt/decrypt data
exchanged between the NE and external entities (e.g. SSH client).
• Currently, only the DSA key is supported. The RSA key will be supported in a future
release.
• Key generation is allowed only when the NE is in the normal mode, to prevent
accidental lockout.
• The Public key part of the Encryption key is not used for authentication. The NE uses
password based authentication only.
• If an encryption key is not generated, the NE will not change security mode from
normal to encrypted.
Encrypted file transfer With SFTP

Both Database Backup and Restore, and software download now support SFTP (Secure
File Transfer Protocol) data transfer. In this case, the NE communicates to an external
SSH server running on the DB backup and software repository machine.
The following notes apply to SFTP based download operations.
• All previous configuration supported in the CLI remains valid for both the operations
(e.g. config software ... or config database ... ).
• The option 'sftp' is now available under the 'server protocol' field, and must be used to
initiate SFTP based transfer,
• An SSH server must be configured using port 22.
• For software and database downloads, the applications running on the NE are SSH (or
SFTP) clients that connect to an external SSH server. Authentication is password
based only. No public key based authentication is performed in this release. As a
result, it is possible to initiate SFTP based database and software download operations
even when no encryption key is generated.
• Note that SFTP based operation may be somewhat slower than traditional tftp/ftp
based transfer.
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Time of day synchronization
Administration
....................................................................................................................................................................................................................................
Time of day synchronization

Overview
Alcatel-Lucent 1830 PSS supports the following:
• Provide time stamping accurate to within ±500 ms per day.
• Synchronize the network element clock from a Network Time Protocol (NTP) server,
using NTP server authentication to provide security.
The system uses a two-digit year, representing the two least significant digits of the year.
Note: In the current software release, gateway NE mediation services for NTP over
OSI and NTP control messages are not supported.
Each compound synchronizes independently.
Extension shelves synchronize to their related main shelf only (also via NTP).
Network Time Protocol synchronization

The following time-of-day synchronization modes are possible:
• Synchronized mode (default)
The internal time-of-day clock of the network element uses the calculated UTC from
the selected NTP server. The NE is polling the NTP server and periodically making
corrections to its internal clock to maintain the same time of day as the NTP server
All messages, event reports, logs, and events that carry time stamps use this time of
day: NTP UTC time
• Non-synchronized (holdover) mode
NTP is enabled but the NE has lost NTP server connectivity. The last known clock
update is used to synchronize the clock.
• Non-synchronized (free-running) mode
The NE is not synchronized to an NTP server and is instead using its own internal
clock as a source. This mode is applicable after a system startup when the system
could not yet synchronize to any of the provisioned NTP servers.
The operator can provision up to 10 NTP servers which are identified by their IP address.
NTP client operation

Alcatel-Lucent 1830 PSS supports an NTP interface over IP. The NTP interface operates
in client mode as defined in RFC 1305 (version 3 or version 4). Alcatel-Lucent 1830 PSS
interoperates transparently with NTP servers that support either version 3 or version 4.
When NTP becomes enabled, the NE selects the NTP server with highest quality timing
signal according to RFC 1305 methods.
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Time of day synchronization
Administration
....................................................................................................................................................................................................................................
Clock recovery on restart
In case of a power failure, the system is able to recover the time and date information
from an internal real time clock (RTC). The maximum bridge period is 15 min with an
accuracy of the timing information after recovery of ±1 s.
Each 15 minutes, the RTC device is updated with the current software clock. Upon NE
restart, the RTC device is read to get a correct clock until NTP works again.
Alcatel-Lucent 1830 PSS NE as NTP server

An Alcatel-Lucent 1830 PSS main shelf can act as an NTP server and perform all of the
standard functions of an NTP server to other network elements. The NTP server network
address may be the same as or different from the customer LAN network address.
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Automatic power adjustments
Administration
....................................................................................................................................................................................................................................
Automatic power adjustments

Automated optical power management system
Automated optical power management is a software system that controls variable optical
attenuators in the Alcatel-Lucent 1830 PSS to control the optical power levels on a
per-wavelength basis, and adjusts target gain setting and spectrum tilt of line driver
(amplifier) packs. Software Control of Optical Transmission (SCOT) is often used to
describe this system.
Several subsystems comprise the power management system:
• Stored target powers, amplifier gain ranges, and modeling parameters from the
Engineering Planning Tool (EPT)
• Pack level control loops
• Add wavelength power adjustment loop
• Amplifier gain and set-point adjustment functions
• Adjustment functions for adjusting power setpoints
• Optical channel technology type knowledge to facilitate use of per technology target
powers
When a system is commissioned, data from the EPT design is transferred to the network
elements (NEs) in the Alcatel-Lucent 1830 PSS. This data includes:
• Nominal target powers per-channel at key locations in the NE
• Expected minimum and maximum gains for amplifiers in the system
• Target Raman gain for Raman amplifiers
• Parameter values modeling the fiber plant
• Per channel technology target power offsets
• Values used to set Wavelength Tracker channel power deviation thresholds
The planning data can be transferred to the NEs either manually by entering the data
using one of the user interfaces (CLI, WebUI/ZIC) or by using the provisioning and
commissioning wizards in the Commissioning and Power Balancing (CPB) tool.
The amplifier minimum and maximum gain values provide operational bounds on the
gains of the amplifiers in the system and ties their gain ranges to the planning of the
network. When an amplifier gain must be set outside the planned range, a potential
optical signal-to-noise ratio (OSNR) problem is indicated within the network: The OSNR
of light paths travelling through this amplifier can experience more OSNR degradation
than planned.
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
Figure 19-1, “EPT parameters for WR-88A ROADM” (p. 19-22) illustrates an
automatically managed re-configurable optical add-drop multiplexer (ROADM) node
with the power targets, parameters, and gain ranges from the planning tool labeled. The
small green circles indicate Wavelength Tracker monitoring points that are used to
retrieve power readings used by the power management system.
Figure 19-1 EPT parameters for WR-88A ROADM
Pack level controls

Pack level loops maintain target output powers that have been calculated and set by the
power management system. There are three types of pack level control loop:
1. In one version, a system defined egress monitor point (or in the case of Anydirection
add/drop block, add or drop monitor point) is used to feedback channel power levels
at a regular rate to the Wavelength Selective Switch (WSS) pack directing channels to
the monitoring point. The channel powers can be from the embedded Wavelength
Tracker decoder, or from a WTOCM (or WTOCMA) pack monitoring that location.
The pack adjusts the variable attenuation for the channel provided by the WSS in a
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
controlled manner to guarantee stability of the system when many WSS blocks are
traversed by a light path. By continually comparing the present channel measured
power to the target channel power at the egress monitor point, the control loop
eliminates the error between the two. SCOT sets the target per channel power at the
egress monitor point.
2. In another version, the VOA used to control the output power of a wavelength at the
point a channel is added into the system is continuously adjusted to meet a target
power set by SCOT. The channel power measurement is local at the same point the
VOA is being adjusted in this case. An example is the embedded Wavelength Tracker
encode circuit of an Optical Translator pack.
3. In another version, the VOA used to control the output power of a wavelength at the
point a channel is added into the system is adjusted to meet a target attenuation set by
SCOT. In this case no local power measurement is made, and a higher level SCOT
loop calculates the required attenuation at the channel control point, which is then
realized by the lock pack loop. An example is the Optical Protection Switch with
Attenuator (OPSA) pack.
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
Figure 19-2, “Per-channel power control points within a TOADM node” (p. 19-24) shows
how channels are per channel equalized at the LINE Out port of Line 2.
Figure 19-2 Per-channel power control points within a TOADM node
Add loop
The add loop handles adjustments to the per channel set-point of a locally added channel.
The add loop periodically compares the measured channel power to the target channel
power at the designated monitoring point (the output port for a node degree, or the add
LD in an Anydirection single node add/drop block). Provided the add control point has
converged to the last adjustment, and is has not reached the limit of its adjustment range,
SCOT will update the target power (or attenuation) for the pack managing power of the
locally added channel. For example, in a TOADM node the add loop can modify the
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
target output power from an OT L1 port. In the case of a WSS in the add path towards the
monitor point, the add control point is only adjusted if the WSS attenuation reaches and
remains at 0 dB without the channel having reached the target power. Coordination
mechanisms exist within SCOT to suspend the add loop at appropriate times when other
SCOT actions occur.
Valid automatic and manual power adjustment configurations
The attribute setting for auto-power management must be consistent across the Through
path of a TOADM or ROADM node. Topological link creation is not allowed if it will
result in a mismatch of auto-power management attributes at opposite ends of a
TOADM/ROADM Through path. The through path is defined by the THRU port to
THRU port bidirectional connection between CWR8 packs or CWR8-88 packs or
WR8-88A packs or WR8-88AF packs or WR2-88 packs.
If a TOADM/ROADM Through path topology is established, when the auto-power
managed attribute of one external fiber is changed, the state of the other end of the
Through path will be changed to match.
The NE is capable of detecting and indicating an invalid auto-power managed Through
path.
Figure 19-3, “Valid automatic and manual power adjustment configurations”
(p. 19-26) illustrates valid and invalid combinations for the TOADM/ROADM Through
path.
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
Figure 19-3 Valid automatic and manual power adjustment configurations
Adjustment functions
For an Auto power managed line, several adjustment functions exist to adjust amplifier
gains, recalculate set-points, adjust amplifier spectrum tilt, and re-calculate Wavelength
Tracker expected powers.
Ingress adjustment
The ingress adjustment function adjusts the gain of the optical amplifier receiving an
incoming line, at the ingress LD, to compensate the loss from the preceding node’s egress
point to the output of the ingress LD. Target powers at the upstream node and the local
node define the required loss. If tilt adjustment is disabled, this function also set the tilt
setting of the ingress LD. Additionally, the function will calculate and set the gain for a
MESH4 pack connected to the ingress degree Wavelength Router pack in a ROADM
node, or in the case of a TOADM node will apply the per channel target powers to CLS
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
Out ports used for locally dropped services. Following a successful adjustment the
Wavelength Tracker expected powers and deviation thresholds are re-calculated and
applied.
Ingress adjustments can be run periodically by setting the auto gain adjust timer attributes
of the OMS segment for the OMS the ingress LD is part of. Running periodic adjustments
ensures that span loss changes are tracked, and the gain setting optimized for the current
channel set in transmission. The ingress adjustment can also be initiated through one of
the user interfaces.
Egress adjustment
The egress adjustment is used usually only when initially installing a system, or when
making equipment changes, or in some cases to make adjustments if the EPT parameters
for a degree have changed due to a new mix of OT types planned for the degree or
network.
The egress adjustment sets the gain of the optical amplifier on an outgoing line, at the
egress LD, to compensate the loss of the network element’s equipment between the
ingress LD output points and the egress LD, and to compensate for the worst case optical
channel power from the local add control points of the degree. Additionally the egress
adjustment will re-calculate the add power control points in relation to the current target
output power per channel at the output monitor location (potentially reflecting a new gain
setting for the egress LD), and walk them to their new setpoints in controlled steps. The
expressing channels for a TOADM or ROADM node will also be walked to their new
power levels. If there is no egress LD for the outgoing line, only the setpoint adjustment
phase is done. Following a successful adjustment the Wavelength Tracker expected
powers and deviation thresholds are re-calculated and applied. Loss checks for certain
paths in the node are also part of the egress adjustment.
The egress adjustment is initiated through one of the user interfaces.
Add adjustment
The add adjustment is used usually only when initially installing an Anydirection
add/drop block, or when making equipment changes, or in some cases to make
adjustments if the EPT parameters for the add/drop block have changed due to a new mix
of OT types planned for the add/drop block.
The add adjustment sets the gain of the add amplifier of an Anydirection add/drop block,
at the add LD, to compensate the loss of the network element’s equipment between the
OTs and the add LD output while accounting for the worst case optical channel power
from the add control points of the add/drop block. Additionally the add adjustment will
re-calculate the add power control points of the add/drop block in relation to the current
target output power per channel at the add monitor location (add LD output), and walk
them to their new setpoints in controlled steps. Following a successful adjustment the
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
Wavelength Tracker expected powers and deviation thresholds are re-calculated and
applied. Loss checks for certain paths in the add/drop block are also part of the add
adjustment.
The add adjustment is initiated through one of the user interfaces.
Drop adjustment
The drop adjustment is used usually only when initially installing an Anydirection
add/drop block, or when making equipment changes, or in some cases to make
adjustments if the EPT parameters for the add/drop block need to be changed.
The drop adjustment sets the gain of the add amplifier of an Anydirection add/drop block,
at the drop LD, to compensate the loss of the network element’s equipment between the
connectivity degree ingress LDs to the drop LD, and to provide the right per channel
output power into the add/drop block. The channels from the connectivity degrees to the
add/drop block will be adjusted to coincide with a new drop LD output power per channel
target. Following a successful adjustment the Wavelength Tracker expected powers and
deviation thresholds are re-calculated and applied. Loss checks for certain paths in the
add/drop block are also part of the add adjustment.
The drop adjustment is initiated through one of the user interfaces.
Tilt adjustment
The tilt adjustment runs automatically when enabled for a degree, and sets the optical
amplifier tilt profile by calculating the required tilt compensation to counteract spectrum
tilt induced in the transmission fiber. In response to changing channel load, the spectrum
tilt of the ingress or egress LD of a degree is adjusted. As part of adjusting the spectrum
tilt setting, the Wavelength Tracker channel expected power values will be adjusted. The
compensation for Stimulated Raman Scattering is only applied in long haul context
networks using WTOCM or WTOCMA packs for channel power monitoring. This
adjustment can be disabled, but this is not recommended for auto power managed
degrees.
Summary of automatic power management features

The automatic power management system enables the following features:
• Automated service turn-up.
• Automatic compensation for loss changes in the network up to a limit.
• One-touch commissioning using the Commissioning and Power Balancing tool (CPB)
for certain network topologies.
• Automatic power adjustments in response to changing channel loading.
....................................................................................................................................................................................................................................
Administration
....................................................................................................................................................................................................................................
• Network level coordination between WSS attenuation control loops to avoid storing
too much loss in the WSS (to avoid overshooting channel nominal power profile).
• Alarms to indicate when operator intervention is required to trigger one of the
adjustments that require user initiation.
Finally, automated power management can be disabled on a line-by-line basis to allow
mixing static OADM network elements with reconfigurable OADM network elements
within the same system. The ability to disable automated power management and use
manual power management also allows Alcatel-Lucent to be flexible when solving
network problems presented by the customer.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Maintenance
Overview
Purpose
This section provides information on the maintenance functionality of Alcatel-Lucent
1830 PSS.
Definition
Maintenance is the capability of the system to continuously monitor its equipment and the
signals that it carries to notify the user of any current or potential problems. The
monitoring enables the user to take appropriate proactive (preventive) or reactive
(corrective) actions.
Reference
For detailed maintenance and trouble-clearing procedures see the Alcatel-Lucent 1830
Photonic Service Switch (PSS) Release 8.2 Maintenance and Trouble-Clearing Guide.
Contents
Fault detection and alarm management 19-31

Loopbacks 19-35
System diagnostics and tests 19-41
Performance monitoring 19-44
Thresholding 19-68
Software management 19-72
Configuration database management 19-73
Protection 19-76
Reports 19-104
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Fault detection and alarm management
Maintenance
....................................................................................................................................................................................................................................
Fault detection and alarm management

Overview
Fault management is a set of functions that enable detection, isolation, and correction of
abnormal operation of the telecommunication network and its environment.
Alarm reporting is the notification to external management systems of the internally
detected faults.
The fault processing and alarm reporting functions are part of the supervision function of
the NE that monitors and manages the NE transmission resources (logical/physical
facilities and associated equipment modules).
Fault management functions

The fault management function consists of the following supervision categories:
transmission, equipment, processing, and correlation. The primary goal of this function is
to monitor and report any failure within the Alcatel-Lucent 1830 PSS system by
identifying the probable cause of abnormal operation of transmission resource supported
by the NE.
Transmission supervision
Transmission supervision consists of the following functions.
• Continuity supervision (monitoring of LOS, UNEQP, OCI, etc.)
• Connectivity supervision (monitoring of TIM)
• Quality supervision (monitoring of DEG and EXC)
• Payload type supervision (monitoring of PLM)
• Multiplex structure supervision (monitoring of payload structure mismatch, PSM)
• Alignment supervision (monitoring of LOF, LOM, and Loss of alignment in VCAT or
GFP frame stream)
• Protocol supervision (monitoring of FOP in protection configurations)
• Backward indication supervision (monitoring for BDI, BIAE, and RDI)
• Alarm correlation and suppression (generation and monitoring of AIS, FDI, and SSF)
Transmission supervision is implemented according to the specific functional model of
the facility being supervised. Details on set of monitored points, detection criteria, and
condition types are provided in the Alcatel-Lucent 1830 Photonic Service Switch (PSS)
Release 8.2 Maintenance and Trouble-Clearing Guide.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Equipment supervision
Equipment supervision provides monitoring, detection, and isolation of equipment-related
problems and abnormal behavior. In general, equipment supervision comprises the
supervision of interchangeable and non-interchangeable units and cables. Probable causes
in this category include power, timing, temperature, and other equipment specific
abnormalities.
Note: During configuration card temperature range should be set to -5 and +90 for
proper system behavior.
Processing supervision
Processing supervision is generally associated with a software or software processing
fault. Probable causes in this category include: software errors, communication errors,
version mismatches, DB consistency errors, etc.
Correlation and suppression
A correlation and suppression function is performed in order to isolate the root cause of
the abnormal system operation. It also suppresses alarming in downstream NEs that are
involved in providing end-to-end service.
Alarm reporting
The Alcatel-Lucent 1830 PSS system provides defect processing, correlation, and
probable cause declaration for each piece of equipment and facility and generates
autonomous message towards the management system (alarm or event) based on the
provisioned alarm severity.
The NE supports five levels of NE condition reporting: CR, MJ, MN, WR, and No Alarm.
A No Report condition is supported for conditions not reported.
• Conditions with a notification code CR (critical), MJ (major), MN (minor), WR
(warning) are reported as alarms.
• Conditions with a notification code NA (Non Alarmed) are reported as events
(standing conditions).
• Conditions with a notification code NR (Not Reported) are autonomously reported but
can be retrieved by user.
All alarms and conditions are available to the management systems as follows:
• Alcatel-Lucent 1830 PSS supports autonomous reporting and logging of all alarms
and conditions via WebUI or SNMP interfaces.
• Alcatel-Lucent 1830 PSS supports retrieval of all alarms and conditions via CLI,
WebUI or SNMP interfaces.
• Management and retrieval of alarm logs is available via CLI, WebUI, and SNMP.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
• All alarms that are reported by the system shall be time-stamped at the source.
• All standing conditions are retrievable regardless of whether these conditions are
reported or not. GR-474-CORE defines a standing condition as follows: “A standing
condition is a state of the NE that can be determined by inspection (e.g., examining a
light display) or by interrogating the NE (e.g., sending a request for status information
through an OS).”
A user can define and modify the severity designated to a particular condition by
configuring a specified alarm severity.
The following are the three levels of severity provisioning in the system.
• Each condition type in the system has a factory default severity.
• Each condition type in the system has a provisionable, system-wide factory override
severity with a higher priority than the factory default for the condition type.
• Each specific entity (AID) in the system has a provisionable severity with a higher
priority than the factory override or factory default for the condition type.
The system-wide factory override severity and specific entity severity are provisionable
via CLI, TL1, and SNMP.
Effect on service declaration

The NE supports the capability of reporting Service Affecting (SA) alarms and
Non-Service Affecting (NSA) alarms. In general, failures impacting any traffic are
Service Affecting when no protection exists or when protection is not operational, and the
alarms impacting no traffic are Non-Service Affecting.
Typically, NSA alarms have a default severity of Minor or below, and SA alarms have a
default severity of Major or Critical. The condition’s report and retrieval processing
include the alarm effect on service parameter (SA/NSA).
Changing the alarm severity while some conditions on the facility are present might not
impact the existing conditions until they clear and get declared again.
For purposes of generating alarm and event reports, time-hysteresis filtering is applied to
all signal conditions as described in GR-253. A condition must be present continuously
for 2.5 seconds before an alarm report is generated, and it must be absent for 10 seconds
before a CLEAR is generated. Some OTS and OCH layer transmission conditions that are
based on analog power monitoring are integrated over longer time periods to avoid
reporting network transient events.
Reported facility conditions correctly identify the underlying equipment source of the
problem. That is, the bay-shelf-slot part of the facility ID refers to the equipment on
which the fault exists.
Reports of alarms and conditions originating from facilities on non-failed equipment as a
result of secondary facility effects are suppressed.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Audible alarm indications
The NE provides audible alarm dry contacts and alarm cut-off capability per GR-833. The
alarm cut-off function (OPR-ACO) removes the signal from the dry contacts, but it does
not change the internal state of the NE, nor affect any of the visual indicators.
The NE provides a visual alarm summary display on the user panel via one LED for each
alarm severity (see LED).
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Loopbacks
Maintenance
....................................................................................................................................................................................................................................
Loopbacks
Loopback definition
A loopback is a troubleshooting feature in which a signal is connected back to the source
from which it came to establish good transmission along one segment of a multi-segment
path. The transmitted and received signals are measured and evaluated by the user to
ensure that the received signal is identical to the original signal. Information described
here about loopback operations is consistent for both OCS and WDM compounds, except
where noted specifically for one or the other.
Note: A loopback is a disruptive operation. It is normally employed as a diagnostic on
a failed facility which must be taken out of service. Therefore it is not expected that
an entity in loopback will function correctly as a member of a protection group.
Signal and overhead monitoring will be affected by an inserted signal (for example,
AIS). In the case of a terminal loopback, ingress monitoring is compromised for both
transparent and nontransparent overhead modes since the ingress signal is overwritten
by the looped back signal at the interface.
Special consideration needs to be taken when looping back a facility that is designated as
a possible timing reference in the network, or may contain a signal that is designated as a
possible timing reference. The loopback may affect network timing. One situation in
which this can happen is if a facility loopback is set on a signal that is being used by the
far end network element as a timing reference. It may also occur if a terminal loopback is
set on a facility that can be used at that same network element as a timing reference. The
operator needs to ensure that the affected timing reference is locked out at the appropriate
network elements.
Controlling loopbacks
Loopbacks can be enabled and disabled using Alcatel-Lucent 1350 OMS or
Alcatel-Lucent 1830 PSS ZIC. See the Alcatel-Lucent 1830 PSS User Provisioning Guide
or the respective management system documentation.
Loopback types
In general, the following types of loopbacks are possible:
• Facility loopback
• Terminal loopback
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-4 Loopback types
Facility loopback
Client port card Matrix Client port card
O/E E/O
(AIS)
O/E E/O
Terminal loopback
Client port card Matrix Client port card
O/E E/O
(AIS)
O/E E/O
g-pipg-0275
Loopbacks are possible on the following facility types:

• OTN (OTU2, OTU2e, OTU3, OTU3e2)
• SDH (STM-1, STM-4, STM-16, STM-64)
• SONET (OC-3, OC-12, OC-48, OC-192)
• Ethernet (1 Gb/s, 10 Gb/s)
If a facility is used in a loopback, the "Active Loopback" condition type (“ACTLPBK”) is
assigned to it.
Facility loopbacks
In a facility loopback, the received incoming signal is connected to the associated
transmitter in the return direction. These loopbacks can be used to test the correct cabling
between two network elements including the involved interface ports. Depending upon
card, facility loopbacks are supported for OTH, SDH/SONET, and Ethernet signals.
Facility loopbacks can be set up as follows:
• Transparent, that means, the signal transmitted in the downstream direction is not
changed
• Force AIS insertion (for OTH/SDH/SONET)
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
• CSF insertion (for Ethernet)
• Shut off the transmitter
The incoming signal in the upstream direction is terminated during the loopback and an
AIS is created.
Terminal loopbacks
In a terminal loopback, the signal that is about to be transmitted is connected to the
associated incoming receiver. These loopbacks can be used to test signal paths through a
network element. Depending upon card, terminal loopbacks are supported for
SDH/SONET, OTH (except uplink cards), and Ethernet signals.
Terminal loopbacks can be set up as follows:
• Transparent, that means, the signal transmitted in the downstream direction is not
changed
• Force AIS insertion (for SDH/SONET and OTH)
• Insertion of a replacement signal (for Ethernet)
Unused signals in the incoming direction of transmission are automatically terminated.
Depending on the configuration of consequent actions, an appropriate consequent action
signal is inserted into unused signals in the outgoing direction of transmission, or the
looped signal is continued in the outgoing direction of transmission.
WDM OT loopback details

The following are some of the key behaviors of a loopback on a WDM transponder card:
• An optical transponder port that has a loopback operated on it, cannot be placed into
service.
• A facility cannot be deleted while a loopback is active.
• Operated loopbacks are persistent on an NE, and will survive a system restart, and an
in-service upgrade.
However, during system restart the looped signal may be temporarily interrupted.
• Loopback operation is independent of the presence of Y-cable protection. Either of the
two supported loopback types can be configured on ports that are members of a
protection group regardless of the state of the protection. (APS is not aware of
loopback status).
• Only one loopback (facility or terminal) can be active on a facility at a time.
• Loopbacks are not supported in REGEN mode on 112SCX10 or 43SCGE1.
• When operated, a loopback on a WDM optical transponder will result in one of the
following conditions, as detailed in Table 19-22, “WDM OT loopback behaviors”
(p. 19-38):
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
- Loopback&Cut: The signal received by the local client is looped back and the
remote client transmits maintenance signal.
- Loopback&Continue: The signal received on the local client is looped back and also
continues toward the remote client which transmits it normally.
Table 19-22 WDM OT loopback behaviors
OT Card Client WDM

Terminal Facility Terminal Facility
11DPM12 Loopback & Cut Loopback & Cut Loopback & Loopback &
(OTU1 Client Continue Continue
11DPM12 Loopback & Cut Loopback & Cut Loopback & Cut Loopback & Cut
(STM-1, STM-4,
STM-16, GbE, FE,
SD-SDI, HD-SDI,
FC-100, FC-200,
FC-400)
11QPA4 Loopback & Cut Loopback & Cut Loopback & Loopback &
(10G LAN GFP-F Continue Continue
mapping mode)
11QPA4 Loopback & Cut Loopback & Loopback & Loopback &
(OTU2, STM-64, 10G Continue Continue Continue
FC, 8G FC, 10G LAN
CBR mapping mode)
11DPE12E1 3 Loopback & Cut Loopback & Loopback & Loopback &
Continue2 Continue2 Continue2
11DPE121 3 Loopback & Cut Loopback & Cut Loopback & Loopback &
Continue2 Continue2
11STMM10 Loopback & Cut Loopback & Cut Loopback & Loopback &
Continue Continue
11STAR1 Loopback & Cut Loopback & Cut Loopback & Cut Loopback &
(STM-64, 10G FC, 10 Continue
GbE - CBRLAN
11.049 & 11.096)
11STAR1 Loopback & Cut Loopback & Cut Loopback & Loopback &
(OTU2, 10 GbE Continue Continue
GFP-F & GFP-P)
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-22 WDM OT loopback behaviors (continued)
OT Card Client WDM

11STAR1A Loopback & Cut Loopback & Cut Loopback & Cut Loopback & Cut
(STM-64, OC-192,
10G WAN,
10GLAN-CBR,
10GFC, 8GFC)
11STAR1A Loopback & Cut Loopback & Cut Loopback & Loopback &
(10GLAN-GFP ) 1 Continue2 Continue2
11STAR1A Loopback & Cut Loopback & Loopback & Loopback & Cut
(OTU2) Continue Continue
43STX4 Loopback & Cut Loopback & Cut Loopback & Cut Loopback & Cut
43STX4P Loopback & Cut Loopback & Cut Loopback & Cut Loopback & Cut
43SCX4 Loopback & Cut Loopback & Loopback & Loopback &
Continue Continue Continue
43STA1 NA NA Loopback & Cut Loopback & Cut
43STA1P NA NA Loopback & Cut Loopback & Cut
43SCA1 Loopback & Cut Loopback & Loopback & Cut Loopback & Cut
Continue
43SCGE1 Loopback & Cut Loopback & Loopback & Loopback &
43SCX4E Loopback & Cut Loopback & Loopback & Loopback &
112SNX10 Loopback & Cut Loopback & Loopback & Loopback &
112SCA1 Loopback & Cut Loopback & Loopback & Loopback &
112SNA1 Loopback & Cut Loopback & Loopback & Loopback &
112SDX11 Loopback & Cut Loopback & Loopback & Loopback &
Note: 16GFC is an
exception. Refer 4
for details.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-22 WDM OT loopback behaviors (continued)
OT Card Client WDM

130SNX10 Loopback & Cut Loopback & Loopback & Loopback &
130SCA1 Loopback & Cut Loopback & Loopback & Loopback &
260SCX2 Loop & cut Loop & Continue Loop & Continue Loop & Continue
D5X500 Loop & Continue Loop & Cut Loop & Continue Loop & Cut
4DPA4 Loopback & Cut Loopback & Cut Loopback & Loopback & Cut
(STM-16, FC400, 1 Continue
GbE, Electrical FE)
4DPA2 Loopback & Cut Loopback & Cut Loopback & Cut Loopback & Cut
(STM-16)
Notes:
1. All behaviors apply for both LOSPROP = LaserON, except where noted.
2. Behavior is “Loopback & Cut” when LOSPROP = Laser OFF
3. This behavior assumes Virtual Time Slot Connection (VTS XC) is up.
4. The exception occurs because the client port of the far end, where the line facility loopback is active, fails to
send valid FC16G signal out.
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and System diagnostics and tests
Maintenance
....................................................................................................................................................................................................................................
System diagnostics and tests

Introduction
Inherent automatic diagnostics functionality has been proven to significantly reduce
network operators’ ongoing operating expense. Consequently, this functionality is
demanded by customers in all public network quality telecommunications systems /
products. Alcatel-Lucent 1830 PSS offers diagnostic functionality to support service
availability and reliability commensurate with customer expectations for this very high
bandwidth.
Equipment protection switching diagnostics

Alcatel-Lucent 1830 PSS autonomously detects and reports hardware and software (for
example, watchdog timer) failures, independent of whether the failed module or unit is in
an active or standby (inactive) mode.The Equipment protection switching time for
transmission affecting failures is below 60 ms, detection time included. Alcatel-Lucent
1830 PSS autonomously detects and reports failures of any intra-system transmission path
(for example, includes communication paths such as LAN cables and traffic carrying
paths).
Communication bus diagnostics

Communication or routing discrepancies on the internal communication buses are
resolved autonomously.
Card Presence and Fault Indication Signal diagnostics

The Card Presence Indication signal is used within a subrack so that the FLC or SLC
processors are able to detect when a circuit pack is removed or a circuit pack is installed.
The system detects failed or missing passive (for example, data and LAN cables) and
non-processor-based system components, as well as “intelligent” processor-based
modules.
Database operation and monitoring diagnostics

Alcatel-Lucent 1830 PSS monitors and takes appropriate corrective action to insure data
consistency. This implies successful transfer of data between processors, consistent data
throughout processors and storage devices, data consistent with hardware.
Digital diagnostics monitoring

All analog optical parameters such as Optical Transmit Power, Optical Receive Power,
and so on, are monitored by Digital Diagnostic function provided by optical modules.
These DDM parameters are monitored on nominal operation condition (with
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
corresponding Baud & reference pattern defined in the specification) and inside the
allowed operating specified EOL range. DDM accuracy is calibrated on such conditions
before module delivery. For example, DDM for Optical Transmitted Power is not valid
when Transmitter is disabled. Especially pointed out here, regarding Optical Transmit
Power for EML XFP, DDM accuracy cannot be guaranteed in case of modulation signal
absence.
Autonomous module diagnostics

Before a module is allowed to transition into an in-service state, the module will be
autonomously tested and verified to be free of any faults. The tests are intrusive or non
intrusive depending on module function/level.
All modules provide autonomous module power-up self-test diagnostics when the module
is powered on, inserted, and recovered to its previous state, or hardware reset.
The power-on self test is triggered by any type of reset of a circuit pack or a device (for
example, an FPGA). This includes resets caused by the following:
• Power on of device / circuit pack / system
• Autonomous or operator triggered reset
• Reset as a consequence of a software or firmware download
The visual indicators of the plug-in units change dependent on the result of the self test
(see “Operations interfaces” (p. 19-3)).
Autonomous recovery of failed modules

Once a module has been declared failed and the detected failure is caused by the system's
environment (for example, too high temperature), then the system periodically tests the
module to see if the failure of the module has gone away. When the failure has gone
away, the module will be put back into service. A persistency filter interval of at least 10 s
avoids too frequent changes.
Lamp test
Alcatel-Lucent 1830 PSS provides one lamp test button on each FLC (PSS-64, PSS-36)
or User Panel (PSS-32 and PSS-16). Pressing the lamp test button on any FLC in the
main shelf activates a lamp test.
When a lamp test is triggered the system lights all LEDs in all shelves of the compound
for 30 seconds. After the 30 seconds the LEDs return to their normal states. “all LEDs”
refers to the following LEDs:
• FLC (PSS-36): LED1 - LED8
• Matrix (PSS-36): LED1, LED2
• User Panel (PSS-32/16): LED3 - LED8
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
• PSF: LED1, LED2
• FAN Unit: LED2
• other I/O Packs: Status LED, Port Status LEDs (if present)
“all LEDs” radiate in amber with the following exceptions:
• The status LED on the SFC8 radiates in green.
• The LOS LED on the SFC8 radiates in red.
• The critical alarm LED on an FLC (PSS-36) or User Panel (PSS-32/16) radiates in
red.
• The major alarm LED on an FLC (PSS-36) or User Panel (PSS-32/16) radiates in red.
The lamp test is applied to all cards where the provisioned type is equal to the actual type.
I/O cards equipped with port level LEDs must be in service (IS), otherwise the port LED
test cannot be assured.
Alcatel-Lucent 1830 PSS allows to trigger the lamp test procedure via management
interface(s). If a lamp test is triggered, while a lamp test is in progress, the trigger is
ignored.
Inter-shelf cabling diagnostics

Alcatel-Lucent 1830 PSS continuously monitors the inter-shelf cabling (via the ES1/ES2
interfaces on the matrices) and derives a shelf topology. This derived shelf topology (from
the perspective of the main shelf) is made available to the operator via the management
interface. This information supports the operator when inter-shelf cabling issues arise
during installation. Alcatel-Lucent 1830 PSS indicates an inter-shelf cabling problem
between the given shelf and another shelf.
Physical layer monitoring for uplink cards

Alcatel-Lucent 1830 PSS provides a physical optical layer monitoring for the optical
interfaces OCH of the DWDM uplink cards for OTU2, OTU2e and OTU3e2 in transmit
and receive direction. This monitoring is only applicable for the uplink cards.
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Performance monitoring
Maintenance
....................................................................................................................................................................................................................................
Performance monitoring
General performance monitoring (PM) processing
Performance Monitoring processing in the Alcatel-Lucent 1830 PSS provides the
following functions.
• Monitors and accumulates digital and analog parameters pertinent to a specific
physical or logical access point (see further detailed description of monitoring types
on specific Alcatel-Lucent 1830 PSS NE entities)
• Stores and manages history accumulation data (up to thirty-three 15-minute and seven
1-day accumulation registers can be stored)
• Validation and threshold crossing processing
• Manages threshold values through profile assignment to individual port entities
• Free-running counters for all monitored points
Performance Monitoring functions are performed on physical and logical points within
the Alcatel-Lucent 1830 PSS NE representing the boundary with other NEs or an external
system. A user can define and monitor Quality Of Service at individual points in which
local NE interacts with other network entities.
PM Profiles are applicable per card and per port. For a port that can support different
FPGA/Signal types, profile ID's listed include all possible profile types for the port.
Profile ID's can be pre-provisioned. SONET/OPR/OPT profile ID's are applicable for
OC192. Profile ID's like OTU/ODURX/ODUTX/OPR/OPT are for OTUx rate.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Refer to Figure 19-5, “Alcatel-Lucent 1830 PSS PM points” (p. 19-45) for an illustration
of performance monitoring points.
Figure 19-5 Alcatel-Lucent 1830 PSS PM points
The identified points in Figure 19-5, “Alcatel-Lucent 1830 PSS PM points”

(p. 19-45) provide the following transport layer and PM monitoring types:
1. OTS layer → monitored type(s): Total OPR
OCh channel within the OTS → monitored type(s): OPR
2. Internal monitoring point for SCOT and diagnostics (not included in PM processing
related to binning and reporting)
6. OTS layer → monitored type(s): TOPT
OCh channel within the OTS → monitored type(s): OPT
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
7. OPS layer → monitored type(s): OPR & OPT (In addition, for 40G and 100G
coherent cards, Chromatic Dispersion (CD), Differential Group Delay (DGD), and
Frequency OFFset (FOFF) are monitored.)
OTUk layer → monitored types: BBE, ES, SES, UAS, FEC-EC, FEC-UBC,
BERpreFEC, BERpostFEC, IAES and BIAEs
ODUk layer → monitored types: BBE, ES, SES and UAS
ODUkTCM layer → monitored types: BBE, BIAES, IAES, ES, SES & UAS
8. Client Optical → monitored types (s): OPR & OPT
9. OSC Receive direction → monitored type(s): OPR, CV, ES, SES, SEFS
10. OSC Transmit direction → monitored type(s): OPT
Whereas 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.
In addition to physical and logical (OCh) facility-related PM support, the Alcatel-Lucent
1830 PSS NE supports monitoring of the equipment controller (EC) processing use of
resources.
The controller card provides monitoring as well as 15-minute and 1-day register
accumulation and provides storage of the following resource utilization statistics.
• Average CPU use
• Peak Heap use
• Peak Memory Pool use
Threshold crossing alert management

Alcatel-Lucent 1830 PSS provides users with the ability to configure and manage
threshold crossing alert message generation for every PM monitoring entity. Designated
threshold for the monitored type is considered crossed when the value in the current
register is equal to or exceeds the value in the corresponding threshold register.
Threshold Crossing Alert (TCA) occurrence is reported through REPT EVT messages or
SNMP traps upon recognition of the threshold crossings. A TCA is considered a transient
condition (implicitly cleared at the end of associated accumulation period).
Users can manage threshold values (change the threshold or disable threshold alert
generation) by modifying threshold attributes in the TCA profile assigned to an
Alcatel-Lucent 1830 PSS NE port entity.
Alcatel-Lucent 1830 PSS supports the following TCA profile types.
• OC_N (SONET port section monitoring)
• STM_N (SDH port section monitoring)
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
• DW (FEC, OTUk and ODUk layer PM parameters for OT cards)
• OTUPM (OTUk PM layer for Client/Line cards and some OT cards)
• ODURX (ODUk PM layer (receive direction) for Client/Line cards and some OT
cards)
• ODUTX (ODUk PM layer (transmit direction) for CLient/Line cards and some OT
cards)
• ETH (Ethernet group, RMON statistic)
• INF (Interface group)
• PCS (PCS layer monitoring for Ethernet/FC ports)
• CP (Equipment PM parameters, applicable to EC, processor resources statistics)
• OPR (Optical Power Received on OT and OSC points)
• OPT (Optical Power Transmitted on OT and OSC points)
Nine instances of each profile type are supported. The user can inhibit individual monitor
type TCA messages by setting the threshold value in a TCA profile assigned to a facility
to 0 if the parameter is digital or to -99.99 dB if the parameter is analog. The Profile with
index 8 contains factory default data with 15-minute and 1-Day defaults pre-loaded.
Profile 8 is a view-only profile, and cannot be modified by the user. Profiles with indices
1-7 are initialized with all values set to 0, and can be customized by the user. During
upgrades from prior releases to Release 6.0, values contained in Profiles 1-7 are retained.
Each port facility can be assigned one or more profile instances.
When a port is created, the network element automatically assigns default profiles within
the applicable profile types to the port for each time period (15-min and 1- day).
Analog parameter TCAs
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.
Two types of thresholds exist.
• 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. TCA notification is raised when tidemark high exceeds the defined
notifyHigh value for the parameter and time period or when tidemark low drops below
the defined notifyLow value for the parameter and time period.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Refer to Figure 19-6, “Analog parameter TCAs” (p. 19-48) for an illustration.
Figure 19-6 Analog parameter TCAs
Note that term exceed used with tidemark low/high monitored parameters indicates that
tidemark high value is greater than the corresponding threshold or that tidemark low is
below the corresponding threshold.
For OT physical layer OPR, OPT parameters TCA profiles contain values for positive and
negative deviation relative to established baselined analog value for that port. Baselining
of OPR/OPT values can be established automatically (at the point the input signal is
applied to the port initially or laser initially enabled) or manually by user command.
Baselining applies to OT and OSC ports but does not apply to OCh and OTS ports. OCh
and OTS port thresholds are established during the commissioning phase.
Digital PM parameters
PreFEC and PostFEC BER (Bit Error Ratio) are the error ratios calculated through the
count of the corrected FEC error bits (FECC) and uncorrected FEC error blocks
(FEC-UBC).
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
The NE software reports the BER to the management system as an integer through the
management interface. The management system displays the BER in a user-friendly
format.
The following uplink I/O cards support the monitoring of PreFEC and PostFEC BER:
• 130SCUP
• 130SCUPB
• 130SCUPC
• 43SCUP
Each uplink port with OTUk signal type provides monitoring of preFEC and postFEC
BER based on 1 second interval measurements as base for the 15-minutes and 1-day
accumulation.
The BER is accumulated and averaged only in valid seconds, during which no LOS and
LOF defects are detected. For 43SCUP the LOF defect is not accessible for valid seconds
calculation and cannot be considered for the BER calculation.
The NE inhibits the accumulation of OCh to OTUk layer adaptation performance
parameters for OTN entities on uplink cards in the case of LOM defects.
Specific PM monitoring parameters

Alcatel-Lucent 1830 PSS optical transponders (OTs) provide a variety of signal types that
a user can configure. Each of the specific signal types includes optical physical layer
monitoring points as well as one or more digital layer monitoring points.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
The following tables list the digital layer monitoring groups that Alcatel-Lucent 1830 PSS
supports.
Table 19-23 SONET Section PM parameters
Parameter Mnemonic per T1.231 Definition

Coding Violations CV-S Count of BIP-8 (Byte B1)
errors
Errored Seconds ES-S Count of seconds with (B1)
Errors ≥ 1 or SEF ≥ 1 or LOS
≥1
Severely Errored Seconds SES-S Count of seconds with (B1)
Errors ≥ x2 or SEF ≥1 or LOS
≥1
Severely Error Frame SEFS-S Count of seconds with SEF ≥
Seconds 1
Coding Violations
Notes:
1. Value “x” is based on GR-253, T1.231 definition of SES for specified signal.
2. SES is a count of seconds in which there are excessive errors. It is not an error count or an
indication of the error rate.
Table 19-24 SONET Line PM parameters

Coding Violations CV-L Count of BIP (Byte B2) errors
Errored Seconds ES-L Count of seconds with (B2)
Errors ≥ 1, or SEF ≥ 1, or
LOS ≥ 1
Severely Errored Seconds SES-L Count of seconds with (B2)
Errors ≥ x2, or SEF ≥ 1, or
LOS ≥ 1
Unavailable Seconds UAS-L 10 or more seconds of SES
Far End Coding Violations FECV-L Count of M1 Byte errors
(REI-L) and SES-L=0
Far End Errored Seconds FEES-L REI-L ≥ 1, or RDI-L ≥ 1 and
SES-L=0
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-24 SONET Line PM parameters (continued)

Far End Severely Errored FESES-L Count of seconds with REI-L
Seconds Errors ≥x2, or SEF ≥ 1, or
LOS ≥ 1 and SES-L=0
Far End Unavailable Seconds FEUAS-L 10 or more seconds of SES
Notes:
Table 19-25 SDH regenerator and multiplex section PM parameters
Parameter Mnemonic Definition

Background Block Errors BBE-RS Σ (pN_EBC for all seconds not declared
SES)
Errored Seconds ES-RS Count of seconds with pN_EBC ≥ 1 or
OOF ≥ 1 or LOS ≥ 1
Severely Errored Seconds SES-RS Count of seconds with Block Errors ≥ x2
or OOF ≥ 1 or LOS ≥ 1
Unavailable Seconds UAS-RS 10 or more seconds of SES
Notes:
1. pn_EBC indicates event of detecting a block error in STM-N structure. ITU-T and ETSI
documents define pN_DS event which contributes to ES, SES, and UAS declaration. This
simplified approach is consistent with pN_DS definition in referred documents.
2. Value “x” is based on G.784 definition of SES.
Table 19-26 OTUk, ODUk, and ODUkTCM Near-END PM Parameters
Parameter Mnemonic CLI MONTYPE Definition

Background Block BBE-OTU RX SM BIP8 Error Count of BIP-8 (SM
Errors Count BIP-8) errors for all
seconds not declared SES
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-26 OTUk, ODUk, and ODUkTCM Near-END PM Parameters (continued)

Errored Seconds ES-OTU RX SM Error Count of seconds with
Seconds (SM BIP-8) Errors ≥ 1 or
LOF = True or LOM =
True or LOS = True
Severely Errored SES-OTU RX SM Severely Count of seconds with
Seconds Error Seconds (SM BIP-8) Errors ≥ x2 or
LOF = True or LOM =
True or LOS = True
Unavailable Seconds UAS-OTU RX SM Unavailable 10 or more seconds of
Seconds SES
Incoming Alignment IAES RX SM IAE Seconds Count of IAE seconds
Error Seconds and LOS=False or
LOF=False or
LOM=False
FEC Corrected FECC RX RS Corrected Count of FEC Errors
Errors Count Corrected3 and LOS =
False and LOD = False
FEC Uncorrected FECUBC RX RS Uncorrected Count of Uncorrectable
Bits Count Bits and LOS = False and
LOF = False
PreFEC Bit Error BERPreFEC Rx preFEC Bit Error Count of preFEC bit error
Ratio Ratio ratio and LOS=False and
LOF=false
PostFEC Bit Error BERPostFEC Rx postFEC Bit Error Count of FEC
Ratio Ratio uncorrectable bit error
ratio and LOS=False and
LOF=false
Background Block BBE-OTU RX PM BIP8 Error Count of BIP-8 (PM
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................

Errored Seconds ES-ODU RX PM Error Count of seconds with
Seconds (PM BIP-8) Errors ≥ 1 or
LOF = True or
LOM = True or
LOS = True or
AIS = True or
OCI = True or
LCK = True or
TIM = True or
PLM = True
Severely Errored SES-ODU RX PM Severely Count of seconds with
Seconds Error Seconds (PM BIP-8) Errors ≥ x2 or
LOF = True or
LOM = True or
LOS = True or
AIS = True or
OCI = True or
LCK = True or
TIM = True or
PLM = True
Unavailable Seconds UAS-ODU RX PM Unavailable 10 or more seconds SES
Seconds
Background Block BBE-TCM RX TCM BIP8 Error Count of BIP-8 (TCM
Incoming Alignment IAES-TCM RX STAT Count of seconds with at
Error Seconds least one TCM STAT IAE
defect occurred
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................

Errored Seconds ES-TCM RX TCM Error Count of seconds with
Seconds (TCM BIP-8) Errors ≥ 1
or
SSF=True or
AIS = True or
OCI = True or
LCK = True or
LTC = True or
TIM = True or
Severely Errored SES-TCM RX TCM Severely Count of seconds with
Seconds Error Seconds (TCM BIP-8) Errors ≥ x
(see note 2) or
SSF = True or
AIS = True or
OCI = True or
LCK = True or
LTC = True or
TIM = True
Unavailable Seconds UAS-TCM RX TCM Unavailable 10 or more seconds SES
Seconds
Notes:
Table 19-27 OTUk, ODUk, and ODUkTCM FarEND PM Parameters

Background Block FEBBE-OTU Rx Far-end SM BIP8 Count of OTU-BEI errors
Errors Error Count for all seconds not
declared far-end SES and
near-end defect seconds.
A far-end block error has
occurred if the BEI value
is between 1 and 8;
otherwise, no far-end
block error has occurred.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-27 OTUk, ODUk, and ODUkTCM FarEND PM Parameters (continued)

Backward Incoming BIAES-OTU Rx BIAE Seconds Count of seconds with at
Alignment Error least one OTU BIAE
Seconds defect occurred.
Errored Seconds FEES-OTU Rx Far-end SM Error Count of all seconds not
seconds declared near-end defect
seconds with (OTU BEI)
Errors ≥ 1 or (OTU BDI)
= True.
Severely Errored FESES-OTU Rx Far-end SM Count of all seconds not
Seconds Severely error declared near-end defect
seconds seconds with (OTU BEI)
Errors > x (see note 2) or
(OTU BDI) = True.
Unavailable Seconds FEUAS-OTU Rx Far-end SM 10 or more seconds SES
unavailable error
seconds
Background Block FEBBE-ODU Rx Far-end PM BIP8 Count of ODU-BEI
Errors Error Count errors for all seconds not
declared not declared
far-end SES and near-end
defect seconds. A far-end
block error has occurred
if the BEI value is
between 1 and 8;
otherwise, no far-end
block error has occurred.
Errored Seconds FEES-ODU Rx Far-end PM Count of all seconds not
Errored Seconds declared near-end defect
seconds with (ODU BEI)
Errors ≥ 1 or (ODU BDI)
= True
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-27 OTUk, ODUk, and ODUkTCM FarEND PM Parameters (continued)

Background Block BBE-TCM RX Error Count Count of BEI (TCM BEI)
Errors TCM BEI errors for all seconds in
which there is no AIS,
OCI, LCK or LTC defect.
A far-end block error has
occurred if the BEI value
is between 1 [0001] and 8
[1000]; otherwise, no
far-end block error has
occurred.
Backward Incoming BIAES-TCM RX TCM BIAE Error Count of seconds with at
Alignment Error Count least one TCM BIAE
Seconds defect occurred
(BIAE=1011).
Errored Seconds ES-TCM RX TCM Error Seconds Count of seconds with
(TCM BEI) Errors ≥ 1 or
(TCM BDI) = True.
Severely Errored SES-TCM RX Severely Error Count of seconds with
Seconds TCM Seconds (TCM BEI) Errors ≥ x or
(TCM BDI) = True.
Unavailable Seconds UAS-TCM RX TCM Unavailable 10 or more seconds SES
Seconds
Notes:
Note: For far-end DW Parameters and IAE/BIAE Seconds, monitoring the far-end
parameters in DW group and IAE seconds are implemented on the following OT
cards: 11QAP4, 43STX4P.
The following 64B/66B Near-End Physical Coding Sublayer parameters can be
monitored for 10 GbE LAN and 10GFC interfaces.
Table 19-28 PCS PM parameter definitions (64B/66B)

Code Violations - PCS CV-PCS Count of 64B/66B or 8B/10B coding
violations
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-28 PCS PM parameter definitions (64B/66B) (continued)

Errored Seconds - PCS ES-PCS Count of 64B/66B or 8B/10B coding
violations ≥ 1 or dLSS = True or dLOS =
True
Severely Errored Seconds - SES-PCS Count of seconds with 64B/66B or
PCS 8B/10B errors ≥ x2or dLSS = True or
dLOS = True
Severely Errored Frame SEFS-PCS Count of seconds in which dLSS = True
Seconds - PCS or dLOS = True
Notes:
2. PM supports PCS monitoring only in Receive direction (for example, 10AN10G, 24ANM,
24ETH1), although at system level also Transmit TCAs can be configured.
The following 8B/10B Near-End Physical Coding Sublayer parameters can be monitored
for 1 GbE and FC100/200/400/800 interfaces.
Table 19-29 PCS PM parameter definitions (8B/10B)

Code Violations - PCS CV-PCS Count of 8B/10B coding violations
Errored Seconds - PCS ES-PCS Count of seconds with 8B/10B coding
violations ≥ 1 or dLSS=True or
dLOS=True
Severely Errored Seconds - SES-PCS Count of seconds with 8B/10B errors ≥
PCS x2or dLSS = True or dLOS = True
Severely Errored Frame SEFS-PCS Count of seconds in which dLSS=True or
Seconds - PCS dLOS=True
Notes:
2. PM supports PCS monitoring only in Receive direction (for example, 10AN10G, 24ANM,
24ETH1), although at system level also Transmit TCAs can be configured.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
MAC layer monitoring types are split into two PM groups: ETH (Ethernet statistics
group) and INF (interface group).
Table 19-30 Ethernet statistics definitions (ETH group)

Ethernet Number of Octets ETHOCTETS Provides a count of the total
number of octets of data
(including the bad packets)
received on the port. Count
excludes framing bits (SFD &
Preamble) but includes Frame
Check Sequence (FCS) octets.
Ethernet Number of Packets ETHPKTS Provides a count of the total
number of packets (including
bad packets, broadcast, and
multicast packets) received.
Ethernet Broadcast Packets ETHBCSTPKTS Identifies a count of the total
number of good packets
received that were directed to
the broadcast address. This
does not include multicast
packets.
Number of collision events on ETHCOLLISIONS Provides a count of the total
Ethernet link number of collisions on the
port.
Ethernet Number of Errored ETHCRCAE Provides a count of the total
Frames number of packets received
that had a length of between
63 and 1518 octets, inclusive,
but had either a FCS with an
integral number of octets
(FCS error) or a bad FCS with
a non-integral number of
octets (Alignment Error). The
packet length excludes
framing bits and includes FCS
octets.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-30 Ethernet statistics definitions (ETH group) (continued)

Ethernet Number of Drop ETHDROPEVTS Provides a count of the total
Events number of events in which
packets were dropped by the
monitoring entity due to a
lack of resources. This value
is not necessarily the number
of packets dropped; it can be
the number of times this
condition has been detected.
Ethernet Incoming ETHFRGMTS Provides a count of the total
Fragmented Packets number of packets sent or
received that were less than
64 octets in length (excluding
framing bits but including
FCS octets) and had either a
bad FCS with an integral
number of octets (FCS Error)
or a bad FCS with a
non-integral number of octets
(Alignment Error).
Ethernet Jabber Packets ETHJABRS Provides a count of the total
number of packets sent or
received that were longer than
1518 octets (excluding
framing bits, but including
FCS octets) and had either a
bad FCS with an integral
number of octets (FCS Error)
or a bad FCS with a
non-integral number of octets
(Alignment Error).
Ethernet Multi-cast Packets ETHMCSTPKTS Provides a count of the total
number of good packets
received that were directed to
a multicast address. This does
not include packets directed
to the broadcast.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................

Ethernet Oversize Packets ETHOVRSIZEPKTS Provides a count of the total
number of packets received
that were longer than 1518
octets and were otherwise
well formed. The packet
length excludes framing bits
and includes FCS octets.
Ethernet Undersized Packets ETHUNDRSIZEPKTS Provides a count of the total
number of packets received
that were less than 64 octets
long and were otherwise well
formed. The packet length
excludes framing bits and
includes FCS octets.
Ethernet 64-octet Packets ETHPKTS64OCTETS Provides a count of the total
number of packets (including
bad packets) received that
were exactly 64 octets in
length. The packet length
excludes framing bits and
includes FCS octets.
Ethernet 65- to 127-octet ETHPKTS127OCTETS Provides a count of the total
Packets number of packets (including
were between 65 and 127
octets in length, inclusive.
The packet length excludes
octets.
octets.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................

octets.
octets.
octets.
Ethernet Packet Error Ratio ETHPKTER Provides the value of packet
error ratio within the
monitoring period
Table 19-31 Interface PM statistics definitions (INF group)
Parameter Output MONTYPE Definition

Interface Incoming Number IFINOCTETS The IFINOCTETS contains
of Bytes the number of received bytes
in good and bad frames.
Interface Outgoing Number of IFOUTOCTETS The IFOUTOCTETS contains
Bytes the number of transmitted
bytes in good and bad frames.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-31 Interface PM statistics definitions (INF group) (continued)

Interface Incoming Number IFINUCASTPKTS The IFINUCASTPKTS
of Unicast Frames contains the number of
received unicast MAC
frames.
Interface Outgoing Number of IFOUTUCASTPKTS The IFOUTUCASTPKTS
Unicast Frames contains the number of
transmitted unicast MAC
frames.
Interface Incoming Number IFINBCASTPKTS The IFINBCASTPKTS
of Broadcast Frames contains the number of
received MAC frames with
broadcast Destination
Address.
Interface Outgoing Number of IFOUTBCASTPKTS The IFINBCASTPKTS
Broadcast Frames contains the number of
transmitted MAC frames with
broadcast Destination
Address.
Interface Incoming Number IFINMCASTPKTS The IFINMCASTPKTS
of Multicast Frames contains the number of
received MAC frames with
multicast Destination
Address.
Interface Outgoing Number of IFOUTMCASTPKTS The IFINMCASTPKTS
Multicast Frames contains the number of
transmitted MAC frames with
multicast Destination
Address.
Interface Incoming Frame IFINERR The IFINERR contains the
Errors number of errored frames
received.
The received frame counts as
errored if it contains:
• Symbol errors
• CRC errors
• Alignment errors
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Table 19-31 Interface PM statistics definitions (INF group) (continued)

Interface Outgoing Frame IFOUTERR The IFOUTERR contains the
Errors number of errored frames
transmitted.
The transmitted frames count
as errored if it contains:
• Symbol errors
• CRC errors
• Alignment errors
Interface Incoming Discarded IFINDSCRD Provides a count of the
Frames number of packets discarded
at the IN port (IfInDiscards)
of the interface.
Interface Outgoing Discarded IFOUTDSCRD Provides a count of the
Frames number of packets discarded
at the OUT port
(IfOutDiscards) of the
interface.
Interface Incoming Frames IFINUNKNOWNPLTS Provides a count of the
with Unknown Protocol number of packets received at
the IN port of the interface for
which the protocol is
unknown.
Interface Incoming IFINUNCLASSPKTS Provides a count of the
Unclassified Frames number of unclassified
packets received at the
interface.
OSC port supports Section/RS monitored types, like OC-3/STM-1 port as well as INF
PM group.
Single-port tunable Any Rate module (11STAR1) supports the following performance
monitoring groups:
• 10 GbE client port entity: ETH, PCS, OPR and OPT
• 10GFC client port entity: PCS, OPR and OPT
• OC-192/STM-64 client port entity: OC_N, STN_N, OPR and OPT
• OTM-0.2 client port entity: DW, OPR and OPT
• Line port entity: DW, OPR and OPT
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Single-line port tunable multi-rate 10-client multiplexing module (11STMM10) supports
the following performance monitoring groups:
• 1/2/4 GFC client port entity: PCS, OPR and OPT
• OC-3/12/48/STM-1/4/16 client port entity: OC_N, STM_N, OPR and OPT
• CBR2G5 client port entity: OC_N, STM_N, OPR and OPT
• Line port entity: DW, OPR and OPT
Single-line port tunable 12 GbE client Multiplexing module (11STGE12) supports the
following performance monitoring groups:
• Line port entity: DW, OPR, and OPT
OTS and OCH entities support only Optical Power Receive and Transmit performance
monitoring groups (no threshold crossing alerts).
The SVAC supports only OPR PM group on the client port and OPT PM group on the
line port.
The 130SCX10, 130SNX10, 112SCX10, and 112SNX10 OTs support the following
performance monitoring groups:
• 10 GbE client port entity: ETH, PCS, OPR, and OPT
• OC-192/STM-64 client port entity: OC_N, STM_N, OPR, and OPT
• OTM-0.2-client port entity: DW, OPR, and OPT
• Line port entity: DW, OPR, OPT, CD, DGD, and FOFF
The D5X500, 260SCX2, 130SCA1, 112SCA1 and 112SNA1 OTs support the following
performance monitoring groups
• 100 Gbe client port entity: DW
• Line port entity: DW, OPR, OPT, CD, DGD, and FOFF
PM details for coherent OTs

Coherent cards: 260SCX2, 130SCA1, 130SCX10, 130SNX10, 112SCX10, 112SNX10,
112SCA1, 112SNA1, 43SCX4, 43SCA1, 1UD200 and D5X500 support the following
line port performance monitoring groups.
• DW (however, IAES and BIAES are not supported)
• OPR, the monitored receive optical power
• OPT, the monitored transmit optical power
• CD, the monitored amount of compensated chromatic dispersion at the line-side
receiver
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
• DGD, the monitored amount of compensated differential group delay at the line-side
receiver
• FOFF, monitored frequency difference between a local oscillator (on the OT) and the
frequency of the incoming signal at the line-side receiver.
Note: The far end PM Monitoring on the line port of 130SCX10 & 112SNX10 is not
supported.
For the Digital Wrapper (DW) group, the performance monitoring attributes include:
• OTUk layer monitored types: BBE, ES, SES, UAS, FEC-EC, FEC-UBC,
BERpreFEC, BERpostFEC
• ODUk layer monitored types: BBE, ES, SES and UAS
Note: The 130SCUP, 130SCUPB, 130SCUPC, 1UD200 and D5X500 also support the
monitoring groups listed above.
Compensated Chromatic Dispersion

The Chromatic Dispersion – received (CDR) parameter is the amount of compensated
chromatic dispersion at the line side optical receiver of the 1UD200, D5X500, 260SCX2,
130SCA1, 130SCX10, 130SNX10, 112SCX10, 112SNX10, 112SCA1 OT, and 112SNA1
OTs. This value is measured by the ADCDSP on each OT line-side receiver. This
measured value is reported through CLI/SNMP, while CDR average is stored as
CDRAVG (CDR average) measurement value. PM uses the measured value of CDR to
calculate average compensated chromatic dispersion in the accumulation period.
The following are the features of Compensated Chromatic Dispersion PM:
• The CDR for each OT is measured in 1-minute intervals.
• The system provides CDRL (CDR Low tide mark) and CDRH (CDR High tide mark)
measured value for each measurement interval when PM is enabled.
Note: The 130SCUP, 130SCUPB, and 130SCUPC also support Compensated
Chromatic Dispersion.
Note: For 130SNX10, the CD values are re-calculated after resetting the optical
interface or after a pack cold reboot. During steady state operation, the CD value
reported in Performance Monitoring (PM) changes in excess of 200 ps/nm.
Compensated Differential Group delay

The Differential Group Delay – received (DGDR) parameter is the amount of
compensated differential group delay at the line side optical receiver of the 260SCX2,
130SCA1, 130SCX10, 130SNX10, 112SCX10, 112SNX10, 112SCA1, and 112SNA1
OTs. This value is measured by the ADCDSP on each OT line-side receiver. This
measured value is reported through CLI/SNMP, while DGDR average is stored as
DGDRAVG (DGDR average) measurement value. PM uses the measured value of DGDR
to calculate average compensated differential group delay in the accumulation period.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
The following are the features of Compensated Differential Group Delay PM:
• The DGDR for each OT is measured in 1-minute intervals.
• The system provides DGDRL (DGDR Low tide mark) and DGDRH (DGDR High
tide mark) measured value for each measurement interval when PM is enabled.
For CD and PMD performance enhancements in future releases, contact Alcatel-Lucent
for interface specifications.
Frequency Offset
The Frequency Offset – received (FOFFR) parameter is a measure of the optical
frequency difference between the local oscillator and the incoming signal at the line side
optical receiver of the 1UD200, D5X500, 260SCX2, 130SCA1, 130SCX10, 130SNX10,
112SCX10, 112SNX10, 112SCA1, and 112SNA1 OTs. This measured value is reported
through CLI/SNMP, while FOFFR average is stored as FOFFRRAVG (FOFFR average)
measurement value. PM uses the measured value of FOFFR to calculate the average
amount of frequency offset in the accumulation period.
The following are the features of Frequency Offset Received PM:
• The FOFFR for each OT is measured in 1-minute intervals.
• The system provides FOFFRL (FOFFR Low tide mark) and FOFFRH (FOFFR High
tide mark) measured value for each measurement interval when PM is enabled.
On-demand latency measurement

The system allows to measure transmission latency for a complete OTH path. A
measurement can be initiated and the results retrieved through management system and
ZIC. The capability to do latency measurements is available on 112SDX11, 11QPA4, and
11QPEN4 cards. This feature is restricted to “on-demand” latency measurement from
operator (no historical performance data measurements).
Delay measurement can be performed from ODU2p (Path layer) on 11QPA4/11QPEN4
line ports to test round-trip delay over bidirectional traffic.
Due to the potential time difference between DM signal reception and transmit in reverse
direction, a additional delay to up 1 frame period can be present. The accuracy for DM on
ODU2 frame could be one frame period. (That is, 12.191 μs for standard OTU2/ODU2 at
10.709 Gbps. Note for overclocking OTU2, the frame period is slightly less, for example,
11.787μs for OTU2e at 11.096 Gbps).
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Delay measurement configuration
The Delay measurement can be configured with the following parameters
• DM CMEP mode: Connection Monitoring End Point defined for delay measurement
on the specified OTU2 port.
– Source: Generates the DM bits and measures the DM bit transition
– Destination: Loopback the received DM bits
– Bypass: The DM bit is not inserted
The default value is Bypass. It is user responsibility to configure the proper CMEP mode
respectively on near and far end nodes.
Add/drop mode and non-OT client configuration
Only configurations of line port works at ADD/Drop mode and client type is non-OTN is
required to support line port delay measurement, in such configurations the DM CEMP
Mode can be provisioned on OTU2 line port.
When the user tries to provision the line Operation mode from ADD/Drop or CrossRegen
to Add-only or DropContinue, the DM CEMP should be reset to default value (bypass)
automatically.
For OTU2 line port works, Add-only or DropContinue, the provisioning of DM CEMP
Mode or DM MODE is denied.
One 11QPA4 and 11QPEN4, each OTU2 line port shall be able to support independent
Delay Measurement, at a time there are up to four Delay Measurement processes running
on one card (one for each OTU2 line port).
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Thresholding
Maintenance
....................................................................................................................................................................................................................................
Thresholding
Threshold crossing alerts (TCAs) and TCA profiles
Alcatel-Lucent 1830 PSS systems support threshold crossing alerts (TCAs) on a per
performance parameter basis by using TCA profiles. The TCA profiles are used to store
the threshold values of the performance parameters related to a specific parameter group
(for example parameters related to the SONET section or line).
Note: Thresholding is supported for OTH, SDH and SONET performance parameters,
but not for Ethernet performance parameters.
When thresholding is activated for a performance parameter the value of the parameter is
compared against the threshold value on a second by second basis. When the current
counter value equals or exceeds the threshold value, then a threshold crossing alert will be
reported as an event notification with a resolution of one second.
As threshold crossing alerts are events, they are stored in the network element event log,
and displayed in the list of TCA events.
Types of TCA profiles

The following types of TCA profiles are supported:
• In OTH mode (ANSI and ETSI):
– OTU4
– OTU3e2
– OTU3
– OTU2e
– OTU2
– ODU4
– ODU3e2
– ODU3
– ODU2e
– ODU2
– ODU1
– ODU0
– ODU4TCM (TCM TCA profile)
– ODU3e2TCM (TCM TCA profile)
– ODU2eTCM (TCM TCA profile)
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
– OCH
OCH is applicable for optical layer monitoring for DWDM uplink cards on
OTU2, OTU2e, OTU3e2, and OTU4 ports.
• In ANSI mode:
– OC-3 (SONET section)
– STS-1 (SONET path)
– STS-3c (SONET path)
• In ETSI mode:
– STM-1 (SDH regenerator section)
– VC-4 (SDH higher-order path)
– VC-4-4c (SDH higher-order path)
– VC-4-16c (SDH higher-order path)
A default profile is predefined for each of these TCA profile types. Furthermore, you can
create, modify or delete TCA profiles of these types.
Note: Thresholding is disabled by default.
TCA modes
Two different TCA modes (or thresholding methods) can be distinguished:
1. Transient condition method (“TR only mode”).
2. Standing condition method (“TR/RTR mode”).
Transient condition method
In the transient condition method, only one threshold, the so-called threshold report (TR)
threshold, is defined.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Note: The transient condition method is used in ANSI mode.
When the counter value of a performance parameter equals or exceeds this threshold, then
a threshold report (TR, synonymous to threshold crossing alert) is generated and stored in
the network element alarm log.
No more than one threshold crossing alert will be generated per performance parameter
during a measurement interval unless the threshold value has been changed, or the
performance parameter has been reset (to zero). When the counter value again reaches or
exceeds the threshold, another threshold crossing alert will be reported.
The following figure illustrates the transient condition method:
Figure 19-7 Thresholding – transient condition method
t
TR TR TR
g-upg-0037
Legend:
1 Threshold for generating a threshold report (TR)
Standing condition method

In the standing condition method, two thresholds are defined, a threshold report (TR)
threshold and a reset threshold report (RTR) threshold.
Note: The standing condition method is used in ETSI mode.
When the counter value of a performance parameter equals or exceeds the TR threshold,
then a threshold report (TR, synonymous to threshold crossing alert) is generated.
Only the first threshold crossing in a sequence of measurement intervals is reported. At
the end of the first interval in which the counter value did not exceed the RTR threshold, a
reset threshold report (RTR) is generated.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
The following figure illustrates the standing condition method:
Figure 19-8 Thresholding – standing condition method
2
t
TR RTR
g-upg-0038
Legend:
1 Threshold for generating a threshold report (TR).
2 Threshold for generating a reset threshold report (RTR)
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Software management
Maintenance
....................................................................................................................................................................................................................................
Software management
In-service upgrade
The in-service upgrade process converts the existing system database to the new release
database and upgrades the existing release software to a new release software while in
service, without impact to existing traffic.
Aspects for control plane managed networks
In a control plane (CP) managed network, a phased approach in order to upgrade all
nodes within a network is supported. To coordinate the deployment of new versions of
network signaling and routing protocols in service, the CP provides nodal attributes to
allow for retrieval of installed SW Version (ISV) and the provisioning of an active SW
version (ASV) value. In addition, a backward compatibility mode for CP network
protocols is supported.
The control plane (CP) in-service upgrade is supported by Alcatel-Lucent 1350 OMS.
In-service upgrade types
This feature supports in-service upgrade from previous 1830 releases (as specified) and
factory load to the current release.
For more details of the applicable load type and the upgrade paths that are supported for
the current release, refer to the Customer Release Notes (CRN) delivered with the system.
Software upgrades for SROS L2 packet cards
Starting with an upgrade to Release 8.1, during a system software upgrade, the new
software is not activated automatically on SROS L2 packetcards (11OPE8, 11QCE12X,
and 11QPE24). This allows the user to control when the new software is activated on each
card. A warm or cold reset of the card after the new software has been downloaded to the
card will activate the new software on the card. This feature enables the scheduled
upgrades for these cards, and the in-service upgrades when the cards are used in protected
configurations (with ERP and MC-LAG).
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Configuration database management
Maintenance
....................................................................................................................................................................................................................................
Configuration database management

Overview
Alcatel-Lucent 1830 Photonic Service Switch (PSS) maintains all its configuration in a
volatile memory database. Non-volatile disk backup databases are maintained implicitly
by the network element, and explicitly by operator commands. The NE is able to restore
its memory database from the contents of a disk backup database at restart time or
triggered by an operator command.
It is possible to transfer a locally stored disk database backup to a remote file system
(RFS) and the other way round. The operator can reset the memory and primary backup
database to a factory installed default configuration. For database upload and download,
the SSH-File Transfer Protocol (SFTP) is supported.
Database types
The volatile memory database (ACTV CPU DB) in the RAM of the First-Level
Controller (FLC) is maintained by the NE. It reflects the current NE configuration, the
NE alarm states and conditions, and the control plane-related information.
Two non-volatile disk database types exist for the NE: the primary backup database
(ACTV DSK DB) and the secondary backup data base (STBY DB). Both are realized by
the solid-state disks located on the FLC. At FLC (re-)start time, the contents of the ACTV
DSK DB is copied into the ACTV CPU DB.
The primary backup database is maintained implicitly by the NE during its normal
operation. At any time, it reflects the state of the volatile memory database. Updating the
primary backup database occurs online without interrupting the normal service operation
of the NE. The operator can initiate a copy of the primary backup database to the
secondary backup database.
The secondary backup database can be copied to the primary backup database. After an
FLC restart (or FLC switch) the memory database will be reloaded from the restored disk
database. The secondary backup database can be copied to/from a remote file server
(RFS) by operator commands (remote backup and remote restore).
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-9 Database types and transitions
Memory
DB
CPU
RESTORE-DB
Factory Primary Secondary

Default DB Backup DB Backup DB
ACT-DB-BACKUP
SSD
FLC
COPY-RFILE
Implicit alignment
By TL1 command Remote

file system
By debug command
g_pipg_0306
Legend:
CPU Central processing unit

DB Database
FLC First-Level Controller
OOS Out of service
SSD Solid-state disk
Disk redundancy
The NE disk is located on the First-Level Controller (FLC). The system ensures
consistency between the active and the standby FLC autonomously. Operator commands
related to database management refer to the active FLC. The system replicates any change
of the disk databases on the active FLC to the corresponding disk on the standby FLC.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Database download performance
The following table summarizes the estimated time to download and process the
configuration database through different transmission channels.
Table 19-32 Database download performance
Download through Estimated download time [h]
LAN 0.25
LAN and one ODU2 or OTU2 GCC hop 3.5

LAN and one ODU2e or OTU2e GCC hop 3.5
LAN and one ODU3 or OTU3 GCC hop 1

LAN and one ODU4 or OTU4 GCC hop 0.25
Database upload performance

The following table summarizes the estimated time to upload the configuration database
to a management system through different transmission channels.
Table 19-33 Database upload performance
Download through Estimated upload time [h]
LAN 0.25
LAN and 1 ODU2 or OTU2 GCC hop 3.5
LAN and 1 ODU2e or OTU2e GCC hop 3.5
LAN and 1 ODU3 or OTU3 GCC hop 1
LAN and 1 ODU4 or OTU4 GCC hop 0.25
CLEI ™ codes
The COMMON LANGUAGE ® equipment codes (CLEI ™ codes) of the Alcatel-Lucent
1830 PSS system components can be retrieved by the operator.
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Protection
Maintenance
....................................................................................................................................................................................................................................
Protection
Overview
This section describes the protection mechanism supported on Alcatel-Lucent 1830 PSS.
Note: The usage of regeneration in E-SNCP and Y-Cable protection configurations
must be validated prior to deployment.
The following OTs support E-SNCP protection in Alcatel-Lucent 1830 PSS:
• 11DPE12
• 11DPE12E
• 11DPE12A
• 11DPM12
• 11QPA4
• 11QPEN4
• 4DPA4 (FlexMux mode only)
• 4DPA2
The following OTs support Y-cable protection in Alcatel-Lucent 1830 PSS:
• 11DPE12
• 11DPE12A
• 11DPE12E
• 11DPM12
• 11QPA4
• 4DPA4
• 112SCX10
• 112SNX10
• 130SCX10
• 130SNX10
• 43SCA1
• 43SCX4
• 43SCX4E
• 11STAR1
• 11STMM10
• 11QPEN4
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
E-SNCP on 4DPA4
E-SNCP bridging for the 4DPA4 is illustrated in Figure 17-125, “E-SNCP on 4DPA4 OT”
(p. 17-145). Each client port (plus the two-line ports) form an independent protection
group. The bridging is performed at the ODU1 level. As a result, all client ports assigned
to the working line are bridged simultaneously to the protection line.
Figure 19-10 E-SNCP on 4DPA4 OT
In the outgoing direction, traffic from the client ports is aggregated into one ODU1 line
signal, then the ODU1 signal is bridged into two parts, one for Working Path and another
for Protection Path. Both parts are inserted with OTU1 overhead and FEC code being sent
to the lines. The optical wavelengths are then modulated with WT encoder/eVOA before
sending to the SFD or FOADM.
In the incoming direction, the OT receives two OTU1 line signals (working and
protection). After FEC error correction and OTU1/ODU1 overhead termination
respectively, client traffic is extracted independently from the two line signals according
to the OPTS mapping structure determined for the outgoing direction. Then, depending
on the external switch commands for individual protection groups, or signal quality, the
traffic for each client port is selected independently from the working or protection line
port.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
E-SNCP on 4DPA2
E-SNCP bridging for the 4DPA2 (1830 PSS-32/1830 PSS-16) is shown in Figure 17-126,
“E-SNCP on 4DPA2 OT” (p. 17-147). The client port (plus both line ports) form an single
protection group.
Figure 19-11 E-SNCP on 4DPA2
In outgoing direction, the client signal from the specified client port is bridged onto the
two line ports, one for Working Path and the other for Protection Path.
In incoming direction, the OT receives two line signals, one is working, the other is
protection. On 4DPA2, the line signal format is identical to the client signal format.
Depending on external switch commands and signal quality, the client traffic is selected
from either the working line port or the protection line port.
For the 4DPA2, the automatic switch decision is made based on Loss of optical
signal/Loss of lock, or by monitoring the following defects:
• TDM RS/MS:
– dLOS
– dLOF
• 1 GbE LAN PCS/MAC
– dLANLOS
– dLANLSS
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
• Eqpt:
– dEQPT
– dFACTERM-DEV
– dREPLUNTMISS
E-SNCP on 11QPA4
With E-SNCP configuration, the 11QPA4 ingress client signal is broadcast by an 8 x 8
matrix. The Optical signal is sent out by the two XFPs and transported through diverse
optical paths through a DWDM domain. The two received signals are processed by the
two OTN mappers. The automatic switch decision is made based on Loss of optical
signal/Loss of lock, or by monitoring LOF/LOM/TIM/SSF/PLM/SD/CSF, as detected by
the OTN mapper.
Figure 19-12, “11QPA4 E-SNCP examples” (p. 19-80) provides two examples of
E-SNCP configuration for the 11QPA4. Each client port and two line ports form an
independent protection group. Protected client(s) and unprotected client(s) can coexist on
the board.
In the source direction, the client involved in a protection group is split into two parts in
the matrix component, each goes to one line OTN mapper/framer for signal mapping,
OTN overhead insertion, and FEC coding. The signal is then transmitted after E/O
conversion. The optical wavelength is modulated with WT encoder or attenuated by slow
eVOA before entering the SFD.
In the receiving direction, the OT receives two line signals from the SFD (a working and
protection, signal belonging to the same protection group). After FEC decoding, OTN
overhead termination, and client signal de-mapping, the two client signals enter the 8 x 8
switch. Depending on the automatic protection switching criteria or external switching
command, one signal is selected and sent to the client port.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-12 11QPA4 E-SNCP examples
As shown in the Figure 19-12, “11QPA4 E-SNCP examples” (p. 19-80), any one-client
port on the 11QPA4 and its corresponding line port and any one of other line ports can
form a protection group. On an idle client port, when the corresponding line port is
involved in a protection group, the SFP does not need be equipped, because no active
traffic goes through this client port. For simplicity, the WT encoder or slow eVOA is not
plotted. Although all E-SNCP protection examples show bidirectional transmission,
unidirectional transmission is possible, depending on the Operational Mode of line ports.
Drop and Continue (one-way) E-SNCP on 11QPA4/11QPA4A OT
Starting from Release 3.6.0, 11QPA4/11QPA4A supports Drop and Continue operational
mode. The unidirectional transmission (one-way) E-SNCP is supported in receiving
direction. Different from Add/Drop bidirectional transmission (two-way) E-SNCP, for
Drop and continue (one-way) application, on the source node (transmission direction), the
traffic is expected to be unidirectional (that is, only transmitting, no receiving), which can
be realized by setting the Operational Mode of addressed line port to be ADDONLY, or
together with a Multicast group created against related client ports. See the following
figure for configuration examples of source node (transmitting direction) of unidirectional
transmission.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-13 Example: source node of unidirectional transmission on

11QPA4/11QPA4A
In 11QPA4/11QPA4A card, one client port and multiple line ports can form one multicast
connection. To create multicast connection, the client port (facility) and its corresponding
line port (facility) must be created first, for example, Ci--- > Li (i=1, 2, 3, 4), thus the Ci
--- >Li is the first multicast member of one multicast group which share the same client
port, which is the base of other multicast members creation. The operational mode for all
involved line ports must be “Add only”. In multicast connection, if a client port does not
belong to a multicasting connection, while its corresponding line port is associated to one
multicasting connection, this client port must be unassigned.
On the sink node (receiving direction), the traffic is expected be unidirectional (that is,
only receiving, no transmitting), which can be realized by setting the Operational Mode
of addressed line port to be Drop_Continue, the following figure shows the one-way
E-SNCP configuration examples (in receiving direction).
Note: If line received power is lower than -18 dBm, 11QPA4 E-SNCP or OMSP
protection switching time may be greater than 50 milliseconds when the client signal
is 8GFC. The line received power has to be adjusted in this case.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-14 Examples: Drop and Continue E-SNCP
E-SNCP on 11DPE12/11DPE12E thru backplane connection

Alcatel-Lucent 1830 PSS supports service cross-connection between two-neighbor OTs
through a backplane high speed connection. Alcatel-Lucent 1830 PSS provides this
E-SNCP protection on the 11DPE12/11DPE12E OT when it is provisioned for Q-in-Q
mode. With the flexible protection provision, two types of protection scenarios are
supported on this OT:
• Line service protection with one-line port bridged to and selected from the other
two-line ports which locate at a same OT
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
• Line service protection with a service of one-line port bridged to and selected from
the other two-line ports which locate at different OTs
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
E-SNCP on 11DPE12
Alcatel-Lucent 1830 PSS supports E-SNCP on 11DPE12 in full rate mode and Q-in-Q
mode (intra-pack). E-SNCP is also supported in Q-in-Q mode between two adjacent
packs. E-SNCP on 11DPE12 OT is a line (network-side) protection mechanism, which
protects against network-side SFP-related failure, line signal failure, which can be caused
by network fiber disconnection, or intermediate NE nodes malfunction.
E-SNCP protection is implemented by permanent head-end bridging and dynamic tail-end
selection. The E-SNCP function is realized within a single 11DPE12 OT. Each client port,
or client port VTS, plus the two-line ports VTS, form an independent protection group.
Bridging is performed at the VTS level. As a result, all client ports or client port VTS
assigned to the working line VTS are bridged simultaneously to the protection line VTS.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
In the source direction, the client port flow for full-rate mode, or client port VTS flow for
Q-in-Q mode from the specified client port, is bridged onto two-line port VTS, one for
the Working Path and another for the Protection Path.
In the receiving direction, the OT receives the Working and Protection line signals.
Depending on the external switch commands, line port signal quality, and VTS alarms,
the traffic is selected from the Working or Protection line port VTS.
Figure 19-15 11DPE12 full rate mode ESNCP
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-16 11DPE12 Q-in-Q mode ESNCP
E-SNCP on 11DPE12E
Alcatel-Lucent 1830 PSS supports intra-pack E-SNCP on 11DPE12E in Q-in-Q mode.
E-SNCP on the 11DPE12E OT is a line side (network-side) protection mechanism which
protects against network-side SFP-related failure, line signal failure caused by network
side fiber disconnection, or intermediate NE nodes malfunction.
selection. The E-SNCP function is realized within a single 11DPE12E OT. Each client
port, or client port VTS, plus the two-line ports VTS, form an independent protection
group. Bridging is performed at the VTS level. As a result, all client ports or client port
VTS assigned to the working line VTS are bridged simultaneously to the protection line
VTS.
In the source direction, the client port flow in Q-in-Q mode from the specified client port,
is bridged onto two-line port VTS, one for the Working Path and another for the
Protection Path.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
In the receiving direction, the OT receives the Working and Protection line signals.
Depending on the external switch commands, line port signal quality, and VTS alarms,
the traffic is selected from the Working or Protection line port VTS.
Figure 19-17 11DPE12E Q-in-Q mode E-SNCP
E-SNCP on 11DPE12A
In Q-in-Q mode, E-SNCP on 11DPE12A OT is a line side (network side) protection
mechanism, which protects the following failures.
• Network side SFP related failure
• Line signal failure caused by network side fiber disconnection
• Intermediate NE nodes malfunction
The E-SNCP protection is implemented by permanent head-end bridging and dynamic
tail-end selection. The E-SNCP function is realized within one 11DPE12A OT. Each
client port VTS (plus the two line ports VTS) form an independent protection group. The
bridging is performed at VTS level.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
In the source direction, the client port VTS level flow from specified client port is bridged
onto two line port VTSs, one for Working Path and another for Protection Path. In the
receive direction, the OT receives two line signals (one is working, another is protection).
The traffic is selected from either working line port VTS or protection line port VTS. This
depends on the external switch commands or line port signal quality and path status
monitoring (ODU2 (APS/PCC) or layer2 (CCM) path depending on the type of SNC
implemented). The following figure shows an example of layer2 SNCP configuration
utilizing the 11DPE12A OT. For 11DPE12A, unidirectional and revertive protection is
supported. Bidirectional protection is not supported.
Figure 19-18 1+1 Layer2 SNCP example with 11DPE12A
E-SNCP on 11DPM12
Alcatel-Lucent 1830 PSS supports E-SNCP on 11DPM12 OT as a line side (network side)
protection mechanism which protects against network side XFP-related failure, line signal
failure caused by network side fiber disconnection or intermediate NE nodes malfunction.
selection. The E-SNCP function is realized within one 11DPM12 OT. In the 11DPM12
card, each ODU0 /ODU1/ODUflex encapsulating client signals (plus the two-line ports)
form an independent protection group. If client ports are encapsulated into one ODUPTF
through OPTSG, the ODUPTF can be protected on ODU1 level. That means all of the
client signal encapsulating into OPTSG under the ODUPTF will be protected
simultaneously.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Note: For clarity, examples of ODU0/ODU1/ODUflex are shown separately. It is
possible for different client signals and their protection to co-exist in one pack as long
as they meet bandwidth and resource requirements.
Figure 19-19 Line E-SNCP on 11DPM12 OT (OPTSG protection) (1 of 2)
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-20 Line E-SNCP on 11DPM12 OT (OPTSG protection) (2 of 2)
Source direction
For client signals aggregated into one ODU0/ODU1/ODUflex, it is bridged to the
Working and Protection line path through the cross-connection among the client side and
line side Lo-ODUk.
Then both have OTN overhead and FEC code added and are transmitted. The optical
wavelengths are modulated with WT encoder/eVOA before sending to the SFD or
FOADM.
Receive direction
The OT receives the Working and Protection OTU2 line signals. After FEC error
correction and OTU/ODU overhead termination, the two-line signals extract ODU0/
ODU1/ODUflex signals independently according to the Lo-ODUk mapping structure in
the receiving payload. Then, depending on external switch commands for individual
protection groups and signal quality, the client traffic is selected independently from
either the Working or Protection line port.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
E-SNCP with regeneration
Alcatel-Lucent 1830 PSS supports protected services with regeneration.
The supported configurations are dependant on the following:
• The protected service on an OT support regeneration
• The type of OTs that support regeneration
• Compatibility of end-point OTs and regen OTs
Regeneration
The Alcatel-Lucent 1830 PSS supports single channel regeneration for DWDM-DWDM
and CWDM-DWDM connections. CWDM-CWDM regeneration is not supported.
DWDM-DWDM single channel OEO regeneration is supported with a single multi-port
pluggable OT. Regeneration occurs between two of the line ports on the card, which are
configured for Cross-Regen mode.
The following OTs support this function
• 11QPA4
• 4DPA4 (FlexMux only)
CWDM-DWDM single channel OEO regeneration is supported with a single OT.
The following OTs support this function:
• With the 4DPA4 OT (FlexMux only), one line/eVOA port is connected to the DWDM
signal and the other line/eVOA port is connected to the CWDM signal. The line ports
are configured for Cross-Regen mode.
• With the 11QPA4 OT, a line/eVOA port is connected to the DWDM signal and the
associated client port is connected to the CWDM signal.
Y-cable protection on 11DPE12/11DPE12E

Alcatel-Lucent 1830 PSS supports on the 11DPE12/11DPE12E. Y-cable protection is a
line side (network-side) protection mechanism, which protects the 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 splitter on the
received signal for 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 accomplished by one of the working/protection OT cards turning
its Tx client-side laser on, while the other turns off its laser. The Tx signal is channeled
through a reverse splitter and sent to the customer equipment. Either the working or
protection card can drive the signal through the reverse splitter.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
The same configuration is used in the other direction to provide protection for both
directions. Local protection negotiations at each end are done through a dedicated
backplane communication channel (which does not require the shelf control card to be
present) for quick signaling between mate cards. The remote end-to-end protection
negotiations are done using the standard GR-253 1+1 APS K-byte protocol, carried in a
proprietary manner in the APS/PCC channel of the 10G ODU2 overhead.
For the 11DPE12/11DPE12E, the Y-cable can be supported in full rate mode, subrate
mode, and Q-in-Q mode, but the protection switching is based on port level not VTS in
subrate and Q-in-Q mode. The following figure shows Y-cable protection examples.
Figure 19-21 11DPE12/11DPE12E full rate Y-cable protection
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-22 11DPE12/11DPE12E subrate Y-cable protection
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-23 11DPE12/11DPE12E Q-in-Q mode Y-cable protection
1+1 Y-cable protection on 11DPE12A

O-SNCP configuration relies on client-transmitter arbitration between the peer protected
entities (11DPE12A packs in adjacent slots). Using a so called Y-cable client input is split
and fed to both 11DPE12A client port inputs; while 11DPE12A client port outputs are run
through a 2:1 coupler. Protection manager on each of the 11DPE12A collects tributary
status signals from local tributary and from the adjacent companion 11DPE12A (through
backplane link). Status of both tributaries is input to a state machine, which determines
the state of associated transponder. This implementation allows 1+1 protection
applications, either unidirectional or bidirectional. One protected instance can be
supported per each client adaptation function.
As shown in the following figure, one channel in a pair of 11DPE12A packs in adjacent
slots are configured for 1+1 protection using Y-cable. Protection manager manages one
instance of protection state machine. The protection state machine takes the inputs, such
as Signal Fail (SF[n] where n=1) or Signal Degrade (SD[n] where n=1) from both local
and companion circuit packs. Based on these inputs and additional Software controls (to
implement Manual, Forced and Inhibit switch requests) protection manager determines
the ON/OFF state of the associated client transmitter. For simplicity in software
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
development and user provisioning, ports with same port number on two boards protect
each other. For example, client port 1 on transponder A protects client port 1 on
transponder B.
Figure 19-24 1+1 Protection using Y-cable
11DPE12A pack has 12 client ports and can have up to 12 separate Y-cable protection
groups. Switching operations, both manual and automatic, are on a per protection group
basis. Each protection group operates completely independent of the others, with its own
protection state machine. However Y-cable performance times (50 ms) may not be met on
11DPE12A if more than six protection groups on one pack are switched together.
The following provisioning rules are to checked in 11DPE12A:
• The VTSXC and VTS parameters in client port and line port should be same for local
working and protection ports.
• The client port type and line port type should be same for local working and
protection.
• All the VTSs in one client port only can be connected to one line port.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Advantages of this protection switching
The 1+1 protection using Y-cable implementation ensures fast protection switching based
on autonomous failures of either transmission path or supporting equipment entities.
Switching time is shorter than 10 ms (detection, except SD) + 50 ms (switch completion)
for failures such as dLOS, dLOF, dAIS or equipment failures.
Y-cable protection on 11QPA4

Alcatel-Lucent 1830 PSS supports Y-cable protection on the 11QPA4. The Y-cable
protection is a line side (network-side) protection mechanism, which protects the 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 splitter on the received signal for the client-side ports. The incoming signal from the
customer equipment is split and received by both the working and protection OT cards.
The following illustrations show Y-cable protection examples.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-25 11QPA4 Y-cable protection
Y-cable protection on 11DPM12

Alcatel-Lucent 1830 PSS supports Y-cable protection on the 11DPM12 card. 11DPM12
supports Y-cable protection over its L1 port only. The Y-cable protection is a line side
(network-side) protection mechanism, which protects the 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.
A passive splitter/joiner (Y-cable) is connected to a pair of client ports on redundant
transponder packs (OTs) at one end of the network, with the same arrangement at the
other end of a point-to-point link across the 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. The near-end working OT must be connected to the far-end
working OT. The near-end protection OT must be connected to the far-end protection OT,
because the protection cards are responsible for the end-to-end K-byte communication
protocol.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Figure 19-26 Y-cable protection on 11DPM12
E Rules for 11DPM12 Y-Cable protection

The following E rules must be followed when implementing the Y-cable protection on
11DPM12 card.
• The local working and protection ports on 11DPM12 card must be of the same type
(that is, same signal rate/format) with the same encapsulation mode (that is,
ODU0/ODU1/ODUflex). The NE software is responsible for enforcing this
requirement. The Y-cable would not be supported on a client port, when the client
signal has encapsulated into OPTSG.
• The following two rules should be checked by a user when creating ODUk
cross-connect for client ports on working and protection packs.
– The ODUk cross-connect must be created from client ports Lo-ODUk entity to L1
port Lo-ODUk entity. L2 port is not permitted to create ODUk cross-connect with
client port in Y-cable protection group.
– The Lo-ODUk ID in line port associated with client ports should be the same for
local working and protection ports.
• The E-SNCP and Y-cable are not allowed to co-exist, that is, if there is at least one
E-SNCP protection group created on the board, the Y-cable protection is not allowed
on the board, and vice versa.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Y-cable priorities
The following table describes the Y-cable priorities for both unidirectional and
bidirectional protection.
Table 19-34 Y-cable priorities - Unidirectional (Working and Protection sides),

Bidirectional (Working side only)
Priority Switch Request

Highest Lockout of Protection
Forced Switch
SF
SD
Manual Switch
Wait to Restore (revertive only)
Reverse Request (bidir only)
Do Not Revert (non-revertive only)
Lowest No Request
Table 19-35 Y-cable priorities - Bidirectional (Protection side only)
Priority Switch Request

Signal Failure on Protection
Forced Switch
Signal Failure on Working
Signal Degrade
Manual Switch
Lowest No Request
Y-Cable protection triggered by Signal Degrade on 11DPM12

Signal Degrade triggered Y-cable protection on 11DPM12 can only be supported for
1GBE/STM-16/OC-48/FC-100 client. For the scenario of Signal Degrade on Line side
Rx, the client ODUPTF dDEG (Rx) should trigger the switch on near end where the PM
BIP-8 errors are propagated from line LOODUk to client transparent terminated ODUk.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
For the scenario of Signal Degrade on Client side Rx, the downstream client dDEG (Rx)
should trigger the switch on the far end where the Code Violations are transparently
propagated from upstream to downstream and detected by non-intrusive monitor of PCS
layer or Sonet section/SDH regeneration layer of SONET/SDH from Egress.
The user can provision and retrieve the SD threshold parameters for the following:
• Client signal (1GbE/OC-48/STM-16/FC-100)
• Client ODU0/ODU1 Termination entity associated with the above client signals
By default configuration, Signal Degrade does not contribute to Y-cable switching. The
customer can choose to manually enable SD as a switch trigger on individual Y-cable
protection groups by provisioning SDEnabled=yes.
1+1 Y-cable protection on 4DPA4

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 (diverse fiber routes).
The following figure illustrates a network level example to support the Y-cable protection
in Alcatel-Lucent 1830 PSS.
Figure 19-27 Network level example of 4DPA4 Y-cable protection in 1830 PSS
E-rules for 1+1 Y-cable protection on 4DPA4

• The Line ports of the working and protection OTs must be the same and both L1, L2
should support Y-cable.
• The line port of Local OT and far-end OT should be the same.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
• 4DPA4 Y-cable protection client signal type should be FC100, 1 GbE and
STM-16/OC-48 in “FlexMux” card mode and support="ADD_DROP".
• 4DPA4 Y-cable should support up to four client ports.
• 4DPA4 Y-cable should be supported in both Unidirectional and Bidirectional
protection mode.
• For 4DPA4, the E-SNCP and Y-cable are not allowed to co-exist. That is, if there is at
least one E-SNCP protection group created on the board, the Y-cable protection is not
allowed on the board, and vice versa.
• The Y-cable protection switching should fulfill 50 ms switching time criteria with all
four client ports protected.
Note: When the 4DPA4 packs are provisioned with Y-cable protection, the protection
switching time may be greater than 50 ms if the switching is triggered by PLM
(Payload Mismatch) condition.
E-SNCP on 11DPM4M/4E
The 11DPM4M/4E pack is capable of supporting 1+1 linear SNC protection switching at
ODU0/ODU1/ODUFlex level.
In the 1+1 ODU0/ODU1/ODUFlex level E-SNCP configuration, in the ingress direction
the client signal is broadcasted toward the associated two OTU2 line interfaces in the
protection group by the ODUk cross-connect function module. The optical signal is sent
out by XFP modules and is transported through diverse optical paths through a WDM
domain. In sink direction, the two received signals are processed by the associated two
OTN line Subsystem inside HyPHY AXS. The automatic switch decision can be made
based on Loss of optical signal/Loss of lock; or by monitoring associated OTN alarms
detected by the OTN mapper. The E-SNCP group contains two line ports and one client
ports. The client port will be in either of the two line ports. Another client port in the
protection group is “unassigned”.
Note: Uni-directional E-SNCP is not supported on 11DPM4M and 11DPM4E.
The following figure shows the graphical illustration of the 1+1 E-SNCP on
11DPM4M/4E.
Figure 19-28 11DPM4M/4E 1+1 E-SNCP at ODUk-level
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
Y-Cable protection triggered by Signal Degrade (130SCX10/130SNX10)

In this kind of protection, the system detects Signal Degrade on the line side Rx
(HO-ODU4 dDEG) or the client side RX (10GbE client), and performs a Y-cable switch
upon detection.
Signal degrade on client side Rx is encoded with LosProp byte=0x02 in ODU4 APS/PCC.
The switch is then performed at the far end, triggered by the received LosProp signal.
Signal degrade triggered Y-cable protection on
43SCX4/43SCX4E/130SCX10/130SNX10 can be supported for 10GBE client.
Figure 19-29 Signal degrade scenario for Y-cable protection
SD switching Enable/Disable
Signal Degrade does not contribute to Y-cable switching, by default. The customer has the
option to manually enable SD as a switch trigger on individual Y-cable protection groups.
This is done by setting SD Enabled = TRUE for that particular protection group. The
default value of SD Enabled = FALSE.
Note: The provisioning of SD Enabled should be denied if the protection group is on
a card which does not support SD switching.
....................................................................................................................................................................................................................................
Maintenance
....................................................................................................................................................................................................................................
While there are multiple SD detection points for each protection group, there is only one
SD switching enable/disable parameter for each protection group. When enabled, the
switching decision considers all implemented SD detection points for that protection
group. When disabled, none of the SD detection points are considered.
Note: Up to 10 separate Y-cable protection groups are supported on each 130SCX10
or 130SNX10 card.
Signal Degrade defect applies to the following ports:
• OTU4 line ports
• 10GbE client ports
The user can provision and retrieve the SD threshold parameters for each 10GbE
client port.
When a protection group is provisioned for unidirectional switching, each end switches
independently based on local "SD" state. SD-triggered switching works with both
revertive and non-revertive Y-cable switching, assuming both options are supported by
the card.
Table 19-36 Y-cable priorities - unidirectional switching
Priority Switch request

Forced Switch
Signal Failure
Signal Degrade
Manual Switch
Wait to Restore
Do Not Revert
Lowest No Request
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Reports
Maintenance
....................................................................................................................................................................................................................................
Reports
Failure reports are generated for software faults.
The first occurrence of pack local equipment failures is stored in a flash memory.
Failure reports are generated for equipment faults and can be forwarded via the EMS
interfaces.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Provisioning
Overview
Purpose
This section provides information about the provisioning concepts realized with
Alcatel-Lucent 1830 Photonic Service Switch (PSS).
Reference
For detailed provisioning procedures and information about specific parameters and their
possible values see the Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 8.2
User Provisioning Guide.
Contents
Equipment provisioning 19-106

Primary and secondary states of system components 19-109
Optical transponder and client/line card protection 19-116
Optical protection for 40G OTs 19-132
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Equipment provisioning
Provisioning
....................................................................................................................................................................................................................................
Equipment provisioning
Definition
Equipment provisioning refers to assigning values to parameters used for specific
functions by network elements. The values of the provisioned parameters determine many
operating characteristics of a network element.
NE start-up provisioning
During the very first startup of the network element, the operator sets important
parameters for the system as a whole:
• Region (ETSI or ANSI), defining if the system works in SDH or SONET mode
• Provisioning mode (autoprovisioning or manual provisioning)
• Automatic in-service threshold time, determining how long a customer signal must be
present on the facility without a failure condition before the system puts the facility in
service.
• Altitude of the NE above sea level
• Operator-defined user label
Equipment types
In Alcatel-Lucent 1830 PSS, two basic types of equipment exist:
• Mandatory equipment entities: These components are essential for the operation of the
system:
1830 PSS - 32 subrack
– 2 Power Filter Cards (PFD A and PFD B)
– 2 Fan Units (FAN and FAN32H)
– 1 User panel (PSS-32 USRPNL)
1830 PSS - 16 subrack
– 2 Power Filter Cards (PFD A and PFD B)
– 1 Fan Unit (FAN16)
– 1 User panel (PSS-16 USRPNL)
• Non-mandatory equipment entities: These components can be installed or activated
optionally, for example depending on the required network interfaces:
– I/O cards (see Table 18-1, “List of Alcatel-Lucent 1830 PSS items” (p. 18-5) for a
comprehensive list)
– Ports
– Optical modules (SFP, XFP, see “PTM optics for WDM optical transponders”
(p. 18-55) for a comprehensive list)
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
The system checks if a provisioned optical module is compatible to the related hosting
I/O card. In case of a mismatch, an alarm is raised.
Provisioning modes
The mandatory equipment entities are provisioned autonomously by the system
independent from their presence in the system.
For non-mandatory equipment entities, the following provisioning modes are supported:
• Autoprovisioning
• Manual provisioning
• Preprovisioning
Autoprovisioning
Autoprovisioning means assigning default configuration parameters to an equipment
component at the time when the component is installed the first time. The default
configuration parameters are read from the NE database.
If no alarm conditions are detected during insertion or power-on diagnostics,
autoprovisioned modules are placed in the state “IS” (in service) automatically.
Manual provisioning
Autoprovisioning will not happen at equipment insertion if disabled on NE parameter
level.
Functionally, manual provisioning is the same as preprovisioning, except that it also
serves to provision a card / module already inserted.
Preprovisioning
Preprovisioning means setting configuration parameters in advance, that means before the
corresponding equipment component is physically present in the system. The
preprovisioned configuration settings are stored in the NE database, and take effect as
soon as the equipment component is installed.
If no alarm conditions are detected during insertion or power-on diagnostics, modules
inserted in a preprovisioned slot are automatically placed in the state “IS” (in service) or
“OOS-MA” (out of service - management). The operator can set this target state for the
equipment being provisioned.
It is not possible to preprovision or autoprovision an entity (for example an XFP) when its
related hosting entity (in this example an I/O card) is not provisioned.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Card management
Card failure, card mismatch, card out, and unconfigured equipment are alarmed. Card
type and status indication can be retrieved using the Alcatel-Lucent 1830 PSS ZIC.
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Primary and secondary states of system components
Provisioning
....................................................................................................................................................................................................................................
Primary and secondary states of system components

Primary states
The following primary states are defined:
• IS – In service
The entity is capable and allowed to provide its provisioned functions. The IS primary
state usually relates to equipment entities.
• IS-NR – In service, Normal
The entity is capable and allowed to provide its provisioned functions. The IS-NR
primary state usually relates to facilities.
• IS-ANR – In service, Abnormal
The entity is capable to provide most of its functions, is allowed to provide its
provisioned functions, but is operating in a degraded or abnormal state.
• OOS-AU – Out of service, Autonomous
The entity is not available for providing its provisioned functions but the entity is not
intentionally suspended by an 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 (for instance, OC-3 LOS detected).
• OOS-MA – Out of service, Management
The entity is intentionally suspended by external management command from
performing its provisioned functions, but the entity may still be operationally capable
of performing its provisioned functions.
• OOS-AUMA – Out of service, Autonomous and Management
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 performing its provisioned functions.
Secondary states
The following secondary states are defined:
• ACT – Active
The entity is currently in use and has spare operating capacity for further usage
demand. When applied to a facility entity, this value means that the entity is
cross-connected (the entity is a constituent leg of a cross-connection) and additional
cross-connection capacity is available, such that more one-way cross-connections can
be added.
• AINS – Automatic In-Service
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
The entity is allowed to transition to the in-service state if it is operationally capable.
For example, an OC-3 transitions from OOS-AU,AINS to IS when all OC-3 alarm
conditions have cleared.
• ANR – Abnormal
• BUSY – Busy
The entity is currently in use and has no spare operating capacity for further usage
demand. For example, a head end bridge with 2 broadcast legs, or a connected test
access port are both BUSY.
• CLKNA – Clock Not Aligned
The clock of the standby matrix is not aligned to the clock of the active matrix.
• CP – Control Plane
The facility or connection is under management by the control plane for data services.
• CPMP – Control Plane
The facility or connection is shared between management plane and the control plane.
• DSBLD – Disabled
The facility entity is prohibited from carrying traffic, for example because the
required supporting equipment is not provisioned or provisioned for another service.
• FAF – Facility Failure
The associated facility entity has failed, for example a LOS, LOF or AIS condition is
present.
• FLT – Fault
Need information
• LPBK – Loopback
A loopback activity is currently being performed on the entity.
• MDLT – Manual Delete
The ODU path-terminated facility has been manually provisioned, and can only be
deleted by manual command. The MDLT secondary state is valid for ODU
path-terminated facilities only.
• MEA – Mismatch of Equipment and Attributes
An incompatible system component is physically present in a provisioned slot.
• MT – Maintenance
The standby FLC is in a temporary maintenance state (for example during
Backup/Restore).
• NBK – No Backup
Information needed
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
• NOIMP – Not Implemented in Hardware
The higher-order ODU path termination function (HO ODUPTF) and lower-order
ODU path termination function (LO ODUPTF; if any) entities are not connected
toward the NNI side.
• PMD – Performance monitoring inhibited and disabled
The performance monitoring counters (current and history counters) have been
removed from memory.
• PSI – Protection Switching Inhibited
The working entity is inhibited from automatic protection switching by means of an
operator command, that means, it is locked out from automatic protection switching.
• SDEE – Supported Entity Service Exists
The entity (equipment or facility) is currently supporting services such as
cross-connections or loopback, or is supporting other entities that are carrying such
services.
Attempts to delete an entity carrying an SDEE secondary state is denied.
When SDEE is set on an entity then the SDEE state is propagated to the entity's
parents and up the supporting hierarchy chain. This applies to the complete facility
and equipment hierarchy.
When SDEE is removed on an entity due to the deletion of a service, then the SDEE
state of the entity's parents is reevaluated. If this is the last service being supported by
the parent(s) then SDEE is removed from the parent(s) also. In this case, the
reevaluation shall continue up the supporting hierarchy chain.
For an OTUk port, SDEE is set if it:
– HO ODUk has SDEE condition
– is involved in a loopback
– has a GCC0 channel enabled.
For an HO ODUk path facility, SDEE is set if it:
– has a GCC1 channel enabled
– is cross-connected to HO ODUkTERM entity (Virtual)
– is cross-connected to another ODUk (Matrix)
– a TCM is provisioned corresponding to this ODUk
For an HO ODUkTERM path facility, SDEE is set if it:
– is cross-connected to ODUk entity (that is, as soon as it is created)
– a TCM is provisioned corresponding to this ODUkTERM
For an LO ODUj path facility, SDEE is set if it:
– is intact cross-connected to another ODUj (Matrix)
– a TCM is provisioned corresponding to this ODUk
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
For an equipment port of an IO card with matrix interface, SDEE is set if:
– the associated OCn/STMn/GBE10 facility is in SDEE (port with non OTN client
port)
– the associated OTU facility is in SDEE (port OTN port)
– the remote connected port (TL1 parameter, RMCONPORT) is set for the OCH
facility on uplink card (port OTN port)
For a transparently transported STMn/OCn, SDEE is set if:
– the ODUkTERM used to carry OCn/STMn is in SDEE
– the OCn/STMn is in a loopback
For a transparently transported GBE10, SDEE is set if:
– the ODUkTERM used to carry GBE10 is in SDEE
– the GBE10 is in a loopback
For a transparently transported GBE, SDEE is set if:
– the ODUkTERM used to carry GBE is in SDEE
– the GBE is in a loopback
For an ODUkTERM used to transparently carry GBE10/OCn/STMn , SDEE is set if:
– the GCC1 is enabled.
– it is cross-connected to ODUk (Matrix).
– a TCM is provisioned corresponding to this ODUkTERM.
For an ODU0TERM used to transparently carry GBE, SDEE is set if:
– the GCC1 is enabled.
– it is cross-connected to ODU0 (Matrix).
– a TCM is provisioned corresponding to this ODUkTERM
For a TCM, SDEE is set if:
– on all TCM entities, which are referenced by the protected method or protecting
method of a protection connection.
For a XFP/SFP, SDEE is set if
– the OCn/STMn/GBE/GBE10 ports residing on the XFP/SFP is in SDEE
For an OCn/STMn port, SDEE is set if it:
– is involved in a loopback
– one of its embedded tributaries has SDEE condition
For a GBE and GBE10 port, SDEE is set if:
– the ODUkTERM used to carry GBE/GBE10 is in SDEE
– the GBE/GBE10 is in a loopback
For an STSn/VCn path facility, SDEE is set if it:
– is used in cross-connection (SST has ACT or BUSY)
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Card/Port/SFP/XFP Level SDEE SST setting rules:
– A Card has the SDEE SST set if at least one Port/SFP/XFP provisioned on it has
the SDEE SST set
– A Port/SFP/XFP has the SDEE SST set if at least one Facility supported by it has
the SDEE SST set
– Just the presence of a facility does not constitute SDEE on the Port/SFP/XFP
SDEE is set by control plane, if:
– The OTU is assigned to MP, associated TCM entity is assigned to CP. Note: This
state is a transient state. It will be left automatically by CP removing the TCM
entity.
The detailed state of affected entities is the following: OCH/OTU/OTUODUn:
SST=MP,SDEE; MGRACD=MGNPLN
– The OTU is assigned to MP, associated TCM is not assigned to any plane. Note:
This state is outside the CP scope.
– The OTU and associated TCM entity are assigned to MP. Note: This state is
outside the CP scope.
– The OTU and associated TCM entity are not assigned to any plane. Note: This
state is outside the CP scope.
SST=SDEE; MGRACD=<>
– The OTU is not assigned to any plane, associated TCM is assigned to MP. Note:
This state is outside the CP scope.
SST=SDEE; MGRACD=<>
– The OTU is not assigned to any plane, the associated TCM entity is assigned to
CP.
SST=SDEE; MGRACD=<>
– The OTU is assigned as supporting facility to an INNI DB, no traffic is
established.
SST=CP,SDEE; MGRACD=CP
– The OTU is assigned as supporting facility to an INNI DB with traffic being
established.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
SST=CP,SDEE; MGRACD=CP
– The OTU is assigned as supporting facility to an INNI DB, traffic is established,
no associated TCM entity exists. Note: This state is a transient state. It will be left
automatically by CP creating a TCM entity.
SST=CP,SDEE; MGRACD=<>
– The OTU is assigned as supporting facility to a DROP DB, traffic is established,
no associated TCM entity exists.
SST=CPMP,SDEE; MGRACD=CP&MGNPLN;
• SGEO – Supporting Entity Outage
The associated supporting entity has failed (OOS-AU) or is out-of-service due to a
management action (OOS-MA or OOS-AUMA), or set itself to state SGEO.
• STBY – Standby
Information needed
• STBYC – Standby Cold
The system component is the standby unit for another system component. A standby
unit with a cold standby status will not be immediately able to take over the role of
the active unit, and will require some initialization activity. An autonomous or manual
switch cannot be performed within 50 ms. Note: The STBYC state will be maintained
even when the standby unit is out of service. The STBYC state is mutually exclusive
with the WRK and STBYH states.
• STBYH – Standby Hot
In a facility protection scheme, this secondary state is declared on the standby facility
whenever a switch request or signal fail or signal degrade (SF/SD) condition is not
present. In the context of equipment protection this state is also declared for the
standby matrix card.
• STBYS – Standby Switched
In a facility protection scheme, this secondary state is declared on the standby facility
whenever any switch request (other than WTR, DNR, or NR) is present.
• SWDL – Software Download
A software download is in progress, the system component is out of service because it
is in the process of acquiring, loading, and/or initializing its software.
• TRM – Terminated
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
The facility entity has been given termination parameters, that means, the entity has
been connected and its path has been terminated (as a result of the connection) or the
parent entity has been terminated as a result of its sub-entities being connected. For
line entities, this state indicates that the entity is supporting cross-connections.
• UAS – 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.
• UEQ – Unequipped
There is no system component in the addressed position.
• WRK – Working
The entity is currently providing service as part of a protection group (for instance,
selector is selecting this entity in a path protection configuration).
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Optical transponder and client/line card protection
Provisioning
....................................................................................................................................................................................................................................
Optical transponder and client/line card protection

Supported transponder cards and types of protection
Optical transponder cards in Alcatel-Lucent 1830 PSS support several protection
configurations.
• Per-channel optical line protection (with OPS) (1+1 optical path)
• Optical sub-block network connection protection (O-SNCP) [O-SNCP, 1+1 Optical
Path and Equipment protection configuration (Y-cable splitter/coupler between the
pair of OTs and client equipment)]
• Diverse route
Note: Y-cable protection cannot currently be used with OTM0.2 client on 11STAR1
OT. ODU2 is handled transparently, so APS/PCC bytes are not available for
protection signaling.
1830 PSS supports fiber span and segment protection of optical transponders:
• Optical Line Protection (OLP) protects the path between two adjacent network
element degrees by splitting to and selecting from two transmission fibers.
• Optical Multiplex Section Protection (OMSP) protects the path between two network
element degrees by splitting the OMS into two diverse transmission paths (each of
which can consists of several spans) at the source end and selecting one of the paths at
the switch end.
Note: Optical protection types cannot be combined along a transmission path. For
example, OCHP should not be combined with OLP or OMSP.
The protection capabilities of and for the Alcatel-Lucent 1830 PSS WDM OTs, and the
release in which they were first supported, are detailed in Table 19-37, “OT protection
support - 100G OTs” (p. 19-116).
Table 19-37 OT protection support - 100G OTs
OT Protection WDM Shelf NE regen. support

type PSS-8 PSS-16 PSS- PSS-32 for protected
16II paths
112SDX11 OMSP R8.2 R7.0 — R7.0 No

112SCA1 OPS (OCHP) — — — R5.1 R5.1
Client side — — — R7.0 R7.0
OPS
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Table 19-37 OT protection support - 100G OTs (continued)

16II paths
112SNA1 OPS (OCHP) — — — R5.1 R5.1

OLP — — — R5.5 R5.5
OMSP — — — R8.0 R8.0
Client side — — — R7.0 R7.0
OPS
112SCX10 OPS (OCHP) — — — R5.1 R5.1
Y-cable — — — R3.6.5 R3.6.5
OMSP — — — R5.0 R5.0
112SNX10 OPS (OCHP) — — — R5.1 R5.1
Y-cable — — — R3.6.5 R3.6.5
OLP — — — R5.5 R5.5
OMSP — — — R6.0 R6.0
130SCX10 OPS (OCHP) R8.1 — R8.2 R5.5 R5.5
Y-cable R8.0.2 — R8.1 R5.5 R5.5
Y-cable SD R8.2 R8.2 R8.2
switching
OMSP R8.1 — R8.2 R8.0 R8.0
130SNQ10 — — — — — —
130SNX10 OPS (OCHP) R8.1 — R8.2 R7.0 R7.0
Y-cable R8.0.2 — R8.1 R7.0 R7.0
Y-cable SD R8.2 R8.2 R8.2
switching
OMSP R8.1 — R8.2 R8.0 R8.0
130SCA1 Client side — — — R6.0.6 R6.0.6
OPS
1UD200 HO-ODU2/2e R8.2 — R8.2 — R8.2
SNCP
(w/20P200)
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Table 19-37 OT protection support - 100G OTs (continued)

16II paths
260SCX2 Client-side — — — R7.0 R7.0

OPS
OMSP R8.1 — R8.2 R8.0 R8.0
OPS (OCHP) R8.1 — R8.2 R7.0 R7.0
Table 19-38 OT protection support - 40G OTs

16II paths
43SCA1 — — — — R7.0 R7.0

43SCGE1 — — — — — —
43SCX4 Y-cable — — — R3.6 R3.6
Y-cable SD — — — R8.2 R8.2
switching
43SCX4E Y-cable — — — R5.0 R5.0
Y-cable SD — — — R8.2 R8.2
switching
43STA1P Y-cable — — — R2.5 No
43STX4 Y-cable — — — R2.0 Yes
43STX4P Y-cable — — — R2.5 Yes
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Table 19-39 OT protection support - other OT/VAC cards

16II paths
11DPE12 E-SNCP — R2.5 — R2.5 No

(FullRate)
E-SNCP — R3.0 — R3.0 No
(Q-in-Q)
OMSP — R6.0 — R6.0 Yes
Y-cable — — — — No
11DPE12A E-SNCP R8.2 R5.1 R8.2 R5.1 Yes
(Q-in-Q)
LAG R8.2 R5.1 R8.2 R5.1 Yes
OMSP R8.1 R8.0 R8.2 R8.0 R8.0
OLP R8.1 R5.5 R8.2 R5.5 R5.5
Y-cable R8.2 R6.0 R8.2 R6.0 R6.0
11DPE12E E-SNCP — R3.5 — R3.5 Yes
(Q-in-Q)
OLP — R5.5 — R5.5 R5.5
OMSP — R8.0 — R8.0 R8.0
Y-cable — — — — Yes
11DPM12 Y-cable R8.0.2 R3.6 R8.1 R3.6 R3.6
Y-cable SD R8.2 R8.2 — R8.2 R8.2
switching
ODU SNCP R8.0.2 R6.0 R8.1 R6.0 R6.0
OLP R8.1 R6.0 R8.2 R6.0 R6.0
OMSP R8.1 R6.0 R8.2 R6.0 R6.0
11OPE8 ERP R8.0.2 R7.0 R8.1 R7.0 R7.0
LAG R8.0.2 R7.0 R8.1 R7.0 R7.0
11QCE12X ERP R8.0.2 R7.0 R8.1 R7.0 R7.0
LAG R8.0.2 R7.0 R8.1 R7.0 R7.0
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Table 19-39 OT protection support - other OT/VAC cards (continued)

16II paths
11QPA4 Client Side — R5.1 — R5.1 Yes

OPS
E-SNCP R8.0.2 R2.5 R8.1 R2.5 Yes
OLP R8.1 R5.5 R8.2 R5.5 R5.5
OMSP R8.1 R5.0 R8.2 R5.0 No
OPS (OCHP) R8.1 R3.6 R8.2 R3.6 R3.6
Y-cable R8.0.2 R3.6 R8.1 R3.6 R3.6
11QPE24 ERP — R5.1 R8.2 R5.1 Yes
LAG — R5.1 R8.2 R5.1 Yes
11QPEN4 E-SNCP R8.0.2 R5.0 R8.1 R5.0 R5.0
OMSP R8.1 R5.0 R8.2 R5.0 No
OPS (OCHP) R8.1 R5.0 R8.2 R5.0 R5.0
Y-cable R8.0.2 R5.0 R8.1 R5.0 R5.0
11STAR1 Client Side — R5.1 — R5.1 Yes
OPS
OLP — R5.5 — R5.5 R5.5
OMSP — R5.0 — R5.0 No
OPS (OCHP) — R3.0 — R1.0 Yes
Y-cable — R2.5 — R1.0 No
11STAR1A Client Side — R5.1 — R5.1 Yes
OPS
OLP — R5.5 — R5.5 R5.5
OMSP — R8.0 — R8.0 R8.0
OPS (OCHP) — R5.0 — R5.0 R5.0
11STGE12 OPS (OCHP) — R3.0 — R1.0 No
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Table 19-39 OT protection support - other OT/VAC cards (continued)

16II paths
11STMM10 Client Side — R5.1 — R5.1 Yes

OPS
OMSP — R5.0 — R5.0 No
OPS (OCHP) — R3.0 — R1.0 No
12P120 ODU SNCP R8.2 — R8.2 R8.2 R8.2
20P200 HO-ODU2/2e R8.2 — R8.2 — R8.2
SNCP
(w/1UD200)
4DPA2 E-SNCP — R2.5 — R2.5 No
4DPA4 E-SNCP R8.2 R2.5 — R2.0 R3.6.5
(FlexMux) Y-cable R8.2 R5.1 — R5.1 R5.1
MVAC OPS (OCHP) — R3.5 — R3.5 No
MVAC8B OPS (OCHP) — R5.0 — R5.0 No
SVAC OPS (OCHP) — R3.0 — R1.0 No
Optical protection overview

The Alcatel-Lucent 1830 PSS and 1830 PSS-4 supports optical 1+1 protection on a
per-wavelength basis over any network topology where diverse routes are available.
Alcatel-Lucent 1830 PSS provides a choice of 1+1 architectures that allow the network
operator to make capex versus service availability trade-offs. In other words, the amount
of line and transmission equipment redundancy can be adjusted to restrict the number of
single points of failure commensurate with a targeted availability requirement.
The Alcatel-Lucent 1830 PSS and 1830 PSS-4 protection options share several common
features.
• Channels are protected on an individual basis
• Protected and unprotected channels can be mixed in nodes and in fiber paths.
• Protection switching is performed in less than 50 ms.
• Lockout, forced, and manual switching are supported.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Examples include: full digital PMs on client and line side, facility and terminal
loopbacks, muxing of lower speed clients into single wavelength, wider range of optical
1+1 protection options, better support of remote clients, guaranteed engineering rules
under all operating conditions and over the lifetime of the equipment.
In addition to the overview information provided here, configuration details are available
in “Protection configurations” (p. 17-117).
Per-channel optical line protection (with OPS)

This 1+1 option protects the optical line only. However, because the optical transponder is
not duplicated, it is the lowest cost option.
Refer to Figure 19-30, “Per-channel optical line protection” (p. 19-122)
Figure 19-30 Per-channel optical line protection
Following the left to right signal path, an unprotected client signal is converted to a WDM
line signal by a transponder. An Optical Protection Switch (OPS) pack is inserted between
the transponder and WDM filter. The OPS head-end bridges (passive optical splitting) the
line signal to a pair of diversely routed fibers. At the far end of the network, the two line
signals are received by the far-side OPS. The OPS switches (optically) a valid line signal
to the far-end transponder, which forwards the signal to the far-end client. In the event of
a line fiber cut on the working path, the far-end OPS switches to the alternate signal. The
switching criteria is based on loss of optical power. The OPS also monitors the health of
the protect path so that if there is a fiber cut, the signal will be switched to a known good
path. The reverse path operates in the same but independent manner, that is, the OPS
supports unidirectional switching.
Only non-revertive mode is currently supported by the OPS in Alcatel-Lucent 1830 PSS.
Revertive switching is planned for support in a future release of Alcatel-Lucent 1830 PSS.
Optical sub-block network connection protection (O-SNCP)

This option 1+1 protects both the optical line and the transponders for higher service
availability.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Refer to Figure 19-31, “Optical sub-network connection protection (O-SNCP)”
(p. 19-123)
Figure 19-31 Optical sub-network connection protection (O-SNCP)
Following the left to right signal path, an unprotected client signal is passively head-end
bridged by the Y-cable to a pair of redundant transponders. Each transponder transmits a
WDM line signal onto a diversely routed fiber. One signal is the primary, and one signal
is the secondary. At the far end, the primary and secondary signals are received by
another pair of redundant transponders. The transponder receiving the primary line signal
converts it to a client signal and passes it through the Y-cable to the client equipment. The
secondary transponder has its client interface turned off. In the event of a primary line
fiber cut or primary transponder failure the primary transponder in the failed path will
disable client signal transmission and the secondary transponder will turn on its client
signal transmission.
A major advantage to O-SNCP over using an OPS card is that the transponders perform
the switching. Because the transponders are O-E-O devices, protection switching can be
triggered by digital performance monitoring. Excessive BER is monitored by a
provisionable parameter, sfth, that the user can set to BER=10-3, or 10-4, or 10-5, when
an 11STAR1 or 11STMM10 client port is provisioned to SONET/SDH. (See
theAlcatel-Lucent 1830 Photonic Service Switch (PSS) Release 8.2 User Provisioning
Guide for complete parameter details.) Defects that contribute to a switch of 10G LAN
clients are Loss of Signal, Loss of Synchronization, HIBER, and line-side OTN defects
(LOS, LOF, LOM, and so on). The HIBER threshold is not a provisionable parameter.
The secondary path is monitored in an identical manner.
Switching can be provisioned as unidirectional or bidirectional, the latter required to
support Gigabit Ethernet auto-negotiation with client switches/routers. Revertive and
non-revertive switching are supported.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
The following tables illustrate the difference between priorities for Y-cable bidirectional
protection-side switching, and bidirectional working-side switching (along with both
unidirectional working and protection side switching).
Table 19-40 Bidirectional working side and Unidirectional (working and

protection side) priorities
Priority rank Switch Request

Forced Switch
SF
Manual Switch
Lowest No Request
Table 19-41 Bidirectional protection side priorities
Priority rank Switch Request

SF
Forced Switch
Manual Switch
Lowest No Request
Although the Y-cable is a single point of failure, it is only a passive component with a
very low failure rate. Note that there are three versions of the Y-cable: one supports
single-mode fiber connections (YSMF), and two support multi-mode client fiber: 50/125
(YMMF50) and 62.5/125 (YMMF62).
One restriction that applies to O-SNCP is that the transponder pair in each node must
reside in the same shelf, as they communicate over the shelf backplane for the protection
switching protocol.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Electrical sub-block network connection protection (E-SNCP)
E-SNCP is a line side (network side) protection mechanism which protects against loss of
the line signal due to an OTM failure, fiber interruption, or a malfunction of an
intermediate NE node.
It is supported on the OTs shown in Table 19-37, “OT protection support - 100G OTs”
(p. 19-116).
selection
Protection of alien wavelengths

Alien wavelengths are admitted into the Alcatel-Lucent 1830 PSS-32/1830 PSS-16 at the
SVAC. To support 1+1 optical layer protection for alien wavelengths, the OPS card is
used on the client side of a pair of redundant SVACs.
Refer to Figure 19-32, “Protection of alien wavelengths” (p. 19-125)
Figure 19-32 Protection of alien wavelengths
The OPS card operates in the same manner with the same features as in optical line
protection, but since it is on the client side of redundant SVACs.
Optical multiplex section protection (OMSP)

Optical multiplex section protection provides two diverse paths for an OMS segment of
the network. This is an expensive option when ILAs are used due to the duplication of
equipment along the working and protection paths, however it provides complete
redundancy of the amplifiers from the OMS split end to the OMS switch end. illustrates
of OMSP for a single span network. Figure 19-34, “OMSP for multi-span network”
(p. 19-126) illustrates the case of multiple spans protected by OMSP. In this case ILA
sites are used between the spans.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Figure 19-33 Single span protected by OMSP
Figure 19-34 OMSP for multi-span network
Note: In above configurations, there could be an ITLB between SFD and OPS card.
The OPS at the source end provides the optical split at the source and at the sink end the
OPS selects one of the two possible input signals. The user provisions the switch
thresholds to use at the OPS for each of the input ports. The hierarchy of switch requests
supported for OCHP is also supported for OMSP.
Supported configurations are listed in “Optical Multiplex Section Protection (OMSP)”
(p. 17-129).
Provisioning required to deploy OMSP can be found in the Alcatel-Lucent 1830 PSS User
Provisioning Guide.
Note: The protection switch time for 100G OTs used with OMSP may exceed 50
msec due to hardware limitations. Refer to the Customer Release Notes for details.
Optical Line Protection (OLP)

Optical Line Protection is a 1+1 protection scheme for the optical line OTS layer,
providing two separate fiber connections between adjacent network element degrees.
(These separate connections could be diversely physically routed.) An optical protection
switch pack provides the optical bridging function at the source end and switch selection
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
of one of the signals from the two possibilities at the receiving end. This option provides
path diversity between adjacent degrees that can be useful for protecting against span
fiber breaks. Figure 19-35, “Basic network connections between nodes supporting OLP”
(p. 19-127) illustrates three examples of spans protected using OLP.
Figure 19-35 Basic network connections between nodes supporting OLP
The user can provision the switch threshold for each of the switch input ports of the OPS;
often the default is sufficient. The hierarchy of switch requests supported for OCHP is
also supported for OMSP.
Supported configurations are listed in “Optical Line Protection (OLP) node
configurations” (p. 17-133).
Provisioning required to deploy OLP can be found in the Alcatel-Lucent 1830 PSS User
Provisioning Guide.
Note: The protection switch time for 100G OTs used with OLP may exceed 50 msec
due to hardware limitations. Refer to the Customer Release Notes for details.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Protection above the optical layer
Alcatel-Lucent 1830 PSS optical 1+1 protection architectures include a tool kit that
provides an alternative to protection above the optical layer by the client equipment. For
protection above the optical layer, SDH/SONET ADMs and XCs, Ethernet switches, and
IP routers can offer the Alcatel-Lucent 1830 PSS-32/1830 PSS-16 redundant client
interfaces and perform protection switching at their respective higher layers.
For protection at the optical layer, the Alcatel-Lucent 1830 PSS-32/1830 PSS-16 treats
the two interfaces independently and routes them diversely.
Although protection above the optical layer can often provide the highest availability, it is
generally the most expensive to deploy.
Client side OPS Protection for cards supporting 100G client signals
This feature provides client-side OPS protection for cards that support 100G client signals
using the OPSB protection card.
The following cards on the PSS-32 shelf support this protection scheme.
• 260SCX2
• 130SCA1
• 112SNA1
• 112SCA1
The feature requires the two transponder cards to be located either in the same shelf,
different shelves in the same NE or in different co-located NEs.
In client-side OPS protection configurations, two transponders are required. These
configurations provide protection against line failures (such as fiber cut or LD failures),
OT failures and shelf power failures. The OPSB card (with the non-latching switch) shall
be used for client-side OPS protection.
This feature is supported in TOADM, ROADM and FOADM nodes. The OPSB card is
positioned between the client equipment and the OT client port. See the general
configuration in the following Figure 19-36, “Client side OPS protection configuration
with OPSB card” (p. 19-129). In this figure, the working OT and the protection OT are
shown in the same shelf, although they can be in separate shelves or NEs.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Figure 19-36 Client side OPS protection configuration with OPSB card
Since the 260SCX2 card supports 130G mode (one client interface equipped) and 260G
mode (two client interfaces equipped), the following cases are supported:
• one client and one OPSB card in 130G mode
• one client and one OPSB card in 260G mode
• two clients and two OPSB cards in 260G mode
Client side OPS Protection in two 1830 NEs
Client side OPS protection is supported in two NEs as shown in the following figure.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
Figure 19-37 Client side protection configuration with OPSB card in two different
NEs for each OT
Working and Protection OTs in different shelves in the same NE

In a client side protection configuration, the working OT, the protection OT, and the
OPSB can be located in two different shelves within the same NE, to protect against shelf
power problems. In this configuration, the OPSB card resides with the working or
protection OT in one shelf. The two shelves can belong to one NE or two NEs. The OT
which resides with the OPSB should connect to port A of the OPSB. The OT in another
shelf should connect to port B of the OPSB (which is the default path for the non-latching
switch).
When provisioning the protection group, the A port is preferred to be on the working path
and the B port is preferred to be on the protection path. But software should not preclude
working path at B port and protection path at A port.
If the B port on the OPSB card is connected to the OT that resides in the shelf with the
OPSB card, the connection between OPSB A port and an OT in another shelf should be
denied, and the NE will give a warning “For the Client Side OPS protection
in two shelves, only the B port is for the OPS connection
between two shelves.”
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
If the B port on the OPSB card is connected to the OT that resides in the shelf with the
OPSB, the connection between the OPS A port and an external point should be denied,
and the NE will give a warning “For the Client Side OPS protection in
two shelves, only the B port of OPS is for the OPS connection
between two shelves.”
If the A port on the OPSB card is connected to an OT on another shelf, the connection
between B port and the OT in the same shelf should be denied, and the NE will give a
warning “For the Client Side OPS protection in two shelves, only B
port is for the OPS connection between two shelves.”
Figure 19-38 Client side protection configuration with OPSB card in two shelves on
the same NE
....................................................................................................................................................................................................................................
WDM operations, administration, maintenance, and Optical protection for 40G OTs
Provisioning
....................................................................................................................................................................................................................................
Optical protection for 40G OTs

1+1 optical protection support
The 40G OTs support 1+1 optical protection through a Y-cable. In this configuration, two
physically adjacent packs have Y-cables equipped on the protected client ports. Y-cable
protection is a network protection mechanism which protects the transponder card, client
side laser, network side laser, and network side fibers (assuming diverse fiber routes).
1+1 Y-cable configuration
Other line-interface based protection schemes, using an OPS pack are not supported. The
40G packs contain a Tunable Dispersion Compensator (TDC) on line-side receive ports.
The amount of time required for this TDC to tune to its optimum dispersion compensating
value does not meet protection switch time requirements.
Y-cable protection is based on permanent head end bridging and dynamic tail-end
selection, with a pair of redundant OT cards at each end. A passive Y-cable (optical
splitter/joiner) is attached to a pair of working/protection ports, one port on the OT card at
each end. The head-end bridge is done by the Y-cable splitter on the Rx of the client-side
ports at the near end. The incoming signal from the client equipment is split and received
by both near end OT cards (working and protection).
Figure 19-39 Y-cable protection
The tail-end selection is done by having one of the far end working/protection OT cards
turn its transmit client-side laser on, while the other turns its laser off. This transmit signal
is channelled through the Y-cable joiner (splitter in reverse direction) and sent to the client
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 also provide protection in that
direction.
Local protection negotiations at each end are done between paired Y-cable OTs through a
dedicated backplane communication channel for quick signalling. This channel does not
require that a shelf control card be present. Remote end-to-end protection information is
exchanged using the standard GR-253 1+1 APS K-byte protocol, carried in a proprietary
manner in the APS/PCC channel of the 40G ODU3 overhead.
....................................................................................................................................................................................................................................
Provisioning
....................................................................................................................................................................................................................................
1+1 Y-cable switching
Y-cable protection 1+1 uni-directional switching is supported. Each end makes an
independent switching decision based on defects affecting the direction of transmission
received from the line side, or based on user commands. One end may select from the
working line while the other end is selecting from protection. The K-byte APS protocol
carries fault status and protection information from end to end, but this information does
not contribute to the near end switching decision. Bi-directional switching may be
considered for future releases.
43G Y-cable protection is currently non-revertive only.
Y-cable pack installation and connection
Both the working and protection OT cards must be installed in the same 1830 PSS shelf
to allow the necessary backplane communication between the paired Y-cable cards.
Within each shelf, there are specific pairs of slot locations which support this backplane
communication between the cards. This allows considerable flexibility in card location,
and does not limit the number of cards per shelf.
Each Y-cable must connect corresponding client ports on the working and protection OT
cards. For example, working port C1 must be connected to protection port C1, or C2 to
C2, and so on. For further Y-cable connection details, refer “Y-Cable protection”
(p. 17-139).
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
20 20 system planning and
WDM
engineering
Overview
Purpose
This chapter provides general system planning and engineering information for
Alcatel-Lucent 1830 Photonic Service Switch (PSS) for the WDM application.
Contents
Alcatel-Lucent 1830 PSS-32/PSS-16/PSS-16II/PSS-8 shelves 20-2

Alcatel-Lucent Engineering and Planning Tool 20-12
Power and grounding 20-13
Operating environment 20-17
Cooling 20-20
...................................................................................................................................................................................................................................
WDM system planning and engineering Alcatel-Lucent 1830 PSS-32/PSS-16/PSS-16II/PSS-8 shelves
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS-32/PSS-16/PSS-16II/PSS-8 shelves

Overview
The Alcatel-Lucent 1830 PSS-16 and Alcatel-Lucent 1830 PSS-32 shelves support WDM
applications. These shelves, and other supporting shelves, are described below.
Universal-slot Shelf Descriptions

The following information describes the Alcatel-Lucent 1830 PSS-32, Alcatel-Lucent
1830 PSS-16, Alcatel-Lucent 1830 PSS-16II, and Alcatel-Lucent 1830 PSS-8 shelves,
used for WDM applications. These 1830 PSS shelf variants support the 1830 PSS
Universal Slot interface on the backplane. Each application card slot supports two card
interfaces per slot, allowing them to accept two half height cards in each slot when that
slot is also equipped with a half-slot adapter (HSLAD).
Alcatel-Lucent 1830 PSS-32 central office shelf (COSHF)
The Alcatel-Lucent 1830 PSS-32 shelf supports:
• 32 paired half height application cards (or 16 full height application cards)
• 2 equipment controllers (EC)
• 2 redundant power input filters
• 1 user panel
• 1 fan unit
All fibering and subrack maintenance can be performed at the front of the chassis, thus
allowing back-to-back installation when mounted in ETSI 300 mm cabinets. Refer
toAlcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 8.2
Installation and System Turn-Up Guide for full details.
Alcatel-Lucent 1830 PSS-16 end office shelf (EOSHF)
• 16 paired half height application cards (or 8 full height application cards)
• 1 user panel (occupies one of the paired application card slots)
• 1 fan unit
All fibering and maintenance can be performed at the front of the chassis, allowing
back-to-back installation in ETSI 300 mm cabinets. (See Alcatel-Lucent 1830 Photonic
Service Switch 16/32 (PSS-16/PSS-32) Release 8.2 Installation and System Turn-Up
Guide for full details.)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS-16II end office shelf (EOSHF)
The Alcatel-Lucent 1830 PSS-16II shelf supports:
• 16 paired half height I/O cards (or 8 full height I/O cards)
• 1 user panel
• 1 fan unit
Service Switch 16II (PSS-16II) Release 8.2 Installation and System Turn-Up Guide for
full details.)
Alcatel-Lucent 1830 PSS-8 end office shelf (EOSHF)
• 8 paired half height I/O cards (or 4 full height I/O cards)
• 1 user panel (In the shared slot of EC when protection EC is not installed)
• 1 shelf panel
• 1 fan unit
Service Switch 8 (PSS-8) Release 8.2 Installation and System Turn-Up Guide for full
details.)
Management connections between main and sub-tending shelves

The Equipment Controller on Alcatel-Lucent 1830 PSS-32, Alcatel-Lucent 1830 PSS-16,
Alcatel-Lucent 1830 PSS-16II and Alcatel-Lucent 1830 PSS-8 shelves provide all node
and shelf control and management functions for a shelf.
The functions performed by the EC depend on the shelf in which it resides. The first
active shelf is the “main” shelf. The EC in the main shelf is the main controller, and it
provides the LAN interfaces to external management systems and sub-tending shelves.
The EC maintains the persistent database and configures all shelves and packs in the NE
accordingly, and it also monitors their health.
An EC in a sub-tending shelf is called a sub-tending controller, which coordinates all
communication within its shelf and communicates fault and performance data back to the
main controller. Flash cards (required) in subtending controllers will be automatically
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
upgraded along with the main controller when software upgrades are performed. Refer to
the Alcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 8.2
Installation and System Turn-Up Guide for upgrade details.
Management connectivity between shelves is done through Ethernet ports on the ECs.
Main and subtending configurations are supported as shown in following table.
Table 20-1 1830 PSS WDM shelf combinations
Main shelf Subtending Number of Non-Universal shelf types

Universal Shelf subtending shelves
PSS-32 PSS-8 0-2 PSS-8 shelves DCM
PSS-16 0-8 PSS-16 shelves ITLB, ITLU
PSS-16II 0 to 23 PSS-16II MSH8-FSM
PSS-32 shelves SFD40, SFD40B, SFD44,
0-23 PSS-32 shelves SFD44B
(Maximum 23
combined)
PSS-32 0-23 PSS-32 shelves ITLB, ITLU
(Maximum 23 SFD40, SFD40B, SFD44,
combined) SFD44B
PSS-16II PSS-16II 0-23 PSS-16II shelves DCM
ITLB, ITLU
SFD44, SFD44B
VWM-CW, VWM-DW
ITLB, ITLU
SFD44, SFD44B
VWM-CW, VWM-DW
Notes:
1. The PSS-8 and PSS-16II shelves cannot be combined together or with any other shelf types.
The following illustrations show examples of possible multi-shelf configurations and their
management connections.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 20-1 Sample multi-shelf 1830 PSS-32 NE connectivity
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 20-2 Sample multi-shelf 1830 PSS-16/32 NE connectivity
....................................................................................................................................................................................................................................

10 - Manual Do Produto - 1830 PSS 16II

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

10 - Manual Do Produto - 1830 PSS 16II

Uploaded by

Copyright:

Available Formats

WDM product description 11G Quad-port encryption transponder (11QPEN4)

11G-Cost/footprint optimized transponder (12P120)

12P120 functional description

Figure 18-160 12P120 block diagram

Table 18-71 12P120 client signal types

Client signal Bit rate Standard

12P120 card configurations

Figure 18-161 12P120 Transponder card configurations

12P120 physical design

Figure 18-162 12P120 front view

1 Card status LED

12P120 pluggable modules

20x10G Multirate I/O Module (20P200)

20P200 physical design

Figure 18-163 20P200 faceplate

1 Card status LED

Figure 18-164 Unprotected Client + Unprotected line configuration

LO-ODUC SNCP XC Model

Figure 18-165 ODU2(e) SNCP XC model

20P200 and 1UD200 ADM network configuration

20P200 and 1UD200 muxponder network configuration

Figure 18-166 100G/200G muxponder with 20P200 and 1UD200

The following ODU XCs support 100G muxponder configuration:

20P200 pluggable modules

40G Single line Coherent Gigabit Ethernet with 1 client

Figure 18-167 C43G4C module (4x10 CFP)

The C43G4C client interface supports the following requirements:

Figure 18-168 43SCGE1 Transmission path

Line transmit direction details:

43SCGE1 front view

Figure 18-169 43SCGE1 faceplate

1 Card status LED

2 Client port Ethernet activity LED (C1 ETH)

3 Client port status LED (C1)

4 Line port status LED (L1)

6 Client port interface

43G Single Port Tunable AnyRate Mux - 4 clients (43SCX4,

Range Minimum Maximum

Wavetracker is supported on the line interface for optical power auto-management in

Client signal Bit rate Standard

Figure 18-170 43SCX4(E) block diagram

43SCX4 and 43SCX4E front views

Figure 18-171 43SCX4 faceplate

4 Client port interfaces (C1 - C4)

5 Client port status LEDs (C1 - C4)

6 Client port Ethernet activity LEDs (C1 ETH - C4 ETH)

43G Single Port Tunable Mux Transponder - 4 clients (43STX4,

43STX4/43STX4P functional description

Figure 18-173 43STX4/43STX4P OT block diagram

43STX4/43STX4P front view

Figure 18-174 43STX4/43STX4P OT faceplate

43G Single Port Tunable AnyRate Transponder - 1 client

43STA1P functional description

Figure 18-175 43STA1P Block Diagram

43STA1P front View

Figure 18-176 43STA1P faceplate

43G Single Port Tunable Coherent AnyRate Transponder - 1

Table 18-72 Line interface range

Range Minimum Maximum

Table 18-73 Client signal supported

Client signal Bit rate Standard

43SCA1 functional description

Figure 18-177 43SCA1 Block Diagram