8650 sdm 4.2.1.1 release notes - nokia networks support cristel backup with external server on mcas...

All rights reserved. Passing on and copying of this

document, use and communication of its contents

not permitted without written authorization from Alcatel-Lucent.

3BL98707IBAAFMZZA Ed05 1

8650 SDM 4.2.1.1

Release Notes





HISTORY................................................................................................................................................. 3

APPLICABILITY ..................................................................................................................................... 3

1 SUPPORTED SYSTEMS................................................................................................................. 4

2 PRODUCT IDENTIFICATION.......................................................................................................... 4

3 NEW FUNCTIONS DELIVERED ..................................................................................................... 6

4 PLATFORM DEPENDENCIES........................................................................................................ 7

4.1 MCAS.................................................................................................................................. 7 4.2 UDM.................................................................................................................................... 9

5 CONFIGURATIONS SUPPORTED............................................................................................... 10

6 DOCUMENTATION ....................................................................................................................... 10

6.1 Customer Documentation .............................................................................................. 10 6.2 Construction Documentation ........................................................................................ 10

7 KNOWN ISSUES LIST .................................................................................................................. 10

7.1 SDM .................................................................................................................................. 10 7.2 DDM.................................................................................................................................. 14 7.3 mCAS ............................................................................................................................... 16 7.4 Installation ....................................................................................................................... 17 7.5 Software Upgrade ........................................................................................................... 17

7.5.1 8650 SDM 3.1.4 to 8650 SDM 4.2.1.1 software upgrade ................................. 17 7.5.2 8650 SDM 4.2.1 to 8650 SDM 4.2.1.1 software upgrade ................................. 17 7.5.3 8650 SDM 4.2.0.1 to 8650 SDM 4.2.1.1 software upgrade .............................. 17

8 RESTRICTIONS LIST.................................................................................................................... 17

8.1 SDM .................................................................................................................................. 17 8.2 DDM.................................................................................................................................. 18 8.3 SYSTEM PERFORMANCE.............................................................................................. 19 8.4 SYSTEM OVERLOAD...................................................................................................... 19 8.5 SYSTEM Flexible Provisioning...................................................................................... 19 8.6 UPGRADE ........................................................................................................................ 20

9 INSTALLATION PROCEDURE..................................................................................................... 20

9.1 First Install ....................................................................................................................... 20 9.2 Upgrade............................................................................................................................ 20

10 PROCEDURE TO GET SDM VERSION INFO.............................................................................. 21

11 INTERFACE CHANGE .................................................................................................................. 21

12 COMPATIBILITY ........................................................................................................................... 21





REFERENCED DOCUMENTS

[1] 8650 SDM 4.2.1 Installation Guide 3BL95949IBAARJZZA

[2] 8650 SDM 4.2.1 Customer Data book 3BL95947IBAADSZZA

[3] 8650 SDM Upgrade MPI from 4.2.0.1 to 4.2.1 3BL98725IBABRJZZA

[4] 8650 SDM Upgrade MPI from 4.2.0.1 to 4.2.1 via COM 3BL98725IBAARJZZA

[5] End to End Procedure for 8650 SDM Upgrade from 4.2.0.1 to 4.2.1 3BL98725IBACRJZZA

[6] 8650 SDM 0-downtime upgrade MPI from 3.1.4 to 4.2.1 3BL98717IBAARJZZA

[7] End to End Procedure for 8650 SDM

0-downtime Upgrade from 3.1.4 to 4.2.1 3BL98717IBABRJZZA

[8] 8650 SDM 4.2.1.1 Functional Restrictions and Residual Anomalies (FRRA) 3BL98707IBZZDEZZA

[9] 8650 SDM 4.2.1.1 Fault Reports and Change Requests corrected 3BL98707IBZZFMZZA

[10] 8650 SDM EBE Installation Guide 3BL98727IBAARJZZA

[11] SDM Upgrade MPI for R4.2.1 to R4.2.1.1 3BL98735IBAARJZZA

HISTORY

Ed 0.1 For 11/30 CI delivery 11/30/2013

Ed 01 SDM 4.2.1 DR4 delivery 01/31/2014

Ed 02 Change ATCA firmware version to 2.90.5.0. 03/14/2014

Ed 03 SDM 4.2.1.1 DR4 delivery 05/15/2014

Ed 04 add JAVA version and browser restriction, and Alert 14-0570 delivery

06/06/2014

Ed 05 Change SDM 4.2.0.1 to 4.2.1.1 upgrade tool name to reflect the timestamp

07/01/2014

APPLICABILITY

First installation

Upgrade from 8650 SDM 3.1.4 to 4.2.1.1

Upgrade from 8650 SDM 4.2.0.1 to 4.2.1.1

Upgrade from 8650 SDM 4.2.1 to 4.2.1.1





1 SUPPORTED SYSTEMS

This delivery apply to 8650 SDM product only.

8650 SDM Expert 4.2.1.1 delivery is not included and it’s in a separate document, please refer to GEDI

3BL96322HCZZRLZZA for SDM Expert 4.2.1.1 release notes.

Distributed Configuration with ATCA V2 BONO, Rouzic hardware and compact configuration with ATCA V2

Rouzic hardware are supported in this release.

The delivery note is adapted to this context. In particular, only relevant FRs are included.

2 PRODUCT IDENTIFICATION

This delivery of product, 8650 SDM 4.2.1.1 is stored on ALED with the packages listed in the table below

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-SDM-FE.tar

c66afe78941e793c8cb3785825e2070a

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-SDM-BE.tar

2caf21ef8cd5cb5b0e04f725c8f5929f

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-SDM-COMPACT.tar

333fba70eb7217c05e640fbbcd3f81bf

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-SDM-FE_STRIPED.tar

bd478643f9c239839aae90f9e02c5a94

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-SDM-COMPACT_STRIPED.tar

a5d417e8be73f3855c61fe4b27e86da8

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-SDM-TOOLS.tar

83e571bef0c3640142b009ab97000f7e

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-SDM-DATA.tar

df41f13c0f70f941228df7834f692793

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-SDM-HEALTH.tar

a40ceac6f4bce49fc1699cdc096fa735

/8650SDM/4.2.1.1/ATCA_V2/Alert_14-0570/8650SDM-4.2.1-2014-06-03-15-SDM-TOOLKIT.zip

e295b368085bd9309e533488074b1ce1

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-iLB.tar

b0254d8dd327e408860c853b601888ca

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-

UpgTool314to421_CMMPV2.tar.gz

507f9f27f678fe85fb0637f923fe1b9f






UpgTool314to421_CSMPV2.tar.gz

3470889e91ca02e6060c04a14c721c8c


UpgTool314to421_DISTRIBUTED.tar.gz

7e21d7fbd086e0816de3d0437b6dda08



296bd2dd3a931ef05c26eac8685cd18e

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-ADAX_Drivers.tar

5d904e140c7ff0309ec2e74b662fe75f

/8650SDM/4.2.1.1/ATCA_V2/DR4_Deliveries/8650SDM-4.2.1-2014-04-24-21-efix.tar

c2cfff1954ea5518f313dc98fb5fadbc

Go to https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=98633 then select 4.2.1.1 -> ATCA-V2-> DR4_Deliveries 8650SDM-4.2.1-2014-06-03-15-SDM-TOOLKIT.zip was delivered by Alert 14-0570, get it by : https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=98633 then select 4.2.1.1 -> ATCA-V2-> Alert_14-0570

OR go to 8650 SDM 4.2.1.1 Solution Page https://services.support.alcatel-lucent.com/services/sdm/index.cgi?path=Documents/8650_SDM/4.2.1.1/V4.2.1.1.html

Package Name Description Checksum (md5sum)

8650SDM-4.2.1-2014-04-24-21-SDM-

BE.tar

Application Package on

BE

2caf21ef8cd5cb5b0e04f725c8f5929f

8650SDM-4.2.1-2014-04-24-21-SDM-

FE.tar


FE

c66afe78941e793c8cb3785825e2070a

8650SDM-4.2.1-2014-04-24-21-SDM-

FE_STRIPED.tar


FE with strip

compilation option.

bd478643f9c239839aae90f9e02c5a94

8650SDM-4.2.1-2014-04-24-21-SDM-

TOOLS.tar

SDM Configuration

Tools Package

83e571bef0c3640142b009ab97000f7e

8650SDM-4.2.1-2014-04-24-21-SDM-

DATA.tar

Sample Data Package df41f13c0f70f941228df7834f692793

8650SDM-4.2.1-2014-04-24-21-SDM-

HEALTH.tar

SDM Health Check

Tool

a40ceac6f4bce49fc1699cdc096fa735

8650SDM-4.2.1-2014-04-24-21-iLB.tar SDM internal load

balancer package.

b0254d8dd327e408860c853b601888ca

8650SDM-4.2.1-2014-04-24-21-SDM-

COMPACT.tar

Application package for

compact configuration

333fba70eb7217c05e640fbbcd3f81bf

https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=98633


https://services.support.alcatel-lucent.com/services/sdm/index.cgi?path=Documents/8650_SDM/4.2.1/V4.2.1.1.html

https://services.support.alcatel-lucent.com/services/sdm/index.cgi?path=Documents/8650_SDM/4.2.1/V4.2.1.1.html





8650SDM-4.2.1-2014-04-24-21-SDM-

COMPACT_STRIPED.tar

Application package for

compact configuration

with strip compilation

option

a5d417e8be73f3855c61fe4b27e86da8

8650SDM-4.2.1-2014-04-24-21-

UpgTool314to421_CMMPV2.tar.gz

8650 SDM 3.1.4 to

8650 SDM 4.2.1.1

upgrade tool package

for Compact Mated-pair

Medium configuration

507f9f27f678fe85fb0637f923fe1b9f

8650SDM-4.2.1-2014-04-24-21-

UpgTool314to421_CSMPV2.tar.gz

8650 SDM 3.1.4 to

8650 SDM 4.2.1.1


for Compact Mated-pair

Small configuration

3470889e91ca02e6060c04a14c721c8c

8650SDM-4.2.1-2014-04-24-21-


8650 SDM 3.1.4 to

8650 SDM 4.2.1.1


for Distributed

configuration

7e21d7fbd086e0816de3d0437b6dda08

8650SDM-4.2.1-2014-06-30-21-


8650 SDM 4.2.0.1 to

8650 SDM 4.2.1.1


for Distributed

configuration

296bd2dd3a931ef05c26eac8685cd18e

8650SDM-4.2.1-2014-06-03-15-SDM-

TOOLKIT.zip

Development Kit

(Client CD)

e295b368085bd9309e533488074b1ce1

8650SDM-4.2.1-2014-04-24-21-

ADAX_Drivers.tar

ADAX drivers

packages

5d904e140c7ff0309ec2e74b662fe75f

8650SDM-4.2.1-2014-04-24-21-efix.tar eFix patch of mCAS

3.2.8

c2cfff1954ea5518f313dc98fb5fadbc

The above “8650SDM-4.2.1-2014-04-24-21-SDM-DATA.tar” is delivered as a sample data package. Note that

customers or service team need to customize the data included in the sample data package accordingly

during site installation. Please refer to [2] for more detail.

The above “8650SDM-4.2.1-2014-06-03-15-SDM-TOOLKIT.zip” is delivered as the development kit package

(Client CD) which provides information of online help documents, exception dictionary, and provisioning

interface description of this product.

3 NEW FUNCTIONS DELIVERED

Below features are delivered in 8650 SDM 4.2.1.1:

Feature Description FFRD

73415 Flexible Provisioning (SOAP/LDAP) for new LDAP Schema and federation use case C183628

72218 Porting EIR from Tomix to mCAS C184301

72219 Porting MNP from Tomix to mCAS C184389

72593 Support of existing rouzic configuration and IP configuration NA

http://inu.ih.lucent.com/fep/cgi-bin/featdetails.pl?feature=72218

http://inserv.ih.lucent.com/compas-cgi/wwwcompas?prodid=184301








74322 Performance Enhancement with USSD Forward C184192

74390 Subscription Type (S-Type) support in SDM-HLR: Orange-Spain C186725

74410 GSM HLR porting gaps completion C182920

74422 Porting from R3.1 (3-Way Replication, ADD) C186130

74461 SDM HLR - CAMEL O-CSI and T-CSI per PLMN Control (Vf-Global) C186299

74760 SMS Barring length check - SDM GSM HLR :VF C163719

74761 Voicemail enhancement for VF UK :NONE VM Type C162381

75031 Support defense mechanism when there is problem on GDMP connection C187047

75000 SDM - EBE configuration & installation support C186346

74182 zero downtime upgrade path from SDM 3.1 to SDM 4.2.1 C184152

74181 Support Cristel backup with external server on mCAS platform C183920

74441 Support SDM upgrade from R4.2 to R4.2.1 C185257

72655 Support node extension in distributed configuration C182692

75571 Interworking with Mavenir solution C189012

75520 Default CFD (Call Forwarding) timer C188959

75444 Short term expansion of RAS/RASP C188482

74788 mCAS: GTT setting not possible with mCAS 3.2 (Support GTT for IPSP-IPSP configuration) C187468

75527 mCAS: Extension of GT Address Information length C189041

4 PLATFORM DEPENDENCIES

4.1 MCAS

New Install Packages – MCAS3.2.8 R30SU2BP base packages and release note are available at: https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=132983 Select: mCAS-3.2.8_R30SU2BP-Software Select: mCAS-3.2.8_R30SU2BP-New-Install Select: mCAS 3.2.8 R30SU2BP New Install Common Packages <next>

which consists of the following software packages (md5sum files also included): COMMON PACKAGES: MCAS Middleware: MasterDisk.tar.gz � File Size: 834335334 � File Sum (md5sum): cd69a04bb033374c9a783b2ddfb1bf38 Audit Siteinfo: audit_siteinfo � File Size: 52124 � File Sum (md5sum): 188dedec4dc4f62f0a4f5a8832cabf92 Golden Disk: golddisk.tgz � File Size: 644760931 � File Sum (md5sum): 58524a89c2d979855a84e6038b820be4 USB Flash Drive Ram Disk: initrd.gz � File Size: 29178743 � File Sum (md5sum): d6f0fd744641c4071375439c5bb584d8

Siteinfo Template: siteinfo.template











� File Size: 48690 � File Sum (md5sum): 1f239dc1419feb745f5e93e93ac6fbcb

USB Flash Drive Linux boot Loader Config File: syslinux.cfg � File Size: 449 � File Sum (md5sum): 242eebac04a0cb5ddfc8899513987c85 USB Flash Drive Linux Boot Loader Program (MS-DOS/Windows): syslinux.exe � File Size: 30208 � File Sum (md5sum): acf4d50d5d5b2d4d27bf60b8528d3d38 Linux Kernel: vmlinuz � File Size: 4048208 � File Sum (md5sum): d65f333961f2f1074fae289b0e0e6a43

OPTIONAL PACKAGES: Go to the following web site to download the packages: https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=132983 Select: mCAS-3.2.8_R30SU2BP-Software Select: mCAS-3.2.8_R30SU2BP-New-Install Select: mCAS 3.2.8 R30SU2BP New Install <name of the package> <next>

SS7config PACKAGE: thirdParty.SS7config.tar.gz � File Size: 5664 � File Sum (md5sum): d5efd41c4266340a15ae523f579fb324 ASR PACKAGE: thirdParty.ASR5350.tar.gz � File Size: 200044386 � File Sum (md5sum): 564cd569d39855cee2e67a6c3f0049d3

Upgrade Packages – OAM scripts packages 30.25 version with upgrade procedure is available on OLCS. https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=132983

Select: OAM Scripts Packages Select: R30 OAM Scripts Select: OAMscripts_MCAS_30.25 OAM Package or later version

Release Notes (MCAS MW, ASR and DDM): Select: MCAS-3.2-Software Select: MCAS-3.2-Patches Select: MCAS-3.2.8 R30SU2BP Patch MCAS Release Notes <next>

Select: MCAS 3.2.8 R30SU2BP Patch MCAS Release Notes

MCAS3.2.8 R30SU2BP patch packages and release note are available at : https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=132983 Select: MCAS-3.2-Software Select: MCAS-3.2-Patches Select: MCAS-3.2.8_R30SU2BP-Patch Select: MCAS 3.2.8 R30SU2BP Patch Common Packages <next>

which consists of the following software packages (md5sum files also included): COMMON PACKAGES: OS Upgrade: OSupgrade_3.2.6.tgz � File Size: 920702324 � File Sum (md5sum): cc2a8b71d222a3713c41c88b3ecc0b7a MCAS IAS Middleware: ltiasr30-b0208.tar.gz � File Size: 405207656






� File Sum (md5sum): fa9d2d445a56b869e955fe48a28c558f SU Data: SU_3.2.8.data � File Size: 1423 � File Sum (md5sum): 43c9e5f49be7333b1af5c9c75ba16cdc Catalog: catalog_3.2.8 � File Size: 515 � File Sum (md5sum): 499e67b991125cc249cd7e923017abe3

OPTIONAL PACKAGES: Go to the following web site to download the packages: https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=132983 Select: MCAS-3.2-Software Select: MCAS-3.2-Patches Select: MCAS-3.2.8_R30SU2BP-Patch

Select: MCAS 3.2.8 R30SU2BP Patch <name of the package> <next> SS7config PACKAGE: thirdParty.SS7config.tar.gz � File Size: 5664 � File Sum (md5sum): d5efd41c4266340a15ae523f579fb324 ASR5350 PACKAGE: thirdParty.ASR5350.tar.gz � File Size: 200044386 � File Sum (md5sum): 564cd569d39855cee2e67a6c3f0049d3

Installation Engineering Handbook (IEH) is available at: https://infoproducts.alcatel-lucent.com/aces/cgi-bin/dbaccessproddoc.cgi.edit?entryId=1-0000000003817&doctype=DOC

Select - MCAS (modular Converged Application Server) ; release = 3.2 - Manuals and Guides - Search for 270-700-300

INSTALLATION ENGINEERING HANDBOOK - 575 Installation and Operation Practices for MiLife and modular Converged Application Server Products (270-700-300)

ATCA Firmware Package https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=132983

Select: MCAS Firmware Select: ATCA Select: FW_2.90.5.0 Select: ATCA FW 2.90.5.0 Select: <Next> Package: fw_atcav2-2.90.5.0.zip MD5SUM : ef010f4ee6f915f297b97cfa60ffcf36

4.2 UDM

This delivery aligns with DDM90.00.12.06 and FlexPro v2.14.9. The packages and delivery notes can be got from: https://download-apac.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=166383

Select: 2.0 Select: UDM-2014-03-31-DDMr90.00.12.06-01.el6.tar.gz MD5SUM: 5d31f10f8245752ad7c51d3a2141f8dc

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



https://support.alcatel-lucent.com/portal/productContent.do?productId=null&entryId=1-0000000003817&type=alpha



https://download-apac.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=166383





Select: UDM-2014-03-31-DDM_sdk_r90.00.12.06-01.el6.tgz MD5SUM: d099ad16035e84a1f9cc009fb40b7f5a

For FlexPro v2.14.9:

Select: UDM-2014-01-30-thirdParty.FlexPro-v2.14.9.tar.gz

MD5SUM: e77fdd33a4255f32773904c47ee6f64e

5 CONFIGURATIONS SUPPORTED

This product supports distributed ATCAv2 BONO, distributed and compact ATCAv2 Rouzic.

6 DOCUMENTATION

All documents delivered can be obtained from GEDI. MCAS and UDM documents can be found from

links provided in section 4

6.1 Customer Documentation

8650 SDM 4.2.1 customer documentation catalogue with reference 3BL98707IBAAADZZA can be

obtained from GEDI.

The customer documentation can be downloaded from OLCS:

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

0000000003265&doctype=DOC Select: SDM 4.2.1

6.2 Construction Documentation

8650 SDM 4.2.1.1 MPI and ATS documentation catalogue can be obtained from GEDI:

• Catalogue of the collection 8650 SDM 4.2.1.1 – MPI 3BL98707IBMAADZZA

• Catalogue of the collection 8650 SDM 4.2.1 – ATS 3BL98707IBTAADZZA

The MPI and ATS are available in GEDI: http://gedi.ln.cit.alcatel.fr/GEDI/, use Menu "Projects"->"Access all documents of a project" and select SDM 4.2.1 project (domain: MOBILE CORE, sub-domain: PRODUCT, syste: 8650 SDM)

7 KNOWN ISSUES LIST

7.1 SDM

Registration Number

Customer severity

Short Description CustomerImpact Workaround

SDMA01FAG290056

G1 SU from R421 to R4211. AUC entry failed to be created by given error frameId 33025 after SU.

This is the same issue as AR 1-5082606 ”MVNO Authentication failure on admin requests”. The impact is : AUC entry creation might fail after BE switchover.

Add one new record for ‘AUC_OAM_IMSI_Management_FirstImsiRange’ entry and then delete it from OAM GUI : HSS > AUC > IMSI_Range_Mana



http://bcv00s0d.cit.alcatel.fr/gold/owa/pck_aw_frcr_display2.frcr_display_main?frcr_id=SDMA01FAG290056






gement > AUC_OAM_IMSI_Management_FirstImsiRange. After waiting for 7 seconds, AUC related entries can be created successfully.

SDMA01FAG290170

G2 [audit RT]SSD inconsistency check didn't report difference if SSD timestamp on main NRG is older than on non-main NRG.

SSD inconsistency check didn't report difference from GUI if SSD timestamp on main NRG is older than on non-main NRG. This is common issue for all configurations and it can be reproduced. Use case :

Manually change the timestamp on

non-main NRG to make main NRG

timestamp is older. It’s desired

that SSD inconsistency report on

GUI displays the difference, but

it didn’t.

No workaround

SDMA01FAG289474

G2 CPU of PDLSM/PDLSU is not balanced with multi-instance on BONO lab

For BONO configuration, testing result showed that CPUs of PDLSM/PDLSU on some blades were much higher than the same process on other blades. This was only happened in Bono configuration and it can be reproduced. Use case :

Measure maximum dynamic capacity

for MNP traffic without WAN delay

Measure maximum dynamic capacity

for EIR without WAN delay.

There were 3 PDLSU and 3 PDLSM,

CPUs of PDLSM/PDLSU were un-

balanced on some blades.

No workaround

SDMA01FAG290200

G2 OamCOMM core dump during rouzic FE running Nessus security scan, on R4.2.1

There might be OamComm coredump on Rouzic configuration when running Nessus security scan. This was only observed in distributed Rouzic configuration, not happened every time.

No workaround

SDMA01FAG290212

G2 MAR message return 5001 when Send database request error.

HSS MAR returns incorrect code 5001 (DIAMETER_USER_UNKNOWN) for an existing subsriber when there is DB overload. This is a common issue for all

No workaround





http://bcv00s0d.cit.alcatel.fr/gold/owa/pck_aw_frcr_display2.frcr_display_main?frcr_id=SDMA01CAG290039








configuration. Use Case :

Add wan delay at GDMP network,

launch HSS traffic to make BE

overload. When DB overload, MAR

handling met "Send database

request error." for a subscriber

in DB. It returned

5001(DIAMETER_USER_UNKNOWN). This

result code is wrong.

SDMA01FAG290145

G3 [4211 CP73 LTE/LEIR overload] - LTE/LEIR traffic to two NRGs, add 50ms WAN-Delay to NRG1, only LEIR traffic to NRG2 got 3004, LTE traffic to NRG2 didn't got 3004.

LEIR message overload reporting is a little earlier than LTE message at the beginning of overload. This issue was reported from a Rouzic environment, but it should be a common issue. Use Case :

Two NRGs.

Launched 2000 TPS LTE&LEIR

traffic1 to NRG1, 2000 TPS

LTE&LEIR traffic2 to NRG2.

No overload, no 3004.

Added 50 ms WAN-Delay to NRG1, no

WAN-Delay to NRG2. All types of

Traffic1 LTE&LEIR got 3004.

Traffic2 There was 3004 for LEIR

message, no for LTE message.

No workaround

SDMA01FAG290190

G3 G2 overload ThresholdCrossed applOverloadRTG2-0 can't be cleared even if GSM traffic stops

G2 overload alarm applOverloadRTG2-0 was triggered when there was overload, but it can not be cleared when there is no overload any more. This happened in Rouzic configuraiton and can not be reproduced every time. Use Case :

During testing split-brain case,

thre are some GSM traffics

running. Due to split-brain

failure-over and switchover, G2

overload alarm was triggered.

But these alarms was not cleared

when there was no overload any

more. After 24 hours, system auto

cleared after later testing.

No workaround

SDMA01FAG290157

G3 HLR add counter twice in degraded broadcast

If HLR BE overload happens in broadcast, and loadDataProfile gets null entry due to BE overload, the message will be dropped, but the

No workaround









counters in table SDM_MEAS_HLR_BE_IN will not be added except SAI. Only the measurement for SAI in this table is added normally. This can be reproduced for any configuration environment. The same issue was not observed in SDM3.1.4. Use case :

Clear index server so the DB

request will broadcast to all

NRGs. Run HLR traffic(any message

type could be used except

SAI) and trigger BE overload on

the subscription data located

NRG, then message will be dropped

due to degraded broadcast. Check

the actually dropped messages'

number and the measurement in

SDM_MEAS_HLR_BE_IN table in the

same time interval.





7.2 DDM

Registration Number

Customer severity


SDMA01FAG288795

G2 When index server is null, DB thread overflow will happen frequently

When DB blade is restarted, while there are some index server broadcast, all RT blades will go to overload status, 1 blade in each FE will keep in overload status finally. This issue will impact QoS when a DB blade is failed. Overload can recover in 10 seconds, failover time is 2 seconds. This happened in Rouzic configuration and it can be reproduced. Use Case :

Restart SDM SPA to clear index

server, then reboot DB blade.

DB thread overflow will happen

then and i twill recover in 10

seconds.

No workaround

SDMA01FAG290132

G2 there are gdmp core when master BE is restarted

Observed GDMP coredump when master BE is restarted, which results in auto switch over. This was happened in Rouzic configuration and it can be reproduced.

No workaround

SDMA01FAG290151

G2 [4211 DB access thread overload]-DB access thread management raised overflow log even the pending threads didn't reach threshold

UTH overload log will be observed while DB access thread number don't reach threshold. This is because overload is triggered at the time so the number dropped, minor issue. This issue was reported from a Rouzic environment, but it should be a common issue. Use case :

Two NRGs.

Launched 2000 TPS HSS traffic1 to

NRG1, 2000 TPS HSS traffic2 to

NRG2.

No overload, no 3004.

Added 250 ms WAN-Delay to NRG1,

no WAN-Delay to NRG2. All types

of traffic to NRG1 and NRG2 got

3004. .

No workaround











7.3 mCAS

Registration Number Customer severity


SDMA01FAG289482

G1 AR 1-5011284: Upgrade: SDM 3.1.4 to 4.2.1 On ROUZIC. Following the installation of new AuC algo libs (using MPI 3BL 96947 IAAA RJZZA) - sigtran associations were OOS

FE sigtran association state before AuC lib install was IS, but the state will remain OOS after new AuC installation and SPA restarts. It's worksing correctly when in SIGTRAN configuration AS –SG, but it's not working in an AS-AS mode.

No workaround

SDMA01FAG290172

G1 IO blades rebooting for ADAX driver issue

IO blades restart with large ss7 configuration during stability run. WA is replacing new ADAX driver and changing unused associations as MOOS

Step 1 : untar 8650SDM-4.2.1-2014-04-24-21-ADAX_Drivers.tar (refer to section 2 in this document for package location), command : tar –xvf 8650SDM-4.2.1-2014-04-24-21-ADAX_Drivers.tar Sample output :

adax-LiS-2.21.1-1-RedHat-6.4-x86-64bit.rpm adax-sctp-1.58-1-RedHat-EL6-x86-64bit-LiS2.21.1.rpm copyright.txt repAdaxRpm.readme.txt version.txt Step 2 : Refer to procedures in above step 1 output file ‘repAdaxRpm.readme.txt’ for driver replacement/backout. Note : The driver replacement is persistent across blade reboot and pilot switch-over. a) Refer to document [1] section

6.11 for details concerning new installation.

b) Refer to document [6] section 8.7 for details concerning SDM 3.1.4 to 4.2.1.1 upgrade.

c) Refer to document [11] section 6.2 for details concerning SDM 4.2.1 to 4.2.1.1 upgrade.

d) Refer to document [3] section 6.5 for details concerning SDM 4.2.0.1 to 4.2.1.1 upgrade.









SDMA01FAG290490

G3 Failover time of iLB on compact lab can not meet the requirement

When reboot malban, switchover time is 20s which can not meet 10s in requirement. The same issue is on SDM 3.x and SDM4.2.1.1. This is for Rouzic Compact configuraiton only. It can be reproduced.

No workaround

7.4 Installation

Refer to section 7.3 of this document for IO blades restart issue addressed by SDMA01FAG290172.

For new installation, it’s required to apply mCAS 3.2.8 eFix patch, refer to document [1] section 5.1.1.3 for

details.

7.5 Software Upgrade

7.5.1 8650 SDM 3.1.4 to 8650 SDM 4.2.1.1 software upgrade


It’s required to apply mCAS 3.2.8 eFix patch, refer to document [7] section 8.7 for details.

7.5.2 8650 SDM 4.2.1 to 8650 SDM 4.2.1.1 software upgrade


7.5.3 8650 SDM 4.2.0.1 to 8650 SDM 4.2.1.1 software upgrade


8 RESTRICTIONS LIST

8.1 SDM

Following applications are in restriction in 8650 SDM 4.2.1.1 compared to other releases

� No support for HP blade in this release.

� To make OAM GUI available, below browser and versions are supported

o JRE Version from 1.6.20 to 1.6.43

o Firefox from 4.0.1 to 22.0.1

o Internet Explorer 7,8,9

o Use Firefox to connect to ASR GUI. It is not possible to open several different NE log with

Internet Explorer

� mCAS does not support incoming ANSI GTT translation.






� For diskless rouzic, ramdisk has only 2GB space. User can not generate additional files under

following directories at pilot station to prevent from directory being full which results in rsync failure

on diskless FE: /PLATsoftware/cs /opt/config/servers/<r-c-s>/ramdisk /opt/config/servers/<r-c-s>/local

� Diameter SCIM for HLR application not supported(not required any more) � Radius interface for IMS HSS application interface not supported � IMS HSS external MAP interface to HLR not supported � ATCAv1 is not supported � Split Brain feature supports manual and auto modes for 2-way NRG configuration in previous

releases. From SDM 4.2.1, 3-way NRG configuration is also supported, but only for manual mode. This is also specified from feature requirements.

8.2 DDM

1. SDM has 2 entries’ RDNs can not be provisioned as max length:

a) Entry AuthChar

DN: authCharId,aucFunctionId=1,managedElementId=HSS1

authCharId type is varstring(128).

Limitation: “authCharId” is limited to be 127 instead of 128.

When provisioning AuthChar entry on OAM GUI:

Common Data Management > HSS > AUC > Authentication_Characteristics >

AUC_OAM_AuthChar_Characteristics. Data

Ensure “authCharId” doesn’t exceed 127 in length.

Impact:

If full size (128) of authCharId is provisioned, PRIDs linked to this entry will have incorrect data, then

authentication will be failed (MAA returns 5012).

b) Entry ExtendedSubscriber

DN: extendedSubscriberId,subscriptionFunctionId=1,managedElementId=HSS1

extendedSubscriberId type is varstring(32).

Limitation: “extendedSubscriberId” is limited to be 31 instead of 32.

When provisioning ExtendedSubscriber entry on OAM GUI: HLR Subscriber Management > HSS > Subscription > Subscription > SUB_OAM_EXTSUB

Ensure “extendedSubscriberId” doesn’t exceed 31 in length.

Impact:

If full size (32) of ExtendedSubscriber is provisioned, the ICCID (“Integrate

circuit card identity”, it’s an unique serial number of a SIM card, and usually printed on the back of SIM

card in plain text) will be incorrect. These data are for VzW as requested by feature 73337(ICCID Support

for VzW), so this impacts VzW customer only.

2. For LdapServer, there is a restriction on multi-valued attribute, the number of values should not

exceeds 100.





This will impact on querying data thru SDMExpert or LDAP client directly.

USE CASE:

1. Create one RestrictionList (120).

SUB,SharedProfile,MS_OAM_Shared_SubscriptionRestriction

restrictionListId=120,mobileNetworkCodeId=01,mobileCountryCodeId=208,plmnFunctionId=1,managedElementId

=HSS1

restrictionListCategory,"PLMNLIST"

restrictionIsdn,"34"

2. Create one GsmServiceProfile.

SUB,Subscription,SUB_OAM_BasicSubscription

gsmServiceProfileId=1,suMSubscriptionProfileId=1,suMSubscriberProfileId=1188880099,subscriptionFunctionId=1,

managedElementId=HSS1

#SUB_OAM_BasicSubscription

mobileCountryCodeId,"208"

mobileNetworkCodeId,"01"

mSubIdentificationNumberId,"1188880099"

MainSNwithBearerService,"33-007-1188899:TELEPHON"

MainSNwithBearerService,"33-007-1188899:GPRS"

networkAccessMode,"BOTH"

accessRestrictionData,"GANA"

accessRestrictionData,"IHSPANA"

#GPRS

packetMsAddressList,"203-6484DC01-11-0"

3. Modify csRestrictionListNum for this GsmServiceProfile is 120.

SUB,RoamingRestriction,MS_OAM_RoamingRestriction

roamingRestricServiceProfileId=1,gsmServiceProfileId=1,suMSubscriptionProfileId=1,suMSubscriberProfileId=1188

880099,subscriptionFunctionId=1,managedElementId=HSS1

RoamingRestrictionType,"PLMNLIST",REPLACE

csRestrictionListNum,120,ADD_VALUES

4. Query this data by the following command. Error will be thrown out.

Command:

/usr/dhafw/tools/ldap/bin/ldapsearch -P3 -x -v -w secret -h 172.25.126.13 -p 20389 -D

"cn=manager,managedElementId=HSS1" -b

"subscriberNumberId=1188899,nationalDestinationCodeId=007,countryCodeId=33,countryFunctionId=1,managed

ElementId=HSS1" -E 1.3.6.1.4.1.637.81.2.10.2=:ANSIPROFILE_MSISDN_IMS -s base "objectclass=*"

Error:

text: asciiGet on eps3gppRestrictionLinkList(JOINT_IDX[121] given maxval : 100 too short

8.3 SYSTEM PERFORMANCE

Not applicable.

8.4 SYSTEM OVERLOAD

Not applicable

8.5 SYSTEM Flexible Provisioning

Not applicable





8.6 UPGRADE

1. For upgrade of 8650 SDM 4.2.1 to 4.2.1.1, only ATCA V2 Bono Distributed configuration and on

ATCA V2 Rouzic Distributed configuration with manual procedure are supported.

2. For zero downtime upgrade from 8650 SDM 3.1.4 to 4.2.1.1, only ATCA V2 Rouzic Distributed

configuration is supported.

9 INSTALLATION PROCEDURE

9.1 First Install

Please refer to document [1] for the installation procedure.

9.2 Upgrade

Please refer to documents [6] [7] for 8650 SDM 3.1.4 to 8650 SDM 4.2.1 upgrade. Patch 13-0947c is required

to be installed on 8650 SDM 3.1.4 before the upgrade of 8650 SDM 3.1.4 to 8650 SDM 4.2.1 upgrade.

Please refer to documents [11] for 8650 SDM 4.2.1 to 8650 SDM 4.2.1.1 upgrade.





10 PROCEDURE TO GET SDM VERSION INFO

After installation complete, run the following command to check application version:

[Prompt] cat /sn/sps/[SPA Name]/ServiceDataVersion

ServiceVersion:421

Note: “SPA Name” can be “OAM421”, “SDM421”, and “OAMBE421” corresponding to the application SPA

installed.

11 INTERFACE CHANGE

North bound interface evolutions are documented in the following document available under OLCS:

• Delta Parameters (OAM Provisioning) between 8650 SDM 3.1 and 8650 SDM 4.2.1

3BL98789IBABPCZZA Edition 02

• Delta Parameters (OAM Provisioning) between 8650 SDM 4.2 and 8650 SDM 4.2.1

3BL98789IBAAPCZZA Edition 02

• SDM delta alarms and counters between 3.1 and 4.2.1 3BL98742IBAAPCZZA Edition 02

12 COMPATIBILITY

This 8650 SDM 4.2.1.1 delivery aligns with SDM 3.1 IAP04, including alerts 12-1601 to 12-1601e, 13-0694a,

13-0970a and 13-0947a to 13-0947c, 14-0229, 14-0249a and 14-0249b, for GSM/UMTS/LTE/HSS/MNP/EIR

applications.

This 8650 SDM 4.2.1.1 delivery aligns with SDM 4.0 IAP002 for IMS HSS application.

This 8650 SDM 4.2.1.1 delivery aligns with SDM 4.1.1 DR4 for GSM/UMTS/LTE/IMS HSS applications

This 8650 SDM 4.2.1.1 delivery aligns with SDM 4.2.0.1, up to alert 14-0065 for GSM/UMTS/LTE/IMS HSS

applications

COM release alignment for SDM 4.2.1.1 is COM 3.3.1. Note: There is no PWT testing of SDM 4.2.1.1 and

COM 3.3.1.

END OF DOCUMENT