XDM®

Version 9.1 R1
Release Notes
XDM Release Notes
V9.1 R1
Drawing No: 417006-RLSN-077-63 Rev. A01
April 2014
1st Edition

ECI's XDM, BroadGate, and NPT product lines comply with MEF9 and MEF14 standards.

ECI's qualification lab is accredited by A2LA for competence in electrical testing according to
the International Standard ISO IEC 17025-2005 General Requirements for the Competence of
Testing and Calibration Laboratories.

ECI's management applications run on VMWare virtualization hypervisors.

© Copyright by ECI, 2004-2014. All rights reserved worldwide.

This is a legal agreement between you, the end user, and ECI Ltd. (“ECI”). BY OPENING THE DOCUMENTATION AND/OR DISK PACKAGE, YOU ARE
AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN
THE UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND BINDERS OR
OTHER CONTAINERS), TO THE PLACE FROM WHICH YOU OBTAINED THEM.
The information contained in the documentation and/or disk is proprietary and is subject to all relevant copyright, patent, and other laws protecting
intellectual property, as well as any specific agreement protecting ECI's rights in the aforesaid information. Neither this document nor the
information contained in the documentation and/or disk may be published, reproduced, or disclosed to third parties, in whole or in part, without
the express prior written permission of ECI. In addition, any use of this document, the documentation and/or the disk, or the information contained
therein for any purposes other than those for which it was disclosed, is strictly forbidden.
ECI reserves the right, without prior notice or liability, to make changes in equipment design or specifications. Information supplied by ECI is
believed to be accurate and reliable. However, no responsibility whatsoever is assumed by ECI for the use thereof, nor for the rights of third parties,
which may be affected in any way by the use and/or dissemination thereof.
Any representation(s) in the documentation and/or disk concerning performance of ECI product(s) are for informational purposes only and are not
warranties of product performance or otherwise, either express or implied. ECI's standard limited warranty, stated in its sales contract or order
confirmation form, is the only warranty offered by ECI.
The documentation and/or disk is provided “AS IS” and may contain flaws, omissions, or typesetting errors. No warranty is granted nor liability
assumed in relation thereto, unless specifically undertaken in ECI's sales contract or order confirmation. Information contained in the
documentation and in the disk is periodically updated, and changes will be incorporated in subsequent editions. If you have encountered an error,
please notify ECI. All specifications are subject to change without prior notice.
The documentation and/or disk and all information contained therein is owned by ECI and is protected by all relevant copyright, patent, and other
applicable laws and international treaty provisions. Therefore, you must treat the information contained in the documentation and disk as any
other copyrighted material (for example, a book or musical recording).
Other Restrictions. You may not rent, lease, sell, or otherwise dispose of the documentation and disk, as applicable. YOU MAY NOT USE, COPY,
MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR ANY COPY IN WHOLE OR PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE.
ALL RIGHTS NOT EXPRESSLY GRANTED ARE RESERVED BY ECI.
All trademarks mentioned herein are the property of their respective holders.
ECI shall not be liable to you or to any other party for any loss or damage whatsoever or howsoever caused, arising directly or indirectly in
connection with this documentation and/or disk, the information contained therein, its use, or otherwise. Notwithstanding the generality of the
aforementioned, you expressly waive any claim and/or demand regarding liability for indirect, special, incidental, or consequential loss or damage
which may arise in respect of the documentation and/or disk and/or the information contained therein, howsoever caused, even if advised of the
possibility of such damages.
The end user hereby undertakes and acknowledges that they read the "Before You Start/Safety Guidelines" instructions (when provided by ECI) and
that such instructions were understood by them.
It is hereby clarified that ECI shall not be liable to you or to any other party for any loss or damage whatsoever or howsoever caused, arising directly
or indirectly in connection with you fulfilling and/or failed to fulfill in whole or in part the "Before You Start/Safety Guidelines" instructions.
All graphics included in this document are for illustrative purposes only and might not correspond with your specific product version.
Contents
1 What's New in XDM V9.1 ............................................................................ 1-1

2 XDM Hardware Versions ............................................................................. 2-1

2.1 New I/O Cards and Modules .................................................................................................. 2-1

3 New Software Features ............................................................................... 3-1

4 Software Versions ....................................................................................... 4-1

4.1 XDM Version Numbers .......................................................................................................... 4-1

5 Upgrade Constraints and Post-Upgrade Activities ....................................... 5-1

5.1 General Upgrade Information ............................................................................................... 5-1
5.2 Traffic-Affecting Activities...................................................................................................... 5-2

6 Operational Notes and Limitations .............................................................. 6-1

6.1 Known Limitations ................................................................................................................. 6-1

7 Resolved Issues ........................................................................................... 7-1

8 Known Issues .............................................................................................. 8-1

9 Related Publications .................................................................................... 9-1

9.1 XDM Converged MSPP and All-Range ROADM (All Platforms).............................................. 9-1
9.2 XDM-1000 Product Line ......................................................................................................... 9-1
9.3 XDM-100 Product Line ........................................................................................................... 9-1
9.4 All XDM Shelves ..................................................................................................................... 9-2
9.5 XDM Documentation CD ........................................................................................................ 9-2

10 Technical Assistance .................................................................................. 10-1

ECI Telecom Ltd. Proprietary iii

Contacts
Name Title Telephone Email
Ezra Yehezkel PLM PTS +972-3-9266429 Ezra.Yehezkel@ecitele.com
Michael Shapiro PLM PTS +972-3-9266981 Michael.Shapiro @ecitele.com

Document History
The following table displays information regarding released editions of this document and briefly describes
the changes made to them.

Rev. No. Release Date Revision (Emb) Responsible Approved by Description of

Changes
A01 06/04/14 048 Ezra Yehezkel Alon Moshes First release

ECI Telecom Ltd. Proprietary 1-1

1 What's New in XDM V9.1
This document provides information regarding the release of XDM V9.1 embedded software.
XDM V9.1 focuses on strengthening ECI's XDM® Ethernet/MPLS and SDH capabilities. It provides various
advanced features that enhance the XDM Ethernet/MPLS and MSPP capabilities.
Following are the main highlights of this release:
 Enhanced Ethernet/MPLS Features
 PW Redundancy
 Y.1731 PM
 FRR and 1:1 protection trigger based on link degradation
 MCS50 and MCSM50 Cards
 eIOP for MCSM50
 MCS50_LAN mode
 MCS50 assignment in XDM500
 Migration from MCSM to MCSM50 and from MCS10 to MCS50
 Unified PM
 Unified PM collection mechanism, which enables the collection of PM data for a large number
of objects.
 Multi-Version Support
 ASTN Features Restored

ECI Telecom Ltd. Proprietary 1-1

2 XDM Hardware Versions
This section describes the new hardware versions in XDM V9.1.

2.1 New I/O Cards and Modules

No. Card Name Description
1 BiDi XFP transceivers OTR64_E27BD and OTR64_E33BD XFP’s with 21dBm power
budget (long range - 60km) in MCS50 and STM64 cards
2 OTC25_xx Add support for OTC25_xx colored interface at STM-1/4 rates in
SIO1_4B

ECI Telecom Ltd. Proprietary 2-1

3 New Software Features
This section describes the new software features in XDM V9.1.
No. Feature
MPLS and Ethernet Features
1 PW redundancy
2 Enhanced IOP
3 Link degradation as a trigger for  XDM will trigger port down upon BER threshold crossing
FRR and 1:1 LSP protection
4 MCS50 LAN
5 MCS50 assignment in XDM500
ECI Telecom Ltd. Proprietary
Description
 PW Redundancy is a mechanism that provides protection at
the Service layer for Service Ports, Pseudowires and PEs and
eliminates single points of failure while ensure that only one
path is active between pair of Provider Edge nodes (PEs) or
Customer Edge nodes (CE).
 The transport layer cannot provide protection against failure
of an edge node where the service end point is located. A
redundant service end point is required, forming a dual
homing topology. PW Redundancy is the standard
mechanism for such case.
 Supported topology is PE Dual homing to H-VPLS with CCN
Enhanced IOP (eIOP ) support for MCSM50-X10G card:
 The current IOP feature provides 1:1 card protection for
MCS cards
 Enhanced IOP adds the functionality of card protection
based on detection of link failure between the MCS cards
and the client equipment in addition to card failure
(EXC – Excessive BER)
 The High BER threshold for 10G ETY/MoE is 10-4,
non-configurable
 XDM add new triggers for port down on EoS/MoT ports as
follows
 No LCAS - VCAT Mode
 EXC – on one of the members in the VCG
 EXC on Far-End - on one of the members in the VCG
 LCAS Mode
 EXC - on the member is a trigger for LCAS to remove
member from VCG
 The feature is supported on all MCS cards
 support for MCS50 in a shelf without HLXC, and in shelves
with legacy matrices (HLXC192/384, XIO192/384F)
 LAN mode in slots I1,I2,I5,I6
 Regular mode (10G slots) I3,I4
3-1
XDM® Release Notes New Software Features

No. Feature Description

6 MCSM and MCS10 migration to  The migration process changes the card type and moves all
MCSM50 and MCS50 connections and configurations from the origin card to the
target one.
 LS V10 is required
7 Y.1731 PM OAM  performance of Ethernet services that include:
 frame delay (FD)
 frame delay variation (FDV)
 frame loss (FL)
 supported in all MCS cards except MCS30
8 Throughput utilization counters  An industry common statistics for bridge/switch
performance.
The statistic counters show real-time and history forwarding
engine performance.
 Supported in all MCS cards
MSPP
1 Unified PM  Unified PM collection mechanism, which enables the
collection of PM data for a large number of objects.
 Replacing older mechanism of PM collection (PM Groups for
SDH and HugePM for Data).
 The UPM mechanism runs in the background of the system,
collecting and recording historical PM data with “Monitor
active” enabled.
 EMS collects from all XDM-s the single PM file
2 xMCP/MXC operation  Improving/Simplifying procedure for MXC/xMCP
improvements replacement
 BIT and DB sync enhancement
For more information please contact your customer support
representative
General
1 Multi-Version support  should work with embedded versions:
 V9.1
 V9.0
 V8.4R2
 V8.3 for XDM50

ECI Telecom Ltd. Proprietary 3-2

4 Software Versions
This section describes the software versions released in XDM V9.1 R1.

4.1 XDM Version Numbers

Product Software Version
Main Version Name XDM V9.1 R1.0
NPT-1600, NPT-1600C v091.048
XDM-1000/2000/3000/40/400/450/500 v091.048
XDM-100/200 w091.048
XDM-50 x083.012
XDM-300 y091.048
XDM-900 z091.048

ECI Telecom Ltd. Proprietary 4-1

5 Upgrade Constraints and Post-Upgrade
Activities
This section describes the constraints related to the upgrading of embedded software in XDM V9.1, and
provides the details required to perform post-upgrade activities.

5.1 General Upgrade Information

Versions for
V9.1R1.0 Upgrade V8.2R4 V8.3R1 V8.4R2 V9.0R1
EMB Up to 82.216 83.112 84.115/118/122 90.060
EMS 82.420 83.137 84.203 21.150

Use the upgrade table from the upgrade procedure only. See the upgrade document for more information.

NOTE: Before upgrading to V9 and above, the NVM of XMC-R must be upgraded to 512MB.
The pre-upgrade check will fail for XMCP-R with a smaller NVM size.

ECI Telecom Ltd. Proprietary 5-1

XDM® Release Notes Upgrade Constraints and Post-Upgrade Activities

5.2 Traffic-Affecting Activities

The following table summarizes which cards must be reset during the upgrade from V9.0 to V9.1 R1 or
might need to be reset at a later date to enable certain functionalities.

Upgrade from Card Requiring FPGA ID FPGA Upgrade Reason for Change
Version Reset Requirement
V9.0 TPM2_63_3 0x6 Mandatory 73-473449 Fix BIT of
test pattern
V9.0 EISMB 0x15 Mandatory Fix problem in
DIOM\EISMB,
CHAVIV I2C
machine that was
redesigned to cope
with simultaneous
accesses of
difference SW
processes.
V9.0 MCS30/X 0x15 Mandatory  73-469895: I2C
does not
recognize the
actual type.
 I2C machine
was replaced
with Chaviv2

ECI Telecom Ltd. Proprietary 5-2

XDM® Release Notes Upgrade Constraints and Post-Upgrade Activities

The following table summarizes which cards must be reset during the upgrade from V8.2 R4 to V9.1 R1 or
might need to be reset at a later date to enable certain functionalities.

Upgrade from Card Requiring FPGA ID FPGA Upgrade Reason for Change
Version Reset Requirement
V8.2 R4 MXC300/SB 0e Mandatory 73-450985 Fix TMU
UART state
machine. In very
rare cases customer
can lose
communication0xC
header
V8.2 R4 MCSX 12 Mandatory 73-448908,
73-449088,
73-449306: On 10G
ETY UNI port (which
is connected to 10G
ETY UNI port of
MCS -50 ) after OTR
extract and reinsert
SWERR “OptParams
record in IDPROM
isn't correct” is
observed and card
takes cold reset.
Type mismatch
alarm observed on
ETY ports after MoE
port configuration
V8.2 R4 SIM 4_8, SIM16_8 120 Mandatory 73-447606:
XDM900 (AUX300B) 1e unexpected single
interrupt after FPGA
loading
V8.2 R4 DIOM 0x26 Mandatory 73-475918 OTR64 &
OTGBE modules are
not detected in
shelf stably after
new installation (Fix
I2C problem when
accessing SFP)
V8.2R4.3 and below xMCP_R 1C Mandatory xMCP_R
occasionally reset
itself due to power
supply (2.1v)
fail.(73-452765)

ECI Telecom Ltd. Proprietary 5-3

XDM® Release Notes Upgrade Constraints and Post-Upgrade Activities

Upgrade from Card Requiring FPGA ID FPGA Upgrade Reason for Change
Version Reset Requirement
V8.2R4.2 and below MCS5 Mandatory  1. traffic
MCS10 problem in
DIOB MCS5/10 and
DIOB across
India - EOS in
Bank B gets TLC
and LOPR
alarms
73-451825
(Clean FPGA
wrong values)
 2. 73-447782:
"watch-dog"
Reset
V8.2R4.2 and below MCSM Mandatory 73-447782:
"watch-dog" Reset
for MCSM cards
around 5-10
minutes
V8.2 R4 TPM2_63_3 0x6 Mandatory BIT rising after
upgrade. altera SW
R/W operation
failure
V8.2 R4 EISMB 0x15 Mandatory 73-475918 OTR64 &
OTGBE modules are
not detected in
shelf stably after
new installation

ECI Telecom Ltd. Proprietary 5-4

XDM® Release Notes Upgrade Constraints and Post-Upgrade Activities

The following table summarizes which cards must be reset during the upgrade from V8.3 R1 to V9.1 R1 or
might need to be reset at a later date to enable certain functionalities.

Upgrade from Card Requiring FPGA ID FPGA Upgrade Reason for Change
Version Reset Requirement
V8.3 R1 MXC300/SB 0c Mandatory 73-450985 Fix TMU
UART state
machine. In very
rare cases, the
customer can lose
communication 0xC
header
V8.3 R1 DIOM 0x26 Mandatory 73-475918 OTR64 &
OTGBE modules are
not detected in
shelf stably after
new installation (Fix
I2C problem when
accessing SFP)
V8.3 R1 MCS30/X 0x15
Mandatory Type mismatch
alarm observed on
ETY ports after MoE
port configuration
V8.3 R1 TPM2_63_3 0x6 Mandatory BIT rising after
upgrade. altera SW
R/W operation
failure

ECI Telecom Ltd. Proprietary 5-5

XDM® Release Notes Upgrade Constraints and Post-Upgrade Activities

The following table summarizes which cards must be reset during the upgrade from V8.4 R2 to V9.1 R1 or
might need to be reset at a later date to enable certain functionalities.

Upgrade from Card Requiring FPGA ID FPGA Upgrade Reason for Change
Version Reset Requirement
V8.4R2 CPTS240
(HLXC768H)
Hybrid user only 0c Mandatory Packet switch
protection. add new
fields that show last
protection switch
cause
V8.4R2.0
(fix in 84.115) SIO64_2/1D
XDM1000/ 3000 0x26 Mandatory XDM3000 DCC
BLOCK: swap
between bus2 &
bus3 .
DIOM 0x15

NOTE: All data cards are reset (warm reset) during the upgrade (traffic-affecting).
Use the updated list of resets from the upgrade procedure

ECI Telecom Ltd. Proprietary 5-6

6 Operational Notes and Limitations
This section describes the known limitations of the current release of XDM V9.1.

6.1 Known Limitations

Cluster Waivers/Limitations Will be Supported in Version
Data 73-484235 - LOS alarm is coming on MCS equipment in V9.2R1
addition to LOS alarm on MCS port
Data No support for UPM for new V9.0, V9.1 data objects. V9.2R1
Data No History PM for BFD and 1:1 LSP protection objects (only V9.2R1
current PM is supported)
Data OAM protocols limitations per MCS50/MCSM50: maximum V9.2R1
host budget is 1800 pps can be used for example for:
Maximum of 50 fast OAM + 400 Slow OAM sessions or
maximum of 900 slow OAM sessions. Slow: 1sec interval, Fast:
100msec interval
Data ERP for MPLS single gateway V9.2R1
Data H-VPLS with S_VLAN tunnels V9.2R1
Data Y.1731 is interoperable with NPT V3 and BGF V16, for NPT V9.1R2
V2.1 and BGF V15.1 please use updated versions – V2.1.33
and V15.1.10
73-484723 Y.1731 - When doing IOP switch- no notification is sent and V9.1R2
CFM pm fails
73-485558 In CFM PM: SLM not working when 3 or more sessions are V9.1R2
enabled.
73-485644 DM sender can't get DmrRxBwd, np2- sender, np4-responder V9.1R2
73-485898 Multicast traffic drops after editing protected Transit tunnel V9.1R2
73-485800 Getting BIT Failed on NVM of Standby MXC After Upgrade to V9.1R2
V9.1 Released Version from 8.2R4
73-485823 Value change of "UPM Collection Mode" V9.1R2
73-485932 UPM counter not collects for AU4, VC4, TU3 and TU12, if V9.1R2
MSPL 1+1 protection port is active.

ECI Telecom Ltd. Proprietary 6-1

7 Resolved Issues
This section describes the issues that have been resolved in the current release of XDM V9.1.

Reference No. Description

73-479025 ME_12 SFP ports 5 to 12 (EMS GUI ports 113 to 120) can host only optical
interfaces
73-478354 RSTP VSI: Editing unprotected RSTP Vi tunnel to protected fails.
73-478772 Huge PM is not working for secured NE
73-476777 PDH card IOP info & attribute propagation not proper

ECI Telecom Ltd. Proprietary 7-1

8 Known Issues
This section describes the issues that have been identified in the current release of XDM V9.1.

Reference No. Description Workaround/Comment

Embedded Software
Data EoS/MoT ports can be renumbered during migration Please follow the migration
(relevant for MCS10/M ports from Bank B/D) procedure for full details
73-481277 Adding/Removing CoS from a tunnel in rare cases may
cause up to 500ms hit to other CoSs
Data For migration process with IOP on XDM900, traffic hit
will be beyond IOP switching time
73-481997 PSI outgoing congestion of 2 tunnels low CoS, diff MoF.
Bad distribution between BW ranges 1 and 3. This is
the known problem of statistic memory accesses
ASTN ASON upgrade - will be supported only from V8.4
Data Up to 1600 Head XCs with Tunnel OAM
Data 8 Priority queues toward CPU are supported only for
NP-4 based cards
73-482205 MCSM to MCSM50 card migration: in EOS ports
assigned bank B goes down immediately after DB
translation is over in EMB.
Data No automatic roll-back in case of failure during the use manual procedure
process
73-483022 MCS10 to MCS50 card migration: Comment given on to be saved & restored manually
ETY ports is not restored after migration.
73-485325 In V9.1, Y.1731 sessions (DMM and/or SLM) If at least Should ideally be configured with
one DMM or SLM session is configured with a packet packet sizes within the range of
size greater than 75 Bytes, the number of DMM/SLM 64-74 Bytes.
sessions per MCS card must be limited to:
DMM/SLM Max # of Max # of
packet size sessions* @ sessions* @
period=1000 sec period=100 sec
512-75 B 128 12
2000-513 B 32 3

ECI Telecom Ltd. Proprietary 8-1

XDM® Release Notes Known Issues

The following issues were found before V9.1 R1 and are still relevant in this release.

Reference No. Description Workaround/Comment

Embedded Software
General No SONET support as of V8.3
Data MCSM50 SFP+ ports 9 to 12 (EMS GUI: 109 to 112) in
1GBE mode must be used with Auto-Negotiation
disable
MSPP xMCP-R NVM Size before upgrade to V9, and above
NVM of XMC-R must be upgraded to 512MB.
Pre-upgrade check will fail for XMCP-R with smaller
NVM size.
MSPP No LCT support for XDM100 to 300 migration
73-466395 MCS50 configured with 3 P2P VSI with All/Other Configure specific VLANs
configuration will result cold reset of 30 minutes
73-473657 1G SFP may not be operational after insertion to Re-assign port
73-476448 ME_12
73-475598 ETGBE as LLCF Client takes 2.5 sec to restore due to Use optical interface
Auto-Negotiation
73-475861 NPT1600C: 13 minutes loss of traffic when performing Less objects may give better
power down/up to NE results
73-477779 BSC traffic with cos 7 is dropped when BSC profile is Use specific values (e.g. 10G)
unlimited and color mode = true and CM: False
73-478354 Editing tunnel associated with RSTP VSI from Create new protected tunnel
unprotected to protected fails and associate it with the
RSTP VSI
73-479153 MCSX-30 Ingress policer with CIR>0; EIR=0) doesn't Configure EXP yellow
drop yellow traffic when EXP yellow is unmapped mapping
73-453076 Long hit times in SNCP in MCS-X
73-475445 MS-SPRing Traffic goes down during HLXC768 to After the TMU switch, it is
CPTS240 Migration. required to have 12 minutes
before disabling MS Spring
and then start the matrix
replacement
73-478870 DCC Link Fail Alarm is not Observed on Clear Channel User need to monitor it.
DCC in XDM900. Clear channel when there are
reports on DCN problems
73-447692 Alarm Severity attributes of the AU4 object changed User should verify manually
automatically to the default definitions after switching that all Alarm Severity's of
back to provisioned path. each AU4 object that was
rerouted and returned, are
provisioned according to
definition

ECI Telecom Ltd. Proprietary 8-2

XDM® Release Notes Known Issues

Reference No. Description Workaround/Comment

73-451977 After reset of ACP, Head End NE failed to find a User needs to perform a
restoration path for localization trail. manual maintenance reroute
for the trail, since it is a rare
case of ACP reset and fiber
cut simultaneously
73-451771 Edit XC on MCS and try to remove members via EMS in
LCAS mode; causes a traffic hit of 2-3 seconds. Editing
the XC via LS NMS is hitless.
73-453130 In V8.3 the MCS50 card supports only cold reset mode.
73-453206 MCS50 AutoNeg doesn't work on 1G ports, the default
configuration of the ports is disabled
73-453650 LCT: MCS PE ID is incorrectly displayed in the FDB
table.
73-453739 MCS30 card for 8.12 operates in 16 port mode, for 8.3
it must operate in 32 port mode. During upgrade the
card is automatically changed to 32 port mode and
must undergo cold reset. In total, MCS30 boot-up time
is around 7 minutes.
73-456458 When LAG is configured on MCS cards, the port
mirroring is limited as follows:- Only traffic from LAG
Master port is mirrored
In Ingress port mirroring - All traffic transmitted to LAG
Master, and Slave ports are mirrored in Egress port
mirroring
73-457047 When configuring Far End loopback on MCS50 card,
the status of the port is down although the port is up
73-414333 Detected RDI alarm gets cleared from the MS User needs to monitor the
Protection object when a maintenance action is RDI alarm before doing
performed. maintenance action.
73-449487 XDM50: HIT on 2M trail during warm reset of MXC
73-450517 XDM900: QB = SIM16_8 mix. LOS on port #7
73-440786 XDM-300: SfMxccmnBoardHolderSetBITToBus: BIT
writing delay exceeds13 sec.
73-446362 Deleting 6000 XCs creates ENMPM core.
73-446683 It is possible to delete TE link on which a 1+1+R trail It is not allowed to delete TE
provisioned, if the trail is in reroute states link if there are trails in
reroute mode
73-445283 XDM-900 with MXC300: Unable to retrieve the FDB
table in both MCSM and EISMB.
73-445746 After a few resets on MXC900, it was observed that
there is continuous hit of DIO-MCSX traffic. EOS port
DIO does not transmit traffic.

ECI Telecom Ltd. Proprietary 8-3

XDM® Release Notes Known Issues

Reference No. Description Workaround/Comment

73-445750 Only during migration from MXC300 to MXC900, When
switching from MXC900-A to MXC900-B, an 11s traffic
hit between EISMB-MCSM was observed.
73-445816 MXC900: 7 sec traffic hit on EISMB card when
performing Warm Reset.
73-448426 PM log files are being modified when copied from Convert PM logs files to ASCII
EMS-XDM SPARC to EMS-XDM x86. in EMS-XDM SPARC and send
to EMS-XDM x86 via FTP.
73-440322 In Dual Homing - ERP topology disabling the CCM on Disable CFM alarms before
one ERP VSI can cause loops in the ring disabling the CCM.
73-435958 TST 1+R with MSP 1+1: reversion time more than 50 User should repair main MSP
ms link first and then ensure
that the reversion switch is
less 50 ms.
73-437253 TST silver: Wrong protection path of provisioned XC After restoration of TST
after reroute for both provision types. Silver with both links in the
edge, the presentation of the
provisioned protection path
should be ignored.
73-422444 Destination PE and SHG sorting functions (in the
Remote PE List) are not working properly.
73-434301 Failure in VSI creation, where the user is able to set a
SHG value different from "1" for RSTP.
73-430349 Hammer icon is not displayed on the standby ACP1000 The maintenance
when a maintenance action is performed on it. information regarding the
ACP 1000 can be found
inside the maintenance info
window.
73-409145 The clock icon of SSM NEs does not disappear after 1. Open the NE shelf.
upload is over following upgrade. 2. Access the timing window.
3. Close the NE shelf.
73-407899 After releasing Facility Loopback, the hammer icon is Close the card's internal
still present on the STS-3C-Snk object. window and reopen it; the
hammer icon is not present.
73-408080 C-VLAN Translation and CoS Translation cannot be Do not configure
operated together with Egress filtering. CoS/C_VLAN translation and
Egress filtering at the same
time.
73-408169 EMS cannot send Loopback/Link Trace to local MAC There is no message.
address.
73-405129 When creating EoS/MoT with VC-4s, all attempts to Delete the oldest VC-4 and
add VC-12s at a later stage fail. add the VC-12.
73-280684 EMS session hangs when trying to set LO squelch for a
node which is disconnected.

ECI Telecom Ltd. Proprietary 8-4

XDM® Release Notes Known Issues

Reference No. Description Workaround/Comment

73-396536 After configuration of 8K VSIs, 16K policers, 16K Open the policer profile list
C-VLANs, and 8K tunnels per MCS10 card and Full and view the policer from
Upload of 8 cards, the policers in the VSI are created there.
without any policer profile.
73-274946 XC set per object does not work on the OPS port in
SIM1_4/0, SIM4_2, SIM16_1, SIM4_4, SIM1_8.
73-275897 XDM-300: Section EXT DCC endpoints become disabled
when the user deletes the corresponding topology
links.
73-276215 MSP 1+1 icon does not appear in shelf after it was Open the info window of the
created via LCT. card.
73-275665 MCSM Local port: TCA of Rx buffer overflow 15 min is TCA for Rx Buffer overflow is
enabled for monitoring. However, the alarm is never not supported on MCSM GE
raised. port. User must not enable
Alarm for monitoring.
73-275961 MCS card: Unable to see the policer in the policer list User can open the list per NE
when opened from the shelf. and filter it.
73-276043 MCS: Cannot configure the Switching mode = PE and 1. Change the Switching
PE ID at the same time. mode to MPLS PE first and
click Apply.
2. Allocate a PE ID to the card
and click Apply.
73-276188 MCS: TCA of Error Octets 15 min is enabled for TCA for Error Octet is not
monitoring on MPLS ports (MoT). However, the supported on MoT ports.
relevant PM counter is NA. User must not enable Alarm
for monitoring.
73-277044 Sometimes user may fail to create a tunnel with a long Limit Customer Name in
Customer Name. tunnels to 31 characters.
73-277267 When changing from MCS5 to MCS10, reassigning the Occurs only in reassignment.
card name is still shown as MCS5 in huge PM logs.
73-275557 SONET STS-1_SPE object gives "DEG" alarm when error
is injected at "EXC" threshold.
73-275870 SONET/OC-192 with FEC: UASFE counter does not
increase in case of fault at the far end.
73-276290 SONET: The LCT enables user to define unsupported These NE types are not
NE: XDM-100B and XDM-100BU. supported in V7.15 and
should not be configured.
73-276803 PIO345_DS3: SF and SD values are overlapping for
STS-1_SPE sink object.
73-266383 In XDM-300, the "Clear channel Support" icon appears Ignore
on the PIM345_3E3 card in slot I3 and I7 while it is not
supported.

ECI Telecom Ltd. Proprietary 8-5

XDM® Release Notes Known Issues

Reference No. Description Workaround/Comment

73-266929 In the Maintenance Info window, when a user Release the still open active
manually selects a large number of maintenance operations manually.
operations and tries to release them, all the selected
operations are not released.
73-267239 Clear Channel: TP does not appear in IP Networking
table. Thus, PM is not possible from LCT.
73-267625 Associate option grayed out for configuring the IOP 1:2 Need to create IOP as 1:1
for PIM 2_63 cards. Associate option grayed out for twice with same SB and
configuring the IOP 1:2 for PIM 2_63 cards. different Main cards. First
create IOP as 1:1 twice with
same SB and different main
cards.
73-267983 Recreation of Default Route is not possible. Deletion of Default Route is
required when using OSPF.
73-271919 GCCO XC cannot be deleted from the XC list. Delete GCC0 XC from the
card internal window.
73-268886 MCS: Able to configure threshold (TCA) of Outwired Do not use.
Ratio ppm for Bypass Transit and Head Tunnel. TCA is not applicable for
Bypass XC.
73-269930 MCS: Alarm of OAM is enabled for monitoring P2P Do not activate "OAM
Transit Unprotected/Bypass tunnels. enable" for P2P Transit
unprotected or Transit
bypass tunnel.
OAM alarm is not applicable
for these tunnels.
73-270158 MCS-LCT: VSI has no current alarms window. VSI current alarm can be
seen in the NE Alarm list.
73-272780 In MCS cards, it is possible to configure a threshold for Do not configure threshold
Rx Error Octets even though the Relevant TCA and PM for Rx Error Octets.
Counter is not applicable.
73-272782 MCSM Local port: TCA of Error Octets 15 min is TCA for Error Octet is not
enabled for monitoring. However, the alarm is never supported on MCSM GE
raised. ports.
73-272832 MCS FRR: Traffic lost when protected port is disabled Disabling MoT port from
and, after enabling the port, the traffic goes on bypass. management station does
not trigger FRR nor disable
bypass tunnel. User must not
disable MoT port when FRR
is active.
73-272890 MCS: Power failure alarm is present on Optical SFPs. In Alarm Severity, an Alarm
of Power failure is mistakenly
present when this alarm is
not relevant for optical SFPs.

ECI Telecom Ltd. Proprietary 8-6

XDM® Release Notes Known Issues

Reference No. Description Workaround/Comment

73-272936 MCS: Resetting daily PM counters resets Tx PM Resetting Daily PM counters
counters of 15 min but not Rx PM counters of 15 min. does not affect the 15 min
RX PM counters.
73-273121 MCS: Rx Oversize Pkts and Rx Pkts PM counters are not Due to hardware chip
counted when the max. frame size is kept as 64 and a limitation (Ravel Mapped),
packet of size 255 is sent from the TEQ. when configuring the max.
frame size 256 works fine
regarding drop and oversize
frame
73-273742 MCS: Usage state of policer profile is not present. A In LCT, a policer profile in use
wrong message is displayed while deleting a policer does not show its usage
profile in use. In LCT, a policer profile in use does not state; when trying to delete
show its usage state; when trying to delete the policer the policer profile, the wrong
profile, the wrong message appears preventing profile message appears preventing
deletion. Message should be: "Policer profile in use, profile deletion. Message
cannot be deleted". should be: "Policer profile in
use, cannot be deleted".
73-259642 When forcing a manual IOP switch of a PIM2_63 The user must make sure
module while an SNCP window related to an endpoint that the SNCP window is
in the same card is open, the IOP keeps toggling. closed while forcing IOP
switch of a PIM2_63.
73-260316 In SONET mode, when the XFCU is out and there is an In SONET mode, the user
alarm master mask, this alarm is not reported in the must not apply master alarm
invisible alarms list. masks to the xFCUs.
73-260724 LCT allows the user to create Ext DCC XC, even if not Does not work in embedded.
supported.
73-264603 In Edit Mode for Timing Configuration when applying 2 Reopening Timing
MHz and PRS quality for T3-1, when applying T3-1 as Configuration resolves this
1st Priority, after two TMUs are synchronized with issue.
T3-1, return 1st Priority to Internal. If you wait for two
TMUs to be synchronized with Internal and try to
change T3 Input configuration from 2 MHz to None,
the edit configuration is rejected. The message quotT3
input type cannot be changed because active
sourcequot appears.
73-263974 If MS-SPRing and revertive SNCP are defined in the Once the problem that
same shelf and both protection schemes are initiated caused the SNCP switch has
due to failures, the revertive mechanism of the SNCP been fixed, a manual
does not work. switchback must be
performed.
73-259483 C_TRP25_2C: When the user is reassigning a OTR25XX For the OPS side, when the
to an OTC25XX, in the card internal window, the actual user assigns the expected
wavelength in nm is not updated and displays an value, the problem
invalid value, and in the OPS side of the card, the info disappears.
window of the module also displays an invalid value of
Expected channel (THZ).

ECI Telecom Ltd. Proprietary 8-7

XDM® Release Notes Known Issues

Reference No. Description Workaround/Comment

73-263925 After changing the CMBR10_T card to Standby mode, When defining protection for
the XCs in the new card do not exist. CMBR10_T, first assign the
card and close the XC
window. Then, reopen the
window and assign the card
as Standby.
73-264297 When performing a XC in a card from type ROADM Opening the XC list (or
from LCT, the "Channel XC" window is not updated. right-clicking the card and
selecting "Get XC per
Object") updates the XCs
reopen window.
73-257754 If the Slip cable is directly removed without the proper
logout via LCT, the message CONFIG Token available
with LCT is shown in the EMS.
73-258903 The Action History does not define the NE name when
the Interface Gateway is being updated.
73-264302 In the XDM-100 EISMB card, after XDM-100 shelf Reset Take into account when
Counters, the GFP Sink counter retains the old values. resetting the counters in this
card.
73-258276 RSTP window: Apply is grayed out until another line is If changing the Path cost
selected after changing free text attributes. (free text), the user has to
select another line in order
to make the Apply icon
available (until then it is
grayed out).
73-259004 In the topology tree, the right slot does not disappear Ignore.
if the left slot was assigned to a wide card (double slot
width like SIO64).
73-259110 In an XDM-100 with MXC100B cards, when a near end
loopback is applied to an SNCP link whose main path is
via the SAM16_1B of slot B, a traffic switch is caused.
73-259318 For BLSR ring info window in SONET mode, BLSR In this case, if West is
east-west attribute displays the incorrect value in the displayed, it is in fact East.
line source object for the east side.
73-259482 C_TRP252c_AD: When the user is reassigning an When the user assigns the
OTR25xx card to an OTC25xx, in the OPS side of the expected value, the problem
card, the info of the module displays the wrong disappears.
wavelength values by default.
73-259872 The shelf view shows both xMCP_B Main and SB cards Close the NE and right-click
as active when the SB xMCP_B card is active and the the NE in the EMS main view
Main card is extracted and reinserted. and select Upload NE data.
After upload, open the NE. It
now shows SB xMCP_B card
as active.

ECI Telecom Ltd. Proprietary 8-8

XDM® Release Notes Known Issues

Reference No. Description Workaround/Comment

73-260204 In PIO345_16, the STS-1 terminal loopback does not
work under SONET mode.
73-260468 OADM4REW: In this card, after the user has changed Closing and reopening the
the side from left to right, he cannot change the side window helps.
back again (right to left) instantly. He has to close and
reopen the window.
73-260611 The system title is not updated in the topology tree Update the name from the
when the name of an NE is changed from the LCT. EMS again and it will be OK.
73-260964 With ROADM card, in case of multichannel port, in In the event of edit, the
Power Attenuation window, the NoC field should not action and all subsequent
be editable on a single channel port. actions fail until the window
is closed and reopened.
73-263233 When unassigning CMBR10 that was first assigned with Despite the failed message,
LCT-XDM, the displayed message is "Cannot assign unassign is performed.
card".
73-263260 LCT-XDM: Auto-connect feature does not work for NEs For these NEs, connect
where a password has been introduced. manually by inserting the
password.
73-251598 On XDM-100, when both MXCs have a hardware
problem, there is an infinite loop of redundancy
switches.
73-252695 RS and MS DCC cannot be configured on the same
interface.
73-254874 XMCP-B: When the NVM is extracted and a cold reset The user must not perform
is performed on the xMCP, it does not pass the boot cold reset to the xMCP-B
state. when the NVM is extracted.
If it happens, the user must
reboot the xMCP-B by
extracting and reinserting
with the NVM inside.
73-255044 XDM-40 supports only six external I/O alarms; the 7th Ignore the 7th and 8th
and 8th must be removed from table. alarms in EMS.
73-259922 Incorrect colors of Stand-By/Maintenance icons in EMS user can see the status
associated working and standby protected cards (TRP of the cards from their info
and CMBR). window.
73-119361 Incorrect indication about pass-through non-SNCP XC
squelching is generated.
73-116585 The PM counters are not automatically reset after The user may perform a
MS-SPRing switch. manual reset if necessary or
ignore the first counting
session following the switch.
73-120519 A resource used as part of a unidirectional TU3 XC The attempt fails.
appears as free when attempting to create a
bidirectional XC of the same rate.

ECI Telecom Ltd. Proprietary 8-9

XDM® Release Notes Known Issues

Reference No. Description Workaround/Comment

73-121991 DCC XC sets (XC with one XC ID and different XC rates) Edit them from the EMS
with two XCs created from the EMS cannot be edited
from the LCT.
73-251476 Active XMCP was changed from C2 to C1 after power
down due to the different RAM sizes of the two xMCP
cards (main and standby).
73-252120 SIM1_4O/E can be assigned incorrectly as SB in IOP in
XDM-100.
73-114291 Creating XC while the related traffic card is in warm Setting the Master Mask to
reset state results in AIS generation. On solves the problem.
73-108899 Under MXC redundancy, when timing is handled by the Workaround: Manually
standby MXCs, the TMU and the active MXC is switch the TMU before
manually switched to standby, errors occur in I/O cards switching the MXC.
(for less than 10 ms).
73-104270 When the lock of the MXC is opened and closed Non TA Workaround: When
without taking out the MXC, the TMU is unable to get performing maintenance
the configuration and does not report alarms. activity on MXC (opening the
lock), the card must be
extracted or cold reset must
be performed on the MXC.
73-80617 When defining a new XC, the first PM count of the Upon definition of a new XC,
counters related to that XC may start from a value the counters must be
other than 0. initialized.

ECI Telecom Ltd. Proprietary 8-10

9 Related Publications

9.1 XDM Converged MSPP and All-Range ROADM

(All Platforms)
Manual Type and File Name Drawing No. Cat. No.
General Description (GD)
XDM V9.1 (H) GD 417006-2002-0H3-D08 X91220

9.2 XDM-1000 Product Line

Manual Type and File Name Drawing No. Cat. No.
Reference Manual (RM)
XDM-1000 PL V9.1 (H) RM 417006-2710-0H3-B05 X91221
Installation and Maintenance Manual (IMM)
XDM-40 V9.1 (H) IMM 417006-2309-0H3-B05 X91222
XDM-450 V9.1 (H) IMM 417006-2317-0H3-A05 X91223
XDM-500 V9.1 (H) IMM 417006-2304-0H3-B05 X91224
XDM-1000 V9.1 (H) IMM 417006-2305-0H3-B05 X91225
XDM-2000 V9.1 (H) IMM 417006-2306-0H3-B05 X91226
XDM-3000 V9.1 (H) IMM 417006-2315-0H3-B05 X91227

9.3 XDM-100 Product Line

Manual Type and File Name Drawing No. Cat. No.
Reference Manual (RM)
XDM-100 PL V9.1 (H) RM 417006-2709-0H3-B05 X91228
Installation and Maintenance Manual (IMM)
XDM-100 V9.1 (H) IMM 417006-2301-0H3-B05 X91229
XDM-300 V9.1 (H) IMM 417006-2311-0H3-B05 X91230
XDM-900 V9.1 (H) IMM 417006-2318-0H3-A05 X91231

ECI Telecom Ltd. Proprietary 9-1

XDM® Release Notes Related Publications

9.4 All XDM Shelves

Manual Type and File Name Drawing No. Cat. No.
System Specifications (all shelves)
XDM V9.1 SYSTEM SPECS 417006-2009-013-A05 X91233
XDM and BG Accessories Catalog
Transport_Packet_Products_Accessories_Catalog_Ma 417006-2908-083-A00 X91236
rach-2014

9.5 XDM Documentation CD

CD Name Drawing No. Cat. No.
XDM V9.1 (H) DOC. CD 417006-C908-H3-A00 X91298

ECI Telecom Ltd. Proprietary 9-2

10 Technical Assistance
If you have questions or concerns about this release note, contact the relevant product manager.
If you require installation personnel to perform the actual installation process, or if you are interested in
obtaining design assistance or a network installation plan from ECI Telecom's Customer Support team,
contact your ECI Telecom sales representative.
For any support-related issues, technical or logistic, contact the ECI Telecom Customer Support center at
your location. If you are not familiar with that location, contact our central customer support center action
line at:

Telephone +972-3-9266000
Telefax +972-3-9266370
Email on.support@ecitele.com
Website http://www.ecitele.com/

ECI Telecom Ltd. Proprietary 10-1