Users Guide

ARQOS NG
Version 1.1.0
Users Manual
Portugal Telecom Inovao, S.A.
Copyright(c) 2010 PT Inovao, S.A. All rights reserved. Full or partial reproduction,
copying, translation or conversion to electronic format of this manual is prohibited
without strict written authorization of PT Inovao, S.A.
ArQoS NG is a registered trademark of PT Inovao, SA.
Users Manual: V.1.0: May 2010

Technical contact information: Manuel Aguiar aguiar@ptinovacao.pt

Rua Eng. Jos Ferreira Pinto Basto
3810-106 Aveiro Portugal
http://www.ptinovacao.pt
Tel: +351 234 403 200
Fax: +351 234 424 723
ii
Users Manual
This manual describes the Management System
ArQoS NG.
The access to this application is done via web
browser by invoking the URL where the web
application management system ArQoS NG
resides.
iii
Index of Content
Introduction
Systems purpose
Architecture
Organization
4.1
Login
4.2
Access control system SCA
4.3
Site Manager - SM
4.4
Resource Manager RM
10
4.4.1
Management and Configuration of Managed Elements
10
4.4.2
Status List
13
4.4.3
Discovery
14
4.4.4
Inserting a probe
15
4.5
Alarm Manager AM
16
4.6
ArQoS
17
4.6.1
Macros
18
4.6.2
Interactive Tests
21
4.6.3
Tests
25
4.6.4
Tests Array
28
4.6.5
Calendar
30
4.6.5.1
Recursive Tests
32
4.6.6
Results
34
4.6.7
Reports
36
Common Problems and Solutions
38
5.1
Cannot access the system
38
5.2
Submit button is invisible or inaccessible.
38
5.3
Button Close in ArQoS (also RM or SM) doesnt perform logout
39
5.4
Error message on running a test
39
5.5
I get an error message when trying to read a test
40
iv
Q_PDS_DM_006_V1.3
Error! Reference source not found.
ArQoS Version 1.1.0
ArQoS Version 1.1.0
1 Introduction
The purpose of this manual is to describe user application interfaces of Management
System ArQoS NG.
The outline of this manual is:
Architecture
Systems components
o
Login and applications selection page component
Access Control System component
Site Manager component
Resource Management component
ArQoS NG component
Q_PDS_DM_006_V1.3
At the end is presented a list of common problems and solutions.
ArQoS Version 1.1.0
2 Systems purpose
Q_PDS_DM_006_V1.3
ArQoS NG system allows the operator to make performance monitoring test

calls/connections over different kinds of network technologies (fixed/mobile/IP). The
system gathers QoS network parameters (KPI and KQI), and evaluates its
associated network services functional aspects, according to the related ETSI/ITUTI/IETF/3GPP standards and recommendations, wherever suitable.
ArQoS Version 1.1.0
3 Architecture
ArQoS NG is a modular, scalable, future-proof solution that can easily adapt to
network or service evolutions.
Figure 1 intends to represent ArQoS NG Management Systems architecture. As
shown below, the System consists of several probes (mobile or fix) and by the
Management System that communicates through a backbone IP. ArQoSs Probes
can have Wireless, PSTN, RDIS and VoIP modules. The Management System
controls ArQoSs probes and allows users to configure tests and generate reports.
Q_PDS_DM_006_V1.3
Figure 1 ArQoS NG - Architecture
ArQoS Version 1.1.0
4 Organization
The Management System ArQoS NG is organized in independent modules that
combined have features to manage/configure/query all systems aspects.
The main modules are:
Access control systems SCA
Site Manager SM
Resource Manager RM
Alarm Manager AM
Configuration Manager CM
ArQoS
A more detailed description is presented below.
4.1
Login
The Management System ArQoS NG is accessed through a central point. To simplify

the reading of this document its assumed that ArQoS NG is accessible in the URL
http://IP:Port/StartingPoint. The IP and Port address are dependent on installation.
Q_PDS_DM_006_V1.3
Figure 2 - Login page
After credentials validation, user is presented with a panel of the modules that are
available on the Management System, as presented in the figure below.
ArQoS Version 1.1.0
Figure 3 - Application Selection Page
The Application Selection Page gives Access to the Management Systems modules.
Logout can be done at this point, otherwise its done automatically when this page is
closed. It is recommended to use the logout button.
All the modules present a quick menu for direct navigation to another module. On the
example below, the selected module is the Site Manager where its possible to
navigate to Resource Manager, Alarm Manager, Access Control System SCA or
ArQoS. If you want to maintain current window opened, navigation must be done
throught Application Selection Page.
Q_PDS_DM_006_V1.3
Figure 4 - Quick menu for module navigation
4.2
ArQoS Version 1.1.0
Access control system SCA
Q_PDS_DM_006_V1.3
Description of Access Control Systems - SCA is not covered by this Manual. The
SCA Users Manual is accessible in the Help link of the application SCA and in the
URL http://172.16.48.20/sca/manuals/SCA_MNMU_UserManual_V3.0.pdf
4.3
ArQoS Version 1.1.0
Site Manager - SM
The purpose of the Site Manager is to create and configure an organizational tree
and hierarchy that supports the arrangement of the resources.
Building this organizational tree must be the first step of the Management Systems
usage.
The following Figure presents one image of the SM with an example of the
organizational tree.
Figure 5 - Site Manager
The functions to add and remove entities from the organizational tree are marked in
yellow with arrow 1. It is possible to refresh the tree with the button
. This function
only affects the attached area. On the figure above, the refresh command marked
with arrow 1 refreshes the organizational tree and the one marked with arrow 2
refreshes the main window.
Q_PDS_DM_006_V1.3
Note that the Close button on yellow area 2 only closes current window, not
performing logout from the Management System.
ArQoS Version 1.1.0
Figure 6 - Element Type Selection
Error! Reference source not found. presents several different entity types that can
define a new element. Element configurations are quite simple, only requiring the
name, code and managed domain. The last parameter, Managed Domain shows a
list of options which are configured usingSCA.
Q_PDS_DM_006_V1.3
Figure 7 Insert New Element
4.4
ArQoS Version 1.1.0
Resource Manager RM
RM is the module to discover, insert and configure ArQoSs Probes. Each probe
must be inserted on the Management System in one single node of the tree that was
previously created on the site manager. By that fact, the general layout of the RM is
quite similar with the SM, but the functionalities and operation are very distinct.
Figure 8 - Resource Manager
Navigation on RM is performed through the buttons identified inside yellow oval of

the above picture, including management and configuration of the managed
elements like ArQoS Probes, status list and discovery.
4.4.1
Management and Configuration of Managed Elements
Q_PDS_DM_006_V1.3
Element selection is possible through tree navigation. With an element selected, new
operation tabs are visible where query, management and configuration operations
are performed. Some examples of query, management and configuration menus are
presented on the next figures. These menus depend on the options selected by
users.
10
ArQoS Version 1.1.0
Figure 9 - Graphic Elements
On area 1 its presented some information about the ArQoS Probe. Some of this
information can be updated/changed by users, while others are merely informative.
The following pictures show different parameters available in different tabs.
Q_PDS_DM_006_V1.3
Figure 10 - Managed Elements - Additional Information
Figure 11 - Managed Elements - Configuration
11
ArQoS Version 1.1.0
Figure 12 - Managed Elements - Status
Area 2 shows the operations executable on the ArQoS Probe. In this case, only
Reset is available.
Area 3 shows the modules preset on the ArQoS Probe. This graphical information is
also showed in a tabular view, as we can see in the figure below.
Figure 13 - Managed Elements - Modules List
Area 4 shows the operations that can be performed on the managed elements, with
emphasis for element removal.
Q_PDS_DM_006_V1.3
Each ArQoS Probe has its own specific configurations, accessible through the lower
tree, as shown in the next figure.
12
ArQoS Version 1.1.0
Figure 14 - Managed Elements - Module Configuration
On the Area 1 the modules are selected and on area 2 its specifics parametters are
showed and can be configured. Its important to notice that there are several tabs
that group related parametters. The number and type of tabs depend on the type of
the selected module.
4.4.2
Status List
Q_PDS_DM_006_V1.3
The option List provides access to a list of existing modules with description of it
status. The Figure bellow presents an example. This list has the advantage of quickly
supply a general preview of the operational and administrative status and location of
each module.
13
ArQoS Version 1.1.0
Figure 15 - Modules Status List
4.4.3
Discovery
The discovery functionality allows to discover probes by IP. Before inserting one
Probe in the system it must be discovered first.
Q_PDS_DM_006_V1.3
This option receives an IP address of a specific ArQoS Probe and try to istablish
communication with it. Its then possible to register that Probe on the management
System.
Figure 16 - Probe Discovery

14
4.4.4
ArQoS Version 1.1.0
Inserting a probe
After establishing a connection with the ArQoS Probe and gather some information,
the probe is ready to be inserted and registered in the ArQoS System. Before that,
the user can update information available, if the probe is selected, in the panel.
To insert a probe the user should drag and drop to one node in the tree.
Q_PDS_DM_006_V1.3
Figure 17 Inserting a Probe
15
4.5
ArQoS Version 1.1.0
Alarm Manager AM
Alarm Manager AM collects and manages system alarms.
Figure 18- Alarm Manager
Q_PDS_DM_006_V1.3
The alarm operations toolbar is marked with yellow area 2. Some of these
functionalities imply that at least one alarm must be selected: comment,
acknowledge, unacknowledge, close, view details and send by e-mail. In this area
there is also a text box to perform searches over listed alarm information and a
button to access filter management.
16
4.6
ArQoS Version 1.1.0
ArQoS
The ArQoS module enables users to create and execute tests, analyze results and
generate reports.
Each test is made of one or more macros. A macro can be defined as a group of
tasks organized in a certain sequence.
Macros and tests are reusable, i.e., after defined they can be used as many times as
needed. The only present restriction is related with the profile of the user that defined
the macro.
The first two phases of ArQoS usage must be macros and test creation. Naturally,
only afterwards its possible to schedule tests, which is simply to define the time
when they are going to be executed.
The final stage is to query and analyze the individual task execution results and to
produce overall reports over this information.
Q_PDS_DM_006_V1.3
Following, more details are presented on each of these phases
17
4.6.1
ArQoS Version 1.1.0
Macros
The ArQoS general layout is presented in the Figure below.
Figure 19 - ArQoS NG - Macros
Q_PDS_DM_006_V1.3
In this figure we can identify several distinct areas:
Area 1: navigation operations between ArQoS screens: Macros, Tests,

Calendar, Results and Reports. These buttons are present in all of the listed
screens. Navigation is possible from each screen to another without any
specific order at any time.
Area 2: macros management operations as search, add new, remove,

duplicate, refresh, export and print.
Area 3: list of existing macros, by default ordered by creation date. The

selection box attached to each macro is only used to select one or more
macros for removal.
Area 4: programming macros. This area is activated after selecting a macro

from the list or by using the option Add Macro .
Bellow the programming grid is presented the name of macro (it must be
unique), a zoom scale selection and, if the user has proper permissions, the
macros scope. The scope defines the visibility of the macro, i.e., a private
macro is only visible to the user that created it, while public ones are
accessible by all users. The permissions to perform this operation (and
others) are defined on SCA.
18
ArQoS Version 1.1.0
Area 5: list of available tasks. Macros are built over a group of pre-defined
and configurable tasks, listed on this area. Tasks are arranged into the
categories Voice, Data, IP, General and Scripts marked with unique and
distinct colors.
Area 6: task categories. Tasks from each category can be hidden or

presented by clicking on the corresponding category. The goal is simplify task
selection tasks,
The most important areas for building a macro are the list of tasks, the programmer
and the task properties area. These areas are displayed with more detail on the
figure below.
Figure 20 ArQoS NG - Building Macros
The grid for building macros is the area where tasks to be executed are placed. The
six lines of the grid, from A to F, represent six potential modules, called virtual
modules, and all the tasks at a line are executed by the same module. At this stage,
no ArQoS Probe Module is specified. With this abstraction level, macros can be
applied later to any module of a Probe, maximizing its reutilization.
Q_PDS_DM_006_V1.3
Tasks arrangement on Timeline is done by simple drag and drop operations from
the tasks list to the desired position. Removing a task on the Timeline is done by
clicking on the option
placed beside the macros name.
Each task has specific properties, showed on the Properties Area, under the
Timeline. These properties must be configured each time a task is used. There are
two properties common to all tasks: the delay of the beginning of the task referred to
the beginning of the macro (by default 0), and the time to end the task, or Timeout,
also referred to the beginning of the task. These two values can be adjusted
graphically, or in a more fine grained way in the properties. Graphically, the
beginning of the test is adjusted by dragging the task on the left side of the task icon.
The termination of the task is adjusted by dragging the right end of the task icon.
19
ArQoS Version 1.1.0
To simplify the manipulation of the programmer grid, users can zoom in and out the
time scale. It is also possible to adjust these parameters writing directly in the related
text boxes.
Q_PDS_DM_006_V1.3
To facilitate the use of the programming schedule, users can increase or decrease
the time scale of the grid, choosing the appropriate time 'Scale' on the select box that
lies underneath the grid. Its also possible to increase or decrease the work areas,
using the 'handles' of horizontal and vertical separators, as shown in the figure.
The command 'Apply' at the lower right allows the user to save changes to the
macro. However, the system is prepared to ask for confirmation when users try to
perform an action that could result in loss of changes.
20
4.6.2
ArQoS Version 1.1.0
Interactive Tests
An Interactive Test is a macro that is being tested as it is being created. This way,
users can immediately check whether the tasks used are appropriate and if the
properties are correctly configured. They are commonly used for troubleshooting
operations or immediate verification tests.
The interactive test button that lies at the right bottom allows access to the area of
Interactive Tests.
As shown in the figure below, some of the macro building details remain visible, as
new screens are visible where the execution can be controlled. Mode detains are
described below.
Q_PDS_DM_006_V1.3
Figure 21 ArQoS - Interactive Test
One of the requirements needed to run an interactive test is to select which ArQoS
modules will run each line of virtual modules on the programmer. To select desired
modules use tab 'Modules', which shows the ArQoS modules available in the system,
and drag them to the programmer boxes that represent virtual modules from 'A' to 'F'.
Each ArQoS module can only perform the tasks in one virtual module, so they
disappear from the available list as they are assigned to virtual modules. If you want
to remove a module, just drag it to the modules list again or press the option
below.
21
ArQoS Version 1.1.0
Double clicking on a ArQoS Probe Module on this list opens a window with the RM
module in question selected. This facility allows users to query and/or configure
ArQoS module parameters, in order to better configure the test in question. In case
you need to consult another ArQoS Probe Module, the content of the window of RM
is updated.
Note that the ArQoS Probe Module list may present the following states:
ArQoS module busy

ArQoS module free
Table 1 - Module states
In case an ArQoS module is busy, it cant be used in an interactive test. It is not

necessary to occupy all the boxes of virtual modules, simply fill in only those with
assigned tasks, or those listed in the configuration tasks. The latter situation may
occur with the task 'Make Call' when indicating the call destination virtual module B.
Even if the module B does not perform any task, as it has been indicated as a call
receiver, if not assigned a ArQoS Probe Module to box B, user will receive an error
message later due to lack of indication of ArQoS Probe Modules.
Figure below shows the commands that can be used to control the interactive tests.
Basically there are three, self-explanatory, commands: "Run" to run the test, 'Restart'
to restart the test and 'Save' to record a macro with the interactive test performed and
the results obtained. In the latter case user is required to specify a name for the
interactive test. The command "Run" automatically changes to 'Stop' when the test is
already running.
It is also shown a summary of the number of tasks to be performed, programmed and
implemented with success or failure.
Q_PDS_DM_006_V1.3
As the test is being executed, the user is having the visual representation of
execution state, as exemplified in the following figure.
22
ArQoS Version 1.1.0
Figure 22 - ArQoS Interactive Test - Results
Q_PDS_DM_006_V1.3
Each symbol has a specific meaning and is listed in the following table:
23
ArQoS Version 1.1.0
The test was totally performed

The test was partially performed
The test is running
Failed to program the module
The tasks were executed successfully
The tasks are being executed
The tasks were executed without success
Table 2 - Interactive Test States
Upon execution completed, the user will have access to the tab 'Results', where
result details for each task are presented.
While a test is running, the user can not change the contents of the programmer or
the properties of tasks. Once the execution ends (because it completed all the tasks
or because the user pressed the command 'Stop'), it is possible to change the
programmer, adding or removing tasks in any of the modules 'A' to 'F', or change the
properties of existing tasks. You can choose to continue running the test from the last
work performed or restart the execution.
When satisfied with the outcome, if required, its possible to leave the area of
Interactive Tests and return to the area of macros' configuration, where you can
record a macro with the tested tasks. Thus, the user can ensure that the created
macro will run the way it aims as its configuration was already tested with ArQoS
Probe Modules.
Q_PDS_DM_006_V1.3
Additionally to create a macro, configure it and test it is also possible to select a preexisting macro from the list of macros and run it in the area of Interactive Tests. It is
also possible to make any necessary changes to the configuration of the macro until
the result is satisfactory. The only caveat here is that if the macro is tested for use in
a test (described below), its not possible to save the modifications with the same
name, and a new macro must be created.
24
4.6.3
ArQoS Version 1.1.0
Tests
The next step is to create tests that use the previously created macros. A test can
only use a single macro, or may consist of several macros and/or repetitions of the
same macro. Thus it is possible to quickly create tests of considerable complexity.
The figure below shows an example of a test screen.
Figure 23 - ArQoS Tests
The elements of this screen are quite similar to the ones on the Macro screen.
The area marked with 1 contains the commands that can be performed on the tests,
including create, remove and duplicate tests as well as searching for specific tests.
The test list displays all existing tests that the user has access to. Note that the
checkbox only serves to select one or more tests for removal.
Area 2 is the test programmer. At the bottom of the programming grid areas the user
has text box in order to assigns a name to the test (this name must be unique). User
can also configure the public scope if he has the proper permissions. The is also an
option to controls the time scale of the programming schedule. The test name should
be unique.
Q_PDS_DM_006_V1.3
In Area 3, on the right, is the list of available macros for creating tests. Macros are
classified according to its scope, public or private, the user can choose to view only
the private macros, only public macros, or both selecting the two buttons located on
top of the list.
25
ArQoS Version 1.1.0
By double click a macro in this list it opens the Macros window, which allows the user
to see the composition of the macro in question. If this window is already opened,
double clicking on another macro replaces the information presented.
The areas 2 and 3 are only active when the user selects the command to create a
new test ( ) or selects a test from the list of existing tests. The same applies to the
tab 'Creation of Tests Array', which is described in following sections.
To configure a test is mandatory identifying the macros that constitute it and its
configuration: sequential, simultaneous or mixed (as is the case represented in the
previous figure). In addition, for each macro is necessary to specify the ArQoS
modules that will occupy the positions of virtual modules.
The following figure shows an example of configuring a test.
Figure 24 - ArQoS Creating Tests
The indication of the macros that are part of a test is done by dragging the selected
macro to the scheduler tests grid. Macros placed in the same row will be executed
sequentially. Macros placed in different rows can be performed simultaneously, if
their moment of execution overlap, or sequentially, if not. It is not mandatory that the
programmer macros are unique. Users can repeat the same macro as many times as
intended so.
The programmer area can be controlled by hiding or adjusting the areas in the left
and below, through the 'handles' in the middle of the existing vertical and horizontal
tabs, as shown in previous figure.
To remove macros from the programmer select the macro and then press the
removal command ( ) that lies at the bottom of the grid.
Q_PDS_DM_006_V1.3
After being placed on the scheduler grid, Macros immediately will present a yellow
warning symbol, meaning that something is not right.
26
ArQoS Version 1.1.0
Macros in conflict (macros with overlapped modules or

with lack of modules indication)
Table 3 Tests States
Typically, the correction of this state is to select the macro in question and then, in
the lower area for allocation of ArQoS modules, drag to each of box the appropriate
modules. Unlike what happens in the configuration of Interactive Tests, here are only
shown the cases of virtual modules that are really necessary. You must fill all the
boxes with ArQoS Probe Modules. This process has to be executed for all the
programmer macros. As already happens in interactive tests, you can only assign
one ArQoS module to each virtual box module. However, it is possible to repeat
ArQoS modules in macros that are executed at different moments in time.
The error indicated in the table above may also occur if two macros share the same
module that is being used at the same time. This may happen, for instance, when
two macros that already have all the ArQoS Probe Modules allocated are moved in
the programming grid to a position where their executions time overlaps. In this case
the modules in conflict should be changed, or the macros moved to positions that do
not overlap.
As already happens in the Interactive Tests, a double-click in the list of ArQoS Probe
Modules provides access to a window positioned at the RM module. A double-click
on other Probe Modules from the list simply updates the information in the RM
window, no more windows are opened.
Q_PDS_DM_006_V1.3
Changes to a test are only complete if the user saves it, by using the 'Apply' button at
the right bottom. However, no changes can be recorded to a test that is being used
on a scheduled test (described below). In that case it can be saved as a new test.
27
4.6.4
ArQoS Version 1.1.0
Tests Array
The test screen is complemented by the tabulator Creation Matrix Test' that lies
behind the list of available tests. In this area the user can quickly configure a new test
by automatically combining existing modules and macros.
This area is only active after creating a test ( ) or after the selecting a test from the
list of tests. The following figure presents an example of usage of the Creation of
Tests Array.
Figure 25 - ArQoS Tests Array
Its use is fairly simple and straightforward: user chooses the macros he wants to use
in the test from the list of macros that appears at the top. It then indicates which
ArQoS modules should be involved in this test.
Q_PDS_DM_006_V1.3
User must also indicate the type of matrix of tests to create: a new matrix, by adding
at the end of an existing test (which may or may not have been created through a
Tests Array) or by inserting the array of tests to create in the middle of a test that
already exists. In the latter case, the macros that might be affected are 'pushed'
forward in the timeline of the test. Besides this option, the user must specify a
maximum limit time for the test set, i.e., the test will have a total duration not longer
than the value indicated. It is also possible to state whether the array of tests to
create can or cannot contain repetitions.
Finally, the command 'Create Automatic Matrix' generates an array using the
selected macros and modules.
28
ArQoS Version 1.1.0
One advantage of creating Matrix-Test is the possibility to edit Macros in the built
test, adding macros manually, or removing and/or modifying the layout of the macros
automatically generated. Furthermore, it is also possible to use an existing test and
complement them with one or more array tests.
Q_PDS_DM_006_V1.3
Editing ArQoS Probe Modules assigned to each macro on the Programmer Testing
Grid is done in the same manner as described in the previous paragraph: just select
the macro in question, query or change its values in the lower area of modules
assignment.
29
4.6.5
ArQoS Version 1.1.0
Calendar
After Test setup, its now possible to schedule it. This operation is done on-screen
Calendar, as exemplified in the following figure. A schedule is, by definition, a test
with date and time assigned for execution.
Figure 26 - ArQoS Calendar

The area identified in 1, in the left part of the figure, presents a calendar which may
or may not contain underscored days. The underlining indicates that there are
scheduled tests to be executed on that day. By default, the date shown is the current
day, but the user can select any day in the past or in the future.
Area 2 contains the scheduling program. Each block represents a programmer on a
schedule or set of schedules of the same type. There is only one schedule per line.
There can be multiple schedules on the same day, and may even exist schedules
that last for several days, but the programmer are only hsows at most one day at a
time.
Q_PDS_DM_006_V1.3
It can also happen that in the calendar there are some underlined days, and when
selecting that day no test appears on the programmer. This means that existing
schedules belong from another user and, but the current user has no permissions to
query the type of activity. In those cases, a marked day still represents that there is
or was scheduled activity for that day.
A feature of the programmer is that it automatically positions the line with the
schedule that is being consulted, with no need for the user to drag the horizontal
scroll to find the schedule for that day.
30
ArQoS Version 1.1.0
The programmer is used for adding, removing and putting tests asleep. For each new
test a new line is added on the programmer.
The area marked with 3 displays the list of tests that are available for creating
schedules. Tests can be public or private and it's possible to filter only private or
public by using the commands above the list. You can also open a specific test by
double-clicking on it. A new window will be opened with the Tests screen and the
details on the selected test.
The Area 4 allows users to configure rules for a more detailed schedule. This area
will be described in greater detail next.
Creating a schedule is made by drag a drop a test to the grid of the programmer, as
exemplified in the next window.
Figure 27 - ArQoS Calendar - Schedulling Creation
Its only possible to drag a test for an empty row of the programmer. If you need to
create more lines, use the command
to create them and then drag the test to test
the grid. To remove a schedule, select the unwanted test and press the button .
Q_PDS_DM_006_V1.3
Each schedule can be configured in more detail in Area 4 as shown in the following
figure. This area can be increased for better presentation, using the 'handles' that
appear in the middle of the horizontal tab, as shown in the figure.
31
ArQoS Version 1.1.0
Figure 28 - ArQoS Calendar - Scheduling Configuration
When setting a schedule, the system suggests a name attribute. Its recommended to
use a name that has a concrete meaning and easy of reading in the programmers
scale.
The user can define more precisely the date of beginning of the schedule, either by
editing the date and time, by selection on the calendar that appears aside, or by
choosing 'Schedule Now', which means that the schedule will start immediately after
pressing the button Apply.
Furthermore, users have the possibility to consult the modules that will run the test.
Its also possible to double click on an ArQoS module in the displayed list to go to the
RM and easily check the configurations of the module.
4.6.5.1 Recursive Tests
Q_PDS_DM_006_V1.3
One possibility that users have is to define rules to repeat schedules. In this case, the
schedule shall be classified as recursive. There are several rules of recursion that
are almost self-explanatory. Tests can be scheduled consecutively or periodically. In
this case, the frequency can be supplied in hours, days, weeks or months. The user
must also indicate how to cease scheduling cycle: after a certain number of
occurrences or after a specific date and time. The button 'Preview recursive test'
allows users to view the schedule in the recursive programming schedule.
The recursive schedules can be expanded or compressed through the commands
and
to show or condense tests area. These buttons are only available for
recursive schedules. The following figure shows an example of expanding a
recursive scheduling. Darker blue areas indicate the times when the tests are
actually being executed.
32
ArQoS Version 1.1.0
Figure 29 - ArQoS Calendar - Recursive Schedulling
The classification of recursive scheduling only serves to help the user to create
repetitive schedules of tests according to a given rule. It has no influence on the
performance of a test nor is reflected in the presentation of results, where all
schedules are individual and schedule resources are shown in multiple individual
schedules.
To conclude, the schedule must be saved before navigating to another area. Users
are notified if trying to run a command that involves the potential loss of unsaved
settings.
The programming grid has several graphic symbols that help to reflect the current
state of a schedule: saved, running, running with error or success, etc. The following
table lists the multiple states and their meaning.
All tasks scheduled successfully

Error in scheduling tasks
Scheduling/Module programming failed
Scheduling/Module programming success
Scheduling conflicts (use of overlapping modules)
Scheduling successfully saved
Sleeping schedule
Q_PDS_DM_006_V1.3
Table 4 - Scheduling States
33
4.6.6
ArQoS Version 1.1.0
Results
The results screen enables users to see Test Results, query details of each
performed task and, whenever possible, the related CDRs. The following figure
shows a possible results screen.
Figure 30 - ArQoS - Results
Q_PDS_DM_006_V1.3
Basically, the window is divided into five separate areas:
Area 1: List of performed tests and overall status. This list is paged, and, by
default, ordered chronologically, from the most recent to the oldest test. This
list is provided with search engines. You can choose to filter only failed tests,
using the 'See only alerts'.
Area 2: List of macros executed on the test. Information in this list depends on
the test user selected in the previous list. Similar to the previous list, you can
also search the list and choose to see only macros that have not gone well.
Note that in the shown example, there are two macros with the same name.
This only means that the test was composed of two equal macros..
Area 3: lists tasks performed by the macro selected in the previous area.
Here too its possibility to search and filter only the results with errors.
Area 4: This area can be subdivided into two parts: test summary and
additional information of the macro. The test summary is only displayed when
users select a test that will ascertain the number of tasks of the test and how
many were planned and executed successfully or with error. Additional
information of the macro is shown only when users select a macro, showing
which ArQoS modules were chosen for the macro in question
34
ArQoS Version 1.1.0
Area 5: This area contains three types of information: CDRs associated with
the macro selected, detailed information about the outcome of the selected
task and information about the properties of the task that was performed. The
following figure shows some examples of this information.
Figure 31 ArQoS Results Result Details
Figure 32 - ArQoS Results - Property Details
Q_PDS_DM_006_V1.3
As can be seen in the examples, tests, macros and tasks are accompanied by
symbols that represent their states. The following table decodes its meaning.
Test / Macro / Task successful results
35
ArQoS Version 1.1.0
Test / Macro / Task results failed

Schedule programming failed
Schedule programming succeeded
Scheduled test but not programmed yet
Table 5 - Result Status
4.6.7
Reports
This module allows extracting reports on tests results. The following figure shows an
example of use.
Figure 33 - Reports
In Area 1 users select the report type. In Area 2 filtering conditions can be specified
and its also possible to exports obtained results to a worksheet.
The bottom area may be increased by using the 'handle' that is in the middle of the
page, this way showing or hiding Area 1.
Information presented in the report is in accordance to the filtering options. These
conditions are additive, i.e., using the example of the previous figure, the results
obtained correspond to the period between 9:00 oclock on day 01/28/2010 and
12:59 from the same day, and which have been obtained by the test MOC probes
'2'and executed by the module' Peak: May: MC8775V: P ...', etc.. Only after selecting
the command 'Search' is being produced the report. If no results conform to these
conditions, the user will be informed.
Q_PDS_DM_006_V1.3
The following figure shows the window when a user access 'Options' command.
36
ArQoS Version 1.1.0
Figure 34 - ArQoS Reports - Filters
Q_PDS_DM_006_V1.3
For each report set, users can select the fields he wants to be presented. Also the
presentation order filed and the ordering criteria (ascending/descending) can be
selected in the same window. The number of results per page is also configurable.
Notice that too many results per page may appear slow in loading the data. Changes
take effect only after pressing the command 'Search' again.
37
ArQoS Version 1.1.0
5 Common Problems and Solutions

5.1
Cannot access the system
Figure 35 - Login Problem 1
Identification: When trying to access the system, at the login page, the message
"Credentials Invalid!" is always returned.
Characterization: This error may be related to a password input error or lack of

permissions to access the system.
Solution: Contact your system administrator or manager to check the

permissions.
5.2
Submit button is invisible or inaccessible.
Q_PDS_DM_006_V1.3
Figure 36 - Login Problem 2
Identification: When trying to access the system button 'Submit' is invisible or

inaccessible.
Characterization: This error can occur after an upgrade or reboot of the server.
Solution: Clean the browser cache and try again. If the problem persists, contact
your system administrator or manager.
38
5.3
ArQoS Version 1.1.0
Button Close in ArQoS (also RM or SM) doesnt perform logout
Figure 37 - Session Expired Problem
Identification: When trying to close a module (ArQoS, RM or SM) with the button
'Close' the window does not close and you can not do anything else.
Characterization: This problem may occur if there is any idle time of application.
In this case, the user session ends and your browser cease communicating with
the server where the application resides. No more pressed commands will
execute.
Solution: Close the window CTRL + F4 (or Alt + F4 if an independent window)

and go to the page selection of applications (Application Selection Page). Choose
again the module in question. If you get the message expired session will have to
log in again.
5.4
Error message on running a test
Figure 38 - Interactive Test Problem
Q_PDS_DM_006_V1.3
Identification: I created an interactive test but when trying to run it I always get a
message reporting that the physical module is not specified.
Characterization: This problem may occur if use tasks that provide links to other
virtual modules and dont identify no physical module for these virtual modules. For
example, the task only uses the module A to make and end a call, but the task of
making call indicates that the destination is the module B. If you do not indicate any
physical module in B, you will get this error.
39
ArQoS Version 1.1.0
Solution: Check the configuration of tasks and make sure that all the modules listed
in the task (A, B, C, D, E or F) have physical modules mapped.
5.5
I get an error message when trying to read a test
Figure 39 - Script Response Problem
Identification: When trying to read a test the browser reports an error message on
the script.
Characterization: This message occurs whenever the server application is taking
too long. This typically happens at reading tests with many macros or at creating an
array of tests that involve many modules and/or macros.
Q_PDS_DM_006_V1.3
Solution: Select 'Continue' for the read request until its completed. Depending on
the complexity of the test, it may happen to receive this message several times.
40

Rua Eng Jos Ferreira Pinto Basto
3810-106 Aveiro - Portugal
Tel: +351 234 403 200
Fax: +351 234 424 723
ISO 17025 - LABORATRIOS ACREDITADOS

CETLAB - Laboratrio de Redes Privadas e Terminais
CETLCE - Laboratrio de Calibrao e Ensaio

Users Guide

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Users Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

ARQOS NG

Portugal Telecom Inovao, S.A.

Users Manual: V.1.0: May 2010

Portugal Telecom Inovao, S.A.

Portugal Telecom Inovao, S.A.

Portugal Telecom Inovao, S.A.

Access control system SCA

Management and Configuration of Managed Elements

Common Problems and Solutions

Cannot access the system

Submit button is invisible or inaccessible.

Button Close in ArQoS (also RM or SM) doesnt perform logout

Error message on running a test

I get an error message when trying to read a test

Portugal Telecom Inovao, S.A.

Error! Reference source not found.

Portugal Telecom Inovao, S.A.

ArQoS Version 1.1.0

Error! Reference source not found.

ArQoS Version 1.1.0

Login and applications selection page component

Access Control System component

Site Manager component

Resource Management component

At the end is presented a list of common problems and solutions.

Portugal Telecom Inovao, S.A.

Error! Reference source not found.

ArQoS Version 1.1.0

ArQoS NG system allows the operator to make performance monitoring test

Portugal Telecom Inovao, S.A.

Error! Reference source not found.

ArQoS Version 1.1.0

Figure 1 ArQoS NG - Architecture

Portugal Telecom Inovao, S.A.

Error! Reference source not found.

ArQoS Version 1.1.0

Access control systems SCA

A more detailed description is presented below.

The Management System ArQoS NG is accessed through a central point. To simplify

Figure 2 - Login page

Portugal Telecom Inovao, S.A.

Error! Reference source not found.

ArQoS Version 1.1.0

Figure 3 - Application Selection Page

Figure 4 - Quick menu for module navigation

Portugal Telecom Inovao, S.A.

Error! Reference source not found.

ArQoS Version 1.1.0

Access control system SCA

Portugal Telecom Inovao, S.A.

Error! Reference source not found.

ArQoS Version 1.1.0

Figure 5 - Site Manager

Portugal Telecom Inovao, S.A.

Error! Reference source not found.

ArQoS Version 1.1.0

Figure 6 - Element Type Selection

Figure 7 Insert New Element

Portugal Telecom Inovao, S.A.

Error! Reference source not found.

ArQoS Version 1.1.0

Figure 8 - Resource Manager

Navigation on RM is performed through the buttons identified inside yellow oval of

Management and Configuration of Managed Elements