usc application software r3.5-mr release notes · ranap_enhanced_relocation_request ... for air...

Cisco Systems, Inc. www.cisco.com

USC Application Software R3.5-MR

Release Notes First Published: 30 March 2015

Last Updated: 08 Feb 2017

Document Version: 16.04

Document Reference: USC-44-54-016

http://www.cisco.com/

USC Application Software R3.5-MR ▄

USC-44-54-016 ii

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO

CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE

BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.

USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN

THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS

REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT

YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of

California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved.

Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE

SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM

ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING,

USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR

INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA

ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses

and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the

document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content

is unintentional and coincidental.

All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should be

referred to for latest version.

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at

www.cisco.com/go/offices.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other

countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks

mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship

between Cisco and any other company. (1110R)

© 2016-2017 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/offices

http://www.cisco.com/go/trademarks


USC-44-54-016 iii

Contents

1 INTRODUCTION ................................................................................................................................................. 5

2 SYSTEM REQUIREMENTS .............................................................................................................................. 6

2.1 COMPONENTS ................................................................................................................................................ 6 2.2 COMPATIBILITY .............................................................................................................................................. 6

3 NEW AND CHANGED INFORMATION .......................................................................................................... 7

3.1 DATABASE VALUES ........................................................................................................................................ 9 3.1.1 Changes to Default Values ................................................................................................................ 9 3.1.2 Modified Parameters (BV3.5.10.14 BV3.5.12.15) ................................................................... 10 3.1.3 Modified parameters (BV3.5.12.15 BV3.5.12.18) .................................................................... 10 3.1.4 Modified parameters (BV3.5.12.18 BV3.5.12.20) .................................................................... 12 3.1.5 Modified parameters (BV3.5.12.20 BV3.5.12.21) .................................................................... 12 3.1.6 Modified parameters (BV3.5.12.21 BV3.5.12.26) .................................................................... 13

3.2 CUSTOMER FIXES INCLUDED IN THIS RELEASE ........................................................................................... 13 3.2.1 BV3.5.12.21-26 .................................................................................................................................. 13 3.2.2 BV3.5.12.20-21 .................................................................................................................................. 14 3.2.3 BV3.5.12.19-20 .................................................................................................................................. 16 3.2.4 BV3.5.12.18-19 .................................................................................................................................. 16 3.2.5 BV3.5.12.15-18 .................................................................................................................................. 16 3.2.6 BV3.5.12.14-15 .................................................................................................................................. 17 3.2.7 BV3.5.12.12-14 .................................................................................................................................. 17 3.2.8 BV3.5.12.9-11 .................................................................................................................................... 17 3.2.9 BV3.5.12.7-8 ...................................................................................................................................... 18 3.2.10 BV3.5.12.1-6 ...................................................................................................................................... 18 3.2.11 Improvements .................................................................................................................................... 18

4 INSTALLATION AND UPGRADE NOTES ................................................................................................... 20

4.1 INSTALLATION ............................................................................................................................................... 20 4.2 UPGRADE PATHS ......................................................................................................................................... 20

5 OPEN AND RESOLVED BUGS ..................................................................................................................... 21

5.1 OPEN INTERNAL ISSUES .............................................................................................................................. 21

6 RELATED DOCUMENTATION ...................................................................................................................... 22

7 OBTAINING DOCUMENTATION AND SUBMITTING A SERVICE REQUEST ..................................... 22

USC Application Software R3.5-MR Release Notes

Introduction


USC-44-54-016 iv


Introduction


USC-44-54-016 5

1 Introduction

This document describes the Cisco Universal Small Cell software product release for R3.5-MR.

Important: Software for the major, minor and maintenance releases of the Universal Small

Cell 3000, 5000, 7000 and 9000 product families are available from CloudBaseTM, not from cisco.com Software Center.

The following are some of the key highlights of USC Application Software R3.5-MR:

Feature Id Feature Title

[FEAT-1102] Interworking with 3GPP Release 10 Compliance Macro RNC

[FEAT-1040] 900Mhz WCDMA Sniff (licensed feature)

[FEAT-1236] Support for Single DRAM G3-Compact HW

[FEAT-800] WB-AMR (HD-Voice)

[FEAT-1235] Geo-Redundancy for SeGW

[FEAT-1237] Manual provisioning for Edge Node Discovery (provides Grid capabilities across LAN subnets)

[FEAT-1238] IMSI Blacklisting

[FEAT-1239] Support RTCP in same deployment as Iurh

Table 1: Features for R3.5-MR

Further information about USC R3.5-MR features can be found in Section 3.


System Requirements


USC-44-54-016 6

2 System Requirements

2.1 Components

Software Version: BV3.5.12.26

Database Version: 1.2.244

Factory Recovery Platform: V2.99.9

RMS: RMS 4.1.0 MR, RMS 5.1, RMS 5.1 MR Hotfix01

2.2 Compatibility

The USC Application Software R3.5-MR is compatible with solution releases SCS3.0 (RMS 4.1.0 MR), SCS4.0 (RMS 4.1.0 MR), SCS4.1 (RMS 5.1), and SCS4.2 (RMS 5.1. MR Hotfix01).

The following table shows the supported and dependent products (HNB HW):

[1] Licence restrictions apply to these 16 call hardware variants.

Product Notes:

SO16 is restricted as HSDPA+ and ActiveSON/Iurh

USC933x is restricted just as ActiveSON/Iurh


New and Changed Information

▄ USC Application Software R3.5-MR

7 USC-44-54-016

3 New and Changed Information

The following section lists the functionality delivered as part of R3.5-MR.

Feature Id Feature Title Description L

icen

ce

Co

ntro

l

Iuh

US

C3

x

US

C5

x

US

C7

x

US

C9

x

[FEAT-1102] Interworking with 3GPP Release 10 Compliance Macro RNC

This feature introduces support of srncRelocation up to Release 10 from macro or HNB cells either via CN or Iurh, which means the USC is able to parse later versions of srncRelocation (Rel_8, Rel_9 and Rel_10) received in RANAP_Relocation_Request (CN based) or RANAP_Enhanced_Relocation_Request (Iurh based). There is no change required for air interface messages or procedures because the USC prepares the handover message (e.g. RadioBearerReconfiguration) based on RAB Requirement (not based on srncRelocation Release or UE Release version) as legacy.

N Y Y Y Y Y

[FEAT-1236] Support for Single DRAM G3-Compact HW

Reinstate support for the G3-Compact device, which was made incompatible through the changes to the ASN.1 compiler optimisations in R3.5.

N Y N N N N

[FEAT-1040] 900Mhz WCDMA Sniff This feature upgrades the USC’s current capabilities (under license) and supports network listening of UMTS Band 8 (900MHz). This feature also extends all legacy procedures to include support for the reporting and auto-configuration of UMTS Band 8 (900MHz) neighbours that are detected via network listen.

Y Y Y Y Y Y

[FEAT-800] WB-AMR (HD-Voice) The USC supports Wide band AMR as per TS26.171 with a specific of RAB combinations. The combinations that are supported are : - 6.6, 8.85, and 12.65 kbit/s (Mandatory multi-rate configuration)

Y Y Y Y Y Y

[FEAT-1235] Geo-Redundancy for SeGW

Geo-redundancy in the Small Cell solution is the ability for the deployment of Small Cells to switch to different backup secondary network nodes in the event that one or more of the primary nodes are unavailable.

N Y Y Y Y Y

[FEAT-1237] Manual provisioning for Edge Node Discovery (provides Grid capabilities across LAN subnets)

ActiveSON peer discovery is implemented by a Broadcast message that is limited to the current LAN subnet. This feature allows the manual provisioning with the IP address of elements of the grid that reside on other LAN subnets. When peer discovery occurs to one element on each other subnet, the subsequent sharing of peer details will allow connection to other grid elements on the other subnet to occur automatically. The result is a fully meshed Grid across multiple LAN subnets.

N Y N Y Y N




USC-44-54-016 8

Feature Id Feature Title Description

Lic

en

ce

Co

ntro

l

Iuh

US

C3

x

US

C5

x

US

C7

x

US

C9

x

[FEAT-1238] IMSI Blacklisting This feature allows the manual provisioning of a blacklist of UE. This is provisioned by a comma separated list of up to 15 IMSI. The UE will be LAU rejected with the LAU cause given by the NAS cause defined in NASCauseForUEReject.

N Y Y Y Y Y

[FEAT-1239] RTCP Support (including Iurh Grid)

This feature provides support for RTCP. This feature has a dependency on HNBGW support of RTCP.

N Y Y Y Y Y




9 USC-44-54-016

3.1 Database Values

The following changes to the default values in the database have been made since BV3.5.10.14. The default values have been modified in line with configuration settings from the RMS and supported functionalities. The database version that supports this load has been updated to UBS-21-23-311 Ubiquisys FAP Database Specification 1.2.243, from which the TR-69/ZMS visible parameters UBS-21-23-316 CISCO HMS FAP Database Specification.xls (Auto Generated) is derived

3.1.1 Changes to Default Values

Parameter Name Parameter Type

Min Value

Max Value Default Value

Reboot Required

HMS Access

Comments

InternetGatewayDevice.Services.FAPService.1.REM.WCDMAFDD

object read This object contains parameters relating to radio environment measurement capabilities for the UMTS system.

ScanTimeout

uint32

0

4294967295 3600

no reboot

read/write

Specifies the time-out value in seconds, measured from the start of the REM scan, before the REM scan will time out.

InternetGatewayDevice.Services.FAPService.1.AccessMgmt

object read "This object contains parameters relating to Access Management (ACL, CSG, LIA).

X_UBIQUISYS_COM_HandoutMode

enumeration

0 2 "All users"

no reboot read/write "Handout Mode:

InternetGatewayDevice.Services.FAPService.1.AccessMgmt.X_UBIQUISYS_COM_PSOffload.ZAPRoute object Default ZAP routing information

DataOffloadEnabled boolean 0 1 0 reboot read/write Configures whether PS data Offload is enabled or not for ZAPRoute rules.

Enable0 boolean 0 1 0 reboot read/write Enables/disables the PSOffload functionality.










InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP object read/write

This object contains parameters relating to the cell level configuration for FDD mode FAP.

X_UBIQUISYS_COM_PSInteractiveBackgroundPreemptionEnabled boolean 0 1 1 no reboot read/write

Enables (1) or disables (0) the feature to allow pre-emption of a PS-interactive/background RAB from CELL_DCH into CELL_FACH to make room for a higher priority RAB (CS or PS streaming)

InternetGatewayDevice.Services.FAPService.1.PerfMgmt.X_UBIQUISYS_COM_Reports.CallSetupQuality

object read "Counters that are associated with call setup quality.

NBAMRtoWBAMRAttempt

uint32 0 6 1 no reboot read/write "RAB modification from NBAMR to WBAMR attempts for CS Voice calls

WBAMRtoNBAMRAttempt

uint32 0 6 1 no reboot read/write "RAB modification from WBAMR to NBAMR attempts for CS Voice calls

NBAMRtoWBAMRSuccess

uint32 0 6 1 no reboot read/write "RAB modification from NBAMR to WBAMR success for CS Voice calls

WBAMRtoNBAMRSuccess

uint32 0 6 1 no reboot read/write RAB modification from WBAMR to NBAMR success for CS Voice calls




USC-44-54-016 10

3.1.2 Modified Parameters (BV3.5.10.14 BV3.5.12.15)

The following highlighted database fields have been amended:


Min Value

Max Value

Default Value

Reboot Required

HMS Access

Comments

InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_GeoRedundancy

object

LastUsedSecGWServer enumeration 0 3 "Unknown"

no reboot read Indication of which SecGW the HNB last connected to

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas

object read This object contains parameters relating to the inter-freq HO control parameters.

HysteresisEvent2b uint32 0 29 4 no reboot read/write "Defines the hysteresis for inter-freq HO measurement when the UE is in Cell-DCH state.

HysteresisEvent2d uint32 0 29 4 no reboot read/write "Defines the hysteresis for inter-freq HO measurement when the UE is in Cell-DCH state.

HysteresisEvent2f uint32 0 29 4 no reboot read/write "Defines the hysteresis for inter-freq HO measurement when the UE is in Cell-DCH state.

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.FrequencyConfig multiobject 0 12

FrequencyConfigNumberOfEntries read/write

Table containing optional configuration for each DL frequency specified in InternetGatewayDevice.Services.FAPService.1.CellConfig. UMTS.RAN.FDDFAP.NeighborListInUse. If an entry of UARFCNDL in this table exists in InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse then the value of X_UBIQUISYS_COM_CellMobilityCriterion is overwritten with value from NeighbourListType. If an entry does not exist in this table for a given entry in the InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse parameter then the value of X_UBIQUISYS_COM_CellMobilityCriterion retains the default value specified for parameter X_UBIQUISYS_COM_CellMobilityCriterion in table InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse

InternetGatewayDevice.Services.FAPService.1.Transport.RealTime

object read This object contains parameters relating to Real Time Transport using RTP.

RTCPEnable boolean 0 1 0 no reboot read/write Enable or disable RTCP. Note this parameter is deprecated and has no effect.

3.1.3 Modified parameters (BV3.5.12.15 BV3.5.12.18)


Min Value

Max Value

Default Value

Reboot Required

HMS Access

Comments

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF

object

read/write This object contains parameters relating to the RF configuration.

MaxFAPTxPower string 0 64 "-14.0..5.0" no reboot read/write

Defines the maximum transmission power allowed on the FAP, maximum value for the linear sum of the power of all downlink physical channels that is allowed to be used in a cell. MaxFAPTxPower is expressed as a range of allowed maximum power levels with "...” (two periods) between the upper and lower values, i.e.




11 USC-44-54-016


Min Value

Max Value

Default Value

Reboot Required

HMS Access

Comments

"<Pmax_low>...<Pmax_high>". MaxFAPTxPower identifies the limits between which the FAP can self-configure its maximum transmit power. Self-configuration for maximum transmission power is controlled by .Capabilities.UMTS.SelfConfig.MaxFAPTxPowerConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.MaxFAPTxPowerSelfConfigEnable from an enabled perspective. <Pmax_low> and <Pmax_high> are measured in dBm and have a range of -40.0 to 30.0 incremented by 0.1dB. 3GPP-TS.32.642 Section 6.3.9, 3GPP-TS.25.104 Section 6.2.1 Note: Ranges adjusted from standard to align with Ubiquisys FAP capabilities Updates to this parameter will only take affect after the following full radio scan (either due to reboot or periodic scan)

MaxULTxPower string 0 64 "5..5" no reboot read/write

Defines the maximum transmission power level a UE can use on PRACH. MaxULTxPower is expressed as a range of allowed maximum power levels with "...” (two periods) between the upper and lower values, i.e. "<Pmax_low>...<Pmax_high>". MaxULTxPower identifies the limits between which the FAP can self-configure its maximum transmit power. Self-configuration for maximum transmission power is controlled by .Capabilities.UMTS.SelfConfig.MaxULTxPowerConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.MaxULTxPowerSelfConfigEnable from an enabled perspective. <Pmax_low> and <Pmax_high> are measured in dBm and have a range of -50 to 33 incremented by 1. 3GPP-TS.25.331 Section 10.3.6.39. Ubiquisys comment: This parameter is also used within RRM for the calculation of the max and min tx power used for the initial DL DCH power calculation. update to this parameter will trigger a full radio scan

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile object read/write

This object contains parameters relating to the Ubiquisys proprietary RRM algorithms

MinWidebandInterferenceLevel int32 -150 -20 -85 no reboot read/write

If the wideband interference (RSSI) on a carrier is below this level (dBm) it is concluded that the carrier is not being used. Update to this parameter will trigger a full radio scan.

MaxTotalWidebandInterferenceLevel int32 -115 -15 -65 no reboot read/write

Maximum allowed wideband interference for straddled carrier (dBm) above which an alarm is triggered update to this parameter will trigger a full radio scan.

MaxTotalMacroPilotInterferenceLevel int32 -115 -15 -65 no reboot read/write

Maximum allowed Macro Layer pilot Interference level per carrier (dBm) above which an alarm is triggered. Update to this parameter will trigger a full radio scan.

MaxZAP_RSCP_Level int32 -150 -50 -90 no reboot read/write

Maximum allowed level of interference (dbm) on a particular scrambling code, above which alarm




USC-44-54-016 12


Min Value

Max Value

Default Value

Reboot Required

HMS Access

Comments

is triggered. Update to this parameter will trigger a full radio scan.

NodeBNoiseFloor int32 -1700 -500 -1027 no reboot read/write

Noise floor for a typical Node B on the macro network (units of 0.1dBm) update to this parameter will trigger a full radio scan.

ULNoiseRiseMargin uint32 0 300 150 no reboot read/write

Margin to ensure that the noise rise caused by multiple ZAP UEs is within acceptable limits (units of 0.1dB) update to this parameter will trigger a full radio scan.

StraddledUplinkNoiseRiseMargin uint32 0 300 150 no reboot read/write

Margin to ensure that the noise rise caused by multiple ZAP UEs is within acceptable limits (units of 0.1dB) used for straddled carriers update to this parameter will trigger a full radio scan.

SlavingZAPRange uint32 10 150 75 no reboot read/write

Maximum pathloss to a ZAP for it to be considered for slaving power levels (dB) update to this parameter will trigger a full radio scan.

ScramblingCodeSelectionMethod enumeration 0 1

"Least Interference" no reboot read/write

Type of scrambling code selection algorithm used by the AP: - "Least Interference”: Select code with least interference from the AllowedCodesList - "Highest Prob Undetected Code”: Select highest probability undetected code from macro neighbour lists. If no macro cells detected, AP reverts to algorithm 0 update to this parameter will trigger a full radio scan.

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.LoadBasedCoverageTuning object read

This object controls the Ubiquisys proprietary load based coverage algorithms

EnableLoadBasedCoverageTuning boolean 0 1 0 no reboot read/write

If true, enables load based coverage auto-tuning. Only settable if not in Enterprise mode. If this parameter is disabled or enabled, cell restart will be triggered causing DLMM RESTART and HNB initiated deregistration


No Changes



Min Value

Max Value

Default Value

Reboot Required

HMS Access

Comments

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse

object

Read

This object contains parameters relating to the neighbour list used by the FAP based on its self-configuration capability and .CellConfig.UMTS.RAN.FDDFAP.NeighborList. Configuration of adding and excluding cells.

X_UBIQUISYS_COM_DominantNeighbourMacroIndex

Int32

-1 1963 -1 no reboot read

Index into the NeighborListInUse.IntraFreqCell or NeighborListInUse.InterFreqCell list for the strongest neighbour (to allow LAC/RAC/PLMN etc. to be read) Value -1 means that no macros have been detected. 0-31 corresponds to entries in the IntraFreqCell list 32-63 corresponds to entries in the InterFreqCell list




13 USC-44-54-016


No Changes

3.2 Customer Fixes Included in this Release

3.2.1 BV3.5.12.21-26

Summary Priority Partner Issue

Tracking Id(s)

Fix Description Root Cause

Get live data fails with RMS routing in NETC tables

Critical CSCva27808 Added functionality to delete route entry in route table for all services (PM upload, RMS, software download and PED upload), which are using old router IP address. New route entry will be created next time relevant service is invoked with new IP address of router.

Route entry for RMS or upload server IP addresses in routing table did not get updated in case, router IP address is changed.

AP triggering CN based handover for FACH user towards wrong cell

Major CSCuy47346 Now decision of relocation request is taking on the basis of cell id (came in cell update message). Therefor correct AP is being selected for relocation.

At Source FAP during Cell FACH relocation, relocation request is sent to the wrong AP instead of the Target FAP due to PSC conflict and hence crash is happening on that AP which has no context of that UE for cell FACH relocation.

CS Iu Release counters are pegged during PS dropped calls resulting in negative DCR

Minor CSCux80169 Pegging of

ABNORMAL_RELEASES and

IU_CS_CAVEAT_CONDITIONS

counters are made in sync as per

release cause received in IU

RELEASE COMMAND.

It seems AP has sent

IU_RELEASE_REQ with

failure cause. And CN has

initiated

IU_RELEASE_COMMAND

with NORMAL release cause,

before receiving

IU_RELEASE_REQ from AP.

Incorrect strongest macro in HNB register request

Critical CSCvc40184 FAP will be not considering Stale

Macro while searching for the

strongest cell from rem band list

FAP was considering stale

Macro while searching for the

strongest cell

AP DL power

changing from RMS

configured from

24dBm to 10dBM

for no reasons

Critical CSCvc49338, CSCva55953

Due to large number of FAPs and

macros deployed at the site, each

FAP is sniffing the neighboring

cells and updating the neighboring

cell lists in the FAP Database. Due

to a local stack corruption

happening while one of the FAP’s

module reads the list of neighbors

from the database, the ‘Load Based

Coverage Auto Tuning’ parameter

The local stack corruption has

been fixed to allow correct

database reading by the FAP

module irrespective of the

count of neighbors received

during SON sniffing.

https://cdetsng.cisco.com/webui/#view=CSCva55953




USC-44-54-016 14

was being wrongly set causing the

power levels of the FAP to lower

down and ultimately leading to a

sleeping cell

Update G3 OpenSSL to 1.0.1u

Critical CSCvb48676 Import latest version of OpenSSL

1.0.1u

Vulnerability in OpenSSL for

following vulnerabilities:

CVE-2016-6304 CVE-2016-

6305 CVE-2016-2183 CVE-

2016-6303 CVE-2016-6302

CVE-2016-2182 CVE-2016-

2180 CVE-2016-2177 CVE-

2016-2178 CVE-2016-2179

CVE-2016-2181 CVE-2016-

6306 CVE-2016-6307 CVE-

2016-6308 CVE-2016-6309

CVE-2016-7052

T-com manufactured HNB fail to FR if DHCP is not ready on power on

Blocker CSCva77346 Ethernet carrier detection loop

corrected.

Ethernet carrier detection loop

has problem.

IP-forwarding should be disabled in FAP

Minor CSCva20224 IP-Forwarding was disabled in

/proc/sys/net/ipv4/ip_forward.

IP-Forwarding was not

required and hence

DISABLED it.

3.2.2 BV3.5.12.20-21

Summary Priority Partner Issue

Tracking Id(s)

Fix Description Root Cause Impact

Incorrect reporting if Dominant cell in HNB register request

Blocker CSCuz48460 Changes are made such that a common offset value is used by RRM and RANC for the strongest inter frequency macro neighbour. Also the max value for the Database parameter which stores the dominant cell index is changed based upon the updated max number of entries in intra/inter frequency lists considering 32 max intra/inter frequency neighbours respectively.

RRM and RANC were using different offset values for storing and fetching the strongest inter frequency macro neighbour to/from DB respectively .So, RANC while sending the HNBAP register request could not get the correct macro related details.

FAP is unable to report its location details in the HNB Register

Request.

MTPAS Enabled Class 14 SIMS will not make calls in

Critical CSCuy23753 Modified System information Block type 3 to include domainSpecificAccessRestrictionParametersForPLMNOfMIB on conditional basis if domain Specific

System information Block Type 3 did not include all relevant Access Control specific IEs required for REL-8(or above) UEs. That's the reason UEs using SIM with ACC 14

Access Class 14 SIMs were not able to make calls.

https://cdetsng.cisco.com/webui/#view=CSCva77346




15 USC-44-54-016

Femto Cells Feature is being used. are getting confused and not able to attempt RRC Connection.

RS exit with RRC core due to RANC sending relocation handover to command to RRC after having received handover cancel

Critical CSCuy67472 When IuRH Hanover is in progress, Relocation command/relocation Cancel Ack/Relocation Prep Failure from Target is ignored at Source of earlier handover procedure. Timer for receiving ignored messages is already expired at Source.

During DCH relocation at source FAP crash is happening due to unexpected relocation command received for which RRC has already sent the relocation cancel request.

FAP crash due to race condition causing AP Service inhibited due to SW fault.

OAMPC exit with TR069C_Main core, inservice=0

Minor CSCuv48237 The recursive function has been rewritten to avoid the use of local buffer variables, which would prevent stack overflow.

A recursive function is using local buffer variables which caused stack overflow in some cases of recursion.

FAP crash during OAMPC module START. May cause delay in FAP bring up

PM stats file generated in unprovisioned state causing reporting errors in prime

Minor CSCuz02687 Now new PM file creation is happening after AP is in provisioned state.

New PM file creation do not check whether AP is provisioned state or not.

PM File with NULL values in header fields uploaded

Update G3 NTP to 4.2.8p7

Critical CSCuz44343 Import latest version of NTP 4.2.8p7

Vulnerability in NTP (CVE-2016-1551, CVE-2016-2516, CVE-2016-2517, CVE-2016-2518, CVE-2016-2519, CVE-2015-8138, CVE-2016-1550, CVE-2015-7704, CVE-2016-1547, CVE-2016-1548, CVE-2016-1549)

Enhancement for vulnerability

Update G3 OpenSSL to 1.0.1t

Critical CSCuz52520 Import latest version of OpenSSL 1.0.1t

Vulnerability in OpenSSL (CVE-2016-2108 CVE-2016-2107 CVE-2016-2105 CVE-2016-2106 CVE-2016-2109 CVE-2016-2176 )


Update G3 NTP to 4.2.8p8

Major CSCuz92778 Import latest version of NTP 4.2.8p8

Vulnerability in NTP (CVE-2016-4957, CVE-2016-4953, CVE-2016-4954, CVE-2016-4955, CVE-2016-4956)





USC-44-54-016 16

3.2.3 BV3.5.12.19-20

Summary Priority Partner Issue Tracking Id(s)

AP sending Inform via the IPSEC tunnel instead of TLS

Critical CSCuy11436

Following issues were resolved as part of this C:ustomer issue

IPT Start/Stop causes K value to be written incorrectly

IPT not starting correctly after swap from 2g macro source

RRM to consider OPLMN macro for timing during full band scan

Critical CSCuy78385

Free space in DB-Secondary area of FAP to remove non-uploaded PM files which prevent SW download

Minor CSCux28534

3.2.4 BV3.5.12.18-19

Summary Priority Partner Id(s)

RRM core dump Major NA

revert the RANC backoff behavior on SCTP failure

N/A NA

3.2.5 BV3.5.12.15-18


Enable USIM process when SIM card validation is required by HMS

Critical CSCux48094

UE is not able to redirect to LTE after CSFB call get disconnected on TGT AP

Critical NA

RRM Crash in GSM Sniff Major CSCuo93450

RS exit with RS_RRC core Major CSCuv46033

RRM exit with RRM_RRMC core, inservice flag=1 Major CSCuv47555

Issues observed in FAP EventList Major CSCuw15914

Uptime counter not showing expected values Major CSCuw41186

Source FAP should not retry the relocation during Cell Fach Relocation failure

Major CSCuv46033

Duplicate entries in SIB 11 Major CSCuw97425

RRC crashes when inter frequency measurement report received

Major CSCuv46033

out of bound of freq included in SIB 19 Major CSCuw99464, SR 636857763

Location Update Reject after PS handin from Macro Major CSCux83424

RRM exit with RRM_RRMC core, inservice flag=0 Minor CSCuv22112

neighbour cell added from frequency object set to – Minor CSCuw48364




17 USC-44-54-016

ignore

Duplicate entries in SIB 19 Minor CSCuw96073

Altering DL power on AP not taken affect until Reboot Minor CSCux10595

Evaluation of usc-iuh for NTP_October_2015 Major CSCuw84995

Evaluation of usc-iuh for OpenSSL December 2015 vulnerabilities...

Minor CSCux41427

CS handin from 2G with WB-AMR RAB setup is rejected by FAP Critical

CSCux82195

AP not recovering after backhaul outage Critical CSCux57825

AP synch switch from 3G to 2G to IPT failure Major CSCux33501

Deactivating parameter "EnableLoadBasedCoverageTuning" causing cell restart Major

CSCux33501

FAP not sending username in inform request after factory reboot Major

CSCux83379

CSFBAttempt Counter is pegged twice if LAU is performed prior to Cm Service Request Minor

CSCux83444

FAP not sending Write-Replace Failure in error scenario Critical

CSCux83433

Modem halt Major CSCux97702

Issues in CS RAB handin from GSM Critical CSCux82195

3.2.6 BV3.5.12.14-15


Georedundancy gateway switching failure Major CSCuw08976

AP initiates IKE_SA rekeying while AP initiated rekeying disabled

Major CSCuv87405

3.2.7 BV3.5.12.12-14


FAP is not coming up if the number of intra, inter & inter-RAT cells filled up with SIB19 set to TRUE.

Critical CSCuv61311

AP 3G REM timing out leading to AP halting provisioning process

Major N/A

NO SON TRAFFIC alarm is not sent with proper alarm format to RMS

Major 635338023, CSCuv18386

WB-AMR Femto to Macro handover prep failure if Target RNC does support release 6 SRNS container

Critical CSCuv33346

Counter IURHDHANDOUTREJECTEDPSTNLUPDATEFAIL is not pegged at all

Minor N/A

3.2.8 BV3.5.12.9-11


SC not cleaning registration manager state after tunnel down indication from Ranc

Major CSCuv21960

Users unable to accept incoming call in transit between two HNBs during call setup phase

Major CSCuu69457

Stale CS RAB state in RANC leading to incorrect pegging of RABATTEMPTFAILCSOTHER

Major

IPsec daemon has exited with Charon core Major CSCuv18392

2G stale cell not getting deleted even if remainingtimetolive count becomes 0

Minor CSCuv15369

Erroneous error message in ZGTT during emergency call setup

Minor CSCuu92640




USC-44-54-016 18


Caveated counter IURELEASECSNOHANDOUTTARGETIDENTIFIED is incorrectly pegged resulting in negative DCR

Minor

3.2.9 BV3.5.12.7-8


WB_AMR sampling rate is incorrect which results in poor voice quality

Critical CSCuu81106

RAB assignment Modification of max bit rate, cause AP to reject RAB assignment and peg RABATTEMPTFAILPSOTHER.

Critical CSCuu80995

Non-Broadcast LAI swap into uuLAC causing UE unreachable in MSC offload

Critical CSCuu57401

HNB fails to come in service after Factory Reset Critical CSCuv11578

HNB did not recover from IuH break test Major CSCuu98974

IPSEC retry failure due tunnel status mismatch Major CSCuu96991

Geo-redundancy confuses primary and secondary gateway addresses

Major CSCuu94586

EPP switches HMS IP address unnecessarily Major CSCuu87845

Duplicate GSM cell entries in NeighbourListInUse Major CSCuu69527

L2 core in multi PDP scenario Major CSCuu59138

IUUP Frame Number should be handled separately in DL and UL directions.

Major CSCuu28978

RRC broadcasts SIB11 again even though nothing has changed in SIB11 contents

Minor CSCuu74787

3.2.10 BV3.5.12.1-6


2d event handled even though 2f procedure is under progress when another 2d event is already queued

Minor

Queued RAB procedures handled prematurely in state RRC_CM_DEACT_WAIT_FOR_MEAS_INACTIVE due to premature compressed mode timer expiry

Minor

Stop fast IPT due to temperature difference during DLMM Minor CSCuu45872

Multi-rab HI has wrong release cause PS domain when CS domain fail Minor CSCuu41854

APM/RRM: No synchronisation on read/write of file for macro env comment block - causes malformed comment block

Major

Issues in back to back compressed mode activation/deactivation leads to call drop

Minor

EEP exit with EPP_Thread_Proc core Minor CSCuu36600

HNB behaviour in CS no encryption and PS UEA1/No encryption scenario Minor CSCuu21505

AP not sending relocation cancel to 2G CN after 3B (PS handout) Minor

Text Description for Hysteresis2x parameters state incorrect range Minor

3.2.11 Improvements

[SW-22829] - APM: Upload files in order of creation (for Prime integration)

o Prime Performance Manager(PPM) require PM files to be uploaded in chronological order to the RMS Upload Server, as PPM uses the uploaded file timestamp rather than the filename to determine order of file creation.

[SW-23318] - RRM will consider Inter frequency peers as valid peers in Iuh Grid

[SW-23381] - HNB to check SAN field also for Host name verification in case of TLS

https://sc-jira.cisco.com:8443/browse/SW-23318




19 USC-44-54-016


Installation and Upgrade Notes


USC-44-54-016 20

4 Installation and Upgrade Notes

4.1 Installation

HMS is fully supported from the management server. It is dependent upon the proper HMS server application having suitable written and tested configuration scripts.

CloudBase must be used to configure the small cell from initial start-up. CloudBase is used to give a small cell its default network connection parameters and licences and relies upon the default connection parameters and security certificates to have been provided to Cisco prior to needing the small cell to be used. Once configured in CloudBase the small cell will contact it over the public Internet and receive its configuration and licences. After which it will start up on a default R3.5MR load and await connectivity to an HMS system for provisioning of its database parameters and final Software Load. If an HMS is not used then the small cell will wait to be manually provisioned. The default CloudBase load must be specified and can be changed by contacting [email protected], the correct image signing policy will also be applied during the configuration of the CloudBase profile.

4.2 Upgrade Paths

Upgrades from HNB Management Systems are not supported when migrating between R3.3 to R3.5-MR; this migration must be performed using Factory Recovery from CloudBase.

Upgrades from HNB Management Systems are supported when migrating between R3.4 to R3.5-MR provided no license changes are required.

Upgrades between R3.4 or R3.5 to R3.5-MR must be performed using Factory Recovery from CloudBase when the new R3.5-MR licences are to be enabled.

Software rollback is only ever possible using Factory Recovery.

[**] – The Software Upgrade procedure was improved from release BV3.5.11.15, therefore, Factory Recovery is recommended in order to avoid any potential issue for loads prior to that point, including R3.4.


Open and Resolved Bugs


21 USC-44-54-016

5 Open and Resolved Bugs

The open and resolved bugs for this release are accessible through the Cisco Bug Search Tool. This web-based tool provides you with access to the Cisco bug tracking system, which maintains information about bugs and vulnerabilities in this product and other Cisco hardware and software products.

Note: You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. If you do not have one, you can register for an account.

For more information about the Cisco Bug Search Tool, see the Bug Search Tool Help & FAQ.

5.1 Open Internal Issues

The following issues are outstanding at the time of release:

Partner Id(s) Summary Priority Comment/Update

Broadcom Case ID: 814110 CSCuq46374,CSCut47912,CSCuq05030

Hardware Watchdog due to register corruption by L1

Major

CSCuu33428 Software Watchdog in BV3.5.11.14 Minor

CSCuu67807 DLMM manager failed, inservice =0 Minor

https://tools.cisco.com/bugsearch/

https://tools.cisco.com/IDREG/guestRegistration.do

http://www.cisco.com/web/applicat/cbsshelp/help.html


Related Documentation


USC-44-54-016 22

6 Related Documentation

[1] Cisco RAN Management System Release 4.1.0 Release Notes http://www.cisco.com/c/en/us/support/wireless/universal-small-cell-ran-management-system/products-release-notes-list.html

[2] USC-44-20-086 Interworking with 3GPP Release 10 Compliance Macro RNC

[3] USC-44-20-088 Iuh 3G 900Mhz Neighbour Cell Sniff

[4] USC-44-20-084 Edge Discovery

[5] USC-44-20-085 Geo-Redundancy

[6] USC-44-20-087 IMSI Blacklist

[7] USC-44-20-078 WB AMR Iuh

7 Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the

What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.

http://www.cisco.com/c/en/us/support/wireless/universal-small-cell-ran-management-system/products-release-notes-list.html

http://www.cisco.com/c/en/us/support/wireless/universal-small-cell-ran-management-system/products-release-notes-list.html

http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html

http://www.cisco.com/assets/cdc_content_elements/rss/whats_new/whatsnew_rss_feed.xml

usc application software r3.5-mr release notes · ranap_enhanced_relocation_request ... for air...

Documents