M07cee 131220151044 Phpapp01

Alcatel-Lucent 9500
MICROWAVE PACKET RADIO FOR ETSI AND ANSI | RELEASE 5.0.0

R E L E A S E N O T I C E
3DB 19083 AAAA DEZZA 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 2013 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 2013 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 R5.0.0 August 2013 iii
3DB 19083 AAAA DEZZA Edition 01
Release Notice
Contents
9500 MPR Release 5.0.0 Release Notice 1
Summary ................................................................................................1
Safety information......................................................................................1
New release capabilities...............................................................................1
NEtO Server Manager [ALL] ............................................................2
Multichannel Link Aggregation L1 with Adaptive Modulation
[MSS1/4/8] .........................................................................2
Recommended Minimal Channel Space and Modulation Scheme in
Adaptive Modulation Mode...................................................3
MultiService Packet Ring enhacement [MSS1/4/8] ................................3
Microwave Access ring..............................................................4
Microwave Aggregation ring .......................................................5
Mixed Fiber/Microwave Ring ......................................................5
Provider Bridge enhancement [MSS-1/4/8] .........................................6
Management of Provider Bridge Ports Port Type...............................7
Ethernet user port LAG.............................................................7
Provider Bridge parameters .......................................................7
Provider Bridge and MultiService Packet Ring [MSS1/4/8] .......................8
TMN-in-band: DSCP value user configurable [MSS1/4/8]..........................8
SDH/SONET (Transparent) loopbacks [MSS-4/8]....................................9
Packet throughput booster on MPT-HL for ANSI market [MSS1/4/8] ............9
Additional modem profiles [ALL] .....................................................9
MPRe Support of Fast Ethernet (100Mb) interface [MPRe]........................9
SNMP support of AM PM, MSE and current modulation [MPRe and
MSS-1c]............................................................................ 10
MPRe: security improvement [MPRe] .............................................. 10
Features significantly changed ..................................................................... 10
Retained capabilities ................................................................................. 11
Discontinued capabilities ............................................................................ 11
Documentation delivery ............................................................................. 12
Software and license delivery ...................................................................... 13
Contents
iv August 2013 Alcatel-Lucent 9500 MPR R5.0.0
Edition 01 3DB 19083 AAAA DEZZA
Release Notice
Software compatibility............................................................................... 14
Downloading the software ........................................................... 14
Installing the software ............................................................... 15
Software components............................................................. 15
TCO suite and MCT system requirements...................................... 16
Upgrade paths ..................................................................... 17
Precautions and recommendations ............................................. 18
Traffic impact during the SWP activation ..................................... 18
Third-party software notes .......................................................... 19
Release content ....................................................................................... 19
Implemented features................................................................ 19
Application notes...................................................................... 19
Closed issues ........................................................................... 20
Usage notes ............................................................................ 21
Technical support..................................................................................... 30
Customer documentation............................................................................ 30
Accessing customer documentation................................................ 30
Providing feedback about customer documentation ............................ 31
Glossary .............................................................................................. 32
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
A.4 Radio PM G.826: current and historical data [MPR-e/MSS-1c] ................... A-4
A.5 AM performance monitoring [MPR-e/MSS-1c]....................................... A-4
A.6 Modem measurements [MPR-e/MSS-1c] ............................................. A-4
B. Previous release capabilities B-1
B.1 Capabilities in R4.2.0................................................................... B-1
1+1 on Core [MSS-4/8]............................................................... B-1
MSS-1 1+1 configuration [MSS-1] ................................................... B-2
MSS Housekeeping [MSS-1/4/8] .................................................... B-2
100 BaseT interface to MPR-e [MPR-e]............................................ B-2
For ANSI market: 1+0 MPT-HL Support on Core [MSS-4/8] ..................... B-2
For ANSI market: 1+0 MPT-HL Support on the MSS-1 [MSS-1].................. B-3
B.2 Capabilities in R4.1.0................................................................... B-3
Provider Bridge QinQ 802.1ad [MSS-1/4/8] ...................................... B-3
Global Configuration............................................................. B-4
S-VLAN creation .................................................................. B-4
Member set and untagged set of a PNP....................................... B-5
S-VLAN removal................................................................... B-5
Equipment components de-provisioning...................................... B-5
S-VLAN ID 1 management ....................................................... B-5
Management of Provider Bridge Ports Port Type............................ B-6
PNP - S-VLAN TPID (Tag Protocol Identifier) ................................. B-6
PNP - Acceptable Frame Type.................................................. B-6
PNP - Port S-VLAN ID............................................................. B-6
PNP - Priority and Drop Eligible................................................ B-7
PNP - Port Priority ............................................................... B-7
Contents
Alcatel-Lucent 9500 MPR R5.0.0 August 2013 v
Release Notice
PNP - Ingress Filtering ........................................................... B-7
PNP - PCP and DEI fields of S-VLAN Tag ...................................... B-7
PNP - S-VLAN Rate Limiter ...................................................... B-8
PNP - Per-CoS Rate Limiter ..................................................... B-8
Customer Network Port Parameters........................................... B-8
Bridge Mode Configuration.....................................................B-10
C-VLAN Translation .............................................................B-11
MultiService Ring Protection 8032 v2 ........................................B-11
Ethernet user port LAG.........................................................B-11
Packet throughput booster (header compression) [ALL] ......................B-11
7705 SAR + MPR-e [MPR-e] .........................................................B-12
7705 SAR + MPR-e Separate NEs...............................................B-12
7705 SAR + MPR-e Single NE ...................................................B-13
IPv6 and OSPFv3 [MSS-1/4/8] .....................................................B-13
TACACS+ enhancements [MSS-1/4/8] ............................................B-14
Features significantly changed in R4.1.0 ........................................B-14
STM-1 channelized support of L2 LAG crossconnections ..................B-14
Adaptive modulation support for ODU300...................................B-15
Transmitter mute function [MSS-1/4/8] .....................................B-15
B.3 Capabilities in R4.0.0..................................................................B-15
SNMPv3 support [MSS4/8] ..........................................................B-16
Per-CoS rate Limiter [MSS-4/8] ...................................................B-16
User configurable label on traffic interfaces [MSS4/8] .......................B-17
ANSI market only: SNMP support for Ethernet counters
[MPR-e/MSS-1c]................................................................B-18
TMN in-band with L2 Ethernet LAG...............................................B-18
ANSI market: OC-3 support [MSS-4/8] ...........................................B-19
MPR-e repeater back to back support [MPR-e] .................................B-19
B.4 Capabilities in R3.4.0..................................................................B-20
Multichannel Link Aggregation L1 [MSS-4/8]....................................B-21
Supported configurations ......................................................B-21
Description of supported scenarios...........................................B-21
LAG L1 configuration ...........................................................B-24
LAG L1 configuration modification ...........................................B-25
LAG L1 activation and deactivation ..........................................B-25
LAG L1 deletion..................................................................B-26
Port Add and Remove operations .............................................B-26
Master port definition ..........................................................B-26
Port provisioning rules..........................................................B-27
Allowed configurations .........................................................B-27
Protected Radio LAG [MPT-HL]................................................B-28
Adaptive Modulation and modem profiles...................................B-29
Service restrictions .............................................................B-29
Service restrictions for the first port added to the LAG [MPT-HL] ......B-29
User ports and radio interfaces ...............................................B-30
Radio QoS configuration........................................................B-30
Supported services and configurations.......................................B-30
Maximum throughput ...........................................................B-30
LAG rate ..........................................................................B-30
Maximum Ethernet frame length .............................................B-31
Admission control ...............................................................B-31
Maximum number of cross-connections......................................B-31
Contents
vi August 2013 Alcatel-Lucent 9500 MPR R5.0.0
Release Notice
Segregations .....................................................................B-31
1+1 FD to LAG conversion procedure [MPT-HL].............................B-32
Synchronization..................................................................B-32
SSM ................................................................................B-33
TMN-RF configuration...........................................................B-33
LAG alarms .......................................................................B-34
Switching criteria ...............................................................B-34
Remote defect indication......................................................B-35
Wait to restore ..................................................................B-35
MPT connected to EAS card [MSS-4/8] ...........................................B-37
Port rate limiter [MSS-4/8] ........................................................B-37
Storm control [MSS-4/8] ...........................................................B-38
Per VLAN rate limiter [MSS-4/8] ..................................................B-38
VLAN swap [MSS-4/8] ...............................................................B-39
ETSI market: Additional modem profiles [MSS-4/8 and MPR-e] ..............B-40
Fiber/microwave protection [MSS-4/8]..........................................B-40
MPT-MC: new modem profiles support, up to 256QAM/56 MHz [ALL].......B-42
TACACS+ [MSS-4/8] .................................................................B-43
Server Support ...................................................................B-43
Authentication/Authorization.................................................B-43
Server Monitoring ...............................................................B-44
Server Validation ................................................................B-44
P32E1DS1 unit performances [MSS-4/8] .........................................B-44
Incoming ..........................................................................B-44
Outgoing ..........................................................................B-45
C. Supported hardware C-1
C.1 Supported hardware .................................................................... C-1
Existing hardware .................................................................... C-1
ODU300 ................................................................................ C-9
D. Closed issues in previous releases D-1
D.1 Closed issues in R4.2.0 ................................................................. D-1
D.2 Closed issues in previous releases .................................................... D-2
Contents
Alcatel-Lucent 9500 MPR R5.0.0 August 2013 vii
Release Notice
List of figures
Figure 1 Ethernet and TDM flows in a ring .........................................................4
Figure 2 Advanced Install Settings screen........................................................ 17
Figure B-1 MPR-e 1+0 repeater configuration .................................................B-20
Figure B-2 Intra Plug-in LAG L1 ..................................................................B-22
Figure B-3 Intra Plug-in LAG L1 scenario .......................................................B-22
Figure B-4 Intra Plug-in LAG L1 scenario .......................................................B-22
Figure B-5 Cross Plug-in LAG L1..................................................................B-23
Figure B-6 Cross plug-in LAG scenarios .........................................................B-23
Figure B-7 Protected Cross Plug-in LAG L1.....................................................B-23
Figure B-8 Supported scenario for Protected Cross Plug-in LAG L1 ........................B-24
Figure B-9 Supported scenario for Protected Cross Plug-in LAG L1 ........................B-24
Figure B-10 Master port definition ..............................................................B-27
Figure B-11 Allowed configurations .............................................................B-28
Figure B-12 Fibre microwave protection .......................................................B-41
Figure B-13 Fiber microwave protection implemented on tail links .......................B-42
List of tables
Table 1 Cards and radios supporting MultiService Packet Ring .................................4
Table 2 9500 MPR R5.0.0 documentation ordering information .............................. 12
Table 3 9500 MPR-A R5.0.0 software ............................................................. 13
Table 4 Third-party software....................................................................... 13
Table 5 R5.0.0 Software components for MSS-1c and MPR-e.................................. 15
Table 6 R5.0.0 Software components for MSS-4 and MSS-8.................................... 16
Table 7 Upgrade paths to Release 5.0.0.......................................................... 17
Table 8 NAOS software included with 9500 MPR R5.0.0 CT software image................ 19
Table 9 Closed issues in R5.0.0 .................................................................... 20
Table 10 Usage notes for R5.0.0................................................................... 21
Table 11 Glossary .................................................................................... 32
Table A-1 Traffic Ethernet port counters [MPR-e].............................................. A-2
Table A-2 Radio Qos counters [MPR-e/MSS-1c].................................................. A-3
Table A-3 Radio PM G.826: current and historical data........................................ A-4
Table A-4 AM performance monitoring counters................................................ A-4
Table A-5 Modem measurements .................................................................. A-5
Table B-1 MSS housekeeping ....................................................................... B-2
Table B-2 Modem profiles supporting OC-3 .....................................................B-19
Table C-1 Existing MSS-4/8 shelf hardware in R5.0.0 .......................................... C-1
Table C-2 Existing MSS-1 hardware in R5.0.0.................................................... C-2
Table C-3 9500 MPR peripheral cards (MSS-4/8 only) .......................................... C-2
Table C-4 Existing MSS-1c hardware in R5.0.0 .................................................. C-2
Table C-5 9500 MPR-E supported flashcards (MSS-1/4/8 only, for ETSI market)........... C-3
Table C-6 Supported SFP modules................................................................. C-4
Table C-7 MPT-HL in R5.0.0, for ANSI market ................................................... C-5
Table C-8 MPT-HC/XP modules in R5.0.0 ........................................................ C-6
Table C-9 9558HC 5.8 GHz unlicensed in R5.0.0, for ANSI market........................... C-6
Table C-10 MPT-HC L6 GHz in R5.0.0 ............................................................. C-6
Contents
viii August 2013 Alcatel-Lucent 9500 MPR R5.0.0
Release Notice
Table C-11 MPT-HC U6 GHz in R5.0.0............................................................. C-6
Table C-12 MPT-HC 6 GHz in R5.0.0 .............................................................. C-6
Table C-13 MPT-HC 7/8 GHz in R5.0.0............................................................ C-7
Table C-14 MPT-HC 11 GHz in R5.0.0 ............................................................. C-7
Table C-18 MPT-XP L6 GHz in R5.0.0 ............................................................. C-8
Table C-19 MPT-XP U6 GHz in R5.0.0 ............................................................. C-8
Table C-20 MPT-XP 7 GHz in R5.0.0............................................................... C-8
Table C-21 MPT-XP 8 GHz in R5.0.0............................................................... C-9
Table C-22 MPT-HC/XP/9558HC external diplexers in R5.0.0 ................................ C-9
Table D-1 Closed issues in R4.2.0 ................................................................. D-1
List of procedures
Procedure 1 To download 9500 MPR software from the OLCS site ........................... 14
Procedure 2 To find contact information for technical assistance........................... 30
Procedure 3 To download customer documentation from the OLCS site.................... 30
Procedure B-1 High-level procedure for configuring TMN in-band with L2 LAG..........B-18
Alcatel-Lucent 9500 MPR R5.0.0 August 2013 1
Release Notice
9500 MPR Release 5.0.0 Release Notice
Summary
The 9500 MPR R5.0.0 addresses both the ETSI and ANSI markets. This document
describes and provides guidelines for both the ETSI and ANSI markets. This
document contains references to ANSI-specific and ETSI-specific equipment.
The 9500 MPR-E designates ETSI software. The 9500 MPR-e designates the
MPT-MC/HC/XP/9558HC deployed in standalone mode or in connection with a
7705 SAR indoor unit. References to MPT-HC in this document refer to the
MPT-HCv2/MPT-XP/9558HC unless otherwise stated.
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 user documentation.
New release capabilities
The features described below are introduced in the 9500 MPR R5.0.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 August 2013 Alcatel-Lucent 9500 MPR R5.0.0
Release Notice
Legend:
[MSS-1/4/8]the feature applies to the MSS-1/4/8 system only
[MSS-4/8]the feature applies to the MSS-4/8 system only
[MSS-1:]:the feature applies to the MSS-1 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
NEtO Server Manager [ALL]
Multichannel Link Aggregation L1 with Adaptive Modulation [MSS1/4/8]
MultiService Packet Ring enhacement [MSS1/4/8]
Provider Bridge enhancement [MSS-1/4/8]
Provider Bridge and MultiService Packet Ring [MSS1/4/8]
TMN-in-band: DSCP value user configurable [MSS1/4/8]
SDH/SONET (Transparent) loopbacks [MSS-4/8]
Packet throughput booster on MPT-HL for ANSI market [MSS1/4/8]
Additional modem profiles [ALL]
MPRe Support of Fast Ethernet (100Mb) interface [MPRe]
SNMP support of AM PM, MSE and current modulation [MPRe and MSS-1c]
NEtO Server Manager [ALL]
The NEtO Servers Manager is an application included in the TCO Tool Suite that
manages the FTP and SFTP servers available on the operators computer/server
where the NEtO application is running. The NEtO Servers Manager also manages
RMI Registry components started through the NEtO application and displays the
number of running components.
The NEtO Servers Manager is started when the first NEtO application is started or
the offline Performance Monitoring Tool is started by the operator. The FTP and
SFTP servers are disabled by default.
The NEtO Servers Manager allows the operator to manage (enable and disable) the
FTP/SFTP server. This functionality works in both IPv4 and IPv6 IP addressing
modes.
Multichannel Link Aggregation L1 with Adaptive Modulation
[MSS1/4/8]
LAG L1 with adaptive modulation is supported by MPT-HC, MPT-XP and MPT-HL
(ANSI only).
Aggregation of Radio Links configured in Adaptive Modulation Mode is allowed if
all Radio Links in the LAG are configured in Adaptive Modulation Mode and have
the same Channel Spacing.
It is not required that the Radio Links compliant with these constraints are also
configured with the same Modulation Range and Reference Modulation.
Release Notice
Recommended Minimal Channel Space and Modulation Scheme in Adaptive
Modulation Mode
For aggregation of Radio Links configured in Adaptive Modulation Mode, the
recommended minimal Channel Spacing and Modulation Scheme for correct
working of the LAG are the following:
[ETSI] Minimal Channel Spacing = 14 MHz
[ANSI] Minimal Channel Spacing = 10 MHz (MPT-HC), 30MHz (MPT-HL)
Minimal Modulation Scheme = 16 QAM
The system will not enforce the configuration of Channel Spacing and/or Modulation
Scheme compliant with these minimal values.
If the Operator configures a value below such minimal values, a Warning message
will be issued to inform that with such settings the LAG traffic integrity is not
guaranteed.
MultiService Packet Ring enhacement [MSS1/4/8]
In R 5.0.0 two main features are added:
Support inside a ring of LAG L1, addressing aggregation rings
Support of mixed ring, meaning the possibility to have ring which links are either
microwave or fiber.
Generally speaking, two different applications can be identified that distinguish
between an access ring and an aggregation ring. The difference is driven by the
capacity that needs to be transported, so that an access ring can be classified from a
microwave point of view as a 1+0 ring. If the capacity is beyond the one that can
fill an entire radio channel, N+ 0 configurations shall be used to increase the
available bandwidth.
The following general points are addressed in R5.0.0 by both access ring and
aggregation ring:
MultiService Packet Ring is supported by the MSS-1/4/8. The NE supports one
ring with two instances. It is possible to use a ring either with the NE working in
802.1Q or (newly introduced) in 802.1ad mode.
Ethernet and TDM flows (TDM2TDM and TDM2ETH) are supported at the
same time in the ring; in the hand off point, three different options can be used:
TDM terminated into an STM1 channalized
TDM terminated into DS1/E1s
TDM not terminated and transported as MEF8 frames.
Release Notice
Figure 1 Ethernet and TDM flows in a ring
Microwave Access ring
In an access ring, the radios are in 1+0 configuration, that is, one radio towards the
east direction and one radio towards the west direction. Taking R5.0.0 as reference,
Table 1 summarizes the different options for radios and cards supporting
MultiService Packet Ring.
Table 1 Cards and radios supporting MultiService Packet Ring
Notes
(1)
ANSI only
(2)
In a Ring topology, Packet Throughput Booster (header compression) can be enabled on the MPTs,
except on the MPTs connected to an EAS card.
The following guidelines apply:
Adaptive modulation can be supported optionally in the ring
Spurs can use ODU300 and/or MPT MC/HC/XP/9558HC
Mixed configuration (east direction on Core-E card and west on MPT plug-in) is
not supported
In case of ring supported by core card, the remaining 4 ports can be used for spurs
connections
In case of ring supported by MPT access cards, the remaining ports are not
expected to be used for spurs
MPT-HC MPT-MC ODU300 MPT-HL
(1)

MPT Access card
Core-E card
(optical or
electrical ports)
MSS-1 (optical or
electrical ports)
EAS (P8ETH)
card
(2)

MPT Access card
Core-E card
(optical or
electrical ports)
MSS-1 (optical or
electrical ports)
Modem card EAS (P8ETH)
card
(2)

Release Notice
In case of ring supported by EAS cards, the remaining ports are not expected to
be used for spurs and/or user access. 1+0 configuration is achieved as a sub-case
of LAG L1 configuration with N=1. LAG L1 with N=1 is not air compatible with
a 1+0 configuration
Packet Throughput Booster (header compression) can be optionally enabled in
MPTs, except the case of MPTs connected to EAS card
Ethernet and DS1/E1 flows are supported (TDM2TDM and TDM2ETH profile)
Microwave Aggregation ring
In an aggregation ring, the radios are in N+ 0 LAG L1 configuration, that is, N radios
groomed into one single logical flow towards east direction and the same towards
west direction.
The following guidelines apply:
One EAS card with N+0 LAG L1 is used for east direction and another EAS card
with N+0 LAG L1 is used for west direction
Adaptive modulation can be supported optionally in the ring
Spurs can use MPT MC/HC/XP
Ethernet and DS1/E1 flows are supported (TDM2TDM and TDM2ETH profile)
XPIC can be used
Switching criteria for the ring is LAG LOS, that is, when all the radios of a given
LAG group are down, a ring switch will be triggered
A 1+0 ring can be implemented using EAS card with LAG N+0 with N=1; it should
be however noted that, in case at least in one node a microwave link uses a LAG L1
configuration (included N=1 case), all the microwave links of the ring must use an
EAS card.
Mixed Fiber/Microwave Ring
A mixed ring is composed of links that can use microwave or fibre as propagation
media; the following situations apply:
East and west ports are fibres
One port is microwave and one port is fibre
East and west are microwave
East and west ports are fibres
Fibers are connected to SFP ports of the Core-E card or MSS-1.
When an Optical User Ethernet interface is assigned as Ring Port, the following
configuration has to be performed by the operator to guarantee a consistent behavior
of MultiService Packet Ring together with Core Protection:
Usage of optical splitter
Disable auto-negotiation on Optical User Ethernet interface
Disable Ethernet LOS as switching criteria for Core protection
Release Notice
Disable Static-LAG
Enable the Hold-Off Timer for Ethernet LOS on both ends of the optical
connection when at least one end of the connection is working with Core
Protection.
A Hold-Off Timer, implemented using defect persistency processing, can be applied
to the Ethernet LOS defect independently for each Optical User Ethernet interface
belonging to the ERPS Topology.
The Hold-Off Timer is fixed to 500 msec to raise the alarm. No persistency check
(Hold-On) is applied to clear the alarm.
Every time an Optical User Ethernet interface is assigned to an ERPS Topology, the
application of Hold-Off Timer to Ethernet LOS defect must be disabled. The
Hold-Off Timer application can be managed (enabled) only after an ERPS Topology
has been created and it is independent of the presence or status of ERPS Instances.
One port is microwave and one port is fiber
One of the following applies:
The optical fiber is connected to one SFP ports of core card. In case of core
protection rules described in the previous session apply.
The microwave direction is connected (with an MPT-HC or HL) to EAS card
with LAG L1 N+0; 1+0 configuration is achieved with LAG L1 with N=1
East and west ports are microwave
Radios can be either MPT-HC/MC or HL. Any of the configurations described in
the Microwave Aggregation ring section can be used. It should be noted, however,
that, if at least in one node a microwave link uses a LAG L1 configuration (included
N=1 case), all the microwave links of the ring must use an EAS card.
Full Fiber Ring
The MSS can support a full fiber ring. Fibers are connected to SFP ports of the
Core-E card or MSS-1. In case of Core protection an optical splitter must be used to
connect Core main and Core spare.
Provider Bridge enhancement [MSS-1/4/8]
When the NE is configured in Provider Bridge (802.1ad) 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:
NNI: this is an interface internal to the Provider Bridged Network. S-VLAN 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
UNI (port based): this is an interface at the edge of the Provider Bridged Network.
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)
UNI (VLAN-based): this is an interface at the edge of the Provider Bridged
Network. S-VLAN is assigned based on C-VLAN ID carried by C-VLAN Tag or
based on User Ethernet port in case of untagged frames (C-tagged service
interface)
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.
Management of Provider Bridge Ports Port Type
Each User Ethernet port of Core and EAS boards can be configured either NNI or as
UNI. For Radio ports, the Port Type is fixed to NNI and cant be modified by
management systems. For Radio ports, the Acceptable Frame Type parameter is
fixed to admit only VLAN-tagged frames and cannot be modified by management
systems.
The default Port Type for User Ethernet ports is NNI.
Ethernet user port LAG
Ethernet user port LAG is compatible with 802.1ad Provider Bridge mode in R5.0.0.
Provider Bridge parameters
Parameters apply for each port type:
NNI - S-VLAN TPID
The S-VLAN TPID selects the service instance associated to the port for
untagged and C-VLAN priority-tagged frames. The port must be in the untagged
set of the S-VLAN.
UNI (port-based)- Port Priority or C-VLAN Priority
The port priority represents the priority assigned to untagged frames ingressing
the port.
UNI (VLAN-based)- C-VLAN/S-VLAN mapping and egress settings
Release Notice
Ingress settings:
The list of C-VLAN IDs represents the list of C-VLANs to be managed by the
port. By default, the list is empty.
Each C-VLAN ID must be mapped to an S-VLAN which represents the service
instance used to carry the C-VLAN in the network. The S-VLAN must have the
port in its untagged set. More than one C-VLAN can be associated to the same
S-VLAN.
The Remove C-VLAN parameter can be set for each C-VLAN ID. This allows
only the S-VLAN tag to be carried over the network when the association
between the C-VLAN and the VLAN-based service instance is one-to-one. The
Remove C-VLAN parameter can only be set for one C-VLAN mapped to an
S-VLAN ID.
The S-VLAN priority defines the priority of the tagged Ethernet frames
ingressing the port. The priority can be inherited from the PCP of the C-VLAN
tag or configured by the user. The default is inherited.
Egress settings:
The C-VLAN tag of Ethernet frames egressing the port can be removed, which
declares the port as untagged. The default Untag C-VLAN parameter is false.
When the port is disabled, the parameter returns to the default value.
For each S-VLAN ID having the port in its member set, the C-VLAN ID of the
C-VLAN tag to be added to Ethernet frames egressing the port can be configured.
This allows a C-VLAN tag to be added to Ethernet frames carried over the
network with only the S-VLAN tag, when the association between the C-VLAN
and the VLAN-based service instance is one-to-one. The default value is 0, which
means that no association to an S-VLAN is in place and no C-VLAN tag will be
added. When the port is disabled, the parameter returns to the default value.
Provider Bridge and MultiService Packet Ring [MSS1/4/8]
The ERPS functionality is supported when the NE is working in one of the following
Bridge Modes:
802.1Q (Virtual Bridge)
802.1ad (Provider Bridge) The VLANs managed by ERPS are the S-VLANs.
It is allowed to change the Bridge Mode from Virtual Bridge to Provider Bridge
when ERPS functionality is active.
TMN-in-band: DSCP value user configurable [MSS1/4/8]
The value of DSCP field of IPv4 packets is user configurable.
The value of DSCP field can range from 0 (000000) to 63 (111111). Default value is
34 (100010 AF41 Codepoint). The configuration of the value of DSCP field is not
allowed when the TMN In-Band networking interface is disabled.
Release Notice
SDH/SONET (Transparent) loopbacks [MSS-4/8]
SDH loopbacks (line-facing and core-facing) have been introduced for SDH
transparent. The loopback can be activated separately on each STM-1/OC-3 port.
Packet throughput booster on MPT-HL for ANSI market [MSS1/4/8]
Packet Throughput Booster is now available to support the MPT-HL in ANSI mode.
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 can be applied to MPT-MC, MPT-HC/XP, and MPT-HL
(ANSI), except when the MPTs are involved in a LAG L1 group. In this case Packet
Throughput Booster cannot be applied with the current release. Packet Throughput
Booster can be applied to 1+0 or 1+1 HSB/FD/SD configurations.
A license string (PTB) is required to enable header compression.
Additional modem profiles [ALL]
MPT-HC /XP:
L6GHz 60/128 QAM, Fixed Mod (ANSI)
L6GHz 60/256 QAM, Fixed Mod (ANSI)
11GHz 30/40/50 MHz with 4-256 QAM, XPIC AM (ANSI)
5.8 GHz 30 MHz 4QAM, Fixed Mod (ETSI)
MPT-HL:
UU6 GHz 25MHz AM with 4-256 QAM (ANSI)
MPRe Support of Fast Ethernet (100Mb) interface [MPRe]
In previous release the 9500 MPR-e required a 1000Mb interface on the electrical
port. Starting in this release, the user can provision the electrical Ethernet port as a
100Mb interface, thus eliminating the need for the 1000Mb interface on the host
system. The QoS in the direction from the radio to the cable is not managed, so
overall radio throughput is expected to be lower or equal to 100 Mbit/sec. When the
MPR-e is in 100Mb mode, only SyncE is allowed for the synchronization.
Release Notice
SNMP support of AM PM, MSE and current modulation [MPRe and
MSS-1c]
SNMP support of:
Adaptive Modulation PM
Current MSE (Mean Square Error) value
Current Modulation
MPRe: security improvement [MPRe]
The following changes have been made:
Possibility to manage Craftperson profile users and a single Admin profile user
User management data are in the MPR-e database and are persistent at any restart
Admin user allowed to change the password for any user account
Craftperson users allowed to change their own password
23 user accounts supported
Password Complexity enforced
Features significantly changed
None
Release Notice
Retained capabilities
The 9500 MPR R5.0.0 retains all capabilities from the 9500 MPR R4.2.0.
Discontinued capabilities
None
Release Notice
Documentation delivery
The 9500 MPR R5.0.0 documentation is available through electronic distribution
only. Contact your Alcatel-Lucent Sales Support Representative to place an order.
Table 2 lists the documentation items. See Customer documentation for information
about downloading the documentation from OLCS.
Table 2 9500 MPR R5.0.0 documentation ordering information
Document Alcatel-Lucent part number
9500 MPR 5.0.0 Release Notice (this document) 3DB19083AAAADEZZA
ANSI documentation
9500 MPR-A 5.0.0 Product Information Guide 3EM23952ANAA
9500 MPR-A 5.0.0 Installation Practices 3EM23953ANAA
9500 MPR-A 5.0.0 Software Installation and Upgrade Guide 3DB19083AAAARJZZA
9500 MPR-A 5.0.0 Operations and Administration Guide 3EM23954ANAA
9500 MPR-A 5.0.0 Turn-Up Manual 3EM23955ANAA
9500 MPR-A 5.0.0 Maintenance and Trouble-Clearing Guide 3EM23956ANAA
9500 MPR-A MPT-HC/MPR-e Modem Specifications 3EM23959ACAA
9500 MPR-A MPT-HL Modem Specifications 3EM23960ABAA
9500 MPR-A ODU300 Modem Specifications 3EM23961ABAA
9500 MPR-A 5.0.0 Engineering Support Documents 3EM23957ANAA
9500 MPR-A 5.0.0 Electronic Documentation 3EM23951ANAA
ETSI documentation
9500 MPR 5.0.0 User Guide 3DB19901ADAA
Documentation for both markets
9500 MPR 5.0.0 MPR-e User Guide 3DB19901EDAA
9500 MPR 5.0.0 MSS-1c User Guide 3DB19901DDAA
9500 MPR 5.0.0 MPT-GC User Guide 3DB19025AAAA 02
Release Notice
Software and license delivery
Table 3 lists the software version information.
Table 3 9500 MPR-A R5.0.0 software
Table 4 lists the third-party software that is used for execution of the 9500 MPR
R5.0.0 and that is liable to license agreements. 9500 MPR R5.0.0 CT operation has
been validated with the following third-party software.
Table 4 Third-party software
Note
(1)
Alcatel-Lucent recommends Windows 7 in an IPv6 environment.
Product Software version
For ANSI market
9500 MPR R5.0.0 MIB
3DB18896EAAA
Alcatel-Lucent 9500 MPR-A Release R5.00 Software CD kit 3DB18970BEAA
Alcatel-Lucent 9500 MPR-A Release R5.0.0 Software
Electronic Delivery kit
3DB18970BEBA
For ETSI market
9500 MPR 5.0.0 Hybrid OS 3DB18969AEAA
9500 MPR 5.0.0 Packet OS 3DB18970AEAA
TCO SW Suite R5.0 3DB18971AEAA
9500 MPR R5.0.0 MIB 3DB18896EAAA
Software Version
Windows XP
(1)
Professional Ed. SP3 (32 bit only)
Windows 7
(1)
Premium (32/64 bit)
Java JRE Version 7, Update 17, 32 bit only (included with 9500 MPR
software)
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.41
Release Notice
Software compatibility
This section describes 9500 MPR software compatibility. Contact your
Alcatel-Lucent Technical Support Representative for assistance before planning or
performing an upgrade.
See Table 7 for migration paths.
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
This section provides an overview of the software installation requirements. See the
9500 MPR-A Software Installation and Upgrade Guide (3DB19083AAAARJZZA)
or the 9500 MPR-E User Guide (3DB19901ADAA) for the procedure.
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 R5.0.0 CT application installed
administrator ID and password to log in to each 9500 MPR shelf
IP Address or host name of each 9500 MPR shelf
9500 MPR System with current equipment as described in the 9500 MPR Release
Notice (this document)
a Core-E card (CSM) equipped with a Compact Flash card
Software components
The delivery for R5.0.0 contains the software elements described in Tables 5 and 6.
Table 5 R5.0.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 V05.00.0V
MPT SW V10.11.09
MCT SWP V08.09.01
Release Notice
Table 6 R5.0.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
TCO SW Suite 5.0.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 2), 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.
Software component Version
MSS-4/MSS-8 SubRelease version 5.00.0G
EC V16.23.03
TCO Suite V5.0
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.
Release Notice
Figure 2 Advanced Install Settings screen
A list of supported Operating systems and browsers can be found in Table 4.
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 an Ethernet interface and the capability to tag VLANs. See
the 9500 MPR R5.0.0 User Guide (3DB19901ADAA).
Upgrade paths
Table 7 shows the upgrade paths to Release 5.0.0.
Table 7 Upgrade paths to Release 5.0.0
Source
release
(ANSI
market)
Source
release
(ETSI
market)
Destination
release
Possible (Y/N)? Notes
3.0.0 3.0.0 5.0.0 N Must upgrade to 3.3.0 and then to 3.4.0 first
3.1.0 3.1.0 5.0.0 N Must upgrade to 3.3.0 and then to 3.4.0 first
3.2.0 3.2.0 5.0.0 N Must upgrade to 3.4.0 first
3.3.0 3.3.0 5.0.0 N Must upgrade to 3.4.0 first
3.4.0 3.4.0
3.4.0 ICS02
5.0.0 Y
4.0.0
4.0.0 ICS02
4.0.0 5.0.0 Y
(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 (MSS-4/8).
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.
Traffic impact during the SWP activation
Traffic impact varies by configuration; from R3.4.0/R4.0.0/R4.1.0/R4.2.0 to R5.0.0:
with ODU300: measured on DS1/E1 interfaces, there are 20/25 seconds of traffic
impact immediately after SWP activation.
with MPT-xC connected to MPT Access unit: measured on E1 interfaces, there
are 50/180 seconds of traffic impact immediately after SWP activation.
with MPT-xC connected to MSS-1: measured on E1 interfaces, there are around
40 seconds of traffic impact immediately after SWP activation.
with MSS-1c: traffic impact due to software migration is around 580 seconds.
with MPR-e: traffic impact due to software migration is around 130 seconds.
4.1.0
4.1.0 ICS04
4.1.0
4.1.0 ICS02
4.1.0 ICS04
5.0.0 Y
4.2.0 4.2.0 5.0.0 Y
Source
release
(ANSI
market)
Source
release
(ETSI
market)
Destination
release
Possible (Y/N)? Notes
(2 of 2)
Caution Perform a database backup before you start an upgrade.
Caution This upgrade procedure will cause traffic and
management interruption during the activation of the R5.0.0 software.
Caution Once the R5.0.0 release software has been activated, the
R5.0.0 CT must be used to manage the NE.
Before the R5.0.0 CT can be used, any FTP or SFTP servers should
be turned off. The R5.0.0 software will manage the servers.
Release Notice
Third-party software notes
Table 8 lists the Non-Alcatel-Lucent Owned Software (NAOS) items that are
included as part of this release.
Table 8 NAOS software included with 9500 MPR R5.0.0 CT software image
Release content
This section provides information about the content of the 9500 MPR release R5.0.0.
Implemented features
The 9500 MPR R5.0.0 includes the features described in New release capabilities.
Application notes
This section defines the usage notes that should be followed during system
management activities.
The 9500 MPR can accept a license key of up to 24 radio directions, however,
only 18 have been validated.
When the 9500 MPR is used with other equipment, the OSPF interface
parameters of the equipment must be the same as those of the related TMN
interface on the 9500 MPR. The 9500 MPR OSPF parameters are:
Hello Interval: 10 seconds
Router Dead Interval: 40 seconds
Retransmit Interval: 5 seconds
Interface Transit Delay: 1 second
MTU: 1500 bytes
ANSI market only: DS3 functionality is limited to support of a maximum of five
additional DS1 connections on any single radio link containing a DS3 connection.
More than five DS1 connections can be added to separate links that do not contain
DS3 connections.
If using the Alarm Monitor via the Web interface, ensure that the proxy is
disabled in your browser application.
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 "V040100", corresponding to version V4.1.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.
NAOS item code NAOS item description
Version 6 update 33
Minimum version 7, update 17, 32 bit only
Java JRE
Release Notice
User-defined site names (radio direction label) must not contain the following
characters: space, &, /, \,:, *,?, <, >, and |. Local language characters are also not
allowed.
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.
For each N x (1+x) where (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 shall be
provisioned as follows.
No radio port can have PPP RF enabled.
The LinkID must be enabled for all the port members of the configuration (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 configuration)
shall have PPP RF enabled and optionally the LinkID provisioned, but the ports
must have a different LINKGRP (for example, 3,...,9).
When using the Packet Throughput booster with the MPT-HL in a 40MHz at
either 128QAM or 256QAM, if all the packet size are 64 bytes long, the
maximum throughput that can be achieved is 640Mbs.
Closed issues
Table 9 describes the closed issues.
Table 9 Closed issues in R5.0.0
Item Description
ALL systems
Upgrade of a remote NE to a higher
modulation scheme
In case of upgrade via Craft Terminal of a remote MPT-xC ODU to a new
modulation scheme (e.g. from 4QAM to 256 QAM), if the current TX Power
is out of range for the new modulation scheme, the remote NE mutes its
transmission.
(1 of 2)
Release Notice
Usage notes
Table 10 describes the usage notes for this release. Usage notes supplement or clarify
information in the documentation. Where available, workarounds have been
provided.
Table 10 Usage notes for R5.0.0
IPv6: need to use FTP/SFTP servers FTP/SFTP servers libraries (by Apache foundation) need JRE7 to run correctly
on IPv6 Windows stack.
This is due to Java 7 improvements about IPv6, not back-ported on Java 6.
The proposal is to use third party FTP/SFTP servers to have the related
services available in IPv6.
SNMPv3, ATPC, and Operator profile In SNMPv3 mode, it is not possible via the Operator profile to enable ATPC.
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.
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.
CLA reset command should be
automatically shown when CLA criteria is
active
When a CLA failure is latched on a radio facility, a "CLA reset" option is added
to the operator switch command drop list. This is not obvious unless you have
seen it before or click on the drop list. The option should be automatically
shown as the drop list selection when the CLA criteria is active. The operator
can then see the option and apply it if desired.
HQAM: inconsistent CLA behavior for
TPS/EPS between main and spare
There are several inconsistent behaviors in the CLA algorithm when using AM
when TPS and EPS must switch together:
A CLA failure status is generated for both EPS and TPS when the failure is
on main but is only generated for TPS when failure is on spare. Failure
should apply to both since both were switched due to CLA fault.
A manual switch command set on spare before spare is failed is cleared
on TPS but not on EPS. The command on main is cleared for both TPS and
EPS when main is failed.
CLA alarm is only generated for spare TPS.
ANSI ODU300 CLA Failure not declared on
EPS Ch 0
HSB Protection Restoration Criteria in Not Revertive Mode to set the Spare
channel Status in Active without any Forced command. Since in ACM
Equipment Protection is in tracking with HSB also this one has Spare channel
active. Get Tx Mute active or decrease rotary attenuator with PTx unbalanced
to have both remote channel in Dem Fail and Local Ch0 with CLA Alarm.
Radio capacity value The Current Configuration View may not show the correct radio capacity.
Item Description
(2 of 2)
Item Description
ALL systems
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.
(1 of 9)
Release Notice
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 6u33 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: Use Internet Explorer or Firefox to install.
Java 6u33 plugin The latest versions of Firefox and Chrome do not enable Java 6u33 by default,
causing installation issues from the CD image.
Work around: In Firefox, manually go to add-ons and enable the 6u33 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.
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
ETSI market only
XPIC configuration for MPT-HC
On some occasions XPIC cannot be configured if the MPT-HC is not physically
present.
Workaround: Ensure that the MPT-HCs are present when configuring for XPIC.
SFP remote inventory On rare occasions the SFP Remote Inventory cannot be read if the SFP is
removed and inserted.
Workaround: None
Migration in Ring configuration If the 9500 MPR is configured in a Ring configuration, using the MPR
MultiService Ring feature, prior to upgrading to R5.0.0, take care to follow the
instructions on the migration process, otherwise severe traffic outage will
occur.
See the customer documentation for the upgrade procedure.
System reset during refresh of a radio
screen
In some cases when doing a refresh of the radio screen in the JUSM, the system
may go through a warm start.
Workaround: None
SDH Loopbacks Active loopbacks on an OC-3 or STM-1 remain active after the OC-3/STM-1 has
been disabled.
Workaround: Verify that loopbacks have been deactivated before disabling the
OC-3/STM-1.
Item Description
(2 of 9)
Release Notice
JUSM crash after IPv6 stack activation Occasionally the JUSM will automatically close after the IPv6 feature is
enabled.
Workaround: Restart the JUSM.
Undeleted cross-connection prevents a
new connection
On rare occasions after deleting a TDM cross-connection, the user may not be
able to create a new cross-connection with the same port.
Workaround: Disable and re-enable the TDM port.
ANSI market only:
Unidirectional fiber failure does not
trigger EPS switchover
When using Optical SFP with the MPT-HL in 1+1 configuration, a uni-directional
fiber failure will not cause an EPS switch.
Workaround: None
Limitation on ECFM Loopback and
Linktrace tools with mixed ring
When the 9500 MPR is configured in a mixed fiber-microwave Ring, Loopback
and Linktrace tools are not supported when the entity under monitoring is a
TDM flow.
Workaround: None
Ring: wrong status reported with SFP Rx
failure
After a uni-directional failure on optical Ethernet interface the wrong
reporting of the Ring Nodes status may occur for less than 5 seconds.
Workaround: None
Tx field of MD300 panel Sometimes the Tx Freq field of the MD300 panel is editable for an ODU300 when
the radio is involved in a Radio Layer 2 LAG.
Workaround: Refresh radio setting screen. If the user tries to edit, the action
is denied.
Message not reported by a MIB Restore
operation when another restore is
blocked
Users may receive the error message Generic Fault when the configuration
of the backup parameters fails. This is due to a backup procedure failure
before activation.
Workaround: Restart the 9500 MPR.
LAG panel continuous refresh When the 9500 MPR is configured with LAG and a fast flat fading occurs (speed
> 30dB/s) if the LAG screen is open at the time the LAG screen will become
unusable.
Workaround: Close the JUSM and restart after the fade has cleared.
EAS segregation in Ring If ports are segregated on the EAS before being configured with Layer 1 LAG in
a Ring configuration, the segregation is not automatically removed as required.
Workaround: Ensure the ports are not segregated before provisioning for LAG
Ring or power cycle the EAS cards.
ANSI market only:
WTPMS and analog PM on MPT-HL during
migration
If the radio PM is already enabled on the MPT-HL prior to upgrading to R5.0.0,
after the upgrade it will not be possible to retrieve the hop PM data.
Workaround: Manually restart the PM on the MPT-HL.
EAS firmware download Module firmware download could take up to 15 minutes when the 9500 MPR has
Core protection enabled.
Workaround: When upgrading do not take any action on the modules until the
firmware download warning alarm has cleared.
Alarm clearing Occasionally alarms may show up in the global alarm log when the alarm profile
is set to no radio alarms.
Workaround: None.
TDM flow deletion and UAT alarm If a TDM flow is deleted while PM is enabled, if a UAT alarm is raised against
that TDM flow, the UAT alarm will still appear.
Workaround: Create the TDM flow, then disable the PM and then delete the
TDM flow.
Default Ethernet PM value in WTPMS In the Ethernet statistics view of the WTPMS tool, if the duration is 0 hours and
x minutes, after navigating away from this view, the duration will change to 1
hour instead of 0.
Workaround: None
Item Description
(3 of 9)
Release Notice
NEtO R5.0.0 discovery doesnt work if
started after NEtO R4.2.0
If older versions of the NEtO are running and the NEtO is started for R5.0.0,
discovery will not work correctly.
Workaround: Close all instances of older NEtOs before starting the NEtO for
R5.0.0.
SW Download failure in SFTP mode In rare cases if a software download fails a warm start of the Core-E will occur.
Workaround: after the Core-E recovers, restart the 9500 MPR again and try
another software download.
RMI registry and FTP/SFTP servers must
be closed before launching NEtO
Before launching the R5.0.0 NEtO on a PC where a previous NEtO release
(R4.2.0 or earlier) was running, open Task Manager and close the RMI registry
process and any running Java process related to FTP or SFTP server.
FTP/SFTP server starts through NEtO
server manager when third party server
is in use
If a third party FTP or SFTP server is running, the user can turn on the FTP or
SFTP server using NEtO server manager. No error message appears, but the
third party server remains on and in use. The NEtO server manager does not
control the third party server.
Workaround: close all FTP and SFTP servers before using the R5.0.0 NEtO.
ANSI market only:
JUSM radio screen for UU6 GHz MPT-HL
In some cases the JUSM radio screen does not update the current TX
modulation.
Workaround: Manually refresh the screen.
Configuration of Port#4 for TMN_In_Band In the very specific case of the following sequence of operations:
configure MSS-1 Port#4 (or MSS-4/8 Core Port#4) as dedicated to TMN
configure Port#4 as Ethernet traffic
then add a TMN_In_Band traffic to Port#4
The TMN_In_Band doesnt work.
Workaround: you can exit from this condition with power cycle of the Network
Element.
Upgrade to R4.2.0 R4.1.0 to enable IPv6 When upgrading a link from R4.0.0 or earlier to R4.2.0 or R4.1.0 to enable IPv6,
a precondition for the successful completion of the upgrade to IPv6 is that both
side of the links run the same SW version greater or equal to R4.1.0. If this is
not the case, a preliminary upgrade for both sides of the link to a Release
allowing activation of the IPv6 stack is mandatory (R4.1.0 or 4.2.0). After that,
to maintain visibility, update to IPv6 first the far end and then the near end.
ANSI market only:
Excessive environmental temperature
alarm on MPT-HL after ISU from R4.0.0
After an upgrade to R4.2.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.
If the 9500 MPR is configured for use with IPv6, it is highly recommended that
Windows 7 is used instead of Windows XP.
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.
Item Description
(4 of 9)
Release Notice
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.0 and 4.2.0 L2 Ethernet LAG and 802.1ad are not
supported simultaneously.
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 ' "" :
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.
SW activation of 3.x load The 9500 MPR R4.2.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
Item Description
(5 of 9)
Release Notice
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
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
ANSI market only:
DS3 loopback
DS3 traffic may take a traffic hit during a system reset if a DS3 loopback is
enabled.
Workaround: Disable loopbacks before doing a system reset.
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.
Item Description
(6 of 9)
Release Notice
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
SW upgrade from R4.0.0 to R4.2.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.2.0 using the MPTACC After upgrading to R4.2.0 using the MPTACC and then migrating to L1LAG on
EAS, the MPT-HC/9558HC 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.
Item Description
(7 of 9)
Release Notice
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.
ANSI market only:
DS1 and DS3 switch times within a LAG
Group
DS1 and DS3 switch times within a LAG Group may exceed 50ms.
Workaround: None
ANSI market only:
HSB or EPS switch commands
When using Layer 1 LAG and MPT-HL in 1+1 configuration manual HSB or EPS
switch commands may take longer than when not in a LAG Group.
Workaround: Adjust the Wait To Restore timer to something lower than 1
second.
ANSI market only:
DEGRADE alarm
When in a Layer 1 LAG configuration with 1+1 MPT-HL, when both the Main and
Spare SFP are unplugged, if the Spare is plugged back in first, the DEGRADE
alarm takes 8 seconds to clear after the RUM on the spare SFP is cleared.
Workaround: Wait 8 seconds or plug Main SFP back in first
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.
ANSI market only:
Upgrade from previous releases to
R3.4.0
Upgrade from previous releases to R3.4.0 with DS1 traffic will have at least a
2 minute outage.
Item Description
(8 of 9)
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.
MSS-1c
Accidental connection with MPT-xC with
XPIC plug-in
The configuration where MPT-xC with XPIC plug-in are connected to the MSS-1c
is not allowed by MPR Releases. If nevertheless this forbidden connection is
made (e.g. by mistake) the MPT-xC enters into an incorrect state.
Workaround: a switch on of the MPT-xC either in split mount configuration
with MSS-1/4/8 or in MPR-e standalone configuration (MPR-e powering
separate from MPR-e data) will allow the MPT-xC to exit the incorrect state
mentioned above.
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
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
(9 of 9)
Release Notice
Technical support
Use Procedure 2 to find the contact information for technical assistance for a country.
Procedure 2 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 3 to download customer documentation from the OLCS site.
Procedure 3 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 11 lists the 9500 MPR acronyms that are used in this document, and their
expansions.
Table 11 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
ERPS Ethernet Ring Protection Switching
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
(1 of 2)
Release Notice
PDH Plesiochronous Digital Hierarchy
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
WTR Wait To Restore
XPIC Cross Polarization Interference Cancellation
Term Description
(2 of 2)
Release Notice
Alcatel-Lucent 9500 MPR R5.0.0 August 2013 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.
Note Radio transmitted/Received Power statistics are not
supported by 1350 OMS.
A. MPR-e and MSS-1c SNMP management
A-2 August 2013 Alcatel-Lucent 9500 MPR R5.0.0
Release Notice
Table A-1 Traffic Ethernet port counters [MPR-e]
A.3 Radio QoS counters [MPR-e/MSS-1c]
Table A-2 shows the Radio QoS counters for MPR-e and MSS-1c.
Ethernet counter Ingress counter Egress counter
For the Traffic Ethernet port
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
Note Traffic Ethernet port counters are not supported by 1350
OMS.
Release Notice
Table A-2 Radio Qos counters [MPR-e/MSS-1c]
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
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
Note Radio QoS counters are not supported by 1350 OMS.
Release Notice
A.4 Radio PM G.826: current and historical data [MPR-e/MSS-
1c]
Table A-3 shows the Radio PM G.826 counters (current and historical data) for
MPR-e and MSS-1c.
Table A-3 Radio PM G.826: current and historical data
A.5 AM performance monitoring [MPR-e/MSS-1c]
Table A-4 shows the Adaptive Modulation counters (current and historical data) for
MPR-e and MSS-1c.
Table A-4 AM performance monitoring counters
A.6 Modem measurements [MPR-e/MSS-1c]
Table A-5 shows the modem data measurements for MPR-e and MSS-1c.
Description Counters
Radio PM ES Yes
Radio PM SES Yes
Radio PM BBE Yes
Radio PM UAS Yes
Note Radio PM G.826 counters are not supported by 1350 OMS.
QPSK Yes
8 PSK Yes
16 QAM Yes
32 QAM Yes
64 QAM Yes
128 QAM Yes
264 QAM Yes
Release Notice
Table A-5 Modem measurements
Near end modulation Yes
Near end MSE Yes
Far end modulation Yes
Far end MSE Yes
Release Notice
Alcatel-Lucent 9500 MPR R5.0.0 August 2013 B-1
Release Notice
B. Previous release capabilities
B.1 Capabilities in R4.2.0
The features described below are introduced in the 9500 MPR R4.2.0.
Legend:
[MSS-4/8]the feature applies to the MSS-4/8 system only
[MSS-1:]:the feature applies to the MSS-1 system only
In Service software upgrade from 9500 MPR R3.4.0 to R4.2.0
1+1 on Core [MSS-4/8]
MSS-1 1+1 configuration [MSS-1]
MSS Housekeeping [MSS-1/4/8]
100 BaseT interface to MPR-e [MPR-e]
For ANSI market: 1+0 MPT-HL Support on Core [MSS-4/8]
For ANSI market: 1+0 MPT-HL Support on the MSS-1 [MSS-1]
1+1 on Core [MSS-4/8]
Release 4.2.0 introduces the support of 1+1 configuration on Core; up to 3x(1+1) is
supported. All configurations of 1+1 radio protections are available, for example,
HSB, SD, FD, and 2x(1+1)XPIC.
B-2 August 2013 Alcatel-Lucent 9500 MPR R5.0.0
Release Notice
Electrical and Optical connections are supported.
Protected and unprotected MPTs can be connected on one Core-E board at the same
time.
If Core-E protection is in use, MPTs directly connected to the Core board is not
supported.
MSS-1 1+1 configuration [MSS-1]
Release 4.2.0 introduces 1+1 functionalities on the MSS-1 via software upgrade; up
to 3x(1+1) per MSS-1 is supported. The 1+1 feature level on the MSS-1 is equivalent
to 1+1 on Core-E described in 1+1 on Core [MSS-4/8].
MSS Housekeeping [MSS-1/4/8]
Release 4.2.0 introduces the following through a software upgrade:
housekeeping management on MSS-1 (four inputs and three outputs)
four housekeeping inputs on the existing fan alarm card for MSS-8
Table B-1 describes the housekeeping options for MSS basebands.
Table B-1 MSS housekeeping
100 BaseT interface to MPR-e [MPR-e]
100 BaseT interface is supported by the MPR-e. Note that:
radio capacity should not exceed 100 Mbit/second
autoneg should be enabled at the two ends, with one of the two pairs advertizing
100Mb/s
For ANSI market: 1+0 MPT-HL Support on Core [MSS-4/8]
The 9500 MPR R4.2.0 adds support of the MPT-HL connected directly to the SFP
ports on the Core-E Card. Up to two MPT-HL can be supported using the Core-E
card. When connecting the MPT-HL directly to the Core-E card 1+0 configuration
is allowed. In this configuration, Core-E protection is not supported. All other
Ethernet ports may be used for user traffic or MPT-HC connections.
Card or shelf HK input (to MPR from
an external device)
MPR internal alarm
towards external device
HK output (from MPR to
external device)
AUX card
(MSS-4/8)
Supported (6 HK in) Not supported Supported (7 HK out)
Fan alarm
card (MSS-8)
Supported (4 HK in) Supported (3 alarms;
Major, Minor, Summary)
Not supported
MSS-1 Supported (4 HK in) Supported (3 alarms;
Major, Minor, Summary)
Not supported
Release Notice
For ANSI market: 1+0 MPT-HL Support on the MSS-1 [MSS-1]
The 9500 MPR R4.2.0 adds support of the MPT-HL connected directly to the SFP
ports on the MSS-1. Up to two MPT-HL can be supported using the MSS-1. When
connecting the MPT-HL to the MSS-1 card 1+0 configuration is allowed. All other
Ethernet ports may be used for user traffic or MPT-HC connections.
The features described below are introduced in the 9500 MPR R4.1.0:
Legend:
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
Release Notice
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.
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.
Release Notice
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.
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.
Release Notice
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.
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.
Release Notice
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.
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.
Release Notice
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.
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).
Release Notice
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
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.
Release Notice
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
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.
Release Notice
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.
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/9558HC 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
Release Notice
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.
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/9558HC.
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/9558HC) 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.
Release Notice
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.
7705 SAR + MPR-e Single NE
The 7705 SAR Release 6.0 R1 and 9500 MPR R4.2.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/
9958HC 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.
Release Notice
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
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.2.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 in R4.1.0
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.
Release Notice
Adaptive modulation support for ODU300
In R4.1.0, Adaptive modulation support for the ODU300 has been extended to
support modulation schemes up to 256QAM. The extended ODU300 Adaptive
modulation feature is enabled via a license key that can be applied while the
9500 MPR is in service. The extended ODU300 only supports 30MHz channel
sizes.
With the extended ODU300 AM feature, the customer can now choose either the
worst receiver (according to MSE value) or the best receiver is drive the Adaptive
Modulation engine when in a 1+1 HSB configuration. Both transmitters are driven
either by the lowest MSE value or by the highest MSE value of the two remote
demodulators.
The changes in Adaptive Modulation are performed only step by step, not skipping
directly to the desired modulation in one pass, e.g., from 64 QAM to 128 QAM and
from 128 QAM to 256 QAM. It is not possible to pass in one step from 64 to 256
QAM.
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.
Legend:
[MSS4/8]the feature applies to the MSS4/8 system only
SNMPv3 support [MSS4/8]
Per-CoS rate Limiter [MSS-4/8]
User configurable label on traffic interfaces [MSS4/8]
ANSI market only: SNMP support for Ethernet counters [MPR-e/MSS-1c]
TMN in-band with L2 Ethernet LAG
ANSI market: OC-3 support [MSS-4/8]
MPR-e repeater back to back support [MPR-e]
Release Notice
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.
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.
Release Notice
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.
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.
Release Notice
The CT allows the Operator to configure a User Label on an interface of a PDH
peripheral.
The configuration is supported on E1, DS1 and DS3 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.
User Label length and the set of characters admitted are the same as those of Radio
Direction Label.
ANSI market only: SNMP support for Ethernet counters [MPR-e/MSS-
1c]
See Appendix A for details.
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.
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
ANSI market: OC-3 support [MSS-4/8]
The SDH card supports OC-3 interfaces.
Table B-2 shows the modem profiles that support OC-3.
Table B-2 Modem profiles supporting OC-3
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 The CT shows STM-1 for OC-3 interfaces.
MPT Type Preset/Adaptive Channel
Spacing
(MHz)
Modulation (QAM)
MPT-HC Preset 30 128
MPT-HL Preset 30 256
MPT-HL Adaptive 30 128 (ref)
MPT-HL Adaptive 30 256 (ref)
ODU300 Preset 30 128
ODU300 Preset 30 256 (high gain)
ODU300 Preset 40 32
ODU300 Preset 50 32
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:
[MSS4/8]the feature applies to the MSS4/8 system only
In service software upgrade from 9500 MPR R3.01.00 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]
ETSI market: 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]
Release Notice
TACACS+ [MSS-4/8]
P32E1DS1 unit performances [MSS-4/8]
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 Interfaces:
1+0 MPT-HL connected to EAS Plug-in SFP ports
1+1 MPT-HL connected to EAS Plug-in SFP ports
1+0 MPT-HC connected to EAS Plug-in SFP ports
The system prevents the configuration of a mixed port membership comprising
MPT-HL and MPT-HC in the same group.
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.
Release Notice
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.
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.
Release Notice
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.
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
Protected Cross Plug-in LAG L1 [MPT-HL]
Figure B-7 shows an example of a protected cross plug-in LAG L1. In this scenario,
a Cross Plug-in LAG, composed of two 1+1 HSB/SD Protection Groups, is created
on NE A. On NE B, two Cross Plug-in LAGs are created to implement a radio
repeater configuration. Protection handles failures on the single radio hop belonging
to the 1+1 Group. From the LAG point of view, two MPTs in protection are seen as
a single radio interface. This means that the LAG capacity is reduced in case of
failure of a whole protection group.
Figure B-7 Protected Cross Plug-in LAG L1
Figures B-8 and B-9 show supported scenarios for Protected Cross Plug-in LAG L1.
Release Notice
Figure B-8 Supported scenario for Protected Cross Plug-in LAG L1
Figure B-9 Supported scenario for Protected Cross Plug-in LAG L1
Since 1+1 MPT-HC Protection Groups are not supported on EAS Plug-in, Protected
scenarios do not apply to MPT-HC Layer1 LAG.
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-10
illustrates Master ports in LAG L1.
Figure B-10 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-11 illustrates the configurations.
Release Notice
Figure B-11 Allowed configurations
Protected Radio LAG [MPT-HL]
Port Add and Remove operations can involve 1+1 Radio Protection Groups.
From the LAG Collector/Distributor perspective, the two MPTs in 1+1 configuration
are considered as a single radio direction. LAG Distributor excludes the protection
group from the traffic transmission/reception only in case of failure of the whole
protection group.
LAG Port Membership configuration involving protection groups shall follow the
procedures below:
1 Operator configures 1+1 Protection and then adds the protection group to the
LAG.
2 Operator removes the protection group from the LAG and then removes the 1+1
Protection.
3 The Operator adds the 1+1 Protection Group to the LAG, configuring the Main
MPT as member of the LAG.
The system prevents:
configuration of MPT 1+1 Protection between radios already part of a LAG
de-provisioning of MPT 1+1 Protection from a protection group already part of a
LAG
Port Provisioning Rules, defined for 1+0 configurations, also apply to 1+1 Protection
Groups.
For those rules and relevant Allowed Configuration tables, Main and Spare MPTs
are considered as normal 1+0 MPT provisioned in homologous Plug-in ports.
In other words, a LAG having 1+1 MPT as member represents a special case of a
Cross Plug-in LAG.
It is allowed the configuration of a mixed LAG Port Membership having both 1+0
and 1+1 Radio directions in the same group.
Release Notice
Port Provisioning Rules are still applicable considering the 1+1 Protection Group as
a pair of 1+0 MPT added to the LAG at once. Since 1+1 MPT-HC Protection Groups
are not supported on EAS Plug-in, protected scenarios do not apply to MPT-HC
Layer1 LAG.
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.
Adaptive Modulation can be added only if one modulation is allowed (i.e., only the
Reference Modulation Scheme selected in the Allowed Modulation); in this case It
is not allowed to add into the same LAG group a mix of Radio in Preset and Adaptive
Modulation.
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.
Service restrictions for the first port added to the LAG [MPT-HL]
For the first port (i.e., Master Port) added to the LAG, Service Restrictions described
above do not apply:
Cross-connections
VLANs
Port Segregations
TMN-RF and Synchronization settings involving the first interface added to the
LAG (that becomes the Master Port) are automatically re-provisioned on the LAG
entity.
Release Notice
This procedure triggers two consequent actions performed by the NE:
1 LAG Administrative State is set to Enabled.
2 ECT is automatically shut down.
This procedure involves a traffic impact.
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).
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.
Note This requirement is applicable to MPT-HL only. This
procedure is denied if the first port added to the LAG has more than
254 Cross-connections configured.
The addition of an MPT-HC to a LAG (either first port or not) shall
respect Service Restrictions requirement described previously.
Release Notice
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: The maximum recommended 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 may 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.
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
Release Notice
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.
1+1 FD to LAG conversion procedure [MPT-HL]
The Operator can substitute an existing 1+1 FD configuration with a LAG without
re-provisioning all the services. This procedure is performed by removing the 1+1
Protection and adding single radio links to the LAG.
In this procedure, Port Provisioning Rules shall be respected. Cross-connections,
VLANs, Segregations, TMN-RF and Synchronization settings are re-provisioned on
the LAG only if the former-Main MPT (that shall be the first port added) is the
Master Port of the LAG.
In all the other conditions (i.e., the interface added is not the first), the addition of the
MPT is forbidden.
This procedure involves a traffic impact.
This procedure is applicable to MPT-HL only.
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.
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.
Release Notice
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.
In case of LAG comprising 1+1 Protection Groups, MPTs in Stand-by EPS status
shall not be considered as a valid synchronization reference.
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.
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.
Release Notice
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.
From a LAG Size perspective, Main and Spare MPTs belonging to a 1+1 Protection
Group are counted as one link. In this scenario, the LAG Degrade alarm shall be
asserted in case of failure of the whole Protection Group and not of the single channel
of the 1+1 direction.
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
These defects are used as switching criteria before the defects correlation and defect
persistency alarm processing actions take place.
In the case of Layer1 LAG with MPT-HL, since the auto-negotiation is disabled on
optical Ethernet connection to MPT, the Ethernet link LOS defect is split in the
following criteria:
Ethernet LOS (MSS-MPT link) detected on MSS side
Ethernet LOS (MSS-MPT link) detected on MPT side
Release Notice
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
LOF of aggregate signal radio side
Link Identifier Mismatch (LIM)
HBER
For MPT-HL, the following additional defects shall be used as RDI generation
criteria:
Ethernet LOS (MSS-MPT link) detected on MSS side
Ethernet LOS (MSS-MPT link) detected on MPT side
MPP Timeout (no reception of MPP frames) detected MPT side
Since MPP frames are generated by MPT-HL SW, MPP Timeout detected MSS
side shall not be taken into account. This is necessary to avoid any traffic impact
during MPT SW restart.
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.
From a LAG perspective, a 1+1 Protection Group is considered as failed only if both
Main and Spare radio channels are not available. For this reason, WTR shall be
applied only to restorations of 1+1 group failure conditions.
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.
Release Notice
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 DS3 TDM2TDM/TDM2ETH profiles
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
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
from LAG L1 to DS3 TDM2TDM/TDM2ETH profiles
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
Release Notice
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
DS3 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.
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.
Release Notice
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.
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.
Release Notice
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.
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.
Release Notice
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.
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.
ETSI market: 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-12. The Main protection
resource is the Optical Fiber, while the Spare protection resource is the Microwave
link.
Release Notice
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.
Figure B-12 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.
Release Notice
The Fiber-Microwave Protection can also be implemented on Tail links having one
MPR NE working as Node, as illustrated in Figure B-13.
Figure B-13 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.
P32E1DS1 unit performances [MSS-4/8]
Selecting the P32E1DS1 unit, the Performance Monitoring (PM) gives indication on
the quality of the DS1 Tributaries, which have been configured as Unframed or
Framed SF or Framed ESF.
Two types of performances are available:
Incoming: performances detected at the input in Tx side;
Outgoing: performances detected at the output in Rx side.
The 9500 MPR is transparent regarding the DS1 stream. The Quality is performed in
accordance with G.826 and G.784. The performance reports are of 2 different types:
15 minutes;
24 hours.
Incoming
Displayed parameters
The displayed parameters are:
Time. It displays the time of the Performance Monitoring. This time changes after
the Auto Refresh;
Elapsed Time. It displays the elapsed time in the current interval of Performance
Monitoring;
Suppressed Intervals: number of intervals (reports) which are automatically
suppressed, because they don't have errors;
If an interval is suspected, it is highlighted in red. An interval is defined as Suspect,
if at least one of the following conditions occurs in the collection period:
the elapsed time deviates more than 10 seconds of the nominal time;
loss of the Performance Monitoring data in the equipment;
performance counters have been reset during the interval.
Release Notice
The displayed counters are:
BBE, Background Block Errors;
ES, Errored Second;
SES, Severely Errored Second;
UAS, Unavailable Second.
Outgoing
Displayed parameters
The displayed parameters are:
Time. It displays the time of the Performance Monitoring. This time changes after
the Auto Refresh;
Elapsed Time. It displays the elapsed time in the current interval of Performance
Monitoring;
Suppressed Intervals: number of intervals (reports) which are automatically
suppressed, because they don't have errors;
If an interval is suspected, it is highlighted in red. An interval is defined as Suspect,
if at least one of the following conditions occurs in the collection period:
the elapsed time deviates more than 10 seconds of the nominal time;
loss of the Performance Monitoring data in the equipment;
performance counters have been reset during the interval.
The displayed counters are:
BBE, Background Block Errors;
ES, Errored Second;
SES, Severely Errored Second;
UAS, Unavailable Second.
Release Notice
Alcatel-Lucent 9500 MPR R5.0.0 August 2013 C-1
Release Notice
C. Supported hardware
C.1 Supported hardware
No new hardware is added in R5.0.0.
Existing hardware
Tables C-1 to C-21 describe supported hardware from previous releases.
Table C-1 Existing MSS-4/8 shelf hardware in R5.0.0
Part number Circuit pack/module Description CLEI
3EM22715AA
3EM22715AB
3EM22715AC
3EM22715AD
3EM22715AE
MSS-8 (ANSI market only) MSS-8 shelf kit
3DB18485AB
3DB18485CA
3DB18485AA
MSS-8
MSS-8 Shelf
3EM24463AA MSS-4 (ANSI market only) MSS-4 shelf Kit
3DB18219AD
3DB18219AC
3DB18219AB
MSS-4 MSS-4 shelf
C-2 August 2013 Alcatel-Lucent 9500 MPR R5.0.0
Release Notice
Table C-2 Existing MSS-1 hardware in R5.0.0
Table C-3 9500 MPR peripheral cards (MSS-4/8 only)
Table C-4 Existing MSS-1c hardware in R5.0.0
3MU00109AA MSS-1 (ANSI market only) MSS-1 kit
3DB19015AA MSS-1 MSS-1 DRMVY10DRA
Product Part number
32E1/DS1 PDH peripheral
3DB18126AE 3DB18126AD
3DB18126AC
Modem300
3DB18136AE
3DB18136AD
3DB18136AC
Modem300 EN
3DB18538AC
3DB18538AB
3DB18538AA
MPT access plug-in 3DB18634AB
Auxiliary peripheral 3DB18236AB
ASAP peripheral 3DB18602AA
SDH access card 3DB18735AA
AWY access card 3DB18628AB
8 ports EAS card 3DB18206AC
Protected +24V DC converter kit 3DB18862AA
Unprotected +24V DC converter kit 3DB18863AA
Power injector card 3CC50120AA
Part number Circuit pack/module Description
3DB18613AA MSS-1c MSS-1c
3DB18613BA MSS-1c MSS-1c
3DB77002AA MSS-1c FAN MSS-1c FAN
Release Notice
Table C-5 9500 MPR-E supported flashcards (MSS-1/4/8 only, for ETSI market)
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
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
(1 of 2)
Release Notice
Table C-6 Supported SFP modules
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
Product Part number Where used
SFP 1000Base-LX Transceiver
3CC50168AAAA
3EM20277AB
Core-E card, MSS-1, MSS-1c, EAS,
MPT access card (indoor-outdoor
on SM fiber)
SFP 1000Base-SX Transceiver (850 nm)
3CC50167AAAA
3EM20277AA
Core-E card, MSS-1, MPT access
card, MSS-1c
EAS
SFP 1000Base-T Copper Transceiver
(1)
3CC50169AAAA
Core-E card, MSS-1, MSS-1c
EAS
SFP 1000Base-ZX
3CC50170AAAA
3EM20277AD
Core-E card, MSS-1
EAS
SFT 1000Base-BX10
3CC50183AAAA (1310nm)
3CC50184AAAA (1550nm)
Core-E card, MSS-1
(1 of 2)
License string Description Alcatel-Lucent part number
(2 of 2)
Release Notice
Note
(1)
Autonegotiation shall be disabled when copper SFP is used.
Table C-7 MPT-HL in R5.0.0, for ANSI market
SFP 1000Base-BX40
3CC50198AAAA (1310nm)
3CC50199AAAA (1550nm)
Core-E card, MSS-1
For ETSI market only
2E1 SFP
3DB78012AAAA
Core-E card, MSS-1
E3 SFP
1AB380750004
Core-E card, MSS-1
E0SDH SFP
1AB380750003
Core-E card, MSS-1
SDH electrical SFP 1AB210170001 SDH access card
SDH optical SFP, S.1.1 3CC50165AAAA SDH access card
SDH optical SFP, L.1.1 1AB194670005 SDH access card
CWDM-SFP-1470 3CC50201AGAA Core-E card, MSS-1
CWDM-SFP-1490 3CC50200AAAA Core-E card, MSS-1
CWDM-SFP-1510 3CC50201ABAA Core-E card, MSS-1
CWDM-SFP-1530 3CC50201ACAA Core-E card, MSS-1
CWDM-SFP-1550 3CC50201AAAA Core-E card, MSS-1
CWDM-SFP-1570 3CC50201ADAA Core-E card, MSS-1
CWDM-SFP-1590 3CC50201AEAA Core-E card, MSS-1
CWDM-SFP-1610 3CC50201AFAA Core-E card, MSS-1
Part number Description Frequency CLEI
3EM22617AA Transceiver Unit - L6/Unl 5.8 57256425 MHz CRTUAAXFAA
3EM22617AB Transceiver Unit - U6 6425-6930 MHz CRTUAAYFAA
3EM22617AE Transceiver Unit - UU6 6875-7125 MHz
3EM22617AC Transceiver Unit HP L6 57256425 MHz CRTUABLFAA
3EM22617AD Transceiver Unit HP U6 6425-6930 MHz CRTUABMFAA A
3EM23888AA Transceiver Unit 10.5G 10400-10700 MHz CRTUABPCAA
3EM23888AB Transceiver Unit 11G Tx(L) 10700-11200 MHz CRTUABRCAA
3EM23888AC Transceiver Unit 11G Tx(H) 11200-11700 MHz CRTUABSCAA
3EM24627AA Transceiver Unit 7/8 7.125-8.115
3EM24627AB Transceiver Unit 7/8 7.395-8.500
Product Part number Where used
(2 of 2)
Release Notice
Table C-8 MPT-HC/XP modules in R5.0.0
Table C-9 9558HC 5.8 GHz unlicensed in R5.0.0, for ANSI market
Table C-10 MPT-HC L6 GHz in R5.0.0
Table C-11 MPT-HC U6 GHz in R5.0.0
Table C-12 MPT-HC 6 GHz in R5.0.0
3DB20116BB
3DB20116BC
XPIC+RPS Module MPT-HC/XP XPIC+RPS Module
3DB20117BA RPS Module MPT-HC/XP RPS Module
Part number Description T/R Separation
3DB20913BA 5725.5-5785.5 MHz 64 MHz
3DB20914BA 5789.5-5849.5 MHz 64 MHz
3DB20441BA 5929 to 6050 MHz 252 MHz
3DB20442BA 6047.96 to 6168 MHz 252 MHz
3DB20443BA 6182 to 6302.04 MHz 252 MHz
3DB20444BA 6300 to 6420.04 MHz 252 MHz
3DB20367BA 6540 to 6610 MHz 160 MHz
3DB20434BA 6590 to 6660 MHz 160 MHz
3DB20435BA 6710 to 6780 MHz 160 MHz
3DB20436BA 6750 to 6820 MHz 160 MHz
3DB20462BA 6640 to 6710 MHz 160 MHz
3DB20463BA 6800 to 6870 MHz 160 MHz
3DB20437BA 6420 to 6600 MHz 340 MHz
3DB20438BA 6565 to 6720 MHz 340 MHz
(1 of 2)
Release Notice
Table C-13 MPT-HC 7/8 GHz in R5.0.0
3DB20439BA 6760 to 6940 MHz 340 MHz
3DB20440BA 6905 to 7060 MHz 340 MHz
3DB20464BA 6595 to 6775 MHz 340 MHz
3DB20465BA 6935 to 7115 MHz 340 MHz
3DB20454BC 7107 to 8377 MHz 175/300 MHz
3DB20456BC 7261 to 8496.114 MHz 175/300 MHz
3DB20371BA 10695 MHz to 10955 MHz 490/500 MHz
3DB20371BC 10695 to 10961 MHz For ANSI market: 490/500
MHz
For ETSI market:
490/500/530 MHz
3DB20547BC 11199 to 11485 MHz 490/500/530 MHz
3DB20546BC 10933 to 11200 MHz 490/500/530 MHz
3DB20548BC 11430 to 11705 MHz 490/500/530 MHz
3DB20373BA 14500 to 14724 MHz 475 MHz
3DB20423BA 14920 to 15144 MHz 475 MHz
(2 of 2)
Release Notice
Table C-18 MPT-XP L6 GHz in R5.0.0
Table C-19 MPT-XP U6 GHz in R5.0.0
Table C-20 MPT-XP 7 GHz in R5.0.0
3DB20432BA
3DB20432BC
17700 MHz to 18140 MHz 1560 MHz
3DB20433BA
3DB20433BC
19260 MHz to 19700 MHz 1560 MHz
3DB20760BA 5929.96 to 6168 MHz 252.04 MHz
3DB20764BA 6182 to 6420.04 MHz 252.04 MHz
3DB20763BA 6420 to 6775 MHz 160/340 MHz
3DB20764BA 6710 to 7115 MHz 160/340 MHz
3DB20771BA 7107 to 7714.5 MHz 175 MHz
3DB20772BA 7261 to 7911 MHz 175 MHz
Release Notice
Table C-21 MPT-XP 8 GHz in R5.0.0
Table C-22 MPT-HC/XP/9558HC external diplexers in R5.0.0
ODU300
For information about ODU300 hardware, see the customer documentation or
Release Notice for R4.2.0.
3DB20773BA 7725 to 8377 MHz 300 MHz
3DB20774BA 8025 to 8496.114 MHz 300 MHz
3DB20752BA
3DB20752BB
External diplexer for 5.8 GHz unlicensed 64 MHz
3DB20753BA
3DB20753BB
External diplexer for L6 GHz 252.04 MHz
3DB20756BA
3DB20756BC
External diplexer for L6 GHz 160 MHz
3DB20755BA
3DB20755BC
External diplexer for L6 GHz 340 MHz
3CC40072AC
3CC40072AD
External diplexer for 7 GHz 175 MHz
3CC40073AC
3CC40073AD
External diplexer for 8 GHz 300/310 MHz
Release Notice
Alcatel-Lucent 9500 MPR R5.0.0 August 2013 D-1
Release Notice
D. Closed issues in previous releases
D.1 Closed issues in R4.2.0
Table D-1 shows closed issues from R4.2.0.
Table D-1 Closed issues in R4.2.0
Item Description
ALL systems
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.
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
MPR-e standalone mode
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
(1 of 2)
D-2 August 2013 Alcatel-Lucent 9500 MPR R5.0.0
Release Notice
D.2 Closed issues in previous releases
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.
Item Description
(2 of 2)
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.
Item Description
ALL systems
(1 of 2)
Release Notice
For ANSI market only:
MPT-HL stuck in ICP after power cycle
Issue: On rare occasions after a power cycle of the MPT-HL, the MPT-HL could
get stuck in ICP alarm.
Workaround: Power cycle MPT-HL again.
MPT-HL: synch anomalous management
Issue: In the case where a 9500 MPR is configured with primary sync from a
MPT-HL and secondary sync off another MPT-HL, the 9500 MPR will report
Synchronization Signal Failure alarm on secondary synch source
downstream.
Workaround: Change the synchronization source:
another MPT-HL not in use as a sync source
a DS1, a 10M sync-in
or free run
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
Item Description
(2 of 2)
Item Description
MSS-4/8
Offline MPT-HL sends duplicate Ethernet
traffic when coming back to standby
Offline MPT-HL sends duplicate Ethernet traffic when coming back to
standby.
MPT-HL RSL History jumps at random to -
6 dBm or +/-25 dB from actual
MPT-HL RSL History jumps at random to -6 dBm or +/-25 dB from actual RSL.
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.
(1 of 2)
Release Notice
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.
ANSI market only:
Discarded Frames for Egress EthTraffic
port counter
Ethernet Traffic port counter incorrectly displays discarded frames. This
problem is present as soon as the flow is over 100Mb/s.
Workaround: mask the mask the flag from the 100B-T FIFO when operating in
1000B-T (MPT FPGA)"
Item Description
(2 of 2)
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.
For ETSI market only:
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.
For ETSI market only:
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.
(1 of 2)
Release Notice
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.
Restart the MPR-e or MSS-1c.
Item Description
(2 of 2)
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
2013 Alcatel-Lucent. All rights reserved.

M07cee 131220151044 Phpapp01

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

M07cee 131220151044 Phpapp01

Caricato da

Copyright:

Formati disponibili

Alcatel-Lucent 9500

MICROWAVE PACKET RADIO FOR ETSI AND ANSI | RELEASE 5.0.0

Potrebbero piacerti anche