DSR 7.0 Network Impact Report - Oracle Help Center · Web viewThis software and related...

Oracle® Diameter Signaling Router DSR Network Impact Report

Release 7.2

DSR-7.2.0.0.0-72.25.0E64830-01

Jun 2016

DSR 7.2 Network Impact Report

Oracle Diameter Signaling Router DSR Network Impact Report, Release 7.2

Copyright © 2011-2016 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license 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. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

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 it on behalf of the U.S. Government, 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 users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. 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 applications that 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 to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are 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 Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

E64830-01 2 Jun 2016


TABLE OF CONTENTS1.0 INTRODUCTION......................................................................................................................................................5

1.1 PURPOSE/SCOPE....................................................................................................................................................51.2 DISCLAIMERS........................................................................................................................................................5

2.0 OVERVIEW OF DSR 7.2 FEATURES....................................................................................................................6

2.1 ENHANCEMENTS TO DSR 7.2 FUNCTIONALITY BY CATEGORY.............................................................................72.2 RADIUS SIGNALING ROUTER (RSR)..........................................................................................................................82.3 DYNAMIC PEER DISCOVERY.................................................................................................................................82.4 DIAMETER OVERLOAD INDICATION CONVEYENCE (DOIC)..................................................................................92.5 ABORT BUTTON FOR SBR RECONFIGURATION...................................................................................................102.6 PER APN PER SUBSCRIBER SESSION LIMITING FEATURE...................................................................................102.7 DCL PEG AND EVENT NORMALIZATION..............................................................................................................102.8 FABR/RBAR ENHANCEMENTS..........................................................................................................................102.8 IDIH ENHANCEMENTS.............................................................................................................................................112.9 SDS ENHANCEMENTS..............................................................................................................................................112.10 DSR/SDS UPGRADE ENHANCEMENTS...................................................................................................................122.11 HARDWARE CHANGES.........................................................................................................................................122.12 SOFTWARE CHANGES..........................................................................................................................................132.13 FIRMWARE CHANGES..........................................................................................................................................142.14 UPGRADE OVERVIEW..........................................................................................................................................142.15 MIGRATION OF DSR DATA.................................................................................................................................15

3.0 FEATURE OAM CHANGES..................................................................................................................................16

3.1 DSR 7.2 RADIUS SIGNALING ROUTER (RSR)..................................................................................................163.2 RADIUS-DIAMETER IWF...................................................................................................................................193.3 DYNAMIC PEER DISCOVERY (DPD)....................................................................................................................243.4 DSR 7.2 DIAMETER OVERLOAD INDICATION CONVEYANCE (DOIC)................................................................253.5 DSR 7.2 ABORT BUTTON FOR SBR RECONFIGURATION....................................................................................333.6 DSR 7.2 PER APN PER SUBSCRIBER SESSION LIMITING.......................................................................................343.7 DSR APPLICATION CHAINING ADDITIONS..........................................................................................................353.8 DCL PEG AND EVENT NORMALIZATION.............................................................................................................353.9 TEKELEC SPECIFIC AVP REMOVAL....................................................................................................................353.10 SDS ENHANCEMENTS.........................................................................................................................................373.11 IDIH ENHANCEMENTS.........................................................................................................................................383.12 DSR/SDS UPGRADE ENHANCEMENTS................................................................................................................38

4.0 MEAL INSERTS......................................................................................................................................................40

4.1 ALARM/MEASUREMENTS/KPIS/MIBS DSR 7.2..................................................................................................404.2 ALARM/MEASUREMENTS/KPIS/MIBS DELTA (DSR 5.1)...................................................................................404.3 ALARM/MEASUREMENTS/KPIS/MIBS DELTA (DSR 6.0)...................................................................................404.4 ALARM/MEASUREMENTS/KPIS/MIBS DELTA (DSR 7.0)...................................................................................404.5 ALARM/MEASUREMENTS/KPIS/MIBS DELTA (DSR 7.1)...................................................................................41

5.0 REFERENCE LIST.................................................................................................................................................42

E64830-01 3 Jun 2016


LIST OF TERMS

ACL ………………………Access Control List ASGU …………………….Automated Server Group Upgrade AVP ………………………Attribute Value Pair

CLI ………………………..Command Line InterfaceDNS ………………………Domain Name ServerGUI ……………………….Graphical User InterfaceHSS .....................................Home Subscriber Server iLO ………………………..Integrated Lights OutIMI ......................................Internal Management Interface IOT ………………………..Interoperability TestsKPI ………………………..Key Performance IndicatorLTE ……………………….Long Term EvolutionMEAL..................................Measurements, Events, Alarms, and Logging MME ……………………...Mobility Management EntityMP.......................................Message Processor MPS ………………………Messages per SecondNE ………………………...Network ElementNMS ………………………Network Management SystemOAM……………………...Operations, Administration, MaintenanceOAM&P .............................Operations, Administration, Maintenance and ProvisioningOCF ………………………On-line Charging FunctionOFCF ……………………..Off-line Charging FunctionPDRA ……………………..Policy Diameter Relay AgentPCRF ……………………..DSR Control and Charging Rules FunctionP-CSCF................................Proxy-Call Session Control Function PDU ………………………Protocol Data UnitPM&C …………………….Platform, Management and ControlS-CSCF ...............................Session Call Session Control Function SLF ……………………….Subscriber Locator FunctionSPR……………………….Subscriber Profile Repository TPD ……………………….ORACLE Platform DistributionVIP ......................................Virtual IP Address XMI......................................External Management Interface XSI.......................................External Signaling Interface

E64830-01 4 Jun 2016


1.0 INTRODUCTION

1.1 PURPOSE/SCOPE

Purpose of this Feature Guide document is to highlight the changes of the product that may have impact on the customer network operations, and should be considered by the customer during planning for this release.

1.2 DISCLAIMERS

This document summarizes Release 7.2 new and enhancement features as compared to Release 7.1, and the operations impacts of these features, at a high level. The Feature Requirements (FRS) documents remain the defining source for the expected behavior of these features.

Note that feature implementations may change slightly during product test.

E64830-01 5 Jun 2016


2.0 OVERVIEW OF DSR 7.2 FEATURES

This section provides an overview of the DSR 7.2 release features that may impact OAM interfaces and activities.

For a list of all features, please see the DSR Release Notes located at the following public web site:

docs.oracle.com

Navigate to: Industries Oracle Communications documentation Diameter Signaling Router Release 7.2

E64830-01 6 Jun 2016


2.1 ENHANCEMENTS TO DSR 7.2 FUNCTIONALITY BY CATEGORY

At the time of upgrade to DSR 7.2, a number of features and enhancements will become visible on the interfaces to the DSR and may change certain existing OAM behaviors of the system. This section will summarize these feature changes as they affect OAM activities.

Note: For information on Upgrade planning and required steps before upgrade, please refer to the DSR 7.2 Software Upgrade Guide.

Table 1 DSR 7.2 New Features/Enhancements

DSR 7.2 Feature/Enhancement Name

Radius Signaling RouterRadius-Diameter IWFDynamic Peer DiscoveryDOCME-DOIC Overload Control: DSR as a “Reacting Node”Abort Button for SBR ReconfigurationPer APN Per Subscriber Session Limiting Feature

FABR-RBAR Application ChainingDCL Peg and Event NormalizationSupport for FABR & OC-DRA InterworkingFABR -> PDRA Application ChainingTekelec Specific AVP RemovalSDS Capacity IncreaseAdd Time Stamp to Subscriber RecordIncrease # IMSI & MSISDN from 1k to 100k entries in SDS

IDIH EnhancementsDSR/SDR Upgrade Enhancements

E64830-01 7 Jun 2016


2.2 RADIUS SIGNALING ROUTER (RSR)

Name Description ScopePR 19083638

DSR 7.2 Radius Signaling Router

RADIUS (Remote Authentication Dial In User Service) is an Authentication, Authorization and Accounting (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.

The RADIUS Signaling Router (RSR) feature of the DSR covers the case of a RADIUS message in and RADIUS message out. No Diameter interworking is involved. There are many potential drivers for RSR, only a few of which are described in the following subsections.

Some examples where RADIUS may be used are:

WLAN authentication and authorization, both in non-roaming and roaming cases,

for a GGSN to authenticate a user and provide (accounting) information to a AAA server on a per APN basis, as and

policy control in broadband networks via dynamic authorization mechanisms.

Major feature

PR 19109995

Radius-Diameter IWF

The RADIUS-Diameter IWF for Authentication feature provides message conversion between a RADIUS based client and a Diameter based AAA server via the Swa or Sta interfaces.

2.3 DYNAMIC PEER DISCOVERY

Name Description Scope

PR 19083633

Dynamic Peer Discovery

DSR support of Dynamic Peer Discovery as per RFC 6733. Meeting requirements in support of DNS Client Application interfaces for S-NAPTR/NAPTR/SRV/A/AAAA query and lookups. Feature allows a DSR SOAM to discover remote hosts within user-defined Realms.

Major feature enhancement

E64830-01 8 Jun 2016


2.4 DIAMETER OVERLOAD INDICATION CONVEYENCE (DOIC)


PR 19120412

DOCME-DOIC Overload Control : DSR as a "Reacting Node"

The “DOIC Feature” is comprised to two major DSR capabilities which are interrelated:

Static ETR Throttling : allows the operator to limit the rate of transactions that are forwarded to a particular Peer Node which are addressed to a particular Diameter Application ID.

Peer Node Reported Congestion : the ability to modify the rate of transactions forwarded to a Peer Node which are addressed to a Diameter Application ID based upon Diameter Overload Reports (OLRs) it receives in Answer responses from the Peer Node. This capability is defined in an IETF standard Error: Reference sourcenot found called Diameter Overload Indication Conveyance (DOIC). “Static ETR Throttling” must be enabled before this capability can be used.

In general, these capabilities layer on top of the existing congestion controls in the DSR. All of the current static controls such as ETLs/ETGs and the connection level congestion controls remain unchanged. This is mainly because the DOIC relationships are currently all scoped by a single Application IDs. Thus there’s still a need for ETGs and ETLs to provide static limiting across Application IDs for peers that support multiple Application IDs.


PR 19090751

Tekelec Specific AVP Removal

A mechanism is provided to allow for user control of selective removal of Tekelec specific AVPs during egress processing.

E64830-01 9 Jun 2016


2.5 ABORT BUTTON FOR SBR RECONFIGURATION


PR 22509379 21128895 An enhancement to the SBR Reconfiguration tool that will:

1) Actively move SBR records from the Initial database to the Target database (Proactive Reconfiguration).

2) Actively move SBR records from the Target database back to the Initial Database, and go back to putting all new records into the initial database (Backout).

Major feature

2.6 PER APN PER SUBSCRIBER SESSION LIMITING FEATURE


PR 20907306 This feature introduces per IMSI per APN session count limitation over binding capable sessions i.e. Gx, Gxx etc. Pre-DSR 7.2 P-DRA functionality imposes a maximum session per subscriber limit which is 10 sessions per subscriber but it does not consider APN.


2.7 DCL PEG AND EVENT NORMALIZATION


PR 19117957 Approximately 170 new, changed, or deleted measurements.

2.8 FABR/RBAR ENHANCEMENTS

Name Description ScopePR 21349662

FABR-RBAR Application Chaining

When FABR is unable to locate a subscriber within FABR DB the Dest-Host will be set to a value which will trigger RBAR invocation and Range-based routing for SA-HSS.

E64830-01 10 Jun 2016


PR 19113766

Support for FABR & OC-DRA Interworking

FABR can be used to take a subscribers identity and select a cluster of OCSs connected to an OC-DRA at a different site or a subset of OCSs connected to the local site. This will require FABR to be invoked prior to OC-DRA invocation for the same Ro (or Sy) request.

PR 19105755

FABR -> PDRA Application Chaining

FABR can be used to take a subscribers identity and select a cluster of PCRFs connected to an OC-DRA at a different site or a subset of PCRFs connected to the local site. This will require FABR to be inoked prior to OC-DRA invocation for the same Gx/Gxx request.

2.8 IDIH ENHANCEMENTS


PR 21607643

New TTR Event for Implicit Realm Routing (IRR) Feature

When DRL attempts to perform Destination-Realm Implicit Routing of a message (when it cannot find a Route List for a Request message via a PRT search and the message is not addresed to a Peer Node via the Destination-Host AVP), it will record metadata using the new TTR event. Using the Destination-Realm AVP and the Application-Id in the Request message, DRL looks for a matching entry in the system-wide Realm Route table which identifies a Route List to use to Destination-Realm implicit route the message. If a match is found, DRL will record the Route List selected using an existing Route List Selected TTR event.

PR 21918650

IDIH – DOIC: AVPs need to be added

DSR DOIC feature introduces 7 new AVP’s which will need to be added to IDIH

2.9 SDS ENHANCEMENTS


E64830-01 11 Jun 2016


PR 20538192

SDS Capacity Increase

SDS capacity support increasing from 500 million to 1 billion


PR 19727402

Add Time Stamp to Subscriber Record

SDS shall provide a create timestamp to indicate the time when a Subscriber Record was created.

SDS shall provide an update timestamp to indicate the time when a Subscriber Record was updated.

PR 21312797

Increase # IMSI & MSISDN from 1k to 100k entries in SDS

The number of IMSI & MSISDN prefixes supported in FABR will increase from 1000 to 100k.

2.10 DSR/SDS UPGRADE ENHANCEMENTS


PR 21157183

Health Check Automation

Early, Pre, & Post Upgrade Health Checks for DSR/SDS 7.2 systems can by initiated via a new “Checkup” button in the NOAM GUI

GUI

2.11 HARDWARE CHANGES

2.11.1 Hardware SupportedHardware Comment

HP BL460 Gen6 c-ClassHP BL620 Gen7 c-ClassHP BL460c Gen8, Gen8_v2 c-ClassHP BL460c Gen9 c-Class HP DL360/380 Gen6 Rack Mount ServerHP DL360/380 Gen8, Gen8_v2 Rack Mount ServerHP DL380 Gen9 Rack Mount Server Sun Netra X3-2 Rack Mount ServerSun Netra X4-2 Rack Mount ServerSun Netra X5-2 Rack Mount ServerSun Netra X5-2 Rack Mount ServerHP 6125, 6120 Enclosure SwitchCisco 3020 Enclosure SwitchCisco 4948E-F Rack SwitchCisco 4948E Rack Switch

Note: Gen9 and Gen 8 v2 hardware (with upgraded processors) are supported when purchased by a customer.

Note: mixed Sun/HP deployments are not generally supported.

E64830-01 12 Jun 2016


2.11.2 Hardware UpgradeNo hardware upgrades are required with this release. Deployment of certain Optional features may require additional hardware.

2.12SOFTWARE CHANGES

Software change include a new release of the software Platform components, and new DSR release.

2.12.1 DSR Release 7.2DSR Release 7.2 inherits all functionality from DSR7.1.

Component ReleaseDSR Release 7.2

2.12.2 iDIH 7.2

Component ReleaseOracle 7.2.0.0.0-72.23.0Mediation 7.2.0.0.0-72.23.0Applications 7.2.0.0.0-72.23.0

2.12.3 SDS Release CompatabilityDSR Release 7.2 is compatible with SDS Release 5.0 using IPV4 and SDS 7.1 using IPV4 and/or IPV6, and

SDS 7.2 using IPV4 and/or IPV6

Component Release Internet Protocol

SDS 5.0 IPV4

E64830-01 13 Jun 2016

Component ReleaseTPD 64 Bit 7.0.3.0.0-86.45.0

COMCOL 6.4-p420

PM&C 6.0.3.0.2-60.28.0TVOE 3.0.3.0.0-86.45.0AppWorks 6.0.42-6.0.1_60.53.0


SDS 7.1 IPV4-IPV6SDS 7.2 IPV4-IPV6

2.13FIRMWARE CHANGES

Firmware release guidance is provided via DSR 7.2 Release Notice in conjuction with the current supported firmware release instructions located at the following link:

docs.oracle.com

2.14 UPGRADE OVERVIEW

This section provides an overview of the Upgrade activities for Release 7.2.

2.14.1 Upgrade Path

The supported upgrade paths for DSR 7.2 (dsr-7.2.0.0.0-72.25.0) are:

5.1 7.2

6.0 7.2

7.0 7.2

7.1 7.2

7.2.x 7.2.y

Note: DSR > 5.1 support the 3-tier network architecture only. Any deployments with 2-tier architecture must migrate to 3-tier before upgrading beyond DSR 5.1.

2.14.2 Order of Upgrade1. If present, the SDS topology is recommended to be upgraded prior to DSR. SDS upgrade

procedures are located in a separate SDS upgrade guide.2. Firmware Upgrade (if required)3. Platform components (if required)

a) TVOE Upgradesb) PM&C Upgrades

4. DSR Upgrade in the following sequencea) A – Level NOAM / DR-NOAMb) B – Level SOAM (site-at-a-time with mate site spare)c) C – Level DA-MP, IPFE, SBR, SS7

E64830-01 14 Jun 2016

https://beehiveonline.oracle.com/teamcollab/wiki/CGBU_Platform_Engineering_Firmware_Workspace:HpFupReleases


5. Configure for new DSR features6. If present, IDIH can be upgrade either before or after DSR upgrade. IDIH upgrade

procedures are contained within the DSR upgrade guide.

2.14.3 Active/Standby DA-MP servers supportedActive/Standby DA-MP server architecture (1+1) continues to be supported in DSR 7.2.

Migration to Multi-active (N+0) DA-MP server architecture is recommended for all customers, and required for activating PDRA functionality.

2.15 MIGRATION OF DSR DATA

As in prior releases, the existing DSR Data will be preserved during the upgrade.

E64830-01 15 Jun 2016


3.0 FEATURE OAM CHANGESThis section describes the OAM changes introduced to the 7.2 product (as compared to the 7.1 release) organized by feature.OAM changes include: User Interfaces (NO GUI, SO GUI), Measurements Reports, Alarms, and KPIs.

Note: this section covers OAM changes that will be visible after upgrade to the 7.2 release, and does not include changes that will be seen only as new Optional Features are Activated on the system (post-upgrade activity, and customer specific).

3.1 DSR 7.2 RADIUS SIGNALING ROUTER (RSR)

3.1.1 DescriptionRADIUS configuration in the DSR 7.2 System is supported via new RADIUS menu folders in both the NOAM and SOAM: Main Menu RADIUS. The majority of RADIUS configuration is performed at the SOAM including the ability to add/modify/delete NAS Nodes. The RADIUS menu folder in the NOAM allows for network-wide configuration of a RADIUS shared secret. In addition, connection, local node, and routing configuration aspects for RADIUS are handled via corresponding pre-existing SOAM configuration forms located under the Main Menu Diameter menu folder.

3.1.2 GUI Configuration for RADIUS

User Configurable Aspects for RADIUS Router

Shared Secret –applied to all DSR’s under a NOAM. This is used to encrypt a User-Password attribute, if present, between DSR’s when a RADIUS Access-Request message is routed. (NOAM)

RADIUS server ports for a DSR local node. (SOAM)

RADIUS client port range for a DSR local node. (SOAM)

Enable/Disable of RADIUS client processing for a local node. (SOAM)

Connection retries upon timeout. (SOAM)

RADIUS Configuration Sets (SOAM)

Message Authenticator Configuration Sets

Shared Secret Configuration Sets ( allows creation of connection specific Shared Secret; Must match Shared

Secret configured on RADIUS peer)

Ingress Status Sever Configuration Sets

NAS table consisting of the following fields: (SOAM)

NAS Name (mandatory) FQDN (mandatory) Realm (mandatory) NAS-Identifier (optional) NAS-IP-Address (optional – max 2 values) NAS-IPv6-Address (optional – max 2 values)

At least one of the three items marked optional must be configured.Note: Here we use the term NAS to cover all possible types of clients, including BNG, BRAS, WAG, and NAS. This table is used for internal RADIUS-Diameter conversion purposes.

E64830-01 16 Jun 2016


3.1.2.1 NOAM GUINetwork-scoped Shared Secret

Figure 1 NOAM RADIUS Shared Secret Configuration

3.1.2.2 SOAM GUILocal Node Configuration Support for RADIUS

Figure 2 SOAM Local Node Table w/New RADIUS Fields

Peer Node Configuration Support for RADIUS

E64830-01 17 Jun 2016


Figure 3 SOAM Peer Node Table w/New RADIUS Ports Field

Connection Configuration Support for RADIUS

Figure 4 SOAM RADIUS Connections Table w/New AAA Protocol Field

New SOAM Menu Item for RADIUS NAS Node Configuration

E64830-01 18 Jun 2016


Figure 5 SOAM NAS Node

3.2 RADIUS-DIAMETER IWF

3.2.1 DescriptionThe RADIUS-Diameter IWF feature provides message conversion between a RADIUS based client and a Diameter based server. An example is shown in Error: Reference source not found, where RADIUS authentication and accounting is used by a WLAN AP, but the AAA server is Diameter based.

Figure 6 RADIUS-DIAMETER IWF Conceptual Diagram

Although the figure shows both authentication and accounting interfaces, accounting is not addressed at the present time.

This feature relies on the RSR feature for base RADIUS/UDP support.

3.2.2 ConfigurationUser configurable aspects of the RADIUS-DIAMETER IWF feature:

E64830-01 19 Jun 2016


Message Conversion Table

o Determines how a particular RADIUS Request Code maps to a Diameter Application/Command Code.

o The 7.2 release offers a preliminary subset of the future functionality and is an engineering-only configurable option for this release.

Figure 7 SOAM Message Conversion Configuration Set

Message Authenticator Configuraiton Sets(SOAM) determine whether he DSR adds an encoded Message-Authenticator to various RADIUS message types on both egress and ingress transactions.

E64830-01 20 Jun 2016


Figure 8 SOAM Message Authenticator Configuration Sets

Shared Secret Configuraiton Sets(SOAM) are used to create shared secret configurations for peer connections. A single set can be applied to single or multiple peer connections.

Figure 9 SOAM Shared Secret Configuration Sets

Ingress Status Sever Configuration Set(SOAM)

Determines how the DSR handles incoming Status-Request messages:

o Configure whether a response is sent or dropped silently

E64830-01 21 Jun 2016


o In cases where response is sent, determine whether it will b an Access-Accept or Accounting-Response

Figure 10 SOAM Ingress Status Server Configuraion Sets

Connection-Configuration Set(SOAM)

This release includes a new tab for RADIUS based peer connections that permits specification of:

o Pending RADIUS transactions per connection

E64830-01 22 Jun 2016


o Duplicate message detection on ingress transactions

o Duplicate message detection on egress transactions

o Cached response for duplicate ingress requests that have a previous reply

Figure 11 SOAM New RADIUS Tab in Connection Configuraion Sets

System Options(SOAM)

This releae includes a new tab for RADIUS UDP socket specific-options including:

o Client Socket Send/Receive Buffer Size

E64830-01 23 Jun 2016


o Server Socket Send/Receive Buffer Size

o Maximum open sockets and retry options

Figure 12 SOAM New RADIUS UDP Options Tab in System Options

3.3 DYNAMIC PEER DISCOVERY (DPD)

3.3.1 DescriptionThe DSR 7.2 release now supports RFC 6733 compliant Dynamic Peer Discovery. This feature enbles the DSR to automatically discover Diameter peers within a configured Realm and also automatically create required configuration in order to support routing of Diameter messages to and from such peers.

Note: Routing of all Diameter application messages (S6a, Gx, Gy, …) is supported for any Dynamically discovered Peer Node. However, DNS expiry times associated with all such Peers prevent the use of application routing within the DSR hence the use of Mediation, RBAR, FABR, & PCA are not supported for this release.

3.3.2 SOAM Dynamic Peer Discovery ConfigurationA small set of configuration items are required as input in order for the DPD feature to function. These items are 1. Realm 2. DNS Server/s 3. Discovery attributes. With these 3 statically configured items in place and with automatically discovered peers then identified the DPD feature will proceed to automatically create Peer Node, Connection,

E64830-01 24 Jun 2016


CEXCfgSet, Route Group, and Route List configuration items which are all necessary prior to being able to begin routing Diameter messages.

The configuration settings for Dynamic Peer Discovery are located on the SOAM within a new “Peer Discovery” menu folder: SOAM Main Menu Diameter Configuration Peer Discovery. Withn the folder are 3 forms to allow Add/Modify/Delete actions for Realms, DSN Sets, and Discovery Attributes.

The status of discovered peers can be checked on the new Peer Discovery form located at: SOAM Main Menu Diameter Maintenance Peer Discovery.

Figure 13 SOAM PDP Configuration GUI Screens

3.4 DSR 7.2 DIAMETER OVERLOAD INDICATION CONVEYANCE (DOIC)

3.4.1 DescriptionDOIC is a new IETF standard for supporting dynamic overload controls between diameter servers and diameter clients. It allows for diameter servers to send overload reports requesting that diameter clients reduce the traffic being sent to the server. It also allows for diameter Agents such as the DSR to act as a proxy for either the clients, by reducing traffic as requested by the servers, or as a proxy for the servers by requesting that traffic be reduced by the clients. For the

E64830-01 25 Jun 2016


DSR 7.2 release the main focus of the DOIC feature will be on the DSR acting as a proxy for the clients, and reducing traffic based on information from the servers. The supported DOIC scope will be Host + Application ID.

3.4.2 SOAM GUI DOIC ConfigurationConfiguration for the DOIC feature is performed on the SOAM in the following 4 locations:

1. Add/Modify/Delete DOIC Configuration Sets

Figure 14 SOAM Traffic Throttle Point Configuration Sets

2. Add/Modify/Delete DOIC Traffic Throttle Points (TTP’s)

Figure 15 SOAM Traffic Throttle Points Table

3. Add/Modify/Delete DOIC Traffic Throttle Groups (TTG’s)

E64830-01 26 Jun 2016


Figure 16 SOAM Traffic Throttle Groups Table

4. Enable/Disable individual TTP’s.

Figure 17 SOAM Traffic Throttle Points Maintenance Screen

5. Enable/Disable individual TTG’s.

E64830-01 27 Jun 2016


Figure 18 SOAM Enable/Disable Traffic Throttle Groups

6. Peer Nodes

Figure 19 SOAM Peer Nodes Table w/New TTP Field

7. Route Lists

E64830-01 28 Jun 2016


Figure 20 SOAM Route Lists Table w/New TTG Field

8. Routing Option Sets

E64830-01 29 Jun 2016


Figure 21 SOAM Routing Option Sets w/8 New DOIC Fields

9. Capacity Summary Screen

E64830-01 30 Jun 2016


Figure 16 SOAM Capacity Summary Table with 11/new items related to DOIC/DPD/RADIUS

E64830-01 31 Jun 2016


3.4.3 DOIC Alarm Summary

Alarm-ID DPI Layer Alarm Name Severity Instance Where Raised

22072 DRL TTP Degraded Major <TTP Name> SOAM

22073 DRL TTP Throttling Stopped Minor <TTP Name> DA-MP

22074 DRL TTP Maximum Loss Percentage Threshold Exceeded

Major <TTP Name> SOAM

(FUTURE)22076

DRL TTG Maximum Loss Percentage Threshold Exceeded

Major <Route List Name>:<Route Group Name>.<TTG Name>

SOAM

25805 OAM Invalid Shared TTG Reference Minor <rl_name>&<rg_name>&<ttg_sg_name>&<ttg_name>

SOAM

25806 OAM Invalid Internal SOAM Server Group Designation

Minor <rl_name>&<rg_name>&<ttg_sg_name>&<ttg_name>

SOAM

3.4.4 DOIC OAM Event SummaryOAM Event-ID OAM Event Name Instance

Throttle Seconds1

Associated Measurement

22068-001 TtpEvDoicException: DOIC OC-Supported-Features AVP not received

<TTP Name>:001 10 14300

22068-002 TtpEvDoicException: DOIC OC-Feature-Vector AVP contains an invalid value

<TTP Name>:002 10 14300

22068-003 TtpEvDoicException: DOIC OC-Report-Type AVP contains an unsupported value

<TTP Name>:003 10 14300

22068-004 TtpEvDoicException: DOIC OC-Sequence-Number AVP contains an out of order sequence number

<TTP Name>:004 10 14300

22068-005 TtpEvDoicException: DOIC OC-Reduction-Percentage AVP contains an invalid value

<TTP Name>:005 10 14300

22068-006 TtpEvDoicException: DOIC OC-Validity-Duration AVP contains an invalid value

<TTP Name>:006 10 14300

22069-001 TtpEvDoicOlr: Valid DOIC OLR Applied to TTP <TTP Name>:001 0 14308

22070-001 TtpEvDegraded: TTP Degraded, Peer Overload <TTP Name>:001 0 NA

22070-002 TtpEvDegraded: TTP Degraded, Peer Overload Recovery <TTP Name>:002 0 NA

22070-003 TtpEvDegraded: TTP Degraded, Static Rate Limit Exceeded

<TTP Name>:003 0 NA

1

E64830-01 32 Jun 2016


OAM Event-ID OAM Event Name Instance

Throttle Seconds

Associated Measurement

22071-001 TtgEvLossChg: TTG Loss Percent Changed <TTG Name>:001 0 NA

3.5 DSR 7.2 ABORT BUTTON FOR SBR RECONFIGURATION

3.5.1 DescriptionThe DSR 7.1 release introduced the ability for DSR systems with PCA activated to resize SBR databases or migrate them. However, once these actions were initiated it wasn’t possible to abort and restore back to the original configuration. DSR 7.2 introduces a new Abort Button which does allow for SBR database Resizing and Migration activities to be safely cancelled leaving the system back in its original SBR database configuration. This is to be considered as an emergency back-out procedure and not recommended unless absolutely necessary. Part of the Abort process involves the use of an Audit mechanism to clean up all migrated sessions including having the DSR send RAR messages to the Packet Gateway. It is also possible to “force complete” the Abort cleanup by clicking the Complete button and bypass the RAR messaging.

3.5.2 Abort Button Location in NOAM

Figure 22 NOAM SBR Reconfiguration Abort Button

E64830-01 33 Jun 2016


3.6 DSR 7.2 PER APN PER SUBSCRIBER SESSION LIMITING

3.6.1 DescriptionThis feature enhances the behavior of the PDRA function of the PCA application by introducing an additional control over Gx/Gxx session establishment. Earlier releases controlled session establishment by limiting the max number of sessions per IMSI to 10. The DSR 7.2 enhancement continues to limit the max number of sessions per IMSI to 10 but additionally allows a configurable APN session maximum. The default value upon upgrade to DSR 7.2 will be 10 but this can then manually be adjusted to any value between 1-10. Additionally, the DSR has a new configuration to determine how to handle new session establishment attempts for APN’s that currently have the max allowed number of sessions already established. In these situations the DSR can be configured to accept the session while simultaneously deleted the oldest of the currently existing sessions or instead the DSR can be configured to simply block the new session.

3.6.2 GUI Configuration There are two new parameters associated with this feature:

Maximum Allowed Sessions per IMSI

Per IMSI Session Exceeded Treatment

These parameters can be found on the NOAM APN Configuration Screen

Figure 23 NOAM APN Configuration with New Session Limitation Fields

3.7 DSR APPLICATION CHAINING ADDITIONS

3.7.1 DescriptionApplication chaining is a feature that was introduced in DSR 7.0. At that time the supported configuration was limited to RBAR PCA PDRA chaining & RBAR PCA OC-DRA chaining. DSR 7.2 now will support the following additional configurations:

FABRRBAR Application Chaining

When FABR is unable to locate a subscriber within FABR DB the Dest-Host will be set to a value which will trigger RBAR invocation and Range-based routing for SA-HSS.

E64830-01 34 Jun 2016


FABR PCA PDRA Application Chaining

FABR can be used to take a subscribers identity and select a cluster of PDRFs connected to an OC-DRA at a different site or a subset of PDRFs connected to the local site. This will require FABR to be inoked prior to OC-DRA invocation for the same Gx/Gxx request.

FABR PCA OC-DRA Applicatin Chaining.

FABR can be used to take a subscribers identity and select a cluster of OCSs connected to an OC-DRA at a different site or a subset of OCSs connected to the local site. This will require FABR to be inoked prior to OC-DRA invocation for the same Ro (or Sy) request.

3.8 DCL PEG AND EVENT NORMALIZATION

3.8.1 DescriptionSeveral issues with pegs and events have been addressed in this DSR release. The following list hightlights the objectives for these changes:

Coverageo Traffic visibility of priority and color

o Traffic and FSM visibility of all exceptoins

Consistencyo Uniform naming convention by scope and function

o Parity between ingress and egres, congestion points, etc

Cohesiono Eliminate redundant and superfluous metrics

o Strive for complementary metrics

o Maintainable and extensible

The changes are reflected in the delta spreadsheets contained within the MEAL Inserts section of this document.

3.9 TEKELEC SPECIFIC AVP REMOVAL

3.9.1 DescriptionTo accommodate peers which are negatively impacted by the presence of specific AVP’s there is a new capability introduced in DSR 7.2 to allow for the creation of AVP removal lists. Each list contains the following configurable items:

1. Name

2. Direction (Ingress Only, Egress Only, Egress & Ingress)

3. Message Type (Request Only, Answer Only, Answer & Request)

4. AVP Removal List

5. 1 or more AVP’s. Each AVP is specified by the followng attributes: (AVP Code, AVP Name, Vendor Id, Vendor Name)

An AVP Removal List is then available as one of the attributes that can be specified within a Peer Node configuration.

E64830-01 35 Jun 2016


3.9.2 GUI Configuration

Figure 24 New SOAM AVP Removal Lists Table

E64830-01 36 Jun 2016


Figure 25 SOAM Peer Node Table w/New AVP Removal List Field

3.10SDS ENHANCEMENTS

3.10.1 DescriptionSDS 7.2 introduces the following 3 changes:

Capacity Increase

Previous SDS releases supported 500 million routing entities. SDS 7.2 now supports 1 billion. Supported HW is HP Gen8/9.

IMSI and MSISDN Prefix capacity Increase

The SDS 5.0 release enhanced the FABR feature by adding the ability to route messages based upon a range of either MSISDN or IMSI prefix values if a FABR lookup had failed to produce a result. This feature is referred to as “Full Address Resolution with Range Fall Through” and in the SDS 5.0 release it supported a maximum of 1000 prefix entries. SDS 7.2 has increased this limit to 100k.

Note: this feature should not be confused with “FABR/RBAR Application Chaining” which is an entirely different approach which is newly supported in DSR 7.2.

Add Time Stamp to Subscriber Record

SDS 7.2 supports the addition of 2 timestamp fields into subscriber data records. One of the fields will reflect the record creation time and the 2nd field will reflect the time of last modification of the record. This feature will be disabled by default. These new record fields will be visible within the GUI.

<<screenshot not yet available>>

E64830-01 37 Jun 2016


3.11 IDIH ENHANCEMENTS

3.11.1 Description

iDIH 7.2 has been updated to support the DOIC & RADIUS features of DSR 7.2.

3.12DSR/SDS UPGRADE ENHANCEMENTS

3.12.1 DescriptionHealth check procedures are performed at various stages throughout the course of DSR upgrades. 3 different types of health checks are specified:

Advance Upgrade Health Check

Pre Upgrade Health Check

Post Upgrade Health Check

The upgrade enhancement introduced in DSR 7.2 involves the automation of each of these types of health check. In each case the health check is manually initiated via a new button appearing in the NOAM GUI Upgrade screens. Upgrade screens are displayed via a series of tabs on a per server group basis. At the bottom of each server group upgrade screen two checkup related buttons are presented:

1. Checkup – Run specified upgrade health checkup on the selected serer(s) or all servers in the active server group tab.

2. Checkup all – Run specified upgrade health checkup on a Network Element basis. Any servers that may be selected are ignored.

Each of these health checks will result in one of the following:

1. A Pass indication

2. A Fail indication

3. A Pass with minor issues indication

In all cases there will be a creation of 1 or more result files placed within the following directory

/var/TKLC/db/filemgmt/UpgradeHealthCheck

3.11.2 NOAM GUI Health Check Button

E64830-01 38 Jun 2016


Figure 26 NOAM Upgrade Screen w/New Health Check Buttons

E64830-01 39 Jun 2016


4.0 MEAL INSERTS

This section will summarize the changes to Alarms, Measurements and KPIs. The following inserts pertain to DSR 7.2 and deltas with earlier releases 5.1, 6.0, 7.0, and 7.1 Alarms, Measurements, KPIs, and MIBs. Except where noted the attached delta reports relate to systems with all features activated. Some measurements showing up in the reports are internal only and will appear with no associated Group name.

DSR 7.2 GA Release is dsr-7.2.0.0.0-71.24.0

4.1 ALARM/MEASUREMENTS/KPIS/MIBS DSR 7.2

4.2 ALARM/MEASUREMENTS/KPIS/MIBS DELTA (DSR 5.1)

Note the attached report relates to a 5.1 system with only PDRA feature activated. RBAR, FABR, Mediation are not activated.



E64830-01 40 Jun 2016



E64830-01 41 Jun 2016


5.0 REFERENCE LIST DSR 7.2 User Guides for DSR (see customer documentation)

http://docs.oracle.com

Diameter Signaling Router (DSR) 7.2 Core Document Set

DSR 7.1 Release NoticePDFDSR 7.1 Licensing Information User ManualPDF

Planning, Installation, Upgrade, and Disaster Recovery DSR Hardware and Software Installation Procedure 1/2PDFDSR Software Installation and Configuration Procedure 2/2PDFDSR 7.1 Software Upgrade GuidePDFThree-tier Disaster Recovery GuidePDFRMS Productization Installation GuidePDFRMS Productization Disaster Recovery GuidePDFPCA ConfigurationPDFGLA Feature Activation ProcedurePDFCPA Feature Activation ProcedurePDFMediation Feature Activation ProcedurePDFFABR Feature Activation ProcedurePDFRBAR Feature Activation ProcedurePDFMAP-Diameter Feature Activation ProcedurePDFDSR Network Impact ReportWord

Diameter Signaling Router 7.2 Core Document Set Operation, Administration, and Maintenance (OAM) GuidePDFCommunication Agent User's GuidePDFRoadmap to Hardware Documentation (Gen8)PDFPolicy and Charging Application User's GuidePDFDiameter User's GuidePDFMediation User's GuidePDFRange Based Address Resolution (RBAR) User's GuidePDFFull Address Based Resolution (FABR) User's GuidePDFCharging Proxy Application (CPA) and Offline Charging Solution User's GuidePDFIP Front End (IPFE) User's GuidePDFDSR Alarms and KPIs ReferencePDFDiameter Measurements ReferencePDFDiameter Common User's GuidePDFDiameter Administrator's GuidePDFMAP-Diameter IWF User's GuidePDFSS7/SIGTRAN User's GuidePDFTransport Manager User's GuidePDF

E64830-01 42 Jun 2016


Gateway Location Application (GLA) User's GuidePDFRelated Publications ReferencePDF

Integrated Diameter Intelligence Hub (IDIH) 7.2 Document Set

IDIH User's GuidePDFIDIH Audit Viewer Administrator's Guide PDFIDIH Alarm Forwarding Administrator's GuidePDFIDIH Operations, Administration and Maintenance Administrator’s GuidePDFIDIH ProTrace User's Guide PDFIDIH System Alarms User's GuidePDFIDIH Log Viewer User's GuidePDF

E64830-01 43 Jun 2016

Date post:	18-Mar-2018
Category:	Documents
Upload:	vannhan
View:	223 times
Download:	7 times

DSR 7.0 Network Impact Report - Oracle Help Center · Web viewThis software and related...

Documents