Oracle Communications DSR Release 7 · DOCME-DOIC Overload Control: DSR as a "Reacting Node" (Bug # 19120412) ... Some key uses are in association with WLAN networks and even some

Oracle® CommunicationsDSR Release 7.2Release Notice

E76365 Revision 05

January 2017

DSR Release 7.2 Release NoticeCopyright © 2011, 2017, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictionson use and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing iton behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,any programs installed on the hardware, and/or documentation, delivered to U.S. Government end usersare "commercial computer software" pursuant to the applicable Federal Acquisition Regulation andagency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptationof the programs, including any operating system, integrated software, any programs installed on thehardware, and/or documentation, shall be subject to license terms and license restrictions applicable to theprograms. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applicationsthat may create a risk of personal injury. If you use this software or hardware in dangerous applications,then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures toensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused byuse of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarksof their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarksare used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of AdvancedMicro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will notbe responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

Table of Contents

Chapter 1: Introduction.................................................................................6DSR 7.2 Introduction.............................................................................................................................7Revision History.....................................................................................................................................7

Chapter 2: Feature Descriptions..................................................................8Oracle Communications Diameter Signaling Router, Core Routing IV (L104787)......................9

Dynamic Peer Discovery (Bug# 19083633).............................................................................9Implicit Realm Routing (Bug# 21239923)................................................................................9DOCME-DOIC Overload Control: DSR as a "Reacting Node" (Bug # 19120412).............9Shared Traffic Throttle Groups (TTGs) for DOIC (Bug# 22151052)....................................9Increase Diameter Connections Limit (Bug# 19129715).......................................................9DSR Application Id Aware Routing (Bug# 21266236)..........................................................9Mediation Enhancements..........................................................................................................9

Oracle Communications Diameter Signaling Router, Translation Agent RADIUS(L104788)..........................................................................................................................................10

RADIUS Signaling Router (Bug# 19083638).........................................................................10Radius-Diameter IWF for WLAN (Bug# 19109995)............................................................10Additional RADIUS attributes to RD-IWF for SW conversion (Bug# 21304884)............10Encrypt master session key attributes (Bug# 21304793) ....................................................10

Oracle Communications Diameter Signaling Router, Full Address Resolution (L99454)........10Add Time Stamp to Subscriber Record (Bug# 19727402)...................................................10

Oracle Communications Diameter Signaling Router, Full Address Resolution (Capacity)(L99450)............................................................................................................................................11

SDS Capacity Increase (Bug# 20538191)...............................................................................11SDS IMSI and MSISDN Prefix Capacity Increase (Bug# 21312797)..................................11

Oracle Communications Diameter Signaling Router, Feature Constant Upgrade 7.2.0 ..........11Application support for upgrade health check GUI button (Bug# 21266236).................11150ms WAN latency support for Replication and Signaling (Bug# 22135733)...............11Support for FABR & OC-DRA interworking (Bug# 19113766).........................................11FABR - PDRA Application Chaining (Bug# 19105755).......................................................11FABR - RBAR Application Chaining (Bug# 21349662).......................................................12

Chapter 3: DSR Release 7.2 Media and Documentation......................13

iiiE76365 Revision 05, January 2017

Media Pack............................................................................................................................................14Documentation Pack............................................................................................................................14

Chapter 4: Supported Hardware Baseline...............................................18Supported Hardware Baseline...........................................................................................................19

Chapter 5: DSR Release 7.2 Supported Upgrade Paths........................20Supported Upgrade Paths...................................................................................................................21

Chapter 6: DSR Release 7.2 Resolved and Known Bugs......................22Severity Definitions..............................................................................................................................23Resolved Bug Listing...........................................................................................................................23Customer Known Bug Listing............................................................................................................26

Chapter 7: Oracle References and Services.............................................60My Oracle Support (MOS)..................................................................................................................61Emergency Response...........................................................................................................................61Customer Training...............................................................................................................................62Locate Product Documentation on the Oracle Help Center Site...................................................62Locate Product Release Software on the Oracle Software Delivery Cloud Site..........................62

Appendix A: Firmware Components.......................................................64Firmware Components........................................................................................................................65

ivE76365 Revision 05, January 2017

List of Tables

Table 1: Media Pack Contents........................................................................................................................14

Table 2: Documentation Pack Contents........................................................................................................15

Table 3: Supported Hardware Baseline........................................................................................................19

Table 4: DSR Release 7.2 Upgrade Paths......................................................................................................21

Table 5: DSR Release 7.2 Resolved Bugs.......................................................................................................24

Table 6: DSR Release 7.2 Customer Known Bugs.......................................................................................27

vE76365 Revision 05, January 2017

Chapter

1Introduction

This Release Notice includes Feature Descriptions,supported Hardware Baseline, Media and

Topics:

• DSR 7.2 Introduction.....7 Documentation pack contents and identifies the• Revision History.....7 Supported Upgrade Paths. This document also

includes listings of both the Resolved and KnownBugs for this Release. Directions for accessing keyOracle sites and Services are also identified in theOracle References and Services chapter.

Release Notices are included in the DocumentationPack made available with every Software Release.

6E76365 Revision 05, January 2017

DSR 7.2 Introduction

The Oracle Communications Diameter Signaling Router (DSR) product is positioned to address theTelecom Operator market's need for Diameter routing functions in 3G and 4G networks. Operatorsare adapting Diameter protocol in migration to LTE converged 3G and 4G networks. DSR 7.2.0 is nota launch of a new product, but rather introduces new functionality to the DSR product, which will beseparately chargeable to new and existing customers. The release also includes feature constant updates.DSR 7.2.0 introduces Core Routing IV, and Translation Agent RADIUS as chargeable features.

Revision History

DescriptionDate

Initial releaseMay 2016

.

Table 1, Media Pack Contents was updated to add part numbers to:June 2016

• V270240-01,Oracle Communications Diameter Signaling Router 7.2.0.0.0MIBS

• V270238-01,Oracle Communications Diameter Intelligence Hub Database7.2.0.0.0-72.23.0 OVA

• V270237-01,Oracle Communications Diameter Intelligence HubApplications 7.2.0.0.0-72.23.0 OVA

• V270236-01,Oracle Communications Diameter Intelligence Hub Mediation7.2.0.0.0-72.23.0 OVA

The Customer Impact statement was added to Bug 23505159 in Table 6, DSRRelease 7.2 Customer Known Bugs.

Removed "Cloud Only" restriction from Netra X5-2 in Table 3, SupportedHardware Baseline.

August 2016

Bug 21804265 for release 5.0 (Reassignment of IP Addr Alt keys can causeP-DRA binding correlation failures) was added to Table 5, DSR Release 7.2Resolved Bugs.

In the Media Pack Contents table, changed the part number for OracleCommunications Diameter Intelligence Hub Database 7.2.0.0.0_72.23.0 fromV266895-01 to V789507-01.

September 2016

In the DSR Release 7.2 Upgrade Paths table, added IDIH as another component.

Added Bug 22580193 (SOAM GUI - Prior Measurements are lost due ARTRule priority change) to Table 5, DSR Release 7.2 Resolved Bugs

January 2017


Introduction

Chapter

2Feature Descriptions

This chapter provides a summary of each featurereleased in DSR 7.2.

Topics:

• Oracle Communications Diameter SignalingRouter, Core Routing IV (L104787).....9

• Oracle Communications Diameter SignalingRouter, Translation Agent RADIUS(L104788).....10

• Oracle Communications Diameter SignalingRouter, Full Address Resolution (L99454).....10

• Oracle Communications Diameter SignalingRouter, Full Address Resolution (Capacity)(L99450).....11

• Oracle Communications Diameter SignalingRouter, Feature Constant Upgrade 7.2.0 .....11


Oracle Communications Diameter Signaling Router, Core Routing IV(L104787)

Dynamic Peer Discovery (Bug# 19083633)

From the DSR signaling point of view there are three basic use-cases for dynamic Diameter peerdiscovery:

• Initiator Mode: DSR discovering the last-hop Diameter peers• Responder Mode: Diameter peers discovering the first-hop DSR• Initiator+Responder Mode: DSR discovering Diameter (Edge) Agent for further handling of a

Diameter operation. It is combination of the above 2 uses cases between two end-points

Implicit Realm Routing (Bug# 21239923)

Realm routing using DNS SRV load-balancing information.

DOCME-DOIC Overload Control: DSR as a "Reacting Node" (Bug # 19120412)

DOIC provides overload control framework that overlay on Diameter Network Elements. Any/AllDNEs can be DOIC end-point. This includes Reporting, Reacting nodes and Back-To-Back Agent.Overload Control States are maintained per {host-id/appl-id, realm-id/appl-id} only at DOIC end-points

Shared Traffic Throttle Groups (TTGs) for DOIC (Bug# 22151052)

This functionality also share the Traffic Throttle Group (TTG) information between DSRs in the network.

Increase Diameter Connections Limit (Bug# 19129715)

Increase the Diameter Connection limit to 384 connections.

DSR Application Id Aware Routing (Bug# 21266236)

Given a Route List (or Implicit Routing), DRL will only consider the RGs and Peers which have availableconnections which can support the application Id of the message during routing decisions.

Mediation Enhancements

• Routing Loop Alarm (Bug# 20323232)• Internal specific AVP removal (Bug# 19090751)• DCL peg and event normalization (Bug# 19117957)


Feature Descriptions

Oracle Communications Diameter Signaling Router, Translation AgentRADIUS (L104788)

RADIUS Signaling Router (Bug# 19083638)

Ability to receive, route, and send RADIUS Request and their Responses (RADIUS in / RADIUS out).No Diameter interworking is involved.

Radius-Diameter IWF for WLAN (Bug# 19109995)

Remote Authentication Dial in User Service (RADIUS) is an Authentication, Authorization, andAccounting (AAA) protocol, which is a predecessor to Diameter. However, it is still widely in use.Some key uses are in association with WLAN networks and even some 3G mobile data applications.

• DSR allow a RADIUS Client to interwork with a Diameter AAA Server.• DSR converts RADIUS Access-Request messages from the Client into Diameter messages (DER)

for the AAA Server.• DSR converts Diameter messages from the Server (DEA) into RADIUS Access-Accept messages

for the RADIUS client.

Additional RADIUS attributes to RD-IWF for SW conversion (Bug# 21304884)

Optional RADIUS attributes added to a conversion from Diameter SWa/STa to RADIUS. These includefor example Acct-Interim-Interval, Transport-Access-Type, and Session-Timeout.

Encrypt master session key attributes (Bug# 21304793)

MS-MPPE-Recv-Key and MS-MPPE-Send-Key attributes are encrypted when sent to the RADIUSclient.

Oracle Communications Diameter Signaling Router, Full AddressResolution (L99454)

Add Time Stamp to Subscriber Record (Bug# 19727402)

Add Date/Time fields to Subscriber record with creation date time and last date/time that subscriberrecord was modified.



Oracle Communications Diameter Signaling Router, Full AddressResolution (Capacity) (L99450)

SDS Capacity Increase (Bug# 20538191)

Increase the SDS Capacity from 500 Million to 1 Billion Entries.

SDS IMSI and MSISDN Prefix Capacity Increase (Bug# 21312797)

Increase the IMSI prefixes & MSISDN prefixes from 1K entries to 100k entries for the Subscriber DataServer (SDS).

Oracle Communications Diameter Signaling Router, Feature ConstantUpgrade 7.2.0

Application support for upgrade health check GUI button (Bug# 21266236)

Health check scripts that are currently were run manually in the past, via CLI, are now able to runthrough a GUI button.

150ms WAN latency support for Replication and Signaling (Bug# 22135733)

Signaling and Subscriber Data Server (SDS) increases from 100ms WAN latency support increases toincreases from 150ms.

Support for FABR & OC-DRA interworking (Bug# 19113766)

Allows for the invocation of FABR followed by OC-DRA for the same Request. This ability will allowthe operator to use FABR subscriber identity and identify a cluster of OCS connected to an OC-DRAat a different site or a subset of OCS's connected to the local site.

FABR - PDRA Application Chaining (Bug# 19105755)

Allows for the invocation of FABR followed by P-DRA for the same Request. This ability will allowthe operator to select a policy server/cluster based on the subscriber identity while P-DRA maintainsthe binding that could be used to correlate other Gx or Rx sessions.



FABR - RBAR Application Chaining (Bug# 21349662)

Allows for the invocation of FABR followed by RBAR for the same request. This ability will allow theoperator to use FABR for resolving individual subscriber entries and if not found, will allow forresolving the destination based on IMSI/MSISDN ranges.



Chapter

3DSR Release 7.2 Media and Documentation

Oracle Communications software is available forelectronic download on the Oracle Software

Topics:

• Media Pack.....14 Delivery Cloud (OSDC). Documentation is delivered• Documentation Pack.....14 electronically on the Oracle Help Center (OHC).

Both the software Media Pack and theDocumentation Pack are listed in this chapter.


Media Pack

All components available for download from the Oracle Software Delivery Cloud(https://edelivery.oracle.com/) are in Table 1: Media Pack Contents.

Note: This list is accurate at the time of release, but is subject to change. View the Oracle SoftwareDelivery Cloud site for the latest information.

Table 1: Media Pack Contents

DescriptionPartNumber

Oracle Communications Tekelec Virtual Operating Environment 3.0.3.0.0_86.45.0 (ISOand USB images)

V138361-01

Oracle Communications Tekelec Platform Distribution 7.0.3.0.0_86.40.0 (ISO and USBimages)

V106309-01

Oracle Communications Tekelec Platform Management and Configuration6.0.3.0.2_60.28.0

V266925-01

Oracle Communications Diameter Signaling Router 7.2.0.0.0_72.25.0V266936-01

Oracle Communications Diameter Signaling Router, Full Address Resolution7.2.0.0.0_72.24.0

V266938-01

Oracle Communications Diameter Intelligence Hub Database 7.2.0.0.0_72.23.0V789507-01

Oracle Communications Diameter Intelligence Hub Applications 7.2.0.0.0_72.23.0V266892-01

Oracle Communications Diameter Intelligence Hub Mediation 7.2.0.0.0_72.23.0V266893-01

Oracle Communications Diameter Signaling Router 7.2.0.0.0 MIBSV270240-01

Oracle Communications Diameter Signaling Router 7.2.0.0.0_72.25.0 OVAV266937-01

Oracle Communications Diameter Signaling Router, Full Address Resolution7.2.0.0.0_72.24.0 OVA

V266939-01

Oracle Communications Diameter Intelligence Hub Database 7.2.0.0.0_72.23.0 OVAV270238-01

Oracle Communications Diameter Intelligence Hub Applications 7.2.0.0.0_72.23.0 OVAV270237-01

Oracle Communications Diameter Intelligence Hub Mediation 7.2.0.0.0_72.23.0 OVAV270236-01

Documentation Pack

All documents available for download from the Oracle Help Center (OHC) site(http://docs.oracle.com/en/industries/communications/) are listed in Table 2: Documentation Pack Contents .

Note: This list is accurate at the time of release but is subject to change. See Oracle Help Center forall available documents.


DSR Release 7.2 Media and Documentation

https://edelivery.oracle.com/

http://docs.oracle.com

Table 2: Documentation Pack Contents

Document Title

Release Notice

Licensing Information User Manual

Tekelec Platform Licensing Information User Manual

Planning, Installation, Upgrade, and Disaster Recovery

Feature Guide

Planning Guide

DSR Hardware and Software Installation Procedure 1/2

DSR Software Installation and Configuration Procedure 2/2

DSR Software Upgrade Guide

3-tier Disaster Recovery Guide

DSR Rack Mount Server Installation Guide

Rack Mount Server Disaster Recovery Guide

PCA Configuration

GLA Feature Activation Procedure

CPA Feature Activation Procedure

Mediation Feature Activation Procedure

FABR Feature Activation Procedure

RBAR Feature Activation Procedure

MAP-Diameter Feature Activation Procedure

DSR Network Impact Report

Cloud Installation and Upgrade

DSR Cloud Installation Guide

SDS Cloud Installation Guide

SDS Cloud Software Upgrade Guide

DSR Cloud Benchmarking Guide

DSR Security Guide

DSR VM Placement and CPU Socket Pinning Tool XLSX

Core DSR Document Set

Operation, Administration, and Maintenance (OAM) User's Guide

Communication Agent User's Guide



Document Title

Roadmap to Hardware Documentation Reference

Policy and Charging Application User's Guide

Diameter User's Guide

Mediation User's Guide

Range Based Address Resolution (RBAR) User's Guide

Full Address Based Resolution (FABR) User's Guide

Charging Proxy Application (CPA) and Offline Charging Solution User's Guide

IP Front End (IPFE) User's Guide

Diameter Common User's Guide

SBR User's Guide

MAP-Diameter IWF User's Guide

SS7/SIGTRAN User's Guide

Transport Manager User's Guide

Gateway Location Application (GLA) User's Guide

Related Publications Reference

Measurements Reference

Alarms and KPIs Reference

RADIUS User's Guide

DSR GLA Feature Activation Procedure

DSR Mediation Feature Activation Work Instruction

DSR CPA Feature Activation Procedure

DSR FABR Feature Activation Procedure

DSR RBAR Feature Activation Procedure

DSR MAP-Diameter Feature Activation Procedure

Core DSR Subscriber Data Server Document Set

Feature Notice

Getting Started

SDS User's Guide

Subscriber Data Server Provisioning Interface

Communication Agent User Guide

Operation, Administration, and Maintenance (OAM) Guide



Document Title

Alarms, KPIs, and Measurements

SDS Initial Installation and Configuration Guide

SDS Software Upgrade Procedure

SDS Disaster Recovery Guide

DSR Integrated Diameter Intelligence Hub (IDIH) Document Set

IDIH User's Guide

IDIH Audit Viewer Administrator's Guide

IDIH Alarm Forwarding Administrator's Guide

IDIH Operations, Administration and Maintenance Administrator's Guide

IDIH ProTrace User's Guide

IDIH System Alarms User's Guide

IDIH Log Viewer User's Guide



Chapter

4Supported Hardware Baseline

The Hardware identified in Table 3: SupportedHardware Baseline comprises the hardware and

Topics:

• Supported Hardware Baseline.....19 server versions that have been verified with thisRelease.


Supported Hardware Baseline

Table 3: Supported Hardware Baseline

DescriptionHardware

Intel Sandy Bridge CPU-based dual-socket blades and rack mountservers manufactured by HP

HP Gen8

Intel Haswell CPU-based dual-socket blades and rack mountservers manufactured by HP

HP Gen9

Intel Haswell CPU-based dual-socket rack mount serversmanufactured by Oracle

Oracle X5-2

Intel Haswell CPU-based dual-socket rack mount serversmanufactured by Oracle

Netra X5-2


Supported Hardware Baseline

Chapter

5DSR Release 7.2 Supported Upgrade Paths

This release has been tested for upgrades fromspecific prior releases; this chapter contains the exact

Topics:

• Supported Upgrade Paths.....21 paths for upgrade. Please verify that your currentinstalled release is listed on a valid upgrade path.


Supported Upgrade Paths

The possible upgrade paths to DSR Release 7.2 are listed below.

Table 4: DSR Release 7.2 Upgrade Paths

ToFromComponent

7.2.05.1.x, 6.0.x, 7.0.x, 7.1.xDSR

7.2.06.0.2, 7.0.x, 7.1.xIDIH

Note:

• Any upgrade other than listed above is not recommended or supported.• 7.2.0 is supported as a new or fresh installation as well.


DSR Release 7.2 Supported Upgrade Paths

Chapter

6DSR Release 7.2 Resolved and Known Bugs

This chapter lists the Resolved and Known Bugs forDSR Release 7.2.

Topics:

• Severity Definitions.....23These bug lists are distributed to customers with anew software release at the time of General• Resolved Bug Listing.....23

• Customer Known Bug Listing.....26 Availability (GA), and are updated for eachMaintenance release.


Severity Definitions

The problem report sections in this document refer to Bug severity levels. Definitions of these levelscan be found in the publication, TL 9000 Quality Management System Measurement Handbook.

Problem Report: A report from a customer or on behalf of the customer concerning a product or processdefect requesting an investigation of the issue and a resolution to remove the cause. The report maybe issued via any medium.

Problem reports are systemic deficiencies with hardware, software, documentation, delivery, billing,invoicing, servicing or any other process involved with the acquisition, operation, or performance ofa product. An incident reported simply to request help to bring back the service or functionality tonormal without the intent to investigate and provide a resolution to the cause of the incident is not aproblem report.

1. Critical: Conditions that severely affect the primary functionality of the product and because ofthe business impact to the customer requires non-stop immediate corrective action, regardless oftime of day or day of the week as viewed by a customer on discussion with the organization suchas:

• Product inoperability (total or partial outage),• A reduction in the capacity capability, that is, traffic/data handling capability, such that expected

loads cannot be handled,• Any loss of emergency capability (for example, emergency 911 calls), or• Safety hazard or risk of security breach.

2. Major: Product is usable, but a condition exists that seriously degrades the product operation,maintenance or administration, etc., and requires attention during pre-defined standard hours toresolve the situation.

The urgency is less than in critical situations because of a lesser immediate or impending effect onproduct performance, customers and the customer's operation and revenue such as:

• Reduction in product's capacity (but still able to handle the expected load),• Any loss of administrative or maintenance visibility of the product and/or diagnostic capability,• Repeated degradation of an essential component or function, or• Degradation of the product's ability to provide any required notification of malfunction.

3. Minor: Other problems of a lesser severity than 'critical' or 'major' such as conditions that havelittle or no impairment on the function of the system.

The numbered severity levels in the tables below correspond to these definitions:

• 1 - Critical• 2 - Major• 3 - Minor

Resolved Bug Listing

Table 5: DSR Release 7.2 Resolved Bugs lists bugs that are resolved in the following builds:


DSR Release 7.2 Resolved and Known Bugs

Application Lineup

• DSR 7.2.0.0.0-72.25.0• IDIH 7.2.0.0.0-72.23.0• SDS 7.2.0.0.0-72.24.0

Platform Lineup

• TPD 7.0.3.0.0-86.40.0* (DSR/IDIH/SDS/PMAC Baseline; Oracle Linux 6.7)• TVOE 3.0.3.0.0-86.45.0• PMAC 6.0.3.0.2-60.28.0• Comcol 6.4-p420• Appworks 6.0.1-60.53.0• Exgstack 7.2.0-72.17.0• HP Firmware 2.2.9 (minimum)• SUN FW 3.1.6 [minimum]

Note: * As part of successful installation of the DSR/IDIH/SDS/PMAC applications, the TPD versionis upgraded to 7.0.3.0.0-86.45.0.

Table 5: DSR Release 7.2 Resolved Bugs

TitleFoundRel

BugNumber

IPFE - Change the name of TSA Priamary/Secondary on GUI display7.123124029

CER message validation before DCL mediation trigger point7.122965537

DSR does not sends SCTP INIT on Primary Path of Multihomed Association7.122891849

[711MR]HA:Resource registrations during network recovery can cause databaseloss

7.122143961

IDB Fragments (PsbrSessionPart.000) getting ousted on PDRA disable.7.121833339

Event 22701 for Answer messages with Missing CC-Request Type AVP forGy/Ro

7.121807197

Peer Node and Connection Scope Value dropdown does not show all connections7.121792100

Fail to set value of IdbSchemaModifier parameter7.121694037

Unable to load /pdra/pdraajax/query?pcrfPoolName=Default&myId=apnstatus: 500

7.121674861

Event 22701 for Answer messages with Missing or Invalid Auth-Application-ID7.121666715

Problem during PCA function disable while performing resizing or migration7.121664865

Act/Stby psbr process restart truncates PDRA4.1 tables; causes bulk audit7.121661360

The SBR reconfiguration data should be deleted during PCA deactivation7.121660446

Sds.db_parts file requires multiple updates to enable DB parts exclusion7.121652977

SSST: Exception Measurements SbrXxxAuditDbErr pegged on Binding SBRs7.121540306

SBRDBRM: Resizing can get stuck with 0 of 0 records remaining7.121539715



TitleFoundRel

BugNumber

Getting numerous call failures when force completing a session resizing7.121488643

Measurement 14075 TxAnswerTimeoutMp is in the wrong measurement group7.121395043

Error: "Configuration Backup" on Database screen7.121363250

Sorting is not working properly on some of the fields of Routing Option Sets..7.121317395

Some Transaction Config Set rules not displayed as expected7.121314249

TotalAllocatedMemory metric is implemented in the wrong component7.121114106

IPFE Initiator Conns issue MJ 22101 "Connection Unavailable" when admindisabled

7.022734729

IPFE cannot add 250 addresses for mixed SCTP and TCP Target Sets7.022664056

Need DSR to revert to DSR 5.0 behavior for bad size in Diam Msg Header7.022629822

RTO value in SCTP parameter7.022244532

Capacity Configuration Set has incorrect description for abatement time7.022112091

Add secondary monitoring tunnel in DAMPs, (DCL,CSL) support for BUG21876176

7.021974924

SBR Memory Utilization alarm generated in non-PCA system7.021937332

IPFE has no available targets when only secondary signaling network is available7.021876176

[SystemTest7.0] TH Description incorrect for S9 PCRF and S9 Af/pCSCF7.020524839

Peer Node identification updates to Connection [Insert] screen7.020493825

[242439]IPFE: Two errors displayed for 'Peer Node Distribution Threshold'missin

7.019120515

MAPIWF: Memory leak in MapInsertSubscriberDataSM6.021951926

TKLCsnmp.log files are growing too large and filling up disk space6.020744242

PRT filter is not working as expected6.019846895

Policy DRA -> Configuration -> Congestion Options on SO has no edit warning6.019135720

[241432]Peer Route Rule fetchAll is very slow6.019119199

[238303]"CFG-DB Validation Error" alarm text to be more user friendly whendeact

6.019115278

[241454]PDRA: Measurement 11311 TxPdraAnswersGeneratedConfigErr is notpegged fo

5.119119224

[240743][PDRA] APN case is not saved when inserting an APN for which anexisting

5.119118400

[240547][POOL] Vital traces present in pSBR tr output5.119118155

[238733]P-DRA CongOptions BIE format contains way too many fields5.119115828



TitleFoundRel

BugNumber

[238361]DSR GUI: Application Route Table screen shows flat list of rules5.119115366

[238022][POOL] BIE: Remove unused fields in Congestion Options CSV file5.119114908

[237820][POOL] GUI: Display the time zone as abbreviation in Binding QueryRepor

5.119114637

[237476][PDRA] MSISDN should only support 15 digits5.119114211

[237171][POOL]GUI: No error displayed on PCRFs screen when field containsinvali

5.119113817

SOAM GUI - Prior Measurements are lost due ART Rule priority change5.022580193

Reassignment of IP Addr Alt keys can cause P-DRA binding correlation failures5.021804265

PDRA Generated RAR routing failure has no Events/Alarms/Measurements5.021620700

GUI does not restrict removing a TSA server from the server group5.021561983

DSCP not working on IPFE: iptables rules are overwritten by the IPFE process5.021033291

Diameter Meas TxConnSendBufAvg 0 & TxConnSendBufPeak n/a unexpectedly5.020878203

Tasks > Active Tasks > Result Details Column = blank on export5.019153312

[239706]DSR 5.0 - ?IPFE_Options? Exported Data ? Following fields are set to?bl

5.019117094

[237016]GUI screen resizing issue with Internet Explorer5.019113617

IPFE blocked ICMP "Fragmentation needed" caused the MTU auto discover notworkin

4.120891191

[229453]GUI - CEX Parameters screen - Edit actions of screen parameters notwor

4.119103892

[225333]PDRA: Incorrect flag value of the Session-Release-Cause AVP in a PDRAge

4.119098692

Optus: Eagle XG DSR 4.0.2-40.27.3 - Missing Entries in RBAR Address Table4.020045307

[227585]Max NE value is specified but not enforced4.019101556

[220176]DSR4.0 - pulldown widget does not keep autocomplete choices attachedto

4.019092331

[216231]Tool tip description for RxApplRuleFwdFailUnavail contains questionmark

3.019087666

Customer Known Bug Listing

Table 6: DSR Release 7.2 Customer Known Bugs lists known bugs in this release.



Table 6: DSR Release 7.2 Customer Known Bugs

Customer Impact StatementTitleReleaseSeverityBug Number

Customer Impact: Potentialimpact to traffic. Network

OOS or ACT MPnetwork flapping can

DSR 7.0223077146

flapping can cause a pattern ofcause DSR proc restartson rest of cluster cycling into and out of a DA-MP

server group which can lead toDSR process restarts. The risk isgreatest for large clusters ofDA-MP servers, but can happenin smaller clusters.

"Customer Impact: If an abtermoccurs during a reboot while the

[711MR] inetrep abterminTmOutgoingChannel::id()

DSR 7.1222227178

database is being replicated, thedatabase may becomeincoherent. The issue wasencountered after repeatedlytaking the switches up anddown. This is is unlikely to occurin the field. Workaround: None.inetrep restarts and recovers byitself with no recovery stepsneeded."

"Customer Impact: Effects SCTPmultihoming with IPv6 only.

[DSR 7.2 ST] SCTPMHSecondary Does not

DSR 7.2222757470

The signaling connection mayPick up Traffic whenPrimary Fails fail if the primary network path

is disrupted.Workaround: None"

"Customer Impact: Potentialimpact for customers using GLA.

DAMPs Restart in DSREVO when DSR Site STI

DSR 7.2222960243

If GLA error conditionsis Taken Down (GLAabterm) pSBR_Query_Timeout and

pSBR_Query_Failure are set tosend-Answer and the SBRs arepowered off allowing queries totimeout, when the SBRs arereturned to service, answer maycause DAMPs to restart.Workaround: Change the errorhandling to 'discard' instead of'send-Answer'. This may affecta small number of Answers inan SBR hard-failure scenario(how the Bug was generated),but these are not normal errorconditions and measurementscan be used to detect them."




Customer Impact: After update,it is necessary to review the

[238523]DSR 5.0, Serverscreen "NTP server"

DSR 5.0319115571

NOAM Configuration --> Servervalue blank afterupgrade when NTP p screen. If the NTP settings are

not what was configured at theservers, then a procedure will beneeded to update the NTP serversettings on the NOAM GUI formto match what is deployed on theservers.

"No Operational Impact: DataExport values may be viewed

[240413]SDS:'Administration ->

DSR 5.0319117992

under the [Main Menu: Status &Remote -> Servers ->Manage -> Tasks -> ScheduledTasks] screen."

Data Export' MinuteValue clears

Customer Impact: If usermanually stops the application

PDRA: SSBR failovertesting resulted in ~5.7

DSR 5.0320123471

on the active Policy SBR, trafficseconds worth trafficloss will not be processed until

failover completes.

The keyexchange that is donefrom the GUI under Main Menu:

Fix Kexchange forcustomers who blockICMP.

DSR 5.0320520696

Administration -> RemoteServers -> Data Export will notwork for customers who blockICMP.

Customer Impact: During 2-tierto 3-tier migration, peer IP routes

syncNetworkRoutescan't work

DSR 5.0323279408

on the MP servers may showtype ‘Discovered’ instead of‘configured’. Editing the routeswill not be possible withouttaking ownership first.

Customer Impact: If a PSBRserver loses cmHA heartbeat

[234101]The psbrprocess must set its HA

DSR 5.1319109938

with its peer due to IP networkstate to OOS when itloses connection t connectivity issue, the psbr

process may remain OOSindefinitely.

Customer Impact: User is unableto edit the admin permissionsfrom GUI.

[236264][POOL]GUI:Failed to edit thegroup 'admin'permission on GUI

DSR 5.1319112623

Customer Impact: The customerwill see incorrect

[237554][POOL] " Audit" Suspend Duration of

DSR 5.1319114308



Customer Impact StatementTitleReleaseSeverityBug Numberinformation(suspend duration)from event 22716 whencongestion is over.

Event 22716 is notshowing a su

Customer Impact: No impact.RAR messages without an

[239435]Auth-Application-Id

DSR 5.1319116743

Auth-Application-Id AVP areAVP validation in DSRrouted without any error. If one5.1 with PDRA

activated of the end points fails the callbecause of the missing AVP, DSRwill be notified of the failure.

Customer Impact: This issue canresult in reduced XMI

[239775]LRGSYS:Statusdata is being merged tothe NO

DSR 5.1319117177

bandwidth to the NOAM. Theissue should be minimal sincethe data is only merged up whenthe connection status changesstate.

"Customer Impact: Inaccuratemeasurement count. Pending

[239800]PSBR: InPending RAR audit

DSR 5.1319117212

RAR audit report has datareport, Num of ReleasePendingRar records not 'Number of Release PendingRar

records not added due to maxcapacity'. But the report does notshow the count of ReleasePendingRar records that couldnot be added because anotherrecord with same session id butdifferent alternate key hadalready been added."

Customer Impact: Customercould delete the Default PCRF

[239854][POOL] " BIE "PCRF Pools screen, the

DSR 5.1319117283

Pool Name value unknowingly,PCRF Pool Name"Default" valu especially if the user follows the

same logic that other attempts todelete the Default values are notallowed.

"Customer Impact: If replicationto the Standby PSBR server fails,

[239988]Replicationfailure on standby

DSR 5.1319117443

the replication barrier will alsoserver is also causingthe replication fa prevent replication to the Spare

PSBR server. This would meana potential loss ofSession/Binding data if theActive server fails. Workaround:Recovery procedure is available."




Customer Impact: The DA-MPserver will come into service

[241561]PDRA -Application enabling on

DSR 5.1319119350

even if it does not have a validDA-MP when some SBRresources are not ava connection to all Binding and

Session sub resources. If it hasconnections to some Binding andSession sub resources it willcome into service. The intentionwas for the DA-MP to provideno service until it has allconnections. It will insteadprovide some service.

Customer Impact: The majorupgrade from DSR 4.1.5 to DSR

[241567]Major upgradetime from DSR 41.20.1

DSR 5.1319119355

5.1 on a large PDRA system is noto DSR 51.18.0 nowexceeds requireme longer able to be executed within

the maintenance upgradewindow.

Customer Impact: User couldencounter errors with Bulk

[241615][POOL] BIE-PCRF Pool to PRT

DSR 5.1319119420

import when there is amisconfiguration.

Mapping import errorswhen when no APN ism

Customer Impact: Inconsistentreport output. The PSBR KPIs is

PSBR KPIs displayed onNO and PDRA servers

DSR 5.1319679676

not applicable to NO server, butit displays "0" value while theother NO server(standby), SO,PDRA, IPFE,etc show "blank".

Customer impact: In the eventof DC (Designated Coordinator)

DSR proc restart relatedto DC election churn

DSR 5.1320990574

election churn, DSR_Process maycaused by DC hangingon a lock get restarted due to OOS

notification.

Customer Impact: Measurementsand event history will be paused

MP->SO links inAuditWait state waiting

DSR 5.1321803930

until condition is cleared.Workaround is available.

for SO->NO link auditcompletion

Minimal Customer Impact:Server Configuration Error: If

[239412]DSR:Whenadding new servers in

DSR 6.0319116714

this issue is encountered user canConfiguration->Serversscreen Interfaces cancel out of screen and re-enter

configuration data.




"Potential Upgrade Event:Unexpected NOAM role

DSR upgrade: does nothandle NO activitychange well

DSR 6.0319306717

changeUnexpected DSR NOAMrole changes during an upgradecan result in misleading upgradestatus information.Workaround:Check the release version of theserver to tell if the upgrade isfinished successfully. At thispoint, it is suggested that theuser force a change-over back tothe original NO that wasmonitoring/administering theupgrade."

"Minimal Customer Impact:Unable to migrate IPv6 MPs

migration script withIPv6 aborts because of

DSR 6.0319402375

User will not be able to docompressed IPv6 IPs indb migration from Active/Standby

to Active/Active configurationif MPs have IPv6 IP Addresses.Workaround: Before migrationChange the format of IPv 6Addresses in Network table,those should be in expandedform like ""fd0d:deba:d97c:0ee5:0000:0000:0000:0000""."

"Customer Impact: Aftersuccessful GGR/GGA query for

IDIH - GLA Metadata -pSBR Response

DSR 6.0319446813

IMSI, there is metadata for themetadata not present onIMSI queries Query Event but not for the

Response. However there isminimal impact, because theresults of the pSBR query areextracted and formatted into theGLA answer message.Workaround: The workaroundis to examine the GLA answermessage. It will contain similarinformation as that producedfrom the pSBR queries. "

Customer Impact: No functionalimpact. This is a usability issue.

APDE Events fileshowed a line count, butfile did not log any data.

DSR 6.0319531576

The customer will not be able tosee the events as the report fileis empty.

Customer Impact: PotentialUpgrade Event: When PDRA

DB inconsistency b/wPSBR active server (64

DSR 6.0319552987



Customer Impact StatementTitleReleaseSeverityBug Numbercustomer upgrades from DSR5.x/6.x to DSR 7.x, then

frags) and standbyserver (8 frags)

upgrading a standby and spare"Session Server" Group, willpotentially lead to "session dataloss".

Minimal Customer Impact: BulkImport/Export for IPFE cannot

BIE broken afterupgrade due to

DSR 6.0319911799

be used until a manualworkaround is performed.

symbolic link created inbackout procedure.

Customer Impact: Users cannotuse the Diameter Maintenance

Diameter maint screensreports "Sorry, an error

DSR 6.0320145717

GUI to assess the health of theiroccured" when noDA-MP leader signaling network. This affects

the Diameter Troubleshootingand/Serviceability at SITE levelusing Diameter Maintenancescreens.

Customer Impact: None ifproper number VCPUs areconfigured.

In virtualizedenvironment PSBRprocessing latency isobserved during traffic

DSR 6.0320244290

Customer impact: Nooperational impact. This bug is

IWF Feature on VMprofiles need 24G RAMto come up

DSR 6.0320347965

relevant only for virtualizedDA-MPs and virtualizedSS7-MPs when we activate MAPinterworking function only.

"Customer Impact: If topologyhiding and RBAR/FABR are

Topology hiding issueDSR 6.0322523318

used in combination, androuting fails, then the selecteddestHost FQDN could be readby the peer. Error messagegeneration will include thedestHost in the ErrorMessageAVP.Workaround: Mediationcould be used to remove/alterthe ErrorMessage AVP."

"Customer Impact: AppWorkspush config script may fail if

Do not check andcorrect the order of

DSR 6.0323243569

alias interfaces areinterfaces sufficiently inAW server expor configured.Workaround: There

are 2 possible workarounds; 1)Edit the order inTKLCConfigData file to create



Customer Impact StatementTitleReleaseSeverityBug Numberthe base bond interface beforethe alias interface. 2)Go toConfiguration -> Network ->Devices then; Go to the MP taband; Highlight your aliasinterface, click edit, and thenapply."

Minimal Customer Impact: Theslow switchovers happen when

SBR servers taking morethan 1 sec to switchover,too slow

DSR 7.0319638376

the servers are completely idle.In the case of completely idleservers not handling traffic, thereis no service impact.

"Customer Impact: If IPFEinitiators and responders are

[STP7.0] IPFE Connstarving Fixed Conn

DSR 7.0320198495

co-located and many peer nodesdue to (upgrade related)MP outage are attempting to establish

connections while DA-MPs arereloading resources can getallocated in an unbalanced waythat keeps some initiatorconnections from establishing.Workaround: Restart some of theIPFE responder connections.This will free resources forinitiators to establish, and theresponders will get moved to aDA-MP with capacity."

"Customer Impact: No impactother than a syscheck

[STP7.0] HardwareConfig Error: 32 CPU(s)

DSR 7.0320237972

alarm.Workaround: Value canon the system, found"31" instead be changed as required for

expected number of CPUs toclear the alarm."

"Customer Impact: Screenrendering is delayed on verylarge topologies. "

[LRGSYS] certainscreens in LargeTopology DSR take longtime to display

DSR 7.0320495654

"Customer Impact: Screenrendering is delayed on verylarge topologies. "

[LRGSYS] certainTAB'ed screens in LargeTopology take long timeto display

DSR 7.0320509743

Customer Impact: No impact tocustomer. Workaround has been

Fresh Install - Featureactivation, feature not

DSR 7.0320670614

documented in the installationguide.

always visible in LHMsites 2/3




"Customer Impact: No impact tosignaling. This DSR 7.0 only

Corrupt ResourceDomain names in PCA

DSR 7.0320787403

issue must be cleared prior totablesattempting DSR 7.0 to DSR 7.1RdName2ComAgent

ResId and PsbrSubRes upgrade. Workaround: DSRupgrade document was updatedto ensure the tables are insync(no corruption) beforeupgrade starts."

"Customer Impact: No functionalimpact.The documentation needs

Clarify New 'TestTransfer' Button on

DSR 7.0320800434

to be updated to state theAdministration-RemoteServers-Data Export functionality provided by test

transfer button."

"Customer Impact: GUI issue, noimpact to traffic. User will not be

NOVIP GUI displayedthe standby NO after 6.0to 7.0 Upgrade

DSR 7.0321493739

able to do provisioning as theGUI VIP will be pointing to theStandby server.Workaround isavailable. Contact My OracleSupport (MOS) for assistance ifneeded."

Customer Impact: Default valuesare restored instead of

Eth config files notrestored after swappingMezz cards

DSR 7.0322321459

previously configured values.Manual steps will need to be runto restore network configuration.

"Customer Impact: User is notallowed to enter an email

Email Address not validwhile creating CSR inNOAM GUI

DSR 7.0322501315

address with a ""."" in thealphanumeric portion before the'@' symbol in the email address.Example:""[email protected]""is not valid, whereas""[email protected]""is valid."

Customer Impact: Customerneeds to verify value is changed

Mediation CAPM_Max[Assigned]ActiveTasks

DSR 7.0323293962

after upgrade otherwisevalues reset to 15 overupgrade Mediation Active Tasks will be

limited to 15.

Customer Impact. The reportmay not complete, resulting in

Large Measurementreport compilation can

DSR 7.0323487754

no/empty file and APDE taskfail due to insufficientspace in /var hung/aborted. Alarms are raised



Customer Impact StatementTitleReleaseSeverityBug Numberand will abate automatically orin some cases require manualintervention to recover thefilespace.

Minimal Operational Impact:Cannot resize columns for

Column resizing notworking on somescreens

DSR 7.1320447504

several menu items usingInternet Explorer 9. Issue notencountered using IE8 and IE10.

"Customer Impact: GUI issue.This issue occurs on the first

[IPv6] DSR ComAgentRemote Server Insert

DSR 7.1320513017

insert attempt after opening aFails First Time onBrowser new browser, or on the first

attempt of a given day. Theinsert does notapply.Workaround: User musttry again. All subsequentattempts will work successfullyfor the remainder of the day."

"Customer Impact: Potentialupgrade / GUI issue.For the

Potential (PDRA)configuration change

DSR 7.1320745780

below parameters that are GUIproblems in an upgradewindow in DSR 5.1+ configurable, during an upgrade

window (OAM has beenupgraded, but not all MPs havebeen upgraded) if these valuesare modified on the GUI, thenew value will not be replicateddown to MPs that are stillrunning the old release (due toupgrade barrier). Affected GUIscreens and parameters:***NOAM Main Menu: Policyand Charging -> Configuration->General Options (Allfields)Network-Wide Options(All allowed fields)OnlineCharging DRA -> OCS SessionState -> [Edit] (""OCS SessionState Enabled"" field) OnlineCharging DRA -> Realms (Allconfigurable fields) OnlineCharging DRA -> Network-WideOptions (All fields) AlarmSettings (All configurableentries) Congestion Options (Allconfigurable entries on thisscreen)***SOAM Main Menu:



Customer Impact StatementTitleReleaseSeverityBug NumberPolicy and Charging ->Configuration ->Policy DRA ->PCRFs (All fields) Policy DRA-> Binding Key PriorityPolicyDRA -> PCRF Pool To PRTMappingPolicy DRA -> SiteOptions (Topology HidingVirtual Name)"

"Customer Impact: As of DSR7.1, IPv6 to IPv4 automatic fail

[DSR IPv6]: No supportfor IPv6 deletion or IPv6to IPv4 failover

DSR 7.1320757520

over is not supported. Example:The system may notautomatically fail over (recoveryseamlessly) if disruption of theIPv6 network is encountered. Asfor IPv6 deletion, this process isnow supported, and is coveredin the IPv6 migration guide(E57517-01) "

"Customer Impact: The impactis limited to those apps (i.e. DSR

[AW] Server and ServerGroup names not

DSR 7.1321075547

Dashboard) that take Server orcompatible with FQDNformat Server Group names and use

them as an FQDN. An exampleis DSR Dashboard. In certaininstances, it will attempt to usethe SOAM server group name tocreate an FQDN to attempt to loginto the SOAM VIP. This will failto resolve if the server groupname happens to utilizeunderscores.Workaround:Configure Server and ServerGroup names that arecompatible with FQDN format."

"Customer Impact: GUI issue.This issue only ocurs only in a

DRNO login takes along time when former

DSR 7.1321273728

disaster recovery scenario, whenprimary NO isunavailable the primary NOAM site has

failed and is not reachable on thenetwork. In this scenario thelogin does work, the issue is thatit is very slow. Work Around:Wait for the login attempt tocomplete."

"Customer Impact: Disk Alarms32312 and 31121 will be present

7.1 SysTest: During DRprocedure, disk

DSR 7.1321385635



Customer Impact StatementTitleReleaseSeverityBug Numberon the GUI for the/var/TKLC/rundb partition on

shortage alarms arepresent on SOs

SOAM server. Workaround isavailable. Contact My OracleSupport (MOS) for assistance ifneeded."

"Customer Impact: Potentialimpact to Diameter traffic if

[NIDIH] Traffic failuresduring match-all IDIH

DSR 7.1321417112

IDIH is configured to match alltrace - large system atmax load traffic while traffic is running at

max rate.Workaround: DisableIDIH, or configure IDIH tomatch a limited scope (not all)."

"Customer Impact: Potentialtraffic impact; if preferred spare

[7.1SysTest] Traffic losswhen recovering a sitefrom outage

DSR 7.1321452436

has taken the active role due toactive/standby being down, ifand active/standby serversbecomes available the preferredspare may give up activity beforethe other server isready.Workaround: To minimizeimpact, if possible, beforerecovering the site that wasdown, ensure it will not becomeactive by forcing the servers to""OOS"" at ""Main Menu > Status& Manage > HA [Edit]"". Thenchanged the servers to ""Active""during a maintenance window."

"Customer Impact: Traffic willfail using session state on OCS

Problem specifying OCSRealm or Node for

DSR 7.1321493608

node.Work Around: Have theSS=Specific Message foradjacent node OCS node or OCS realm be

located in the DSR as the CTFnode. Or change the session stateto ""All message""."

Customer Impact: No impact totraffic. Exception Measurement

SSST: ExceptionMeasurement

DSR 7.1321509820

SbrRemoveSessDbErr canSbrRemoveSessDbErr(depending on the call mix) bepegged during sunny

day call flow pegged while running a sunnyday call flow. In this case it ismisleading to peg an errormeasurement when in fact thesignaling behavior is working



Customer Impact StatementTitleReleaseSeverityBug Numbercorrectly. The impact is that theerror pegs are misleading.

Customer Impact: No impact totraffic. Exception Measurement

During sessionmigration,

DSR 7.1321531146

SbrOcSessionNot found areSbrOcSessionNotFoundpegged on SBRs even thoughmeasurement

unexpectedly pegged even everything is workingcorrectly. The impact is that theerror pegs are misleading.

"Customer Impact: Nooperational impact. The

Unknown instancename in event report forbackup instance

DSR 7.1321620807

""instance"" name should be theserver name, but the server canstill be identified by looking atthe event."

Customer Impact: Nooperational impact. Upgrade

pdbRelayMsgLogTimeStamp should be

DSR 7.1321692073

Backout wipes out theseparated from theProvOptions table pdbRelayMsgLogTimeStamp

causing pdbRelay to fail. Thishas been compensated bywork-around in current Backoutprocedures until a SW fix isavailable.

Customer Impact: Nooperational impact. Workaround

Failure to resolve IPv6addresses in DNS post-IPv6 migration

DSR 7.1321861273

has been incorporated in theIPv6 Migration Guide.

Customer Impact: TemperatureWarning Trap is generated.

[VEDSR] X5-2:TemperatureWarningalarms

DSR 7.1321866548

Customer is warned thattemperature is rising. ILO doesnot indicate any issue. Customershould inspect for temperatureissues in the area to verifyhardware is sufficiently cooled.If ILO does not have anywarning, no additional action isnecessary.

Customer Impact: Nooperational impact. Workaround

[Appworks]: Failure toresolve IPv6 addresses

DSR 7.1321917304

has been incorporated in theIPv6 Migration Guide.

in DNS post- IPv6migration

Customer Impact: UnexpectedComAgent behavior. ComAgent

[Cloud]Hardware Id isHW_UNKNOWN onKVM / Openstack

DSR 7.1321965489

parameters are set to high for



Customer Impact StatementTitleReleaseSeverityBug NumberCloud installations when theHardware Id is not recognized"HW_UNKNOWN". TheComAgent Parameters are set toHP Gen6 hardware which willpotentially cause the Cloudinstallation to be overwhelmedwith ComAgent traffic.

Customer Impact: Inter-ServerGroup full parallel upgradecoordination is not supported.

ASGU Feature notimplemented accordingto spec

DSR 7.1321975470

Customer Impact: Customermust use the same hostname

DB compare shouldensure hostname of

DSR 7.1322121220

previously assigned during therestore server exists inServer table DSR Disaster Recovery

procedure to configure the firstNOAM server otherwise thedatabase restore will fail.

Customer Impact: This is a rarescenario in that the spare server

[711MR] Spare fails tobulk audit Standby

DSR 7.1322180707

must have been idle whenrebooting both the previouslyactive and standby serversresulting in database loss.

Customer Impact: Could causereplication issues due to

[711MR] OneTableaudit stuck in loopwhen forcing full audit

DSR 7.1322194751

replication link being stuck in aloop.

"Customer Impact: This onlyimpacts SDS SOAM with IPv6

Seeing "Upgradeexception is

DSR 7.1322353640

or dual stack managementREBOOTING butnetwork. During upgrade, Taskswaiting for

VALIDATED" Tab may show ""Server Upgradeexception <hostname>: Server<hostname> is REBOOTING butwaiting for VALIDATED.""Workaround may be applied tocomplete upgrade.Workarounds:*** If upgradeprocess hangs afterstarting(upgrade not completed);Manually 'complete' theupgrade. Selected the server andstart the upgrade again. *** Ifupgrade completed; Once theserver is up and present on theStatus & Manage -> Server page,



Customer Impact StatementTitleReleaseSeverityBug Numberrestart the application manually.The upgrade status should thenupdate. Either manually refreshthe GUI or allow time for autorefresh."

"Customer Impact: None.Workaround is documented in

MAP Interworkingfeature activation is not

DSR 7.1322384908

the DSR MAP-Diameter FeatureActivation Procedure."

configured on DRNOAMs

Customer Impact: None.Installation document has

[VEDSR] Can't PXEboot from PCIe NIC

DSR 7.1322590226

workaround, which wasmodified to accommodate thiscondition.

"Customer Impact: Running 2IPFEs on VEDSR on the same

[VEDSR] G9RMS: IPFERead/Write Errors athigh rate.

DSR 7.1323041283

server at 60K MPS with a largenumber of connections maycause TCP errors and alarms.Workaround: Move traffic toIPFE on another server or use anadditional XSI for signalingtraffic."

"Customer Impact: If 2 SBRs arebulk-audit/loading

[VEDSR] G9RMS: 2Simultaneous Bulk

DSR 7.1323064842

simultaneously on the sameAudits result in callfailure server, there may be momentary

traffic alarms due to networksaturation. Workaround:Perform SBR database loads ona server one at a time."

Customer Impact: Nooperational Impact. The text of

DSR GUI - CEX Cfg SetInsert show bad errormsg

DSR 7.2322111284

the error code could be wordeddifferently.

"Customer Impact: No signalingor functional impact. The

[PDRA] Session AuditReport "Records

DSR 7.2322306417

""Records Removed due toRemoved due to PolicyClient Query Results" Policy Client Query Results""

field of the Audit Statistics reportmay not always show correctdata because of raceconditions.Workaround: Use thePsbrStaleSessionsRemovedmeasurement in SBR Audit



Customer Impact StatementTitleReleaseSeverityBug Numbergroup to find the number ofStale Sessions Removed."

"Customer Impact: When thebackupAllHosts utility is used

7.2:Upgrade:backupAllHosts utility

DSR 7.2322482446

to backup a specified site withshould consider SpareSO & Spare SBR servers the --site=<> parameter, the

utility will backup all servers atthat physical site. There will beno backup for spare serversbelonging to this site at othersites however spare serversbelonging to other sites will bebacked up.Workaround: The/usr/TKLC/appworks/sbin/full_backup command can beused on an individual server tomanually backup any server thatwas not backed up with thebackupAllHosts command."

Customer Impact: No impact tofunctionality. SBR is listed as an

BIE - A scopedapplication 'Sbr' is

DSR 7.2322658869

Application while dependent onshowing in 'ExportPCA. Also SBR configuration isApplication' drpdown

list only entered on the NOAM, soALL data selected on the SOAMwill export nothing.

"Customer Impact: Minimal GUIissue, that only impacts Internet

GxLimit - Action buttonis not working on single

DSR 7.2322689717

Explorer. If using IE, double clickclick for all screens onIE10 on Insert/Edit/Delete button to

get the desiredresult.Workaround: Use MozillaFirefox browser."

Customer Impact: Diametersignaling that requires a Policy

PCA SSST: HAResource Switchover

DSR 7.2322709649

SBR query/transaction will failtime is longer thanexpected. during switchover until Active

server is available and normal.

Customer Impact: No signalingimpact. More IDIH traces maybe captured than expected.

[DSR 7.2 UPG] Numberof matches from DSRGUI is much larger thanfrom IDIH GUI

DSR 7.2322829662

Customer Impact: Customersmay only query servers within

SDS Query screen -SOAP calls need to

DSR 7.2322850342

the NOAM NE until the upgradecompatible amongseveral releases completes at the SOAM NE level.



Customer Impact StatementTitleReleaseSeverityBug NumberEach SOAM NE will respond tothe query correctly onceupgraded.

"Customer Impact: No impact tosignaling as MP was already

[DSR 7.2 ST] AddingDAMP server to DAMP

DSR 7.2322864399

OOS prior to this event. Thisserver group failed dueto DNS issue. issue is not likely to occur in the

field. It requires the user tospecify an external DNS server,then to remove and re-add aserver to a server group. If DBreplication is not caught up thiscould result in an emptyresolv.conf file. Workaround: Torecover, a resolv.conf file with avalid internal DNS server wouldneed to be copied to the server."

"Customer Impact: User has towait 90 seconds for the Status

LRGSYS:Status&Manage->Processes

DSR 7.2322915417

and Manage->Processes screenscreen takes 90 secondsto display to render. This screen is an

informational screen whichdisplays process informationexecuting onservers.Workaround: User canlogin to a specific server andquery the process informationfrom the command line."

"Customer Impact: Potentialsignaling impact. There is no

PDRA GUI: Novalidation for

DSR 7.2323014285

validation to prevent a ServerPlaceAssoc whilethat belongs to a Place that is notinserting new server to

existing SG part of any Place Association toa Server Group. If such a serveris added to a Policy Binding orPolicy Session Server Group andthe server becomes active,signaling may fail.Workaround:None. Be careful when addingServers to Policy Binding orPolicy Session Server Group."

Customer Impact: Customer willbe unable to restore the SOAM

Restore hangs due tounexpected ping

DSR 7.2323018247

database when spare SO is inbehavior when spare SOis in another networ another network and is

unreachable.




Customer Impact: Customer mayexperience 2-10 second delay inGUI refresh.

DOIC-NOAM SharedTTG screen notrefreshing within 10seconds

DSR 7.2323057378

Customer Impact: None.Workaround is documented in

Provisioned DR-NOservers which are not

DSR 7.2323070168

the installation procedure to rundeployed aborts PCAActivation script feature activation again on the

DR-NO.

"Customer Impact: Minimal GUIissue, that only impacts IE9 and

Buttons on view screensis not working on single

DSR 7.2323092341

IE10. Workaround: The user canclick for all screen inIE9-10 use a different browser or by

double clicking on the impactedoperations."

Customer Impact: No impact tofunctionality or throttling. Thisonly affects the alarming.

[VEDSR] Upgrade from7.1.x to 7.2 does notupdate the IPFE alarmthresholds

DSR 7.2323093382

"Customer Impact: Potentialsignaling impact. If the session

[PDRA] Losing bindingrecords during sitefailure/recovery

DSR 7.2323139593

SBRs at Site 2 recover from thereboot while the HA networksare down, a split brain willoccur. If this happens andComAgent is able to route frombinding SBRs to the session SBRsat Site 2, there will be record losscaused by the binding audit.Workaround: None "

Customer Impact: Customermust review raised alarm todetermine why cell is red.

DOIC/ETG Maint.screens: red cellsmissing 'SMS degraded'on ComAgent conn chg

DSR 7.2323236381

Customer Impact: User is unableto add a Message Priority

DOIC: SQL error whenTTG inserted with no

DSR 7.2323267849

Configuration Set that usesDA-MP server groupsconfigured. wildcard for Application ID and

Command Code.

Customer Impact: Minimal GUIissue. Customer can configure

SO Local node portDSR 7.2323283553

local node TCP/SCTP portsbeyond maximum stated onGUI. There is an error in the field



Customer Impact StatementTitleReleaseSeverityBug Numberdescription on the GUI. The portrange maximum is 65535.

Customer Impact: In large cloudtopologies (over 200 virtual

LRGSYS: inetrepprocess bouncing (andabterm'ing) in SOAM

DSR 7.2323285485

machines) “inetrep” process maybounce and cause comColconnections between servers tobounce.

"Customer Impact: If the targetserver of the query is a NOAM

Fail to load data onquery screen when

DSR 7.2323313139

or SOAM server, login to theremote server IP is usedby another DP GUI using the server's XMI IP

address to query the server data.If the target server of the queryis a DP server, then perform thequery from its Active SOAMparent GUI."

"Customer Impact: Customerwill need to perform one of the

Delete subscriber failswhen filtered by

DSR 7.2323479752

workarounds below to delete aMSISDN/IMSI when >1MSISDN/IMSI exist Subscriber from the

GUI.Workaround 1: If anAccount ID is present, find therecord using the ""Account ID""filter and then re-attempt thedelete. Workaround 2: If anAccount ID is not present, deleteall but one IMSI or MSISDNindividually viaSDS->Configuration->RoutingEntities page, then re-attempt thedelete using that filter type."

Customer Impact: If DA-MPs arereporting as Unk in Maintenance

[DSR 7.2 ST] DA-MPreport Unk and

DSR 7.2323505159

> DA-MPs and subsequently theUnexpected Conn Reseton DC Leader Reboot DC Leader is rebooted,

associated connections willre-establish to other DA-MPs.

Workaround: During upgrades,DC-MP should be last one to beupgraded, which would reducethe probability of this issueoccurring.

Customer Impact: Disasterrecovery of MP servers could

DSR 5.0 - Configurationof DA-MP took 3 hours

DSR 5.0419552760



Customer Impact StatementTitleReleaseSeverityBug Numberrequire extended maintenancewindow.

to execute script tillcompletion

Customer Impact: The second2-tier NOAM must be changed

Migration for second2-tier NOAM to the

DSR 5.0421620890

to OOS using documentedworkaround.

3-tier SOAM does notwork

Minimal Customer Impact:Unwanted ComAgent Major

[239975][M2D-60.10.0-RMS]:

DSR 6.0419117425

Alarms"ComAgent ConnectionComm AgentDown" alarms for the standbyDA-MP are safe to ignore.

Connection Down onSS7-MPs w/ACT/STBY DA-

Minimal Customer Impact:SNMP Notifications Contain

SNMP NotificationsContain RedundantText

DSR 6.0419209874

Redundant Text Extra "Notify"at end of affected notifications.

"Minimal Customer Impact: GUIErrorMissing DM-IWF Alarms

DM-IWF Alarms /Measurements

DSR 6.0419327392

and Measurement descriptions.descriptions needs to beupdated as per user doc For scenarios wherein request

and answer messages receivedfrom DRL by DM-IWFapplication whose size aregreater than""DiameterMaxMessageSize""following alarm wouldn't bedisplayed on GUI: Alarm Id:33015 Alarm Name: DM-IWFDiameter message size exceededmaximum supported size AlarmDescription: DM-IWF failed toforward the Diameter messageto SS7-MP because the messagesize exceeds supportedmaximum message size.Workaround: This scenario canstill be tracked by followingmeasurement: Measurement Id:15641 Measurement description:Number of diameter messagesreceived from DRL that gotrejected because diametermessage size exceededsupported maximum.Measurement Group: DM-IWFException"




Customer Impact: Peformanceof FABR-DIWF application

ComAgentEgressQueueis getting full while

DSR 6.0419538108

chained traffic will be impacted.executingComAgent Egress task100%Fabr-Diwf

Chaining Case. utilization will be high even atrelatively low traffic load.

Customer Impact: Nooperational impact. After

Upgrade GUI form -takes more than a

DSR 6.0419570299

selecting the "Accept" button onminute to refreshUpgrade State change the form, the form re-paints itself

after one second, but theUpgrade State is still shown as"Accept or Reject". The Minoralarm then clears withing a fewseconds, but the "Upgrade State"indicator takes about a minuteto refresh.

"Customer Impact: In DSR 6.0,the capacity of the PDRA

PDRA Topology Hidingtable limit exceededafter upgrade from 5.0.1

DSR 6.0419905484

Topology Hiding table waslowered to 1000 entries. If over1000 enteries were provisionedprior to upgrade, upgrade canbe successfully completed. "

Customer Impact: None. Usercan modify file duringinstallation as needed.

Samplechange_ilo_admin_passwd.xml file inES4118 does not matchsample in ISO

DSR 6.0420145631

Customer Impact: User will needto enable global provisioning for

User can notcancel/resume a paused

DSR 6.0420906170

cancel/resume functionality tobe available.

SG upgrade task withglobal prov disabled

Customer Impact: Duringinstallation or reconfiguration if

Failure to create 1 guestcauses all the steps afterit to fail in fdconfig

DSR 6.0422351289

failure is encountered with thefdconfig script, user will need tocorrect the issue before the scriptwill continue to next step.

Customer Impact: Alarm wasgenerated after rebooting all SBR

[comcol] False alarmgenerated stating time

DSR 7.0419773691

servers. The alarm automaticallyis 1,278,385,514 secondsbehind clears in 5 minutes and has no

impact to replication functions.




"Customer Impact: Some of theAvg measurements for the entire

OCDRA- AverageMeasurements are

DSR 7.0419846672

network work may not show theshowing half value thanactual value correct values. Workaround: Use

the Average measurementsvalue per Server. "

"Customer Impact: No impact tonormal DSR operation. This was

dsr process not exitingcleanly when underload

DSR 7.0419903633

encountered during reboot of aTVOE host with DAMP guests.Dsr process will not gracefullyshutdown when traffic isrunning.Workaround: Disableconnections before reboot. "

Customer Impact: Customer mayrequire extended and/or

[Upg 7.0] CertainUpgrade/Backouts

DSR 7.0420078150

multiple maintenance windowsto schedule upgrade activities.

unable to finish within4hr maint window

"Customer Impact: Unlikely toimpact customer. This issue was

LRGSYS: AppWorksSOAP Server DB ReInit

DSR 7.0420440390

encountered in a testThread StuckSometimes environment where user was

trying to setup hundreds ofservers at the same time. Theimpact is DB reinitialization willnot start for any newly addedservers.Workaround isavailable."

"Customer Impact: This canresult in a stuck 'backup failed'

LRGSYS: BackupFailure Alarm 10020seen on MPs

DSR 7.0420440552

alarm on some MPs. This issuehas not been observed in thefield. It has only been created inlab situations.Workaround: Thealarm alarm can be manuallycleared."

"Customer Impact: GLA featureconfiguration can not be done on

[STP7.0] GLA notactivated on DRNOs

DSR 7.0420696324

the DR NOAM if the primaryDSR NOAMs becomeunavailable.Workaround: GLAcan be activated on the DRNOAMs procedurally byrunning the feature activationscript on the DR NOAMservers."




Customer Impact: No functionalimpact.

Duplicate Parent Topiclinks in Online Help

DSR 7.0420696866

Customer Impact: No functionalimpact.

Incorrect Navigationbeing displayed

DSR 7.0420697000

No Operational Impact:Instructions are correct. This

Update Help Text onRemote Servers-Data

DSR 7.0420805853

addresses grammatical andformatting issues.

Export-Keys ReportPage

"Customer Impact: Both NOAMand SOAM keys are exchanged

APDE KeyexchangeFrom NOAM

DSR 7.0421130374

with the Remote Server whenExchanges Keys FromNOAM and SOAM using the ""SSH Key Exchange""

button. Note this does not breakany functionality. The only issuehere is that the SOAM keys arealso exchanged which may notbe desired.Workaround: Thereare two possible workarounds;1)Keys can be manually exchangedbetween NOAM and RemoteServer. 2) Remove the key fromthe authorized_keys file on theRemote Server for the SOAMafter the keys has beenexchanged using the ""SSH KeyExchange"" button."

"Customer Impact: After userperforms backout to DSR 7.0,

verifyBackout scriptreturns with error

DSR 7.0421459134

verifyBackout script will notwork. Workaround: User cancheck the upgrade.log file to seeif there are any ""ERROR"" tagslogged."

Customer Impact: If the Appl Idor CC in the Msg Priority Config

Cannot modify the ApplId or CC from a specific

DSR 7.0421933076

Set must be modified fromentry to a wildcardentry in Msg specific to wildcard, the entire

record must be deleted andre-added.

Customer Impact: If platcfg isused to edit NTP configuration,

platcfg NTP Edit is notconsistent

DSR 7.0422353448

user must verify updates weresuccessful. If not succesful usercould do a delete and add tomodify NTP configuration.




Customer Impact: Unable tosuccessfully remove IP routesfrom MP servers.

Host Route is added asNetwork Route

DSR 7.0423028528

Customer Impact: Error messageis not clear. This could affect

DSR 7.0DIAM-ERR-3002205: No

DSR 7.0423330034

troubleshooting of routingissues.

routes found. RouteList:X is not clear

"Minimal Customer Impact: Ifuser makes changed on ""Main

[7.1]ESBC:Groupadministration Edit

DSR 7.1420778632

Menu: Administration -> Accessfunction ofControl -> Groups [Edit]""Network-Options

screen broken Pressing ""Ok"" may not recordchanges. Workaround: Press""Apply"", then ""Ok"". "

No Functional Impact: User willreceive messages for both

DB backup returnserroneous info message

DSR 7.1421313048

Provisioning and Configurationbackups completing when thereshould only be one forConfiguration.

No Operational Impact: The MPis going down and an abtermwas generated during shutdown.

[SSST 7.1 Issue 6]Abterm inDiameterStack::shutdownPlugIn()during DC reboot

DSR 7.1421353768

No Functional Impact: The issueis with GUI data presentation

[DSR 7.1 ST] Diameter -Maintenance - DA-MPs

DSR 7.1421424088

when IPFE Initiator andGUI needs updating forIPFE I+R Responder connections are

present.

"Customer Impact: No functionalimpact. Alarm 31225 will be

EventID 31225 - HAService Start Failure on

DSR 7.1421465801

visible on Active NOAM fromDR-NOAMs after freshinstall Both Active and Standby

DRNOAM. If DRNOAM is notpresent alarm will notoccur.Workaround:Workarounds are documentedin the Installation and DisasterRecovery Guides."

Customer Impact: If PCRFPooling Migration fails to

PCRF Migration StatusVerification tool does

DSR 7.1421473561

complete due to some "straggler"not have option toremove records records, customer will need to

contact Oracle to help identify



Customer Impact StatementTitleReleaseSeverityBug Numberand remove the non-migratedrecords.

"Customer Impact:MAP-Diameter IWF menu item

[7.1SysTest] MD-IWFdoes not activate onDRNOs

DSR 7.1421479472

will not be available on theDisaster Recovery NOAM.Workaround: The featureactivation script can be executedon the Disaster RecoveryNOAM."

"Customer Impact: Potentialupgrade workaround. If any

Local Initiate PortValues Not Shown After6.0 to 7.1 Upgrade

DSR 7.1421493343

DSR initiator connections areconfigured with a local initiateport values, user will need todisable and re-enableconnections after the upgrade iscomplete to re-establishconnections.Workaround: Toestablish the connection on theLocal Initiate Port, Disable andthen Enable the connection."

Customer Impact: User will seeconfusing information in the

IDIH Event Data for DPserver shows IPv6

DSR 7.1421553687

FABR metadata in an IPv6network.

address followedby"(IPv4)"

"Customer Impact: Customercould intermittently experience

PCA SSST: StuckSysMetricThreshold

DSR 7.1421554520

stuck alarms after an SBRAlarms after SBRswitchover failover. Alarms are stuck until

manual intervention is appliedto clear them.Workaround isavailable. Contact My OracleSupport (MOS) for assistance ifneeded."

Customer Impact: If a CSRFvalidation failure is received

CSRF validation failureon configuration andmaintenance screens

DSR 7.1421591252

when attempting to an operationthru the GUI (rare occurrence),the user will have to make a 2ndattempt for the same action withsame data set to have the updatesuccessfully applied.

Customer Impact: None.Messages with a bad length (i.e.

[7.1SysTest] DWR/DPRmessage ignored iflength is incorrect

DSR 7.1421608339

not a multiple of 4) will be



Customer Impact StatementTitleReleaseSeverityBug Numberdiscarded at the point of entryinto the DSR instead of beingpossibly parsed.

"Customer Impact: User cannotview the 'psbr' process on the

SSST: Status & Manage> Processes screen does

DSR 7.1421629948

following GUI screen: Mainnot show psbr processstatus Menu: Status & Manage ->

Processes. This screen providesinformation on start time, status,# starts, CPU utilization, andmemory usage."

"Customer Impact: ""DiameterCommon -> Import"" task list

Diameter CommonImport Tasks List NotComplete

DSR 7.1421684532

may not be complete.Workaround: User could checkImportExportStatus logs in thefile management area ""Status &Manage -> Files"". "

Customer Impact: Generic error,"An internal error has occurred

Display appropriateerror in DSRdeployment screen

DSR 7.1421757262

- please contact Oracle CustomerSupport.", if an error isencountered during ISOdeployment. There is noindication if ISO deployment isalready in progress or alreadyfinished.

"Customer Impact: Possiblefailures of session creation

Issue in PCA comAgentqueue full errorhandling

DSR 7.1421796989

requests while resizing plan is inprogress only when thecomAgent queue is full andtopology hiding/Session state isenabled."

"Customer Impact: User cannotdelete multiple servers at one

Cannot Delete MultipleServers on NO GUIConfiguration->Servers

DSR 7.1421840386

time. Deletion must beserial.Workaround: Deleteservers one at a time."

Customer Impact: No systemimpact. In the SOAM GUI under

Cloud DSR - SS7 MPMP Profile assignment

DSR 7.1421909709

Main Menu -> Diametercurrent valueCommon -> MPs -> Profiledescription is

misleading Assignments the current valuecolumn will not be valid.




Customer Impact: If SS7 MPservers are mistakenly assigned

Unable to delete SS7MPs when group

DSR 7.1421955953

to the NOAM NE rather than theassigned to NOAM NErather than SOAM NE SOAM NE, user will not be able

to delete the servers from theserver group via the DSR GUI.

Customer Impact: User must adda non-preferred spare server tothe server group first.

Unable to add spareSBR server as the firstserver in a server group

DSR 7.1421955996

Customer Impact: On the DSRGUI Configuration->Servers

Multiple servers are notbeing deleted when

DSR 7.1421956002

screen only one server can beselected via the serverscreen deleted at a time. Although

multiple servers may be selected,deleted and success message isreceived, only one server isactually deleted.

Customer Impact: The MaximumMPS traffic alarm will not be

[Cloud] Max MPS trafficalarm [i.e. 22106] does

DSR 7.1422217695

raised for MAP originated trafficnot consider MAP origtraffic even if the traffic is greater than

the alarm thresholds. TheMaximum MPS traffic alarmdoes not consider diametertraffic running on DA-MPs dueto MAP originated calls. OnlyDiameter originated traffic isconsidered.

Customer Impact: Alam31100-DB Replication Fault couldbe seen during a site recovery.

[711MR] Removeunnecessary alarmwhen deleting AuditArbitrator link

DSR 7.1422227120

"Customer Impact: ""DiameterCommon -> Import"" task list

[VEDSR] DiameterCommon Import TasksList Not Complete

DSR 7.1422257229

may not be complete.Workaround: User could checkImportExportStatus logs in thefile management area ""Status &Manage -> Files"". "

"Customer Impact: No impact tosystem. After upgrade to DSR

IPFE upgrade logcomplains Mysql server

DSR 7.1422393186

7.1.1 the customer will see thenot running whenupgrading to DSR7.1.1 following when running

verifyUpgrade.ERROR: Upgradelog (/var/TKLC/log/upgrade/upgrade.log) reports errors!



Customer Impact StatementTitleReleaseSeverityBug NumberERROR: 1450291163::ERROR:mysql invocationfailedWorkaround: Customercan delete these lines from thelog and re-run verifyUpgrade. "

"Customer Impact: Import ofpeers and connections may be

[VEDSR] DSR ImportsFail onPeers/Connections

DSR 7.1422843973

impacted by presence of extracolumns orcommas.Workaround: Redoimport file or manuallyconfigure missing data."

Customer Impact: GUI userswith read-only privledges cannot

Some DSR config datanot viewable in GUI forread-only users

DSR 7.1422910567

view screens where "View" and"Edit" buttons are combined.Examples are ART and PRTtables.

Customer Impact: Nooperational impact. This error

[VEDSR]doExtValidation error

DSR 7.1423054720

was observed when attemptingobserved while deletingserver to delete a server while assigned

to a server group.

Customer Impact: No impact, asDA-MP was being shutdownwhen abterm occurred.

[VEDSR] G9 RMS:abterm Seen on DAMPover Graceful HostShutdown

DSR 7.1423075799

Customer Impact: No functionalimpact. If user were to copy and

Space Inserted in ActualHostname on TopologyHiding Screens

DSR 7.1423083657

paste the hostname from the GUIscreen a space may be added.

"Customer Impact: DisablingSBR DB on NO could result in

[VEDSR] G9 RMS: ErrorSeen Disabling SBR-sDB on NO

DSR 7.1423124073

error andDB will not be disabled.Workaround: Disable SBR DBagain."

"Customer Impact: Exported filecan not be immediately

CEX parameter exportszero instead of NULLdata

DSR 7.2421613805

re-imported. Workaround:Exported file must be modifiedto clear the Vendor Id field if 0is present prior to importing CExparameters."




Customer Impact: No functionalimpact. Default description isincorrect.

Routing Option Sets'Answer Error-Messagefield default value descris incorrect

DSR 7.2421634383

Customer Impact: Nooperational impact. There is still

RADIUS SOAM DSRGUI: Add some Selectsto the Connections form

DSR 7.2421787087

an arrow in each field whichindicates that a pull-down menuof options is available.

Customer Impact: No impact tosystem as an error is displayed

RADIUS SOAM DSRGUI: Incorrect Error

DSR 7.2421818410

but it could be clearer. If a usercode displayed wheninserting a Connection attempts to Insert a Diameter

Connection with the "MessagePriority Setting" set to "UserConfigured", if they don't set the"Message Priority ConfigurationSet" field, [Error Code 002] -Invalid Syntax is displayed.

Customer Impact: User mustinsure realm names are <= 253characters.

[DPD] Realm Namelimitation should bechanged to 253

DSR 7.2421910155

"Customer Impact:Configuration operation could

Incorrect Validation ofTest Mode Option onConnection Edit Screen

DSR 7.2421919320

fail however the followingworkaround may be applied.Workaround: Uncheck TestMode, press Apply. Re-checkTest Mode, press OK/Apply."

"Customer Impact: No impact tosystem. Some SOAM GUI

Contents window can'tbe maximized when usr

DSR 7.2421920725

screens will not resize whenclick the Maximizebutton on the IE maximized. Workaround: The

issue can be resolved by closingthe window and openinganother window to the SOAMGUI and maximize it. "

Customer Impact: Nooperational Impact. When IP

Peer NodesConfiguration GUI

DSR 7.2422078507

address filed is expanded the IPdisplays incorrect fieldindicators addresses are displayed however

a mixture of three dots "..." andtildes "~" are displayed for theother fields.




Customer Impact: Unable filter"Site Name" column on

DOIC: TTG Filteringbug in Viewing TTGsfor Route List screen

DSR 7.2422153433

"=,!=,LIKE" in Viewing TrafficThrottle Groups for Route Listscreen.

"Customer Impact: Minimalimpact. This is only an issue with

Can't delete a routegroup from route list

DSR 7.2422194872

IE browsers that have the clearicon. Once it is observed that theroute group was not removed bythe clear icon, the user can usethe delete or backspacekeys.Workaround: 1. Click onedit after selecting any RouteList having 2 or more RouteGroups configured on Route Listscreen.2. Clear Route Groupvalues using backspace.3. Afterclearing Route Group valuesform filtering select box, clickanywhere outside this box andnotice that priority text box isdisabled.4. Then Click onOK/Apply button.5. RouteGroup which you have clearedwill be deleted form this selectedRoute List."

"Customer Impact: Minimalimpact. At the bottom of the

not all data displayingin Maintenance->RouteGroups

DSR 7.2422195338

screen should be displayed aPause Updates button and thecount of Route Groups beingdisplayed. If not visable, theycan be seen by sizing thebrowser window and scrollingto the bottom.Workaround:Resize browser window andscroll to the bottom of the screen."

Customer Impact: MinimalImpact. The filter order

Order of filters forRoute Option Setsincorrect

DSR 7.2422218009

inconsistentcy may require theoperator to spend a little moretime finding the needed filter.

Customer Impact: No impact tofunctionality. There are

DSR Dashboard: BulkImport Metric Group

DSR 7.2422295701



Customer Impact StatementTitleReleaseSeverityBug Numberbackslash '\' characters in theerror text output.

error text incorrect forerror code 002

Customer Impact: No impact tofunctionality. The field

DSR GUI - RemoveIPFE-specific wording

DSR 7.2422306292

description may not make itfrom IPFE Conn Res IngMPS Scaling desc clear to operators that adding

fixed connections can also berejected.

"Customer Impact: No impact tofunctionality. If there are

Green Info box doesn'tproperly display the list

DSR 7.2422361516

numerous local nodes using aof LN on Conn Cfg SetGUI. connection cfg set, the info box

may not display all ofthem.Workaround: The entirelist of local nodes can becaptured by copying them fromthe info box and pasting them."

Customer Impact: Nooperational impact.

[BIE] AAA andCfgLevel should not besupported by BIE

DSR 7.2422568910

Customer Impact: MajorHardware Fault errors may be

[TPD] syscheck raisesfalse alarm for ECCMemory errors

DSR 7.2422616950

raised on GUI. When syscheckis unable to communicate withthe iLO, it can sometimes raiseECC Correctable Memory Erroralarms, but there are no actualECC errors.

Customer Impact: Nooperational impact. The name iscorrect, except for missing space.

ESBC uses site (B)-scoped measurementreport group "P-DRASite Diameter Usage"

DSR 7.2422658517

Customer Impact: GUI will showincorrect value for Percent of

DOIC TTP Maint SceenPercent of Transactions

DSR 7.2422682570

Transactions Diverted on theDiverted is incorrect insome case TTP maintenance screen when

the priority of the request is >=the Override Message PriorityThreshold of the TTP.

"Customer Impact: No onlinehelp for SMS queue utilization

Add online help forSMS Queue utilizationalarm

DSR 7.2422696184

alarm 19827. This alarm will beraised when SMS queueutilization is above configuredthreshold limits"




Customer Impact: DiameterCommon > Dashboard, DA-MP

Dashboard usingincorrect source metricfor DA-MP ingress MPS

DSR 7.2422720063

ingress MPS rate only reflectsaccepted traffic after validationand congestion controls.Dropped traffic manifests asfailed transactions.

"Customer Impact: None. Theapplication name is just repeated

File name of exportedfile has the App name

DSR 7.2422850537

in the name of the export filetwice when ALL optionis invoked when Export Data is set to ALL.

Workaround: None. Export filecan be used as is, the applicationtype is just repeated in thefilename."

Customer Impact: User can notuse parentheses in theapplication ID name.

SOAM: App ID namefor NSN (UCTF) causesinvalid syntax

DSR 7.2422951982

Customer Impact: No functionalimpact. Duplicate names couldconfuse user.

SOAM: App ID does notprevent applications forhaving the same name

DSR 7.2422958053

"Customer Impact: The time ofthe last update for a shared TTG

Time of last update fieldnot initialized in TTG

DSR 7.2422964920

is not available. Workaround:maint. screen for sharedTTG Perform an update on the shared

TTG."

"Customer Impact: No impact tosignaling. If the invalid

Stale sbr data added incase of resource domaininsert failure

DSR 7.2422981773

configuration attempt isrepeated too many number oftimes such that the ComAgentresource Ids gets exhausted(capacity: 65), no more ResourceDomains can be configured inthe system. Workaround: Thestale database entries can bemanually removed."

Customer Impact: Minor GUIissue. Subscriber Database

Updated path needed inOnline Help ExportMaintenance screen

DSR 7.2423076165

Server User's Guide >Maintenance > Exportmaintenance screen The path ismissing a ">" between theMaintenance and Export .




"Customer Impact: No functionalimpact as SBR database was

GUI allows PlaceAssociation to be

DSR 7.2423100157

disabled at the time.deleted whenWorkaround: Delete SBRdatabase and create a new one."

referenced by SBRDatabase

Customer Impact: Minimal GUIissue. The UDP port field is not

Peer Nodes GUI Formshouldn't label UDP

DSR 7.2423106100

required. The asterisk can beingnored.

Server Port asmandatory

Customer Impact: No functionalimpact. The file operations work

Global provisioningusing this screen

DSR 7.2423106613

as expected. The user could bedisplayed on SOAM forfiles menu confused by the false warning

message.

Customer Impact: No functionalimpact for the record limit being

DOIC - Max SharedAssociation/STTG tablelimit can be exceeded

DSR 7.2423108551

exceeded. If the system is closeto the maximum number ofShared Associations or SharedTTGs and shared associationsare added simultaneously onmultiple sites where thoseinsertions will exceed themaximum limit, no errors willbe raised on either site and thetable will have a number ofrecords that exceed themaximum limit.

Customer Impact: None.DSR App Changes(GLA and SDS) forAccessibility Changes

DSR 7.2423115521

"Customer Impact: Customercould experience a minor

Routing Option Set CanBe Inserted where

DSR 7.2423200424

difference in message processingTransaction Lifetime<PAT in timeout

scenarios.Workaround: Insurethat the transaction lifetimevalue is greater than the pendinganswer timer setting. "

Customer Impact: VE DSRcustomers should use dsr.Cpu

System.CPU_UtilPctsysmetric is lower thanexpected on VM

DSR 7.2423222826

instead of System.CPU_UtilPctas metric.

Customer Impact: Minimal GUIissue. The user should select the

[GUI] Application IdInsert -> Selecting radio

DSR 7.2423229945



Customer Impact StatementTitleReleaseSeverityBug NumberApplication ID value prior toentering the Application Name

button deletes enteredname

otherwise the Application namewill need to be re-entered.

Customer Impact: None. If a TTPis disabled, the signaling code

DOIC: TTPMaintenance screen,

DSR 7.2423235694

will ignore the dynamicDynamic Throttlingbuttons become active. throttling state, and will treat it

as disabled.

Customer Impact: No impact totraffic. Inaccurate measurement

DOIC-pegstatDivertedOut for TTPs

DSR 7.2423323324

count for DivertedOutare incorrect forConnection RGs measurements for Connection

Route Groups that route tomultiple peers.

"Customer Impact: No functionalimpact except when an SBR

Wrong confirmationmessage on Preparing

DSR 7.2423329636

Database Resizing Plan is beingSBR Db Reconfig Planof resizing type executed, an invalid

confirmation message may bedisplayed asfollows;Confirmation Message -SBR Data Migration planshaving the same Migration Typemust be run at the same time.Click Continue to perform thisaction on the following plans, orclick Cancel to cancel this action.Affected plans are: <plans list>The above message is only validfor migration plan. NOTE: Thiswill only occur if there is anothermigration plan and an adminaction has been executed on theother plan just before the aboveaction. Workaround: Noworkaround needed. Just clickcontinue on the confirmationmessage."

Customer Impact: User will notbe able to delete stale transport.

SS7MP Server getsdeleted even whentransport is configured

DSR 7.2423477541



Chapter

7Oracle References and Services

This chapter describes how to obtain help, whereto find related documentation, and provides othergeneral information.

Topics:

• My Oracle Support (MOS).....61• Emergency Response.....61• Customer Training.....62• Locate Product Documentation on the Oracle Help

Center Site.....62• Locate Product Release Software on the Oracle

Software Delivery Cloud Site.....62


My Oracle Support (MOS)

MOS (https://support.oracle.com) is your initial point of contact for all product support and trainingneeds. A representative at Customer Access Support (CAS) can assist you with MOS registration.

Call the CAS main number at 1-800-223-1711 (toll-free in the US), or call the Oracle Support hotlinefor your local country from the list at http://www.oracle.com/us/support/contact/index.html. When calling,make the selections in the sequence shown below on the Support telephone menu:

1. Select 2 for New Service Request2. Select 3 for Hardware, Networking and Solaris Operating System Support3. Select one of the following options:

• For Technical issues such as creating a new Service Request (SR), Select 1• For Non-technical issues such as registration or assistance with MOS, Select 2

You will be connected to a live agent who can assist you with MOS registration and opening a supportticket.

MOS is available 24 hours a day, 7 days a week, 365 days a year.

Emergency Response

In the event of a critical service situation, emergency response is offered by the Customer AccessSupport (CAS) main number at 1-800-223-1711 (toll-free in the US), or by calling the Oracle Supporthotline for your local country from the list at http://www.oracle.com/us/support/contact/index.html. Theemergency response provides immediate coverage, automatic escalation, and other features to ensurethat the critical situation is resolved as rapidly as possible.

A critical situation is defined as a problem with the installed equipment that severely affects service,traffic, or maintenance capabilities, and requires immediate corrective action. Critical situations affectservice and/or system operation resulting in one or several of these situations:

• A total system failure that results in loss of all transaction processing capability• Significant reduction in system capacity or traffic handling capability• Loss of the system’s ability to perform automatic system reconfiguration• Inability to restart a processor or the system• Corruption of system databases that requires service affecting corrective actions• Loss of access for maintenance or recovery operations• Loss of the system ability to provide any required critical or major trouble notification

Any other problem severely affecting service, capacity/traffic, billing, and maintenance capabilitiesmay be defined as critical by prior discussion and agreement with Oracle.


Oracle References and Services

https://support.oracle.com

http://www.oracle.com/us/support/contact/index.html

http://www.oracle.com/us/support/contact/index.html

Customer Training

Oracle University offers expert training on Oracle Communications solutions for service providersand enterprises. Make sure your staff has the skills to configure, customize, administer, and operateyour communications solutions, so that your business can realize all of the benefits that these richsolutions offer. Visit the Oracle University web site to view and register for Oracle Communicationstraining: education.oracle.com/communication. To reach Oracle University:

• In the US, please dial 800-529-0165.

• In Canada, please dial 866-825-9790.

• In Germany, please dial 0180 2000 526 (toll free) or +49 8914301200 (International).

• In Spain, please dial +34 91 6267 792.

• In the United Kingdom, please dial 0845 777 7 711 (toll free) or +44 11 89 726 500 (International).

For the appropriate country or region contact phone number for the rest of the world, please visitOracle University's web site at http://www.oracle.com/education/contacts.

Locate Product Documentation on the Oracle Help Center Site

Oracle Communications customer documentation is available on the web at the Oracle Help Center(OHC) site, http://docs.oracle.com. You do not have to register to access these documents. Viewing thesefiles requires Adobe Acrobat Reader, which can be downloaded at http://www.adobe.com.

1. Access the Oracle Help Center site at http://docs.oracle.com.2. Click Industries.3. Under the Oracle Communications subheading, click the Oracle Communications

documentation link.The Communications Documentation page appears. Most products covered by these documentationsets will appear under the headings “Network Session Delivery and Control Infrastructure” or“Platforms.”

4. Click on your Product and then the Release Number.A list of the entire documentation set for the selected product and release appears.

5. To download a file to your location, right-click the PDF link, select Save target as (or similarcommand based on your browser), and save to a local folder.

Locate Product Release Software on the Oracle Software Delivery CloudSite

Oracle Communications software is available for electronic download at the Oracle Software DeliveryCloud site, https://edelivery.oracle.com. Only authorized customers with a valid password may downloadsoftware from the site.



http://education.oracle.com/pls/web_prod-plq-dad/ou_product_category.getFamilyPage?p_family_id=41&p_mode=Training&sc=WWOU14047594MPP002C005

http://www.oracle.com/education/contacts


http://www.adobe.com


https://edelivery.oracle.com

For directions on downloading the software and other information about using this site, click FAQ inthe top right corner.



Appendix

AFirmware Components

The firmware components are software that isinstalled on the hardware. These components are

Topics:

• Firmware Components.....65 listed in this chapter, and are also listed in theFirmware Release Notice. Please refer to the latestFirmware Release Notice for any updates to this list.


Firmware Components

The Oracle® Communications HP Solutions Firmware Upgrade Pack Software Centric Release Notes Release2.2.9 lists the firmware versions approved for this HP Solutions Firmware Upgrade Pack release toassist customers with upgrading their HP hardware. Also, additional instructions and guidance onthe firmware upgrades have been provided where possible.

Oracle FUP

The Oracle® Communications Oracle Firmware Upgrade Pack, Release Notes 3.1.6 lists the firmware versionsapproved for this Oracle Firmware Upgrade Pack release to assist customers with upgrading theirOracle hardware. Also, additional instructions and guidance on the firmware upgrades has beenprovided where possible.

The Release Notes are available on Oracle Help Center (OHC) athttp://docs.oracle.com/cd/E57832_01/index.htm

HP FUP

The Oracle® Communications HP Solutions Firmware Upgrade Pack, Software Centric Release Notes 2.2.9lists the firmware versions approved for this HP Solutions Firmware Upgrade Pack release to assistcustomers with upgrading their HP hardware. Also, additional instructions and guidance on thefirmware upgrades has been provided where possible.

The Release Notes are available on Oracle Help Center (OHC) athttp://docs.oracle.com/cd/E57832_01/index.htm


Firmware Components

http://docs.oracle.com/cd/E57832_01/index.htm

http://docs.oracle.com/cd/E57832_01/index.htm

Documents

Oracle Communications DSR Release 7 · DOCME-DOIC Overload Control: DSR as a "Reacting Node" (Bug # 19120412) ... Some key uses are in association with WLAN networks and even some