oracle communications diameter signaling router · 2016. 12. 5. · oracle® communications...

Oracle® CommunicationsDiameter Signaling RouterSession Binding Repository (SBR) User's Guide

E76926 Revision 01

March 2017

Oracle Communications Diameter Signaling Router Session Binding Repository (SBR) User's GuideCopyright © 2016, 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.................................................................................7Revision History.....................................................................................................................................8Overview.................................................................................................................................................8Scope and Audience..............................................................................................................................8Manual Organization.............................................................................................................................8Documentation Admonishments.........................................................................................................8Related Specifications............................................................................................................................9Locate Product Documentation on the Oracle Help Center Site.....................................................9Customer Training...............................................................................................................................10My Oracle Support (MOS)..................................................................................................................10Emergency Response...........................................................................................................................10

Chapter 2: User Interface Introduction....................................................12User Interface Organization...............................................................................................................13

User Interface Elements...........................................................................................................14Main Menu Options.................................................................................................................15

Missing Main Menu options...............................................................................................................20Common Graphical User Interface Widgets....................................................................................20

Supported Browsers.................................................................................................................21System Login Page...................................................................................................................21Main Menu Icons......................................................................................................................23Work Area Displays.................................................................................................................24Customizing the Splash Page Welcome Message...............................................................27Column Headers (Sorting)......................................................................................................27Page Controls............................................................................................................................27Clear Field Control...................................................................................................................28Optional Layout Element Toolbar.........................................................................................28Filters..........................................................................................................................................29Pause Updates..........................................................................................................................32Max Records Per Page Controls.............................................................................................32

Chapter 3: SBR Introduction......................................................................33The SBR Database.................................................................................................................................34

iiiE76926 Revision 01, March 2017

Database Growth......................................................................................................................35SBR Database Resizing............................................................................................................35SBR Data Migration.................................................................................................................35SBR Database High Availability............................................................................................36SBR Databases Audit...............................................................................................................36

Chapter 4: Configuration............................................................................37SBR Configuration...............................................................................................................................38

SBR Databases...........................................................................................................................38SBR Database Resizing Plans.................................................................................................40SBR Data Migration Plans.......................................................................................................43Database Options.....................................................................................................................45

Chapter 5: Maintenance..............................................................................47SBR Maintenance..................................................................................................................................48

SBR Database Status................................................................................................................48SBR Status..................................................................................................................................50SBR Database Reconfiguration Status...................................................................................51

Alarms, KPIs, and Measurements.....................................................................................................56SBR Alarms and Events...........................................................................................................56SBR KPIs....................................................................................................................................56SBR Measurements..................................................................................................................57

Glossary...............................................................................................................................58

ivE76926 Revision 01, March 2017

List of Figures

Figure 1: Oracle System Login.......................................................................................................................22

Figure 2: Paginated Table................................................................................................................................24

Figure 3: Scrollable Table................................................................................................................................25

Figure 4: Form Page.........................................................................................................................................25

Figure 5: Tabbed Pages....................................................................................................................................26

Figure 6: Tabbed Pages....................................................................................................................................26

Figure 7: Report Output..................................................................................................................................26

Figure 8: Sorting a Table by Column Header..............................................................................................27

Figure 9: Clear Field Control X.......................................................................................................................28

Figure 10: Optional Layout Element Toolbar...............................................................................................28

Figure 11: Automatic Error Notification.......................................................................................................29

Figure 12: Examples of Filter Styles...............................................................................................................30

vE76926 Revision 01, March 2017

List of Tables

Table 1: Admonishments..................................................................................................................................9

Table 2: User Interface Elements....................................................................................................................14

Table 3: Main Menu Options..........................................................................................................................15

Table 4: Main Menu Icons...............................................................................................................................23

Table 5: Example Action Buttons...................................................................................................................27

Table 6: Submit Buttons...................................................................................................................................28

Table 7: Filter Control Elements.....................................................................................................................30

Table 8: SBR Database Elements....................................................................................................................38

Table 9: SBR Database Resizing Plans Elements.........................................................................................41

Table 10: SBR Data Migration Plans Elements.............................................................................................44

Table 11: Database Options Elements...........................................................................................................45

Table 12: SBR Database Status Pane Elements.............................................................................................48

Table 13: SBR Status Elements........................................................................................................................50

Table 14: Reconfiguration Status Pane Elements.........................................................................................51

viE76926 Revision 01, March 2017

Chapter

1Introduction

This chapter contains a brief description of theSession Binding Repository (SBR). The contents

Topics:

• Revision History.....8 include sections about the document scope,• Overview.....8 audience, and organization, how to find related

publications, and how to contact customerassistance.

• Scope and Audience.....8• Manual Organization.....8• Documentation Admonishments.....8• Related Specifications.....9• Locate Product Documentation on the Oracle Help

Center Site.....9• Customer Training.....10• My Oracle Support (MOS).....10• Emergency Response.....10

7E76926 Revision 01, March 2017

Revision History

DescriptionDate

Initial releaseJune 2016

Updated based on support for U-SBRJune 2016

Overview

The SBR User's Guide provides a conceptual overview of SBR's purpose, architecture, and functionality.

It also describes the pages and elements on the SBR GUI (Graphical User Interface), as well as proceduresfor using the SBR interface.

Scope and Audience

This document is intended for anyone responsible for configuring and using the SBR. Users of thismanual must have a working knowledge of telecommunications and network installations.

Manual Organization

This manual is organized into chapters:

• Introduction contains general information about the DSR documentation, the organization of thismanual, and how to get technical assistance.

• User Interface Introduction describes the organization and usage of the application user interface,including information about how the interface options are organized, how to use widgets andbuttons, and how filtering and other page display options work.

• SBR Introduction describes the topology, architecture, components, and functions of the SBR.• Configuration describes configuration of SBR components.• Maintenance describes maintenance and status information for SBR.

Documentation Admonishments

Admonishments are icons and text throughout this manual that alert the reader to assure personalsafety, to minimize possible service interruptions, and to warn of the potential for equipment damage.


Introduction

Table 1: Admonishments

DescriptionIcon

Danger:

(This icon and text indicate the possibility ofpersonal injury.)

Warning:

(This icon and text indicate the possibility ofequipment damage.)

Caution:

(This icon and text indicate the possibility ofservice interruption.)

Topple:

(This icon and text indicate the possibility ofpersonal injury and equipment damage.)

Related Specifications

For information about additional publications related to this document, refer to the Oracle Help Centersite. See Locate Product Documentation on the Oracle Help Center Site for more information on relatedproduct publications.

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.


Introduction

http://docs.oracle.comhttp://www.adobe.comhttp://docs.oracle.com

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.

Customer Training

Oracle University offers training for service providers and enterprises. Visit our web site to view, andregister for, Oracle Communications training:

http://education.oracle.com/communication

To obtain contact phone numbers for countries or regions, visit the Oracle University Education website:

www.oracle.com/education/contacts

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:


Introduction

http://education.oracle.com/pls/web_prod-plq-dad/ou_product_category.getFamilyPage?p_family_id=41&p_mode=Training&sc=WWOU14047594MPP002C005http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=225https://support.oracle.comhttp://www.oracle.com/us/support/contact/index.htmlhttp://www.oracle.com/us/support/contact/index.html

• 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.


Introduction

Chapter

2User Interface Introduction

This section describes the organization and usageof the application's user interface. In it you can find

Topics:

• User Interface Organization.....13 information about how the interface options are• Missing Main Menu options.....20 organized, how to use widgets and buttons, and

how filtering and other page display options work.• Common Graphical User Interface Widgets.....20


User Interface Organization

The user interface is the central point of user interaction within an application. It is a Web-basedgraphical user interface (GUI) that enables remote user access over the network to an application andits functions.

The core framework presents a common set of Main Menu options that serve various applications.The common Main Menu options are:

• Administration• Configuration• Alarms and Events• Security Log• Status and Manage• Measurements• Help• Legal Notices• Logout

Applications build upon this framework to present features and functions. Depending on yourapplication, some or all of the following Main Menu options may appear on the Network Operation,Administration, and Maintenance ( NOAM) GUI:

• Communication Agent• Diameter Common• Diameter• UDR (User Data Repository)• MAP-Diameter IWF• RADIUS (Remote Authentication Dial-In User Service)• SBR (Session Binding Repository)• Policy and Charging• DCA (DOIC Capabilities Announcement) Framework

The DSR System OAM GUI may present even more Main Menu options as listed below. The end resultis a flexible menu structure that changes according to the application needs and features activated.

• Transport Manager• SS7/Sigtran• RBAR (Range Based Address Resolution)• FABR (Full Address Based Resolution)• GLA (Gateway Location Application)• MAP-Diameter IWF• RADIUS• SBR• Mediation• Policy and Charging• DCA Framework• IPFE (IP Front End)


User Interface Introduction

Note that the System OAM (SOAM) Main Menu options differ from the Network OAM (NOAM)options. Some Main Menu options are configurable from the NOAM server and view-only from theSOAM (SOAM) server. This remains true for other applications.

User Interface Elements

Table 2: User Interface Elements describes elements of the user interface.

Table 2: User Interface Elements

FunctionLocationElement

The left side of the banner provides the followinginformation:

Top bar across theweb page

IdentificationBanner

• Displays the company name,• product name and version, and• the alarm panel.

The right side of the banner:

• Allows you to pause any software updates.• Links to the online help for all software.• Shows the user name of the currently logged-in user.• Provides a link to log out of the GUI.

A tree-structured menu of all operations that can beperformed through the user interface. The plus character(+) indicates a menu item contains subfolders.

Left side of screen,under banners

Main Menu

• To display submenu items, click the plus character, thefolder, or anywhere on the same line.

• To select a menu item that does not have submenuitems, click on the menu item text or its associatedsymbol.

Consists of three sections: Page Title Area, Page ControlArea (optional), and Page Area.

Right side of panelunder status

Work Area

• Page Title Area: Occupies the top of the work area. Itdisplays the title of the current page being displayed,date and time, and includes a link to context-sensitivehelp.

• Page Control Area: Located below the Page Title Area,this area shows controls for the Page Area (this area isoptional). When available as an option, filter controlsdisplay in this area. The Page Control Area contains theoptional layout element toolbar, which displays differentelements depending on which GUI page is selected. Formore information, see Optional Layout Element Toolbar.

• Page Area: Occupies the bottom of the work area. Thisarea is used for all types of operations. It displays alloptions, status, data, file, and query screens. Information



FunctionLocationElementor error messages are displayed in a message box at thetop of this section. A horizontal and/or vertical scrollbar is provided when the displayed information exceedsthe page area of the screen. When a user first logs in,this area displays the application user interface page.The page displays a user-defined welcome message. Tocustomize the message, see Customizing the LoginMessage.

The left side of the banner provides the following sessioninformation:

Across the bottom ofthe web page

Session Banner

• The name of the machine to which the user is connected,and whether the user is connected via the VIP or directlyto the machine.

• The HA state of the machine to which the user isconnected.

• The role of the machine to which the user is connected.

The right side of the banner shows the alarm panel.

Main Menu Options

Table 3: Main Menu Options describes all main menu user interface options.

Note: The menu options can differ according to the permissions assigned to a user's log-in account.For example, the Administration menu options do not appear on the screen of a user who does nothave administrative privileges.

Note: Some menu items are configurable only on the Network OAM and view-only on the SystemOAM; and some menu options are configurable only on the System OAM.

Note: Some features do not appear in the main menu until the features are activated.

Table 3: Main Menu Options

FunctionMenu Item

The Administration menu allows the user to:Administration

• General Options. Configure options such as password history andexpiration, login message, welcome message, and the number of failedlogin attempts before an account is disabled

• Set up and manage user accounts• Configure group permissions• View session information• Manage sign-on certificates• Authorize IP addresses to access the user interface• Configure SFTP user information• View the software versions report• Upgrade management including backup and reporting



FunctionMenu Item• Authenticate LDAP servers• Configure SNMP trapping services• Configure an export server• Configure DNS elements

On the NOAM, allows the user to configure:Configuration

• Network Elements• Network Devices• Network Routes• Services• Servers• Server Groups• Resource Domains• Places• Place Associations• Interface and Port DSCP

Allows the user to view:Alarms and Events

• Active alarms and events• Alarm and event history• Trap log

Allows the user to view, export, and generate reports from security loghistory.

Security Log

Allows the user to monitor the individual and collective status of NetworkElements, Servers, HA functions, Databases, KPIs, system Processes, and

Status and Manage

Tasks. The user can perform actions required for server maintenance,database management, data, and ISO file management.

Allows the user to view and export measurement data.Measurements

On the SOAM, allows the user to configure adjacent nodes, configurationsets, or transports. A maintenance option allows the user to perform enable,

Transport Manager(optional)

disable, and block actions on the transport entries. This option only appearswith the DSR application.

Allows the user to configure Remote Servers, Connection Groups, andRouted Services. The user can perform actions to enable, disable, and block

Communication Agent(optional)

connections. Also allows the user to monitor the status of Connections,Routed Services, and HA Services.

On the SOAM, allows the user to configure various users, groups, remotesignaling points, links, and other items associated with SS7/Sigtran; perform

SS7/Sigtran (optional)

maintenance and troubleshooting activities; and provides a command lineinterface for bulk loading SS7 configuration data. This option only appearswith the DSR application.



FunctionMenu Item

Allows the user to view or configure:Diameter Common(optional) • Dashboard, configure on the NOAM; view on both OAMs

• Network Identifiers on the SOAM - MCC Ranges• Network Identifiers on the NOAM - MCCMNC and MCCMNC Mapping• MPs (on the SOAM) - editable Profile parameters and Profile

Assignments

The DSR Bulk Import and Export functions are available on both OAMsfor the data configured on that OAM.

Allows the user to configure, modify, and monitor Diameter routing:Diameter (optional)

• On the NOAMP, Diameter Topology Hiding and Egress Throttle Listconfiguration

• On the SOAM, Diameter Configuration, Maintenance, Reports,Troubleshooting with IDIH, AVP Dictionary, and Diameter Mediationconfiguration

Allows the user to add, edit, store, and manage subscriber and pool data.The user can also monitor the import, export, and subscribing client status.This option only appears with the UDR application.

UDR (User DataRepository) (optional)

Allows the user to configure the following Range-Based Address Resolution(RBAR) settings:

RBAR (Range-BasedAddress Resolution)(optional) • Applications

• Exceptions• Destinations• Address Tables• Addresses• Address Resolutions• System Options

This is accessible from the SOAM only. This option only appears with theDSR application.

Allows the user to configure the following Full Address Based Resolution(FABR) settings:

FABR (Full AddressBased Resolution)(optional) • Applications

• Exceptions• Default Destinations• Address Resolutions• System Options

This is accessible from the SOAM only. This option is only available withthe DSR application.

On the SOAM, allows the user to perform configuration tasks, edit options,and view elements for:

Gateway LocationApplication (optional)

• Exceptions



FunctionMenu Item• Options

GLA can deploy with Policy DRA (in the same DA-MP or a separateDA-MP). This option only appears with the DSR application.

On the SOAM, allows the user to perform configuration tasks, edit options,and view elements for the DM-IWF DSR Application:

MAP-DiameterInterworking (optional)

• DM-IWF Options• Diameter Exception

On the NOAMP, allows the user to perform configuration tasks, edit options,and view elements for the MD-IWF SS7 Application:

• MD-IWF Options• Diameter Realm• Diameter Identity GTA• GTA Range to PC• MAP Exception• CCNDC Mapping

This option only appears with the DSR application.

Allows the user to perform configuration tasks, edit system options, andview elements for:

RADIUS (RemoteAuthentication Dial-InUser Service) (optional) • Network Options

• Message Authenticator Configuration Sets• Shared Secret Configuration Sets• Ingress Status Server Configuration Sets• Message Conversion Configuration Sets• NAS Node


Allows the user to perform configuration tasks, edit system options, andview elements for:

SBR (Session BindingRepository) (optional)

• SBR Databases• SBR Database Resizing Plans• SBR Data Migration Plans• Database Options

Additionally, on the NOAMP, users are allowed to perform maintenancetasks, edit options, and view elements for:

• Maintenance

• SBR Database Status• SBR Status• SBR Database Reconfiguration Status




FunctionMenu Item

Allows the user to make routable decisions to end the reply, drop themessage, or set the destination realm.

Mediation

On the NOAMP, allows the user to perform configuration tasks, edit options,and view elements for:

Policy and Charging(optional)

• General Options• Access Point Names• Policy DRA

• PCRF Pools• PCRF Sub-Pool Selection Rules• Network-Wide Options

• Online Charging DRA

• OCS Session State• Realms• Network-Wide Options

• Alarm Settings• Congestion Options

Additionally on the NOAMP, users are allowed to perform maintenancetasks, edit options, and view elements for:

• Maintenance

• SBR Database Status• SBR Status• SBR Database Reconfiguration Status• Policy Database Query

On the SOAM, allows the user to perform configuration tasks, edit options,and view elements for:

• General Options• Access Point Names• Policy DRA

• PCRFs• Binding Key Priority• PCRF Pools• PCRF Pool to PRT Mapping• PCRF Sub-Pool Selection Rules• Policy Clients• Suspect Binding Removal Rules• Site Options

• Online Charging DRA

• OCSs• CTFs



FunctionMenu Item• OCS Session State• Realms

• Error Codes• Alarm Settings• Congestion Options


Allows the user to perform configuration tasks, edit system options, andview elements for DCA applications:

DCA Framework(optional)

• Custom MEALs (Measurements, Events, Alarms, and Logs)• General Options• Trial MPs assignment• Application Control• System Options

Allows the user to configure IP Front End (IPFE) options and IP List TSAs.

This is accessible from the SOAM server only. This option only appearswith the DSR application.

IPFE (optional)

Launches the Help system for the user interfaceHelp

Product Disclaimers and NoticesLegal Notices

Allows the user to log out of the user interfaceLogout

Missing Main Menu options

Permissions determine which Main Menu options are visible to users. Permissions are defined throughthe Group Administration page. The default group, admin, is permitted access to all GUI optionsand functionality. Additionally, members of the admin group set permissions for other users.

Main Menu options vary according to the group permissions assigned to a user's account. Dependingon your user permissions, some menu options may be missing from the Main Menu. For example,Administration menu options do not appear on your screen if you do not have administrativepermissions. For more information about user permissions, see Group Administration in the OAMsection of the online help, or contact your system administrator.

Common Graphical User Interface Widgets

Common controls allow you to easily navigate through the system. The location of the controls remainsstatic for all pages that use the controls. For example, after you become familiar with the location ofthe display filter, you no longer need to search for the control on subsequent pages because the locationis static.



Supported Browsers

This application supports the use of Microsoft® Internet Explorer 8.0, 9.0, or 10.0.

is designed to work with most modern HTML5 compliant browsers and uses both JavaScript andcookies. Please refer to the Oracle Software Web Browser Support Policy for details

System Login Page

Access to the user interface begins at the System Login page. The System Login page allows users tolog in with a username and password and provides the option of changing the password upon login.The System Login page also features a date and time stamp reflecting the time the page was lastrefreshed. Additionally, a customizable login message appears just below the Log In button.

The user interface is accessed via HTTPS, a secure form of the HTTP protocol. When accessing a serverfor the first time, HTTPS examines a web certificate to verify the identity of the server. The configurationof the user interface uses a self-signed web certificate to verify the identity of the server. When theserver is first accessed, the supported browser warns the user that the server is using a self-signedcertificate. The browser requests confirmation that the server can be trusted. The user is required toconfirm the browser request to gain access.

Customizing the Login MessageBefore logging in, the System Login page appears. You can create a login message that appears justbelow the Log In button on the System Login page.



http://www.oracle.com/technetwork/indexes/products/browser-policy-2859268.html

Figure 1: Oracle System Login

1. From the Main Menu, click Administration > General Options.The General Options Administration page appears.

2. Locate LoginMessage in the Variable column.3. Enter the login message text in the Value column.4. Click OK or Apply to submit the information.

A status message appears at the top of the Configuration Administration page to inform you if theoperation was successful.

The next time you log in to the user interface, the login message text displays.

Accessing the DSR Graphical User InterfaceIn DSR, some configuration is done at the NOAM server, while some is done at the SOAM server.Because of this, you need to access the DSR graphical user interface (GUI) from two servers. CertificateManagement (Single Sign-On) can be configured to simplify accessing the DSR GUI on the NOAMand the SOAM.

For information on configuring Single Sign-On certificates, see OAM > Administration > AccessControl > Certificate Management in the DSR online help.



After the certificates have been configured, you can log into the DSR GUI on any NOAM or SOAM,and then access the DSR GUI on other servers (NOAM or other SOAMs) without having to re-enteryour login credentials.

1. In the browser URL field, enter the fully qualified hostname of the NOAM server, for examplehttps://dsr-no.yourcompany.com.When using Single Sign-On, you cannot use the IP address of the server.

2. When prompted by the browser, confirm that the server can be trusted.The System Login page appears.

3. Enter the Username and Password for your account.The DSR GUI for the NOAM appears.

4. To access the DSR GUI for the SOAM, open another browser window and enter the fully qualifiedhostname of the SOAM.The DSR GUI for the SOAM appears

You can toggle between the DSR GUI on the NOAM and the DSR GUI on the SOAM as you performconfiguration tasks.

Main Menu Icons

This table describes the icons used in the Main Menu.

Table 4: Main Menu Icons

DescriptionNameIcon

Contains a group of operations. If the folder is expanded byclicking the plus (+) sign, all available operations and sub-foldersare displayed. Clicking the minus (-) collapses the folder.

Folder

Contains operations in an Options page.Config File

Contains operations in a Status View page.File withMagnifying Glass

Contains operations in a Data View page.File

Contains operations in a File View page.Multiple Files

Contains operations in a Query page.File with QuestionMark



DescriptionNameIcon

Contains operations related to users.User

Contains operations related to groups.Group

Contains operations related to TasksTask

Launches the Online Help.Help

Logs the user out of the user interface.Logout

Work Area Displays

In the user interface, tables, forms, tabbed pages, and reports are the most common formats.

Note: Screen shots are provided for reference only and may not exactly match a specific application'sGUI.

Tables

Paginated tables describe the total number of records being displayed at the beginning and end of thetable. They provide optional pagination with First|Prev|Next|Last links at both the beginning andend of this table type. Paginated tables also contain action links on the beginning and end of each row.For more information on action links and other page controls, see Page Controls.

Figure 2: Paginated Table

Scrollable tables display all of the records on a single page. The scroll bar, located on the right side ofthe table, allows you to view all records in the table. Scrollable tables also provide action buttons thatoperate on selected rows. For more information on buttons and other page controls, see Page Controls.



Figure 3: Scrollable Table

Note: Multiple rows can be selected in a scrollable table. Add rows one at a time using CTRL-click.Add a span of rows using SHIFT-click.

Forms

Forms are pages on which data can be entered. Forms are typically used for configuration. Formscontain fields and may also contain a combination of pulldown lists, buttons, and links.

Figure 4: Form Page

Tabbed pages

Tabbed pages provide collections of data in selectable tabs. Click on a tab to see the relevant data onthat tab. Tabbed pages also group Retrieve, Add, Update, and Delete options on one page. Click onthe relevant tab for the task you want to perform and the appropriate fields populate on the page.Retrieve is always the default for tabbed pages.



Figure 5: Tabbed Pages

Figure 6: Tabbed Pages

Reports

Reports provide a formatted display of information. Reports are generated from data tables by clickingReport. Reports can be viewed directly on the user interface, or they can be printed. Reports can alsobe saved to a text file.

Figure 7: Report Output



Customizing the Splash Page Welcome Message

When you first log in to the user interface, the splash page appears. Located in the center of the mainwork area is a customizable welcome message. Use this procedure to create a message suitable foryour needs.

1. From the Main Menu, click Administration > General Options.2. Locate Welcome Message in the Variable column.3. Enter the desired welcome message text in the Value column.4. Click OK to save the change or Cancel to undo the change and return the field to the previously

saved value.A status message appears at the top of the page to inform you if the operation was successful.

The next time you log in to the user interface, the new welcome message text is displayed.

Column Headers (Sorting)

You can sort a table by a column by clicking the column header. However, sorting is not necessarilyavailable on every column. Sorting does not affect filtering.

When you click the header of a column that the table can be sorted by, an indicator appears in thecolumn header showing the direction of the sort. See Figure 8: Sorting a Table by Column Header. Clickingthe column header again reverses the direction of the sort.

Figure 8: Sorting a Table by Column Header

Page Controls

User interface pages contain controls, such as buttons and links, that perform specified functions. Thefunctions are described by the text of the links and buttons.

Note: Disabled buttons are grayed out. Buttons that are irrelevant to the selection or current systemstate, or which represent unauthorized actions as defined in Group Administration, are disabled. Forexample, Delete is disabled for users without Global Data Delete permission. Buttons are also disabledif, for example, multiple servers are selected for an action that can only be performed on a single serverat a time.

Table 5: Example Action Buttons contains examples of Action buttons.

Table 5: Example Action Buttons

FunctionAction Button

Inserts data into a table.Insert

Edits data within a table.Edit

Deletes data from table.Delete



FunctionAction Button

Changes the status of a managed object.Change

Some Action buttons take you to another page.

Submit buttons, described in Table 6: Submit Buttons, are used to submit information to the server. Thebuttons are located in the page area and accompanied by a table in which you can enter information.The Submit buttons, except for Cancel, are disabled until you enter some data or select a value for allmandatory fields.

Table 6: Submit Buttons

FunctionSubmit Button

Submits the information to the server, and if successful, returns to the Viewpage for that table.

OK

Submits the information to the server, and if successful, remains on the currentpage so that you can enter additional data.

Apply

Returns to the View page for the table without submitting any informationto the server.

Cancel

Clear Field Control

The clear field control allows you to clear the value from a pulldown list. The clear field control isavailable only on some pulldown fields.

Click the X next to a pulldown list to clear the field.

Figure 9: Clear Field Control X

Optional Layout Element Toolbar

The optional layout element toolbar appears in the Page Control Area of the GUI.

Figure 10: Optional Layout Element Toolbar

The toolbar displays different elements depending on which GUI page is selected. The elements ofthe toolbar that can appear include:

• Filter – Allows you to filter data in a table.• Errors – Displays errors associated with the work area.• Info – Displays information messages associated with the work area.• Status – Displays short status updates associated with the main work area.• Warning – Displays warnings associated with the work area.



NotificationsSome messages require immediate attention, such as errors and status items. When new errors occur,the Errors element opens automatically with information about the error. Similarly, when new statusitems are added, the Status element opens. If you close an automatically opened element, the elementstays closed until a new, unacknowledged item is added.

Figure 11: Automatic Error Notification

Note: Viewing and closing an error does not clear the Errors element. If you reopen the Errors element,previously viewed errors are still in the list.

When new messages are added to Warning or Info, the styling of the element changes to indicate newmessages are available. The styling of the Task element changes when a task changes state (such as,a task begins or ends).

Opening an Element in the ToolbarUse this procedure to open an element in the optional layout element toolbar.

1. Click the text of the element or the triangle icon to open an element.The selected element opens and overlays the work area.

2. Click X to close the element display.

Filters

Filters are part of the optional layout element toolbar and appear throughout the GUI in the PageControl Area. For more information about optional layout element toolbar functionality, see OptionalLayout Element Toolbar.

Filters allow you to limit the data presented in a table and can specify multiple filter criteria. By default,table rows appear unfiltered. Three types of filters are supported, however, not all filtering optionsare available on every page. The types of filters supported include:

• Network Element – When enabled, the Network Element filter limits the data viewed to a singleNetwork Element.

Note: Once enabled, the Network Element filter affect all pages that list or display data relatingto the Network Element.

• Collection Interval – When enabled, the collection interval filter limits the data to entries collectedin a specified time range.

• Display Filter – The display filter limits the data viewed to data matching the specified criteria.



Once a field is selected, it cannot be selected again. All specified criteria must be met in order for arow to be displayed.

The style or format of filters may vary depending on which GUI pages the filters are displayed.Regardless of appearance, filters of the same type function the same.

Figure 12: Examples of Filter Styles

Filter Control ElementsThis table describes filter control elements of the user interface.

Table 7: Filter Control Elements

DescriptionOperator

Displays an exact match.=

Displays all records that do not match the specified filter parameter value.!=

Displays all records with a parameter value that is greater than the specified value.>

Displays all records with a parameter value that is greater than or equal to the specifiedvalue.

>=

Displays all records with a parameter value that is less than the specified value.<

Displays all records with a parameter value that is less than or equal to the specifiedvalue.

1. Click Filter in the optional layout element toolbar.2. Select a Network Element from the Network Element pulldown menu.3. Click Go to filter on the selection, or click Reset to clear the selection.

Records are displayed according to the specified criteria.

Filtering on Collection IntervalThe Collection Interval filter allows a user to limit the data viewed to a specified time interval. Thisfiltering option may not be available on all pages.

1. Click Filter in the optional layout element toolbar.2. Enter a duration for the Collection Interval filter.

The duration must be a numeric value.

3. Select a unit of time from the pulldown menu.The unit of time can be seconds, minutes, hours, or days.

4. Select Beginning or Ending from the pulldown menu.5. Click Go to filter on the selection, or click Reset to clear the selection.


Filtering Using the Display FilterUse this procedure to perform a filtering operation. This procedure assumes you have a data tabledisplayed on your screen. This process is the same for all data tables. However, all filtering operationsare not available for all tables.

1. Click Filter in the optional layout element toolbar.2. Select a field name from the Display Filter pulldown menu.

This selection specifies the field in the table that you want to filter on. The default is None, whichindicates that you want all available data displayed.

The selected field name displays in the Display Filter field.

3. Select an operator from the operation selector pulldown menu.4. Enter a value in the value field.

This value specifies the data that you want to filter on. For example, if you specify Filter=Severitywith the equals (=) operator and a value of MINOR, the table would show only records whereSeverity=MINOR.

5. For data tables that support compound filtering, click Add to add another filter condition. Thenrepeat steps 2 through 4.Multiple filter conditions are joined by an AND operator.

6. Click Go to filter on the selection, or click Reset to clear the selection.




Pause Updates

Some pages refresh automatically. Updates to these pages can be paused by selecting the Pause updatescheckbox. Uncheck the Pause updates checkbox to resume automatic updates. The Pause updatescheckbox is available only on some pages.

Max Records Per Page Controls

Max Records Per Page is used to control the maximum number of records displayed in the page area.If a page uses pagination, the value of Max Records Per Page is used. Use this procedure to changethe Max Records Per Page.

1. From the Main Menu, click Administration > General Options.2. Change the value of the MaxRecordsPerPage variable.

Note: Maximum Records Per Page has a range of values from 10 to 100 records. The default valueis 20.

3. Click OK or Apply.

OK saves the change and returns to the previous page.

Apply saves the change and remains on the same page.

The maximum number of records displayed is changed.



Chapter

3SBR Introduction

This section introduces SBR, key concepts, and basicfunctionality.

Topics:

• The SBR Database.....34SBR is a feature of the Diameter Signaling Router(DSR), which is part of the Oracle product line ofsignaling products.


The SBR Database

SBR provides a common database framework to host database solutions for native or customapplications. The major functionalities of the SBR infrastructure include:

• A common framework to host a generic database that can be used by multiple and different customapplications and for many built-for-purpose databases for some other applications such as PCAor GLA

• A common configuration and maintenance system to enable users to configure and managedatabases for various types of applications, and a common control for database audit

• A common communication mechanism to allow various applications to communicate with differentgeneric or built-for-purpose databases using the DSR ComAgent routing services and a commonstack event library

• A common High Availability (HA) policy management and Resource/Sub-resource managementfor various database

• A common set of Alarms, Events, KPIs, and Measurements for database usages that are applicablefor all applications

An SBR Database consists of several fields:

• A user-configured Database Name• A Database Type (Session, Binding, or Universal)• The name of the Resource Domain that contains the SBR Server Groups• The Number of Server Groups that define the capacity of the SBR database• The Place Association that uses the SBR database• The Owner Application that shows which application has the privileges to write, read, and manage

the configured SBR database

Note: An SBR database must be configured after configuring SBR server groups, resource domains,and binding region, application region, or mated sites place associations.

To use an SBR database, it must register to the local ComAgent for the registered resource (identifiedby the resource IDs) as resource providers to be used by registered resource users (applications) forthe same registered resource. Registering to a ComAgent as a resource provider requires configuringthe SBR server topology and the SBR database on the SBR > Configuration > SBR Databases page,as well as preparing the configured SBR database on the SBR > Maintenance > SBR Database Statuspage.

Once the SBR database is configured and prepared, it is registered to ComAgent as a ComAgentprovider for the assigned resource ID and the assigned sub-resource IDs. Then, the SBR database canbe enabled by activating applications that own and use the SBR database.

While multiple applications may use the same SBR database, the database can have only one ownerapplication associated with it.

The life cycle of a SBR database is related to the application that owns the database:

• While a SBR database can be configured without an owner application being specified at theconfiguration, the SBR database can't be prepared or enabled without an owner application beingconfigured

• After the owner application is activated and configured in the SBR database configuration, the SBRdatabase can be prepared and then be enabled.


SBR Introduction

• The SBR database can be used by the owner application and other custom applications.• The SBR database can be deleted only if the SBR database is configured with no owner application

specified. The owner application field in the SBR database configuration is None.

For further information on configuring an SBR Database, refer to Configuration.

For further information on maintaining an SBR Database, refer to Maintenance.

Database Growth

SBR Databases can be created with different sized session databases for each Policy and ChargingMated Sites instance. Each instance of the Session SBR Database can be sized appropriately for theexpected level of signaling traffic at that set of mated sites.

Session SBR Databases can be resized without loss of policy or charging data and without disruptionto policy or charging signaling. Binding SBR Databases can be resized without loss of binding dataand without disruption to policy signaling.

For further information about how to resize an SBR database, refer to SBR Database Resizing Plans.

SBR Database Resizing

An SBR Resizing Plan is the configuration that identifies the SBR Database to be resized and the TargetResource Domain to which the SBR data will be migrated.

SBR Resizing involves changing the capacity (number of server groups) of an SBR Database by creatinga new Resource Domain (called the Target Resource Domain) for the SBR Database and migrating thedata from the Initial Resource Domain to the Target Resource Domain. The Target Resource Domainmay be larger or smaller than the Initial Resource Domain, allowing the SBR Database to grow orshrink in size.

For further information on configuring SBR Database Resizing Plans, refer to SBR Database ResizingPlans.

SBR Data Migration

SBR Data Migration is used when the SBR Database topology is to be changed for session databasesor universal databases. SBR Data Migration is the process of moving data from the Initial to TargetSBR Database by creating new records in the target and allowing records in the initial to be removedby normal PCA Diameter signaling.

There are multiple situations in which SBR Data Migration may occur:

• Mating (combining SBR Databases when transitioning from stand-alone PCA DSR sites to matedPCA DSR sites or stand-alone DCA sites to mated DCA sites)

• Un-mating (Separating SBR Databases when transitioning from mated PCA DSR sites to stand-alonePCA DSR sites or mated DCA sites to stand-alone DCA sites)

• Re-mating (Swapping mate relationships between two sets of mated sites)

For further information on configuring SBR Data Migration Plans, refer to SBR Data Migration Plans.


SBR Introduction

SBR Database High Availability

The SBR infrastructure provides a High Availability (HA) database solution for native and customapplications. Two HA policies are used for the SBR databases and various HA configurations aresupported (such as Active, Active/Standby, Active/Spare, Active/Standby/Spare, andActive/Standby/Spare/Spare). Binding SBR Databases are associated with one HA policy, whileSession and Universal SBR Databases are associated with a different policy. Universal SBR Databasescan coexist on the same SBR server groups with Session SBR Databases. However, Universal SBRDatabases cannot coexist on the same server groups with Binding SBR Databases.

SBR Databases Audit

SBR performs audit functions on all SBR database tables to verify the validities and staleness of thedatabase records and remove those invalid or stale records from the databases.

The frequency of audit functions is configured in the Audit Operation Rate field on the SBR >Configuration > Database Options GUI page. The SBR database audit function runs continuouslythrough all SBR database tables until it is suspended automatically due to the local SBR MP congestion.Audit suspension can occur for several reasons:

• Congestion of the SBR server running in the audit• Binding audit will not send audit messages to session SBRs that are in congestion• Binding audit is suspended if session integrity messaging reaches an engineering configurable

level

The Audit Operation Rate applies to all SBR Database audits, regardless of the database type.

Each active SBR server runs the audit independently:

• Each table is audited no more than once per ten minute period• Each active SBR generates an audit statistics report for each table it audits whenever a pass of that

table is completed

At the end of each audit cycle, the SBR audit function generates a report with all the audit statistics.


SBR Introduction

Chapter

4Configuration

The SBR > Configuration GUI pages for SBRcomponents provide fields for entering the

Topics:

• SBR Configuration.....38 information needed to manage SBR configurationin the DSR.


SBR Configuration

This section describes the SBR > Configuration GUI pages.

SBR Databases

On the SBR > Configuration > SBR Databases page on an Active NO, an SBR Database can beconfigured. For each database the Resource Domain, number of Server Groups, and Place Associationare defined.

Note: SBR Database is also available to be viewed on the SO GUI. However, these options are onlyable to be sorted and filtered on the SO. Modifying these options is only permissible on the NO.

The fields are described in SBR Database elements.

SBR Database elementsTable 8: SBR Database Elements describes the elements on the SBR > Configuration > SBR Databasespage on the NO GUI.

Table 8: SBR Database Elements

Data Input NotesDescriptionFields (* indicates arequired field)

Format: Text boxA name that uniquely identifies the SBRDatabase.

Database Name*

Default: N/A

Range: A 32-character string.Valid characters arealphanumeric and underscore.Must contain at least one alphaand must not start with a digit.

Format: Drop-down ListThe type of SBR Database.Database Type*

Default: N/ASelect Binding for a Policy Binding database,select Session for a Policy DRA or Online Range: Binding, Session, or

UniversalCharging DRA Session database, or selectUniversal for a Universal SBR database.

Format: Drop-down ListThe Policy Session or Policy BindingResource Domain that contains the SBR

Resource Domain*

Default: N/AServer Groups configured for use by thisdatabase. Range: Configured Resource

Domains matching the selectedSelect the Resource Domain that will hostthis database. Database Type that have notalready been assigned to a

Database.


Configuration


Format: Text boxThe number of SBR Server Groups requiredto host this database.

Number of ServerGroups* Default: N/A

Enter or change the number of ServerGroups necessary to support the desired Range: 1 to 8

capacity of the database. If the selectedResource Domain already contains ServerGroups, the number of Server Groups in theResource Domain is displayed in the field,but can be overridden as desired.

Format: Drop-down ListThe Place Association that contains thePlaces (Sites) that will use this database.

Place Association*

Range: Configured PlaceAssociations matching theSelect the Place Association that is to use this

SBR Database. selected Database Type that havenot already been assigned to aDatabase

Format: Drop-down ListThe name of the application that owns theconfigured SBR DB.

Owner Application

Default: None• If the database type is Session, PCA is

automatically displayed as the OwnerApplication

Range: None, PCA, andconfigured DCA applicationnames

• If the database type is Binding, PCA isautomatically displayed as the OwnerApplication

• If the database type is Universal, selectthe Owner Application for the SBRdatabase

Inserting SBR DatabasesUse this task to insert an SBR Databases on the NO GUI.

The fields are described in SBR Database elements.

1. Select SBR > Configuration > SBR Databases.The SBR > Configuration > SBR Databases page appears.

2. Click Insert.3. Enter a unique Database Name in the Database Name field.4. Select a Database Type from the dropdown list.5. Select a Resource Domain from the dropdown list.6. Enter a number of Server Groups in the Number of Server Groups field.7. Select a Place Association from the dropdown list.8. Select an Owner Application from the dropdown list.9. Click:


Configuration

• Ok to save the new SBR Database and return to the SBR > Configuration > SBR Databasespage.

• Apply to save the new SBR Database and remain on the page.• Cancel to return to the SBR > Configuration > SBR Databases page without saving any changes.

Deleting an SBR DatabaseUse this task to delete an SBR Database.

1. Select SBR > Configuration > SBR Databases.The SBR > Configuration > SBR Databases page appears.

2. Select the SBR Database to be deleted.3. Click Delete.

A popup window appears to confirm the delete.4. Click:

• Ok to delete the SBR Database.• Cancel to cancel the delete function and return to the SBR > Configuration > SBR Databases

page.

If Ok is clicked and a problematic condition exists, an error message appears:

• The entry no longer exist.• A specific SBR Database must be Disabled prior to deletion.• A specific SBR Database is referenced by at least one SBR Database Resizing Plan.• A specific SBR Database is reference by at least one SBR Data Migration Plan.

SBR Database Resizing Plans

On the SBR > Configuration > SBR Database Resizing Plans page on an Active NO, SBR DatabaseResizing Plans can be configured. An SBR Database Resizing plan allows for changing the size of arunning SBR Database.

Each database is to be resized by migrating records from the Initial Resource Domain to the TargetResource Domain. Creation of an SBR Database Resizing Plan has no effect on the running database.After creating a Resizing Plan, go to the SBR Database Reconfiguration Status screen to prepare,start and monitor the migration. Once migration has completed, or has been cancelled, the SBR DatabaseResizing Plan should be deleted.

Note: SBR Data Migration Plans are configurable only on an Active NO, but are viewable on NO andSO servers.

Resizing Plans can be configured prior to the start of the plan's execution.

The fields are described in SBR Database Resizing Plans elements.

SBR Database Resizing Plans elementsTable 9: SBR Database Resizing Plans Elements describes the elements on the SBR > Configuration >SBR Database Resizing Plans page on the NO GUI.


Configuration

Table 9: SBR Database Resizing Plans Elements


Format: Text boxA name that uniquely identifies the SBRDatabase Resizing Plan

Plan Name*

Default: N/A


Format: Drop-down ListThe SBR Database to be resizedDatabase Name*

Default: N/A

Range: List of configuredDatabases eligible to be resized

This read only field displays theResource Domain associatedwith the selected database.

The Resource Domain configured for theselected database.

Initial ResourceDomain

This read-only field displays theDatabase Type associated withthe selected database.

The type of SBR DatabaseDatabase Type

This read only field displays thenumber of Server Groups

The number of Server Groups hosting thisdatabase.

Initial Number ofServer Groups

contained in the Initial ResourceDomain.

Format: Drop-down ListThe Resource Domain into which thedatabase is to be migrated.

Target ResourceDomain* Default: N/A

Select the Resource Domain that will hostthe resized database Range: Configured ResourceDomains eligible for use as a

target resource domain for thisresizing plan

Format: Text boxThe total number of Policy SBR ServerGroups required to support the migrated orresized database.

Target Number ofServer Groups* Default: N/A

Range:1 to 8Enter the total number of Server Groupsnecessary to support the capacity of theresized database, including any servergroups that will be reused from the originalresource domain.


Configuration

Inserting SBR Database Resizing PlansUse this task to insert an SBR Database Resizing Plans on the NO GUI.


1. Select SBR > Configuration > SBR Database Resizing Plans.The SBR > Configuration > SBR Database Resizing Plans page appears.

2. Click Insert.3. Enter a unique Plan Name in the Plan Name field.4. Select a Database Name from the dropdown list.5. The Initial Resource Domain field is read only.6. The Database Type field is read only.7. The Initial Number of Server Groups field is read only.8. Select a Target Resource Domain from the dropdown list.9. The Target Number of Server Groups field initially displays the number of Server Groups

configured for the selected Target Resource Domain. However, this value may be modified to anyvalue from 1 to 8. Refer to Editing SBR Database Resizing Plans for information on modifying theTarget Number of Server Groups value.

10. Click:

• Ok to save the new SBR Database Resizing Plan and return to the SBR > Configuration > SBRDatabase Resizing Plans page.

• Apply to save the new SBR Database Resizing Plan and remain on the page.• Cancel to return to the SBR > Configuration > SBR Database Resizing Plans page without

saving any changes.

Editing SBR Database Resizing PlansUse this task to edit an SBR Database Resizing Plans on the NO GUI.



2. Click Edit.3. Edit the Plan Name in the Plan Name field.4. Select a Database Name from the dropdown list.5. The Initial Resource Domain field is read only.6. The Database Type field is read only.7. The Initial Number of Server Groups field is read only..8. Select a Target Resource Domain from the dropdown list.9. If needed, edit the total number of Server Groups needed to support the capacity of the resized

database in the Target Number of Server Groups field.10. Click:

• Ok to save the edited SBR Database Resizing Plan and return to the SBR > Configuration >SBR Database Resizing Plans page.


Configuration

• Apply to save the edited SBR Database Resizing Plan and remain on the page.• Cancel to return to the SBR > Configuration > SBR Database Resizing Plans page without

saving any changes.

Deleting an SBR Database Resizing PlanUse this task to delete an SBR Database Resizing Plan.

Note: The SBR > Configuration > SBR Database Resizing Plans page is also available to be viewedon the SO GUI. However, these options are only able to be sorted and filtered on the SO. Modifyingthese options is only permissible on the NO.


2. Select the SBR Database Resizing Plan to be deleted.3. Click Delete.

A popup window appears to confirm the delete.4. Click:

• Ok to delete the SBR Database Resizing Plan.• Cancel to cancel the delete function and return to the SBR > Configuration > SBR Database

Resizing Plans page.

If Ok is clicked, but the SBR Database Resizing Plan is not in the Planned administrative state orin the Complete administrative state with an operational status of Migration Plan Completed, anerror is displayed.

SBR Data Migration Plans

On the SBR > Configuration > SBR Data Migration Plans page on an Active NO, an SBR DataMigration Plan can be configured.

SBR Data Migration is the process of moving data from an Initial SBR Database to a Target SBR Databaseby creating new records in the target and allowing records in the initial to be removed by normal PCADiameter signaling.

Creation of an SBR Data Migration Plan has no effect on either database. After creating a Data MigrationPlan, go to the SBR Database Reconfiguration Status screen to prepare, start and monitor the migration.Once migration has completed, or has been cancelled, the SBR Data Migration Plan should be deleted.

Note: SBR Data Migration Plans are configurable only on an Active NO, but are viewable on NO andSO servers.

Data Migration Plans can be configured prior to the start of the plan's execution.

The fields are described in SBR Data Migration Plans elements.

SBR Data Migration Plans elementsTable 10: SBR Data Migration Plans Elements describes the elements on the SBR > Configuration > SBRData Migration Plans page on the NO GUI.


Configuration

Table 10: SBR Data Migration Plans Elements


Format: Text boxA name that uniquely identifies the SBR DataMigration Plan.

Plan Name*

Default: N/A


Format: Drop-down ListThe type of data migration plan that thisplan is to be a part of.

Migration Type*

Default: N/A

Range: Un-Mating, Mating,Re-Mating

Format: Drop-down ListA name that uniquely identifies the databasefrom which records are to be migrated.

Initial Database*

Default: N/A

Range: List of configuredDatabases eligible to be thesource of a migration

This read only field displays thePlace Association configured forthe Target Database.

The Place Association configured to use theInitial Database.

Initial PlaceAssociation

Format: Drop-down ListA name that uniquely identifies the databaseto which records are to be migrated.

Target Database*

Default: N/A

Range: List of configuredDatabases eligible to be the targetof a migration

This read only field displays thePlace Association configured forthe Target Database.

The Place Association configured to use theTarget database.

Target PlaceAssociation

Inserting SBR Data Migration PlansUse this task to insert an SBR Data Migration Plans on the NO GUI.

The fields are described in SBR Data Migration Plans elements.

1. Select SBR > Configuration > SBR Data Migration Plans.The SBR > Configuration > SBR Data Migration Plans page appears.

2. Click Insert.3. Enter a unique Plan Name in the Plan Name field.


Configuration

4. Select a Migration Type from the dropdown list.5. Select an Initial Database from the dropdown list.6. The Initial Place Assoication field is read only.7. Select a Target Database from the dropdown list.8. The Target Place Assoication field is read only.9. Click:

• Ok to save the new SBR Data Migration Plan and return to the SBR > Configuration > SBRData Migration Plans page.

• Apply to save the new SBR Data Migration Plan and remain on the page.• Cancel to return to the SBR > Configuration > SBR Data Migration Plans page without saving

any changes.

Deleting an SBR Data Migration PlanUse this task to delete an SBR Data Migration Plan.

1. Select SBR > Configuration > SBR Data Migration Plans.The SBR > Configuration > SBR Data Migration Plans page appears.

2. Select the SBR Data Migration Plan to be deleted.3. Click Delete.

A popup window appears to confirm the deletion.4. Click:

• Ok to delete the SBR Data Migration Plan.• Cancel to cancel the delete function and return to the SBR > Configuration > SBR Data

Migration Plans page.

Database Options

On the SBR > Configuration > Database Options page on an Active NO, database options can beconfigured.

The fields are described in Database Options elements.

Database Options elementsTable 11: Database Options Elements describes the elements on the SBR > Configuration > DatabaseOptions page on the NO GUI.

Table 11: Database Options Elements

Data Input NotesDescriptionField

Format: Text boxThe maximum rate at which the databaserecords are validated. The users may

Audit Operation Rate

Default: 50000 per secondexchange the database audit rate basedon, for example, Diameter signalling Range: 25000-50000 per secondtraffic load, the number of databases to


Configuration

Data Input NotesDescriptionFieldbe audited, and the size of the databases.The larger the rate it, the more impact onthe system performance the audit maycause.

Editing Database OptionsUse this task to edit database options on the NO GUI.

1. Select SBR > Configuration > Database Options.The SBR > Configuration > Database Options page appears.

The fields are described in Database Options elements.

2. Edit the Audit Operation Rate.3. Click:

• Apply to save the data written to the database and update the General Options screen.• Cancel to avoid making changes to the configuration data.


Configuration

Chapter

5Maintenance

This chapter describes or indicates where to findinformation that can be used for SBR:

Topics:

• SBR Maintenance.....48• Maintenance and status information that is

maintained by the SBR Configuration and• Alarms, KPIs, and Measurements.....56Maintenance components and displayed on theSBR > Maintenance pages.

• Descriptions of SBR alarms, KPIs, andmeasurements


SBR Maintenance

This section describes the SBR > Maintenance GUI pages on the NOAM.

SBR Database Status

The SBR > Maintenance > SBR Database Status page is used to prepare, enable, disable, and monitorthe status of SBR Databases that have been configured on the SBR > Configuration > SBR Databases.

Fields are described in SBR Database Status elements.

SBR Database Status elementsTable 12: SBR Database Status Pane Elements describes the elements on the SBR > Maintenance > SBRDatabase Status page.

The main SBR Database Status pane shows the details for a configured SBR Database.

Table 12: SBR Database Status Pane Elements

DescriptionElements

The name of the configured SBR DatabaseDatabase Name

The state that the operator commands the SBR Database to be in(Disable, Prepare, or Enable)

Administrative State

The state that the SBR Database is actually in, as reported by theresource users and resource providers of the database

Operational Status

The status of the SBR Database as reported by all resource users of thedatabase

Resource User OperationalReason

The status of the SBR Database as reported by all resource providers(such as the active server of each SBR server group hosting the database)of the database

Resource ProviderOperational Reason

Set to No if no SBR Database Reconfiguration is in progress that containsthis database. Set to Resizing if a Resizing Plan for that database is in

Reconfiguration in Progress

progress. Set to Data Migration if an SBR Data Migration Plan specifyingthe SBR Database as either the Initial Database or the Target Databaseis in progress

Set to Session if the SBR Database Type is Session. Set to Binding if theSBR Database Type is Binding. Suffixed with (Target) if the SBRDatabase is the target of an SBR Data Migration Plan

Database Type

The Resource User pane and the Resource Provider panes provide additional details when the ResourceUser Operational Status or Resource Provider Operational Status for an SBR Database are coloredyellow or red, which indicates a problem. If no problems exist, the Resource User and Resource Providerpanes are empty.


Maintenance

Managing an SBR DatabaseIn order to use the SBR Database, configure the options on the SBR Database Status screen.

1. Select the new SBR Database row and click Prepare. Preparing the database allows the user toverify connectivity between the SBR Database and all users of that SBR Database before the SBRDatabase is used by the PCA application.

If the operational status changes to Prepared, then

• All ComAgent connections applicable to the database are connected• An active SBR server is available for each Policy and Charging SBR Server Group in the SBR

Database's Resource Domain• All resource users have received notification that all portions of the SBR Database (one portion

per SBR server group) are available

Once the SBR Database is in the Prepare administrative state, then the operational status can takea value:

• Preparing - At least one resource user of the SBR Database cannot successfully access at leastone portion of the SBR Database

• Prepared - All resource users of the SBR Database can successfully access all portions of theSBR Database

2. Select the Prepared SBR Database row and click Enable. Enabling the database allows the PCAapplication to begin using the database to store and retrieve binding or session records

If the operational status was Preparing at the time Enable was clicked, then some resource userscannot successfully access the SBR Database. A confirmation dialog appears to warn that thedatabase is not entirely ready to be Enabled. The user can choose to cancel the Enable or proceeddespite the warning. If the user proceeds, the operational status in the Enable state will likely beeither Unavailable or Degraded.

Once the SBR Database is in the Enable administrative state, the SBR Database Status screen canbe used to monitor the status of the database. An Enabled database will have one of severaloperational statuses:

• Normal - Everything related to the SBR Database is functioning normally• Degraded - At least one resource user of the SBR Database cannot successfully access at least

one portion of the database• Unavailable - None of the resource users of the SBR Database can successfully access any portion

of the database• Congested - At least one of the resource users of the SBR Database is experiencing congestion

for at least one portion of the SBR Database. This problem could be due to congestion at anactive SBR server of the database, or due to congestion of a ComAgent connection between theresource user and an active SBR server. Both Degraded and Unavailable take precedence overCongested. For example, if an SBR Database is both Degraded and Congested, then theOperational Status will be Degraded.

3. If it becomes necessary to Disable an SBR Database, select the row for the desired SBR Databaseon the SBR Database Status screen and click Disable.

If the SBR Database was in the Enable administrative state prior to clicking Disable, a confirmationdialog appears to warn about impacts on the PCA application. The user can choose to cancel theDisable or proceed despite the warning.


Maintenance

If the SBR Database was in the Prepare administrative state prior to clicking Disable, no confirmationdialog appears since the database is not being used by PCA.

Once Disable is clicked, the operational status takes on one of several values:

• Users Detaching - waiting for all resource users to detach from the SBR Database• Providers Detaching - waiting for all resource providers to detach from the SBR Database• Disabled - all resource users and resource providers are detached from the SBR Database and

the SBR Database may be safely deleted

SBR Status

The SBR > Maintenance > SBR Status page displays a collapsed or expanded detailed report for SBR.The data is displayed within Server Groups by configured Place Associations.

Fields are described in SBR Status elements.

SBR Status elementsTable 13: SBR Status Elements describes the elements on the SBR > Maintenance > SBR Status page,which displays SBR Server Status data within Server Groups that are assigned to each type of PlaceAssociation.

Each tab name was configured on the Configuration > Place Associations GUI page.

Table 13: SBR Status Elements

Data Input NotesDescriptionElements

The page is view-only.A list of all configured Server Groups that areassigned to the Binding Region Place Association.

Binding Region tab

The Server Group ineach row under the tabThe Resource Domain Name and the Resource

Domain Profile of each Server Group is shown. can be expanded orcollapsed by clicking onThe Server Name, Resource HA Role of the Server,

the server's Congestion Level, and a list of Sub the + symbol, to list theServers that areResource

oracle communications diameter signaling router · 2016. 12. 5. · oracle® communications...

Documents