The recommended approach for scheduling these tests suites is as follows:
•
Test suites T1, T2, T3, T4 can be scheduled on the hour and repeat every 10 minutes
•
Test suites T5, T6, T7, T8 can be scheduled on the hour + 5 minutes and repeated
every 10 minutes
This will ensure no more than 200 elemental tests are scheduled to run concurrently.
Factors impacting the number of elemental tests that can be executed in a given time frame
The following factors can impact the number of elemental tests that can be executed
during a given time frame:
•
The type of tests being executed. Each type of elemental test takes varying quantities
of time to complete (e.g. a simple LSP ping of an LSP that spans only two routers
may take less than 2 seconds; an MTU ping could take many minutes).
•
The amount of data that is generated/updated by the test within the network elements.
5620 SAM will have to obtain this information and store it in the 5620 SAM
database. The quantity of data depends on the type of tests being performed and the
configuration of the objects on which the tests are performed.
•
The number of test suites scheduled at or around the same time
•
The number of tests in a test suite
•
The number of routers over which the tests are being executed. Generally, a large
number of tests on a single router can be expected to take longer than the same
number of tests distributed over many routers.
•
A 5620 SAM Database backup may temporarily reduce the system’s ability to write
test results into the database.
•
The workstation used to perform the tests will dictate how many physical resources
5620 SAM can dedicate to executing elemental tests. On the minimum supported
workstation (collocated 5620 SAM Server and 5620 SAM Database on a single
Server), the number of concurrent tests must be limited to 1,00.
Possible consequences of exceeding the capacity of the system to perform tests
5620 SAM will exhibit the following symptoms if the number of scheduled tests exceeds
the system’s capacity.
Skipped Tests:
If a test suite is still in progress at the time that its Schedule triggers again, then that
scheduled task will be marked as skipped and that test suite will not be attempted again
until the next scheduled time.
Scaling
Scaling guidelines for scheduled tests (STM)
Scaling guidelines for scheduled tests (STM)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-20
5620 SAM
3HE-09809-AAAG-TQZZA 13.0 R7
Issue 1
December 2015
