Ensemble Controller R13 3 3 ReleaseNotes RevA

Ensemble Controller R13.3.
Document Number: 80000071399

Ensemble Controller R13.3.3
Ensemble Controller
Release 13.3.3
Release Notes
ADVA Optical Networking SE

Campus Martinsried
Fraunhoferstrasse 9a
82152 Martinsried/Munich
Germany
Phone: +49 89 89 06 65 0
ADVA Optical Networking SE

Maerzenquelle 1-3
98617 Meiningen-Dreissigacker
Germany
Phone: +49 3693 450 0
ADVA Optical Networking

5755 Peachtree Industrial Blvd
Norcross, GA 30092
Phone: +1 678 728 8600
E-mail: info@advaoptical.com
www.advaoptical.com 1
- Classified as Confidential -
Version: A Ensemble Controller R13.3.3
Contents January 20, 2023
1 Revision History ............................................ 4

2 Product Survey ............................................. 5
2.1 Enhancements in Version 13.3.3 ..................................... 5
Version: 1.1
2.2 Important Notes ........................................................... 6
2.3 Life Cycle Information ................................................... 7
2.4 Product Documentation ................................................. 7
2.5 Ensemble Controller Pro-Vision Customers ....................... 8
2.6 Pro-Vision to Ensemble Controller (ENC) Migration ............ 8
3 Supported Devices ........................................ 9

4 Customer Defects Fixed in This Release ......... 13
4.1 Pro-Vision Customer Defects Fixed in This Release .......... 14
5 System Requirements .................................. 15

5.1 General System Requirements...................................... 15
6 Installation Instructions ............................... 15

6.1 Migration Hints ........................................................... 17
6.2 Installation on Windows ............................................... 17
6.2.1 Full Installation .................................................................19
6.2.2 Upgrade from Version 12.1.1 or higher ................................20
6.3 Installation on Linux.................................................... 23
6.3.1 Full Installation .................................................................23
6.3.2 Upgrade from Version 12.1.1 or higher ................................25
6.4 Migration from Windows to Linux .................................. 27
7 Known Issues (List of Limitations) ................. 27

7.1 Pro-Vision Known Issues(List of Limitations) .................. 29
7.2 TAPI Limitations ......................................................... 30
8 Version History ........................................... 31

8.1 Enhancements to Version 13.3.2 .................................. 31
9 Fixes in Historical Releases ........................... 39

9.1 Pro-Vision Fixes in Historical Releases ........................... 55
10 Historical Limitations................................ 60
10.1 Pro-Vision Historical Limitations .................................... 66
11 Legal Information .................................... 68

12 Support Contact Information .................... 69
2
Version: 1.1
3
1 Revision History
Revision Date Reasons for Revision

Version:
A 1.1
20-Jan-2023 Document Creation
4
2 Product Survey
Beginning with Ensemble Controller version 13.1, the Embedded License Server (ELS)
manages any required licenses which must be ordered from the ADVA Customer Focus
Team. The licenses determine the scope of system functions and features in Ensemble
Controller, and also whether you have unimpeded access to all network objects within a
Version: 1.1
particular network. Your administrator must prepare and enable the Embedded License
Server as described in the Administrator Manual and install the required licenses.
2.1 Enhancements in Version 13.3.3
ENC R13.3.3 is a maintenance release that provides defect fixes in key areas of the system.
5
2.2 Important Notes
• Ensemble Controller R13.3.3 release requires supplemental scripts (that need to be

downloaded from Customer Portal) to validate database integrity and MUST be executed
prior to the upgrade process. Users are strongly advised to run these scripts in their
prior release and ONLY proceed with the upgrade process if the database validity check
Version:
passes. 1.1
In case of database integrity validation failure, please contact customer support
for further assistance.
• Note that FileZilla is now a package that can optionally be installed. It is a separate step
for Windows environment, but will not be installed and started by default
• While Discovering FSP3000 R7, the user is advised to change the general SNMP settings
in Ensemble Controller to match the new default SNMP settings on the device prior to
discovery.
• The ports used for client-server communication are configured by setting the
com.adva.fnm.option.webserver.port (insecure) property and/or the
com.adva.fnm.option.rest.securePort (secure) property in the server’s fnm.properties
file. 8080 and 8443 are the default values for these properties respectively. There must
be a corresponding entry for the launcher.webserver.port_X (where X is an integer)
property in the client’s launcher.properties file in the clientupdater directory. The
configured port(s) must be open in the firewall in order for the client to run and
communicate with the server.
• Beginning with R8.3.1, server overload protection has been implemented in relation to
short term performance objects. When the server starts, short term performance objects
stored in the database are counted and if they exceed the value configured in the
com.adva.nlms.mediation.performance.watchdog.max15minPmo property in
fnm.properties, all performance collection is suspended until enough performance
templates are unassigned such that the total number of performance objects are
brought below the configured threshold. For further details see the Scaling Options
section in the NM Specifications portion of the Ensemble Controller Administrator
Manual.
• The CSV service inventory report dump file, generated by the “Service Inventory Report
Generation” regular action will have the name format: Services_<date>.csv.
• Ensemble Controller R12.1.1 and later requires licenses stored in an ADVA embedded
license server, typically referred to as ELS. This server could be installed as an option
within the ENC installation. We recommend to use this option unless you have explicitly
planned for a different option. This server requires port 7071 and 8444 to be opened.
Please refer “Accessing the Embedded License Server Web GUI” chapter in the User
Manual and to the Manual for the ELS for more details.
• The Centralized Control Plane(CPc) requires a Java Runtime Environment installed on
the computer to run properly. If you intend to install the Centralized Control Plane on
your Linux Server please make sure that a recent java version is already installed in this
server before you start installation of Linux Ensemble Controller with Centralized Control
Plane. Please contact ADVA to obtain a copy of the Network Controller Administration
manual. If you use classic Control Plane or have no active DWDM Service Provisioning at
all, you don’t need the Centralized Control Plane and consequently also no pre-installed
Java. In this case just install Ensemble Controller without the Centralized Control Plane.
• The NCU3 controller of FSP3000 F7 is not supporting the classic, distributed Control
Plane (CPd) and should for this reason not be used in networks where the CPd is in use
with the optional Ensemble Optical Director.
• If an error occurs when starting the Ensemble Controller client in a Windows
environment which states “Error occurred during initialization of VM. Could not reserve
enough space…”, the following workaround is suggested. Go to the <Ensemble
Controller Installation Directory>/clientupdater directory. Edit the –Xmx parameter of
the lax.nl.java.option.additional property in the FSP NM ClientUpdater.lax file to be –
Xmx256M. Secondly, edit the –Xmx parameter of the launcher.nl.java.option.addtional
property in launch.properties to be –Xmx512M. Then restart the client. For larger
networks lowering the Xmx attribute of the launcher.nl.java.option.addtional could lead
to out of memory exceptions.
6
• When upgrading from a release prior to R13.2.2, the ENC client must be re-installed.
• Changes made to the FSP 3000AC using the Netconf interface can override changes
made from ENC even when the running configuration is locked on the network element.
• Beginning with ENC R13.1.x, the default theme of the ENC client has been enhanced for
better usability and includes a breadcrumb trail for navigation. This theme is called the
“ADVA” theme. No functionality has been lost as compared with the previous theme,
Version: 1.1 to as the Accessible theme. The user is able to choose between the ADVA
now referred
theme or the Accessible theme upon initial login after installation. The selection can be
changed from the view options.
• ADVA has improved software so you can manage Z4806V2 devices with the Pro-Vision
client on ENC software release 13.3. Because of these improvements, earlier releases
20.1.1 and previous are not compatible with ENC release 13.3. Z4806V2 R20.5.1 is
compatible with ENC release 13.3.
• Beginning with ENC R13.1.1, the format of the date in the notification manager was
changed from “HH:MM:SS MM/DD/YYYY” to the ISO8601 format “YYYY-MM-DD
HH:MM:SS”
• Sync Assurance users should backup the GNSS and TPA databases before upgrading to
ENC R13.3. See “Requirements to Upgrade Sync Assurance” section of the Administrator
Manual for more details.
• ENC R13.3.3 was released after ENC R14.1.1 and R14.2.1. Upgrades from 13.3.3 to
these releases may not be supported. Please contact customer support for more
information.
Note: The user should check the customer portal for the most updated copy of the release
notes.
2.3 Life Cycle Information
Ensemble Controller 13.3 is the final version of the 13.x release cycle and is treated as the
long term support version.
Enhancements for existing Ensemble Controller R13.3.3 (Build #10700) installations can be
ordered until the end of July 2025. Support for this release will be available until the end of
January 2027 when it will reach end of life.
ADVA reserves the right to replace Ensemble Controller R13.3.3 by a maintenance release
containing fixes for defects appearing in customer networks. If this release is produced, it
will also replace 13.3.3 as the long-term support version for 13.3.x and will be made
available free of charge to customers updating from 13.1.x or 13.2.x.
2.4 Product Documentation
The following support documentation is available for Ensemble Controller:

• Administrator Manual
o Includes Pro-Vision Administrator Appendix and Installing Ensemble Controller
for Pro-Vision
• User Manuals
• Integration Manual
• Pro-Vision Client User Guide
These can be found on the installation media, in the installation directory or on the ADVA
Customer Portal.
7
2.5 Ensemble Controller Pro-Vision Customers
For Ensemble Controller Pro-Vision customers there are specific locations within the
Ensemble Controller documentation that provide important installation, enabling and
upgrade information.
• For Ensemble Controller/Pro-Vision Installation procedures, see “Installing Ensemble
Version: 1.1 for Pro-Vision” in the Ensemble Controller Administrator Manual for more
Controller
information.
• For enabling Pro-Vision on the Ensemble Controller, see “Installing Ensemble
Controller for Pro-Vision” in the Ensemble Controller Administrator Manual for more
information.
• For Ensemble Controller upgrade procedures, see “Maintaining the Ensemble
Controller” in the Ensemble Controller Administrator Manual for more information.
2.6 Pro-Vision to Ensemble Controller (ENC) Migration
IMPORTANT
Due to the complex nature of the migration process, it is necessary to get in touch with the
ADVA Sales Representative. They will initiate the process that will guide through the
migration and provide further information. During this process, the necessary files and
documentation will be made available and potential support from ADVA side can be
negotiated.
8
3 Supported Devices
Table given below summarizes the products that are supported by this Ensemble Controller
release (compatibility).
Version: 1.1
Product Versions Comment
R3.1.1, R3.2.1, R3.2.2, R3.3.1, R3.3.2,

FSP 150CCf-825
R3.3.3, R3.3.4, R3.4.1, R3.5.1, R3.5.2
R6.1.1, R6.2.2, R6.5.1, R6.5.4, R6.5.5,

FSP 150CC-GE206
R7.1.1, R7.1.2, R7.1.3, R7.1.4, R7.1.5,
(All Variants)
R8.1.2, R8.1.3, R8.1.5, R8.5.1, R8.5.2
R7.1.4, R8.5.3, R9.6.1, R9.6.2, R9.6.3,

FSP 150CC-GE206V only R10.1.1, R11.1.1, R11.1.3, R11.2.1,
R11.2.2, R12.1.1
R6.1.1, R6.2.2, R6.5.1, R6.5.4, R6.5.5,

FSP 150CC-GE201 R7.1.1, R7.1.2, R7.1.3, R7.1.4, R7.1.5,
(All Variants) R8.1.2, R8.1.3, R8.1.5, R8.5.1, R8.5.2,
R9.6.2
GE114H/PH are
supported by
R.5.4.1 and above.
FSP 150CC-GE112, GE114S/SH
R5.2.1, R5.2.2, R5.3.1, R5.4.1, R5.4.2,
FSP 150CC-GE114, without IEEE 1588
R6.1.1, R6.2.1, R6.3.1, R7.1.1, R7.1.2,
FSP 150CC-GE114PH, PTP is supported
R7.1.3, R8.1.1, R8.1.2, R8.1.5, R8.5.1,
FSP 150CC-GE114H, from R6.1.1
R8.5.2, R9.5.1, R9.6.1, R10.1.1,
FSP 150CC-GE114SH, GE114S/SH with
R10.1.2, R10.5.1, R10.5.2, R10.5.3,
FSP 150CC-GE114S, IEEE 1588 PTP is
R11.1.2
FSP 150CC-GE114G supported from
R6.3.1, GE114G is
supported from
R8.1.1
GE101Pro support
GE112Pro, GE112ProM, R7.1.1, R7.1.2, R7.1.3, R8.1.1, R8.1.2,
is from R8.5.1
GE112ProH, GE114Pro, R8.1.5, R8.1.6, R8.5.1, R8.5.2, R9.1.1,
GO102ProS,
GE114ProC, GE114ProSH, R9.1.2, R9.1.3, R9.2.1, R9.5.1, R9.5.2,
GO102ProSP
GE114ProCSH, GE114ProHE, R9.5.3, R9.5.4, R9.5.5, R9.6.1, R9.6.2,
support is from
GE101Pro, GE102ProH, R9.6.3, R10.1.1, R10.1.2, R10.1.3,
R9.1.1; R9.6.1 is
GO102ProS, GO102ProSP, R10.5.1, R10.5.2, R10.5.3, R11.1.2,
not supported for
GO102ProSM, GE104, R11.5.1, R11.5.2, R11.6.2, R12.1.1,
GE102ProH.
XJ128SH, GE014E R13.1.1
GE114ProVMe, GE114ProVMe-
R7.5.1, R7.5.2, R7.6.1
C, GE114ProVMe-CS
XG108, XG108-H, XG108-SH R12.1.1, 13.1.1
R6.1.1, R6.2.2, R6.5.1, R6.5.2, R6.5.3, FSP 150CC-XG210-

R7.1.1, R7.1.2, R7.1.3, R7.1.4, R7.1.5, C available from
FSP 150CC-XG210, FSP
R8.1.2, R8.1.3, R8.1.5, R8.5.1, R8.5.2, R7.1.1, R11.1.2 only
150CC-XG210-C
R8.5.3, R9.6.1, R9.6.2, R9.6.3, R9.6.4, applies to FSP
R10.1.1, R10.1.2, R11.1.1, R11.1.2, 150CC-XG210-C
9
R11.1.3, R11.2.1, R11.2.2, R12.1.1,

R12.1.2
FSP 150-XG116Pro, FSP 150-

R9.1.1, 9.2.1, R9.2.2, R9.6.1, R9.6.2,
XG116ProH, FSP 150-
R10.1.1, R10.5.1, R10.5.2, R10.5.3,
XG118ProSH AC, FSP 150-
Version: 1.1DC, FSP 150- R10.5.4, R10.6.1, R11.1.1, R11.5.1,
XG118ProSH
R11.5.2, R11.6.1, R11.6.2, R12.1.1,
XG120Pro, FSP 150-
R12.1.2
XG120ProSH
FSP 150 XG300 (OS-V):

FSP 150-XG304 Native support may
FSP 150-XG304-F be limited in R12.1.1.
FSP 150-XG304U R4.7.4, R4.7.5, R20.1.1 PV client may be
FSP 150-XG304U-F used as a
FSP 150-XG308 workaround.
FSP 150-XG308-F
FSP 150XG440 R5.5.1
R18.1.2, R18.5.1, R19.1.2, R19.2.1,

FSP 150-XG404, FSP 150- PM collection is not
R19.5.1, R19.6.1, R19.6.2, R19.7.1,
XG418, FSP 150-XG480 supported for R19.6.1
R19.7.2
R8.1.1, R8.1.3, R8.5.1, R8.5.3, R9.5.1,

OSA 5410, OSA 5411
R9.5.3, R9.5.4, R9.5.5, R9.5.6
R8.1.1, R8.1.2, R8.1.3, R8.5.1, R8.5.2,

R8.5.3, R9.1.1, R9.1.2, R9.1.3, R9.5.1,
OSA 5420, OSA5421 R9.5.2, R10.1.1, R10.1.2, R10.2.1,
R10.2.2, R10.5.1, R10.5.2, R10.5.3,
R10.5.4, R10.5.5, R11.1.1
OSA 5412, OSA 5422 R10.6.1, R11.1.1
R10.1.1, R10.1.3, R10.2.1, R10.2.2,

R10.2.5, R10.2.3, R10.2.4, R10.5.1,
OSA 5430, OSA 5440
R10.5.2, R10.5.3, R10.5.4, R10.5.5,
R11.1.1
OSA 5331 R2.22, R2.23
R2.2.1, R2.2.2, R2.2.3, R2.3.1, R2.4.1,

OSA 5335, 5548C
R2.4.2, R2.5.1, R2.5.2, R2.5.3, R2.5.4
R8.5.1, R9.1.1, R9.1.2, R9.1.3, R9.1.5,

OSA 5401, 5405 R9.1.6, R9.5.1,R10.1.1, R10.5.1,
R11.1.1, R11.5.1
This device can be
OSA 3230B R1.09, R1.9.1, R2.2.1, R2.3.1 managed only by one
application at a time.
OSA 3350 R4.1.1, R4.1.2
R15.1.0.24, R15.2.1.6, R15.4.0.30,

SFP Discovery not
FSP 150EG-M R16.1.1, R16.2.1, R17.1.1, R17.2.1,
supported for R18.2.1
R17.3.1, R18.1.1, R18.2.1
R5.6.1, R6.1.1, R7.1.1, R7.1.2, R7.1.3,

FSP 150EG-X R8.1.1, R8.1.2, R8.2.1, R9.1.1, R9.1.2,
R9.5.1, R9.5.2, R9.5.3
10
FSP 150CC-T1804
R5.2.1, R6.1.1, R6.5.1, R6.6.1
FSP 150CC-T3204
SNMP managed.
EFM managed via
FSP 150CP R2.4.x, R2.6.1, R2.7, R2.8 FSP 150CP. EFM
Version: 1.1 managed via FSP
150CM.
R3.3.2, R4.1.1, R4.2.1, R4.2.2, R4.2.3,

FSP 150CM
R4.3.1, R4.3.2, R4.3.5
FSP3000-SH1PCS R6.6.1
FSP 1500 R3.0, R3.2
R13.1.2, R13.2.1, R13.2.2, R13.2.3,

R13.3.1, R13.3.2, R15.1.1, R15.1.2,
R15.2.1, R16.1.1, R16.1.2, R16.1.3,
R16.1.4, R16.2.1, R16.2.2, R16.3.1,
R16.3.2, R16.3.3, R17.1.1, R17.1.2,
FSP 3000R7 R17.2.1, R17.2.2, R17.2.3, R17.2.4,
R18.1.1, R18.1.2, R18.2.1, R18.2.2,
R18.2.3, R18.2.4, R19.1.1, R19.1.1A1,
R19.1.2, R19.2.1, R19.3.1, R19.3.2,
R20.1.1, R20.2.1, R20.3.1, R20.4.1,
R21.1.1, R21.1.2, R21.1.3, R21.1.4
R2.1.1, R2.1.2, R2.2.1, R2.2.3, R2.2.6,

FSP 3000C R3.1.1, R3.1.5, R3.1.6, R3.2.0, R3.2.1,
R3.3.1, R3.4.1, R4.1.1
R6.2.2, R7.2.6, R7.2.8, R7.2.9,

Hatteras HN4000/HN400
R14.2.35, R14.2.39, R15.1.3, R15.1.4
R2.2.1, R2.3.1, R3.1.2, R3.2.1, R3.2.2,

FSP 3000 ALM R3.3.1, R3.4.1, R4.1.1, R4.1.3, R4.5.1,
R4.5.2
ADVA 1400 R16.1.4
Juniper MX240
Juniper MX480 15.1F5
Juniper MX960
Table 1: Supported Device Types and Releases
11
The following table lists devices supported by Ensemble Controller via the Pro-Vision Web
Client
Product Versions Comment
Version:
OS606 1.1 R4.5.81/1.5.8.1
OS904, OS904-MBH, OS906, OS906G-M,

OS912, OS940, OS904-M R4.5.81
OS9124-410G, OS9244-1210G R4.5.81
XG304, XG304u, XG308 R19.6.2
EM316LNXM-OT R4.9fdr14
OD-NM R5.15.2
Z4806V2 R20.5.1
The table below consists of the FSP Element Manager versions that are embedded in this NMS
release.
Product EM Version Comment

FSP 1500 Element Manager R3.2.6
Sync View Plus/OSA EM R2.4,
OSA 5335, OSA 5548C
2.5
Table 2: Embedded Element Manager Versions
Your license key for any version prior to 13.x is no longer valid for this release. A license for
13.x is required, which is typically delivered as a .bin file. This license needs to be installed
in the ELS server assigned to this ENC instance. An upgrade procedure with database
migration is supported from Ensemble Controller 12.1.x, 12.2.x, 12.3.x, 12.4.x, 13.1.x,
13.2.x, and 13.3.1. Please note that the upgrade procedure has some additional steps
described in Section 6.
ELS R3.3.2 is packaged with ENC R13.3.3. Previous versions of ELS are also compatible with
ENC R13.3.3, but are not recommended due the log4j security vulnerabilities, CVE-2021-
44228 and CVE-2021-45046.
12
4 Customer Defects Fixed in This Release
The following tables list customer defects and defects previously on the List of Limitations
which were resolved in this release.
Version: 1.1
Ensemble Optical Director
ID Reference Description
In ENC R13.1.2, the OTS layer is sometimes duplicated, but
FNMD-65922 with different names.
In ENC R13.3.1, the user was unable to delete a link due to
TS 301871 a service being on the link, even though the service was not
FNMD-73308 TS 302845 found.
In ENC R13.3.1, service provisioning with odd lambdas
FNMD-74677 TS 303056 failed.
In ENC R13.3.2, Services with back to back 40CSM modules
FNMD-75354 TS 305648 were not working.
In ENC R13.3.2, a null pointer exception occurred after TAPI
FNMD-75598 discovery which led to notification failures
Ensemble Packet Director

In ENC R13.3.1, fiber break indications were displayed on
links between FSP XG480 devices which did not have
FNMD-73613 TS 301268 services
Note: Please see Section 9 for Fixes in Historical Releases
13
4.1 Pro-Vision Customer Defects Fixed in This Release
ID Description
On an air-gapped network with no internet access, the system did not
download all the fonts, so there were font issues in the Pro-Vision displays
and icons. The system now displays all Pro-Vision fonts and icons
Version: 1.1
FNMD-67104 correctly.
See Section 9.1 for list of Provision defects fixed in historical releases.
14
5 System Requirements
In order to use the software download and the NE configuration backup/restore feature, an
FTP server is required which is not part of the Ensemble Controller installation. ADVA
recommends the following FTP and SCP/SFTP servers for Windows Platform:
• Windows: FileZilla (FTP); CopSSH (SCP, SFTP), free limited test version of these
Version: 1.1
applications is provided with the Ensemble Controller Installation
5.1 General System Requirements

The Ensemble Controller software is using Operating System and network resources.
Without full access to these resources, Ensemble Controller cannot work properly and may
show erroneous behavior.
Therefore, it is required that any security software such as virus scanners and firewalls are
configured to grant access to the resources that Ensemble Controller uses:
• Full read-write access to Ensemble Controller installation folders

• Full network access for Ensemble Controller executable
• No blocking for network traffic on ports used Ensemble Controller.
• ADVA optical networks is not able to support customers installing the software in
virtual environments such as VMWare ® or KVM and we can’t give any advice how to
set up virtual machines to ensure proper operation for these operating systems. We
therefore reserve the right to reject all malfunction reports raised for virtualized
systems, except the issue can be reproduced in a non-virtual environment as well.
The exception to this is that virtualized server environments are possible using
Windows or Red Hat Linux with VMWare. Other solutions are not tested and
therefore cannot be supported.
Please refer to the Ensemble Controller Administration Guide, section 1.2 Installation
Requirements for further details.
6 Installation Instructions
For the full installation any previous version of the Ensemble Controller must be uninstalled
before you install this version of Ensemble Controller.
We recommend that you disable anti-virus software and Personal Security Suites
temporarily during the installation process.
The user is advised that during the installation/upgrade process to not minimize the wizard
dialogue and allow the process to complete without disruption.
A physical medium is optionally available for installation.
The Ensemble Controller Server Installation is supported on the following Operating

Systems:
• Windows Server 2012 R2 (64 bit)
• Windows Server 2016 (64 bit)
• Linux Red Hat Enterprise Linux 7.6 through 7.9 (64 bit only)
o Deployment of Ensemble Fiber Director requires 7.8 or higher
• Linux Red Hat Enterprise Linux 8.1 through 8.2 (64 bit only). Testing has been
performed with Linux 8.2.
15
Optional applications using Docker containers like GNSS assurance and PTP Assurance as
extensions of Ensemble Sync Director, Ensemble Fiber Director or TAPI NBI are only
available for Linux. The system administrator is responsible for the correct installation and
maintenance of Docker. The minimum version of Docker required is v18.09 which has been
tested with all supported versions of Linux.
Version:
Note: 1.1 Ensemble Controller on a Windows Server in general, you must first
To install
install the Microsoft Visual C++ 2015 Redistributable Package on your 64-bit
system.
The Ensemble Controller Client Installation is supported on the following Operating

Systems:
• Windows Server 2012 R2 (64 bit)
• Windows 10
• Linux Red Hat Enterprise Linux 7.6 through 7.9 (64 bit only)
• Linux Red Hat Enterprise Linux 8.1 through 8.2 (64 bit only). Testing has been
performed with Linux 8.2.
Note: All supported Windows and Linux operating systems may be used natively or on
VMWare vSphere 6.5/6.7/7.0
Note: Running the ENC client in a Red Hat Linux environment is only supported with the
GNOME 3 desktop manager with X11 protocol. The X11 server, GNOME desktop manager
and the ENC client must run on the same machine.
Pro-Vision Web Client Supported Browsers

Browser
Platforms
Internet Google
Firefox Safari Edge
Explorer Chrome
Windows
94.0.2 IE11 Not Applicable 96 Not Applicable
Server 2008
Windows
Server 94.0.2 IE11 Not Applicable 96 Not Applicable
2008-R2
Windows
Server 2012
Windows
Server 94.0.2 IE11 Not Applicable 96 Not Applicable
2012-R2
Windows
Server 2016
Windows
Server 2019
Windows 10 94.0.2 IE11 Not Applicable 96 96.0.1054.43
16
Mac OS X
66 Not Applicable 11.1.1 78 Not Applicable
(10)
Version:
For 1.1 please check the Administrator Manual of the Ensemble Controller.
more details,
Note: When running the Ensemble Controller client on Windows operating systems, ADVA
recommends using 64 bit machines when managing larger networks for performance
reasons. Additionally, enabling Pro-Vision on a Windows server is only supported with the
64 bit installation on a 64 bit machine.
6.1 Migration Hints
The installation supports only upgrades from version R12.1.1, R12.2.1/2, R12.3.1, R12.4.1,
R13.1.x, R13.2.x, 13.3.x to R13.3.3. If upgrading from a release prior to R12.1.1, please
refer to the migration hints in the release notes of R12.1.1 for the appropriate upgrade
instructions and path. Please note that the upgrade of the Ensemble Controller server for
large networks may take several hours and the user is advised to not login to Ensemble
Controller client during this period.
Please make sure you have a copy of all intermediate versions before you start the upgrade
procedure. After each installation step, the Ensemble Controller server must be started once
to complete the respective upgrade step.
Please note that only the client of Ensemble Controller R13.3.3 is compatible with the
Ensemble Controller server R13.3.3.
Please close all other applications before installing Ensemble Controller.
It is recommended to double-check all output paths for Ensemble Controller generated files:
• inventory dump: <install-dir>/var/csv/

• event log: <install-dir>/var/log/
• performance data dump: <install-dir>/var/PM/
• Ensemble Controller database backup: <install-dir>/var/db.backup/
Note: Beginning with ENC R12.1.1, the upgrade process for HA configuration has changed.
Please refer to the administration manual for details.
Note: Due to security enhancements, beginning with ENC R12.3.1, the SNMP profile settings
configured for a given device must match the device exactly. In the past, for example, if the
default v3 settings failed to successfully contact the device, ENC would attempt to use the
default v2c settings. This will no longer be the case.
6.2 Installation on Windows
Ensemble Controller supports the 64 bit (to be used only with 64 supporting hardware)
windows installations.
The Windows package of Ensemble Controller includes the free FTP server FileZilla version
0.9.29 and the free SCP/SFTP server CopSSH version 5.4.2. This version of CopSSH is
17
packaged with Ensemble Controller for testing purposes only. It is not intended for a
production environment and ADVA does not offer technical support for CopSSH. ADVA
recommends that an up to date commercially licensed SSH tool be installed. Please refer to
the Administration Guide, section 1.2 Installation Requirements for further details.
Note: FileZilla is now a package that needs to be installed as a separate step for Windows
Version: 1.1
environment, it will not be installed and started by default
When specifying the directory on the FTP or SCP/SFTP server for Software Download or NE
configuration backup/restore in the Ensemble Controller Network Properties page, we
recommend using absolute paths only (starting with a slash), e.g. “/my-fnm-files”.
When using FileZilla this refers to the FTP user’s home directory as specified in FileZilla (e.g.
C:\FTP\my-fnm-files).
When using OpenSSH this by default refers to the OpenSSH installation folder (e.g.
C:\Program Files\OpenSSH\my-fnm-files).
SNMP Forwarder
The SNMP Forwarder Service is primarily used by the FSP 1500 Element Manager and is no
longer started by default. To start it manually, cd to the following directory: C:\Program
Files (x86)\ADVA Optical Networking\FSP Network Manager\bin
Execute the following script with Administrator privileges: StartSnmpForwarder.bat
To stop it manually, cd to the following directory: C:\Program Files (x86)\ADVA Optical

Networking\FSP Network Manager\bin
Execute the following script with Administrator privileges: StopSnmpForwarder.bat
The SNMP Forwarder service is set to Manual during installation. The user can set it to
automatic if they want the SNMP Forwarder to start automatically after a reboot.
18
6.2.1 Full Installation

• Make sure you have full administrator permissions to your local PC.
• Uninstall any previous version of Ensemble Controller using the Windows Control
Panel. It is important to close all other applications before uninstalling Ensemble
Controller because the machine will restart at the end of the uninstallation process.
Version: 1.1from Windows and log in again.
• Log off
• Download and copy the Ensemble Controller installation executable
(Ensemble_Controller_for_Windows_v13.3.3-B10700-64bit.exe or
Ensemble_Controller_for_Windows_v13.3.3-B10700-bit.exe) to a directory on your
local hard drive and execute it.
Note: The two Window installation zip files (.zip.001 and .zip.002) downloaded from
the customer portal can be joined back together by unzipping the first file, i.e.
“Ensemble_Controller_for_Windows_v13.3.3_64bit.zip.001”.
• Or insert the Ensemble Controller DVD into your DVD-ROM drive and start the
installation program by launching the file Setup.exe.(Run as Administrator)
• Follow the steps of the installation wizard.
o Note: The Embedded License server can be installed at this stage if it has not
already been installed. Please refer to the installation instructions in the
Administration Guide for details
o Required licenses should also be installed on the ELS before running the
Ensemble Controller Server. Please refer to the installation instructions in the
• Open the Service Control Panel from the Windows System Control and check that all
services starting with “ADVA:” are running. These services incorporate the Ensemble
Controller Server.
• To enable Pro-Vision, set the following properties in fnm.properties:
o com.adva.nlms.mediation.pv.startModule=true
o com.adva.nlms.sdn.enabled=true
• After the installation you can start the Ensemble Controller from the Start menu. The
initial administrator account is
o User: admin
o Password: ChgMeNOW
• The Pro-Vision client may be started by:
1. Pointing a web browser to https://<ipaddress>:8443/pv
Upon first login you might see a message stating that ENC has no access to ELS and
consequently no license. This window also provides the hint that either a local ELS should be
installed or that the respective entry in fnm.properties should be changed to point to the
designated ELS. If you haven’t yet obtained a 12.x ENC license please talk to your local
sales representative.
Note: For more details on installation instructions, refer to the Administration Manual.
19
6.2.2 Upgrade from Version 12.1.1 or higher

• Start your current Ensemble Controller client
• Select the Root Network Node from the Network Tree and use the right
mouse and select the “Check DB Inconsistency” menu option.
• If any errors are shows, Select the Root Network Node from the Network Tree
Version: 1.1and select the “Fix DB Inconsistency” Menu option. Wait for this operation to
complete and exit the client.
• Make sure you have full administrator permissions to your local PC.
• Close all Ensemble Controller Client applications.
• Verify with the Windows Task Manager that there is no more process called
“fnm.exe” running any more. If there are such processes, it is required to terminate
them using the Windows Task Manager.
• Copy the following scripts from the DVD (scripts directory) to the previous Ensemble
Controller Installation scripts directory - (e.g.
C:\Program Files\ADVA Optical Networking\FSP Network Manager\scripts)
• printDBInconsistenciesPostgres.bat
• printDBInconsistenciesPostgres.sql
• Open a command window by launching “cmd” in the “execute” entry of the Windows
start menu.
• Change the directory to the location where the scripts are installed. (e.g.
C:\Program Files\ADVA Optical Networking\FSP Network Manager\scripts
• Check if Database is running:
1. Verify that the Postgres database is running by typing “net start Postgres” in
this window.
2. This should inform the user that database service was started or is already
running.
• Check if Database is running:
1. Run the file printDBInconsistenciesPostgres.bat (use default password
“NeverChange”)
• The error free output should be:
=======================================================================
=
= SEARCHING FOR DB INCONSISTENCIES. PLEASE CONTACT TECH SUPPORT TEAM IF ANY ARE FOUND! =
=
=======================================================================
Searching for not supported devices:
find_unsupported_devices
--------------------------
check_aps_group_inconsistecies
--------------------------------
=======================================================================
=
= SEARCHING FOR ORPHAN ENTITIES. FNM UPGRADE WILL FAIL IF THERE ARE ANY! =
=
=======================================================================
check_entity_db_impl_relations
--------------------------------
check_cn_network_element_table
--------------------------------
find_entities_with_invalid_ne_reference
-----------------------------------------
check_mac_address_duplications
--------------------------------
20
=======================================================================
Services on FSP3000 R7 nodes where the optical channels are missing network ptp information:
check_fsp3000r7_services_missing_network_port_ptp
---------------------------------------------------
=======================================================================
Services containing optical channels which are missing port or module information:
label | subchconn_id
-------+--------------
Version: 1.1
=======================================================================
Services which are missing port or module information:
label | id
-------+----
=======================================================================
Modules referencing services which do not exist:
name0 | aidstring | id
-------+-----------+----
=======================================================================
List of duplicated aids:
ne_id | aidstring | count
-------+-----------+-------
=======================================================================
Duplicate entities have such ids:
name0 | id | id
-------+----+----
Entities in cycle size 1 have such ids:
id
----
id | id
----+----
id | id | id
----+----+----
id | id | id | id
----+----+----+----
Duplicated CC825 shapers:
ne_id | portindex | flowindex | qosindex
-------+-----------+-----------+----------
=======================================================================
Fdfr ends without parent:
id | shortdescription
----+------------------
=======================================================================
Duplicated PG Ports:
shortdescription | ne_id | count
------------------+-------+-------
=======================================================================
Entities which have reference to non existent Network Element:
id | ne_id | shortdescription | jdoclass
----+-------+------------------+----------
=======================================================================
List of Alarms associated to multiple Services:
sourcene | entitydescription | moduletypename | services
----------+-------------------+----------------+----------
List of entities with too long entity alias

id
----
21
• Only proceed if the database validation succeeds. Please call Customer Service for
support in case of failures.
• If unsupported devices (devices for which support has been removed) are found in
the database, the script will provide a warning that says “UNSUPPORTED, PLEASE
REMOVE BEFORE UPGRADE”. If these devices are not removed, the upgrade will fail.
• Please
Version: 1.1backup the fnm.properties file and reportdb directory from the previous
versions also described in Ensemble Controller Administration Manual Upgrade
Installation sections (preparations)
• Also copy the file fnm.properties, log4j.properties from the Installation
directory to a secure location
• The user is advised to back up the contents of the reportdb directory (from
the previous version installation directory) to a safe location
• The user is advised to back up the contents of the images directory (from the
previous version installation directory) to a safe location (if images had been
used)
• The user is advised to back up the contents of the CustomProducts directory
(from the previous version installation directory) to a safe location (if Custom
Products had been used)
• Copy (Ensemble_Controller_for_Windows_v13.3.3-B10700-64bit.exe or
Ensemble_Controller_for_Windows_v13.3.3-B10700.exe) to a directory on your local
hard drive or insert the Ensemble Controller DVD into your DVD-ROM drive.
1. Note: upgrade from the 64 bit version to the 32 bit version is not supported.
Neither is an upgrade from the 32 bit version to the 64 bit version. The
workaround is to back up the database, uninstall the old version, install the
new version and restore the database.
• Start the installation program (Run as Administrator)
• Follow the steps of the installation wizard.
• Note: The Embedded License server can be installed at this stage if it has not
• Required licenses should also be installed on the ELS before running the
• Please restart the machine once the installation completes.
• After the machine comes back up, you must wait until the system upgrades the
database. Refer to the 'dbupgrade.log' file located under var\log for the following
messages:
1. At the beginning of a database upgrade:
INFO - =======================================================================
INFO - DATABASE UPGRADE HAS BEEN STARTED AND THIS PROCESS CAN TAKE A WHILE TO
COMPLETE. PLEASE WAIT FOR THE DATABASE UPGRADE COMPLETION MESSAGE BEFORE
CONTINUING.
INFO - =======================================================================
2. Note
The upgrade process may take some time to finish, which is dependent upon
the database size, the upgrade path (number of skipped intermediate NM
versions) and the server performance.
3. Upon completion of a database upgrade:

INFO - =======================================================================
INFO - DATABASE UPGRADE HAS BEEN FINISHED.
INFO - =======================================================================
22
• Open the Service Control Panel from the Windows System Control and check that the
following services are started:
• ADVA: JMS Server
• ADVA: Mediation Server
• ADVA: PostgreSQL Server
Version:•1.1ADVA: SNMP
• Copy the images directory from the backup secure location to the new installation
directory (e.g. C:\Program Files\ADVA Optical Networking\FSP Network
Manager\images)
• Copy the CustomProducts directory from the backup secure location to the new
installation directory (e.g. C:\Program Files\ADVA Optical Networking\FSP Network
Manager\ CustomProducts)
• Modify the new fnm.properties in the installation directory to update any variables
you may have changed in the previous version or to set new variables available in
the new version. Use the fnm.properties file that you saved in the secure location as
a reference only
• Please perform a server restart for the properties files changes to take effect
• Upon first login after upgrading you might see a message stating that ENC has no
access to ELS and consequently no license. This window also provides the hint that
either a local ELS should be installed or that the respective entry in fnm.properties
should be changed to point to the designated ELS. If you haven’t yet obtained a 12.x
ENC license please talk to your local sales representative.
• Cleanup
1. If you have successfully logged on to the Ensemble Controller after this
procedure, invoke the cleanPostgresAfterUpgrade.bat script (Batch file) to
clean up existing Postgres folders and terminate any of its processes.
Please note that the first server startup phase after an upgrade takes reasonably more time
than a regular startup. During the startup phase client logins are rejected.
6.3 Installation on Linux

Note: The two Linux installation files downloaded from the customer portal must be
concatenated prior to installation using the following command:
cat Ensemble_Controller_for_Linux_v13.3.3.tar.* >
Ensemble_Controller_for_Linux_v13.3.3.tar
SNMP Forwarder
The SNMP Forwarder process is primarily used by the FSP 1500 Element Manager and is no
longer started by default. To start it manually, cd to the following directory:
/opt/adva/fsp_nm/bin
Execute the following script: snmpforwarder.sh start
To stop it manually execute the following script: ./snmpforwarder.sh stop
To check the status of the SNMP forwarder, execute: ./snmpforwarder.sh status
6.3.1 Full Installation

• Become root:
• su –
• Uninstall any previous version of Ensemble Controller:
• cd /opt/adva
23
• ./uninstall-fsp_nm
• Copy the Ensemble Controller installation file to a directory on your local hard drive.
• Untar the archive:
• tar xf <tar archive>
• Start the installation program:
Version:•1.1./install
• If you wish to run Ensemble Controller as a user other than root, follow these
instructions (which can also be found in the Administrator Manual)
a) Shutdown the Ensemble Controller server using the following command:
/opt/adva/fsp_nm/bin/fnm.server stop
b) Shutdown the Database server by executing the following command as root:
/opt/adva/fsp_nm/postgres/support-files/postgres.server stop
Create a user account for the remote communication:
c) Set the user password with the following command: passwd username
d) Change to the current directory by typing: cd/opt/adva/fsp_nm
e) Run the changeUser.sh script by typing:
/opt/adva/fsp_nm/bin/changeUser.sh <username><groupname>
f) Only for a Linux OS, restart the server computer for the changes to take effect.
g) Start the Database server by executing the following command as root:
/opt/adva/fsp_nm/postgres/support-files/postgres.server start
h) Start the NM server using the following command:
/opt/adva/fsp_nm/bin/fnm.server start
• To enable Pro-Vision, set the following properties in fnm.properties:
1. com.adva.nlms.mediation.pv.startModule=true
2. com.adva.nlms.sdn.enabled=true
• After the installation you can start the Ensemble Controller typing “fnm” The initial
administrator account is
• User: admin
• Password: ChgMeNOW
• The Pro-Vision client may be started by:
1. Pointing a web browser to https://<ipaddress>:8443/pv
• Upon first login you might see a message stating that ENC has no access to ELS and
consequently no license. This window also provides the hint that either a local ELS
should be installed or that the respective entry in fnm.properties should be changed
to point to the designated ELS. If you haven’t yet obtained a 12.x ENC license please
talk to your local sales representative. Note: The Linux installation does not include
FileZilla or CopSSH as Linux contains an FTP server.
Note: For more details on installation instructions, refer to the Administration Manual.
24
6.3.2 Upgrade from Version 12.1.1 or higher

• Start your current Ensemble Controller client
1. Select the Root Network Node from the Network Tree and use the right
mouse and select the “Check DB Inconsistency” menu option
2. If any errors are shows, Select the Root Network Node from the Network Tree
Version: 1.1and select the “Fix DB Inconsistency” Menu option. Wait for this operation to
complete and exit the client.
• Become root:
1. su –
• Copy the following scripts from the DVD (scripts directory) to the previous Ensemble
Controller Installation scripts directory - (e.g. /opt/adva/fsp_nm/scripts)
1. printDBInconsistenciesPostgres.sh
2. printDBInconsistenciesPostgres.sql
• Run the shell script printDBInconsistenciesPostgres.sh (to check for basic
inconsistencies) with the following command:
1. cd /opt/adva/fsp_nm/scripts
2. ./printDBInconsistenciesPostgres.sh (use default password
“NeverChange”)
• The error free output should be:
======================================================================================
= =
= SEARCHING FOR DB INCONSISTENCIES. PLEASE CONTACT TECH SUPPORT TEAM IF ANY ARE FOUND! =
= =
======================================================================================
Searching for not supported devices:
find_unsupported_devices
--------------------------
check_aps_group_inconsistecies
--------------------------------
======================================================================================
= =
= SEARCHING FOR ORPHAN ENTITIES. FNM UPGRADE WILL FAIL IF THERE ARE ANY! =
= =
======================================================================================
check_entity_db_impl_relations
--------------------------------
check_cn_network_element_table
--------------------------------
find_entities_with_invalid_ne_reference
-----------------------------------------
check_mac_address_duplications
--------------------------------
=====================================================================================
Services on FSP3000 R7 nodes where the optical channels are missing network ptp information:
check_fsp3000r7_services_missing_network_port_ptp
---------------------------------------------------
=====================================================================================
Services containing optical channels which are missing port or module information:
label | subchconn_id
-------+--------------
=====================================================================================
Services which are missing port or module information:
label | id
-------+----
=====================================================================================
Modules referencing services which do not exist:
name0 | aidstring | id
25
-------+-----------+----
=====================================================================================
List of duplicated aids:
ne_id | aidstring | count
-------+-----------+-------
=====================================================================================
Duplicate entities have such ids:
Version:
name0 | id 1.1
| id
-------+----+----
id
----

id | id
----+----
id | id | id
----+----+----
id | id | id | id
----+----+----+----
Duplicated CC825 shapers:

ne_id | portindex | flowindex | qosindex
-------+-----------+-----------+----------
=====================================================================================
Fdfr ends without parent:
id | shortdescription
----+------------------
=====================================================================================
Duplicated PG Ports:
shortdescription | ne_id | count
------------------+-------+-------
=====================================================================================
Entities which have reference to non existent Network Element:
id | ne_id | shortdescription | jdoclass
----+-------+------------------+----------
=====================================================================================
List of Alarms associated to multiple Services:
sourcene | entitydescription | moduletypename | services
----------+-------------------+----------------+----------
List of entities with too long entity alias

id
----
• ONLY proceed if the database validation succeeds. Please call Customer Service for
support in case of failures.
• If unsupported devices(devices for which support has been removed) are found in
the database, the script will provide a warning that says “UNSUPPORTED, PLEASE
REMOVE BEFORE UPGRADE”. If these devices are not removed, the upgrade will fail.
• Copy the file fnm.properties from the Installation directory to a secure location
• Copy the Ensemble Controller Installation file to a directory on your local hard drive.
• Untar the archive:
• tar xf <tar archive>
• Start the installation program:
• ./install
26
• After the installation completes, you must wait until the system upgrades the
database. Refer to the 'dbupgrade.log' file located under var\log for the following
messages:
• At the beginning of a database upgrade:
INFO - =======================================================================
INFO - DATABASE UPGRADE HAS BEEN STARTED AND THIS PROCESS CAN TAKE A WHILE
Version: 1.1 TO COMPLETE. PLEASE WAIT FOR THE DATABASE UPGRADE COMPLETION MESSAGE
BEFORE CONTINUING.
INFO - =======================================================================
• Note
The upgrade process may take some time to finish, which is
dependent upon the database size, the upgrade path (number of
skipped intermediate NM versions) and the server performance.
• Upon completion of a database upgrade:

INFO -=======================================================================
INFO - DATABASE UPGRADE HAS BEEN FINISHED.
INFO -=======================================================================
• Modify the new fnm.properties in the installation directory to update any variables
you may have changed in the previous version or to set new variables available in
the new version. Use the fnm.properties file that you saved in the secure location as
a reference only. Please ensure the server has completed the upgrade process before
stopping the server, updating the file and restarting the server.
• Upon first login after upgrading you might see a message stating that ENC has no
access to ELS and consequently no license. This window also provides the hint that
either a local ELS should be installed or that the respective entry in fnm.properties
should be changed to point to the designated ELS. If you haven’t yet obtained a 12.x
ENC license please talk to your local sales representative.Cleanup
• If you have successfully logged on to the NM after this procedure, invoke the
cleanPostgresAfterUpgrade.sh script to clean up existing Postgres folders and
terminate any of its processes.
Please note that the first server startup phase after an upgrade takes reasonably more time
than a regular startup. During the startup phase client logins are rejected.
6.4 Migration from Windows to Linux
• Prepare Ensemble Controller database backup on existing system.

• Install Ensemble Controller on Linux and restore database.
• Start Ensemble Controller server.
7 Known Issues (List of Limitations)
ID Description
FNMD-46463 The "Set to Managed" menu item is only support for data services.
When replacing an OSFM module with an OSFMA module, the "In Use"
column of the Modules tab may not update dynamically. The workaround
is to click on another tab and then come back to the Modules tab which
FNMD-55418 will refresh the display.
27
The “OTN (Link) Layer” feature visible in the topology graph doesn’t
support the old service model (classic) trails as carried connections. If an
OTN Link is selected in the topology graph, the connection table tab
doesn’t list classic trails and the classic trails aren’t counted as traffic
FNMD-55839 (active, standby) in the link overview tab.
The names of some of the layers may be changed during the re-explore
Version: 1.1
FNMD-58391 after a reconfiguration operation.
Protection switches for OPPM line protected services in VSM mode should
not be performed from the topology graph(i.e. "Switch to Line B").
FNMD-65797 Protection switches should be performed from the service tree.
Service creation between a 2WCC10G and an UNO NE passing through
another 2WCC10G may fail if the user uses the default setting of the
facility type on the source network interface on the parameter page of the
service wizard. The user must set the source node facility type to match
FNMD-66016 the facility type of the virtual port on the UNO NE.
After service restoration or re-explorartion, custom names for certain
layers may not be preserved and the default names will be shown. The
FNMD-66418 user will have to rename those layers again.
Discovered explored Network Media Channel connections between FSP
3000C devices which are managed using the "Set to Managed" options
from the context menu cannot be modified. The workaround is to create
FNMD-66676 the explored service from the service wizard.
On rare occasions, performing a "Delete from Database" operation on a
service results in the service re-appearing in the Discovered folder.
FNMD-66689 Restarting the client will remove the service from the client display.
For services where the signal flows through a 16PSM module twice on
different ports, the layer browser and optical trace browser may not
FNMD-66793 display the position of the modules properly.
The ability to delete or “Set to Discovered” for an NFC is not supported.
However, if the last CFC associated with the NFC is set to discovered, then
the NFC will be as well. If a managed CFC is not available, the workaround
is to select a discovered CFC associated with the NFC, set it to managed,
FNMD-71322 and then set it to discovered again.
ID Description
If the oper state of some services are not correct in the Ethernet Service
Manager after an upgrade, the workaround is to execute an inventory
FNMD-66305 polling on the nodes.
After upgrading, it's possible that services in the Unassiged folder will not
FNMD-66823 be included in the service inventory report generated via regular actions.
General Functionality
ID Description
It may not be possible to acknowledge multiple alarms simultaneously
FNMD-55792 when sorting the alarm table by "Ack'd At" or "Ack'd By"
The ELS server will not function properly on machines using the “Thailand”
locale or where time is displayed in the Buddhist calendar format.
If ELS is installed with these parameters, the only workaround is to
FNMD-57733 reinstall windows and set it up using a Western calendar.
PM collection and display from ENC is not supported for device FSP 3000C
FNMD-59184 R3.3.1
GNSS data may not be collected from OSA devices using IPv6. The
FNMD-63181 workaround is to use IPv4.
28
In the tab section of the ENC client, if the user hides a column, the column
resize functionality may not be available for the remaining columns. The
FNMD-65619 workaround is to switch to another tab and then switch back again.
If the user uses "Ctrl-v" to paste the password into the password field of
the ENC login screen and the password is incorrect, the client may crash
on the 2nd attempt. The workaround is to restart the client and use the
Version: 1.1
FNMD-66624 correct password.
Note: Please See Section 10 for Historical Limitations
7.1 Pro-Vision Known Issues(List of Limitations)
Issue Description
Headless Pro-Vision Excel export can fail on headless Pro-Vision installations if

Installations and Excel fonts are not installed. To avoid this, install the missing
Export (FNMD-65696) “fontconfig” package.
The “Search” function in the Search tab in the Pro-Vision

“Search” Function in the online help does not find the item you searched for and
Pro-Vision Online Help returns a “null.” However, the table of contents in the
(FNMD-65092) Contents tab works correctly and you can search using the
browser search function.
Adding a local user with the same name as the LDAP user
Local User and LDAP User
generates an error. You must add the local user before the
Names (FNMD-55929)
LDAP user is created.
The *, ?, <, >, |, and : characters are not supported in

Windows filenames. To prevent Windows file naming issues,
Invalid Characters for Pro-Vision now maps these invalid characters to “_” when
Device Backup Filenames creating SFTP device backup files. For example, two devices
on Windows (FNMD- with the names device* and device? map to the same
54598) backup file on windows, so when you backup either device it
overwrites the other device’s backup. Both devices backup to
the file device-startup.
The port labels on the OD-RA12 RAMAN module front panel

OD-RA12 RAMAN Port
are reversed. The top port should be labeled RAMAN and the
Labels (FNMD-44718)
bottom port should be labeled MON.
In the Tools menu Upgrade Devices and Modules: Upgrade

Devices table, if you attempt an upgrade on a FiberDriver
Upgrade Devices Table and
that is configured with an incorrect TFTP server and/or
the Software Upgrade
directory, the Software Upgrade Status column entry shows
Status Column (FNMD-
it as successfully completed, even though it was not. To
38672)
avoid this, make sure that the TFTP server and directory are
configured correctly.
See section 10.1 for Pro-Vision historical limitations.
29
7.2 TAPI Limitations
Issue Description
TAPI does not support:

Version: 1.1
TAPI not supported • Protected services
services • Services that appear in the old model in Ensemble
Controller GUI
• NfC provisioning
Retrieving whole TAPI data To retrieve whole TAPI data store an additional 16GB of RAM
is needed, so it is not recommended to query it.
30
8 Version History
8.1 Enhancements to Version 13.3.2
ENC R13.3.2 is a maintenance release that provides defect fixes in key areas of the system
and the following
Version: 1.1 features:
Sync Product Support

• Integrate CMSW 3.04B2 (Element Manager SW for OSA3350 Cesium Clock)

• TAPI - Support CFC CS provisioning over existing NFC
• TAPI – CS to report control plan activation state
ENC R13.3.1 is a minor release that provides support for Optical, Packet Edge Cloud, and
Sync product devices. It also provides new features and enhancements to existing features.
Optical Product Support

• FSP 3000AC R21.1.1
• FSP 3000C R4.1.1
• FSP ALM 4.5.1
Packet Edge Cloud Product Support

• FSP 150 XG400 R19.5.1, R19.6.1, R19.7.1
• FSP 150 XG108/XJ128 R13.1.1
• FSP 150 GE104 R13.1.1
• FSP 150 GE100Pro/GO100Pro R13.1.1

• OSA 5330/40 R11.1.1
• OSA 542x/12 R11.1.1

• Support FSP 3000AC R21.1.1
• TAPI - Support for port parameter specification during connectivity service
provisioning
• TAPI – Report control plane state information per node
• TAPI - Support for updating Connectivity Service, Connection names, Connectivity
Service customer/folder and Connection Managed State
• Detection and display of loops in Network Element routing configuration

• Service name inheritance from top level connection for track services
Ensemble Sync Director

• REST NBI support for Inventory/Fault management for OSA5422/5412
• Support FSP150 XG400 Release 19.x
Ensemble Fiber Director

• Integration of Fiber Editor R13.3.1
• Shorten email event table
• Fiber alarm pinpoint and alarm altitude group color coding on geographical maps
General Features
31
• Security – Delay future logins after failed attempts

• Populate ELS service name and IP address
• Support software download for FSP 150 XG400 devices
• Security upgrade of the log4j library to 2.17.1
Version: 1.1
ENC R13.2.2 is a maintenance release that provides defect fixes in key areas of the system.
It also addresses the log4j security vulnerabilities, CVE-2021-44228 and CVE-2021-45046
by upgrading the log4j library to version 2.16.0.
Support is provided for ELS R3.2.2 which has also been updated to address the log4j
security vulnerabilities.
ENC R13.2.1 is a minor release that provides support for WDM, and Sync product devices. It
also provides new features and enhancements to existing features.
WDM Product Support

• FSP 3000AC R20.4.1
• FSP 3000C R3.4.1

• OSA 540x R11.5.1

• FSP3000C Network Media Channel Provisioning Support
• Service name inherited by the top level connection
• Support for service provisioning in mixed filter / splitter configurations

• Intermediate Nodes Support

• GNSS Assurance - show CNO of selected satellite(s) over time on chart view
• GNSS Assurance - Per Constellation Analysis
• GNSS Assurance - option to customize default values of GNSS Health test criteria
• GNSS Assurance support for 3rd parties - replace "CLI Script" with "Custom GNSS
Script"
• Integrate the CMSW 3.0.3B03(Element Manager for OSA3350 Cesium Clock)

• Integration of SNMPv3 credentials for ALM connections/discovery
• Email Notification for Fiber Faults
General Features
• Software Download Support for FSP 3000C
• LDAP Support for "isMemberOf" attribute
• Keystore Password Encryption Enhancements
• Support ELS R3.2.1
• Support Certificate Property in ENC Client
• Events filtering on the NBI(separate configuration for SNMP and CSV)
• Enhance scope of forced parameter use for client settings
Pro-Vision Features
32
• Support for Config Changed Trap field for XG300 R20.2.x for NSO integration.
• Support for Ethernet Backup/Restore for XG300 PV Client.
• Support for performing in-service remote ping tests on an XG304u service
Version:
8.5 1.1
Enhancements to Version 13.1.2
ENC R13.1.2 is a major release and the first GA-release of the R13.x series that provides
support for WDM, Ethernet, and Sync product devices. It also provides new features and
enhancements to existing features.
WDM Product Support

• FSP 3000AC R20.3.1
• FSP 3000C R3.3.1
• FSP ALM R4.1.1/3
Ethernet Product Support

• FSP 150GxPro R11.6.2
• FSP 150XGPro R11.6.1 and R12.1.1(Remote G.Metro Plug in Inventory)
• FSP XG108 R12.1.1
• FSP 150CC-GE/XG 12.1.1
• FSP 150 XG300 R20.1.1
• FSP 150 XG400 R19.2.1

• OSA 54x2 R10.6.1

• Support for FSP 3000AC R20.3.1
• OTN Multi-Layer Link Support
• Provisioning Support for OTN Connections in Cascade Scenarios
• Support for Teraflex Provisioning with 50/100 GHz Channels
• TAPI Support for Detailed Connection Inventory
• Protected WDM and OTN Services via CPc
• Lambda Co-routing Support
• High Availability for CPc

• Single Ended Service Support
• FSP XG400 LAG support
• ERP Track Service Support for FSP XG400

• Support for OSA 54x2 R10.6.1
• GNSS Assurance Support for OSA 54x2 R10.6.1
• PTP Assurance Enhancements

• FSP ALM Discovery
General Features
• Modify AMP Client via MTOSI Using Create/Delete Operations
• Support AutoTune via MTOSI for FSP 150 XG120Pro-SH R12.1.1
• Support SSO for FSP ALM
• Country of Origin Enhancements
• Authentication and Authorization of ActiveMQ Notification Service
• Prevention of Deserialization Attacks
33
• Native Client Installation Option

• Separate Event NBI Filter for SNMP and CSV
• Port Alias Information for FSP ALM Email Notification
• Single Sign On Configuration per Device Type
• MTOSI Support for Dedicated F7 Modules
• SSH Path Setting in Properties File for CLI
Version: 1.1 Analysis Table for FSP ALM Email Notification
• No Fault
• Health Center
• License Mismatch Alarm
• License Reporting Improvements
• New ENC Client Theme Including Breadcrumb Trail Navigation
Pro-Vision Features
ENC R13.1.1 is a major release that has not reached GA and that provides support for WDM
and Ethernet product devices. It also provides new features and enhancements to existing
features.
WDM Product Support

• FSP ALM R4.1.1/3

• FSP 150GxPro/XGPro R11.6.2
• FSP 150CC-GE/XG 12.1.1
• FSP XG400 R19.2.1

• FSP XG400 LAG support

• FSP ALM Discovery
• Ability to remove reference to Fiber Director server
General Features
• Modify AMP Client via MTOSI Using Create/Delete Operations
• Support AutoTune via MTOSI for FSP 150 XG120Pro-SH R12.1.1
• Separate Event NBI Filter for SNMP and CSV
• Port Alias Information for FSP ALM Email Notification
• MTOSI Support for Dedicated F7 Modules
• SSH Path Setting in Properties File for CLI
• No Fault Analysis Table for FSP ALM Email Notification
• Health Center
• License Mismatch Alarm
• New ENC Client Theme Including Breadcrumb Trail Navigation
Pro-Vision Features
34
ENC R12.4.2 is a maintenance release that provides support for Ethernet product devices. It
also provides defect fixes in key areas of the system.
Version:
Ethernet 1.1 Support
Product
• FSP150 Z4806V2 R20.5.1
Pro-Vision Features
• Pro-Vision supports version 20.5.1 of Z4806V2 Ensemble Activator
ENC R12.4.1 is a minor release that provides support for WDM, Ethernet, and Sync product
devices. It also provides new features and enhancements to existing features.
WDM Product Support

• FSP 3000AC R20.2.1
• FSP 3000C R3.2.1

• FSP150 Z4806 R20.1.1

General Features
• Support Different Passwords for the Key and Keystore
Pro-Vision Features
• Pro-Vision supports version 20.1.1 of Z4806 Ensemble Activator
• Improved Z4806 Ensemble Activator support on the Z4806 Service End Points Flows
tab
ENC R12.3.1 is a minor release that provides support for WDM, Ethernet, and Sync product
devices. It also provides new features and enhancements to existing features.
WDM Product Support

• FSP 3000AC R20.1.1
• FSP 3000C R3.2.0
• FAS ALM R3.4.1

• FSP150 XG480 R19.1.2

• OSA 3350 R4.1.1

• Support for Node and Service Reconfiguration
35

• Support for FSP150 XG480 R19.1.2

• Support GNSS Assurance for 3rd Party Devices
Version: 1.1 Reactive Automatic Actions for GNSS Assurance
• Support

• Full Passive Environment Sensor(PES) Support
General Features
• Properties File Upgrade Handling
• Support FSP 3000AC File Transfer via SCP+key
• Support for FSP 3000C Reports
• Support Backup/Restore for FSP 3000C
• Support Different Passwords for the Key and Keystore
• Removal of the Restrictions on the Length of the Post Login Dialog Message
• SNMP Security Extensions
• Version Check During Upgrade and Activation
Pro-Vision Features
• Support for Maintenance Association Name and Maintenance Association Name Type
in OAM Configuration when adding a service
• Pro-Vision NetConf is now compatible with “ssh-secured-ciphers” mode on the
OptiSwitch/XG300 family
• Improved performance of the Pro-Vision device status polling mechanism
• Porting of PC SOAP API definitions to REST API
• XG300 and OS9244 Support for Flood Limiting
• Support for Zero Touch Automation APIs
ENC R12.2.2 is a maintenance release based on R12.2.1 which provides defect fixes in key
areas of the system.
The Ensemble Controller version 12.2.1 is a minor release that provides support for multiple
WDM and Ethernet products. It also provides new features and enhancements to existing
features.
WDM Support
• Support for FSP 3000C R3.1.6
Ethernet Support
• Support for HN400/4000 R15.1.3/4
• Support for FSP150CC-GE/XG R11.2.1

• Support Filtering of Service Types by Layer Protocol
• Support Handover Provision Services
36
• Persistent Bookmarks for Services

• Service Types
o E-Line EPL/EVPL
Version:o1.1E-Access EPL/EVPL
o Transit E-Line EPL/EVPL
o No support for intermediate nodes or path computation
• OAM Capabilities
o CFM
▪ Provisioning
▪ Connectivity Monitoring
• SAT Capabilities
o Y.1564
▪ Activation of pre-provisioned test
▪ Birth Certificate Report
• Device Support
o FSP 150CC GE/XG
o FSP 150 GEPro/GOPro
o FSP 150 XGPro
• Access and Network side LAGs

• Support for OSA542x/30/40 R10.5.1/10.5.2
• PTP Assurance GUI for TE/TIE Test Results Display and Comparison
• Support Secure GNSS Based on Two Receivers on OSA540x for Spoofing/Jamming
Detection
General Features
• SNMP Profiles
• Report Impacted Connection in Fiber Alarm via SNMP NBI
• Support RHEL 8
• Set Event Severity for System Alarms
• Filter Alarms Sent via NBI Based on Severity
• Disk Space Control
• LDAP Authentication and Authorization
Pro-Vision Features
• Support for LDAP Authentication and Authorization
• Enhancements to the Pro-Vision GUI to support the Ensemble Network Controller
• Support for FSP 150 XG30x R19.6.1
The Ensemble Controller version 12.1.1 is a major release that provides support for multiple
WDM and Ethernet products. It also provides new features and enhancements to existing
features.
WDM Support
• FSP 3000AC R19.1.2
• FSP 3000AC R19.2.1
• Enhancements to Software Download for FSP 3000AC
• FSP 3000 ALM R3.2.2
37
• FSP 3000 ALM R3.3.1

• Direct Cut-through to Entities on the FSP 3000AC NED
Ethernet Support
• FSP 150 XG100Pro R11.5
Version:
• ADVA 1.1
XG480 R18.5
• FSP 150 GEPro/GOPro R11.5
• MTOSI – EAD Automated Configuration
• MTOSI – EAD Next Generation, including FSP 150-XG120Pro-SH, GE102ProH, and
GO102ProSM
• Support Security Feature for FSP 150CC-GE/XG R11.1

• Support path exploration with OF400 and OF400+ in CrossConnect mode
• Consolidation of Servers: Customers and Services
• Renaming of Service Objects
• Convert Explored Trails to Provisioned

• OSA540X R10.5
• PTP Remote Slaves/Clients Connection Monitoring
General Features
• Enhancements to Default Positioning of New NEs on the Map
• Embedded License Server(ELS) Based Licensing
• Streaming Replication High Availability
• License Server Supervision for 2 servers
• Restrict the Number of Concurrent User Sessions per User Group
Pro-Vision Features
• Improved FSP150 XG304u LTE Module support using MOS 19.5.1
• Improved IP Address/Mask field in Zero Touch Image Upgrade Window to support
Classless Inter-Domain Routing (CIDR)
• Support for MOS release 19.5.1 on Supported XG304 and XG308 Devices
38
9 Fixes in Historical Releases
These tables list defects fixed in R13.3.2

Version: 1.1 In ENC R13.2.2, the user documentation did not reflect the
FNMD-66778 TS 286747 correct format of the NBI Trap Transmitter Date/Time.
In ENC R13.3.1, the server was running out of memory due
FNMD-67509 TS 292087 to an error in the PV client.
Packet and Sync Devices

In ENC R13.3.1, PMs on the SOAM Y.1731 entity of the FSP
FNMD-67883 TS 293223 150 XG400 devices were not collected properly.
In ENC R13.3.1, several parameters from the OSA5440
FNMD-68146 TS 293730 device are incorrect.
In ENC R13.3.1, the tooltips for the OSA 5440 chassis view
FNMD-68536 TS 293799 slots are incorrect.

IN ENC R13.1.2, a service containing the PSM40-MROADM
FNMD-66387 TS 287796 modules was discovered incorrectly.
FNMD-66643 In ENC R13.1.2, services appear duplicated after renaming.
TS 290360 In ENC R13.1.2, protected services may not have been
FNMD-67017 TS 295523 displayed properly even after re-explore.
In ENC R13.1.2, services are not displayed properly after
FNMD-67914 TS 284696 reconfiguring from 100G to 200G.
In ENC R13.2.1, it was not possible for some discovered
FNMD-68850 TS 292522 services to be set to managed.
In ENC R13.1.2, link deletion was not possible due to
FNMD-68978 TS 294446 associated services.
In ENC R13.1.2, OPR-OPT is missing for entities with UNO
FNMD-69769 TS 294263 interconnections.
FNMD-70882 TS 294706 10G service discovered with missing layers and entities.
In ENC R13.2.2, the backup server in a high availability
FNMD-71276 TS 295425 configuration was not syncing with the CPc.
FNMD-71294 TS 298981 The node page of the service wizard was occasionally empty.
In ENC R13.3.1, the CPc HA Synchronization process hangs
FNMD-71582 after changing the db password.

In ENC R13.3.1, the validation of VLAN members for
FNMD-67561 intermediate nodes was incorrect.

39
For large networks, the "Fix DB Inconsistency" process may

not finish after several hours. It is recommended to restart
FNMD-47968 From LOL the ENC server is this happens.
The RHEL 8 package manager does not accept spaces in the
path name. Until this issue is resolved, users should avoid
FNMD-51244 From LOL installing ENC in directory paths containing spaces.
Version: 1.1 In ENC R13.1.2, the SNMP Forwarder held port 2545 open
FNMD-63352 TS 279877 which presented a possible security risk.
After upgrading to ENC R13.1.2, the saved filter from the
FNMD-63453 TS 278464 previous release did not work.
In ENC R13.1.2 the NE Master Profile was downloaded but
FNMD-63815 TS 280962 not activated.
After successfully updating the software on an FSP 3000AC, if
the user starts to update the firmware, there may be a
warning that the user is about to update the firmware
FNMD-63850 From LOL without first updating the software. This warning is incorrect.
In ENC R13.1.2 it was not possible to permanently display
FNMD-63911 TS 281093 SSO to devices.
In ENC R12.4.1 master profiles did not display names
FNMD-63961 TS 281605 properly.
In ENC R12.4.1, the Fiber Assurance Manager was causing
FNMD-64088 TS 281605 the database size to increase exponentially.
In ENC R13.1.2, the client froze after the shelf view was
FNMD-64147 TS 282868 changed.
In ENC R13.1.2 sorting was not possible in the Manage NE
FNMD-64371 TS 283418 Software Versions tab.
In ENC R13.2.1, sorting of emails by ID in the Ensemble
FNMD-64607 TS 283826 Fiber Director was string based and not integer based.
In ENC R13.1.2 the Fingerprint and Fault Analysis displayed
FNMD-64840 TS 282358 the wrong time stamp in the Fiber Assurance tab.
In ENC 13.2.1, the backup ELS server was showing the same
FNMD-64964 TS 284295 device ID as the primary server.
In ENC R13.2.1, the SNMP Profiles tab showed the incorrect
software version for FSP ALM devices after they had been
FNMD-65085 TS 284825 upgraded.
FNMD-65286 TS 285633 In ENC R13.1.2 a planned node showed a mismatch alarm.
In ENC R13.1.2, the Linux client froze after a transition from
FNMD-65302 TS 283265 a master server to the slave server.
In ENC R13.2.1, after running the changeuser script, some
FNMD-65132 files were left with unsecure permissions.
After upgrading from ENC R12.3.1 to R13.2.1 errors were
FNMD-65209 seen in the mediation log.
In FSP NM R10.3.3, the Event list contained empty rows in
FNMD-65497 TS 285914 the table and appeared to flicker.
In ENC R13.2.1, the BLSU alarm did not clear after restarting
FNMD-65691 the secondary ELS server.
In ENC R12.4.2, ENC was not refreshing licenses correctly
FNMD-65959 while configured for Streaming HA.
In ENC R13.1.2, the REST credentials were not being updated
FNMD-66175 TS 281220 in the backup tab.
The 13.2.1 ENC Administrator Manual needed a correction
FNMD-66356 TS 289711 regarding the elsechangeuser.sh script.
The 13.2.1 ENC Administrator Manual did not include Docker
FNMD-66589 TS 290025 v7.9 support.
Optical Devices
40
PM collection and display from ENC is not supported for
FNMD-59184 From LOL device FSP 3000C R3.3.1
In ENC R13.1.2 the entity alias was not displayed in the
FNMD-64554 TS 283620 entity alias column for FSP 3000C devices.
Version: 1.1
Packet and Sync Devices
If the Module Type and Serial Number fields for the PSU
module of the FSP XG400 device are not populated, the
FNMD-63428 From LOL Installation Status field should be ignored.
BW Director is not presenting CIR/EIR values for
Active/Standby and Load Sharing LAG between XG400 and
FNMD-63566 From LOL XG100.
In ENC R13.2.1 the HN4000 devices were causing numerous
FNMD-65126 errors in the mediation log related to traps.

In ENC R12.2.2, an OpenFab service cascaded with a
QuadFlex module and single channel OPPM protection did not
FNMD-55982 TS 250071 show all of the layers.
In ENC R11.1.3, the oper state was not down after the "No
FNMD-58361 TS 258181 Authentication Key" alarm was raised.
In ENC R12.4.1, the oper state was displayed as a ? on a
FNMD-60147 TS 267117 discovered external channel service.
In ENC R12.4.1, the SERV-N-AFFECTED alarm was re-raised
FNMD-61186 with a different ID after status polling.
TS
225959, In ENC R13.1.2, services were not be shows from the shelf
FNMD-62807 TS 288740 view for MA-B5LT modules.
In ENC R13.1.2 service modification did not work for certain
FNMD-63271 TS 279761 services.
In ENC R13.1.2 1000Base T services were note displayed in
FNMD-63345 TS 279050 the Overview tab.
In ENC R13.1.2, different users with identical permissions
FNMD-63402 TS 280157 were seeing different numbers of services.
In ENC R13.1.2 the oper state of an empty Unassigned folder
FNMD-64152 TS 280248 was red.
In ENC R13.1.2, service exploration failed for a 100GB
FNMD-64174 TS 282909 service on an OpenFab module.
In ENC R13.1.2 the service wizard used incorrect VCHs, ODU-
FNMD-64726 TS 283890 ID and time slot if a port was already created on the device.
In ENC R13.2.1, the server would not start because NEs had
FNMD-65250 TS 283478 been deleted without deleting the related services.
In ENC R13.2.1 the user was unable to change the admin
FNMD-65347 TS 285783 state to maintenance for certain services.
In ENC R13.21 the user documentation needed to be updated
to indicate the track services are not supported for FSP
FNMD-65494 TS 286453 3000C devices.
In ENC R13.1.2, renaming of protected services was not
FNMD-65766 TS 287298 working.
In ENC R13.1.2, a duplicated service appeared after running
FixDBInconsistencies when the facility type was OTU2-FSR on
FNMD-65778 TS 275194 a 10TCC100G module
41

In ENC R13.2.1, the user was unable to select an access
FNMD-64816 TS 283478 flowpoint as part of an E-Line track service.
Version: 1.1 In ENC R13.2.1 it was not possible to create ERP on FSP 150
FNMD-65828 TS 278839 XG480 devices.
This table lists defects fixed in R13.2.2

Changing the admin state of a data service on the 10TCE
module may disable the admin state of the network port
FNMD-65083 TS284819 affecting traffic on other services using that port.

WDM Product
In ENC R12.4.1, it is not possible to connect to FSP 3000C
devices unless the NeTlsCertificateHandling property is set
correctly in fnm.properties. Changing this property requires a
FNMD-58884 server restart.
In ENC R11.2.3, Ethernet PMs were not being collected
FNMD-62284 TS274718 properly for the 10TCC module.
In ENC R13.1.2, the FSP ALM CLI client cannot be opened
FNMD-62798 with Secure Shell Configuration.
Ethernet Product
In ENC R12.3.1, the "Switch Election no Change" alarm on
FNMD-60577 the HN4000 device had an unknown severity.

In ENC R11.1.3, large service reports take a long time to
FNMD-53761 TS235698 create.
In ENC R12.2.1, the user text field for some network
FNMD-56205 elements was used in the name of the services.
TS245828 In ENC R11.1.3, it was not possible to manage encryption
FNMD-56282 -9 between nested ODSs.
Creation of an OT200 NfC on the MA-B5LT module may
appear to timeout during tunnel creation. ENC then displays a
DCN alarm. The service is created properly on the device.
Executing an inventory polling on the device refreshes the
FNMD-59481 From LOL display to the correct status.
In ENC R12.4.1, selecting "Make Free of Traffic" may fail
FNMD-59646 TS264581 when selecting multiple service types at the same time.
In ENC R12.3.1, the fiber break alarm did not appear for
FNMD-61145 OPPM services when an EDFA is present.
42
When creating a provision service on the 10TCC-PCTN-

4GUS+10G-x#D module the default value of the "Laser Off
Delay" parameter is Enabled and this is incorrect and using
this value may cause service creation to fail. Manually set
this parameter to Disable on the facility page of the service
FNMD-61278 From LOL wizard for proper service creation.
Version: 1.1 In order to rename an External Channel Service (ECH
Service), the user will have to first change the state of the
service to "discovered", change the name and change the
FNMD-61491 From LOL service back to "managed" state.
In ENC R13.1.2 the refresh button in the Optical Trace tab
FNMD-61530 TS274595 does not work properly.
FNMD-61673 TS266409 In ENC R12.4.1, ODS name is set to a default value.
In ENC R13.1.2, amplifiers were set to disabled when some
FNMD-61816 TS273551 Quadflex services were set to down.
In ENC R12.2.2, an error occurred when attempting to delete
FNMD-62566 TS276371 a CCCP track service.
After an upgrade to ENC R13.1.2, duplicated services were
FNMD-62823 TS277177 found.
In ENC R13.1.2, the user documentation did not cover HA for
FNMD-62872 TS27667 CPc.
In ENC R13.1.2, the 48CSM was not available for selection in
FNMD-62914 TS277603 an ECH Track service creation.
In ENC R13.1.2, it was not possible to add intermediate
FNMD-62927 TS277432 modules for track services.
Ensemble Packet Director and Ethernet Service Manager

In ENC R12.4.1, the action description is not completely
FNMD-60687 TS269068 visible in the Transfer Configuration File tab.
In ENC R12.4.1, the ERP sub-ring is not available for
FNMD-61654 TS272776 selection in the service wizard.
In ENC R11.132, it was not possible to create an ERP Sub-
FNMD-63192 TS278839 ring service on an FSP XG480 device.
Ensemble Sync Manager

In ENC R13.1.2, the Sync Assurance ports were not listed in
FNMD-63046 the Administrator Manual.
In ENC R12.4.1, scroll bars may appear in the Optical Track
FNMD-60797 TS269022 Map when they are unnecessary.
In ENC R12.3.1, ENC did not support isMemberOf in LDAP
FNMD-60939 TS266556 configurations.
In ENC R11.1.3 the table layout will not get saved even if the
FNMD-61012 TS269857 "save as" button is used if the client crashes.
In ENC R12.3.1, the support info window could not be
FNMD-61275 accessed when the client crashes.
In ENC R12.2.2, there were performance issues that may
FNMD-61328 TS268288 cause the server to crash.
In ENC R13.1.2, in an HA configuration, it is not possible to
re-connect to the primary server after it has gone down and
FNMD-61354 comes back up as the slave server.
43
In ENC R12.4.1, the ENC client stopped responding when

FNMD-61927 TS273237 trying to copy objects.
In ENC R13.1.2, SSO via Adhoc user prevents NED access to
FNMD-62543 the NE.
In ENC R13.1.2, the ENC client was occasionally observed to
FNMD-62976 TS276733 crash at the “Activating UI” phase of initialization.
Version: 1.1
Changes to modules on the HN418 devices are not
automatically reflected in the Modules tab. The workaround is
FNMD-35596 From LOL to select another tab and re-select the modules tab.
FNMD-38601 TS200742 Missing port indication in topology on 8ROADMM80
After Upgrading to ENC 12.3.1 the user cannot create provisioned
FNMD-50960 TS261560 services
Collecting PM values from MLG entities in the FSP3000C
FNMD-51411 From LOL device is currently not implemented.
An adopted CPd service is created with protection goal
desired on the WDM tunnel. This prevents enabling
guaranteed restoration via NFC service modification, because
only unprotected services are supported for guaranteed
restoration.
This can be fixed by setting the protection goal of the WDM

tunnel to unprotected (assuming the service is actually
unprotected) via NED / CRAFT. Then guaranteed restoration
FNMD-55294 From LOL may be configured on the service.
ENC does not display a faulted OMS layer for a QSFP/ER4
FNMD-55603 TS248970 network line
In order to use the ROADM replacement feature, the user
must first manually remove the WCH entities on the FSP
3000 AC device before executing the "Replace ROADM
FNMD-55790 From LOL Configuration" option on ENC.
In ENC R12.2.2, some of the log4j configuration files were
set to the wrong permissions after installation on a Linux
FNMD-55818 server.
A 1GBE spur link configuration can operate using a 2TWCC
module aggregated with a 16TCC or 10TCC module in two
options, with and without provisioned WDM layer service. The
former option does not work without explicit definition of a
fiber map termination (optical line). The workaround is to
create an OL object on the aggregating module via craft or
FNMD-55887 From LOL NED.
Provision service creation involving the ROADM_C80 module
may fail on the first attempt. The workaround is to try to
FNMD-55911 From LOL create the service again.
In ENC R12.2.2, a service with an OF module cascaded with a
QF module and multichannel OPPM protection doesn't
calculate the outage correctly on layers after working line is
FNMD-55938 TS250068 cut.
44
In the cascaded service configuration 2WCC10G/4WCC10G to

10TCC100G, the OTU2 facility type cannot be used due to the
inability to set the OTU termination level. The workaround is
to recreate the client and network port with the appropriate
facility type and termination level from the NED or craft of
the network element after the service has been created. This
Version: 1.1 also requires the deletion and recreation of the WDM cross
FNMD-56107 From LOL connect.
10G/100G service created with MA-B5LT modules result in a
FNMD-56154 TS250937 service display issue
FNMD-56292 TS251315 Notification Manager does not send Email's in ENC 12.2.2
In ENC R12.2.2, when the Fiber Director is disconnected from
ENC, it is not possible to remove a Fiber Director
configuration or delete the group in which a data service has
FNMD-56353 TS251935 been provisioned.
External Channel Service creation for 75/100 Ghz cannot be
created on 16 PSM Passive shelf. Needs to use Network
FNMD-56402 TS252416 Element version 20.3.1
In ENC R12.2.1, when provisioning a CfC on QF cards with
bottom up (NfC created and selected) then the wizard selects
FNMD-56404 TS251275 the OF cards automatically.
FNMD-56407 No messages in the message pane during restoration
In ENC R12.2.2, the client was observed freezing for several
FNMD-56571 TS253056 seconds.
In ENC R12.3.1, the make free of traffic process window was
showing 50% progress while the process had already
FNMD-56729 TS253719 completed.
In ENC R12.2.1, the ENC-NMCL-F7-S license is not working
FNMD-56755 TS251630 properly.
In ENC R11.1.3, the wrong IP address was displayed in the
FNMD-56814 TS252850 NE Backup tab.
In ENC R12.1.2, some services were not shown using the T-
FNMD-56891 TS253434 API interface after rebooting the server.
In ENC R11.2.3, an error message contained the wrong
FNMD-56958 TS254623 service name while attempting to delete a service.
In ENC R11.2.3, no security even was generated while
FNMD-57252 TS256929 deleting an NfC.
In ENC R12.2.1, the client was unable to connect to the
server and a corresponding database exception was seen in
FNMD-57347 TS255407 the logs.
In ENC R11.1.3, the "Reset Counter" operation in the
Encryption Manager was not supported for the 9TCE-AES-G
FNMD-57562 module.
FNMD-57567 TS256754 ENC Server freezes with Database exceptions
In ENC R12.2.1, in the HA configuration, it was not possible
to connect to the secondary server after the primary server
FNMD-57596 TS256754 crashed.
GUI reporting service Admin Status Mismatch after optical
FNMD-58023 TS259271 power equalization when the service is in Maintenance
In ENC R12.3.1, there were some problems with the Sync
FNMD-58224 TS258880 Assurance information updating on a Linux client.
In ENC R12.3.1, software update fails when a DNS hostname
is used for the NE Update configuration as opposed to an IP
FNMD-58483 TS259779 address.
FNMD-59019 TS261540 Services were created with Admin State Maintenance
45
In ENC R12.4.1, when sound is enabled for alarms, the sound

FNMD-59213 TS262908 is always generated regardless of the severity setting.
The upgrade from ENC R12.2.2 to R12.4.1 was failing when
FNMD-59406 TS263718 FSP 150CC-GE206V devices were discovered.
In ENC R12.3.1, the number of satellites shown in the GNSS
Assurance application is inconsistent with the available
Version: 1.1 TS262886
FNMD-59435 receivers and gaps.
The first 10GBE service on the MA-B5LT module must be
FNMD-59507 From LOL created on the first client port.
An OT200 NfC on the MA-B5LT module may appear in the
FNMD-59541 From LOL classic model. Fix DB Inconsistency resolves the problem.
In ENC R12.4.1, it is possible to attempt to create a 10Gbe
service when the OTU4 Nfc is already in use by a 100Gbe
FNMD-59542 From LOL service, but service creation fails.
In ENC R12.4.1, "Go to Tree" in the bookmarks tab was
FNMD-59645 TS265091 replaced by "Go to Item".
ETH10G NfC’s may be displayed in the classic model. Fix DB
FNMD-59751 Inconsistency resolves the problem.
In ENC R12.4.1, Fix DB Inconsistency returned an error when
FNMD-59805 TS265654 CPc was not present.
In ENC R12.4.1, service names were limited to 128
FNMD-59878 characters.
TS266230, In ENC R12.4.1, the performance report and pmDump was
FNMD-59997 TS266232 not generated properly after changing the separator.
In ENC R12.4.1, explore path does not work for flexgrid when
passing through the 5PSM module connected to a 9ROADM-
FNMD-60135 RS module.
In ENC R12.4.1, a VLAN based service failed to provision
FNMD-60136 TS266674 using the Ensemble Packet Director.
In ENC R12.4.1, the Entities tab was empty for some
FNMD-60474 TS268110 services.
In ENC R12.4.1, track service creation failed for the Teraflex
FNMD-60601 TS268789 module.
Copy-Paste operation of Network Elements in the Tree causes issues
FNMD-60699 TS268288 on the server
TS
269231, In ENC R12.4.1, the SNMP profile was missing the NE
FNMD-60892 TS269233 Identifier and SW Version.
In ENC R13.1.1, the SSH path was not being set from
FNMD-60932 fnm.properties.
External Channel Provisioned service cannot be created due
FNMD-61069 TS270343 to a provisioning error
Both Servers in an HA pair crash due to service model
FNMD-61156 TS268288 inconsistency

In ENC R10.2.3, re-exploring a service after a module
FNMD-28932 TS168814 replacement is not working.
The Modules tab is not automatically updated when an SFP is
removed from an FSP 150 XG120ProSH device. The
workaround is to select another tab and re-select the
FNMD-49122 From LOL Modules tab.
In ENC R12.1.1, in the security manager the Application
group indicated that permissions were not allowed for the
FNMD-52252 group even though the sub permissions were allowed.
46
In ENC R11.2.3, the fiber break alarm was not displayed for
FNMD-52451 some links that were down.
The user may see a fiber break indication on multiple trails,
FNMD-52895 From LOL but the main fiber break is only caused by one of them.
When ENC is configured as a standalone(non HA
configuration) and running on a Linux server and the
Version: 1.1 mediation service fails to start, it may get attempt to restart
FNMD-52938 From LOL itself repeatedly.
When changing the configuration of an unprotected explore
service to protected, the user should delete the unprotected
service from the database and then re-explore the service.
The same procedure applies when going from protected to
FNMD-53886 From LOL unprotected.
If an External Channel(ECH) service is created on a filter
module, the client port used in this service may not be
indicated on the module page of the service wizard when
creating a second service. The preferred procedure is to
select the network port first and then select the ECH from the
FNMD-54445 From LOL ECH combo box on the module page.
The network VCH is not automatically put in service for
FNMD-54661 From LOL services using the MicroMux plug on the Quadflex module.
In ENC R12.2.2, the OSA 3350 device alarm list was not
FNMD-55477 aligned with the MIB.
Splitting an intra stitched cascaded configuration service into
FNMD-55667 From LOL two services automatically does not work properly.
In ENC R12.2.2, keystore files had incorrect permissions and
FNMD-55909 were readable by everyone.
Services using the WCC-PCN-100GB module may appear in
the classic service model display. Running Fix DB
Inconsistencies displays the service in the new multi layer
FNMD-56014 From LOL model display.
Client Channel Card Protected services may appear in the old
service model display. Running Fix DB Inconsistencies should
FNMD-56075 From LOL convert the display to the new Mult Layer Model.
When the user creates client facing connection and sets the
initial state to maintenance in the service wizard, it may
result in the underlying network facing connections also being
set to maintenance. The user is advised to create the service
initially as in service and then change the state to
FNMD-56178 From LOL maintenance after creation.
Unprotected provision services passing through the 5PSM and
CCM modules may appear in the old service model display.
Running Fix DB Inconsistencies will return them to the new
FNMD-56234 From LOL multi layer model display.
In ENC R13.1.1, the cryptographic control setting hmac-
FNMD-56237 sha2-512 was introduced for SSH applications.
In ENC R12.3.1, bookmarking a service may duplicate the
FNMD-56508 bookmarks tab if the tab was previously closed.
In ENC 12.3.1, it is not possible to create a service on the
Quadflex module when 16PSM passive is selected on the
FNMD-56637 TS253275 ingress node.
In ENC R11.3.2, the admin state of 200G services may not be
FNMD-56728 TS253337 correct.
In ENC R12.3.1, the ENC client was not working properly with
FNMD-56804 TS253301 Japanese language settings in Windows.
47
In ENC R12.2.2, there is an occasional warning in the log file

that the attribute "name" can’t be added to the
FNMD-57106 MtosiMONotification.
TS254885.
TS254853. In ENC R11.1.3, the ENC client froze and login was not
FNMD-57118 TS254959 possible until after restarting the server.
Version: 1.1 In ENC R12.3.1, the fiber break alarm was not displayed for
FNMD-57282 TS253383 some links that were down.
In ENC R11.2.1, a user with the configurator role does not
FNMD-57367 have permissions to search for links.
In ENC R13.1.1, the engine boot value was added to the
SNMPv3 NBI forwarding as well as the ability to increment
FNMD-57388 this value without restarting the server.
In ENC R12.2.2, the ENC client crashing after entering a
FNMD-57415 password in an SNMP profile using a KeePass application.
In ENC R11.3.2 PM dump files stopped generating
FNMD-57520 TS255738 automatically.
The flexnetls.conf file in the ELS installation had incorrect
FNMD-57633 TS255930 permissions.
The els_cleanlogs script run during the ELS installation had
FNMD-57634 TS255930 an error.
In ENC R12.3.1, the postgres user directory was created in
FNMD-57635 TS255930 the wrong directory.
In ENC R12.3.1, the DUP-PTP-MASTER-SLAVE-IP alarms are
FNMD-58418 TS259498 not cleared.
In ENC R11.1.3, the service inventory report was incomplete
FNMD-58999 TS262058 for large networks.
In ENC R12.4.1, the optical trace map is incorrectly display
OL and MAPB information for services on the MA-B5LT
FNMD-59265 module.
In ENC 12.3.1, there was a spelling mistake in the Neighbor
FNMD-59873 Discovery Detected a Far End Change event.
In ENC R12.4.1, ENC reverts to old fiber link after inserting a
FNMD-59999 TS266233 node in a link.
The user documentation needed to be updated to include
FNMD-60291 information on updating the keystore password.

In ENC R11.2.1, the keystore and key passwords had to be
FNMD-46253 the same.
When creating provisioned Quadflex services with non-default
Setpoint it is likely that equalization would fail due to
equalization starting before port settings are completed. The
workaround would be to issue a subsequent manual re-
FNMD-54109 From LOL equalization of service.
When the user has 2 unprotected services which need to be
stitched together, the re-explore option will not combine the
services into one. The workaround is to set the services to
FNMD-55666 From LOL discovered and then re-explore one of the services.
The automatic reconfiguration of service paths (i.e during
restoration) may not result in the correct path or proper
mismatch indication in ENC. The suggested workaround is to
execute polling of nodes and executing fix database
FNMD-55763 From LOL consistency.
48
In ENC R12.2.2, there was a problem with selecting a service

FNMD-56757 TS253924 in the Make Free of Traffic window.
In ENC R12.3.1, ENC was reporting Fiber Mismatch alarms on
FNMD-56796 TS254004 links incorrectly.
In ENC R12.3.1, some service artifacts remained and the NE
FNMD-56894 TS254338 was deleted.
Version: 1.1 In ENC R12.3.1, 10GB services were appearing in the old
model, while 100GB services were appearing in the new
FNMD-56899 TS254097 model on the MA-B5LT module.
In ENC R12.3.1, the entities tab was empty for external
FNMD-57112 TS254794 channel services.
In ENC R12.3.1, a user with Monitor privileges was allowed to
FNMD-57374 TS255616 edit the Customer, group, service, and service objects.
In ENC R12.3.1, path computation was not displaying all
FNMD-57378 TS255712 potential paths for directionless, colorless service structures.
In ENC R12.3.1, an OTU4 provision service on an
FNMD-57379 TS255721 OpenFabric+ module failed equalization.
In ENC R12.3.1, service modifications were returning an
FNMD-57432 TS255617 SNMP error in certain situations.
In ENC R12.3.1, there was a null pointer exception in the
FNMD-58191 TS259598 logs after running Fix DB Inconsistencies.
In ENC R12.3.1, there was not equalization menu option for
FNMD-58242 TS257790 external WDM services with VECH endpoints.

Performance Monitoring collection may not be available for
FNMD-37198 From LOL the Cryptomux+ module.
In ENC R11.2.1, the ENC client may freeze after a prompt to
FNMD-44325 change the password.
In ENC R11.3.2 Service-related DB inconsistencies were
FNMD-50331 TS225754 found.
In ENC R11.1.3, the NE did not update properly in ENC after
FNMD-50692 reconfiguration.
PMs for FSP 150XG120Pro devices may not be displayed in
FNMD-51034 From LOL the performance tab.
In ENC R11.3.2, the OPT, OPR, and SNR PMs were not
collected for the WCC-PCN-100GB, 10TCE-PCN-16GU+100,
FNMD-51126 and MP-2B4CT modules
In ENC R11.3.2, it was not possible to search for a service
FNMD-52565 TS237287 using the alternate name field.
In ENC R11.2.1, ENC with high availability enabled could not
FNMD-52798 TS234908 be installed in the root folder of a drive (i.e. E:\).
Sorting and Filtering is not support for the life cycle state
FNMD-53031 From LOL column for the services and connections tabs.
In ENC R11.1.3 it is possible to set the OPS to admin state
FNMD-53114 TS244571 "Down"
Deleting a large number of reports at once may cause the
ENC server to crash. It is recommended that no more than
FNMD-53243 From LOL 100 reports be deleted at once.
In ENC R11.1.3, if an attempt to upgrade the software on the
FSP 3000AC device times out, the device will downgrade and
FNMD-53632 TS241581 return to factory settings.
In ENC R12.2.1, clicking in an empty Bookmarks tab and
then switching to another tree will result in an empty display
FNMD-53691 for the other tree as well.
49
In ENC R12.1.1, the service name changes caused by

FNMD-53783 database upgrades were not correct.
In ENC R12.2.1, performing "set to Managed" on a service
FNMD-54015 TS243855 using port C5 on the cryptomux+ module fails.
In ENC R11.3.2, license disconnect alarms were not displayed
FNMD-54063 TS244025 in ENC.
Version: 1.1 In ENC R12.2.1, the version of the Postgres db used with
FNMD-54080 TS244155 ENC allowed XXE.
In ENC R11.1.3, creating a service with a set point of 0.0 on
the MP-2B4CT module will result in a service with a set point
FNMD-54174 TS244274 of 0.5.
In ENC R11.1.3, ENC did not display timestamps for the last
FNMD-54243 TS244866 successful and failed key exchanges.
In ENC R12.2.1, database exceptions were seen when
FNMD-54350 TS245146 creating provision services.
In ENC R12.2.1, the link loss threshold event was not
FNMD-54386 displayed from the network level.
In ENC R12.2.1, the MTOSI command
deactivateAndDeleteFDFr failed when used with an HN4000
FNMD-54426 device.
In ENC R12.1.1, provisioned ECH services could not be
FNMD-54597 TS246087 created between modules of a different type.
In ENC R12.2.2, the property HeapMemoryLimit was not
FNMD-54633 described in the user documentation.
In ENC R12.2.2, provision service creation on the 2WCC10G
FNMD-54705 TS246032 modules may fail.
In ENC R12.2.2, service exploration will fail if an 8CSMU_D_P
FNMD-54734 TS246529 module is in the path of the fiber map.
In ENC R12.2.2, the module page of the service wizard may
not allow new services to be provisioned on the 9TCE10G
FNMD-54751 T246735 module if other services have already been created.
In ENC R12.2.2, protection switching was not available for
FNMD-54858 TS246529 ADM protected track services on OpenFab modules.
In ENC R12.2.2, the operational state of an E-Line service
FNMD-54874 TS246824 was degraded when it should have been normal.
In ENC R11.3.2, changing the value of custom fields from the
FNMD-54940 table view does not work correctly.
In ENC R11.3.2, switching between undiscovered NEs in the
FNMD-54941 network tree causes a slight delay in the GUI.
In ENC R11.2.3, if a network element was pre-provisioned,
FNMD-54942 the overview tab did not show the network element type.
In ENC R12.2.2, crypto manager support for the cryptomux+
FNMD-54977 TS246920 module was not fully supported.
In ENC R12.2.2, some service objects from Ethernet services
FNMD-55004 TS246827 were not displaying the operational status.
In ENC R12.1.1, many Ethernet services were stuck in a
FNMD-55014 TS246493 degraded state even when the underlying entities were ok.
In ENC R12.2.2 the duplicate IP alarm could not be
FNMD-55208 supressed.
In ENC R11.2.1, ENC stopped processing MTOSI requests and
FNMD-55375 required a server restart.
The operational status of a service displayed in the
FNMD-55380 TS248479 Bookmarks tab is not being updated.
FNMD-55382 TS248450 Parenthesis were not supported in the search feature.
In ENC R12.2.1, the http proxy command redirected requests
FNMD-55458 to internal ports.
50
In ENC R12.2.1, the ENC manual describes port 33029 as

FNMD-55460 being required to be opened.
In ENC R12.2.1, the http proxy server header contained too
FNMD-55464 much information.
In ENC R12.2.2, the fiber break alarm may not clear
Version: 1.1
FNMD-55585 In ENC R12.2.1 keystore files were human readable.
FNMD-55616 In ENC R12.2.1, the JMS was listening on multiple ports.
MP Flow should be excluded from the service operational
FNMD-55699 state computation for rings and subrings.
In ENC R11.2.1, the number of files allowed to be open
FNMD-55770 exceeds the limit set forth in limits.conf.
In ENC R11.3.2, there was an error with continuous discovery
FNMD-55793 on the backup server.
In ENC R12.2.1, the admin manual was missing references to
running ENC services under a non-root account and disabling
FNMD-55825 JMX.
FNMD-55851 TS248450 Ethernet track services were not found using the search tool.
In ENC R12.2.2, the migrate ENC tool was throwing an
FNMD-55955 exception.
In ENC R12.2.1, some of the scripts needed to be updated to
FNMD-56155 TS250315 reference jre64 as opposed to jre.

After the upgrade from ENC R10.3.3 to R11.3.2 service
FNMD-50107 TS221191 related db inconsistencies were found which were not fixed
FNMD-53665 TS242660 by the “Fix DB Inconsistencies” tool.
In ENC R12.1.1, the Centralized Control Plane manager
FNMD-53238 TS239578 opens on port 8080 in the Linux GUI.

The "Force Key Exchange" button in the Encryption Manager
may cause the Key Exchange Status to get stuck in an In
FNMD-27574 From LOL Progress state. The workaround is to hit the Refresh button.
In ENC R11.1.3, the optical trace displayed incorrect labels
FNMD-41802 TS205565 for the ports on the EDFA and DCM modules.
In ENC R11.1.3, some services in the new model reverted to
FNMD-44705 the old model.
In ENC R10.4.2, an event flood of "Num Tracking Satellites"
FNMD-45342 TS207677 events was seen.
In ENC R11.2.2, some of the service mismatch alarms were
FNMD-45597 not produced in ENC.
In ENC R11.2.1, the documentation did not mention that the
activemq process opens a random port to communicate with
FNMD-46373 clients that are already open.
In ENC R11.1.3, the inventory report for the GE206V
FNMD-46938 TS186672 combines the HW and serial number values into one column.
TS184436,
TS185293, In ENC R11.1.3, the inventory report for GE206V does not
FNMD-47090 TS186647 always show the correct value in the clock field.
In ENC R11.1.3, entities are not shown in the entities tab
FNMD-47344 TS200724 when selecting an NE in the layer browser.
51
In ENC R11.1.3, the encryption manager shows the pairing

FNMD-47531 TS212609 state as incomplete even though pairing was successful.
In ENC R11.1.3, the SFP module type on the GE206V device
FNMD-47534 TS184436 was not displayed properly
In ENC R11.3.1, service provisioning failed on the even ports
FNMD-47934 TS219927 of the OpenFabric+ module.
Version: 1.1 In ENC R11.1.3, some of the OCH layers were in an unknown
FNMD-47991 TS220838 state.
In ENC R11.1.3, the OCH layer may not be displayed
FNMD-48013 properly in the graph.
In ENC R11.3.2, intermediate entities may be removed from
FNMD-49163 TS221666 a track service after a service name change.
In ENC R11.3.2, the fix db inconsistency tool may cause
FNMD-49540 TS223202 service layers to appear and disappear during execution.
In ENC R11.1.3, the sync topology view was not displayed
FNMD-49589 TS224194 correctly.
In ENC R11.3.1 the db inconsistencies displayed several
FNMD-49865 TS222586 service view object inconsistency errors.
When upgrading from a prior ENC release, the Active PTP RS
Usage and PTP RS Connectivity tabs may be empty. The
FNMD-49977 From LOL workaround is to refresh the sync topology.
When restoring databases including the NI controller, if the
credentials have changed since the databases were created,
the NI controller database restoration will fail. The
workaround is to set the communication credentials to the NI
FNMD-49999 From LOL controller to the previous user and password.
In ENC R12.1.1, the SERV-N-AFFECTED alarm is not
FNMD-50021 associated with the service.
TS201865, In ENC R10.5.1, an invalid ne_id error was seen in the output
FNMD-50030 TS225854 of the printDBInconsistencies script.
In ENC R11.3.1, the equalize menu option was not available
FNMD-50203 TS222586 for path protected services.
Native discovery of the XG300 devices may not function
properly in ENC R12.1.1. The workaround is to use the Pro-
FNMD-50334 From LOL Vision client.
In ENC R11.3.2, ENC does not collect utilization PM data for
FNMD-50396 TS226120 the MP-2B4CT module.
In ENC R12.1.1, the DATA-SERV-AS-DOWN alarm did not
FNMD-50580 TS227727 appear for services in the down state.
TS213162, In ENC R11.1.3, services on the G1550 and C1550 channel
FNMD-50583 TS239373 could not be re-explored.
In ENC R11.1.3, services associated with the MA-B5LT
FNMD-50804 TS225959 module were not shown in the shelves tab.
In ENC R11.2.1 error messages in the security manager were
FNMD-50849 appearing prematurely
In ENC R12.1.1, the equalization menu option was not
FNMD-51005 TS230823 available for some layers.
In ENC R10.5.1, negative nelogindexes were seen which
FNMD-51014 TS230322 caused event handling to stop.
TS233462, In ENC R11.1.3, changing the name of a service was also
FNMD-51585 TS234304 seen to change the admin state of the entities in the service.
in ENC R12.1.1, the obfuscate_ssl_password script threw an
FNMD-51622 exception.
In ENC R11.2.1, the documentation regarding the shared
FNMD-51702 secret length was incorrect.
TS- In ENC R12.1.1, some protected services are displayed as
FNMD-51876 235745 unprotected.
52
In ENC R11.3.2, the client was seen to occasionally freeze

FNMD-52177 TS224312 when ENC was configured for HA.
In ENC R11.2.1, the user documentation was missing some
information regarding software update for the OSA5430/40
FNMD-52194 TS236048 devices.
In ENC R11.3.2, user login fails if it does not have
FNMD-52376 MessageViewer permissions.
In ENC R12.1.1, Fixing the db inconsistency, "New service
FNMD-52833 TS237759 object missing for ..." produced and error and was not fixed.
In ENC R12.1.1, the MTOSI command
deletePrecisionTimeProtocolFlowPoint on the NET port of the
FNMD-52850 GO102Pro-SM device fails.
In ENC R12.1.1, the admin manual needed clarification on
FNMD-53134 using high availability with ELS.
In ENC R12.1.1, single signon was not working for the
FNMD-53188 XG120Pro-SH device.

In ENC R10.2.3, the columns and headers in the tab pane
FNMD-34319 TS187006 may not be aligned properly.
In ENC R11.1.1, the service inventory report generation does
FNMD-36893 not complete.
In FSP NM R10.5.1, 10G services with RSM may not display
FNMD-40859 In ENC R11.1.1, so PMs did not appear in the PM report.
In ENC R11.1.3, 10GBE services ending on an "unknown
object"(UNO) are missing the ODU2e layer in the layer
browser but have an additional OTU2 layer which should not
FNMD-41287 TS204474 be present.
In ENC R11.1.3, some of the OMS and ODS layers appeared
FNMD-41791 TS205567 in the old service model.
In ENC R11.1.3, the OPT/OPR values of a channelcard client
or network interface are displayed in the sum power overview
FNMD-41820 TS205565 instead of the OP channel display.
In ENC R11.1.1, the column containing the service name was
FNMD-41896 labeled "Resource Name" in several tables.
The status change start time in the faulted services tab may
FNMD-44363 From LOL display the incorrect time for some ethernet services.
In ENC R11.1.3, some service layers below the ODU4 were
not displayed and the ODU4 was seen to have an incorrect
FNMD-45247 TS207427 oper state.
In ENC R11.1.3, the Associated Services tab would
FNMD-45254 occasionally appear to flicker when updating.
FSP 3000AC devices cannot be discovered by Ensemble
FNMD-45326 From LOL Controller using IPv6.
In ENC R11.2.2, the user documentation needed to clarify the
FNMD-45499 TS209001 meaning of Mixed mode for file transfers.
In ENC R11.2.2, it was not possible to create a second
service on the C3+N3 ports of the 9TCE module in
FNMD-45565 TS209858 transponder mode.
In ENC R11.2.3, there were problems deleting ECH services
which were configured using 16PSM4 modules as and
FNMD-46100 TS211397 add/drop.
In ENC R11.2.1, the user was able to enable HA when the
FNMD-46227 master and slaver servers were running 2 different versions.
53
In ENC R11.2.1, NE backup fails if the sub container contains

FNMD-46332 TS212286 special characters.
FNMD-46418 TS212519 In ENC R11.2.1, the client was observed to have frozen.
In ENC R11.2.1, the server had to be restarted several times
FNMD-46422 to remain up due to a configuration file problem
Version: 1.1 In ENC R11.2.1, the ENC server running on a Linux machine
may display an error claiming "Permission Denied" for the
FNMD-46454 fnmserver.pid file.
When upgrading Ensemble Controller with MTOSI enabled,
errors about not being able to find NEs may appear in the
FNMD-46523 From LOL mediation log.
In ENC R11.2.1, the value of the
com.adva.fnm.security.CLI_WINDOWS property set in
fnm.properties is not be set in the Secure Shell (SSH) Setting
FNMD-46531 in the User Settings dialog.
In ENC R11.1.3, service exploration fails for the open fabric
FNMD-46533 TS212496 module configured in cross connect mode.
When operating Ensemble Controller in multi-server mode,
the user is able to search for services on multiple servers, but
selecting "go to properties" on a service from a server other
than the one currently selected will not display the service
FNMD-46535 From LOL properties.
In ENC R11.2.1, the security manager windows did not
FNMD-46700 display a reference to the server it was associated with.
In ENC R11.2.1, if network element has not completed
discovery and the user changes the SNMP settings, they may
FNMD-46714 TS213945 revert back to the global settings.
In ENC R11.2.2, the SERVICE-M-CP-AS mismatch alarm may
FNMD-46761 TS212712 not clear after the ROADM VCH has been restored.
In ENC R11.2.1 the script used to obfuscate the ssl password
FNMD-46804 produced an error.
In ENC R11.2.1, the changeUser script was not fully
documented as well as some other configuration issues with
FNMD-46869 Linux.
In ENC R11.2.1, the oper state for ERP Protected Services
FNMD-46874 TS215845 may not be calculated properly.
In ENC R10.4.2, the scripts referenced certificates and
FNMD-46903 keystores in multiple locations.
In ENC R11.2.1, "Switch to working traffic" is not working
In ENC R11.3.2 the fnm property
FNMD-47290 CP_POLICY_PROXY_NODES_IP was not documented properly.
TS218346, In ENC R11.1.3, setting a service to managed state may not
FNMD-47340 TS218077 work properly.
In ENC R11.3.1, some of the PM data for Ethernet services
FNMD-47408 TS213477 was missing from the csv reports.
In ENC R11.2.3, the MAPB-OSC-C alarm displayed the wrong
FNMD-47746 module type.
In FSP NM R10.3.1, the Reports tab did not show newly
FNMD-47759 TS 219910 generated reports.
FNMD-47790 TS216894 In ENC R11.2.3, the NI Manager could not user RADUIS.
In ENC R11.3.1, the alias of the ch port of MA-B5LT is not
FNMD-47886 displayed properly when the module is used in a service.
In ENC R11.3.1, service provisioning failed for a 100G service
FNMD-47935 TS219920 on the MA-B5LT module.
54
In ENC R11.2.3, the equipment parameter page of the

service wizard is not automatically selecting the correct
FNMD-47969 TS221047 parameters for an OTU4 service on the MA-B5LT module.
In ENC R11.3.1, the ordering of the nodes in the service
FNMD-47971 TS221040 graph was seen to be incorrect for a MA-B5LT service.
In ENC R11.2.3, newly discovered nodes were automatically
FNMD-47988 added to NI Manager after changing the SysIP.
In ENC R11.3.1, the alias of the I1-N port 96CSM module was
FNMD-48025 not populated properly.
In ENC R11.2.3, the NI Manager was only accessible by
FNMD-48055 TS221119 someone with administrator privileges.
In ENC R11.2.3, all service layers were not displayed for
FNMD-48129 TS221382 customized users.
In ENC R11.3.2, the physical layer performance PM was not
FNMD-48227 collected for the VCH of the 9ROADM-RS module.
in ENC R11.3.2, the protection state showed an unknown for
FNMD-48256 TS221346 a quadflex path protected track service.
In ENC R11.3.1, the service wizard allows the user to select
ports equipped with QSFP10 plugs which should not be
FNMD-48278 TS221493 available for 100G services on the MA-B5LT module
TS206064, In ENC R11.2.2, the user manual did not fully describe the
FNMD-49038 TS212006 user account needed to create an ENC to NI connection.
In ENC R11.3.2, an Ethernet service was seen to have a
faulted oper state when none of the underlying entities had a
FNMD-49246 TS204999 faulted oper state.
In ENC 11.3.2 protection switching on the Quadflex module is
protecting the traffic as expected. However, manual
switching between the two operating paths is only possible
on client port 1. If a service on the same optical signal is
provisioned on client port 2, it will also be switch to the same
FNMD-49480 TS221346 path as the one used by client port 1.
In FSP NM R10.3.1, the slaves count on a given node int he
PTP csv report does not match number of slaves on the
FNMD-49596 TS219910 device.
In ENC R11.3.2, the db backup for Sync Assurance is not
FNMD-49675 working properly.
In ENC R11.3.2, there was an error when running the
FNMD-49703 healthcheck generation command in the nmsadmin tool.
In ENC R11.2.2, the user documentation should be updated
to specify which versions of Linux are supported for Network
FNMD-49913 Intelligence installation.
In ENC R11.3.2, a loop detected in the fiber traversal
FNMD-49997 TS224821 prevented a service from being set to managed.
After an upgrade to ENC R11.3.2 the operational state of
FNMD-50302 TS225636 some services was not set correctly.
Note: Please refer to the release notes of previous releases for all defect fixes that had
been fixed prior to R12.1.1
9.1 Pro-Vision Fixes in Historical Releases
55
ID Description
On an air-gapped network with no internet access, the system did not
download all the fonts, so there were font issues in the Pro-Vision displays
and icons. The system now displays all Pro-Vision fonts and icons
FNMD-67104 correctly.
Version: 1.1
ID Description
When you performed the Zero Touch procedure properly and turned it on,
the 100G Devices table Zero Touch Status column incorrectly showed
Not Configured instead of the correct In Progress. Now the 100G
FNMD-65371 Devices table Zero Touch Status column shows In Progress.

ID Description
The Pro-Vision Health Monitor reported active and reserved database
connections incorrectly. Now the Pro-Vision Health Monitor reports active
FNMD-62242 and reserved database connections correctly.
After you cleared alarms, the devices did not clear automatically from the
Faulted Devices area in the Logical Map. Now when you clear alarms,
FNMD-61395 devices clear from the Faulted Devices area.
The S-Tag value in the device view Port Config/Details window displayed
inconsistent values for the S-Tag type “tagged”. Now the S-Tag value
FNMD-60543 shows accurate values for the S-tag type “tagged”.

ID Description
Searching the Flow Config table using the device name did not work. Now
FNMD-56425 you can search the Flow Config table with the device name.

ID Description
Pro-Vision/ENC generated an information alarm every five minutes about a
link being up when the port was down on one side. Pro-Vision no longer
FNMD-59816 generates a link up alarm in this case.
After an ENC upgrade or migration the Historical Optical Spectrum
Analysis Chart only displayed the first selected channel, which was always
the first and lowest channel number shown from the selection. Now all
selected channels data displays correctly in the Historical Optical Spectrum
FNMD-59138 Analysis Chart.
In the Wavelength Services table, you could not change the Customer
Name field on a configured Wavelength Service if the Path Type was set to
Automatic. Now you can change the Customer Name field on a
FNMD-59022 Wavelength Service if the Path Type is set to Automatic.
After you cleared an event in the Remark Action Profiles table, the event
kept its original severity level and did not display “Clear” in the Severity
column. Now the clear severity is no longer supported and was removed
FNMD-56027 as an option.
56
ID Description
Pro-Vision generated an “Incorrect max bandwidth” error when you tried
to update the XG300 port configuration settings. Now Pro-Vision no longer
generates the “Incorrect max bandwidth” error during a port configuration
FNMD-65103 update.
Version: 1.1 Some alarms generated from an OptiDriver showed an AID with Power
Supply 2 when it should have been a Port or Fan. Now these alarms
generated from an OptiDriver no longer show Power Supply 2 in place of
FNMD-64968 something else.
The IP Address/Mask field was not mandatory when you added a Virtual
Interface through the Pro-Vision GUI, but when you saved the
configuration Pro-Vision generated a “Invalid IP Address/Mask” error
anyway. Now Pro-Vision does not generate a “Invalid IP Address/Mask”
FNMD-64957 error.
Many unnecessary debug log messages appeared in the log file. Now these
FNMD-63809 debug log messages do not appear in the log file.
When using SNMPv3, the device poller sometimes returned unexpected
OIDs which the poller logged as errors. To avoid this, ADVA improved the
log message reported when receiving a SNMPv3 out of time window error
while polling devices from “Expected SW version but got
OID=snmpModules.15.1.1.2.0, value=#” to “SNMPv3 time window out of
FNMD-63803 sync while polling <DEVICE>”.
Pro-Vision was selecting 0.0.0.0/0 for a network instead of the specified
network range while performing a software upgrade using zero touch. Now
FNMD-63573 Pro-Vision selects the correct network and device IP.
The SNMP tab System Location field allowed 0-63 characters, which
caused an error when you tried to save the device. To prevent such errors,
the maximum SNMP tab System Location field character length is now
FNMD-63557 80 characters.
Pro-Vision returned an internal error when you opened the Managed
Session window. Session exceptions are now handled when gathering
session information to display in the manage session dialog, allowing the
FNMD-63556 dialog to open.
Any action filter such as sending a trap was checking for duplicates, so
status change traps were not sent if they were not processed fast enough.
FNMD-63101 Now duplicates are no longer dropped.

ID Description
Some LDAP users had the Password Change Required flag enabled, so
they could not log in after their password expired. Deleting the user from
ENC/Pro-Vision resolved the issue. Now the Password Change Required
FNMD-58347 flag is always disabled, and LDAP users can log in.
You were able to access the REST interface only if you logged in to the
user interface. Now you do not have to log in to the user interface to
FNMD-57799 access the REST interface.
The software incorrectly set the SAT Service Acceptance Criteria FLR on
the NE. The values between ENC and the NE now match. Also, you were
unable to set the SAT Service Acceptance Criteria FTD/FDV to less than 1
FNMD-56607 ms through ENC. You can now use decimal values for better granularity.
Inventory table filter fields performed filtering before you completed
adding the whole filter. Now you must leave the Inventory table filters
FNMD-56432 field to apply the filter.
57
After you changed channels mid-stream on a path using an OD-DMR10G,

the wavelength service did not build. The error message “Path cannot be
found” displayed. Now the wavelength service builds successfully in this
FNMD-54139 configuration type.
After you changed channels mid-stream on a path using an OD-1MXP200-
QC2D, the wavelength service did not build. The error message “Path
Version: 1.1 cannot be found” displayed. Now the wavelength service builds
FNMD-53496 successfully in this configuration type.

ID Description
After you performed a device reset or reboot, the message in the audit log
did not provide enough information. Now the message provides the action
FNMD-55808 that was performed, such as reset or reboot.
An OS-V8 device that completed Zero Touch remained in an “In Progress”
state. Now an OS-V8 device that completes Zero Touch does not remain in
FNMD-55428 the “In Progress” state.
After Pro-Vision users migrated to ENC, the ENC database did not display
the Pro-Vision users. Now Pro-Vision users display in the ENC database
after a Pro-Vision-to-ENC migration. However, if a Pro-Vision user’s
password includes his or her username, the migration process leaves out
FNMD-55103 that user.
OptiDriver nodes did not receive traps, and SNMP settings were not
available for that network. Now OptiDriver nodes correctly receive traps,
FNMD-54508 and SNMP settings are available.
If you deleted the snmp server from a device and then tried to configure
OptiDriver or Fiber Driver devices, Pro-Vision generated a pvautotrap bad
value(3) error. Now you can delete the snmp-server from a device and
then configure OptiDriver or FiberDriver devices without generating an
FNMD-54230 error.
An internal error occurred if you tried to change the bandwidth profile
assigned to a service endpoint when the profile currently assigned was not
compatible with the service endpoint. Now the misleading error no longer
displays. However, when you save the bandwidth profile selection for the
service endpoint and that profile is incompatible with the service endpoint,
FNMD-53837 a warning message displays.
The OS Ethernet Service MTU size was not being updated in Pro-Vision
when you performed a Device to PV sync operation. Now the OS Ethernet
Service MTU size is updated in Pro-Vision when you perform a Device to
FNMD-53784 PV sync operation.
When you used the OD-EA-VMPR2017 or OD-EA-VMPR3017 together with
the MD40 Mux in ENC, the wavelength path creation failed. Now when you
FNMD-53694 use this device combination, the wavelength path creation succeeds.
Pro-Vision did not allow .0 device IP addresses. Now Pro-Vision allows .0
FNMD-53668 device IP addresses.
The fiber type G.653 was missing from the Add Link window Fiber Type
field options. Now fiber type G.653 is an available option in the Fiber
FNMD-53500 Type field.
If you right-clicked a link and selected View Services, and then right-
clicked a service, a default browser menu opened instead of the expected
FNMD-53430 services context menu. Now the correct services context menu opens.
After you performed an NNI delete operation, the error message in the
audit log showed an incorrect port name. Now the error message shows
FNMD-53398 the correct port name.
58
After an upgrade from Pro-Vision to ENC 11.3.x, the Digital Diagnostics

window Wavelength field displayed incorrect digital diagnostics data. To
open the window, right-click the appropriate wavelength service in the list,
select Status, and then select the Digital Diagnostics tab. Now the
Wavelength field displays the correct digital diagnostics data after an
FNMD-53375 upgrade.
Version: 1.1
ID Description
When you right-clicked on a device in the Backup/Restore dialog and
selected View Config Files, this opened a number of files and did not
close them. This generated an error message when Pro-Vision reached the
maximum open files environment variable for a Linux user. Now Pro-Vision
FNMD-51334 closes the generated files and there is no error message.
When you tried to create a wavelength service, this generated the Error
is item(s): For input string” “0,911” error message. The Locale setting
FNMD-50360 of the server caused the error. This error no longer occurs.
The OptiDriver device view did not show any chassis connections. Now the
FNMD-50359 OptiDriver device view displays the chassis connections.
The Optical Power Summary stopped reporting RX/TX power levels after a
Pro-Vision to Ensemble Controller migration. Now the Optical Power
Summary correctly reports RX/TX power levels after a Pro-Vision to
FNMD-50333 Ensemble Controller migration.
Double-clicking a device in the Device Summary window to open a device
view generated an internal error. Instead, right-click the device and select
FNMD-50324 Device View to open a device view.
Device Configuration backup did not function properly after you added a
new device. Some devices did not appear in the Backup/Restore Devices
table, and profile changes were not updated on the device. Now Device
configuration backup works correctly, and profile changes are updated on
FNMD-49951 the device.

ID Description
Pro-Vision set Netconf configuration to defaults in the OptiSwitch Device
object for legacy models which did not support Netconf. Pro-Vision now
FNMD-49378 clears the Netconf configuration for legacy devices.
Previously, there was no way for you to view the Dest MEP ID column in
the Service End Points table. Now you can view the Dest MEP ID column in
FNMD-47288 the Service End Points Table.
When you added or removed an OptiDriver module from any OptiDriver
chassis, the Device View GUI window did not update the added or deleted
slots. The Device View GUI window now correctly updates the added and
FNMD-47252 deleted slots.
Previously, you could add a device even if you did not set the SNMPv3
User credentials. Now you cannot add a device without setting the
FNMD-47211 SNMPv3 User credentials.
Pro-Vision did not generate a "device down" error when executing the
"Overview" module command for a V8-M module on a down device. Now
Pro-Vision generates a "device down" error when executing the
FNMD-46846 "Overview" module command for a V8-M module on a down device.
Not all devices appeared in the Backup/Restore Devices list. Now all
FNMD-45343 devices appear in the Backup/Restore Devices list.
59
10 Historical Limitations
1. No polling available for FSP Element Manager (Rack View). Workaround:

Ensemble Controller Server should always be registered as Trap Sink in all
managed Network Elements. The Ensemble Controller server, however, makes an
Version:attempt
1.1 to register itself as trap sink for newly discovered devices.
2. If events are acknowledged using the function “Acknowledge until…” the
acknowledging user is not saved. Workaround: Acknowledge multiple
alarms/events by marking multiple or all (<Ctrl-A>) in the respective event
browser and then pressing <Space>.
3. If the GUI startup takes too long (e.g. because the server is busy) the client
session may time out before the GUI startup is finished. This leads to an error
message “Cannot load configuration”. Workaround: Typically, it is sufficient to
just restart the client. If the problem persists you may increase the session
timeout (property com.adva.fnm.option.server_timeout in file
fnm.properties).
4. If an invalid time range is entered in Report Generation empty reports will be
generated. Network names will be shown as “null”.
5. User action log for NE configuration restoration does not include the NE name.
6. When using low screen resolution, certain fields and buttons in editors may not
be visible per default. The windows size must be adapted by the user to make
them accessible.
7. On Windows the client (GUI) hangs on rare occasions. Resumes operation after a
short waiting time.
8. On Windows operating systems, if the network cable is unplugged, the
connection between client and server (both on the same machine) may fall apart,
which sometimes requires a server restart.
9. Tracked Service: The icon color used to denote a connection’s state is grey if the
state of the connection could not be set via SNMP. On rare occasions this icon
may be colored even if the SNMP commands were not successful.
10. High Availability, Operating System Windows: On rare occasions there is an error
message “Couldn't initialize SFTP basesystem”, when the primary server is
switched back to master mode, using the secondary server and ‘Replicate’ is
selected. If necessary, the database of the primary server needs to be updated
manually via FTP transfer with the DB backup of the secondary server.
11. If the user deletes all reports from the client, some report files may remain on
the server folder var/log/reportDB. These files need to be deleted manually.
12. Launching the standard Windows Telnet client from within Ensemble Controller is
not supported when running the Ensemble Controller client on a Windows x64
OS. Workaround: Configure an external Telnet/SSH client in fnm.properties.
13. In the Inventory Report (PDF and CSV) the “Order Info” field for HN4000
equipment shows inappropriate contents.
14. The Ensemble Controller server does not run on Japanese language Windows
versions. Workaround: Use English language Windows version for server.
15. On initial performance data collection for a newly discovered NE, if there are
performance bins marked as invalid on the NE then Ensemble Controller will not
collect any bins older than the invalid one.
16. Ensemble Controller allows changing the polling interval for performance data
collection. Any deviation for the default for performance data collection (short
60
term) may cause missing performance data (FSP 150Cx only). Workaround: Stick
to default settings (15 minutes).
17. The performance template filter per NE type always shows “Physical Layer
Performance” even if not supported by the selected NE type.
18. On very rare occasions the Network Element’s may stop responding to SNMP
Version:requests
1.1 from the Network Management System. Workaround: Use the GUI to
reset the SNMP session in Ensemble Controller for the respective NE.
19. PDF report view generation for large performance reports is inefficient. No
workaround is available. PM Reports for large subnets should be avoided.
20. File Transfer process during Software Download of a Hatteras HN4000 might fail
due to timeout, if they take longer the 8 minutes. Workaround: The minimum
required DCN speed between the Ensemble Controller and the Network
Element(s) is 64 KBit/sec.
21. Ensemble Controller may not collect all the historical PM bins for FSP 150CM
when historical bins that are invalid are present at the NE. This is a startup
condition and only occurs during the first polling of the NE. All subsequent
collection proceeds normally, but the history is not filled once an invalid bin is
reached. No workaround is currently available.
22. Network Element layer performance data is not collected for remotely un-
managed FSP 150CP. No workaround is currently available as the NE does not
support PM’s for remote devices.
23. Assignment of performance management templates to large subnets (or
assigning large templates to subnets) takes a long time. The only workaround
currently available is the advice to perform this operation on smaller subnets or
avoiding use of large templates. If the user chooses such operation, then it’s
advisable to let the operation complete without interruption.
24. In High Availability configurations, the Ensemble Controller client may fail to
reconnect to the Standby server after a switch-over. Workaround: Close the
application client and restart.
25. For FSP 150CC-825 QOS Ethernet layer port PM is not collected. The user is
advised to use the NE Web interface to obtain the data.
26. For FSP 150CP Network Elements, the System Contact and Location information
will not be restored after a NE database restore operation. Workaround: The user
will have to enter the information again using the EM interface.
27. FSP 150CM Master NE when moved to a different subnet then the remote node
may cause a connection failure from the client to the server. Workaround: The
FSP 150CM and its remote nodes must reside in the same subnet and hence be
moved together during copy/paste operations.
28. For FSP 150CC-825 Network Elements, multiple restarts can result in Ensemble
Controller showing a loss of communication via SNMPV3 due to protocol
discrepancy. Workaround: Use the GUI to reset the SNMP session in Ensemble
Controller for the respective NE.
29. Sometimes when creating a tracked service, a clock mismatch warning is raised
by the service wizard even though the ports are configured correctly. This
warning can be ignored.
30. In rare situations, it has been observed that some OTU layer and SDH multiplex
layer performance parameters were not collected completely from FSP 3000R7.
31. When a FSP 3000R7 channel module is replaced by a different type of module
(re-provisioned on the NE), then it is required to follow exactly the procedure
61
described in the User Manual, Replacing Hardware. Otherwise, the new module
may not be discovered properly, and hence are not selectable as connection
termination point.
32. When Service add/remove operations are performed rapidly on the same module,
the module selection page in the service wizard may incorrectly display port
Version:availability
1.1 status. Workaround: Avoid performing rapid service add/delete
operations on the same module (wait 1 min) or use the back button followed by
next button to re-load the module selection page.
33. In very rare occasion a busy cursor may be shown when navigating to the
module selection page in the service wizard. Workaround: Restart the client and
then re-run the Service Wizard.
34. To avoid PM collection issues with FSP 1500 devices, please ensure that PM
templates do not contain any unsupported Mon Types. Additionally, please avoid
assigning templates to Subnets containing such devices (i.e. assign templates to
services instead). Workaround: One should use the Element Manager to
determine the supported Mon Types and only use these Mon Types in the
template.
35. For large subnets, report generation could be slow. Workaround: Please generate
reports on subnets with 20 NE’s or less only. Additionally, for PM reports there is
a configurable limit (maxNECountperformance) which if set will warn the user and
prevent the report generation of large subnets.
36. Insertion of a new NE on a fiber between two Network elements is not supported
in the subnet editor. Workaround: Remove the link and re-create the fibers
between NEs.
37. The service wizard module selection page will always show modules with 1 slot
width even when the module is 2 slots wide.
38. When subsequent template assignments are done for the same entity (e.g. one
template is first assigned to a service and then another template is assigned to a
subnet), the last template assignment will prevail.
39. When creating Tracked Service with FSP 1500, the default admin state is set to
down. Workaround: Please set the admin state by invoking the operation on the
selected service from the Service Tree.
40. Channel Card protected services in provisioning mode for WCC10GT and
4TCC10G modules may incorrectly display the active path in the service tree icon
as well as the service editor detail display after a protection switch operation.
41. Browse Service and View Services actions are not supported in the Security
Manager for the Service Tree. Workaround: Please use “Customers” in the “Edit
View” to control authorizations of service per users in the Service Tree.
42. The Chassis View tab in the Network tree may improperly display alarms for
40CSM-2HU and ROADM-2DC shelves. Workaround: use the NED to verify the
alarms.
43. Fiber Break indication persists in the Network View Map even when the last
service is removed from the fiber.
44. If the OS system time is or time zone is changed on the system running
Ensemble Controller server, the Ensemble Controller server must be shut down
first, then change time, followed by a server restart.
45. Duplicate Unauthorized Events can be received from FSP3000R7 due to Network
Element software related issue.
46. In the context of data services, some PM Monitoring Types will not be collected
network side of 10TCC10GT-DL modules.
62
47. It is recommended that while using the Service Manager to create provisioned
services, any configuration changes (e.g. to the Fiber Map) made at the NE are
allowed sufficient time (5 Min) to propagate to Ensemble Controller prior to
initiating Service creation operations. Workaround: one can trigger a manual
status poll operation before performing service creation operations.
48. For
Version: 1.1FSP 150 CCf-825 devices, the ABRL-TX PM point shows the value of ABR-TX
PM Point. The user is advised to use the NE Web interface to obtain the data
49. For FSP 150 CCf-825 devices, the Parameter "Frames Marked as Green by RX
Policer" shows an incorrect value. The user is advised to use the NE Web
interface to obtain the data.
50. For FSP 1500 devices, PM’s are not collected for SDH/Sonet Performance (High
Order Path) and SDH/Sonet Performance (Low Order Path) layer.
51. Performance collection may fail to collect ‘System Up Time’ and ‘System
Availability’ monitoring types for some devices (e.g. FSP 150CC-825)
52. Force Delete operations on track services should be avoided as they may leave
counters for Folders and customers in an inconsistent state and hence show
inconsistent operational state in the service tree. Workaround: Please use the
normal delete operation on track services.
53. Mismatch alarms on services will be present in Ensemble Controller if proper
order of de-commissioning the modules is not followed. Workaround: The user
should delete the service from Ensemble Controller first, the remove the module
from the NE and finally remove the module from Ensemble Controller system.
54. Administrative Operation on the Optical Channel may result in an inconsistent
display of service detail and the status of Optical Channel in the Split Pane under
the Service Tree. The Data Service status in the Service Tree is always correct.
Workaround: Reselect the Data Service from the Service Tree to display the
updated status.
55. It is advised that the user should avoid changing the severity of the fiber break
alarm from the default critical severity.
56. It is advised that the user should avoid changing the default severities of server
generated alarms (SRV) in the events severities window as these severities will
not be reflected when the alarm is raised.
57. It is not possible to start a telnet session from NM GUI in a 64-bit Windows
system. Workaround: When telnet access to elements is required in a 64-bit
installation, use the free “putty” application (32bit) instead.
To use “putty” put the following line in the fnm.properties file:
com.adva.fnm.security.CLI_WINDOWS=C:\\path_to_putty\\putty.exe -telnet
{ip}where “path_to_putty” represents the full path to the putty.exe file
58. For 5TCE10GT-D modules service provisioning fails when the user specifies a
path and a channel number to be used for the service. Workaround: The user
should not specify the channel number and let the Control Plane pick the channel
number for the service
59. For FSP 1500 Devices, the user is advised to use the element manager to
restore the NE Database backup configuration that may have been performed
using Ensemble Controller.
60. For FSP3000R7 devices, the 40CSM OJG shelf is not supported in the Service
Wizard.
61. In a High Availability configuration when the system automatic switchover to a
standby server, the optional supplemental shell script (secondary.sh) will be
executed twice.
63
62. Data Services sharing the same OCS should reside in the same Service Group
folder or directly under the same Customer.
63. For provisioned service, the user may see an error message in the message
window stating that equalization of the service has failed. Workaround: The user
may trigger a manual equalization process on the Service. The user may also
Version:ignore
1.1 such message if it is not for the first service on the tunnel
64. The user may see an error message in the performance management window
when entities are removed from the system while the PM template assignment
action is being applied. Workaround: The user can use the refresh button from
the tool bar before viewing the results
65. Provisioned services should only be deleted from the system while in the “UP”
state. This will ensure that that proper cleanup of all the entities is performed at
the NE.
66. Provision Services for 2TWCC2G7 on FSP3000R7 do not support OTU1 facility
type setting on the Network Port for GBE client service type. Workaround: The
user should provision OC48 or STM16 network facility types for such services.
67. For FSP 150CM, the user should avoid manually changing LinkLossFwdSignalType
and LinkLossFwdTrigerType parameters using the craft interface as event
notifications of such action are not sent to Ensemble Controller. Additionally,
requests that fail and must undo these parameter settings will not update
Ensemble Controller database due to missing notifications.
68. Services involving 4TCA-PCN+4GU module in ADM mode for FSP3000R7 may not
correctly display the Active Path status (either displays both path’s active or
displays an incorrect path active). Workaround: The user should run status poll
on the start and end nodes of the service.
69. Protected provisioned involving 4TCA-PCN+4GU in ADM mode do not properly
deescalate alarms on the protection path. Moreover, alarms from intermediate
modules in such configurations are also correlated to the service.
70. When there is a condition on a VCH affecting the network port or equipment, the
faulted service view will show a Service-C-Affected alarm in the faulted service
view instead of Service-N-Affected alarm.
71. The user is advised to not modify the restoration configuration (enabled/disabled)
for provisioned services after the service has been created. This parameter can
be set when the service is being created for the first time.
72. For provisioned protected services with a mixed configuration of fixed and
tunable filter for working/protection path, the user advised to retry a failed
provisioning by specifying the channel number for the fixed filter.
73. Multiple Dying Gasp Host unreachable (configuration) alarms are not handled
properly in Ensemble Controller.
74. Previously collected PM data for FSP 150CM Devices Access Port will be lost when
the media type of the port is changed.
75. When creating a restored provisioned service (“Restoration Enabled” box
checked) ensure that there is a valid signal already on the desired working and
protected paths, so that the service will not try to protection switch and/or
restore as soon as it’s created.
76. The user is advised not to minimize the Install Anywhere installation tool during
the installation of Ensemble Controller on a Windows OS. If the user does
minimize it, it's important to restore the window before the installation
completes. If the installation completes with the Install Anywhere window
minimized, it will not be possible to restore the window. The user will have to kill
the Ensemble Controller process from the task manager.
64
77. If Ensemble Controller is managing an FSP 1500 device and the NMS IP address
is not in the trap receiver list for the device, configuration change traps for the
High Speed Service Ports will not appear in NMS even after configuration polling.
Please make sure the Ensemble Controller is in the trap receiver list for the
device.
78. When an FSP 150EG-X device is discovered on Ensemble Controller and has
Version:TS/BC
1.1 Sync Node provisioned with multiple SOOCs protection, and the user
selects the route containing this TS/BC Sync Node, and uses “Go to slave Sync
Node” menu option to navigate to this slave Sync Node on the Synchronization
tree, the Synchronization tree path which is open as a result may not show the
active clock path to this TS/BC Sync Node. As a workaround, the user can look
for the active clock route in the Sync Map view, for this selected TS/BC Sync
Node.
79. Trap sink registration via SNMPv3 is not available on the FSP 150CCf-825 device
due to a defect on the device. Traps are sent via SNMP v2 instead.
80. Some service types and also parameters on the facility page of the service wizard
contain values required to support services provided by newer releases of the
FSP 3000R7. Some of these values may not be backwards compatible with older
releases of the device and using them may cause service creation to fail. The
solution is to make sure to provision the service with the appropriate values the
software release of the NE being managed.
81. OTU-2 services on 10TCC100G are created with EFEC as the most efficient FEC.
This mode is not support on older versions FSP 3000R7(12.x and older). Please
make sure FEC is set to GFEC when creating OTU-2 services on older versions of
the element. ADVA recommends upgrading to a current release of the device.
82. Due to a limitation on the device, NE Database Backups scheduled between 0:00
and 1:00 will fail on FSP1500 devices. The workaround is to enable the NE
backup retry and set it to 2 retries at 30 minute intervals.
83. In certain configurations it is possible that provisioning a service between NEs
with older releases will not complete successfully with an error indicating that
there was an ‘SNMP Commit Failure’. The recommendation is to upgrade the NEs
to the latest version that is compatible with the Ensemble Controller version.
84. The module page of the service wizard may allow the user to select a port on the
4TCA4G module which is not supported for the selected service type.
85. Ensemble Controller Optical Director supports setting the Error Forwarding Mode
to Laser Off on network interfaces of the 2WCC10G module. Service creation may
fail if this value is used while managing older versions of the FSP 3000AC.
86. L2 Remote PTP Slaves on OSA540x devices are not shown in Sync Director
87. After a software upgrade of the OSA5440 device, the device may appear to have
an SNMP communication failure of the switchover does not complete in under 40
minutes. The workaround is to run inventory polling on the device.
88. OCH layers created in releases prior to ENC R11.3.1 which use PM modules may
not show the correct oper state. Re-exploring the service(for explored services)
or setting the admin state to the same state it is currently in will recompute and
correct the oper state.
89. If the user uses Remote Desktop to connect to a Windows 10 machine to use the
Ensemble Controller client, the client may appear to freeze if it is open when the
RDP sessions starts. The workaround is to restart the ENC client.
90. FSP ALM devices that will be integrated to Fiber Director Server, must use SNMP
v1 or v2c during the ENC discovery process. SNMPv3 is not yet supported by
Fiber Director.
91. PM Points on XG480, XG418, XG404 devices can be collected using default PM
Profiles only. User defined PM Profiles are not supported by ENC for these
devices.
92. Explore path services are not supported for services with the Unknown Network
device in the path. Unknown Object should be used instead.
93. The Remark and Alternate Name fields in the Overview tabs of services may not
be populated properly. The workaround is to open the Modify wizard from the
65
context menu of the service and then click Finish. The fields should be populated
after this step.
94. Although DCN Alarm for OSA3230B mentions SNMP in the description text, the
DCN for OSA3230B is based on TCP disconnect. SNMP is not used for OSA3230B
95. TAPI does not support:
• Protected services
Version:•1.1Services that do not appear in the multi-layer model in ENC
• NfC provisioning
10.1 Pro-Vision Historical Limitations
1. Device support is unavailable for VIF and Dummy Interfaces, service RFC2544,
service Y1564, SCP and FTP Backup, Restore, and Upgrade support.
2. When you configure or modify an OSPF Area in a dummy or virtual interface using
the GUI, the OSPF Area field is created or modified correctly, but the new or
modified entry is not added to the OSPF Areas list. To add the entry to the OSPF
Areas list, use the CLI to manually add the new row in the OSPF Areas table under
OSPF Protocol Configuration.(PV-13458)
3. Performing an SFTP upgrade on an OptiPacket does not work, and generates an
"Error (permission denied)" status message. This can occur when any user other
than the Pro-Vision NETCONF user previously performed an upgrade using the CLI
with an image name that is the same as the image name the user is trying to
upgrade from Pro-Vision. Since the owner/permissions do not match, the image can't
be uploaded and the upgrade fails. To avoid this, login to the OptiPacket, open the
Linux shell, and manually delete the old image file(s) from the "/ver" directory so
that Pro-Vision can upload its upgrade image.(PV-12867)
4. You can only set port assignments while adding UNIs/NNIs, not while updating them.
Therefore, you cannot change port assignments for a UNI or NNI that is already
assigned to a service.(PV-12146)
5. Wavelength services that use muxponder trunk ports as endpoints are currently not
supported. You should create these types of wavelength services from access port to
access port. For example, if you need to create a wavelength service between Node
A, slot 10 port 9 and Node B, slot 10 port 9 (assume these are OD-DMXP10G
modules), you will need to use any one of the eight access ports on either
muxponder as endpoints of that wavelength service.(PV-11779)
6. The configuration that follows is part of the factory default configuration for a V8-M
device. If a "Module does not exist" error is displayed when you attempt to issue any
of the VDSL module commands in Pro-Vision, verify that this configuration exists on
the device.(PV-11033)
7. No option currently exists to configure the index at the AC interface, for example,
attached to the port number .25 at eth-1/0/1.25, when you add a service to an
OptiPacket device. Pro-Vision automatically adds this service.(PV-8933)
8. After the system adds an E-Service bandwidth profile to an OptiPacket end point,
any changes you make to that bandwidth profile in the Pro-Vision database do not
automatically push down to the device. If this situation occurs, you need to manually
66
update the bandwidth profile directly on the device by using the chassis panel E-
Services: Policer/Shaper table. First disable the profile, save it, and then change the
profile. Save the profile again, re-enable it, and then save it.(PV-8886)
9. The outer tag is used as the sub-interface index. For example, for port 1.20 and
outer tag 214, the AC created will be eth-1/0/20.214, with outer tag 214. If you
create an AC using the CLI, you must use the same convention as Pro-Vision. It is
Version: 1.1 that the sub-interface and outer tag match. If you do not use this method
mandatory
while configuring using the CLI, you may see discrepancies in Pro-Vision.(PV-7720)
10. When you create OptiPacket services, unintended updates are made to a profile on
the OptiPacket if you have already added the profile using another service and
assigned that same profile to another service. If the Pro-Vision profile contains
changed values, the device reflects these values if the service is added or updated.
This situation occurs if you create a profile on Pro-Vision in the Bandwidth Profile
window (Policer or Shaper), create an E-Service and assign the profile, change the
profile on the Pro-Vision Bandwidth Profile window, and create a new E-Service on
the device with the profile assigned. The device updates, and Pro-Vision reflects the
changes. Both services reflect the change because multiple services share the
profile. The same updates will occur if any other services on the device change their
profile assignments to this updated profile.
11. The purpose of the Sync Config (Pro-Vision to Device) feature is to restore the
configuration after you replace an OptiSwitch. This feature has certain limitations
because if you replace an OptiSwitch, its configuration must be minimal to ensure no
dependency issues arise. For example, if the OptiSwitch has an enabled service, the
switch does not allow SNMP sets to the ports that the service uses. If you run Sync
Config (Pro-Vision to Device) on an OptiSwitch that has this configuration, potential
problems might occur. The feature currently only synchronizes objects that are in the
Pro-Vision database. If other configurations exist on the switch, for example,
configurations manually done through the CLI, you might encounter a dependency
issue.
12. The configuration for the Batch Upgrade (FTP) and Backup/Restore Config (FTP)
features are stored only in the switch, not in the database. Therefore, the Sync
feature does not support them.
13. Pro-Vision does not recognize any services you have previously created on
OptiSwitches without using the Pro-Vision service CLI. If you previously created a
service through the service CLI on an OptiSwitch before the use of Pro-Vision, any
attempt by Pro-Vision to configure a port belonging to that service will fail.
14. Currently, Pro-Vision supports only Version 2 and Version 3 trap filters for ADVA
proprietary traps. You must configure the trap client on your device as an SNMPv2 or
greater client trap in order for Pro-Vision to properly process received traps.
67
11 Legal Information
Copyright © 2001-2021. ADVA Optical Networking SE
All rights reserved. Hardware and software mentioned in this document includes software
developed by ADVA SC Optical Networking ("ADVA"), the Apache Software Foundation
Version: 1.1
(http://www.apache.org), Teodor Danciu (http://jasperreports.sourceforge.net), and/or
other open source software. Some software was created using ORBacus for Java by Object-
Oriented Concepts, Inc.
TRADEMARKS
The terms ADVA and FSP are trademarks or registered trademarks of ADVA in the United
States, Germany and/or other countries. All other company, product, or service mentioned in
this document may be trademarks or service marks of ADVA or their respective owner.
PATENTS
The content described in this document may be covered by patents or pending patent
applications of ADVA. The furnishing of this document does not give you any license to these
patents.
DISCLAIMERS
The content of this document could include technical inaccuracies or typographical errors, and
is subject to change at any time without notice. Reliance on this content is at the relying
party's sole risk and will not create any liability or obligation for ADVA. Any references in this
document to non-ADVA publications and/or non-ADVA Internet sites are provided for
convenience only and do not in any manner serve as an endorsement of those publications
and/or Internet sites. The materials within those publications and/or Internet sites are not
part of the materials for any ADVA information, product or service, and use of those
publications and/or Internet sites is at your own risk.
THE CONTENT OF THIS DOCUMENT IS PROVIDED ''AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL ADVA, ITS AFFILIATES, EMPLOYEES,
OFFICERS OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THE
SAME APPLIES FOR ANY HARDWARE OR SOFTWARE COVERED BY THIS DOCUMENT,
UNLESS A SIGNED AGREEMENT WITH ADVA OR THE APPLICABLE PRODUCT
LIABILITY LAW EXPRESSLY STATES OTHERWISE.
68
12 Support Contact Information
For further information contact the ADVA support:
Europe:
support@adva.com
Version: 1.1
North America:
support-americas@adva.com
Asia:
support-asia@adva.com
69

Ensemble Controller R13 3 3 ReleaseNotes RevA

Uploaded by

Copyright:

Available Formats

Ensemble Controller R13 3 3 ReleaseNotes RevA

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

Ensemble Controller R13 3 3 ReleaseNotes RevA

Uploaded by

Copyright:

Available Formats

Ensemble Controller R13.3.

Document Number: 80000071399

ADVA Optical Networking SE

ADVA Optical Networking SE

ADVA Optical Networking

Contents January 20, 2023

1 Revision History ............................................ 4

3 Supported Devices ........................................ 9

5 System Requirements .................................. 15

6 Installation Instructions ............................... 15

7 Known Issues (List of Limitations) ................. 27

8 Version History ........................................... 31

9 Fixes in Historical Releases ........................... 39

11 Legal Information .................................... 68

Revision Date Reasons for Revision

2.1 Enhancements in Version 13.3.3

2.2 Important Notes

• Ensemble Controller R13.3.3 release requires supplemental scripts (that need to be

2.3 Life Cycle Information

2.4 Product Documentation

The following support documentation is available for Ensemble Controller:

2.5 Ensemble Controller Pro-Vision Customers

2.6 Pro-Vision to Ensemble Controller (ENC) Migration

R3.1.1, R3.2.1, R3.2.2, R3.3.1, R3.3.2,

R6.1.1, R6.2.2, R6.5.1, R6.5.4, R6.5.5,

R7.1.4, R8.5.3, R9.6.1, R9.6.2, R9.6.3,

R6.1.1, R6.2.2, R6.5.1, R6.5.4, R6.5.5,

XG108, XG108-H, XG108-SH R12.1.1, 13.1.1

R6.1.1, R6.2.2, R6.5.1, R6.5.2, R6.5.3, FSP 150CC-XG210-

R11.1.3, R11.2.1, R11.2.2, R12.1.1,

FSP 150-XG116Pro, FSP 150-

FSP 150 XG300 (OS-V):

FSP 150XG440 R5.5.1

R18.1.2, R18.5.1, R19.1.2, R19.2.1,

R8.1.1, R8.1.3, R8.5.1, R8.5.3, R9.5.1,

R8.1.1, R8.1.2, R8.1.3, R8.5.1, R8.5.2,

OSA 5412, OSA 5422 R10.6.1, R11.1.1

R10.1.1, R10.1.3, R10.2.1, R10.2.2,

OSA 5331 R2.22, R2.23

R2.2.1, R2.2.2, R2.2.3, R2.3.1, R2.4.1,

R8.5.1, R9.1.1, R9.1.2, R9.1.3, R9.1.5,

OSA 3350 R4.1.1, R4.1.2

R15.1.0.24, R15.2.1.6, R15.4.0.30,

R5.6.1, R6.1.1, R7.1.1, R7.1.2, R7.1.3,

R3.3.2, R4.1.1, R4.2.1, R4.2.2, R4.2.3,

FSP 1500 R3.0, R3.2

R13.1.2, R13.2.1, R13.2.2, R13.2.3,

R2.1.1, R2.1.2, R2.2.1, R2.2.3, R2.2.6,

R6.2.2, R7.2.6, R7.2.8, R7.2.9,

R2.2.1, R2.3.1, R3.1.2, R3.2.1, R3.2.2,

ADVA 1400 R16.1.4

Table 1: Supported Device Types and Releases

Product Versions Comment

OS904, OS904-MBH, OS906, OS906G-M,

OS9124-410G, OS9244-1210G R4.5.81

XG304, XG304u, XG308 R19.6.2

Product EM Version Comment

Table 2: Embedded Element Manager Versions

4 Customer Defects Fixed in This Release