Alcatel 1000 E10

CDRA Tutorial

215 49426 EAAH TCQEA Ed. 03

Status Change Note

Released

Short Title UG 14 All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

2 / 50

215 49426 EAAH TCQEA Ed. 03

Contents

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Overview of the CDRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 1.2 1.3 1.4 Functionality of the CDRA . . . . . . . . . . . . . . . . . . . . . . Operational Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . Calling of a Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Structure of a form . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 "Scheduled Job" Button . . . . . . . . . . . . . . . 2.2.3 Parameter Area . . . . . . . . . . . . . . . . . . . . . Activating a Function . . . . . . . . . . . . . . . . . . . . . . . . . . Registration of a Scheduled Job . . . . . . . . . . . . . . . . . Call Detail Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linear Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication with the CDR Collector . . . . . . . . . . File and Data Management . . . . . . . . . . . . . . . . . . . . Alarm Administration . . . . . . . . . . . . . . . . . . . . . . . . . User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.1 Statistics Counters . . . . . . . . . . . . . . . . . . . 4.6.2 Measurement Interval . . . . . . . . . . . . . . . . 4.6.3 Counter Reliability . . . . . . . . . . . . . . . . . . . 4.6.4 Storage of Measurements Results . . . . . . 4.6.5 Record Store Occupancy Alarms . . . . . . . 4.6.6 Corrupted Raw Records Alarm . . . . . . . . Attachment of Access Rights to Forms 7 9 10 10 11 12 12 12 15 16 16 16 17 18 18 19 21 21 21 24 25 25 28 30 32 33 33 33 33 34 34 34 36 37 39

Common Concepts for the Graphical User Interface . . 2.1 2.2

2.3 2.4 3 3.1 3.2 3.3 4 4.1 4.2 4.3 4.4 4.5 4.6

CDRs: Collection and Administration . . . . . . . . . . . . . . . . .

CDRA Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A

215 49426 EAAH TCQEA Ed. 03

3 / 50

Contents

Index

..........................................

43

4 / 50

215 49426 EAAH TCQEA Ed. 03

Contents

Figures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Overview of the Call Detail Record Application . . . . . . . . . . . Hardware Architecture of the CDRA (Duplex DS10) . . . . . . . Example for CDRA main menu on an A 1360 SMC screen . Example for the layout of a form . . . . . . . . . . . . . . . . . . . . . . . Form "Scheduled Job" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transfer File Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage and output of CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Circular Database" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Export" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Compression" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Alarm Display" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Backup" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Record Store Occupancy" . . . . . . . . . . . . . . . . . . . . . . . Measurements Alarm Threshold . . . . . . . . . . . . . . . . . . . . . . . . Form Corrupt Record Alarm" . . . . . . . . . . . . . . . . . . . . . . . . . 9 11 15 17 19 22 23 26 27 28 29 33 34 35 36 36

215 49426 EAAH TCQEA Ed. 03

5 / 50

Contents

6 / 50

215 49426 EAAH TCQEA Ed. 03

Preface

Preface
This tutorial is provided for the system administrator of the Call Detailed Record Application (CDRA). The objective of the tutorial is to give an overview of the CDRA function and operation. Information for each form of the graphical user interface is offered in the online help system. This help system provides a detailed description of all functions and parameters of the forms used for the various tasks. This tutorial does not contain any installation information. The CDRA Check List for the Functional Check" provides a description of procedures for checking the hardware and software of the CDRA. Possibilities for analyzing errors, tracking the OSI stack and process administration are described in the "CDRA Trouble Shooting Guide".

215 49426 EAAH TCQEA Ed. 03

7 / 50

Preface

8 / 50

215 49426 EAAH TCQEA Ed. 03

1 Overview of the CDRA

1 Overview of the CDRA

By installing the billing functionality on a Nectar based duplex server a higher transmission rate of Call Detail Records (CDR) is achieved. Figure 1 shows the basic implementation of the CDRA. The CDRA is connected to the Core Switch by a Local Subnetwork (LSN). The CDRA provides data transmission to the CDR Collector via File Transfer Protocol (FTP) (see figure 1). The operator can access the graphical user interface (GUI) of the CDRA via a local XTerminal or via an A 1360 Switch Management Center (SMC).

215 49426 EAAH TCQEA Ed. 03

9 / 50

1 Overview of the CDRA

A 1360 SMC

X11 Protocol

X11 Protocol

CDR via FTP

Core Switch

CDRA
TCP/IP Ethernet (LSN) UDP/IP

CDR Collector

Figure 1

Overview of the Call Detail Record Application

10 / 50

215 49426 EAAH TCQEA Ed. 03

1 Overview of the CDRA

1.1

Functionality of the CDRA

The communication between CDRA and core switch is based on both UDP/IP and TCP/IP . The CDRA multicasts a message containing its IPaddress, port number and state to the core switch. The UDP protocol is used for this. Call Detail Data (CDD) are directly transmitted from the Core Switch to the CDRA via FTP Internet Protocol. The Core Switch holds these CDD only until they are stored on the CDRA disk.

215 49426 EAAH TCQEA Ed. 03

11 / 50

1 Overview of the CDRA

1.2

Operational Aspects
The operator gets access to the CDRA graphical user interface via an XTerminal. It is also possible to operate the CDRA from the A 1360 Switch Management Center (SMC). A detailed description of both variants is given in chapter 2.

12 / 50

215 49426 EAAH TCQEA Ed. 03

1 Overview of the CDRA

1.3

Hardware Architecture
The CDRA is equipped with a duplicate set of hardware for switching to the standby unit in case of a failure in the active unit. Figure 2 shows the hardware architecture of the CDRA. The hardware is located in a dedicated rack of a switch. Because the connection between CDRA and CoreSystem is realized via a duplicated ethernet LAN, the rack for the CDRA must be located within 100 meters of the CoreSystem.

2 Shared Disks

2 Mirror Disks

Figure 2

Hardware Architecture of the CDRA (Duplex DS10)

215 49426 EAAH TCQEA Ed. 03

13 / 50

1 Overview of the CDRA

1.4

High Availability
The CDRA is designed as a high availability system; this includes the hardware as well as the software.

1.4.1

Hardware
The hardware works on the principle of 'No Single Point of Failure' , which means that the breakdown of a single hardware component does not lead to a complete breakdown of the CDRA. The high availability feature is realized using the following techniques:
" " "

duplicated hardware (Compaq DS10) substitution high mean time between failure (MTBF) of components and low mean time to repair (MTTR).

The following duplication strategies are used: 1. The CDRA is configured as an active/standby pair of two identical computers with two shared disks. Each shared disk has its own mirror disk. Each computer is provided with a CPU, local disk, duplicated interface cards, a CDROM drive, and a DATdrive for backup/restore tapes. If one computer fails the other computer takes over the complete functionality of the CDRA. 2. The LSN connection, including HUBs between CDRA and Core Switch (EPM), is duplicated so that data exchange is possible even if the LAN connection or the HUB fails. 3. Billing data are stored on 2 shared disks. These shared disk operate as mirrored disks. They can be changed while the CDRA system is running. The power supply, fan, controller and the SCSI connections to the computers are duplicated. In addition to the duplication of the identified hardware components, a third technique, high MTBF and low MTTR of components, is implemented.
" "

Billing data is stored in a Linear Database (LDB). It is possible to write billing data to tape (DAT).

14 / 50

215 49426 EAAH TCQEA Ed. 03

1 Overview of the CDRA

1.4.2

Software
To achieve high availability of the software, the following techniques are implemented:
" "

Highavailability Software in the runtime system 3rdPartySoftware.

Highavailability Software For supervision and handling of hardware and software errors the NECTAR (New Control Architecture) availability Server and Manager are used (NECTAR GP3.2). The NECTAR Availability Server (AS) package is a set of software components and Application Programming Interfaces (APIs) which provide secure processing in a distributed environment such as a multistation UNIX configuration. AS can multiprocess threads (software execution units) even of the same process and spread them over several microprocessors providing real parallel execution. Service continuity is achieved by an active/standby configuration.
"

Active/standby means that for each UNIX server or station used, the processes are automatically shadowed or replicated on a standby station.

So, if a station fails, the data traffic is taken over to the remaining station. In the event of an application process or a station failure the switchover to standby can be triggered automatically. AS has four service components, each controlled through a corresponding API:
"

Data Management (DM) which handles in-memory user data requests and data integrity, Communication System (CS) which provides secured communication between each component, The UNIX Operating System (OS) extension which provides functions for software supervision, The UNIX Middleware Administrator (XMA) which provides failure detection and switch-over.

"

"

"

215 49426 EAAH TCQEA Ed. 03

15 / 50

1 Overview of the CDRA

The NECTAR Availability Manager (AM) is an optional enhancement to the Availability Server and runs on standard Digital UNIX hardware using Digital Logical Storage Manager (LSM) and Advanced File System (AdvFS). AM provides:
"

a secured Local Sub Network (LSN) and secured File Management (FM), practical tools to increase availability, at platform, station and process level, configuration tools to declare, update and supervise the application hardware and software.

"

"

The Local Sub Network provides interconnection for all stations of the platform and is currently based on Ethernet. The LSN, being a duplicated LAN with two double SCSI disks for each pair of stations, guarantees the availability of the inter-station communication against network failures. This system works for all IP based communications. Application data is kept consistent and available by a secured File Management service. This is achieved through software replication (mirroring) on disks shared by a pair of active/standby stations. Even if an active station fails, the application still has access to the data. The two copies of the data are kept consistent by the AS Data Management (DM), writing all or no data to both disks. This avoids the need for file system check and reduces the time taken for a station restart. These services are being enhanced to include the use of double-shared SCSI disks and access to files even on non-pilot stations, that is, those not piloting or managing the LSN. Pilot stations also supervise the use of station resources and enable a smooth shutdown. AM tools enable hardware and software redundancy, in particular initialization, defense and re-configuration. Initialization is the action of bringing an application or a part of it from an idle or maintenance state into operation. Initialization occurs whenever an application is restarted or hardware/software is inserted. 3rdPartySoftware: Where possible, 3rdPartySoftware is used because the world wide use of such software gives the advantage of a low number of undetected errors and a high quality standard.

16 / 50

215 49426 EAAH TCQEA Ed. 03

2 Common Concepts for the Graphical User Interface

2 Common Concepts for the Graphical User Interface

The graphical user interface (GUI) is based on the OSF/Motif and follows the OSF/Motif style guide. An operator can access the graphical user interface of the CDRA via an XTerminal or from the A 1360 Switch Management Center (SMC). 1. It is possible to log in on the CDRA via an XTerminal. First a login window requesting the user name and the password is displayed. After successful login, a desktop user interface is provided. 2. The A1360 Switch Management center provides for each core switch the possibility to connect to the CDRA. The "A1360 SMC User Handbook" includes a description of how to establish a connection. After a successful login, the main menu of the CDRA appears on the screen (see figure 3).

Figure 3

Example for CDRA main menu on an A 1360 SMC screen

215 49426 EAAH TCQEA Ed. 03

17 / 50

2 Common Concepts for the Graphical User Interface

2.1

Calling of a Form
After the selection of an entry in the main menu a pull down menu is displayed. In this menu several entries are offered. Entries that represent a cascade menu are marked with an arrow on the right margin of this entry. Each entry is the start point of a form. By clicking on the entry, a form is selected and displayed. Note In the following sections starting a special form is described in the following format: <Main Menu> <Pull Down Menu> <Cascade Menu> <Entry>

2.2

Structure of a form
All forms of the CDRA are structured in the same way. In figure 4 the form "Statistics" is used as an example for the general structure. A form consists of the three following parts:
" " "

Menu Bar Button "Scheduled Job" Parameter Area.

2.2.1

Menu Bar
Within each form the menu bar is located at the top. The menu "Action" is located on the left end of the menu bar. Activating this menu will cause the display of a pull down menu which has "Close" as the last entry. Depending on the form this pull down menu can contain several other entries. On the right end of the menu bar you find the menu "Help". Activating this menu will cause the display of a pull down menu which offers online help topics for this form and the online help on the general use. Some forms provide additional menus in the menu bar. The functions of these menus are described in the online help for these forms.

18 / 50

215 49426 EAAH TCQEA Ed. 03

2 Common Concepts for the Graphical User Interface

Menu "Action"

Menu Bar

Button "Scheduled Job"

Menu "Help"

Parameter Area

Figure 4

Example for the layout of a form

2.2.2

"Scheduled Job" Button

Below the menu bar the button "Scheduled Job" is located. The button "Scheduled Job" can be set to "active" or "not active". The status "not active" can be recognized by a blue clock on the button and the status "active" by a red clock on the button. By clicking on the button the status can be changed from "active" to "not active" or vice versa. The default status of the button is "not active". If the button "Scheduled Job" has the status "active", functions that cannot be performed as scheduled jobs are locked. Forms that do not provide the possibility for creating a scheduled job have no "Scheduled Job" button.

215 49426 EAAH TCQEA Ed. 03

19 / 50

2 Common Concepts for the Graphical User Interface

2.2.3

Parameter Area
In the parameter area all input and output parameter are displayed that are necessary to perform the function associated with the form. Inputs are immediately checked for their syntax. E.g., invalid characters entered while specifying a date are rejected immediately. A semantic check of several parameters is performed after the function is activated.

20 / 50

215 49426 EAAH TCQEA Ed. 03

2 Common Concepts for the Graphical User Interface

2.3

Activating a Function
The button "Scheduled Job" must have the status "not active" if a function is to be performed immediately. The "Action" menu is used to select a function. All parameters that are needed for the performance of this function are checked. If an error is detected (missing or wrong parameter), a corresponding message will be displayed. After the correct input of all values, the action is started immediately. The result of the action is displayed in a message window when the action is finished.

215 49426 EAAH TCQEA Ed. 03

21 / 50

2 Common Concepts for the Graphical User Interface

2.4

Registration of a Scheduled Job

To register a function as a scheduled job the button "Scheduled Job" must have the status "active". The "Action" menu is used to select a function. All parameters that are needed for the performance of this function are checked. If an error is detected (missing or wrong parameter), a corresponding message will be displayed. After the correct input of all values, the form "Scheduled Job" will be opened. In this form, a date, time and optionally a period as starting points of an action can be specified. When the action "Store" is selected all parameters are checked. If no errors have been detected, the scheduled job will be registered and the form will be closed. At the specified time, the action will be performed. The result can be viewed via the form "Result Display" (see chapter 5.3). Note The time entered must at least be current time + 5 minutes!

Menu Bar Help Menu

Action Menu Parameter "Time" Parameter "Date"

Parameter "Period"

Figure 5

Form "Scheduled Job"

22 / 50

215 49426 EAAH TCQEA Ed. 03

3 CDRs: Collection and Administration

3 CDRs: Collection and Administration

215 49426 EAAH TCQEA Ed. 03

23 / 50

3 CDRs: Collection and Administration

3.1

Call Detail Records

Usually CDRs are transferred to the CDR Collector via FTP . The CDRs can also be written on DAT. Therefore, the necessary actions must be performed in a defined sequence. First the Call Detail Records are prepared, next the data is written to DAT. The CDRA provides the following possibilities for handling and administration of Call Detail Records:
" " " "

Prepare CDRs for the Linear Database (LDB) Export CDRs to DAT Statistics Change the thresholds of the disk occupancy, for sending alarms and warnings to the CDRA Alarm Handler.

24 / 50

215 49426 EAAH TCQEA Ed. 03

3 CDRs: Collection and Administration

3.2

Linear Database
The raw data is converted into call detail records. Each transfer file contains all CDRs received from the CoreSwitch within a defined interval and up to a defined size. When the configured time interval expires or the maximum file size is reached (whatever happens first), the current working file is closed and a new one is created. The closed working file then becomes a transfer file which can be fetched by the CDR Collector via file transfer or dumped to DAT by the operator. When a new working file is created because the old one has reached the file size limit, the time interval is not reset. The created transfer files are allowed to be up to 2kByte larger than the configured maximum file size. Both parameters are specified offline. It is possible to define an infinite value for one of the parameters or to switch off one of the two criteria.

215 49426 EAAH TCQEA Ed. 03

25 / 50

3 CDRs: Collection and Administration

Example: T = TransferFileInterval= 12 hours nd On the 2 day at 6 oclock, an additional transfer file is created because the maximum file size is exceeded.

Day 1
Transfer File 1 Transfer File 2

Day 2
fixed closing time for Transfer Files ! Transfer File 4

Day 3
Transfer File 5

T
0 12

T
24|0

T
6 12

T
24|0

T
12

hours

Intermediate Transfer File 2.1

Transfer File 3

Day 1: Transfer File 1 contains records from timeinterval 0...12 hours 12 ..24 hours Transfer File 2 contains records from timeinterval Day 2: Intermediate Transfer File 2.1 contains records from timeinterval 0...6 hours 6...12 hours Transfer File 3 contains records from timeinterval Transfer File 4 contains records from timeinterval 12...24 hours Day 3: Transfer File 5 contains records from timeinterval 0...12 hours

Figure 6

Transfer File Creation Raw blocks are stored in a raw buffer on disk immediately after reception. The raw records contained in those raw blocks are processed to cooked detailed billing records at once. They are buffered in socalled working files and stored as files of billing records (transfer files) in a linear database. Files which have been transferred to the CDR Collector and/or dumped to DAT can be deleted from the record store via FTP or operator command. Operators can only delete files that have already been stored on DAT. When the disk space assigned to the Linear Database is fully occupied, new records received from the core switch are stored in the raw buffer. The process stops acknowledgment and storage of new raw blocks from the core switch as soon as the raw buffer is full. Therefore the filling of the record store is supervised and alarms are generated at configurable thresholds.

26 / 50

215 49426 EAAH TCQEA Ed. 03

3 CDRs: Collection and Administration

CDRA

Figure 7

Storage and output of CDRs

The storage procedure works automatically without any operator intervention. It allows to store billing records as well as the maximum possible amount of CDRs.

215 49426 EAAH TCQEA Ed. 03

27 / 50

3 CDRs: Collection and Administration

3.3

Communication with the CDR Collector

Prepared Call Detail Records are fetched by the CDR Collector via FTP from the Linear Database. The interface is based on standard FTP , with the CDRA as the FTP server and the CDR Collector as the FTP client. The CDRA has only one IP address, regardless which station is the currently active one. This address can be given in the standard notation with dots (e.g. 123.45.67.89).

28 / 50

215 49426 EAAH TCQEA Ed. 03

4 CDRA Operation

4 CDRA Operation
The operation of the CDRA is supported by the following applications:
" " " " " "

File and Data Management Alarm Administration User Administration Backup and Restore Time Scheduling Measurements

215 49426 EAAH TCQEA Ed. 03

29 / 50

4 CDRA Operation

4.1

File and Data Management

The CDRs that are generated from the raw data from the core switch are temporarily stored in a working file. As soon as either a predefined delay timer has expired or a predefined record lenght is reached the working file is closed and converted into a transfer file that is then moved into the record store . Note The database variant is defined at installation time. For the CDRA a Linear Database is used (see above 3.2). The menu, however, does not reflect this setting. The menu entry is Circular database" by default. The following user actions can be performed via the menu Billing/Accounting":
" " " " "

Display Current Configuration Prepare records for export to DAT Export records to DAT Delete records from database Set compression option (on/off).

Scenario: View Occupancy

View occupancy of record store and prepare records for export to DAT: 1. Open the Form Circular Database": Billing Server Billing / Accounting Circular Database 2. Select a Database from the field Names of Circular Database", e.g., Detailed Billing". 3. Select menu option Current Configuration. A list of all records available in the database is displayed.

30 / 50

215 49426 EAAH TCQEA Ed. 03

4 CDRA Operation

Figure 8

Form Circular Database"

The form displays the following information on the occupancy of the database:
D D D D D D D D D D

globally for the entire database: number of days covered number of records date and air seizure time of oldest record data and air seizure time of youngest record for each day covered: date number of records date and air seizure time of oldest record data and air seizure time of youngest record

Prepare Transfer File

1. Select menu option Prepare from the menu Action of the form Billing Server Billing / Accounting Circular Database A transfer file containing the most recent data will be created. If prepare has already been started by another user or by the normal preparation cycle, a corresponding message is displayed and the action is aborted.

Export Transfer File

1. Open Form Export": Billing Server Billing / Accounting Export

215 49426 EAAH TCQEA Ed. 03

31 / 50

4 CDRA Operation

Figure 9

Form Export"

2. Select a database name from the field Names of Circular Database", e.g., Detailed Billing". 3. Select option Current Configuration from the menu Action to update the database contents display. 4. Select a DAT device. 5. Select the transfer file(s) to be exported from the database contents file list. 6. Select option Export from the action menu to dump the selected files to DAT.

Delete Files from Database Set Compression

1. In the form Export": Select file(s) to be deleted from the database contents file list. 2. Select option Delete from the menu Action. The menu option Billing Server Billing / Accounting Compression allows administration of the compression option for the transfer files via the form Compression".

32 / 50

215 49426 EAAH TCQEA Ed. 03

4 CDRA Operation

Figure 10

Form Compression"

1. Select option Current Configuration from the menu Action. 2. Select compression option (on/off). 3. Select menu option Save from the menu Action to save the new setting.

215 49426 EAAH TCQEA Ed. 03

33 / 50

4 CDRA Operation

4.2

Alarm Administration
If the CDRA detects a serious error, a corresponding alarm is set to "On". If this failure is fixed, the corresponding alarm is set to "Off". If the Core System is connected to a A 1360 Switch Management Center, the CDRA alarms and the alarms of the Core System can be handled by this A 1360 Switch Management Center. The CDRA includes the form "Alarm Display", which can be used to display the CDRA alarms and reports independent of an existing connection to the Core System.

Figure 11

Form Alarm Display"

The form "Alarm Display" can not be used to activate or deactivate alarms ! The form offers two lists. One for displaying all active alarms, the other for displaying reports. For each alarm and report the operator has the possibility to display corresponding detailed information. By clicking on the alarm/report entry, single alarm/reports can be selected. After choosing the menu entry "Alarm Description" or "Report Description" the alarm/report text, a detailed description and recommended actions will be displayed in a separate window.

34 / 50

215 49426 EAAH TCQEA Ed. 03

4 CDRA Operation

4.3

User Administration
The following nine different user groups are defined for the CDRA: OMC_MAN: ADM: OC: COC: ALCATEL: CCC: NM: ICEP: EMERG DISP OMCManagement AgencyAdministrator Operation Control Central Operation Control System Supplier (Remote Diagnostics & SWInstallation) Access Administration (Central Charging Comparison) Central Network Management Interception Emergency Administrator Display

When a user is registered at the CDRA, this user is assigned to one user group. Each user group has its own set of forms that can only be accessed by users registered to this group. E. g., the form "User Administration" is attached to the user groups "ADMIN" and "COC". This form cannot be accessed by a user attached to the user group "OMC_MAN". Refer to appendix A for the allocation of forms to user groups. The main menu of the CDRA is adjusted in a way that when a user logs on, only those forms associated with the user group of the user are accessible. At the first registration of a user, the associated account name and password are identical. When this user logs on for the first time, the form "Change Password" will appear automatically. Restrictions regarding user accounts:
" "

The user account smc_adm is not allowed for the CDRA. The user acounts bill_adm, oftuid, MSBACK, uce_ins, root, sys, adm are not allowed as common users.

Scenario:

Changing Access Rights of a User Initial Situation: A user is attached to the user group "ADMIN".

215 49426 EAAH TCQEA Ed. 03

35 / 50

4 CDRA Operation

Task: The task area of a user is to be changed from group "ADMIN" to the user group "EMERG". 1. Call the form "User Administration": Billing Server Administration User Administration
D

The form "User Administration" will be displayed on the screen. The form "User List" will be displayed. All user names of the CDRA are listed in the "List of Users". The selected name is displayed in the parameter "Selected User". The window "User List" will be closed. In the form "User Administration" the selected name is displayed in the parameter "User Name". The button "ADMIN" in the parameter "User Groups" is active. In the list "Registered Scheduled Jobs" all scheduled jobs are displayed that are registered by the selected user. Within the parameter "User Groups", the button "ADMIN" is no longer active but the button "EMERG" is now active.

2. Choose the function "Select User" in the menu "Action".

D D

3. Select a user in the parameter "List of Users".

D

4. Press the "OK" button.

D D D D

5. Click the button "EMERG" in the parameter "User Groups".

D

6. Choose the function "Change" in the submenu "User" of the menu "Action".
D D

In the area of the form, the mouse pointer changes its appearance to a clock. At the end of the action, a dialogue window with the result message appears on the screen. The mouse pointer resets its appearance to "Pointer". The message window is closed and the action is finished.

7. Press the "OK" button for confirmation.

D D

36 / 50

215 49426 EAAH TCQEA Ed. 03

4 CDRA Operation

4.4

Scheduled Jobs
Nearly all the functions that can be started immediately can also be registered as scheduled jobs. One exception to this rule is, e.g., the action "Change Password". The registration of scheduled jobs is described in chapter 2.4. Display scheduled jobs: Billing Server Administration Scheduled Jobs Registered Scheduled Jobs Only users attached to the user group ADMIN have access to the scheduled jobs of other users. For members of this user group the form "User Administration" provides the option of display and deletion of any scheduled job of any user. Billing Server Administration User Administration

ATTENTION

Administration of Results

The result of scheduled jobs can be displayed and deleted via the form "Result Display": Billing Server Administration Scheduled Jobs Results This form displays a list of the results of scheduled jobs that have been registered by the user. Single results can be selected by clicking on the corresponding entry in the list. Choosing the entry "Description" in the menu "Display" will cause a detailed description of the selected result to be displayed in the parameter "Result Description". The action "Delete" and "Delete All" can be used to delete selected or all results. A user attached to the user group "User Administration", can view and delete results of other users via the form "User Administration". Within this form the function "Select User" in the menu "Action" can be started. Results of the selected user can be displayed and also be deleted.

215 49426 EAAH TCQEA Ed. 03

37 / 50

4 CDRA Operation

4.5

Backup/Restore
A user attached to the user group "System Administration" is authorized to perform a backup and restore activity. For initiating a system backup the following forms are used: Billing Server System Administration Backup Within this last form, a backup can be started immediately or as a scheduled job. Details of this action can be found in the document Trouble Shooting Guide" (UG23).

Figure 12

Form Backup"

38 / 50

215 49426 EAAH TCQEA Ed. 03

4 CDRA Operation

4.6
4.6.1

Measurements
Statistics Counters
The CDRA provides the following statistics counters:
" " "

Number of raw records received Number of corrupted raw records detected Number of cooked records written on disk.

4.6.2

Measurement Interval
All statistics counters have the same measurement interval. At the end of each interval all current counter values are written on disk and then reset to zero. The Interval can be specified via menu selection: Billing Server Statistics

Figure 13

Counter Intervals

4.6.3

Counter Reliability
In case of an application restart or platform switchover it is not required to recover the values of the statistics counters. The counters is reset to zero and the measurement interval is started from the beginning after the restart/switchover.

215 49426 EAAH TCQEA Ed. 03

39 / 50

4 CDRA Operation

4.6.4

Storage of Measurements Results

The file with the measurements results is in readable ASCII format. It has the following columns: end date / time of the interval and one column for each of the counters. In case of a restart/switchover a line indicating the reset of the counters is written to disk, consisting of date/time and placeholders for the counter values (e.g. `###'). The measurements results shall be kept for StorageRetain Measurements days on the CDRA disks.

4.6.5

Record Store Occupancy Alarms

The menu selection Billing Server Disk Occupancy Occupancy File Store provides a form in which alarm and warning thresholds for monitoring the occupancy of the partition that contains all record stores can be defined. The following occupancy values can be displayed and defined:
"

Alarm level Disk occupancy of the record store partition in percent. If the disk occupancy reaches the specified value, an alarm is issued. The value can range from 1100, 100% meaning that the alarm function is disabled.

"

Warning level If the disk occupancy reaches the specified value, a warning is issued.

"

Warning repetition level Specifies the disk occupancy increment value for further warnings to be issued after the warning threshold has been reached (e.g., if the warning threshold is set to 30 %, and the repetition level to 5%, a new warning will be issued when 35%, 40%, etc. occupancy is reached).

The menu option Current Configuration from the menu Action displays the current setting for the thresholds. New settings have to be saved via menu option Save .

40 / 50

215 49426 EAAH TCQEA Ed. 03

4 CDRA Operation

Figure 14

Form Record Store Occupancy"

4.6.6

Corrupted Raw Records Alarm

If the value of the `number of corrupted raw records' counter exceeds a configurable threshold during a measurement interval, an alarm is triggered before the end of the interval. The measurement interval for the corrupted raw records alarm is configured at installation time and independent of the measurement interval of the corresponding statistics counter.
threshold crossing alarm

# of corrupted raw records

measurement interval

alarm threshold

time t

Figure 15

Measurements Alarm Threshold

215 49426 EAAH TCQEA Ed. 03

41 / 50

4 CDRA Operation

This threshold can be set via the form Billing Server Disk Occupancy Corrupted Record Alarm

Figure 16

Form Corrupt Record Alarm"

The menu option Current Configuration from the menu Action displays the current setting for the threshold. A new setting has to be saved via menu option Save.

42 / 50

215 49426 EAAH TCQEA Ed. 03

Abbreviations

Abbreviations
AM APIs AS CDD CDR CDRA CS DAT DM FM FTP GUI LDB LSM LSN LSN MTBF MTTR OS OSF SMC XMA Availability Manager Application Programming Interfaces Availability Server Call Detail Data Call Detail Records Call Detailed Record Application Communication System Digital Audio Tape Data Management File Management File Transfer Protocol Graphical User Interface Linear Database Digital Logical Storage Manager Local Subnetwork (ethernet in a Nectar environment) Local Sub Network Mean Time Between Failure Mean Time To Repair Operating System Open Software Foundation Switch Management Center UNIX Middleware Administrator

215 49426 EAAH TCQEA Ed. 03

43 / 50

Abbreviations

44 / 50

215 49426 EAAH TCQEA Ed. 03

Appendix A Attachment of Access Rights to Forms

Appendix A
A.1 Menu "Print":

Attachment of Access Rights to Forms

This menu is only provided after a direct login via XTerminal.

Menu "Print"

OMC_MAN

ADM

OC

COC

AL CA TEL x x x

CCC

NM

ICEP EMERG DISP

Print Form Print Region Print Screen

x x x

x x x

x x x

x x x

x x x

x x x

x x x

A.2

Menu "Desk":
This menu is only provided after a direct login via XTerminal.
Menu "Desk" OMC_MAN ADM OC COC AL CA TEL x x CCC NM ICEP EMERG DISP

Desktop Style Text Editor

x x

x x

x x

x x

x x

x x

x x

A.3

Menu "Administration":
OMC_MAN ADM OC COC AL CA TEL x x x CCC NM ICEP EMERG DISP

Menu "Administration"

Change Password User Administration Scheduled Job: Results Scheduled Job: Created Jobs

x x x x

x x x

x x x

x x x x

x x x x

A.4

Menu "System Administration":

OMC_ MAN x x x x x x ADM OC COC AL CA TEL x x CCC NM ICEP EMERG DISP

Menu "System Ad ministration" UNIX Window Backup

x x

215 49426 EAAH TCQEA Ed. 03

45 / 50

Appendix A Attachment of Access Rights to Forms

A.5

Menu "Billing/Accounting":
Menu"Billing/ Accounting" OMC_MAN ADM OC COC AL CA TEL x x x CCC NM ICEP EMERG DISP

CDB Compression CDB Prepare Export to DAT

x x x

x x x

x x x

A.6

Menu "Disk Occupancy":

OMC_MAN ADM OC COC AL CA TEL x x x CCC NM ICEP EMERG DISP

Menu "Disk Occupan cy" Corrupted CDD Alarm Threshold CDB Occupancy Real Time Buffer

x x x

x x x

x x x

A.7

Menu "Communication":
OMC_MAN ADM OC COC AL CA TEL x x CCC NM ICEP EMERG DISP

Menu "Communica tion" Real Time Block Size Billing Center IP address change

x x

x x

x x

A.8

Menu "Statistics":
OMC_MAN ADM OC COC AL CA TEL x CCC NM ICEP EMERG DISP

Menu "Statistics"

Measurement adminis tration

A.9

Menu "Alarm":
Menu "Alarm" OMC_MAN ADM OC COC AL CA TEL x CCC NM ICEP EMERG DISP

Alarm Display

46 / 50

215 49426 EAAH TCQEA Ed. 03

Appendix A Attachment of Access Rights to Forms

A.10 Menu "Statistics":

Menu "Alarm" OMC_MAN AD M OC COC AL CA TEL x CCC NM ICEP EMERG DISP

Measurements Adminis tration

215 49426 EAAH TCQEA Ed. 03

47 / 50

Appendix A Attachment of Access Rights to Forms

48 / 50

215 49426 EAAH TCQEA Ed. 03

Index

Index A
Action Menu, 18 Alarms Alarm Administration, 28 Corrupted Raw Records, 36 Thresholds, 36 AMA, 23 Availability Server, 13 Availabilty Manager, 13

E
Export, 27

F
File and Data Management, 25 Compression, 28 Delete, 28 Export Transfer File, 27 Prepare Transfer File, 27 Forms, 16 Parameters, 18 FTP , 9, 10, 21, 22, 24

B
Backup/Restore, 33

C
CDD, 10 CDR, 9, 21, 24 File Management, 25 Storage, 23 CDR Collector, 9, 21, 22, 24 CDRA, 7 Functionality, 10 Hardware Architecture, 11 Main Menu, 15 Operation, 10, 25 Overview, 9 Compression, 28 Core System/Switch, 9, 10, 11, 12, 15, 21, 28 Corrupted Raw Record Alarm, 36 Counters, 33 Reliability, 34

G
Graphical User Interface, 9 Action Menu, 18 Forms, 16 Main Menu, 15 Menu Bar, 16 Overview, 15

H
Hardware, 12 Hardware Architecture, 11 Help, 16 High Availability, 12 HUB, 12

I
IP Address, 24

D
DAT Drive, 12 DAT Dump, 21 Data Management, 13, 14 Delete, 28

L
LAN, 11, 14 Linear Database, 12, 21 LSN, 12, 13

215 49426 EAAH TCQEA Ed. 03

49 / 50

Index

M
Measurements, 33 Measurement Interval, 33 Storage of Results, 34 Menu Bar, 16 Mirror Disk, 12 MTBF , 12 MTRR, 12

Storage Procedure, 23

T
TCP/IP , 10 Transfer File, 21, 22 File Size, 21 Trouble Shooting Guide, 7, 33

N
NECTAR, 13

U
UDP , 10 User Administration, 30 User Groups, 30

O
Occupancy Alarms, 34 File Store, 25 OSI Stack, 7

X
X-Terminal, 10, 15

P
Password, 32 Prepare, 27 Protocols FTP , 9, 10, 21, 22, 24 TCP/IP , 10 UDP , 10

R
Raw Blocks, 22 Raw Buffer, 22

S
Scheduled Jobs, 17, 32 Registration, 19 SMC, 9, 15, 28 Software, 12 3rd Party Software, 14 High Availability, 12 Statistic Counters, 33

50 / 50

215 49426 EAAH TCQEA Ed. 03