3db19043aaaafmzza01_v1_9500 Mpr-e r4.1.0 Release Notice

5/20/2018 3db19043aaaafmzza01_v1_9500 Mpr-e r4.1.0 Release Notice

1

Alcatel-Lucent 9500MICROWAVE PACKET RADIO FOR ETSI | RELEASE 4.1.0R E L E A S E N O T I C E

3DB 19043 AAAA FMZZA Edition 01

Alcatel-Lucent ProprietaryThis document contains proprietary information of Alcatel-Lucent and is not to be disclosedor used except in accordance with applicable agreements.Copyright 2012 Alcatel-Lucent. All rights reserved.

R E L E A S E N O T I C E


2

When printed by Alcatel-Lucent, this document is printed on recycled paper.

Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is

subject to change without notice.

Alcatel, Lucent and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent. All other

trademarks are the property of their respective owners.

Copyright 2012 Alcatel-Lucent.

All rights reserved.

Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design

engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous

environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft

navigation or communication systems, air traffic control, direct life-support machines, or weapons

systems, in which the failure of products could lead directly to death, personal injury, or severe physical

or environmental damage. The customer hereby agrees that the use, sale, license or other distribution

of the products for any such application without the prior written consent of Alcatel-Lucent, shall be atthe 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 byAlcatel-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.


3

Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 iii


Release Notice

Contents

9500 MPR-E Release 4.1.0 Release Notice 1Summary ................................................................................................1

Safety information......................................................................................1

New release capabilities...............................................................................1

Provider Bridge QinQ 802.1ad [MSS-1/4/8] .........................................2

Global Configuration................................................................2

S-VLAN creation .....................................................................3

Member set and untagged set of a PNP..........................................3

S-VLAN removal......................................................................4

Equipment components de-provisioning.........................................4

S-VLAN ID 1 management ..........................................................4

Management of Provider Bridge Ports Port Type...............................4

PNP - S-VLAN TPID (Tag Protocol Identifier) ....................................4

PNP - Acceptable Frame Type.....................................................5

PNP - Port S-VLAN ID................................................................5

PNP - Priority and Drop Eligible...................................................5

PNP - Port Priority ..................................................................6

PNP - Ingress Filtering ..............................................................6

PNP - PCP and DEI fields of S-VLAN Tag .........................................6

PNP - S-VLAN Rate Limiter.........................................................6

PNP - Per-CoS Rate Limiter ........................................................7

Customer Network Port Parameters..............................................7

Bridge Mode Configuration.........................................................8C-VLAN Translation .................................................................9

MultiService Ring Protection 8032 v2 ............................................9

Ethernet user port LAG.............................................................9

Packet throughput booster (header compression) [ALL] ........................ 10

7705 SAR + MPR-e [MPR-e]........................................................... 11

7705 SAR + MPR-e Separate NEs................................................. 11

7705 SAR + MPR-e Single NE ..................................................... 12


4

Contents

iv November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0

Edition 01 3DB 19043 AAAA FMZZA

Release Notice

IPv6 and OSPFv3 [MSS-1/4/8] ....................................................... 12

TACACS+ enhancements [MSS-1/4/8] .............................................. 13

Features significantly changed ..................................................................... 13

STM-1 channelized support of L2 LAG crossconnections ........................ 13

Transmitter mute function [MSS-1/4/8]........................................... 13

Retained capabilities................................................................................. 14Discontinued capabilities ............................................................................ 14

Documentation delivery ............................................................................. 15

Software and license delivery ...................................................................... 16

Software compatibility............................................................................... 17

Backwards compatibility and migration ........................................... 17

Downloading the software ........................................................... 17

Installing the software ............................................................... 18

Software components............................................................. 18

TCO suite and MCT system requirements...................................... 19

Upgrade paths ..................................................................... 20

Precautions and recommendations............................................. 21

Traffic impact during the SWP activation ..................................... 22

Third-party software notes .......................................................... 22Release content ....................................................................................... 24

Implemented features................................................................ 24

Closed issues ........................................................................... 24

Usage notes ............................................................................ 24

Technical support..................................................................................... 32

Customer documentation............................................................................ 32

Accessing customer documentation................................................ 32

Providing feedback about customer documentation ............................ 33

Glossary .............................................................................................. 34

A. MPR-e and MSS-1c SNMP management A-1A.1 MPR-e and MSS-1c SNMP management............................................... A-1

A.2 Traffic Ethernet port counters [MPR-e].............................................. A-1

A.3 Radio QoS counters [MPR-e/MSS-1c] ................................................. A-2

B. Previous release capabilities B-1B.1 Capabilities in R4.0.0................................................................... B-1

SNMPv3 support [MSS4/8]........................................................... B-1

Per-CoS rate Limiter [MSS-4/8] .................................................... B-2

User configurable label on traffic interfaces [MSS4/8] ........................ B-3

TMN in-band with L2 Ethernet LAG................................................ B-4

MPR-e repeater back to back support [MPR-e] .................................. B-4

B.2 Capabilities in R3.4.0................................................................... B-5Multichannel Link Aggregation L1 [MSS-4/8]..................................... B-6

Supported configurations ....................................................... B-6

Description of supported scenarios............................................ B-6

LAG L1 configuration ............................................................ B-8

LAG L1 configuration modification ............................................ B-9

LAG L1 activation and deactivation ........................................... B-9

LAG L1 deletion..................................................................B-10

Port Add and Remove operations .............................................B-10


5

Contents

Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 v


Release Notice

Master port definition ..........................................................B-10

Port provisioning rules..........................................................B-11

Allowed configurations .........................................................B-11

Adaptive Modulation and modem profiles...................................B-12

Service restrictions .............................................................B-12

User ports and radio interfaces ...............................................B-12Radio QoS configuration........................................................B-13

Supported services and configurations.......................................B-13

Maximum throughput ...........................................................B-13

LAG rate ..........................................................................B-13

Maximum Ethernet frame length .............................................B-13

Admission control ...............................................................B-14

Maximum number of cross-connections......................................B-14

Segregations .....................................................................B-14

Synchronization..................................................................B-14

SSM ................................................................................B-15

TMN-RF configuration...........................................................B-15

LAG alarms .......................................................................B-16

Switching criteria ...............................................................B-16Remote defect indication......................................................B-16

Wait to restore ..................................................................B-17

MPT connected to EAS card [MSS-4/8]...........................................B-18

Port rate limiter [MSS-4/8] ........................................................B-19

Storm control [MSS-4/8] ...........................................................B-19

Per VLAN rate limiter [MSS-4/8] ..................................................B-20

VLAN swap [MSS-4/8] ...............................................................B-21

Additional modem profiles [MSS-4/8 and MPR-e] ..............................B-22

Fiber/microwave protection [MSS-4/8]..........................................B-22

MPT-MC: new modem profiles support, up to 256QAM/56 MHz [ALL].......B-24

TACACS+ [MSS-4/8] .................................................................B-25

Server Support ...................................................................B-25

Authentication/Authorization.................................................B-25

Server Monitoring ...............................................................B-26

Server Validation ................................................................B-26

B.3 Capabilities in R3.3.0..................................................................B-26

RING support with MPT-MC/HC [MSS-4/8].......................................B-26

XPIC support over MPR-e [MPR-e].................................................B-27

XPIC and Adaptive Modulation [MSS-4/8, MPR-e] ..............................B-27

XPIC and ATPC [MSS-4/8, MPR-e].................................................B-27

1+1 radio protection on MPT-HC without tight cable [MSS4/8] ..............B-27

Improvement of MSS-1c MCT [MSS-1c] ...........................................B-28

2x(1+0) MSS-1c repeater configuration [MSS-1c] ...............................B-28

Troubleshooting tool [MSS4/8] ....................................................B-29

Separate alarms for battery A and battery B [MSS-8] .........................B-29B.4 Capabilities in R3.2.0..................................................................B-30

Quality of Service ...................................................................B-30

Forwarding class mapping......................................................B-31

QoS scheduler setting ..........................................................B-33

Queue size setting ..............................................................B-33

Link aggregation managed through CT/NMS ................................B-35


6

Contents

vi November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0


Release Notice

C. Supported hardware C-1C.1 Supported hardware .................................................................... C-1

Existing hardware .................................................................... C-1

MPT supported codes ............................................................ C-5

D. Closed issues in previous releases D-1D.1 Closed issues in previous releases .................................................... D-1

E. VLAN values for STM-1 flows E-1E.1 VLAN values tables...................................................................... E-1

F. Open issues in R3.2.0 and earlier F-1F.1 Open issues in R3.2.0 and earlier..................................................... F-1

Usage notes ........................................................................... F-1

Open issues............................................................................ F-7


7

Alcatel-Lucent 9500 MPR-E R4.1.0 November 2012 1


Release Notice

9500 MPR-E Release 4.1.0 Release Notice

Summary

The 9500 MPR R4.1.0 addresses both the ETSI and ANSI markets. This documentdescribes and provides guidelines for the 9500 MPR ETSI-related features. Refer to9500 MPR-A Release Noticefor ANSI-related information.

The 9500 MPR-E designates ETSI software. The 9500 MPR-e designates theMPT-MC/HC/XP deployed in standalone mode or in connection with a 7705 SARindoor unit. References to MPT-HC in this document refer to the MPT-HC V2.

Safety information

This document contains safety statements. Safety statements indicate where risks ofdamage to personnel, equipment, and operation may exist. Failure to follow thedirections in a safety statement may result in serious consequences.

For additional safety precautions, see the 9500 MPR User Guide(3DB-19901-ABAA).

New release capabilities

The features described below are introduced in the 9500 MPR R4.1.0:

Caution ETSI modem profiles only support E1 signals and ANSImodem profiles only support DS1/DS3 signals. Mixed configurationsare not supported unless explicitly documented.


8/


2 November 2012 Alcatel-Lucent 9500 MPR-E R4.1.0


Release Notice

Legend:

[MSS-1/4/8]the feature applies to the MSS-1/4/8 system only

[MSS-1c:]:the feature applies to the MSS-1c system only

[MPR-e]: the feature applies to the MPR-e system only

[ALL]: the feature applies to all systems

In Service software upgrade from 9500MPR R3.4.0 to R4.1.0

In Service software upgrade from 9500MPR R4.0.0 to R4.1.0

Provider Bridge QinQ 802.1ad [MSS-1/4/8]

MSS-1 shelf introduction (1+0 and ring configurations)

Packet throughput booster (header compression) [ALL]

7705 SAR + MPR-e [MPR-e]

IPv6 and OSPFv3 [MSS-1/4/8]

TACACS+ enhancements [MSS-1/4/8]

New XPIC modem profiles on 7/14 MHz channel spacings (MPT-HC/XP, fixed

and adaptive modulation) [MSS-1/4/8 and MPR-e]

Provider Bridge QinQ 802.1ad [MSS-1/4/8]

The switch supports double tagging according to 802.1ad, in particular:

adding a service VLAN on the ingress traffic

pbits value of service VLAN is: user configurable same value of customer VLAN

The EtherTypes supported are:

EtherType 0x8100

EtherType 0x9100

EtherType 0x88A8

Global Configuration

On an NE basis, in the CT/NMS it is possible to define the way to manage theEthernet 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 theuser ports of an EAS card.

When the NE is configured in Provider Bridge mode, the forwarding of Ethernettraffic is managed according to Service VLAN. Each Service VLAN (S-VLAN)represents a service instance where Ethernet traffic from a customer network ismapped to.


9/




Release Notice

In Provider Bridge mode, an S-VLAN is assigned to all Ethernet frames managed bythe NE. The assignment of an S-VLAN to an Ethernet frame ingressing the NE shallbe done according to the type of the Provider Bridge port:

Provider Network Port (PNP), this is an interface internal to the Provider BridgedNetwork (NNI), SVLAN is assigned based on S-VLAN ID carried by S-VLANTag 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 ProviderBridged Network (UNI), S-VLAN is assigned based on User Ethernet port(Port-based service interface) regardless of the type of customer traffic (C-VLANtagged or untagged);

When the NE is working in Provider Bridge mode, all the switches process Ethernetframes 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 doubletagged 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 VLANIDs already defined to cross-connect internal flows (i.e. TDM2TDM,TDM2ETH) cannot be used. The management system shall prohibit the definitionof S-VLAN ID already used and shall highlighting the issue. The S-VLAN IDmust be different also from the Flow ID associated to E1 tributaries not yet crossconnected.

Define S-VLAN Name; this is a text string of up to 32 characters. There is nocheck 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 portsinclude L2 Radio LAG and L1 Radio LAG too) can be member of an SVLAN.This means that a disabled port can be configured as a member of an S-VLANand a port already member of an S-VLAN can be disabled continuing to be in themember set of that S-VLAN.

Define among the ports belonging to member set of this S-VLAN those whereS-VLAN will be removed from the frames delivering them untagged in egress(S-VLAN Untagged Set). Only the User Ethernet ports, enabled and disabledshall be manageable. The S-VLAN is never removed from the Radio ports (withthe 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 setand 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 morethan 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 thanone S-VLAN and is never in the untagged set of those S-VLANs.


1




Release Notice

S-VLAN removal

It is possible to remove an S-VLAN from the S-VLAN Table even if the S-VLANID has been configured on one or more User Ethernet ports (being PNP or CNP) asPort 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-VLANuntagged frames received on this port. Before applying the removal, the managementsystem does request to the operator confirmation of the operation, highlighting theconsequence of the operation.

Equipment components de-provisioning

When an equipment component, on which there is at least one port belonging to themember set of an S-VLAN, is declared by the operator as no more expected in thecurrent equipment position, the management system rejects the operation.

The board can be declared as no more expected only when no one of its interfacesbelong 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-VLANTable when the Provider Bridge type is selected. This S-VLAN shall be shown to theoperator 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 areenabled or disabled and port type, must be in the member set of the S-VLAN havingS-VLAN ID 1.

The S-VLAN ID 1 shall be always removed at the egress of all PNPs. This meansthat PNPs are always in the untagged set of S-VLAN having S-VLAN ID 1.

CNP is by default in the untagged set of any S-VLAN including S-VLAN ID 1.

Management of Provider Bridge Ports Port Type

Each User Ethernet port of Core and EAS boards can be configured either ProviderNetwork Port (PNP) or as Customer Network Port (CNP). For Radio ports, the PortType 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 toidentify the Ethernet frame as S-VLAN tagged, S-VLAN untagged or S-VLANpriority-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 valueis 0x8100.


1




Release Notice

For Radio ports, the S-VLAN TPID is fixed to 0x8100 and cannot be modified bymanagement systems.

PNP - Acceptable Frame Type

Acceptable Frame Type parameter controls which type of Ethernet frames areaccepted 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 areadmitted.

For Radio ports, the Acceptable Frame Type parameter is fixed to admit onlyVLAN-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-VLANhaving S-VLAN ID 1 and accepting only S-VLAN tagged frames in ingress, thedelivery 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, theS-VLAN ID to be assigned to S-VLAN untagged or S-VLAN priority-tagged framesare configurable by management systems.

Only S-VLAN IDs related to S-VLANs having the PNP in their member set can beselected.

The default value of Port S-VLAN ID is 1.When the Acceptable Frame Type parameter is set to Admit only VLAN taggedframes, the Port S-VLAN ID is set to default value.

When a PNP is changed to CNP, Port S-VLAN ID parameter is kept.

PNP - Priority and Drop Eligible

For S-VLAN tagged and S-VLAN priority-tagged frames ingressing a PNP, thepriority is determined by the PCP (Priority Code Point) field carried by S-VLANTag.

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 (everyEthernet frame is considered as in-profile or green). Priority Code PointDecoding Table is not managed.


1




Release Notice

PNP - Port Priority

When the Acceptable Frame Types parameter is set to admit all frames, the priorityto be assigned to S-VLAN untagged frames shall be configurable by managementsystems (for S-VLAN priority-tagged frames the priority is the one carried by PCPfield).

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 taggedframes, 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-VLANuntagged frames is the Forwarding Class related to the DSCP field carried by theframe according to the configuration of IPv4/IPv6 DiffServ to internal ForwardingClass 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 bymanagement systems. This means that an S-VLAN tagged frame received on a PNPthat is not in the member set associated with the frames S-VLAN ID shall bediscarded.

PNP - PCP and DEI fields of S-VLAN Tag

S-VLAN Tags PCP (Priority Code Point) field of S-VLAN tagged frames egressinga PNP is determined by the priority assessed at ingress port.

S-VLAN Tags DEI (Drop Eligible Indication) field of S-VLAN tagged framesegressing a PNP is set to:

The same value of received S-VLAN Tags DEI field when the frame was anS-VLAN tagged or S-VLAN priority tagged frame and the ingress port was aPNP

Zero when the frame was an S-VLAN untagged frame and the ingress port was aPNP since Drop eligible is set to false

Zero when the ingress port of the frame was a CNP since Drop eligible is set tofalse

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 Limiteracts always on the outer VLAN Tag, in case of PNP it acts as an S-VLAN RateLimiter.


1




Release Notice

PNP - Per-CoS Rate Limiter

The Per CoS Rate Limiter feature described is also supported on PNP. Since thePer-VLAN Per CoS Rate Limiter acts always on the outer VLAN Tag, in case ofPNP 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 areaccepted in ingress at the CNP. Taking into account the CNP is a port of anS-VLAN Component, the only permissible value for this parameter is Admitonly untagged and priority-tagged frames, the parameter is not configurable bymanagement 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 theS-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 framesare 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 arerecognized as C-VLAN priority tagged frames at CNP).

CNP - Port S-VLAN ID

For a CNP, the Port S-VLAN ID represents the S-VLAN ID assigned to all theEthernet frames ingressing the port. Port S-VLAN ID selects the port-basedservice instance associated to CNP. According the management of CNP in theS-VLAN Table, at most two S-VLANs have the CNP in their member set, andone is the S-VLAN having S-VLAN ID 1.

Since the S-VLAN ID 1 cant represent a service instance, a Port S-VLAN IDother 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 Ethernetframes 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 framesingressing a CNP can be also determined looking to the PCP field of C-VLAN


1




Release Notice

Tag in case of C-VLAN tagged or C-VLAN priority-tagged frames. The selectionbetween the usage of Port Priority or Customer Priority shall be configurable bymanagement systems.

When Customer Priority is selected and the received frame is untagged, the PortPriority 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 (everyEthernet frame is considered as in-profile or green). When a CNP is changedto PNP, Port Priority parameter is kept, while priority assignment is set to thedefault (Port Priority).

When the QoS classification is based on DiffServ, the priority assigned tountagged frames is the Forwarding Class related to the DSCP field carried by theframe according to the configuration of IPv4/IPv6 DiffServ to internalForwarding Class mapping. The priority assigned to a frame not carrying andIPv4/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 RateLimiter 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 thePer-VLAN Per CoS Rate Limiter acts always on the outer VLAN Tag, in case ofCNP 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 Priorityusage, the only selectable PCP is Port Priority value. In case of Customer Priorityusage the full range of PCPs is selectable.

Bridge Mode Configuration

The following considerations apply when changing bridge mode:

Change bridge mode configuration from 802.1D (MAC Bridge) to 802.1ad(Provider Bridge)

To change the NE bridge mode from MAC Bridge to Provider Bridge allcross-connections must be removed. No check is requested by NE and CT/NMSto enforce cross-connections removal, in case Provider Bridge were activatedhaving cross-connections still configured, the delivery of cross-connected trafficis not guaranteed.

After the change all User Ethernet interfaces are set as PNP with S-VLAN TPIDequal 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 VLANTable can be kept in case of change of NE bridge mode from Virtual Bridge toProvider Bridge. Changing from Virtual Bridge to Provider Bridge, there will be


1




Release Notice

a traffic impact on the delivery of cross-connected and Ethernet traffics duringrestart, due to the unavoidable reconfiguration of the Ethernet switches in 802.1admode.

After restart all User Ethernet interfaces are set as PNP with S-VLAN TPID equalto 0x8100.

The S-VLAN Table is filled with S-VLANs having S-VLAN ID equal to theVLAN ID of VLANs previously defined in the VLAN Table. Port VLAN ID andPort Priority assigned to User Ethernet interfaces are assigned as Port S-VLANID and Port Priority of PNPs.

This allows continuing to deliver existing C-VLAN tagged Ethernet traffic evenif the NE bridge mode is changed to Provider Bridge. C-VLANs are seen by theNE as S-VLANs since all the ports are PNP with S-VLAN TPID same ofC-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 allcross-connections and all defined S-VLANs must be removed.

No check is requested by NE and CT/NMS to enforce cross-connections andS-VLANs removal, in case MAC Bridge were activated havingcross-connections and S-VLANs still configured, the delivery of cross-connectedtraffic 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 allcross-connections and all defined S-VLANs must be removed. No check isrequested by NE and CT/NMS to enforce cross-connections and S-VLANsremoval, in case Virtual Bridge were activated having cross-connections andS-VLANs still configured, the delivery of cross-connected traffic and Ethernettraffic is not guaranteed.

Upon changing from Provider Bridge to MAC Bridge, the NE shall perform arestart.

C-VLAN Translation

The C-VLAN Translation feature is not available when the NE is configured inProvider Bridge mode. The request to enable the Provider Bridge mode when thereare 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 modeand 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.


1




Release Notice

Packet throughput booster (header compression) [ALL]

A data packet often has a large amount of overhead compared to the actual usertraffic (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 toimprove throughput.

Packet Throughput Booster is for MPT-MC/MPT-HC/MPT-XP units

The following describes some details about the header fields.

Inter-Frame GAP (12 bytes). Ethernet devices must allow a minimum idle periodbetween 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 beentirely eliminated

Preamble and Start of Frame Delimiter (8 bytes). They have been added by IEEE802.3 standard to allow devices on the network to easily detect a new incomingframe. These bytes are not needed in a microwave transmission and can beentirely eliminated.

Ethernet header. This is the information used to switch an Ethernet frame acrossa 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 EthernetFrame.

CRC (4 byte): Frame check sequence, used to detect errored frames - Payload(46-1500 bytes): user data

For example, the minimum Ethernet message is 64 bytes long. If one VLAN ispresent, then that frame carries only 42 bytes of useful information (payload) butrequires 84 bytes overall to transport, equaling a 100% overhead to payload ratio.Examining closer, the inefficiency of small packets is even worse when using otherprotocols such as IPv4 or IPv6 because they are encapsulated in the Ethernetpayload; IPv6 IP addresses occupy an additional 32 bytes, making transportefficiency of multi-protocol packets of short length very poor.

Header compression can significantly increase radio link throughput reducingprotocol header overhead. The header size that is compressed is constant, whilst thepacket payload is variable: from this there is an inverse proportion between packetlength and related gain.

Packet Throughput Booster can be applied to MPT-MC and MPT-HC/XP, exceptwhen the MPTs are involved in a LAG L1 group. In this case Packet ThroughputBooster cannot be applied with the current release.


1




Release Notice

Packet Throughput Booster can be applied to 1+0 or 1+1 HSB/FD/SDconfigurations. For 1+1 configurations, in case the RPS module is not used, it shouldbe considered that the maximum throughput at L2 can be some 440 Mbit/sec; if theL2 throughput does exceed this threshold RPS module and tight cable have to beused.

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 differentlevels 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 andMPT-HC/XP.

The main radio configurations and topologies available in this case are:

1+0 hop, with one MPR-e and one 7705 SAR per site.

2x(1+0) XPIC, with two MPR-e (MPT-HC/XP) and one 7705 SAR per site.

N+0 hop, with N MPR-e and one 7705 SAR per site. The 7705 IP/MPLSnetworking and protections apply here.

Ring/mesh topologies, with N MPR-e and one 7705 SAR per site. 7705 IP/MPLSnetworking and protections apply here.

In addition to these variants, the 7705 SAR Release 5.0 R4 introduced the PMC card(Packet Microwave Adapter - PN 3HE02782AA) for the 7705 SAR shelf, which is afirst step of microwave integration between 7705 SAR and MPR-e. The additionalfeatures are:

HW readiness for the SingleNE approach

Proprietary Clock Recovery (PCR), a way to distribute synchronization alongSAR-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 000xTQZZA) and the related user guides.


1




Release Notice

7705 SAR + MPR-e Single NE

The 7705 SAR Release 6.0 R1 and 9500 MPR R4.1.0 releases introduce thefollowing, providing an increase in the level of integration between the MPR-e andthe 7705 SAR-8/18:

SingleNE 1+1 HSB SD functionality with MPT-HC/MPT-XP (RPS module andcoupling 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 tothe 7705 SAR baseband are reachable using the 7705 SAR IP address (system IP orothers) using the MCT Launcher.

Available radio configurations: on top of the ones described above for separate NEs,here one configuration more is available: 1+1 HSB SD introducing standard uW

protections in IP/MPLS uW networks. This feature requires an MPT-HC/XP with thecoupling link and two PMCs on the 7705 SAR, thereby protecting the 7705 SARhardware 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 the9500 MPR does not support "dual stacks", that is, IPv4 and IPv6 enabled at the sametime.

When IPv6 is enabled, the 9500 MPR will restart, disable the IPv4 mode, and allowthe user to configure the IPv6 address.

The NE Local IPv6 address is a Global Unicast address configured statically by theoperator through the management systems which identifies the NE in the DCN. Thedefault address is FEC0:0:0:1::1. The prefix length is not configurable and is fixedto 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


1




Release Notice

TMN In-band interface #1

TMN In-band interface #2

TACACS+ enhancements [MSS-1/4/8]

TACACS+ (Terminal Access Controller Access-Control System Plus) is an accesscontrol network protocol.

TACACS+ has been supported in 9500 MPR since R3.4.0. In R4.1.0 additionalfunctionality has been added to further support the TACACS+ standard:

In 9500 MPR R4.1.0, TACACS+ Accounting provides limited supported for theWT-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 SETcommand received from a registered manager.

The SET commands to register a manager and SET commands to perform aregistration deletion are also reported.

Accounting notifications are not supported for commands received on the HTTPinterface.

Features significantly changed

This section describes features that have significantly changed from the prior releaseto the current release.

STM-1 channelized support of L2 LAG crossconnections

L2 LAG cross-connections are supported on SDHCHANN cards.

Transmitter mute function [MSS-1/4/8]

In R4.1.0, the Transmitter mute function has been improved to add a timer toautomaticity unmute the transmitter. The operator can now provide the duration ofthe command (timeout). It is expressed in days, hours and minutes starting from thetime of the TX Mute activation. The default value is 30 minutes. The maximumduration is 2 days, 0 hours, 0 minutes.

A value of 0 days 0, hours and 0 minutes is not allowed.


2




Release Notice

Retained capabilities

The 9500 MPR R4.1.0 retains all capabilities from the 9500 MPR R4.0.0.

Discontinued capabilitiesNone.


2




Release Notice

Documentation delivery

The 9500 MPR R4.1.0 documentation is available through electronic distributiononly. Contact your Alcatel-Lucent Sales Support Representative to place an order.Table 1lists the documentation items. See Customer documentationfor information

about downloading the documentation from OLCS.

Table 1 9500 MPR R4.1.0 documentation ordering information

Document Alcatel-Lucent part number

9500 MPR-E 4.1.0 Release Notice(this document) 3DB-19043-AAAA-FMZZA

9500 MPR 4.1.0 User Guide 3DB-19901-ABAA

9500 MPR 4.1.0 MPR-e User Guide 3DB-19901-EBAA

9500 MPR 4.1.0 MSS-1c User Guide 3DB-19901-DBAA

9500 MPR 4.1.0 MPT-GC User Guide 3DB-19025-AAAA 02


2




Release Notice

Software and license delivery

Table 2lists the software version information.

Table 2 9500 MPR-E R4.1.0 software

Note(1) Available through download from OLCS.

Table 3lists the third-party software that is used for execution of the 9500 MPRR4.1.0 and that is liable to license agreements. 9500 MPR R4.1.0 CT operation hasbeen validated with the following third-party software.

Table 3 Third-party software

Note(1) Alcatel-Lucent recommends Windows 7 in an IPv6 environment.

Description Alcatel-Lucent part number

9500 MPR 4.1.0 Hybrid OS 3DB18969ACAA(1)

9500 MPR 4.1.0 Packet OS 3DB18970ACAA(1)

TCO SW Suite R4.9.0 3DB18971ACAA(1)

9500 MPR 4.1.0 SNMP 3DB18896DAAA(1)

Software Version

Windows XP(1) Professional Ed. SP3 (32 bit only)

Windows 7(1) Premium (32/64 bit)

Java JRE Minimum Version 6, Update 30, 32 bit only (included on CD

3DB18971ACAA TCO SW Suite R4.9)

MS IE Explorer Version 8 on Windows XP, Version 9 or higher on Windows 7

Firefox Version 12 or higher

Chrome Version 20 or higher

FTP Servers (for software download feature) Tested FTP servers:

Apache FTP Server (http://incubator.apache.org/ftpserver/)Default available with WebEML (JUSM/CT)

VSFTPD, version 2.0.5

FileZilla FTP Server, version 0.9.23
http://incubator.apache.org/ftpserver/http://incubator.apache.org/ftpserver/


2




Release Notice

Software compatibility

This section describes 9500 MPR software compatibility.

Backwards compatibility and migrationThe 9500 MPR-E R4.1.0 supports migration from the following releases:

9500 MPR-E R3.4.0

9500 MPR-E R4.0.0

See the 9500 MPR User Guide(3DB-19901-ABAA) for an overview of themigration procedures.

Contact your Alcatel-Lucent Technical Support Representative for assistance beforeplanning or performing an upgrade.

Downloading the softwareThe electronic delivery site gives you access to the product software packages. If youare a new user and require access to this service, please contact your Alcatel-Lucentsales representative.

Use Procedure 1to 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 Deliverypage 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.
http://www.alcatel-lucent.com/myaccesshttp://www.alcatel-lucent.com/myaccess


2




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 areLow, Medium, High), then click on the Download button to start the file

transfer.

b Click on the Download Plus button to start the file transfer with the GetPlus

download agent, and follow the instructions on the screen.

Installing the software

The following materials are required:

software kit identified in the Software Information section

Ethernet cable to connect to the core module (crossover or straight-through), orfor connection over an existing Ethernet network

laptop or other PC with the 9500 MPR-E R4.1.0 CT application installed

administrator ID and password to log in to each 9500 MPR-E shelf

IP Address or host name of each 9500 MPR-E shelf

9500 MPR-E System with current equipment as described in the 9500 MPR-E

Release Notice (this document) a Core-E card (CSM) equipped with a Compact Flash (see Table C-3for the

codes; for example, MPR Memory L6TD-410)

Software components

The delivery for R4.1.0 contains the software elements described in Tables 4and 5.

Table 4 R4.1.0 Software components for MSS-1c and MPR-e

Note The Download Plus button may not be available on thesoftware download page. The system prompts you to install a browser

plug-in to activate this download option, and provides you with

installation instructions. Some browser versions do not support the

Download Plus plug-in.

Software component Version

MSS-1c/MPR-e SubRelease version V04.10.0N

MPT SW V08.15.03

MCT SWP V06.14.00


2




Release Notice

Table 5 Release 4.1.0 Software components for MSS-4 and MSS-8

TCO suite and MCT system requirements

To install the TCO suite application (including Craft Terminal), verify that yourcomputer meets the following minimum system requirements:

PC hardware configuration CPU: AMD Atlhon/Intel Celeron/Intel Pentium 4 or higher RAM: 1 GB minimum disk space: 1.5 GB (available space needed for log files, JRE excluded) minimum resolution: 4:3 equal or higher 1152x864 pixel minimum resolution: 16:9 equal or higher 1280x800 pixel DVD-ROM Drive: 24x primary interface: Ethernet Card 10/100 Mb/s (1 Gbit/s for MPR-e)

additional requirements minimum HTML page size shown must be 1024x768 pixels PC standard user mode can be used to run the applications, but for TCO Suite usage

the Administrator password is needed

all firewall software must be disabled TCO Provisioning Tool should be used for the first commissioning of the equipment

if the TCO tool is used on a PC with Windows Vista Ultimate, verify that in thelist of network connections available, the one used to connect the PC to the NE isnot the first connection in the list. To change the order of the list, in WindowsVista, go to Control Panel!Network and Sharing Center!Manage Network

Software component Version

MSS-4/MSS-8 SubRelease version 4.1.0v

EC V14.15.05TCO Suite V410.04

ODU300 software version 04.06.10

Caution TCO Suite contains 32-bit Java VM only. This can beused with 32-bit Internet browsers only such as Mozilla Firefox,

Internet Explorer or Google Chrome. Note that reference MicrosoftWindows operating systems do not allow a 64-bit Internet browser(not even Microsoft Internet Explorer 64-bit) as default browser forthe system in use. In case a 64-bit browser needs to be used, manuallyinstall 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 TCOSuite DVD-ROM root directory.

If a Java VM version 7 is installed, there is no need to remove it or toset a specific configuration. TCO Suite and WebEML willautomatically use any Java VM version 6 (greater than 6u26)available on the system only for its own session. All other javaapplications, web applications or applets using Java VM version 7will continue to work with version 7.


2




Release Notice

Connections!Advanced!Advanced Settings menu (press and release the ALTkeyboard button to show the menus). The list of network connections appears: theorder of the list can be modified using the arrow button on the right.

TCO SW Suite 4.9.0 includes an option dedicated to the 5620 SAM.

To create a local copy of WebEML, use the Local Copy of WebEML button (as

shown in Figure 1), as in previous TCO versions. To create a local copy of theCraft Terminal of the MSS-1c/MPR-e/MSS-4/MSS-8, use the 5620 SAM NEtOMultiversion button to create a local copy of a profiled version of the entireWebEML.

Figure 1 Advanced Install Settings screen

A list of supported Operating systems and browsers can be found in Table 3.

For MPR-e provisioning, the PC used must be able to tag VLANs, in order to connectto the MPT through the TMN in-band VLAN. Otherwise, the PC must be connectedto a Layer 2 switch with a GE interface and the capability to tag VLANs. See the9500 MPR R4.1.0 User Guide(3DB-19901-ABAA).

Upgrade paths

Table 6shows the upgrade paths to Release 4.1.0.

Table 6 Upgrade paths to Release 4.1.0

System Source

release

Destination

release

Possible (Y/N)? Notes

MSS-1/4/8 3.0.0 4.1.0 N Must upgrade to 3.3.0 and then to 3.4.0 first

(1 of 2)


2




Release Notice

The estimated total time to execute the installation procedure is approximately 40minutes per 9500 MPR shelf in 1+1 radio protection. This time does not include anysite preparation and pre/post-installation retrievals or setup.

This software is supported on Core-E (CSM) controller modules only.

Precautions and recommendations

Read the entire software installation procedure before beginning.

This procedure should be performed by a qualified Field Service Engineer trainedon the 9500 MPR during an approved maintenance window.

3.1.0 4.1.0 N Must upgrade to 3.3.0 and then to 3.4.0 first

3.2.0 4.1.0 N Must upgrade to 3.4.0 first


3.4.0 4.1.0 Y

4.0.0 4.1.0 Y

MSS-1c/MPR-e 3.0 4.1.0 N Must upgrade to 3.3.0 and then to 3.4.0 first

3.1.0 4.1.0 N Must upgrade to 3.3.0 and then to 3.4.0 first



3.4.0 4.1.0 Y

4.0.0 4.1.0 Y

System Source

release

Destination

release

Possible (Y/N)? Notes

(2 of 2)

Caution Do not upgrade the Network Element Software unless itis required. Once the software is upgraded, it is very difficult to returnto a previous software release. If software needs to be returned to a

prior release, contact Alcatel-Lucent before you start.

Caution This upgrade procedure will cause traffic andmanagement interruption during the activation of the R4.1.0 software.

Caution Once the Release 4.1.0 release software has beenactivated, the Release 4.1.0 CT must be used to manage the NE.


2




Release Notice

Traffic impact during the SWP activation

Traffic impact varies by upgrade path.

from R3.4.0/R4.0.0 (with ODU300) to R4.1.0: measured on E1 interfaces, thereare 0/25 seconds of traffic impact immediately after SWP activation.

from R3.4.0/R4.0.0 (with MPT-xC connected to MPT Access unit) to R4.1.0:measured on E1 interfaces, there are 120/160 seconds of traffic impactimmediately after SWP activation.

from R3.4.0/R4.0.0 (with MPR-e or MSS-1c) to R4.1.0: traffic impact in case ofsoftware migration is around 150 seconds.

Procedure 2shows the general steps to upgrade to Release 4.1.0. Refer to the9500 MPR 4.1.0 User Guide(3DB-19901-ABAA) for the detailed procedure.

Procedure 2 To upgrade from R3.4.0/4.0.0 to R4.1.0

1 Install the R 4.1.0 version of the 9500 MPR-E Craft Terminal on the Craft PC.

Pre-loading operation verification

2 Check and set the system time.

3 Check for Alarms and Abnormal Conditions.

4 Ensure that the main Core module is active (Protected Core configurations only).The migration procedure is not allowed if the spare core module is active (MSS-4/8

only).

5 Retrieve and save the current configuration and perform a backup.

6 Install the R4.1.0 Software Package (SWP) to the Craft Terminal PC or on a FTP

server (for MPR-e/MSS-1c).

7 Download the R4.1.0 Software Package to the 9500 MPR.

8 Activate the R4.1.0 Software Package on the 9500 MPR.

9 Verify activation of the R4.1.0 Software Package on the 9500 MPR.

10 Check for Alarms and Abnormal Conditions.

11 Load the R4.1.0 Software Package into the Standby software bank.

12 Optionally, update the License Key (MSS-1/4/8 only).

Third-party software notes

Table lists the Non-Alcatel-Lucent Owned Software (NAOS) items that are includedas part of this release.


2




Release Notice

NAOS software included with 9500 MPR R4.1.0

NAOS item code NAOS item description

Minimum version 6, update 30, 32 bit only Java JRE


3



Release Notice

Release content

This section provides information about the content of the 9500 MPR release R4.1.0.

Implemented featuresThe 9500 MPR R4.1.0 includes the features described in New release capabilities.

Closed issues

Table 7describes the closed issues.

Table 7 Closed issues in R4.1.0

Usage notesTable 8describes the usage notes for this release. Usage notes supplement or clarifyinformation in the documentation. Where available, workarounds have beenprovided.

Item Description

ALL systems

Firmware download In some cases, MSS boards could be stuck in a continuous firmware downloadmode.

AUX card alarms AUX card alarms inconsistent raise and clear and do not correlate to the mainalarm window.

JUSM MSS Radio Main View JUSM MSS Radio Main View behavior inconsistent

MSS-1/4/8

MPT-HL reports wrong shifter ranges for7/8 GHz

The MPT-HL is reporting the wrong range values for all 7/8 GHz shifters, thusthe 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 SoftwareDownload Error is displayed and the stand-by software package is notupdated.

During the download on the standby bank of the same Sw version alreadyuploaded on the active bank, a StandBy Version Mismatch alarm isgenerated on the MPT.

Workaround: Do the software download via the Forced option.

MPR-e

MCT application freeze after restore insome case

After a Restore db of the MPR-e, if the user does not validate the Successdialog box before the Connection Lost dialog box, the MCT application willfreeze.

Workaround: Validate first the SUCCESS dialog box before the ConnectionLost dialog box.


3




Release Notice

Table 8 Usage notes for R4.1.0

Item Description

ALL systems

Time to perform software downloadusing FTP in IPv6 on remote NE In some cases using FTP with IPv6, software download can take up to 30minutes to complete.

Workaround: Wait at least 30 minutes for the software to download.

SFTP connection not released in case ofMIB backup/restore failure

If the MIB backup or restore procedure using SFTP fails, additional operationsusing SFTP may not be possible.

Workaround: Close and restart the Craft Terminal.

Software download start using SFTP failsif attempted immediately after softwaredownload manual abort

If the user manually aborts a software download using SFTP then immediatelyrestarts the software download, the user will receive an NE internal errormessage.

Workaround: After a manual software download abort, wait at least oneminute before starting another SFTP software download.

Google Chrome as default browser If Google Chrome is the default browser when the start.exe is executed on theWebEML TCO, even with Java 6u30 installed it tries to install the latest Javaversion. 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 theuser to the Java website to install Java 7 which is not supported.

Work Around: None.

Java 6u30 plugin The latest versions of Firefox and Chrome do not enable Java 6u30 by default,causing installation issues from the CD image.

Work around: In Firefox, manually go to add-ons and enable the 6u30 plugin.In Chrome click on "run this time" each time it appears.

Suggested DCN topology When the 9500 MPR is used as the designated router, on the same LAN, themaximum 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 theyreach 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 todelete the user and re-create the user using a new password.

Adaptive modulation With Adaptive Modulation enabled on the ODU300, when the CLA function isstarted there could be switching every 30 seconds on main or spare.

Workaround: The oscillations stop after 10 minutes.

False CLA After a 30 sec of RX common outage, the CLA criteria is declared and the TX isswitched (expected). The TX continues to switch every 30 sec while the RXoutage remains. When the RX recovers, the CLA criteria remains set on thestandby 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 notCard Fail Alarm.

Workaround: If LOS is still present after troubleshooting the LOS, replace the

SFP.

TDM2ETH EC ID for Rx/Tx cannot use the value of 1 for TDM2ETH

Per MEF8 standard, Rx ECIDs must be unique on the same NE.

MSS-1/4/8

(1 of 7)


3




Release Notice

Mixed network with 9500 MPR R4.1.0IPv6 stack active and older releases

A mixed link with IPv4 and IPv6 is not supported and the TMN channel will notoperator properly when configured in this manner.

Workaround: Ensure that both ends of the link are in the same operating mode.When migrating to IPv6, always update the far end, then the near end to

maintain visibility.

Excessive environmental temperaturealarm on MPT-HL after ISU from R4.0.0

After an upgrade to R4.1.0 occasionally the MPT-HL will declare an "ExcessiveEnvironmental Temperature" alarm.

Workaround: Clear the alarm via warm start of the MPT-HL via the craftterminal.

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 IPv4and IPv6 address, the 9500 MPR craft terminal is slow.

Workaround: When using Windows XP, it is not recommended to use IPv6 andIPv4. Only enable IPv4.

IPv6: issues on Windows XP If the 9500 MPR is configured for use with IPv6, it is highly recommended thatWindows 7 is used instead of Windows XP.

Workaround: None - use Windows 7.

Disconnect to remote server - differentbehavior in SFTP compared to FTP

Using FTP mode the session disconnection reactivity time is longer than in SFTPmode.

Workaround: Even though the FTP mode is longer than SFTP mode, the time isthe same as in previous releases.

Core protection in Y configuration With CORE Protection and using optical splitters on either Ethernet port 5 or 6and Using the LoS switch criteria, when the main side LOS is cleared traffic maybe affected.

Workaround: When using an optical splitter verify that LOS disable is set. Theusage the optical splitter on the CORE is intended for protecting against Coreboard failure and not for line protection.

LOS criteria is intended to be used only in case of 9500 MPR stackingconfigurations.

Cannot set port VLAN or priority onEthernet LAG when in 802.1ad (providerbridge) mode

Once the bridge mode is changed to 802.1ad, it is not possible to assign a portVLAN to an L2 Ethernet LAG. Also, if one already exists before converting from802.1q to 802.1ad, it is no longer possible to remove or change the VLAN onthe LAG, or to remove the VLAN.

Workaround: In 9500 MPR 4.1 L2 Ethernet LAG and 802.1ad are not supportedsimultaneously.

SSm message from Eth port afterunprovisioning MPT MC-HC

If an Ethernet port has been configured as an MPT-xC on the Core-E and thenconfigured as a user Ethernet port with SSM enabled, the SSM functionality willnot function properly.

Workaround: A warm start of the 9500 MPR will correct the issue.

IPv6: DAD alarm severity notmanageable

The DAD alarm severity is not managed properly using ASAP profiles.

Workaround: None

NEtO discovery protocol When in IPv6 mode, NEtO discovery of the 9500 MPR may not work if multicastUDP 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 thecolon, single quote and double quote.

Workaround: User passwords are allowed alphabet letters a-z and numbers 0-9.

Password printable characters are allowed except ' "" :

Item Description

(2 of 7)


3




Release Notice

AUX module on SBD On the summary block diagram, the AUX module does not show any alarmsynthesis nor can the user navigate to the AUX module from the summary blockdiagram.

Workaround: Exit the Summary block diagram and navigate to the AUX board

from the equipment view.

Radio capacity value The Current Configuration View may not show the correct radio capacity.

Workaround: If the radio capacity is in question, navigate to the radio view andverify the radio capacity.

SW activation of 3.x load The 9500 MPR R4.1.0 supports upgrades from R3.4.0, however softwarerollback to R3.4.0 is not supported.

Workaround: None

CT not enabling TX Mute Auto Localwhen Incompatible TX Power is set

When an Incompatible TX Power alarm is raised the radio CT screen TX Mutedoes 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 notwork. The window that opens allows you to select the network location butupon clicking Done it does not save the filter.

Workaround: Map network location to a drive letter and use that to save to thenetwork 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 onlysupport queue size of 3 987 220 bytes. Should the system be set between thosesizes, 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-EEthernet port, a traffic hit on this particular port occurs. Workaround: None

MSS 4/8 Configuration changes MSS 4/8 Configuration changes are not retained after the following operationssequence:

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 nowplugged in.

Workaround: After changes create a database backup with changes beforeplugging 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 asoftware 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 Lagconfigurations:

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 thesame plug-in

A mixed configuration of a Layer1 LAG and a 1+0/1+1 radio link configuredon plug-ins on the same row.

Workaround: None

Item Description

(3 of 7)


3




Release Notice

Migrating from a 1+1 FD system When migrating from a 1+1 FD system to a 1+0 with PM already active, thecounter 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 to802.1q mode, TDM traffic may be affected.

Workaround: None

MPT-ACC/EAS plug-in insertion After plugging in a MPT-ACC or an EAS card, the Ethernet Statistics may beinaccurate right after insertion.

Workaround: After MPT-ACC/EAS plug-in insertion, it is necessary to wait atleast 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 TDMtraffic is looped back.

Workaround: If loopbacks must be used when in Layer 1 LAG, then all TDM flowsmust be looped back.

L1 LAG Ethernet PM counters With no user traffic on the radio, the L1 LAG Ethernet PM counters still showframe counts. L1 LAG Ethernet Statistics take into account internalmanagement traffic too.This means that counter will show this traffic on top

of customer data. As an example, in case of null customer traffic, EthernetStatistics show a value different from zero due to the internal managementtraffic.

VLAN Rate Limiting When in 802.1q mode, after a VLAN has been provisioned with the rate limitingfunction, new members may not be added.

Workaround: Remove all associated VLAN rate limiters before adding newmembers to a VLAN.

Threshold Cross Alarms on DS1 and E1s Present Threshold Cross Alarms on DS1 and E1s are not cleared if the DS1 or E1port 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 changingthe VLAN rate limiter.

Workaround: None

RUM alarm with Protected Core-E andMPT Ports

If the system is provisioned with CORE-E Protection and SFP port is provisionedthen configured as MPT-HC port, there will be a standing Replaceable UnitMissing Alarm on the Spare CORE-E.

Workaround: CORE-E Protection is not supported when MPT-HC is connected tothe 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 tobe provisioned on that card, otherwise the system will generate unnecessaryAlarms.

TTO counter TTO counter may not be accurate at high data rates and update time greaterthan 30 seconds.

Workaround: Set update time below 30 seconds.

Storm control and Port Rate Limitingwith SSM and TDM Cross Connections

Enabling Storm Control or Port rate limiting on an Ethernet port that is usedwith 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 impacttraffic.

TDM: Rate limiting or Storm Control (multicast) can drop TDM traffic TMN: Rate limiting and Storm Control can drop TMN packets or interrupt

OSPF LSA's causing loss of visibility

Item Description

(4 of 7)


3




Release Notice

SW upgrade from R4.0.0 to R4.1.0 on aNE 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 atraffic impact could be seen on the MPT-xC not included in the L1 LAG, after aCore-E switch or a NE restart.

Workaround: in these very specific conditions a Backup and Restore on the NEwill solve the issue.

Upgrading to R4.1.0 using the MPTACC After upgrading to R4.1.0 using the MPTACC and then migrating to L1LAG onEAS, the MPT-HC needs a power cycle for the module to link up with thesystem. Workaround: None

LAG configuration GUI Radio and Ethernet ports may not show up in the LAG configuration GUI. If aport does not meet certain criteria, such as PPP/RF disabled, ports will notshow up in the list. See the help file for a list of all pre-requisites.

Migrating from Non LAG Configurationsto LAG configurations

When migrating from Non LAG Configurations to LAG configurations, takecaution 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 thebandwidth 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 supervisionremains available (there is a minimum guaranteed bandwidth reserved forTMN).

Operator can proceed with the LAG membership creation adding the secondport.

Bandwidth will be enough again and the traffic will be recovered.

Provisioning a second SFP in an SDHACC1+1 protection pair

Provisioning a second SFP in an SDHACC 1+1 protection pair fails.

Workarounds:

Provision all SFPs before configuring protection.

Use other slots or cards for additional equipment. Remove protection before adding the second port. This will disrupt traffic.

Provisioning multiple ERP instances When provisioning multiple ERP instances in the Ring Configuration dialog, theCraft discards changes without warning when switching to another ERPinstance.

Workaround: Apply changes after editing one ERP instance before moving tothe other ERP instance.

Link Configuration Mismatch alarm Expected behavior: Alarm is addressed to 'Radio Direction' object in AM andWeb Server. 'Navigate to USM' function in AM leads to alarmed object.Observedbehavior: for ODU300, alarm in AM is addressed to 'Dir/Ch' object, and alsonavigation to USM leads to this object, that is not alarmed, while is correctlyaddressed to 'Dir' object in Web Server/Entity field.

For MPT: in AM is correctly addressed to 'Dir' object, while in Web Server iserroneously 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 isdetected for the slot.

Navigation Navigation from the Summary Block Diagram to the 1+1 MPT-HL or 1+1 MPT-HCTraffic Port of Tx-Ch#0 view does not open the view.

Workaround: Open the Radio View from JUSM directly.

Item Description

(5 of 7)


3




Release Notice

System Maintenance of Core-E If the CORE-E Spare is not fully inserted in a prompt fashion, a Mismatch alarmmay occur.

Workaround: Plug in the CORE-E card promptly according to thedocumentation.

VLAN CIR Rate limiter VLAN CIR Rate limiter will not be set correctly if the only the apply button isclicked.

Workaround: After changing the CIR, the user must hit enter first beforeapplying the changes.

Spare ACM loop problem alarm When configured in XPIC with 1+1 in AMC mode, if the optical coupling isremoved at the far-end, no spare ACM loop problem alarm is raised.

Workaround: none

MSS-1c

OSPF: NMS1 link down does not updaterouting table in same subnet

If the MSS-1c and the MSS-1/4/8 on the same link are on the same subnet, ifthe MSS-1c NMS1 link goes down, the OSFP routing tables are not updatedproperly.

Workaround: Take care in the TMN configuration not to have the same subnetfor both the MSS-1c and MSS-1/4/8.

Migrating from MSS-1c 10 E1/DS1 toMSS1c 16 E1/DS1

When migrating from MSS-1c 10 E1/DS1 to MSS1c 16 E1/DS1 no message isdisplayed to convert the provisioning.

Workaround: Click on the Refresh button on the MCT.

MPR-e standalone

RTPC Power setting using Sliding option In the MCT, the RTPC slider allows 0.5 db more than the maximum limit.

Workaround: None

MPT QoS Ingress counter In the MCT Ethernet counter view, the back button does not work.

Workaround: None

MPR-e in Single NE with 7705 SAR

Setting line and radio side at the sametime in a MW-link

It is possible to set both the link and radio side loopback for a link.

Workaround: Ensure that you only set the radio side or the line side loopback

independently.

XPIC and 1+1 configuration In Single NE with 7705 SAR mode, 1+1 and XPIC are not supported, even if thesystem allows this configuration.

Workaround: A warm start of the MPT will clear any remaining conditionsshould the user provision 1+1 and XPIC at the same time.

Crash of MCT or MCT Launcher Occasionally the MCT or MCT launch will unexpectedly close or becomeunresponsive if left open for an extended period of time.

Workaround: Close the MCT or MCT launcher when necessary operations arecompleted.

RPS in Main MPT not aligned after Trafficcable plugged in or out in non revertivemode

After a removal/insertion of the traffic cable on the main MPT, the MCT willnot display the correct protection states on the main MCT.

Workaround: None

After upgrade 1+0 to 1+1: must close and

restart MCT Main to activate the PMRadio Link

After upgrading a link from 1+0 to 1+1 Radio PM inside the MCT no longer works

properly.

Workaround: Restart the MCT application

Item Description

(6 of 7)


3




Release Notice

On spare MPT is generated a RUP AlarmSpecific problem is reported as ModemTX Synch

In a 1+1 configuration if a TX mute on the Main MPT and both Main and SpareMPT are reset, the spare MPT will have a RUP alarm.

Workaround:

To clear the RUP alarm on the Spare MPT:

Unplug both main and spare PMC card Power off the Spare MPT Insert PMC where MPT main is connected (MPT still powered) Wait for Main radio hop to come up Insert the PMC where the Spare MPT is connected and at the same time

supply MPT SPARE

MPR-e standalone and MPR-e in Single NE with 7705 SAR

PM view and counters In the MCT may become slow and unresponsive in the PM view when open longterm.

Workaround: Close the MCT when necessary operations are completed.

MCT will not run with 64-bit java The MCT is only supported with 32-bit version of Java.

Workaround: Verify that the PC has 32-bit version of Java.

Item Description

(7 of 7)


3




Release Notice

Technical support

Use Procedure 3to find the contact information for technical assistance for a country.

Procedure 3 To find contact information for technical assistance1 Go to http://support.alcatel-lucent.com.

2 Log in to the Alcatel-Lucent Customer and Business Partner Portals with the username and password for your OLCS account. A customized Customer Center pag

Documents

3db19043aaaafmzza01_v1_9500 Mpr-e r4.1.0 Release Notice