FCM9002 USER MANUAL
76-02-095 Rev.B
Page 136 of 145
4.7.2.4.4.1 Background Rate
When multiple flows are being tested, the SAM module will select the flow that is
not in foreground and has highest configured CIR. The background Rate menu
setting defines the amount of background traffic based on percentage of CIR.
For example,
Tesing flows 1-3 where they are defined as follows
Flow 1, CIR=50M, CBS=10k, EIR=50M, EBS=10k
Flow 2, CIR=50M, CBS=10k
Flow 3, CIR=10M, CBS=10k, EIR=10M, EBS=10k
While testing flow 1, flow 2 with the CIR of 50M will be selected as the
background stream. When testing flow 2, Flow 1 will then be selected as the
background stream.
The background rate is defined as a percentage of the CIR
Eg
CIR = 50M, 95% = 47.5M
Generating background traffic allows the test to validate that the link has not
been over provisioned for CIR traffic.
4.7.2.4.4.2 Go/No Go Test
The purpose of the Go / No Go test is to provide a quick test to validate that the
flow has actually been provisioned and that a loopback is actually available.
The Go/No Go test starts will a low traffic rate and slowly ramps the traffic rate up
to the configured value. The test starts by sending traffic at 10% of the flow CIR
and ramps up to 90% of the CIR in 10% steps.
The Go/No Go Test monitors the received traffic and if the SLA cannot be
achieved at any of the transmission rates, the test will fail. If the SLA is met, then
the next test phase can continue.
4.7.2.4.4.2.1
Go/No Go Test Time
The Time menu item defines the time spent in each step of the test. The time is
defined in seconds. Generally, as the go/no go test is intended to provide a
quick check that the service is available this time should be kept short, and 30 to
60 seconds would provide a good balance taking between 5 and 10minutes to
run the full go/no go test