P.

1 of 5
1 Performance KPI on Alcatel-Lucent 5620 SAM
1.1 5620 SAM Statistics
The 5620 SAM can be configured to collect statistics counters from managed NEs and from
the 5620 SAM servers. These statistics are typically used for monitoring and troubleshooting
on the 5620 SAM, and for SLA and billing functions performed by OSS applications
connected to the 5620 SAM.

Statistics can be viewed directly on the 5620 SAM as tabular or graphical data, and can be
exported to OSS applications via the 5620 SAM-O interface. Tabular and graphical data
viewed on the 5620 SAM can also be saved as .csv, .html, or .jpeg files.

Before the 5620 SAM can collect statistics, policies must be configured to specify:

On which network objects to collect statistics
Which counters to collect
The rate of collection
How long to retain collected statistics in the 5620 SAM

After the policies are configured, collection begins.

When NEs are discovered in the 5620 SAM, MIB statistics policies can be applied to enable
performance statistics on the NE without further operator intervention.

Collected statistics are viewed in the 5620 SAM GUI by navigating to the desired object and
viewing the statistics from the Statistics tab on the object properties form. Statistics are
collected either by polling the MIB counters or by transferring accounting files from NEs
(where this is supported by the NE, for example, SR OS-based NEs). Statistics for the
performance of the 5620 SAM servers are collected internal to the server.

MIB-based and SAM server performance statistics are available for collection and graphing in
real time, and are available for on-demand collection where a new record is added each time
the Collect button is clicked. Accounting statistics are not available for real-time or on-
demand collection.
Statistics scheduled by a statistics collection policy or collected on-demand are stored in the
5620 SAM database and are available to all operators. Statistics collected for real-time
display are available only for the duration of the session and to the operator that initiates the
session. Real-time statistics are not stored in the 5620 SAM database.

The 5620 SAM supports the following statistics types.

Performance statistics.
Accounting statistics.
SAM-server performance statistics





P.2 of 5
Statistics are stored in the 5620 SAM database for a configurable length of time. The time to
retain statistics is defined in a statistics log policy on the 5620 SAM. After the retention time
is exceeded, the statistics are removed from the database.

1.1.1 Performance statistics
Performance statistics are counters that typically provide information for monitoring and
troubleshooting purposes on physical equipment, routing, and other aspects of the NE.

Performance statistics counters are collected from MIBs on the NEs using the SNMP protocol.
The statistics can be collected on-demand or scheduled for regular collection using an NE or
specific collection policy.

Performance statistics can be collected and graphed in real time. Historical performance
statistics stored in the 5620 SAM database can be viewed as tabular or graphical data.

Performance statistics are stored in the 5620 SAM database and can be exported via the
5620 SAM-O interface.

1.1.2 Accounting statistics
Accounting statistics are counters that typically provide information for billing or SLA
purposes for services or subscribers.

Accounting statistics are collected from files stored on Alcatel-Lucent SR OS-based NEs
managed by the 5620 SAM using FTP or SCP.

Accounting statistics are scheduled for collection using accounting policies. Accounting
statistics also require the deployment of a file policy to the NEs to instruct them on how to
store the data on the NEs.

Historical accounting statistics stored in the 5620 SAM database can be viewed as tabular or
graphical data.

Accounting statistics are stored in the SAM database and may be exported via the SAM-O
interface. The following accounting statistics types are supported:

Service accounting statisticscollected on every queue on every SAP linked to an
accounting policy. Service accounting statistics provide queue throughput and drop
information and can be used to provide billing and SLA information.
Network accounting statisticscollected on every queue on every SDP or collected
on network ports linked to an accounting policy. Network accounting statistics
measure usage within each forwarding class queue, defined on the network port. This
information is used to monitor link utilization and network traffic patterns and trends,
which helps with capacity planning and traffic engineering.



P.3 of 5
Subscriber accounting statisticscollected on a subscriber profile for residential
subscriber instances. Subscriber accounting statistics are used for billing and SLA
information.

1.1.3 Statistics presentation
The 5620 SAM provides several convenient methods to view statistics depending on the
operators needs.

Statistics can be viewed as numerical data in a table, which is useful for getting exact values.
The tabular data can be sorted, filtered, and exported to .cvs and .html files.

Statistics can also be viewed in graphical format to more clearly see trends in the data.
Multiple statistics counters can be displayed on one graph and each graph can have multiple
independently scaled axes. This allows operators to compare, on the same graph, statistics
with very high numbers (for example, throughput) with statistics with very low numbers (for
example, dropped packets). Graphs can be exported as .jpg or .png files.

All statistics types supported by the 5620 SAM (performance, accounting, and SAM server
performance) can be graphed and viewed in tabular form.



1.2 Service Assurance
The 5620 SAM service assurance system provides the ability to group various OAM tests into
test suites for network troubleshooting and to verify compliance with SLAs. Network
administrator can schedule the periodic execution of a test suite to provide continual
performance feedback, or run a test suite on demand to investigate service issues. The 5620
SAM archives test-result data for monitoring and trend analysis purposes.

The grouping of tests into a test suite (Error! Reference source not found.) allows a 5620
SAM operator to use one schedule for the periodic execution of multiple OAM diagnostics
against multiple network objects; for example, services, devices, or network transport
components. An operator can choose to include existing tests, use the 5620 SAM to
generate the tests that comprise a test suite, or both. Groups of tests in a suite can be
configured to execute sequentially or concurrently.




P.4 of 5


Figure 1: 5620 SAM-driven scheduled OAM tests


1.2.1 Test Policies
To enable the automatic generation of tests for a test suite, the 5620 SAM requires a test
policy that contains a set of test definitions and pre- and post-processing rules. A test policy
also specifies the order of execution for the generated tests. A test policy applies to only one
test suite, and a test suite has only one test policy associated with it.

A test policy is specific to one type of entity; for example, a VLL service or service tunnel. The
test definitions in the policy are restricted to the tests that apply to the entity type specified
in the policy. A test policy is applied to a test suite during test suite creation. The figure
below shows the test policy creation form.

1.2.2 Test Suites

A test suite contains three test groups:

First-run tests
Generated tests
Last-run tests

First-run tests are the tests in a suite that the 5620 SAM executes before the tests in the
other groups. First-run tests are chosen from a list of existing tests and might typically
include high-level diagnostics; for example, a service site ping or VPRN ping. No restrictions
apply to the types of tests that are selectable as first-run tests.

Generated tests are created by the 5620 SAM for use against a particular network entity,
based on the type of entity specified in the suite and the information in the associated test
policy. For example, a policy that specifies a service site ping as a test definition is associated
Test Manager
Test Policy Test
Suite
Test Result Test Scheduler



P.5 of 5
with a test suite for a VPRN service that has three sites. The 5620 SAM thus generates six
tests: one site ping test from each site in the VPRN to the other sites.

Last-run tests are the tests in a suite that the 5620 SAM executes after the tests in the other
groups. Last-run tests are chosen from a list of existing tests and might typically include
transport-layer diagnostics; for example, an LSP trace or a tunnel ping. No restrictions apply
to the types of tests that are selectable as last-run tests.

The use of test suites offers a high degree of configuration flexibility. The inclusion of tests in
any group of a test suite is optional. When you specify that no network entity is associated
with a test suite, the test suite is limited to the first-run and last-run test groups. In this way,
you can create a group of disparate tests to which no test policy restrictions apply.

To manage the system resources that test execution consumes, the 5620 SAM assigns a
weight value to a test. When the 5620 SAM executes a test, it attempts to reserve the test
weight from a resource pool, performs the test, then returns the test weight to the pool. The
weight of a test suite is the sum of the weights of the individual tests in the suite. The 5620
SAM attempts to reserve the weight of the whole suite for the duration of suite execution. If
the required weight for a test or test suite is unavailable, execution is halted and the Status
value contained in the test result is set to Not Enough Resources.