rate (Chatter module only)

Defines the test frequency for this type of active measurement test.

Important: This measurement rate applies to all CNA agents in the Chatter network performing this type of test. It is not the measurement rate between two specific CNA agents.

rate <value> {per-second | per-minute | per-hour | per-day}

no rate

Must be in Chatter Active Measurement Configuration mode. For information on how to access this mode, see Accessing and exiting command modes.

Use once.

5 tests per minute

Defines the test frequency for this type of active measurement test.

Important: This measurement rate applies to all CNA agents in the Chatter network performing this type of test. It is not the measurement rate between two specific CNA agents.

Defines the overall measurement rate for this type of active measurement test conducted across the Chatter network.

The no command restores the default measurement rate of 5 tests per minutes.

There is a trade-off between setting the test rate:

• High enough to quickly detect down links and other problems

AND

• Low enough so that all of the tests together do not generate a load that exceeds the hive or end point capacity.

In the ideal case, with unlimited capacity, set the rate based on the zone hierarchy as follows:

1. Follow down the levels of the hierarchy. At each branch point, add the number of paths as follows:
• For each two-way branch, add 2 paths.
• For each three-way branch, add 6 paths.
• For each four-way branch, add 12 paths.
• For each five-way branch, add 20 paths.
• Do not add any for zones that contain endpoints instead of subzones.
2. Divide the total number of paths by the number of minutes desired between tests.

For example, 100 paths to be checked every minute means a rate of 100 tests per minute. If two minutes between tests is acceptable, then 50 tests per minute is sufficient.

To find the best rate for your system, Avaya recommends the following steps:

1. Start the system with the default setting (5 tests per minute).
2. Wait a while and then look at several links and note the Inter Arrival Time (time between tests).
3. If the Inter Arrival Time is too long, restart the system with a higher rate.
4. Look at the link test spacing and the drops to see if tests are being dropped. If tests are being dropped, the total frequencies (for all types of tests) is too high.
5. Raise the frequency if the system can handle it.