9500 MPR Rel 1 4 Product Release Note

9500 MPR V1.4.
0
Product Release Notice
3DB18715AAAA FMZZA, February 2010
Product Release Notice, Version 1.4.0
All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval
system, or translated into any language or computer language, in any form or by any means, electronic, magnetic,
optical, chemical, manual or otherwise, without the prior written permission of ALCATEL-LUCENT and or its
licensors.
DISCLAIMER
ALCATEL_LUCENT makes no representation or warranties with respect to the contents hereof and specifically
disclaims any implied warranties or merchantability or fitness for any particular purpose. Further, ALCATEL-LUCENT
reserves the right to revise this publication and to make changes from time to time in the content hereof without
obligation of ALCATEL-LUCENT to notify any person of such revision or changes.
ii
Product Release Notice, Version 1.4.0
RELEASE NOTICE ORGANIZATION

The following major topics are covered in this Release Notice:
SCOPE AND PURPOSE .............................................................................................................................. 1

NEW FEATURES ....................................................................................................................................... 2
SOFTWARE UPGRADE PROCESS ............................................................................................................... 9
SOFTWARE COMPONENTS .................................................................................................................... 10
USAGE NOTES ....................................................................................................................................... 11
KNOWN RESTRICTIONS.......................................................................................................................... 15
RESOLVED ISSUES.................................................................................................................................. 17
SYSTEM REQUIREMENTS ....................................................................................................................... 19
SUPPORTED SW ITEM............................................................................................................................ 20
SUPPORTED HARDWARE ....................................................................................................................... 23
iii
9500 MPR Product Release Notes, Version 1.4.0
SCOPE AND PURPOSE

This document provides product release information on supported functionality, compatibility, and
known customer affecting issues, relating to the released software versions.
Please read these notes before reporting any issue to Alcatel-Lucent.
The intended users of this document are:
Alcatel-Lucent Customers
Alcatel-Lucent Value Added Resellers
Alcatel-Lucent Value Added Service Providers
Alcatel-Lucent Product Support staff
Alcatel-Lucent Field Service staff
Page 1
NEW FEATURES
The following sections describe the new features introduced in release 1.4.0 compared to MPR 1.3.1
Synchronization
Synchronous Ethernet
Synchronous Ethernet provides a mechanism to transfer frequency over the
Ethernet physical layer as specified by G. 8261. Performances are defined in
G.8262 and replicate those achievable from SDH transport networks, allowing as
a migration path from TDM to Ethernet for service delivery. Furthermore, as
such solution uses the physical layer, it is immune to traffic load and packet
delay variation.
The entire six user Ethernet interfaces of the 9500 MPR core card are
Synchronous Ethernet interfaces (both electrical and optical). Current
release manages only one of the two available optical interfaces.
Synchronous Ethernet is supported for electrical ports in 1000 BaseT mode
only.
Each interface might be configured to work in either non-synchronous or
synchronous operation mode. Default mode is non-synchronous.
A Synchronous Ethernet interface configured in non-synchronous mode is
an interface that does not participate to the synchronization network and is
functionally identical to an asynchronous interface as defined in IEEE 802.3.
A synchronous Ethernet interface configured in synchronous operation
mode extracts the frequency of its input signal and passes it to the system
clock. In the particular case of electrical User Ethernet interfaces, the auto
negotiation parameters allowed are: Speed=1000 Mbit/s and Mode=Full
Duplex). The clock role (master/slave) shall be configured in order to
properly use the synchE interface.
SynchE is an additional option as synchronization input or as
synchronization output.
o When synchE option is used as synch source option, the synchE
physical interface clock role (see previous bullet) has to be
configured as slave.
o When synchE option is used as synch-out to deliver synchronization,
the synchE physical interface clock role (see previous bullet) has to
be configured as master.
In case 9500MPR is used as master node from synchronization point of view,
synchE ports can be used as:
o Primary reference clock source
o Secondary reference clock source (being used for primary clock
source another synchronization input)
o One port as primary clock source and a second port of the same
core card as secondary clock source.
In case 9500MPR is used as slave node from synchronization point of view,
synchE ports can be used as:
Page 2
Primary reference clock source

Secondary reference clock source (being used for primary clock
source another synchronization input)
o One port as primary clock source and a second port of the same
core card as secondary clock source.
o Typical application is the interconnection of two MSS4/MSS8
shelves in stacking configuration
SynchE can be used with MPR working in Hybrid mode or in Packet mode
SSM messages are not managed in this release.
o
o

E1 clock recovery
Node timing
This feature (called either network clock re-timing or node timing or,
according to G. 8261 wording, network-synchronous operation for service
clock) introduces an additional possibility to recover E1 clock.
Node timing is a way to recover TDM clock quite popular in the industry of
service routers and site aggregator boxes; this feature inside the 9500 MPR
platform is adding interworking capabilities with third parties service routers
and circuit emulations gateway.
In node-timing working mode, all the E1s are re-sampled with the network
element clock
Node timing is applicable both to MPR working in hybrid mode or MPR
working on packet mode. Recovered E1 clock is according to G. 823
synchronization masks
Node timing option, once selected, is applied to all the E1s belonging to the
same 32E1 PDH card
The available clock recovery techniques in hybrid mode (TDM2TDM profile)
are:
o DCR: differential clock recovery
o Node timing
DCR working mode is selected disabling node-timing feature. Default is
node-timing disabled (so default is DCR)
The available clock recovery techniques in packet mode (TDM2ETH profile)
are:
o ACR: adaptive clock recovery
o DCR: differential clock recovery
o Node timing.
DCR/ACR working modes are selected disabling node-timing feature. It
should be noted that, if node-timing is enabled, Craft Terminal still propose
the possible selection among ACR and DCR: in this specific case, the
meaning of this option is not related to the clock recovery algorithm, but
rather to the MEF8 frame format (choosing DCR the MEF8 RTP field is
inserted, while choosing ACR the RTP field is NOT inserted).
The selection of the clock recovery type has to be common for all the E1s
belonging to the same 32E1 PDH card, independently if node timing has
been enabled. Examples of possible admitted configuration
o Mix in the same card of TDM2TDM and TDM2ETH profiles (with
DCR) with node timing disabled
DCR) with node timing enabled
Page 3
Examples of not admitted configurations:

ACR) with node timing disabled
ACR) with node timing enabled
o Mix in the same card of TDM2ETH profiles (with ACR) and TDM2ETH
profiles (with DCR) with node timing either disabled or enabled
In the same NE it is possible to mix 32E1 PDH cards with E1s configured in
DCR and 32E1 cards with E1s configured in ACR.
Modem profiles
256QAM@56 MHz

Core protection
256QAM@56 MHz modem profile has been added, in static modulation.

It is supported by Modem300 card (3DB18136xxxx) and not by Modem300
EN card (3DB18538xxxx)
It is supported only with ODU300 with integrated lightening arrestor (with
ALU part number with H as first letter, e.g. similar to 3DB23045Haxx see
table 6)
Core protected configurations are built by plugging a Spare Core board into the
reserved slot #2. Spare Core board provides a protection option for the Main
Core failure with backup for:
Built in Ethernet ports
Microprocessor and control platform (management)
Built-in Ethernet Switch.
MPR 1.4 has introduced an additional mode for the protection of the built-in
Ethernet ports (called also User Ethernet ports). While Mode#1 is the default
behaviour of previous MPR releases, Mode#2 has been added to MPR 1.4
release:
o
Mode#1. The User Ethernet ports of the Core in standby status are
switched off at physical layer (PCS/PMA). In case of optical User
Ethernet interface the laser of SFP is also switched off.
o
Mode#2. Static active/standby LAG. The User Ethernet interfaces of
the Core in standby status have the physical layer enabled and the
MAC layer in Blocking state (no forwarding of user traffic). This
behaviour allows reducing the out of service time of user traffic
passing through User Ethernet interfaces in case of Core switching.
In that case, the typical switching time on optical interface is 200
ms.
When activating/de-activating the active/standby static LAG feature
(Mode#2) traffic is impacted (40 seconds) on all the core board Ethernet
interfaces.
This management of User Ethernet interfaces (Mode#2) shall not be used
when the 9500MPR is connected to equipment not supporting static LAG
Active/Standby.
The core switching criteria are the following:

o Core Card Missing
o Core Card Fail
o Control Platform operational status failure
Page 4
o Flash Card failure

While the above root causes were considered in previous MPR releases, the
following additional criterion starting from MPR 1.4 can be optionally added to
the criteria listed above by means of a user configuration at CT:
o LOS of Ethernet traffic.
This LOS of Ethernet traffic is triggered by any of the following conditions:
LOS of any Optical User Ethernet interfaces
Card Fail of any SFP optical modules
Card Missing of any SFP optical modules
LOS of any Electrical User Ethernet interfaces, including the LOS of the
forth User Ethernet interface (either if configured for Traffic or
configured as TMN interface).
The selection of these additional criteria will trigger a core switch in presence
of any of the previous four conditions, both in Mode#1 and in Mode#2.
The usage of this additional criterion should be avoided when performing
installation and maintenance operations in order to not deal with triggering of
Core protection switch during such operations.
In case of LOS alarm present on both the two core cards:
o in Mode#1 the active core is the main
o in Mode#2 the active board is the one in which LOS alarm has been
raised first
Stacking
configuration
Stacking configuration (i.e two MPR shelves interconnected through an Ethernet

cable) can be used to increase the number of ODU300 that can be managed by a
single NE.
Repeater site
HUB site
Access
Access
9500 MPR
9500 MPR
9500 MPR
9500 MPR
MSS-8
Access
Protected or high
capacity backhaul link
Access
Local Traffic
ATM; TDM; Ethernet
Here above a typical network scenariowhere stacking can be useful is depicted:

the hub node has to manage six ODU300 additionally to local traffic cards. Being
the number of slot of an MSS8 limited to eigth, stacking together two MSS8
shelves is a possible solution to increase the number of card managed by a
node.
Page 5
TMN
Shelf 2
Ethernet
Ethernet
TMN
Shelf 1
E1 loopback
In this example the four radios coming from the access are managed by Shelf#1,
while the 1+1 radio going towards the backbone and the local accesses are
managed by Shelf2.
It is possible to stack up to two MSS8/MSS4 shelves; mixed MSS8-MSS4
stacking is allowed as well
Stacking configuration can be implemented with or without core
protection. In case of core protection, Ethernet Interface Criteria for 1+1
EPS core (LOS) has to be enabled.
Operator commands related to core protection have to be applied in
homogeneous way in the two shelves (i.e if a force command is applied to
core of shelf#1, a force command to core of shelf#2 has to be applied as
well)
The interconnection between the two shelves can be done using electrical
or optical GE ports
It is strongly suggested to use Ethernet port#4 to interconnect TMN
If E1s are transported from the radio connected to shelf1, TDM2ETH profile
has to be used, cross-connecting those E1s from radio to Ethernet port of
core card. In shelf 2, the E1s have to be cross-connected from Ethernet port
of core card towards the radio. Please refers to user manual for details
If ATM flows are transported from the radio connected to shelf1, ATM2ETH
cross-connections from radio to Ethernet port of core card. In shelf 2, the
ATM flows have to be cross-connected from Ethernet port of core card
towards the radio. Please refer to user manual for details.
For synchronization distribution, two options can be used: synchE or syncin/synch-out connectors of core cards using dedicated cords. Please refer to
user manual for details.
Number of shelves that can be stacked is 2
In order to improve troubleshooting capabilities, two different E1s
loopbacks have been introduced:
o External, i.e. towards the line
o Internal, i.e. towards to core/radio
The loopbacks can be activated separately on each of the 32 E1 interfaces of
32E1 PDH card.
It is possible to define the duration of the loopback (time-out period);
default time-out is 5 minute
Page 6

Backup and restore
The loopbacks on E1 interfaces are not introducing traffic impact (loop &
continue mode)
Backup
This operation allows the management system (or craft terminal) to get the
configuration stored on the NE. The information that will be stored in the
backup file is the ones stored in the flash memory on the NE.
During the Backup procedure the NE refuses every configuration coming
from the management systems.
The NE refuses the request to perform the Backup procedure when Forced
Switch command related to Core protection is active.
Restore
Restore is the complementary operation of backup. It permits the management
system to download into the NE a configuration information previously backedup. It is mainly used when the operator wants to force a previous configuration.
Before the download of backup file, the compatibility between the software
version of the file that will be transferred to the NE and the NE software
version must be verified. The compatibility between the content of the
backup file and the license key of the NE must be verified as well.
Once the download has been performed, the operator can request to apply
the content of file restored into the NE. Consequently the NE automatically
restarts.
Restore procedure doesn't execute any check in order to apply to the NE
only the differences between the actual configuration and what is stored in
the Backup file.
The Restore procedure affects the delivery of user traffic as long as the
restoring of the backed-up configuration is completed
The Restore procedure can be activated only when the Main Core is in active
status.
Ethernet features
Synchronization
ATM MPLS
interworking
The following features managed through CLI files have been added. Please refer
to user manual for a general explanation of CLI file management approach.
Per flow policer: ingress rate limiter per VLAN, dropping the traffic
exceeding a given CIR value
Broadcast storm control: ingress rate limiter on broadcast traffic
Multicast storm control: ingres rate limiter on multicast
MAC address access control list: only packet with SA inside a given list are
transmitted towards the radio
1.024 MHz clock has been added as option for synch out signal. Available
choises are now: 1.024 MHz, 2.048 MHz, 5 MHz, 10 MH
The ATMP MPLS interworking is used when ATM service is needed for benefiting
from statistical multiplexing when using legacy 3G ATM base stations with ATM
technology for packet services (HSPA).
MPR offers on a Carrier Ethernet model (native Ethernet) ATM PW services.
At the interconnection point the ATM PW transported on dedicated VLAN on
MPR network is delivered to the to the MPLS network with an IETF compliant
label stack.
MEF8 and ETH services are delivered as Ethernet traffic
Page 7
This feature allows to make independent, on the MPR NE interfacing the

IP/MPLS equipment, the ATM PW Service from Ethernet Layer 2 transport used
within the overall MPR network:
- all ATM PW flows egressing MPR network will have the same VLAN ID, which
has been swapped from the several VLAN IDs used by ATM PW flows within
MPR network
- for the opposite direction, all ATM PW flows ingressing MPR network will have
the above common VLAN ID swapped to VLAN IDs used by ATM PW flows on
single PW basis (i.e. according to the PW Label value)
- all ATM PW flows egressing MPR network will have the same 802.1p bit field
remarked according to ATM PW CoS information contained into EXP bit field of
ATM PW Label (removing the Green or Yellow information)
- for the opposite direction, all ATM PW flows ingressing MPR network will have
the same 802.1p bit field remarked as Green
Such operations requires, only for MPR NE interfacing, the use of a dedicated
configuration file as described in the user manual, configuration file chapter,
section VLAN SWAP AND DOT1P REMARKING FOR ATM PW SERVICE.
Page 8
SOFTWARE UPGRADE PROCESS

The following sections contain information on upgrading to the R 1.4.0 software version. The 9500
MPR does support ISSU (In Service Software Upgrade) which process is described in the user manual.
Modules that have updated FPGA software will suffer a momentary loss of traffic.
Hereafter software upgrade notes are described.
ISSU FROM MPR
1.3.0/1.3.1

ISSU FROM MPR

1.2.1/1.2.2

Migration from MPR 1.3.0/1.3.1 to MPR 1.4 has 20 sec of traffic impact
(measured on E1 interface)
Automatic database migration is performed
Download time of MPR 1.4.0 is around 10 minutes, considering both the
two cases: local or remote download (remotely with a TMN bandwidth
of 512 Kbit/sec). No traffic impact is present during the download of the
SWP.
Migration from MPR 1.2.x to MPR 1.4.0 has 20 sec of traffic impact
(measured on E1 interfaces)
Automatic database migration is performed
Download time of MPR 1.4.0 is around 10 minutes, considering both the
two cases: local or remote download (remotely with a TMN bandwidth
of 512 Kbit/sec). No traffic impact is present during the download of the
SWP.
Page 9
SOFTWARE COMPONENTS
The following section contain information on the SW components version building MPR 1.4.0 SWP
MDPAR
OC_R (ODU300 SW)
FCERE (FPGA)
FGUIN (FPGA)
FDUFF (FPGA)
FFURO (FPGA)
FRCFG
FCNFD
FASP
FASAB
EC
V 03.00.07
V 04.06.04
V 01.02.04
V 03.10.02
V 01.01.15
V 02.01.07
V 00.00.03
V 00.00.59
V 01.02.00
V 01.01.10
V 06.00.14
Page 10
USAGE NOTES
The following information supplements or clarifies information on the manual
Note: bracketed () references are internal tracking number
Provisioning
Provisioning tool
Craft Terminal
Core protection
56 MHz channel spacing is not foreseen by ETSI standard in some

frequency bands and for this reason it is not supported by all the
ODU300 codes. Before selecting a modem profile with channel spacing
equal to 56 MHz in the radio channel, please check that the ODU is
supporting it because no consistency check is performed by the system
(no error notification is reported). In case of doubts, please push the
refresh button: if the frequency values has been reported as 00, it
means that the 56 MHz option has been refused and it is not supported
by ODU (CONbb10051)
During equipment configuration, we recommend not to use
simultaneously craft terminal and TCO provisioning tool. Some conflicts
can appear. A warning message is displayed from craft terminal
(CONbb11165, CONbb11080, CONbb11109)
It is strongly suggested to terminate TCO session using close current
session button. Otherwise in order to re-open a new TCO session, a PC
reboot may be needed (CONbb11549).
It is recommended not to have more than one Craft Terminal instance
open for a given NE on the same manager (PC). (CONbb08787)
It is recommend not to run 9500 MPR craft terminal the same time as
9400AWY Craft Terminal when this one is connected to F interface (in
such a case the remote 9500MPR NE wouldnt be reachable).
(CONbb08644)
In case of main core board replacement (and more in general during
synchronization between the two core boards), it is recommended not
to switch off the equipment in order to avoid the flash card
misalignment. In any case before switching off, it is recommended to
remove the force command. (CONbb09467, CONbb09587,
CONbb09589).
The SW license upgrade is possible only when core main is active. After
having applied the new license string, in case it is needed a force
operation on the spare core, it is recommended to wait few minutes,
otherwise the core spare will work with old license value. (CONbb09592)
The following operation is not recommended: to make a force operation
on spare core and then subsequently to cancel using craft terminal the
core protection. This will cause traffic interruption. (ONDrd03290)
Only in case of core protected configuration, usage of hw reset button
present on the core boards is generating generate a traffic hit. It is
recommended to use the SW reset (CONbb10988).
After a power off/on of the NE or plug out/plug in of the core board,
please wait that the LED on the core board are in the final configuration
because an alignment of the two core boards could be on going. This
process could take some minutes. (CONbb11067, CONbb11386)
Page 11
DCN
SW download
TX mute
Upgrade from 1+0 to

1+1
Event Log Browser
Adaptive Modulation
Before enabling an additional Ethernet port on a core card, in case static

LAG option AND LOS as core switching criteria have been selected, it is
strongly recommended to disable Ethernet Interface Criteria for 1+1
EPS core . The LOS could be the re-enabled after that this additional
port has been properly configured. No traffic impact is foreseen by this
operation. Please refer to MPR 1.4 user manual for details
(CONbb15306).
It should be noted that during any operation that is impacting NE
provisioning, it is not guaranteed that core protection is triggered by
Ethernet LOS alarm. (CONbb15394)
The maximum tolerated broadcast traffic injected on the NMS interface
available on the core is 5Mbit/s (ONDrd03025)
If Port #4 of core board is used in TMN mode, the user should not add
this port as member of any VLAN membership table in 802.1Q mode.
(CONbb11756)
During the SW download and activation operation, if a failure occurs
there is no warning message and the system reverts back to the old SW
version (ONDrd03403)
For Software Download, the FTP server must be reachable by the
Network Management System itself (Craft Terminal or NM) and not only
by the Network Element. (CONbb07932)
During the download of the FPGA of ASAP card, differently from other
cards, RUP alarm is raised. After the firmware download is over, RUP
alarm is correctly switched off. (CONbb12468)
In 1+1 HSB configuration, in the craft terminal screens, two different
checkboxes for TX muting enable command are present (one for main
ODU and one of the spare ODU). In 1+1 HSB configuration only one
transmitter is switched on: making TX mute operation on the active
transceiver, the entire traffic is dropped (ONDrd03062)
Maintenance operations on remote site like TX mute and Far End IF
loopback could cause permanent remote NE isolation. A warning
message is appearing on the screen when attempting to make such
operations. It is recommended that such operation be only applied with
local presence. (CONbb08473)
The configuration upgrade (PDH card or Modem card) from 1+0 to 1+1
and vice versa is not error free (CONbb09364, CONbb10894)
It is recommended to wait the end of any operations inside ELB tool,
before performing a NE refresh, otherwise it could happen that the ELB
automatically closes (Onbb09759)
If admission control is enabled, in case of 1+1 HSB, maintenance
operations on modem boards is not error free on traffics that exceed
4QAM bandwidth. TDM2TDM guaranteed traffics are in any case not
impacted. (CONbb09564).
If admission control is disabled, in case of 1+1 HSB, maintenance
operations on modem boards are not error free. TDM2TDM guaranteed
traffics, in case exceeding 4QAM throughput, is impacted as well. Traffic
hit might be as long as 5 sec. (CONbb13101, CONbb13106)
Page 12
IF loopback
Remote manual
command
TDM2ETH
SNMP
The maximum output power is the one corresponding to 64 QAM

modulation scheme and it does not change according to the modulation
scheme (CONbb09213)
Changing the configuration from presetting mode to adaptive
modulation, a false Warning Message of TX Power Out of Range appears
for bad Range. Re-edit the output power and ignore the message.
(CONbb10492)
If admission control is disabled and the number of E1 exceeds 4QAM
bandwidth, when RSL value degrades causing a modulation scheme
downgraded, usually all the TDM traffic is impacted. It might happen
that some E1s are temporarily up and transmitting.
In case of system with adaptive modulation enabled, after the first
modem configuration a false message PTx out of range" is shown
(CONbb09623)
Maintenance operation such as Local loop-back requires local TX mute
enabling before. If the Early Warning alarm is active after the local loopback activation, disable and enable the loop-back again. (CONbb08488,
CONbb08835).
A manual command on Hot Stand-By protection performed on the
remote equipment might produce an error message even if the
operation is correctly performed. Close the pop-up window and
continue. (CONbb08614)
With reference to MEF8 standard, it should be noted on the current
implementation of CES over Metro Ethernet that is addressing structureagnostic emulation for E1 ports bits R, M and L are not managed
(CONbb07597)
SNMP commands sent by a generic MIB browser: the usage of the MIB
browser must be limited to applications enabling the get

commands only retrieving traps and status of the variables
PM tool
AUX card
ASAP card
It is recommended, in case counters related to radio queues are active,

not to plug out modem card, otherwise counters values might be lost.
Please stop the counters before maintenance operations.
(CONbb11999)
It is recommended to avoid maintenance operation of Modem card
when Ethernet radio counters are activated. In this case data could be
accidentally lost (CONbb10394)
It is recommended not to keep opened PM tool during equipment
configuration; otherwise, please close and open it again after the
completion of configuration process (CONbb14278)
24 hours PM: please note that after that 24 hours have been elapsed, it
is shown in the screen of PM tool 00.00.00 instead of 24.00.00
(CONbb14610)
Service channels traffic should be cross-connected in a given radio
direction always together with at least another type of traffic (e.g.
Ethernet or TDM or ATM). If in a radio link only the service channels are
transported, performances are not guaranteed (CONbb12265)
An IMA-group is declared as operational associating E1-links and not, as it
Page 13
Backup and Restore
might be expected, only when at least one links of the group is

operational up (TSAlo46735)
ASAP card start up voltage is 44V.
In case of force command (core protection) from spare core to main
core, before making a backup it is necessary to wait few minutes, to
permit flash cards database alignment. In case the backup has been done
during this alignment phase, the backup operation can fail; in this case,
please close Craft terminal, re-open it and apply again backup.
(CONbb15552)
Page 14
KNOWN RESTRICTIONS
The following are specific technical restrictions that exist in this release. Please also consult the Known
limitation section
Configuration/
Provisioning
NTP
Battery alarm
PM tool
2x(1+0) 2x(1+1)
configuration
Configuration file
In the TCO Set-Up Tool, if the login window is closed before any
username/password has been entered, it is necessary to close and
restart the TCO application it will fail to open correctly. This limitation is
experienced with any type of browser (CONbb08429).
In First configuration by Craft Terminal if an error message appears after
setting E1 tributaries flow Identifier, disable the E1 tributaries and
repeat again the operation (CONbb08771)
Craft Terminal is allowing a PTX change by step of 1 dB. In case the
maximum ODU output power is xx.5, a starting value with .5 digit needs
to be written (CONbb09517)
In case of usage of Provisioning tool for configuring E1 Flow ID , after
having inserted the last value, the user should hit return after inserting a
value otherwise a message of error occurs. (CONbb10113)
The setting of28MHz 256QAM takes 10 sec to be applied (more then
other modem profiles) (CONbb12044)
It is suggested, in case of configuration change from E1 framed to E1
unframed, not to use the apply all button: in this case the change of
configuration will have effects on E1 already Xconnected, causing a
traffic hit (CONbb12139)
In case of loss of one of the two NTP servers, the NTP is immediately
synchronized to the second one, but the notification is reported with 30
minutes of delay. A false message appears at craft terminal.
(CONbb09481)
In case of a battery fail alarm is present, a blue light bullet is displayed
inside the block diagram view (inside Craft Terminal) but the navigation
is not correct: it is redirected to core main instead of to MSS-8.
(CONbb09758)
With MSS-8, with only one battery input connected, there is a standing
Battery Fail warning.
The navigation between alarm and Alarm Monitoring window is not
supported (CONbb12102)
It might happen, according to the number of E1s under monitor, that PM
tool is taking some few minutes to load and consequently display the
history table (CONbb12278, CONbb12210)
It is not possible to de-assert TMN RF after having enabled it. If an
attempt to disable it has been done, a false alarm of PPPfail is raised
(but in reality TMN RF is still active). The only way to disable TMN RF is
to disable it through CT and to apply then an NE reset. (CONbb15431)
QinQ: TPID value different from 0x8100 might cause traffic hit of few
tens of seconds in case of core EPS switch and SW download activation
Page 15
Alarm monitoring
Backup&Restore
(CONbb13267)
During navigation from Alarm Monitoring to Craft Terminal (and vice
versa), it could happen that the target window is not shown up to the
front, needing in this case the frontal window to be iconized to view the
other one. (CONbb09794)
Craft Terminal screen PDH view and Alarm monitor use different
names for E1 LOF alarms (CON12232)
FTS (File Transfer Scheduler) of backup function is not supported from
1350MS/1350OMS managers. The same feature instead is available
from MPR 1.4 CT (locally or remotely).
Page 16
RESOLVED ISSUES
The following are specific technical issues that have been resolved in this release since Release 1.3.1

Configuration
Provisioning
Operation
Provisioning tool
PM tool
This release does not support the Backup & Restore functionality even if
it is selectable by the Craft Terminal (CONbb07839, CONbb07844,
CONbb08441)
In the Xconnection configuration report presented in the TCO Set-Up,
there is an arbitrary sequence number (starting from 1) displayed instead of
the Flow Identifier (CONbb08425)
256QAM in 56 MHz channel spacing is not a supported modem profile,
even if there is not a check preventing this option from CT. In case of
selection of 256QAM@56 MHz, performances are not guaranteed.
(CONbb13250)
In Craft Terminal, synchronization window, changing the settings of
secondary source and then pushing the apply button, a loading window
remains incorrectly. Please close it manually. (CONbb09654)
The Save As operation in TCO Pre-Provisioning Tool and Set-Up Tool
does not allow modifying the directory names (this should be done from
Windows File Manager). (CONbb08734)
Prior any change of the modulation scheme in static mode, TX output
power must be set within the allowed range. (CONbb11484)
When cross-connection operations are in process, it is recommended to
avoid triggering other configuration operations. (CONbb07719,
CONbb08333, CONbb08388)
In the craft terminal screen of CORE Main View, reporting the status of
auto-negotiation process, the label other is always incorrectly displayed.
The information related to auto-negotiation results (speed, flow control...)
are anyway correctly reported in the top part of the same screen.
(CONbb08452)
Provisioning tool is not correctly computing the maximum number of E1
that is possible provisioning for 16QAM@56 MHz and 256QA@28 MHz
modem profiles. The not allowed E1s shall be added using Craft Terminal
(CONbb12309)
In TCO Set-Up Tool, the Help Windows may be blocked after several
successive activations. In such case, restart the help application.
(CONbb08752)
It is recommended to avoid maintenance operation of PDH card when E1
performances monitoring are activated. In this case data could be
accidentally lost (CONbb12378)
In case of a system with radio protected and in adaptive modulation it is
not possible to start the radio counters inside PM-tool because the tool
buttons (Stop, Refresh, Reset, ) are grayed. Click on any other window and
then come back to clear the situation (CONbb11457)
Page 17
Alarm monitoring
SW license
Core protection
Maintenance
Link identifier
The help menu inside the alarm-monitoring tool is not available.

(CONbb09828)
Synchronization alarms (synch degrade and synch LOS) are not reported
in the Alarm Log (CONbb13321)
In case of more than 500 alarms present in Alarm Log Global, in case of
disconnection of the TMN cable, it is recommended to close and re-open
again the Alarm Monitor in order to have a correct view of new and old
alarm. (CONbb09935)
It is recommended not to keep opened Alarm monitoring window during
equipment configuration; otherwise, please make sure to make a refresh
after the completion of configuration process (CONbb13520)
If, during the SW license upgrade process, a provisioning mismatch alarm
should appear, it is recommended an NE reset in order to proper apply
the new SW license (CONbb09354)
In core protection configuration, the green LED on the TMN port remains
green even if no cable is plugged. (CONbb10160)
In case of presence of demodulator failure alarm or cable disconnected
in 1+1 FD or HSB configuration with forced lockout condition, the alarm is
not displayed at link level but it is displayed at hop level. (CONbb11288,
CONbb11589)
In case of ODU disconnection (cable loss alarm or ICP alarm) there is an
inconsistency between tree view and graphical icon view in craft terminal.
Correct alarm status is displayed on the tree view. (CONbb09818)
After a configuration change from 1+0 to 1+1 HSB, the LIM alarm is not
revaluated; in order to re-evaluate please disable/enable link identifier.
(CONbb09610)
Page 18
SYSTEM REQUIREMENTS
To properly install TCO Suite application (including Craft Terminal), make sure your computer meets
the following minimum system requirements
PC HW Configuration
CPU: Pentium III 850 MHz
RAM: 1 GB (suggested)
Min. disk space: 1,5 GB (available space needed for log files, JRE excluded)
Min. resolution:
o 4:3 equal or higher 1152x864 pixel
o 4:3 equal or higher 1280x800 pixel
CD-ROM/DVD/Blue-Ray Drive: 24x
Primary Interface: Ethernet Card 10/100 Mbit/sec.
Operating Systems Supported
Microsoft Windows 32-bit versions: Microsoft Windows XP Professional service pack2, Windows
Vista Ultimate.
Tested FTP Servers (for Software Download feature)
Apache FTP Server (http://incubator.apache.org/ftpserver/). Default available with WebEML
(JUSM/CT);
VSFTPD, version 2.0.5;
FileZilla FTP Server, version 0.9.23
Additional requirements
Microsoft Internet Explorer 6.0 SP1+ ,7, 8 or higher, Mozilla Firefox 2,3,3.5 or higher.
Minimum HTML page size shown shall be 1024x768 pixels.
PC standard user can be used to run the applications but for TCO Suite usage Administrator
password is needed
JRE (Java Runtime Environment) 6 Update 14
Disable all Firewall software on used PC
TCO Provisioning Tool should be used for the first commissioning of the equipment
If TCO tool is used on a PC with Windows Vista Ultimate, please make sure that in the list of
networks connections available, the one used to connect PC to NE is not the first one. In order to
change the order of the list, iIn Windows Vista, go to Control Panel -> Network and Sharing Center
-> Manage Network Connections -> Advanced -> Advanced Settings menu (hit and release ALT
keyboard button to show menus). The list of network connections appears: the order of the list can
be modified using the arrow button on the right
Page 19
SUPPORTED SW ITEM
The 9500 MPR Release 1.4.0 SW set consist of the items listed in Table 1:
Alcatel-Lucent Part#
3DB18554AI
Description
SWP 9500 MPR 1.4.0 Hybrid Operating System
Introduced
R 1.4.0
3DB18555AI
SWP 9500 MPR 1.4.0 Packet Operating System
R 1.4.0
3DB18557AI
TCO SW Suite R3.4.0 [1]
R 1.4.0
3DB18556AD
9500 MPR 1.4.0 SNMP [2]
R 1.4.0
3DB18497AI
9500 MPR 1.4.0 User Guide
R 1.4.0
Table1: 9500 MPR CD ROM

[1] TCO SW suite R3.4.0 manages MPR NE with R 1.4.0 (the management of network elements
differently from MPR 1.4.0 with TCO 3.4.0 is not guaranteed).
[2] The proper SNMP specs defining the OID are detailed in the document 9500MPR-E 1.4 System
Specification SNMP Management Interface (code 3DB 18619 0000 DSZZA).
Description
3DB18283AFXX
MPR Memory L6TD-131
3DB18284AFXX
MPR Memory M1TD-131
3DB18285AFXX
MPR Memory M2TD-131
3DB18501AFXX
MPR Memory M6TD-131
3DB18286AFXX
MPR Memory H1TD-131
3DB18287AFXX
MPR Memory H2TD-131
3DB18502AFXX
MPR Memory H6TD-131
3DB18288AFXX
MPR Memory V1TD-131
3DB18289AFXX
MPR Memory V2TD-131
3DB18489AFXX
MPR Memory V6TD-131
3DB18290AFXX
MPR Memory E1TD-131
3DB18291AFXX
MPR Memory E2TD-131
3DB18490AFXX
MPR Memory E6TD-131
3DB18283BFXX
MPR Memory L6SA-131
Introduced
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
Page 20
3DB18284BFXX
MPR Memory M1SA-131
3DB18285BFXX
MPR Memory M2SA-131
3DB18501BFXX
MPR Memory M6SA-131
3DB18286BFXX
MPR Memory H1SA-131
3DB18287BFXX
MPR Memory H2SA-131
3DB18502BFXX
MPR Memory H6SA-131
3DB18288BFXX
MPR Memory V1SA-131
3DB18289BFXX
MPR Memory V2SA-131
3DB18489BFXX
MPR Memory V6SA-131
3DB18290BFXX
MPR Memory E1SA-131
3DB18291BFXX
MPR Memory E2SA-131
3DB18273BFXX
MPR Memory E6SA-131
3DB18579AFXX
MPR Memory I1TD-131
3DB18580AFXX
MPR Memory I2TD-131
3DB18581AFXX
MPR Memory I6TD-131
3DB18582AFXX
MPR Memory I1SA-131
3DB18583AFXX
MPR Memory I2SA-131
3DB18584AFXX
MPR Memory I6SA-131
3DB18585AFXX
MPR Memory A1TD-131
3DB18586AFXX
MPR Memory A2TD-131
3DB18587AFXX
MPR Memory A6TD-131
3DB18588AFXX
MPR Memory A1SA-131
3DB18589AFXX
MPR Memory A2SA-131
3DB18590AFXX
MPR Memory A6SA-131
3DB18591AFXX
MPR Memory A1TD-131A
3DB18592AFXX
3DB18593AFXX
3DB18594AFXX
MPR Memory A1SA-131A
3DB18595AFXX
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
Page 21
3DB18596AFXX
3DB18562AFXX
MPR Memory L6TD-131A
3DB18563AFXX
MPR Memory M2TD-131A
3DB18564AFXX
MPR Memory M6TD-131A
3DB18565AFXX
MPR Memory V1TD-131A
3DB18566AFXX
MPR Memory L6SA-131A
3DB18567AFXX
MPR Memory M2SA-131A
3DB18569AFXX
MPR Memory M6SA-131A
3DB18568AFXX
MPR Memory V1SA-131A
3DB18727AFXX
MPR Memory E6TD-131A
3DB18728AFXX
MPR Memory E6SA-131A
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
R 1.3.1
Table2: 9500 MPR supported Flash Card.
Important note: these codes are not compatible with former releases of MPR (ex: 1.2.0, 1.2.1,
1.2.2,1.3.0). These flash cards can run only SW MPR 1.3.1, 1.4.0 or later releases.
Page 22
SUPPORTED HARDWARE
The following tables summarize the hardware supported in this release
3DB18485AA
Description
9500 MSS-8 Shelf
Introduced
R 1.0.0
3DB18219AB
9500 MSS-4 Shelf
R 1.2.0
3DB18134BB
3DB18134BA
9500 MSS-8 Fan Module
R 1.0.0
3DB18218AD
3DB18218AC
9500 MSS-4 Fan Module
R 1.2.0
3DB18326AC
3DB18326AB
Core enhanced
R 1.2.0
Table3: 9500 MPR Common equipment
3DB18126AE
3DB18126AD
3DB18126AC
3DB18126AC
3DB18136AE
Description
32E1/DS1 PDH peripheral
Introduced
R 1.0.0
Modem300
R 1.0.0
Modem300 EN
R 1.1.0
3DB18236AB
Auxiliary peripheral
R 1.3.0
3DB18602AA
ASAP peripheral
R 1.2A
3DB18136AD
3DB18136AC
3DB18538AC
3DB18538AB
3DB18538AA
Table4: 9500 MPR peripheral cards
Page 23
Description
1AB187280040
SFP 1000Base-LX Transceiver
Introduced
R 1.1.1
1AB187280045
SFP 1000Base-SX Transceiver
R 1.1.1
1AB359780001
SFP 1000Base-T Copper Transceiver [3]
R 1.4.0
Table5: Supported Small Form-factor Pluggable (SFP) Modules

[3]. Electrical SFP is managed starting from release 1.4. It does require a specific configuration file. Please refer
to user manual for details.
Frequency band
TX-RX separation
3DB23215HA
6 GHz
252 MHz
6 GHz
340 MHz
7 GHz
154 MHz
7 GHz
161 MHz
3DB23215HD
3DB23215HB
3DB23215HE
3DB23215HC
3DB23215HF
3DB23216HA
3DB23216HB
3DB23216HC
3DB23216HD
3DB23216HE
3DB23216HF
3DB23027HA
3DB23027HB
3DB23028HB
3DB23028HG
3DB23028HC
3DB23028HI
3DB23028HD
3DB23028HK
3DB23028HO
3DB23028HR
3DB23028HP
3DB23028HA
3DB23028HQ
Page 24
3DB23028HT
3DB23028HE
3DB23028HL
3DB23028HH
3DB23028HM
3DB23028HJ
3DB23028HN
3DB23028HA
3DB23028HF
3DB23184HA
3DB23185HA
3DB23296HA
3DB23296HB
3DB23296HC
3DB23296HD
3DB23026HA
7 GHz
154 /161 /168 MHz
7 GHz
168 MHz
7 GHz
161 / 168 MHz
7 GHz
196 MHz
7 GHz
245 MHz
8 GHz
119 / 126 MHz
3DB23026HD
3DB23026HB
3DB23026HE
3DB23026HC
3DB23026HF
3DB23186HA
3DB23186HB
3DB23186HC
3DB23186HD
3DB23188HA
3DB23188HB
3DB23188HC
3DB23188HD
3DB23189HA
3DB23189HB
3DB23189HC
3DB23189HD
3DB23189HE
3DB23189HF
3DB23029HA
3DB23029HD
Page 25
3DB23029HB
3DB23029HE
3DB23029HC
3DB23029HF
3DB23030HA
8 GHz
151 MHz
8 GHz
195 MHz
8 GHz
208 MHz
8 GHz
266 MHz
8 GHz
310 MHz
8 GHz
305 / 310 MHz
10.5 GHz
91 MHz
3DB23030HC
3DB23030HB
3DB23030HD
3DB23289HA
3DB23289HB
3DB23031HA
3DB23031HC
3DB23031HB
3DB23031HD
3DB23031HE
3DB23031HF
3DB23032HA
3DB23032HC
3DB23032HB
3DB23032HD
3DB23034HA
3DB23034HC
3DB23034HB
3DB23034HD
3DB23033HA
3DB23033HC
3DB23033HB
3DB23033HD
3DB23255HA
3DB23255HB
3DB23255HC
3DB23255HD
3DB23255HE
3DB23255HF
3DB23255HG
3DB23255HH
3DB23255HI
Page 26
3DB23255HL
3DB23255HM
3DB23255HN
3DB23261HA
10.5 GHz
350 MHz
11 GHz
490 / 500 / 530 MHz
13 GHz
266 MHz
15 GHz
315 MHz
15 GHz
420 MHz
15 GHz
475/490 MHz
3DB23261HB
3DB23261HC
3DB23261HD
3DB23035HA
3DB23035HE
3DB23035HB
3DB23035HF
3DB23035HC
3DB23035HG
3DB23035HD
3DB23035HH
3DB23036HA
3DB23036HE
3DB23036HB
3DB23036HF
3DB23036HD
3DB23036HH
3DB23036HC
3DB23036HG
3DB23037HA
3DB23037HC
3DB23037HB
3DB23037HD
3DB23038HA
3DB23038HD
3DB23038HB
3DB23038HE
3DB23038HC
3DB23038HF
3DB23039HC
3DB23039HD
3DB23039HE
3DB23039HF
Page 27
3DB23039HA
3DB23039HB
3DB23295HA
15 GHz
644 / 728 MHz
18 GHz
340 MHz
18 GHz
1008/1010/1090 /1120 MHz
18 GHz
1560 MHz
23 GHz
600 MHz
23 GHz
1008 MHz
23 GHz
1200 / 1232 MHz
26 GHz
1008 MHz
3DB23295HB
3DB23041HA
3DB23041HD
3DB23041HB
3DB23041HE
3DB23041HC
3DB23041HF
3DB23042HA
3DB23042HE
3DB23042HB
3DB23042HF
3DB23042HC
3DB23042HG
3DB23042HD
3DB23042HH
3DB23062HC
3DB23062HD
3DB23043HA
3DB23043HB
3DB23044HA
3DB23044HD
3DB23044HC
3DB23044HF
3DB23044HB
3DB23044HE
3DB23045HA
3DB23045HE
3DB23045HB
3DB23045HF
3DB23045HC
3DB23045HG
3DB23045HD
3DB23045HH
3DB23259HA
Page 28
3DB23259HB
3DB23259HC
3DB23259HD
3DB23259HE
3DB23259HF
3DB23213HA
28 GHz
1008 MHz
32 GHz
812 MHz
38 GHz
1260 MHz
3DB23213HD
3DB23213HB
3DB23213HE
3DB23213HC
3DB23213HF
3DB48245HA
3DB48245HB
3DB48245HC
3DB48245HD
3DB48245HE
3DB48245HF
3DB48245HG
3DB48245HH
3DB23258HA
3DB23258HB
3DB23258HC
3DB23258HD
3DB23258HE
3DB23258HF
3DB23258HG
3DB23258HH
3DB23258HI
3DB23258HL
3DB23258HM
3DB23258HN
Table6: 9500 MPR ODU300 supported codes (*)
(*) In Table6 code of ODUs with integrated lightening arrestor are reported. MPR 1.4.0 supports
ODU with non-integrated lightening arrestor as well: the list of these codes can be found in the
Product Release Note of MPR 1.2.1.
Page 29

9500 MPR Rel 1 4 Product Release Note

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9500 MPR Rel 1 4 Product Release Note

Uploaded by

Copyright:

Available Formats

9500 MPR V1.4.

3DB18715AAAA FMZZA, February 2010

Product Release Notice, Version 1.4.0

3DB18715AAAA FMZZA, February 2010

Product Release Notice, Version 1.4.0

RELEASE NOTICE ORGANIZATION

SCOPE AND PURPOSE .............................................................................................................................. 1

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

SCOPE AND PURPOSE

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

Primary reference clock source

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

Examples of not admitted configurations:

256QAM@56 MHz modem profile has been added, in static modulation.

The core switching criteria are the following:

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

o Flash Card failure

Stacking configuration (i.e two MPR shelves interconnected through an Ethernet

Here above a typical network scenariowhere stacking can be useful is depicted:

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

This feature allows to make independent, on the MPR NE interfacing the

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

SOFTWARE UPGRADE PROCESS

ISSU FROM MPR

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

56 MHz channel spacing is not foreseen by ETSI standard in some

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

Upgrade from 1+0 to

Before enabling an additional Ethernet port on a core card, in case static

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

The maximum output power is the one corresponding to 64 QAM

browser must be limited to applications enabling the get

It is recommended, in case counters related to radio queues are active,

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

Backup and Restore

might be expected, only when at least one links of the group is

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

Note: bracketed () references are internal tracking number

3DB18715AAAA FMZZA, February 2010

9500 MPR Product Release Notes, Version 1.4.0

The help menu inside the alarm-monitoring tool is not available.