3db19043aaaafmzza01 - v1 - 9500 Mpr-E r4.1.0 Release Notice

Alcatel-Lucent 9500
MICROWAVE PACKET RADIO FOR ETSI | RELEASE 4.1.0

R E L E A S E N O T I C E
3DB 19043 AAAA FMZZA Edi ti on 01
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2012 Alcatel-Lucent. All rights reserved.
R E L E A S E N O T I C E
When printed by Alcatel-Lucent, this document is printed on recycled paper.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is
subject to change without notice.
Alcatel, Lucent and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent. All other
trademarks are the property of their respective owners.
Copyright 2012 Alcatel-Lucent.
All rights reserved.
Disclaimers
Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design
engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous
environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft
navigation or communication systems, air traffic control, direct life-support machines, or weapons
systems, in which the failure of products could lead directly to death, personal injury, or severe physical
or environmental damage. The customer hereby agrees that the use, sale, license or other distribution
of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at
the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from
any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the
use, sale, license or other distribution of the products in such applications.
This document may contain information regarding the use and installation of non-Alcatel-Lucent
products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent
tries to ensure that this information accurately reflects information provided by the supplier, please refer
to the materials provided with any non-Alcatel-Lucent product and contact the supplier for
confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete
information provided about non-Alcatel-Lucent products.
However, this does not constitute a representation or warranty. The warranties provided for
Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by
Alcatel-Lucent and its customers.
This document was originally written in English. If there is any conflict or inconsistency between the
English version and any other version of a document, the English version shall prevail.
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 iii
3DB 19043 AAAA FMZZA Edition 01
Release Notice
Contents
9500 MPR-E Release 4.1.0 Release Notice 1
Summary ................................................................................................1
Safety information......................................................................................1
New release capabilities...............................................................................1
Provider Bridge QinQ 802.1ad [MSS-1/4/8] .........................................2
Global Configuration................................................................2
S-VLAN creation .....................................................................3
Member set and untagged set of a PNP..........................................3
S-VLAN removal......................................................................4
Equipment components de-provisioning.........................................4
S-VLAN ID 1 management ..........................................................4
Management of Provider Bridge Ports Port Type...............................4
PNP - S-VLAN TPID (Tag Protocol Identifier) ....................................4
PNP - Acceptable Frame Type.....................................................5
PNP - Port S-VLAN ID................................................................5
PNP - Priority and Drop Eligible...................................................5
PNP - Port Priority ..................................................................6
PNP - Ingress Filtering ..............................................................6
PNP - PCP and DEI fields of S-VLAN Tag .........................................6
PNP - S-VLAN Rate Limiter .........................................................6
PNP - Per-CoS Rate Limiter ........................................................7
Customer Network Port Parameters..............................................7
Bridge Mode Configuration.........................................................8
C-VLAN Translation .................................................................9
MultiService Ring Protection 8032 v2 ............................................9
Ethernet user port LAG.............................................................9
Packet throughput booster (header compression) [ALL] ........................ 10
7705 SAR + MPR-e [MPR-e] ........................................................... 11
7705 SAR + MPR-e Separate NEs................................................. 11
7705 SAR + MPR-e Single NE ..................................................... 12
Contents
iv November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Edition 01 3DB 19043 AAAA FMZZA
Release Notice
IPv6 and OSPFv3 [MSS-1/4/8] ....................................................... 12
TACACS+ enhancements [MSS-1/4/8] .............................................. 13
Features significantly changed ..................................................................... 13
STM-1 channelized support of L2 LAG crossconnections ........................ 13
Transmitter mute function [MSS-1/4/8] ........................................... 13
Retained capabilities ................................................................................. 14
Discontinued capabilities ............................................................................ 14
Documentation delivery ............................................................................. 15
Software and license delivery ...................................................................... 16
Software compatibility............................................................................... 17
Backwards compatibility and migration ........................................... 17
Downloading the software ........................................................... 17
Installing the software ............................................................... 18
Software components............................................................. 18
TCO suite and MCT system requirements...................................... 19
Upgrade paths ..................................................................... 20
Precautions and recommendations ............................................. 21
Traffic impact during the SWP activation ..................................... 22
Third-party software notes .......................................................... 22
Release content ....................................................................................... 24
Implemented features................................................................ 24
Closed issues ........................................................................... 24
Usage notes ............................................................................ 24
Technical support..................................................................................... 32
Customer documentation............................................................................ 32
Accessing customer documentation................................................ 32
Providing feedback about customer documentation ............................ 33
Glossary .............................................................................................. 34
A. MPR-e and MSS-1c SNMP management A-1
A.1 MPR-e and MSS-1c SNMP management ............................................... A-1
A.2 Traffic Ethernet port counters [MPR-e].............................................. A-1
A.3 Radio QoS counters [MPR-e/MSS-1c] ................................................. A-2
B. Previous release capabilities B-1
B.1 Capabilities in R4.0.0................................................................... B-1
SNMPv3 support [MSS4/8] ........................................................... B-1
Per-CoS rate Limiter [MSS-4/8] .................................................... B-2
User configurable label on traffic interfaces [MSS4/8] ........................ B-3
TMN in-band with L2 Ethernet LAG................................................ B-4
MPR-e repeater back to back support [MPR-e] .................................. B-4
B.2 Capabilities in R3.4.0................................................................... B-5
Multichannel Link Aggregation L1 [MSS-4/8]..................................... B-6
Supported configurations ....................................................... B-6
Description of supported scenarios............................................ B-6
LAG L1 configuration ............................................................ B-8
LAG L1 configuration modification ............................................ B-9
LAG L1 activation and deactivation ........................................... B-9
LAG L1 deletion..................................................................B-10
Port Add and Remove operations .............................................B-10
Contents
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 v
Release Notice
Master port definition ..........................................................B-10
Port provisioning rules..........................................................B-11
Allowed configurations .........................................................B-11
Adaptive Modulation and modem profiles...................................B-12
Service restrictions .............................................................B-12
User ports and radio interfaces ...............................................B-12
Radio QoS configuration........................................................B-13
Supported services and configurations.......................................B-13
Maximum throughput ...........................................................B-13
LAG rate ..........................................................................B-13
Maximum Ethernet frame length .............................................B-13
Admission control ...............................................................B-14
Maximum number of cross-connections......................................B-14
Segregations .....................................................................B-14
Synchronization..................................................................B-14
SSM ................................................................................B-15
TMN-RF configuration...........................................................B-15
LAG alarms .......................................................................B-16
Switching criteria ...............................................................B-16
Remote defect indication......................................................B-16
Wait to restore ..................................................................B-17
MPT connected to EAS card [MSS-4/8] ...........................................B-18
Port rate limiter [MSS-4/8] ........................................................B-19
Storm control [MSS-4/8] ...........................................................B-19
Per VLAN rate limiter [MSS-4/8] ..................................................B-20
VLAN swap [MSS-4/8] ...............................................................B-21
Additional modem profiles [MSS-4/8 and MPR-e] ..............................B-22
Fiber/microwave protection [MSS-4/8]..........................................B-22
MPT-MC: new modem profiles support, up to 256QAM/56 MHz [ALL].......B-24
TACACS+ [MSS-4/8] .................................................................B-25
Server Support ...................................................................B-25
Authentication/Authorization.................................................B-25
Server Monitoring ...............................................................B-26
Server Validation ................................................................B-26
B.3 Capabilities in R3.3.0..................................................................B-26
RING support with MPT-MC/HC [MSS-4/8].......................................B-26
XPIC support over MPR-e [MPR-e].................................................B-27
XPIC and Adaptive Modulation [MSS-4/8, MPR-e] ..............................B-27
XPIC and ATPC [MSS-4/8, MPR-e] .................................................B-27
1+1 radio protection on MPT-HC without tight cable [MSS4/8] ..............B-27
Improvement of MSS-1c MCT [MSS-1c] ...........................................B-28
2x(1+0) MSS-1c repeater configuration [MSS-1c] ...............................B-28
Troubleshooting tool [MSS4/8] ....................................................B-29
Separate alarms for battery A and battery B [MSS-8] .........................B-29
B.4 Capabilities in R3.2.0..................................................................B-30
Quality of Service ...................................................................B-30
Forwarding class mapping......................................................B-31
QoS scheduler setting ..........................................................B-33
Queue size setting ..............................................................B-33
Link aggregation managed through CT/NMS ................................B-35
Contents
vi November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Release Notice
C. Supported hardware C-1
C.1 Supported hardware .................................................................... C-1
Existing hardware .................................................................... C-1
MPT supported codes ............................................................ C-5
D. Closed issues in previous releases D-1
D.1 Closed issues in previous releases .................................................... D-1
E. VLAN values for STM-1 flows E-1
E.1 VLAN values tables...................................................................... E-1
F. Open issues in R3.2.0 and earlier F-1
F.1 Open issues in R3.2.0 and earlier..................................................... F-1
Usage notes ........................................................................... F-1
Open issues............................................................................ F-7
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 1
Release Notice
9500 MPR-E Release 4.1.0 Release Notice
Summary
The 9500 MPR R4.1.0 addresses both the ETSI and ANSI markets. This document
describes and provides guidelines for the 9500 MPR ETSI-related features. Refer to
9500 MPR-A Release Notice for ANSI-related information.
The 9500 MPR-E designates ETSI software. The 9500 MPR-e designates the
MPT-MC/HC/XP deployed in standalone mode or in connection with a 7705 SAR
indoor unit. References to MPT-HC in this document refer to the MPT-HC V2.
Safety information
This document contains safety statements. Safety statements indicate where risks of
damage to personnel, equipment, and operation may exist. Failure to follow the
directions in a safety statement may result in serious consequences.
For additional safety precautions, see the 9500 MPR User Guide
(3DB-19901-ABAA).
New release capabilities
The features described below are introduced in the 9500 MPR R4.1.0:
Caution ETSI modem profiles only support E1 signals and ANSI
modem profiles only support DS1/DS3 signals. Mixed configurations
are not supported unless explicitly documented.
2 November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Release Notice
Legend:
[MSS-1/4/8]the feature applies to the MSS-1/4/8 system only
[MSS-1c:]:the feature applies to the MSS-1c system only
[MPR-e]: the feature applies to the MPR-e system only
[ALL]: the feature applies to all systems
In Service software upgrade from 9500MPR R3.4.0 to R4.1.0
In Service software upgrade from 9500MPR R4.0.0 to R4.1.0
Provider Bridge QinQ 802.1ad [MSS-1/4/8]
MSS-1 shelf introduction (1+0 and ring configurations)
Packet throughput booster (header compression) [ALL]
7705 SAR + MPR-e [MPR-e]
IPv6 and OSPFv3 [MSS-1/4/8]
TACACS+ enhancements [MSS-1/4/8]
New XPIC modem profiles on 7/14 MHz channel spacings (MPT-HC/XP, fixed
and adaptive modulation) [MSS-1/4/8 and MPR-e]
Provider Bridge QinQ 802.1ad [MSS-1/4/8]
The switch supports double tagging according to 802.1ad, in particular:
adding a service VLAN on the ingress traffic
pbits value of service VLAN is:
user configurable
same value of customer VLAN
The EtherTypes supported are:
EtherType 0x8100
EtherType 0x9100
EtherType 0x88A8
Global Configuration
On an NE basis, in the CT/NMS it is possible to define the way to manage the
Ethernet traffic according to one of the following options:
802.1D (MAC Address bridge)
802.1Q (Virtual Bridge)
802.1ad (Provider Bridge), newly introduced in the CT in R4.1.0
Provider bridge (802.1ad) can be applied to the user ports of a Core-E card and to the
user ports of an EAS card.
When the NE is configured in Provider Bridge mode, the forwarding of Ethernet
traffic is managed according to Service VLAN. Each Service VLAN (S-VLAN)
represents a service instance where Ethernet traffic from a customer network is
mapped to.
Release Notice
In Provider Bridge mode, an S-VLAN is assigned to all Ethernet frames managed by
the NE. The assignment of an S-VLAN to an Ethernet frame ingressing the NE shall
be done according to the type of the Provider Bridge port:
Provider Network Port (PNP), this is an interface internal to the Provider Bridged
Network (NNI), SVLAN is assigned based on S-VLAN ID carried by S-VLAN
Tag or based on the ingress interface in case of S-VLAN untagged frames;
Customer Network Port (CNP), this is an interface at the edge of the Provider
Bridged Network (UNI), S-VLAN is assigned based on User Ethernet port
(Port-based service interface) regardless of the type of customer traffic (C-VLAN
tagged or untagged);
When the NE is working in Provider Bridge mode, all the switches process Ethernet
frames according to SVLAN Tag to perform functions such as forwarding, filtering,
and policing. The tag of a single tagged Ethernet frame or the outer tag of a double
tagged frame is recognized as S-VLAN Tag according to the port S-VLAN TPID.
S-VLAN creation
By CT/NMS you can create an S-VLAN in the S-VLAN Table. The operator can:
Define S-VLAN ID; the configurable values are in the range 2 - 4080. The VLAN
IDs already defined to cross-connect internal flows (i.e. TDM2TDM,
TDM2ETH) cannot be used. The management system shall prohibit the definition
of S-VLAN ID already used and shall highlighting the issue. The S-VLAN ID
must be different also from the Flow ID associated to E1 tributaries not yet cross
connected.
Define S-VLAN Name; this is a text string of up to 32 characters. There is no
check on ambiguous names.
Define the interfaces which are member of this S-VLAN (S-VLAN Member Set).
All User Ethernet ports and all Radio ports shall be considered. Both enabled and
disabled User Ethernet ports and Radio ports (take into account that Radio ports
include L2 Radio LAG and L1 Radio LAG too) can be member of an SVLAN.
This means that a disabled port can be configured as a member of an S-VLAN
and a port already member of an S-VLAN can be disabled continuing to be in the
member set of that S-VLAN.
Define among the ports belonging to member set of this S-VLAN those where
S-VLAN will be removed from the frames delivering them untagged in egress
(S-VLAN Untagged Set). Only the User Ethernet ports, enabled and disabled
shall be manageable. The S-VLAN is never removed from the Radio ports (with
the exception of the S-VLAN ID 1, see S-VLAN ID 1 management).
When a new S-VLAN is defined, by default none of the ports are in the member set
and none of the ports are in the untagged set.
Member set and untagged set of a PNP
When a User Ethernet port is configured as PNP, it can be in the member set of more
than one S-VLAN and can be or not in the untagged set of those S-VLANs.
A Radio port is always configured as PNP, it can be in the member set of more than
one S-VLAN and is never in the untagged set of those S-VLANs.
Release Notice
S-VLAN removal
It is possible to remove an S-VLAN from the S-VLAN Table even if the S-VLAN
ID has been configured on one or more User Ethernet ports (being PNP or CNP) as
Port S-VLAN ID to be added in ingress to S-VLAN untagged frames.
As consequence, the S-VLAN ID 1 and Priority 0 are assigned to the S-VLAN
untagged frames received on this port. Before applying the removal, the management
system does request to the operator confirmation of the operation, highlighting the
consequence of the operation.
Equipment components de-provisioning
When an equipment component, on which there is at least one port belonging to the
member set of an S-VLAN, is declared by the operator as no more expected in the
current equipment position, the management system rejects the operation.
The board can be declared as no more expected only when no one of its interfaces
belong to the member set of an S-VLAN.
S-VLAN ID 1 management
S-VLAN having S-VLAN ID 1 shall be implicitly defined by the NE in the S-VLAN
Table when the Provider Bridge type is selected. This S-VLAN shall be shown to the
operator but it can be neither changed nor removed by the management systems.
All the User Ethernet ports and all the Radio ports, regardless of whether they are
enabled or disabled and port type, must be in the member set of the S-VLAN having
S-VLAN ID 1.
The S-VLAN ID 1 shall be always removed at the egress of all PNPs. This means
that PNPs are always in the untagged set of S-VLAN having S-VLAN ID 1.
CNP is by default in the untagged set of any S-VLAN including S-VLAN ID 1.
Management of Provider Bridge Ports Port Type
Each User Ethernet port of Core and EAS boards can be configured either Provider
Network Port (PNP) or as Customer Network Port (CNP). For Radio ports, the Port
Type is fixed to PNP and cant be modified by management systems.
Default Port Type for User Ethernet ports is PNP.
PNP - S-VLAN TPID (Tag Protocol Identifier)
S-VLAN TPID can be configured for PNP in order to:
Identify in ingress the outer VLAN Tag as an S-VLAN Tag and then be able to
identify the Ethernet frame as S-VLAN tagged, S-VLAN untagged or S-VLAN
priority-tagged (when S-VLAN ID is 0)
Set the TPID of S-VLAN Tag at egress.
S-VLAN TPID permissible values are 0x8100, 0x88A8 and 0x9100. Default value
is 0x8100.
Release Notice
For Radio ports, the S-VLAN TPID is fixed to 0x8100 and cannot be modified by
management systems.
PNP - Acceptable Frame Type
Acceptable Frame Type parameter controls which type of Ethernet frames are
accepted in ingress at the PNP.
The permissible values for this parameter are:
Admit only VLAN-tagged frames; only S-VLAN tagged frames are admitted,
S-VLAN untagged frames and S-VLAN priority-tagged frames are dropped.
Admit all frames; S-VLAN tagged, untagged and priority-tagged frames are
admitted.
For Radio ports, the Acceptable Frame Type parameter is fixed to admit only
VLAN-tagged frames and cannot be modified by management systems.
According to the last statement, a service based on S-VLAN ID 1 is not supported
over Radio ports. Because a Radio port is always in the untagged set of S-VLAN
having S-VLAN ID 1 and accepting only S-VLAN tagged frames in ingress, the
delivery of traffic based on S-VLAN ID 1 is not feasible.
PNP - Port S-VLAN ID
When the Acceptable Frame Type parameter is set to Admit all frames, the
S-VLAN ID to be assigned to S-VLAN untagged or S-VLAN priority-tagged frames
are configurable by management systems.
Only S-VLAN IDs related to S-VLANs having the PNP in their member set can be
selected.
The default value of Port S-VLAN ID is 1.
When the Acceptable Frame Type parameter is set to Admit only VLAN tagged
frames, the Port S-VLAN ID is set to default value.
When a PNP is changed to CNP, Port S-VLAN ID parameter is kept.
PNP - Priority and Drop Eligible
For S-VLAN tagged and S-VLAN priority-tagged frames ingressing a PNP, the
priority is determined by the PCP (Priority Code Point) field carried by S-VLAN
Tag.
The Use DEI parameter is always false and is not configurable by management
systems.
Drop eligible assigned to Ethernet frames ingressing a PNP is always false (every
Ethernet frame is considered as in-profile or green). Priority Code Point
Decoding Table is not managed.
Release Notice
PNP - Port Priority
When the Acceptable Frame Types parameter is set to admit all frames, the priority
to be assigned to S-VLAN untagged frames shall be configurable by management
systems (for S-VLAN priority-tagged frames the priority is the one carried by PCP
field).
Port Priority can be selected in the range 0 to 7. Default value of Port Priority is 0.
When the Acceptable Frame Type parameter is set to Admit only VLAN tagged
frames, the Port Priority is set to the default value.
When a PNP is changed to CNP, the Port Priority parameter is kept.
When the QoS classification is based on DiffServ, the priority assigned to S-VLAN
untagged frames is the Forwarding Class related to the DSCP field carried by the
frame according to the configuration of IPv4/IPv6 DiffServ to internal Forwarding
Class mapping.
The priority assigned to a frame not carrying an IPv4/IPv6 packet is 0.
PNP - Ingress Filtering
Ingress Filtering parameter is always enabled on PNP and its not configurable by
management systems. This means that an S-VLAN tagged frame received on a PNP
that is not in the member set associated with the frames S-VLAN ID shall be
discarded.
PNP - PCP and DEI fields of S-VLAN Tag
S-VLAN Tags PCP (Priority Code Point) field of S-VLAN tagged frames egressing
a PNP is determined by the priority assessed at ingress port.
S-VLAN Tags DEI (Drop Eligible Indication) field of S-VLAN tagged frames
egressing a PNP is set to:
The same value of received S-VLAN Tags DEI field when the frame was an
S-VLAN tagged or S-VLAN priority tagged frame and the ingress port was a
PNP
Zero when the frame was an S-VLAN untagged frame and the ingress port was a
PNP since Drop eligible is set to false
Zero when the ingress port of the frame was a CNP since Drop eligible is set to
false
Zero when the ingress port of the frame was a CEP since Drop eligible is set to false.
Priority Code Point Encoding Table is not managed.
PNP - S-VLAN Rate Limiter
The VLAN Rate Limiter is also supported on PNP. Since the VLAN Rate Limiter
acts always on the outer VLAN Tag, in case of PNP it acts as an S-VLAN Rate
Limiter.
Release Notice
PNP - Per-CoS Rate Limiter
The Per CoS Rate Limiter feature described is also supported on PNP. Since the
Per-VLAN Per CoS Rate Limiter acts always on the outer VLAN Tag, in case of
PNP it acts as a Per-S-VLAN Per-CoS Rate Limiter.
Customer Network Port Parameters
The following are the CNP parameters:
CNP - Acceptable Frame Type
Acceptable Frame Types parameter controls which type of Ethernet frames are
accepted in ingress at the CNP. Taking into account the CNP is a port of an
S-VLAN Component, the only permissible value for this parameter is Admit
only untagged and priority-tagged frames, the parameter is not configurable by
management systems.
Untagged frames, C-VLAN tagged frames and C-VLAN priority-tagged
(C-VLAN ID = 0) frames are all seen as S-VLAN untagged frames by the
S-VLAN Component. The priority-tagged frames in the context of a CNP,
means S-VLAN priority-tagged (S-VLAN ID = 0) frames. Those type of frames
are not managed as Ethernet frames ingressing a CNP and are dropped by the NE
(take care that S-VLAN priority-tagged frames having TPID equal to 0x8100 are
recognized as C-VLAN priority tagged frames at CNP).
CNP - Port S-VLAN ID
For a CNP, the Port S-VLAN ID represents the S-VLAN ID assigned to all the
Ethernet frames ingressing the port. Port S-VLAN ID selects the port-based
service instance associated to CNP. According the management of CNP in the
S-VLAN Table, at most two S-VLANs have the CNP in their member set, and
one is the S-VLAN having S-VLAN ID 1.
Since the S-VLAN ID 1 cant represent a service instance, a Port S-VLAN ID
other than 1 must be selected by operator for a CNP.
The default value of Port S-VLAN ID is 1.
When a CNP is changed to PNP, Port S-VLAN ID parameter is kept.
CNP - Port Priority/Customer Priority
For a CNP, the Port Priority represents the priority assigned to all the Ethernet
frames ingressing the port. Port Priority can be selected in the range 0 to 7.
Default value of Port Priority is 0. The priority assigned to Ethernet frames
ingressing a CNP can be also determined looking to the PCP field of C-VLAN
Release Notice
Tag in case of C-VLAN tagged or C-VLAN priority-tagged frames. The selection
between the usage of Port Priority or Customer Priority shall be configurable by
management systems.
When Customer Priority is selected and the received frame is untagged, the Port
Priority parameter value is assigned instead.
The default value is usage of Port Priority.
Drop eligible assigned to Ethernet frames ingressing a CNP is always false (every
Ethernet frame is considered as in-profile or green). When a CNP is changed
to PNP, Port Priority parameter is kept, while priority assignment is set to the
default (Port Priority).
When the QoS classification is based on DiffServ, the priority assigned to
untagged frames is the Forwarding Class related to the DSCP field carried by the
frame according to the configuration of IPv4/IPv6 DiffServ to internal
Forwarding Class mapping. The priority assigned to a frame not carrying and
IPv4/IPv6 packet is 0.
CNP - S-VLAN Rate Limiter
The VLAN Rate Limiter is also supported on CNP. Since the VLAN Rate Limiter
acts always on the outer VLAN Tag, in case of CNP it acts as an S-VLAN Rate
Limiter applicable to Port S-VLAN ID only.
CNP - Per-CoS Rate Limiter
The Per CoS Rate Limiter described feature is supported on CNP too. Since the
Per-VLAN Per CoS Rate Limiter acts always on the outer VLAN Tag, in case of
CNP it acts as a Per-S-VLAN Per-CoS Rate Limiter.
The only selectable S-VLAN ID is the Port S-VLAN ID. In case of Port Priority
usage, the only selectable PCP is Port Priority value. In case of Customer Priority
usage the full range of PCPs is selectable.
Bridge Mode Configuration
The following considerations apply when changing bridge mode:
Change bridge mode configuration from 802.1D (MAC Bridge) to 802.1ad
(Provider Bridge)
To change the NE bridge mode from MAC Bridge to Provider Bridge all
cross-connections must be removed. No check is requested by NE and CT/NMS
to enforce cross-connections removal, in case Provider Bridge were activated
having cross-connections still configured, the delivery of cross-connected traffic
is not guaranteed.
After the change all User Ethernet interfaces are set as PNP with S-VLAN TPID
equal to 0x8100.
S-VLAN Table is empty except for S-VLAN having S-VLAN ID 1.
Change bridge mode configuration from 802.1Q (Virtual Bridge) to 802.1ad
(Provider Bridge)
The existing cross-connections or the existing VLANs defined in the VLAN
Table can be kept in case of change of NE bridge mode from Virtual Bridge to
Provider Bridge. Changing from Virtual Bridge to Provider Bridge, there will be
Release Notice
a traffic impact on the delivery of cross-connected and Ethernet traffics during
restart, due to the unavoidable reconfiguration of the Ethernet switches in 802.1ad
mode.
After restart all User Ethernet interfaces are set as PNP with S-VLAN TPID equal
to 0x8100.
The S-VLAN Table is filled with S-VLANs having S-VLAN ID equal to the
VLAN ID of VLANs previously defined in the VLAN Table. Port VLAN ID and
Port Priority assigned to User Ethernet interfaces are assigned as Port S-VLAN
ID and Port Priority of PNPs.
This allows continuing to deliver existing C-VLAN tagged Ethernet traffic even
if the NE bridge mode is changed to Provider Bridge. C-VLANs are seen by the
NE as S-VLANs since all the ports are PNP with S-VLAN TPID same of
C-VLAN TPID.
Change bridge mode configuration from 802.1ad (Provider Bridge) to 802.1D
(MAC Bridge)
To change the NE bridge mode from Provider Bridge to MAC Bridge all
cross-connections and all defined S-VLANs must be removed.
No check is requested by NE and CT/NMS to enforce cross-connections and
S-VLANs removal, in case MAC Bridge were activated having
cross-connections and S-VLANs still configured, the delivery of cross-connected
traffic and Ethernet traffic is not guaranteed.
Change bridge mode configuration from 802.1ad (Provider Bridge) to 802.1Q
(Virtual Bridge)
To change the NE bridge mode from Provider Bridge to Virtual Bridge all
cross-connections and all defined S-VLANs must be removed. No check is
requested by NE and CT/NMS to enforce cross-connections and S-VLANs
removal, in case Virtual Bridge were activated having cross-connections and
S-VLANs still configured, the delivery of cross-connected traffic and Ethernet
traffic is not guaranteed.
Upon changing from Provider Bridge to MAC Bridge, the NE shall perform a
restart.
C-VLAN Translation
The C-VLAN Translation feature is not available when the NE is configured in
Provider Bridge mode. The request to enable the Provider Bridge mode when there
are translated C-VLANs on any User Ethernet interface is refused by the CT/NMS.
MultiService Ring Protection 8032 v2
The 802.1ad mode is not supported if a 9500 MPR node is configured in ring mode
and ring protection is not available in 802.1ad mode.
Ethernet user port LAG
Ethernet user port LAG is not compatible with 802.1ad Provider Bridge mode.
Release Notice
Packet throughput booster (header compression) [ALL]
A data packet often has a large amount of overhead compared to the actual user
traffic (payload). The overhead fields are of course needed for several reasons
(routing, collision, flow identification,) in complex LAN/WAN networks;
however, this overhead can be drastically limited to improve and increase overall
throughput over the air.
With the packet throughput booster feature, the packet header is compressed to
improve throughput.
Packet Throughput Booster is for MPT-MC/MPT-HC/MPT-XP units
The following describes some details about the header fields.
Inter-Frame GAP (12 bytes). Ethernet devices must allow a minimum idle period
between transmission of Ethernet frames known as the Inter-Frame Gap (IFG);
IFG has been introduced by IEEE 802.3 to avoid collision over a shared medium
(LAN). These bytes are not needed in a microwave transmission and can be
entirely eliminated
Preamble and Start of Frame Delimiter (8 bytes). They have been added by IEEE
802.3 standard to allow devices on the network to easily detect a new incoming
frame. These bytes are not needed in a microwave transmission and can be
entirely eliminated.
Ethernet header. This is the information used to switch an Ethernet frame across
a network segment:
Destination addresses (6 bytes)
Source addresses(6 bytes)
802.1Q tag (4 bytes): optional VLAN tag
Ethertype/length (2 bytes); EtherType is a two-octet field in an Ethernet frame. It is
used to indicate which protocol is encapsulated in the PayLoad of an Ethernet
Frame.
CRC (4 byte): Frame check sequence, used to detect errored frames - Payload
(46-1500 bytes): user data
For example, the minimum Ethernet message is 64 bytes long. If one VLAN is
present, then that frame carries only 42 bytes of useful information (payload) but
requires 84 bytes overall to transport, equaling a 100% overhead to payload ratio.
Examining closer, the inefficiency of small packets is even worse when using other
protocols such as IPv4 or IPv6 because they are encapsulated in the Ethernet
payload; IPv6 IP addresses occupy an additional 32 bytes, making transport
efficiency of multi-protocol packets of short length very poor.
Header compression can significantly increase radio link throughput reducing
protocol header overhead. The header size that is compressed is constant, whilst the
packet payload is variable: from this there is an inverse proportion between packet
length and related gain.
Packet Throughput Booster can be applied to MPT-MC and MPT-HC/XP, except
when the MPTs are involved in a LAG L1 group. In this case Packet Throughput
Booster cannot be applied with the current release.
Release Notice
Packet Throughput Booster can be applied to 1+0 or 1+1 HSB/FD/SD
configurations. For 1+1 configurations, in case the RPS module is not used, it should
be considered that the maximum throughput at L2 can be some 440 Mbit/sec; if the
L2 throughput does exceed this threshold RPS module and tight cable have to be
used.
A license string (PTB) is required to enable header compression.
7705 SAR + MPR-e [MPR-e]
The 7705 SAR and MPR-e can be connected and used together, with two different
levels of integration:
7705 SAR + MPR-e Separate NEs
7705 SAR + MPR-e Single NE
7705 SAR + MPR-e Separate NEs
The entire 7705 SAR family can be connected to the MPR-e in 'Separate NEs' mode;
this approach applies to all 7705 SAR variants and to both MPT-MC and
MPT-HC/XP.
The main radio configurations and topologies available in this case are:
1+0 hop, with one MPR-e and one 7705 SAR per site.
2x(1+0) XPIC, with two MPR-e (MPT-HC/XP) and one 7705 SAR per site.
N+0 hop, with N MPR-e and one 7705 SAR per site. The 7705 IP/MPLS
networking and protections apply here.
Ring/mesh topologies, with N MPR-e and one 7705 SAR per site. 7705 IP/MPLS
networking and protections apply here.
In addition to these variants, the 7705 SAR Release 5.0 R4 introduced the PMC card
(Packet Microwave Adapter - PN 3HE02782AA) for the 7705 SAR shelf, which is a
first step of microwave integration between 7705 SAR and MPR-e. The additional
features are:
HW readiness for the SingleNE approach
Proprietary Clock Recovery (PCR), a way to distribute synchronization along
SAR-8/18 rings with GbE electrical connection between the SAR and MPR-e.
Here data AND SynchE synchronization are protected along the ring.
Each PMC can support up to four MPR-e.
For more detailed information, see the 7705 SAR OS 5.0 Software Release Notice
(3HE 06942 000x TQZZA) and the related user guides.
Release Notice
7705 SAR + MPR-e Single NE
The 7705 SAR Release 6.0 R1 and 9500 MPR R4.1.0 releases introduce the
following, providing an increase in the level of integration between the MPR-e and
the 7705 SAR-8/18:
SingleNE 1+1 HSB SD functionality with MPT-HC/MPT-XP (RPS module and
coupling link), two PMCs on the 7705 SAR-8/18
SingleNE for all the 1+0 configurations described in the previous paragraph
Fast Fault Detection (FFD), a way to improve standard IP/MPLS switching times
Up to four MPR-e per PMC
When this solution is adopted, the MPR-e is part of the 7705 SAR Network Element.
The MPR-e does not have a dedicated IP address, however, all MPR-es connected to
the 7705 SAR baseband are reachable using the 7705 SAR IP address (system IP or
others) using the MCT Launcher.
Available radio configurations: on top of the ones described above for separate NEs,
here one configuration more is available: 1+1 HSB SD introducing standard uW
protections in IP/MPLS uW networks. This feature requires an MPT-HC/XP with the
coupling link and two PMCs on the 7705 SAR, thereby protecting the 7705 SAR
hardware in addition to the MPR-e.
See the MPR-e User Manual and the 7705 SAR OS 6.0 Software Release Notice
(available in February 2013) and related user guides for more details.
IPv6 and OSPFv3 [MSS-1/4/8]
IPv6 and OSPFv3 are supported.
The default mode of operation for the 9500 MPR is IPv4 and currently the
9500 MPR does not support "dual stacks", that is, IPv4 and IPv6 enabled at the same
time.
When IPv6 is enabled, the 9500 MPR will restart, disable the IPv4 mode, and allow
the user to configure the IPv6 address.
The NE Local IPv6 address is a Global Unicast address configured statically by the
operator through the management systems which identifies the NE in the DCN. The
default address is FEC0:0:0:1::1. The prefix length is not configurable and is fixed
to 128. The IPv6 addresses must be configured according to the following rules:
IPv6 addresses having the Interface ID portion equal to all 0 are not allowed
IPv6 address ::/128 (Unspecified address) is not allowed
IPv6 address ::1/128 (Loopback Address) is not allowed
IPv6 addresses having FF00::/8 as high-order bits (Multicast addresses) are not
allowed
IPv6 addresses having FE80::/10 as high-order bits (Link Local Addresses) are
not allowed
IPv6 is supported on the same interfaces as IPv4:
Local TMN port
TMN port #4
Release Notice
TMN In-band interface #1
TMN In-band interface #2
TACACS+ enhancements [MSS-1/4/8]
TACACS+ (Terminal Access Controller Access-Control System Plus) is an access
control network protocol.
TACACS+ has been supported in 9500 MPR since R3.4.0. In R4.1.0 additional
functionality has been added to further support the TACACS+ standard:
In 9500 MPR R4.1.0, TACACS+ Accounting provides limited supported for the
WT-CLI as well as the SNMP commands.
The telnet/ssh interfaces report all WT-CLI commands including any arguments.
The SNMP interface reports all object ID strings and values contained in any SET
command received from a registered manager.
The SET commands to register a manager and SET commands to perform a
registration deletion are also reported.
Accounting notifications are not supported for commands received on the HTTP
interface.
Features significantly changed
This section describes features that have significantly changed from the prior release
to the current release.
STM-1 channelized support of L2 LAG crossconnections
L2 LAG cross-connections are supported on SDHCHANN cards.
Transmitter mute function [MSS-1/4/8]
In R4.1.0, the Transmitter mute function has been improved to add a timer to
automaticity unmute the transmitter. The operator can now provide the duration of
the command (timeout). It is expressed in days, hours and minutes starting from the
time of the TX Mute activation. The default value is 30 minutes. The maximum
duration is 2 days, 0 hours, 0 minutes.
A value of 0 days 0, hours and 0 minutes is not allowed.
Release Notice
Retained capabilities
The 9500 MPR R4.1.0 retains all capabilities from the 9500 MPR R4.0.0.
Discontinued capabilities
None.
Release Notice
Documentation delivery
The 9500 MPR R4.1.0 documentation is available through electronic distribution
only. Contact your Alcatel-Lucent Sales Support Representative to place an order.
Table 1 lists the documentation items. See Customer documentation for information
about downloading the documentation from OLCS.
Table 1 9500 MPR R4.1.0 documentation ordering information
Document Alcatel-Lucent part number
9500 MPR-E 4.1.0 Release Notice (this document) 3DB-19043-AAAA-FMZZA
9500 MPR 4.1.0 User Guide 3DB-19901-ABAA
9500 MPR 4.1.0 MPR-e User Guide 3DB-19901-EBAA
9500 MPR 4.1.0 MSS-1c User Guide 3DB-19901-DBAA
9500 MPR 4.1.0 MPT-GC User Guide 3DB-19025-AAAA 02
Release Notice
Software and license delivery
Table 2 lists the software version information.
Table 2 9500 MPR-E R4.1.0 software
Note
(1)
Available through download from OLCS.
Table 3 lists the third-party software that is used for execution of the 9500 MPR
R4.1.0 and that is liable to license agreements. 9500 MPR R4.1.0 CT operation has
been validated with the following third-party software.
Table 3 Third-party software
Note
(1)
Alcatel-Lucent recommends Windows 7 in an IPv6 environment.
Description Alcatel-Lucent part number
9500 MPR 4.1.0 Hybrid OS 3DB18969ACAA
(1)
9500 MPR 4.1.0 Packet OS 3DB18970ACAA
(1)
TCO SW Suite R4.9.0 3DB18971ACAA
(1)

9500 MPR 4.1.0 SNMP 3DB18896DAAA
(1)
Software Version
Windows XP
(1)
Professional Ed. SP3 (32 bit only)
Windows 7
(1)
Premium (32/64 bit)
Java JRE Minimum Version 6, Update 30, 32 bit only (included on CD
3DB18971ACAA TCO SW Suite R4.9)
MS IE Explorer Version 8 on Windows XP, Version 9 or higher on Windows 7
Firefox Version 12 or higher
Chrome Version 20 or higher
FTP Servers (for software download feature) Tested FTP servers:
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
Release Notice
Software compatibility
This section describes 9500 MPR software compatibility.
Backwards compatibility and migration
The 9500 MPR-E R4.1.0 supports migration from the following releases:
9500 MPR-E R3.4.0
9500 MPR-E R4.0.0
See the 9500 MPR User Guide (3DB-19901-ABAA) for an overview of the
migration procedures.
Contact your Alcatel-Lucent Technical Support Representative for assistance before
planning or performing an upgrade.
Downloading the software
The electronic delivery site gives you access to the product software packages. If you
are a new user and require access to this service, please contact your Alcatel-Lucent
sales representative.
Use Procedure 1 to download the 9500 MPR software.
Procedure 1 To download 9500 MPR software from the OLCS site
1 Go to http://www.alcatel-lucent.com/myaccess.
2 Log in to the Alcatel-Lucent Customer and Business Partner Portals with the user
name and password for your OLCS account. A customized Customer Center page
opens.
3 Choose the product name from the Technical Content for drop-down menu.
4 Click on the Downloads: Electronic Delivery hyperlink. The Electronic Delivery
page opens. This page lists a series of drop-down menus that you must use to
navigate through the hierarchy of software items.
5 Choose a software item from the drop-down menu. The page refreshes and
displays a drop-down menu that contains entries for additional software items
associated with the selected item. Depending on the product, you may need to
repeat this step multiple times. Each time you choose a software item from a
drop-down menu, the page may refresh and display an additional drop-down
menu.
6 Click on the Next button. A software download page opens. This page contains
installation instructions and notes, a table with detailed information about your
software download (filename, size, and hash values), and two download options.
7 If needed, record the MD5 hash value provided in the software download table
(you can also print the page for future reference). After you have downloaded the
software, you can use an MD5 hash checker to verify that you have received an
exact copy.
Release Notice
Example of an MD5 hash value: MD5:894c9c70ad276ee755773bc4f339c905
8 Choose one of the following software download options:
a Enter a Download Directory and choose a Log Detail Level (the options are
Low, Medium, High), then click on the Download button to start the file
transfer.
b Click on the Download Plus button to start the file transfer with the GetPlus
download agent, and follow the instructions on the screen.
Installing the software
The following materials are required:
software kit identified in the Software Information section
Ethernet cable to connect to the core module (crossover or straight-through), or
for connection over an existing Ethernet network
laptop or other PC with the 9500 MPR-E R4.1.0 CT application installed
administrator ID and password to log in to each 9500 MPR-E shelf
IP Address or host name of each 9500 MPR-E shelf
9500 MPR-E System with current equipment as described in the 9500 MPR-E
Release Notice (this document)
a Core-E card (CSM) equipped with a Compact Flash (see Table C-3 for the
codes; for example, MPR Memory L6TD-410)
Software components
The delivery for R4.1.0 contains the software elements described in Tables 4 and 5.
Table 4 R4.1.0 Software components for MSS-1c and MPR-e
Note The Download Plus button may not be available on the
software download page. The system prompts you to install a browser
plug-in to activate this download option, and provides you with
installation instructions. Some browser versions do not support the
Download Plus plug-in.
Software component Version
MSS-1c/MPR-e SubRelease version V04.10.0N
MPT SW V08.15.03
MCT SWP V06.14.00
Release Notice
Table 5 Release 4.1.0 Software components for MSS-4 and MSS-8
TCO suite and MCT system requirements
To install the TCO suite application (including Craft Terminal), verify that your
computer meets the following minimum system requirements:
PC hardware configuration
CPU: AMD Atlhon/Intel Celeron/Intel Pentium 4 or higher
RAM: 1 GB
minimum disk space: 1.5 GB (available space needed for log files, JRE excluded)
minimum resolution: 4:3 equal or higher 1152x864 pixel
minimum resolution: 16:9 equal or higher 1280x800 pixel
DVD-ROM Drive: 24x
primary interface: Ethernet Card 10/100 Mb/s (1 Gbit/s for MPR-e)
additional requirements
minimum HTML page size shown must be 1024x768 pixels
PC standard user mode can be used to run the applications, but for TCO Suite usage
the Administrator password is needed
all firewall software must be disabled
TCO Provisioning Tool should be used for the first commissioning of the equipment
if the TCO tool is used on a PC with Windows Vista Ultimate, verify that in the
list of network connections available, the one used to connect the PC to the NE is
not the first connection in the list. To change the order of the list, in Windows
Vista, go to Control Panel!Network and Sharing Center!Manage Network
Software component Version
MSS-4/MSS-8 SubRelease version 4.1.0v
EC V14.15.05
TCO Suite V410.04
ODU300 software version 04.06.10
Caution TCO Suite contains 32-bit Java VM only. This can be
used with 32-bit Internet browsers only such as Mozilla Firefox,
Internet Explorer or Google Chrome. Note that reference Microsoft
Windows operating systems do not allow a 64-bit Internet browser
(not even Microsoft Internet Explorer 64-bit) as default browser for
the system in use. In case a 64-bit browser needs to be used, manually
install a 64-bit Java VM and load manually (e.g.: from the browser
"File"->"Open" command) the Start.html file you can find in the TCO
Suite DVD-ROM root directory.
If a Java VM version 7 is installed, there is no need to remove it or to
set a specific configuration. TCO Suite and WebEML will
automatically use any Java VM version 6 (greater than 6u26)
available on the system only for its own session. All other java
applications, web applications or applets using Java VM version 7
will continue to work with version 7.
Release Notice
Connections!Advanced!Advanced Settings menu (press and release the ALT
keyboard button to show the menus). The list of network connections appears: the
order of the list can be modified using the arrow button on the right.
TCO SW Suite 4.9.0 includes an option dedicated to the 5620 SAM.
To create a local copy of WebEML, use the Local Copy of WebEML button (as
shown in Figure 1), as in previous TCO versions. To create a local copy of the
Craft Terminal of the MSS-1c/MPR-e/MSS-4/MSS-8, use the 5620 SAM NEtO
Multiversion button to create a local copy of a profiled version of the entire
WebEML.
Figure 1 Advanced Install Settings screen
A list of supported Operating systems and browsers can be found in Table 3.
For MPR-e provisioning, the PC used must be able to tag VLANs, in order to connect
to the MPT through the TMN in-band VLAN. Otherwise, the PC must be connected
to a Layer 2 switch with a GE interface and the capability to tag VLANs. See the
9500 MPR R4.1.0 User Guide (3DB-19901-ABAA).
Upgrade paths
Table 6 shows the upgrade paths to Release 4.1.0.
Table 6 Upgrade paths to Release 4.1.0
System Source
release
Destination
release
Possible (Y/N)? Notes
MSS-1/4/8 3.0.0 4.1.0 N Must upgrade to 3.3.0 and then to 3.4.0 first
(1 of 2)
Release Notice
The estimated total time to execute the installation procedure is approximately 40
minutes per 9500 MPR shelf in 1+1 radio protection. This time does not include any
site preparation and pre/post-installation retrievals or setup.
This software is supported on Core-E (CSM) controller modules only.
Precautions and recommendations
Read the entire software installation procedure before beginning.
This procedure should be performed by a qualified Field Service Engineer trained
on the 9500 MPR during an approved maintenance window.
3.1.0 4.1.0 N Must upgrade to 3.3.0 and then to 3.4.0 first
3.2.0 4.1.0 N Must upgrade to 3.4.0 first
3.4.0 4.1.0 Y
4.0.0 4.1.0 Y
MSS-1c/MPR-e 3.0 4.1.0 N Must upgrade to 3.3.0 and then to 3.4.0 first
3.1.0 4.1.0 N Must upgrade to 3.3.0 and then to 3.4.0 first
3.4.0 4.1.0 Y
4.0.0 4.1.0 Y
System Source
release
Destination
release
Possible (Y/N)? Notes
(2 of 2)
Caution Do not upgrade the Network Element Software unless it
is required. Once the software is upgraded, it is very difficult to return
to a previous software release. If software needs to be returned to a
prior release, contact Alcatel-Lucent before you start.
Caution This upgrade procedure will cause traffic and
management interruption during the activation of the R4.1.0 software.
Caution Once the Release 4.1.0 release software has been
activated, the Release 4.1.0 CT must be used to manage the NE.
Release Notice
Traffic impact during the SWP activation
Traffic impact varies by upgrade path.
from R3.4.0/R4.0.0 (with ODU300) to R4.1.0: measured on E1 interfaces, there
are 0/25 seconds of traffic impact immediately after SWP activation.
from R3.4.0/R4.0.0 (with MPT-xC connected to MPT Access unit) to R4.1.0:
measured on E1 interfaces, there are 120/160 seconds of traffic impact
immediately after SWP activation.
from R3.4.0/R4.0.0 (with MPR-e or MSS-1c) to R4.1.0: traffic impact in case of
software migration is around 150 seconds.
Procedure 2 shows the general steps to upgrade to Release 4.1.0. Refer to the
9500 MPR 4.1.0 User Guide (3DB-19901-ABAA) for the detailed procedure.
Procedure 2 To upgrade from R3.4.0/4.0.0 to R4.1.0
1 Install the R 4.1.0 version of the 9500 MPR-E Craft Terminal on the Craft PC.
Pre-loading operation verification
2 Check and set the system time.
3 Check for Alarms and Abnormal Conditions.
4 Ensure that the main Core module is active (Protected Core configurations only).
The migration procedure is not allowed if the spare core module is active (MSS-4/8
only).
5 Retrieve and save the current configuration and perform a backup.
6 Install the R4.1.0 Software Package (SWP) to the Craft Terminal PC or on a FTP
server (for MPR-e/MSS-1c).
7 Download the R4.1.0 Software Package to the 9500 MPR.
8 Activate the R4.1.0 Software Package on the 9500 MPR.
9 Verify activation of the R4.1.0 Software Package on the 9500 MPR.
10 Check for Alarms and Abnormal Conditions.
11 Load the R4.1.0 Software Package into the Standby software bank.
12 Optionally, update the License Key (MSS-1/4/8 only).
Third-party software notes
Table lists the Non-Alcatel-Lucent Owned Software (NAOS) items that are included
as part of this release.
Release Notice
NAOS software included with 9500 MPR R4.1.0
NAOS item code NAOS item description
Minimum version 6, update 30, 32 bit only Java JRE
Release Notice
Release content
This section provides information about the content of the 9500 MPR release R4.1.0.
Implemented features
The 9500 MPR R4.1.0 includes the features described in New release capabilities.
Closed issues
Table 7 describes the closed issues.
Table 7 Closed issues in R4.1.0
Usage notes
Table 8 describes the usage notes for this release. Usage notes supplement or clarify
information in the documentation. Where available, workarounds have been
provided.
Item Description
ALL systems
Firmware download In some cases, MSS boards could be stuck in a continuous firmware download
mode.
AUX card alarms AUX card alarms inconsistent raise and clear and do not correlate to the main
alarm window.
JUSM MSS Radio Main View JUSM MSS Radio Main View behavior inconsistent
MSS-1/4/8
MPT-HL reports wrong shifter ranges for
7/8 GHz
The MPT-HL is reporting the wrong range values for all 7/8 GHz shifters, thus
the user cannot set the Tx/RX frequenices correctly.
Workaround: Use custom shifter to directly enter the TX and RX frequencies.
Software download If downloading the NE SWP with the same version user will see Software
Download Error is displayed and the stand-by software package is not
updated.
During the download on the standby bank of the same Sw version already
uploaded on the active bank, a StandBy Version Mismatch alarm is
generated on the MPT.
Workaround: Do the software download via the Forced option.
MPR-e
MCT application freeze after restore in
some case
After a Restore db of the MPR-e, if the user does not validate the Success
dialog box before the Connection Lost dialog box, the MCT application will
freeze.
Workaround: Validate first the SUCCESS dialog box before the Connection
Lost dialog box.
Release Notice
Table 8 Usage notes for R4.1.0
Item Description
ALL systems
Time to perform software download
using FTP in IPv6 on remote NE
In some cases using FTP with IPv6, software download can take up to 30
minutes to complete.
Workaround: Wait at least 30 minutes for the software to download.
SFTP connection not released in case of
MIB backup/restore failure
If the MIB backup or restore procedure using SFTP fails, additional operations
using SFTP may not be possible.
Workaround: Close and restart the Craft Terminal.
Software download start using SFTP fails
if attempted immediately after software
download manual abort
If the user manually aborts a software download using SFTP then immediately
restarts the software download, the user will receive an NE internal error
message.
Workaround: After a manual software download abort, wait at least one
minute before starting another SFTP software download.
Google Chrome as default browser If Google Chrome is the default browser when the start.exe is executed on the
WebEML TCO, even with Java 6u30 installed it tries to install the latest Java
version. The Browser will open, the 1C and MPR-e images are not displayed and
it prompts to install the Java plug-in. If user says "install plug-in" it takes the
user to the Java website to install Java 7 which is not supported.
Work Around: None.
Java 6u30 plugin The latest versions of Firefox and Chrome do not enable Java 6u30 by default,
causing installation issues from the CD image.
Work around: In Firefox, manually go to add-ons and enable the 6u30 plugin.
In Chrome click on "run this time" each time it appears.
Suggested DCN topology When the 9500 MPR is used as the designated router, on the same LAN, the
maximum number of suggested direct neighbors is 8.
PM QOS Ethernet counters With the MPT-xC ODU the QoS Ethernet counters will restart to 0 after they
reach 2^32.
Workaround: None
SNMPv3 To change a user's password, the users old password is required.
Workaround: The best way for the Admin user to change a users password is to
delete the user and re-create the user using a new password.
Adaptive modulation With Adaptive Modulation enabled on the ODU300, when the CLA function is
started there could be switching every 30 seconds on main or spare.
Workaround: The oscillations stop after 10 minutes.
False CLA After a 30 sec of RX common outage, the CLA criteria is declared and the TX is
switched (expected). The TX continues to switch every 30 sec while the RX
outage remains. When the RX recovers, the CLA criteria remains set on the
standby TX even though there was no fault on that facility.
Workaround: Operator must then manually clear the alarm.
SDHACC In case of SFP failure on the SDHACC board, the alarm raised is LOS and not
Card Fail Alarm.
Workaround: If LOS is still present after troubleshooting the LOS, replace the
SFP.
TDM2ETH EC ID for Rx/Tx cannot use the value of 1 for TDM2ETH
Per MEF8 standard, Rx ECIDs must be unique on the same NE.
MSS-1/4/8
(1 of 7)
Release Notice
Mixed network with 9500 MPR R4.1.0
IPv6 stack active and older releases
A mixed link with IPv4 and IPv6 is not supported and the TMN channel will not
operator properly when configured in this manner.
Workaround: Ensure that both ends of the link are in the same operating mode.
When migrating to IPv6, always update the far end, then the near end to
maintain visibility.
Excessive environmental temperature
alarm on MPT-HL after ISU from R4.0.0
After an upgrade to R4.1.0 occasionally the MPT-HL will declare an "Excessive
Environmental Temperature" alarm.
Workaround: Clear the alarm via warm start of the MPT-HL via the craft
terminal.
CFNR CFNR tool not available via SSH protocol.
Windows XP with IPv6/IPv4 double stack In Windows XP when the network interface card is configured with both an IPv4
and IPv6 address, the 9500 MPR craft terminal is slow.
Workaround: When using Windows XP, it is not recommended to use IPv6 and
IPv4. Only enable IPv4.
IPv6: issues on Windows XP If the 9500 MPR is configured for use with IPv6, it is highly recommended that
Windows 7 is used instead of Windows XP.
Workaround: None - use Windows 7.
Disconnect to remote server - different
behavior in SFTP compared to FTP
Using FTP mode the session disconnection reactivity time is longer than in SFTP
mode.
Workaround: Even though the FTP mode is longer than SFTP mode, the time is
the same as in previous releases.
Core protection in Y configuration With CORE Protection and using optical splitters on either Ethernet port 5 or 6
and Using the LoS switch criteria, when the main side LOS is cleared traffic may
be affected.
Workaround: When using an optical splitter verify that LOS disable is set. The
usage the optical splitter on the CORE is intended for protecting against Core
board failure and not for line protection.
LOS criteria is intended to be used only in case of 9500 MPR stacking
configurations.
Cannot set port VLAN or priority on
Ethernet LAG when in 802.1ad (provider
bridge) mode
Once the bridge mode is changed to 802.1ad, it is not possible to assign a port
VLAN to an L2 Ethernet LAG. Also, if one already exists before converting from
802.1q to 802.1ad, it is no longer possible to remove or change the VLAN on
the LAG, or to remove the VLAN.
Workaround: In 9500 MPR 4.1 L2 Ethernet LAG and 802.1ad are not supported
simultaneously.
SSm message from Eth port after
unprovisioning MPT MC-HC
If an Ethernet port has been configured as an MPT-xC on the Core-E and then
configured as a user Ethernet port with SSM enabled, the SSM functionality will
not function properly.
Workaround: A warm start of the 9500 MPR will correct the issue.
IPv6: DAD alarm severity not
manageable
The DAD alarm severity is not managed properly using ASAP profiles.
Workaround: None
NEtO discovery protocol When in IPv6 mode, NEtO discovery of the 9500 MPR may not work if multicast
UDP packets are blocked by firewalls.
Workaround: Either manually enter the IPv6 Address or validate that the
firewall settings would allow for UDP multicast packets with TLV protocol.
Characters in username/password Some special characters are not allowed for user passwords. Do not use the
colon, single quote and double quote.
Workaround: User passwords are allowed alphabet letters a-z and numbers 0-9.
Password printable characters are allowed except ' "" :
Item Description
(2 of 7)
Release Notice
AUX module on SBD On the summary block diagram, the AUX module does not show any alarm
synthesis nor can the user navigate to the AUX module from the summary block
diagram.
Workaround: Exit the Summary block diagram and navigate to the AUX board
from the equipment view.
Radio capacity value The Current Configuration View may not show the correct radio capacity.
Workaround: If the radio capacity is in question, navigate to the radio view and
verify the radio capacity.
SW activation of 3.x load The 9500 MPR R4.1.0 supports upgrades from R3.4.0, however software
rollback to R3.4.0 is not supported.
Workaround: None
CT not enabling TX Mute Auto Local
when Incompatible TX Power is set
When an Incompatible TX Power alarm is raised the radio CT screen TX Mute
does not report the Auto Local option is ON.
Workaround: None
Saving alarm filter to network location Attempting to save alarm filters from AM tool to a network location does not
work. The window that opens allows you to select the network location but
upon clicking Done it does not save the filter.
Workaround: Map network location to a drive letter and use that to save to the
network location.
For example, H:\9500\R4.1\Screenshots\AM-Filter-Angus174.xml
Maximum buffer queue size The CT allows maximum queues size of 4 034 836 bytes but the system will only
support queue size of 3 987 220 bytes. Should the system be set between those
sizes, there could be an impact to Back to Back tests.
Workaround: Ensure that the queue size is only set to 3 987 220 Bytes.
Port Rate Limiting parameters When changing the Port Rate Limiting parameters on an EAS or CORE-E
Ethernet port, a traffic hit on this particular port occurs. Workaround: None
MSS 4/8 Configuration changes MSS 4/8 Configuration changes are not retained after the following operations
sequence:
Switch CORE-E by Forced command
CORE-E Main becomes Standby and CORE-E Spare is now Active
Unplug CORE-E Spare
CORE-E Main becomes Active
Any changes made now will not be retained when the Spare board is now
plugged in.
Workaround: After changes create a database backup with changes before
plugging in Spare CORE-E.
Spare CORE-E plugged into the MSS If the Spare CORE-E is plugged into the MSS but is not configured, during a
software activation, a traffic hit may occur.
Workaround: Always configure the Spare CORE-E if plugged into the MSS
Monitoring of services MIPs cannot be used for the monitoring of services in the following Layer 1 Lag
configurations:
Two Layer1 LAGs belonging to the same plug-in
Two Layer1 LAGs configured on plug-ins on the same row
A mixed configuration of a Layer1 LAG and a 1+0 radio link belonging to the
same plug-in
A mixed configuration of a Layer1 LAG and a 1+0/1+1 radio link configured
on plug-ins on the same row.
Workaround: None
Item Description
(3 of 7)
Release Notice
Migrating from a 1+1 FD system When migrating from a 1+1 FD system to a 1+0 with PM already active, the
counter PM Radio Hop will be deactivated.
Workaround: Restart the PM Radio Hop Counter.
Radio Repeater with LAG When in a Radio Repeater with LAG, changing the system from 802.1d mode to
802.1q mode, TDM traffic may be affected.
Workaround: None
MPT-ACC/EAS plug-in insertion After plugging in a MPT-ACC or an EAS card, the Ethernet Statistics may be
inaccurate right after insertion.
Workaround: After MPT-ACC/EAS plug-in insertion, it is necessary to wait at
least 15 seconds to have accurate values for Ethernet Statistics.
Looping radios with Layer 1 LAG When using Radio Layer 1 LAG, TDM Loopbacks may not work unless all TDM
traffic is looped back.
Workaround: If loopbacks must be used when in Layer 1 LAG, then all TDM flows
must be looped back.
L1 LAG Ethernet PM counters With no user traffic on the radio, the L1 LAG Ethernet PM counters still show
frame counts. L1 LAG Ethernet Statistics take into account internal
management traffic too.This means that counter will show this traffic on top
of customer data. As an example, in case of null customer traffic, Ethernet
Statistics show a value different from zero due to the internal management
traffic.
VLAN Rate Limiting When in 802.1q mode, after a VLAN has been provisioned with the rate limiting
function, new members may not be added.
Workaround: Remove all associated VLAN rate limiters before adding new
members to a VLAN.
Threshold Cross Alarms on DS1 and E1s Present Threshold Cross Alarms on DS1 and E1s are not cleared if the DS1 or E1
port is disabled and the PM not stopped.
Workaround: Disable PM via the WTPMS tool before disabling the E1/DS1 port.
Changing VLAN Rate Limiter The VLAN rate limiter allows a large burst of frames (full rate) when changing
the VLAN rate limiter.
Workaround: None
RUM alarm with Protected Core-E and
MPT Ports
If the system is provisioned with CORE-E Protection and SFP port is provisioned
then configured as MPT-HC port, there will be a standing Replaceable Unit
Missing Alarm on the Spare CORE-E.
Workaround: CORE-E Protection is not supported when MPT-HC is connected to
the CORE-E.
Using the MPT-ACC card as a PFoE source When using the MPT-ACC card as a PFoE source the MPT-HC does not need to
be provisioned on that card, otherwise the system will generate unnecessary
Alarms.
TTO counter TTO counter may not be accurate at high data rates and update time greater
than 30 seconds.
Workaround: Set update time below 30 seconds.
Storm control and Port Rate Limiting
with SSM and TDM Cross Connections
Enabling Storm Control or Port rate limiting on an Ethernet port that is used
with SSM, TDM Cross Connections (especially multicast, Protected PDH traffic)
or TMN traffic could affect the performance of those services.
Workaround:
SSM: rate limiting this port can cause sync source switching and impact
traffic.
TDM: Rate limiting or Storm Control (multicast) can drop TDM traffic
TMN: Rate limiting and Storm Control can drop TMN packets or interrupt
OSPF LSA's causing loss of visibility
Item Description
(4 of 7)
Release Notice
SW upgrade from R4.0.0 to R4.1.0 on a
NE with LAG L1 plus additional MPT-xC
In the following specific case of a Network Element (NE):
configured in R4.0.0 and simultaneously
using an L1 LAG on slots 3 or 4, and simultaneously
using an MPT-xC not involved in the L1 LAG
if a SW upgrade is performed from R4.0.0 to R4.1.0, after the SW upgrade a
traffic impact could be seen on the MPT-xC not included in the L1 LAG, after a
Core-E switch or a NE restart.
Workaround: in these very specific conditions a Backup and Restore on the NE
will solve the issue.
Upgrading to R4.1.0 using the MPTACC After upgrading to R4.1.0 using the MPTACC and then migrating to L1LAG on
EAS, the MPT-HC needs a power cycle for the module to link up with the
system. Workaround: None
LAG configuration GUI Radio and Ethernet ports may not show up in the LAG configuration GUI. If a
port does not meet certain criteria, such as PPP/RF disabled, ports will not
show up in the list. See the help file for a list of all pre-requisites.
Migrating from Non LAG Configurations
to LAG configurations
When migrating from Non LAG Configurations to LAG configurations, take
caution that there is enough bandwidth on a Single radio for all the TDM or
traffic will drop.
Workaround:
Remove cross-connections, before the L1 migration, in order to fit with the
bandwidth of the LAG. Add the second port and then add remaining flows
(in this use case, one of the DS3 flow shall be removed; DS1 is not enough)
Add the port to the LAG. TDM will be lost but the remote supervision
remains available (there is a minimum guaranteed bandwidth reserved for
TMN).
Operator can proceed with the LAG membership creation adding the second
port.
Bandwidth will be enough again and the traffic will be recovered.
Provisioning a second SFP in an SDHACC
1+1 protection pair
Provisioning a second SFP in an SDHACC 1+1 protection pair fails.
Workarounds:
Provision all SFPs before configuring protection.
Use other slots or cards for additional equipment.
Remove protection before adding the second port. This will disrupt traffic.
Provisioning multiple ERP instances When provisioning multiple ERP instances in the Ring Configuration dialog, the
Craft discards changes without warning when switching to another ERP
instance.
Workaround: Apply changes after editing one ERP instance before moving to
the other ERP instance.
Link Configuration Mismatch alarm Expected behavior: Alarm is addressed to 'Radio Direction' object in AM and
Web Server. 'Navigate to USM' function in AM leads to alarmed object.Observed
behavior: for ODU300, alarm in AM is addressed to 'Dir/Ch' object, and also
navigation to USM leads to this object, that is not alarmed, while is correctly
addressed to 'Dir' object in Web Server/Entity field.
For MPT: in AM is correctly addressed to 'Dir' object, while in Web Server is
erroneously addressed to 'Dir/Ch' object.
RUTM Existing PPP Fail & Dialog Failure / Internal Communication Problem (ICP)
alarms are not cleared when Replaceable Unit Type Mismatch alarm is
detected for the slot.
Navigation Navigation from the Summary Block Diagram to the 1+1 MPT-HL or 1+1 MPT-HC
Traffic Port of Tx-Ch#0 view does not open the view.
Workaround: Open the Radio View from JUSM directly.
Item Description
(5 of 7)
Release Notice
System Maintenance of Core-E If the CORE-E Spare is not fully inserted in a prompt fashion, a Mismatch alarm
may occur.
Workaround: Plug in the CORE-E card promptly according to the
documentation.
VLAN CIR Rate limiter VLAN CIR Rate limiter will not be set correctly if the only the apply button is
clicked.
Workaround: After changing the CIR, the user must hit enter first before
applying the changes.
Spare ACM loop problem alarm When configured in XPIC with 1+1 in AMC mode, if the optical coupling is
removed at the far-end, no spare ACM loop problem alarm is raised.
Workaround: none
MSS-1c
OSPF: NMS1 link down does not update
routing table in same subnet
If the MSS-1c and the MSS-1/4/8 on the same link are on the same subnet, if
the MSS-1c NMS1 link goes down, the OSFP routing tables are not updated
properly.
Workaround: Take care in the TMN configuration not to have the same subnet
for both the MSS-1c and MSS-1/4/8.
Migrating from MSS-1c 10 E1/DS1 to
MSS1c 16 E1/DS1
When migrating from MSS-1c 10 E1/DS1 to MSS1c 16 E1/DS1 no message is
displayed to convert the provisioning.
Workaround: Click on the Refresh button on the MCT.
MPR-e standalone
RTPC Power setting using Sliding option In the MCT, the RTPC slider allows 0.5 db more than the maximum limit.
Workaround: None
MPT QoS Ingress counter In the MCT Ethernet counter view, the back button does not work.
Workaround: None
MPR-e in Single NE with 7705 SAR
Setting line and radio side at the same
time in a MW-link
It is possible to set both the link and radio side loopback for a link.
Workaround: Ensure that you only set the radio side or the line side loopback
independently.
XPIC and 1+1 configuration In Single NE with 7705 SAR mode, 1+1 and XPIC are not supported, even if the
system allows this configuration.
Workaround: A warm start of the MPT will clear any remaining conditions
should the user provision 1+1 and XPIC at the same time.
Crash of MCT or MCT Launcher Occasionally the MCT or MCT launch will unexpectedly close or become
unresponsive if left open for an extended period of time.
Workaround: Close the MCT or MCT launcher when necessary operations are
completed.
RPS in Main MPT not aligned after Traffic
cable plugged in or out in non revertive
mode
After a removal/insertion of the traffic cable on the main MPT, the MCT will
not display the correct protection states on the main MCT.
Workaround: None
After upgrade 1+0 to 1+1: must close and
restart MCT Main to activate the PM
Radio Link
After upgrading a link from 1+0 to 1+1 Radio PM inside the MCT no longer works
properly.
Workaround: Restart the MCT application
Item Description
(6 of 7)
Release Notice
On spare MPT is generated a RUP Alarm
Specific problem is reported as Modem
TX Synch
In a 1+1 configuration if a TX mute on the Main MPT and both Main and Spare
MPT are reset, the spare MPT will have a RUP alarm.
Workaround:
To clear the RUP alarm on the Spare MPT:
Unplug both main and spare PMC card
Power off the Spare MPT
Insert PMC where MPT main is connected (MPT still powered)
Wait for Main radio hop to come up
Insert the PMC where the Spare MPT is connected and at the same time
supply MPT SPARE
MPR-e standalone and MPR-e in Single NE with 7705 SAR
PM view and counters In the MCT may become slow and unresponsive in the PM view when open long
term.
Workaround: Close the MCT when necessary operations are completed.
MCT will not run with 64-bit java The MCT is only supported with 32-bit version of Java.
Workaround: Verify that the PC has 32-bit version of Java.
Item Description
(7 of 7)
Release Notice
Technical support
Use Procedure 3 to find the contact information for technical assistance for a country.
Procedure 3 To find contact information for technical assistance
1 Go to http://support.alcatel-lucent.com.
opens.
3 Under Product Technical Support, select a country. The Alcatel-Lucent Support
Contact Numbers window opens and displays the phone and email contact
information for technical assistance for the selected country.
Customer documentation
This section contains information about downloading product documentation and
providing feedback about documentation.
Accessing customer documentation
The OLCS site gives you access to the latest Alcatel-Lucent customer
documentation, including product manuals and documentation updates. If you are a
new user and require access to this service, please contact your Alcatel-Lucent sales
representative.
Use Procedure 4 to download customer documentation from the OLCS site.
Procedure 4 To download customer documentation from the OLCS
site
1 Go to http://www.alcatel-lucent.com/myaccess.
opens.
3 Choose the product name from the Technical Content for drop-down menu.
4 Click on one of the following hyperlinks:
Manuals and Guidesdisplays a list of customer documents by title and part
number
Release Informationdisplays a list of release notices by title and part number
Release Notice
You can filter the list using the Release drop-down menu.
5 Click on the PDF hyperlink to open or save the file.
Providing feedback about customer documentation
We value your feedback. Direct questions or comments about Alcatel-Lucent
documentation to: documentation.feedback@alcatel-lucent.com.
Release Notice
Glossary
Table 9 lists the 9500 MPR acronyms that are used in this document, and their
expansions.
Table 9 Glossary
Term Description
AM Adaptive Modulation
APS Automatic Protection Switching
ATPC Automatic Transmit Power Control
CBS Committed Burst Size
CIR Committed Information Rate
CSM(E) Core Switching Module
CT Craft Terminal
DC Direct Current
DS1 Digital Signal Level 1
DS3 Digital Signal Level 3
DSCP Differentiated Service Code Point
DWRR Deficit Weighted Round Robin
EAS Ethernet Access Switch
ECID Emulated Circuit Identifiers
EPS Equipment Protection Switch
EW Early Warning
FD Frequency Diversity
FTP File Transfer Protocol
HSB Hot Standby
LED light-emitting diode
MEF Metro Ethernet Forum
MIB Management Information Base
MPR Microwave Packet Radio
MPT Microwave Packet Transport
MSS Microwave Service Switch
NE Network Element
NEtO Network Element Overview
ODU Outdoor Unit
P8ETH Eight Port Ethernet Access Switch (EAS)
PCP Priority Code Point
PDH Plesiochronous Digital Hierarchy
(1 of 2)
Release Notice
PMC Packet Microwave Card
PtP Point to Point
PTx Transmission power
QAM Quadrature Amplitude Modulation
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
RPL Ring Protection Link
RPS Receive protection switch
RSL Receive Signal Level
RTPC Remote Transmit Power Control
RU Rack Unit
SD Space Diversity
SDH synchronous digital hierarchy
SFP Small form-factor pluggable
SFTP Secure file transfer protocol
SONET Synchronous optical networking
SP Strict Priority
SW Software
TCA Threshold Crossing Alert
TFTP Trivial File Transfer Protocol
TPS Transmit protection switch
XPIC Cross Polarization Interference Cancellation
Term Description
(2 of 2)
Release Notice
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 A-1
Release Notice
A. MPR-e and MSS-1c SNMP
management
A.1 MPR-e and MSS-1c SNMP management
The following features related to MPR-e/MSS-1c are supported by any SNMP
manager:
SNMPv2 registration
Alarms (see user manual of MPR-e/MSS-1c for details)
SWP download (transfer and activation)
Radio Transmitted Power (local/remote) statistics
Radio Received Power (local/remote) statistics
A.2 Traffic Ethernet port counters [MPR-e]
Table A-1 shows the supported traffic Ethernet port counters for MPR-e.
Table A-1 Traffic Ethernet port counters [MPR-e]
Note Radio transmitted/Received Power statistics are not
supported by 1350 NM.
Ethernet counter Ingress counter Egress counter
For the Traffic Ethernet port
(1 of 2)
A. MPR-e and MSS-1c SNMP management
A-2 November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Release Notice
A.3 Radio QoS counters [MPR-e/MSS-1c]
Table A-2 shows the Radio QoS counters for MPR-e and MSS-1c.
Table A-2 Radio Qos counters [MPR-e/MSS-1c]
Ingress/Egress number of bytes Yes Yes
Ingress/Egress number of frames Yes Yes
Ingress/Egress number of discarded frames Yes Yes
Ingress/Egress number of Unicast frames Yes Yes
Ingress/Egress number of Broadcast frames Yes Yes
Ingress/Egress number of Multicast frames Yes Yes
Ingress number of Errored frames
This counter is the sum of the following counters:
Total Number of RX FCS Error Packets
Total Number of RX Alignment Error Packets
Total Number of RX Fragment Error Packets
Total Number of RX Undersize Error Packets
Total Number of RX Oversize Error Packets
Yes N/A
Ethernet counter Ingress counter Egress counter
(2 of 2)
Ethernet counter Counters
Pure Ethernet traffic QoS queues counters (queue from 1 to 5)
Queue 1: Frames Discarded (Number of frames that
were discarded at the entrance of the queue)
Yes
Queue 1: Frames in (Number of frames which have been
placed in the queue)
Yes
Queue 1: Number of Tx Bytes (which have been placed
in the queue)
Yes
Queue 2: Frames Discarded (The number of frames that
Yes
Yes
in the queue
Yes
Yes
Yes
in the queue)
Yes
Yes
(1 of 2)
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 A-3
Release Notice
Yes
in the queue)
Yes
Yes
Queue 5: Frames in (Number of which have been placed
in the queue)
Yes
in the queue)
Yes
Aggregate: Frames Discarded (Number of frames that
were discarded at aggregate level (sum of the queues))
Yes
Aggregate: Frames in (Number of frames which have
been placed at aggregate level (sum of the queues))
Yes
Aggregate: Number of Tx Bytes (which have been placed
at aggregate level (sum of the queues))
Yes
Ethernet counter Counters
(2 of 2)
A-4 November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Release Notice
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 B-1
Release Notice
B. Previous release capabilities
B.1 Capabilities in R4.0.0
Legend:
[MSS4/8]the feature applies to the MSS4/8 system only
In Service software upgrade from 9500 MPR R3.2.0 to R4.0.0
SNMPv3 support [MSS4/8]
Per-CoS rate Limiter [MSS-4/8]
User configurable label on traffic interfaces [MSS4/8]
TMN in-band with L2 Ethernet LAG
MPR-e repeater back to back support [MPR-e]
SNMPv3 support [MSS4/8]
The 9500 MPR supports access from SNMP managers implementing SNMPv3 or
SNMP v2/v1.
TACACS+ is not supported on the SNMP interface when the NE is in SNMPv3
mode. The NE doesnt operate in SNMPv3 mode when TACACS+ is enabled on the
SNMP port.
B-2 November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Release Notice
Per-CoS rate Limiter [MSS-4/8]
A Per-VLAN Per-CoS Rate Limiter can be applied to each User Ethernet interface
(of Core card and/or of EAS card) for ingress direction.
The rate limiter is applied to a tagged Ethernet flow classified according to the value
of VLAN ID and PCP fields of the VLAN Tag. One VLAN ID value and one PCP
value identifies the flow.
The VLAN IDs to which the Per-VLAN Per-CoS Rate Limiter can be applied are the
ones that have the User Ethernet interface belonging to their member set.
You can specify the value "Any" as the VLAN ID; in that case the tagged Ethernet
flow will be classified according to the value of the PCP field only.
The parameters of Per-VLAN Per-CoS Rate Limiter are CIR and CBS. The Per-
VLAN Per-CoS Rate Limiter is managed according to a Token Bucket algorithm:
Ethernet frames that do not find available tokens are dropped. CIR refers to Ethernet
throughput not taking into account Preamble and IFG. CIR can be configured in the
range from 0 Kbit/s to 1 Gbit/s at step of 64 Kbit/s.
CIR equal to 0 Kbit/s means drop of the Ethernet flow.
CBS can be configured in the range from 4 Kbytes (4096 bytes) to 16 MBytes. The
allowed values are:
4 Kbytes;
8 Kbytes;
16 Kbytes;
32 Kbytes;
64 Kbytes;
128 Kbytes;
256 Kbytes;
512 Kbytes;
1 Mbytes;
2 Mbytes;
4 Mbytes;
8 Mbytes;
16 Mbytes
Default value for CIR is 64 Kbit/s, default value for CBS is 16 Kbytes.
The Per-VLAN Per-CoS Rate Limiter can be applied to User Ethernet interfaces of
Core board and EAS peripheral.
Up to 16 Rate Limiters can be activated per User Ethernet interface, up to 32 Rate
Limiters can be activated on a Core-E card and up to 32 Rate Limiters can be
activated on each EAS peripheral.
The feature can be enabled and configured only when the User Ethernet interface is
enabled and the Bridge mode is 802.1Q (Virtual Bridge).
The User Ethernet interface can't be disabled when the Per-VLAN Per-CoS Rate
Limiter feature is enabled.
Release Notice
When a Per-VLAN Per-CoS Rate Limiter is enabled on a VLAN ID, any
modification of the parameters of the VLAN or the removal of the VLAN from the
VLAN Table is not allowed.
On the same User Ethernet interface the activation of Rate Limiter on an Ethernet
flow identified by PCP value only (VLAN ID = "Any") when there is already a Rate
Limiter active on an Ethernet flow identified by a specific VLAN ID and by the same
PCP value of the previous flow and vice versa is not supported.
On the same User Ethernet interface, the activation of Per-VLAN Per-CoS Rate
Limiter on an Ethernet flow identified by a VLAN ID value already used to perform
a VLAN Rate Limiter is not allowed.
The activation of Per-VLAN Per-CoS Rate Limiter on an Ethernet flow identified by
PCP value only (VLAN ID = "Any") when there is already at least one VLAN Rate
Limiter activated on the same User Ethernet interface is not supported.
It should be noted that when Per-VLAN Per-CoS Rate Limiter is activated in
conjunction with Port Rate Limiter, the Per-VLAN Per-CoS Rate Limiter applies to
Ethernet frames that meet the Port Rate Limiter parameters. It's up to the operator to
guarantee that rate limiters settings were compatible and do not create conflict with
Ethernet traffic pattern ingressing the User Ethernet interface.
Being the process which changes the C-VLAN ID (From) to C-VLAN ID (To)
implemented in the egress pipeline of the Ethernet Switch, while the Per-VLAN Per-
CoS Rate Limiter is implemented in the ingress pipeline, the Per-VLAN Per-CoS
Rate Limiter is not applicable in conjunction with CVLAN Translation unless
VLAN ID "Any" value is selected.
User configurable label on traffic interfaces [MSS4/8]
The CT allows the Operator to configure a User Label on Ethernet User Ports.
The configuration is supported on:
Core-E Ethernet User Ports
EAS peripheral Ethernet User Ports
In case of Ethernet LAG, the User Label of the group (that is, the LAG Name
parameter) is independent from User Labels of Ethernet Ports belonging to the LAG:
it is possible to configure one User Label for the Ethernet LAG and one User Label
for each interface belonging to it.
User Label length and the set of characters admitted are the same as those of Radio
Direction Label.
The CT allows the Operator to configure a User Label on an interface of a PDH
peripheral.
The configuration is supported on E1 ports.
CT allows the Operator to configure a User Label on an interface of an SDH
peripheral.
The configuration is supported on STM-1 Ports of an SDH Transparent peripheral
and E1 Ports of an SDH Channelized peripheral.
Release Notice
User Label length and the set of characters admitted are the same as those of Radio
Direction Label.
TMN in-band with L2 Ethernet LAG
The Ethernet ports involved in an L2 LAG can be used as TMN in-band interfaces.
You need to configure the TMN in-band before can be creating the LAG. After the
LAG has been created, TMN in-band cannot be created unless the LAG is removed.
Procedure B-1 is the general procedure for configuring TMN in-band with L2 LAG.
Procedure B-1 High-level procedure for configuring TMN in-band
with L2 LAG
TMN in-band configuration
1 Set the parameters of the interface.
2 In the Associated Ethernet Ports panel, select all the user interfaces that have to
be included in the LAG.
3 Enable the TMN In-Band interface.
LAG configuration
4 Create the LAG.
5 Add user interfaces to the group.
6 Enable the LAG.
MPR-e repeater back to back support [MPR-e]
A 1+0 repeater configuration can be setup with two MPR-e placed back to back as
shown in Figure B-1.
Note 1 After Procedure B-1 has been performed, TMN In-Band
parameters cannot be changed, for example, the interface cannot be
disabled.
Note 2 User interfaces belonging to the LAG are not shown in the
Associated Ethernet Ports panel of the TMN In-Band interface.
Release Notice
Figure B-1 MPR-e 1+0 repeater configuration
This solution is available with MPT-HC and MPT-XP with:
Data exchanged between the two MPR-e through an optical link only
Synchronization configured in SynchE
No XPIC support
Supported Services: TDM2ETH, Ethernet traffic
Powering of MPTs shall be assured through either direct connection to battery or to
other means.
Legend:
In service software upgrade from 9500 MPR R3.2.0 to R3.4.0
In service software upgrade from 9500 MPR R3.3.0 to R3.4.0
Multichannel Link Aggregation L1 [MSS-4/8]
MPT connected to EAS card [MSS-4/8]
Port rate limiter [MSS-4/8]
Storm control [MSS-4/8]
Per VLAN rate limiter [MSS-4/8]
VLAN swap [MSS-4/8]
Additional modem profiles [MSS-4/8 and MPR-e]
Fiber/microwave protection [MSS-4/8]
MPT-MC: new modem profiles support, up to 256QAM/56 MHz [ALL]
TACACS+ [MSS-4/8]
Release Notice
Multichannel Link Aggregation L1 [MSS-4/8]
Layer1 Link Aggregation allows the aggregation of multiple radio links in order to
obtain a unique logical connection with increased traffic capacity.
A Link Aggregation Group (LAG) represents the group of links bundled together
between two Aggregation Systems (NEs connected through the LAG).
In a Layer1 Link Aggregation, the Distributor performs a packet-based traffic
distribution over multiple links regardless of the content of packet itself. Distributor
takes into account the number of bytes sent over a specific link and loads links
according to the available bandwidth.
Consequently, Layer1 Link Aggregation allows a traffic load balancing
independently of traffic content. Since the distribution does not depend on Layer2 or
Layer3 header content, this kind of Link Aggregation is called Layer1 (i.e.,
associated with the physical layer).
On the contrary, traffic distribution in a Layer2/Layer3 Link Aggregation is
performed avoiding mis-ordering on the transmitter side and relying on Layer2/
Layer3 fields contained in transmitted frames: an even traffic load balancing can be
achieved if Layer2 (or Layer3) fields (e.g., Destination MAC Address, Source MAC
Address, VLAN ID, and so on) of the incoming traffic are equally distributed.
Supported configurations
Layer1 LAG is supported on the EAS peripheral plug-in.
Layer1 LAG is supported on the following Radio Interface:
1+0 MPT-HC connected to EAS Plug-in SFP ports
The maximum number of Layer1 LAG in a NE is 2. It is not allowed to configure
more than two LAGs per MSS row (two Plug-ins on Slots on the same row).
Two different configurations are supported:
LAG with MPTs belonging to the same Plug-in (Intra Plug-in Link Aggregation)
LAG with MPTs belonging to two Plug-ins on the same MSS4/8 row (Cross
Plug-in Link Aggregation)
Description of supported scenarios
Intra Plug-in LAG L1
Figure B-2 shows an example. An Intra Plug-in LAG, composed of 4 Radio Links,
is created on NE A.
On NE B, two Intra Plug-in LAGs are created in order to implement a radio repeater
configuration.
In case of Plug-in failure, the associated LAG direction is lost.
Release Notice
Figure B-2 Intra Plug-in LAG L1
Figures B-3 and B-4 show supported scenarios for Intra Plug-in LAG L1.
Figure B-3 Intra Plug-in LAG L1 scenario
Figure B-4 Intra Plug-in LAG L1 scenario
Cross Plug-in LAG L1
Figure B-5 shows an example of a cross plug-in LAG L1. In this scenario, a Cross
Plug-in LAG, composed of 4 Radio Links, is created on NE A.
On NE B, two Cross Plug-in LAGs are created in order to implement a radio repeater
configuration.
In case of Plug-in failure, LAG capacity is reduced but the radio direction is still
available thanks to the remaining radio interfaces on the other Plug-in.
Release Notice
Figure B-5 Cross Plug-in LAG L1
Figure B-6 shows supported scenarios for Cross Plug-in LAG L1.
Figure B-6 Cross plug-in LAG scenarios
LAG L1 configuration
A Link Aggregation Group is created providing following parameters:
LAG ID
LAG Name
LAG Type
LAG Size
Administrative Status
At the creation, the Administrative Status is Disabled. The Wait To Restore of the
LAG is set to the default value of 1 second.
LAG Identifier
LAG ID is an integer parameter that identifies the Link Aggregation Group in the
NE. It is a mandatory parameter that shall be provisioned by the Operator at LAG
Creation and cannot be modified later. Applicable range for LAG ID is the integer
range from 1 to 14. System prevents the creation of a LAG with same LAG ID of an
existing one. Additionally, it is not allowed to create a LAG with LAG ID equal to
the Administrative Key of an existing Layer2 LAG.
LAG Name
LAG Name is a string associated to the LAG that can be used by the Operator to
easily identify the virtual radio direction. It is an optional parameter (an empty value
is set by default) and can be modified run-time. LAG Name has no dependency with
Operator Label of single radio interfaces belonging to the LAG.
LAG type
Release Notice
LAG Type identifies the Layer1 Radio Link Aggregation and must be set
accordingly (i.e., L1 Radio). It is a mandatory parameter that shall be provisioned by
the Operator at LAG Creation and cannot be modified later.
LAG size
LAG Size represents the maximum number of links in the LAG. It is a mandatory
parameter that shall be provisioned by the Operator at LAG Creation. LAG Size can
be changed at run-time. LAG Size cannot be lower than the number of links
belonging to the LAG. From a LAG Size perspective, Main and Spare MPTs
belonging to a 1+1 Protection Group are counted as one link.
LAG L1 configuration modification
Following parameters can be modified after the LAG creation:
LAG Name
LAG Size
Wait To Restore time
The WTR time value is configurable in the following ranges:
LAG L1 activation and deactivation
Operator can configure the Administrative State of an existing LAG. If the LAG is
Disabled, no traffic is sent out from the LAG. Moreover, generic PDUs (e.g., SSM,
CCM) and TMN RF traffic is dropped.
The system prevents the Activation of a LAG with no port associated: at least one
port shall belong to the Group.
After the Activation, the LAG can be:
involved in a Cross-connection
part of a 802.1Q VLAN port membership
selected as Synchronization Reference
A LAG cannot be Disabled if:
Cross-connections are configured on LAG
LAG is part of any 802.1Q VLAN, except VLAN 1 (default VLAN)
LAG in selected as Synchronization Reference
100 ms
200 ms
300 ms
400 ms
500 ms
600 ms
700 ms
800 ms
1 s
2 s
3 s
4 s
5 s
6 s
7 s
8 s
Release Notice
LAG alarms (LAG LOS or LAG Degrade) are reported to CT/NMS, according to
LAG current status, only if the LAG is Enabled.
LAG L1 deletion
A LAG can be Deleted only if:
its Administrative State is Disabled
no ports are member of the LAG
Port Add and Remove operations
Operator can change the LAG Port Membership performing Port Add/Remove
operations.These operations shall respect restrictions and provisioning rules
described below.
The Operator shall perform a TX Mute on the radio to be added to a LAG with
Enabled Administrative Status.
The TX Mute must not be removed until the mating ports have been added to the
LAG at each end of the link.
These operations block traffic from being prematurely distributed to the new port,
avoiding traffic loops and any traffic outages due to temporary asymmetric LAG
memberships on the two NEs.
The same TX Mute operation is required before the removal of a radio from a LAG
with Enabled Administrative Status.
If the LAG is Enabled, the System shall prevent the addition/removal of a link with
TX Mute disabled. This check is performed by ECT/NMS only and not by the NE.
The Operator is in charge of the TX Mute operation.
Segregation and TMN-RF require at least one radio link in the group. For this reason,
it is not allowed the removal of the last port from a LAG having a Segregation
configured or TMN-RF enabled.Additionally, if the Administrative State of the LAG
is Enabled, it is not allowed the removal of the last port. At least one port shall belong
to a LAG with Administrative State enabled.
During any Port Add/Remove operation a traffic impact could be experienced on the
updated LAG and/or on the other LAG on the same MSS row.
Master port definition
For each Link Aggregation Group, the first port provisioned inside the group is
defined as the Master port.
Considering EAS port indexing (comprising RJ45 ports), the Master Port can be
Port5 or Port7 according to the different scenarios, meaning that the first port to be
provisioned is either 5 or 7.
In case of IntraEAS LAG, only one Master Port is reserved (either Port5 or Port7)
In case of CrossEAS LAG, homologous ports are reserved on both EAS as Master
Ports (e.g., both Port5 on EAS on the same row).
Release Notice
Only one of the two Master Ports is used. The other Master Port is used as spare
interface in case of failure of the EAS hosting the Active Master Port. Figure B-7
illustrates Master ports in LAG L1.
Figure B-7 Master port definition
Port provisioning rules
During Port Add/Remove operations, the following rules shall be followed:
considering the Slot, Master Port shall have the lowest index in the LAG port
membership (i.e., if Master Port is Port7, Port6 cannot be added)
the set of ports added to the LAG shall be adjacent considering the Slot (i.e., no
holes are allowed in the LAG port membership filtered by Slot)
in case of Cross Plug-in LAG, the maximum number of Ports per Slot is 2 (i.e., it
is not possible to aggregate 3 ports on one Plug-in and 1 on the other one)
the Master Port cannot be changed (if Master Port is Port7, Port5 and Port6 cannot
be added to the LAG since Port5 would become the new Master Port) and it is not
possible to add an homologous Master Port with slot/port that is lower in value
than the current Master Port slot/port of the LAG.
Rules are applied to LAG Port Add and LAG Port Remove operations considering
the new port membership. For example, even if only one port is added to an existing
LAG, checks are performed on the entire set of ports. A port that is already part of a
LAG cannot be added to another Link Aggregation Group.
Allowed configurations
Considering previous rules, these are the configurations allowed for a single Link
Aggregation Group. For Cross Plug-in LAG, lines between Slots represent possible
combinations. Figure B-8 illustrates the configurations.
Release Notice
Figure B-8 Allowed configurations
Adaptive Modulation and modem profiles
Aggregated Radio Links shall have the same Modem Profiles:
Checks are performed by the System to prevent the aggregation of radios with
different modem profiles.
Once a radio has been added to the LAG, modem profiles cannot be changed.
The selected Modulation Scheme shall be the same for all Radio Links in the LAG.
Additionally, Radio Links in Adaptive Modulation cannot be added to the LAG.
XPIC modem profiles are supported with LAG L1.
Service restrictions
As a general rule, a port to be added to a LAG shall not have any of the following
configured:
Cross-connection
VLAN
Port Segregation
Additionally, the following conditions shall be satisfied for the port to be added to
the LAG:
TMN-RF shall not be enabled on that interface
the interface shall not be configured as Synchronization reference
SSM shall not be enabled on that interface
All services and segregations shall be removed from the radio by the Operator before
adding it to the LAG.
User ports and radio interfaces
Electrical and Optical EAS ports not belonging to a LAG can be used as User Ports
or Radio Interfaces (SFP ports only) both in 1+0 and 1+1 (MPT-HL only).
Release Notice
1+1 MPT-HC Protection Groups are not supported on the EAS Plug-in.
Radio QoS configuration
After a Radio is added to the LAG, all NE QoS settings (i.e., QoS Scheduler settings,
QoS Mapping) and Radio Queue sizes previously configured on that specific radio
are lost.
Radio Queue size configuration for that radio interface are available to the Operator.
NE QoS settings are applied again to the radio interface whenever it is removed from
the LAG. On the contrary, Radio Queue sizes are set to default configuration.
Supported services and configurations
The following services are supported over Layer1 LAG:
Ethernet Services
Cross-connections: see SR ID TRAF_MGMT-12700 for detailed list
Maximum throughput
The Radio LAG throughput cannot be higher than the capacity available at the back
panel (1 Gbit/s).
LAG rate
LAG Rate represents the total capacity of the Radio LAG bundle.
This value has to be made available to the Operator in order to configure properly the
amount of services to be carried through the LAG. It depends on the number of links
added to the bundle and the Capacity of each Radio Links.
In this release, since all the Radio Links in the LAG shall have the same modem
profile, the LAG Rate is calculated by multiplying the Capacity of one of the Radio
Links by the number of links in the LAG membership. If none of the Radio Links in
the LAG is online, since the NE is not able to retrieve the actual Capacity, a default
value of 400Mbps is used for the LAG Rate computation.
Maximum Ethernet frame length
Two scenarios are available to the Operator:
Mixed TDM and Ethernet Scenario: maximum Ethernet frame length is 1540
bytes. It is up to the Operator to not introduce traffic with higher frame lengths.
If this constraint is not respected, traffic hits can occur on TDM flows.
Additionally, since the competition frames length is reduced, PDV is reduced on
TDM traffic and a higher number of hops can be supported.
Pure Ethernet Scenario: maximum Ethernet frame length is 9728 bytes. No TDM
traffic present. The system does not apply any specific configuration (e.g., MTU)
to avoid TDM traffic impacts.
Release Notice
Admission control
Admission Control is not performed on LAG. The operator should ensure that
bandwidth of cross-connected traffic does not overcome the capacity of one single
radio link of the LAG.
CES Layer2 Ethernet bandwidth of the cross-connected flow has to be taken into
account during this procedure. The system does not perform any check on the correct
bandwidth allocation.
Maximum number of cross-connections
The maximum number of E1/DS1 Cross-connections supported over a Layer1 LAG
is 254.
Segregations
The following Segregation configurations involving a LAG are supported:
LAG can be Segregated with a User Port, MPTs or LAG belonging to the same
EAS or the EAS on the same MSS row.
Intra Plug-in LAG can be Segregated with an interface of the Core. This operation
implies the Segregation of the entire Plug-in slot with the Core interface.
Cross Plug-in LAG can be Segregated with an interface of the Core. This
operation implies the Segregation of both Plug-in slots, hosting the LAG, with the
Core interface
Intra to Cross Plug-in LAG changes (if applicable, based on Port Provisioning
Rules), due to the Port Add operation, are handled in the following way:
Plug-in slot Segregation (with an interface of the Core), is replicated on the mate
Plug-in slot
Internal Segregation, between a Plug-in interface and the LAG Master Port, is
replicated on the homologous port on the other Plug-in
Cross to Intra Plug-in LAG changes (if applicable, based on Port Provisioning
Rules), due to the Port Remove operation, are handled in the following way:
Plug-in slot Segregation (with an interface of the Core), is removed on the mate
Plug-in slot. This action is not performed if the slot hosts other Cross Plug-in
LAG or 1+1 MPT Protection Group.
Internal Segregation, between a Plug-in interface and the LAG Master Port, is
removed on the homologous port on the other Plug-in
A LAG involved in a Segregation shall have at least one port in the group. This
requirement has to be considered by the System to deny illegal Port Remove
operations.
Synchronization
Layer1 LAG can be selected as a Synchronization Reference.
From the system perspective, the Layer1 Radio LAG direction has to be managed as
a single logical synchronization interface.
Release Notice
According to LAG Administrative State, the system checks that:
LAG interface can be selected as Synchronization Reference only if it is Enabled
If a LAG is configured as Synchronization Reference, it cannot be Disabled
Physical radio interfaces belonging to the LAG cannot be selected as
Synchronization References.
The System automatically selects one of the radio links, belonging to the LAG
chosen as Synchronization Reference, according to the alarm status of single
interfaces. In case of synchronization failure of the selected reference, the NE
performs a selection switch on another interface belonging to the same group
(passing through the Holdover). This selection is performed looking for a non-
faulted interface in the LAG.
This synchronization selection process is non-revertive.
All the synchronization interfaces in the LAG have the same quality (because they
are traceable to the same node):
whenever the faulted interface becomes available again (after a failure recovery), the
selected input is kept on the current valid synchronization interface.
A LAG Synchronization Reference is no longer valid if none of the radio interfaces
of the Group represents a valid synchronization source (Synchronization Fail).
A LAG Synchronization Reference is no longer valid if the degrade alarm is detected
on the selected radio interface of the Group (Synchronization Degrade). The
detection of a synchronization degrade alarm on the selected reference has to be
considered as a degraded condition of the whole radio direction, since it is related to
the quality of the clock supplied by the remote NE.
Any other synchronization problem related to radio interfaces involves a
synchronization fail event (and not degrade) and is managed according to the
synchronization failure case described above in this requirement.
SSM
SSM is configured (Enabled/Disabled) on the logical LAG interface. Since the LAG
represents a unique logical Radio interface, a single ESMC (Ethernet
Synchronization Messaging Channel) is established over the Group to deliver/
retrieve the QL to/from the connected Synchronization Node.
SSM configuration of single Radio interfaces belonging to the LAG shall not be
available. As soon as a Radio is added to the LAG, SSM configuration of that
interface shall be denied to the Operator.
TMN-RF configuration
A Radio interface with TMN-RF Enabled cannot be added to a LAG. The Operator
shall disable it before the Port Add operation.
This restriction is not applicable to the first Master Port added to the LAG.
TMN-RF configuration of single Radio interfaces belonging to the LAG shall not be
available. As soon as a Radio is added to the LAG, TMN-RF configurations of that
interface shall be denied to the Operator.
Release Notice
TMN-RF configuration is available at the group level. The entire LAG direction is
represented as a unique PPP-RF interface. At the LAG creation, TMN-RF is
Disabled by default. TMN-RF can be enabled when at least one radio interface
belongs to the LAG.
The last interface in the LAG cannot be removed until TMN-RF is disabled on LAG.
The Operator shall deactivate LAG and disable TMN-RF before removing the last
radio interface in the LAG.
In order to disable PPP-RF, all IP Static Route entries involving that interface shall
be removed.
LAG alarms
The following LAG alarms are supported and shown at ECT/NMS:
LAG Degrade: the number of active interfaces is lower than the LAG Size
LAG LOS: all the interfaces of the LAG are down
LAG alarms (LAG LOS or LAG Degrade) shall be reported to CT/NMS, according
to LAG current status, only if the LAG is Enabled.
Switching criteria
The following defects are used by the Layer1 LAG logic to remove radio links from
the group:
MPT Card Fail
Card Fail (EAS peripheral)
Card Missing (EAS peripheral)
Card Mismatch (EAS peripheral)
Demodulator Fail
LOF of aggregate signal radio side
Remote Defect Indication (RDI) coming from remote end
Ethernet link LOS (MSS-MPT link)
SFP Card Missing (MSS-MPT link)
SFP Card Fail (MSS-MPT link)
HBER (High BER)
Link Identifier Mismatch (LIM) alarm
Incompatible Frequency alarm
Incompatible Shifter alarm
Incompatible Power alarm
Incompatible Modulation Parameters alarm
Remote defect indication
Following defects shall be used by MPT as criteria for Remote Defect Indication
(RDI) to be forwarded to the remote NE on the other side of the radio link:
MPT Card Fail
Demodulator Fail
Release Notice
LOF of aggregate signal radio side
Link Identifier Mismatch (LIM)
HBER
For MPT-HC, an Ethernet link LOS (MSS-MPT link) generates a Tx Mute: for this
reason, it is not necessary any RDI generation.
For MPT-HC, the following additional defect shall be used as RDI generation
criteria:
MPP Timeout (no reception of MPP frames) detected MSS side
In case of MPT-HC, MPP Timeout detected MPT side generates a Tx Mute: for this
reason, RDI generation is not necessary.
Wait to restore
After a failure condition on a radio interface in the LAG, a Wait to Restore time,
started at the alarm clearing instant, shall be applied on that interface. Once the WTR
time is expired, the link can be put back as member of the LAG.
WTR shall not be applied to the restoration of a single channel belonging to the 1+1
radio direction.
In case of 1+1 Protection Groups belonging to a LAG, hardware failures of the
transmitter or operator commands on TPS/EPS can cause a temporary double failure
at the receiver side. In this scenario, a short TDM traffic hit is experienced (same
entity as the traffic impact observable on not-LAG TPS switchovers) and, on top of
this, the Layer1 LAG capacity could be reduced (since the 1+1 Protection Group is
removed for a period equal to the WTR time.
Propagation issues in SD/FD do not have impacts on Layer1 LAG thanks to the RPS
that recovers the traffic.
Propagation issues in HSB configuration (or on both channels in case of SD/FD) and
double radio failures imply the removal of the Protection Group from the LAG.
The LAG capacity reduction period, here described, can be decreased setting a lower
WTR value. The Operator is in charge of configure the proper WTR value,
considering that a low WTR period could not be suitable in case of fast/intermittent
failure conditions.
The following cross-connection are supported, in case of LAG L1 with MPT-HC:
from LAG L1 to E1/DS1 TDM2TDM/TDM2ETH profiles of PDH card
from LAG L1 to E1 TDM2TDM/TDM2ETH profiles of SDH channelized card
Radio-to-Radio cross connections between LAG L1 and ODU300 radio
Radio-to-Radio cross connections between LAG L1 and MPT-HC/MC connected
to MPT access card
to core card
Radio-to-Radio cross connections between LAG L1 and MPT-HL connected to
EAS card
Radio-to-Radio cross connections between LAG L1 and MPT-HC connected to
EAS card
Release Notice
Radio-to-Radio cross connections between LAG L1 and MPT-HC/MC involved
in a ring
Radio-to-Radio cross connections between LAG L1 and another LAG L1 with
MPT-HL
MPT-HC
The following cross-connection are supported, in case of LAG L1 with MPT-HL:
from LAG L1 to E1/DS1 TDM2TDM/TDM2ETH profiles of PDH card
Radio-to-Radio cross connections between LAG L1 and ODU300 radio
to MPT access card
to core card
Radio-to-Radio cross connections between LAG L1 and MPT-HL connected to
EAS card
Radio-to-Radio cross connections between LAG L1 and MPT-HC connected to
EAS card
Radio-to-Radio cross connections between LAG L1 and MPT-HC/MC involved
in a ring
MPT-HL
ODU300
MPT connected to EAS card [MSS-4/8]
An MPT-HC can be connected to EAS card in 1+0 configuration, through optical
SFP connections (port#5 through #8); an MPT Power Unit or a power injector card
or an MPT access card (that provides power through RJ45 Power Feed over Ethernet
connector) shall be used to feed power.
When an MPT is connected to EAS card, the following configurations are not
supported:
Ring topology (ERPS)
1+1 Radio protection
Radio LAG L2/L3
Power Source Management and related alarm
When MPT is connected to EAS card, the following cross-connections are
supported:
E1/DS1 TDM2TDM/TDM2ETH profiles
SDH channelized card - E1 TDM2TDM/TDM2ETH profiles
Radio-to-Radio cross connections with MPT-HC/MC connected to core card
Radio-to-Radio cross connections with another MPT-HC connected to EAS card
Radio-to-Radio cross connections with MPT-HC/MC connected to MPT access card
are not supported.
Release Notice
SDH (STM-1 and OC3) transparent flows are supported by MPT connected to EAS
card.
It is possible to provision up to 4 MPTs on the same EAS card, each in 1+0
configuration only.
The XPIC function can be configured in the cases where an MPT is connected to an
EAS Peripheral port that has been provisioned for connection to MPT.
Port rate limiter [MSS-4/8]
A Rate Limiter can be applied to each User Ethernet interface for both ingress and
egress direction.
The parameters of Rate Limiter are CIR (Committed Information Rate) and CBS
(Committed Burst Size). The Rate Limiter is managed according Leaky Bucket
algorithm, Ethernet frames that do not find room in the Bucket are dropped at ingress
or buffered at egress until there is room in the bucket. Ingress frames are also
dropped if there is insufficient room in the packet buffer memory. CIR is referring to
Ethernet throughput not taking into account Preamble and IFG.
CIR can be configured in the range from 64 Kbit/s to 1000000 Kbit/s at step of 64
Kbit/s.
CBS can be configured in the range from 4 Kbytes (4096 bytes) to 16 MBytes at step
of 4 Kbytes.
The default value for CIR is 64 Kbit/s; default value for CBS is 12 Kbytes.
The Rate Limiter can be applied to User Ethernet interfaces of Core board and EAS
peripheral.
Ingress Rate Limiter and Egress Rate Limiter can be enabled or disabled
independently.
enabled and the Bridge mode is either 802.1D (MAC Bridge) or 802.1Q (Virtual
Bridge).
The User Ethernet interface can't be disabled when the Port Rate Limiter feature is
enabled.
It should be noted that when VLAN Rate Limiter is activated in conjunction with
ingress Port Rate Limiter, the VLAN Rate Limiter applies to Ethernet frames that
meet the ingress Port Rate Limiter parameters.
The operator must ensure that rate limiters settings are compatible and do not create
conflict with Ethernet traffic pattern ingressing the User Ethernet interface.
Storm control [MSS-4/8]
This feature allows restricting the number of incoming broadcast, multicast or
unknown (not already learned) traffic in a 1 second interval on a specific User
Ethernet interface.
If, in a 1 second time interval, the number of broadcast, multicast and unknown
Ethernet frames exceeds the configured limit, the dropping mechanism is applied.
Release Notice
The parameters the operator is able to configure are the frame rate (Frame/s)
threshold of broadcast traffic, the frame rate (Frame/s) threshold of multicast traffic
and the frame rate (Frame/s) threshold of unknown frames traffic.
Frame rate threshold can be configured in the range from 1 Frame/s to 16777215
Frame/s for all. Default is 100 Frame/s for all.
The application of Storm Control is enabled or disabled at the same time for all the
types of frames.
The Storm Control can be applied to User Ethernet interfaces of the Core board and
the EAS peripheral.
enabled and the Bridge mode is either 802.1D (MAC Bridge) or 802.1Q (Virtual
Bridge).
The User Ethernet interface cannot be disabled when the Storm Control feature is
enabled.
Per VLAN rate limiter [MSS-4/8]
A VLAN Rate Limiter can be applied to each User Ethernet interface for ingress
direction.
The VLAN IDs where you can apply the VLAN Rate Limiter are the ones which
have the User Ethernet interface belonging to their member set.
The parameters of VLAN Rate Limiter are CIR (Committed Information Rate) and
CBS (Committed Burst Size). The VLAN Rate Limiter is managed according to the
Token Bucket algorithm: Ethernet frames that do not find available tokens are
dropped. CIR is referring to Ethernet throughput not taking into account Preamble
and IFG.
CIR can be configured in the range from 64 Kbit/s to 32 Gbit/s at step of 64 Kbit/s.
CBS can be configured in the range from 4 Kbytes (4096 bytes) to 2 MBytes. The
allowed values are:
4 Kbytes
8 Kbytes
16 Kbytes
32 Kbytes
64 Kbytes
128 Kbytes
256 Kbytes
512 Kbytes
1 Mbytes
2 Mbytes
The default value for CIR is 64 Kbit/s, default value for CBS is 16 Kbytes.
The VLAN Rate Limiter can be applied to User Ethernet interfaces of Core board
and EAS peripheral. Any port ingress rate limiting is applied to the traffic flow
before the VLAN rate limiting. This will affect the VLAN rate limiting behavior.
Release Notice
The maximum number of VLAN IDs for User Ethernet interface where the Rate
Limiter can be activated is 8.
The User Ethernet interface can't be disabled when the VLAN Rate Limiter feature
is enabled.
VLAN swap [MSS-4/8]
A C-VLAN Translation can be applied to each User Ethernet interface, the
translation is applied bi-directionally.
The C-VLAN ID (for example, From) of tagged frames entering the User Ethernet
interface is changed to a new C-VLAN ID (for example, To). At the same time the
C-VLAN ID (To) of tagged frames egressing the User Ethernet interface is changed
to C-VLAN ID (From).
The PCP field and CFI field are left unchanged.
The available set of C-VLAN IDs (To) is the list of VLAN IDs which have the User
Ethernet interface belonging to their member set and have at most two interfaces in
their member set.
At most 8 C-VLAN IDs (From) can be translated to C-VLAN IDs (To).
The C-VLAN Translation can be activated on User Ethernet interfaces of Core board
and EAS peripheral.
The User Ethernet interface can't be disabled when the C-VLAN Translation feature
is enabled.
When a C-VLAN ID is selected as C-VLAN ID (To), any modification of the
parameters of the VLAN or the removal of the VLAN from the VLAN Table is not
allowed.
The C-VLAN ID selected as C-VLAN ID (From) does not have to belong to the
VLAN Table.
When a C-VLAN ID is selected as C-VLAN ID (From), the creation of that VLAN
in the VLAN Table is denied by the CT.
VLAN Rate Limiter is not applicable in conjunction with C-VLAN Translation.
C-VLAN Translation feature is not compatible, and then does not have to be
activated, in conjunction with the following features:
Ethernet Ring Protection Switching
ECFM
L2 Radio Link Aggregation
L2 Ethernet Link Aggregation
L1 Radio Link Aggregation.
Release Notice
Being the process which changes the C-VLAN ID (From) to C-VLAN ID (To)
implemented in the egress pipeline of the Ethernet Switch, while the VLAN Rate
Limiter is implemented in the ingress pipeline, the VLAN Rate Limiter is not
applicable in conjunction with C-VLAN Translation. No check is performed by the
CT or the NE to avoid this situation.
Additional modem profiles [MSS-4/8 and MPR-e]
New modem profiles have been added (applicable to MPT-HC):
XPIC@ 40 MHz, 64QAM, static modulation
XPIC@ 40 MHz, from 64QAM to 256QAM, adaptive modulation
XPIC@ 28 MHz, 64QAM fixed modulation
XPIC@56 MHz, 64QAM fixed modulation
Fiber/microwave protection [MSS-4/8]
This feature is supported by ODU300 only.
The Fiber-Microwave Protection feature allows protecting an Optical Fiber
connection with a Microwave link, as illustrated in Figure B-9. The Main protection
resource is the Optical Fiber, while the Spare protection resource is the Microwave
link.
When the Optical Fiber connection is lost, the traffic (Ethernet and TDM) is rerouted
automatically to the Microwave link. When failure on the Optical Fiber connection
is cleared, the traffic is rerouted again on the Optical Fiber following a Revertive
behavior.
Release Notice
Figure B-9 Fibre microwave protection
The Fiber-Microwave Protection feature is supported by the 9500 MPR NE using
ERPS performing the following configuration:
1 Create a Topology having a radio interface and an optical User Ethernet interface
as Ring Ports
2 Create a single Instance in the Topology created before. Since it is requested to
manage the overall traffic either over Fiber connection or over radio link, the
usage of two Instances to load balance traffic in the Ring is not required.
3 Define one of the two NEs as RPL Owner and configure the radio interface as
RPL. In no-fault condition, this will leave the Ring Port related to radio interface
in blocking, allowing the traffic to be forwarded over the Ethernet optical
connection.
In case of Core protection the following configuration has to performed by the
operator in order to guarantee a consistent behavior of the Fiber-Microwave
Protection:
Use an optical splitter
Disable auto-negotiation on optical User Ethernet interface
Disable Ethernet LOS as switching criteria for Core protection
Disable Static-LAG
The Fiber-Microwave Protection feature is applicable to point-to-point link.
The Fiber-Microwave Protection can also be implemented on Tail links having one
MPR NE working as Node, as illustrated in Figure B-10.
Release Notice
Figure B-10 Fiber microwave protection implemented on tail links
The scenario has to be supported by 9500 MPR NE using ERPS performing the
following configuration:
1 Create two Topologies in the NE acting as Node, each Topology having a radio
interface and an optical User Ethernet interface as Ring Ports
2 Create a single Instance in both the Topologies created before
3 For each Instance, define the NE acting as Node or the other NE at Tail end as
RPL Owner and configure the radio interface as RPL. In no-fault condition, this
will leave the Ring Port related to radio interface in blocking, allowing the traffic
to be forwarded over Ethernet optical connection.
The management of TDM traffic in such a scenario does not support the cross-
connection of TDM traffic between the two topologies, while it manages tagged
Ethernet traffic with same VLANs over the two Tail links. This means that the same
VLAN ID can be associated to both the Instances belonging to the two Topologies
in the NE acting as Node.
Repeater configuration is not supported.
Radio to radio cross-connection are supported only with spurs with ODU300.
1+1/2+0 radio configurations are not supported.
TDM cross-connection between core card and a mixed fiber/microwave link are not
supported.
MPT-MC: new modem profiles support, up to 256QAM/56 MHz [ALL]
The MPT-MC supported modem profile list has been aligned (with the exception of
XPIC) to that of MPT-HC. Therefore the following profiles are supported:
3.5, 7, 14, 28, 40, 56 MHz
From 4QAM to 256QAM
Static and adaptive modulation
An MPT-MC already deployed with previous releases (differently from R3.4.0) can
be upgraded up to 256QAM/56 MHz though SW upgrade to R4.0.0 and related
license string upgrade. The 50 MHz market dedicated to the Mexican market is also
supported.
Release Notice
TACACS+ [MSS-4/8]
The system supports a TACACS+ client as defined by IETF draft-grant-tacacs-02 to
perform centralized Authentication, Authorization, and Accounting (AAA) of user
logins.
Login requests are authenticated using TACACS+ instead of the local user database,
whenever TACACS+ is enabled and a configured server is available.
TACACS+ Authorization is used to determine user membership in one of the
existing 9500 MPR privilege groups. Authorization of individual commands is not
supported.
TACACS+ accounting procedures are not supported.
If TACACS+ is enabled, users cannot change their own passwords. If a password
needs to be changed, an administrator user must change the local user accounts.
Server Support
The client supports a priority list of up to four TACACS+ servers with a unique
server encryption key for each. Automatic failover is supported when a higher
priority server does not respond.
All server exchanges are secured by the TACACS+ protocol by multiplexing the
appropriate contents with a string of MD5 hashes based on the provisioned server
secret key. The unencrypted mode of operation is not supported.
Server messages and custom prompts received in a TACACS+ response are accepted
but not displayed to users.
Authentication/Authorization
Each time an authentication is required on a user interface, the client uses the server
selection process to determine if a TACACS+ server is available. When no servers
are available, the local login database is used. The authentication request is denied if
a matching username and password are not found. If a server is available, the client
uses the selected server to perform authentication/ authorization.
The authorization response of PASS-ADD is parsed to locate a command pair
vacm={administrator | craftperson | operator | viewer}, that assigns the privilege
group for the user. The authorization is denied for any other authorization response
or if no valid privilege group is defined for the user. This provides security against
authentication of valid users, who are not authorized to access the NE.
The TACACS+ single-connection mode is not supported. Each TCP session is
closed after authentication or authorization is complete and a new TCP session is
used for the next request.
Note The Operator shall be explicitly alerted about the requested
settings server side to build a set-up that is interoperable with
9500 MPR, for example, the Authorization response shall include
the command pair vacm={administrator | craftperson | operator |
viewer}, otherwise login procedures will fail.
Release Notice
Server Monitoring
TACACS+ status monitoring is implemented through a command in the Ethernet
Features shell. The command is only supported for users with administrator
privilege.
The command displays the current TACACS+ configuration, attempt failures for
each server, and time since last server failure.
Server Validation
TACACS+ validation testing is implemented through a command in the Ethernet
Features shell. This test allows to monitor round-trip response times for determining
proper timeout settings and to confirm correct secret keys.
The command is only supported for users with administrator privileges.
Legend:
In Service software upgrade from 9500 MPR-E R3.0.0
MultiService Packet RING support with MPT-MC/HC [MSS-4/8]
XPIC support over MPR-e [MPR-e]
XPIC and Adaptive Modulation [MSS-4/8, MPR-e] support
XPIC and ATPC [MSS-4/8, MPR-e] support
1+1 radio protection on MPT-HC without tight cable [MSS4/8]
Separate alarms for battery A and battery B [MSS-8] (MSS-8 only)
Improvement of MSS-1c MCT [MSS-1c]
2x(1+0) MSS-1c repeater configuration [MSS-1c]
Troubleshooting tool [MSS4/8] (L2 routing table, VLAN table, ARP)
RING support with MPT-MC/HC [MSS-4/8]
Basic principles of RING support with MPT are applicable to the MPT-MC/HC in
addition to the MSS-4/8.
Release Notice
Supported configurations:
MPT-HC/MC connected to Ethernet ports of core card. In this case core
protection is not supported.
MPT-HC/MC connected to MPT Access card. In this case only one MPT can be
connected to a single MPT access card; the remaining port cannot be used for
other purposes.
MPT-HC connected to MPT Access card as one Ring port (East/West) and MPT-
MC connected to MPT Access card as other Ring port (West/East).
MPT-HC connected to one port of the core card as one Ring port (East/West) and
MPT-MC connected to a second port of the core card as the other Ring port
(West/East).
MPT-HC/MC connected to Core as one Ring port (East/West) and MPT-HC/MC
connected to MPT Access card as the other Ring port (West/East).
The configuration having ODU 300 radio interface as one Ring port (East/West) and
MPT-HC/MC connected to MPT Access card or to the core card as other Ring port
(West/East) is not supported.
Radios in 1+1 and/or N+0 configuration are not supported.
XPIC support over MPR-e [MPR-e]
The feature is supported by MPT-HC v2, equipped with an XPIC module. The two
mate MPTs shall be connected through coupling cable (for example, 3CC52169AA)
and through XPIC cable (for example, 3CC52186AA). this is different from the split
mount version where only XPIC cable is needed.
XPIC and Adaptive Modulation [MSS-4/8, MPR-e]
The feature is supported by MPT-HC v2, equipped with an XPIC module. On top of
the already supported modem profile in R3.2.0, the following modem profiles are
introduced for the ETSI market:
28 MHz: adaptive modulation from 4QAM to 256QAM; reference modulations:
4QAM; 16QAM or 64QAM
56 MHz: adaptive modulation from 4QAM to 256QAM; reference modulations:
4QAM; 16QAM or 64QAM
50MHz (for Mexican market): adaptive modulation from 64QAM to 256QAM;
reference modulations: 64QAM
XPIC and ATPC [MSS-4/8, MPR-e]
ATPC function and XPIC can be enabled simultaneously on the same radio interface.
1+1 radio protection on MPT-HC without tight cable [MSS4/8]
Starting from R3.4.0, RPS modules 3DB1820117BA and the tight cable between two
mate MPT-HCs are optional in 1+1 HSB/FD/SD radio protected configuration.
Release Notice
Default configuration for 1+1 HSB/SD/FD radio protection does not require an RPS
module and tight cable: signals needed for RPS are exchanged between two mate
MPTs through IDU/ODU cables and through MSS, instead of using RPS modules
and tight cable.
If jumbo frames (>5000 bytes) are transported with mixed TDM traffic, the
maximum number of TDM2TDMs that can be cross-connected in a given radio
direction in 1+1 configuration without RPS module and tight cable is 110 E1 in
channel spacing of 40 Mhz and 81 E1 in channel spacing of 56 MHz. If no jumbo
frames are transported or if the number of TDM flows is lower than the maximum,
the suggested configuration is without RPS module and tight cable.
For MPT-MC, an RPS module is not foreseen and the only possible working mode
is without the tight cable between the two mate MPTs (no changes compared to
previous releases).
A mixed radio link in 1+1 configuration, with one terminal equipped with MPT-MC
and the other terminal equipped with MPT-HC working with RPS module and
coupling cable is not supported.
A mixed radio link in 1+1 configuration, with one terminal equipped with MPT-MC
and the other terminal equipped with MPT-HC working without RPS module and
without coupling cable is supported.
In case of XPIC protected configuration 2x(1+1) tight cable is always mandatory.
Radio queue size user configurability might be non meaningful in configurations
without tight cable in 40/50/56 MHz channel spacing.
Improvement of MSS-1c MCT [MSS-1c]
The following improvements have been made.
The GUI of the Provisioning tool has been integrated in the GUI of the MCT.
The MCT navigator has been modified introducing an orange color for the menu
related to MSS-1c.
The File Management item is removed and integrated in the main view of MSS-
1c Provisioning.
2x(1+0) MSS-1c repeater configuration [MSS-1c]
MSS-1c support 1+0 configuration only (in R3.3.0). However, it is possible to add a
second radio direction connecting one MPR-e to one user port of MSS-1c. See
Figure B-11.
Release Notice
Figure B-11 MSS-1c 1+0 configuration
Usage notes:
MPR-e can be MPT-MC or MPT-HC, using electrical or optical connectivity
MPR-e can be connected to user port #2,#3,#4
A DC injector box should be used to power the MPR-e
Troubleshooting tool [MSS4/8]
Troubleshooting tool provides NE layer 2 information for debug purposes. The
following commands are available by Web interface:
Switch l2 show: list all the MAC addresses and associated VLANs learnt by NE
(the list includes static entries self-defined by NE).
Switch vlan show: list the configured VLANs inside the NE with the ports
member of VLAN (VLAN member set) and ports where VLAN Tag is removed
in egress (VLAN untagged set).
arp -a: list the ARP (Address Resolution Protocol) table entries which associate
IP addresses belonging to local connected subnets to related MAC addresses.
Separate alarms for battery A and battery B [MSS-8]
Two separate alarms for battery A and B are now available:
Battery Fail or Missing: The alarm reports a failure or missing of A side power.
Secondary Battery Fail or Missing: The alarm reports a failure or missing of B
side power.
Release Notice
ODU300 Layer 2 LAG support
support of radio LAG has been extended to ODU300. The rules and usage notes
for MPT LAG also apply to ODU300.
radio and Ethernet LAG configurations are managed via the Craft Terminal (CT
Quality of Service settings have been expanded to include the following and are
managed via the CT:
Buffer size
Forwarding class mapping
QoS scheduler setting and weighting
increased EAS support from two cards to six cards
MPT support in multiservice packet ring topology
MSS-1c and MPR-e support OSPF in greenfield deployments.
For all systems:
Quality of Service
The Quality of Service feature assigns the priority for general Ethernet packets
according to:
IEEE 802.1p: the packet is examined for the presence of a valid 802.1p user
priority tag. If the tag is present, the corresponding priority is assigned to the
packet.
DiffServ: each packet is classified based on the DSCP field in the IP header to
determine the priority
Disabled: when this option is selected, all Ethernet traffic has the same priority.
This means that for each user port and radio peripheral, there is only one queue
(FIFO), therefore the first packet that arrives is the first that will be transmitted.
The default configuration is disabled. All the QoS settings are valid for all network
elements. It is not possible to customize the QoS configuration differently for each
specific Ethernet port and radio peripheral.
When 802.1p QoS classification is selected, the reference is the standard IEEE
802.1q-2005 Annex G User priorities and traffic classes that defines eight traffic
types and the corresponding user priority values. The priority values carried by the
PCP field are not directly mapped to queues but are mapped to internal forwarding
classes according to the Regenerated Priority concept introduced in IEEE 802.1q and
applied in the MPR to both 802.1q Bridge mode and 802.1d Bridge mode. The
priority values are mapped into eight internal forwarding classes from 0 (lowest
priority) to 7 (highest priority).
When an incoming packet does not carry an 802.1p priority (untagged frame), the
assigned priority is:
port priority for 802.1q Bridge mode
priority 0 for 802.1d Bridge mode
Release Notice
When DiffServ QoS classification is selected, the classification uses the DS field of
the IPv4 or IPv6 packet header defined in RFC 2474.
The priority values carried by the DSCP field are not directly mapped to queues but
are mapped to internal forwarding classes as explained previously.
The priority values are mapped into eight internal forwarding classes from 0 (lowest
priority) to 7 (highest priority).
When an incoming packet is not IPv4 or IPv6, it will be assigned to the lowest-
priority queue.
Forwarding class mapping
When 802.1p QoS classification is selected as the QoS classification criteria for the
Ethernet flows, the default mapping between PCP values and internal forwarding
classes is applied as shown in Table B-1.
Table B-1 802.1p priority mapping
You can modify the mapping between PCP values and internal forwarding classes.
The configuration is made at the NE level and is applied to all radio QoS (ODU300
and MPTs). Each PCP value is mapped to only one forwarding class, from
forwarding class 0 (lowest priority) to forwarding class 7 (highest priority). Multiple
PCP values can be mapped to the same forwarding class. In the current release, the
CT allows a mapping of PCP values only to forwarding classes 0 to 4.
When DiffServ QoS classification is selected as the QoS classification criteria for the
Ethernet flows, the default mapping between DSCP values and internal forwarding
classes is applied by the NE as shown in Table B-2.
Table B-2 Diffserv priority mapping
PCP Forwarding class
7 4
6 3
5 2
4 2
3 1
2 1
1 0
0 0
DSCP Forwarding class
111000 (56) Class Selector 7 4
(1 of 2)
Release Notice
You can modify the mapping between DSCP values and internal forwarding classes.
The configuration is made at the NE level and is applied to all radio QoS (ODU300
and MPTs).
Each DSCP value is mapped to only one forwarding class, from forwarding class 0
(lowest priority) to forwarding class 7 (highest priority).
Multiple DSCP values can be mapped to the same forwarding class. In the current
release, the CT allows a mapping of DSCP values to forwarding classes 0 to 4.
The default mapping between internal forwarding classes and queues is shown in
Table B-3.
Table B-3 Forwarding class mapping
101110 (46) EF 4
100110 (38) AF4 High 3
100100 (36) AF4 Medium 3
100010 (34) AF4 Low 3
011110 (30) AF3 High 2
011100 (28) AF3 Medium 2
011010 (26) AF3 Low 2
010110 (22) AF2 High 1
010100 (20) AF2 Medium 1
010010 (18) AF2 Low 1
001110 (14) AF1 High 1
001100 (12) AF1 Medium 1
001010 (10) AF1 Low 1
Remaining values 0
Forwarding class Queue
7 7
6 6
5 6
(1 of 2)
DSCP Forwarding class
(2 of 2)
Release Notice
QoS scheduler setting
The default configuration of the QoS scheduler is shown in Table B-4.
Table B-4 Scheduler mapping
You can configure the scheduling algorithm, either SP or DWRR, to be applied from
Q1 (lowest-priority queue) to Q5 (highest-priority queue). For DWRR, the weight to
be applied to the specific queue is also configurable. The configuration is made at the
NE level and is applied to all radio QoS (ODU300 and MPTs). The set of queues
using the SP or DWRR scheduling algorithm must be continuous, with SP always
applied to the highest-priority. The weight of the queues configured using DWRR is
configurable in the range 1 to 32.
Queue size setting
Through CT/NMS, it is possible to configure the size of queues from Q1 (lowest-
priority queue) to Q5 (highest priority queue). The configuration is made at the radio
interface level and is applied to radio QoS in the following configurations:
1+0
1+1 FD, 1+1 HSB/SD (the two protected radio interfaces have the same setting)
Layer 2 Radio Link Aggregation (each radio interface in the LAG has its own
setting
4 5
3 4
2 3
1 2
0 1
Queue Scheduler Weight
8 SP n/a
7 SP n/a
6 SP n/a
5 DWRR 16
4 DWRR 8
3 DWRR 4
2 DWRR 2
1 DWRR 1
Forwarding class Queue
(2 of 2)
Release Notice
The size of the queue is defined by the number of bytes of Ethernet traffic that must
be buffered by the queue. The size can be configured in the following range:
maximum queue size = 4034836 bytes
minimum queue size = 2480 bytes
A queue is implemented as an array of data blocks, each data block carrying at most
124 bytes of an Ethernet frame fragment (an Ethernet frame of 124 bytes fills one
data block).
The queue size configured by the operator must be converted to the number of the
queues data blocks according to the following expressions:
MPT-HC/MC QSDB = [QS / 124] + 100
ODU 300/MPT-HL QSDB = [QS / 124] + 80
where QSDB is the queue size in number of data blocks, QS is the queue size in
number of bytes configured by the operator, and [x] indicates rounding to the nearest
integer.
If the queue size is changed and the new queue size value is less than the current
value, traffic is impacted if the queue is filled with Ethernet traffic at a higher level
than the new queue size value; otherwise, the change of queue size has no traffic
impact.
In order to give the operator an estimate of the maximum delay that an Ethernet
frame can experience when entering the specific queue in case of radio interface
congestion, the CT must show a read-only value that is the queue size configured by
the operator converted to a time value (ms).
The maximum delay must be estimated according to the following parameters:
queue size in bytes as configured by the operator
maximum Ethernet available bandwidth of the radio interface (and consequently
by the modem profile used)
scheduling algorithm applied to the queue
weight, if the scheduling algorithm is DWRR
You can restore the default configuration of the following settings:
802.1p to internal forwarding classes mapping
IPv4/IPv6 DiffServ to internal forwarding classes mapping
internal forwarding class to queue mapping
QoS scheduler setting
Restoring the default configuration is made at the NE level and is applied to all radio
QoS. It does not impact traffic.
It is also possible to restore the buffer size. If the default buffer size is restored and
the default queue size is less than the current size, traffic is impacted if the queue is
filled with Ethernet traffic at a higher level than the default queue size; otherwise, the
restore does not impact traffic.
Release Notice
Link aggregation managed through CT/NMS
The LAG Type parameter identifies the Layer 2 Ethernet Link Aggregation or Layer
2 Radio Link Aggregation and must be set accordingly. It is a mandatory parameter
that is provisioned by the operator at LAG creation and cannot be modified later.
The LAG Name parameter can be configured with an empty string.
A radio interface with TMN-RF Enabled cannot be added to a LAG. The operator
must disable it before the Port Add operation.
TMN-RF configuration of single radio interfaces belonging to the LAG shall not be
available.
TMN-RF configuration is available at the group level. The entire LAG direction is
represented as a unique PPP RF interface. At the LAG creation, TMN-RF is disabled
by default. TMN-RF can be enabled when at least one radio interface belongs to the
LAG. The last interface in the LAG can be removed only when TMN-RF is disabled
on the LAG. The operator must deactivate the LAG and disable TMN-RF before
removing the last radio interface in the LAG.
In 9500 MPR R3.0.0 and 9500 MPR R3.1.0, the operator explicitly enabled the
TMN-RF on only one radio interface. This is different from R3.4.0, where TMN-RF
is applied at the LAG level. When upgrading the software from those 9500 MPR
R3.0.0 and R3.1.0, there are two options:
keep the TMN-RF configuration at the radio interfaces level. If this option is
selected, it should be noted that it will be possible in future to disable (but not
enable), the TMN-RF of single radio interfaces
disable the TMN-RF configuration at the radio interface level and then enable
TMN-RF supervision at the LAG level
In the case of Ethernet LAG with LACP enabled, the following LACP counters are
available to the operator on each port of the group:
LACPDU Transmitted/Received
Marker PDU Transmitted/Received
Marker Reply PDU Transmitted/Received
Illegal LACPDU
Unknown LACPDU
Frames used by the Link Aggregation Marker Protocol are represented in the Marker
PDU and Marker Reply PDU counters.
The Illegal LACPDU counter represents the number of frames received that either:
carry the Slow Protocols Ethernet Type value, but contain an unknown PDU, or
are addressed to the Slow Protocols group MAC address, but do not carry the
Slow Protocols Ethernet Type
Note This procedure can only be done locally.
Release Notice
The Unknown LACPDU counter represents the number of frames received that carry
the Slow Protocols Ethernet Type value, but contain a badly formed PDU or an
illegal value of Protocol Subtype.
The LAG Port Status shall be shown to the Operator according to the Link
Aggregation state machine. The following values are displayed:
UP (the port is an active member of the LAG)
STANDBY (the port is a member of the LAG but is currently in standby mode,
applicable in an Active/Standby configuration)
DOWN (the port is down and is not able to carry traffic)
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 C-1
Release Notice
C. Supported hardware
C.1 Supported hardware
Support of the MSS-1 shelf is new in R4.1.0.
Existing hardware
Tables C-1 to C-6 describe supported hardware from previous releases.
Table C-1 9500 MPR MSS-4 and MSS-8 common equipment
Note The codes shown in Table C-3 are compatible with
9500 MPR releases 1.3.1 or later.
Product Part number First release
9500 MPR MSS-8 Shelf 3DB18485AB
3DB18485AA
R1.0.0
9500 MPR MSS-4 Shelf
3DB18219AD
3DB18219AC
3DB18219AB
R1.2.0
9500 MPR MSS-8 Fan Module
3DB18134BB
3DB18134BA
R1.0.0
9500 MPR MSS-4 Fan Module
3DB18218AD
3DB18218AC
R1.2.0
9500 MPR Fan Alarm Module 3EM23911AA R3.0
(1 of 2)
C-2 November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Release Notice
Table C-2 MSS-1 part numbers
Table C-3 9500 MPR-E supported flashcards (MSS-1/4/8 only)
Core enhanced
3DB18326AC
3DB18326AB
R1.2.0
9500 MPR MSS-1 unit 3DB19015AA R4.1.0
License string Description Alcatel-Lucent part number
R/12Cap350/TDM2Eth/ATM2Eth/12modAdp MPR Memory D12SA-410A 3DB18900ABXX
R/12Cap040 MPR Memory L6TD-410 3DB18901ABXX
R/11Cap040/1Cap080 MPR Memory M1TD-410 3DB18902ABXX
R/11Cap040/1Cap100 MPR Memory H1TD-410 3DB18905ABXX
R/11Cap040/1Cap150 MPR Memory V1TD-410 3DB18908ABXX
R/11Cap040/1Cap300 MPR Memory E1TD-410 3DB18911ABXX
R/6Cap040/6Cap350 MPR Memory D6TD-410 3DB18914ABXX
R/12Cap040/TDM2Eth/ATM2Eth MPR Memory L12SA-410 3DB18915ABXX
R/11Cap040/1Cap080/TDM2Eth/ATM2Eth MPR Memory M1SA-410 3DB18916ABXX
R/11Cap040/1Cap100/TDM2Eth/ATM2Eth MPR Memory H1SA-410 3DB18919ABXX
R/11Cap040/1Cap150/TDM2Eth/ATM2Eth MPR Memory V1SA-410 3DB18922ABXX
(1 of 2)
(2 of 2)
Release Notice
R/11Cap040/1Cap300/TDM2Eth/ATM2Eth MPR Memory E1SA-410 3DB18925ABXX
R/11Cap040/1Cap060 MPR Memory I1TD-410 3DB18928ABXX
R/11Cap040/1Cap060/TDM2Eth/ATM2Eth MPR Memory I1SA-410 3DB18931ABXX
R/11Cap040/1Cap130 MPR Memory A1TD-410 3DB18934ABXX
R/11Cap040/1Cap130/TDM2Eth/ATM2Eth MPR Memory A1SA-410 3DB18937ABXX
R/11Cap040/1Cap130/12modAdp MPR Memory A1TD-410A 3DB18940ABXX
R/11Cap040/1Cap130/TDM2Eth/ATM2Eth/12modAdp MPR Memory A1SA-410A 3DB18943ABXX
R/12Cap040/12modAdp MPR Memory L12TD-410A 3DB18946ABXX
R/10Cap040/2Cap080/12modAdp MPR Memory M2TD-410A 3DB18947ABXX
R/6Cap040/6Cap080/12modAdp MPR Memory M6TD-410A 3DB18948ABXX
R/11Cap040/1Cap150/12modAdp MPR Memory V1TD-410A 3DB18949ABXX
R/12Cap040/TDM2Eth/ATM2Eth/12modAdp MPR Memory L12SA-410A 3DB18950ABXX
R/10Cap040/2Cap080/TDM2Eth/ATM2Eth/12modAdp MPR Memory M2SA-410A 3DB18951ABXX
R/6Cap040/6Cap080/TDM2Eth/ATM2Eth/12modAdp MPR Memory M6SA-410A 3DB18952ABXX
R/11Cap040/1Cap150/TDM2Eth/ATM2Eth/12modAdp MPR Memory V1SA-410A 3DB18953ABXX
R/6Cap040/6Cap350/TDM2Eth/ATM2Eth/12modAdp MPR Memory D6SA-410A 3DB18954ABXX
R/6Cap040/6Cap350/12modAdp MPR Memory D6TD-410A 3DB18955ABXX
License string Description Alcatel-Lucent part number
(2 of 2)
Release Notice
Table C-4 9500 MPR peripheral cards (MSS-4/8 only)
Table C-5 MSS-1c part numbers
Table C-6 Supported SFP modules
32E1/DS1 PDH peripheral
3DB18126AE 3DB18126AD
3DB18126AC
R1.0.0
Modem300
3DB18136AE
3DB18136AD
3DB18136AC
R1.0.0
Modem300 EN
3DB18538AC
3DB18538AB
3DB18538AA
R1.1.0
MPT access plug-in 3DB18634AB R2.1.0
Auxiliary peripheral 3DB18236AB R1.3.0
ASAP peripheral 3DB18602AA R1.2A
SDH access card 3DB18735AA R3.0.0
AWY access card 3DB18628AB R2.1Y.0
8 ports EAS card 3DB18206AC R3.1.0
Protected +24V DC converter kit 3DB18862AA R3.1.0
Unprotected +24V DC converter kit 3DB18863AA R3.1.0
Power injector card 3CC50120AA R3.1.0
9500 MPR MSS-1c 3BD 18613 AA R2.2.0
MSS-1c 16E1/DS1 3DB18613BA R3.1.0
Fan Unit 3DB 77002 AA R2.2.0
Product Part number Where used First release
SFP 1000Base-LX Transceiver 3CC50168AAAA
Core card, MSS-1c, EAS, MPT
access card (indoor-outdoor
on SM fiber)
R1.1.1
SFP 1000Base-SX Transceiver (850 nm) 3CC50167AAAA
Core card, MPT access card,
MSS-1c
EAS
R2.1.0
(1 of 2)
Release Notice
MPT supported codes
Refer to the 9500 MPR tuning guide, edition 13 or higher, for the list of MPT
supported codes.
SFP 1000Base-T Copper Transceiver 3CC50169AAAA
Core card, MSS-1c
EAS
R1.4.0
SFP 1000Base-ZX 3CC50170AAAA Core card R3.0.0
SFT 1000Base-BX10
3CC50183AAAA (1310nm)
3CC50184AAAA (1550nm)
Core card
R3.3.0
SFP 1000Base-BX40
3CC50198AAAA (1310nm)
3CC50199AAAA (1550nm)
Core card
R3.3.0
2E1 SFP 3DB78012AAAA Core card R3.0
E3 SFP 1AB380750004 Core card, MSS-1 R3.3
EoSDH SFP 1AB380750003 Core card, MSS-1 R3.0
SDH electrical SFP 1AB210170001 SDH access card R3.0
SDH optical SFP, S.1.1 3CC50165AAAA SDH access card R3.0
SDH optical SFP, L.1.1 1AB194670005 SDH access card R3.0
CWDM-SFP-1470 3CC50201AGAA Core card R4.1.0
CWDM-SFP-1490 3CC50200AAAA Core card R4.1.0
CWDM-SFP-1510 3CC50201ABAA Core card R4.1.0
CWDM-SFP-1530 3CC50201ACAA Core card R4.1.0
CWDM-SFP-1550 3CC50201AAAA Core card R4.1.0
CWDM-SFP-1570 3CC50201ADAA Core card R4.1.0
CWDM-SFP-1590 3CC50201AEAA Core card R4.1.0
CWDM-SFP-1610 3CC50201AFAA Core card R4.1.0
Product Part number Where used First release
(2 of 2)
Release Notice
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 D-1
Release Notice
D. Closed issues in previous releases
D.1 Closed issues in previous releases
Table D-1 shows closed issues from R4.0.0.
Table D-1 Closed issues in R4.0.0
Item Description
ALL systems
PPP fail alarm Issue: When the 9500 MPR is configured with 12 radio directions, the PPP fail
alarm can remain active even if the if PPP is working properly.
Workaround: Perform a warm start of the 9500 MPR.
TACACS With TACACS enabled, using the Current Configuration View or Ethernet
Feature Shell from the Configuration Menu are not possible.
Workaround: None
MSS-4/8
VLAN CIR Rate limiter VLAN CIR Rate limiter will not be set correctly if the only the apply button is
clicked.
Workaround: After changing the CIR, the user must hit enter first before
applying the changes.
Spare ACM loop problem alarm When configured in XPIC with 1+1 in AMC mode, if the optical coupling is
removed at the far-end, no spare ACM loop problem alarm is raised.
Workaround: none
D-2 November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Release Notice
Item Description
MSS-4/8
MPT-HC may not be able to operate at 256
QAM in AM mode
In certain MPT-HC, the AM function cannot switch to 256 QAM and operate
only at 128 QAM and below.
FlowControl mismatch for Core Ethernet
port
Enable/Disable Flow Control for a user Ethernet Port and associate that port
in E-LAG with other ports with homogeneous configuration. EC refuses
association with SNMP error message error adding port to ELAG.
Workaround: Reset Flow Control configuration before adding the port in a E-
LAG.
Traffic hit on MPT repeater VLAN editing In a repeater MPT topology there is a traffic hit while editing the VLAN is
edited.
802.1Q In a repeater configuration with MPT-MC/HC/HL, with MPR in 802.1Q mode,
adding a local Ethernet port to VLAN membership of an already existing VLAN
group, might cause a traffic hit on the Ethernet flow with the same VLAN ID
forwarded by the repeater.
MSS-1c and MPR-e
ATPC settings Driving Remote RSL When ATPC is enabled there is a selectable field related to 1+1HSB.
Item Description
ALL systems
XPIC XPIC and Adaptive Modulation are not supported in the current release.
In an XPIC configuration, if the XPIC cable is removed, a traffic hit might
occur on the remote Rx of the orthogonal polarization.
The ATPC function cannot be activated if XPIC has been configured on the
related radio interface.
MSS-4/8
WTPMS tool The WTPMS tool cannot be launched from NEtO if there is no active
connection to the 9500 MPR.
Use the desktop shortcut to launch the off-line WTPMS tool.
PM tool Depending on the number of E1 links being monitored, the PM tool might take
a few minutes to load and display the history table.
After 24 hours have elapsed, the PM tool screen shows 00.00.00 instead of
24.00.00.
Craft Terminal In the current configuration view window, the EAS segregated port 8 is
reported as MPT-ACC plug-in Slot 5.
DS1/E1 flows Simultaneous TDM2TDM and TDM2TDM2Ethernet cross-connections are not
supported on MPT-HC/MC. TDM2TDM and TDM2Eth flow are instead supported
simultaneously. This restriction does not apply to ODU300.
Provisioning tool MPT Protection 2*(1+1) in W configuration. Get and Set operations are not
guaranteed if one of these configurations is present in the Network Element.
(1 of 2)
Release Notice
Table D-4 shows closed issues from previous releases.
Table D-4 Issues in previous releases
STM1 channelized STM-1 channelized and multiservice packet ring cannot be supported at
the same time in a 9500 MPR NE. This means that E1 handoff in a
multiservice packet ring environment cannot be done through an STM-1
channelized interface.
E1 cross-connections between a radio direction with radio LAG and an
SDH channelized board are not supported.
RING Ring with MPTs is supported only with an MPT connected to the core; ring
is not supported if MPTs are connected to and MPT access card.
Ring with MPTs is not supported in an NE with core protection enabled.
Cross-connections from a radio direction (spur) not belonging to the ring
are not supported; this means, for example, that the E1/DS1/DS3s need
to be terminated in the NE supporting ring and cross-connected to the
radio belonging to the ring.
The ring cross-connection screen is not supported by NMS.
Battery alarm If battery fail alarm is present, a blue light bullet is displayed inside the block
diagram view (inside the Craft Terminal) but the navigation is not correct; it
is redirected to the main core instead of to the MSS-8.
If the MSS-8 has only one battery input connected, a standing Battery Fail
warning is present.
MSS-1c
TMN When the MCT is connected to the MSS-1c or MPR-e through another switch or
router via TMN in-band, some TMN frames may be dropped if there is
congestion on the switch or router.
MSS-1c and MPR-e
Upgrade When upgrading from MPR3.0, the high and low thresholds of the TCA alarms
are inversed; after the migration, the operator must manually reconfigure the
thresholds through the MCT.
OSFP After attach/detach of the OSFP area several times, the NE does not respond.
Restart the MPR-e or MSS-1c.
Provisioning tool In some cases the provisioning tool does not allow the use of ECID values after
modification of the flow ID when there were errors.
Produce the configuration file without creating duplicate IDs.
Temporary link failure After a temporary link failure on a radio hop causing an interruption PPP RF,
it takes 4 minutes before to open the MCT on the remote station.
The problem is not present when the firewall is disabled on the PC (as
recommended in the User Guide).
OSPF When using OSPF, after changing the NMS IP address of the MSS1c/MPRE, the
OSPF convergence does not complete.
Item Description
(2 of 2)
Item Description
Restrictions
All systems
(1 of 12)
Release Notice
R3.2.0-001
Performance Management
The NE Time/date is not persistent on an MPT restart.
MSS-4/8
PDH alarm directions PDH alarm directions are defined using the standard DCE conventions (Tx is
input, Rx is output). This means that alarms are raised with the direction
relative to the radio signal, not the physical PDH port.
This is the expected system operation.
CFM frames CFM frames (Ethertype 0x8902) are being looped or repeated by the standby
CSM when sent over either MPT-HC/MC or ODU300.
Workaround: None
EPS With MPT-HC configured in 1+1 and the MPT-ACC card in 1+1 and in NON
revertive mode, if an EPS occurs on the MPT-ACC card when the RPS is on
SPARE, after the EPS switch, the RPS will switch to MAIN even thought it is
configured for NON revertive switching
ATPC Loop Problem alarm The ATPC Loop Problem alarm is not generated on spare link in 1+1 FD
configuration.
Queue numbers The event log browser and the JUSM QoS / Scheduler configuration queue
numbers do not align.
Workaround: When looking at the Event log browser, add 1 to the queue
number for correspondence with CT mapping.
MPT profile compatibility The 50/256 MPT profile in R3.3.0 is NOT air compatible with the 50/256 profile
in R3.0.0.
Workaround: When migrating from R3.1.0 to R3.3.0, ensure the far-end radio
is upgraded first.
Transmit power The Transmit power shows different ranges between the main and spare
channel.
Workaround: Perform a warm start of the shelf to correct the issue.
XPIC automute When in XPIC mode the automute clears when MPT-HC or MPTACC powered
down and back up with the XPIC cable still removed.
Workaround: Perform an MPT-xC restart and ensure that the XPIC cable is
connected, or do not restart an MPT-xC if the XPIC cable is disconnected.
Ethernet PM When the ethernet PM stats are running on the ODU, if the MD300 is physically
removed, invalid values are returned.
Workaround: Stop Ethernet PM before removing the board.
Link Aggregation Type The CT still shows the LAG type as Layer 2 radio or Layer 2 Ethernet when L3
is selected as the Hash method.
Workaround: Link Aggregation Type is used to distinguish between Radio Link
Aggregation and Ethernet Link Aggregation. After configuring the Link
Aggregation Type, the user can change the hashing algorithm in order to select
Layer 2 (distribution of frames based on MAC header and VLAN tag) or Layer 3
(distribution of frames based on IP header). By default, Layer 2 hashing is
selected.
IF loopback When the ODU is configured in a LAG, IF loopbacks will cause the ODU to be
removed from the LAG.
Workaround: Do not use IF loopbacks when the ODU is a member of a LAG.
Java version Java 6 is required for proper operation of the 9500 MPR Craft Terminal. Java 7
is not supported.
Item Description
(2 of 12)
Release Notice
LAG status In a LAG with at least 3 members, if one member is already in the Down state,
if an additional member fails, its status is not updated in the LAG window in
the Craft Terminal.
Workaround: Use the refresh button to refresh the screen status.
MPT-HC profile compatibility MPT-HC 10/128 profile is not air compliant with the MPT-HC 10/128 in R3.1.
PM measurement history When the MPT-xC is connected to the CSM, the PM measurement history only
allows to view the data one direction (forward) because the back button is
grayed out.
Workaround: Open and close the measurement value screen.
MPT-ACC view When there is a radio alarm on MPT-ACC and there is an adjacent PDH card,
navigation from the alarm tool the GUI opens the PDH card view instead of
MPT-ACC view.
Multiple software download To make software upgrades I parallel on the nodes belonging to the same tree
or sub-network: it is strongly suggested, in case Ethernet user port #4 is used
in any node of the sub-network to transport TMN traffic, to limit the number
of concurrent software download to 1. This is valid for CT/1350 OMS/5620 SAM.
Of course, in case of multiple sub-networks, the scheduled download (from
1350OMS or 5620 SAM), shall address only one NE of each sub-network per
time, so that it is possible in any case to perform multiple downloads,
addressing in parallel multiple NEs belonging to different sub-networks.
Changing modulation with MPT-MC/HC With MPT-MC/HC, changing from static modulation to adaptive modulation and
then going again back to static modulation.
It is recommended to provision again PTx value, otherwise it could happen that
the PTX value provisioned in adaptive modulation is kept.
ASAP card The CIR of CBR/UBR+ traffic over MPT-xC might be not guaranteed over MPT if
there is radio congestion.
ATM cross-connections between the ODU300 and MPT-xC are not supported.
NTP If one of the two NTP servers is down, the NTP is immediately synchronized to
the second server, but the notification is reported with 30 minutes of delay.
An incorrect message appears on the CT.
Maintenance If a demodulator failure alarm is raised or a cable is disconnected in a 1+1
FD or HSB configuration with a forced lockout condition, the alarm is not
displayed at the link level but is displayed at the hop level.
Operation On the Craft Terminal screen of the CORE Main View, when reporting the
status of the autonegotiation process, the label other is always incorrectly
displayed. The information related to the autonegotiation results (speed, flow
control, and so on) are correctly reported in the top part of the same screen.
Alarm severity is dependent on the provisioning order of protection groups. For
example, if you remove a P32E1DS1 module that is in a protection group, the
alarm is raised as minor; however, if you provision the spare module
unequipped and then create a protection group, the alarm is raised as major.
Link identifier After a configuration change from 1+0 to 1+1 HSB, the LIM alarm is not
revaluated; in order to re-evaluate disable/enable the link identifier. This
behavior is common to ODU300 and MPT-HC.
PM tool The navigation between an alarm and the Alarm Monitoring window is not
supported.
After a migration from 9500 MPR R3.00 to 9500 MPR R3.01, if performance
monitoring is started in R3.00, it is not automatically started in R3.01.
Workaround: Manually start the PM data.
Item Description
(3 of 12)
Release Notice
2x(1+0) 2x(1+1) configuration It is not possible to disable TMN RF after it has been enabled. If the operator
attempts to disable it, 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 the CT
and reset the NE.
Alarm monitoring During navigation from the Alarm Monitoring window to the Craft Terminal
(and vice versa), the target window might not be shown in front. In order to
view the target window, make the front window an icon.
Synchronization alarms (synch degrade and synch LOS) are not reported in the
Alarm Log.
ODU300 The Craft Terminal allows a PTX change in steps of 1 dB. If the maximum ODU
output power is 0.5, a starting value of 0.5 must be written.
Changing the configuration from presetting mode to adaptive modulation
raises an incorrect warning message of Tx Power Out of Range. Re-edit the
output power and ignore the message.
The setting of28MHz 256QAM takes 10 s to be applied (longer than other
modem profiles).
MPT-xc If the RPS interconnection cable fails (with the corresponding activation of the
coupling link alarm), operator commands (forced and lockout) are not
applied. The coupling link alarm is also raised in the event of a hardware
failure or switch off of one of the two MPT-HC MPTs.
A false indication of remote Automute may occur if the MPT Tx is unmuted
without any impact on the XPIC and 1+1 functionalities.
Backup and restore Configuration changes are not blocked during backup operations. Customers
should coordinate provisioning changes for times when backup operations are
not scheduled.
MSS-1c
Ethernet services At 100 Mb/s and 10 Mb/s, the maximum size for jumbo frames is limited to 9143
bytes. The Ethernet port must be set to 1Gb/s to support jumbo frames up to
9728 bytes.
Usage notes
All systems
Tx Far end reading When Tx Power is set with an odd decimal, the Tx Far end reading is neared to
a lower even decimal. The Tx power of the remote MPT is reported with a
precision of 0.2 dB. This is due to the coding of the power using 8 bits and the
power range to cover.
MPT-MC/HC ANSI modem profile 256QAM @ 10 MHz of R3.4.0 is not air compatible with the
same profile of R3.1.0. In case of SW upgrade, ensure that the remote site is
upgraded first.
Craft Terminal To avoid conflict among the different JRE versions, ensure that only the
recommended JRE version is enabled. Note: For 64-bit systems, 32-bit Java is
suggested (as installed via TCO Suite), since 64-bit Java ships only the 64-bit
browser plug-in, but only 32-bit browsers can be set as default.
When using the Alarm Monitor via the Web interface, ensure that the proxy is
disabled in your browser application.
Flow control It is recommended that flow control be used in half-duplex mode.
Item Description
(4 of 12)
Release Notice
Alarms An HBER alarm can be raised, according to the different modem profiles, in
arrange of BER from 1e-4 to 1e-7 (TSAlo51767).
For MPT-HC 1+1 radio protected configurations, if LOS is generated by an IDU-
ODU cable disconnection of one of the two MPTs, alarms reported in the CT RPS
section are not meaningful (WTDcd03748).
After each provisioning or maintenance operation, it is recommended the CT
alarm bullets status be refreshed using the refresh button, to ensure that the
CT is showing the right bullets color.
Adaptive modulation With MPT-xC, in adaptive modulation, it is possible to use manual mode for
troubleshooting. Disabling manual mode might cause a traffic impact.
MSS-4/8
Synchronization QL state When the Synchronization tab is opened the state of Quality Level is not
updated. A refresh is necessary.
Java RMI errors related to install or
uninstall of various Java versions
The last Java6u29 contains a Java bug that impacts NEtO: it blocks NEtO
running by providing the following error message: rmi resource not
available.
Java Virtual Machine (VM) version 6 update 29 (6u29)is not supported, due
to a documented bug in Oracle Java VM. Please remove it if already
installed and install the Java VM provided with TCO Suite DVD-ROM.
No denial if using 64b Java to run
WebEML
There are no blocking points in running NEtO/TCO with Java 64bit.
The only impact is on the 'autorun' facility of the CD ROM device that uses the
'default browser'. The default browser must be a 32bit browser so they run only
with Java 32bit. Currently, on Windows OSes 64bit browsers cannot be set as
default.
If autorun does not work or it is not enabled, TCO can be run by running either
32bit or 64bit browser and opening the Start.html page inside the CD. Double-
clicking on Start.html page will always automatically run the 32bit browser set
as the default.
XPIC Auto Remote Mute not declared when MPTACC module is unplugged.
EAS card From Alarm Monitoring, navigation to the Ethernet ports of EAS card is not
supported.
Existing PPP Fail & Dialog Failure / Internal Communication Problem (ICP)
alarms are not cleared when Replaceable Unit Type Mismatch alarm is
detected for the slot. Workaround: a NE reset will clean the alarms.
Ethernet user ports Disabling both Auto negotiation & Advertised capability to lower rate at the
same time is not allowed for Ethernet ports of core card/EAS when there is LOS
on the port & at least one cross-connection associated to it.
Workaround:
The change of Ethernet parameters can be done in 2 steps.
Change to the lower rate Advertisement capability (100 Mb/s/Full Duplex)
without disabling auto negotiation.
Disable auto-negotiation.
MPT-HL ATPC loopback alarm is not available when MPT-HL in configured in adaptive
modulation.
Radio LAG In case of LAG L2, if hashing L3 is selected, hashing algorithm does not take
into account TCP/UDP destination port and TCP/UDP source port.
Adaptive modulation ATPC and AM features are not supported at the same time.
AM is not launched with proxy enabled.
Item Description
(5 of 12)
Release Notice
Changing protection on an ODU300 from
1+1 fd to 1+1
A warning message is presented: the protection configuration is not allowed
with the current capacity license.
Workaround:
downgrade, remove protection: 1+0
upgrade new protection type 1+1 hsb
Radio LAG For radio LAG N+0, the sum of TDM traffic (E1, DS1, DS3, STM-1) must fit the
bandwidth of a single radio channel. For adaptive modulation, the sum of TDM
traffic (E1, DS1, DS3, STM-1) must fit the bandwidth associated with the
minimum modulation scheme selected on a single radio channel.
Backup and restore The backup filename must not include the following characters: space, &, /,
\,:, *,?, <, >, and |. Local language characters are also not allowed. The
filename always contains the version as prefix; for example, "V020100",
corresponding to version V2.1.0, or "V030200" corresponding to version V3.4.0.
This prefix is inserted automatically by the software when the MIB backup file
is created, and is used automatically by the software when the MIB restore
must be performed.
Radio Direction label User-defined site names (radio direction label) must not contain the
following characters: space, &, /, \,:, *,?, <, >, and |. Local language
characters are also not allowed.
5620 SAM/Nx(1+0) For each Nx(1+x) (x=[0...1]) radio configuration, the involved radio ports must
be provisioned as follows.
Only one radio port can have PPP RF enabled.
The LinkID must be enabled for all the port members of the configuration
having the same LINKGRP and different LINKMEMBER, matching the far-end
radio ports: LinkID Expected and Sent values are requested to be equal (for
example, (11,11), (13,13), (15,15).)
For multiple Nx(1+x) radio configurations on the same node, the LINKGRP
must be unique without overlapping (for example, 1 and 2). Other radio
ports not involved in Nx(1+0) protection (in single 1+0 or 1+1 radio
configurations) must have PPP RF enabled or PPP RF disabled and
optionally the LinkID provisioned, but the ports must have a different
LINKGRP (for example, 3,...,9) so that other LINKMEMBERs are not
discovered.
5620 SAM/Radio LAG For radio LAG, the involved radio ports must be provisioned as follows.
No radio port can have PPP RF enabled.
(LAG membership). A different LINKMEMBER must be used, matching the
far-end radio ports: LinkID Expected and Sent values are requested to be
equal (for example, (11,11), (13,13), (15,15)).
Other radio ports not involved in a LAG (in single 1+0 or 1+1 radio
configurations) must have PPP RF enabled and optionally the LinkID
provisioned, but the ports must have a different LINKGRP (for example,
3,...,9).
SDH channelized MSP protection is not supported. 1+1 SDH protection is EPS only
Backup and restore During a database restore operation, the restore might fail with an
operation failed pop-up window. If this occurs, perform the restore
operation again.
If a force command is entered (core protection) from the spare core to the
main core, before making a backup it is necessary to wait a few minutes,
in order to permit the flash cards database alignment. If the backup has
been done during this alignment phase, the backup operation can fail; if
this occurs, close the Craft Terminal, reopen it and apply the backup again.
Item Description
(6 of 12)
Release Notice
Radio LAG It is recommended that radio LAG be disabled before changing the modem
profile of one of the links already involved in the LAG.
Ethernet OAM LT and Loopback cause traffic impact on TDM2ETH flows if they
are cross-connected to a LAG.
The maximum number of MPTs inside a radio LAG is four.
Radio LAG is not supported with MPT directly connected to the Core card.
The LAG ID parameter value must be in the range 1:8. This applies to User
port LAG and to radio LAG.
During the provisioning phase, removing a radio link inside a LAG might cause
traffic impact on all the links in the group.
Synchronization If primary and secondary synchronization sources are radio (slave node), either
SSM is disabled or enabled in a homogeneous way on the primary and secondary
sources.
MPT connected to core MPT connected to the core is not supported if the core; is protected.
EAS card If the SFP is plugged into the SFP port of the EAS before the port is
provisioned, the RI of the SFP will not be displayed. Unplug the SFP and
plug it in after the port is provisioned.
On both the Core card and EAS Ethernet ports, if autonegotiation is
enabled, flow control does not get configured properly.
The EAS module and the MPT-ACC module should not be provisioned in the
same row (that is, do not provision EAS in slot 3 and MPT-ACC in slot 4 or
vice versa)
XPIC XPIC and Adaptive Modulation are not supported in the current release.
In an XPIC configuration, if an MPT-HC is in alarm, the XPD value may not
be accurate.
In an XPIC configuration with radio LAG configured, if the MPT-ACC module
is reset or if the MPT-HC is power cycled, there is an extended traffic loss
on the entire LAG.
In an XPIC configuration, when the remote Tx is muted, the XPD value is
not accurate.
In order to correctly configure XPIC in 1+1, the protection must first be
configured between mate MPTs and then the XPIC in the protected radio
direction must be configured.
MPT-MC/HC In a 1+1 MPT-MC/ HC configuration, if both channels fail with the same
alarm, the protection of the MPT-HC remains on the spare channel. This is
normal behavior since this is a double fault.
In a 1+1 MPT-MC/HC protection configuration, if an MPT-ACC board is
extracted and inserted, it is possible that the channel will remain in the
equipment failure state. This issue is only seen when the MPT-ACC module
is extracted and inserted quickly (approximately 10 seconds between
actions). If the MPT-ACC module is inserted after 15 seconds, this issue is
not seen. An NE restart clears the equipment status.
In a 1+1 FD configuration with MPT-MC, the switching time for the MPT
access card missing state might be up to 500 ms.
The maximum number of MPTs that can be powered through an MSS-8 shelf
is eight. If the number of MPT exceeds this limit, DC injector boxes or a
direct connection of MPT to battery can be used.
Item Description
(7 of 12)
Release Notice
Ring In G.8032 ring configurations, it is possible for the ERPS states to be in a
dead-locked scenario where the non-RPL owner nodes are in an idle
state and the RPL owner is in a protection state. If this occurs, disable
and enable the RPL owner instance after all the other non-RPL owner ERP
instances have been activated.
There is no alarm or condition reported when a G.8032 ring is not in the
idle state. However, on the EPRS configuration screen, the current status
of the G.8032 ring is reported.
The ERPS topology label does not allow for special characters.
In a G.8032 ring configuration, if the same VLAN is deleted from one
instance and added to the other instance, Ethernet traffic will be affected
for approximately 300 seconds.
TMN in-band Disabling TMN in-band does not free the VLAN ID from being used for other
functionality. In this case, disable the Ethernet port or assign another VLAN ID
to that port to free the previous VLAN ID.
Performance monitoring PM history is cleared if the PM is refreshed when an active dialog failure
alarm is present.
Ethernet statistics are not initialized to zero when the EAS/Core card
module resets or during a equipment protection on the EAS ports.
After a reset of the MPT-MC or MPT-HC, the 24-hour PM is lost.
After starting PM and loading PM data, the hourglass disappears after 1
minute but the tool is still loading. Wait until the counters have the green
checkmarks and the start/stop button shows that PM is running.
Preprovisioning tool The following features are not supported by the provisioning tool or by the web
interface:
ASAP card mng
AUX card mng
8 Gbit ports EAS card mng
LAG
SDH If an HBER condition occurs over the radio, a scrambled all 1s signal is
inserted in the outgoing STM-1 flow (Rx side), not an MS_AIS signal.
For MPR back-to-back configurations, ALS on the SDH card should be disabled.
Only 1xSTM-1 electrical SFP can be configured on the SDH Access Card, due to
the mechanical interference between two electrical SFPs inserted in the same
board.
SDH traffic is not supported in stacking configurations (two or three MSS
connected through Ethernet cable).
LAG The LAG ID parameter value must be in the range 1:8. This applies to user
2E1 SFP For 2 E1 SFP protection (one SFP connected the main core, the second SFP
connected to the spare core, and the two cores connected together through a
Y-cable), LOS must be disabled as the Core EPS switching criteria, meaning that
Ethernet user port protection cannot be available at the same time.
EoSDH For EoSDH SFP protection (one SFP connected to the main core, the second SFP
NPT For protection of the NTP server, the IP addresses of the two NTP servers must
be provisioned in the NTP Craft Terminal screen (main and spare). If the NTP
server is not protected, the same IP address must be inserted twice in the main
and spare NTP Craft Terminal window.
Item Description
(8 of 12)
Release Notice
PM tool When case counters related to radio queues are active, it is recommended that
the modem card not be removed; otherwise, counter values might be lost. To
avoid this, stop the counters before maintenance operations.
It is recommended that maintenance operation of the modem card be avoided
when Ethernet radio counters are activated; otherwise, data could be
accidentally lost.
It is recommended that the PM tool be closed during equipment configuration;
it can be opened again after the completion of configuration process.
AUX card Service channel traffic should always be cross-connected in a given radio
direction together with at least one other type of traffic (for example,
Ethernet, TDM or ATM). If only the service channels are transported in a radio
link, performances are not guaranteed.
ASAP card An IMA group is declared as operational when associating E1 links and not only
when at least one link of the group is operationally up.
The ASAP card startup voltage is 44 V.
IMA counters and ATM counters are mutually exclusive; that is, only one set of
counters can be activated at one time.
ODU300 56 MHz channel spacing is not foreseen by the ETSI standard in some
frequency bands and is therefore not supported by all the ODU300 codes.
Before selecting a modem profile with channel spacing equal to 56 MHz in
the radio channel, check that the ODU is supporting it because no
consistency check is performed by the system (no error notification is
reported). To confirm support, push the refresh button: if the frequency
value has been reported as 00, it means that the 56 MHz option has been
refused and is not supported by ODU.
If admission control is enabled, for 1+1 HSB, maintenance operations on
modem boards are not error-free on traffic that exceeds 4QAM bandwidth.
TDM2TDM guaranteed traffic is not impacted.
If admission control is disabled, for 1+1 HSB, maintenance operations on
modem boards are not error-free. TDM2TDM guaranteed traffic that
exceeds 4QAM throughput is impacted as well. The traffic hit might be as
long as 5 s.
The maximum output power corresponds to the 64 QAM modulation scheme
and it does not change according to the modulation scheme.
If the configuration is changed 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.
If admission control is disabled and the number of E1 links exceeds 4QAM
bandwidth, when the RSL value degrades and causes a modulation scheme
downgrade, usually all the TDM traffic is impacted. It is possible that some
E1s stay temporarily up and transmitting.
Item Description
(9 of 12)
Release Notice
MPT-xC On an upgrade from 1+0 to 1+1 HSB, a false LOF alarm might appear. If this
occurs, close and then reopen the NeTO session.
A Tx fail event is shown as auto-mute status inside the CT radio panel.
1+1 switching from a traffic point of view is not affected by this incorrect
indication.
For 1+1 radio protection, both channels must be provisioned in the same
way, for static or adaptive modulation. This configuration (adaptive or
static) must be done before enabling the protection scheme. If both
channels are not configured the same way, performances are not
guaranteed.
When changing the configuration from adaptive modulation to static
modulation, it is recommended that other modem parameters (for
example, channel spacing, modulation) not be changed before the
completion of this operation.
MPT-HC: If the RPS interconnection cable fails (with the corresponding
alarm coupling link), operator commands (force and lockout) are not
applied.
MSS-1c
MCT For the MPR-1c/MPR-e side, MCT cannot be opened when special characters
are present in the path of MCT installation.
Workaround: None
OSPF In some cases, up to 40 s is required to recalculate a new route when OSPF is
enabled.
NE IP address With OSFP enabled on the MSS-1c, when the NE IP address changes, there is a
traffic impact.
Storm control The real traffic at the output of the police might be lower than the
provisioned threshold if there is Ethernet switch congestion.
DLF storm control and ingress rate limiter cannot be used at the same time.
MSS-1c 16E1 The MSS-1c 16E1/DS1 variant is not compatible with the MPT-MC/HC loaded
with 3.0 SWP. Refer to the user guide for instructions.
VLAN mng Modification of the pbit value of VLAN=1 has no effect on traffic, even if CT
allows the modification.
SFP management If there is an inconsistency between the SFP type installed (optical or
electrical) and the SFP type configured, no traffic will start on the
impacted port.
For a remote MCT connection, the real hardware status can be checked
from the Remote Inventory.
If an SFP is configured in the MCT but not inserted, an LOS alarm is raised
and maintained even after the SFP is inserted. The alarm is cleared once
the configuration is reapplied.
Network Management The administrative and operational status of ports is not updated in the
network manager. Ports are always seen as up and operational. Alarms are
correctly reported.
Synchronization The maximum round-trip delay accepted for the SNTP server is 2 seconds. After
that time, the SNTP server is declared unreachable and time synchronization
is impossible.
MSS-1c and MPR-e
MCT The routing table is not refreshed automatically when opened. Workaround:
click on the Refresh button.
With NTP protocol disabled, mistakenly setting the NE date with a value
greater that the PC date (assuming that this is the correct value), it is not
possible to restore the correct date
Item Description
(10 of 12)
Release Notice
MPR-e: History upload time mismatch The time-stamps used for PM history data are 1 hour different from the one
used to display the PM on MCT.
The display of this date/time-stamps may be done in local time by applying the
appropriate offset to the UTC time.
XPIC polarization or XPIC to non XPIC
configuration change triggers MPT
restart
When changing MPT XPIC polarization or moving from XPIC to non XPIC
configuration, a warm restart of the MPT is triggered automatically, causing a
loss of supervision for about 2 minutes.
MPR-e: NE time update without NTP If the MPT has been set with a date in the future, this timedate will be used as
starting point as soon as the MPT restarts. The timedate can be up-dated
through MCT but in case of restart of MPT, the timedate in the future will be
re-applied.
PM/Ethernet counters The time-stamps used for PM history data are 1 hour different from the one
used to display the PM on MCT. The time-stamp used in history is UTC (GMT)
while the local time is used on MCT.
Applicable to MPR-e only: Ethernet Traffic port counter displayed is not
meaningful if the Ethernet flow throughput is higher than 100Mb/s.
XPIC When changing MPT XPIC polarization (example from H to V) or changing from
XPIC to non XPIC configuration, a loss of supervision (about 2 minutes) will
occur. However, no traffic hit is present.
Provisioning tool A bad entry in the provisioning tool is highlighted in red, however after
correction, the entry is still in red.
Workaround: Close and reopen the tab.
ASBR router By default MPR-e/MSS1c acts as an ASBR router even if a static route does not
exist in the NE
S-VLAN ID Traffic will not pass if S-VLAN ID is 1.
Workaround: S-VLAN 1 cannot be used to carry customer VLANs. In 802.1ad, the
operator must declare at least one S-VLAN in the range of 2 to 4080.
QoS The expected S-TPID value for a QinQ frame is 0x8100.
IP setting If there is a radio connection between an MSS-1c terminal (or MPR-e terminal)
and an MSS-4/8 terminal, at least a subnet 255.255.255.252, mask /30, must
be booked for each MPR-e/MSS-1c so that a network static route can be
addressed. This allows the reachability of MSS-1c and MPR-e in case OSPF
routing was enabled for the MSS-4/8 portion.
MCT When simultaneously changing two parameters for the IP address for NMS1
and NMS2 (for example, NMS1 and NMS2 IP addresses or NMS1 IP address
and mask), if the error message NMS IP configuration failed appears,
then apply each change separately.
If the MCT laptop is connected successively on collocated NEs, the operator
must wait 10 s before connecting to the other NE (otherwise, the waiting
time is 2 min).
An alternative is to clean the ARP table of the PC with the command: arp
-d*.
If the MCT is connected to the NE for more than 1 day, the connection may
time out.
Security Unlike the MSS-4/8, the source IP address used for the SNTP query is not the
NE IP address, but the used port IP address. Therefore, if a firewall is used, all
the addresses of the port interfaces (NMS1, NMS2, TMN in-band) must be
authorized.
TMN The TMN in-band VLAN ID is always reserved (default: 4080), even if TMN in-
band is not used. Any traffic using the same VLAN ID will be flooded.
Some instability may be observed if the NE is flooded by TMN flow or with short
frame lengths (64 bytes).
Item Description
(11 of 12)
Release Notice
MPR-e
QoS Ethertype 81xx and 91xx are not managed correctly regarding QoS.
Item Description
(12 of 12)
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 E-1
Release Notice
E. VLAN values for STM-1 flows
E.1 VLAN values tables
Tables E-1, E-2, and E-3 show VLAN values for STM-1 flows. You can use these
values to cross-connect STM-1 transparent flows coming from one or two SDH
access cards to a LAG, to achieve N+1 protection on STM-1 flows.
Table E-1 VLAN values for STM-1 flows - VLAN set 1
VLAN set 1
2 10 18 26 34 42 50 58 66 74
82 90 98 106 114 122 130 138 146 154
162 170 178 186 194 202 210 218 226 234
242 250 259 267 275 283 291 299 307 315
323 331 339 347 355 363 371 379 387 395
403 411 419 427 435 443 451 459 467 475
483 491 499 507 512 520 528 536 544 552
560 568 576 584 592 600 608 616 624 632
640 648 656 664 672 680 688 696 704 712
720 728 736 744 752 760 769 777 785 793
801 809 817 825 833 841 849 857 865 873
881 889 897 905 913 921 929 937 945 953
961 969 977 985 993 1001 1009 1017 1030 1038
1046 1054 1062 1070 1078 1086 1094 1102 1110 1118
(1 of 3)
E-2 November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Release Notice
1126 1134 1142 1150 1158 1166 1174 1182 1190 1198
1206 1214 1222 1230 1238 1246 1254 1262 1270 1278
1287 1295 1303 1311 1319 1327 1335 1343 1351 1359
1367 1375 1383 1391 1399 1407 1415 1423 1431 1439
1447 1455 1463 1471 1479 1487 1495 1503 1511 1519
1527 1535 1540 1548 1556 1564 1572 1580 1588 1596
1604 1612 1620 1628 1636 1644 1652 1660 1668 1676
1684 1692 1700 1708 1716 1724 1732 1740 1748 1756
1764 1772 1780 1788 1797 1805 1813 1821 1829 1837
1845 1853 1861 1869 1877 1885 1893 1901 1909 1917
1925 1933 1941 1949 1957 1965 1973 1981 1989 1997
2005 2013 2021 2029 2037 2045 2050 2058 2066 2074
2082 2090 2098 2106 2114 2122 2130 2138 2146 2154
2162 2170 2178 2186 2194 2202 2210 2218 2226 2234
2242 2250 2258 2266 2274 2282 2290 2298 2307 2315
2323 2331 2339 2347 2355 2363 2371 2379 2387 2395
2403 2411 2419 2427 2435 2443 2451 2459 2467 2475
2483 2491 2499 2507 2515 2523 2531 2539 2547 2555
2560 2568 2576 2584 2592 2600 2608 2616 2624 2632
2640 2648 2656 2664 2672 2680 2688 2696 2704 2712
2720 2728 2736 2744 2752 2760 2768 2776 2784 2792
2800 2808 2817 2825 2833 2841 2849 2857 2865 2873
2881 2889 2897 2905 2913 2921 2929 2937 2945 2953
2961 2969 2977 2985 2993 3001 3009 3017 3025 3033
3041 3049 3057 3065 3078 3086 3094 3102 3110 3118
3126 3134 3142 3150 3158 3166 3174 3182 3190 3198
3206 3214 3222 3230 3238 3246 3254 3262 3270 3278
3286 3294 3302 3310 3318 3326 3335 3343 3351 3359
3367 3375 3383 3391 3399 3407 3415 3423 3431 3439
3447 3455 3463 3471 3479 3487 3495 3503 3511 3519
3527 3535 3543 3551 3559 3567 3575 3583 3588 3596
3604 3612 3620 3628 3636 3644 3652 3660 3668 3676
3684 3692 3700 3708 3716 3724 3732 3740 3748 3756
3764 3772 3780 3788 3796 3804 3812 3820 3828 3836
3845 3853 3861 3869 3877 3885 3893 3901 3909 3917
3925 3933 3941 3949 3957 3965 3973 3981 3989 3997
4005 4013 4021 4029 4037 4045 4053 4061 4069 4077
VLAN set 1
(2 of 3)
Release Notice
4085 4093
VLAN set 2
3 11 19 27 35 43 51 59 67 75
83 91 99 107 115 123 131 139 147 155
163 171 179 187 195 203 211 219 227 235
243 251 258 266 274 282 290 298 306 314
322 330 338 346 354 362 370 378 386 394
402 410 418 426 434 442 450 458 466 474
482 490 498 506 513 521 529 537 545 553
561 569 577 585 593 601 609 617 625 633
641 649 657 665 673 681 689 697 705 713
721 729 737 745 753 761 768 776 784 792
800 808 816 824 832 840 848 856 864 872
880 888 896 904 912 920 928 936 944 952
960 968 976 984 992 1000 1008 1016 1031 1039
1047 1055 1063 1071 1079 1087 1095 1103 1111 1119
1127 1135 1143 1151 1159 1167 1175 1183 1191 1199
1207 1215 1223 1231 1239 1247 1255 1263 1271 1279
1286 1294 1302 1310 1318 1326 1334 1342 1350 1358
1366 1374 1382 1390 1398 1406 1414 1422 1430 1438
1446 1454 1462 1470 1478 1486 1494 1502 1510 1518
1526 1534 1541 1549 1557 1565 1573 1581 1589 1597
1605 1613 1621 1629 1637 1645 1653 1661 1669 1677
1685 1693 1701 1709 1717 1725 1733 1741 1749 1757
1765 1773 1781 1789 1796 1804 1812 1820 1828 1836
1844 1852 1860 1868 1876 1884 1892 1900 1908 1916
1924 1932 1940 1948 1956 1964 1972 1980 1988 1996
2004 2012 2020 2028 2036 2044 2051 2059 2067 2075
2083 2091 2099 2107 2115 2123 2131 2139 2147 2155
2163 2171 2179 2187 2195 2203 2211 2219 2227 2235
2243 2251 2259 2267 2275 2283 2291 2299 2306 2314
2322 2330 2338 2346 2354 2362 2370 2378 2386 2394
2402 2410 2418 2426 2434 2442 2450 2458 2466 2474
(1 of 2)
VLAN set 1
(3 of 3)
Release Notice
2482 2490 2498 2506 2514 2522 2530 2538 2546 2554
2561 2569 2577 2585 2593 2601 2609 2617 2625 2633
2641 2649 2657 2665 2673 2681 2689 2697 2705 2713
2721 2729 2737 2745 2753 2761 2769 2777 2785 2793
2801 2809 2816 2824 2832 2840 2848 2856 2864 2872
2880 2888 2896 2904 2912 2920 2928 2936 2944 2952
2960 2968 2976 2984 2992 3000 3008 3016 3024 3032
3040 3048 3056 3064 3079 3087 3095 3103 3111 3119
3127 3135 3143 3151 3159 3167 3175 3183 3191 3199
3207 3215 3223 3231 3239 3247 3255 3263 3271 3279
3287 3295 3303 3311 3319 3327 3334 3342 3350 3358
3366 3374 3382 3390 3398 3406 3414 3422 3430 3438
3446 3454 3462 3470 3478 3486 3494 3502 3510 3518
3526 3534 3542 3550 3558 3566 3574 3582 3589 3597
3605 3613 3621 3629 3637 3645 3653 3661 3669 3677
3685 3693 3701 3709 3717 3725 3733 3741 3749 3757
3765 3773 3781 3789 3797 3805 3813 3821 3829 3837
3844 3852 3860 3868 3876 3884 3892 3900 3908 3916
3924 3932 3940 3948 3956 3964 3972 3980 3988 3996
4004 4012 4020 4028 4036 4044 4052 4060 4068 4076
4084 4092
VLAN set 3
0 8 16 24 32 40 48 56 64 72
80 88 96 104 112 120 128 136 144 152
160 168 176 184 192 200 208 216 224 232
240 248 257 265 273 281 289 297 305 313
321 329 337 345 353 361 369 377 385 393
401 409 417 425 433 441 449 457 465 473
481 489 497 505 514 522 530 538 546 554
562 570 578 586 594 602 610 618 626 634
642 650 658 666 674 682 690 698 706 714
722 730 738 746 754 762 771 779 787 795
803 811 819 827 835 843 851 859 867 875
(1 of 3)
VLAN set 2
(2 of 2)
Release Notice
883 891 899 907 915 923 931 939 947 955
963 971 979 987 995 1003 1011 1019 1028 1036
1044 1052 1060 1068 1076 1084 1092 1100 1108 1116
1124 1132 1140 1148 1156 1164 1172 1180 1188 1196
1204 1212 1220 1228 1236 1244 1252 1260 1268 1276
1285 1293 1301 1309 1317 1325 1333 1341 1349 1357
1365 1373 1381 1389 1397 1405 1413 1421 1429 1437
1445 1453 1461 1469 1477 1485 1493 1501 1509 1517
1525 1533 1542 1550 1558 1566 1574 1582 1590 1598
1606 1614 1622 1630 1638 1646 1654 1662 1670 1678
1686 1694 1702 1710 1718 1726 1734 1742 1750 1758
1766 1774 1782 1790 1799 1807 1815 1823 1831 1839
1847 1855 1863 1871 1879 1887 1895 1903 1911 1919
1927 1935 1943 1951 1959 1967 1975 1983 1991 1999
2007 2015 2023 2031 2039 2047 2048 2056 2064 2072
2080 2088 2096 2104 2112 2120 2128 2136 2144 2152
2160 2168 2176 2184 2192 2200 2208 2216 2224 2232
2240 2248 2256 2264 2272 2280 2288 2296 2305 2313
2321 2329 2337 2345 2353 2361 2369 2377 2385 2393
2401 2409 2417 2425 2433 2441 2449 2457 2465 2473
2481 2489 2497 2505 2513 2521 2529 2537 2545 2553
2562 2570 2578 2586 2594 2602 2610 2618 2626 2634
2642 2650 2658 2666 2674 2682 2690 2698 2706 2714
2722 2730 2738 2746 2754 2762 2770 2778 2786 2794
2802 2810 2819 2827 2835 2843 2851 2859 2867 2875
2883 2891 2899 2907 2915 2923 2931 2939 2947 2955
2963 2971 2979 2987 2995 3003 3011 3019 3027 3035
3043 3051 3059 3067 3076 3084 3092 3100 3108 3116
3124 3132 3140 3148 3156 3164 3172 3180 3188 3196
3204 3212 3220 3228 3236 3244 3252 3260 3268 3276
3284 3292 3300 3308 3316 3324 3333 3341 3349 3357
3365 3373 3381 3389 3397 3405 3413 3421 3429 3437
3445 3453 3461 3469 3477 3485 3493 3501 3509 3517
3525 3533 3541 3549 3557 3565 3573 3581 3590 3598
3606 3614 3622 3630 3638 3646 3654 3662 3670 3678
3686 3694 3702 3710 3718 3726 3734 3742 3750 3758
3766 3774 3782 3790 3798 3806 3814 3822 3830 3838
VLAN set 3
(2 of 3)
Release Notice
3847 3855 3863 3871 3879 3887 3895 3903 3911 3919
3927 3935 3943 3951 3959 3967 3975 3983 3991 3999
4007 4015 4023 4031 4039 4047 4055 4063 4071 4079
4087 4095
VLAN set 3
(3 of 3)
Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 F-1
Release Notice
F. Open issues in R3.2.0 and earlier
F.1 Open issues in R3.2.0 and earlier
This chapter describes the issues that were open for R3.2.0 and prior releases.
Usage notes
The information in Table F-1 and Table F-2 supplements or clarifies information in
the documentation.
Table F-1 Usage notes for Release 3.2.0
Item Description
All systems
Craft Terminal To avoid conflict among the different JRE versions, ensure that only the
recommended JRE version is enabled. Note: For 64-bit systems, 32-bit Java is
suggested (as installed via TCO Suite), since 64-bit Java ships only the 64-bit
browser plug-in, but only 32-bit browsers can be set as default.
When using the Alarm Monitor via the Web interface, ensure that the proxy is
disabled in your browser application.
MSS-4/8
Radio LAG For radio LAG N+0, the sum of TDM traffic (E1, DS1, DS3, STM-1) must fit the
bandwidth of a single radio channel. For adaptive modulation, the sum of TDM
traffic (E1, DS1, DS3, STM-1) must fit the bandwidth associated with the
minimum modulation scheme selected on a single radio channel.
(1 of 2)
F-2 November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0
Release Notice
Table F-2 Usage notes for previous releases
Backup and restore The backup filename must not include the following characters: space, &, /,
\,:, *,?, <, >, and |. Local language characters are also not allowed. The
filename always contains the version as prefix; for example, "V020100",
corresponding to version V2.1.0, or "V030200" corresponding to version V3.2.0.
This prefix is inserted automatically by the software when the MIB backup file
is created, and is used automatically by the software when the MIB restore
must be performed.
Radio Direction label User-defined site names (radio direction label) must not contain the
following characters: space, &, /, \,:, *,?, <, >, and |. Local language
characters are also not allowed.
Ring Ring with MPTs is supported only with an MPT connected to the core; ring is not
supported if MPTs are connected to and MPT access card.
Ring with MPTs is not supported in an NE with core protection enabled.
Cross-connections from a radio direction (spur) not belonging to the ring are
not supported; this means, for example, that the E1s need to be terminated in
the NE supporting ring and cross-connected to the radio belonging to the ring.
The ring cross-connection screen is not supported by NMS.
5620 SAM/Nx(1+0) For each Nx(1+x) (x=[0..1]) radio configuration, the involved radio ports must
be provisioned as follows.
Only one radio port can have PPP RF enabled.
having the same LINKGRP and different LINKMEMBER, matching the far-end
radio ports: LinkID Expected and Sent values are requested to be equal (for
example, (11,11), (13,13), (15,15).)
For multiple Nx(1+x) radio configurations on the same node, the LINKGRP
must be unique without overlapping (for example, 1 and 2). Other radio
ports not involved in Nx(1+0) protection (in single 1+0 or 1+1 radio
configurations) must have PPP RF enabled or PPP RF disabled and
optionally the LinkID provisioned, but the ports must have a different
LINKGRP (for example, 3,...,9) so that other LINKMEMBERs are not
discovered.
5620 SAM/Radio LAG For radio LAG, the involved radio ports must be provisioned as follows.
No radio port can have PPP RF enabled.
(LAG membership). A different LINKMEMBER must be used, matching the
far-end radio ports: LinkID Expected and Sent values are requested to be
equal (for example, (11,11), (13,13), (15,15)).
Other radio ports not involved in a LAG (in single 1+0 or 1+1 radio
configurations) must have PPP RF enabled and optionally the LinkID
provisioned, but the ports must have a different LINKGRP (for example,
3,...,9).
Item Description
All systems
Flow control It is recommended that flow control be used in half-duplex mode.
E1 flows Simultaneous TDM2TDM and TDM2TDM2Ethernet cross-connections are not
supported on MPT-HC/MC. TDM2TDM and TDM2Eth flow are instead supported
simultaneously. This restriction does not apply to ODU300.
(1 of 6)
Item Description
(2 of 2)
Release Notice
Alarms An HBER alarm can be raised, according to the different modem profiles, in
arrange of BER from 1e-4 to 1e-7 (TSAlo51767).
For MPT-HC 1+1 radio protected configurations, if LOS is generated by an IDU-
ODU cable disconnection of one of the two MPTs, alarms reported in the CT RPS
section are not meaningful (WTDcd03748).
After each provisioning or maintenance operation, it is recommended the CT
alarm bullets status be refreshed using the refresh button, to ensure that the
CT is showing the right bullets color.
Adaptive modulation With MPT-xC, in adaptive modulation, it is possible to use manual mode for
troubleshooting. Disabling manual mode might cause a traffic impact.
MSS-4/8
SDH channelized STM-1 channelized and multiservice packet ring cannot be supported at the
same time in a 9500 MPR NE. This means that E1 handoff in a multiservice
packet ring environment cannot be done through an STM-1 channelized
interface.
MSP protection is not supported. 1+1 SDH protection is EPS only
E1 cross-connections between a radio direction with radio LAG and an SDH
channelized board are not supported.
Backup and restore During a database restore operation, the restore might fail with an
operation failed pop-up window. If this occurs, perform the restore
operation again.
If a force command is entered (core protection) from the spare core to the
main core, before making a backup it is necessary to wait a few minutes,
in order to permit the flash cards database alignment. If the backup has
been done during this alignment phase, the backup operation can fail; if
this occurs, close the Craft Terminal, reopen it and apply the backup again.
Craft Terminal In the current configuration view window, the EAS segregated port 8 is
reported as MPT-ACC plug-in Slot 5.
Radio LAG It is recommended that radio LAG be disabled before changing the modem
profile of one of the links already involved in the LAG.
Ethernet OAM LT and Loopback cause traffic impact on TDM2ETH flows if they
are cross-connected to a LAG.
The maximum number of MPTs inside a radio LAG is four.
Radio LAG is not supported with MPT directly connected to the Core card.
The LAG ID parameter value must be in the range 1:8. This applies to User
During the provisioning phase, removing a radio link inside a LAG might cause
traffic impact on all the links in the group.
Synchronization If primary and secondary synchronization sources are radio (slave node), either
SSM is disabled or enabled in a homogeneous way on the primary and secondary
sources.
MPT connected to core MPT connected to the core is not supported if the core; is protected.
EAS card If the SFP is plugged into the SFP port of the EAS before the port is
provisioned, the RI of the SFP will not be displayed. Unplug the SFP and
plug it in after the port is provisioned.
On both the Core card and EAS Ethernet ports, if autonegotiation is
enabled, flow control does not get configured properly.
On 10/100 Base-T interfaces, jumbo frames are not supported.
Port segregation between an MPT access card and an EAS card that are
inserted in slots in the same row does not work properly. If the two cards
are inserted in slots in different rows, the problem is not present.
Item Description
(2 of 6)
Release Notice
XPIC The ATPC function cannot be activated if XPIC has been configured on the
related radio interface.
XPIC and Adaptive Modulation are not supported in the current release.
In an XPIC configuration, if an MPT-HC is in alarm, the XPD value may not
be accurate.
In an XPIC configuration with radio LAG configured, if the MPT-ACC module
is reset or if the MPT-HC is power cycled, there is an extended traffic loss
on the entire LAG.
In an XPIC configuration, if the XPIC cable is removed, a traffic hit might
occur on the remote Rx of the orthogonal polarization.
In an XPIC configuration, when the remote Tx is muted, the XPD value is
not accurate.
In order to correctly configure XPIC in 1+1, the protection must first be
configured between mate MPTs and then the XPIC in the protected radio
direction must be configured.
MPT-MC/HC In a 1+1 MPT-MC/ HC configuration, if both channels fail with the same
alarm, the protection of the MPT-HC remains on the spare channel. This is
normal behavior since this is a double fault.
In a 1+1 MPT-MC/HC protection configuration, if an MPT-ACC board is
extracted and inserted, it is possible that the channel will remain in the
equipment failure state. This issue is only seen when the MPT-ACC module
is extracted and inserted quickly (approximately 10 seconds between
actions). If the MPT-ACC module is inserted after 15 seconds, this issue is
not seen. An NE restart clears the equipment status.
In a 1+1 FD configuration with MPT-MC, the switching time for the MPT
access card missing state might be up to 500 ms.
The maximum number of MPTs that can be powered through an MSS-8 shelf
is eight. If the number of MPT exceeds this limit, DC injector boxes or a
direct connection of MPT to battery can be used.
Ring In G.8032 ring configurations, it is possible for the ERPS states to be in a
dead-locked scenario where the non-RPL owner nodes are in an idle
state and the RPL owner is in a protection state. If this occurs, disable
and enable the RPL owner instance after all the other non-RPL owner ERP
instances have been activated.
There is no alarm or condition reported when a G.8032 ring is not in the
idle state. However, on the EPRS configuration screen, the current status
of the G.8032 ring is reported.
The ERPS topology label does not allow for special characters.
In a G.8032 ring configuration, if the same VLAN is deleted from one
instance and added to the other instance, Ethernet traffic will be affected
for approximately 300 seconds.
TMN in-band Disabling TMN in-band does not free the VLAN ID from being used for other
functionality. In this case, disable the Ethernet port or assign another VLAN ID
to that port to free the previous VLAN ID.
Performance monitoring PM history is cleared if the PM is refreshed when an active dialog failure
alarm is present.
Ethernet statistics are not initialized to zero when the EAS/Core card
module resets or during a equipment protection on the EAS ports.
The WTPMS tool cannot be launched from NeTO if there is not an active
connection to the 9500 MPR. Workaround: Use the desktop shortcut to
launch the off-line WTPMS tool.
After a reset of the MPT-MC or MPT-HC, the 24-hour PM is lost.
After starting PM and loading PM data, the hourglass disappears after 1
minute but the tool is still loading. Wait until the counters have the green
checkmarks and the start/stop button shows that PM is running.
Item Description
(3 of 6)
Release Notice
Preprovisioning tool The following features are not supported by the provisioning tool or by the web
interface:
ASAP card mng
AUX card mng
8 Gbit ports EAS card mng
LAG
MPT Protection 2*(1+1) in W configuration. Get and Set operations are not
guaranteed if one of these configurations is present in the Network
Element.
SDH If an HBER condition occurs over the radio, a scrambled all 1s signal is
inserted in the outgoing STM-1 flow (Rx side), not an MS_AIS signal.
For MPR back-to-back configurations, ALS on the SDH card should be disabled.
Only 1xSTM-1 electrical SFP can be configured on the SDH Access Card, due to
the mechanical interference between two electrical SFPs inserted in the same
board.
SDH traffic is not supported in stacking configurations (two or three MSS
connected through Ethernet cable).
LAG The LAG ID parameter value must be in the range 1:8. This applies to user
2E1 SFP For 2 E1 SFP protection (one SFP connected the main core, the second SFP
EoSDH For EoSDH SFP protection (one SFP connected to the main core, the second SFP
NPT For protection of the NTP server, the IP addresses of the two NTP servers must
be provisioned in the NTP Craft Terminal screen (main and spare). If the NTP
server is not protected, the same IP address must be inserted twice in the main
and spare NTP Craft Terminal window.
PM tool When case counters related to radio queues are active, it is recommended that
the modem card not be removed; otherwise, counter values might be lost. To
avoid this, stop the counters before maintenance operations.
It is recommended that maintenance operation of the modem card be avoided
when Ethernet radio counters are activated; otherwise, data could be
accidentally lost.
It is recommended that the PM tool be closed during equipment configuration;
it can be opened again after the completion of configuration process.
After 24 hours have elapsed, the PM tool screen shows 00.00.00 instead of
24.00.00.
AUX card Service channel traffic should always be cross-connected in a given radio
direction together with at least one other type of traffic (for example,
Ethernet, TDM or ATM). If only the service channels are transported in a radio
link, performances are not guaranteed.
ASAP card An IMA group is declared as operational when associating E1 links and not only
when at least one link of the group is operationally up.
The ASAP card startup voltage is 44 V.
IMA counters and ATM counters are mutually exclusive; that is, only one set of
counters can be activated at one time.
Item Description
(4 of 6)
Release Notice
ODU300 56 MHz channel spacing is not foreseen by the ETSI standard in some
frequency bands and is therefore not supported by all the ODU300 codes.
Before selecting a modem profile with channel spacing equal to 56 MHz in
the radio channel, check that the ODU is supporting it because no
consistency check is performed by the system (no error notification is
reported). To confirm support, push the refresh button: if the frequency
value has been reported as 00, it means that the 56 MHz option has been
refused and is not supported by ODU.
If admission control is enabled, for 1+1 HSB, maintenance operations on
modem boards are not error-free on traffic that exceeds 4QAM bandwidth.
TDM2TDM guaranteed traffic is not impacted.
If admission control is disabled, for 1+1 HSB, maintenance operations on
modem boards are not error-free. TDM2TDM guaranteed traffic that
exceeds 4QAM throughput is impacted as well. The traffic hit might be as
long as 5 s.
The maximum output power corresponds to the 64 QAM modulation scheme
and it does not change according to the modulation scheme.
If the configuration is changed 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.
If admission control is disabled and the number of E1 links exceeds 4QAM
bandwidth, when the RSL value degrades and causes a modulation scheme
downgrade, usually all the TDM traffic is impacted. It is possible that some
E1s stay temporarily up and transmitting.
MPT-xC On an upgrade from 1+0 to 1+1 HSB, a false LOF alarm might appear. If this
occurs, close and then reopen the NeTO session.
A Tx fail event is shown as auto-mute status inside the CT radio panel.
1+1 switching from a traffic point of view is not affected by this incorrect
indication.
For 1+1 radio protection, both channels must be provisioned in the same
way, for static or adaptive modulation. This configuration (adaptive or
static) must be done before enabling the protection scheme. If both
channels are not configured the same way, performances are not
guaranteed.
When changing the configuration from adaptive modulation to static
modulation, it is recommended that other modem parameters (for
example, channel spacing, modulation) not be changed before the
completion of this operation.
MPT-HC: If the RPS interconnection cable fails (with the corresponding
alarm coupling link), operator commands (force and lockout) are not
applied.
MSS-1c
Storm control The real traffic at the output of the police might be lower than the
provisioned threshold if there is Ethernet switch congestion.
DLF storm control and ingress rate limiter cannot be used at the same time.
MSS-1c 16E1 The MSS-1c 16E1/DS1 variant is not compatible with the MPT-MC/HC loaded
with 3.0 SWP. Refer to the user guide for instructions.
VLAN mng Modification of the pbit value of VLAN=1 has no effect on traffic, even if CT
allows the modification.
Item Description
(5 of 6)
Release Notice
Open issues
Table F-3 describes the restrictions from previous releases. Table F-4 describes the
open issues and restrictions for this release. Where available, workarounds have been
provided.
SFP management If there is an inconsistency between the SFP type installed (optical or
electrical) and the SFP type configured, no traffic will start on the
impacted port.
For a remote MCT connection, the real hardware status can be checked
from the Remote Inventory.
If an SFP is configured in the MCT but not inserted, an LOS alarm is raised
and maintained even after the SFP is inserted. The alarm is cleared once
the configuration is reapplied.
Network Management The administrative and operational status of ports is not updated in the
network manager. Ports are always seen as up and operational. Alarms are
correctly reported.
Synchronization The maximum round-trip delay accepted for the SNTP server is 2 seconds. After
that time, the SNTP server is declared unreachable and time synchronization
is impossible.
MSS-1c and MPR-e
QoS The expected S-TPID value for a QinQ frame is 0x8100.
IP setting If there is a radio connection between an MSS-1c terminal (or MPR-e terminal)
and an MSS-4/8 terminal, at least a subnet 255.255.255.252, mask /30, must
be booked for each MPR-e/MSS-1c so that a network static route can be
addressed. This allows the reachability of MSS-1c and MPR-e in case OSPF
routing was enabled for the MSS-4/8 portion.
Alarms There is no alarm indicating failure of PPP RF. If a radio link failure occurs, the
user is notified by an alarm.
MCT When simultaneously changing two parameters for the IP address for NMS1
and NMS2 (for example, NMS1 and NMS2 IP addresses or NMS1 IP address
and mask), if the error message NMS IP configuration failed appears,
then apply each change separately.
If the MCT laptop is connected successively on collocated NEs, the operator
must wait 10 s before connecting to the other NE (otherwise, the waiting
time is 2 min).
An alternative is to clean the ARP table of the PC with the command: arp
-d*.
If the MCT is connected to the NE for more than 1 day, the connection may
time out.
Security Unlike the MSS-4/8, the source IP address used for the SNTP query is not the
NE IP address, but the used port IP address. Therefore, if a firewall is used, all
the addresses of the port interfaces (NMS1, NMS2, TMN in-band) must be
authorized.
TMN When the MCT is connected to the MSS-1c or MPR-e through another switch or
router via TMN in-band, some TMN frames may be dropped if there is
congestion on the switch or router.
The TMN in-band VLAN ID is always reserved (default: 4080), even if TMN in-
band is not used. Any traffic using the same VLAN ID will be flooded.
Some instability may be observed if the NE is flooded by TMN flow or with short
frame lengths (64 bytes).
Item Description
(6 of 6)
Release Notice
Table F-3 Restrictions in previous releases
Issue number Item Systems Description
R3.2-001 Ethernet services MSS-1c At 100 Mb/s and 10 Mb/s, the maximum size for jumbo frames is
limited to 9143 bytes. The Ethernet port must be set to 1Gb/s to
support jumbo frames up to 9728 bytes.
R3.2-002 Performance
Management
All The NE Time/date is not persistent on an MPT restart.
R3.2-003 ASAP card MSS-4/8 The CIR of CBR/UBR+ traffic over MPT-xC might be not
guaranteed over MPT if there is radio congestion.
ATM cross-connections between the ODU300 and MPT-xC are not
supported.
R3.2-004 NTP MSS-4/8 If one of the two NTP servers is down, the NTP is immediately
synchronized to the second server, but the notification is
reported with 30 minutes of delay. An incorrect message appears
on the CT.
R3.2-005 Battery alarm MSS-4/8 If battery fail alarm is present, a blue light bullet is displayed
inside the block diagram view (inside the Craft Terminal) but the
navigation is not correct; it is redirected to the main core instead
of to the MSS-8.
If the MSS-8 has only one battery input connected, a standing
Battery Fail warning is present.
R3.2-006 Maintenance MSS-4/8 If a demodulator failure alarm is raised or a cable is
disconnected in a 1+1 FD or HSB configuration with a forced
lockout condition, the alarm is not displayed at the link level but
is displayed at the hop level.
R3.2-007 Operation MSS-4/8 On the Craft Terminal screen of the CORE Main View, when
reporting the status of the autonegotiation process, the label
other is always incorrectly displayed. The information related
to the autonegotiation results (speed, flow control, and so on)
are correctly reported in the top part of the same screen.
Alarm severity is dependent on the provisioning order of
protection groups. For example, if you remove a P32E1DS1
module that is in a protection group, the alarm is raised as minor;
however, if you provision the spare module unequipped and then
create a protection group, the alarm is raised as major.
R3.2-008 Link identifier MSS-4/8 After a configuration change from 1+0 to 1+1 HSB, the LIM alarm
is not revaluated; in order to re-evaluate disable/enable the link
identifier. This behavior is common to ODU300 and MPT-HC.
R3.2-009 PM tool MSS-4/8 The navigation between an alarm and the Alarm Monitoring
window is not supported.
Depending on the number of E1 links being monitored, the PM
tool might take a few minutes to load and display the history
table.
After a migration from 9500 MPR R3.00 to 9500 MPR R3.01, if
performance monitoring is started in R3.00, it is not
automatically started in R3.01. Workaround: Manually start the
PM data.
R3.2-010 2x(1+0) 2x(1+1)
configuration
MSS-4/8 It is not possible to disable TMN RF after it has been enabled. If
the operator attempts to disable it, 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 the CT and reset the NE.
(1 of 2)
Release Notice
Table F-4 Open issues in R3.2.0
R3.2-011 Alarm monitoring MSS-4/8 During navigation from the Alarm Monitoring window to the Craft
Terminal (and vice versa), the target window might not be shown
in front. In order to view the target window, make the front
window an icon.
Synchronization alarms (synch degrade and synch LOS) are not
reported in the Alarm Log.
R3.2-012 ODU300 MSS-4/8 The Craft Terminal allows a PTX change in steps of 1 dB. If the
maximum ODU output power is .5, a starting value of .5 must be
written.
Changing the configuration from presetting mode to adaptive
modulation raises an incorrect warning message of Tx Power
Out of Range. Re-edit the output power and ignore the
message.
The setting of28MHz 256QAM takes 10 s to be applied (longer
than other modem profiles).
R3.2-013 MPT-xc MSS-4/8 If the RPS interconnection cable fails (with the corresponding
activation of the coupling link alarm), operator commands
(forced and lockout) are not applied. The coupling link alarm
is also raised in the event of a hardware failure or switch off of
one of the two MPT-HC MPTs.
A false indication of remote Automute may occur if the MPT Tx
is unmuted without any impact on the XPIC and 1+1
functionalities.
R3.2-014 Backup and
restore
MSS-4/8 Configuration changes are not blocked during backup operations.
Customers should coordinate provisioning changes for times
when backup operations are not scheduled.
Item number Description Comments
MSS-4/8
R3.2-002 CFM frames (Ethertype 0x8902) are being
looped/repeated by the standby CSM when sent
over either MPT-HC/MC or ODU300.
None
R3.2-004 With MPT-HC configured in 1+1 and the MPT-
ACC card in 1+1 and in NON revertive mode, if
an EPS occurs on the MPT-ACC card when the
RPS is on SPARE, after the EPS switch, the RPS
will switch to MAIN even thought it is
configured for NON revertive switching
R3.2-005 The ATPC Loop Problem alarm is not generated

on spare link in 1+1 FD configuration.
R3.2-006 The event log browser and the JUSM QoS /

Scheduler configuration queue numbers do not
align.
When looking at the Event log browser, add
1 to the queue number for correspondence
with CT mapping.
R3.2-007 The 50/256 MPT profile in R3.2.0 is NOT air
compatible with the 50/256 profile in R3.1.0.
When migrating from R3.1.0 to R3.2.0,
ensure the far-end radio is upgraded first.
R3.2-008 The Transmit power shows different ranges
between the main and spare channel.
Perform a warm start of the shelf to correct
the issue.
(1 of 3)
Issue number Item Systems Description
(2 of 2)
Release Notice
R3.2-009 When in XPIC mode the automute clears when
MPT-HC or MPTACC powered down and back up
with the XPIC cable still removed.
Perform an MPT-xC restart and ensure that
the XPIC cable is connected, or do not restart
an MPT-xC if the XPIC cable is disconnected.
R3.2-010 When the ethernet PM stats are running on the
ODU, if the MD300 is physically removed,
invalid values are returned.
Stop Ethernet PM before removing the board.
R3.2-011 The CT still shows the LAG type as Layer 2 radio
or Layer 2 Ethernet when L3 is selected as the
Hash method.
Link Aggregation Type is used to distinguish
between Radio Link Aggregation and
Ethernet Link Aggregation. After configuring
the Link Aggregation Type, the user can
change the hashing algorithm in order to
select Layer 2 (distribution of frames based
on MAC header and VLAN tag) or Layer 3
(distribution of frames based on IP header).
By default, Layer 2 hashing is selected.
R3.2-012 When the ODU is configured in a LAG, IF
loopbacks will cause the ODU to be removed
from the LAG.
Do not use IF loopbacks when the ODU is a
member of a LAG.
R3.2-013 Java 6 is required for proper operation of the
9500 MPR Craft Terminal. Java 7 is not
supported.
R3.2-014 In a LAG with at least 3 members, if one

member is already in the Down state, if an
additional member fails, its status is not
updated in the LAG window in the Craft
Terminal.
Use the refresh button to refresh the screen
status.
R3.2-015 MPT-HC 10/128 profile is not air compliant with
the MPT-HC 10/128 in R3.1.
R3.2-016 When the MPT-xC is connected to the CSM, the

PM measurement history only allows to view
the data one direction (forward) because the
back button is grayed out.
Open and close the measurement value
screen.
R3.2-017 When there is a radio alarm on MPT-ACC and
there is an adjacent PDH card, navigation from
the alarm tool the GUI opens the PDH card view
instead of MPT-ACC view.
R3.2-018 Multiple software download (to make software

upgrades I parallel on the nodes belonging to
the same tree or sub-network): it is strongly
suggested, in case Ethernet user port #4 is used
in any node of the sub-network to transport
TMN traffic, to limit the number of concurrent
software download to 1. This is valid for CT/
1350 OMS/5620 SAM. Of course, in case of
multiple sub-networks, the scheduled
download (from 1350OMS or 5620 SAM), shall
address only one NE of each sub-network per
time, so that it is possible in any case to
perform multiple downloads, addressing in
parallel multiple NEs belonging to different
sub-networks.
R3.2-019 With MPT-MC/HC, changing from static

modulation to adaptive modulation and then
going again back to static modulation, it is
recommended to provision again PTx value,
otherwise it could happen that the PTX value
provisioned in adaptive modulation is kept.

(2 of 3)
Release Notice
MSS-1c/MPR-e
R3.2-020 After a temporary link failure on a radio hop
causing an interruption PPP RF, it takes 4
minutes before to open the MCT on the remote
station.
The problem is not present when the firewall is
disabled on the PC (as recommended in the
User Manual).
R3.2-021 A bad entry in the provisioning tool is

highlighted in red, however after correction,
the entry is still in red.
Close and reopen the tab.
R3.2-022 After attach/detach of the OSFP area several
times, the NE does not respond.
R3.2-023 By default MPR-e/MSS1c acts as an ASBR router
even if a static route does not exist in the NE
R3.2-024 Traffic will not pass if S-VLAN ID is 1. S-VLAN 1 cannot be used to carry customer
VLANs. In 802.1ad, the operator must
declare at least one S-VLAN in the range of 2
to 4080.
R3.2-025 In some cases the provisioning tool does not
allow the use of ECID values after modification
of the flow ID when there were errors.
Produce the configuration file without
creating duplicate IDs.
R3.2-026 When using OSPF, after changing the NMS IP
address of the MSS1c/MPRE, the OSPF
convergence does not complete.
R3.2-027 When upgrading from MPR3.0, the high and low
thresholds of the TCA alarms are inversed;
after the migration, the operator must
reconfigure manually the thresholds through
the MCT.
MSS-1c
R3.2-003 For the MPR-1c/MPR-e side, MCT cannot be
opened when special characters are present in
the path of MCT installation.
None
R3.2-028 In some cases, up to 40 s is required to
recalculate a new route when OSPF is enabled.
R3.2-029 With OSFP enabled on the MSS-1c, when the NE

IP address changes, there is a traffic impact.
MPR-e
R3.2-030 Ethertype 81xx and 91xx are not managed
correctly regarding QoS.

(3 of 3)
Release Notice
Customer documentation and product support
Customer documentation
http://www.alcatel-lucent.com/myaccess
Product manuals and documentation updates are available at
alcatel-lucent.com. If you are a new user and require access to this
service, please contact your Alcatel-Lucent sales representative.
Technical Support
http://support.alcatel-lucent.com
Documentation feedback
documentation.feedback@alcatel-lucent.com
2012 Alcatel-Lucent. All rights reserved.

3db19043aaaafmzza01 - v1 - 9500 Mpr-E r4.1.0 Release Notice

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

3db19043aaaafmzza01 - v1 - 9500 Mpr-E r4.1.0 Release Notice

Transféré par

Droits d'auteur :

Formats disponibles

Alcatel-Lucent 9500

MICROWAVE PACKET RADIO FOR ETSI | RELEASE 4.1.0

R3.2-005 The ATPC Loop Problem alarm is not generated

R3.2-006 The event log browser and the JUSM QoS /

R3.2-014 In a LAG with at least 3 members, if one

R3.2-016 When the MPT-xC is connected to the CSM, the

R3.2-018 Multiple software download (to make software

R3.2-019 With MPT-MC/HC, changing from static

Item number Description Comments

R3.2-021 A bad entry in the provisioning tool is

R3.2-029 With OSFP enabled on the MSS-1c, when the NE

Item number Description Comments

Vous aimerez peut-être aussi