BCR4.3.1_V1_Small Cell Cluster Release BCR4.3.1 - Release Letter

8/20/2019 BCR4.3.1_V1_Small Cell Cluster Release BCR4.3.1 - Release Letter

http://slidepdf.com/reader/full/bcr431v1small-cell-cluster-release-bcr431-release-letter 1/41

el-Lucent Alcatel-Lucent

Release Letter

15th November, 2013 Delivery

Small Cell Cluster Release

BCR4.3.1



RELEASE LETTER 15TH November, 2013 SMALL CELLS BCR4.3.1

Alcatel-Lucent – Proprietary

See Notice on Page 2 2

Copyright © 2013 by Alcatel-Lucent. All Rights Reserved.

This material is protected by the copyright and trade secret laws of France and othercountries. It may not be reproduced, distributed, or altered in any fashion by any entity(either internal or external to Alcatel-Lucent), except in accordance with applicableagreements, contracts or licensing, without the express written consent of the W-CDMAPortfolio Management Team and the business management owner of the material.

About Alcatel-Lucent

Alcatel-Lucent provides solutions that enable service providers, enterprises andgovernments worldwide, to deliver voice, data and video communication services to end-users. As a leader in fixed, mobile and converged broadband networking, IP technologies,

applications, and services, Alcatel-Lucent offers the end-to-end solutions that enablecompelling communications services for people at home, at work and on themove. Alcatel-Lucent is a local partner with global reach. The company has the mostexperienced global services team in the industry, and one of the largest research,technology and innovation organizations in the telecommunications industry. For moreinformation on Alcatel-Lucent, visit its web site at: http://www.alcatel-lucent.com.

Notice

At the time of publication, this document reflects the latest information on the Alcatel-Lucent’s Small Cell BSR Cluster Release 4.1 offering. This document will be updated eachtime a new set of features becomes generally available.

Trademarks

All trademarks and service marks specified herein are owned by their respectivecompanies.

http://www.alcatel-lucent.com/









PUBLICATION HISTORY

25/October/2013

Edition v1.0/ Standard Document – initial draft version

12/November/2013

Edition v1.1/ Standard Document – updated with CR fixed lists and latest open

CRs

14/November/2013

Edition v1.2/ Standard Document – updated with comments

18/November/2013

Edition v1.3/ Standard Document – updated with final comments






1 INTRODUCTION ............................................................................................ 7

1.1 SCOPE .................................................................................................... 7

1.2 AUDIENCE FOR THIS DOCUMENT ........................................................................... 7 2 RELATED DOCUMENTS .................................................................................... 8

2.1 REFERENCE DOCUMENTS .................................................................................. 8

2.2 APPLICABLE DOCUMENTS ................................................................................. 8

2.3 ABBREVIATIONS ........................................................................................... 8

3 SMALL CELL BCR4.3 DELIVERY ....................................................................... 10

3.1 LOAD HIGHLIGHTS .......................................................................................10

3.2 LOAD LINE UP............................................................................................10

3.3 V1.0, V1.2 AND V1.5 VERSIONS .......................................................................14

3.4 UPGRADE PATHS .........................................................................................15

3.4.1 FBSR Upgrade Paths ...........................................................................15 3.4.2 FGW Upgrade Paths ...........................................................................16

3.4.3 ALVF-1200HS (Brick) Upgrade Paths ........................................................16

3.4.4 IPC Upgrade Paths .............................................................................17

3.4.5 SCMS (FMS) Upgrade Paths ...................................................................18

3.4.6 AAA Upgrade Paths ............................................................................20

3.4.7 Brilliant Telecom Upgrade Paths ...........................................................20

3.4.8 BSR Data Version Changes ....................................................................20

3.4.1 FGW Data Version Changes ..................................................................20

3.5 SCMS RELEASE NOTES ..................................................................................21

3.6 NPO RELEASE NOTES ...................................................................................21

3.7 FRESH INSTALL PATHS ...................................................................................22 3.7.1 Small Cell Install Paths .......................................................................22

3.7.2 9365 BSR Gateway Install Paths .............................................................22

3.7.3 VPN Firewall Brick Install Paths ............................................................22

3.7.4 Iu Protocol Converter Install Paths .........................................................22

3.7.5 Small Cell Management System (SCMS) Install Paths ...................................22

3.7.6 8950 AAA Install Paths ........................................................................22

3.7.7 Brilliant Telecom Install Paths ..............................................................22

3.7.8 Data Version Install Paths ....................................................................22

3.8 FEATURE COMPLIANCE ...................................................................................23

3.8.1 Features without restrictions ...............................................................23

Features with limitations ...............................................................................24

3.8.2 Features in restriction ........................................................................26

SATELLITE BACKHAUL MANDATORY CHECKS ........................................................... 27

3.9 MANDATORY ACCEPTANCE CRITERIA FOR ROLL OUT .....................................................27

OPERATOR’S BACKHAUL NEEDS TO MEET OUR BACKHAUL REQUIREMENTS (NO EXCEPTIONS) SEE SECTION 4.2. ..............................................................................................27






OPERATORS’ NETWORK NEEDS TO BE ON RIGHT BCR RELEASE (MINIMUM BCR 3.03) AND ONLY

V2.X OR HIGHER CPE RUNNING ON BCR 3.03 OR LATER SW CAN BE USED. ............................27

OPERATOR NEEDS TO AGREE THE LIMITATIONS AND WHAT IS NOT SUPPORTED SEE SECTIONS

4.3 AND 4.4. ...................................................................................................27

CERTIFICATION TESTS NEEDS TO BE SUCCESSFULLY PASSED. .......................................27

IF ALL CONDITIONS MET SUCCESSFULLY ROLL-OUT CAN START. ...........................................27 3.10 BACKHAUL REQUIREMENTS (HIGH LEVEL VIEW) .......................................................27

3.11 LIMITATIONS ..........................................................................................28

V2.X OR HIGHER CPE HARDWARE RUNNING ON BCR 3.0.3 OR LATER SOFTWARE NEEDED. ......28

M AXIMUM ONE FEMTO PER LINK/MODEM. NO SHARING OF SINGLE LINK BY MULTIPLE FEMTOS. ...28

FEMTO OVER SATELLITE BACKHAUL WILL ONLY SUPPORT FIXED LOCATION DEPLOYMENTS E.G. CELL IN A VILLAGE, RURAL AREA. .............................................................................28

CLASS OF SERVICE (COS) BASED QUEUING HAS TO BE CONFIGURED IN THE SATELLITE

EQUIPMENT. ....................................................................................................28

AS IT CANNOT BE GUARANTEED THAT THE SATELLITE BACKHAUL HAS SUFFICIENT BANDWIDTH

RESOURCES, VOICE CALL ADMISSION DEPENDS ON HOW THE SATELLITE MODEM PROVIDES BANDWIDTH

CAPACITY (IMPORTANT FOR EMERGENCY CALLS) ...........................................................28

ALU KPI NOT COMPLIANT FOR SATELLITE BACKHAUL ................................................28

LOW DATA THROUGHPUT FOR PS CALL (DEPENDS OF SATELLITE BACKHAUL CONTEXT) ...........28

3.12 NOT SUPPORTED......................................................................................28

4 LIST OF SET-UP INFORMATION, KNOWN ISSUES, WORKAROUNDS ............................ 29

4.1 SILENT REBOOT ISSUE (WITH CHANGE IN CPU FREQUENCY CR 906938) ................................29

4.1.1 Summary ........................................................................................29

4.1.2 Impact of Frequency Change ................................................................29

4.1.3 How to do this via MIM .......................................................................29

4.1.4 How to verify current CPU Frequency .....................................................30

4.1.5 How to enforce 600Mhz CPU frequency ...................................................30

4.1.6 How to revert back to 700Mhz from 600Mhz CPU frequency ..........................30 4.1.7 How to enforce 600Mhz on a specific unit ................................................30

4.2 BSR SPARE PARAMETER WORKAROUNDS .................................................................30

4.2.1 Spare Parameter 9 (CR 910750) .............................................................31

4.2.2 Spare Parameter 10 (CR 898131) ...........................................................31



4.2.5 Spare Parameter 23 ...........................................................................32

4.3 FMS RADIUS PASSWORD SERVER CONFIGURATION .......................................................32

4.3.1 How To Enable this Feature .................................................................32

4.3.2 Nominal Case Scenario ........................................................................32

4.3.3 Which Condition It Should Fail ..............................................................33 4.3.4 How To Configure WMS-For-Small Cell Server To Allow WIPS Access Even If RADIUSWas Setup For Small Cells ...............................................................................33

4.4 MODIFY FEMTO SERIAL NUMBER .........................................................................34

4.5 EDCH 2MS TO BE USED IN DEMOS ONLY ..................................................................35

See section 3.7.2 “Features with limitations” ......................................................35

4.6 MACRO TO FEMTO HAND OVER BEHAVIOUR ..............................................................35






4.7 MODIFICATION OF 32 USER FEATURE PARAMETERS .......................................................35

5 LIST OF BCR4.3 CORRECTED ARS/CRS .............................................................. 36

5.1 9361 HOME CELL, 9362 ENTERPRISE CELL, 9363 METRO CELL-INDOOR, 9364 METRO CELL-OUTDOOR

36

5.2 9365 BSR GATEWAY ....................................................................................37 5.1 VPN FIREWALL BRICK ...................................................................................37

5.1 8950 AAA ..............................................................................................38

5.2 SMALL CELL MANAGEMENT SYSTEM (SCMS) .............................................................38

6 LIST OF OPEN BCR4.3/4.3.1 ARS/CRS............................................................... 39

6.1 FEMTO OPEN CR / AR ..................................................................................39

6.2 9365 BSR GATEWAY OPEN CR / AR ...................................................................39

6.1 SMALL CELL MANAGEMENT SYSTEM (SCMS) OPEN CR / AR .............................................40






1 INTRODUCTION

This document covers the Small Cell BSR Cluster Release BCR4.3.1 network software &

hardware information, known issues and workarounds.

All field deployments are advised to run the latest available software version.

1.1 Scope

This document is valid for the BCR4.3.1 network software version.

This document provides information on Network Elements (NEs) tested in Network Level

test (NLT) end-to-end environment.

The document does not include the Core Network or any UEs.

This document provides information on the following NEs:

Alcatel-Lucent Home, Enterprise & Metro Cell – HW V1.0, V1.2, V1.5, V2.0,

V2.2, LR2100, LR1900, V2.1, V3.0

Alcatel-Lucent 9366 Small Cell Gateway including:

o Iu Protocol Converter

o 9365 BSR Gateway

o VPN Firewall Brick

o 8950 AAA

Small Cell Management System (SCMS)

Brilliant NTP Server

Symmetricom NTP Server

Each customer network may be configured differently using a combination of some or all

of the network elements listed above.

1.2 Audience for this document

This document is the Release Letter for the BCR4.3.1 load and is intended for Alcatel-

Lucent customers and Alcatel-Lucent functional groups.






2 RELATED DOCUMENTS

2.1 Reference Documents

BCR/SYS/INF/038475 V01 ED02 BCR4.3 Feature Planning Guide

BCR/FMS/INF/039025 V01 Small Cells Management System 4.0 Feature Planning Guide

BCR/DCL/APP/041694BCR4.3ALTPnoticeofAvailability

2.2 Applicable Documents

None

2.3 Abbreviations

AAA Authentication, Authorization, and Accounting

BCR BSR Cluster Release

BSG Base Station Signalling Gateway

BSR Base Station Router

CR Change Request = internal issue tracking number

FBSR Femto BSR

FFA FirstFieldApplication

FGW Femto Gateway

FOA First Office Application

HDM Home Device Manager

IOT Inter Operability Tests

IPC Iu Protocol Convertor

NE Network Element

NLT Network Level Test

NTP Network Timing Protocol

OS Operating System

POR Plan of Record

SCMS Small Cell Management System (aka FMS)






TIS Technology Introduction & Support

UE User Equipment

VPN Virtual Private Network

WMS Wireless Management System






3 SMALL CELL BCR4.3 DELIVERY

3.1 Load Highlights

This load is the main BCR4.3.1 load for FOA activities. This is a minor release update tothe main BCR4.3 FOA load delivering CR fixes, restriction removal and minor featurecontent

3.2 Load line up

The BCR4.3.1 load consists of the following equipment and associated software release.

The table below shows all the equipment for the ALU solution; some equipment is

optional per customer implementation.






Equipment Software version New

9361 Home Cell

9362 Enterprise Cell

9363 Metro Cell-Indoor

9364 Metro Cell-Outdoor

FBSR-04.03.41 Yes

9361 Home Cell Askey V3 FBSR-04.03.41.aky Yes

9365 BSR Gateway FGW-04.03.01.04.02 Yes

VPN Firewall Brick SW 9.4.171 +

SW 9.4.409

Yes

Iu Protocol Converter BSR-IPC- 03.00.01.05.01 No

Small Cell ManagementSystem (WMS / HDM)

SCMS-4.3.1.0-EP2:

FMS-FileServer-4.3.0.1_13w24HDM-3.1HDM-3.1.7HDM-4.1HDM-4.1.3HDM-4.1_13w44_linuxHDM-Adaptation-Kit-4.3.0.1_13w35WMS-For-Femto-4.3.1.0-EP1WMS-For-Femto-4.3.1.0-EP2WMS-For-Femto-4.3.1.0_13w36WPS-9952-3.0.20

Yes

NPO NPO55D46 No

8950 AAA 8.1.0 No

Brilliant NTP Server 1.3.0 No

Symmetricom NTP Server Symm-NTP-02.01.04.00 No

Golden Profile / Day 1 Data(BSR)

BCR4.3.1_MIM6.1_v306 Yes

Golden Profile / Day 1 Data(FGW)

FGW4.3_MIM6.0_v305 Yes

OS updates (see next page for details, new OS updatesfor this release are highlighted in bold)

Yes






Operating system information:

NetworkElement

Information

Small Cell Each delivery contains all required OS elements.

9365BSRGateway(FGW)

Software Requirements

TCL 8.6a2

netSnmp 5.7.1

IPMITool 1.8.11

IPMIUtil 2.3.2 (Sun only)

OS Requirements for existing installs:

RHEL 6.2

BSG-OS-RHEL-Feb-2013-v01 +

BSG-OS-RHEL-Apr-2013-v01

OS Requirements for new installs: RHEL 6.2 (New for BCR4.3)

BSG-OS-Install-BCR4.3-RHEL6.2-ATCA-SUN-PLT-Sept-2013-v02

VPNFirewallBrick

Software requirements

Microsoft® Windows Platform:

XP Pro SP2 and SP3, 2003 Server SP2, Vista SP2

o NTFS file system

Solaris Platform:

SunOS 5.10 under Solaris 10 with version Generic_127111-09

ALSMS-OS-Solaris-Jun-2010-01

Linux Platform:

OS Requirements for existing installs: RHEL 5 32-bit Linux

ALSMS-OS-RHEL-Oct-2011-v01 Patch +

ALSMS-OS-RHEL-Oct-2011-v02 Patch +

ALSMS-OS-RHEL-Mar-2012-v01 Patch +

ALSMS-OS-RHEL-Jun-2012-v01 Patch +

ALSMS-OS-RHEL-Nov-2012-v01 Patch +

ALSMS-OS-RHEL-Jul-2013-v01 Patch +

ALSMS-OS-RHEL-Sep-2013-v01 Patch

OS Requirements for new installs:

RHEL 5 32-bit Linux

ALSMS-OS-Install-RHEL-Sep-2013-v01

Iu ProtocolConverter

OS requirements for the cards used in IPCFMS - SunOS 01 5.9 Generic_122300-27 sun4u sparc SUNW,Netra-CP2300GICC 1.1 - VxWorks (for Artesyn Spiderware NP 8260) version 6.2Kernel: WIND version 2.8.CICC1.1 - VxWorks (for Artesyn CICC750F) version 6.2.

Kernel: WIND version 2.8.






Small CellManagement System(WMS /

HDM /Fileserver)

HDM and Fileserver Solaris:

SunOS 5.10 under Solaris 10 10/09 (Update 9)

The WMS OS version is contained in the Bootmedia delivered with the WMS

NetworkElement

Information

8950 AAA

Solaris Platform:

SunOS 5.10 under Solaris 10 with version Generic_127111-09

AAA-OS-Solaris-Jun-2010-01

Linux Platform:

OS Requirements for existing installs:

RHEL 5 32-bit Linux

AAA-OS-RHEL-Oct-2011-v01 Patch + AAA-OS-RHEL-Oct-2011-v02 Patch +

AAA-OS-RHEL-Mar-2012-v01 Patch +

AAA-OS-RHEL-Jun-2012-v01 Patch +

AAA-OS-RHEL-Nov-2012-v01 Patch +

AAA-OS-RHEL-Jul-2013-v01 Patch +

AAA-OS-RHEL-Sep-2013-v01 Patch

OS Requirements for new installs:

RHEL 5 32-bit Linux

AAA-OS-RHEL-Sep-2013-v01






Dependencies:

3.3 V1.0, V1.2 and V1.5 Versions

Note, V1.0, V1.2 and V1.5 CPEs will be supported with the BCR4.3 cluster. These CPEs

will run the BCR3.0 software versions and will not be upgraded to BCR4.3

Standalone Home CPE Enterprise CPE Metro CPE

V1.0

V1.2

V2-EC

V2-AC

V2-AC AWS

V2-EC-S

V1.5-EE

V2.2-EE

V2.1

V2-EO

V2-AO

V2-AI

LR1900

LR2100






3.4 Upgrade paths

Only the following configuration of NE loads has been certified in Alcatel-Lucent labs ascomprising this load. If applying this load, please plan to update all NEs to be consistentwith this reference configuration.

3.4.1 FBSR Upgrade Paths

From Release To Release

BCR3.0.3.8

(FBSR-03.00.84)

BCR4.3*

(FBSR-04.03.31.a.2)

BCR4.1.2.2

(FBSR-04.00.63.a.12)

BCR4.3*

(FBSR-04.03.31.a.2)

BCR3.0.3.8

(FBSR-02.60.77)

BCR4.3*

(FBSR-04.03.31.a.2)

BCR3.0.3.8

(FBSR-03.00.84)

BCR4.3.1

(FBSR-04.03.41)

BCR4.1.2.2

(FBSR-04.00.63.a.12)

BCR4.3.1

(FBSR-04.03.41)

BCR4.1.2.5

(FBSR-04.00.63.a.16)

BCR4.3.1

(FBSR-04.03.41)

BCR3.0.3.8

(FBSR-02.60.77)

BCR4.3.1

(FBSR-04.03.41)

BCR4.3

(FBSR-04.03.31.a.2)

BCR4.3.1

(FBSR-04.03.41)

* These particular paths are superseded by the equivalent path into BCR4.3.1

Can upgrade from any BCR2.6, BCR3.0, BCR4.1 load to 04.03.41






3.4.2 FGW Upgrade Paths

.


BCR3.0.3.8

(FBSR-03.00.84)

BCR4.3*

(FBSR-04.03.31.a.2)

BCR4.1.2.2

(FBSR-04.00.63.a.12)

BCR4.3*

(FBSR-04.03.31.a.2)

BCR3.0.3.8

(FBSR-02.60.77)

BCR4.3*

(FBSR-04.03.31.a.2)

BCR3.0.3.8

(FGW-03.00.01.23+

FGW-03.00.01.23.08 )

BCR4.3.1

(FGW-04.03.01.04+

FGW-04.03.01.04.02)

BCR4.1.2.2

(FGW-04.00.00.22+

FGW-04.00.00.22.04)

BCR4.3.1

(FGW-04.03.01.04+

FGW-04.03.01.04.02)

BCR4.1.2.5

(FGW-04.00.00.22+

FGW-04.00.00.22.06)

BCR4.3.1

(FGW-04.03.01.04+

FGW-04.03.01.04.02)

BCR4.3

(FGW-04.03.00.12+

FGW-04.03.00.12.03)

BCR4.3.1

(FGW-04.03.01.04+

FGW-04.03.01.04.02)

* These particular paths are superseded by the equivalent path into BCR4.3.1

3.4.3 ALVF-1200HS (Brick) Upgrade Paths

For reference (non Solaris based should stay on SW9.4.171 + SW 9.4.300B):


SW 9.4.171 +SW 9.4.300B

SW 9.4.171 +SW 9.4.409

SW 9.4.171 +

SW 9.4.346H

SW 9.4.171 +

SW 9.4.409

SW 9.4.171 +

SW 9.4.406

SW 9.4.171 +

SW 9.4.409






3.4.4 IPC Upgrade Paths

No change from last release load, for reference.


BSR-IPC- 02.04.02.02.02 BSR-IPC-03.00.01.05 +

BSR-IPC-03.00.01.05.01






3.4.5 SCMS (FMS) Upgrade Paths


BCR3.0.3.8

SCMS-3.0.1.2 MNCL2 EP2FMS-FileServer-3.0.1.0_12w03FMS-OS-SOLARIS1OHW0910SPARC _PATCH_V10_09_E15HDM-3.1 & HDM-3.1.5HDM-Adaptation-Kit-3.0.1.2_13w21WMS-For-Femto-3.0.1.2 +

WMS-For-Femto-3.0.1.2-EP1 +WMS-For-Femto-3.0.1.2-EP2WPS-MEDIA-V3.0-09-350-20130205

BCR4.3

SCMS-4.3.1.0-EP1

FMS-FileServer-4.3.0.1_13w24

HDM-3.1

HDM-3.1.7

HDM-4.1

HDM-4.1.2

HDM-4.1_linuxHDM-Adaptation-Kit-4.3.0.1_13w35WMS-For-Femto-4.3.1.0-EP1

WMS-For-Femto-4.3.1.0_13w36

WPS-9952-3.0.19.1

BCR4.1.2.2

SCMS-4.1.1.1 EP6 containing

FMS-FileServer-4.1.1.1_13w16HDM-3.1HDM-3.1.5HDM-4.0

HDM-4.1HDM-4.1.1HDM-Adaptation-Kit-4.1.1.1_13w18WMS-For-Femto-4.1.1.1WMS-For-Femto-4.1.1.1-EP1WMS-For-Femto-4.1.1.1-EP2WMS-For-Femto-4.1.1.1-EP3WMS-For-Femto-4.1.1.1-EP4WMS-For-Femto-4.1.1.1-EP5WPS-9952-3.0.16.1

BCR4.3

SCMS-4.3.1.0-EP1

FMS-FileServer-4.3.0.1_13w24HDM-3.1HDM-3.1.7HDM-4.1

HDM-4.1.2HDM-4.1_linuxHDM-Adaptation-Kit-4.3.0.1_13w35WMS-For-Femto-4.3.1.0-EP1WMS-For-Femto-4.3.1.0_13w36WPS-9952-3.0.19.1

BCR4.1.2.5


FMS-FileServer-4.1.1.1_13w16HDM-3.1HDM-3.1.5HDM-4.0HDM-4.1HDM-4.1.1HDM-Adaptation-Kit-4.1.1.1_13w18

BCR4.3

SCMS-4.3.1.0-EP1

FMS-FileServer-4.3.0.1_13w24HDM-3.1HDM-3.1.7HDM-4.1HDM-4.1.2HDM-4.1_linuxHDM-Adaptation-Kit-4.3.0.1_13w35






WMS-For-Femto-4.1.1.1WMS-For-Femto-4.1.1.1-EP1WMS-For-Femto-4.1.1.1-EP2WMS-For-Femto-4.1.1.1-EP3WMS-For-Femto-4.1.1.1-EP4

WMS-For-Femto-4.1.1.1-EP5WPS-9952-3.0.16.1

WMS-For-Femto-4.3.1.0-EP1WMS-For-Femto-4.3.1.0_13w36WPS-9952-3.0.19.1

BCR4.1.2.5


FMS-FileServer-4.1.1.1_13w16HDM-3.1HDM-3.1.5HDM-4.0HDM-4.1HDM-4.1.1HDM-Adaptation-Kit-4.1.1.1_13w18WMS-For-Femto-4.1.1.1

WMS-For-Femto-4.1.1.1-EP1WMS-For-Femto-4.1.1.1-EP2WMS-For-Femto-4.1.1.1-EP3WMS-For-Femto-4.1.1.1-EP4WMS-For-Femto-4.1.1.1-EP5WPS-9952-3.0.16.1

BCR4.3.1

SCMS-4.3.1.0-EP2

FMS-FileServer-4.3.0.1_13w24HDM-3.1HDM-3.1.7HDM-4.1HDM-4.1.3HDM-4.1_13w44_linuxHDM-Adaptation-Kit-4.3.0.1_13w35WMS-For-Femto-4.3.1.0-EP1

WMS-For-Femto-4.3.1.0-EP2WMS-For-Femto-4.3.1.0_13w36WPS-9952-3.0.20

BCR4.3

SCMS-4.3.1.0-EP1

FMS-FileServer-4.3.0.1_13w24HDM-3.1HDM-3.1.7

HDM-4.1HDM-4.1.2HDM-4.1_linuxHDM-Adaptation-Kit-4.3.0.1_13w35WMS-For-Femto-4.3.1.0-EP1WMS-For-Femto-4.3.1.0_13w36WPS-9952-3.0.19.1

BCR4.3.1

SCMS-4.3.1.0-EP2

FMS-FileServer-4.3.0.1_13w24HDM-3.1HDM-3.1.7

HDM-4.1HDM-4.1.3HDM-4.1_13w44_linuxHDM-Adaptation-Kit-4.3.0.1_13w35WMS-For-Femto-4.3.1.0-EP1WMS-For-Femto-4.3.1.0-EP2WMS-For-Femto-4.3.1.0_13w36WPS-9952-3.0.20

Note, HDM is upgraded via intermediate HDM4.0 (HDM3.1.5--->HDM4.0--->HDM4.1)






3.4.6 AAA Upgrade Paths

No change from last release maintenance load, for reference.

From Release To Release Upgrade Path

7.2.0 8.1.0 BCR4.1.x applicable

8.0.1 8.1.0 BCR3.x applicable

Official documentation can be obtained from https://infoproducts.alcatel-

lucent.com/aces/cgi-bin/dbaccessproddoc.cgi.edit?entryId=1-0000000002020&doctype=DOC

3.4.7 Brilliant Telecom Upgrade Paths

No change from last release maintenance load, for reference:


1.3.0 1.3.0

3.4.8 BSR Data Version Changes


BCR3.0 (MIM 6.0c) V039 BCR4.3_MIM6.1_v304

BCR4.1.2.2 (MIM6.1) v104 BCR4.3_MIM6.1_v304

BCR4.3_MIM6.1_v304 BCR4.3.1_MIM6.1_v306

3.4.1 FGW Data Version Changes


New in BCR4.3 FGW4.3_MIM6.0_v302

FGW4.3_MIM6.0_v302 FGW4.3_MIM6.0_v305

https://infoproducts.alcatel-lucent.com/aces/cgi-bin/dbaccessproddoc.cgi.edit?entryId=1-0000000002020&doctype=DOC













3.5 SCMS Release Notes

SCMS / HDM release information:

SCMS information:

Release Notes forSCMS04.3.pdf

HDM information: https://infoproducts.alcatel-lucent.com/aces/cgi-bin/dbaccessfilename.cgi/PUBS9YZ05167AAJAA_V1_HDM%204.1.3%20Patch%20Readme.pdf

3.6 NPO Release NotesNPO release information:

http://petrus.fr.alcatel-lucent.com/NPO/delivery/NPO55D46_Linux/index.htm

https://infoproducts.alcatel-lucent.com/aces/cgi-bin/dbaccessfilename.cgi/PUBS9YZ05167AAJAA_V1_HDM%204.1.3%20Patch%20Readme.pdf
















3.7 Fresh Install paths

This section details the install paths if a fresh install of the NE is required.

3.7.1 Small Cell Install Paths

Not applicable. Can fresh install any Small Cell load on to a new Small Cell.

3.7.2 9365 BSR Gateway Install Paths

OS and application software as detailed in Section 3.2

3.7.3 VPN Firewall Brick Install Paths

Red Hat Kick Start DVD ALSMS-OS-Install-RHEL-Sep-2013-v01 +

OS Patches as detailed in Section 3.2 +

Application software as detailed in Section 3.2

3.7.4 Iu Protocol Converter Install Paths


3.7.5 Small Cell Management System (SCMS) Install Paths


3.7.6 8950 AAA Install Paths

Red Hat Kick Start DVD ALSMS-OS-Install-RHEL-Sep-2013-v01 +

OS Patches as detailed in Section 3.2 +

Application software as detailed in Section 3.2

3.7.7 Brilliant Telecom Install Paths

Application software as detailed in Section 3.2.

3.7.8 Data Version Install Paths

Software as detailed in Section 3.2.






3.8 Feature Compliance

All potential issues impacting features are described in detail in Chapter 6 of this

document. All POR features are listed in the following sections.

3.8.1 Features without restrictions

FeatureID

Feature Title Comments Release FeatureIntroduced

122468Satellite connection as a BH shall besupported.

Refer to section 4 for mandatorycompliance information to deploythis feature.

BCR3.0

116498Multi-Objectives joint coverage optimization forFemto groups

The restrictions that were presentin BCR4.1 have been lifted inBCR4.3

NOTE: deployment guidelines forMOJO feature are required andfeature should be considered asrequiring controlled introduction ona per customer basis.

BCR4.1

34649 SCMS FGW Object Editor

Reported issue within CR 866227,modifying class 0 attributes withsetonline command form WICL isrestricted.

BCR4.1

172085 Call failure report enhancements part 1 Certified with BCR4.3 BCR4.3

172248 Release PS during Sim Bearer (CS+PS) Handover Certified with BCR4.3 BCR4.3

170891 Neighbour list optimization based on UEmeasurements and mobility reports

Certified with BCR4.3 BCR4.3

172133 PM Counter Enhancements for Call Drop andMobility part 1


171355 Coordinated self optimization in groups (SCMSonly)


168841 Additional PM counters - Part 2 Certified with BCR4.3 BCR4.3

171299 Brick Tunnels Capacity improvement.

Certified with BCR4.3

Brick 1200 R3 HS hardware andadditional tunnel licenses arerequired to provide the additionalcapacity.

BCR4.3

124168 DPDK support on 9365 BSR-GW

Certified with BCR4.3.1

Removed the need to manually

enable DPDK following upgrade(1059939) This step is nowautomated

BCR4.3

163819 flexible port bundling on 9365 BSR-GW

Certified with BCR4.3.1

intra switchover when the portsare disabled/blocked or whenreduction in bandwidth happenshas been corrected (1069288)

BCR4.3






Features with limitations

A feature with a limitation is an operational feature with known and acceptable issues,deployable to start First Office Application (FOA) activities and trials.

Limitations can be linked to testing limitation, issues or a specific configuration.

FeatureID

CR FeatureTitle Limitations description

Release FeatureIntroduced

113161

131828

118878

2ms TTI on E-DCH

Limitations remaining

• If CS & PS co-exist (on same UE), no PS on 2ms

If CS exists and PS comes in, establish on a

10ms PSIf PS exists and CS comes in, PS is“dropped” to allow CS. PS will re-establish and then it will be on setup on 10ms

• No Compressed Mode for PS on 2ms

Select DAHO instead of MAHO for 2ms TTIuser

• Max 2ms TTI user = 1

Lab results indicate sub-optimal throughputif max 2ms users > 1

If 2ms PS user exist already, subsequentusers on 10ms have better throughputcompared to if they were on 2ms

• Lab/demo only restriction on PC302 (Home

deployments)Having 2ms call means data rate on otherusers drop to 0K throughput.

BCR2.4

124168 1088805 DPDK supporton 9365 BSR-GW

There is a higher than expected SCTP/IP message rate to beexchanged between the DPDK application and the Linux KernelIP stack.

Load test analysis shows 30% CPU usage per core to process100,000 PDU/s

Sub system load test shows 20% CPU usage per core for

BCR4.3

159532LR Metro Cell Outdoor Traffic Management -Daisy Chain

Certified with BCR4.3.1 BCR4.3.1

163133 LR MCO MS Transport and QoS Management Certified with BCR4.3.1 BCR4.3.1

1711319764 Metro Cell Outdoor Wi-Fi AP - Wi-FiCommercial launch in BCR

Certified with BCR4.3.1 BCR4.3.1

171231WCDMA OAM support for MCO Wi-fi AP Certified with BCR4.3.1

BCR4.3.1

172448 WTA validation in BCR4Certified with BCR4.3.1 BCR4.3.1

170881170881 3G-4G & 3G Group sniffing co-ordination

Certification targeted Jan 2014

(This features uses featurescontained in BCR4.3.1 load forSMP integration)

BCR4.3.1

1-4708449/

1068292WMS profiles issues (enhancement)

Certification with BCR4.3.1 -Delivery of BSR profile changesmanagement during upgrade

BCR4.3.1

http://wsa.web.alcatel-lucent.com/reports/feature?PPM_ID=132761

http://wsa.web.alcatel-lucent.com/reports/feature?PPM_ID=132761






200000 PDU/s

While the behaviour is a system improvement over previousreleases further improvements can be realised by replacing theTAP interface with KNI interface, timeframe TBD






3.8.2 Features in restriction

A feature in restriction is a feature with at least one known issue that prevents it frombeing validated during FOA/trial activities.

This could be due to lack of testing in R&D, dependency on other undeliveredfeature/product, or even a gating feature bug.

Feature ID

CR FeatureTitle Restrictions description

Release FeatureIntroduced

158467

Support of 32PS usercapacity on V2Enterprise &Metro cell

32 User – UL restrictions:

• 32 x HSDPA Calls allowed but limit on UL DCH

Supported DL configuration will be

32 x R99 PS Users

32 x HSDPA PS Users (or any mix of

R99, HS users with in 32 user limit)Supported UL configuration will be

Limit UL DCH rate to 64K for allHSDPA calls

Limit UL DCH rate to 64K for R99calls, if there are >4 R99 calls on thesystem

32 User – SimBearer restrictions:

• 24 x SimBearer (CS+PS) calls allowed

Due to UL SF limitation, 32 users with allCS+PS if users are all on R99 cannot besupported

Supported configuration will be

24 Simbearer CS+PS Users + 8 x CSusers

15 R99 users can have Simbearer,beyond that extra simbearer is onlyallowed for HS users.

BCR3.0

163761

PKImanagement

for digitalcertificates

Integration with 9981 CMS application is not supported

PKI is only supported on the following hw:

V2 Home, V2.1 Enterprise, V2.2 Enterprise, V3

BCR4.3






SATELLITE BACKHAUL MANDATORY CHECKS

3.9 Mandatory Acceptance Criteria for Roll Out

Operator’s backhaul needs to meet our backhaul requirements (no exceptions) seesection 4.2.

Operators’ network needs to be on right BCR release (minimum BCR 3.03) and only V2.x orhigher CPE running on BCR 3.03 or later SW can be used.

Operator needs to agree the limitations and what is not supported see sections 4.3 and4.4.

Certification tests needs to be successfully passed.

If all conditions met successfully roll-out can start.

3.10 Backhaul Requirements (High Level View)

• Profile numbers:

o Maximum RTT (Femto-NTP server): ≤ 700 ms

o Maximum RTT (Femto-GW): ≤ 700 ms

o Maximum RTT (Femto-FMS): ≤ 700 ms

o Maximum packet loss: ≤ 0.5 %

o Maximum jitter: ≤ 10 ms

o Minimum guaranteed bandwidth (Femto-Gateway): 70 kbps per simultaneous call +50 kbps for the signalling

• MTU size: 1500 bytes






3.11 Limitations

V2.x or higher CPE hardware running on BCR 3.0.3 or later software needed.

Maximum one Femto per link/modem. No sharing of single link by multiple Femtos.

Femto over satellite backhaul will only support fixed location deployments e.g. cell in avillage, rural area.

Class of Service (CoS) based queuing has to be configured in the satellite equipment.

As it cannot be guaranteed that the satellite backhaul has sufficient bandwidth resources,voice call admission depends on how the satellite modem provides bandwidth capacity(important for emergency calls)

ALU KPI not compliant for satellite backhaul

Low data throughput for PS call (depends of satellite backhaul context)

3.12 Not Supported

• Location lock and national lock (disabled)

• Small Cell mobility over satellite e.g. small cell in ship, car, ferry, train

• Bandwidth measurements (disabled)

• Femto to Femto handover (disabled)• Femto groups






4 LIST OF SET-UP INFORMATION, KNOWNISSUES, WORKAROUNDS

This section identifies known issues, workarounds or required set-up information asidentified by the design, test and FOA teams. Issues are all tracked by Change Requests(CRs) according to the standard process. CRs are either:

Open Priority 1 (P1) and Priority 2 (P2) CRs, under investigation (i.e. issueconfirmed, but fix not yet available).

or

already planned for being fixed in next releases.

4.1 Silent Reboot issue (with change in CPU frequency CR906938)

4.1.1 Summary

In V2 Metro boards, a silent reboot is observed randomly (some units displayed frequentoccurrence and some very rarely or not at all). Note: Change also affects Light radioboards.

Investigation resulted in a hardware modification. However, a work around is available toachieve stability by reducing the CPU frequency.

PC3x3 ARM core by default boots at 600Mhz and during kernel boot the CPU frequencyis scaled up to 700Mhz as per the datasheet.

If we avoid frequency scaling and run at default boot speed of 600Mhz, the frequentlyrebooting units displayed better stability.

Hence this is a MIM controlled way of setting the CPU frequency to either 700Mhz(default) or 600Mhz (on operator's preference).

This CPU frequency change via MIM involves a system reboot and has to done during amaintenance window.

4.1.2 Impact of Frequency Change

This change affects both V2 Metro and Light Radio boards.

Minor impact for single UE / 64QAM / HSDPA / DL.

Minor impact for two UE / 64QAM / HSDPA / DL.

No voice quality impact.

4.1.3 How to do this via MIMsparePara11 - is the MIM parameter used to control this customization.

* If this attribute is empty no action will be taken

* The string entry values are case sensitive






4.1.4 How to verify current CPU Frequency

cat /proc/cpuinfo

...

BogoMIPS : 696.32

...(is the frequency in Mhz)

4.1.5 How to enforce 600Mhz CPU frequency

< Attr name="sparePara11">

<String>cpuClk=down</String>

</Attr >

1. If this attribute is empty no action will be taken

2. If this attribute contains “cpuClk=down” string and the board is already running at 600Mhzno action will be taken.

3. If this attribute contains “cpuClk=down” string and the board is running at 700Mhz, the

code triggers a reboot indication to OAM and OAM reboots the system.4. On next reboot the CPU Frequency will be 600Mhz. This can be verified with the cat

/proc/cpuinfo command.

4.1.6 How to revert back to 700Mhz from 600Mhz CPU frequency

< Attr name="sparePara11">

<String>cpuClk=up</String>

</Attr >

1. If this attribute contains “cpuClk=up” string and the board is running at 700Mhz no actionwill be taken.

2. If this attribute contains “cpuClk=up” string and the board is already running at 600Mhz,

the code triggers a reboot indication to OAM and OAM reboots system.3. On next reboot the CPU Frequency will be 700Mhz. This can be verified with the cat

/proc/cpuinfo command.

4.1.7 How to enforce 600Mhz on a specific unit

1. This has to be done via the same "sparePara11" with the same value ("cpuClk=down") asbefore but done via the Management system i.e. via a BSR_CONFIG message.

2. This procedure has to be done during a maintenance window as this involves a systemreboot to take effect.

4.2 BSR Spare Parameter Workarounds

Complete spare parameter deltas are detailed in release operational impact documents. Available via OLCS at the following location:

https://support.alcatel-lucent.com/portal/olcsHome.do









9YZ-05614-0017-RKZZAAlcatel-LucentSmallCell-ReleaseOperationalImpact-ReferenceGuide

9YZ-05614-0650-RKZZAAlcatel-LucentSmallCell-ReleaseOperationalImpact-ReferenceGuidefromBCR4.1toBCR4.3

4.2.1 Spare Parameter 9 (CR 910750)

Contains “intraBsrOwnEcNo” and “nbrBsrHOAbsThresh” for optimisation of intra frequencyhandover. Settings to be determined from deployment optimisation.

nbrBsrHOAbsThresh:

Defines the CPICH Ec/No threshold for BSR neighbour cells reported in UE measurementsat which handover will still be favoured to the BSR neighbour cell even when Macroneighbour cells are reported by the UE with higher CPICH Ec/No.

The syntax is “nbrBsrHOAbsThresh=<value>”, where the value is an integer with range [-24..0], default=-13, unit=dB. If not set, the value -24dB will be used and BSR neighbour

cells reported by the UE will always be favoured for handover before macro neighbourcells.

intraBsrOwnEcNo:

If measurement reports for event 1C contains better BSR neighbour cells, only attempthandover to those neighbour BSRs if CPICH Ec/Io reported for the serving cell is notgreater than intraBsrOwnEcNo.

The syntax is “intraBsrOwnEcNo=<value>” where <value> is an integer with range[-24..0].which corresponds to CPICH Ec/N0 of the serving cell specified in dB. If not set the value0dB will be used and handover will always be attempted to a better cell.

The setting of intraBsrOwnEcNo must also consider the setting ofBSR::psInterferenceThreshold to ensure that handover of a PS call will be attemptedbefore the Target Cell Protection (Interference Reduction) is activated.


RlctCphNoEncInf controls whether a target cell will support incoming relocation of a UE onwhich ciphering has been started but when the core network does not populate EncryptionInformation in the relocation request. Normally it is expected that Encryption Information ispopulated when ciphering has been started, however RlctCphNoEncInf set to true - allowsincoming handover to be supported for exception scenarios (for example Emergency calls

without ciphering, but when ciphering is already started on the UE).The Syntax is ““RlctCphNoEncInf=True”, if not set the value false will be used andrelocation request will be failed under the described scenario.







This is used for timer for handover failure improvement. It contains string‘tBsrRelocAudit=<valueT>; mBsrRelocAudit=<valueM>’ where <valueT> is a time in therange 0..30 seconds and <valueM> is a count of UL message in the range 0..30. If thestring is not present, <valueT> and <valueM> will default to 0.

valueT is the time in seconds the source cell waits before performing an audit for the UE todetermine if it is still present following the start of the handover procedure, if set to 0 thetimer is not started. valueM is the number of UL messages received on the source cellfollowing the start of the handover procedure that will trigger an audit to determine if the UEis still present, if valueT is non zero and valueM is set to 0, UL messages received on thesource cell will not trigger the audit. The UE audit will be performed on the earliest of thetimer expiry or the UL message limit being reached.


sparePara20 is used to set the file size for generating the neighbour list summaryinformation, e.g. it contains “neighFileSz =100000”, if unset (or set to 0), the file will not

be generated. Note the file is written to /tmp/measData.txt

4.2.5 Spare Parameter 23

SpareParam23 when set to ”HC=0,1,2,3,4;” provides a work around for CR 916077 wherethe SRNC ID is temporarily modified during small cell to small cell handover for certain UEtypes (Motorola Atrix 2 4G, MB 865, Samsung i997 Infuse 4G, Motorola Atrix 2 ME 865)

4.3 FMS Radius Password Server Configuration

4.3.1 How To Enable this Feature

To enable this future Small Cell Radius feature deployment: The feature is activated by

filling the shared secret into Small Cell " passwdSharedSecret" attribute, If the attribute is

left at its default value (zero-length string) then the feature will not be activated. If it is not

activated, then the Small Cell will fall back to using fixed passwords.

4.3.2 Nominal Case Scenario

Password string restriction: secret should be at least 16 bytes and less than 128 bytes." @this point [SEC EncryptSecret -entity FEMTO -secret "< anypassword >"]

From WICL write the command

SEC EncryptSecret -entity FEMTO -secret "< anypassword >"

(this will generate an encrypted password. Write this encoded password to the

FemtoCluster BSRClusterProfilepasswdSharedSecret






attribute and write the LDAP server IP address to the

FemtoCluster BSRClusterProfilepasswdServerFQDN attribute in the WMS database.)

Then register the femto and in the bulkcm file there will be an attribute

passwdSharedSecret containing the decoded password. Small Cell will use this file for

authentication. For successful authentication you should declare NAS at WMS. Running

the configure_radius.sh script.

1. Log in to the network management server with the Alcatel-Lucent account. Refer to

Logging in to an OAM server for assistance.

2. Enter: su - root

3. At the Password prompt, type: <password>

- where <password> is the password for the root user ID, the password should be at least

16 bytes but less than 128 bytes

4. Change directory to the RADIUS configuration script:cd /opt/nortel/shell/security

5. Type the following command:

./configure_radius.sh -subcomponent clients (Write the femto IP as the radius client IP,

sharedsecret as the decoded script, and Not_Specified as the radius NE type)

4.3.3 Which Condition It Should Fail

If the user doesn’t have sufficient rights to generate WICL script it should fail while running

the SEC EncryptSecret command.The user connects to FEMTO with a wrong user name and/or password,

NAS IP@ in not available in the NAS allowed list,

Inconsistent configuration between Radius server configuration and FEMTO provisioning(shared secret, ServerIP@), Radius server is stopped/ Ldap Server is stopped.

4.3.4 How To Configure WMS-For-Small Cell Server To Allow WIPSAccess Even If RADIUS Was Setup For Small Cells

bash-3.00# ./configure_radius.sh -subcomponent clientsNOTE: Configuring component radius

NOTE: Configuring clients subcomponentWhat action do you want to perform [list(default), add, remove]: addEnter radius client IP or subnet to ADD ( "end" to terminate ): 127.0.0.1Enter radius client shared secret []: <entered "alcatellucent" without quotes>Enter radius client type [(no default)Not_Specified rnc1500 poc Bts]: Not_SpecifiedNOTE: Adding Radius server client: 127.0.0.1Enter radius client IP or subnet to ADD ( "end" to terminate ): endNOTE: Done adding new radius client(s) successfully.






NOTE: Done configuring radius.bash-3.00#

4.4 Modify Femto Serial NumberFemtos with alpha-numeric serial numbers (older models) will need the serial numberchanging to numeric format:

On the Femto update the serial number using the programInventory command with – Aparameter, where 4012110001 is the new serial number eg:

root@femto-0Z1031022250:~# programInventory.vx -A 4012110001FSN: 4012110001

Clear femto DB:

root@femto-0Z1031022250:~#cd /mnt/mainfs/oam_data; rm –rf *

reboot femto:

root@femto-0Z1031022250:~#reboot

Wait for femto to come back and confirm it registers with HNM using new serial number,state should be “waiting for provisioning data”

Now update the WMS to reflect the correct serial number:

Make a work order to modify the femto serial number in WMS eg:

<?xml version='1.0' encoding='UTF-8'?><workorders><workorder name="new workorder" creationDate="2011-03-29 14:08:27.423 +0100"originator="" description=""><FemtoCluster id="55" model="OAM" version="OAM" clusterId="UMAINSERV1"><FemtoGroup id="12345"><Femto id="239" method="modify"><attributes><serialNumber>4012110001</serialNumber></attributes></Femto></FemtoGroup></FemtoCluster></workorder></workorders>bash-3.00#

Process the work order and confirm femto state in HNM changes to Active.






4.5 EDCH 2ms to be used in demos only

See section 3.7.2 “Features with limitations”

4.6 Macro to Femto Hand Over behaviour

During incoming Macro to Femto Hand Over, if the BSR baseband load check fails, thewhole procedure shall fail and no downgrading is applied. DBC downgrade of existingcalls is not performed to support the incoming handover. This is to avoid existing callsbeing impacted if a target cell has been incorrectly selected for the handover (due to PSCreuse, target cell selection may not be correct).

4.7 Modification of 32 user feature parameters

Modifying the below parameters from the supplied defaults is not recommended, as it couldlead to system instability when the 32 user feature is enabled:

Lcell::r99psUserThrsLcell::r99PsUserRate

Lcell::r5psUserTHrs

Lcell::R5PsUserRate

These parameter recommendations are designed to limit the BCR4.1 new capability tomore efficiently assign RAB rates on the UL given an improved UL baseband resourcesestimate algorithm.

In an ideal lab environment, with these parameters NOT set, then the benefit to the userwould be: Higher R99 RAB rates being allocated more often

However, in the real world environment more RF triggered overload problems could lead todropped calls/RRC connections and high risk signalling procedures

The parameters settings are designed to provide a greater emphasis on system stabilityrather than R99 RAB rates (fewer and fewer R99 UEs in the field) and the aboveparameters settings effectively LIMIT the UL RABs rates granted






5 LIST OF BCR4.3 CORRECTED ARS/CRS

5.1 9361 Home Cell, 9362 Enterprise Cell, 9363 Metro Cell-Indoor, 9364 Metro Cell-Outdoor

The following table provides the list of Change Requests (CRs) fixed.

CR AssistanceRequest

(AR)

Abstract

836522 Femto HO algorithm not reliable when duplicate PSCs are contained in neighbour list

977164CS Call Drop - repeated-integrity-checking-failure after ueMeasReport received (improved trace

only)

989183 PS Call Drop due to repeated-integrity-checking-failure after measurementReport following F2FHO

1022461 1-4543094 CS/PS RAB Drop KPI degradation after upgrading to BSR-03.00.76.a.9 from BSR-3.0.74 load

1023996 Security vulnerability VU-130625-1 CVE-2013-2174, Vulnerability in cURL and libcURL

1038459MR2603 - BSR does not obey new Timer "registrationWaitPeriod" for registration request[CMAS]

1038570 NLA not restarted after NLA crash leading to 15+ minute downtime

1047524 mahoNoCellTime supervision timer started at wrong place

1048705 1-4627180Security Mode Failure with incompatibleSimultaneousReconfiguration during closely associatedSecurity Mode procedures

1052096 measurementControl set bsic-VerificationRequired to required with no ARFCN ambiguity

1052717 Call Drop Rate KPI impact due to radioLinkReconfigurationReadyFailures

1054334 UBM PANIC on SIB19 encode failed, field 'physicalCellIdentity'

1054895 UBM PANIC on LCell_sIBUpdateCCCError

1064498 relocation procedure not triggered after PS RAB release for MRAB call

1068786 Incorrect pegging of counter RRC.ConnSRBDrop.CS

1072702 1-4708890 Enabling nationalLocationLock causing 3G Sniffing To Fail - Band 0 not supported by HW

1075259 RRC_ConnSRBDrop_PS is pegged incorrectly

1079627 RadioTemperature Alarms bouncing

1085200 Core file while running MPDP Sim Bearer tests on BCM board

1085610 1-4749728Zones files updating required as wrong ToD on the femtos, Israel winter time was delayed fromSept 8th to Oct 27th

1086595 F2F SIM bearer HO - Fwd SRNS Context not sent from source

1091460BCM board, CPU utilisation hits 100% and Panic is seen and femto reboots, while running 8 UE(3)MPDP SB test cases

1091798 Femto to Femto PS HO failed due to wrong SGSN user plane IP sent in DPAT Binding Request.

1091875 Unnecessary Failure_Indication signalling from femto with Invalid SAI during self-optimization

1092519 UE Context is not cleared in femto even if UE is in IDLE mode after stopping MPDP

1092823 1-4580509 PS RB Release message contains a number of optional IE's making it larger than it should be

1094029 Incorrect PositioningMethod populated in RANAP LocationReport for E911

1096776 1-4763726Call Drop due to timeout:tActiveSetUpdate, despite activeSetUpdateComplete received duringSecurityMode

1097629 RSCP value is missing in syslog of femto.






1100077 1-4764068Call Drop - CS Iu-ReleaseCommand not processed (no RB Release) duringPhysicalChannelReconfig

1112043 1-4810350 BSR::maximumAllowedNtpJitter threshold limit too restrictive for Satellite Backhaul

5.2 9365 BSR Gateway



(AR)Abstract

858427 Resiliency:subscriber test 19.04 reports less than 99 IMSI's output at WMS

1059939 DPDK is not coming up as default enabled after Kernel Upgrade from 3.0 to 4.3

1069288 [ATCA RTM Port Bundling] - Intra switchover needs to be done when 50% of the ports for aparticular cluster configuration is observed.

1076592 generic NAT proxy failing to create

1087921 4.3 network upgrade-> connectionType needs to be "logical" for for InterfaceType cnCSCP1 forboth SUN and ATCA.

5.1 VPN Firewall Brick



(AR)

Abstract

1325039 The previous default key algorithm and length in the Certificate Manager for creating a CSR wasRSA 1024. This is no longer considered secure enough so the default is changed to RSA 2048.

1325044 When using certificates to authenticate a tunnel with IKEv1, the Brick may leak memory.

1325051 Certain detailed log messages from within the actual IKEv2 protocol handler are not being sent.

1325053 If an IKEv2 tunnel has little to no data traffic and heartbeats (i.e Dead Peer Detection) are (is)enabled, then rekeys may fail if the rekey falls in the same polling cycle as the heartbeat attempt.

1325055 The Brick may leak memory when certificates are applied to the Brick or it may panic.

1325058 When a Femto BSR has an IKEV2 tunnel established with the Brick and the FBSR changes NATbindings, the Brick leaks memory.

1325063 When you change the certificate assigned to a TEP, the old one is not removed.

1325065 Brick may panic in certain IKEv2 error conditions

1325069 Loading a large CRL can cause packet processing to be interrupted for up to several seconds ona Brick model 1200r3 for very large CRLs(~5MB).

1325072 If there are multiple LAN-LAN tunnels defined that share some, but not all, of the remote hostaddresses, then the Brick may panic after failover.

1325074 If AAA is slow to respond because of Java garbage collection, ALSMS mistakenly thinks the AAAis down and switches to the secondary AAA server. The secondary does not respond to somemessages because they are part of authentication sessions that were started on the primary.

This causes ALSMS to think the secondary is down so it switches back to the primary. Thisbouncing continues until ALSMS is rebooted. ALSMS should not switch AAA servers in themiddle of an authentication session.

1325077 In an unusual race condition, the Brick may panic.

1325079 With heavy IKE load and/or certain error conditions, the Brick may panic.

1325082 Very rarely, model 1100A and 1200 Bricks with both manually keyed and IKE tunnels may panic.

1325086 The database auto-repair feature attempted to repair the database on a secondary ALSMS if itwas not able to sync with the primary ALSMS for more than 60 minutes. Unfortunately thisfeature sometimes caused the secondary to get stuck in a loop restarting services. This change






disables the auto-repair feature unless it is specifically enabled on the secondary ALSMS with"secondary.enableSelfRepair=true" in the config.ini file. The dbsetup utility may be used tomanually sync the secondary ALSMS database with the primary ALSMS if automaticsynchronization fails for some reason.

1325087 If the Brick has an IKEv1 tunnel established using certificates, it will panic when an apply isdone.

1325091 This change increases the performance of the Brick model 1200R3 Basic.13250831325093

If the Encryption Accelerator card fills up with Security Associations (SAs), the Brick will panic.The capacity is 262,000 SAs, so this is not normally reached, but it has been seen on thestandby in some unusual test scenarios. Additionally, the Brick may panic after it goes active.

132503513250641325080

This improves the number of tunnels per second that the Brick can establish - especially forGroup 5 and Group 14 Diffie-Hellman.

132505013250521325089

If you configure a client IKEV2 TEP to allow the Brick to create a second child SA, there weremultiple issues with the way the Brick handles them including creating incorrect traffic selectorsand deleting the wrong SA under certain circumstances.

132504013250421325043132504613250471325049

1325062

Performance improvements for UDP encapsulated IPSec traffic.

5.1 8950 AAAFor AAA list of Change Requests (CRs) fixed, please refer to the documentation link available in

section 3.4.6.

5.2 Small Cell Management System (SCMS)For SCMS list of Change Requests (CRs) fixed, please refer to the pdf file available in section 3.2

SCMS Release Notes.






6 LIST OF OPEN BCR4.3/4.3.1 ARS/CRS

The following sections detail information for all Network Elements. Some customers will nothave these Alcatel-Lucent elements in their network.

6.1 Femto Open CR / AR

CR / ARnumber

Sev Found In Targetdate for

resolution

FeatureName or

ValidationCriteria

Description

Description of missingfunctionality or reason for

blockage

Impact of missing functionality(implications and mitigation)

1060630

3 BCR4.3.1 TBD 172281 KPI: GSM macro to Openaccess Femto CS HO is notworking

GSM to Femto HO's will fail when usingSamsung and iPhone5 Ues, this works wiQualcomm phones

974478

3 BCR4.3.1 LR14.2.SC WIPS currently allows you to adda MetroDock MO child of BSR anda remoteInventory MO child ofMetroDock - it should not

Failure relates to WiPS constraint but reqa MIM-update which will not be updated inBCR4.x.

10619923 BCR4.3.1 TBD Low Throughput on LR1900 for

64QAM UDP downloadOccasional low throughput seen, subsequcalls throughput recovers to expected valu

1074395

3 BCR4.3.1 TBD CP regression:Less uplinkthroughput is observed for R6 cat4UE in 2msec on PC333

Cat4 UE for 2ms TTI is giving throughput 1.2 mbps, Cat6 Ues give good throughput(meeting requirements)expectation is UE population in the field ishigher for Cat6, in addition as 2ms TTI is oavailable for 1 user per Femto, the frequewhere this degardation of throughput is visis very low

1119021

3 BCR4.3.1 TBD Regression: 4 CS call MAHO toMacro (Inter) - Only 2 / 3completes successfully

Only two, sometimes three of the calls arehanded over. The other calls are droppedThis is only applicable to Broadcom baseCPEs

6.2 9365 BSR Gateway Open CR / AR

CR / ARnumber


resolution

FeatureName or

ValidationCriteria

Description


blockage


1-4830001

3 BCR4.3 TBD FOA

FOA BCR4.3: FGW constraintcheck failed for superLAC whendownload new DB from WMS

When bulkCM file is downloaded from WMto FGW, some checks are performed on Fand it errors on superLAC values which isoptional. In case when superLAC is send <unset>, though download was successfu

there was problem in sending the dbStatuWMS (setting of AVCN).

1-48279583 BCR4.3 TBD FOA FOA BCR4.3:Malban Card losing

eth2 config and hostname afterfirmware upgrade

1-4827931

3 BCR4.3 TBD FOA

FOA BCR4.3:bono doesn't bootup after firmware upgrade

Workaround is to change the boot order(before doing the reboot of BONO),To read boot order list:

/usr/board/tools/bios/read_bol.sh

http://destgsu0682.de.alcatel-lucent.com/UMTS/TOOLS/ARToolsConverged/common/ARDetail.php?ARId=1-4830001&generation=All











To change the boot order list:

/usr/board/tools/bios/mod_bol.sh

1111435

3 BCR4.3.1 BCR4.3.1maint

[SUN Resiliency]:Changes are notgetting reflected to Satndby BSGafter connecting the internodecable in SUN system.

It may result in outage in case ofswitchover/failover scenarios due to the Odata sync issue. Scenario worked properlyBCR4.3 release and issue observed only SUN but not on ATCA.

1117174


NLT-BCR-4.3.1:In Releasedocument bono.cfg configurationsection two different nameserverip is mentioned wrongly for eth2and eth3

This is document CR only, User has to mothe bono.cfg file before doing freshinstallation.

1102639


[Stability]shelfoam.exe core dumpobserved with minimal load run

ATCA shelf level alarms will not be reportduring this time(3-5 sec)Workaround :shelfoam.exe will restartautomatically

1117034


4.3.1 network upgrade-> SCTPassociation with newly comingFGW not happened up to it cameas active during KU to .04 load.

When BSG is upgraded, an 7 minute delahas been introduced between upgrade ofindividual gateway cards. The purpose ofdelay is to enable the active warm standb

feature to ensure that the upgrade can ocwithout an extended loss of service. (Notthat any calls active at the point when thegateway fails over as part of upgrade will dropped, but the amount of time during whnew calls can’t be established will be limitto a few seconds, and the small cells will nstop radiating).

1111435


[SUN Resiliency]:Changes are notgetting reflected to Standby BSGafter disconnecting andreconnecting the internode cablein SUN system.

Impact is to Sun based FGW systems on

1107245


DPDK PM NicTxPkts[core][port]incorrectly incremented

This counter may give a lower than expecvalue for the number of outgoing PDUs. T

counter is not used in current KPI calculat

6.1 Small Cell Management System (SCMS) Open CR / AR

CR / ARnumber


resolution

FeatureName or

ValidationCriteria

Description


blockage


1-4843909 2BCR4.3 TBD FOA FOA BCR4.3: passwordChange

tool in WMS fails to updatewiclsysaccount password

1-4842352 3

BCR4.3 TBD FOA FOA BCR4.3: WPS check fail for

securityGatewayFemtoVPNSubnet - set to NULL failed

1-4837897 2BCR4.3 TBD FOA FOA BCR4.3: Activation of any

service impacting FGW workordershould prompt a warning

1-4837516 2

BCR4.3 TBD FOA FOA BCR4.3: WMS onlyaccepting admin/admin for FGWSSH launch while FGW adminpassword has changed












1-4835841 2BCR4.3 TBD FOA FOA BCR4.3: WMS fails to launch

WO for FGW due to optionalparameter errors

1-4831385 2BCR4.3 TBD FOA FOA BCR4.3: Access to 4.3

FGWs (FGW2 and FGW4) viaSSH from WMS fails.

1-4827672 2BCR4.3 TBD FOA FOA BCR4.3: WICL commands

cannot save output in/home/customer directories

1-4827445 3BCR4.3 TBD FOA FOA BCR4.3: Some WICL

commands (utran list) do not work.

1-4825564 3BCR4.3 TBD FOA FOA BCR4.3: Light System

Monitor on WMS FS - installationprocedure needed

1-4825524 2BCR4.3 TBD FOA FOA BCR4.3: Default user and

groups cannot be deleted in NG-SEC after upgrade to BCR4.3

1-4825289 3BCR4.3 TBD FOA FOA BCR4.3: Bundle Import

button accessible even if importprocess on-going

1-4825238 2BCR4.3 TBD FOA FOA BCR4.3: Admin process

stopped with core dump

1-4813290 2BCR4.3 TBD FOA FFA BCR4.3: Failure after 1st

sync point during WMS SWupgrade

1-4843909 2BCR4.3 TBD FOA FOA BCR4.3: passwordChange

tool in WMS fails to updatewiclsysaccount password

11129293

BCR4.3.1 BCR4.3.1maint

[OAMRegression] Synthetic andThreshold alarms are not raised.

11073723 BCR4.3.1 BCR4.3.1

maint Trigger CM File creation” Action isnot working in HDM-4.1.3

End of Document



















