gateway location application (gla) release 8 · select 2 for new service request 2. select 3 for...

Tekelec PlatformGateway Location Application (GLA)

Release 8.2

E89011

January 2018

Tekelec Platform Gateway Location Application (GLA), Release 8.2

E89011

Copyright © 2011, 2018, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions onuse 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. Ifyou 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 onbehalf 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 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 theprograms, 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 thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused 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 MicroDevices. 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 unlessotherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliateswill not be responsible for any loss, costs, or damages incurred due to your access to or use of third-partycontent, products, or services, except as set forth in an applicable agreement between you and Oracle.

This documentation is in preproduction status and is intended for demonstration and preliminary use only. Itmay not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliatesare not responsible for and expressly disclaim all warranties of any kind with respect to this documentationand will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

The information contained in this document is for informational sharing purposes only and should beconsidered in your capacity as a customer advisory board member or pursuant to your beta trial agreementonly. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon inmaking purchasing decisions. The development, release, and timing of any features or functionalitydescribed in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusiveproperty of Oracle. Your access to and use of this confidential material is subject to the terms and conditionsof your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetworkAgreement, Oracle distribution agreement, or other license agreement which has been executed by you andOracle and with which you agree to comply. This document and information contained herein may not bedisclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent ofOracle. This document is not part of your license agreement nor can it be incorporated into any contractualagreement with Oracle or its subsidiaries or affiliates.

Contents

1 Introduction

Revision History ....................................................................................................................................... 1-1

Overview.................................................................................................................................................... 1-1

Scope and Audience ................................................................................................................................. 1-1

Manual Organization ............................................................................................................................... 1-1

Documentation Admonishments ........................................................................................................... 1-2

Related Publications ................................................................................................................................. 1-2

Locate Product Documentation on the Oracle Help Center Site ....................................................... 1-2

Customer Training.................................................................................................................................... 1-3

My Oracle Support (MOS)....................................................................................................................... 1-3

Emergency Response................................................................................................................................ 1-3

2 User Interface Introduction

User Interface Organization .................................................................................................................... 2-1

User Interface Elements................................................................................................................... 2-2

Main Menu Options ......................................................................................................................... 2-5

Missing Main Menu options ................................................................................................................. 2-11

Common Graphical User Interface Widgets ....................................................................................... 2-11

Supported Browsers....................................................................................................................... 2-11

System Login Page ......................................................................................................................... 2-12

Main Menu Icons............................................................................................................................ 2-13

Work Area Displays ....................................................................................................................... 2-14

Customizing the Splash Page Welcome Message...................................................................... 2-17

Column Headers (Sorting) ............................................................................................................ 2-17

Page Controls .................................................................................................................................. 2-17

Clear Field Control ......................................................................................................................... 2-18

Optional Layout Element Toolbar................................................................................................ 2-18

Filters................................................................................................................................................ 2-20

Pause Updates................................................................................................................................. 2-22

Max Records Per Page Controls ................................................................................................... 2-22

iii

3 The Gateway Location Application

The Gateway Location Application (GLA) ........................................................................................... 3-1

Gateway Location Application (GLA) Description ............................................................................. 3-1

GLA GUI Conventions .................................................................................................................... 3-2

GLA Functions.................................................................................................................................. 3-2

ComAgent Connectivity for GLA.................................................................................................. 3-3

Ingress Message Rate Alarming..................................................................................................... 3-3

GLA Operational Status .................................................................................................................. 3-3

4 Gateway Location Application Configuration

GLA Configuration Overview ................................................................................................................ 4-1

GLA Exceptions ........................................................................................................................................ 4-1

Configure GLA Exceptions elements ............................................................................................ 4-2

Configuring GLA Exceptions ......................................................................................................... 4-2

GLA System Options................................................................................................................................ 4-3

Configure GLA System Options elements.................................................................................... 4-4

Configuring GLA System Options................................................................................................. 4-5

GLA Alarm Settings ................................................................................................................................. 4-6

Configure GLA Alarm Settings elements ..................................................................................... 4-7

Configuring GLA Alarm Settings .................................................................................................. 4-7

Post Configuration Activities.................................................................................................................. 4-8

Enable the GLA................................................................................................................................. 4-8

ComAgent and SBR Status Verification ........................................................................................ 4-8

Verify Application Route Table ...................................................................................................... 4-9

Enable GLA Query Client Connections ........................................................................................ 4-9

Bulk Import and Export................................................................................................................. 4-10

iv

List of Figures

2-1 Oracle System Login................................................................................................................. 2-122-2 Paginated Table.......................................................................................................................... 2-152-3 Scrollable Table.......................................................................................................................... 2-152-4 Form Page................................................................................................................................... 2-162-5 Tabbed Pages.............................................................................................................................. 2-162-6 Tabbed Pages.............................................................................................................................. 2-162-7 Report Output............................................................................................................................ 2-172-8 Sorting a Table by Column Header......................................................................................... 2-172-9 Clear Field Control X................................................................................................................ 2-182-10 Optional Layout Element Toolbar........................................................................................... 2-192-11 Automatic Error Notification................................................................................................... 2-192-12 Examples of Filter Styles.......................................................................................................... 2-20

v

List of Tables

1-1 Admonishments........................................................................................................................... 1-22-1 User Interface Elements.............................................................................................................. 2-32-2 Main Menu Options.................................................................................................................... 2-62-3 Main Menu Icons....................................................................................................................... 2-132-4 Example Action Buttons........................................................................................................... 2-182-5 Submit Buttons........................................................................................................................... 2-182-6 Filter Control Elements............................................................................................................. 2-203-1 Ingress Message Rate Settings................................................................................................... 3-34-1 Configure GLA Exception Elements......................................................................................... 4-24-2 Configure GLA System Options Elements.............................................................................. 4-44-3 Configure GLA Alarm Settings Elements................................................................................ 4-7

vii

1Introduction

This chapter contains a brief description of the Gateway Location Application (GLA)feature. The contents include sections about the document scope, audience, andorganization; how to find related publications; and how to contact Customer Supportfor assistance.

Revision History

Date Description

June 2016 Accessibility changes throughout.

OverviewThis documentation:

• Gives a conceptual overview of the application's purpose, architecture, andfunctionality

• Describes the pages and fields on the application GUI (Graphical User Interface)

• Provides tasks for using the application interface

• Explains the organization of, and how to use, the documentation

Scope and AudienceThis document is intended for anyone responsible for configuring and using theEAGLE XG DSR Gateway Location Application functionality. Users of this manualmust have a working knowledge of telecommunications and network installations.

Manual OrganizationThis manual is organized into the following chapters:

• Introduction contains general information about the Gateway LocationApplication (GLA) documentation, the organization of this document, and how toget technical assistance.

• User Interface Introduction describes the organization and usage of theapplication user interface. In it you can find information about how the interfaceoptions are organized, how to use widgets and buttons, and how filtering andother page display options work.

Introduction 1-1

• The Gateway Location Application describes the topology, architecture,components, and functions of the GLA.

• Gateway Location Application Configuration describes configuration of GLAapplication components.

Documentation AdmonishmentsAdmonishments are icons and text throughout this manual that alert the reader toassure personal safety, to minimize possible service interruptions, and to warn of thepotential for equipment damage.

Table 1-1 Admonishments

Icon Description

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

Related PublicationsFor information about additional publications related to this document, refer to theOracle Help Center site. See Locate Product Documentation on the Oracle Help CenterSite for more information on related product publications.

Locate Product Documentation on the Oracle Help Center SiteOracle Communications customer documentation is available on the web at the OracleHelp Center (OHC) site, http://docs.oracle.com. You do not have to register to accessthese documents. Viewing these files requires Adobe Acrobat Reader, which can bedownloaded 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 OracleCommunications documentation link.

The Communications Documentation page displays. Most products covered bythese documentation sets display under the headings "Network Session Deliveryand Control Infrastructure" and "Platforms."

4. Click on your Product and then the Release Number.

Documentation Admonishments

1-2 Tekelec Platform Gateway Location Application (GLA)

http://docs.oracle.com

http://www.adobe.com

http://docs.oracle.com

A list of the entire documentation set for the selected product and release displays.

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

Customer TrainingOracle University offers training for service providers and enterprises. Visit our website to view, and register for, Oracle Communications training at http://education.oracle.com/communication

To obtain contact phone numbers for countries or regions, visit the Oracle UniversityEducation web site at www.oracle.com/education/contacts

My Oracle Support (MOS)MOS (https://support.oracle.com) is your initial point of contact for all productsupport and training needs. A representative at Customer Access Support (CAS) canassist you with MOS registration.

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

1. Select 2 for New Service Request

2. Select 3 for Hardware, Networking and Solaris Operating System Support

3. 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 are connected to a live agent who can assist you with MOS registration andopening a support ticket.

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

Emergency ResponseIn the event of a critical service situation, emergency response is offered by theCustomer Access Support (CAS) main number at 1-800-223-1711 (toll-free in the US),or by calling the Oracle Support hotline for your local country from the list at http://www.oracle.com/us/support/contact/index.html. The emergency response providesimmediate coverage, automatic escalation, and other features to ensure that the criticalsituation is resolved as rapidly as possible.

A critical situation is defined as a problem with the installed equipment that severelyaffects service, traffic, or maintenance capabilities, and requires immediate correctiveaction. Critical situations affect service and/or system operation resulting in one orseveral of these situations:

• A total system failure that results in loss of all transaction processing capability

• Significant reduction in system capacity or traffic handling capability

• Loss of the system’s ability to perform automatic system reconfiguration

Customer Training

Introduction 1-3

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

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

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=225

https://support.oracle.com

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




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

Any other problem severely affecting service, capacity/traffic, billing, andmaintenance capabilities may be defined as critical by prior discussion and agreementwith Oracle.

Emergency Response


2User Interface Introduction

This section describes the organization and usage of the application's user interface. Init you can find information about how the interface options are organized, how to usewidgets and buttons, and how filtering and other page display options work.

User Interface OrganizationThe user interface is the central point of user interaction within an application. It is aWeb-based graphical user interface (GUI) that enables remote user access over thenetwork to an application and its functions.

The core framework presents a common set of Main Menu options that serve variousapplications. 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. Dependingon your application, some or all of the following Main Menu options may display onthe 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)

User Interface Introduction 2-1

• Policy and Charging

• DCA (DOIC Capabilities Announcement) Framework

The DSR System OAM GUI may present even more Main Menu options as listedbelow. The end result is a flexible menu structure that changes according to theapplication 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)

Note that the System OAM (SOAM) Main Menu options differ from the NetworkOAM (NOAM) options. Some Main Menu options are configurable from the NOAMserver and view-only from the SOAM (SOAM) server. This remains true for otherapplications.

User Interface ElementsTable 2-1 describes elements of the user interface.

User Interface Organization


Table 2-1 User Interface Elements

Element Location Function

Identification Banner Top bar across the web page The left side of the bannerprovides the followinginformation:• Displays the company

name,• product name and

version, and• the alarm panel.The right side of the banner:

• Allows you to pause anysoftware updates.

• Links to the online helpfor all software.

• Shows the user name ofthe currently logged-inuser.

• Provides a link to logout of the GUI.

Main Menu Left side of screen, underbanners

A tree-structured menu of alloperations that can beperformed through the userinterface. The plus character(+) indicates a menu itemcontains subfolders.• To display submenu

items, click the pluscharacter, the folder, oranywhere on the sameline.

• To select a menu itemthat does not havesubmenu items, click onthe menu item text or itsassociated symbol.



Table 2-1 (Cont.) User Interface Elements


Work Area Right side of panel understatus

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

Occupies the top of thework area. It displaysthe title of the currentpage being displayed,date and time, andincludes a link tocontext-sensitive help.

• Page Control Area:Located below the PageTitle Area, this areashows controls for thePage Area (this area isoptional). Whenavailable as an option,filter controls display inthis area. The PageControl Area containsthe optional layoutelement toolbar, whichdisplays differentelements depending onwhich GUI page isselected. For moreinformation, see Optional LayoutElement Toolbar.

• Page Area: Occupies thebottom of the work area.This area is used for alltypes of operations. Itdisplays all options,status, data, file, andquery screens.Information or errormessages are displayedin a message box at thetop of this section. Ahorizontal and/orvertical scroll bar isprovided when thedisplayed informationexceeds the page area ofthe screen. When a userfirst logs in, this areadisplays the application



Table 2-1 (Cont.) User Interface Elements


user interface page. Thepage displays a user-defined welcomemessage. To customizethe message, see Customizing the LoginMessage.

Session Banner Across the bottom of the webpage

The left side of the bannerprovides the followingsession information:• The name of the

machine to which theuser is connected, andwhether the user isconnected via the VIP ordirectly to the machine.

• The HA state of themachine to which theuser is connected.

• The role of the machineto which the user isconnected.

The right side of the bannershows the alarm panel.

Main Menu OptionsTable 2-2 describes all main menu user interface options.

Note: The menu options can differ according to the permissions assigned to auser's login account. For example, the Administration menu options do notdisplay on the screen of a user who does not have administrative privileges.

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

Note: Some features do not display in the main menu until the features areactivated.



Table 2-2 Main Menu Options

Menu Item Function

Administration The Administration menu allows the user to:• General Options. Configure options such

as password history and expiration,login message, welcome message, andthe number of failed login attemptsbefore 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• Authenticate LDAP servers• Configure SNMP trapping services• Configure an export server• Configure DNS elements

Configuration On the NOAM, allows the user to configure:• Network Elements• Network Devices• Network Routes• Services• Servers• Server Groups• Resource Domains• Places• Place Associations• Interface and Port DSCP

Alarms and Events Allows the user to view:• Active alarms and events• Alarm and event history• Trap log

Security Log Allows the user to view, export, and generatereports from security log history.

Status and Manage Allows the user to monitor the individualand collective status of Network Elements,Servers, HA functions, Databases, KPIs,system Processes, and Tasks. The user canperform actions required for servermaintenance, database management, data,and ISO file management.

Measurements Allows the user to view and exportmeasurement data.



Table 2-2 (Cont.) Main Menu Options

Menu Item Function

Transport Manager (optional) On the SOAM, allows the user to configureadjacent nodes, configuration sets, ortransports. A maintenance option allows theuser to perform enable, disable, and blockactions on the transport entries. This optiononly displays with the DSR application.

Communication Agent (optional) Allows the user to configure Remote Servers,Connection Groups, and Routed Services.The user can perform actions to enable,disable, and block connections. Also allowsthe user to monitor the status of Connections,Routed Services, and HA Services.

SS7/Sigtran (optional) On the SOAM, allows the user to configurevarious users, groups, remote signalingpoints, links, and other items associated withSS7/Sigtran; perform maintenance andtroubleshooting activities; and provides acommand line interface for bulk loading SS7configuration data. This option only displayswith the DSR application.

Diameter Common (optional) Allows the user to view or configure:• 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 AssignmentsThe DSR Bulk Import and Export functionsare available on both OAMs for the dataconfigured on that OAM.

Diameter (optional) Allows the user to configure, modify, andmonitor Diameter routing:• On the NOAMP, Diameter Topology

Hiding and Egress Throttle Listconfiguration

• On the SOAM, Diameter Configuration,Maintenance, Reports, Troubleshootingwith IDIH, AVP Dictionary, andDiameter Mediation configuration

UDR (User Data Repository) (optional) Allows the user to add, edit, store, andmanage subscriber and pool data. The usercan also monitor the import, export, andsubscribing client status. This option onlydisplays with the UDR application.




Menu Item Function

RBAR (Range-Based Address Resolution)(optional)

Allows the user to configure the followingRange-Based Address Resolution (RBAR)settings:• Applications• Exceptions• Destinations• Address Tables• Addresses• Address Resolutions• System OptionsThis is accessible from the SOAM only. Thisoption only displays with the DSRapplication.

FABR (Full Address Based Resolution)(optional)

Allows the user to configure the followingFull Address Based Resolution (FABR)settings:• Applications• Exceptions• Default Destinations• Address Resolutions• System OptionsThis is accessible from the SOAM only. Thisoption is only available with the DSRapplication.

Gateway Location Application (optional) On the SOAM, allows the user to performconfiguration tasks, edit options, and viewelements for:• Exceptions• Options

GLA can deploy with Policy DRA (in thesame DA-MP or a separate DA-MP). Thisoption only displays with the DSRapplication.

MAP-Diameter Interworking (optional) On the SOAM, allows the user to performconfiguration tasks, edit options, and viewelements for the DM-IWF DSR Application:• DM-IWF Options• Diameter Exception

On the NOAMP, allows the user to performconfiguration tasks, edit options, and viewelements for the MD-IWF SS7 Application:• MD-IWF Options• Diameter Realm• Diameter Identity GTA• GTA Range to PC• MAP Exception• CCNDC MappingThis option only displays with the DSRapplication.




Menu Item Function

RADIUS (Remote Authentication Dial-InUser Service) (optional)

Allows the user to perform configurationtasks, edit system options, and view elementsfor:• Network Options• Message Authenticator Configuration

Sets• Shared Secret Configuration Sets• Ingress Status Server Configuration Sets• Message Conversion Configuration Sets• NAS NodeThis option only displays with the DSRapplication.

SBR (Session Binding Repository) (optional) Allows the user to perform configurationtasks, edit system options, and view elementsfor:• SBR Databases• SBR Database Resizing Plans• SBR Data Migration Plans• Database Options

Additionally, on the NOAMP, users areallowed to perform maintenance tasks, editoptions, and view elements for:• Maintenance

– SBR Database Status– SBR Status– SBR Database Reconfiguration

StatusThis option only displays with the DSRapplication.

Mediation Allows the user to make routable decisions toend the reply, drop the message, or set thedestination realm.




Menu Item Function

Policy and Charging (optional) On the NOAMP, allows the user to performconfiguration tasks, edit options, and viewelements for:• 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 OptionsAdditionally on the NOAMP, users areallowed to perform maintenance tasks, editoptions, and view elements for:• Maintenance

– SBR Database Status– SBR Status– SBR Database Reconfiguration

Status– Policy Database Query

On the SOAM, allows the user to performconfiguration tasks, edit options, and viewelements 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– OCS Session State– Realms

• Error Codes• Alarm Settings• Congestion OptionsThis option only displays with the DSRapplication.




Menu Item Function

DCA Framework (optional) Allows the user to perform configurationtasks, edit system options, and view elementsfor DCA applications:• Custom MEALs (Measurements, Events,

Alarms, and Logs)• General Options• Trial MPs assignment• Application Control• System Options

IPFE (optional) 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 displays with the DSRapplication.

Help Launches the Help system for the userinterface

Legal Notices Product Disclaimers and Notices

Logout Allows the user to log out of the userinterface

Missing Main Menu optionsPermissions determine which Main Menu options are visible to users. Permissions aredefined through the Group Administration page. The default group, admin, ispermitted access to all GUI options and functionality. Additionally, members of theadmin group set permissions for other users.

Main Menu options vary according to the group permissions assigned to a user'saccount. Depending on your user permissions, some menu options may be missingfrom the Main Menu. For example, Administration menu options do not display onyour screen if you do not have administrative permissions. For more informationabout user permissions, see Group Administration in the OAM section of the onlinehelp, or contact your system administrator.

Common Graphical User Interface WidgetsCommon controls allow you to easily navigate through the system. The location of thecontrols remains static for all pages that use the controls. For example, after youbecome familiar with the location of the display filter, you no longer need to search forthe control on subsequent pages because the location is static.

Supported BrowsersThis 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 bothJavaScript and cookies. Please refer to the Oracle Software Web Browser SupportPolicy for details

Missing Main Menu options


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

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

System Login PageAccess to the user interface begins at the System Login page. The System Login pageallows users to log in with a username and password and provides the option ofchanging the password upon login. The System Login page also features a date andtime stamp reflecting the time the page was last refreshed. Additionally, acustomizable login message displays just below the Log In button.

The user interface is accessed via HTTPS, a secure form of the HTTP protocol. Whenaccessing a server for the first time, HTTPS examines a web certificate to verify theidentity of the server. The configuration of the user interface uses a self-signed webcertificate to verify the identity of the server. When the server is first accessed, thesupported browser warns the user that the server is using a self-signed certificate. Thebrowser requests confirmation that the server can be trusted. The user is required toconfirm the browser request to gain access.

Customizing the Login Message

Before logging in, the System Login page displays. You can create a login message thatdisplays just below the Log In button on the System Login page.

Figure 2-1 Oracle System Login

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

2. Locate LoginMessage in the Variable column.

3. Enter the login message text in the Value column.

Common Graphical User Interface Widgets


4. Click OK or Apply to submit the information.

A status message displays at the top of the Configuration Administration page toinform you if the operation was successful.

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

Accessing the DSR Graphical User Interface

In DSR, some configuration is done at the NOAM server, while some is done at theSOAM server. Because of this, you need to access the DSR graphical user interface(GUI) from two servers. Certificate Management (Single Sign-On) can be configured tosimplify accessing the DSR GUI on the NOAM and the SOAM.

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

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

1. In the browser URL field, enter the fully qualified hostname of the NOAM server,for example https://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 displays.

3. Enter the Username and Password for your account.

The DSR GUI for the NOAM displays.

4. To access the DSR GUI for the SOAM, open another browser window and enter thefully qualified hostname of the SOAM.

The DSR GUI for the SOAM displays.

You can toggle between the DSR GUI on the NOAM and the DSR GUI on the SOAMas you perform configuration tasks.

Main Menu IconsThis table describes the icons used in the Main Menu.

Table 2-3 Main Menu Icons

Icon Name Description

Folder Contains a group ofoperations. If the folder isexpanded by clicking theplus (+) sign, all availableoperations and sub-foldersare displayed. Clicking theminus (-) collapses the folder.



Table 2-3 (Cont.) Main Menu Icons

Icon Name Description

Config File Contains operations in anOptions page.

File with Magnifying Glass Contains operations in aStatus View page.

File Contains operations in a DataView page.

Multiple Files Contains operations in a FileView page.

File with Question Mark Contains operations in aQuery page.

User Contains operations relatedto users.

Group Contains operations relatedto groups.

Task Contains operations relatedto Tasks

Help Launches the Online Help.

Logout Logs the user out of the userinterface.

Work Area DisplaysIn the user interface, tables, forms, tabbed pages, and reports are the most commonformats.

Note: Screen shots are provided for reference only and may not exactly matcha specific application's GUI.

Tables

Paginated tables describe the total number of records being displayed at the beginningand end of the table. They provide optional pagination with First|Prev|Next|Lastlinks at both the beginning and end of this table type. Paginated tables also contain



action links on the beginning and end of each row. For more information on actionlinks and other page controls, see Page Controls.

Figure 2-2 Paginated Table

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

Figure 2-3 Scrollable Table

Note: Multiple rows can be selected in a scrollable table. Add rows one at atime 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 forconfiguration. Forms contain fields and may also contain a combination of lists,buttons, and links.



Figure 2-4 Form Page

Tabbed pages

Tabbed pages provide collections of data in selectable tabs. Click on a tab to see therelevant data on that tab. Tabbed pages also group Retrieve, Add, Update, and Deleteoptions on one page. Click on the relevant tab for the task you want to perform andthe appropriate fields populate on the page. Retrieve is always the default for tabbedpages.

Figure 2-5 Tabbed Pages

Figure 2-6 Tabbed Pages

Reports

Reports provide a formatted display of information. Reports are generated from datatables by clicking Report. Reports can be viewed directly on the user interface, or theycan be printed. Reports can also be saved to a text file.



Figure 2-7 Report Output

Customizing the Splash Page Welcome Message

When you first log into the user interface, the splash page displays. Located in thecenter of the main work area is a customizable welcome message. Use this procedureto create a message suitable for your needs.


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 tothe previously saved value.

A status message displays at the top of the page to inform you if the operation wassuccessful.

The next time you log into the user interface, the new welcome message text displays.

Column Headers (Sorting)You can sort a table by a column by clicking the column header. However, sorting isnot necessarily available on every column. Sorting does not affect filtering.

When you click the header of a column in a table that can be sorted, an indicatordisplays in the column header showing the direction of the sort. See Figure 2-8.Clicking the column header again reverses the direction of the sort.

Figure 2-8 Sorting a Table by Column Header

Page ControlsUser interface pages contain controls, such as buttons and links, that perform specifiedfunctions. The functions are described by the text of the links and buttons.



Note: Disabled buttons are grayed out. Buttons that are irrelevant to theselection or current system state, or which represent unauthorized actions asdefined in Group Administration, are disabled. For example, Delete isdisabled for users without Global Data Delete permission. Buttons are alsodisabled if, for example, multiple servers are selected for an action that canonly be performed on a single server at a time.

Table 2-4 contains examples of Action buttons.

Table 2-4 Example Action Buttons

Action Button Function

Insert Inserts data into a table.

Edit Edits data within a table.

Delete Deletes data from table.

Change Changes the status of a managed object.

Some Action buttons take you to another page.

Submit buttons, described in Table 2-5, are used to submit information to the server.The buttons are located in the page area and accompanied by a table in which you canenter information. The Submit buttons, except for Cancel, are disabled until you entersome data or select a value for all mandatory fields.

Table 2-5 Submit Buttons

Submit Button Function

OK Submits the information to the server, and ifsuccessful, returns to the View page for thattable.

Apply Submits the information to the server, and ifsuccessful, remains on the current page sothat you can enter additional data.

Cancel Returns to the View page for the tablewithout submitting any information to theserver.

Clear Field ControlThe clear field control allows you to clear the value from a list. The clear field control isavailable only on some lists.

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

Figure 2-9 Clear Field Control X

Optional Layout Element ToolbarThe optional layout element toolbar displays in the Page Control Area of the GUI.



Figure 2-10 Optional Layout Element Toolbar

The toolbar displays different elements depending on which GUI page is selected. Theelements of the toolbar that can display 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.

Notifications

Some messages require immediate attention, such as errors and status items. Whennew errors occur, the Errors element opens automatically with information about theerror. Similarly, when new status items are added, the Status element opens. If youclose an automatically opened element, the element stays closed until a new,unacknowledged item is added.

Figure 2-11 Automatic Error Notification

Note: Viewing and closing an error does not clear the Errors element. If youreopen 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 changesto indicate new messages are available. The styling of the Task element changes whena task changes state (such as, a task begins or ends).

Opening an Element in the Toolbar

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



FiltersFilters are part of the optional layout element toolbar and appear throughout the GUIin the Page Control Area. For more information about optional layout element toolbarfunctionality, see Optional Layout Element Toolbar.

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

• Network Element – When enabled, the Network Element filter limits the dataviewed to a single Network Element.

Note: Once enabled, the Network Element filter affect all pages that list ordisplay data relating to the Network Element.

• Collection Interval – When enabled, the collection interval filter limits the data toentries collected in a specified time range.

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

Once a field is selected, it cannot be selected again. All specified criteria must be met inorder for a row to be displayed.

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

Figure 2-12 Examples of Filter Styles

Filter Control Elements

This table describes filter control elements of the user interface.

Table 2-6 Filter Control Elements

Operator Description

= Displays an exact match.

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

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



Table 2-6 (Cont.) Filter Control Elements

Operator Description

>= Displays all records with a parameter valuethat is greater than or equal to the specifiedvalue.

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

<= Displays all records with a parameter valuethat is less than or equal to the specifiedvalue.

Like Enables you to use an asterisk (*) as awildcard as part of the filter parameter value.

Is Null Displays all records that have a value of IsNull in the specified field.

Note: Not all filterable fields support all operators. Only the supportedoperators are available for you to select.

Filtering on the Network Element

The global Network Element filter is a special filter that is enabled on a per-user basis.The global Network Element filter allows a user to limit the data viewed to a singleNetwork Element. Once enabled, the global Network Element filter affects all sub-screens that display data related to Network Elements. This filtering option may notbe available on all pages.

1. Click Filter in the optional layout element toolbar.

2. Select a Network Element from the Network Element list.

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

4. For data tables that support compound filtering, click Add to add another filtercondition and repeat steps 2 through 4.

Multiple filter conditions are joined by an AND operator.

Records are displayed according to the specified criteria.

Filtering on Collection Interval

The Collection Interval filter allows a user to limit the data viewed to a specified timeinterval. This filtering option may not be available on all pages.


2. Enter a duration for the Collection Interval filter.

The duration must be a numeric value.



3. Select a unit of time from the list.

The unit of time can be seconds, minutes, hours, or days.

4. Select Beginning or Ending from the list.

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


Filtering Using the Display Filter

Use this procedure to perform a filtering operation. This procedure assumes you havea data table displayed on your screen with the Display Filter field. This process is thesame for all data tables. However, all filtering operations are not available for alltables.

Note: Display Filter does not support compound filtering. For example, youcannot filter on both severity and a server name. Try to filter on a single filtercriteria, such as the server hostname for server-scoped metric cells; or theapplication name for St- and NE-scoped metric cells. You can also sort bycongestion level (descending) to help improve your filter.


2. Select a field name from the Display Filter list.

This selection specifies the field in the table that you want to filter on. The default isNone, which indicates that you want all available data displayed.

3. Select an operator from the operation selector list.

4. Enter a value in the value field.

This value specifies the data that you want to filter on. For example, if you specifyFilter=Severity with the equals (=) operator and a value of MINOR, the table wouldshow only records where Severity=MINOR.

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


Note: PCA was known as PDRA and may still be seen in some filtering.

Pause UpdatesSome pages refresh automatically. Updates to these pages can be paused by selectingthe Pause updates checkbox. Uncheck the Pause updates checkbox to resumeautomatic updates. The Pause updates checkbox 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 inthe page area. If a page uses pagination, the value of Max Records Per Page is used.Use this procedure to change the Max Records Per Page.




2. Change the value of the MaxRecordsPerPage variable.

Note: Maximum Records Per Page has a range of values from 10 to 100records. The default value is 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.




2-24 Gateway Location Application (GLA)

3The Gateway Location Application

The Gateway Location Application (GLA) is a feature of the Diameter SignalingRouter (DSR). GLA runs as a DSR Application to provide a Diameter interface tosubscriber data stored in the DSR's Policy Session Binding Repository (SBR).

The Gateway Location Application (GLA)The Gateway Location Application (GLA) is a DSR Application that provides aDiameter interface to subscriber data stored in the DSR's Policy Session BindingRepository (SBR). Subscriber data concerning binding and session information ispopulated in the SBR-B (Policy SBR - Binding) by the Policy Diameter Routing Agent(Policy DRA). GLA provides methods for a Diameter node to query bindinginformation stored in the SBR-B. The query can be by either IMSI or MSISDN.

GLA processes Diameter Requests and generates Diameter Answers. It does not routeDiameter Requests to other Diameter nodes. A Diameter Peer Node can be a GatewayQuery Client (GQC). GLA allows DSR to be a Gateway Query Server (GQS).

GLA provides the following capabilities:

• Ability to configure GLA exceptions

• Ability to configure GLA system options

• Ability to configure GLA alarm thresholds

Gateway Location Application (GLA) DescriptionGateway Location Application (GLA) is a DSR Application that retrieves subscriberdata stored in Policy Session Binding Repository (SBR) provided by Policy DRA. TheGLA is deployed and must be in the same Resource Domain as DA-MPs activatedwith Policy DRA. No additional Resource Domain configuration is needed specificallyfor GLA in the DSR GUI.

After a DA-MP is activated with the GLA, it receives a Request (Get Gateway Request(GGR)) generated by the Gateway Query Client (GQC), decodes subscriberinformation (IMSI or MSISDN), and queries the SBR (via ComAgent within theGateway Query Server (GQS) or DSR). The GLA generates an Answer (Get GatewayAnswer (GGA)) with subscriber information that includes the number of bindings forthe subscriber, and the following information is included for each session:

• Access point name

• PCEF FQDN

• Creation timestamp

The GLA is dependent on Policy DRA to populate data in SBR and thus GLA usesActivation/Deactivation rules in the following conditions:

The Gateway Location Application 3-1

• The GLA is activated using the same mechanism as Policy DRA. It is activated atthe NOAM, and activation is performed so that it activates all SOAMs under acommon NOAM.

• GLA cannot be activated unless Policy DRA is activated and PCRF-Pooling hasbeen enabled.

• Policy DRA cannot be deactivated if GLA is activated.

To simplify deployment of GLA, it is piggybacked on Policy DRA's configuration ofDA-MPs within its Resource Domain and configuration of ComAgent connectionsbetween DA-MPs and SBRs.

If PCRF pooling is enabled with GLA activated, Policy DRA stores all informationrequired by GLA.

GLA GUI ConventionsThe GLA GUI uses the following conventions (this is not an all-inclusive list):

• The breadcrumb displays at the top of the GUI page reflects your position in themenu tree.

• Context sensitive online help is available via the help icon in the upper right sideof the GUI page.

• Action buttons are available at the bottom of the GUI page.

• Edit and delete actions are validated.

• Successful edit and delete actions generate a confirmation message.

• The items that are displayed on the GUI page differ from SOAM and NOAMviews.

• The workspace grid is displayed in ascending order by the first field in the grid.

• All columns in the managed object View screen can be sorted by column headers.

• The column headers on all of the GLA view screens are sorted in ascending orderby default.

• You can select only one row at a time in the work area grid of the managed objectView screen, unless otherwise specified.

• Edit and Delete are not active until you select a row.

• Apply applies any updates and remains on the same GUI page. OK applies andupdates and returns to the pervious GUI page.

• OK, Apply, and Cancel are enabled by default on all Insert and Edit screenswhere they appear.

GLA FunctionsThe GLA application performs the following major functions:

• Provides a Diameter interface to subscriber data stored in the DSR's Policy SessionBinding Repository (SBR)

Gateway Location Application (GLA) Description


• Provides methods for a Diameter node to query binding information stored in theSBR-B

• Processes Diameter Requests and generates Diameter Answers

ComAgent Connectivity for GLAGLA works with DA-MPs that require ComAgent connectivity to every SBR-B serverin a Policy Binding Resource Domain.

GLA does not configure its own ComAgent connections, but relies on the ComAgentconnectivity setup already provided by Policy DRA. When a DA-MP initializes withGLA active, the DA-MP automatically creates ComAgent connections to each SBR-B.

Ingress Message Rate AlarmingGLA generates alarms based on the ingress message rate. The message processingrates required to generate an alarm are set by the user while configuring GLA, andshould be significantly lower than a standard DA-MP’s ingress message rate underany DA-MP profile.

The Ingress Message Rate Alarm is a notification that higher than expected rates oftraffic are being processed by the DSR Application.

Alarm trigger points differ based on whether the GLA is deployed as the sole DSRApplication on a DA-MP or combined with Policy DRA on the same DA-MP. Tosatisfy the deployment variables, the Ingress Message Rate has the following settings:

Table 3-1 Ingress Message Rate Settings

Field DefaultConfigurable Range Rules

Maximum DA-MP MaxIngress MessageRate

N/A Not configurable. This value isprovided by the DA-MP Profile

CL 1 Abatement/Onset(% of Maximum)

50/60 1-99 CL1 Onset > CL1 Abatement


70/80 1-99 CL2 Abatement > CL1 Onset

CL2 Onset > CL2 Abatement


90/95 1-99 CL3 Abatement > CL2 Onset

CL3 Onset > CL3 Abatement

GLA Operational Status

The operational status determines when DRL delivers a request to GLA (for example,when GLA is the Available status) and when DRL uses the Unavailability Action forrequests (for example, when GLA is in the Unavailable status).

GLA’s Operational Status is dependent on the following items:

• Admin State

• GLA Congestion Level

• SBR-B SubResource Availability


The Gateway Location Application 3-3

• Previous Operational Status

When the GLA initializes with the Admin State set to Disabled, the Operational Statusis set to Unavailable. When the Admin State changes from Enabled to Disabled, theOperational Status is transitioned to Unavailable.

When the GLA initializes with the Admin State set to Enabled, or if the Admin State ischanged from Disabled to Enabled, the system begins to monitor resources todetermine if it can change its Operational Status.

Once GLA moves into the Available state, the system attempts to answer as manyqueries as possible and remains available as long as any of the SBR-B SubResourcesare also available.



4Gateway Location Application

Configuration

The GLA > Configuration GUI pages for GLA components provide fields for enteringthe information needed to manage Gateway Location Application configuration in theDSR.

GLA Configuration OverviewThe GLA > Configuration GUI pages for Gateway Location Application componentsprovide fields for entering the information needed to manage GLA configuration inthe DSR.

Before configuring information in GLA the following characteristics need to be met:

• Since GLA retrieves subscriber information stored in SBR-B by Policy DRA, PolicyDRA must be active for data to be retrieved.

• GLA is activated at the NOAM, and also activates all SOAMs under a commonNOAM.

• GLA cannot be active unless Policy DRA is active and PCRF-Pooling is enabled.

The GLA > Configuration GUI pages allow you to configure:

• Exceptions - direct the actions that are taken when specific requests cannot beprocessed correctly by the system

• System Options - determines actions taken when GLA is unavailable, as well ashow the Realm and Fully Qualified Domain Name are applied to the answermessage

• Alarm Settings - set alarm thresholds

GLA ExceptionsGLA allows the configuration of exceptions to manage object attributes for errorhandling. This enables the configuration of error answers, which provide informationon the result code, vendor ID, and the appropriate error message for each condition.

The following exception types are supported:

• Decode Error

• Unknown Application ID

• Unknown Command Code

• IMSI and MSISDN Present

Gateway Location Application Configuration 4-1

• IMSI and MSISDN Absent

• SBR-B Query Failure

• SBR-B Query Timeout

• Resource Exhausted

• Unable to Process

Configure GLA Exceptions elementsThis table describes the elements for configuring GLA error exceptions:

Table 4-1 Configure GLA Exception Elements

Element Description Data Input Notes

Action The action to be taken whenencountering the specific error.

Format: Options

Range:

• Discard - Request is discarded and noanswer is sent

• Answer with Result Code - aDiameter Answer message with theResult-Code AVP is sent to Request'sOrigin-Host.

• Answer with Experimental ResultCode - Diameter Answer messagewith an Experimental-Result AVP issent to Request's Origin-Host Answerwith Experimental Result Code

Result Code The value displayed in themessage if the Action is Answerwith Result Code or Answerwith Experimental Result Code.

Select a Result Code from thelisting provided or enter aspecific code.

Format: List

Range: 1000-5999

Vendor ID The vendor ID displayed in theExperimental-Result pair if theAction is Answer withExperimental Result Code.

Format: Text box

Range: 1 - 4294967295

Error String The text string appended to theError-Message AVP.

Format: Text box

Range: 0 to 64 characters

Configuring GLA Exceptions

Use this task to configure exceptions for GLA. Exceptions direct the actions that aretaken when specific requests cannot be processed correctly by the system.

The steps below apply to any exception code listed on the GLA Exceptions page. Allindividual exception codes can be updated independently using these steps.

GLA Exceptions


1. Click GLA > Configuration > Exceptions.

The fields are described in Configure GLA Exceptions elements.

2. Select an Action from the available options. Valid options are:

• Discard - the request is discarded and no answer is sent.

• Answer with Result Code - an answer message with the Result Code AVP issent to the request originator.

• Answer with Experimental Result Code - an answer message with anExperimental Result Code AVP is sent to the request originator.

3. Enter a Result Code or select one from the listing. If Discard is selected for theAction, this field is grayed out. If the Action is other than Discard, the result code issent with the exception answer.

4. Enter a Vendor ID. This field is activated only if you selected Answer withExperimental Result Code for the Action. This value is sent with the experimental/result pairing.

5. Enter an Error String to be appended to the error/message pairing sent with theanswer message.

6. Click Apply or Cancel.

If Apply is clicked and any of the following conditions exist, an error messageappears:

• Any fields contain a value that contains invalid characters or is out of theallowed range.

• Any required field is empty (not entered).

• A Result Code value is not set when Answer With Result Code or AnswerWith Experimental Result Code is selected.

• An Vendor ID value is not set when Answer With Experimental Result Codeis selected.

GLA System OptionsGLA allows the configuration of system options. Setting options allows you todetermine actions taken when GLA is unavailable, as well as how the Realm and FullyQualified Domain Name are applied to the answer message.

The system options set include:

• Realm

• Fully Qualified Domain Name

• Application Unavailable Action

• Application Unavailable Route List

• Application Unavailable Result-Code

• Application Unavailable Error Message

GLA System Options


• Application Unavailable Vendor-ID

Configure GLA System Options elementsThis table describes the elements for configuring GLA system options:

Table 4-2 Configure GLA System Options Elements


Realm A list of alphanumeric labels (a label is1-63 characters, and may contain letters,digits, dashes and underscore) separatedby dots (.). A label must start with a letter,digit or underscore and must end with aletter or digit.

This value is placed in the Origin-RealmAVP of the Answer message generated byGLA.

A Fully Qualified Domain Name isrequired to configure the Realm.

Format: Alphanumeric (A-Z,a-z, 0-9), dash (-) andunderscore (_) characters. Notcase-sensitive.

Range: Maximum of 255characters.

Fully QualifiedDomain Name

A list of alphanumeric labels (a label is1-63 characters, and may contain letters,digits, dashes and underscore) separatedby dots (.). A label must start with a letter,digit or underscore and must end with aletter or digit.

This value is placed in the Origin-RealmAVP of the Answer message generated byGLA.

A Realm is required to configure FullyQualified Domain Name.

Format: Alphanumeric (A-Z,a-z, 0-9), dash (-) andunderscore (_) characters.Maximum of 255 characters.Not case-sensitive.

Range: Maximum of 255characters.

ApplicationUnavailableAction

Action to be taken when GLA applicationis unavailable to process messages.

Format: Option

Range: Valid responses

• Continue Routing• Default Route• Send Answer with

Result-Code pair• Send Answer with

Experimental-Result AVP• Discard

ApplicationUnavailableRoute List

Route List used to route requests whenUnavailability Action is Default Routeand GLA application is not available.Using a route list bypasses the PeerRouting Rules.

Format: List

Range: Available Route Lists

GLA System Options


Table 4-2 (Cont.) Configure GLA System Options Elements


ApplicationUnavailableResult-Code

The Result-Code or Experimental-Result-Code value returned in an Answermessage when a message is notsuccessfully routed because the GLAapplication is unavailable.

If Vendor-ID is configured, this valuewould be included with theExperimental-Result Code AVP in theAnswer message.

Format: Option/List

Default: 3002

Range: 1000 - 5999

ApplicationUnavailableError Message

The Error-Message AVP value returned inan Answer message when a message isnot successfully routed because the GLAapplication is not unavailable.

Format: Text box

Default: GLA Unavailable

Range: 0 to 64 characters

ApplicationUnavailableVendor-ID

The Vendor-ID AVP value returned in anAnswer message when a message is notsuccessfully routed because the GLAapplication is unavailable.

If Vendor-ID is configured, this valuewould be included with theExperimental-Result Code AVP in theAnswer message.

Format: Text box

Default: N/A

Range: 1 to 4294967295

Configuring GLA System Options

Use this task to configure system options for GLA.

1. Click GLA > Configuration > System Options.

The fields are described in Configure GLA System Options elements.

2. Enter a Realm (optional). A Fully Qualified Domain Name is required for this valueto be configured, and this value becomes part of the origin/realm pairing in theAnswer message. If a realm is not configured, DSR uses the local node informationfor Answers.

3. Enter a Fully Qualified Domain Name (optional). A Realm is required for this valueto be configured. If a FQDN is not configured, DSR uses the local node informationfor Answers.

4. Select an Application Unavailable Action from the available choices. Thisdetermines the action to be taken by the system is the application is unavailable.Valid options are:

• Continue Routing

• Default Route

• Send Answer with Result-Code AVP

• Send Answer with Experimental-Result AVP

GLA System Options


• Discard

5. Select the Application Unavailable Route List. This option is only available ifDefault Route is selected as the Unavailable Action, enabling the selected route listto be used when the application is unavailable.

6. Select the Application Unavailable Result-Code. This option is only available ifSend Answer with Result-Code AVP or Send Answer with Experimental-ResultAVP are selected as the Unavailable Action. This option determines the messagereturned in an Answer message when the application is unavailable.

7. Select the Application Unavailable Error Message. This option is only available ifSend Answer with Result-Code AVP or Send Answer with Experimental-ResultAVP are selected as the Unavailable Action. This option determines the error/message pair returned in an Answer message when the application is unavailable.

8. Select the Application Unavailable Vendor ID. This option is only available if SendAnswer with Experimental-Result AVP is selected as the Unavailable Action. Thisoption determines the vendor/ID pair returned in an Answer message when theapplication is unavailable.




• Any required field is empty (not entered).

• An Application Unavailable Route List value is not set when Default Route isselected.

• An Application Unavailable Result-Code value is not set when Send Answerwith Result-Code AVP or Send Answer with Experimental-Result AVP isselected.

• An Application Unavailable Vendor ID value is not set when Send Answerwith Experimental-Result AVP is selected.

GLA Alarm SettingsGLA allows the configuration of alarm thresholds. These thresholds are used togenerate notifications concerning the ingress message rates for the application.

Alarm thresholds may be set for the following limits:

• Critical Alarm Clear

• Critical Alarm Threshold

• Major Alarm Clear

• Major Alarm Threshold

• Minor Alarm Clear

• Minor Alarm Threshold

GLA Alarm Settings


Configure GLA Alarm Settings elementsThis table describes the elements for configuring a GLA Alarm Setting:

Table 4-3 Configure GLA Alarm Settings Elements

Element DescriptionData InputNotes

Critical AlarmThreshold(Percent)

GLA ingress message rate threshold for this alarm to beraised as a severity Critical. The threshold is expressed asa percentage of the Ingress Message Capacity.

Default: 95

Range: 1 to 99

Critical AlarmClear (Percent)

GLA ingress message rate clear for this alarm to beraised as a severity Critical. The threshold is expressed asa percentage of the Ingress Message Capacity.

Default: 90

Range: 1 to 99

Major AlarmThreshold(Percent)

GLA ingress message rate threshold for this alarm to beraised as a severity Major. The threshold is expressed asa percentage of the Ingress Message Capacity.

Default: 80

Range: 1 to 99

Major AlarmClear (Percent)

GLA ingress message rate clear for this alarm to beraised as a severity Major. The threshold is expressed asa percentage of the Ingress Message Capacity.

Default: 70

Range: 1 to 99

Minor AlarmThreshold(Percent)

GLA ingress message rate threshold for this alarm to beraised as a severity Minor. The threshold is expressed asa percentage of the Ingress Message Capacity.

Default: 60

Range: 1 to 99

Minor AlarmClear (Percent)

GLA ingress message rate clear for this alarm to beraised as a severity Minor. The threshold is expressed asa percentage of the Ingress Message Capacity.

Default: 50

Range: 1 to 99

Configuring GLA Alarm Settings

Use this task to configure alarm settings for GLA.

1. Click GLA > Configuration > Alarm Settings.

The fields are described in Configure GLA Alarm Settings elements.

2. Select a value for the Critical Alarm Threshold percent. This determines the ingressmessage rate threshold for this alarm to be raised as Critical. The default is 95percent.

3. Select a value for the Critical Alarm Clear percent. This determines the ingressmessage rate clear for this alarm to be raised as Critical. The default is 90 percent.

4. Select a value for the Major Alarm Threshold percent. This determines the ingressmessage rate threshold for this alarm to be raised as Major. The default is 80percent.

5. Select a value for the Major Alarm Clear percent. This determines the ingressmessage rate clear for this alarm to be raised as Major. The default is 70 percent.

6. Select a value for the Minor Alarm Threshold percent. This determines the ingressmessage rate threshold for this alarm to be raised as Minor. The default is 60percent.

GLA Alarm Settings


7. Select a value for the Minor Alarm Clear percent. This determines the ingressmessage rate clear for this alarm to be raised as Minor. The default is 50 percent.




• A Critical Alarm Clear value is greater than the Critical Alarm Threshold.

• A Major Alarm Clear value is greater than the Major Alarm Threshold.

• A Minor Alarm Clear value is greater than the Minor Alarm Threshold.

• A Major Alarm Threshold value is greater than the Critical Alarm Clear orCritical Alarm Threshold.

• A Minor Alarm Threshold value is greater than the Major Alarm Clear orMajor Alarm Threshold.

Post Configuration ActivitiesAfter GLA configuration is complete, the following activities need to be performed tomake the GLA application fully operational in the system:

• Enable GLA on the DA-MPs that process traffic

• Verify GLA comes into service in the Normal state

• Verify the Application Routing Table that has GLA rules is used for traffic arrivingfrom Gateway Query Clients

• Enable any connections that carry GL traffic and verify they are in-service

Enable the GLA

Use this task to enable GLA. For each Active SOAM,

1. Click Diameter > Maintenance > Applications.

2. Under DSR Application Name, select each GLA row.

To select more than one row, press and hold Ctrl while you click each row.

3. Click Enable.

4. Verify the application status on the page.

The Admin State, Operational Status, Operational Reason, and Congestion Levelin each of the selected rows should change respectively to Enabled, Available,Normal, Normal.

ComAgent and SBR Status Verification

Use the following task to verify ComAgent and SBR status after configuration iscomplete.

Post Configuration Activities


1. Verify Communication Agent (ComAgent) HA Services Status.

a. At the Active NOAM, click Communication Agent > Maintenance >Connection Status.

b. Verify Resource Routing Status is Available for all listed User/Provider entries.

2. Verify the ComAgent Automatic Connection Status.

a. At the Active NOAM, click Communication Agent > Maintenance > HaServices Status.

b. Verify Automatic Connection Count is X of Y In Service, where Y >= X and X =Y indicate successful Automatic Connection setup.

3. Verify Policy SBR Status.

a. At the Active NOAM, click Policy DRA > Maintenance > Policy SBR Status.

b. Verify the Resource HA Role server is Active/Standby/Spare and CongestionLevel is Normal for all servers in each Server Group in the Binding Region andMated Site tab entries.

Verify Application Route Table

Use the following task to verify the Application Routing Table that includes GLA rulesis used for traffic arriving from Gateway Query Clients.

1. At the Active SOAM, click Diameter > Configuration > Application Route Tables.

2. Verify there is an Application Route Table and Rules set up for GLA. If no table andrules exist, refer to the DSR Administration Guide.

3. Select GLA from the Application Route Table and click View/Edit Rules.

4. Select the available rules from the table and click Edit.

5. Examine the Application Routing Rules that direct traffic to GLA and verify thatthe Application-ID is configured as GL (16777321) and the Command-Code isconfigured as GGR (8388655) for all Application Routing Rules referring to GLA.

Once all information is verified, click OK or Cancel.

Enable GLA Query Client Connections

Use the following task to enable one or more GLA Query Client connections to PeerNodes.

1. At the Active SOAM, click Diameter > Maintenance > Connections.

2. Select 1 - 20 connections to enable.

To select multiple connections, press and hold the Ctrl key while you select eachconnection.

To select multiple contiguous connections, click the first connection you want, pressand hold the Shift key, and select the last connection you want. All the connectionsbetween are also selected.



3. Click Enable.

A confirmation box appears.

4. Click OK.

The selected connections are enabled.

If any of the selected connections no longer exist (they have been deleted byanother user), an error message is displayed, but any selected connections that doexist are enabled.

5. Verify Connection status on the page.

Verify that the Admin State of all connections changes to Enabled and theOperational Reason shows Connecting for connections to PCRF nodes andListening for connections to other nodes (such as policy clients – PCEF, AF, andothers).

For connections of type Responder Only (Policy Client nodes), the OperationalStatus and Operational Reason are Unk if IPFE TSA connections are used.

Bulk Import and ExportThe Diameter Common User's Guide describes the use and operation of Bulk Import andExport functions:

• Help > Diameter Common > Bulk Import

• Help > Diameter Common > Bulk Export

The Bulk Import and Export functions can be used to export Diameter, IPFE, andApplication configuration data in CSV files to a location outside the system, and toimport the files (usually edited) into the system where the Import function is executed.

Bulk Import

The Bulk Import operations use configuration data in ASCII Comma-Separated Values(CSV) files (.csv), to insert new data into, update existing data in, or delete existingdata from the configuration data in the system.

Note: Some configuration data can be imported only with the Updateoperation, and other data can be imported with Insert and Delete operationsbut not Update. Refer to the Diameter Common User's Guide or the DiameterCommon > Import Help for valid Import operations.

Import CSV files can be created by using a Bulk Export operation, or can be manuallycreated using a text editor.

Note: The format of each Import CSV file record must be compatible with theconfiguration data in the release used to import the file. Across differentrelease versions, column counts may not be compatible, and the import fails.

Files that are created using the Bulk Export operation can be exported either to thelocal Status & Manage File Management Directory (Status & Manage > Files page), orto the local Export Server Directory.



CSV files that are in the local File Management area can be used for Bulk Importoperations on the local system.

Files can be created manually using a text editor; the files must be uploaded to the FileManagement area of the local system before they can be used for Import operations onthe local system.

Multiple Import operations can be performed:

• Insert new configuration data records that do not currently exist in the system

• Update existing configuration data in the system

• Delete existing configuration data from the system

Each Import operation creates a log file. If errors occur, a Failures CSV file is createdthat appears in the File Management area. Failures files can be downloaded, edited tocorrect the errors, and imported to successfully process the records that failed. Failuresfiles that are unchanged for more than 14 days and log files that are older than 14 daysare automatically deleted from the File Management area.

Bulk Export

The Bulk Export operation creates ASCII Comma-Separated Values (CSV) files (.csv)containing Diameter, IPFE, and Application configuration data. Exportedconfiguration data can be edited and used with the Bulk Import operations to changethe configuration data in the local system without the use of GUI pages. The exportedfiles can be transferred to and used to configure another system.

Each exported CSV file contains one or more records for the configuration data thatwas selected for the Export operation. The selected configuration data can be exportedonce immediately, or exports can be scheduled to periodically occur automatically atconfigured times.

Configuration data can be exported in one Export operation:

• All exportable configuration data in the system

• All exportable configuration data from the selected Application, IPFE, or Diameter(each component's data is in a separate file)

• Exportable configuration data from a selected configuration component for theselected Application, IPFE, or Diameter

Exported files can be written to the File Management Directory in the local FileManagement area (Status & Manage > Files page), or to the Export Server Directoryfor transfer to a configured remote Export server.

CSV files that are in the local File Management area can be used for Bulk Importoperations on the local system.

If the export has any failures or is unsuccessful, the results of the export operation arelogged to a log file with the same name as the exported file but with a .log extension.Successful export operations are not logged.




4-12 Gateway Location Application (GLA)

gateway location application (gla) release 8 · select 2 for new service request 2. select 3 for...

Documents