Scaling guidelines for scheduled tests (STM)
Scaling guidelines for scheduled tests (STM)
Scaling guidelines for scheduled tests (STM)
5620 SAM provides the ability to generate, manage and schedule STM tests within the
network. This section provides guidelines that can be used to determine the extent to
which STM tests can be scheduled and launched within a network.
There are a number of factors which will influence 5620 SAM’s ability to concurrently
manage and schedule a large number of tests. 5620 SAM keeps track of how many tests
are running concurrently. This is to limit the initiation of the tests, and the processing of
the results without interfering with the system’s other functions.
To understand the STM guidelines, the following terminology is required:
Elemental Test
: An OAM test to be sent to a router such as an LSP ping
Elemental Test
Result: An OAM test result received from a network element
Accounting file Test
: An OAM test that is initiated in the default manner, however, the test
results are retrieved from the network element via FTP on a periodic basis.
Test Policy
: A definition or configuration that tells 5620 SAM the specifics about how to
generate a test. A test policy can contain multiple test definitions. The policies are used by
test suites.
Test Suite
: A collection of elemental tests that can be assigned to a specific schedule.
There are three defined sections in which tests can be placed within a test suite: First run,
Generated and Last run. The tests are executed in order by these sections. It is possible to
configure the execution order of tests within the First Run and Last Run sections to be
parallel or sequential. The tests in the Generated position are run by the system as
concurrently as possible. If the Generated section contains tests from several different test
definitions, then all the tests belonging to one definition will be executed before the tests
of the next definition begin. Within a definition, the system will attempt to execute the
tests as concurrently as possible. This is important to note, as a test suite containing a
large number of tests in the Generated section (or in the First Run/Last Run sections set to
parallel) may tax the system. Part of the increased stress placed on the system by
concurrent tests is a result of the need for the system to use greater amounts of resources
in order to initiate, wait for and process many tests concurrently. As well, tests that result
in a large amount data to be returned from the routers will place increased demands on the
5620 SAM.
Scaling
Scaling guidelines for scheduled tests (STM)
Scaling guidelines for scheduled tests (STM)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-16
5620 SAM
3HE-09809-AAAG-TQZZA 13.0 R7
Issue 1
December 2015
