CRN 1830PSS R7.0.2 PDF

October31!
Og16
Alcatel-Lucent 1830
Photonic Service Switch 16/32 (PSS-16/PSS-32) | Release 7.0.2
Customer Release Notes
8DG-62933-AAAA
Issue 1 | October 2014
Alcatel-Lucent Proprietary
Use pursuant to applicable agreements
Alcatel-Lucent Proprietary 1
Use pursuant to applicable agreements
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2014 Alcatel-Lucent. All Rights Reserved.

Contains proprietary/trade secret information which is the property of Alcatel-Lucent.
Not to be made available to, or copied or used by anyone who is not an employee of Alcatel-Lucent except when there is a valid non-disclosure agreement in
place which covers such information and contains appropriate non-disclosure and limited use obligations. Not to be used or disclosed except in accordance
with applicable agreements.
Notice
Every effort was made to ensure that this information product was complete and accurate at the time of printing. However, information is subject to change.
Conformance statements
Interference Information: Part 15 of FCC Rules
NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits
are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy. If the equipment is not installed and used in accordance with the guidelines in this document, the
equipment may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference,
in which case the user will be required to correct the interference at the expense of the user.
Security statement
In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such an event,
applicable tariffs require that the customer pay all network charges for traffic. Alcatel-Lucent cannot be responsible for such charges and will not make any
allowance or give any credit for charges that result from unauthorized access.
Limited warranty
For terms and conditions of sale, contact your Alcatel-Lucent Account Team.
Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary ii

8DG-62933-AAAA Release 7.0.2 Use pursuant to applicable agreements
Issue 1 October 2014
Contents
Contents
About this document ix
ix
ix
Purpose ..................................................................................................................................................... ix
ix
Reason for reissue .................................................................................................................................... ix
Intended audience..................................................................................................................................... ix
ix
ix
How to use this document ........................................................................................................................ ix
x
Safety information ......................................................................................................................................x
Conventions used .......................................................................................................................................x
x
Related information .................................................................................................................................. xi
xi
Software ordering ................................................................................................................................... xiii
xiii
Online Customer Support (OLCS) ......................................................................................................... xiii
xiii
How to comment .................................................................................................................................... xiii
xiii
1 Features 15
15
Supported hardware .................................................................................................................................16
16
New features in Release 7.0.2 ..................................................................................................................25
25
Features in Release 7.0.1 ..........................................................................................................................36
36
Features in Release 7.0.0 ..........................................................................................................................41
41
Supporting tools .......................................................................................................................................49
49
Application notes .....................................................................................................................................50
50
2 Issues 55
55
Resolved issues ........................................................................................................................................56
56
Known issues in Release 7.0.2 .................................................................................................................65
65
Restrictions.............................................................................................................................................145
145
3 Software Installation and Upgrade 149
149
New software installation general instruction ........................................................................................151
151
Software upgrade general instruction .....................................................................................................163
163
CLI instructions......................................................................................................................................180
180
WebUI instructions ................................................................................................................................231
231
PhM instructions ....................................................................................................................................266
266
iii Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

Use pursuant to applicable agreements 8DG-62933-AAAA Release 7.0.2
Contents
Example configuration of ftp server ...................................................................................................... 303

303
Firmware for Release 7.0.2 .................................................................................................................... 313
313
Firmware management procedures ........................................................................................................ 338
338
Maintain current firmware ..................................................................................................................... 340
340
Normal firmware upgrade (cold reboot) ................................................................................................ 342
342
In-service (hitless) firmware upgrade for OT cards ............................................................................... 344
344
In-service (hitless) firmware upgrade for LD cards ............................................................................... 346
346
Firmware issues if upgrading from Release 3.6.58 to Release 7.0.2 via Release 5.1.6 ......................... 348
348
Firmware-related operations for reference ............................................................................................. 349
349
Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary iv

Contents
List of figures
Figure 3-1 PC command window .................................................................................................................... 155 155
Figure 3-2 156
Login Screen .................................................................................................................................. 156
Figure 3-4 Alcatel-Lucent 1830 PSS-16/PSS-32 WebUI uninitialized database warning .............................. 158 158
Figure 3-5 WebUI system properties .............................................................................................................. 159 159
Figure 3-6 Windows firewall settings ............................................................................................................. 161 161
Figure 3-8 Windows Firewall settings ............................................................................................................ 177 177
Figure 3-12 CLI FTP server settings ................................................................................................................. 196 196
Figure 3-13 CLI FTP server settings ................................................................................................................. 219 219
Figure 3-14 WebUI FTP server settings ............................................................................................................ 231 231
Figure 3-15 WebUI software upgrade ............................................................................................................... 232 232
Figure 3-17 236
Login Screen .................................................................................................................................. 236
Figure 3-18 WebUI system properties .............................................................................................................. 237 237
Figure 3-21 WebUI backup/restore window ..................................................................................................... 239 239
Figure 3-22 241
Software NE .................................................................................................................................. 241
Figure 3-25 WebUI software upgrade ............................................................................................................... 244 244
Figure 3-26 WebUI software revert warning window....................................................................................... 248 248
Figure 3-27 WebUI ECX - FTP server settings ................................................................................................ 250 250
Figure 3-28 WebUI ECX software upgrade ...................................................................................................... 251 251
Figure 3-30 WebUI ECX - Login Screen ......................................................................................................... 255 255
Figure 3-31 WebUI ECX system properties .................................................................................................... 256 256
Figure 3-32 WebUI Software NE ...................................................................................................................... 257 257
Figure 3-33 WebUI ECX FTP server settings ................................................................................................... 258 258
Figure 3-34 WebUI ECX FTP server settings ................................................................................................... 259 259
Figure 3-35 WebUI ECX software upgrade ...................................................................................................... 260 260
Figure 3-36 WebUI software revert warning window....................................................................................... 265 265
Figure 3-37 1354 RM-PhM NE backup menu .................................................................................................. 267 267
Figure 3-38 1354 RM-PhM NE backup ............................................................................................................ 267 267
Figure 3-39 1354 RM-PhM NE backup details menu ....................................................................................... 268 268
Figure 3-40 1354 RM-PhM NE backup icon .................................................................................................... 268 268
Figure 3-41 1354 RM-PhM software upgrade menu......................................................................................... 270 270
Figure 3-42 1354 RM-PhM software upgrade window..................................................................................... 271 271
Figure 3-43 1354 RM-PhM software upgrade properties window.................................................................... 271 271
Figure 3-44 1354 RM-PhM Add NEs window ................................................................................................ 272 272
Figure 3-45 1354 RM-PhM target directory window........................................................................................ 273 273
Figure 3-46 1354 RM-PhM software upgrade menu......................................................................................... 274 274
v Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32
Contents
Figure 3-47 1354 RM-PhM software upgrade window ..................................................................................... 275 275
Figure 3-48 1354 RM-PhM target directory window ........................................................................................ 276 276
Figure 3-49 1354 RM-PhM software upgrade phase icons................................................................................ 276 276
Figure 3-50 1354 RM-PhM software upgrade audit confirmation window ....................................................... 277 277
Figure 3-51 1354 RM-PhM software load warning ........................................................................................... 277 277
Figure 3-52 1354 RM-PhM software activate warning...................................................................................... 279 279
Figure 3-53 1354 RM-PhM software upgrade alarm acknowledge window ..................................................... 279 279
Figure 3-54 1354 RM-PhM software commit warning ...................................................................................... 280 280
Figure 3-56 1354 RM-PhM software backout menu ......................................................................................... 283 283
Figure 3-57 1354 RM-PhM software backout warning ..................................................................................... 283 283
Figure 3-59 1354 RM-PhM PSSECX software upgrade menu .......................................................................... 286 286
Figure 3-60 1354 RM-PhM PSSECX software upgrade window ...................................................................... 287 287
Figure 3-61 1354 RM-PhM software upgrade properties window .................................................................... 287 287
Figure 3-62 1354 RM-PhM PSSECX - Add NEs window ............................................................................... 288 288
Figure 3-63 1354 RM-PhM PSSECX target directory window ......................................................................... 289 289
Figure 3-64 1354 RM-PhM PSSECX software upgrade menu .......................................................................... 290 290
Figure 3-65 1354 RM-PhM PSSECX software upgrade window ...................................................................... 291 291
Figure 3-66 1354 RM-PhM PSSECX target directory window ......................................................................... 292 292
Figure 3-67 1354 RM-PhM PSSECX software upgrade phase icons ................................................................ 292 292
Figure 3-68 1354 RM-PhM PSSECX software upgrade audit confirmation window 1 .................................... 293 293
Figure 3-72 1354 RM-PhM PSSECX software load warning ........................................................................... 295 295
Figure 3-73 1354 RM-PhM PSECX software activate warning ........................................................................ 297 297
Figure 3-74 1354 RM-PhM PSSECX software upgrade alarm acknowledge window...................................... 298 298
Figure 3-75 1354 RM-PhM PSSECX software commit warning ...................................................................... 299 299
Figure 3-77 1354 RM-PhM software backout menu ......................................................................................... 301 301
Figure 3-78 1354 RM-PhM software backout warning ..................................................................................... 301 301
Figure 3-80 FileZilla connect to server window ............................................................................................... 303 303
Figure 3-81 FileZilla server window................................................................................................................. 304304
Figure 3-82 FileZilla server Active menu ......................................................................................................... 304 304
Figure 3-83 FileZilla server Active screen ........................................................................................................ 305 305
Figure 3-84 305
Apache ftp server........................................................................................................................... 305
Figure 3-85 306
FileZilla groups menu ................................................................................................................... 306
Figure 3-86 FileZilla groups window................................................................................................................ 306 306
Figure 3-87 FileZilla add group window .......................................................................................................... 307 307
Figure 3-88 FileZilla groups shared folders window ........................................................................................ 308 308
Figure 3-89 FileZilla browse folder window .................................................................................................... 308 308
Figure 3-90 309
FileZilla users menu ...................................................................................................................... 309
Figure 3-91 310
FileZilla users window .................................................................................................................. 310
Figure 3-92 FileZilla add user window ............................................................................................................. 310 310
Figure 3-93 FileZilla users shared folders window ........................................................................................... 311 311
Figure 3-94 FileZilla browse folder window .................................................................................................... 312 312
Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary vi

Contents
List of tables
Table 1 Related documentation ..................................................................................................................... xixi
Table 2 xiii
Software ordering ........................................................................................................................... xiii
Table 3 Supported hardware for 1830 PSS-16/PSS-32 ................................................................................ 16 16
Table 4 Software upgrade path summary for 1830PSS-7.0-2 ................................................................. 164 164
Table 5 Software upgrade path summary for 1830PSSECX-7.0-2*, ..................................................... 169 169
Table 6 Typical software upgrade time interval table for Release 7.0.2 .................................................... 173 173
Table 7 Firmware changes from default to non-default versions in Release 7.0.2 ..................................... 314 314
Table 8 Firmware changes from Release 7.0.1 to Release 7.0.2 ................................................................ 316 316
Table 11 Firmware changes from Release 6.0.6 and 6.0.7 to Release 7.0.2................................................. 326 326
Table 12 Firmware changes from Release 5.1.6 to Release 7.0.2 ............................................................... 330 330
Table 13 Firmware changes from Release 3.6.60 to Release 7.0.2 .............................................................. 335 335
vii Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

Contents
Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary viii

About this document
Purpose
These Customer Release Notes provide information on the Alcatel-Lucent 1830 Photonic
Service Switch (PSS) features, known issues, resolved issues, software installation,
upgrade procedures, and other helpful information.
Reason for reissue

This document is the first issue of the Alcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-
16/PSS-32) Release 7.0.2 Customer Release Notes.
Intended audience
This document is intended for individuals who are responsible for the installation,
acceptance, operations, and maintenance of the Alcatel-Lucent 1830 PSS-16/PSS-32.
How to use this document

Chapter 1, Features
This chapter provides a listing of new features for the current release of Alcatel-Lucent
1830 PSS-16/PSS-32.
Chapter 2, "Issues"
This chapter provides descriptions of known issues in Release 7.0.2 as well as resolved
issues from previous software releases.
Chapter 3, "Software installation and upgrade"
This chapter provides the procedure to install the Alcatel-Lucent 1830 PSS-16/PSS-32
Release 7.0.2 software into a new network element. It also provides procedures to
perform software upgrades to Release 7.0.2.
ix Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

About this document Safety information
Safety information
For your safety, this document contains safety statements. Safety statements are given at
points where risks of damage to personnel, equipment, and operation may exist. Failure
to follow the directions in a safety statement may result in serious consequences.
Conventions used
This guide uses the following typographical conventions:
Appearance Description
emphasis Text that is emphasized
document titles Titles of books or other documents
file or directory names The names of files or directories
graphical user interface text Text that is displayed in a graphical user interface
keyboard keys The name of a key on the keyboard
system input Text that the user types or selects as input to a system
system output Text that a system displays or prints
variable A value or command-line parameter that the user provides
[] Text or a value that is optional
{value1 | value2 } A choice of values or variables from which one value or variable is
{variable1 | variable2 } used
Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary x

About this document Related information
Related information
The following documents provide additional information about the Alcatel-Lucent 1830
PSS-16/PSS-32 and other Alcatel-Lucent 1830 PSS products with which it interworks:
Table 1 Related documentation
Document No. Title Updated

for this
Release
Alcatel-Lucent 1830 Photonic Service Switch (PSS)
8DG-61258-GAAA-TAZZQ Yes
Release 7.0 Safety Guide
8DG-61258- GCAA-TBZZA Release 7.2 Commissioning and Power Balancing Tool (CPB) User Yes
Guide
8DG-61258-GAAA-TCZZA Yes
Release 7.0 User Provisioning Guide
8DG-61259- AAAA-TDZZA Raman Amplifier and Erbium Doped Fiber Amplifier (EDFA) No
Release 6.0 User Guide
8DG-61258-GAAA-TEZZA Yes
Release 7.0 Engineering and Planning Tool User Guide
8DG-61258-GAAA-TFZZA Release 7.0 TL1 Commands and Messages Guide Yes
(Switching Applications)
8DG-61258-GAAA-TGZZA Release 7.0 TL1 Commands and Messages Guide Yes
(Photonic Applications)
8DG-61258-GAAA-THZZA Yes
Release 7.0 CLI Command Guide
8DG-61258-GAAA-TIZZA No
Release 7.0 Key Management Tool (KMT) Installation Guide
Alcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-16/32)
8DG-61258-GAAA-TJZZA Yes
Release 7.0 Installation and System Turn-Up Guide
Alcatel-Lucent 1830 Photonic Service Switch 36 (PSS-36) Release
8DG-61258-GAAA-TKZZA Yes
7.0 Installation and System Turn-Up Guide
Alcatel-Lucent 1830 Photonic Service Switch 64 (PSS-64) Release
8DG-61258-GAAA-TLZZA Yes
7.0 Installation and System Turn-Up Guide
8DG-61258-GAAA-TMZZA Yes
Release 7.0 Maintenance and Trouble-Clearing Guide
8DG-61258-GAAA-TNZZA Yes
Release 7.0 Quick Reference Guide
8DG-61258-GAAA-TPZZA Release 7.0 DCN Planning and Engineering Guide No
(Photonic Applications)
xi Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

About this document
Document No. Title Updated

for this
Release
8DG-61258-GAAA-TQZZA Yes
Release 7.0 Product Information and Planning Guide
8DG-61258-GAAA-TRZZA Release 7.0 DCN Planning and Engineering Guide (Switching Yes
Applications)
8DG-61258-GAAA-TTZZA Yes
Release 7.0 Single TID and TL1 Commands User Guide
8DG-61258-GAAA-TUZZA No
Release 7.0 Key Management Tool (KMT) Administration Guide
8DG-61258-GAAA-TVZZA No
Release 7.0 Key Management Tool (KMT) User Guide
8DG-61258-GAAA-TWZZA Yes
Release 7.0 GMPLS/GMRE Guide
Alcatel-Lucent 1354 RM-PhM Photonic Manager
8DG-61258-GCAA-TXZZA Yes
Release 12.2 EMS Reference Guide
Alcatel-Lucent Smart Compact Ethernet Demarcation Device
8DG-61259-AAAA-TYZZA No
(Smart cEDD) User Guide
8DG-61258-GAAA-TZZZA Yes
Release 7.0 Electronic Documentation Library
Alcatel-Lucent 1830 Photonic Service Switch 4
3KC-13386-AAAA Yes
(PSS-4) Release 7.0.2 Customer Release Notes
Alcatel-Lucent 1830 Photonic Service Switch 16/32
8DG-62933-AAAA Yes
(PSS-16/PSS-32) Release 7.0.2 Customer Release Notes
Alcatel-Lucent 1830 Photonic Service Switch 36/64
3AG-34247-AACA Yes
(PSS-36/PSS-64) Release 7.0.2 Customer Release Notes
Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary xii

About this document Software ordering
Software ordering
The following table summarizes the software ordering information:
Table 2 Software ordering
Ordering No. Description

SWP 1830PSS R7.0.2
Alcatel-Lucent 1830 PSS Release 7.0.2 Software and Customer Release Notes on
DVD.
8DG-62929-AAAA
(Supports 1830 PSS-16/32 without L0 GMPLS functionality. Either the 4 or 16 GB
EC is supported. See note 1 below for the circuit packs that are not supported by this
software load.)
SWP 1830PSSECX R7.0.2
Alcatel-Lucent 1830 PSS Release 7.0.2 Software and Customer Release Notes on
8DG-62931-AAAA DVD.
(Supports 1830 PSS-16/32 including L0 GMPLS. The 16 GB EC is required.)
1. The following circuit packs are not supported by SWP 1830PSS R7.0.2 (8DG-62929-AAAA)
but are supported by SWP 1830PSSECX R7.0.2 (8DG-62931-AAAA).
112SDX11
11OPE8
11QCEX12
WR20-TFM
WTOCM-F
OTDR
MCS8-16
ASWG
A4PSWG
AAR-8A
MSH8-FSM
Online Customer Support (OLCS)

The Online Customer Support (OLCS) web site provides technical support, as wellas
documentation and software ordering.
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
xiii Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

1 Features
Overview
Purpose
This chapter of the Customer Release Notes describes features and enhancements in this
release, a summary of new and enhanced commands, and any additional product changes.
Contents
This chapter contains the following:
Supported hardware 16
New features in Release 7.0.2 25
Features in Release 7.0.1 36
Features in Release 7.0.0 41
Supporting tools 49
Application notes 50
15 Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

Features Supported hardware
Supported hardware
Alcatel-Lucent 1830 Photonic Service Switch (PSS-16/PSS-32) Release 7.0.2 is supported on PSS-16
and PSS-32 shelves.
Table 3 Supported hardware for 1830 PSS-16/PSS-32
Card slots
Apparatus
Description PSS- PSS-16 Comments GMPLS
Code
32
2 Req. (1 w/alarms)
PFDCxx 20A, 30A, 50A, 60A, 70A PFDC50 also supports
x=20,30,50, DC Power Filter- PSS-32 19, 36 N/A power filter variant Yes
60,70 Shelf with input power
monitoring capability
PFDCxxK PSS-16 DC Power Filter

N/A 1, 11 Yes
x=20, 35 Managed (20A, 35A)
Power Distribution Unit - Unit is mounted

PDU1C N/A N/A Yes
ETSI (12 input, 12 outputs) external to the shelf

PDU2C N/A N/A Yes
ANSI (12 input, 12 outputs) external to the shelf
USRPNL User Interface Panel 40 10 1 Req. per main shelf Yes
PF Power Filter 19, 36 1, 11 2 Req. (1 w/ alarms) Yes
FAN Fan Subsystem 37 21 1 Req. Yes

PDU1B N/A N/A Yes
ETSI (4 inputs, 12 outputs) external to the shelf

PDU2 N/A N/A Yes
NAR (2 input, 6 outputs) external to the shelf

PDU2B N/A N/A Yes
NAR (4 input, 12 outputs) external to the shelf
NAR Rear Access (4 inputs, Unit is mounted

PDU2D N/A N.A Yes
4 outputs) - isolated RTNs external to the shelf
Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary 16

Card slots
Apparatus
Code
32
1 Req., 2 for
EC Equipment Controller (4 GB) 1, 18 2, 12 No
redundancy
1 Req., 2 for
redundancy
Equipment Controller (16
EC 1, 18 2, 12 Required for Release Yes
GB)
3.6.1 and Release
3.6.21
4G Dual Port Pluggable 2-17, 3-9,

4DPA4 No
AnyRate (4 clients) 20-35 13-19
4G Dual Port Pluggable 2-17, 3-9,

4DPA2 No
AnyRate (2 clients) 20-35 13-19
11G Single Port Tunable

2-17, 3-9,
11STAR1 AnyRate Transponder (1 Yes
20-35 13-19
client)
11STAR1A 11G Single Port Tunable 2-17, 3-9,

Yes
** AnyRate -Enhanced (1client) 20-35 13-19

11STGE12 GBE Muxponder 2-17 3-9 Yes
(12 Clients)

11STMM10 Multirate Muxponder (10 2-17 3-9 Yes
universal clients)
11G Dual Port Pluggable

11DPE12 2-17 3-9 Yes
GBE Muxponder (12 Clients)

11DPE12E** GbE Muxponder, Enhanced 2-17 3-9 Yes
(12 Clients)

11DPE12A 12xGbE Muxponder 2-17 3-9 Yes
Enhanced (12 Clients)

Card slots
Apparatus
Code
32
24x GbE & 4x

11QPE24 10GbE/OTU2s Ethernet 2-16 3-8 Yes
Muxponder
Please note the known

issues related to
11QPA4 with FEC
11G Quad Port AnyRate (4 type as EFEC2.
11QPA4** 2-17 3-9 Yes
clients) Customers shall use
RS-FEC and EFEC at
11QPA4 line to avoid
the known issues listed.
Please note the known

issues related to
11QPA4A with FEC
11G Quad Port Pluggable
type as EFEC2.
11QPA4A** Anyrate HARDENED (4 2-17 3-9 No
Customers shall use
Clients)
RS-FEC and EFEC at
11QPA4A line to avoid
the known issues listed.
Release 5.1.6 or
onward releases shall
be used for the initial
deployment of
11QPEN4 packs where
11G Quad Port Encryption IBM GDPS
11QPEN4** 2-17* 7-9 certification is not ***
Transponder (4 clients) required. For
supporting application
requiring IBM GDPS
certification, Release
5.1.2 shall be used for
initial deployment.

11DPM12** MultiRate Mux Transponder 2-17 3-9 Yes
(12 Clients)

Card slots
Apparatus
Code
32
8x10GbE/OTU2e High-
11OPE8 ,
Capacity L2 Switching 2-17* 7-9 No
MuxOT
Carrier Ethernet MuxOT,
11QCE12X
4x10GbE/OTU2e Lines, 2-17* 7-9 No
12x1GbE Clients
4x10Gb/s MUX Transponder

Multirate Multiprotocol
43STX4 2-15 N/A No
MUX Tunable Transponder
(4 universal clients)
4x10Gb/s MUX Transponder

Multirate Multiprotocol
43STX4P MUX Tunable Transponder 2-15 N/A Yes
(4 universal clients) with
dPSK at line port

43STA1P Anyrate (1 client) - PDPSK 2-15 N/A Yes
modulation

43STA1PB Anyrate (1 client) - PDPSK 2-15 N/A No
modulation
Release 3.6.0 /1 and

4x10Gb/s Coherent
onward releases shall
Multiprotocal Muxponder
43SCX4 2-15* N/A be used for initial Yes
with Single Tunable Line (4
deployment of the
Clients)
43SCX4 pack

43SCX4E Mux Coherent (4 client), 2 2-16* N/A Yes
Slot

43SCA1 Anyrate Coherent (1 client) 2-15* N/A Yes
A/D
43SCGE1 Single Port Tunable 2-15* N/A No

Coherent GBE Transponder

Card slots
Apparatus
Code
32
(1 client)

112SCA1 Coherent AnyRate 2-15* N/A Yes
Transponder (1 client)

112SCX10 Coherent Mux Transponder 2-15* N/A Yes
(10 clients)

Mux (10 universal clients),
112SNX10 2-15* N/A Yes
Coherent, w/Enhanced
OSNR for extended reach

Coherent AnyRate
112SNA1 Transponder w/enhanced 2-15* N/A Yes
OSNR (1 client) for extended
reach
112G DCI High Capacity

112SDX11 Mux Transponder 2-17* 7-9 No
(11 clients)

130SCX10 Mux (10 universal clients), 2-16* N/A Yes
Coherent, with SD FEC
130SNX10 100G Mux
130SNX10 2-16* N/A Yes
10CL, Flex Coherent
100G SD-FEC Add/ Drop,

Yes for
Flex-Coherent 2-16* NA
Z25 extended shelf 100G mode
(8DG62184AA)
cover (APN=
200G SD-FEC Mux 2CL, 8DG61487AA) is
260SCX2 required to manage No for 200G
Flex Coherent 2-16* NA
client fiber jumper mode
(8DG62185AA)
bend radius on the
100G/200G, SD-FEC Flex 260SCX2. Yes for
2-16* NA 100G
Coherent (8DG62186AA)
No for 200G

Card slots
Apparatus
Code
32
mode
Colorless Wavelength Router

CWR8 2-16 N/A No
(44 channels)
8 Channel Colorless
Wavelength Router
CWR8B 2-16 N/A No
(Supplemental Vendor) (44
channels)
Colorless Wavelength Router Yes (in add/

CWR8-88 2-16 N/A drop block)
(88 channels)
Wavelength Router Card

with Add-Side 9x1 WSS
WR8-88A 2-16 3-8 Yes
supporting 50-GHz channel
spacing
Wavelength Router Card

WR8-88AF 2-16 3-8 Yes
with Flex Grid (88 channels)
Wavelength Router Card 2-16, 3-8,

WR2-88 with Add side Wavelength Yes
20-34 13-18
Selective Switch (2x1)
Twin 1x20 w/ MPO

WR20-TFM 2-16 3-8 No
Connectors
1x4 Mesh Extension Pack

MESH4 2-17 N/A Yes
(external coupler card)
2-17, 3-9,
WTOCM-F Enhanced WT-OCM module No
20-35 13-19
MSH8-FSM Mesh 8-deg Fiber Shuffle NA NA No
MultiCastSwitch 8-deg 16-

MCS8-16 2-17 No
ports
OTDR for fiber

OTDR 2-17 3-9 No
characterization
Amplifier, Switched Gain

ASWG 2-17 3-9 No
EDFA

Card slots
Apparatus
Code
32
Hybrid Amp 4 RP + SG
A4PSWG 2-16* 6/7, 8/9 No
EDFA
AAR-8A Amp Array 8-amps 2-17 No
88 Channel Interleaver Unit is mounted

ITLU N/A N/A Yes
(unidirectional) external to the shelf
Unit is mounted
ITLB 88 Channel Interleaver N/A N/A Yes
external to the shelf
ALPHG Low Power High Gain Amp 2-17 N/A Yes
AHPHG High Power High Gain Amp 2-17 3-9 Yes
AHPLG High Power Low Gain Amp 2-17 3-9 Yes
A2325A 23-dB Variable Gain Amp 2-17 3-9 Yes
RA2P Raman Amplifier, 2 pumps 2-17* 7-9 Yes
+21 dBm output power, 25-

AM2125A dB gain optical amplifier 2-17 3-9 Yes
with mid-stage access
Release 3.6.0/3.6.1 and

+21 dBm output power, 25- onward releases shall
AM2125B dB gain optical amplifier 2-17 3-9 be used for initial Yes
without mid-stage access deployment of
AM2125B.
Low Variable Gain

AM2318A Amplifier, No Mid-Stage 2-17 3-9 Yes
Access
AM2625A 26dBm VGain

AM2625A Uni-amp w/ DCM & LBO 2-16 3-8 Yes
Kit
AM2032A 20dBm VGain

AM2032A 2-17 3-9 Yes
Uni-amp w/ DCM access

Card slots
Apparatus
Code
32
A2P2125 is a two-slot
wide circuit pack
A2P2125 Hybrid Amplifier 2-15* 8 Yes
supported on PSS-16
shelf in slots 8+9
Bidirectional Optical 2-17, 3-9,

OPSA No
Protection Switch 20-35 13-19
Enhanced Optical Protection 2-17, 3-9,

OPSB Switch Card with Non- No
20-35 13-19
Latching Switch
Optical Supervisory Card 2-17, 3-9,

OSCT No
Total Power 20-35 13-19
2-17, 3-9,
SVAC Single Port VOA Card No
20-35 13-19
2-17, 3-9,
MVAC Multiple port VOA card No
20-35 13-19
Bidirectional Multi-port
MVAC8B 2-17 3-9 No
Variable Attenuator Card
Wavelength Tracker optical 2-17, 3-9,

WTOCM Yes
channel monitor 20-35 13-19
WTOCMA is fully
WTOCM supporting OSNR 2-17, 3-9,
WTOCMA supported beginning in Yes
measurements 20-35 13-19
Release 7.0.1.
2-17, 3-9,
SFD5 5 channel static DWDM filter No
20-35 13-19
SFD8 8 channel static DWDM filter 2-17 3-9 No
2-17, 3-9,
SFC2 2 channel static CWDM filter No
20-35 13-19
2-17, 3-9,
SFC4 4 channel static CWDM filter No
20-35 13-19
SFC8 8 channel static CWDM filter 2-17 3-9 No

Card slots
Apparatus
Code
32
40 Channel Optical Unit is mounted

SFD44 N/A N/A No
Mux/Demux external to the shelf

SFD40B N/A N/A No
Mux/Demux -50 GHz Offset external to the shelf

SFD44 N/A N/A Yes
Mux/Demux (even channels) external to the shelf

SFD44B N/A N/A Yes
Mux/Demux (odd channels) external to the shelf
Note:
* To ensure sufficient thermal management, the following cards require high-power fan (FAN32H) to be
used in the 1830 PSS-32 shelf as enforced by the Engineering & Planning Tool (EPT): 260SCX2,
130SCX10, 130SNX10, 112SCA1, 112SNA1, 112SCX10, 112SNX10, 112SDX11, 11QPEN4,
11OPE8, 11QCE12X, 43SCA1, 43SCGE1, 43SCX4, 43SCX4E, RA2P, A2P2125, and A4PSWG.
This note applies to 112SA1L, 112SX10L, and 43SCX4L in the 1830 PSS-32 shelf as a high speed OT
drop shelf configuration.
** It is highly recommended to always use FECTYPE=EFEC or RS-FEC for 11DPM12, 11DPE12E,
11QPA4, 11QPA4A, 11QPEN4 and 11STAR1A.
*** 11QPEN4 is only supported under GMRE control plane as an SpcEndPoint. It cannot be used as a 3R.
Use 11QPA4 for 3R instead.
Release 7.0.2 or a later release must be used for initial deployments of the 112SDX11 pack.
112SDX11 complies to ETSI EN 300 019-1-3 and ANSI Data Center GR-3160-CORE thermal
requirements with the operation temperature of -5 to +45 C (23 to 113 F). 112SDX12 does not
comply to the ANSI CO thermal requirements (GR-63-CORE).
When 11OPE8 cards are used in 1830 PSS-16 shelf, pluggables with extended temperature range
should be used.
EFEC2 is not supported on 11OPE8 and 11QCE12X packs.

Features New features in Release 7.0.2
DRAFT
New features in Release 7.0.2
The following new hardware and software features are supported by Alcatel-Lucent 1830
Photonic Service Switch (PSS) Release 7.0.2. The new features are listed versus the
preceding releases.
New Release 7.0.2 WDM Hardware

Carrier Ethernet xWDM/OTN Integrated 1/100GbE L2 Muxponder (11QCE12X)
11QCE12X is a Carrier Ethernet xWDM/OTN integrated 1/10GbE L2 muxponder card
supported in Release 7.0.2 in 1830 PSS-4, PSS-16 and PSS-32 shelves. 11QCE12X is
designed as a 1-slot version of 11QPE24 and is intended for the same applications. It is
equipped with the latest-generation Ethernet switch device for HW-readiness for future
capabilities. The 11QCE12X supports carrier-grade L2 features aligned with 11QPE24 in
Release 7.0.0. The 11QCE12X is a single-width, full-height card. Characteristics:
10 x 1GbE/FE SFP client ports if 2 eVOA SFPs are used for WT, or 12 x
1GbE/FE client ports if VOA SFP is not used
Future dual-channel Compact SFP (CSFP) to increase client interfaces up to 22
GbE
4 x 10GbE/OTU1e/OTU2e (XFP) flexible client or line ports
Client 10G XFP ports: 10GbE IEEE 802.3 LAN PHY
Network/Line ports: 10GbE IEEE 802.3 LAN PHY or G.709 OTU2e or OTU1e, up to two
ports with WT
Hardware ready to support BITS and 1pps+ToD interfaces
State-of-the-art latest generation L2 Switch ASIC and Controller.
Hardware ready for MPLS-TP, IEEE 1588v2, Control processor alignment with
7210 SAS-X/T/R6
4x 10 Gbit/s Mate Interface to neighbor slot for equipment protection (combined
with MC-LAG and ERP) in 1830 PSS-4 and PSS-32 shelves
Carrier-grade L2 features aligned with 11QPE24 in Release 7.0.2
Support for -40+65C hardened temperature range for outside plant installations -
MEF CE 2.0 certification for all service types: E-Line, E-LAN, E-Tree, E-Access
DRAFT

FlexGrid OCM Card (WTOCM-F)

The WTOCM-F is the next evolution of Wave-Tracker Optical Channel Monitoring,
capable of supporting FlexGrid architecture. Similar to the WTOCM card, WTOCM-F
can report WT and OCM information of every channel supported on standard fixed ITU
50GHz grid. In addition, WTOCM-F is capable of supporting channels that are off the
standard grid, as long as the channels follow the ITU-T recommendation G.694.1. The
WTOCM-F can monitor up to four optical lines via separate optical taps. It utilizes an
OCM component that can operate under fixed grid or FlexGrid. The WTOCM-F is single
width, half height card supported on 1830 PSS-32 and PSS-16 shelves in Release 7.0.2.
Twin 1x20 flex-grid WSS with MPO connectors (WR20-TFM)
The WR20-TFM is composed of two 1x20 WSS modules mounted together. The twin
1x20 WSS is hardware ready and capable of supporting FlexGrid architecture. It can be
provisioned to support standard fixed ITU 50GHz grid, or set to spectrally filter off-grid
following ITU recommendation G.694.1. WR20-TFM supports MPO connectors, for
use with the new MCS and Fiber-Shuffle in the CDC-F configuration. It is supported on
the 1830 PSS-32 shelves in Release 7.0.2.
Amp Array with 8 discrete amps for 4-degrees (AAR-8A)
The AAR-8A is an external amp array that can be used in conjunction with a Multicast
Switch (MCS) to support CDC-F configuration. The AAR-8A consists of 8 amplifiers (4
in the transmit direction, and 4 in the receive direction) and supports up to 4 degrees.
The AAR-8A supports ~15 dB gain and ~ +16dBm output power. The AAR-8A is a
single width, full height card supported in 1830 PSS-32 shelves in Release 7.0.2.
Switched Gain EDFA (ASWG)
The ASWG can operate in 2 modes (low-gain mode and high-gain mode). When in low-
gain mode, the device will support 8-17dB flat gain, with 24dB max gain. When in high-
gain mode, it will support 14-24dB flat gain, with 30dB max extended gain. The output
power of ASWG is ~ 23dBm. This EDFA can support 4800GHz band (that is, 96
channels at 50GHz spacing). This amplifier has OTDR monitoring ports, to be used in
conjunction with the OTDR cards for monitoring and characterization of the outside plant
fiber. The ASWG is supported in 1830 PSS-32 and PSS-16 shelves.
Flexible Grid Multicast-Select switch (MCS8-16)
CDC-F Add/Drop block can be built using Multicast-select switch module with 16
colorless ports for connection to transponder/switchponder modules and 8 aggregation
ports for connection to Flexible grid optical lines. The MCS8-16 is designed to support
connectivity up to 8 degrees, with 16 client ports for transmitting any of the client
services to any of the 8 degrees.

The MCS8-16 can be used in conjunction with the AAR-8A amplification array to
provide the necessary amplification. The MSC8-16 is a single-width, full height card
supported in 1830 PSS-32 shelves in Release 7.0.2.
Meshed Fiber Shuffle (MSH8-FSM)
Passive Fiber Shuffle module (MSH8-FSM) can be used for optimized connectivity
between OTS lines of Flexible Grid contention-less architecture Node and CDC-F
Add/Drop block. The MSH8-FSM is a passive, rack mounted 3-RU pizza box style card
that handles all of the WSS interconnections including the mesh connections,
preconfigured for degree 8 support. There are two ribbon connectors for each dual WSS
card (with up to 8 WSS cards supported to service 8 degrees); each with up to 20 fibers.
One fiber from each ribbon is routed to the LC connectors for expansion, and 7 dedicated
express fibers (per WSS) are interconnected for degree 8 meshed node support. The other
12 fibers are rearranged through the fiber shuffles, such that the ribbon connections to
each MCS card contain 1 fiber pair from each WSS pair. In this variation of the card, up
to 12 Add/Drop multicast switches can be supported. The MSH8-FSM is supported in
Release 7.0.2.
OTDR for fiber characterization and network performance
The OTDR card is an optional photonics card, capable of characterizing fibers out
beyond 100km. This device can be shared amongst up to 4 degrees, monitoring both the
Ingress and Egress direction of each degree. The OTDR is a single width, full height
card that can support up to 8 input fibers to monitor a 4-degree system. The fiber
characterization and monitoring is non-intrusive, i.e. the operation of the OTDR function
does not interfere with transmission of service channels. An optional pack, the OTDR can
be supported only on the A4PSWG and ASWG amplifiers. Legacy amplifiers do not have
the APC taps to work with this card. The OTDR is supported on 1830 PSS-32 and PSS-
16 shelves in Release 7.0.2.
Switched Gain Hybrid Amplifier for ULH (A4PSWG)
The hybrid Raman with Switched Gain EDFA is comprised of a RAM4 module (4 pumps
Raman amplifier module) and a switched gain EDFA component module. The A4PSWG
is designed with optimized ingress performance for both low and high EDFA gain stages.
It is coherent optimized to eliminate mid-stage DCM loss. The A4PSWG supports
WaveTracker detection and supports up to +23dBm output power and 4800GHz
bandwidth (96 channels at 50GHz channel spacing). This amplifier supports OTDR
monitoring taps via Angle Polished Connectors (APC). The A4PSWG is supported in
1830 PSS-32 and PSS-16 shelves in Release 7.0.2.
SFP+ 10GBASE-ER/ OTM-0.2 CWDM SH (APN: 3AL82018AAAA~AHAA)
The 10GBASE-ER/OTM-0.2 CWDM SFP+ 40 km SMF, 1550 nm are introduced in
Release 7.0.2 on 11OPE8. Supported operating temperature range: 5 to +85 C (23 to
185 F).
Integrated Bay
The Alcatel-Lucent 1830 PSS-64 and Alcatel-Lucent 1830 PSS-32 are orderable in
configurations with pre-installed equipment in a bay. This configuration is called
integrated bay. Only cards, fibres and power cables need to be installed.
Core parts of this package are:
14 in deep SNBF rack (ANSI bay)
Air inlet damper
Damper assembly
ANSI HPCFAP cover support
Alcatel-Lucent 1830 PSS-64 subrack
Rear access HPCFAP
Alcatel-Lucent 1830 PSS-64 vertical duct assembly, ANSI
Heat baffle cover
Alcatel-Lucent 1830 PSS-64 main cover
ANSI HPCFAP damper cover
Stile strip assembly
Rack rear cover ANSI
2 Power filter (PSF3T8)
2 Fan tray
Clamp extracting machine LC
SFP removal tool
Alcatel-Lucent 1830 PSS-64 cable kit ANSI
2 GC slot dummy plate
Besides these parts listed, there are sets of brackets, flanges, supports, screws and
washers. For the 1830 PSS-32 CDC-F ROADM configuration, an integrated bay is
supported where only external power cables need to be attached to the (PDU2D) rear
access power distribution unit.
One ANSI, 14 deep, 26 total width, bay frame
One Power Distribution Unit (PDU2D) with four 40A breakers, two per PSS-32 shelf
and toggle handles one per breaker
Two PSS-32 (13) shelf subracks, each with High Capacity Fan/baffle, bumped out
Z25 cover, PFDC30 power filters - two per PSS-32 shelf
One 8RU FLEX container shelf (to hold Fiber Storage Tray(s) and/or MSH8-FSM)
Vertical fiber guide/management parts
Rear Access PDU: Rear Access PDU2D (integrated bay)

A pre-configured integrated 1830 PSS-32 bay comprises a rear access PDU that offers
rear access for the CO power cables.
Raised floor installation kit: (integrated bay)
Raised floor allows routing the power cables via the bottom of the bay. The Integrated
bay raised floor installation kit supports a floor anchor kit that attaches the integrated bay
from the raised floor to the ground floor.
Additional components required for the raised floor application include
Extended rear guardrail and cable retainers
Cable mounting brackets used to secure power cables bay frame upright
Mounting screws
13 PSS-32 Shelf in CDC-F networks: (integrated bay)
The 13 PSS-32 includes horizontal fiber trays that extend out from the front of the shelf,
for better fibering (less bending) to the card faceplates with flush mount pluggables and
MPO connectors. In the CDC-F Network, this shelf will always be paired with a new 14
Installation kit, making its depth 14 so its consistent with the Integrated Bay. This kit
will include the extended/bumped out shelf covers plus extender brackets. This kit has no
ferrites on the power cables (for EMC shielding) and ONLY the Voltage Monitored
Power Filters which have EMC enhancements (AM8 version) will be allowed in the
design of the PSS-32 shelf. This is the only type of PSS-32 shelf that EPT will design in
this release for CDC-F Networks.
13 PSS-32 Shelf in non-CDC-F networks
The 13 PSS-32 includes horizontal fiber trays that extend out from the front of the shelf,
for better fibering (less bending) to the card faceplates with flush mount pluggables and
MPO connectors. 13 PSS-32 fits under the bumped out (Z25) shelf covers. Since
bumped out shelf covers cause the real depth of the shelf to be 13, the 13 shelf will
always be used when the bumped out covers are required on a PSS-32. The 13 PSS-32
shelf will be the EPT default even when conventional shelf covers are requested, but the
12 PSS-32 shelf is a user selectable option.

New Release 7.0.2 WDM Software Features

System
Card sensor based fan control
Release 7.0.2 changes the fan control on the 1830 PSS-32 shelf to utilize the thermal
sensors on the 100G circuit packs (130SCX10, 130SNX10, 112SCA1, 112SCX10,
112SNA1, and 112SNX10) to adjust shelf fan speed for airflow control in addition to the
inlet air temperature. The system will run fans at the lowest speed to guarantee lifetime
performance of all packs in the 1830 PSS-32 shelf. An alarm will be generated if the
required pack operating temperature range cannot be maintained.
Clock out of specification alarm support
Release 7.0 introduced the alarm for PFDC based system clocks that have failed or
drifted out of specification (BADCLKFREQ is raised when the drift is greater than
55PPM) and initiates a switch to the system clock from the other PFDC. If the system
clock drifts marginally out of its specified range (9PPM-55PPM), the system may not be
able to reliably determine which clock is out of specification, so the system will raise an
alarm (SUSPECTCLKFREQ) against both clocks requesting the operator to identify the
failing clock. The operator can then use the new clock switch commands to request that
system uses one clock or the other for system timing. The operator will monitor existing
system alarms to isolate the source of the problem. The first warning of system clock drift
will be missing or unexpected wavekey alarms. These will clear when the system has
switched away from a clock exhibiting oscillator drift. Alcatel-Lucent 1830 PSS-32
detects clock drift on the PFDC, so the system will alarm when the clock drifts. The PSS-
32 supports automatic and manual clock switching for the following cards:
Release 7.0.0: 11STAR1, 11STMM10, 11QPA4, 11DPM12, 11STGE12, 43SCA1,
43SCX4, and 43SCX4E
Release 7.0.1: 11DPE12, AHPHG, AHPLG, A2325A, AM2125A, AM2125B,
AM2318A, AM2625A, AM2032A, CWR8, CWR8-88, WR2-88, WR8-88A, and
WR8-88AF
Release 7.0.2: 11DPE12A, 11DPE12E
Alcatel-Lucent 1830 PSS-16 does not have clock detection in its PFDC, so it will only
alarm and protect against clock failures if one of the following cards are present and have
been upgraded to the latest FPGA FW:
Release 7.0.0: 11STAR1, 11STMM10, 11QPA4, 11DPM12, 11STGE12
Release 7.0.1: 11DPE12, AHPHG, AHPLG, A2325A, AM2125A, AM2125B,
AM2318A, AM2625A, and AM2032A
Release 7.0.2: 11DPE12A, 11DPE12E

In addition to the cards listed above which can detect clock drift in Alcatel-Lucent 1830
PSS-16, PSS-16 will respond to both manual and automatic switching for the following
cards:
Release 7.0.1: 43STA1P, 43STA1PB, 43STX4, 43STX4P, CWR8, CWR8-88, WR2-
88, WR8-88A, and WR8-88AF
Note: All 100G OTs have their own on-board clock and do not use the shelf clock.
Note: The non-default firmware versions shall be used to support the clock out of
specification alarm feature. Refer to Firmware for Release 7.0.2 for details.
Node setup via console (CLI)
Release 7.0.2 supports initial node setup (such as Nodename, TID, IP addresses, etc.) via
CLI with the command config admin commission. Once entered, the user will be asked
several questions to initialize the setup parameters.
Electro-Optics
Latency Measurements on 100GE / 10x10G OTU2
Release 7.0.2 introduces the capability enabling operators to query real-time path delays
for line side HO-ODU4 paths for 260SCX2, 130SCX10 and 130SNX10. The feature is
based on the delay measurement as defined by G.709 which includes both fiber and FEC
processing delay.
Note: The non-default firmware versions (Profile 2.2.1 for 130SCX10 and Profile 1.3.1
for 130SNX10) shall be used to support the latency measurement feature. 260SCX2
supports the latency measurement feature in the default profile. Refer to Firmware for
Release 7.0.2 for details.
Release 7.0.2 supports the 11DPM12 cascade over 40G (43SCX4, 43SCX4E) or 100G
(130SCX10) and using GCC1 for nodal communication, which allows for extended
management connectivity.
Support of OTU-2/1f client interfaces on 112SDX11
The cascade of 11DPM12 with 112SDX11 in OTU2 mode is supported
Support of TCA for encrypted services over 11QPEN4
Support for zero chirped 10-Gbit/s DWDM XFP on 11DPM12
The zero chirped 10-Gbit/s DWDM XFPs (APN: 1AB394040003) is supported on
11DPM12
The following features are included in the Release 7.0 documentation. These features are not
supported in Release 7.0.2 but will be available in a future release.
112SDX11: 2 x 40GbE (SR4) client interface support over 4 x SFP+ via fan out
cable.
112SDX11: 100GbE (SR10) client interface support over 10 x SFP+ via fan-out cable

112SDX11: ISL trunking support on FC ports (up to 8 ports for 4/8/16 G FC)
Photonics
The Any-Color, Any-Direction, and Non-contention (CDC-F) configuration is comprised
of twin 1x20 WSS and MCS8-16 where the twin 1x20 WSS resides at the optical line,
enabling Route & Select architecture is supported in Release 7.0.2.
Additional combinations of Amplifiers support with AM2625A
Release 7.0.2 supports an expanded set of allowable amplifiers to be used in the Egress
and Ingress direction of a ROADM network element. In particular, the AM2625A, which
is normally used as an Egress amplifier, can now be supported in conjunction with the
following unidirectional amplifier combinations in the Ingress direction:
AM2125A
AM2125B
RA2P + AM2125A
RA2P + AM2125B
DGE Node support for CDC ROADM
Release 7.0.2 supports an interim DGE solution that is comprised of a single PSS32 shelf,
requisite amplifiers, and two WR20-TFM modules. The two WR20-TFM modules are
fibered together via two MPO fiber jumpers, directly connecting the ADD1 to DROP1
ports of the WR20-TFM modules.
11DPM12 cascade over coherent OT, using GCC1 for nodal communication
Release 7.0.2 supports the cascade of 11DPM12 over the 43SCX4E, or over the
130SCX10. By carrying the management traffic over the GCC1, it is possible to manage
the remote NE over very long span distances where the OSC reach could not be
supported.
Fault Detection During Commissioning of CDC ROADM
Release 7.0.2 supports fault detection during commissioning of the CDC ROADM
network element. During the initial commissioning, there are fiber connections that need
to be made, in particular the connections between the WR20-TFM and the MSH8-FSM,
which make use of the MPO fiber jumpers. The MPO fiber jumpers contain many
individual fibers that are inaccessible to the operators. Starting with Release 7.0.2, 1830
PSS supports an external PC-based tool that assists operators with bringing up the
ROADM NE. The tool helps to determine at the onset whether there are cabling issues
(faulty connectors, jumpers or ports in the MSH8-FSM, WR20-TFM, or AAR-8A).

Packet
The following are the Packet features in WDM Release 7.0.2:
Full support for mate interface on 11OPE8 card
Support for Carrier Ethernet xWDM/OTN integrated 1/10 GbE L2 muxponder
(11QCE12X)
IEEE 802.1AX LAG and MC-LAG across cards with LACP for card redundancy through
mate interface is supported on 11QCE12X cards in Release 7.0.2 in 1830 PSS-4 and PSS-
32 shelves
The new packet software features supported on 11QCE12X are the same as on 11QPE24
Release 7.0.0 (see description in Release 7.0.0 Customer Release Notes for QoS
enhancement (L3/4 classification, L1/2 policing mode), G.8021 compliant fault
management for Ethernet OAM, Multi-ring ERP Mode w/ R-APS virtual channel, ETSI
mode for TCA, L2 alarm severity setting, cascading with 11QPEN4 and 100G OTs) with
the addition of two new features in Release 7.0.2 described below:
100 ms period for ITU-T Y.1731 pro-active SLM and FLR accuracy improvement:
Since Release 5.1, ETH-SLM (Ethernet Synthetic Loss Measurement Function)
defined in ITU-T Y.1731 and MEF17/35 is available on Up MEPs to measure frame-
loss of an Ethernet service (EVC). Pro-active ETH-SLM was added in R6.0 with
associated FLR SLA performance monitoring counters. This OAM function uses OAM
PDUs called SLM (transmitted by Source MEP) and SLR (replied by Destination
MEP). At the source MEP, the SLM PDU transmission period is configurable as per
MEF35 [R76]. Periods supported are 1 s (default) or 10 s.
SLM frame size is also configurable, compliant to MEF35 [R78].
Starting in R7.0.2, SLM frame rate is improved with the option for SLM PDU
transmission period of 100 ms. Configurable range is now {100 ms, 1 sec, 10 s}. This
allows improving the accuracy of FLR measured via SLM and fully complies with
MEF35 [R77].
Note that the default remains 1s, compliant with MEF35 [D30], keeping same default
on all cards and avoid upgrade problems.
This is implemented only on 11OPE8 and 11QCE12X.
ETH-DM Frame Size Configuration:
Since Release 5.1, ETH-DM (Ethernet Delay Measurement Function) defined in ITU-
T Y.1731 and MEF17/35 is available on Up MEPs to measure two-way frame delay
and one-way frame delay variation of an Ethernet service (EVC). Pro-active ETH-DM
was added in R6.0 with associated FD/FDV SLA performance monitoring counters.
This OAM function uses OAM PDUs called DMM (transmitted by Source MEP) and

DMR (replied by Destination MEP). The DMM PDU transmission period is

configurable as per MEF35 [R61]. Periods supported are 1 s (default) or 10 s.
In order to measure latency for different frame sizes, the option to configure the DMM
frame size is added in R7.0.2. The DMM frame size is now configurable up to the 9.6k
bytes (which corresponds to the MTU), compliant with MEF 35 [R63], [R64] and
[D23]. This is done by configuring the "size", that is, size of the data portion of the
data TLV added to the frame.
This is implemented on all SROS cards 11QPE24, 11OPE8 and 11QCE12X.
All the SFP and XFPs supported on 11QPE24 are supported on 11QCE12X. This
includes the new XFPs introduced in R7.0.0 on 11QPE24 which are as follows:
100GHz fixed DWDM XFPs (40km, 16 channels) (APNs: 1AB422360001~16).
Note, The APNs of the 40kM DWDM 10G XFP (1AB422360001 ~ 1AB422360016)
will be changed to 3AL82001AAAA ~3AL82001ARAA in the future.
Zero chirped 10 Gb/s DWDM XFPs (APN: 1AB394040003) for enhanced reach
The latency of 11QCE12X in 1830 PSS-32, PSS-16 and PSS-4 shelves can be
optimized via disabling FEC. This requires the utilization of the T-XFP (APN:
1AB375650047) supporting error free performance in NO FEC mode for 10GbE
client (CBR mapping) at 11.096 Gbit/s.
Note: Users shall ensure that the XFP port is equipped with a low-latency/No- FEC
XFP (APN: 1AB375650047) when disabling FEC on that port. The software will not
check nor raise a warning message. The FEC disabling option is available for any
XFP but error-free transmission may not be guaranteed.
TSOP Smart SFPs: A new category of Smart SFP is introduced in Release 7.0.0 on
11QPE24 and Release 7.0.2 on 11QCE12X: TSoP Smart SFP module allows
operators to make a graceful transition from SONET/SDH to PSN.
TSoP protocol (Transparent SONET/SDH over Packet) is a new technology defined
in IETF (http://www.ietf.org/id/draft-manhoudt-pwe3-tsop-05.txt) that converts
SONET/SDH traffic into a packet stream while being fully transparent to payload,
overhead bytes (FM, protection, DCC, synchronization). An operator that has a
majority of Ethernet traffic compared to SONET/SDH traffic, can now transport
SONET or SDH traffic across a packet network or Packet over OTN/WDM network
by simply plugging TSoP Smart SFP into Ethernet cards instead of using a separate
TDM transponder and consuming an extra wavelength. This provides a simpler
CAPEX and OPEX-optimized backhaul for mix of STM-1/4 and Ethernet services.
The TSoP Smart SFPs support on 11QCE12X in Release 7.0.2 exists in different
versions in terms of rate and reach: STM-1/OC-3 (APNs: 1AB407440021 for S-1.1,
1AB407440022 for L-1.1) and STM-4/OC-12 (APNs: 1AB407440024 for S-4.1,
1AB407440025 for L-4.1), industrial temperature-range.

The support of the SFP comes along with full set of fault management and
performance monitoring function for the ToSP CES Interworking Function and
remains plug & play for commissioning.
Release 7.0.2 GMPLS Enhancements

Support of interoperability among the 100G OTs as follows:
Support of asymmetrical modules when photonic and electrical compatibility exists
Support of best matching FEC and encoding type
The OPSA (as O-SNCP and O-PRC) will be supported with following:
config D'' and config D' are supported
colored OTs only
coherent 100G OTs only
protected services requires 2 different AD-groups
No mix of AD-group types are supported (for example no mix of config D'' for main
leg and config D' for spare leg)
In case of config D', both AD-groups for main/work and spare/protect legs must be in
the same TOADM NE
Only symmetrical main and spare association at both ends of the protection trail
supported. That is, OPSA main port on one side cannot be connected to OPSA spare
port on the other side.

Features Features in Release 7.0.1
Features in Release 7.0.1

The following new hardware and software features are supported by Alcatel-Lucent 1830 Photonic
Service Switch (PSS) Release 7.0.1. The new features are listed versus the preceding releases.
New Release 7.0.1 WDM Hardware

The following new WDM (1830 PSS-16 and 1830 PSS-32) hardware features are supported by
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0.1.
100G High Capacity Multiprotocol Muxponder (112SDX11)
The 112SDX11 is a high-capacity multiprotocol Muxponder optimized for low latency,
high-capacity transport of Ethernet and other data center traffic over MAN distances. The
112SDX11 can multiplex up to ten 10 GbE clients through SFP+ and support 40 GbE
(SR4 & LR4) clients through QSFP+. The 112SDX11 supports 4/8/10/16 FC and IB
DDR over SFP+. The 112SDX11 also supports ODU2e client interfaces. These
interfaces are multiplexed on the line side via tunable 4x28Gb/s ODB CFP with 50GHz
spacing for FOADM application in Release 7.0.1. The 112SDX11 is hardware ready to
support a tunable 50GHz spacing Coherent line CFP (PDM-QPSK) for ROADM
compatibility, reach extension to regional and DCU free operation. The 112SDX11 is
also hardware ready to support embedded Encryption (AES256) per client selectable
and/or on ODU4 payload. The 112SDX11 is suitable for disaster recovery, business
continuity, and mission-critical applications, as well as low-latency applications for
banking, finance, and high-performance computing involving Ethernet transport over
MAN. The 112SDX11 is a single-width full-height circuit pack supported on 1830 PSS-
4, PSS-16 and PSS-32 shelf with the operation temperature of -5 to +45 C (23 to 113
F).
Carrier Ethernet xWDM/OTN Integrated 10GbE L2 Muxponder (Carrier Ethernet
xWDM/OTN Integrated 10GbE L2 Muxponder (11OPE8)
The 11OPE8 is a carrier Ethernet xWDM/OTN integrated 8x10GbE L2 Muxponder
supporting high capacity, scalable 10GbE/OTU2e Ethernet aggregation with protection
options. It is intended to be used either as an access card or as, typically used in pair, to
close at the head-end packet rings of 11QPE24 and 11QCE12X. The 11OPE8 is a single
slot wide, full-height card with eight 10G optical client/line ports and four eVOA line
ports. The 11OPE8 is supported on 1830 PSS-4, PSS-16 and PSS-32 shelves and is MEF
CE 2.0 certified.

Characteristics:
8 x 10G Flexible Client or Line ports (individually configurable)
4 x 10GbE/OTU1e/OTU2e (XFP), 2 x 10GbE/OTU2e (SFP+), 2 x 10GbE (SFP+)
4 eVOA SFPs
Hardware ready with 1pps+ToD interface
State-of-the-art latest generation L2 Switch ASIC and Controller
120Gbit/s effective switching capacity
40 Gbit/s Mate Interface to neighbor slot for equipment protection (combined
with MC-LAG & ERP) in PSS-32 shelves (refer to Issue #PSSKPL-104)
Hardware ready for MPLS-TP, IEEE 1588v2 in a future release, Control
processor alignment with 7210 SAS-R6
Carrier-grade L2 features aligned with 11QPE24 in Release 7.0.0
New Release 7.0.1 pluggables
The 100GBASE-LR4 dual rate (100GbE/OTU4) CFP2 module (APN=3AL81820AAAA)
The dual rate 100BASE-LR4 (flat top) CFP2 is introduced in Release 7.0.1 to support
100GbE and OTU4 clients on 1AN100G in 1830 PSS-36 and PSS-64 shelves. The OCS
software support for OTU4 operation mode on 1AN100G is planned in a future release.
100GBASE-SR10 (APN: 1AB426470002)
The single rate 10GBASE-SR10 (flat top) CFP2 is introduced in R7.0.1 to support short
reach 100GbE client on 260SCX2 card over MMF ribbon cable, operating distance
100/150 meters
40GBASE-SR4 QSFP+ (APN: 1AB392040001)
The single rate 40GBASE-SR4 QSFP+ is introduced in Release 7.0.1 to support short
reach 40GbE client on 112SDX11 over MMF ribbon cable, operating distance 100/150
meters
40GBASE-LR4 QSFP+ (APN: 1AB392040002)
The 40GBASE-LR4 QSFP+ is introduced in Release 7.0.1 to support 40GbE client on
112SDX11 over 10km SMF links.
CFP 4x28G Tunable DWDM ODB (with flat top)
The 4x28G tunable DWDM ODB CFP (APN=1AB402160016) is supported on
112SDX11 in Release 7.0.1
SFP+ 10GBASE-LR LW_1200-SM-LL-L (APN: 1AB390930002)
The 10GBASE-LR LW_1200-SM-LL-L (10km, Single-Mode, 1310nm) SFP+ is
introduced in Release 7.0.1 to support 11OPE8 and 112SDX11 with the operating
temperature of 5 degree C to +85 degree C.

SFP+ 10GBASE-SR-SW_1200-MX-SN-I (APN: 1AB390930004)

The 10GBASE-SR-SW_1200-MX-SN-I (<500m, Multi-mode, 850nm) SFP+ is
introduced in Release 7.0.1 to support 11OPE8 and 112SDX11 with the operating
temperature of 5 degree C to +85 degree C.
SFP+ 2FC/4FC/8FC SM-LC-L Infiniband SDR/DDR 1xLX (APN: 1AB390930007)
The 2FC/4FC/8FC SM-LC-L Infiniband SDR/DDR 1xLX SFP+ is introduced in Release
7.0.1 to support FC/infiniband client on 112SDX11 over 10km SMFF, 1310nm, with the
operating temperature of 5 degree C to +85 degree C.
SFP+ 4/8/16G FC SM-LC-L (APN: 1AB390930009)
The 4/8/16G FC SM-LC-L SFP+ is introduced in Release 7.0.1 to support
4.25GFC/8.5GFC/16GFC client on 112SDX11 over 10km SMF, 1310nm, with the
SFP+ 4/8/16G FC MX-SN-I (APN: 1AB390930010)
The 4/8/16G FC MX-SN-I SFP+ is introduced in Release 7.0.1 to support
4.25GFC/8.5GFC/16GFC on 112SDX11 over MMF link, <500m, 850nm, with the
SFP+ P1I1-2D1/SR1/10GBASE-LR/W/10xFC (APN: 1AB390930013)
The 10GBASE-LR(W) - 10G FC - OTM-0.2/e/f (P1I1-2D1) SFP+ is introduced in
Release 7.0.1 to support clients on 112SDX11 and 11OPE8 over 2/10Km, SMF, 1310nm,
with the operating temperature of 5 degree C to +85 degree C.
SFP+ P1S1-2D2b/IR-2/10GBASE-ER(W) (APN: 1AB390930014)
The 10GBASE-ER(W) - OTM-0.2/e/f (P1S1-2D2b) SFP+ is introduced in Release 7.0.1
to support 10GbE/OTM-0.2 on 11OPE8 over 40km SMF links, 1550nm, with the

Release 7.0.1 WDM Software Features
Systems
1830 PSS WDM network element (PSS-16 and PSS-32) WebUI supports the Internet
Explorer 11 in Release 7.0.1.
Synchronization
Clock out of specification alarm support
Release 7.0.0 introduced the alarm for PFDC based system clocks that have failed or drifted out of
specification (BADCLKFREQ is raised when the drift is greater than 55PPM) and switch to the system
clock from the other PFDC. If the system clock drifts marginally out of its specified range (9PPM-
55PPM), the system may not be able to reliably determine which clock is out of specification, so the
system will raise an alarm (SUSPECTCLKFREQ) against both clocks requesting the operator identify the
failing clock. The operator can then use the new clock switch commands to request that system uses one
clock or the other for system timing. The operator will monitor existing system alarms to isolate the
source of the problem. The first warning of system clock drift will be missing or unexpected wavekey
alarms. These will clear when the system has switched away from a clock exhibiting oscillator drift.
Alcatel-Lucent 1830 PSS-32 detects clock drift on the PFDC, so the system will alarm when the clock
drifts. The PSS-32 supports automatic and manual clock switching for the following cards:
Release 7.0.0:
11STAR1, 11STMM10, 11QPA4, 11DPM12, 11STGE12, 43SCA1, 43SCX4, and
43SCX4E
Release 7.0.1:
11DPE12, AHPHG, AHPLG, A2325A, AM2125A, AM2125B, AM2318A,
AM2625A, AM2032A, CWR8, CWR8-88, WR2-88, WR8-88A, and WR8-88AF
Alcatel-Lucent 1830 PSS-16 does not have clock detection in its PFDC so it will only alarm and protect
against clock failures if one of the following cards are present and have been upgraded to the latest FPGA
FW.
Release 7.0.0
11STAR1, 11STMM10, 11QPA4, 11DPM12, 11STGE12
Release 7.0.1
11DPE12, AHPHG, AHPLG, A2325A, AM2125A, AM2125B, AM2318A,
AM2625A, and AM2032A

In addition to the cards listed above which can detect clock drift in 1830 PSS-16. The PSS-
16 will respond to both manual and automatic switching for the following cards:
Release 7.0.1
43STA1P, 43STA1PB, 43STX4, 43STX4P, CWR8, CWR8-88, WR2-88, WR8-88A,
and WR8-88AF
Note, all 100G OTs have their own on-board clock and do not use the shelf clock.
Electro-Optics
The 260G mode support on 260SCX2 (SD-FEC Flex-Coherent Add/Drop and
Muxponder) is introduced in Release 7.0.1.
The 260SCX2 is a coherent Add/Drop and Muxponder Flex-Grid ready OT supporting
100 Gbit/s single carrier transmission using DP-QPSK and 200 Gbit/s single carrier
transmission using DP-16QAM in a single card. The 260SCX2 card is commercialized
in Release 7.0.0 with hardware capable of supporting two modes of operation: 130G
mode and 260G mode. In the 260G mode, either one or two 100GbE clients are
aggregated onto a single DP-16QAM carrier and transported on the DWDM line for
metro/regional applications. The 260SCX2 supports OCH protection using OPSA and
client side OPSB protection of either one or both 100G CFP2 client ports.
The on-demand latency measurement on 112SDX11 is supported in 1830 PSS-16 and
PSS-32 Release 7.0.1. Operators can initiate query to measure path latency using HO
ODUk hardware timestamping and the results can be retrieved via management system
and user interface.
Interworking between 11STAR1 and 11QPA4 is supported in Release 7.0.1
Packet
The new packet software features supported on 11OPE8 are the same as on 11QPE24 Release 7.0.0.
Control Plane Enhancements

Layer 0 (L0) GMPLS control plane support for AM2625A and AM2032A is introduced in Release 7.0.1.

Features in Release 7.0.0

The following new hardware and software features were introduced in Alcatel-Lucent 1830 Photonic
Service Switch (PSS) Release 7.0.0. The new features are listed versus the preceding releases.
R7.0.0 WDM hardware features
The following WDM (1830 PSS-16 and 1830 PSS-32) hardware features were introduced in
260SCX2 SD-FEC Flex-Coherent Add/Drop and Muxponder: The 260SCX2 is a
coherent Add/Drop and Muxponder Flex-Grid ready OT supporting 100 Gbit/s single
carrier transmission using DP-QPSK and 200 Gbit/s single carrier transmission using DP-
16QAM in a single card. The 260SCX2 is hardware capable of supporting two modes of
operation: 130G mode and 260G mode. The 260SCX2 is a 2-slot width, full height card
supported in 1830 PSS-32 shelves. The 260SCX2 is factory tested for both 130G mode
and 260G mode, but NE software support for 260G mode is not certified until a future
release.
AM2625A: The AM2625A is a unidirectional optical amplification and transmission
pack. It can be configured for egress or ILA applications. The AM2625A is a two-slot
width, full height card supported in 1830 PSS-32 and PSS-16 shelves.
AM2032A: The AM2032A is a unidirectional optical amplification and transmission
pack. It can be configured for egress or ILA applications. The AM2032A is a single-slot
width, full height card supported in 1830 PSS-32 and PSS-16 shelves.
Bidirectional amplifiers variants with OSC SFPs extruded on the faceplate: New variants
of the A2325A (APN= 8DG60242AB), AHPHG (APN= 8DG59245AB), and AHPLG
(APN= 8DG59945AB) are introduced to support OSC SFP on the faceplate allowing the
replacement of the OSC SFP without extracting amplifiers. The new hardware variants
are functionally identical to the legacy versions of the hardware and support the same
transmission performance for C-band channels. The new hardware variants are single-
slot width, full-height cards (with the same mechanical dimension as the legacy version)
supported in 1830 PSS-32, PSS-16 and PSS-4 shelves.
New pluggable modules
100GBASE-LR4 CFP2 (APN= 1AB426470001)
The single rate 100GBASE-LR4 (flat top) CFP2 with DDM is introduced to support 100-
GbE client on 260SCX2

New 100GBASE-LR4 CFP (APN= 1AB402160018)

The single rate 100GBASE-LR4 CFP variant is introduced on 112SCA1 and 112SNA1
with improved worst case power consumption with respect to 1AB402160012
Support for TSOP Smart SFP on 11QPE24
In release R6.0, the concept of Smart SFP, that integrates intelligent and innovative
system functions into an SFP module, was introduced starting with a L2
OAM/demarcation Smart SFP.
A new category of Smart SFP is introduced in Release 7.0.0: TSoP Smart SFP module
allows operators to make a graceful transition from SONET/SDH to PSN.
The TSoP protocol (Transparent SONET/SDH over Packet) is a new technology defined
overhead bytes (FM, protection, DCC, synchronization). An operator that has a majority
of Ethernet traffic compared to SONET/SDH traffic, can now transport SONET or SDH
traffic across a packet network or Packet over OTN/WDM network by simply plugging
TSoP Smart SFP into Ethernet cards instead of using a separate TDM transponder and
consuming an extra wavelength. This provides a simpler CAPEX and OPEX-optimized
backhaul for mix of STM-1/4 and Ethernet services.
The TSoP Smart SFPs are supported on 11QPE24 in Release 7.0.0. They exist in
different versions in terms of rate and reach: STM-1/OC-3 (APNs = 1AB407440021 for
S-1.1, 1AB407440022 for L-1.1) and STM-4/OC-12 (APNs = 1AB407440024 for S-4.1,
The support of the SFP comes along with full set of fault management and performance
monitoring function for the ToSP CES Interworking Function and remains plug & play
for commissioning.
STM-1e electrical SFP on 11DPM12
The STM-1e electrical SFP (APN=1AK05176AAAA) is introduced and supported on
11DPM12 client port
Support for 100GHz fixed DWDM XFP (40km, 16 channels)
The 100GHz fixed DWDM XFPs (40km, 16 channels) (APNs= 1AB422360001~16) are
supported on 11DPE12A, 11DPE12E, 11DPM4M, 11DPM12, 11QPA4 and 11QPA4A in
Release 7.0.0
Support for zero chirped 10-Gbit/s DWDM XFP on 11DPE12A/11QPE24
The zero chirped 10-Gbit/s DWDM XFPs (APN= 1AB394040003) is supported on
11DPE12A and 11QPE24

R7.0.0 WDM software features

The following WDM (1830 PSS-16 and 1830 PSS-32) software features were introduced in
Security
Collection of time-specific log: 1830 PSS-16 and PSS-32 support the ability to accept a
time window for log collection, which allows the NMS users to send a query specifying
the time window for log collection. The NE will respond back with log entries that fall
within that time window.
Separation of roles between Admin and Crypto officer: The network and 1354 RM-PHM
support the separation of the roles between Admin and the Crypto officer. The Crypto
officer will administer entering and exiting encryption modes and management of
encryption keys. The actions associated with a crypto officer (enabling encryption,
collecting security logs, reviewing encryption status, etc) are separate and excluded from
that of the standard network element/PhM node administrator role.
AES256 algorithm for SNMPv3 in the Network Element: The AES256 version of
SNMPv3 is supported in 1830 PSS network element (1830 PSS-32/PSS-16/PSS-4).
Privacy key is used to encrypt the PDU payload in SNMP v3 messages. It is based on
Symmetric Encryption Protocol, Cipher Feedback Mode of block size 128 bits and 14
rounds for AES-256 (CFB128-AES-256).
IB 5G (DDR) support on 11QPEN4: The IB DDR (5-Gb/s) interface is supported on
11QPEN4 for IBM Z-system backhauling.
Electro-Optics
The 260SCX2 supports two modes of operation (1) 130G mode and (2) 260G mode.
For 130G mode, the transmission of one 100 GbE client signal is supported on the
DWDM line interface for ULH application. The 100 GbE client signal is mapped into an
OTU-4, and either SDFEC or AFEC can be provisioned. The line rate is then 130Gbit/s
(for SDFEC) or 112 Gbit/s (for AFEC).
For 260G mode, the transmission of up to two 100 GbE client signals are transported on
one DWDM line interface for metro/regional application. Each 100 GbE client signal is
mapped into an OTU4. The two OTU-4 signals are then combined to form a 260 Gbit/s
carrier at the interface. The 260SCX2 is factory tested for both 130G mode and 260G
mode, but NE software support for 260G mode is not certified until a future release.

The 260SCX2 supports full C-Band tunable transmitter with integrated WaveTrackerTM
and FlexGrid capability. The 260SCX2 supports OCH protection using OPSA and client
side OPS protection via OPSB. 100G interworking between 260SCX2 and 112SCA1
using 100G AFEC is supported.
TCM support on ODUk structures within 11QPA4: 1830 PSS-32, PSS-16 and PSS-4
supports up to 3 configurable TCM ODUkT or ODUkT-NIM functions per ODUk. Users
can configure any 3 out of 6 TCM layers. The TCM support includes the related fault
and performance monitoring.
The single rate 100GBASE-LR4 (flat top) LR4 CFP2 (APN= 1AB426470001) with
DDM is introduced to support 100-GbE client on 260SCX2.
The single rate 100GBASE-LR4 CFP variant (APN= 1AB402160018) is introduced on
112SCA1 and 112SNA1 with improved worst case power consumption with respect to
1AB402160012
STM-1e electrical SFP is supported on 11DPM12 client port with SDH DCC
transparency. The interoperability between STM-1 electrical client and STM-1 optical
client is supported.
Full support on 100GHz fixed DWDM XFP (40km, 16 channels): The full software
support of 100GHz fixed DWDM XFPs (40km, 16 channels) (APN = AB422360001~16)
are introduced on 11DPE12A, 11DPE12E, 11DPM4M, 11DPM12, 11QPA4 and
11QPA4A in Release 7.0.0
The latency of 11QPA4, 11QPEN4 and 11QPE24 in 1830 PSS-32 and PSS-16 shelves
can be optimized via the use of T-XFP (APN=1AB375650047) supporting error free
performance in NO FEC mode for 10GbE client (CBR mapping) at 11.096 Gb/s and
10GFC (CBR mapping) at 11.27 Gb/s
The on-demand latency measurement on 11QPA4 is supported in 1830 PSS-4, PSS-16
and PSS-32 shelves. Operators can initiate query to measure path latency from ODU2p
(Path layer) for ODU terminated port to test the round-trip delay over bidirectional traffic
and the results can be retrieved via management system and user interface.
The client-side OPS protection is supported for 260SCX2, 112SCA1 and 112SNA1 in
1830 PSS-32 shelves using OPSB, where a single client interface is connected to dual
cards either in the same shelf, different shelves of the same network element, or different
collocated network elements.
Optical Power TCAs and History Bins on ports with CFP/CFP2 modules are supported
on 260SCX2, 112SCA1, 112SNA1 in 1830 PSS-32 shelves. The network element
supports optical power monitoring on ports implemented with CFP/CFP2 modules. The
OPR and OPT parameters monitor the total optical power across multiple wavelengths
generated by CFP/CFP2 modules. The 15-min and 24-hour bins as well as OPR-L/H and
OPT-L/H threshold processing are supported. The CFP/CFP2 modules that do not
support OPR/OPT monitoring will be indicated by having the PM Status field set to N/A.
Test signal generation is supported on 260SCX2, 130SCX10, 130SNX10, 112SCA1,

112SCX10, 112SNA1 and 112SNX10 in 1830 PSS-32 shelves. The circuit pack
generates a test signal to test the DWDM route in helping new service turn-up and fault
isolation
Photonics
The AM2625A can support output power up to +26dBm and 16~25dB gain, with tilt
adjustable over range -1.0 to -6.0dB. The AM2625A can support ultra long haul
transmission up to 1x44dB without requiring Raman.
The AM2032A can support output power up to +20dBm and 26 ~32dB gain range with
tilt adjustable over range 0 ~ -3dB. The AM2032A can support at least 6x35dB spans for
long-haul application.
Packet
Quality of Service enhancements are supported on 11QPE24 in 1830 PSS-32, PSS-16
and PSS-4 shelves
Enhancements to the SAP ingress QoS classification criterias already supported
(IEEE 802.1 p-bits/PCP, MAC SA/DA, Ethertype, IPv4 and IPv6 DSCP. The new
criterias introduced in Release 7.0.0 are: IPv4/v6 Source Address & Destination
Address (incl. Mask), IPv4 protocol, IPv6 Next Header, TCP/UDP source &
destination port
L1/L2 option for meter/policing/shaping, allowing to chose between L2 MAC frame
rate or L1 LAN frame rate for policing/shaping
The zero-chirped 10-Gb/s DWDM Tunable XFP (APN=1AB394040003) is supported on
11DPE12A and 11QPE24 in 1830 PSS-32, PSS-16 and PSS-4 shelves.
Support for TSOP Smart SFP on 11QPE24
In release R6.0, the concept of Smart SFP, that integrates intelligent and innovative
system functions into an SFP module, was introduced starting with a L2
OAM/demarcation Smart SFP. A new category of Smart SFP is introduced in Release
7.0.0: TSoP Smart SFP module allows operators to make a graceful transition from
SONET/SDH to PSN.
The TSoP protocol (Transparent SONET/SDH over Packet) is a new technology defined
overhead bytes (FM, protection, DCC, synchronization). An operator that has a majority
of Ethernet traffic compared to SONET/SDH traffic, can now transport SONET or SDH
traffic across a packet network or Packet over OTN/WDM network by simply plugging
TSoP Smart SFP into Ethernet cards instead of using a separate TDM transponder and
consuming an extra wavelength. This provides a simpler CAPEX and OPEX-optimized
backhaul for mix of STM-1/4 and Ethernet services.

The TSoP Smart SFPs are supported on 11QPE24 in Release 7.0.0. They exist in
different versions in terms of rate and reach: STM-1/OC-3 (APNs = 1AB407440021 for
S-1.1, 1AB407440022 for L-1.1) and STM-4/OC-12 (APNs = 1AB407440024 for S-4.1,
The support of the SFP comes along with full set of fault management and performance
monitoring function for the ToSP CES Interworking Function and remains plug & play
for commissioning.
The interworking between 11QPE24 and 7750 SR in head-end has been tested for both
UNI and NNI L2 interworking, managed under 5620 SAM.
New cascading configurations for packet cards are supported in Release 7.0.0. The
network element and management system provide OCh trail management through a
cascaded configuration..
The 11DPE12E line port is connected to a 130SCX10 client port. Up to 10x10G
line ports from the same or different 11DPE12E OTs may be connected to one
130SCX10.
The 11QPE24 line port is connected to a 112SCX10 or 112SNX10 client port. Up
to 10x10G line ports from the same or different 11QPE24 OTs may be connected
to one 112SCX10 or 112SNX10.
The 11QPE24 line port is connected to a 130SCX10 or 130SNX10 client port. Up
to 10x10G line ports from the same or different 11QPE24 OTs may be connected
to one 130SCX10 or 130SNX10.
The following enhancements are supported on 11QPE24 in 1830 PSS-32, PSS-16 and
PSS-4 shelves
TR/RTR thresholding method for TCA (ETSI mode)
L2 alarm severity setting (L2 alarms were supported but their severity could not
be modified by the user in previous releases)
Multi-ring ERP Mode w/ R-APS virtual channel (completing the mode without R-
APS virtual channel already introduced in Release 6.0)
The enabling of BITS (external station clock) input/output on 11DPE12A is supported in
1830 PSS-32, PSS-16 and PSS-4 shelves. The provisioning for 2MHz, E1 or DS1
interfaces is configurable. The BITS input can participate the timing reference selection
and protection process like other SyncE inputs (with configurable QL/SSM) and the
BITS output is configurable to be timed either from the T0 (system timing) or from an
independent clock selection process.
The latency of 11DPE12A and 11QPE24 in 1830 PSS-32, PSS-16 and PSS-4 shelves can
be optimized via disabling FEC mode in Release 7.0.0. This requires the utilization of the
T-XFP (APN=1AB375650047) supporting error free performance in NO FEC mode for
10GbE client (CBR mapping) at 11.096 Gbit/s.
Note: Users shall ensure that the XFP port is equipped with a low-latency/No-FEC XFP
(APN=1AB375650047) when disabling FEC on that port. The software will not check
nor raise a warning message. The FEC disabling option is available for any XFP but
error-free transmission may not be guaranteed.
It is now possible to tunnel transparently LACP PDUs on 11QPE24. This configuration is
at port level (since LACP are link-level untagged frames using slow-protocol MAC
address). This is consistent with the fact that LACP transparency only applies to EPL
Option 2 according MEF 6.1.1 standard. It is supported on null SAPs, explicit null SAPs
and default SAPs.
ITU-T G.8021 compliant processes for defect detection, consequent actions, defect
correlation into alarms are added on 11QPE24 in 1830 PSS-32, PSS-16 and PSS-4
shelves, for ITU Transport look & feel. New Ethernet Service OAM alarms such as
cLOC, cRDI, cUNL, cMMG, cUNM, cUNP, cUNPr are defined in addition to IEEE
802.1ag currently supported. The user has to set ITU/IEEE alarm mode per card
ITU-T Y.1731 PM functions are enhanced for 11DPE12A in 1830 PSS-32, PSS-16 and
PSS-4 shelves. The ITU-T Y.1731 PM functions (LM, SLM, 1-way DM, 2-way DM,
pro-active) were already implemented on 11DPE12A in Release 6.0 but only on-demand.
This releases adds pro-active support together with associated counters per EVC/CoS
compliant to G.7710/G.8051/Y.1564/MEF 35/36 (minimum, average, maximum FLR or
FD in measurement interval, SES, UAS) with binning and thresholding.
Accurate ITU-T Y.1731 1-way DM (with PTP) is supported on 11DPE12A in 1830 PSS-
32, PSS-16 and PSS-4 shelves..
Synchronization
Release 7.0.0 will alarm PFDC based system clocks that have failed or drifted out of
specification (BADCLKFREQ is raised when the drift is greater than 55PPM) and switch
to the system clock from the other PFDC. If the system clock drifts marginally out of its
specified range (9PPM-55PPM), the system may not be able to reliably determine which
clock is out of specification, so the system will raise an alarm (SUSPECTCLKFREQ)
against both clocks requesting the operator identify the failing clock. The operator can
then use the new clock switch commands to request that system uses one clock or the
other for system timing. The operator will monitor existing system alarms to isolate the
source of the problem. The first warning of system clock drift will be missing or
unexpected wavekey alarms. These will clear when the system has switched away from
a clock exhibiting oscillator drift.

Alcatel-Lucent 1830 PSS-32 supports automatic and manual switching for the following
cards: 11STAR1, 11STMM10, 11QPA4, 11DPM12, 11STGE12, 43SCA1, 43SCX4, and
43SCX4E. Alcatel-Lucent 1830 PSS-16 will only alarm and protect against clock failures
if one of the following cards are present: 11STAR1, 11STMM10, 11QPA4, 11DPM12,
11STGE12 and have been upgraded to the latest FPGA FW. Note, all 100G OTs have
their own on-board clock and do not use the shelf clock.
GMPLS Enhancements
GMPLS control plane support
260SCX2 (100G Mode)
130SNX10
130SCUPB (same as 130SCUP, part of L1 CP as iNNI port and L0 CP as drop
port)
MRN improvements
Support of automated reversion of tunnels
The priority of the tunnel inherits from the priority of the client traffic/service

Features Supporting tools
Supporting tools
Engineering and planning tool (EPT)
Alcatel-Lucent 1830 PSS-16/32 Release 7.0.2 will be supported by EPT Release 7.0.2.
Note: Contact Alcatel-Lucent Technical Support for questions regarding EPT support
of Alcatel-Lucent 1830 PSS-16/32 Release 7.0.2.
Key Management Tool (KMT)

The 11QPEN4 pack is supported by KMT Release 7.0.0.
Note: Refer to the KMT Release 7.0.0 Customer Release Notes for the KMT Release 7.0.0
details.
1354RM-PhM and Commssioning and Power Balancing Tool (CPB)

Alcatel-Lucent 1830 PSS-16/32 Release 7.0.2 is supported by PhM Release 12.2.0 and CPB
Release 7.2.0.
Note: Refer to the 1354 RM-PhM Release 12.2.0 Customer Release Notes for the 1354
RM-PhM Release 12.2.0 details.
Note: Refer to the CPB Release 7.2.0 Customer Release Notes for the CPB Release 7.2.0
details.

Application notes
Overview
This section highlights some important considerations and limitations associated with this
release. Refer to Chapter 2, "Issues" for a list of known issues associated with this
release.
NE Uni-directional topology details

A mixed network with an NE running 1830 PSS Release 6.0.0 or later connected to an
NE running software earlier than Release 3.5 is not recommended. If such a network
exists, the NEs cannot auto-discover the external bi-directional topology between them
for a new LD line connection - where there is an NE running Release 6.0.0 or later on one
side and an NE running a software release earlier than Release 3.5 on the other. The
topology needs to be manually added on both NEs for the newly created connection.
System Clock Selection

The card initialization process has a preference for Clock A, but not exclusively as there
are a number of events that can influence the automatic selection to choose Clock B. If
the user wants to be certain all cards are selecting a single clock, the following procedure
can be used: After verifying clocks are in specification, provision the system to select
clock A, remove and reinsert PFDC B, and then provision the clock selection to auto.
These steps do not impact transmission as manual clock switches are hitless when both
clocks are operating within specification.
CLI alarm profile commands
An additional parameter is introduced in the middle of two CLI alarm profile commands.
The purpose of the change is to improve the messaging performance and optimize the PM
TCA operation. The new syntax of the commands is:
config alm prfl

show alm prfl
The introduction of the parameter to display and configure an alarm profiles affects all
cards. For more information, refer to Alcatel-Lucent 1830 Photonic Service Switch
(PSS) Release 7.0 CLI Command Guide.

11DPE12 ESNCP switch time

The number of ESNCP protection groups that can switch in less than 50 ms between
11DPE12A and 11DPE12 is limited to 2. This limitation only applies to mixed 11DPE12-
11DPE12A configuration. 11DPE12A-11DPE12A configurations can support a higher
number of ESNCP protection groups.
11DPE12A facility loopbacks

If a client facility loopback is established on an optical FE port of the 11DPE12A pack,
received frames are less than transmitted frames, about 1% are lost. Release the client
facility loopback, and the FE traffic will run error free.
DWDM XFP 80km

DWDM XFP 80km (1AB375650001 -thru- 1AB375650044) are certified for use with
112SCX10, 112SNX10, 130SCX10, and 130SNX10 in USER mode only.

100G LR10 CFP and Digital Diagnostic Monitoring

A new version of the 100G LR10 CFP (1AB402160010) is introduced which has the
same capabilities as the current version and additionally supports Digital Diagnostic
Monitoring (DDM). 1830 PSS Release 6.0.0/7.0.0 supports reporting DDM information
for all CFPs which support the feature. In situations where both versions of the 100G
LR10 CFP exist in the network, DDM will be reported only for the new versions of the
CFP.
100G/200G FEC TCA default values

Default values for FEC TCAs are triggered when system margin drops below 7dB. This
may not be adequate for 100G packs. A value of 1dB is recommended. As such, for 100G
packs (130SCX10, 112SCX10, 112SCA1, 112SNA1, 112SNX10, and 260SCX2), a
profile with different values should be used. The steps below summarize the values to be
used for 1dB margin for both SDFEC and AFEC:
1) Enter values in profile 1 (to be used for AFEC)
conf profile pm dw 1 tca RxBERPreFEC15MinTr 1.4E-3
conf profile pm dw 1 tca RxBERPreFEC15MinRTr 4E-4
conf profile pm dw 1 tca RxBERPreFEC1DayTr 1.4E-3
conf profile pm dw 1 tca OTU4RxRSCorrCnt15MinTr 140000000000
conf profile pm dw 1 tca OTU4RxRSCorrCnt15MinRTr 40600000000
conf profile pm dw 1 tca OTU4RxRSCorrCnt1DayTr 13500000000000

2) Enter values in profile 2 (to be used for SDFEC)

conf profile pm dw 2 tca RxBERPreFEC15MinTr 1.9E-2
conf profile pm dw 2 tca RxBERPreFEC15MinRTr 1E-2
conf profile pm dw 2 tca RxBERPreFEC1DayTr 1.9E-2
conf profile pm dw 2 tca OTU4RxRSCorrCnt15MinTr 200000000000
conf profile pm dw 2 tca OTU4RxRSCorrCnt15MinRTr 180000000000
conf profile pm dw 2 tca OTU4RxRSCorrCnt1DayTr 100000000000000
3) Enter values in profile 3 (to be used for SDFEC-200G mode)

conf profile pm otu 3 tca OtuRxBERPreFEC15MinTr 1.26E-2
conf profile pm otu 3 tca OtuRxBERPreFEC15MinRTr 6E-3
conf profile pm otu 3 tca OtuRxBERPreFEC1DayTr 1.26E-2
conf profile pm otu 3 tca OTU4RxRSCorrCnt15MinTr 200000000000
conf profile pm otu 3 tca OTU4RxRSCorrCnt15MinRTr 180000000000
conf profile pm otu 3 tca OTU4RxRSCorrCnt1DayTr 100000000000000
4) Assign profile 2 to all 100G cards with OTU4 line interfaces (for SDFEC):
Example for all SDFEC 100G packs (except 260SCX2):
config interface 130scx10 1/6/l1 pm dw 0 profile 2
Example for 260SCX2 (100G mode)
config otu 1/6/l1ch1 pm otupm 0 profile 2
config out 1/6/l1ch1 pm otupm 1 profile 2
5) Assign profile 1 to all 100G cards with OTU4 line interfaces (for AFEC).
Example for all SDFEC 100G packs (except 260SCX2):
config interface 130scx10 1/6/l1 pm dw 0 profile 1
Example for 260SCX2 (100G mode)
6) Assign profile 3 to all 260SCX2 cards running in 200G mode:

Example for 260SCX2 (200G mode):

11QPE24 - Clear CCM defect reports RDI MEP trap

RDI traps are declared when peer MEP is enabled. This is normal behavior when the
MEPs are first turning on as they are first receiving their CCMs. This condition will clear
very quickly as they stabilize.
11QPE24 Network QoS Egress Traffic Remarking

The marking of the S-VLAN/C-VLAN p-bits (called PCP in IEEE 802.1 terminology) on
the uplink/network (NNI) port egress is working as follows:
1. With remarking disabled (default), the C-VLAN p-bits will be copied into the S-
VLAN p- bits/PCP for all egress frames.
2. With remarking enabled, the behavior is dependent on the svc-sap-type:
when svc-sap-type type is not dot1q-preserve, the S-VLAN and C-VLAN
p-bits/PCP will both be set according to the network policy FC to PCP
mapping.
when svc-sap-type type is dot1q-preserve, the S-VLAN p-bits/PCP will
be set according to the network policy FC to PCP mapping, while the C-
VLAN p-bits/PCP will be preserved.
The IEEE/MEF standard compliant behavior is achieved when remarking is enabled and
svc-sap-type dot1q-preserve is used (item 2b).
TSoP per circuit pack limitation

Due to thermal concerns, only a subset of the available SFP ports should be equipped
with TSoP SFPs.
For the 11QPE24:
a maximum of twelve TSoP SFPs can be installed on the pack for use in central
office. The TSoP SFPs can only be installed in ports C7 - C22.
a maximum of six TSoP SFPs can be installed on the pack for use outside plant. The
TSoP SFPs can only be installed in ports C17 - C22.
For the 11QCE12X:
a maximum of twelve TSoP SFPs can be installed on the pack for use in central
office. The TSoP SFPs can be installed in any port.
a maximum of six TSoP SFPs can be installed on the pack for use outside plant. The
TSoP SFPs can be installed in any port.


2 Issues
Overview
Purpose
This chapter of the Customer Release Notes provides a list of resolved issues, known
issues, and restrictions in Release 7.0.2.
Contents
This chapter contains the following:
Resolved issues 56
Known issues in Release 7.0.2 65
Restrictions 145

Issues Resolved issues
Resolved issues
Resolved issues for Release 7.0.2
The following issues have been resolved in Release 7.0.2:

Issue #PSSKPL-11
If all ports (UNI and NNI) on an 11QPE24 or 11OPE8 need to be configured in different
LAGs, the port assignment can be done without restriction. The last port that is not yet
assigned into a LAG can be configured in either sub-group#1 or in sub-group#2.
Issue #PSSKPL-14
If an inserted pluggable is supported for the current port role (Line, Client, VOA), but it
is not supported for the port type (1GbE, FE, 10GbE LAN, OTU2), an
UNKNOWNMOD "Pluggable Module unknown" alarm will now be raised.
Issue #PSSKPL-18
When a link partner sends a Remote Fault indication to an 11QPE24 1GbE/FE port, the
expected LANRFI condition is raised.
Issue #PSSKPL-21
Upon LC reset, ECDC mismatch alarm no longer raised for SyncE when SyncE actually
working correctly.
Issue #PSSKPL-25
After deprovisioning a SyncE line reference (assport null), no unexpected alarms raised.
Issue #PSSKPL-26
After an NE is upgraded to R7.0.1 and higher, all 11QPE24 unassigned client 1GbE ports
will have the correct auto-negotiation default value of "True" after being assigned as
1GbE/FE Does not apply to optical FE port, which should have AN=False (see Issue
#PSSKPL-34).

Issue #PSSKPL-27
Expected maintenance conditions are now raised for 11OPE8 M ports.
When M port Admin State is set to Maintenance, the expected MAN condition is raised.
When a terminal loopback is set on M port, the expected LPBKTERM condition is
raised.
When a facility loopback is set on M port, the expected LPBKLINE condition is raised.
Issue #PSSKPL-29
When CLI is used to provision the AINS attribute on an 11QPE24/11OPE8 card, no
denial message is returned, and the card is provisioned as expected.
Issue #PSSKPL-31
If AINS state is provisioned on M port, and alarms are cleared, the AINS count down will
now start as expected.
Issue #PSSKPL-32
For the 11QPE24 cards, if speed/duplex mismatch is created between link partners on
1G/FE electrical ports, a LINKDOWN alarm is now raised as expected.
Issue #PSSKPL-34
Setting auto-negotiation (AN) to "True" on an 11QPE24 optical FE port is blocked in the
user interface, since it may cause port not to pass traffic. This limitation does not apply to
electrical FE ports.
Issue #PSSKPL-35
If the size of an incoming frame without FCS exceeds the configured port MTU by up to
4 bytes, the frame is counted and discarded as over-sized which is the expected behavior.
Issue #PSSKPL-37
The CLI command "show ... igmp-snooping base" returns the right number of igmp-
groups when the dynamic groups exceed 1000.
Issue #PSSKPL-50
In the WebUI All Logs report, entries in the Conditions and/or Categories columns are no
longer marked as "INVALID".

Issue #PSSKPL-59
1350 OMS Notify Audit will not fail if SNC is in state Ready To Revert, its active route
is equal to the Nominal route and active route is not using it Nominal wavelength.
Issue #PSSKPL-64
Modifying the description of an existing ODUkXC on a 112SDX11card and then either
warm resetting or reseating the EC no longer impacts traffic.
Issue #PSSKPL-65
If the 112SDX11 is provisioned with 40GbE QSFP+ traffic, the CRC error rate (of
Ethernet Rx PM) is counted correctly on the C11 port after the LANLOS alarm is
cleared.
Issue #PSSKPL-89
When the VTS Classification Mode of an 11DPE12A port is provisioned to Port or
Untagged, the 1588 packets will be received and the PTP function will work as expected.
Issue #PSSKPL-94
RSFEC can be used on DWDM XFPs in 11OPE8 cards without any restrictions.
Issue #PSSKPL-101
When an 11OPE8 X port is assigned as an OTU2 and FEC type EFEC2 is provisioned,
traffic will pass normally and there will be no unexpected alarms.
Issue #PSSKPL-104
11OPE8 mate ports pass traffic without interruption.
Issue #PSSKPL-116
When a MSH8-FSM shelf is provisioned in a system with AINS disabled, the shelf
comes up as AINS UP as expected.
Issue #PSSKPL-117
Egress adjustments on ASWG amplifiers operate as expected, without erroneous alarms.
Issue #PSSKPL-118
When cross-connects and topologies exist on a MSH8-FSM shelf, deleting the shelf is
denied.

Issue #PSSKPL-119
For WR20-TFM cards, the loss report displays the Actual Loss (Gain) value for port to
port loss.
Issue #PSSKPL-123
The power suspended alarm is now reported, as expected, on the WR8-88 sig out port.
Issue #mh06844
Data Column correctly displays values for PM TCA in Report->Logs->All Logs from
WebUI.
Issue #mh06940
OMSP protection shemes hosted on OPSA packs can now operate TL1-commands
related to OTS facilities.
Issue #mh06941
TL1 commands targeting facilities hosted on 11DPM12 now accept any valid facility
type.
Issue #mh07320
When a line terminal loopback is enabled on a 112SCA1/112SNA1, the problem with
ODU_AIS insertion is no longer an issue in R7.0.2.
Issue #mh08767
Setting the client LOS Propagation to LASER OFF on 112SCA1/112SNA1 in 1830PSS
R7.0.2 does not impact existing transmission.
Issue #mh12818
Upon firmware upgrade, LSP/services will not fail if EFEC2 is not selected.
Issue #mh14346
If an OAMP, VOIP, E1, E2 interface has OSPF enabled and properly configured such
that the OSPF adjacency state is FULL and the IP address/Mask is subsequently changed
to an invalid value for the LAN configured on the interface, the OSPF adjacency state is
reliably shown as DOWN when it is actually DOWN.

Issue #mh15630
Fiber plugout on client port of 11STAR1A 3R correctly triggers an LOS-P alarm which
will clear on fiber repair.
Issue #mh16847
Networks designed via EPT for R7 where the default FEC type is EFEC, will not have
LSPs with feasibility violation error due to choice of FEC type.
Issue #mh17438
RTRV-ALM-ODU now working with specific AIDs.
Issue #mh17443
RTRV-ALM-OTU now works with the unspecific "ALL" AID.
Issue #mh18113
If an AM2125B is equipped in a line as either an ingress LD or an egress LD, the
operational state for the cross connections on that line will be up.
Issue #mh18176
RTRV-ALM-OCH is now working with specific AIDs.
Issue #mh18177
ED-CRSPROT-ODU command will no longer be denied when the AID order does not
match the order in which the AIDs were provisioned.
Issue #mh18178
The ENT-OTU4, ED-OTU4, DLT-OTU4 TL1 commands for 112SNA1 and 112SCA1
are now supported.
Issue #mh18341
Option "All" for PM retrieval now provides 15-min,1-day, and Raw bins as expected.
Issue #mh18477
When optically connecting an 1830 amplifier to an 1696 OSC WDM port, the associated
1830 OSC port OSPF Adjacency state reliably enters Full when the connection is
created or restored.

Issue #mh18701
The 1830 PSS correctly handles LSAs from 1696 ROADM NEs.
Issue #mh18725
Create ESNCP of FC100 or FC200 on 4DPA4; introduce an LOS, and then clear the LOS
at the client port, the FELSS on the far-end client port will now be cleared consequently.
Issue #mh20076
CLI command "config interface state sh/sl up|down" is executed as expected for uni-
directional amplifiers.
Issue #mh24399
The AINS timers on the client port and the OT Line port are independent of the system
AINS timer.
Issue #mh25936
If a new protection group is created while there is an active protection switch due to
signal failure on the line, the switch status of existing protection group remains as "Signal
failure". The new protection group is created with the correct status of "Signal failure".
Issue #mh26178
Under CLI commands, provisioning of GCC1 or GCC2 for the 11QPA4 client ports will
be denied by the system.
Issue #mh26822
In this 1830 PSS software release, as well as in previous releases, the cli command
"config interface sh/sl/meshoutx description text" is correctly blocked as it is not
supported on the PSS-32/16 shelf.
Issue #mh26996
Under user define mode, when provisioning odd channel 50GHz fixed DWDM XFP (i.e.
1AB2435100xx) on 11DPE12, 11dpe12e, 11dpe12a, or 11dpm12 line port, physical
topolgy between VOA port and related channel can be successfully created.
Issue #mh27132
OSPF interworking between 1830PSS OCS shelves and 1830PSS-4 shelves allows GCC
communiction without the need for static routes.

Issue #mh34426
Using PhM, an NE user can be added, modified, or deleted when a valid password is
used.
Issue #mh34907
The WR OSNROOMR (OSNR measurement out of range) alarm is not incorrectly raised
on a WTOCMA port against a channel that is not present.
Issue #mh35876
The SET-ATTR-ODU and RTRV-ATTR-ODU commands are now supported to
configure or retrieve the notification code (NTFCNCDE) for the conditions of 260SCX2
ODU4 facility.
Issue #mh35884
The SET-ALMPRFL-TCM and SET-ATTR-TCM commands are now supported to
configure or retrieve the notification code (NTFCNCDE) for TCM conditions.
Issue #mh36053
unsupported TILT parameter has been removed from EDPWRMGMTEGRESS and
EDPWRMGMTINGRESS TL1 commands.
Issue #mh36237
In CLI, XFP module type provisioning is handled correctly now.
Issue #mh36307
In an 130SCX10 to 130SCUPB IOP configuration, when Line facility loopback is
enabled on an 130SCX10 pack, traffic restores immediately and returns to error-free
operation.
Issue #mh36315
The AINS timer of the client port can only be set if it is greater than the AINS timer of
the Line port. If the Line port timer value is greater than the client port timer value, a
denial message is reported as "Error:Request failed - Inconsistent network and client port
AINS timers".

Issue #mh36792
The MC-LAG parameter "propagate-hold-time" has the intended effect.
Restriction: #mh36775
For 11QPE24, all packets above 9216 are now included in the "Packets of 1519 or more
Octets" counter.
Issue #mh37218
The 11DPE12A pack supports software downgrade from R7.0. Software downgrade will
not cause the 11DPE12A to fail to boot-up.
Issue #mh38412
When wtdusage is provisioned as wtocm, a warm reset on wtocm/wtocmf pack will not
add power values to nonexisting channels in OCH PM OPR.
Restriction: #43268
Certain units require the usage of the high power fan tray (8DG59243AB). EPT designs
enforce the usage of these fan units and the system will raise an alarm if an inappropriate
fan unit is present in the system (FAN32HRQD).
Issue #52245
The (+/-) sign of the reported Chromatic Dispersion PM parameter for the 112SCX10 and
112SCA1 circuit packs is correctly reported.
Issue #78823
The RTRV-CRS-OCH TL1 command now supports DETAIL and TRACE parameters.
Issue #83246
After a cold reboot/warm reboot/reseat of a 43STX4/43STX4P pack, the "Pluggable
Module Mismatch" and "Pluggable Module Unknown" alarms are no longer reported on
the client port.
Issue #83615
RTRV-PM-OTU3 can be used now with TMPER = 1DAY.

Issue #84373
When the 11DPE12 is provisioned for the first time, with a line rate of 10 GbE and qinq
mode, transmission will come up normally.
Issue #97514
When the 11DPE12A total service frames sent rate exceeds the maximum port bandwidth
(for GbE port, the maximum port bandwidth is 1Gbps), sub-services' CIR bandwidth can
be guaranteed.

Issues Known issues in Release 7.0.2
Known issues in Release 7.0.2

CDC-F configuration
The following are issues that affect the circuit packs used in the CDC-F configuration on the
Alcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 7.0.2:
Issue #PSSKPL-225
The user channel target power offset function is not available on WebUI.
Workaround:
Use CLI to configure and view current settings for the user channel target power offset.
Issue #PSSKPL-221
Some existing Network Interface IDs (GCC terminations) may not display in the
Network Interface list. In these cases, the user may not be able to re-create the same
Network Interface item or re-configure the associated GCC port admin state to down.
Despite not being shown on the user interface, the GCC termination is operational.
Workaround:
Perform a cold reboot of the Active EC and the NE will recover the missing network
interface items automatically.
Issue #PSSKPL-223
The pump temperatures and currents are only displayed for the first 3 of 4 EDFA pumps
in ASWG and A4PSWG.
Workaround:
None.
Issue #PSSKPL-219
If special characters are entered in the scan description field, an OTDR scan will fail.
Special characters include double quotation mark (") and semicolon (;). Currently, these
characters may be entered in the description in WebUI by pasting a text string, or in CLI
proceeded by two double quotation marks ("").
Workaround:
Avoid special characters in the scan description field.

Issue #PSSKPL-126
Occasionally, "Power management suspended" conditions are raised and cleared for
channels on the WR20-TFM pack.
Workaround:
These are are non-transmission impacting conditions; they will clear without
intervention.
Issue #PSSKPL-124
In CLI, certain custom profile settings may lead to OTDR scan failures.
Workaround:
Use WebUI for OTDR scans with custom profile settings.
Issue #PSSKPL-68
OCHKEYUNAVAIL is not reported on MCS ports. If Wave Key assignment fails due to
running out of unique instances for the channel frequency network-wide, the operator
will not be informed of the failed assignment by this condition.
Workaround:
If the channel fails to launch, check the cross-connect Wave Keys for the source node
cross-connect. If the cross-connect Wave Keys are 0,0 in the direction that failed to
launch, the connection can be assigned keys by using the "rekey allow duplicates" cross-
connect command. The CLI command is config xc <id> wavekey rekeyallowdups.
General
The following are general issues and issues affecting multiple circuit pack types on the Alcatel-
Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 7.0.2:
Issue #PSSKPL-217
If an XL-64TCW (zero chirp T-XFP) is provisioned on the line port of an 11DPE12A,
11QPA4(A), or 11DPM12 pack, an LOM alarm cannot be raised on the line side.
Workaround:
None.
Issue #PSSKPL-216
If MANUAL power management is used in a FOADM system and XL-64TCW (zero
chirp T-XFP) is provisioned on an 11DPM12 or 11DPE12A line port, the Expected
Network Output Power on VA port cannot be provisioned to a power level greater than
-5.5 dBm.
Workaround:
None.
Issue #PSSKPL-214
During the addition of a subtending shelf, a CPUPERFORMANCE alarm may be
reported for EC in the subtending shelf. This alarm may be raised permanently.
Workaround:
Perform a warm reset on the active EC in the Master Shelf to clear the alarm.
Issue #PSSKPL-135
If a single-slot card is inserted in an empty slot that is pre-provisioned for a multi-slot
card, a mismatch alarm is not reported.
Workaround:
None.
Issue #PSSKPL-131
Card mismatch may not be reported when a a card is inserted into a slot reserved for a
multi-slot card or 1/2 slot card.
Workaround:
Check the slot status to see if the equipment secondary state value (SST) was set to MEA
which indicates that the card physically present in the slot is inconsistent with slot
provisioning data.
Issue #PSSKPL-39
For OTN packs, provisioning the Primary State of a port with OTN signal type to In
Service, AINS will suppress the LOS-P alarm reported on the port layer, while the
accompanied SSF-OTU condition is reported on the OTU layer.
Workaround:
Set the Primary State to In Service, AINS at OTU layer to suppress the accompanied
SSF-OTU on the OTU layer.
Issue #PSSKPL-41
Provisioning a 16-character MD5 key string and warm rebooting the EC will cause an
OSPF MD5 authentication failure. As a result, the OSPF Adjacency State will be down.
Workaround:
Provision the length of the MD5 key string to be less than 16 characters.

Issue #PSSKPL-42
When the GCC MTU is provisioned as 576 and the RNE is pinged with a packet size
greater OR equal to 38085, it will not return 100%. The following packs are impacted by
this scenario:
11DPE12/A/E
11DPM12
11QPA4
11QPE24
112SDX11
11OPE8
Workaround:
Either provision the ping packet length to less than 38085 or provision the MTU size to
1500.
Issue #PSSKPL-43
Occasionally, the SDEE (Support Entity Service Exists) Secondary State on 112SDX11
and 11DPM12 cards will not function properly in the following two scenarios:
When ODUkXC is created or a loopback is set against the client port, the SDEE
does not appear in the client port details.
Before ODUkXC is created, the SDEE unexpectedly appears.
Workaround:
None.
Issue # PSSKPL-92
On occasion, an Oplink XS-64.2D pluggable module on the line port of an OT card may
incorrectly shut down its transmitter power while OPT PM may show normal, and a "Port
failure - device" alarm is possibly raised. The following packs are impacted by this
scenario:
11DPE12/A/E
11DPM12
11QPA4(A)
The module information: Module Type/Vendor: XS-64.2D/Oplink
APN: 1AB422360001~1AB422360016
Workaround:
Re-seat the pluggable module or cold reboot the pack.

Issue #PSSKPL-95
In CLI, the SHLEFINCON alarm is raised against the PF slot, even though the alarm is
intended to be raised against the shelf level object. WebUI does displays the appropriate
alarm source.
Workaround:
Ignore PF as the alarm source. Follow the troubleshooting as indicated in the Alcatel-
Lucent 1830 Photonic Service Switch (PSS) Maintenance and Trouble-Clearing Guide.
The proper shelf number is indicated in the CLI alarm message.
Issue #PSSKPL-99
If the ssh handshake during opening of a sftp file transfer session fails, the NE does not
discard the operation. As a result, the file tranfser stalls and does not time out.
Subsequent file transfers may be blocked. There is no command to abort the stalled
transfer.
Workaround:
For redundant ECs, perform an EC sideswitch on the affected NE.
For non-redundant ECs, perform a warm reset on the EC.
Issue #mh36672
NETIF/OSC Actual MTU size is always reported as "-" when the interface is UP. This
issue affects NETIF/OSCs provisioned on the following OT packs:
11DPE12/A/E
11DPM12
11QPA4
11QPE24
11QPEN4
11STAR1A
112SDX11
11OPE8
Workaround:
When the NETIF/OSC interface is UP the negotiated Actual MTU size is the lesser of the
two Configured MTU sizes on either side of the NETIF/OSC interface.
Issue #mh36663
During the activate phase of a software upgrade, OT packs may fail to reboot and load
the new software. The upgrade status displays the "Card not found". Transmission is not
affected.
Workaround:
Perform a warm reset on the card that failed to boot. Repeat the audit, download, and
activate steps for the software upgrade. These steps will execute quickly since the
software is already loaded.

Issue #mh27021
Intershelf cabling alarms (ES1/ES2 link down) are raised and cleared directly following
system initialization or in-service upgrade. The raising/clearing of these alarms is
expected to stop autonomously.
Workaround:
None. If problem persists, contact Alcatel-Lucent support.
Issue #mh26390
Coherent, regenerated wavelength services are built using multiple, unidirectional OCh
trails. When using CLI or WebUI to show path power trace AtoZ of any given trail, the
output is of the correct service but of a different trail than the one being requested.
Workaround:
At every 3R site and at each endpoint along the service, show path power trace AtoZ of
all corresponding trails.
Issue #mh16852
Cards are shown in-service (admin and operation state UP) during card initialization.
Workaround:
Wait for card initialization alarm to clear before retrieving the card status.
Issue #mh24440
On 4DPA4, when provisioning a facility loopback on a client or a line port, LOS alarm is
raised against the port while the loopback is active. Traffic remains error free.
Workaround:
Ignore the LOS alarm; the alarm is cleared once the loopback is removed.
Issue #mh18105
Inserting a card in slot that has been reserved or preprovisioned for a multislot card may
result in incorrect card mismatch alarming.
Workaround:
Technician should verify card placement prior to insertion. In the event that a card
mismatch occurs, remove the card and warm reboot the main controller card.

Issue #78826
After the transmit frequency is changed for any non-coherent OT, cross connection
provisioning for the OT might fail.
Workaround:
Follow these steps:
De-provision the OTU trail and Physical connection from the OMS original frequency;
change the frequency to None using WebUI; re-create the Phyconn & OTU trail using
the OMS expected frequency.
Issue #78487
On rare occasions, during a greenfield setup for an interconnection between 10G line
interfaces with RS-FEC type [11DPE12(E), 11QPA4, 11DPM12], traffic may not come
up when the line port FEC type is re-provisioned to RSFEC from other FEC types (i.e
EFEC/EFEC2).
Workaround:
Re-seat the XFP module, or cold reboot the pack to allow traffic.
Issue #22337
While creating services with any user interface, the cross connection operation state is
always down when the CH is add/drop at the SFD channel port.
Workaround:
When the services are provisioned, set the admin state to up for the SFD CH port.
Issue #27442
Transient alarms may be observed during a software upgrade or due to a protected
equipment controller switch.
Workaround:
No action is required. The transient alarms can be ignored and will clear on their own.
Issue #53370
When a customer network router/switch, manually configured to 100Mbps and Full
Duplex, is connected to the Alcatel-Lucent 1830 PSS-16/PSS-32 via the OAMP port, the
NE OAMP link interface may negotiate down to 100Mbps/Half Duplex mode when the
NE OAMP port Configured Speed and Configured Duplex Mode port settings are both
set to auto-negotiate.
Workaround:
Manually set both the NE OAMP port and Customer Router/Switch Configured Speed to
Auto and the Configured Duplex Mode to Auto.

Issue #43272
If the two client ports of an 112SCX10 or 43SCX4 are provisioned with different
encapsulation modes, there will be intermittent declaration of ODU-CCI, ODU-LCK and
ODU-DEG alarms in addition to the expected ODU-PLM alarm.
Workaround:
Ignore ODU-OCI, ODU-LCK and ODU-DEG alarms during service reconfiguration.
After the provisioning at both ends matches, these alarms will clear.
100G OT
The following are issues related to the 112SCX10 10x10-Gb/s muxponder, the 112SNX10
extended reach 10x10-Gb/s coherent optical muxponder, the 112SCA1 100-Gb/s Add/Drop, and
the 112SNA1 extended reach 100-Gb/s coherent Add/Drop optical transponder OT circuit packs
on the Alcatel-Lucent 1830 PSS-16/PSS-32. This section also includes the 130SCX10 and
130SNX10 muxponders.
Issue #PSSKPL-165
Cross-connection provisioning on 130SCX10 and 130SCUP packs may fail after the
system is upgraded to release R7.0.1 or R7.0.2 if the following conditions are all true:
System was running a software release prior to R7.0.1
130SCX10 packs are installed or intercompound topologies are provisioned for
130SCUP packs
No cross-connections are provisioned on the pack
Workaround:
To avoid the situation: Prior to upgrading the software provision at least one cross-
connection on all 130SCX10 and 130SCUP packs.
To correct the situation after the system is upgraded to R7.0.1 or R7.0.2:
Follow these steps for 130SCX10:
1. Delete all topologies from the 130SCX10 cards without any cross-connections
2. De-provision the 130SCX10 cards without cross-connections
3. Re-provision the 130SCX10 cards
4. Re-provision the topologies.
Follow these steps for 130SCUP:
1. Delete the intercompound topologies for the 130SCUP packs without any cross-
connections
2. Re-provision the topologies.

Issue #PSSKPL-55
When 112SCA1/112SNA1 packs are operating in OTU4 mode and TTI trace comparison
and TTI mismatch response are enabled, a valid mismatch will increment the UAS count
(as expected). However, after the mismatch is cleared, the UAS will continue to
increment.
Workaround:
Perform a warm reset on the pack to stop the UAS from incrementing.
Issue #mh36306
In a 130SCX10 to 130SCUPB interop configuration, with 130SCX10 packs as regen
packs, using AFEC, the line facility loopback on the 130SCX10 pack does not work
correctly.
Workaround:
Use SDFEC mode on the line side.
Issue #mh36308
Sometimes, bit errors are not in sync with the NEND BIP parameters on 130SCX10 and
the FEND BBE parameter on 130CUPB on Line OTU4.
Workaround:
None.
Issue #mh36310
The Line Terminal Loopback cannot be used in Y-Cable configurations with 130SCX10
OTs. The digital Line PM parameters may not be correct when the Line Terminal
Loopback is enabled on 130SCX10 OT.
Workaround:
Ignore the PM errors when Line Terminal loopback is enabled. Do not enable Line
Terminal Loopback in Y-cable configurations.
Issue #mh36958
The "Asymmetric parameter" of an OCS Compound, when used for an IOP configuration
with 130SCUPB or 130SCUP and 112SCX10 or 112SCA1 will get disabled
approximately 30 seconds after provisioning. This results in loss of transmission.
Workaround:
Enable the "Asymmetric Mode" on 130SCUP/130SCUPB, then create the DWDM
Topology / OCH XC connections between the OCS and DWDM compound. Creating
the service in this manner correctly creates the service.

Issue #mh32981
Based on ITU standards, a Generic-AIS (PN-11) signal is inserted inside of OPU-n
payload area in case of CBR client signal LOS The issue is that 130SCX10/130SNX10
OTs at the far end would interpret PN-11 as OTU2-AIS. The unexpected OTU2-AIS
would trigger ODU2-AIS insertion downstream and ODU2-BDI insertion upstream. This
issue may also affect legacy OTs - 112SCX10/112SNX10 when these packs are set up for
interworking with new 130/260 OTs.
1. In IOP configurations where one end of the Pt-Pt link between a pair of
130SCX10/130SNX10s is configured as OC-192 or 10GBE (CBR11096 or
CBR11049) and the other end is configured as OTU2, incoming LOS condition at the
OC-192/10GbE port receiver will result in an ODU-AIS being sent out on OTU2 NNI
interface (instead of Generic-AIS within OPU2) and an ODU-BDI being sent
upstream.
2. For Pt-Pt links with the client signal provisioned as SONET or 10GBE (CBR11096 or
CBR11049) at both ends, a client LOS on the 130SCX10 will result in an ODU-BDI
coming from the far end 130SCX10/130SNX10 OT.
3. For cases where a service is between 10AN10(G)/130SCUP(B) and
130SCX10/130SNX10, an OC-192/10GbE client LOS on the 10AN10(G) will result
in an ODU-BDI coming from the far end 130SCX10/130SNX10.
Workaround:
None.
Issue #mh18339
On 112SCA1/112SNA1, CRC errored packets are included in the total packet count.
Workaround:
Good packet counts can be derived by subtracting the CRC errored packets counter.
Issue #mh17527
The default bin status for current bin is showing "Valid" instead of "" (null). This is seen
for Line and client side PM.
Workaround:
None. At the end of the accumulation period, the validity flag will be properly populated.

Issue #mh25512
Occasionally, switch times on 112SNA1 or 112SCA1 packs may exceed 50ms depending
on the combination of CFPs used in the 1830PSS and the client equipment CFPs.
Workaround:
Contact ALU customer support if these issues are encountered for recommended client
CFPs.
Issue #43274
When the 112SCX10 circuit pack is deprovisioned, the user actions log entry for this
operation incorrectly displays the lower slot number for the pack instead of the upper slot
number.
Workaround:
None required. This affects the log only and does not impact system behavior.
Issue #67637
If the 112SCA1 OT mode is changed from Regen to Add/Drop, transmission is affected.
Workaround:
Cold reboot of the 112SCA1 pack restores transmission.
Issue #98046
The Jumbo Packets are incorrectly binned in the 112SCX10 utilizing the Yahara A
device. Jumbo Packets are incorrectly binned at the Rx Drop Events Counter when the
Jumbo Packet length is less than 4100 bytes. In addition, when the Jumbo Packet length
is greater than or equal to 4100 bytes, the Tx side PM may not be accurate.
Workaround:
There is no impact in the transmission. Ignore the Rx Drop Event counter on the MAC
layer PM. All other MAC counters are working correctly.
Note: The last two digits of the ICS code will determine the Yahara type. The ICS code
is located on the lower tab of the card to the right of the ALU part number.
03 or lower = Yahara A device
04 or higher = Yahara B device

Issue #43973
Jumbo frames (MAC PDUs with size exceeding 1518 bytes) are also counted as
undersized frames and as a result, the Frame Error Ratio is calculated incorrectly when
jumbo frames are present in the bit stream.
Workaround:
The undersized frame count and Frame Error Ratio should be ignored in the presence of
jumbo frames in the bit stream.
Issue #51172
An incoming overclocked (11.096 Gbps or 11.049 Gbps) OTU2 service interface defect
(e.g., dLOS, DLOF, dLOM, or dOTU_TIM) is expected to produce ODU2-AIS at the
far-end egress port. However, the 112SCX10 currently generates an unframed signal
resulting in client equipment reporting LOF.
Workaround:
Provision the LOSPROP parameter as Laser Off for OTU2_11.096 and OTU2_11.049
signal types.
Issue #mh07323
If an incoming line side defect is detected by a 112SCA1/112SNA1 Regen with its Regen
Response set to "Laser Off", the system will report "Channel power unstable" against the
output port of the Regen. The alarm in this instance may be a false alarm.
Workaround:
If no upstream failure exists then the "Channel Power Unstable" alarm is not false.
Issue #mh07326
A transient Signal Degrade alarm may be reported after clearing signal defects on
112SCA1/112SNA1 pack with an OTU4 client signal.
Workaround:
None.
Issue #mh14856
When the 112SNA1 and 112SNX10 are provisioned in an OCHP/OLP/OMSP
configuration, the protection switching time may exceed 50ms.
Workaround
None.

Issue #mh09102
OCH protection switching using OPSA will sometimes exceed 100ms for 8GFC client
signals for 112SCX10 and 112SNX10 and cause temporary Fibre Channel switch
reconfiguration. There is no issue with 130SCX10 and 130SNX10.
Workaround:
None. For protection switching cases that exceed 100 ms time, the storage area network
will experience a temporary FC fabric reconfiguration typically lasting only a second or
two. No additional action is needed.
260SCX2
The following issue is related to the 260SCX2 pack.
Issue #PSSKPL-195
When the 260SCX2 OT is set up for a REGEN application and OTU4x2 mode is
changed to OTU4 mode, the Regen Response, "LaserOff" may turn off the line-side laser.
Workaround:
Perform a warm reset on the 260SCX2 pack.
Transmission
The following issues are related to transmission.
Issue #PSSKPL-140
If the upstream NE has an RA2P and bi-directional LD (ALPHG, AHPHG, AHPLG,
A2325A), the hitless firmware upgrade of the LD will impact transmission. In this case,
OSC loss will trigger APR which will recover on its own in less than 2 minutes. Other
amplifier combinations have an improved APR trigger that will not suffer an outage
during FPGA update of the LD card.
Workaround:
None. Transmission is impacted for less time if a hitless upgrade is done versus a cold
reboot of the LD.
Issue #mh06267
The WR8-88A and WR8-88AF packs may retrieve an unwanted "INV" port when
executing the SHOW and CONFIG interface CLI commands.
Workaround:
None. There is no service impact by retrieving this "INV" port.

Issue #mh35736
When OCHKEYDUP alarm is raised because of duplicate wave keys on two channels
within the same node, the OCHKEYDUP alarm may not clear when one of the cross-
connects is deleted.
Workaround:
Avoid using duplicate wave keys within the same NE. If the alarm does not clear,
perform a warm reset on the active EC to clear the alarm.
Issue #mh25354
When the 11QPA4 is provisioned with 10GbE traffic with GFP-F encapsulation mode, if
there is a LOS alarm raised against the client port when the pack is warm rebooting, the
traffic would not recover after the pack boots up if the LOS condition is cleared during
the pack warm reboot.
Workaround:
When using GFP-F encapsulation on 11QPA4, LOSPROP should be set to LASERON to
avoid this problem.
Issue #mh06160
Changing Wavetracker usage to "off" on TOADMs or ROADMs could cause
transmission interruptions.
Workaround:
Keep wavetracker usage set to "On" or "Inferred" on TOADMs or ROADMs when there
are services present.
Issue #mh16831
After LSP creation or restoration over a ROADM connection block, performing a path
power trace may reveal that some WR ADDIN ports are expecting the wrong channel
power (a very low dBm value like -95.00).
Workaround:
For each ADDIN port reporting the wrong value, locate the upstream ingress amplifier
and perform an ingress power adjust. Once all the adjusts are complete, repeat the path
power trace to verify that the expected power values have been corrected.

Issue #mh14638
In some cases, the power levels in the power trace for WR8-88A MeshOut and AddIn
ports may appear to indicate a small amount of gain or larger than expected loss between
these two ports. This results from the inaccuracies of the inferred power, and should not be
a source of concern.
Workaround:
None.
Issue #mh16852
When the SIG port of OPS pack is disconnected, the power management state of the SIG
port will revert to "ManualUndetermined". If a subsequent topological connection is made
to an OT or some other topologies, that connected topology will become
ManualUndetermined. This is not an issue if another port in the topology is already set
manually.
Workaround:
Re-connection of any desired topological links. After disconnecting the SIG port of an
OPS, the OPS card/slot should be de-provision and re-provision using the following steps
to ensure correct behavior on a subsequent re-connection.
1. Disconnect all ports of the OPS card
2. Turn the slot and ports admin down
3. Configure the slot as empty
4. Re-provision the slot with the correct OPS cardtype
5. Re-provisioning any OPS configuration
6. Re-connect any desired topological links.
WebUI
The following issues are related to the WebUI interface.
Issue #PSSKPL-74
The WebUI opens correctly with Java 7v55 or higher. However, when the graphical
physical topology window is issued, Java asks the user to provide login credentials.
Workaround:
Use Java8 or provide the credentials again.

Issue #mh36314
When the OT is provisioned with OPRMODE=REGEN, the REGENRESP parameter is
applicable to the 43SCX4, 43SCX4e, and 43SCA1 OT line ports. Currently, the
REGENRESP parameter cannot be provisioned via the CLI or WEBUI interfaces. The
default value of laseron is used.
Workaround:
None.
Issue #mh19711
HTTP user sessions are not terminated properly when the LAN connection between the
user and the node is lost.
Workaround:
Terminate unused HTTP sessions manually via WebUI >Administration > Security >
Sessions > Terminate option.
Note: Users should always logout of the WebUI session prior to closing the web browser.
Issue #18168
The login screen does not appear when connecting to the NE when some versions of Java
are installed.
Workaround:
If this occurs, verify the version of Java installed on the PC by going to the following url:
http://www.java.com/en/download/installed.jsp?detect=jre&try=1
If the page shows Java Version 6 Update 10 or later, perform the following steps.
1. Go to the Windows Control Panel (accessed via the Start button) and select Java.
2. The Java Control Panel window appears. Select the Advanced tab and expand the
Java Plug-in item.
3. Uncheck the option to enable next-generation Java plug-in and click OK.
4. The browser window must be restarted for this change to become effective.

CLI
The following issues are related to the CLI interface.
Issue #PSSKPL-181
The CLI "show xc <id> trace atoz" and "show xc <id> trace ztoa" commands result in an
incomplete lightpath trace when the source/destination cross-connect terminates on an
MVAC8B (used for alien channel transmission).
Workaround:
To get a complete lightpath trace using the CLI, log into each node along the lightpath
and get the trace for each node individually using the "show xc <id> trace" CLI
command.
Issue #PSSKPL-75
Using CLI, when AINS state is provsioned on a pack the following error is falsely
reported: "Error:invalid argument(s)".
Workaround:
None. Ignore the error. Provisioning will succeed. Alternatively, use the WebUI to
provision the AINS state.
Issue #59191
The user screen could hang while attempting to log out when multiple CLI (SSH)
sessions are logged into an encrypted mode NE. The user screen will remain hung until
the last CLI session is logged out.
Workaround:
Log out in the exact reverse order of creation to logout all CLI (SSH) sessions.
TL1
The following issues are related to the TL1 interface.
Issue #PSSKPL-202
When connected via TL1 over SSH, rtrv-status does not display the correct user IP
address. When connected via telnet, the correct user IP address is displayed.
Work-around:
None.

Issue #PSSKPL-201
The init-ssh-key, rtrv-ssh-key, and dlt-ssh-key TL1 commands are not available for TL1
over SSH. Therefore, TL1 cannot be used to retrieve, generate, or delete the SSH key for
TL1 over SSH.
Work-around:
Use the WebUI/CLI to retrieve, generate, or delete the SSH Key.
Issue #PSSKPL-36
The following TCM-related commands are not supported in TL1:
SET/RTRV-TH
SET/RTRV-THPRFL
SET/RTRV-THPRFL-NAME
Work-around:
Use the WebUI/CLI interface to execute these TCM-related commands.
Issue #mh35879
If RTRV-ATTR-ODU and RTRV-ATTRSUP-ODU commands are executed to retrieve
ODU conditions for all provisioned facilities with AID as 'ALL', conditions for 260SCX2
ODUk conditions are not displayed.
Workaround:
Use the RTRV-ATTR-ODU and RTRV-ATTRSUP-ODU TL1 commands with a specific
AID (Access Identifier) to retrieve list of ODU conditions for the ODUk facilities for
260SCX2 cards.
Issue #mh25778
PREFECBER and POSTFECBER parameters for OTUk facilities are not displayed in
TL1 interface.
Workaround:
Use WebUI or CLI on the packs that support this parameter.
Issue #mh18181
rtrv-pm-odunim and rtrv-pm-oduptf retrieves None for 24ANM, 4QPA8, and
11DPM12 packs.
Workaround:
CLI and WEBUI can be used to retrieve the PM data.

Issue #mh18174
RTRV-TH retrieves PM data when the facility is not provisioned.
Workaround:
PM data for unassigned facilities should be ignored.
Issue #78825
Using TL1, the ODU0INTERWK parameter for ODU1PTF is not retrieved and the AID
in the autonomous message is not correct.
Workaround:
Use the CLI Interface to retrieve the ODU0INTERWK parameter.
Issue #78770
When specifying the AID 11DPE12-<shelf>-<slot>-VA{1-2}, PM data for 11DPE12 VA
ports is not retrieved.
Workaround:
PM data can be retrieved for the VA ports of the 11DPE12 pack by entering the RTRV-
PM-OCH command without specifying the AID.
Issue #22187
The ENT-rr command does not support provisioning Timeslot and Primary State at the
same time for all OTs that support time slots.
Workaround:
Provision the Timeslot using ENT-rr and then modify the Primary State using ED-rr.
Protection
The following issues are related to the protection features.
Issue #mh22615
In a Y-cable protection configuration, with LOSPROP=LASEROFF, a stuck "Y-cable
switchover timer expired alarm may occur when there is an active switch condition and
the client signals on the protection and working packs are removed.
Workaround:
Warm reboot of the OT pack will clear the Y cable switchover timer expired alarm.

Issue #mh25940
On the 43STX4 a "Signal Failure" alarm may occur and not be cleared in a uni-
directional y-cable protection configuration . The alarm may be raised when there is a
line LOS on the working pack , all client signal are removed, and then subsequently
restored, and the line LOS clears.
Workaround:
A Warm reboot the pack is required to clear the alarm.
Issue #mh26046
On the 11STMM10, Y-CABLE-APS Channel Mismatch alarm (APSCM) is not reported
in revertive mode.
Workaround:
Other system alarms will be raised that may be used to detect the Channel Mismatch
condition (e.g. USALS, OPTL).
Issue #mh18111
Total power not shown for OPSA sig port.
Workaround:
None.
Issue #20265
A Switch Request is sometimes reported as a Reverse Request when it should be No
Request. All switching happens correctly. This will occur if on the near end (NE) of a
protected circuit if a force switch request is made to the protection path followed by a
signal failure (SF) on the far end (FE) of the protection path. When the SF on the FE is
cleared, the Switch Request on the NE will be Reverse Request instead of No
Request.
Workaround:
The Switch request will be reported correctly when another switch occurs.
Issue #79210
MN PWRTILTSUSP may not clear even when the local tilt setting matches that of the
OMS TX.
Workaround:
Toggling the power management setting for this line interface (e.g., auto > manual >
auto), should clear this alarm. On an ILA, if the alarm returns after toggling the power
management setting, a warm reset of the EC should clear it.

Issue #92635
Upon warm rebooting the OPSB pack, an "Automatic switch to Protection" or
"Automatic switch to working" condition is raised. This is a non-service affecting
condition.
Workaround:
None required. The condition will be cleared automatically.
Issue #mh05835
Protection switch occurs after EC card reinstalled if there is an existing manual switch on
OPSA (in OCHP/OMSP/OLP mode) A/B port and automatic switch performed while EC
card not present.
Workaround:
Any time after a manual switch is performed, release the manual switch request.
Issue #mh07097
When the 11STAR1A pack is provisioned in an OCHP/OLP configuration, the protection
switching time may exceed 50ms when the client port is provisioned to 8GFC, and FEC
mode with the line OTU2 rate is RSFEC.
Workaround:
Provision the FEC mode to EFEC.
Issue #mh03684
On an OLP-protected system: A critical condition, such as "OPS Input Loss of Signal"
alarm, at BOTH the A and B ports of the OPSA, will also cause a "LD Input LOS", but
incorrectly raised as a critical alarm.
On an OMSP-protected system: A critical "Loss of Signal" condition raised at the OPSA-
SIG In port, will also cause two "Outgoing Loss of signal" alarms, but incorrectly raised
as critical alarms.
Workaround:
None.
Issue #mh07095
When the 11QPA4 pack is provisioned in an OCHP/OLP/OMSP configuration, the
protection switching time may exceed 50ms when the client port is provisioned to
10GbE.
Workaround:
None.

Issue #mh07329
When cold restart is performed on the protection OT (112SCX10, 112SNX10 and
43SCX4E) in a Y-cable configuration, the near end working path may experience
transmission interruptions for up to 2 sec.
Workaround:
Disconnect the fibers on the protection path before cold restarting the OT.
Fault management
The following issues are related to the fault management (alarming) features.
Issue #mh17365
In the OMSP configuration, the severity of ingress LOS is incorrectly displayed as
critical instead of minor on the standby path.
Workaround:
None. The alarm will be cleared when path is restored.
Issue #20199
The time to clear a LAN LOS alarm is 15 seconds.
Workaround:
The alarm will clear autonomously.
Issue #61076
Power fluctuation (e.g., due to a fiber cut, an add/delete channel, pack cold reboot, or an
internal fiber handling) could result in Optical Intrusion alarms.
Workaround:
If the power fluctuation can be attributed to a known activity taking place in the network,
clear the Optical Intrusion alarms.
Issue #20326
The severity of port level EQPT conditions on the OT line port can not be provisioned.
Workaround:
The severity will remain at the default levels.
Issue #61994
On occasion, false Optical Intrusion Suspended alarms may occur.
Workaround:
None. These alarms will clear autonomously.

11STGE12
The following issues are related to the 11STGE12 circuit packs.
Issue #mh36311
Ethernet PM statistics, such as jabbers and CRC errors, reported on a 11STGE12 near-
end client port are not propogated to the 11STGE12 far-end client port.
Workaround:
None.
Issue #mh36312
Jabber packet injected into the near end client are correctly counted by the near end client
PM. However, they are not counted by the far end OT.
Workaround:
None.
Issue #mh36716
On 11STGE12 packs, T-CV-PCS TCA is not reported when the CV PM count crosses
the threshold value.
Workaround:
None.
Issue #18402
The 11STGE12 and 11STMM10 circuit packs may not perform optimally after
modifying the FECTYPE from EFEC2 to RSFEC.
Workaround:
Cold reboot the circuit packs before connecting a client signal if the FECTYPE is
changed from EFEC2 to RSFEC.
Issue #62054
After a cold reset of the 11STGE12, a TTI mismatch alarm may be raised.
Workaround:
After the cold reset, re-enter the new tx_sapi and exp_sapi values at both ends to
remove the TTI mismatch alarms.

Issue #17934
The LOM condition takes 45-75 seconds to clear instead of 10 seconds.
Workaround:
Wait for the LOM condition to clear.
Issue #33063
The LosProp parameter on the 11STGE12 does not work properly when interworking with the
1696 ROADM.
Workaround:
None.
Issue #18543
When the 11STGE12 is provisioned for auto-negotiation and the LOS Propagation is set
to LASER ON, the client side or line side defects will not result in a maintenance
signal (RF or all-0s in /C/ field) generated towards the client.
Workaround:
Configure LOS Propagation as LASER OFF if a fast trigger is needed to initiate client
protection. Without a maintenance signal transmitted as a result of server failure, client
equipment will need protocol timers to trigger re-routing.
Issue #83870
Traffic is not restored after Fault alarm (LOS/LSS) is being cleared during warm reboot
of 11STGE12.
Workaround:
Wait until warm reboot of 11STGE12 completes before clearing fault. If problem is
encountered, toggling auto-negotiation by CLI command will restore traffic.
Issue #83871
An OPS switch on uni-directional OPS protected 11STGE12 service will result in a
traffic hit at both ends of the service. The hit at one end is due to the OPS switch and is
expected. The hit at the other end is not expected but is much shorter in duration than the
hit caused by the OPS switch.
Workaround:
None.

Issue #46408
If power filter A is removed on a PSS-16 shelf, 11STGE12 circuit packs will experience
a short transmission hit (~200 msecs).
Workaround:
None.
11STMM10
The following issues are related to the 11STMM10 circuit packs.
Issue #mh36303
On the 11STMM10 pack, when a mismatched time slot is assigned on 1GbE port, only
the near end reports the FEPORTMISMATCH alarm. On far end, the ingress direction
reports "Loss of Synchronization" and egress direction reports "VCG Server Signal
Failure" alarm; FEPORTMISMATCH is not reported on the far end.
Workaround:
None.
Issue #22189
After a re-seat or cold restart an 11STMM10 OT, an OC48/STM16 port may experience
persistent B3 errors.
Workaround:
Re-seat or cold restart of 11STMM10 OT again.
Issue #18402
The 11STGE12 and 11STMM10 circuit packs may not perform optimally after
modifying the FECTYPE from EFEC2 to RSFEC.
Workaround:
Cold reboot the circuit packs before connecting a client signal if the FECTYPE is
changed from EFEC2 to RSFEC.
Issue #11577
When ports 7 or 8 on the 11STMM10 circuit pack are configured for OC48/STM16,
FC400, or CBR2G5 services, jitter generation may exceed the mask defined in ITU-T
G.825.
Workaround:
Use ports 1-6, 9 or 10 for OC48/STM16 or CBR2G5 services.

Issue #21920
A single bit error in 8B/10B stream may occasionally be counted as both an invalid code
and a disparity error resulting in increased PM coding violation counts on the
11STMM10 OT.
Workaround:
Note that the PM counts may be off.
Issue #22192
It is not possible to provision Timeslot for 11STMM10 using the TL1 interface while the
port is in OOS-MA,MT state.
Workaround:
Set the port to OOS-MA before provisioning Timeslot.
11STAR1(A)
The following issues are related to the 11STAR1 circuit packs.
Issue #17718
If the 11STAR1 is warm reset while in terminal loopback on the line port, a brief
transmission disruption on the looped signal may occur.
Workaround:
Repeat testing using loopback if a warm reset occurs.
Issue #17474
When TIMRESP (Trail Trace Identifier Mismatch Response) or PLMRESP (Payload Type
Mismatch) attributes are set to DISABLE, they incorrectly contribute to aTSF (aSSF) and
generate associated consequent action (such as aBDI or aAIS generation).
Workaround:
Match TTI fields on the connected OTN entities or disable TIM comparison using the
TRCCMP attribute to avoid consequent action based on dTIM. Match service types on the
end points and leave the default PT field code points to avoid consequent action based on
dPLM.
Issue #20201
In a Uni-directional protection configuration with Y-cable on all OTs supporting this
configuration, Signal Failure (SF) at the protection pack overrides the Force Switch.
Workaround:
None.

Issue #33506
There is a LAN PHY interoperability issue between the 11STAR1 and 43STX4 circuit packs.
When the 43STX4 generates GFP Client Management Frames, the 11STAR1 OT at the Far
End will report GFP User Payload Mismatch.
Workaround:
Use 10GbE LAN PHY rather than OTN at intermediate nodes when handing off to 43STX4.
Issue #83390
HIBER defect does not trigger the ES, SES of the 11STAR1A PCS PM when the pack is
provisioned for 10GbE traffic.
Workaround:
None.
Issue #83602
When 11STAR1A client is provisioned to OTU2 with rate 11.096 Gbps and there is no signal
input to the client during provisioning, the local line will transmit an abnormal AIS signal
which leads to a LOF on the far end line.
Workaround:
Connect a signal to the client port to clear client LOS. Subsequent client LOS events will
transmit the correct AIS signal.
Issue #92429
If 11STAR1A is provisioned with FECTYPE set to EFEC2, there is a minor chance that
under certain conditions, traffic will be impacted. The two ends will no longer be able to pass
traffic correctly.
Workaround:
Cold reboot 11STAR1A packs on both ends to recover. It is highly recommended to always
use FECTYPE=EFEC or RSFEC. The default setting for the 11STAR1A is EFEC.
Issue #96625
When 11STAR1A packs are provisioned with y-cable protection, and the traffic is switched
to protection line due to client LOS, the restore of the client signal may not clear the Signal
Failure status of the protection.
Workaround:
Warm reboot the protection pack at the far end.

Issue #mh09491
When the 11STAR1A pack with all ports in state UP is reseated, the client and line status
LEDs are turned off after the pack boots up.
Workaround:
Provision the primary state of client and line ports to out of service or maintenance prior
to reseating the 11STAR1A pack. Provision the ports to In service state after the pack boots
up, the status LEDs will be turned on.
11DPE12(A, E)
The following issues are related to the 11DPE12, 11DPE12E, and 11DPE12A circuit packs.
Issue #PSSKPL-228
When a XL-64TCW (zero chirp T-XFP) is provisioned on an 11DPE12A line port, the
Expected Network Output Power on VA port cannot be provisioned to a power level
greater than -5.5 dBm.
Workaround:
None.
Issue #PSSKPL-187
During a 11DPE12A pack warm reboot, there is LAG group traffic loss. The traffic will
recover after the reboot completes.
Workaround:
None.
Issue #PSSKPL-186
If LAG traffic on 11DPE12A packs is provisioned with a range of CVLAN ID, the
following issues may be observed:
1. Attaching a new client port to the related LAG group (maximum number of LAG ports
are four) causes traffic loss on the attached port.
2. LAG traffic may not recover after pack cold re-booting.
Workaround:
In a LAG configuration, if VTS Classification Mode is provisioned with "CE-VLAN
tagged", do not provision CVLAN ID with a range (example: do not provision 500~600
for CVLAN ID).

Issue #mh36668
When SyncE with SSM, or PTP clock is configured on 11DPE12A, an EC cold reset on
the upstream NE will cause Loss of Lock on the downstream NE for a few minutes.
Workaround:
Wait for a few minutes and the clock can be restored.
Issue #mh37279
When the PMON Policy type is provisioned to Two-Way LM, the provisioning of
Xn_FLR (Maximum Near-end Frame Loss Ratio) and Xf_FLR (Maximum Far-end
Frame Loss Ratio) will be denied and the error message Error: Request Failed C
Unsupported TCA id is reported. As a result, the related TCA alarms:
T_PMON_LMXNFLR_15MIN and T_PMON_LMXNFLR_1DAY,
T_PMON_LMXFFLR_15MIN and T_PMON_LMXFFLR_1DAY cannot be raised on
11DPE12A.
Workaround:
Provision aN_FLR and aF_FLR for Average Near-end Frame Loss Ratio and Average
Far-end Frame Loss Ratio respectively.
Issue #17921
When using FE port when switching from a line reference to another, on occasion, the
11DPE12A sync0 TIE will temporarily exceed the G.8262 specification during the ramp
phase, but it does not exceed 1000ns plateau.
Workaround:
Use GbE as sync0 lineref signal instead of FE.
Issue #68666
The 11DPE12 can drop packets for client ports with CIR provisioned to a value less than 100% of
the client signal data rate independent of the level of loading on the line.
Workaround:
Provision the CIR to 100% of the client signal data rate (100% = 1000 Mb/s for 1GbE)
on all client ports.

Issue #68663
When untagged packets or CEVLAN tagged packets come to the 11DPE12 client port, a
four-byte SVLAN will be added to those packets and sent to the line port. The four-byte
SVLAN will reduce the client port available bandwidth to less than 1Gbps and the line
port available bandwidth to less than 10 Gbps.
Workaround:
Keep the client ingress bandwidth less than 95% of 1 Gbs.
Issue #58271
Uni-directional traffic is not supported on the 11DPE12E circuit pack.
Workaround:
None.
Issue #67813
During green field set up, a false LOF alarm may be reported against the Line port with
valid input power.
Workaround:
Cold reboot the pack to clear the false alarm.
Issue #47102
When the 11DPE12 circuit pack is in QinQ mode, and the stream contains jumbo frames,
frame loss might be observed.
Workaround:
The sum of the CIR values for all flows transported by a line port should be less than or
equal to 8Gb/s to keep the utilization under 80% of the effective throughput.
Issue #47493
TCA alarms are not supported on the 11DPE12 circuit pack in QinQ mode when the line
type is 10GBE LAN.
Workaround:
Periodically review PM bins to identify if there is any quality of service degradation
requiring attention.

Issue #58267
When untagged packets or CEVLAN tagged packets come to the 11DPE12A or
11DPE12E client port, a four-byte SVLAN will be added to those packets and sent to the
line port. The four-byte SVLAN will reduce the client port available bandwidth to less
than 1Gbps and the line port available bandwidth to less than 10Gbps.
Workaround:
Keep the client ingress bandwidth less than 95% of 1Gbs.
Issue #59224
XFP (1AB375380005 JDSU JXPR01EMB83AL and 1AB375380007 JDSU
JXPR01LMB84AL) raises a port failure - device alarm on the 11DPE12E circuit pack
when it is inserted in the line port. This also causes other client port to port failures and
laser shut down, which will take down traffic.
Workaround:
Do not use XFP (1AB375380005 JDSU JXPR01EMB83AL and 1AB375380007 JDSU
JXPR01LMB84AL) on the 11DPE12E circuit pack.
Issue #61900
Auto Negotiation does not work on the electric 1GbE SFP (1000BASE-T) of the
11DPE12A or 11DPE12E pack.
Workaround:
Disable Auto Negotiation.
Issue #58263
11DPE12E will discard Ethernet Control frame with ETHTYPE equal to 0x8808.
Workaround:
None.
Issue #83992
When the 11DPE12 1GbE traffic automatically switches to the protection line of the
ESNCP due to a defect on the working line, warm reboot of the pack will cause packet
loss.
Workaround:
Make sure the working line defect is cleared before executing a warm reboot.

Issue #83991
On very rare occasions, a Pluggable Module Unknown alarm will be raised against the
11DPE12 when using the optical FE SFP. Traffic is not affected, however a warm reboot
will bring traffic down.
Workaround:
Reseat the module to clear the alarm.
Issue #97512
There may be 11DPE12A packet loss during the upgrade from previous releases.
Workaround:
None.
Issue #97960
When changing the 1588 topology, the 11DPE12A may lose its 1588 synchronization to
the 1588 master clock.
Workaround:
Cold reboot the 11DPE12A.
Issue #97513
After NE upgrade or pack cold reboot of the 11DPE12A, LAG actadmstate parameters
Aggregation, Lacpactivity and Lacptimeout may be changed to non-default value which
will cause the LAG ports to standby.
Workaround:
Delete the LAG ports and then re-attach the client ports to LAG groups with parameters
Aggregation as true, Lacpactivity as active, Lacptimeout as short.
Issue #97961
On occasion, when the ambient temperature is lower than 5 degree C, the 11DPE12A
ToD output port may not be usable for timing distribution.
Workaround:
Use the PTP port but not the ToD port for timing distribution.

Issue #98038
When 11DPE12A switches the frequency synchronous path from one 10GbE/OTU2 port
to another 10GbE/OTU2 port, SyncE performance exhibits a transient phase error of
several microseconds during switching, which exceeds the ITU-T G.8262 specification.
Workaround:
None.
Issue #94104
On a 11DPE12A pack when a Client Terminal Loopback is enabled at the far end NE, the
transmit power at the far end client port will be off.
Workaround:
None. For problem isolation start with client facility loopback and then enable client
terminal loopback.
Issue #mh21653
11DPE12, 11DPE12A, and 11DPE12E support a single priority level/CoS for user traffic.
Internally the software implements a prioritization scheme that assigns in-profile (<CIR)
traffic, co-called green frames, into a high priority queue and out-of-profile traffic
(<PIR but >CIR), so-called yellow frames into a lower priority queue. A SP (strict
priority) based scheduling algorithm is used to prioritize green/in-profile traffic. It is
strictly internal and not visible to the operator.
This prioritization is proprietary since according to IEEE 802.1Q standards, green and
yellow traffic for the same CoS should always be mapped to the same queue; then -
within a queue - color is used to determine which packet to drop first in case of
congestion.
However as a result of this proprietary prioritization, there exists a potential for mis-
ordering for a given conversation/flow.
Workaround:
To prevent mis-ordering, it is recommended to use strict policing with CIR = PIR (EIR =
0), thereby avoiding existence of yellow packets.

11DPM12
The following issues are related to the 11DPM12 circuit packs.
Issue #PSSKPL-238
If the 11DPM12 is provisioned for Y-cable configuration with FC400 signal and Client
LOS propagation set to laser OFF, traffic may not come up.
Workaround:
Set LOS propagation to laser ON to enable traffic. If required, LOS propagation may then
be provisioned to laser OFF.
Issue #PSSKPL-237
When the 11DPM12 is provisioned for Y-cable configuration with FC400 service, a
FDICLT (Forward Defect Indication Client Failure) will be unexpectedly reported on
the line port. Protection service and switching are not affected.
Workaround:
None.
Issue #PSSKPL-236
If the 11DPM12 y-cable protection group ID is provisioned to be greater than 65002, the
protection status may display unknown and protection switching may fail.
Workaround:
When using y-cable protection on 11DPM12 packs, ensure the protection group ID is less
than 65002.
Issue #PSSKPL-215
If the 11DPM12 ODU2 Payload Type is provisioned as a value other than 33 (0x21) or
32 (0x20), the received ODU2 structure is reported as null. Consequently, the client
traffic will not recover after an 11DPM12 pack cold reset.
Workaround:
Retain the ODU2 Payload Type default value of 33 (0x21) for the 1.25G timeslot
application, or 0x32 (0x20) for the 2.5G timeslot application.
Issue #PSSKPL-48
When a 11DPM12 pack is interworking with a 11DPM8 pack in end to end transmission,
and the signal type is FE, there will be an Outgoing Payload Mismatch Indication
ODU alarm reported on the 11DPM8.
Workaround:
None.

Issue #mh27191
The 11DPM12 pack low frequency jitter performance for SD-HDI/HD-SDI signals for an
11DPM12 cascade, with multiple OTU1 demap/map stages, can exceed SMPTE 259M
standards. This does not affect other client services including Ethernet, SONET/SDH,
and FiberChannel.
Workaround:
Minimize the number of 11DPM12 OTU1 de-map stages by using the 11DPM12 ADM
function.
Issue #78488
When the C3 port of the 11DPM12 pack works in optical FE mode, if the transmission
frame size is fixed to 9600 frames, there will be CRC errors reported.
Workaround:
None. However other ports on the 11DPM12 will work with this fixed frame size.
Issue #67817
Alarm severity is not de-escalated on a protection switch. This applies to both Y-cable
protection and E-SNCP.
Workaround:
None.
Issue #67816
On occasion, with a bi-direction and non-revertive Y-cable configuration, the remote
protection status cannot recover from "Reverse Request" to "No Request" when the
request status of the local protection line goes from "signal failure" to "No Request".
Workaround:
Clear the switch on the remote protection group.
Issue #67815
On occasion, during green field setup, a false LSS (Loss of Synchronization) alarm may
be raised against the 11DPE12 line port when it is provisioned to 10GbE LAN.
Workaround:
Cold reboot the pack to clear LSS alarm.

Issue #78774
The far-end LOF reported at the client Tx port will not be suppressed when the Line Port
detects the failures (e.g. LOS/LOF/ODU2-AIS) in the receiving direction, under the
following conditions, and the client Tx alarms will be reported together with the Line Rx
alarms.
1. When the card is rebooted with Line failures, the suppression does not work until
there is a valid Line signal input.
2. The alarm suppression does not work for the optsg mapped STM-1/STM-4, OC-3/
OC-12 clients in the cascading path.
3. The alarm suppression may not work when the ODU cross-connection is not set up.
Workaround:
None.
Issue #58275
The Ethernet Port Activity LED is always off and does not reflect the status of Ethernet
transmission.
Workaround:
None.
Issue #61893
On occasion, during a cold reboot, or line port state transitions, an OTU2 LOF/LOM/SD
alarm may be raised against the line port when the 11DPM12 OTU2 FEC type is
provisioned to EFEC2.
Workaround:
Change the FEC type to RSFEC then change back to EFEC2 to clear the OTU2
LOF/LOM/SD alarm.
Issue #61894
An LOS-P alarm raised at line port2 will result in the GCC0 state of line port1 to go
down.
Workaround:
None. Alcatel-Lucent 1830 PSS does not support GCC0 on line port2. An attempt to
provision the line port2 GCC0 will be rejected by the NE with the message Error:
Unknown.

Issue #61896
Two types of XFPs (1AB375380005 and 1AB375380007) will raise a port failure alarm
on the 11DPM12 when it is inserted in the line port. The XFP insertion also causes other
client port to port failures and a laser shut down.
Workaround:
Do not use the two XFP types.
Issue #58274
The following Ethernet PM parameters are missing from the 1GbE PM report for the
11DPM12.
GbEth_CodeErrors // 8B/10B code errors (Gb Eth)
GbEth_DisparityErrors // 8B/10B disparity errors (Gb Eth)
Frame Length Rx Packet Counters
Frame Length Tx Packet Counters direction.
Workaround:
None.
Issue #62156
When the 11DPM12 has all ports provisioned, 15-minute and 1-day bin status is
incorrect. The bin status will show partial or long.
Workaround:
None. Ignore the status field.
Issue #62082
The SD-SDI/HD-SDI client interface is supported on 11DPM12 and 4DPA4. The
11DPM12 and 4DPA4 do not support the SD-SDI/HD-SDI pathological test pattern
defined in SMPTE RP178 when the following SFPs are used.
APN=1AB376370005 (SFP B&W Multirate 2.7 Gbps)
APN=1AB377160001 thru 1AB377160008 (SFP CWDM, Multirate 2.7Gbps, 40km)
APN=1AB377200001 thru 1AB377200008 (non-ETR) (SFP CWDM, Multirate
2.7Gpbs, 80km)
APN=1AB377200009 thru 1AB377200016 (ETR) (SFP CWDM, Multirate 2.7Gpbs,
80km)
Workaround:
None. The 11DPM12 and 4DPA4 support the SD-SDI/HD-SDI pathological test pattern
defined in SMPTE RP178 when the following SFPs are used.
APN=1AB300320001 (SFP CWDM, 3G-SDI-SH, 14Km)
APN=1AB300320002 (SFP CWDM, 3G-SDI-MH, 20Km)

Issue #94128
In occasion, Port failure device alarm will be raised against the line port of the
11DPM12 pack when unqualified XFP module is inserted even the Pluggable Module
Type is provisioned with User mode.
Workaround:
Use Alcatel-Lucent approved pluggable modules to avoid port failure alarm.
Issue #mh05933
For the 11DPM12 pack, when the flow rate exceeds the GCC bandwidth, there will be a
transient link down alarm against the GCC channel for less than 15 secs.
Workaround:
None. Keep the flow rate to be less than the GCC bandwidth.
Issue #mh06658
After upgrade from a previous release, the description of the existing alarms or events
against the Logical low level ODU port on the 11DPM12 pack will incorrectly be
displayed as "Defunct event 0x3a001003 in the NE system logs.
Workaround:
Export the system logs prior to software upgrade.
Issue #mh07965
When the 11DPM12 is provisioned for Y-cable configuration with OTU1 service and
LOS propagation set to laser off, a defect against both working and protection lines at the
near end will not cause laser shut down at the client port of the active path at the far end.
Workaround:
None.
112SDX11
The following issues are related to the 112SDX11 circuit packs.
Issue #PSSKPL-226
When establishing end-to-end DDR traffic on 112SDX11 packs and an LANLOS alarm
is raised on the upstream client port, an LSSEGR alarm will be raised incorrectly against
the downstream client port in place of the expected CSF-ODU alarm.
Workaround:
None.

Issue #PSSKPL-222
When provisioning the 112SDX11 L1 port for the first time, the CFP module type
(C113G4T) is correctly recognized on the L1 port, but may fail to synchronize on the L2-
L4 ports. Consequently, if the 112SDX11 pack is interworking with a MVAC8B pack,
warm rebooting the 112SDX11 pack changes the Expected Network Output Power on
the line port of the MVAC8B to the default value (-20dBm), which results in traffic
down.
Workaround:
If performing a green field installation, perform a warm reset of the 112SDX11 pack or
re-insert the CFP module to synchronize the CFP module on all four of the line ports.
If traffic is down due to the asynchronization of the CFP module type on the line ports,
manually change the Expected Network Output Power on the line port of the
MVAC8B to the expected value.
Issue #PSSKPL-210
When 112SDX11 packs are provisioned with 10GbE or 40GbE traffic, Ethernet PM
counts are incorrect.
Workaround:
None.
Issue #PSSKPL-208
Occasionaly, provisioning an 112SDX11 client port may cause a traffic hit on existing
traffic on other ports of the 112SDX11 pack.
Workaround:
None.
Issue #PSSKPL-189
When an 112SDX11 C11 port is provisioned with QSPF+ module, the creation of
ODUkXC between client and line port will fail if the module is absent from C11.
Workaround:
Before creating the ODUkXC, insert the QSFP+ pluggable module in C11 port.

Issue #PSSKPL-188
After an 112SDX11 pack cold boots, the LOODUk DM value will be abnormal (Current
Value: 0, Current Status: Invalid).
Workaround:
Change the DM Attributes (Connection Monitoring End Point Mode) to Bypass or
Destination and then change back to Source.
Issue #PSSKPL-184
The Dual Rate 40GBE-LR4 QSFP+ (1AB392040002) module cannot be recognized as
Q40GLR4 on C11 port of an 112SDX11 pack. "Pluggable module unknown" alarm will
be reported on C11 port.
Workaround:
Provision the QSFP+ module in USER mode.
Issue #PSSKPL-44
When an ODUkXC is deleted at the far end, an unexpected LO-ODUk LOFLOM alarm
is raised incorrectly on the ODUflex entity of the near end 112SDX11 pack in place of
the expected LO-ODUk OCI alarm.
Workaround:
None.
Issue #PSSKPL-45
When the 112SDX11 is provisioned with OTU2e traffic, Egress TTI Status is incorrectly
displayed in the Non-Terminated ODU Settings in the following two scenarios involving
Ingress TTI Comparison settings:
When the Ingress TTI Comparison is enabled, the Egress TTI status reports
Mismatch or Normal even though the Egress TTI is Disabled.
When Ingress TTI Comparison is disabled, the Egress TTI status reports
Unspecified even though the Egress TTI Comparison is Enabled.
Workaround:
None.
Issue #PSSKPL-60
After re-provisioning any ODUkXC on a 112SDX11 card, a Data Error alarm may be
reported on the pack. Traffic is not affected.
Workaround:
Perform a warm reset on the 112SDX11 pack to clear the alarm.

Issue #PSSKPL-66
If the 112SDX11 is provisioned with the 40GbE QSFP+ traffic and the error rate reaches
7.0E-5, the PCS Rx PM on the C11 port stops counting.
Workaround:
None. If the error rate drops below 7.0E-5, the PCS Rx PM on the C11 port will resume
counting.
Issue #PSSKPL-70
Occasionally, retrieving ODU4 details (WebUI or CLI) will display an unexpected Rx
ODU even after deleting all the ODUkXC on both 112SDX11 packs of the end to end
traffic.
Workaround:
Re-establish the ODUkXC and the unexpected Rx ODU will be overwritten by the actual
Rx ODU.
Issue #PSSKPL-71
After establishing end to end DDR traffic on 112SDX11 packs and if there is a LANLOS
alarm raised on the upstream client port, the Tx SEFS_PCS on the downstream client port
will be 0.
Workaround:
None.
Issue #PSSKPL-72
When the 112SDX11 pack is provisioned with DDR or FC traffic, the LSS alarm
reported on the near-end client port will cause unexpected PLMODU-OUT (Outgoing
Payload Mismatch Indication ODU) or DEG (Outgoing Signal Degrade ODU) alarm
raised on the LoODUk entity of the far-end client port.
Workaround:
None.
Issue #PSSKPL-73
In very rare occasions, the 112SDX11 traffic is not recovered after a pack cold reset.
LOL, LOF, and signal degrade may be reported on the L1 line side interface.
Workaround:
Cold reset the 112SDX11 pack again.

Issue #PSSKPL-91
On occasion (3 out of 100 times), 112SDX11 OMSP protection switching times may be
greater than 100msecs if the 112SDX11 pack is provisioned with FC4G, FC8G or FC16G
signal type. If the client port is interoperated with Brocade switch, link_failure will be
reported on Brocade.
Workaround:
None.
40G Mux
The following issues are related to the 40G Mux circuit packs.
Issue #PSSKPL-52
The WebUI and CLI do not support the retrieval of PM data (15-MIN and 1-DAY bins)
for the 43STX4/43STX4P card.
Workaround:
Use the TL1 interface to retrieve PM data for the 43STX4/43STX4P card.
Use the CLI interface to retrieve "raw" PM data.
Issue #PSSKPL-53
TCA events FECC, FECUBC, BBE-OTU are not reported for 43STX4 Line ports.
Workaround:
None.
Issue #PSSKPL-76
When the 43SCX4E is provisioned for BITSYNC mapping, CSFODUEGR is not raised
on the far end pack when the near end has a client LOS. LOFEGR is raised at the far end
instead.
Workaround:
None. The 43SCX4E works correctly in ASYNC mapping. This issue is not seen on the
43SCX4.
Issue #mh36316
When a 43SCX4/4E pack is provisioned with a client rate of FC800 and a client facility
loopback is enabled, the pack exhibits loopback and cut behavior instead of the required
loopback and continue behavior.
Workaround:
None. The other 43SCX4/4E client rates exhibit the expected loopback and continue
behavior.

Issue #72735
A 40G Mux client port may on rare occasion falsely report PM OPR or OPT high/low
TCA messages.
Workaround:
As long as there are no associated transmission errors or alarm conditions, ignore the
TCA messages.
Issue #68513
10GLAN client on 43SCX4E, 112SCX10, and 112SNX10 do not report TX PCS error
counts.
Workaround:
None.
Issue #68514
Initial provisioning of the 43SCX4 or 112SCX10 OTU2 client from RSFEC/EFEC to
EFEC2 fectype sometimes does not work correctly.
Workaround:
Deprovision/reprovision the OTU2 client or toggle the OTU rate (10.709/11.049/11.096).
Issue #72186
After initiating a cold reboot or reseating a 43STX4 or 43STX4P pack, it may not
successfully boot if a 'card unknown' or 'Add Power Control Failure' alarm is reported.
Workaround:
Before initiating a cold reboot or reseating the pack, make sure the fan speed is set to
maximum and all empty slots on the shelf are filled up with slot blanks.
Issue #61591
Warm reboot of a 43STX4/43STX4P OT may cause PM PCS ES/SES count to be set
to 1. There is no transmission hit.
Workaround:
Disregard and clear the PCS count after warm reboot.
Issue #32226
When High BER is detected in the ingress direction of the 43STX4 card and the client
signal is provisioned to 10GBE, the HIBER alarm is not raised.
Workaround:
None.

Issue #32466
When Errored Frame Drop Mode is Enabled, the 43STX4 records all the received packets
except errored frames. Errored frames are only recorded as error packets, so the value of
Rx Error Ratio in PM report could be inaccurate.
Workaround:
The correct Rx Error Ratio can be calculated using the following formula:
(errored packets+undersized packets)/received packets
Issue #32971
When 10GbE LAN PHY packets with an IPG (Inter Packet Gap) set to 12 are received as
a tributary on a 43STX4 circuit pack, some packets may be dropped when using the GFP-
P (semi-transparent) mapping.
Workaround:
To avoid dropped packets, use the standard mapping, GFP-F.
Issue #41115
When using 40G MUX OTs (43STX4 and 43STX4P) in Y-Cable regenerator
applications (with back-to-back 40G Mux OT's), bi-direction protection is not supported.
Workaround:
None.
Issue #41314
A cold reset of the 43STX4 circuit pack sometimes causes an unexpected LOF condition
to be reported on one of the client ports.
Workaround:
Repeat the cold reset to clear the LOF.
Issue #63111
During a 43SCX4 pack reboot, a transient EQPTBOOT "Card failure - boot failure"
alarm may be raised.
Workaround:
None. These transient alarms will automatically clear after the pack is rebooted.

Issue #83245
'PreFEC Signal Degrade' or 'PostFEC Signal Degrade' may be reported on the 43STX4P
line port after a cold reboot of the pack.
Workaround:
Cold reboot the pack again. If the condition is still not cleared, de-provision and re-
provision the pack.
Issue #83244
"APS Channel Mismatch" condition may be reported after a manual switch is performed
on a Y-cable protection group.
Workaround:
Cold reboot the 43STX4/43STX4P pack.
Issue #83276
If LOS propagation is set to laser off, ODU2 OCI and LCK egress defects invokes
consequent action on OTU2 ports of 40G muxponders (43SCX4, 43SCX4e) causing a
non transparent ODU2 OCI, LCK maintenance signal.
Workaround:
Keep LOS propagation as laser ON.
Issue #83667
For cases where a service is between 10AN10/43SCUP and a 43SCX4/4E, a STM-64
client LOS on the 10AN10 will result in an ODU-BDI coming from the far end
43SCX4/4E.
Workaround:
None.
Issue #92644
43SCX4/43SCX4E packs may raise a card boot failure alarm when inserting or re-seating
the pack.
Workaround:
None. The condition clears automatically.

Issue #92637
The WebUI and CLI do not support the retrieval of the power trace for an end-to-end
connection involving 43SCX4/43SCX4E in Regen and re-coloring configuration.
Workaround:
Either use PhM to retrieve the entire power trace or use the WebUI or CLI to retrieve the
power trace for each NE.
40G add/drop
The following issues are related to the 40G add/drop circuit packs.
Issue #PSSKPL-49
43STA1P client port AINS timer is not working.
Workaround:
Do not provision the AINS timer on the 43STA1P client port.
Issue #mh36318
When the payload type on a 43SCGE1 is configured with a value other than the default
value (0x21), traffic is not error free.
Workaround:
None.
Issue #mh06843
Retrieval of the AINS timer status during countdown may return incorrect values if the
system timer and pack timer are provisioned to different values.
Workaround:
None. Timer function is counting correctly.
Issue #38834
During the receiver optimization process of the 43STA1P, the client output signal will
toggle between the AIS-L and LOF.
Workaround:
When the receiver optimization is complete, the client output signal will be correct.

Issue #39149
If the laser propagation is provisioned as Laser On and there is a client failure such as
LOF, the PM parameters TX ESS, TX SESS and TX SEFSS on the downstream
transponder will incorrectly increment.
Workaround:
None.
Issue #39150
When there is a client signal failure and the 1-byte J0 trace is being used, the J0 value
will be reported as 63 when it should be reported as ???.
Workaround:
Ignore J0 when there is a client signal failure.
4DPA4
The following issues are related to the 4DPA4 circuit packs.
Issue #PSSKPL-185
When 4DPA4 packs are provisioned with y-cable protection, a Pluggable Module
missing (REPLUNITMISSMOD) alarm on the client port will not trigger traffic
switching.
Workaround:
None.
Issue #72551
When there is a Line LOS on the OT line port of a 4DPA4 pack, EGRESS alarms for the
STM4, 1GBE, FC100 signal rates on the upstream node are suppressed.
Workaround:
Check the downstream line ports and client ports for related conditions.
Issue #38309
When the 4DPA4 is in DualTran card mode and there is LOS/LOF/LOM, there is no line
PM data available. All counts show 0.
Workaround:
Ignore the line DW PM data when the client signal type is FC400.

Issue #38843
When the eVOA is in the DOWN state, it reports a value for received power when it
should report no value in this state.
Workaround:
Ignore the received power values when the eVOA is in the DOWN state.
Issue #38941
When the 4DPA4 is in DualTran card mode, it will not report an OTU1 BDI condition
when the downstream circuit pack has an OTU1 LOS-P/LOF alarm.
Workaround:
Check the upstream circuit pack for other alarms that may explain the downstream
condition.
Issue #39120
When an FC400 client signal is provisioned, the 4DPA4 will not report LANLSS alarms.
Workaround:
If transmission is not functioning, use trouble clearing procedures to verify the correct
client input.
Issue #35263
When the incoming and expected trail trace does not match, the Trail Trace Mismatch
alarm is not reported for FC400 signals.
Workaround:
None.
Issue #41117
Sometimes after a cold reset of the 4DPA4 in DualTran mode, an LOF alarm is raised
and cleared.
Workaround:
None required. The LOF alarm will clear autonomously.
Issue #41118
When the 4DPA4 is in DualTran mode with LANLOS, the far end node may see a
toggling LANLOS alarm.
Workaround:
Disregard the toggling alarm.

4DPA2
The following issues are related to the 4DPA2 circuit pack.
Issue #83601
On occasion, the 4DPA2 ESNCP may show a switch status of Signal Failure instead of
No Request.
Workaround:
Warm reboot the 4DPA2 pack to clear the Signal Failure Switch Status.
11QPA4
The following issues are related to the 11QPA4 circuit pack.
Issue #PSSKPL-239
TL1 support for managing PM thresholds on TCM instances is limited.
Workaround:
Use WebUI or CLI t o manage thresholds for TCM-based PM points.
Issue #PSSKPL-204
Occasionally, after a EC warm reboot, it may take ~30 minutes for an NE to report
11QPA4(A) alarms.
Workaround:
None.
Issue #PSSKPL-196
A TIMTCM (Trail Identifier Mismatch TCM) alarm that is declared against TCM4-BM
on a 11QPA4 pack cannot be cleared.
Workaround:
None.
Issue #PSSKPL-193
The severity of LTCTCM (Loss Of Tandem Connection TCM) on 11QPA4(A) cannot
be changed.
Workaround:
None.

Issue #mh36669
When 11QPA4/4A is provisioned with E-SNCP group, the delay measurement function
may not work on the protection line in below two scenarios:
1. The ESNCP is created for the first time.
2. Change the encapsulation mode when the 11QPA4/4A is provisioned with
10GbEtraffic.
Workaround:
Exchange source and destination CMEPMODE (Connection Monitoring End Point
Mode) on the protection line ports.
Issue #78494
If the 11QPA4 is provisioned for OTU2 traffic, the FEC type is EFEC2, the line rate is
10.709, and the LosP is provisioned to OFF at both ends of point-to-point traffic, an LOS
alarm raised at near end client may cause LOF alarm to be reported against the same NE.
When the line rate is 11.049 or 11.096, an LOS alarm raised at the near end client may
cause an LOF alarm to be reported against far end NE line port, regardless of the setting
of LosP.
Workaround:
Clear the LOS or provision the FEC type to EFEC or RSFEC, and then back to EFEC2 to
clear the LOF.
Issue #58679
During a cold reboot, or client/line port state transitions, an OTU2 LOF/PLM/SD/OCI
alarm may occasionally be raised against the 11QPA4 or 11QPA4A line port when the
OTU2 FEC type is provisioned to EFEC2.
Workaround:
To clear the OTU2 PLM/SD/OCI alarm, change the FEC type to RSFEC and then change
the FEC type back to EFEC2.
To clear the OTU2 LOF alarm, cold reboot the pack.
Issue #70588
When the 11QPA4 is provisioned for 10GbE LAN traffic and Jumbo frames are
transmitted, the PM count of Tx Jabbers is incremented.
Workaround:
Ignore this incorrect PM reading.

Issue #58820
On rare occasions, when an 11QPA4 is configured as cross-regen using AFEC (EFEC2)
and the client side fiber is disconnected or the signal is lost, transmission may not recover
when the signal is restored.
Workaround:
Use EFEC or G.709 FEC in cross-regen mode.
Issue #61596
Manual, forced, or automatic protection switch time for the 11QPA4 in OMSP
configuration, with 8G FC client is around 200 ms.
Workaround:
None.
Issue #67820
The 11QPA4 experiences a laser transient on insertion. This can effect existing traffic,
especially a Y-cable configuration.
Workaround:
Before inserting an 11QPA4 verify that the line and client ports are not fibered. Fiber the
ports after the pack completes initialization.
Issue #48003
When an 11QPA4 circuit pack is configured to regenerate an 11DPE12 circuit, and the
FEC type is changed from EFEC2 to EFEC; error-free transmission may not be restored.
Workaround:
Use the following procedure to change the FEC type in this configuration:
1. Set the port status to OOS on the line side of the 11QPA4 and 11DPE12.
2. Change the FEC type
3. Set the port status to IS on the line side of 11QPA4 and 11DPE12.
If this procedure is used, error-free transmission will be restored.

If the above procedure is not followed, and the problem has occurred, cold reboot both
11DPE12 OTs. Error-free transmission will be restored.

Issue #83715
11QPA4 Line Port is configured with RS-FEC mode and DWDM XFPs, and the client
port is configured as OC192 or STM-64 mode. When the upstream OT toggles the
mapping mode between Bit-Synch mapping mode to Asynch mapping mode, there is a
possibility that the downstream 11QPA4 Line Port may not recover from hit introduced
by the mapping mode change. FEC Signal Degrade or LOF alarm may be reported on the
11QPA4 Line Port.
Workaround:
Before changing the mapping mode or changing the FEC mode (from EFEC to RSFEC)
of the 11QPA4 Line Port, first provision the Line Port to Down. When all the OT cards
are provisioned, provision the line port states to Up.
Issue #94108
The client terminal loopback is not error free when the 11QPA4(A) is provisioned for
Infiniband DDR traffic.
Workaround:
In order to perform client terminal loopback use another (non DDR) signal type.
Issue #72103
When a shelf is equipped with only 11QPA4/11QPA4A packs, if the WT oscillator
module on the power filter fails, the WT timing will be protected by automatically
switching to backup PF, but PF module failure alarm is not reported.
Workaround:
None.
Issue #mh07720
On occasion, for the 11QPA4 pack, a warning message 'OPRL tidemark Threshold
Crossing detection' may be incorrectly raised against the line port with a received power
within normal range.
Workaround:
None. Retrieve the PM value for OPR and if this is within range, ignore the warning
message. There is no traffic impact. The warning message will clear in the next PM bin.

11QPEN4
The following issues are related to the 11QPEN4 circuit packs.

Issue #PSSKPL-206
If a Terminal Loopback is deprovisioned on 11QPEN4 Line port and the client port is
configured as 10GbE, traffic may not recover.
Workaround:
Perform a warm reset on the card.
Issue #PSSKPL-164
If an NE is in SDH mode with the Encryption Threshold Alert configured to a non-zero
value, the alarm appears as expected if this Encryption Threshold is crossed. However,
the alarm does not clear when the PM bins roll over.
Workaround:
Perform a warm reset on the card to clear all Threshold Alerts.
Issue #mh36234
Rolling encryption keys while there is a line side loopback can result in a loss of traffic
and key mismatch alarms when the loopback is removed.
Workaround:
Do not roll keys while there is any kind of loopback in the network between 11QPEN4
line ports. This includes both electrical and optical loopbacks. Ensure KMT automatic
key provisioning is disabled before creating any loopbacks between 11QPEN4 line ports.
If keys are mismatched after the loopback is removed, attempt to restore traffic by rolling
the service to new encryption keys. If this is not successful, then disable and re-enable
encryption with new keys. Putting the client ports admin state down before disabling
encryption will ensure traffic is not sent plaintext on the line.
Issue #83766
The system accepts more than 16 characters in the provisioning of WKAT but only uses
the first 16 characters.
Workaround:
Do not type in more than 16 characters into the WKAT. If you do, reprovision it to only
have 16 characters.

Issue #93590
When an 11QPEN4/11QPA4 10G FC client is connected to a Brocade switch and the
client LOS Propagation is set to LaserOff, traffic cannot be established through the
network.
Workaround:
Set the client LOS Propagation to LaserOn.
Issue #93484
When using Y-cable APS groups on 11QPEN4 ports, SF switching conditions detected
due to a line-side signal failure can become stuck in the APS group. After the line-side
failure is cleared the APS group will continue to report a SF condition against the
previously failed line. This will prevent manual switches and revertive switches from
occurring, but it will not block future switches due to signal failures, forced switches or
lockouts of protection.
Workaround:
To clear the stuck SF, operate a forced switch towards the currently active side and then
clear the switch.
11QPE24/11OPE8/11QCE12X
The following issues are related to the 11QPE24, 11OPE8, and/or 11QCE12X circuit packs. If
an issue applies to all packs, the pack names are not mentioned in the issue description. If an
issue applies to a subset of the packs, the packs names are included in the issue description.
Issue #PSSKPL-218
When an EC redundancy switch occurs, there is a small probability (about 3%) of an
unexpected packet card reset, which is traffic affecting.
Workaround:
None.
Issue #PSSKPL-205
When a TIM/TIMODU alarm is raised on an 11OPE8/11QCE12X X port, a
BDI/BDIODU indication is not sent to the upstream peer OTU2 port, and expected the
BDI/BDIODU conditions are not raised on the upstream port.
Workaround:
None.

Issue #PSSKPL-179
When RSFEC is provisioned on an 11QPE24 X port and line BER reaches 1e-8, error
correction may gradually stop working, causing uncorrected errors and BER degrade
alarms.
Workaround:
To clear the condition, create LOS on X port Rx for a few seconds (for example by
toggling peer X port Admin State).
To avoid the condition, use EFEC/EFEC2 instead of RSFEC.
Issue #PSSKPL-177
After an 11QCE12X reset (warm, cold or power reset) there is a small probability (about
3%) of a card initialization failure. The failure is indicated by the CONTCOM (Card
failure - communication) alarm. In this state, the card will not pass traffic.
Workaround:
Peform the following steps to clear the CONTCOM alarm. Continue to the next step if
the previous step does not clear the CONTCOM alarm.
1. Perform a warm reset of the card.
2. Perform a cold reset of the card.
3. Reseat the card.
4. Replace the card.
Issue #PSSKPL-175
A PSS Equipment Controller card could reset during a MIB synchronization if both of the
following conditions are true.
1. One of the data cards (11QPE24, 11OPE8, or 11QCE12X) is operationally disabled.
2. There are a large number of static entries in the FDB.
VPLS and SAP service show commands could experience a 2-3 minute delay prior to
displaying results.
Workaround:
Ensure all data cards are operationally enabled during a MIB synchronization and the
number of static entries in the FDB should be limited to 100.

Issue #PSSKPL-172
When a provisioned 11QPE24 port wavelength (e.g. 1310nm, 1550nm, 850nm etc) does
not match the wavelength in the present SFP/XFP inventory, the expected
MISMATCHMOD alarm is not raised.
Workaround:
Ensure that provisioned the 11QPE24 port wavelength matches the wavelength in the
present SFP/XFP inventory.
Issue #PSSKPL-169
Upon warm/cold reset, the PACKETCARDINIT alarm is cleared up to 3 mins before the
card is completely initialized and able to carry traffic.
Workaround:
None.
Issue #PSSKPL-168
If RSFEC is configured on a packet card X port, and the BER is gradually reduced after
having reached a peak uncorrected rate of 1e-3, the normal line performance may not
restore until the error rate is reduced to about 1 error per second or less.
Workaround:
Create LOS condition on X port for a few seconds (for example toggle the peer line X
port Admin state), or use EFEC instead of RSFEC.
Issue #PSSKPL-167
The DATAERR alarm may be seen on 11OPE8 during the EC switch operation. In this
case existing traffic is not affected, but new traffic cannot be provisioned.
Workaround:
Warm reset the 11OPE8 pack to clear the DATAERR alarm. This is service affecting and
should be scheduled accordingly.
Issue #PSSKPL-163
During maintenance procedures like software upgrade, database restore, etc or any
maintenance activity that causes an 11QPE24, 11OPE8, or 11QCE12X card to reset,
inaccurate extra alarms could be generated after the procedure is complete.
Workaround:
Compare system alarms before and after maintenance procedure.
If an additional alarm is present, admin down and up the service to clear the alarm.
This procedure might be traffic impacting depending on which alarm is present.

Issue #PSSKPL-162
When retrieving igmp-snooping information on a service, in case there are more than a
hundred igmp dynamic or static groups, or igmp sources, the user interface response time
may be slow.
Workaround:
None.
Issue #PSSKPL-159
When Facility Loopback is activated on an 11QCE12X Mate port, a packet drop of up to
1% may occur. The problem does not occur for Terminal loopback.
Workaround:
None. Packet loss at this low level (around 1%) seen with Facility Loopback on a Mate
port does not indicate a problem with the card, with no corresponding packet loss when
the loopback is disabled. (Higher rates of packet loss could indicate a problem on one of
the cards or the backplane.)
Issue #PSSKPL-158
When a TIMODU alarm is raised on 11QCE12X X port, an unexpected LANLSS alarm
is also raised.
Workaround:
None. Ignore the LANLSS alarm.
Issue #PSSKPL-157
When MISMATCHMOD, UNKNOWNMOD, EQPTPORT alarms are raised on a packet
card X port, the expected URU-OUT condition is not raised which may lead an operator
to create a GMRE service using a packet card port that is inoperable.
Workaround:
Do not create a GMRE service while MISMATCHMOD, UNKNOWNMOD or
EQPTPORT alarm is active.
Issue #PSSKPL-156
During a card warm reset, the expected URU-S condition is not raised which may lead an
operator to create a GMRE service using a packet card that is inoperable.
Workaround:
Do not create a GMRE service while PACKETCARDINIT alarm is active.

Issue #PSSKPL-155
Some data is missing from the analog TCA messages:
TCA warning in conditions list does not indicate the threshold value, baselined value, or
current register value
TCA log in logs list does not indicate the parameter register, threshold value, baselined
value, or current register value
TCA traps do not show the baselined value
Workaround:
Use CLI to retrieve the threshold value, baselined value, and/or current register value. For
example:
show profile pm opr 8 tca
show interface 11ope8 1/10/x1 pm opr baseline
show interface 11ope8 1/10/x1 pm opr 0 0
Issue #PSSKPL-154
When there is no valid signal at the Rx of an 11QPE24 or 11QCE12X 1GbE/FE
electrical port, LINKDOWN is raised instead of the expected LANLOS.
Workaround:
None. In this case, LINKDOWN can be considered equivalent to LANLOS.
Issue #PSSKPL-152
When an 11OPE8 or 11QCE12X port is set Admin Down, an unexpected NR NSA
condition MODOUTOOR "Modulator output power out of range" may be raised.
Workaround:
None. Ignore the MODOUTOOR condition.
Issue #PSSKPL-151
When LOS/LOF/LOM alarms are raised on an 11QPE24 X port, the expected SSF
condition is not raised.
Workaround:
None.

Issue #PSSKPL-150
The field for IfInOctets and IfOutOctets in PMON Port statistics in the 1 day bin
sometimes rollover when large amounts of traffic are sent in one day. The rollover can be
noted by the presence of a ~ in the field.
Workaround:
If this is seen, the entire value should be disregarded as it is not accurate. Refer to the
values in the PMON SAP statistics as they are accurate and will not rollover.
Issue #PSSKPL-146
When an 11QPE24 port is Admin Down, an unexpected LASEREOL condition may be
raised.
Workaround:
None. Ignore the LASEREOL condition.
Issue #PSSKPL-143
When the analog PM is manually baselined, an unexpected OPRH (Optical Power
Receive High) 15Min and 1Day TCA may be reported.
Workaround:
None. Ignore the TCA.
Issue #PSSKPL-134
When 11QCE12X ports C11 or C12 are provisioned as 1GbE/FE and VOA SFP is
inserted by mistake, an unexpected REPLUNITMISSING alarm is raised instead of
expected UNKNOWNMOD, and the inventory shows all entries for this SFP as "empty"
for both C and VOA ports.
Workaround:
None. In this cas, REPLUNITMISSING indicated that inserted module does not match
provisioned port type.
Issue #PSSKPL-108
When a client facility loopback is activated on an 11QCE12X client port that is
provisioned as optical FE, a permanent packet drop of up to 10% will occur. This
problem does not occur for any other type of loopback or for any other rates.
Workaround:
If possible based on network configuration and other services, use line terminal loopback
or use physical fiber loopback for testing.

Issue #PSSKPL-88
Dropped packets are not reported in SAP PMON statistics.
Workaround:
To see if packets are being discarded, either use WebUI to expand the 11QPE24 pack and
select Service > VPLS, <Service-id> > SAPs, <SAP-ID> > Details or use the CLI
command: show card <card-type> <shelf/slot> service id <id> sap <sap> detail.
Issue #PSSKPL-51
In an E-Tree configuration, some customer ports (leaves) in the same vpls service are
configured in the same Split Horizon Group for traffic isolation. It is possible to
configure an UPMEP on only one leaf port in an E-Tree VPLS.
Workaround:
Configure one UPMEP on only one of the leaf ports in an E-Tree.
Issue #PSSKPL-33
If an 11OPE8 M port is associated with a SyncE Line Reference, setting loopbacks on M
port may disrupt system synchronization causing packet loss on other ports of the card.
Workaround:
If an 11OPE8 M port is associated with a SyncE Line Reference, do not set up loopbacks
on M port. If loopback is already set up, remove loopback to return to normal operation.
Issue #PSSKPL-30
For the 11QPE24 card, an unexpected Server Signal Failure (SSF) alarm is raised along
with an expected Trail Identifier Mismatch (TIM) alarm.
Workaround:
None. Ignore the unexpected SSF alarm. The unexpected SSF alarm will clear when the
TIM alarm clears.
Issue #PSSKPL-28
For 11OPE8 and 11QPE24 cards, BDI alarms may not clear.
Workaround:
Perform a warm reset on the card to clear the alarm.

Issue #PSSKPL-22
For an 11OPE8 card, when Remarking is disabled while using VPLS svc-sap-type
"any", C-vlan pbits are changed according through which forwarding class that they are
passing through. Original C-vlan pbits are not preserved. For an 11QPE24 card, C-VLAN
pbits are preserved and are not dependant on the forwarding class they are passing
through.
Workaround:
None.
Issue #PSSKPL-15
Beginning in 7.0.1, packet cards support a maximum 63 MAC/IP/IPV6 match criteria per
QoS SAP Ingress policy. In the event that a total 64 match criteria entries were
configured in an earlier release, the 64th entry will be rejected by the EC every time the
card is rebooted.
Workaround:
Remove the extra entry to ensure that there are no more than 63 match criteria per policy.
Issue #PSSKPL-12
Depending on the card (11QPE24/11OPE8/11QCE12X) and port type used (C or X),
UNI port shut-down, as consequent action of LLF notification, results in different alarms.
If the card is 11QPE24 and the port that is shut-down by LLF is a C port, the alarms are
LINKDOWN and LASEREOL.
If the card is 11QPE24 and the port that is shut-down by LLF is a X port, there is no
alarm.
If the card is 11OPE8 and the port that is shut-down by LLF is a C port, the alarms are
MODOUTOOR and LASEREOL.
If the card is 11OPE8 and the port that is shut-down by LLF is a X port, the alarms are
LANLFI, MODOUTOOR and LASEREOL.
If the card is 11QCE12X and the port that is shut-down by LLF is a C port, the alarms are
LINKDOWN and MODOUTOOR.
If the card is 11QCE12X and the port that is shut-down by LLF is a X port, the alarm is
LANLFI.
Workaround:
None.

Issue #PSSKPL-10
For igmp-snooping, VPLS and SAP configured parameters are not displayed in CLI or
WebUI.
Workaround:
If in doubt about the configuration, use CLI or WebUI to set configuration parameters to
the expected/required values.
Issue #mh38193
If an ERP system using L2 cards is converted from CCM-managed state to a PHY-
managed state, meaning that the ERP links will monitor the port state rather than the
MEP state, the paths will not recover properly and will remain down.
Workaround:
Shutdown all facility meps that are part of the ERP topology and have been set to a PHY-
managed state. Re-enable the facility meps using the no shutdown command.
Issue #mh28521
CFM PDUs are not terminated by passive side of meps. If the CFM is misconfigured, it
will be detected by the next active side of a mep which will report either an ErrorCCM or
XconCCM defect, if CCM transmission is enabled.
Workaround:
None.
Issue #mh32826
When EFM is enabled on a port, if the discovery process does not complete, a "Link
Down" alarm is raised and traffic is lost. There is no alarm for Discovery Not Complete.
Workaround:
To recover traffic, check the operational state of the port with EFM enabled at both ends
of the link. If it is operationally down, disable EFM on both peers and verify that traffic
has been recovered.
Issue #mh33368
For a setup where there is an OTU2 link between 11QPE24 and 11QPA4 line ports, the
OTU2 link will NOT be operational until 11QPA4 client receives a valid Ethernet signal.
Workaround:
Make sure the 11PQA4 client port is physically connected and receives a valid Ethernet
signal.

Issue #mh36397
Proactive SLM PM has the following limitations:
During a period of high frame loss, occasionally a minimum FLR of zero is reported.
During a period of no frame loss, occasionally a nonzero FLR is reported.
Workaround:
None.
Issue #mh37258
A warm/cold reset on a SROS packet card (example, 11QPE24) will temporarily
interrupt Layer 2 service/traffic on the card.
Workaround:
None.
Issue #mh37194
The ITU-T G.8021 unexpected priority defect (dUNPr) is not displayed and is not raised
as an alarm. The configuration of different priorities for CCM at different MEPs
belonging to the same MEG cannot be detected.
Workaround:
Check the CCM priority for every MEP of the same MEG.
Issue #mh37274
Photonic cross-connection supporting L2 service can be deleted while L2 service (SAP)
is still provisioned on a port associated with the cross-connection.
Workaround:
Do not delete a Photonic Cross-Connection having L2 SAPs provisioned on a port
associated with the cross-connection. First, delete all L2 SAPs, and then delete the cross-
connection.
Issue #mh13220
When a CFM MEP is created on an RMD with ccm-interval different from the local peer
MEP, LOC and RDI alarms might be periodically raised and cleared.
Workaround:
Both MEPs should be configured with the same ccm-interval.

Issue #mh06663
For the 11QPE24 cards, LAG statistics correctly report incoming number of bytes on a
LAG, incoming number of packets on a LAG, outgoing number of bytes on a LAG, yet
are missing outgoing number of packet on a LAG.
Workaround:
Use statistics on the LAG peer device (incoming number of packets on LAG port).
SVAC/MVAC
The following issues are related to the SVAC or MVAC circuit packs.
Issue #32626
It is possible to get a power spike on the line if an SVAC circuit pack is cold rebooted.
Workaround:
Before cold rebooting an SVAC circuit pack or a single shelf containing an SVAC,
remove the fiber patch to the C1 input of the SVAC. Re-insert the fiber after the pack
completes booting.
Issue #57431
It is possible to get a power spike on the line if an MVAC circuit pack is cold rebooted.
Workaround:
Before cold rebooting an MVAC circuit pack or a single shelf containing an MVAC,
remove the fiber patch to the C1 input of the MVAC. Re-insert the fiber after the pack
completes booting.
Issue #83102
With WTD usage set to WT-OCM, for any external topology provisioned to a cls port of
a CWR8-88 pack, the power trace at the cls input port of CWR8-88 is missing.
Workaround:
None.
Issue #84369
When MVAC8B is OPS protected, incorrect service activity information is displayed.
Workaround:
None.

Issue #94122
Alien EGR LOS is reported with Critical severity against the line port of MVAC8B when
a uni-directional cross-connection is created.
Workaround:
Do not create uni-directional cross-connection against MVAC8B.
Issue #mh14736
OPTL Threshold alarm is not raised for SVAC Line port.
Workaround:
None.
Issue #mh14734
When the SVAC Line port state is changed to state down, the PM OPTL is not displaying
as "-40.00", instead it is showing the same OPT value.
Workaround:
The OPT value will display properly when the line port is changed to state up.
Amplifiers
The following issues are related to the amplifiers.
Issue #PSSKPL-142
When using CLI or WebUI, a preprovisioned OSC SFP will display a false Pluggable
Module Temperature reading.
Workaround:
None. When an actual Pluggable Module is installed, the temperature reading will display
correctly.
Issue #PSSKPL-69
When an A4PSWG or A2P2125 LD card undergoes a warm reset, the APRUNAVAIL
alarm is raised against both the LineIn and LineOut ports. The alarm should be raised
only against the LineIn port. There is no impact on transmission.
Workaround:
None. The alarm will clear automatically at both ports when the reboot is completed.

Issue #PSSKPL-58
Disabling APR in ILAs will fail with the following error message: "Error:
AprEnable/Disable not applicable to the requested Amplifier".
Workaround:
None. Do not disable APR at ILAs.
Issue #mh06666
URU-S alarms may be raised incorrectly against LDs in place of the expected URU-
OTS-LOS, URU-OTS-RX, or URU-OTS-TX alarms.
Workaround:
None. These are derived conditions/alarms that do not affect NE functions.
Issue #mh26823
If there has been an OSC data link down condition in a system for a long period of time,
users could experience a slow response from the system, and ingress or egress
adjustments may fail.
Workaround:
Clear the OSC data link down condition and then warm reset the LD that had data link
down condition.
Issue #mh35108
Unlike those for bi-directional LDs, the OSC OPT PM values for uni-directional LDs are
not calibrated to the fiber span line interfaces, and may not represent the values and states
of the OSC transmitted onto the line interfaces. These OSC OPT PM values for uni-
directional LDs are from the OSCSFPs of the mating cards. If a fiber jumper between the
cards is disconnected or broken, the actual OSC power transmitted onto the line would
be "nil", even though OSC OPT reports normal powers. For AM2625A with an integral
OSC amplifier, the OSC OPT values are related to the input levels (e.g., 1.5 dBm) to the
OSC amplifier, not to the output levels (e.g., 11.0 dBm) transmitted onto the line.
Note: Bi-directional LDs include: AHPHG, AHPLG, ALPHG, and A2325A Uni-
directional LDs include: AM2125A, AM2125B, AM2318A, A2P2125A, AM2032A and
AM2625A
Workaround:
None for binned values. The current values can be retrieved via CLI "show interface
<shelf>/<slot>/Lineout details" under "Supvy Out Power".

Issue #mh25931
Under some rare conditions, during the scheduled or manual ingress gain adjustment on
a TOADM or ROADM that is equipped with bidirectional LDs and has 80+ channels,
users may experience delayed responses from the system.
Workaround:
None. Transmission is not affected, and the system performance returns to normal when
the ingress gain adjustment completes.
Issue #mh47077
Cards are shown in-service (admin and operation state UP) during card initialization.
Workaround:
Wait for card initialization alarm to clear before retrieving the card status.
Issue #67821
For A2325A, AHPHG, AHPLG, there may be a less than 100 second inaccuracy during
the 1-day accumulation periods.
Workaround:
None.
Issue #68129
If a two-or-more-degree TOADM did not have a through channel and did not go through
ASE commissioning, the DCM-Out target power will not be set. As a result, false OPR
alarms may be raised.
Workaround:
Add a temporary through channel and run egress adjust to set the DCM-Out target.
Issue #58115
In-service ingress and egress power adjustments on RA2P and AM2125 packs may
produce erroneous results if services have not yet been provisioned.
Workaround:
Do not execute in-service power adjustments until there are channels on the RA2P and
AM2125 packs.

Issue #58822
When the RA2P pumps are off due to APR, any input LOS alarm may not be cleared.
When the RA2P pumps are on, input LOS will not be detected.
Workaround:
This issue only impacts alarm reporting. When pumps are off, the Raman gain is 0. If
the total input power level is -31dBm or higher, the LOS should have been cleared.
When pumps are on, use signal input power less Raman gain to estimate the input level.
A value less than -34dBm would indicate input LOS.
Issue #78828
The channel power levels at bidirectional egress LD input port are inferred from the
egress LD DCM port, and these inferred values may not be accurate when span tilt is set
to a non-zero value.
However, when span tilt is set to a non-zero value, the channel power levels at the egress
unidirectional LD input port will be correctly inferred from the egress unidirectional LD
output port.
Workaround:
None.
Issue #58980
Typically, if there is a channel collision from upsteam, a USOCHCOLLISION condition
is raised at LineIn and masks subsequent alarms on the same. On a uni-directional LD,
USOCHCOLLISION is not detected at LineIn. As a result, critical alarm
OCHCOLLISION-OUT may be raised at LineOut due to upstream channel absent.
Workaround:
Check upstream NE to see if there is a similar condition raised.

Issue #mh16947
When setting the id VOA Initial, if the Mid EVOA Initial is less than current Mid EVOA
Minimum Attenuation, or greater than the current Mid EVOA Maximum Attenuation, the
following the error message: The initial mid voa loss is not within a valid range.
Workaround:
The following manual steps can be started from the Web UI - Power Commissioning
setting page:
1. Set the "Mid EVOA Minimum Attenuation" to the lesser of (current "Mid EVOA
Minimum Attenuation", new "Mid EVOA Minimum Attenuation", current "Mid
EVOA Initial Loss").
2. Set the "Mid EVOA Maximum Attenuation" to the greater of (current 'Mid EVOA
Maximum Attenuation', new 'Mid EVOA Maximum Attenuation', current 'initial mid-
VOA loss')
3. Set new "Mid EVOA Initial Loss", then set new "Mid EVOA Minimum Attenuation",
and new "Mid EVOA Maximum Attenuation"
Note: For CPB, use the same workaround then select Retry.
WTOCM/WTOCMA
The following issues are related to the wavelength tracker optical channel monitor circuit packs
and the WTOCM/WTOCMA pack that supports OSNR measurements.
Issue #PSSKPL-19
In a FOADM with thru channels, monitored with OCM with power manager type set to
manual, power trace for thru channels does not show measured power for an egress
amplifier.
Workaround:
None if the network requires WTOCM monitoring.
If the network has been equipped with WTOCM but does not require the OCM for
channel monitoring, embedded WT channel monitoring can be used by setting wtdusage
mode to WTDonon. Check the EPT design to determine if the embedded WT channel
monitoring is acceptable.
Issue #48359
When a tilt adjustment is suspended due to a fiber cut between the WTOCM port and the
line driver, multiple alarms are raised.
Workaround:
None. The alarms will clear when the fiber cut is restored.

PTPCTL
The following issues are related to the PTPCTL circuit packs.
Issue #mh17348
During a warm reboot of the PTPCTL, the PTPCTL switches to free-running and stops
sending SSM messages. The adjacent node raises an alarm, "'All selectable timing
reference fail".
Workaround:
If QL (SSM) is enabled in the adjacent nodes, the node will switch to the secondary
timing reference. After the warm reboot of the PTPCTL has completed and the alarm
clears, the adjacent node will switch back to the primary timing reference.
Issue#mh17069
The output of 1PPS signal may have +/-60ns in variation.
Workaround:
None.
Issue #mh17913
On occasion, the cold reboot of EC may cause the warm reboot of the PTPCTL card.
During the course of the PTPCTL warm reboot, it will stop sending SyncE SSM and PTP
packets.
Workaround:
None. SyncE SSM and PTP transmission will resume upon completion of the warm
reboot process.
Performance monitoring
The following issues are related to performance monitoring.
Issue #PSSKPL-180
Occasionally, in the initial 1-day bin for OPIN PM, the Minimum value may not be
reported (left blank).
Workaround:
None.

Issue #PSSKPL-139
After toggling the maintenance mode of the port with the TCA(s), a stuck TCA may
persist after the alarm condition that caused the TCA has cleared.
Workaround:
Perform a warm reset on the pack to clear any stuck TCAs.
Issue #PSSKPL-133
EC CPU PM values for average CPU usage, heap usage, and pool usgage are unavailable
("0" displayed).
Workaround:
None. Ignore this PM category.
Issue #mh33108
Occasionally, when line interface bidirectional LDs detect LOS, the Raw Bin and Current
Bin will not display PM data for optical power for line-in and optical power for line-out.
Workaround:
None.
Issue #mh17973
Code Violation (CV) TCAs are not supported for the FE, DVBASI and SDR signal types.
Workaround:
None. Code violations are counted and binned for FE, DVBASI and SDR signal types
and can be retrieved via user interfaces.
Issue #93588
When an 11QPEN4/11QPA4 10G FC client is connected to a Brocade switch, false PCS
PMs can be continuously counted against the port. The affected PMs are ES_PCS,
SES_PCS and SEFS_PCS. This can result in TCA events and alarms being raised if the
PMs cross the provisioned threshold. There is no impact to traffic.
Workaround:
There is no workaround to prevent the PMs. The TCA events and alarms can be
prevented by setting the thresholds for these PMs to 0.

Issue #78829
The reported interface group PM values on OSC AIDs may not be accurate.
Workaround:
None.
Issue #78830
On uni-directional LDs, false large surges in values can be observed in OPIN PM at
LINEIN, especially during initial service provisioning.
Workaround:
None.
Issue #78831
On OSC AIDs, SONET far-end Line PMs or SDH far-end MS PMs are reported at the
near-end NE. These PM values may not match those retrieved on the far-end NE.
Workaround:
Ignore values reported in the far-end PM group.
Issue #28847
The default CV-PCS TCA threshold for FC1 and FC2 is incorrectly set to 1125.
Workaround:
Manually set the TCA for FC1 to 96 and FC2 to 121.
Issue #32283
The PM counters Rx Undersized Packets is incremented when undersized packets are
received on the client ports of the 43STX4 but Rx Octets is not incremented.
Workaround:
None.
Issue #59136
After power cycling the NE, some TCA related notifications may have a 70/01/01
timestamp.
Workaround:
A warm reboot of the NE will correct the timestamps.

Commissioning
The following issues are related to the commissioning of Alcatel-Lucent 1830 PSS.
Issue #PSSKPL-138
When deleting an Egress AdjustPoint that is not on the THRU path, power adjustment
could fail with the following error: "Unable to complete request. Error: Topology
provisioning is incomplete".
Workaround:
Perform a warm reset the EC.
Issue #68169
When provisioning 11QPA4/11DPE12 topological connections, if the connection
between the line tx port and Va port is provisioned last, the Tx frequency gets set to
9590.
Workaround:
Provision the topological connection between the line tx port and the va port first. Then
the Tx frequency stays at NONE.
Issue #48480
DCM power does not get set correctly if a 2-degree node with an A2325A egress
amplifier is brought up without any THRU service.
Workaround:
Add a THRU service and then run an egress adjustment.
Issue #62058
Loss values in the loss report may not be correct if auto ingress gain adjust is enabled
during greenfield commissioning.
Workaround:
Disable auto ingress adjust during greenfield commissioning.
Issue #59203
Sometimes power adjustments can not run on an ILA after the DCM topology has
changed.
Workaround:
Change the power management mode to manual before changing the DCM topology.
Then change the power management mode back to auto.

Security
The following issues are related to security on Alcatel-Lucent 1830 PSS.
Issue #67825
Client IP address in SNMP log is always 127.0.0.1.
Workaround:
None.
Software upgrade, backup, and restore

The following issues are related to software upgrades, backups, and restores on Alcatel-Lucent
1830 PSS.
Issue #PSSKPL-211
Beginning in R7.0, the GCC termination provisioning model was modified from Port-
based to NETIF-based instances. During an upgrade from an earlier release, a Port-based
GCC "Data Link down" is raised and this alarm remains orphaned in R7.0.x and cannot
be cleared.
Workaround:
During software upgrades prior to the activation of the new SW release, all GCC related
"Data Link down" alarms must be cleared. Perform upgrades for NEs hosting GCC
terminations in a sequential manner; activate one NE at a time, not simultaneously. The
SW upgrade of the peer NE hosting the far end GCC termination must be fully completed
and "Data link down" alarms must be cleared on the local NE before starting the SW
activation on the local NE.
Issue #PSSKPL-171
During the activation phase of an upgrade, packet cards are reset to activate the new
software load (which is traffic affecting). However, the expected PACKETCARDINIT
alarm is not raised.
Workaround:
None.
Issue #mh36233
The hardware settings on 11QPA4 line cards are not updated when a database restore
operation is executed. The card will maintain the provisioning established before the
database restore. As the database is properly restored, the information presented via the
user interfaces may not align with the actual provisioning on the cards.
Workaround:
After the database restore operation completes, cold reset the affected cards to apply the
actual provisioning.

Issue #mh37261
During a software upgrade, the software warm re-boot during the software activation
process of a SROS packet card (example, 11QPE24 or 11OPE8) will temporarily
interrupt Layer 2 service/traffic on the card.
Workaround:
None.
Issue #mh24795
The in-service upgrade activate operation may clear the event historical log.
Workaround:
Before attempting an in-service upgrade, use the Log File Transfer operation to save the
event historical log.
Issue #mh25298
Shelf addition to existing multishelf NE requires special procedure in case the intershelf
cabling rules have not been obeyed. In case the installation of the intershelf cabling did
not follow the ES2 > ES1 rule (as depicted in customer documentation) but implemented
a reversed ES1 > ES2 scheme the newly inserted shelf might not boot up as expected.
Workaround:
Contact TEC to inquire how to correct the shelf cabling.
Issue #58757
The software download abort operation is not supported.
Workaround:
None.
Issue #61902
After an upgrade from a previous release with 11QPA4 E-SNCP when traffic is on the
protection line, traffic could be lost.
Workaround:
Prior to the upgrade, switch the 11QPA4 traffic to the working line. After the upgrade,
clear any alarms (e.g., LOF, SD, PLM) on the protection line by toggling the FEC /
Payload type on the protection line at both ends. If a standing LOF alarm on the
protection line still exists, perform a cold reboot of the packs at both ends to clear the
LOF.

Issue #48044
If both WebUI and PhM sessions are open to a remote node via GCC, a software
download initiated from one of the interfaces will not succeed.
Workaround:
Make sure only one WebUI or PhM session is open when executing a remote software
download to a node. After initiating the software download, close the session. Log in
later to check the status.
Issue #78785
During the activate phase of software upgrade, MVAC, WTOCM, 11DPM12, and
11DPE12E cards may fail to reboot and load the new software. A Card unknown alarm
may be raised about 30 minutes later and a Software upgrade failed alarm may be
raised after that. Transmission is not affected but the cards will not report new alarms,
provide power readings.
Workaround:
Warm reboot MVAC, WTOCM, and 11DPE12E cards reporting Card unknown (CLI
command config card sh/sl reset warm). Allow 7 or 8 minutes for the cards to boot and
Card unknown to clear. If the Software upgrade failed alarm was raised, repeat the
audit, download, and activate steps for the software upgrade (these steps will execute
quickly since the software is already loaded). Upgrade the card firmware to prevent the
problem from re-occurring for future software upgrades. Refer to the Firmware
management procedures.
Issue #48764
Occasionally, software downloads executed from PhM via GCC to 1830 PSS may fail.
Workaround:
Retry the download using PhM. Alternatively, use WebUI or CLI to initiate the software
download.
Issue #48766
A Data link down alarm may be reported and cleared over the GCC link during high
bandwidth data transfers.
Workaround:
The alarm will clear autonomously.

Issue #82135
In a single shelf NE with redundant ECs, sometimes software activation status will be
reported as complete even though the standby EC hasnt completely booted up in the new
software load.
Workaround:
Wait for the standby EC to come up. It will come up about 10 minutes after activation
completed.
Issue #81442
During NE software upgrade or EC/System reset the RNE may raise DBINVALID alarm
and the visibility from the DCN will be lost.
Workaround:
Database restore operation should be done via Master Active EC CIT port.
External Raman amplifier

The following issues are related to the external Raman amplifier on Alcatel-Lucent 1830 PSS.
Issue #39580
The external Raman/EDFA booster craft terminal may not start from a remote network
element (RNE) ports E1/E2 if the MTU setting on the PC is 1500.
Workaround:
Set the PC MTU size to 1491 or lower.
GMPLS
The following issues are related to GMPLS on Alcatel-Lucent 1830 PSS.
Issue #PSSKPL-56
EC may indicate not Ready to Protect if Active EC was cold reset while DB backup
operation was in progress and interrupted. Further DB backup requests will be successful
with temporary shut down and restart of GMRE applications during backup, as long as
EC is not Ready to Protect.
Workaround:
Perform a warm reset on the Standby EC.

Issue #PSSKPL-57
If the backup route did not already carry other light paths and an Ingress Power Adjust
Required alarm is raised because power management was suspended, traffic restoration
may take up to hour.
Workaround:
To avoid automatic power adjustment delays, it is recommended to permanently occupy
paths with a test or pilot light path.
Issue #PSSKPL-98
The 43SCX4E pack is not fully transparent in regen mode for all OTN functionality and
interop configurations with the 43SCUP are impacted. In an interop configuration,
GMRE cannot be used to set up services.
Workaround:
None.
Issue #mh35903
After cold or warm reset of node, the GMRE may report "Control plane degraded" to
1350 OMS.
Workaround:
Perform a warm reset on the Main EC.
Issue #mh36342
Cold boot of 130SCUP or 130SCUPB card in PSS-36/PSS-64 may lead to ASONTOPO
being raised against CWR8-88 or SFD on PSS-16/PSS-32. The 130SCUP and
130SCUPB cards cold boot automatically during PSS-36/64 in-service software
upgrades.
Workaround:
Clear the ASONTOPO fault.

Issue #mh26319
During LSP creation or restoration, there is a remote possibility that Wavelength Tracker
keys may not get fully propagated to all network elements. In such cases, the OCh cross
connects display AZ and/or ZA keys as all-zeros (0,0). It is also likely that one or more
OCHUNKNOWN alarms will be raised, indicating which OCh is experiencing the
problem. Without proper keying, wavelength service cannot automatically power-
balance.
Workaround:
Rekey the OCh service at the source transmitter.
Issue #mh13275
For colored OTs in directionless configurations with subgroup width 100GHz, the next
and previous wavelengths to the nominal wavelength cannot be used for restoration with
wavelength change. This issue is applies to 43STA1P, 43STX4P, 112SCA1, 112SNA1 &
112SCX10.
Workaround:
In the combination of colored OT on one side and colorless OT on the other side with 3R
points in between, use a nominal wavelength on the colorless side of minimum distance
of 2 wavelengths from the colored side, or the same wavelength.
Issue #mh10250
If the safety switch of a unidirectional ingress amplifier is lifted to the "laser off"
position, the LSPs on that line may not restore, and there may not be an ASON alarm to
indicate the point of failure.
Workaround:
There will be other NE alarms raised as a consequence of the safety switch. . Refer to the
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Maintenance and Trouble-Clearing
Guide to locate and correct the failure. Use 1350 OMS to manually re-route LSPs over an
alternative path until the failure can be corrected.
Issue #74624
Network manager may experience temporary loss of connectivity to NE(s) when LSPs
are initially created or restored.
Workaround:
None.

Issue #mh12816
If an OMS line containing RAMAN amplifiers (RA2P, RA3P, or A2P2125) experiences
an intra-nodal fiber failure, the LSPs on that line may not restore, and there may not be an
ASONTOPO alarm to indicate the point of failure.
Workaround:
Other NE alarms are raised as a consequence of the intra-nodal fiber failure. Refer to the
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Maintenance and Trouble-Clearing
Guide to locate and correct the failure. Use 1350 OMS to manually re-route LSPs over an
alternative path until the failure can be corrected.
Issue #68365
40G LSP does not restore if fiber pulled on client side of 3R point involving back-to-back
43STA1P along the route.
Workaround:
When a CR SA LOS alarm appears on client side of 43STA1P, use 1350 OMS to move
LSP away from the 3R point.

Issues Restrictions
Restrictions
General
This section describes feature limitations, and some procedures that should be avoided because
they have undesired effects on the system.
Restriction: #PSSKPL-209
When an 11DPE12A pack is provisioned with 1GbE Y-cable protection, disable Auto
Negotiation on client ports.
In Release 7.0.0 and later, the EC auto upgrade is supported for the EC equipped with 16GB
flash memory modules (either EC APN = 8DG59241AD or field upgraded EC with 16G
capacity via upgrade kit APN = 8DG60968AA).
For the EC equipped with 4GB flash memory module (EC APN = 8DG59241AB with 4G
capacity), the auto upgrade is supported only if the EC is already loaded with the factory
load, Release 3.6.60, Release 5.1.x or later releases. The auto upgrade is not supported for
the EC with 4GB flash memory module if the EC is already loaded with the software releases
prior to Release 5.1.x.
43SCGE1, 130SCX10, 130SNX10, and 11QCUPC will not show pack LED status as SOLID
RED for card mismatch scenarios. There is no impact on the core functionality.
In a multi OSPF Area environment on an NE with greater than one OSC/GCC interfaces to
the same neighboring NE, the OSPF cost metric value on each of the OSC/GCC interfaces
should be set to the same value. In such multi OSPF Area environment or a backbone OSPF
Area environment (i.e. OSPF Area = 0) on an NE with a mix of both OSC & GCC interfaces
to the same neighboring NE, best performance is achieved if all GCC interfaces on both the
neighboring NEs are disabled/deleted.
On a 11DPE12A pack, when there is only one lag member in the LAG group, if the user
deleted the LAG member first, then the LAG VTSXC cannot be deleted. Delete the LAG
VTSXC first, then delete the LAG member.

Issues Restrictions
11QPE24/11OPE8/11QCE12X
This section describes situations that should be avoided as they have undesired effects on the
11QPE24/11OPE8/11QCE12X packs and the system.
Restriction #PSSKPL-20
Due to a hardware limitation on the 11OPE8 and 11QCE12X cards, when egress queues are
set in strict priority scheduling mode, egress traffic shaping on queues AF and L1 may be up
to ~10% inaccurate compared to the provisioned shaper CIR for traffic rates lower than 200
Mbps. There is no impact to the traffic flow.
1. For 11QPE24 1G ports, octets are only counted up to the MTU limit; any octets that cause
a packet to fail the MTU check are not counted. Even though packet counts are correct, if
there are too-long frames, the RX and total octet counts are less than expected.
2. For 11QPE24 10G ports, Ethernet Statistics etherStatsBroadcastPkts and
etherStatsMulticastPkts include errors, contrary to RFC 1759/2819.
3. For 11QPE24 10G ports Ethernet Statistics etherStatsPkts512to1023Octets and
etherStatsPkts1024to1518Octets do not count packets that match or exceed the MTU when
MTU is configured between 512 and 1514; instead any packets matching this condition are
counted in etherStatsPkts1518PlusOctets. If the configured MTU is at least 1515 then the
stats are correct.
4. For 11QPE24 10G ports, rx broadcast, multicast and unicast packets beyond the maximum
MTU size plus 8 are not counted. However, the number of errors, oversize packets, and too-
long frames are correct. In such scenarios, the number of input packets shown under Traffic
Statistics are incorrect because this number is the result of input packets minus input errors,
or just input packets if input errors is greater than input packets.
EFEC2 is not supported on 11OPE8 and 11QCE12X. Starting in R7.0.2, EPT designs will
not allow EFEC2 to be used for 11OPE8 and 11QCE12X. When upgrading from R7.0.1
where a 11OPE8 is configured with EFEC2, the value will be retained but should be changed
to a supported FEC during a maintenance window.

Issues Restrictions
The 1 GbE CWDM SFP can be used in the Smart cEDD but the WUP (Wrong Unit Present)
alarm is erroneously reported. The alarm should be ignored as it has no effect on operation.
The alarm can be suppressed on PSS to be not-reported.
Example command: config alm attr l2data 1/9/rmd19/customer/mau rmdifmau rmd-if-mau-
wup notreported
Where 1/9 shelf/slot, rmd19 configured rmd Id number = 19.
When upgrading from a R6.x release to a R7.x release, any EFM device discovered on a
11QPE24 card will not be recognized after the upgrade. The RMD ID Type appears as
UNKNOWN in the CLI output for command "show card sh/sl rmd". After the upgrade to 7.x,
EFM type RMD needs to be deleted and recreated.
Due to a hardware limitation on the 11QPE24, 11OPE8, and 11QCE12X cards, when packets
are received with MTU size greater than the configured Port MTU, they are correctly
dropped, but QoS meters still count their octets.
Due to a hardware limitation on the 11QPE24 cards, the "show ... mep ... remote-mepid" CLI
command does not function for down-meps.
If the configuration for 11QPE24 cards in a NE is changed, restoring a previous NE database
could result in configuration issues on 11QPE24 cards in the NE. These issues could
manifest themselves as ports that do not go in-service or traffic not flowing.
Fast Ethernet optical modules (100mbps) are supported on the 11QPE24 cards. For these
optical modules, the user is able to properly configure module_type parameter as "fe" (fast
ethernet). But for the same kind of modules, the user is also able (using both CLI and
WebUI) to configure module_type parameter as "1GbE" (gigabit ethernet) without an error
message. After the last (wrong) configuration, this module is managed by the system as a
gigabit Ethernet module instead of a fast ethernet module. In such condition, the user is able
to create configuration using ports with physical characteristics (speed) different from what
has been configured. (i.e. user is able to add a such kind of port in a LAG made by gigabit
ethernet modules). If a Fast Ethernet module is configured as gigabit ethernet, the user needs
to delete the module (unassigned) and configure it again using the proper module type.
Issues Restrictions
Restriction: #95949
If a mismatched optical signal is connected to the 11QPE24 Client port, such as a 100 Mb
FE to a 1 GE SFP, there may be no indication of the mismatch and the port appears to be in
service.

3 Software Installation and
Upgrade
Overview
Purpose
This chapter provides procedures to download and activate the Alcatel-Lucent 1830
Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 7.0.2 software on a new NE or
upgrade the software on an existing NE.
Alcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 7.0.2
includes two software load variants.
1830PSS-7.0-2 is supported on Alcatel-Lucent 1830 PSS-16/PSS-32 shelves.
This software load supports non-GMPLS photonic application only. The
equipment controllers with both 4G compact flash (8DG59241AB) and 16G
compact flash (8DG59241AD) are supported. Note: 112SDX11, 11OPE8,
11QCEX12, WR20-TFM, WTOCMF, OTDR, MCS8-16, ASWG, A4PSWG,
AAR-8A, and MSH8-FSM are not supported with this software load.
1830PSSECX-7.0-2 is supported on Alcatel-Lucent 1830 PSS-16/PSS-32 shelves.
This software load supports GMPLS control plane functionality and non-GMPLS
control plane functionality. The equipment controllers with 16G compact flash
(8DG59241AD) are required. Equipment controllers 8DG59241AB which have
been upgraded to a 16G compact flash can support this software load. Note:
11OPE8 is supported with this software load.

Software Installation and Upgrade Restrictions
Contents
This chapter contains the following topics:
New software installation general instruction 151
Software upgrade general instruction 163
CLI instructions 180
WebUI instructions 231
PhM instructions 266
Example configuration of ftp server 303
Firmware for Release 7.0.2 313
Firmware management procedures 338
Maintain current firmware 340
Normal firmware upgrade (cold reboot) 342
In-service (hitless) firmware upgrade for OT cards 344
In-service (hitless) firmware upgrade for LD cards 346
Firmware issues if upgrading from Release 3.6.58 to Release 7.0.2 via 348
Release 5.1.6
Firmware-related operations for reference 349

Software Installation and Upgrade New software installation general instruction
New software installation general instruction

Purpose
This section provides procedures to download and activate the Alcatel-Lucent 1830 Photonic
Service Switch 16/32 (PSS-16/PSS-32) Release 7.0 software on a new NE.
Note: Refer to the Alcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32)
Release 7.0 Installation and System Turn-Up Guide , for the complete turn-up and
commissioning procedures.
NOTICE
Service disruption hazard
These procedures should be completed on a new NE only. Existing provisioning on the NE

including any traffic will be lost.
Required materials
The following items are required:
Personal computer (PC) running Windows 2000, Windows 7, or Windows 8
Note: Windows XP computers will no longer receive automatic updates that help protect
personal information. Windows XP is not supported by 1830 PSS Release 7.0.2.
The following software should be loaded on the PC.
Internet Explorer 8.0, 9.0, or 11.0
The Internet Explorer 8.0 browser does not support launching JDSU viewer for
viewing OTDR scan results.
MAC OS 10.9 (with Firefox browser only)
Firefox through v30. The following WebUI functionality is not supported with the
Firefox browser:
o Show in separate window
o Export to Excel
o Launching JDSU viewer for viewing OTDR scan results
J2SE Java Runtime Environment (JRE) 5.0 thru 7u51.

Note: Although the WebUI application software is zero install, the user must
install JRE on the PC to allow the WebUI to run.
10/100 BaseT LAN card and a shielded RJ45 straight through cable.
Note: It is extremely important that the RJ45 cable be shielded. Unshielded RJ45 cables
do not provide adequate protection to the system hardware.
ESD wrist strap
Required change notices (CNs)

There are no required change notices published for this software release.
Precautions and recommendations

Be sure to read and understand the following:
Read the entire software installation procedure before beginning.
The person performing the software installation must be trained and have an
understanding of the Alcatel-Lucent 1830 PSS-16/PSS-32 system.
Perform the software installation procedure in the sequence provided; any deviation may
lead to unpredictable Alcatel-Lucent 1830 PSS-16/PSS-32 behavior.
If installing a GMPLS network with an active control plane, please refer to the Alcatel-
Lucent 1830 Photonic Service Switch (PSS) Release 7.0 GMPLS/GMRE Guide.
Use care when handling circuit packs.
Make use of ESD wrist straps and static-safe bags.
Notes
Please read the following note:
All of the graphics utilized in this section may not contain current release designations.
They are for reference only.
Preconditioning procedure
Follow this procedure to ensure that the NE has been installed as described in the Alcatel-
Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 7.0 Installation
and System Turn-Up Guide, and is ready for software installation.
1 Refer to the site documentation (i.e., network information report generated from the
planning tool) and verify that all circuit packs are present and slotted correctly. Verify
correct dispersion compensation modules and optical multiplexer/demultiplexer shelves
are installed.

2 Verify the fibers are dressed and run correctly between packs and to optical
multiplexer/demultiplexer and dispersion compensation modules. Verify any required
protection Y-cables are installed.
3 Check all power and electrical cabling to be sure they are run properly. If there are
multiple shelves, verify the cables are properly daisy-chained to the ES ports as described
in Chapter 4 (1830 PSS-16) and Chapter 7 (1830 PSS-32) of the Alcatel-Lucent 1830
Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 7.0 Installation and System
Turn-Up Guide and identify the master shelf.
4 Verify inventory cables are connected at the line driver or wavelength router
(CWR8/CWR8B and CWR8-88) packs and remain disconnected at the DCM, SFD44,
SFD44B, SFD40, SFD40B, ITLB, and ITLU units.
5 Verify the shelf is powered up. Make sure fan modules are installed properly and
fastened securely. Fully seat power filters if they are not engaged, and verify green led is
lit on both. Verify fans are running.
6 Fully seat all circuit packs in all shelves if they have not been seated except for any
redundant controllers as noted below.
Important! Verify the Part Number (APN) of all Equipment Controller (EC)
circuit packs on 1830 PSS-16/32 shelves.
8DG59241AD variant supports software version 1830PSSECX-7.0-2. This

particular EC contains a 16GB Compact Flash that supports GMPLS.
Upgraded 8DG59241AB variants to have 16G compact flash can support

1830PSSECX-7.0-2 software. By default, this variant comes with 4G compact
flash.
All other EC variants only support 1830PSS-7.0-2. 1830PSS-7.0-2 does not

support GMPLS.
Important! If any shelf is to be configured in a duplex (redundant controller)

configuration (for example, EC circuit packs equipped in slots 1&18 on PSS-32
shelves and slots 2&12 on PSS-16 shelves):

1. All EC circuit packs must be either 8DG59241AB or 8DG59241AD. Both

variations are allowed to co-exist within a network element.
2. On the master shelf, ensure the standby EC circuit pack remains unseated (slot 12
for PSS-16 and slot 18 for PSS-32). The standby EC may be inserted anytime
after the Release 7.0 software is committed.
Important! Unseat all EC circuit packs on all peer subracks (extension shelves)
until after the Release 7.0 software is committed.
Important! During initial installation, if a main shelf is configured in a simplex

(single controller) configuration, the EC circuit pack must be seated in slot 2 for PSS-
16 and in slot 1 for PSS-32. These may be relocated to slot 12 on PSS-16 shelves and
slot 18 on PSS-32 shelves anytime after the Release 7.0 software is committed.
Note: Each EC in the master shelf as well as all extension shelves should already be
installed with the factory software load. All new EC packs come with the software
pre-installed.
END OF STEPS
Connect to the NE and prepare NE for software installation
Overview
You can connect directly to the network element to access the web interface (WebUI).
No client software is needed on your computer, only a web browser (Internet Explorer or
Firfox).
The Equipment Controller ships with software and a factory image. This procedure
provides the first steps for establishing connection to the NE using WebUI and creating
an initial database.
You can connect a computer (typically a laptop) directly to a network element to access
the WebUI using Internet Explorer via the CIT port on the faceplate of the active
Equipment Controller (EC) card on the Alcatel-Lucent PSS-16/32 shelf. On multi-shelf
network elements, the CIT port is active on the master shelf only.
Note: Popup blockers should be turned off in Internet Explorer.
Note: The NE is equipped with a DHCP server. Your LAN port should be
configured to obtain an IP address automatically.

Connect and Log In to the NE
1 Connect one end of the Ethernet cable to the CIT port on the active EC card (indicated by
a green Active LED) on the master shelf. Connect the other end of the cable to the
Ethernet port on your PC.
Note: If the circuit packs have recently been seated, you will not be able to access
the EC.
2 Open a PC command window and type ipconfig and <Enter>. Verify the IP address
assigned by the NE to your PC is 172.16.0.x. See Figure 3-1, PC command window.
Figure 3-1 PC command window
3 Launch Internet Explorer and enter http://172.16.0.1 in the Address bar. This is the
default IP address of the CIT port.
Note: Make sure Internet Explorer is not using a proxy server to access this address.
4 Click Go. The browser connects to the network element and the WebUI login window is
displayed. See Figure 3-2, Login Screen.

Figure 3-2 Login Screen
Note: The WebUI welcome screen will indicate Release 7.0 regardless of whether
the software version is 1830PSS-7.0-2 or 1830PSSECX-7.0-2. After logging into the
NE, the WebUI displays the System screen which contains the actual software
version.
5 Enter admin in the User: field and admin in the Password: field. Then click the Login
button.
6 If this is an Alcatel-Lucent 1830 PSS-16/PSS-32 shelf with factory load 1830PSS32-

0.00-7, a warning message appears similar to Figure 3-3, Alcatel-Lucent 1830 PSS-
16/PSS-32 WebUI uninitialized database warning indicating that the database is
uninitialized. DO NOT CLICK OK. Continue with Step 7.
Important! If the message in Figure 3-3 does not appear, that indicates the TID is
already configured. Proceed to Step 11.

Figure 3-3 Alcatel-Lucent 1830 PSS-16/PSS-32 WebUI uninitialized

database warning
If this is an 1830 PSS-16/PSS-32 shelf with factory load 1830PSS-0.32-1, a warning

message appears similar to Figure 3-4, Alcatel-Lucent 1830 PSS-16/PSS-32 WebUI
uninitialized database warning. Enter the NE name and click Submit, causing the NE to
reboot. Proceed to Step 10.

Figure 3-4 Alcatel-Lucent 1830 PSS-16/PSS-32 WebUI uninitialized

database warning
7 Click Cancel.
8 The system will prompt for a new NE name. Type the NE name provided in the site
documentation.
9 Click the Submit button and the system will restart once again.
10 After the restart is complete, login to WebUI using Username/Password admin/admin.
11 The WebUI will open with the system properties view as shown in Figure 3-5 WebUI
system properties.
Note: You may see a warning that the loopback address has not been configured.
The procedures for provisioning the address after software installation is found in
Chapter 8 of the Alcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32)
Release 7.0 Installation and System Turn-Up Guide .
Note: A DBINVALID alarm is present. The alarms clear later in the procedure
when the Release 7.0 software is activated.

Figure 3-5 WebUI system properties
END OF STEPS
Configure the software environment and load, and commit the software
Overview
The NE is shipped with software pre-loaded. However, the software version that is pre-
loaded on the cards may not be the same as the software version that will run in the
network. You must therefore perform the following tasks to load and commit the correct
software load on the NE.
The PC connected to the NE must have an FTP server running. The first procedure
prepares the FTP server on the NE. Follow either the WebUI or CLI procedure to
download and activate the software.
Note: If this is a multi-shelf system, the software automatically loads onto the
subtending shelves as well as the master shelf.

FTP server preparation
Note: Refer to Example configuration of ftp server, for more detailed instructions
on configuring an FTP server.
Note: Make sure that there is no other FTP server running on your PC. Note that if
the 1354 RM-PhM server is installed on your PC, the Apache ftp service may be
running and should be stopped.
1 Start the FTP server application on your PC and create a user account. Record the userid
and password established for the account.
2 Establish a root directory for the server and make sure it has read and write privileges.
You may create a folder in the root directory that will contain the NE software.
Important! There can be no spaces in the folder names in the path to the software.
3 Copy the folder and subfolders with the NE software into the FTP root directory
established above.
Note: For Alcatel-Lucent 1830 PSS-16/PSS-32, the software folder name to be

copied is either 1830PSS-7.0-2 (no support for GMPLS) or 1830PSSECX-7.0-2
(supports GMPLS, requires 16GB Compact Flash on all Equipment Controllers).
For 1830PSS-7.0-2 locate the desired subfolder from within the parent EC folder.
Inclusive to the software folder, there are three subfolders named 1830PSS,
1830PSSM, and usbkey, as well as a CATALOG file.
For 1830PSSECX-7.0-2 locate the desired subfolder from within the parent EC
folder. Inclusive to the software folder, there are three subfolders named
1830PSSECX, 1830PSSECXM, and usbkey, as well as a CATALOG file. The
software folder should be copied to the FTP server in its entirety. The software will
typically be provided on DVD or downloaded from the Alcatel-Lucent OnLine
Customer Support (OLCS) web site.
PC preparation
4 Open Windows Firewall from the Control Panel. See Figure 3-6, Windows firewall
settings.

Figure 3-6 Windows firewall settings
5 Select Off. Then click OK.
6 Open a PC command window and type ipconfig and <Enter>. Once again verify the IP
address assigned by the NE to your PC is 172.16.0.x. See Figure 3-7, PC command
window. Record this address because this will be used later as the server IP address.

7 If using CLI continue to "CLI procedure for 1830PSS-7.0-2 software upgrade" or CLI
procedure for 1830PSSECX-7.0-2 software upgrade.
If using WebUI continue to WebUI procedure for 1830PSS-7.0-2 software upgrade
or WebUI procedure for 1830PSSECX-7.0-2 software upgrade.
Important! If this is an Alcatel-Lucent 1830 PSS-16 shelf, use the CLI procedure.
END OF STEPS

Software Installation and Upgrade Software upgrade general instruction
Software upgrade general instruction

Purpose
This section provides procedures to perform a software upgrade to Release 7.0.2 of the
Alcatel-Lucent 1830 PSS-16/32.
Upgrade paths
This section provides information regarding in-service software upgrade paths to Release
7.0.2.
Note: Refer to the specific Customer Release Notes for each release in an upgrade path.
Alcatel-Lucent 1830 PSS Release 7.0.2 includes two software load variants.
1830PSS-7.0-2 is supported on Alcatel-Lucent 1830 PSS-16/PSS-32 shelves.
This software load supports non-GMPLS photonic applications only. The
equipment controllers with both 4G compact flash (8DG59241AB) and 16G
compact flash (8DG59241AD) are supported. Note: 112SDX11, 11OPE8,
11QCEX12, WR20-TFM, WTOCMF, OTDR, MCS8-16, ASWG, A4PSWG,
AAR-8A, and MSH8-FSM are not supported with this software load.
1830PSSECX-7.0-2 is supported on Alcatel-Lucent 1830 PSS-16/PSS-32 shelves.
This software load supports GMPLS control plane functionality and non-GMPLS
control plane functionality. The equipment controllers with 16G compact flash
(8DG59241AD) are required. Equipment controllers 8DG59241AB which have
been upgraded to a 16G compact flash can support this software load.
Note: When upgrading to 1830PSSECX-7.0-2 from a non-ECX software load, the

user must use the nobackupforce option in the CLI install command. This option
must be set when upgrading from a non-GMPLS load to a GMPLS load, due to the
name change in the SW load (1830PSS vs. 1830ECX). When the nobackupforce
option is set, the NE does not perform any pre-checks. The customer is required to
manually backup all NEs in the network prior to upgrade.
You can upgrade to 1830PSSECX-7.0-2 from the following software releases without
using nobackupforce:
Factory Load
1830PSSECX-6.0-6
1830PSSECX-7.0-0
1830PSSECX-7.0-1
You must use nobackupforce when upgrading to 1830PSSECX-7.0-2 from the

following non-GMPLS software releases:
1830PSS-5.1-6
1830PSS-6.0-0
1830PSS-6.0-6
1830PSS-6.0-7
1830PSS-6.2.0
1830PSS-7.0-0
1830PSS-7.0-1
1830PSS-7.0-2
Use one of the following procedures for these upgrades.
CLI procedure for 1830PSSECX-7.0-2 software upgrade
WebUI procedure for 1830PSSECX-7.0-2 software upgrade
PhM procedure for 1830PSSECX-7.0-2 software upgrade
Table 4 Software upgrade path summary for 1830PSS-7.0-2
Source Next Next Next Next Next Next Next Next

Release Release Release Release Release Release Release Release Release
1.0.0 1.0.5 1.1.0 1.1.2 2.0.0 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
1.0.5 1.1.0 1.1.2 2.0.0 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
1.1.0 1.1.2 2.0.0 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
1.1.2 2.0.0 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
2.0.0 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
2.0.20 2.0.50 3.0.3 3.6.54 5.1.6 1830PSS-

7.0-2
2.0.3 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2


2.0.50 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
2.0.60 3.0.4 3.6.54 5.1.6 1830PSS-

7.0-2
2.0.65 3.0.4 3.6.54 5.1.6 1830PSS-

7.0-2
2.5.0 3.0.4 3.6.54 5.1.6 1830PSS-

7.0-2
2.5.1* 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
2.5.30 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
2.9.0 2.9.1 3.0.0 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
2.9.1 3.0.0 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
3.0.0 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
3.0.1 3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
3.0.2 3.6.54 5.1.6 1830PSS-

7.0-2
3.0.3 3.6.54 5.1.6 1830PSS-

7.0-2
3.0.4 3.6.54 5.1.6 1830PSS-

7.0-2
3.0.5 3.6.54 5.1.6 1830PSS-

7.0-2
3.5.0 3.6.20 5.1.6 1830PSS-

7.0-2


3.5.1 3.6.20 5.1.6 1830PSS-

7.0-2
3.5.2 3.6.20 5.1.6 1830PSS-

7.0-2
3.5.3 3.6.54 5.1.6 1830PSS-

7.0-2
3.5.5 3.6.54 5.1.6 1830PSS-

7.0-2
3.5.96** 5.5.2 1830PSS- 1830PSS-

7.0-0 7.0-2
3.6.0 3.6.54 5.1.6 1830PSS-

7.0-2
3.6.20 5.1.6 1830PSS-

7.0-2
3.6.22 3.6.54 5.1.6 1830PSS-

7.0-2
3.6.52 5.1.6 1830PSS-

7.0-2
3.6.54 5.1.6 1830PSS-

7.0-2
3.6.56 5.1.6 1830PSS-

7.0-2
3.6.58 3.6.60*** 1830PSS-

7.0-2
3.6.60 1830PSS-
7.0-2
5.0.0 5.1.6 1830PSS-

7.0-2
5.1.0 1830PSS- 1830PSS-

6.0-6 7.0-2


5.1.2 1830PSS- 1830PSS-

7.0-0 7.0-2
5.1.6 1830PSS-
7.0-2
5.1.8 1830PSS- 1830PSS-

6.0-6 7.0-2
5.1.10 1830PSS- 1830PSS-

6.0-6 7.0-2
5.1.12 1830PSS- 1830PSS-

7.0-0 7.0-2
5.5.0 1830PSS- 1830PSS-

6.0-6 7.0-2
5.5.2 1830PSS- 1830PSS-

7.0-0 7.0-2
5.5.4 1830PSS- 1830PSS-

6.0-7 7.0-2
1830PSS- 1830PSS- 1830PSS-

6.0-0 7.0-1 7.0-2
1830PSS- 1830PSS-
6.0-6 7.0-2
1830PSS- 1830PSS-
6.0-7 7.0-2
1830PSS- 1830PSS-
6.2-0 7.0-2
1830PSS- 1830PSS-
7.0-0 7.0-2
1830PSS- 1830PSS-
7.0-1 7.0-2
Notes:
* 1830 PSS Release 2.5.1 is displayed in the user interface as 1830PSS32-2.5-20
** Contact Alcatel-Lucent Technical Support for Software Upgrade from Release 3.5.96 to Release 5.5.2

*** Equipment controllers with 4G CF (8DG59241AB) upgrading from R3.6.58 to R5.1.6 must first
upgrade to R3.6.60. Equipment controllers equipped with 16G CF can upgrade directly from R3.6.58
to R5.1.6.
Because firmware on the 11QPE24 cards is updated automatically during software upgrade, the
11QPE24 cards do not support in-service software upgrades to 1830PSS-7.0-2. Refer to Firmware for
Release 7.0.2 for more information.

Table 5 Software upgrade path summary for 1830PSSECX-7.0-2*,
Source Next Next Next Next Next Next Next

Release Release Release Release Release Release Release Release
**
3.6.1 3.6.21 3.6.23 3.6.27 3.6.51 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
3.6.21 3.6.23 3.6.27 3.6.51 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
3.6.23 3.6.27 3.6.51 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
3.6.25 3.6.31 3.6.53 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
3.6.27 3.6.51 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
3.6.29 3.6.53 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
3.6.31 3.6.53 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
3.6.51 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
3.6.53 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
3.6.60 5.1.6*** 1830PSSEC

X-7.0-2
5.1.0 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
5.1.1 5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
5.1.2*** 1830PSS-6.0- 1830PSSEC 1830PSSEC

0 X-6.0-6 X-7.0-2
5.1.6*** 1830PSSEC
X-7.0-2

Source Next Next Next Next Next Next Next

Release Release Release Release Release Release Release Release
**
5.1.7*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
5.1.8 1830PSS-6.0- 1830PSSEC

6*** X-7.0-2
5.1.12*** 1830PSSEC 1830PSSEC

X-7.0-0 X-7.0-2
5.5.0 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
5.5.2*** 1830PSSEC 1830PSSEC

X-6.0-6 X-7.0-2
1830PSS - 1830PSSEC 1830PSSEC

6.0-0*** X-7.0-1 X-7.0-2
1830PSSEC 1830PSSEC
X-6.0-6 X-7.0-2
1830PSS- 1830PSSEC
6.0-7*** X-7.0-2
1830PSS - 1830PSSEC
6.2-0*** X-7.0-2
1830PSS- 1830PSSEC
7.0-0*** X-7.0-2
1830PSSEC 1830PSSEC
X-7.0-0 X-7.0-2
1830PSS- 1830PSSEC
7.0-1*** X-7.0-2
1830PSSEC 1830PSSEC
X-7.0-1 X-7.0-2
1830PSS- 1830PSSEC
7.0-2*** X-7.0-2

Notes:
* For software upgrades to 1830PSSECX-7.0-2 from non-GMPLS releases prior to Release 3.6.1, refer
to Table 4.
** The equipment controller (8DG59241AD) with 16GB Compact Flash is required for software upgrade
support to 1830PSSECX-7.0-2 on 1830 PSS-16/PSS-32 shelves.
*** You must use nobackupforce when upgrading to 1830PSSECX-7.0-2 from these non-GMPLS
software releases.
Not supported on NEs with L0-GMRE enabled.
Because firmware on the 11QPE24 and 11OPE8 cards is updated automatically during software
upgrade, the 11QPE24 and 11OPE8 cards do not support in-service software upgrades to
1830PSSECX-7.0-2. Refer to Firmware for Release 7.0.2 for more information.

Upgrade guidelines for Release 7.0.2

The active software release on the Alcatel-Lucent 1830 PSS-16/PSS-32 system must be
listed in Table 4, "Software upgrade path summary for 1830PSS-7.0-2" or Table 5,
"Software upgrade path summary for 1830PSSECX-7.0-2" as a release directly
upgradeable to Release 7.0.2. The system turn-up procedures described in the Alcatel-
Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 7.0 Installation
and System Turn-Up Guide should have been completed.
The software upgrade can be performed through CLI, WebUI, or 1354 RM-PhM
photonic manager. After completing the Software upgrade general instruction section,
please follow the procedures specifically defined for each of these user interfaces in this
chapter.
Important! Verify the Part Number (APN) of all Equipment Controller (EC)
circuit packs on 1830 PSS-16/32 shelves.
8DG59241AD variant supports software version 1830PSSECX-7.0-2. This

particular EC contains a 16GB Compact Flash that supports.
Upgraded 8DG59241AB variants to have 16G compact flash can support

1830PSSECX-7.0-2 software. By default, this variant comes with 4G compact
flash.
All other EC variants only support 1830PSS-7.0-2. 1830PSS-7.0-2 does not

support GMPLS.
Important! Verify that the network under upgrade is not using a 16byte OSFP MD5
authentication key. See Issue #PSSKPL-41 for details. The configuration change must
be completed before the ISUG is attempted, otherwise connectivity to the RNEs
might be lost permanently.
Important! All databases must be backed-up prior to upgrade as instructed by the

procedures within this section.
Important! During activation, ensure that data communications with the remote
database backup server is maintained at all times. Activation may fail if a network
element cannot communicate with the server. Avoid activating more than one NE
simultaneously if doing so would disrupt the lines of communication to the server.
Important! If upgrading a GMPLS network with an active control plane:

Avoid activating more than one neighbor NE simultaneously.

After the SW has been committed on all the NEs in the network, please refer to
the GMPLS/GMRE guide to update the active network version (GMPLS/GMRE
Guide Procedure 8-1)
Important! Please refer to Chapter 2, Issues for known issues related to the
software upgrade.
Note: Under normal (unencrypted UI) mode, any NE can be configured as a

designate SWNE (Software Download Network Element), which runs ftp server and
be available to accept FTP request over OSC and GCC interfaces. This enhances the
software download performance for RNEs. For software upgrade in a network with
GNE and RNE nodes, the SWNE feature is recommended.
Note: When upgrading a network with GNE and RNE nodes without using SWNE
feature, it is recommended to upgrade the RNE nodes farthest from the GNE node
first, then work back toward the GNE node.
Software upgrade interval

The following table summarizes the typical network element software upgrade time
intervals for Release 7.0.2. These intervals are provided for reference only, as the time
required will depend on the actual network configuration.
Table 6 Typical software upgrade time interval table for Release 7.0.2
Software Node Per EC Per LC

upgrade step
1830PSS-7.0-2 1830PSSECX-7.0-2
Audit ~0.5 min. NA NA NA
Download* NA ~12 min. FTP ~25 min. FTP NA

~20 min. SFTP ~30 min. SFTP
~8 min. SWNE** ~20 min. SWNE**
Backup ~0.5 min. NA NA NA
Activate NA ~22 min. per EC ~30 min. per EC (Active ~10 min. per LC
(Active and Standby and Standby subtending (Started after EC
subtending shelf EC are shelf EC are activated in activation is
activated in parallel) parallel) completed. All LC
activations performed
in parallel)
Commit ~0.5 min. NA NA NA

Note:
* The Download time depends on key factors including but not limited to:
1. Release Version
2. File transfer protocol
3. Number of EC packs
4. DCN link speed between NE and NMS
5. GNE/RNE configuration
** SWNE is recommended for normal software upgrade.
Required materials list

The following items are required when using WebUI:
Personal computer (PC) running, Windows 2000, Windows 7, or Windows 8
Note: Windows XP computers will no longer receive automatic updates that help protect
personal information. Windows XP is not supported by 1830 PSS Release 7.0.2.
The following software should be loaded on the PC.
Internet Explorer 8.0, 9.0, or 11.0
The Internet Explorer 8.0 browser does not support launching JDSU viewer for
viewing OTDR scan results.
MAC OS 10.9 (with Firefox browser only)
Firefox through v30. The following WebUI functionality is not supported with the
Firefox browser:
o Show in separate window
o Export to Excel
o Launching JDSU viewer for viewing OTDR scan results
J2SE Java Runtime Environment (JRE) 5.0 thru 7u51.
Note: Although the WebUI application software is zero install, the user must install
JRE on the PC to allow the WebUI to run.
Telnet application
FTP server software (required for software download)
TFTP server software (required for database backup and restore)
10/100 BaseT LAN card and a shielded RJ45 straight through cable.
Note: It is extremely important that the RJ45 cable be shielded. Unshielded RJ45 cables
do not provide adequate protection to the system hardware.
ESD wrist strap

1354 RM-PhM Release12.2 if that application is to be used.
Required change notices (CNs)

There are no required change notices published for this software release.
Precautions and recommendations

Be sure to read and understand the following:
Read the entire software installation procedure before beginning.
The person performing the software upgrade must be trained and have an understanding
of the Alcatel-Lucent 1830 PSS-16/PSS-32 system.
Perform the software upgrade procedure in the sequence provided; any deviation may
lead to unpredictable behavior.
Use care when handling circuit packs.
Make use of ESD wrist straps and static-safe bags.
If upgrading a NE containing one or more 11QPE24 cards, wait 1 hour after upgrading to
Release 7.0.2 before performing any configuration involving a 11QPE24 card.
If upgrading software from previous releases through the GCC channel of 11QPA4(A) ,
11DPE12E, 11DPE12A, or 11QPEN4 packs, the MTU size should be set to less than
1000 to avoid a software download failure.
Note
Please read the following note:
All of the graphics utilized in this section may not contain current release designations.
They are for reference only.
Perform software upgrade general
Description
The PC/server used to perform the database backup must have an FTP server running. If
the upgrade is to be performed using 1354 RM-PhM Photonic Manager, that software
comes with its own FTP server. Otherwise, the PC must have FTP server software loaded
and configured.
FTP server preparation
Note: Refer to Example configuration of ftp server, for more detailed instructions on
configuring an ftp server.

1 If 1354 RM-PhM Photonic Manager is to be used to perform the upgrade, proceed

to PhM instructions. For CLI and WebUI, continue to Step 2.
Start the FTP server application on your PC and create a user account. Record the userid
and password established for the account. Refer to FTP Server Configuration using
Filezilla
2 Establish a root directory for the server and make sure it has read and write privileges.
You may create a folder in the root directory that will contain the NE software. Refer
to FTP Server Configuration using Filezilla
3 Copy the folder and subfolders with the NE software into the ftp root directory
established above.

copied is either 1830PSS-7.0-2 (does not support GMPLS) or 1830PSSECX-7.0-2
(supports GMPLS and requires 16GB Compact Flash on all Equipment Controllers
on 1830 PSS-16/32 shelves).
For 1830PSS-7.0-2 locate the desired subfolder from within the parent EC folder.
Inclusive to the software folder, there are three subfolders named 1830PSS,
1830PSSM and usbkey, as well as a CATALOG file.
For 1830PSSECX-7.0-2 locate the desired subfolder from within the parent EC
1830PSSECX, 1830PSSECXM and usbkey, as well as a CATALOG file.
The software folder should be copied to the FTP server in its entirety. The software
will typically be provided on DVD or downloaded from the Alcatel-Lucent OnLine
PC preparation
4 If the Windows Firewall has already been turned off, proceed to Step 8.
5 Open Windows Firewall from the Control Panel. See Figure 3-8, Windows Firewall
settings.

Figure 3-8 Windows Firewall settings
7 Open a PC command shell and type ipconfig and <Enter>. Note the IP address
assigned to your PC. This will be used later in the procedure. See Figure 3-9, PC
command window.

8 If using CLI continue to "CLI procedure for 1830PSS-7.0-2 software upgrade" or CLI
procedure for 1830PSSECX-7.0-2 software upgrade..
If using WebUI continue to WebUI procedure for 1830PSS-7.0-2 software upgrade
or WebUI procedure for 1830PSSECX-7.0-2 software upgrade.
If using PhM continue to PhM procedure for 1830PSS-7.0-2 software upgrade or PhM
procedures for 1830PSSECX-7.0-2 software upgrade.
END OF STEPS
General guideline on software upgrade under KMT

It is recommended to upgrade KMT to Release 7.0.x prior to upgrading the Network Elements to Release
7.0.2. Follow these steps:
1 Before NE is upgraded, all circuits on this NE should be set to Maintenance state.
2 When upgrade is finished, a new snmpv3 crypto user should be created:

In CLI: con admin snmpusers add <username> crypto
i.e.
con admin snmpusers add kmtuser crypto
Followed by password string containing minimum of 12 alphanumeric characters. This password
string becomes your
Authentication key and Privacy key.
3 Delete trap destination on upgraded Network element:

In CLI: show snmpserver trapdest
Example output:
SNMP Notification Destinations
Identifier Target Address Port Timeout Retry SNMP NMS UserName Count
Vers
-------------------------------- ---------------- ------ ------- ----- ---- --- --------------------------------
NDE[ARTEMKMT] 135.121.45.63 162 1500 3 v3 0 v3Default
User
PhM[nmsx10] 135.121.44.110 162 1500 3 v2c 1
Note the name of your KMT server and execute:

con snmpserver trapdest delete <kmt server name>
i.e.
con snmpserver trapdest delete NDE[ARTEMKMT]
4 In KMT edit Network Element username, authentication key and privacy key, press save.
5 Restart SCA.
6 In 5 minutes observe that there is a new entry in trap destination table containing your
new snmpv3 user name
In CLI: show snmpserver trapdest
Example output:
SNMP Notification Destinations
Identifier Target Address Port Timeout Retry SNMP NMS UserName Count
Vers
-------------------------------- ---------------- ------ ------- ----- ---- --- --------------------------------
NDE[ARTEMKMT] 135.121.45.63 162 1500 3 v3 0 kmtus
er
PhM[nmsx10] 135.121.44.110 162 1500 3 v2c 1
7 You can now enable circuits associated with the NE.

END OF STEPS

Software Installation and Upgrade CLI instructions
CLI instructions
Overview
This section provides CLI instructions for the following procedures:
New software installation
Database backup
Software upgrade
Software rollback to previous release
CLI procedure for 1830PSS-7.0-2 new software installation
This section provides CLI procedures for new software installation.
If you wish to upgrade software, proceed to "CLI procedure for 1830PSS-7.0-2 software
upgrade".
Important! Perform these steps only after following New software installation general
instruction.
Connect to the NE for CLI access
Overview
After completing the TID configuration using WebUI, you can connect directly to the
network element to access the CLI. No client software is needed on your PC, only a telnet
application.
Procedure
the CLI using the CIT port on the faceplate of the active Equipment Controller (EC) card
on the Alcatel-Lucent PSS-16/32 shelf. On multi-shelf network elements, the CIT port is
active on the master shelf only. Note this is the same connection used for the WebUI
interface.
1 If not already connected, connect one end of the Ethernet cable to the CIT port on the
active EC card (indicated by a green Active LED) on the master shelf. Connect the other
end of the cable to the Ethernet port on your PC.

2 Use a telnet application on your PC and open a telnet session connected to the IP address
of the CIT port.
The default CIT IP address is 172.16.0.1
3 Hit <Enter> and the login: prompt appears. Type cli and <Enter>.
4 Type cli at the Password: prompt and <Enter>.
5 This starts the CLI, and another Username: prompt appears. Type admin and <Enter>.
6 At the Password: prompt type admin and <Enter>. The following warning notice
appears.
1830 PSS-32, WAVELENGTH TRACKER
Alcatel-Lucent
(c) 2008 Alcatel-Lucent. All rights reserved.
Welcome to the CLI
Warning Notice
This system is restricted solely to Alcatel-Lucent authorized
users for legitimate business purposes only. The actual or
attempted unauthorized access, use, or modification of this
system is strictly prohibited by Alcatel-Lucent. Unauthorized
users are subject to Company disciplinary proceedings and/or
criminal and civil penalties under state, federal, or other
applicable domestic and foreign laws. Use of this system may
be monitored and recorded for administrative and security
reasons. Anyone accessing this system expressly consents to
such monitoring and is advised that if monitoring reveals
possible evidence of criminal activity, Alcatel-Lucent may
provide the evidence of such activity to law enforcement
officials. All users must comply with Alcatel-Lucent Corporate
Instructions regarding the protection of Alcatel-Lucent
information assets.

Do you acknowledge? (Y/N)?
7 Type Y and <Enter>.
8 The current alarm summary will be displayed followed by the NE# prompt. CLI
commands can now be entered. Type ? for a list of commands. See the Alcatel-Lucent
1830 Photonic Service Switch (PSS) Release 7.0 CLI Command Guide for more
information about CLI commands.
END OF STEPS
Install 1830PSS-7.0-2 new software
1 Type config software server ip <ip> and <Enter>.

Where <ip> is the ip address of the PC with the FTP server. This is the same ip address
obtained using the ipconfig command in the PC command window.
2 Type config software server userid <userid> and <Enter>.

Where <userid> is the userid for the user account defined on the FTP server.
See the sample output below.
Enter password:
3 Type <pw> and <Enter>.

Where <pw> is the password for the user account defined on the FTP server.
4 Type config software server root <path> and <Enter>.

Where <path> is the path to the NE software relative to the server root
directory.
Note: If the software folder was copied directly into the root directory, enter / for the
<path>.
5 Type config software server detail and <Enter>. See the sample output below:
Software Server Protocol : FTP
Software Server IP : 172.16.0.2
Software Server Userid : sw1

Software Server Root Directory : /

Verify the server settings are correct.

6 Type config software upgrade status and <Enter>. See the sample output
below:
Software Upgrade Information:

Committed Release :
Working Release Directory :
Working Release : 1830PSS32-5.1-0
Active Release : 1830PSS32-5.1-0/
Operation :
Operation Status :
Upgrade Path Available : True
Software Download Script (Timezone: ):
Verify the current active software is an older release than software you are loading.
7 Type config software upgrade manual audit <releasedir> nobackup and

<Enter>.
Where <releasedir> is the directory name on the PC containing the software within the
Software Server Root Directory. For Alcatel-Lucent 1830 PSS-16/PSS-32 Release 7.0.2,
the folder name is 1830PSS-7.0-2 .
This will check the path and verify the system is ready for upgrade.
8 Type config software upgrade status and <Enter>.

A listing of packs will be displayed along with the status showing which packs need to be
upgraded. See the sample output below.

Software Server Root Directory : /SVT/

Committed Release :
Working Release Directory : 1830PSS-7.0-2/
Working Release : 1830PSS-7.0-2
Active Release : 1830PSS32-5.1-6
Operation : Audit
Operation Status : Completed
Stage=0 Step=1 SH/SL: 1/1 CARDTYPE: EC

ACTION: Audit node Completed 100% complete
RESULT: Success
Stage=1 Step=0 SH/SL: 0/0 CARDTYPE: Empty

ACTION: Transfer to disk Planned 0% complete
RESULT: None

ACTION: Activate Planned 0% complete
RESULT: None
Stage=3 Step=0 SH/SL: 1/2 CARDTYPE: AHPHG

RESULT: None
Stage=3 Step=1 SH/SL: 1/3 CARDTYPE: CWR8


RESULT: None
Stage=3 Step=2 SH/SL: 1/7 CARDTYPE: 11STAR1

RESULT: None

RESULT: None

RESULT: None
Stage=3 Step=6 SH/SL: 1/17 CARDTYPE: ALPHG

RESULT: None
9 Repeat Step 8 until the Operation Status indicates Completed. Verify the Upgrade Path
Available changes to True.
10 Type config software upgrade manual load and <Enter>.

This will transfer the software to the NE.

Watch for the following lines.
...
Operation : Load
Operation Status : In Progress 0%
...

Continue to execute the status command until the Operation Status shows Completed.
Note: In large multishelf configurations, the execution of the config/show software
upgrade status command during software load may result in resource
currently unavailable errors, dropped CLI connectivity, and CPUPERMANCE
alarms. Wait a few minutes, and login into the NE again and reissue the command
(PSSKPL-224).
12 Type config software upgrade manual activate and <Enter>.

The software on the EC card activates.
13 The NE reboots and the telnet connection drops. Wait about 2 minutes after the fan speed
drops back to normal speed and log back into the NE.

...
Operation : Activate
...
Note: The output also displays the progress of the activation on each of the packs in
the NE. The Operation Status shows completed after the new software is activated all
packs.
15 Type config database clear and <Enter>.

All sessions connected to the NE close and the NE reboots.
16 Login to CLI again and type config software upgrade commit and <Enter>.
The software is commited as the primary release.


...
Operation : Commit
...
18 After the last status command is executed, verify the new software release displays as the
committed, working, and active release. See the sample output below.

Committed Release : 1830PSS-7.0-2
Active Release : 1830PSS-7.0-2/
Operation : Commit
Upgrade Path Available : False
19 The system is now ready for provisioning. Refer to Alcatel-Lucent 1830 Photonic Service
Switch 16/32 (PSS-16/32) Release 7.0 Installation and System Turn-Up Guide for the
detailed steps.
END OF STEPS

CLI procedure for 1830PSS-7.0-2 software upgrade
Important! Perform these steps only after following Software upgrade general
instruction.

You can connect directly or remotely to the Network Element (NE) to access the CLI
interface. No client software is needed on your PC, only a telnet application.
Upgrade to 1830PSS-7.0-2 software
1 If connecting locally at the NE, continue to Step 2.

If connecting remotely to the NE, proceed to Step 4.
active (indicated by a green Active LED) EC card (PSS-16/32) on the master shelf.
Connect the other end of the cable to the Ethernet port on your PC.
of the CIT port.
Proceed to Step 6.
4 Connect the PC to the Data Communications Network that has access to the NE.
5 Use a telnet application on your PC and open a telnet session. Connect to the OAMP IP
address if the NE is a GNE. Connect to the Loopback IP address if the NE is a RNE.
Note: When upgrading a network with GNE and RNE nodes, it is recommended to
upgrade the RNE nodes farthest from the GNE node first, then work back toward the
GNE node.

8 This starts the cli interface, and another Username: prompt appears. Type admin and
<Enter>.
9 At the Password: prompt type admin and <Enter>. This will bring up the following
warning notice.
Alcatel-Lucent
Welcome to the CLI
Warning Notice

information assets.

11 The current alarm summary will be displayed followed by the TID# prompt. CLI
12 Proceed to CLI procedure for database backup.

END OF STEPS
CLI procedure for database backup

A database backup must be performed on each NE before beginning the upgrade. The
database backup may be necessary if there is a significant failure either during or after the
upgrade.
The PC/Server used to perform the database backup must have a TFTP server running.
1 Start the TFTP server application on your PC.
2 Create a folder under the TFTP root directory where you would like to store the backup.
3 Open Windows Firewall from the Control Panel. See Figure 3-10, Windows Firewall
settings.

5 Open a PC command shell separate from the existing NE login and type ipconfig and
<Enter>. Note the IP address assigned to your PC. This will be used later in the
procedure. See Figure 3-11, PC command window.

6 In the NE login window type configure database server ip <server ip> and
<Enter>.
Where <server ip> is the IP address of your PC obtained at Step 5 .
7 Type configure database path <path> and <Enter>.

Where <path> is the path relative to the TFTP server root directory to the
location where the backup will be stored. The end of the path must contain a descriptive
filename for the database backup. The filename should have a .bak extension.
8 Type show database and <Enter>.

See the sample output below:
Remote Server Configuration
---------------------------
Protocol : TFTP
IP : 172.16.0.2
Userid :
Path : /pssnfs/backups/C2 11 19 08 1.bak
Last Backup Information

-----------------------
File :
Time : N/A (UTC)
Crc : 0

Last Operation
--------------
Command : No Command
Progress : 0 %
Status :
Verify the server configuration is correct.
9 Type configure database backup and <Enter>.

Continue with the database backup (yes,no)?
10 Type yes and <Enter>.

Database backup in progress...
database backup complete
11 Type show database and <Enter>.

Remote Server Configuration
---------------------------
Protocol : TFTP
IP : 172.16.0.2
Userid :
Path : /pssnfs/backups/C2 11 19 08 1.bak
Last Backup Information

-----------------------
File :
Time : N/A (UTC)

Crc : 0
Last Operation
--------------
Command : Backup
Progress : 100 %
Status : Success
Verify the Status field shows Success.
12 Repeat this procedure for each NE that will be upgraded.

END OF STEPS
1830PSS-7.0-2 software upgrade with or without SWNE feature (CLI)

If using CLI with SWNE feature, continue with CLI procedure to 1830PSS-7.0-2 software
upgrade with SWNE feature.
If using CLI without SWNE feature, proceed to CLI procedure to 1830PSS-7.0-2 software
upgrade without SWNE feature"
CLI procedure for 1830PSS-7.0-2 software upgrade with SWNE feature

Note: In order to use the SWNE feature in Release 7.0.2, one NE will need to be running
1830PSS-7.0-2 and committed before it can be used as the SWNE.
Note: Only FTP protocol can be used by GNE/RNE for software download via
SWNE. GNE/RNE can download only the active software in the SWNE. (A double
commit in the SWNE will remove any standby software).
1 Login to the PSS-R7.0 NE to enable DFTP server.
2 Type config general ftpserver enable and <Enter>. See Figure 3-12, CLI
FTP Server Setting.

Figure 3-12 CLI FTP server settings
3 Login to the pre-R7.0 NE to be upgraded and follow the procedure.

Where <ip> is the loopback ip address of the GNE/RNE where DFTP server is enabled.

Where for SWNE <userid> is UserSWNE
Enter password:

Where <pw> is the password for the SWNE userid UserSWNE.
Note: The default password for UserSWNE is Ftp-id#1

Where for SWNE <path> is the /dftp/swp/EC
8 Type config software server detail and <Enter>.


Software Server Userid : UserSWNE
Software Server Root Directory : /dftp/swp/EC


Committed Release : 1830PSS32-5.1.0
Operation :
Operation Status :
Verify the current active software is directly upgradeable to Release 7.0.2 as shown
on Table 4, "Software upgrade path summary for 1830PSS-7.0-2".
10 Proceed to Step 8 in CLI procedure to 1830PSS-7.0-2 software upgrade without SWNE

feature.

CLI procedure for 1830PSS-7.0-2 software upgrade without SWNE feature
1 If not logged in, login to the NE to be upgraded following the procedure.

Where <ip> is the ip address of the PC with the FTP server. Use the IP address verified
in Step 7 in PC preparation.

Where <userid> is the userid for the user account defined on the ftp server.
Enter password:
Refer to FTP server configuration

Where <pw> is the password for the user account defined on the ftp server.
Refer to FTP server configuration

directory.
<path>.




Operation :
Operation Status :
Verify the current active software is directly upgradeable to Release 7.0.2 as shown
in Table 4, "Software upgrade path summary for 1830PSS-7.0-2".
Note: Prior to Audit, for redundant system in the master shelf, ensure duplex controllers
are equipped in all extension shelves and ensure the duplex controller status in the master
and extension shelves are in a good state.

<Enter>.
Where <releasedir> is R7.0 folder name present in the SWNE server or the folder name
on the PC containing the software.


A listing of packs displays along with the status showing which packs need to be

Committed Release : 1830PSS32-5.1-0
Operation : Audit

RESULT: Success

RESULT: None

RESULT: None


RESULT: None

RESULT: None

RESULT: None

RESULT: None

RESULT: None

RESULT: None
10 Repeat Step 9 until the Operation Status indicates Completed. Verify Upgrade Path

The software transfers to the NE.


...
Operation : Load
...
Continue to execute the status command until the Operation Status shows
Completed.
13 For any system with simplex EC, continue with Step 14.
Important! For all systems, regardless of whether or not the ECs are redundant, the
following minor, non-service affecting alarm may raise during the course of the
software upgrade.
SWUPGFAIL - Software upgrade failed SWUPGFAIL
If this Software upgrade failed alarm appears, wait until the DBUNSYNC and
UNKNOWN alarms automatically clear, then repeat the Audit-Load-Activate
command until the In-Service-Upgrade (ISUG) to Release 7.0.2 completes.
During the upgrade process, if there is a Card Unknown alarm (e.g., for the
WTOCM, MVAC), refer to Issue #78785 of the Known issues list.
Important! For systems with redundant ECs, during the in-service upgrades to
Release 7.0.2, the following minor, non-service affecting alarms will raise.
DBUNSYNC - Active and standby Main EC databases are not synchronized
UNKNOWN - Card unknown Equipment Controller
These two alarms are expected during the in-service upgrade and will automatically
clear after the standby EC database is synchronized with the active EC.
Important! From CLI - execute "show software upgrade ne brief" and confirm all
the EC in that node have the next Software release in the standby bank.
Note: After the Load step has been completed, users can choose to perform the
Activate Step 14 at a later time. If the Activate is performed at a later time or the EC
is reset after Load Operation, users must perform Audit and Load before performing

the Activate stage as described in Step 8 to Step 12. The Audit and Load steps need to
be performed in order to ensure that the appropriate packs are activated properly. The
Load step will not re-load the NE Software unless prior Load step has not been
successfully completed.

The software is activated on the NE.
15 The NE reboots and the telnet connection drops. Wait about 2 minutes after the fan speed
drops back down to normal speed and log back into the NE.

...
...
Note: The output will also display the progress of the activation on each of the
packs in the NE. The Operation Status will not show completed until all packs have
been activated on the new release.
17 Type show software ne brief and <Enter>.

Ensure that all circuit packs have been activated to Release 7.0.2.
18 Check for unexpected alarms and conditions on the system and make sure traffic is still
unaffected.
Important! This is the last point where a software rollback can be performed, so it
is very important to verify the system is operating normally before committing the
software.
Note: FWUPGRADEPENDING and FWVERSIONNOTDEFAULT conditions may

exist on some circuit packs. Refer to Firmware management procedures to address
these conditions.

Note: An Amplifier Gain Tilt Adjustment Suspended alarm is raised on nodes

where a WTOCM FPGA is not upgraded. As a result, the tilt adjustment will be
suspended until users complete Normal firmware upgrade (cold reboot) on the
WTOCM circuit packs. Once the firmware has been upgraded the tilt adjustment can
be restarted.
19 Type config software upgrade commit and <Enter>.

The software is committed as the primary release.

...
Operation : Commit
...
Completed.
21 After the last status command is executed, verify the new software release displays as the
committed, working, and active release. See the sample output below.

Committed Release : 1830PSS-7.0-2
Operation : Commit

22 Verify the current active software iRepeat step Step 1 through Step 21 for each NE to be
upgraded.
23 The software upgrade is now complete. A backup should be performed on all upgraded
NEs referring to the procedure CLI procedure for database backup.
24 After the software upgrade, some circuit packs may have FWUPGRADEPENDING
and FWVERSIONNOTDEFAULT conditions. Proceed to Firmware management
procedures to maintain or upgrade firmware for these circuit packs.
END OF STEPS

CLI procedure for 1830PSS-7.0-2 software roll back to previous release
Pre-requisite:
Before beginning this procedure, ensure the database parameters (server ip, protocol,
userid, path) are configured properly such that the NE is pointing to the location of a
previously backed-up database file.
Purpose
The following procedure will allow the user to remotely roll back the Alcatel-Lucent
1830 PSS-16/PSS-32 Network Element software to the previous software release. This
procedure should be used in the event that unexpected problems occur during the
software upgrade to Release 7.0.2.
Important! This procedure can only be performed if the Release 7.0.2 software has
not been committed.
CLI procedure for software rollback to previous release


Committed Release :
Working Release :

Software Installation and Upgrade
Verify the Committed Release is not 7.0.2
2 Type config software upgrade backout and <Enter>.

WARNING: You are about to perform a backout.
This may be service affecting.
Enter 'yes' to confirm, 'no' to cancel:
4 The NE will reboot. Wait about 2 minutes after the fan speed drops back down to normal
speed and log back into the NE.
5 Type show version and <Enter>

Software Version: 1830PSS-6.0-6
Verify the software version is restored to the original release version before the software
upgrade.
6 Type config software upgrade commit and <Enter>

This will commit the software to be the primary release.
7 The software rollback is now complete.

END OF STEPS

CLI procedure for 1830PSSECX-7.0-2 software

This section provides CLI instructions for the following procedures:
Database backup. Refer to CLI procedure for database backup.
Software upgrade
CLI procedure for 1830PSSECX-7.0-2 new software installation

This section provides CLI procedures for new software installation. If software upgrade operation
is needed, please proceed to CLI procedure for software upgrade.
Important! Perform these steps only after following New software installation general
instruction.
Overview
After completing the TID configuration using WebUI, you can connect directly to the
network element to access the CLI. No client software is needed on your PC, only a telnet
application.
Procedure
the CLI using the CIT port on the faceplate of the active Equipment Controller (EC) card
on the Alcatel-Lucent PSS-16/32 shelf. On multi-shelf network elements, the CIT port is
active on the master shelf only. Note this is the same connection used for the WebUI
interface.
active EC card (indicated by a green Active LED) on the master shelf. Connect the other
end of the cable to the Ethernet port on your PC.
of the CIT port.

5 This starts the CLI, and another Username: prompt appears. Type admin and <Enter>.
warning notice.
Alcatel-Lucent
Welcome to the CLI
Warning Notice
information assets.
8 The current alarm summary will be displayed followed by the NE# prompt. CLI

END OF STEPS

Install 1830PSSECX-7.0-2 new software

Where <ip> is the ip address of the PC with the FTP server. This is the same ip address
obtained using the ipconfig command in the PC command window.

Where <userid> is the userid for the user account defined on the FTP server.
Enter password:

Where <pw> is the password for the user account defined on the FTP server.

directory.
<path>.




Committed Release :
Operation :
Operation Status :
Verify the current active software is an older release than software you are loading.

<Enter>.
Where <releasedir> is the directory name on the PC containing the software within the
Software Server Root Directory. For Alcatel-Lucent 1830 PSS-16/PSS-32 Release 7.0.2,
the folder name should be 1830PSSECX-7.0-2.

A listing of packs displays along with the status showing which packs need to be
upgraded. See the sample output below:

Committed Release :
Working Release Directory : 1830PSSECX-7.0-2/
Active Release : 1830PSS-0.32-1
Operation : Audit

RESULT: Success

RESULT: None

RESULT: None

RESULT: None

RESULT: None


RESULT: None

RESULT: None

RESULT: None

RESULT: None
9 Repeat Step 8 until the Operation Status indicates Completed. Verify the Upgrade Path

The software is transferred to the NE.

...
Operation : Load
...

The software is activated on the EC card.

13 The NE will reboot and the telnet connection will drop. Wait about 2 minutes after the
fan speed drops back to normal speed and log back into the NE.

...
...
Note: The output displays the progress of the activation on each of the packs in the
NE. The Operation Status shows completed after the new release is activated on all
packs.
15 Type config database clear and <Enter>.

All sessions connected to the NE close and the NE to reboots.
16 Login to CLI again and type config software upgrade commit and <Enter>.
The software is committed as the primary release.

...
Operation : Commit
...
18 After the last status command is executed, verify the new software release is displayed as
the committed, working and active release. See the sample output below:


Committed Release : 1830PSSECX-7.0-2
Working Release : 1830PSSECX-7.0-2
Active Release : 1830PSSECX-7.0-2/
Operation : Commit
19 If installing a GMPLS network with an active control plane, after the SW has been
committed on the NE, refer to the GMPLS/GMRE guide to activate the GMRE.
detailed steps.
END OF STEPS
CLI procedure for 1830PSSECX-7.0-2 software upgrade
instruction.

You can connect directly or remotely to the Network Element (NE) to access the CLI
interface. No client software is needed on your PC, only a telnet application.

If connecting remotely to the NE, proceed to Step 4.

active (indicated by a green Active LED) EC card (PSS-16/32) on the master shelf.
Connect the other end of the cable to the Ethernet port on your PC.
of the CIT port.
Proceed to Step 6.
5 Use a telnet application on your PC and open a telnet session. Connect to the OAMP IP
address if the NE is a GNE. Connect to the Loopback IP address if the NE is a RNE.
GNE node.
8 This starts the cli interface, and another Username: prompt appears. Type admin and
<Enter>.
warning notice.
Alcatel-Lucent
Welcome to the CLI
Warning Notice

information assets.
11 The current alarm summary displays followed by the TID# prompt. CLI commands can
now be entered. Type ? for a list of commands. See the Alcatel-Lucent 1830 Photonic
Service Switch (PSS) Release 7.0 CLI Command Guide for more information about CLI
commands.
12 Proceed to CLI procedure for database backup.

END OF STEPS

1830PSSECX-7.0-2 software upgrade with or without SWNE feature (CLI)

If using CLI with SWNE feature, continue with CLI procedure for1830PSSECX-7.0-2 software
upgrade with SWNE feature.
If using CLI without SWNE feature, proceed to CLI procedure for 1830PSSECX-7.0-2
software upgrade without SWNE feature.
CLI procedure for 1830PSSECX-7.0-2 software upgrade wih SWNE feature

Note: In order to use the SWNE feature in R7.0.2, one NE needs to be running
1830PSSECX-7.0-2 and committed before it can be used as the Software Server NE
(SWNE).
Note: Only FTP protocol can be used by GNE/RNE for software download via
SWNE. GNE/RNE can download only the active software in the SWNE. (A double
commit in the SWNE will remove any standby software).
1 Login to the 1830PSSECX-7.0-2 NE to enable DFTP server.
2 Type config general ftpserver enable and <Enter>.See Figure 3-13, CLI
FTP Server Setting.
Figure 3-13 CLI FTP server settings

3 Login to the pre-R7.0 NE to be upgraded and follow the procedure.

Where <ip> is the loopback ip address of the GNE/RNE where DFTP server is enabled.

Where for SWNE <userid> is UserSWNE
Enter password:

Where <pw> is the password for the SWNE userid UserSWNE.
Note: The default password for UserSWNE is Ftp-id#1

Where for SWNE <path> is the /dftp/swp/EC

Software Server Userid : UserSWNE



Operation :
Operation Status :
Verify the current active software is directly upgradeable to 1830PSSECX-7.0-2 as

shown Table 5, "Software upgrade path summary for 1830PSSECX-7.0-2".
10 Proceed to Step 8 in CLI procedure for 1830PSSECX-7.0-2 software upgrade without

SWNE feature.
END OF STEPS
CLI procedure for 1830PSSECX-7.0-2 software upgrade without SWNE feature
1 If not logged in, login to the NE to be upgraded following the procedure.

Where <ip> is the ip address of the PC with the FTP server. Use the IP address verified
in Step 7 in PC preparation.

Where <userid> is the userid for the user account defined on the ftp server.
Enter password:
Refer to FTP server configuration.


Where <pw> is the password for the user account defined on the ftp server.
Refer to FTP server configuration.

directory.
<path>.



Operation :

Operation Status :
Verify the current active software is directly upgradeable to 1830PSSECX-7.0-2 as

shown Table 5, "Software upgrade path summary for 1830PSSECX-7.0-2".
are equipped in all extension shelves and ensure the duplex controller status in the master
8 Type config software upgrade manual audit <releasedir>

nobackupforce and <Enter>.
Note: nobackupforce is only required if upgrading to 1830PSSECX-7.0-2 from a
non-ECX software load. Refer to Upgrade paths.
Where <releasedir> is 1830PSSECX-7.0-2 folder name present in the SWNE server or
the folder name on the PC containing the software.
This step checks the path and verifies that the system is ready for upgrade.

A listing of packs will be displayed along with the status showing which packs need to be

Committed Release : 1830PSS32-5.1-0
Operation : Audit
Upgrade Path Available : FLASE

RESULT: Success

RESULT: None

RESULT: None

RESULT: None

RESULT: None

RESULT: None


RESULT: None

RESULT: None

RESULT: None
10 Repeat Step 9 until the Operation Status indicates Completed. Verify Upgrade Path

This will transfer the software to the NE.

...
Operation : Load
...
Completed.
13 For any system with simplex EC, proceed to Step 14 if nobackupforce option is being
used.
software upgrade.

command until the In-Service-Upgrade (ISUG) to Release 7.0.2 completes.
the Activate stage as described in Step 8 to Step 12. The Audit and Load steps need to
be performed in order to ensure that the appropriate packs are activated properly. The

This will activate the software on the NE.
Important! If upgrading a GMPLS network with an active control plane, avoid

activating more than one neighbor NE simultaneously.
15 The NE will reboot and the telnet connection will drop. Wait about 2 minutes after the
fan speed drops back down to normal speed and log back into the NE.


...
...
Note: The output will also display the progress of the activation on each of the
packs in the NE. The Operation Status will not show completed until all packs have
been activated on the new release.
17 Type show software ne brief and <Enter>.

Ensure that all circuit packs have been activated to PSSECX Release 7.0.2.
unaffected.
software.

these conditions.

WTOCM circuit packs. Once the firmware has been upgraded the tilt adjustment can
be restarted.
19 Type config software upgrade commit and <Enter>.



...
Operation : Commit
...
Completed.
21 After the last status command is executed, verify the new software release is displayed as
the committed, working and active release. See the sample output below:

Committed Release : 1830PSSECX-7.0-2
Working Release : 1830PSSECX-7.0-2
Operation : Commit

Verify the current active software is PSSECX Release 7.0.2.
22 Repeat step Step 1 through Step 21 for each NE to be upgraded.
23 If upgrading a GMPLS network with an active control plane, after the SW has been
committed on all the NEs in the network, please refer to Alcatel-Lucent 1830 Photonic
Service Switch (PSS) Release 7.0 GMPLS/GMRE Guide to update the active network
version.

24 The software upgrade is now complete. A backup should be performed on all upgraded
NEs referring to the procedure CLI procedure for database backup.
END OF STEPS
CLI procedure for 1830PSSECX-7.0-2 software roll back to previous release
Pre-requisite:
Purpose
not been committed.
CLI procedure for software rollback to previous release


Committed Release :
Working Release :

Verify the Committed Release is not 7.0.2
2 Type config software upgrade backout and <Enter>.

WARNING: You are about to perform a backout.
This may be service affecting.
Enter 'yes' to confirm, 'no' to cancel:
4 The NE will reboot. Wait about 2 minutes after the fan speed drops back down to normal
speed and log back into the NE.
5 Type show version and <Enter>

Software Version: 1830PSSECX-6.0-6
Verify the software version is restored to the original release version before the software
upgrade.
6 Type config software upgrade commit and <Enter>

7 The software rollback is now complete.

END OF STEPS

Software Installation and Upgrade WebUI instructions
WebUI instructions
Overview
This section provides WebUI instructions for the following procedures:
Database backup
Software upgrade
WebUI procedure for 1830PSS-7.0-2 new software installation

This section provides WebUI instructions for new software installation. If software
upgrade operation is needed, please proceed to WebUI procedure for 1830PSS-7.0-2
software upgrade.
Important! Perform these steps only after following New software installation
general instruction.
Steps
1 Select the Software menu item under Administration and then select FTP Server. The
FTP server settings window appears as shown in Figure 3-14, WebUI FTP server
settings.
Figure 3-14 WebUI FTP server settings

2 Enter NE IP address obtained earlier in PC preparation for the Server IP Address.
3 Enter the path to the NE software relative to the server root directory in
the Root Directory field.
Note: If the software folder was copied directly into the root directory, enter / in this
field.
4 Enter the UserID and Password to match the account created on the FTP server.
5 Click the Apply button.
Note: The Password fields will be blanked out after you click Apply. There is
no need to reenter the data.
6 Select Administration > Software > Upgrade from the top menu.
7 The Software Upgrade window appears as shown in Figure 3-15, WebUI software
upgrade .
Note: The software release will be the current factory load.
Figure 3-15 WebUI software upgrade
8 Select Audit from the Action Type drop down list.

9 Enter the folder name containing the NE software in the Release Directory field.
Note: This field can only be edited after Audit has been selected for the Action
Type.
10 Select the Force Upgrade option from the Audit Settings.
11 Click Apply. The Status field will change to In Progress.
12 Periodically click the Refresh button until the Status field changes to Completed.
Verify the Result is Success and the Upgrade Path Available field indicates Yes.
13 Select Download for the Action Type and click Apply. The Status field will
change to In Progress.
Verify the Result is Success.
15 Select Activate for the Action Type and click Apply. The Status field will
change to In Progress. The NE will then reboot, and the WebUI will automatically
logout.
16 Wait about 2 minutes after the fan speed drops back down to normal speed and log back
into the NE.
17 Login to CLI following the procedure Connect to the NE for CLI access.
Type config database clear and <Enter>.
This will close any sessions connected to the NE and cause the NE to reboot.
18 Login to WebUI and verify the DBINVALID alarm has cleared and a no committed
software alarm is present. Return to the Software Upgrade window by selecting
Administration > Software > Upgrade from the top menu.

19 Select Commit for the Action Type and click Apply. The Status field will
21 Verify the Active and committed releases have changed to the new release.
detailed steps.
END OF STEPS
WebUI procedure for 1830PSS-7.0-2 software upgrade
instruction.
Connect to the NE for WebUI access

You can connect remotely or directly to the Network Element (NE) to access the web
interface (WebUI). No client software is needed on your PC, only Internet Explorer.
Note: Popup blockers should be turned off, and proxy servers should not be used in
Internet Explorer.
Connect and login to NE

If connecting remotely to the NE, skip to Step 5.
2 Connect one end of the Ethernet cable to the CIT port on the active (indicated by a green
Active LED) EC card (PSS-16/32) on the master shelf. Connect the other end of the cable
to the Ethernet port on your PC.

3 Open a PC command shell and type ipconfig and <Enter>. Verify the NE has assigned
an IP address to your PC. The PC IP address should be in the same subnet as the CIT port
IP address. See Figure 3-16, PC command window.
Note: Typically the PC IP address will be 172.16.0.x.
4 Launch Internet Explorer and enter http:// followed by the CIT IP address in the
Address bar and click Go.
Note: The default CIT IP address is 172.16.0.1.

Proceed to Step 7.
6 Launch Internet Explorer.

If the NE is a GNE, enter http:// followed by the OAMP IP address of the NE in the
If the NE is a RNE, enter http:// followed by the Loopback IP address of the NE in the
Note: Use https:// when using WebUI in encrypted mode.
GNE node.
7 The browser connects to the network element and the WebUI login window is displayed.
See Figure 3-17, "Login_Screen".

Figure 3-17 Login Screen
button.
Note: If the login and password have changed from the default, obtain this
information from the network administrator.
9 The WebUI interface will open with the system properties view as shown in Figure 3-18,
"WebUI system properties".

Figure 3-18 WebUI system properties
10 Click on the Alarms icon and verify there are no unexpected alarms. Refer to the Alcatel-
Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Maintenance and Trouble-
Clearing Guide for troubleshooting assistance.
11 Proceed to WebUI procedure for database backup.

END OF STEPS
WebUI procedure for database backup

A database backup must be performed on each NE before beginning the upgrade. The
upgrade.
1 Start the TFTP server application on your PC.
2 Create a folder under the TFTP root directory where you would like to store the backup.

3 Open Windows Firewall from the Control Panel. Refer to Figure 3-19, "Windows
Firewall settings"
5 Open a PC command shell and type ipconfig and <Enter>. Note the IP address
assigned to your PC. This will be used later in the procedure. Refer to Figure 3-20, "PC
Command window".

6 Select Administration > Database from the top menu.
7 The database backup/restore window will be displayed as shown in Figure 3-21, WebUI
backup/restore window.
Figure 3-21 WebUI backup/restore window
8 Enter your PC IP address obtained previously in the Server IP Address field.
9 Enter the path relative to the TFTP server root directory to the location
where the backup will be stored in the Directory field.
10 Enter a descriptive filename for the backup file with a .bak extension in the Filename
field.
11 Click the Apply button and the Backup button will become available.
12 Click the Backup button.

13 Wait a few seconds and click the Refresh button. Repeat this step until the Last
Command Status indicates Success.
14 Repeat this procedure for each NE that will be upgraded.

END OF STEPS
1830PSS-7.0-2 software upgrade with or without SWNE feature (WebUI)

If using WebUI with SWNE feature, continue with WebUI procedure to 1830PSS-7.0-2
software upgrade with SWNE feature
If using WebUI without SWNE feature, proceed to WebUI procedure to 1830PSS-7.0-2
software upgrade without SWNE feature
WebUI procedure to 1830PSS-7.0-2 software upgrade with SWNE feature

Note: In order to use the SWNE feature in R7.0.2, one NE needs to be running 1830PSS-
7.0-2 and committed before it can be used as the Software Server NE (SWNE).
instruction.
1 Login to the R7.0 NE to enable DFTP server following the procedure Connect to the NE
for WebUI access.
2 From the top menu select Adminstartion > Software > Software NE
3 The Software NE settings window appears as shown in Figure 3-22, Software NE.

Figure 3-22 Software NE
4 Select Ftp Server Enabled and press the Apply button.
5 Login to the NE to be upgraded following the procedure Connect to the NE for WebUI
access.
6 From the top menu select Administration > Software > FTP Server.
7 In the active WebUI window the FTP server settings window appears as shown in Figure
3-23, WebUI FTP server settings.

8 Enter the SWNE GNE/RNE loopback ip address obtained previously in the Server IP
Address field.
9 Enter the path /dftp/swp/EC in the Root Directory field.
10 Enter the User ID : UserSWNE and Password to match the SWNE Server setting.
Note: By default the UserSWNE password is Ftp-id#1
Note: The Password fields will be blanked out after you click Apply. There is no
need to reenter that data.
12 Proceed to Step 8 in WebUI procedure to 1830PSS-7.0-2 software upgrade without

SWNE feature.
END OF STEPS
WebUI procedure to 1830PSS-7.0-2 software upgrade without SWNE feature
instruction.
access.
3 The FTP server settings window appears as shown in Figure 3-24, "WebUI FTP Server".

4 Enter the PC IP address obtained previously in the Server IP Address field.
field.
6 Enter the User ID and Password to match the account created on the ftp server.
8 Select the Software menu item under Administration and then select Upgrade.
9 The Software Upgrade window appears as shown in Figure 3-26, WebUI software
upgrade" Verify the committed release is is directly upgradeable to Release 7.0.2 as
shown in Table 4, "Software upgrade path summary for 1830PSS-7.0-2".

Figure 3-25 WebUI software upgrade
are equipped in the extension shelve and ensure the duplex controller status in the master
11 Enter the folder name containing the NE software in the Release Directory dialogue
box.
Type.
Note: If audit fails, confirm all FTP settings are correct. Delete cookies on PC and
re-try.
Verify the Result is Success and the Upgrade Path Available: field indicates
Yes.

14 Select Download for the Action Type and click Apply. The Status: field will
15 Periodically click the Refresh button until the Status: field changes to Completed.
software upgrade.
command until the In Service Upgrade (ISUG) to Release 7.0.2 completes.
DBUNSYNC - Active and standby Main EC databases are not synchronized.
UNKNOWN - Card unknown Equipment Controller.
the Activate stage as described in Step 10 to Step 15. The Audit and Load steps need
to be performed in order to ensure the appropriate packs are activated properly. The

17 Select Activate for the Action Type and click Apply. The Status: field will
18 A warning appears. Click OK. The NE will then reboot and the WebUI connection will
drop.
into the NE.
20 Return to the Software Upgrade window by selecting Administration > Software >
Upgrade from the top menu. Verify the Status field now indicates Completed, and
verify the Result is Success.
21 In Card View Details check that the EC and LC pack display the software load as
1830PSS-7.0-2.
unaffected.
software.

these conditions.

WTOCM circuit packs. Once the firmware has been upgraded, the tilt adjustment can
be restarted.

25 Verify the Active and Committed releases have changed to Release 7.0.2.
26 Repeat Step 1 through Step 25 for each NE to be upgraded.
27 The software upgrade is now complete. A backup should be performed referring to the
procedure WebUI procedure for database backup.
END OF STEPS
WebUI procedure for 1830PSS-7.0-2 software rollback to previous release
Pre-requisite:
Purpose
This procedure can only be performed if the Release 7.0.2 software has not been
committed.
WebUI procedure for software rollback to previous release
1 Select the Administration > Software > Upgrade from the top menu.
2 The Software Upgrade window appears.

3 Verify the Release 7.0.2 software is not yet committed.
4 Select Revert from the Action Type drop down list and click the Apply button.
5 A warning, shown in Figure 3-26, WebUI software revert warning window", appears.
Click the OK button.
Important! During reversion, ensure that data communications with the remote
database backup server is maintained at all times. Reversion may fail if a network
element cannot communicate with the server. Avoid reverting more than one NE
Important! If rolling back a GMPLS network with an active control plane, avoid
reverting more than one neighbor NE simultaneously.
Figure 3-26 WebUI software revert warning window
into the NE.
7 Select Administration > Software > Upgrade from the top menu:
Verify Status field indicates Complete, and verify the Result field indicates
Success.
8 Select Commit for the Action Type and click Apply.

The status field will change to In Progress.
10 Verify the working and active software release is restored to the original release version
before the upgrade.

11 Check and make sure there are no unexpected alarms.
12 The software roll back is complete.

END OF STEPS

WebUI procedures for 1830PSSECX-7.0-2 software

This section provides WebUI instructions for the following procedures:
Database backup. Refer to WebUI procedure for database backup.
Software upgrade
WebUI procedure for 1830PSSECX-7.0-2 new software installation

This section provides WebUI instructions for new software installation. If software
upgrade operation is needed, please proceed to WebUI procedure for 1830PSSECX-7.0-
2 software upgrade.
Important! Perform these steps only after following New software installation
general instruction.
Steps
1 Select the Software menu item under Administration and then select FTP Server. The
FTP server settings window appears as shown in Figure 3-27, "WebUI ECX - FTP server
settings" .
Figure 3-27 WebUI ECX - FTP server settings
2 Enter NE IP address obtained earlier in PC preparation for the Server IP Address.

field.
4 Enter the UserID and Password to match the account created on the FTP server.
Note: The Password fields will be blanked out after you click Apply. There is
no need to reenter the data.
6 Select Administration > Software > Upgrade from the top menu.
7 The Software Upgrade window appears as shown in Figure 3-28, WebUI ECX software
upgrade .
Note: The software release will be the current factory load.
Figure 3-28 WebUI ECX software upgrade

9 Enter the folder name containing the NE software in the Release Directory field.
Type.
Verify the Result is Success and the Upgrade Path Available field indicates Yes.
12 Select Download for the Action Type and click Apply. The Status field will
14 Select Activate for the Action Type and click Apply. The Status field will
change to In Progress. The NE will then reboot, and the WebUI will automatically
logout.
into the NE.
16 Login to CLI following the procedure Connect to the NE for CLI access.
Type config database clear and <Enter>.
This will close any sessions connected to the NE and cause the NE to reboot.
17 Login to WebUI and verify the DBINVALID alarm has cleared and a no committed
software alarm is present. Return to the Software Upgrade window by selecting
Administration > Software > Upgrade from the top menu.

20 Verify the Active and committed releases have changed to the new release.
21 If installing a GMPLS network with an active control plane, after the SW has been
committed on the NE, refer to the GMPLS/GMRE guide to activate the GMRE.
detailed steps.
END OF STEPS
WebUI procedure for 1830PSSECX-7.0-2 software upgrade
instruction.
Connect to the NE for WebUI access

You can connect remotely or directly to the Network Element (NE) to access the web
interface (WebUI). No client software is needed on your PC, only Internet Explorer.
Note: Popup blockers should be turned off, and proxy servers should not be used in
Internet Explorer.
Connect and login to NE
1 If connecting locally at the NE, continue with Step 2.

If connecting remotely to the NE, procced to Step 5.

2 Connect one end of the Ethernet cable to the CIT port on the active (indicated by a green
Active LED) EC card (PSS-16/32) on the master shelf. Connect the other end of the cable
to the Ethernet port on your PC.
3 Open a PC command shell and type ipconfig and <Enter>. Verify the NE has assigned
an IP address to your PC. The PC IP address should be in the same subnet as the CIT port
IP address. See Figure 3-29, PC command window.
Note: Typically the PC IP address will be 172.16.0.x.
4 Launch Internet Explorer and enter http:// followed by the CIT IP address in the
Note: The default CIT IP address is 172.16.0.1.

Proceed to Step 7.
6 Launch Internet Explorer.

If the NE is a GNE, enter http:// followed by the OAMP IP address of the NE in the
If the NE is a RNE, enter http:// followed by the Loopback IP address of the NE in the
Note: Use https:// when using WebUI in encrypted mode.
GNE node.

7 The browser connects to the network element and the WebUI login window is displayed.
See Figure 3-30, "WebUI ECX - Login Screen".
Figure 3-30 WebUI ECX - Login Screen
button.
Note: If the login and password have changed from the default, obtain this
information from the network administrator.
9 The WebUI interface will open with the system properties view as shown in Figure 3-31.
"WebUI ECX system properties".

Figure 3-31 WebUI ECX system properties
10 Click on the Alarms icon and verify there are no unexpected alarms. Refer to the Alcatel-
Lucent 1830 Photonic Service Switch Maintenance and Trouble-Clearing Guide for
troubleshooting assistance.
11 Proceed to WebUI procedure for database backup.

END OF STEPS
1830PSSECX-7.0-2 software upgrade with or without SWNE feature (WebUI)

If using WebUI with SWNE feature, continue with WebUI procedure for 1830PSSECX-7.0-2
software upgrade with SWNE feature.
If using WebUI without SWNE feature, proceed to WebUI procedure for 1830PSSECX-7.0-2
software upgrade without SWNE feature.
WebUI procedure for 1830PSSECX-7.0-2 software upgrade with SWNE feature

(SWNE).
instruction.
1 Login to the R7.0 NE to enable DFTP server following the procedure Connect to the NE
for WebUI access.
2 From the top menu select Adminstartion > Software > Software NE
3 The Software NE settings window appears as shown in Figure 3-32, WebUI Software
NE.
Figure 3-32 WebUI Software NE
4 Select Ftp Server Enabled and press the Apply button.
access.
7 In the active WebUI window the FTP server settings window appears as shown in Figure
3-33, WebUI ECX FTP server settings.

Figure 3-33 WebUI ECX FTP server settings
8 Enter the SWNE GNE/RNE loopback ip address obtained previously in the Server IP
Address field.
9 Enter the path /dftp/swp/EC in the Root Directory field.
12 Procedure to Step 8 in WebUI procedure for 1830PSSECX-7.0-2 software upgrade

without SWNE feature.
END OF STEPS
WebUI procedure to 1830PSSECX-7.0-2 software upgrade without SWNE feature
instruction.
access.

3 The FTP server settings window appears as shown in Figure 3-34, "WebUI ECX FTP
serve settings".
Figure 3-34 WebUI ECX FTP server settings
4 Enter the PC IP address obtained previously in the Server IP Address field.
field.
6 Enter the User ID and Password to match the account created on the ftp server.
8 Select the Software menu item under Administration and then select Upgrade.

9 The Software Upgrade window appears as shown in Figure 3-35, WebUI ECX software
upgrade" Verify the committed release is directly upgradeable to Release 7.0.2 as shown
in Table 5, "Software upgrade path summary for 1830PSSECX-7.0-2".
Figure 3-35 WebUI ECX software upgrade
11 Enter the folder name containing the NE software which is 1830PSSECX-7.0-2 in the
Release Directory dialogue box.
Type.
12 Select the Force Upgrade option from the Audit Settings.

Note: The Force Upgrade option should be selected when nobackupforce is being
used. nobackupforce is only required if upgrading to 1830PSSECX-7.0-2 from a non-
ECX software load. Refer to Upgrade paths.

Note: If audit fails, confirm all FTP settings are correct. Delete cookies on PC and
re-try.
Verify the Result is Success and the Upgrade Path Available: field indicates
Yes.
15 Select Download for the Action Type and click Apply. The Status: field will
used.
software upgrade.
UNKNOWN - Card unknown Equipment Controller.

18 Select Activate for the Action Type and click Apply. The Status: field will
19 A warning appears. Click OK. The NE will then reboot and the WebUI connection will
drop.
into the NE.
21 Return to the Software Upgrade window by selecting Administration > Software >
Upgrade from the top menu. Verify the Status field now indicates Completed, and
verify the Result is Success.
22 In Card View Details check that the EC and LC pack display the software load as
1830PSSECX-7.0-2.
unaffected.

software.

these conditions.

be restarted.
26 Verify the Active and Committed releases have changed to Release 7.0.2.
27 Repeat Step 1 through Step 27 for each NE to be upgraded.
committed on all the NEs in the network, please refer to Alcatel-Lucent 1830 Photonic
Service Switch (PSS) Release 7.0 GMPLS/GMRE Guide to update the active network
version.
29 The software upgrade is now complete. A backup should be performed referring to the
procedure WebUI procedure for database backup.
END OF STEPS

WebUI procedure for 1830PSSECX-7.0-2 software rollback to previous release
Pre-requisite:
Purpose
This procedure can only be performed if the Release 7.0.2 software has not been
committed.
WebUI procedure for software rollback to previous release
1 Select the Administration > Software > Upgrade from the top menu.
2 The Software Upgrade window appears.
3 Verify the Release 7.0.2 software is not yet committed.
4 Select Revert from the Action Type drop down list and click the Apply button.
5 A warning, shown in Figure 3-36, WebUI software revert warning window", appears.
Click the OK button.
Important! During reversion, ensure that data communications with the remote
database backup server is maintained at all times. Reversion may fail if a network
element cannot communicate with the server. Avoid reverting more than one NE
reverting more than one neighbor NE simultaneously.

Figure 3-36 WebUI software revert warning window
into the NE.
7 Select Administration > Software > Upgrade from the top menu:
Verify Status field indicates Complete, and verify the Result field indicates
Success.
8 Select Commit for the Action Type and click Apply.

The status field will change to In Progress.
10 Verify the working and active software release is restored to the original release version
before the upgrade.
11 Check and make sure there are no unexpected alarms.
12 The software roll back is complete.

END OF STEPS

Software Installation and Upgrade PhM instructions
PhM instructions
Overview
This section provides PhM instructions for the following procedures:
Database backup
Software upgrade
PhM procedure for database backup

A database backup must be performed on each NE before begining the upgrade. The
upgrade.
For 1354 RM-PhM Photonic Manager, the software comes with its own TFTP server.
1354 RM-PhM procedure for database backup

The procedure assumes the 1354 RM-PhM Photonic Manager server is already connected
to the network, and all the NEs have been discovered.
1 Select Admin > Settings... from the top menu in the Topology View window.
2 In the Settings window select the System Settings top tab and then the File Transfer
sub-tab.
3 Verify the root directory is /tftpfiles in the TFTP Root Directory (/PhM by default) of the
1354 RM-PhM server.
4 Click OK.
5 Select the NE you want to backup in the Topology View window.
6 Select Maintenance > NE Database Backup & Restore from the top menu bar as shown
in Figure 3-37, 1354 RM-PhM NE backup menu".

Figure 3-37 1354 RM-PhM NE backup menu
7 Click the OK button and the NE backup & Restore window, shown in Figure 3-38,
1354 RM-PhM NE backup", appears.
Figure 3-38 1354 RM-PhM NE backup
8 Right click on the NE and select Details... from the menu as shown in Figure 3-39,
1354 RM-PhM NE backup details menu".

Figure 3-39 1354 RM-PhM NE backup details menu
9 In the Backup Properties window check both Use the EMS Server as Backup host
recommended and Use default backup directory recommended.
10 Click OK.
11 Make sure the NE is selected in the list and click on the Backup selected NE(s) icon as
shown in Figure 3-40, 1354 RM-PhM NE backup icon".
Figure 3-40 1354 RM-PhM NE backup icon
12 The backup progress appears in the bottom half of the Backup & Restore window. Wait
for the Backup Success message.
13 Verify the database backup file is present in the PhM server PC. The path is
C:\PhM\nebackup\<NE name>\<filename>.
Where <filename> has the format <NE name>_<release descriptor>_<backup
date>_<backup time>.bak.
14 Are there additional NEs that have not been backed up?
If yes, repeat Step 5.
If no, this procedure is complete.
END OF STEPS

1830PSS-7.0-2 software upgrade with or without SWNE feature (PhM)
If using PhM with SWNE feature, continue with 1354 RM-PhM procedure for 1830PSS-7.0-2
software upgrade with SWNE feature".
If using PhM without SWNE feature, proceed to 1354 RM-PhM procedure for 1830PSS-7.0-2
software upgrade without SWNE feature".
1354 RM-PhM procedure for 1830PSS-7.0-2 software upgrade with SWNE feature
Note: In order to use the SWNE feature in R7.0.2, one NE needs to be running 1830PSS-
7.0-2 and committed before it can be used as the Software Server NE (SWNE).
instruction".
Important! Before using DFTP via PhM, the FTP port should be enabled in the GNE
using ACL feature as explained below using WebUI.
Procedure for enabling ftp port using WebUI in GNE.
1 In WebUI, Enable ACL Configuration via SNMP, By clicking Administration > Security
> Access Control List > System Defaults, "ACL Configuration via SNMP Enabled:"
option.
2 Create a Pattern, by clicking create button under Administration > Security > Access
Control List > Patterns.
1. Type a PatternID for example: dftppattern
2. Select Action as PASS
3. Type GNEs IP address as Designation IP.
4. Select IP Protocol as TCP
5. Type TCP/UDP Destination Port as 21
6. Save the pattern.
3 Create a Filter, by clicking Create button under Administration > Security > Access
Control List > Filters.
Type a FilterID for example: dftpfilter
4 Go to Administration > Security > Access Control List > Filters and select dftpfilter and
click Add Pattern Button.
1. Select the Filter ID as dftpfilter

2. Select the Pattern ID as dftppattern

3. Type Pattern Index as 1 <any number between 1-256 is valid>
5 Go to Administration > Security > Access Control List > Ports.

Select the Port Name as 1/40/OAMP and click details.
2. Save it by clicking the Apply button
6 In PhM use the GNEs IP address to connect to SW Server.
After the above procedures, software upgrade with DFTP via PhM can proceed.
7 In the topology view, select one R7.0 GNE NE which the SWNE need to be enabled.
8 Select Maintenance > NE Software Upgrade from the top menu as show in Figure 3-41,
1354 RM-PhM software upgrade menu".
Figure 3-41 1354 RM-PhM software upgrade menu
9 The software upgrade window displays as shown in Figure 3-42, 1354 RM-PhM
software upgrade window". Each NE selected is shown in the list.

Figure 3-42 1354 RM-PhM software upgrade window
10 From the Software Upgrade window Select View > Details.
The Software properties settings window appears as shown in Figure 3-43, 1354 RM-
PhM software upgrade properties window".
Figure 3-43 1354 RM-PhM software upgrade properties window
11 Check the Ftp Server Enabled box and click OK.

12 From the Software Upgrade window Select File > AddNE.

The Add NEs window appears as shown in Figure 3-44, 1354 RM-PhM Add NEs
window".
Figure 3-44 1354 RM-PhM Add NEs window
13 Select the pre-R7.0 NE to be upgraded and click OK.
14 The added pre-R7.0 NE will be listed in the Software Upgrade window.
15 Uncheck the EMS is SW Server box and enter the GNE/RNE LoopbackIP address of
the SWNE server where the software resides. Also select the FTP radio button.

17 Click on the folder icon next to Target Dir: then click the Connect button and a
browser window will open as shown in Figure 3-45, 1354 RM-PhM target directory
window".
Figure 3-45 1354 RM-PhM target directory window
18 For 1830PSS-16/32 Select the path /dftp/swp/ECand the 1830PSS-7.0-2 folder.
19 Proceed to Step 9 in 1354 RM-PhM procedure for 1830PSS-7.0-2 software upgrade

without SWNE feature".
1354 RM-PhM procedure for 1830PSS-7.0-2 software upgrade without SWNE feature
instruction.
1 Copy the folder and subfolders with the NE software into the ftp root directory (/PhM by
default) of the 1354 RM-PhM server.

copied is either 1830PSS-7.0-2 (no support for GMPLS). For 1830PSS-7.0-2 locate
the desired subfolder from within the parent EC folder. Inclusive to the software
folder, there are three subfolders named 1830PSS, 1830PSSM and usbkey, as
well as a CATALOG file. The software folder should be copied to the FTP server in
its entirety. The software will typically be provided on DVD or downloaded from the
Alcatel-Lucent OnLine Customer Support (OLCS) web site.
2 In the topology view, select one or more NEs to be upgraded. (Use <ctrl> and left mouse
button to select multiple NEs.)

Note: NEs should be selected in groups starting with the furthest from the GNE.
When upgrading a network with GNE and RNE nodes, it is recommended to upgrade
the RNE nodes farthest from the GNE node first, then work back toward the GNE
node.
Important! If upgrading multiple Alcatel-Lucent 1830 PSS-16/PSS-32 NEs that are

connected to a single Alcatel-Lucent 1830 PSS-16/PSS-32 NE via GCC links, only
one NE should be upgraded at a time.
1354 RM-PhM software upgrade menu".
Figure 3-46 1354 RM-PhM software upgrade menu
4 The software upgrade window will be displayed as shown in Figure 3-47, 1354 RM-
PhM software upgrade window". Each NE selected is shown in the list.

5 If the software resides on the same machine as the 1354 RM-PhM, then the EMS is SW
Server checkbox can be checked (this is typical). Otherwise, uncheck the box and enter
the IP address of the server where the software resides. Also select the FTP radio button.
6 Enter the User ID and Password of the FTP server.
Note: The 1354 RM-PhM User ID and Password can be provisioned by selecting
Admin > Settings... from the topology window top menu and entering the User ID
and Password in the file transfer window. Then click OK.
browser window will open as shown in Figure 3-48, 1354 RM-PhM target directory
window".

Figure 3-48 1354 RM-PhM target directory window
8 For 1830PSS-16/32 Select the 1830PSS-7.0-2 folder.
9 Select the Backup checkbox. Leave the Check Upgrade checkbox unselected.
Note: A backup must be performed on all NEs to be upgraded. Refer to 1354 RM-PhM
procedure for database backup.
10 The top of the software upgrade windows has a series of software phase icons as shown
in Figure 3-49, 1354 RM-PhM software upgrade phase icons". Each icon will be used in
phase 1 through 4 of the upgrade.
Figure 3-49 1354 RM-PhM software upgrade phase icons
11 Make sure all the NEs to be upgraded are highlighted and click on the phase 1 icon to
start the audit and verify there is an upgrade path. A confirmation window, shown
in Figure 3-50, 1354 RM-PhM software upgrade audit confirmation window", appears.

Figure 3-50 1354 RM-PhM software upgrade audit confirmation window
12 Click Yes and the audit will start. When the audit is complete, verify that the status
shows Completed - Success for each NE.
start the software load. A warning window, shown in Figure 3-51, 1354 RM-PhM
software load warning", appears.
Figure 3-51 1354 RM-PhM software load warning
14 Click Yes and the software load will start. The progress of the load operation will be
shown in the software upgrade window. Wait for the load to complete and verify the
status field shows Completed - Success for each of the NEs.

software upgrade.
Load step will not re-load the NE software unless prior Load step has not been
16 Make sure all the NEs to be upgraded are highlighted and click the phase 3 icon to start
the activation of the software. A warning window, shown in Figure 3-52, 1354 RM-PhM
software activate warning", appears.

Figure 3-52 1354 RM-PhM software activate warning
17 Click Yes to start the activation.
Note: If there are any unacknowledged alarms, they will be displayed in a separate
window as shown in Figure 3-53, 1354 RM-PhM Software Upgrade alarm
acknowledge window".Verify there are no unexpected alarms, then highlight them
and click the check mark icon to acknowledge them. Close the window and resume
the activation.
Figure 3-53 1354 RM-PhM software upgrade alarm acknowledge window
18 Communication will be temporarily lost to each of the NEs while they are reset. As
communication is restored, the activation progress appears in the software upgrade
window. Wait for the activation to complete and verify the status field shows Completed
- Success for each of the NEs.
19 In Card Inventory check that EC and LC display software version as 1830PSS-7.0-2.

20 Check for unexpected alarms and conditions on the NEs and make sure traffic is still
unaffected.
software.

these conditions.

suspended until users complete the Normal firmware upgrade (cold reboot) on the
be restarted.
21 Make sure all the NEs that have been upgraded are highlighted and click the phase 4 icon
to commit the software. A warning window, shown in Figure 3-54, 1354 RM-PhM
software commit warning", appears.
Figure 3-54 1354 RM-PhM software commit warning
22 Click Yes. Once the commit is complete verify the status field shows Completed -
Success for each of the NEs.
23 Repeat Step 2 through Step 22 for each NE or group of NEs that will be upgraded.

24 The software upgrade is complete. A backup should be performed on all upgraded NEs
referring to the procedure 1354 RM-PhM procedure for database backup.
software upgrade.
END OF STEPS
PhM procedure for 1830PSS-7.0-2 software rollback to previous release
Pre-requisite:
Purpose
The following procedure allows the user to remotely roll back the Alcatel-Lucent 1830
PSS-16/PSS-32 Network Element software to the previous software release. This
not been committed.

1354 RM-PhM procedure for software rollback to previous release
1 The software upgrade window should be open. See Figure 3-55, 1354 RM-PhM
software upgrade window.
2 Verify Release 7.0.2 has not been committed on the NE(s) to be backed out.
3 Select the NE(s) to be backed out and select Action > Back out from the software
upgrade menu. See Figure 3-56, 1354 RM-PhM software backout menu.

Figure 3-56 1354 RM-PhM software backout menu
4 A warning message appears as shown in Figure 3-57, 1354 RM-PhM software backout
warning".
Figure 3-57 1354 RM-PhM software backout warning
5 Click Yes. Communication is temporarily lost to each of the NEs while they are reset.
As communication is restored, the backout progress appears in the software upgrade
window. Wait for the backout to complete and verify the status field shows Completed -
Important! During backout, ensure that data communications with the remote
database backup server is maintained at all times. Backout may fail if a network
element cannot communicate with the server. Avoid backing out more than one NE
backing out more than one neighbor NE simultaneously.

6 Ensure the backout operation status field shows completed, then click the phase 4 icon to
commit the software. A warning window as shown in Figure 3-58, 1354 RM-PhM
software commit warning, is displayed.
Click Yes.
When the commit is complete verify the status field as Completed-Success.
7 Verify the active and committed release software is restored to the original release
version before the upgrade.
8 The software roll back is now complete.

END OF STEPS
PhM procedure for 1830PSSECX-7.0-2 software upgrade

This section provides PhM instructions for the following procedures:
Database backup
Software upgrade
1830PSSECX-7.0-2 software upgrade with or without SWNE feature (PhM)
Note: A backup must be performed on all NEs to be upgraded. Refer to 1354 RM-PhM
procedure for database backup.
If using PhM with SWNE feature, continue with "1354 RM-PhM procedure for 1830PSSECX-
7.0-2 software upgrade with SWNE feature.
If using PhM without SWNE feature, proceed to "1354 RM-PhM procedure for 1830PSSECX-
7.0-2 software upgrade without SWNE feature".

1354 RM-PhM procedure for 1830PSSECX-7.0-2 software upgrades with SWNE feature
(SWNE).
instruction".
Important! Before using DFTP via PhM, the FTP port should be enabled in the GNE
using ACL feature as explained below using WebUI.
Procedure for enabling ftp port using WebUI in GNE.
1 In WebUI, Enable ACL Configuration via SNMP, By clicking Administration > Security
> Access Control List > System Defaults, "ACL Configuration via SNMP Enabled:"
option.
2 Create a Pattern, by clicking create button under Administration > Security > Access
Control List > Patterns.
1. Type a PatternID for example: dftppattern
2. Select Action as PASS
3. Type GNEs IP address as Designation IP.
4. Select IP Protocol as TCP
5. Type TCP/UDP Destination Port as 21
6. Save the pattern.
3 Create a Filter, by clicking Create button under Administration > Security > Access
Control List > Filters.
Type a FilterID for example: dftpfilter
4 Go to Administration > Security > Access Control List > Filters and select dftpfilter and
click Add Pattern Button.
2. Select the Pattern ID as dftppattern
3. Type Pattern Index as 1 <any number between 1-256 is valid>
5 Go to Administration > Security > Access Control List > Ports.

Select the Port Name as 1/40/OAMP and click details.

2. Save it by clicking the Apply button
6 In PhM use the GNEs IP address to connect to SW Server.
After the above procedures, software upgrade with DFTP via PhM can proceed.
7 In the topology view, select one 1830PSSECX-7.0-2 GNE NE on the SWNE to be

enabled.
1354 RM-PhM PSSECX software upgrade menu"
Figure 3-59 1354 RM-PhM PSSECX software upgrade menu
9 The software upgrade window, shown in Figure 3-60, 1354 RM-PhM software upgrade
window", appears. Each NE selected is shown in the list.

Figure 3-60 1354 RM-PhM PSSECX software upgrade window
10 From the Software Upgrade window Select View > Details.
The Software properties settings window appears as shown in Figure 3-61, 1354 RM-
PhM software upgrade properties window"
Figure 3-61 1354 RM-PhM software upgrade properties window
11 Check the Ftp Server Enabled box and click OK.

12 From the Software Upgrade window Select File > AddNE.

The Add NEs window, shown in Figure 3-62, 1354 RM-PhM PSSECX - Add NEs
window", appears
Figure 3-62 1354 RM-PhM PSSECX - Add NEs window
13 Select the pre-R7.0 NE to be upgraded and click OK.
14 The added pre-R7.0 NE is listed in the Software Upgrade window.
15 Uncheck the EMS is SW Server box and enter the GNE/RNE LoopbackIP address of
the SWNE server where the software resides. Also select the FTP radio button.

browser window, shown in Figure 3-63, 1354 RM-PhM PSSECX target directory
window", appears.
Figure 3-63 1354 RM-PhM PSSECX target directory window
18 For 1830PSS-16/32 Select the path /dftp/swp/ECand 1830PSSECX-7.0-2 folder.
19 Continue to Step 9 in "1354 RM-PhM procedure for 1830PSSECX-7.0-2 software

upgrade without SWNE feature".
1354 RM-PhM procedure for 1830PSSECX-7.0-2 software upgrade without SWNE feature
instruction.
1 Copy the folder and subfolders with the NE software into the ftp root directory (/PhM by
default) of the 1354 RM-PhM server.

copied is 1830PSSECX-7.0-2 (supports GMPLS, requires 16GB Compact Flash on
all Equipment Controllers. Locate the desired subfolder from within the parent EC
1830PSSECX, 1830PSSECXM and usbkey, as well as a CATALOG file.The
software folder should be copied to the FTP server in its entirety. The software is
typically be provided on DVD or downloaded from the Alcatel-Lucent OnLine

2 In the topology view, select one or more NEs to be upgraded. (Use <ctrl> and left mouse
button to select multiple NEs.)
Note: NEs should be selected in groups starting with the furthest from the GNE.
When upgrading a network with GNE and RNE nodes, it is recommended to upgrade
the RNE nodes farthest from the GNE node first, then work back toward the GNE
node.
Important! If upgrading multiple Alcatel-Lucent 1830 PSS-16/PSS-32 NEs that are

connected to a single Alcatel-Lucent 1830 PSS-16/PSS-32 NE via GCC links, only
one NE should be upgraded at a time.
1354 RM-PhM PSSECX software upgrade menu".
Figure 3-64 1354 RM-PhM PSSECX software upgrade menu
4 The software upgrade window, shown in Figure 3-65, 1354 RM-PhM ECX software
upgrade window" appears. Each NE selected appears in the list.

Figure 3-65 1354 RM-PhM PSSECX software upgrade window
5 If the software resides on the same machine as the 1354 RM-PhM, then the EMS is SW
Server checkbox can be checked (this is typical). Otherwise, uncheck the box and enter
the IP address of the server where the software resides. Also select the FTP radio button.
6 Enter the User ID and Password of the FTP server.
Note: The 1354 RM-PhM User ID and Password can be provisioned by selecting
Admin > Settings... from the topology window top menu and entering the User ID
and Password in the file transfer window. Then click OK.
browser window, shown in Figure 3-66, 1354 RM-PhM ECX target directory window",
appears.

Figure 3-66 1354 RM-PhM PSSECX target directory window
8 For 1830PSS-16/32 Select 1830PSSECX-7.0-2 folder.
9 UnSelect the Backup checkbox. Leave the Check Upgrade checkbox unselected.
Note: The Backup and Check Upgrade boxes should be unchecked when
nobackupforce is being used. nobackupforce is only required if upgrading to
1830PSSECX-7.0-2 from a non-ECX software load. Refer to Upgrade paths.
Confirm that a database backup was performed on NEs to be upgraded. Refer

to 1354 RM-PhM procedure for database backup.
10 The top of the software upgrade windows has a series of software phase icons as shown
in Figure 3-67, 1354 RM-PhM PSSECX software upgrade phase icons". Each icon will
be used in phase 1 through 4 of the upgrade.
Figure 3-67 1354 RM-PhM PSSECX software upgrade phase icons
start the audit and verify there is an upgrade path. A confirmation window, shown

in Figure 3-68, 1354 RM-PhM PSSECX software upgrade audit confirmation window
1", appears.
Figure 3-68 1354 RM-PhM PSSECX software upgrade audit confirmation

window 1
Click Yes.

window 2

Click Yes, then select the Database backup file.

(PhM/ nebackup/<Ne name> / Older version DB File)

window 3
After Choosing the correct DB File (current of Software Release), click the Select
button.


window 4
12 Click Yes and the audit starts. When the audit is complete, verify that the status shows
Completed - Success for each NE.
start the software load. A warning window, shown in Figure 3-72, 1354 RM-PhM
PSSECX software load warning", appears.
Figure 3-72 1354 RM-PhM PSSECX software load warning

14 Click Yes and the software load starts. The progress of the load operation is shown in
the software upgrade window. Wait for the load to complete and verify the status field
shows Completed - Success for each of the NEs.
used.
software upgrade.
Release 7.0.2, the following minor, non-service affecting alarms are declared.
These two alarms are expected during the in-service upgrade and automatically clear
after the standby EC database is synchronized with the active EC.
Load step will not re-load the NE software unless prior Load step has not been

16 Make sure all the NEs to be upgraded are highlighted and click the phase 3 icon to start
the activation of the software. A warning window, shown in Figure 3-73, 1354 RM-PhM
PSSECX software activate warning", appears.
Figure 3-73 1354 RM-PhM PSECX software activate warning
17 Click Yes to start the activation.

Note: If there are any unacknowledged alarms, they appear in a separate window as
shown in Figure 3-74, 1354 RM-PhM PSSECX Software Upgrade alarm
acknowledge window".Verify there are no unexpected alarms, then highlight them
and click the check mark icon to acknowledge them. Close the window and resume
the activation.

Figure 3-74 1354 RM-PhM PSSECX software upgrade alarm acknowledge

window
18 Communication will be temporarily lost to each of the NEs while they are reset. As
communication is restored, the activation progress appears in the software upgrade
window. Wait for the activation to complete and verify the status field shows Completed
- Success for each of the NEs.
19 In Card Inventory check that EC and LC display software version as 1830PSSECX-7.0-2.
20 Check for unexpected alarms and conditions on the NEs and make sure traffic is still
unaffected.
software.

these conditions.

suspended until users complete the Normal firmware upgrade (cold reboot) on the
be restarted.

21 Make sure all the NEs that have been upgraded are highlighted and click the phase 4 icon
to commit the software. A warning window, shown in Figure 3-75, 1354 RM-PhM
PSSECX software commit warning", appears.
Figure 3-75 1354 RM-PhM PSSECX software commit warning
22 Click Yes. Once the commit is complete verify the status field shows Completed -
23 Repeat Step 2 through Step 22 for each NE or group of NEs that will be upgraded.
committed on all the NEs in the network, please refer to the GMPLS/GMRE guide to
update the active network version (GMPLS/GMRE Guide Procedure 8-1)
25 The software upgrade is complete. A backup should be performed on all upgraded NEs
referring to the procedure 1354 RM-PhM procedure for database backup.
software upgrade.
END OF STEPS

PhM procedure for 1830PSSECX-7.0-2 software rollback to previous release
Pre-requisite:
Purpose
The following procedure allows the user to remotely roll back the Alcatel-Lucent 1830
PSS-16/PSS-32 Network Element software to the previous software release. This
not been committed.
1354 RM-PhM procedure for software rollback to previous release
1 The software upgrade window should be open. See Figure 3-76, 1354 RM-PhM
software upgrade window.

2 Verify Release 7.0.2 has not been committed on the NE(s) to be backed out.
3 Select the NE(s) to be backed out and select Action > Back out from the software
upgrade menu. See Figure 3-77, 1354 RM-PhM software backout menu.
Figure 3-77 1354 RM-PhM software backout menu
4 A warning message appears as shown in Figure 3-78, 1354 RM-PhM software backout
warning".
Figure 3-78 1354 RM-PhM software backout warning
5 Click Yes. Communication is temporarily lost to each of the NEs while they are reset.
As communication is restored, the backout progress appears in the software upgrade
window. Wait for the backout to complete and verify the status field shows Completed -

Important! During backout, ensure that data communications with the remote
database backup server is maintained at all times. Backout may fail if a network
element cannot communicate with the server. Avoid backing out more than one NE
backing out more than one neighbor NE simultaneously.
6 Ensure the backout operation status field shows completed, then click the phase 4 icon to
commit the software. A warning window as shown in Figure 3-79, 1354 RM-PhM
software commit warning, is displayed.
Click Yes.
When the commit is complete verify the status field as Completed-Success.
7 Verify the active and committed release software is restored to the original release
version before the upgrade.
8 The software roll back is now complete.

END OF STEPS

Software Installation and Upgrade Example configuration of ftp server
Example configuration of ftp server

Background
There are many different ftp server software applications available. This procedure
provides detailed configuration instructions using one of the most common platforms,
FileZilla. However, the steps can be used as a reference for configuring other ftp server
applications. Consult the documentation for your specific FTP server software for
detailed instructions.
Purpose
This procedure provides more detail to the steps listed in FTP server preparation.
Prerequisites
The ftp server application must be downloaded and installed on the PC. The FileZilla
server software can be downloaded from http://filezilla-
project.org/download.php?type=server.
FTP server configuration using FileZilla
1 Start the FileZilla server software. The Connect to Server window, shown in Figure 3-80,
FileZilla connect to server window", appears.
Figure 3-80 FileZilla connect to server window
2 Leave the default settings and click OK. The server window, shown in Figure 3-81,
FileZilla server window", appears.

Figure 3-81 FileZilla server window
3 Switch the server to off-line mode and back to on-line mode and check that the socket on
port 21 is listening.
Figure 3-82 FileZilla server Active menu
If another ftp server is running, the socket on port 21 will fail to listen.

Figure 3-83 FileZilla server Active screen
Note: If you have installed the 1354 RM-PhM server locally on your PC, Apache
FTP server may be running. Stop the related service and proceed to the next step.
Figure 3-84 Apache ftp server
4 Select Edit > Groups from the top menu as shown in Figure 3-85, FileZilla groups
menu".

Figure 3-85 FileZilla groups menu
5 The Groups window, shown in Figure 3-86, FileZilla groups window, appears.
Figure 3-86 FileZilla groups window

6 With the General page highlighted in the left bar, click on the Add button on the
right. The Add user group window, shown in Figure 3-87, FileZilla add group
window, appears.
Figure 3-87 FileZilla add group window
7 Enter a group name in the dialogue box and click the OK button.
8 Select the Shared folders page in the left bar and the Groups window changes as shown
in Figure 3-88, FileZilla groups shared folders window".

Figure 3-88 FileZilla groups shared folders window
9 Click the Add button and a browse window, shown in Figure 3-89, "FileZilla browse
folder window", appears.
Figure 3-89 FileZilla browse folder window
10 Browse to the folder where the Alcatel-Lucent 1830 PSS-16/PSS-32 software is or will
be copied to, and select it. Then click OK.
Note: You may wish to create a new folder for the software before performing this
step.
11 The folder appears in the directories window. With the newly added folder selected,
make sure the Read and Write checkboxes are checked.
12 Click the Set as home dir button.
13 Click the OK button to close the window.
14 Select Edit > Users from the top menu as shown in Figure 3-90, FileZilla users menu.
Figure 3-90 FileZilla users menu
15 The Users window, shown in Figure 3-91, FileZilla users window, appears.

Figure 3-91 FileZilla users window
16 With the General page highlighted, click on the Add button on the right. The Add
user account window, shown in Figure 3-92, FileZilla add user window, appears.
Figure 3-92 FileZilla add user window
17 Type a user account name in the top dialogue box.
Note: The account name is the user id used in Software upgrade general
instruction and "New software installation general instruction".
18 Select the group created in Step 7 from the drop down list and click OK.

19 Check the Password checkbox and type a password in the dialogue box.
Note: This is the password used in Software upgrade general instruction"

and "New software installation general instruction".
20 Select the group created in Step 7 from the Group Membership: drop-down list.
21 Select the Shared folders page in the left bar and the Users window changes as shown
in Figure 3-93, FileZilla users shared folders window.
Figure 3-93 FileZilla users shared folders window
22 Click the Add button and a browse window, shown in Figure 3-94, FileZilla browse
folder window", appears.

Figure 3-94 FileZilla browse folder window
23 Browse to the folder where the Alcatel-Lucent 1830 PSS-16/PSS-32 software is or will
be copied to, and select it. Then click OK.
24 The folder appears in the directories window. With the newly added folder selected,
make sure the Read and Write checkboxes are checked.
25 Click the Set as home dir button.
26 Click the OK button to close the window.

END OF STEPS

Software Installation and Upgrade Firmware for Release 7.0.2
Firmware for Release 7.0.2

Overview
Various circuit packs in the Alcatel-Lucent 1830 PSS system provide flexible
implementation via Field Programmable devices (FPGAs). On some of those circuit
packs, the traffic is carried through programmable devices that may need upgrading to
add additional features or functions. This section of the document defines a list of FPGAs
that would have an updated image along with new software release. The execution of
FPGA upgrades is up to the discretion of the operator and can be done separately for each
individual circuit pack in a time window after upgrading the NE software. For complete
information on the specific upgrade procedure please refer Firmware management
procedures.
The firmware changes introduced in 1830 PSS Release 7.0.2 are described in the
following section for reference.

Table 7 Firmware changes from default to non-default versions in Release 7.0.2

Service
Default FW Non-Default Impact
Pack FW change version in FW version (service
FW change description
Mnemonic Classification* Release in Release disruption
7.0.2 7.0.2 in
minutes**)
Recommended
This FW allows 11STAR1 to alarm and
for 1830 PSS-16
11STAR1 1.1.1 1.2.1 protect against clock failures in 1830 <8
Optional for
PSS-16 shelf.
1830 PSS-32
Recommended
This FW allows 11QPA4/11QPA4A to
11QPA4 for 1830 PSS-16
1.7.1 1.8.1 alarm and protect against clock failures in <11
11QPA4A Optional for
1830 PSS-16 shelf.
1830 PSS-32
Recommended
This FW allows 11STGE12 to alarm and
for 1830 PSS-16
11STGE12 3.2.1 3.3.1 protect against clock failures in 1830 <8
Optional for
PSS-16 shelf.
1830 PSS-32
Recommended
This FW allows 11STMM10 to alarm and
for 1830 PSS-16
11STMM10 2.1.1 2.2.1 protect against clock failures in 1830 <10
Optional for
PSS-16 shelf.
1830 PSS-32
Recommended
This FW allows 11DPE12 to alarm and
for 1830 PSS-16
11DPE12 3.2.1 3.3.1 protect against clock failures in 1830 <8
Optional for
PSS-16 shelf.
1830 PSS-32
This FW allows 11DPE12E to alarm and
11DPE12E Recommended 1.6.1 1.7.1 protect against clock failures in 1830 <5
PSS-16 and PSS-32 shelves.
This FW allows 11DPE12A to alarm and

11DPE12A Recommended 1.4.1 1.5.1 protect against clock failures in 1830 <6
PSS-16 and PSS-32 shelves.
This FW enables the support of HO-
130SCX10 Optional 2.3.1 2.2.1 <18
ODU4 latency measurements.
This FW enables the support of HO-
130SNX10 Optional 1.4.1 1.3.1 <18
ODU4 latency measurements.
Recommended None: in-
This FW allows AHPHG to alarm and
for 1830 PSS-16 service FW
AHPHG 1.1.1 1.2.1 protect against clock failures in 1830
Optional for upgrade
PSS-16 shelf.
1830 PSS-32 supported
This FW allows AHPLG to alarm and
AHPLG 2.0.1 2.1.1 protect against clock failures in 1830
PSS-16 shelf.

Service
Default FW Non-Default Impact
Pack FW change version in FW version (service
Mnemonic Classification* Release in Release disruption
7.0.2 7.0.2 in
minutes**)
This FW allows A2325A to alarm and
A2325A 1.1.1 1.2.1 protect against clock failures in 1830
PSS-16 shelf.
This FW allows AM2125A to alarm and
AM2125A 1.2.1 1.3.1 protect against clock failures in 1830
PSS-16 shelf.
This FW allows AM2125B to alarm and
AM2125B 1.2.1 1.3.1 protect against clock failures in 1830
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
Note:
Required FW change indicates that FW image upgrade along with new SW load is necessary to ensure
long-term error-free operation of a specified pack.
Recommended FW change indicates that FW change is desired to avoid issues that could hinder product
operation associated with the anomaly described in FW change description column. If the
user prefers to retain previous FW version without a standing condition
FWUPGRADEPENDING, it may be done according to the Firmware management
procedures.
Optional FW change indicates that FW image upgrade may be done if introduced functionality is of
interest to a specific configuration or application. If the user prefers to retain previous FW
version without a standing condition FWUPGRADEPENDING, it may be done according to
the Firmware management procedures.
** Service impact indicates disruption on services carried by pack which is performing firmware
upgrade. Values given in the table show maximum measured service disruption times when
pack firmware upgrades are performed one at a time.

Table 8 Firmware changes from Release 7.0.1 to Release 7.0.2

Service
Default FW Default FW Impact
Pack FW change version in version in (service
Mnemonic Classification* Release Release disruption
7.0.1 7.0.2 in
minutes**)
Recommended 1.2.1
for 1830 PSS-16 (Non-
11STAR1 1.1.1 protect against clock failures in 1830 <8
Optional for Default
PSS-16 shelf.
1830 PSS-32 Version)
Recommended 1.8.1
11QPA4 for 1830 PSS-16 (Non-
1.7.1 alarm and protect against clock failures <11
11QPA4A Optional for Default
in 1830 PSS-16 shelf.
Recommended 3.3.1
This FW allows 11STGE12 to alarm
11STGE12 3.2.1 and protect against clock failures in <8
1830 PSS-16 shelf.
Recommended 2.2.1
This FW allows 11STMM10 to alarm
11STMM10 2.1.1 and protect against clock failures in <10
1830 PSS-16 shelf
Recommended 3.3.1
11DPE12 3.2.1 protect against clock failures in 1830 <8
PSS-16 shelf.
1.7.1
This FW allows 11DPE12E to alarm
(Non-
11DPE12E Recommended 1.6.1 and protect against clock failures in <5
Default
1830 PSS-16 and PSS-32 shelves.
Version)
1.5.1
This FW allows 11DPE12A to alarm
(Non-
11DPE12A Recommended 1.4.1 and protect against clock failures in <6
Default
Version)
This FW resolves the issue that may
FW upgrades clog GNE when several network
11QPE24 automatically 1.1.1 1.2.1 management servers (1350 OMS and <13
with SW upgrade 1354 RM-PhM etc) manage RNE
(through GNE) at the same time.
clog GNE when several network
11DPM12 Recommended 1.8.1 1.9.1 management servers (1350 OMS and <5
1354 RM-PhM etc) manage RNE
11OPE8 automatically 1.2.1 1.3.1 management servers (1350 OMS and <9
with SW upgrade 1354 RM-PhM etc) manage RNE

Service
7.0.1 7.0.2 in
minutes**)
This FW update is needed for
112SDX11 Required 1.2.1 1.3.1 NA
compatibility with the line card software
2.2.1
(Non- This FW enables the support of HO-
130SCX10 Optional 2.3.1 <18
Default ODU4 latency measurements.
Version)
1.3.1
(Non- This FW enables the support of HO-
130SNX10 Optional 1.4.1 <18
Default ODU4 latency measurements.
Version)
Recommended 1.2.1 None: in-
for 1830 PSS-16 (Non- service FW
AHPHG 1.1.1 protect against clock failures in 1830
Optional for Default upgrade
PSS-16 shelf.
1830 PSS-32 Version) supported
AHPLG 2.0.1 protect against clock failures in 1830
PSS-16 shelf.
A2325A 1.1.1 protect against clock failures in 1830
PSS-16 shelf.
AM2125A 1.2.1 protect against clock failures in 1830
PSS-16 shelf.
AM2125B 1.2.1 protect against clock failures in 1830
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
Note:

procedures.
Release 7.0.2 or a later release must be used for initial deployments of the 112SDX11 pack.


Service
7.0.0 7.0.2 in
minutes**)
Recommended 1.2.1
PSS-16 shelf.
Recommended 1.8.1
11QPA4 for 1830 PSS-16 (Non-
1.7.1 alarm and protect against clock failures <11
11QPA4A Optional for Default
in 1830 PSS-16 shelf.
Recommended 3.3.1
1830 PSS-16 shelf.
Recommended 2.2.1
1830 PSS-16 shelf
Recommended 3.3.1
PSS-16 shelf.
1.7.1
(Non-
Default
Version)
1.5.1
This FW allows 11DPE12A to alarm
(Non-
11DPE12A Recommended 1.4.1 and protect against clock failures in <6
Default
Version)
with SW upgrade 1354 RM-PhM etc) manage RN E
clog GNE when several network
11DPM12 Recommended 1.8.1 1.9.1 management servers (1350 OMS and <5
1354 RM-PhM etc) manage RNE
This FW aligns the FW profiles with
130SCA1 Optional 2.1.1 2.2.1 <17
100G SD-FEC coherent packs.

Service
7.0.0 7.0.2 in
minutes**)
None: in-
This FW enables the interworking service FW
Recommended 2.1.1 2.3.1
between 112SNX10 and 130SCX10 upgrade
supported
130SCX10
2.2.1 This FW enables the interworking
(Non- between 112SNX10 and 130SCX10.
Recommended 2.1.1 <21
Default This FW enables the support of HO-
Version) ODU4 latency measurements.
None: in-
This FW enables the interworking service FW
between 112SNX10 and 130SNX10. upgrade
supported
130SNX10
1.3.1 This FW enables the interworking
(Non- between 112SNX10 and 130SNX10.
Default The FW enables the support of HO-
Version) ODU4 latency measurements.
This FW enables the interworking
between 112SNA1/112SNX10 and
None: in-
260SCX2 and increases the tolerance of
service FW
260SCX2 Recommended 1.1.1 1.2.1 260SCX2 protection switching in the
upgrade
presence of high PMD. This FW
supported
supports the HO-ODU4 latency
measurements.
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.

Service
7.0.0 7.0.2 in
minutes**)
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
Note:
procedures.


Service
6.2.0 7.0.2 in
minutes**)
Recommended 1.2.1
PSS-16 shelf.
This FW supports on-demand latency
measurement on11QPA4/11QPA4A and
Optional 1.6.1 1.7.1 supports short packets (non standard <11
compliant size packets) for interworking
over GCC.
11QPA4
measurement on 11QPA4/11QPA4A
11QPA4A
Recommended 1.8.1 and supports short packets (non standard
for 1830 PSS-16 (Non- compliant size packets) for interworking
1.6.1 <11
Optional for Default over GCC. This FW allows
1830 PSS-32 Version) 11QPA4/11QPA4A to alarm and protect
against clock failures in 1830 PSS-16
shelf.
measurement on 11QPEN4 and supports
short packets (non standard compliant
size packets) for interworking over
11QPEN4 Optional 1.2.1 1.3.1 <15
GCC. New FW resolves the issue of
RNE synchronization with PhM when
the packet size of the synchronization
message is within 1018~1022.
This FW supports Proactive SLM, LM,
DM, and BITS support and supports
Optional 1.3.1 1.4.1 size packets) for interworking over <10
GCC. New FW improves 1588v2 PTP
accuracy to +/-30ns for the two directly
connected BC nodes.
11DPE12A DM, and BITS support and supports
1.5.1 size packets) for interworking over
(Non- GCC. New FW improves 1588v2 PTP
Default accuracy to +/-30ns for the two directly
Version) connected BC nodes. This FW allows
11DPE12A to alarm and protect against
clock failures in 1830 PSS-16 and PSS-
32 shelves.

Service
6.2.0 7.0.2 in
minutes**)
This FW resolves false Looduk LOF
LOM alarm when client ports are
disconnected for Bitsync OC-48/STM-
16 with ESNCP configuration. This FW
11DPM12 Recommended 1.7.1 1.9.1 resolves the issue that may clog GNE <5
when several network management
servers (1350 OMS and 1354 RM-PhM
etc) manage RNE (through GNE) at the
same time.
Recommended 3.3.1
1830 PSS-16 shelf.
Recommended 2.2.1
1830 PSS-16 shelf
Recommended 3.3.1
PSS-16 shelf.
1.7.1
(Non-
Default
Version)
with SW upgrade 1354 RM-PhM etc) manage RN E
This FW addresses problems
experienced on some 40G packs
43SCA1
including: Reduced transmission
(SONET/ Required 1.1.1 2.1.1 <14
[OSNR sensitivity] performance over
SDH)
time, Card degrade or OT minor alarms
and missing PMs (OCC lockup).
43SCA1 including: Reduced transmission
Required 1.1.1 2.1.1 <14
(OTU3) [OSNR sensitivity] performance over

Service
6.2.0 7.0.2 in
minutes**)
43SCX4 Required 1.4.1 2.2.1 <23
Reseating XFPs on 43SCX4E will no
longer raise a false port failure alarm.
43SCX4E Required 1.1.1 2.2.1 <23
Reseating XFPs on 43SCX4E will no
longer raise a false port failure alarm.
This FW resolves scenario resulting in
occasional Line-Side UCBs. New FW
130SCA1 Recommended 1.1.1 2.2.1 <17
aligns the FW profiles with 100G SD-
FEC coherent packs
This FW resolves scenario resulting in None: in-
occasional Line-Side UCBs. New FW service FW
enables the interworking between upgrade
112SNX10 and 130SCX10 supported
130SCX10 This FW resolves scenario resulting in
2.2.1 occasional Line-Side UCBs. New FW
(Non- enables the interworking between
Default 112SNX10 and 130SCX10. The FW
Version) enables the support of HO-ODU4
latency measurements.
112SNX10 and 130SNX10 supported
130SNX10 This FW resolves scenario resulting in
Default 112SNX10 and 130SNX10. The FW
Version) enables the support of HO-ODU4
latency measurements.
PSS-16 shelf.

Service
6.2.0 7.0.2 in
minutes**)
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
PSS-16 shelf.
This FW improves PTP timestamping

PTPCTL Optional 1.1.1 1.2.1 <5
processing and resolution.
Note:
procedures.
Required to support on-demand latency measurement on 11QPA4/11QPA4A.
Required to support on-demand latency measurement on 11QPEN4.
Required to support Proactive SLM, LM, DM, and BITS.

Table 11 Firmware changes from Release 6.0.6 and 6.0.7 to Release 7.0.2
Default Service
Default
FW Impact
Pack FW change FW version
version in FW change description (service
Mnemonic Classification* in Release
Release disruption in
7.0.2
6.0.6/6.0.7 minutes**)
Recommended 1.2.1
11STAR1 1.1.1 protect against clock failures in 1830 PSS- <8
Optional for 1830 Default
16 shelf.
PSS-32 Version)
measurement on 11QPA4/11QPA4A and
over GCC.
11QPA4
11QPA4A
Recommended 1.8.1 supports short packets (non standard
for 1830 PSS-16 (Non- compliant size packets) for interworking
1.6.1 <11
Optional for Default over GCC. This FW allows
1830 PSS-32 Version) 11QPA4/11QPA4A to alarm and protect
against clock failures in 1830 PSS-16
shelf.
short packets (non standard compliant size
packets) for interworking over GCC. New
11QPEN4 Optional 1.2.1 1.3.1 <15
FW resolves the issue of RNE
synchronization with PhM when the packet
size of the synchronization message is
within 1018~1022.
New FW supports Proactive SLM, LM,
DM, and BITS support and supports short
packets (non standard compliant size
Optional 1.3.1 1.4.1 packets) for interworking over GCC. New <10
FW improves 1588v2 PTP accuracy to +/-
30ns for the two directly connected BC
nodes.
11DPE12A
DM, and BITS support and supports short
1.5.1
(Non-
Recommended 1.3.1 FW improves 1588v2 PTP accuracy to +/- <10
Default
30ns for the two directly connected BC
Version)
nodes. This FW allows 11DPE12A to
alarm and protect against clock failures in

Default Service
Default
FW Impact
7.0.2
6.0.6/6.0.7 minutes**)
This FW resolves false Looduk LOF LOM
alarm when client ports are disconnected
for Bitsync OC-48/STM-16 with ESNCP
configuration.
11DPM12 Recommended 1.7.1 1.9.1 This FW resolves the issue that may clog <5
GNE when several network management
servers (1350 OMS and 1354 RM-PhM
etc) manage RNE (through GNE) at the
same time.
Recommended 3.3.1
11STGE12 3.2.1 protect against clock failures in 1830 PSS- <8
16 shelf.
PSS-32 Version)
Recommended 2.2.1
11STMM10 2.1.1 protect against clock failures in 1830 PSS- <10
16 shelf.
PSS-32 Version)
Recommended 3.3.1
11DPE12 3.2.1 protect against clock failures in 1830 PSS- <8
16 shelf.
PSS-32 Version)
1.7.1
(Non-
11DPE12E Recommended 1.6.1 protect against clock failures in 1830 PSS- <5
Default
16 and PSS-32 shelves.
Version)
This FW resolves the issue that may clog
FW upgrades GNE when several network management
11QPE24 automatically 1.1.1 1.2.1 servers (1350 OMS and 1354 RM-PhM <20
with SW upgrade etc) manage RNE (through GNE) at the
same time.
This FW addresses problems experienced
on some 40G packs including: Reduced
43SCA1
transmission [OSNR sensitivity]
performance over time, Card degrade or
SDH)
OT minor alarms and missing PMs (OCC
lockup).


43SCA1 transmission [OSNR sensitivity]
Required 1.1.1 2.1.1 <14
(OTU3) performance over time, Card degrade or
lockup).
Default Service
Default
FW Impact
7.0.2
6.0.6/6.0.7 minutes**)

43SCX4 Required 1.4.1 2.2.1 performance over time, Card degrade or <23
lockup). Reseating XFPs on 43SCX4 will
no longer raise a false port failure alarm.
43SCX4E Required 1.1.1 2.2.1 performance over time, Card degrade or <23
lockup). Reseating XFPs on 43SCX4E will
occasional Line-Side UCBs. New FW
130SCA1 Recommended 1.1.1 2.2.1 <17
aligns the FW profiles with 100G SD-FEC
coherent packs
112SNX10 and 130SCX10 supported
130SCX10
Default 112SNX10 and 130SCX10. The FW
Version) enables the support of HO-ODU4 latency
measurements.
AHPHG 1.1.1 protect against clock failures in 1830 PSS-
Optional for 1830 Default upgrade
16 shelf.
PSS-32 Version) supported
AHPLG 2.0.1 protect against clock failures in 1830 PSS-
16 shelf.
A2325A 1.1.1 protect against clock failures in 1830 PSS-
16 shelf.

AM2125A 1.2.1 protect against clock failures in 1830 PSS-
16 shelf.
Default Service
Default
FW Impact
7.0.2
6.0.6/6.0.7 minutes**)
AM2125B 1.2.1 protect against clock failures in 1830 PSS-
16 shelf.
16 shelf.
This FW improves PTP timestamping
PTPCTL Optional 1.1.1 1.2.1 <5
processing and resolution.
Note:
procedures.
Required to support on-demand latency measurement on 11QPEN4.
Required to support Proactive SLM, LM, DM, and BITS.


Service
5.1.6 7.0.2 in
minutes**)
This FW resolves the issue of RNE
11STAR1A Recommended 1.1.1 1.2.1 <12
within 1018~1022.
Recommended for 1.2.1
1830 PSS-16 (Non-
16 shelf.
PSS-32 Version)
within 1018~1022. New FW supports on-
Recommended 1.5.1 1.7.1 <11
demand latency measurement
on11QPA4/11QPA4A and supports short
packets) for interworking over GCC.
11QPA4
11QPA4A
within 1018~1022. New FW supports on-
1.8.1
demand latency measurement on
(Non-
Recommended 1.5.1 11QPA4/11QPA4A and supports short <11
Default
Version)
packets) for interworking over GCC. This
FW allows 11QPA4/11QPA4A to alarm
and protect against clock failures in 1830
PSS-16 shelf.
This FW resolves the possibility of service
impact during encryption key switching
( #mh11880).
New FW supports on-demand latency
11QPEN4 Recommended 1.1.1 1.3.1 short packets (non standard compliant size <15
FW resolves the issue of RNE
within 1018~1022.

Service
5.1.6 7.0.2 in
minutes**)
Recommended 1.5.1 1.6.1 <5
within 1018~1022.
11DPE12E
1.7.1
(Non-
Recommended 1.5.1 within 1018~1022. This FW allows <5
Default
11DPE12E to alarm and protect against
Version)
clock failures in 1830 PSS-16 and PSS-32
shelves.
This FW supports the interworking between
11DPE12 and 11DPE12A. New FW
supports Proactive SLM, LM, DM, and
BITS support and supports short packets
Optional 1.2.1 1.4.1 <10
(non standard compliant size packets) for
interworking over GCC. New FW improves
1588v2 PTP accuracy to +/-30ns for the
two directly connected BC nodes.
This FW supports the interworking between
11DPE12A 11DPE12 and 11DPE12A. New FW
supports Proactive SLM, LM, DM, and
BITS support and supports short packets
1.5.1
(non standard compliant size packets) for
(Non-
Recommended 1.2.1 interworking over GCC. New FW improves <10
Default
1588v2 PTP accuracy to +/-30ns for the
Version)
two directly connected BC nodes. This FW
allows 11DPE12A to alarm and protect
against clock failures in 1830 PSS-16 and
PSS-32 shelves.
This FW resolves false Looduk LOF LOM
alarm when client ports are disconnected
for Bitsync OC-48/STM-16 with ESNCP
configuration. This FW resolves the issue
11DPM12 Recommended 1.7.1 1.9.1 <5
that may clog GNE when several network
management servers (1350 OMS and 1354
RM-PhM etc) manage RNE (through GNE)
at the same time
1830 PSS-16 (Non-
16 shelf.
PSS-32 Version)
1830 PSS-16 (Non-
16 shelf.
PSS-32 Version)

Service
5.1.6 7.0.2 in
minutes**)
1830 PSS-16 (Non-
16 shelf.
PSS-32 Version)
This FW resolves the issue that may clog
FW upgrades GNE when several network management
11QPE24 automatically with 1.1.1 1.2.1 servers (1350 OMS and 1354 RM-PhM etc) <20
SW upgrade manage RNE (through GNE) at the same
time.
This FW ensures GbE client support when
4DPA4 is provisioned with the maximum
bandwidth for the configurations below
(1) FC100+GbE+GbE+GbE
4DPA4
Optional 2.6.1 2.7.1 (2) FC100+FC100+GbE+GbE or <4
(FlexMux)
FC100+GbE+FC100+GbE
(3) FC200+FE+GbE+GbE
This FW version is required in order to
support the configurations specified above.
43SCA1
performance over time, Card degrade or OT
SDH)
minor alarms and missing PMs (OCC
lockup).
43SCX4 Required 1.4.1 2.2.1 performance over time, Card degrade or OT <23
lockup). Reseating XFPs on 43SCX4 will
43SCX4E Required 1.1.1 2.2.1 performance over time, Card degrade or OT <23
lockup). Reseating XFPs on 43SCX4E will
This FW introduces RMON support for 100
GbE client interface and further improves
line transmission performance. New FW
reduces the protection switch times as well
112SCA1
Required 2.2.1 4.1.1 as address problems experienced on some <17
(100GbE)
3-slot 100G packs including: Reduced
performance over time, Card degrade
alarms and missing PMs (OCC lockup).

Service
5.1.6 7.0.2 in
minutes**)
New FW introduces RMON support for 100
GbE client interface and further improves
line transmission performance. New FW
reduces the protection switch times as well
112SNA1
Required 1.2.1 3.1.1 as address problems experienced on some <17
(100GbE)
3-slot 100G packs including: Reduced
performance over time, Card degrade
alarms and missing PMs (OCC lockup).
This FW reduces the protection switch
times as well as address problems
experienced on some 3-slot 100G packs
including: Reduced transmission [OSNR
112SCX10 Required 2.2.1 4.1.1 <14
sensitivity] performance over time, Card
degrade alarms and missing PM (OCC
lockup). New FW improves line
transmission performance.
This FW reduces the protection switch
times as well as address problems
experienced on some 3-slot 100G packs
including: Reduced transmission [OSNR
112SNX10 Required 1.2.1 3.1.1 <14
sensitivity] performance over time, Card
degrade alarms and missing PM (OCC
lockup). New FW improves line
transmission performance.
Recommended for 1.2.1 None: in-
1830 PSS-16 (Non- service FW
16 shelf.
16 shelf.
16 shelf.
16 shelf.

Service
5.1.6 7.0.2 in
minutes**)
16 shelf.

16 shelf.
Note:
procedures.
Required to support interworking between 11DPE12 and 11DPE12A.


Service
3.6.60 7.0.2 in
minutes**)
Recommended 1.2.1
16 shelf.
over GCC.
11QPA4 This FW supports on-demand latency
11QPA4A measurement on 11QPA4/11QPA4A and
Recommended 1.8.1
supports short packets (non standard
1.6.1 compliant size packets) for interworking <11
over GCC. This FW allows
11QPA4/11QPA4A to alarm and protect
against clock failures in 1830 PSS-16 shelf.
This FW supports standard SNC-P ODUk
protection implementation
for interworking with 24xAny I/O card and
supports the option of
setting line port FEC type to No FEC. New
FW resolves false Looduk LOF LOM alarm
11DPM12 Recommended 1.6.1 1.9.1 when client ports are disconnected for <5
Bitsync OC-48/STM-16 with ESNCP
configuration. This FW resolves the issue
that may clog GNE when several network
management servers (1350 OMS and 1354
RM-PhM etc) manage RNE (through GNE)
at the same time.
Recommended 3.3.1
16 shelf.
Recommended 2.2.1
16 shelf.
Recommended 3.3.1
16 shelf.
1.7.1
(Non-
11DPE12E Recommended 1.6.1 protect against clock failures in 1830 PSS- <5
Default
16 and PSS-32 shelves.
Version)
Service
3.6.60 7.0.2 in
minutes**)
This FW ensures GbE client support when
4DPA4 is provisioned with the maximum
bandwidth for the configurations below
(1) FC100+GbE+GbE+GbE
4DPA4
Optional 2.6.1 2.7.1 (2) FC100+FC100+GbE+GbE or <4
(FlexMux)
FC100+GbE+FC100+GbE
(3) FC200+FE+GbE+GbE
This FW version is required in order to
support the configurations specified above.
43STA1P This FW resolves the false switching in 1+1
Optional 1.3.1 1.4.1 <12
43STA1PB Y-cable protection.
This FW allows reseating XFPs on 43SCX4
43SCX4 Recommended 2.1.1 2.2.1 <15
without raising a false port failure alarm.
16 shelf.
16 shelf.
16 shelf.
16 shelf.
16 shelf.
16 shelf.
Note:

procedures.
Required for 1+1 Y-cable protection configuration.

Software Installation and Upgrade Firmware management procedures
Firmware management procedures

Purpose
After the software upgrade, some circuit packs may have FWUPGRADEPENDING
and FWVERSIONNOTDEFAULT conditions. Refer to Firmware for Release 7.0.2 for
detailed information about the features provided by the firmware upgrade if the upgrade
is required, and if an in-service (hitless, non-service affecting) upgrade is possible.
Choose the appropriate procedure below to either maintain the current firmware or
upgrade the firmware on each card with the conditions noted above.
The preceeding firmware change tables refer to default and non-default firmware
versions. Cards are provisioned by default to use the default firmware for the software
release. This default setting works and is recommended for most cards. However, some
features are only available in non-default firmware versions. To upgrade card firmware to
a non-default version, provision the firmware release to the desired version and upgrade
the firmware using one of the normal or in-service (hitless, non-service affecting)
upgrade procedures. The section Firmware-related operations for reference is the
procedure to select a specific or default firmare version.
The following cards automatically upgrade their firmware during a software upgrade or a
card warm reset: 11QPE24, 11OPE8, and 11QCE12X. These cards must remain
provisioned to use the default firmware.
Firmware issues if upgrading from Release 3.6.58 to Release 7.0.2 via Release 5.1.6 may
be referenced as needed.
Steps
1 To maintain current firmware until upgrade via subsequent cold reboot, no action is
necessary and this procedure is complete.
2 To maintain and lock in current firmware during subsequent cold reboots, proceed
to Maintain current firmware.

Software Installation and Upgrade Firmware management procedures
3 To upgrade firmware on cards where an in-service firmware upgrade is not available,

proceed to Normal firmware upgrade (cold reboot).
Important! Upgrading firmware with this procedure is service affecting and should
be completed at low traffic periods as determined by the customer, typically a
predetermined maintenance window. Refer to Firmware for Release 7.0.2 for details
on the service interruption duration.
Important! Do not remove or touch circuit packs while the firmware upgrade is in
progress.
4 To upgrade firmware on OT cards (130SCX10, 130SNX10, and 260SCX2) that support

in-service (hitless) upgrade, continue with In-service (hitless) firmware upgrade for OT
cards.
progress.
5 To upgrade firmware on LD cards (AHPHG, AHPLG, A2325A, AM2125A, AM2125B,

AM2318A, AM2032A, and AM2625A) that support in-service (hitless) upgrade,
continue with In-service (hitless) firmware upgrade for LD cards.
Important! If the upstream NE has an RA2P and bi-directional LD, the in-service
firmware upgrade of the LD will impact transmission. Refer to Issue #PSSKPL-140 for
details.
progress.
END OF STEPS

Software Installation and Upgrade Maintain current firmware
Maintain current firmware

Purpose
This procedure establishes a specific firmware release (the currently active release) for a
card rather than the default version for the latest software release. This procedure is not
service affecting. After this procedure, the specific firmware version will be maintained
during subsequent cold reboots.
Steps
1 Display and record the currently active firmware release

CLI show firmware card <shelf/slot> detail
WebUI Expand the equipment tree, select a card, select the Firmware tab.
PhM In the NE inventory window, click on the Administration menu and select Card Firmware.
The Card Firmware window can remain open for this procedure.
Record the "Active Release" of the card for use in the next step.
2 Provision the firmware release to the currently active firmware release

Use the active release from the previous step for this operation
CLI config firmware card <shelf/slot> <active-release>
(example, if active release is profile_1.5.1: config firmware card 1/13 1.5.1)
WebUI In the card Firmware tab, click on the Provisioned Release drop-down menu, select the active
release (for example, profile_1.5.1), and press the Submit button.
PhM In the Card Firmware window, double-click on a card. Select the desired profile (for example,
1.5.1) in the Provisioned Release pull-down menu and press the OK button.

Software Installation and Upgrade Maintain current firmware
3 Optional step: Perform a warm reset on the card to clear the FWUPGRADEPENDING
condition (if raised).
Result: Triggers a warm reset to the card that is not service affecting.
CLI config card <shelf/slot> reset warm yes
WebUI In the card Reboot tab, select Warm Reboot and click submit.
PhM In the NE inventory window, select a card, click on the Administration menu and select Card
Reset Operation (Warm Reset).
After the warm reset completes, the FWUPGRADEPENDING condition clears (if it
was previously raised). The FWVERSIONNOTDEFAULT condition will be raised if
the active/installed version is not the default version for the SW release.
END OF STEPS

Software Installation and Upgrade Normal firmware upgrade (cold reboot)
Normal firmware upgrade (cold reboot)

Purpose
This is the normal procedure to upgrade firmware on a card. It is used in cases where an in-
service (hitless) firmware upgrade is not available.
Important! Upgrading firmware with this procedure is service affecting and should be
completed at low traffic periods as determined by the customer, typically a predetermined
maintenance window. Refer to Firmware for Release 7.0.2 for details on the service
interruption duration.
progress.
Steps
1 Display the provisioned firmware release.

2 Provision the firmware release (if necessary) to the desired profile, either a specific
profile or default.
CLI config firmware card <shelf/slot> <profile>
(example for specific version: config firmware card 1/4 1.3.1)
(example for default: config firmware card 1/4 default)
WebUI In the card Firmware tab, click on the Provisioned Release drop-down menu, select the desired
profile (for example, profile_1.3.1 or --default--), and press the Submit button.
1.3.1 or --default--) in the Provisioned Release pull-down menu and press the OK button.

Software Installation and Upgrade Normal firmware upgrade (cold reboot)
3 Cold reset the card to upgrade the firmware

Result: Triggers a cold reset to the card that is service affecting.
CLI config card <shelf/slot> reset cold
WebUI In the card Reboot tab, select the Cold Reboot radio button and click submit.
PhM In the NE inventory window, select a card, click on the Administration menu and select Card
Reset Operation (Cold Reset)
Note for an in-service card: Before a cold reset can be performed, the ports and slot
must first be put in the Maintenance or Out of Service state. After the cold reset has
been initiated, the slot and ports can be put back to their prior state.
4 Wait for the duration indicated in the appropriate table in Firmware for Release 7.0.2
and verify the FWUPGRADEPENDING and FWVERSIONNOTDEFAULT
conditions on the card have cleared. The FWVERSIONNOTDEFAULT condition will
not clear if the active/installed version is not the default version for the SW release.
END OF STEPS

Software Installation and Upgrade In-service (hitless) firmware upgrade for OT cards
In-service (hitless) firmware upgrade for OT cards

Purpose
This procedure is used to upgrade firmware on OT cards (such as, 130SCX10) when:
The firmware change tables indicate that an in-service upgrade is possible and
The firmware upgrade is to the default firmware version for this software release. (This
procedure can be adapted to upgrade to a specific, non-default firmware version if an in-
service upgrade is possible.)
Steps
1 Display the provisioned firmware release and verify that it is set to default.
Verify that the "Provisioned Release" is default. If not, set it to default in the next step.
2 Provision the firmware release to default (if necessary).

Result: Sets the "Provisioned Release" to default if it was not default in the previous step.
CLI config firmware card <shelf/slot> default
WebUI In the card Firmware tab, click on the Provisioned Release drop-down menu, select --default--,
and press the Submit button.
PhM In the Card Firmware window, double-click on a card. Press the Default button then the OK
button.
3 Verify that a hitless upgrade is possible.

WebUI Select the card Firmware tab.
PhM In the Card Firmware window, double-click on a card. Note: the Firmware Profile Details are
not displayed in this SW release, but a hitless upgrade can still be performed (next step).

Software Installation and Upgrade In-service (hitless) firmware upgrade for OT cards
Look at the Firmware Profile Details which show the status of each device. If all
devices report either "active" or "hitless" status (at the end of each line) then a hitless
upgrade is possible. If any device reports "pending" then a normal firmware upgrade
(non-hitless, cold reset of the card) must be performed.
The SW needs a short amount of time (10 to 30 seconds) to determine if a hitless upgrade
is possible after provisioning the firmware profile. If the firmware profile was
provisioned in the previous step, it may be necessary to repeat this step (or press
Refresh in WebUI) to see the updated hitless status.
4 Initiate a hitless firmware upgrade.

Result: Triggers a warm reset of the card and hitless firmware upgrade.
CLI config firmware card <shelf/slot> hitless
WebUI In the card Firmware tab, click the Hitless Upgrade checkbox, and press the Submit button.
PhM In the Card Firmware window, double-click on a card. Click the Hitless Upgrade checkbox
then the OK button.
5 Wait for the upgrade to complete and verify firmware conditions have cleared.
The warm reset and hitless firmware upgrade take about 7 minutes to complete. During
device programming, the FPGAINITNSA[n] alarm is raised.
CLI show condition
WebUI Click on the Reports menu then select Condition List.
PhM In the main Topology View window, select the desired NE. Click on the Fault menu and select
Show Conditions.
After firmware upgrade and card boot complete, verify that the
FWUPGRADEPENDING and FWVERSIONNOTDEFAULT conditions on the card
have cleared.
END OF STEPS

Software Installation and Upgrade In-service (hitless) firmware upgrade for LD cards
In-service (hitless) firmware upgrade for LD cards

Purpose
This procedure is used to upgrade firmware on LD cards (such as, AHPHG) when:
The firmware change tables indicate that an in-service upgrade is possible and
The firmware upgrade is to a non-default firmware version for this software release
Important! If the upstream NE has an RA2P and bi-directional LD, the hitless firmware
upgrade of the LD will impact transmission. Refer to Issue #PSSKPL-140 for details.
Steps
1 Display the provisioned firmware release.

WebUI Expand the equipment tree, select a card, select the Firmware tab
2 Provision the firmware release to the desired profile.

(example: config firmware card 1/4 1.3.1)
WebUI In the card Firmware tab, click on the Provisioned Release drop-down menu, select the desired
profile (for example, profile_1.3.1), and press the Submit button
3 Verify that a hitless upgrade is possible.

WebUI Select the card Firmware tab
PhM In the Card Firmware window, double-click on a card. Note: the Firmware Profile Details are
not displayed in this SW release, but a hitless upgrade can still be performed (next step).

Software Installation and Upgrade In-service (hitless) firmware upgrade for LD cards
Look at the Firmware Profile Details which show the status of each device. If all
devices report either "active" or "hitless" status (at the end of each line) then a hitless
upgrade is possible. If any device reports "pending" then a normal firmware upgrade
(non-hitless, cold reset of the card) must be performed.
The SW needs a short amount of time (10 to 30 seconds) to determine if a hitless upgrade
is possible after provisioning the firmware profile. It may be necessary to repeat this step
(or press Refresh in WebUI) to see the updated hitless status.
4 Initiate a hitless firmware upgrade.

Result: Triggers a warm reset of the card and hitless firmware upgrade.
CLI config firmware card <shelf/slot> hitless
WebUI In the card Firmware tab, click the Hitless Upgrade checkbox, and press the Submit button.
PhM In the Card Firmware window, double-click on a card. Click the Hitless Upgrade checkbox
then the OK button.
5 Wait for the upgrade to complete and verify firmware conditions.

The warm reset and hitless firmware upgrade take about 4 minutes to complete. During
device programming, the FPGAINITNSA[n] alarm is raised.
CLI show condition
Show Conditions.
After firmware upgrade and card boot complete, verify that the
FWVERSIONNOTDEFAULT condition is raised for the card, but not
FWUPGRADEPENDING or FWPENDINGOBSOLETE.
FWVERSIONNOTDEFAULT is expected because the active/installed version is not
the default version for the SW release.
END OF STEPS

Software Installation and Upgrade Firmware issues if upgrading from Release 3.6.58 to Release 7.0.2 via Release 5.1.6
Firmware issues if upgrading from Release 3.6.58 to Release

7.0.2 via Release 5.1.6
Overview
Upgrades from Release 3.6.58 to Release 7.0.2 can proceed through Release 5.1.6 as the
intermediate release if the EC is equipped with 16GB flash memory modules (either EC
APN = 8DG59241AD or field upgraded EC with 16G capacity via upgrade kit APN =
8DG60968AA). Since Release 3.6.58 contains firmware profiles that are not present in
Release 5.1.6, special precautions must be taken. If such a profile is specifically
provisioned in Release 3.6.58 and the software is then upgraded to Release 5.1.6, the card
will not boot following a cold reset.
Considerations before upgrading
Before upgrading software to Release 5.1.6 from Release 3.6.58, make sure all cards are
provisioned with the default firmware profile or a specific profile that is also available in
Release 5.1.6.
Refer to Alcatel-Lucent 1830 Photonic Service Switch 32/16 (PSS-32/PSS-16) Release

5.1.6 Customer Release Notes, 8DG61793AAAA and Alcatel-Lucent 1830 Photonic
Service Switch 32/16 (PSS-32/PSS-16) Release 3.6.58 Customer Release Notes,
8DG62168AAAA to determine the available firmware versions for each pack.
It is permissible for a card to have a higher version of firmware installed that is not
available in Release 5.1.6. After the software is upgraded to Release 5.1.6, the
FWVERSIONNOTDEFAULT, FWUPGRADEPENDING, and
FWPENDINGOBSOLETE conditions are raised for the card. FWPENDINGOBSOLETE
is raised since the software cannot find the installed profile in the set of available profiles.
The higher version of firmware is retained as long as the card is not cold reset while in
Release 5.1.6. If a card cold reset occurs (planned or by accident) in Release 5.1.6, the
firmware may be downgraded, depending on what version is installed and what version is
provisioned.

Software Installation and Upgrade Firmware-related operations for reference
Firmware-related operations for reference

Firmware (FW) is upgraded or installed in a card in one of two ways:
Cold reset (user-initiated cold reset of the card or NE, or plugging in a card): while the card
is booting, the software (if necessary) programs devices on the card with the firmware
versions corresponding to the Provisioned Release for the card.
In-service (hitless) upgrade: some devices on some cards support firmware upgrade, without
affecting traffic, while the card remains in service. A user-initiated hitless firmware upgrade
triggers a warm reset of the card. While the card is booting, the software programs devices
on the card with the firmware versions corresponding to the Provisioned Release for the
card.
After the card has completely booted from one of the above resets, the Active Release will then
be the same as the Provisioned Release.
The following cards are exeptions in the manner of firmware installation; the firmware is
automatically upgraded during a software upgrade or a card or NE warm reset: 11QPE24,
11OPE8, and 11QCE12X. These cards must remain provisioned to use the default firmware for
the software release and will always have the default firmware installed.
The following are some firmware-related operations for reference:
Display all conditions on the NE, including FW-related conditions
CLI show condition
Show Conditions.
The following are the FW-related conditions:
FWUPGRADEPENDING: raised when the Active Release does not match the
Provisioned Release, awaiting a normal or hitless firmware upgrade
FWVERSIONNOTDEFAULT: raised when the Active Release does not match the
default firmware for the software release.
FWPENDINGOBSOLETE: raised when the Active Release does not match any of the
available firmware profiles for the card.
The above conditions are only raised or cleared following a card warm or cold reset, including
user-initiated, SW upgrade, database restore, and card insertion.

Display all available FW profiles for a card in the software release

CLI show firmware available (lists available FW profiles for all cards)
show firmware available <card>
(example: show firmware available 43stx4)
The default profile for the SW release is marked with an asterisk
WebUI Expand the equipment tree, select a card, select the Firmware tab, and click on the Provisioned
Release drop-down menu. The default profile for the SW release is marked with an asterisk.
PhM In the NE inventory window, click on the Administration menu and
select Card Firmware. In the Card Firmware window, click on
the highlighted button shown to open the installed firmware table. The
default profile for the SW release is marked with a checkmark.
Display the FW attributes of an individual card

To display or change the attributes of an individual card, double-click on a card in the Card
Firmware window.
Display the FW attributes of all cards in an NE

CLI show firmware ne detail
WebUI Click on the Reports menu then select Firmware.
Provision a card to load a specific FW profile

(example: config firmware card 1/3 1.4.1)
WebUI Expand the equipment tree, select a card, select the Firmware tab, click on the Provisioned
Release drop-down menu, select the desired profile (for example, profile_1.4.1), and press the
Submit button.
In the Card Firmware window, double-click on a card. Select the desired profile (for example,
Note: This establishes a specific firmware release for a card rather than the default
version for the software release. After provisioning, the specific firmware version will be
installed or maintained during subsequent cold reboots.

Provision a card to load the default FW profile

CLI config firmware card <shelf/slot> default
WebUI Expand the equipment tree, select a card, select the Firmware tab, click on the Provisioned
Release drop-down menu, select --default--, and press the Submit button.
In the Card Firmware window, double-click on a card. Press the Default button then the OK
button.
Note: In a new NE or an NE with a clear database, each card has the Provisioned Release
set to default. In this state, the default FW profile is automatically selected for the SW
release.
Firmware provisioning example for 260SCX2:
The following table shows 260SCX2 availble firmware profiles in R7.0.0, R7.0.2, and a
hypothetical future release. The default FW profile is marked with an asterisk:
Software release: 7.0.0 Software release: 7.0.2 Software release: future
profile_1.1.1 * profile_1.1.1 profile_1.1.1
profile_1.2.1 * profile_1.2.1
profile_1.3.1 *
In software release R7.0.2, the 260SCX2 firmware Provisioned Release can be set to one of
three values:
1.1.1: this will cause firmware profile_1.1.1 to be loaded into the card on the next cold
reset or hitless upgrade. This firmware version will be maintained or locked-in during
subsequent cold reboots and software upgrades.
1.2.1: this will cause firmware profile_1.2.1 to be loaded into the card on the next cold
reset or hitless upgrade. This firmware version will be maintained or locked-in during
subsequent cold reboots and software upgrades.
Default (--default--): because profile_1.2.1 is the default in R7.0.2, this will cause
firmware profile_1.2.1 to be loaded into the card on the next cold reset or hitless upgrade,
similar to provisioning 1.2.1. However, if the software is upgraded to a future release
with profile_1.3.1 as the default, then profile_1.3.1 will automatically be selected.



CRN 1830PSS R7.0.2 PDF

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

CRN 1830PSS R7.0.2 PDF

Uploaded by

Copyright:

Available Formats

October31!

Copyright 2014 Alcatel-Lucent. All Rights Reserved.

Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary ii

iii Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

Example configuration of ftp server ...................................................................................................... 303

Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary iv

Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary vi

vii Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary viii

Reason for reissue

How to use this document

ix Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

emphasis Text that is emphasized

document titles Titles of books or other documents

file or directory names The names of files or directories

keyboard keys The name of a key on the keyboard

system output Text that a system displays or prints

variable A value or command-line parameter that the user provides

[] Text or a value that is optional

Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary x

Table 1 Related documentation

Document No. Title Updated

xi Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

Document No. Title Updated

Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary xii

Table 2 Software ordering

Ordering No. Description

Online Customer Support (OLCS)

xiii Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

New features in Release 7.0.2 25

Features in Release 7.0.1 36

Features in Release 7.0.0 41

15 Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

Table 3 Supported hardware for 1830 PSS-16/PSS-32

PFDCxxK PSS-16 DC Power Filter

Power Distribution Unit - Unit is mounted

Power Distribution Unit - Unit is mounted

USRPNL User Interface Panel 40 10 1 Req. per main shelf Yes

PF Power Filter 19, 36 1, 11 2 Req. (1 w/ alarms) Yes

FAN Fan Subsystem 37 21 1 Req. Yes

Power Distribution Unit - Unit is mounted

Power Distribution Unit - Unit is mounted

Power Distribution Unit - Unit is mounted

NAR Rear Access (4 inputs, Unit is mounted

Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary 16

4G Dual Port Pluggable 2-17, 3-9,

4G Dual Port Pluggable 2-17, 3-9,

11G Single Port Tunable

11STAR1A 11G Single Port Tunable 2-17, 3-9,

11G Single Port Tunable

11G Single Port Tunable

11G Dual Port Pluggable

11G Dual Port Pluggable

11G Dual Port Pluggable

17 Alcatel-Lucent Proprietary Alcatel-Lucent 1830 PSS-16/PSS-32

24x GbE & 4x

Please note the known

Please note the known

11G Dual Port Pluggable

Alcatel-Lucent 1830 PSS-16/PSS-32 Alcatel-Lucent Proprietary 18

4x10Gb/s MUX Transponder

4x10Gb/s MUX Transponder

40G Single Port Tunable